MINI MINI MANI MO
/ $Header: rdbms/mesg/error.txt /main/131 2016/09/25 16:57:55 jdavison Exp $ error.txt
/
/ Copyright (c) 1987, 2016, Oracle and/or its affiliates. All rights reserved.
/
/ The quality and value of the error messages you write can be ensured by
/ applying the Error Message Writing Guidelines located at the following link:
/
/ https://confluence.oraclecorp.com/confluence/display/SCMS/Error+Message+Writing+Guidelines
/
/ Copyright (c) 1999, 2017, Oracle and/or its affiliates. All rights reserved.
/
/ NAME
/ e0.msg
/ DESCRIPTION
/ Error messages for Oracle
/ NOTES
/ Language : American
/ Character set : US7ASCII
/
/ List of ORACLE errors
/
/ This file is converted to header/message files using lmsgen.c.
/
/ The first col is the ORACLE error number.
/ The second column is reserved and must (for now) be x00000.
/ The remainder of the line is the error text (max 76 characters).
/
/ Adding an error:
/ Check out this file, add the error, and check it back in.
/ Error numbers should always be ordered.
/ The second column should always be x00000.
/ Pseudo-error debugging events:
/ Error codes 10000 .. 10999 are reserved for debug event codes
/ that are not really errors.
/
/ MODIFIED
/ ansriram 10/13/17 - bug26482601- change error message for ORA-160
/ nrcorcor 06/14/17 - review comment - change error message
/ rankalik 04/10/17 - BUG25256476: Adding error messages for XE
/ cwang 02/10/17 - add 39511 39512
/ nmacnaug 07/28/16 - remove USE_INDIRECT_DATA_BUFFERS error messages
/ nmuthukr 11/17/15 - add gen1 process
/ adalee 03/08/16 - Bug 22808010: reword ORA-241
/ zhefan 12/08/15 - Bug 22161812: Added message 00764.
/ ashahu 07/01/15 - Bug 21189257: added error OER(143)
/ nmuthukr 06/16/15 - add MGA heap related error messages
/ nlee 05/26/15 - Add 511 error for LMFC process.
/ nrcorcor 05/17/15 - Bug 20885151 - error message refers to log, used in
/ two situations
/ nmuthukr 05/06/15 - add MGA errors
/ jgiloni 03/23/15 - Quarantine
/ surikuma 03/12/15 - forward listener
/ surikuma 03/05/15 - pdb listeners
/ kishykum 02/27/15 - Bug 20640579: Add errors for cancel_sql and
/ dequeue_parallel_statement
/ nrcorcor 01/13/15 - Bug 13539672/Project 41272 New lost write protection
/ zhefan 12/17/14 - Bug 20088066 : System parameter
/ _suspended_session_timeout seems not work
/ nmuthukr 11/25/14 - add prespawn related errors
/ surikuma 10/29/14 - lreg default network
/ jgiloni 06/12/14 - Add exit error message for PMON slaves
/ nmuthukr 04/25/14 - add prespawn not enabled error
/ jajapate 03/18/14 - Bug 6837816 - Fixing comment for 00601
/ jgiloni 03/17/14 - Add exit error messages for CLMN & PMAN
/ mawatts 03/12/14 - bug 18246644: fix outdated references in ORA-00257
/ rrungta 10/14/13 - Add error code for alive background process
/ mcoulter 08/13/13 - bug 16654560, change atleast -> at least in message
/ 371.
/ jgiloni 04/24/13 - Bug 16624893: shared_servers enable/disable per-PDB
/ aikumar 08/15/12 - Add OER 46 & OER 47
/ rthammai 06/19/12 - fix type
/ jdavison 05/31/12 - Fix messages with incorrect action format
/ nrcorcor 05/24/12 - bug 12979281 - disambiguate 3020 errors
/ jooskim 05/14/12 - bug 13482047: ora-45 for kill session noreplay
/ sanselva 05/03/12 - add new error code for FENC death
/ vpantele 03/23/12 - add ORA-388
/ rthammai 03/23/12 - update ora-66
/ smcgee 02/14/12 - Change 00742 to use "%s
/ jgiloni 07/26/11 - connection_broker parameter errors
/ surikuma 09/05/11 - add ora-500: error message for LREG
/ shsong 08/11/11 - add error code 742
/ jgiloni 07/13/11 - Error range for connection broker
/ yuli 03/02/11 - modify 285
/ vzsridha 02/06/11 - add ora-499: raised when XDMG fails to initialize
/ repeatedly
/ sanselva 01/26/11 - proj33056: ORA-851 for RMON termination
/ vgokhale 01/12/11 - Add OER-387
/ mmpandey 05/20/10 - 9714832: modify ADRCI Note, per new requirement
/ mmpandey 05/13/10 - 9713537: modify ORA-00600 Cause/Action message
/ vpantele 02/26/10 - ORA-244 and 245
/ vzsridha 04/25/09 - add exit error for XDMG process
/ jjlee 03/03/09 - add ORA-241
/ clhsu 02/23/09 - add a new process 496
/ adalee 01/08/09 - add ORA-495
/ kgiyer 11/15/08 - Bug-7503836: Shorten text for ORA-336
/ kgiyer 05/20/08 - Bug-6746478: add OER 242 and 243
/ vpantele 09/05/08 - fix ORA-752
/ rlong 08/07/08 -
/ jgiloni 08/04/08 - Add 135-139
/ jjlee 07/15/08 - comment change
/ jiashi 06/05/08 - update ORA-235
/ mcoulter 03/27/08 -
/ clhsu 03/07/08 - bug6513336: change ora-494 to conform language rules
/ shsong 02/13/08 - enhance OER 336 message
/ pbagal 12/06/07 - add inst. type to 99
/ mcoulter 11/21/07 - BUG 6603046 - need to handle more error paremeters
/ (9)
/ slahoran 10/22/07 - bug/6327593 : add ORA-44
/ yuli 09/04/07 - RECOVER UNTIL CONSISTENT
/ kesriniv 08/03/07 - add ORA-66 for ksp-invalid-sid msg
/ bbaddepu 08/01/07 - add 848-850
/ vpantele 04/25/07 - add OER 239, 240 and 494
/ kesriniv 05/08/07 - add ORA-00098 and ORA-00099
/ bbaddepu 04/26/07 - enhance 840 and 839 messages
/ banaras 02/07/07 - lock_sga and memory_target are not compatible
/ bbaddepu 01/19/07 - enhance 845 msg
/ siroych 12/27/06 - add 846
/ kumamage 08/01/06 - add soft internal error
/ rvingral 07/24/06 - add OER(493)
/ tyurek 06/13/06 - define 00491 for RMS0
/ yohu 06/01/06 - add OER(492)
/ bbaddepu 05/23/06 - add 843, 845
/ siroych 05/19/06 - add OER 844
/ bbaddepu 04/30/06 - add 839, 840/1/2
/ siroych 04/11/06 - add OER 837, 838
/ vpantele 02/15/06 - Add error 752 for lost write detection
/ jiashi 03/27/06 - remove OER(343), modify OER(346)
/ avaliani 03/29/06 - incorporate erros_us feedback
/ ramekuma 02/23/06 - ddl_waitlock: update definition of ORA 54
/ ltominna 01/25/06 - remote op fail error OER(43)
/ avaliani 11/21/05 - reserve OER(39)
/ bbaddepu 07/13/05 - add diag events notes
/ seeda 06/30/05 - 4226133: ORA-64 doesn't report caller description
/ mjstewar 06/24/05 - add OER(751)
/ yuli 06/23/05 - add 725
/ jiashi 02/25/05 - modify OER(63), obsolete OER(66)
/ hmankude 02/03/05 - Bug 4160349: new msg for ckpt death
/ jiashi 12/16/04 - modify messages for 216, 217, 219
/ kumamage 12/14/04 - add message for 453
/ avaliani 11/30/04 - add OER(569)
/ pokumar 09/08/04 - add event 833
/ pokumar 07/15/04 - add message 832
/ wojeil 07/27/04 - bug-3449667:add error message for enabling
/ USE_INDIRECT_DATA_BUFFERS on non-VLM platforms
/ pokumar 06/23/04 - add event 831 for stress testing
/ sridsubr 04/18/04 - Add service name error msg 42
/ tbosman 02/11/04 - numa
/ tbosman 10/02/03 -
/ tbosman 09/20/03 - attach failed
/ tbosman 08/20/03 - add PSP error
/ eyho 05/24/04 - remove OER 99
/ jiashi 05/16/04 - update OER 302
/ rlong 11/06/03 - OSM->ASM
/ tsepez 11/04/03 - RBAL/ORB* termination messages
/ pokumar 10/28/03 - add 830
/ pokumar 10/08/03 - add event 829 for stress testing
/ rasivara 09/25/03 - correct typo in ORA-288 message
/ cluu 08/29/03 - add err msg 105,109,110,111,112,117,118,133,134
/ kpatel 08/18/03 - add error 828
/ pokumar 07/29/03 - add error message 827
/ asundqui 07/14/03 - add Resource Manager abort_sql/kill_session messages
/ pokumar 05/30/03 - change text of 824
/ pokumar 05/01/03 - add sga-tuning error messages
/ pokumar 04/18/03 - enhance ora-371 to include size recommendation
/ tlahiri 03/18/03 - Add sga_target too large message
/ vsrihari 02/27/03 - reuse 397 for instance recovery abort
/ tlahiri 01/23/03 - Add error for MMAN process start failure
/ pritto 12/05/02 - Fix typo in 486
/ lilin 01/06/03 - change messages with thread no. to include instance
/ pritto 12/05/02 - Fix typo in 486
/ kumamage 12/14/02 - add error 450
/ bbaddepu 11/19/02 - modify err msg 218.
/ tlahiri 12/10/02 - Add error messages for SGA tuning
/ jiashi 09/24/02 - add error message 740, 741
/ banand 03/15/02 - recovery thru resetlogs : change 342
/ cluu 10/07/02 - remove unused messages: 117,124,118
/ cluu 10/06/02 - remove unused messages: 105,111,112,120,121
/ swerthei 04/26/02 - block change tracking; add 487 for CTWR
/ yuli 10/03/02 - add 750
/ yuli 09/20/02 - obsolete alter database convert
/ kumamage 09/04/02 - add internal error message
/ pritto 07/01/02 - Only one umbilicus per db instance
/ jarnett 05/10/02 - bug 2314669 - make DX overflow a user error.
/ jwlee 05/08/02 - add error 479.
/ pritto 10/22/01 - Rename PSM to OSM.
/ pritto 10/15/01 - Add OSM Background message
/ wojeil 02/11/02 - adding 385.
/ yuli 01/16/02 - tablespace rename project
/ yuli 02/08/02 - 10i irreversible compatibility project
/ msusaira 12/07/01 - add error messages for H.A.R.D project
/ vkarra 11/20/01 - add error message for auto segment space management
/ smuthuli 10/18/01 - add 478
/ pritto 10/02/01 - Update detached process number range.
/ sdizdar 02/23/01 - added 0217
/ mwjohnso 07/26/01 - modify ora-298 text
/ mjaeger 07/05/01 - bug 479696: 00295: alter db datafile/tempfile <fno>
/ bsinha 07/20/01 - fix distributed autonomous txn
/ ilam 06/18/01 - Add 485 error for DIAG
/ bsinha 06/13/01 - autonomous-distributed interop
/ cluu 04/27/01 - add listener error messages
/ eyho 03/06/01 - RAC name changes
/ qcao 02/14/01 - fix bug 407350
/ anithrak 03/05/01 - Enhance ORA-379 message to add block size
/ vjoshi 12/13/00 - change error message
/ robermar 11/22/00 - Detect Multiple strand redo
/ heneman 10/21/00 - Rename MTS.
/ jarnett 08/17/00 - bug 1217450 - disallow autonomous in distributed
/ vsrihari 07/19/00 - add 299 for block media recovery
/ smukkama 07/20/00 - change 374 - db_block_size must be multiple of 512
/ vsrihari 06/12/00 - add 399 for change vector corruption
/ vsrihari 06/06/00 - fix ORA-396 message argument
/ vsrihari 05/24/00 - add 398 for instance recovery abort
/ tlahiri 05/08/00 - Add dynamic cache error messages
/ smukkama 03/04/00 - Add 380,381,382 - multiple block size project
/ apadmana 01/19/00 - changed SNAPSHOT to MATERIALIZED VIEW
/ eyho 02/14/00 - add 484 error for LMS
/ vsrihari 02/02/00 - add msg 397 for two-pass recovery
/ jarnett 07/02/99 - bug 853211 - allow local transaction disable on V8
/ pogilvie 06/15/99 - testing error 607
/ gcandea 02/11/99 - Add 127 and 128 for ALTER SYSTEM SHUTDOWN
/ robermar 10/22/98 - Error message 396 for two-pass recovery
/ drehfiel 09/10/98 - updating to follow message standards
/ skray 08/28/98 - edit message text for 38
/ skray 08/14/98 - add 37, 38
/ drehfiel 08/13/98 - editing action for message ORA-00001
/ agreenbl 05/28/98 - Fix text for 00093, 00094
/ mcoyle 04/03/98 - Add ops-aware oradebug mesgs
/ mcoyle 03/02/98 - Add errors for ops-aware oradebug
/ emagrath 02/26/98 - Add new archive log/state parameter support
/ mwjohnso 02/17/98 - Add 298 & 299
/ heneman 12/03/97 - Add 2 MTS refuse error codes
/ bchang 09/26/97 - 000439: first character should be lower case
/ tlahiri 09/23/97 - add 379
/ swerthei 08/13/97 - add 296, 297
/-------------------------------------------------------------------------------
00000, 00000, "normal, successful completion"
// *Cause: Normal exit.
// *Action: None.
00001, 00000, "unique constraint (%s.%s) violated"
// *Cause: An UPDATE or INSERT statement attempted to insert a duplicate key.
// For Trusted Oracle configured in DBMS MAC mode, you may see
// this message if a duplicate entry exists at a different level.
// *Action: Either remove the unique restriction or do not insert the key.
/0002 reserved for v2 compatibility (null column)
/0003 reserved for v2 compatibility (column value truncated)
/0004 reserved for v2 compatibility (end-of-fetch)
/0009 reserved for v2 compatibility
/
/ 10 - 49 user session and session switching errors
/
00017, 00000, "session requested to set trace event"
// *Cause: The current session was requested to set a trace event by another
// session.
// *Action: This is used internally; no action is required.
00018, 00000, "maximum number of sessions exceeded"
// *Cause: All session state objects are in use.
// *Action: Increase the value of the SESSIONS initialization parameter.
00019, 00000, "maximum number of session licenses exceeded"
// *Cause: All licenses are in use.
// *Action: Increase the value of the LICENSE MAX SESSIONS initialization
// parameter.
00020, 00000, "maximum number of processes (%s) exceeded"
// *Cause: All process state objects are in use.
// *Action: Increase the value of the PROCESSES initialization parameter.
00021, 00000, "session attached to some other process; cannot switch session"
// *Cause: The user session is currently used by others.
// *Action: Do not switch to a session attached to some other process.
00022, 00000, "invalid session ID; access denied"
// *Cause: Either the session specified does not exist or the caller
// does not have the privilege to access it.
// *Action: Specify a valid session ID that you have privilege to access,
// that is either you own it or you have the CHANGE_USER privilege.
00023, 00000, "session references process private memory; cannot detach session"
// *Cause: An attempt was made to detach the current session when it contains
// references to process private memory.
// *Action: A session may contain references to process memory (PGA) if it has
// an open network connection, a very large context area, or operating
// system privileges. To allow the detach, it may be necessary to
// close the session's database links and/or cursors. Detaching a
// session with operating system privileges is always disallowed.
00024, 00000, "logins from more than one process not allowed in single-process mode"
// *Cause: Trying to login more than once from different processes for
// ORACLE started in single-process mode.
// *Action: Logoff from the other process.
00025, 00000, "failed to allocate %s"
// *Cause: Out of memory.
// *Action: Restart with larger sga heap.
00026, 00000, "missing or invalid session ID"
// *Cause: Missing or invalid session ID string for the current operation.
// *Action: Retry with a valid session ID.
00027, 00000, "cannot kill current session"
// *Cause: Attempted to use ALTER SYSTEM KILL SESSION to kill the current
// session.
// *Action: None.
00028, 00000, "your session has been killed"
// *Cause: A privileged user has killed your session and you are no longer
// logged on to the database.
// *Action: Login again if you wish to continue working.
00029, 00000, "session is not a user session"
// *Cause: The session ID specified in the current operation was not a user session (for example, recursive, etc.).
// *Action: Retry with a user session ID.
00030, 00000, "User session ID does not exist."
// *Cause: The user session ID no longer exists, probably because the
// session was logged out.
// *Action: Use a valid session ID.
00031, 00000, "session marked for kill"
// *Cause: The session specified in an ALTER SYSTEM KILL SESSION command
// cannot be killed immediately (because it is rolling back or blocked
// on a network operation), but it has been marked for kill. This
// means it will be killed as soon as possible after its current
// uninterruptable operation is done.
// *Action: No action is required for the session to be killed, but further
// executions of the ALTER SYSTEM KILL SESSION command on this session
// may cause the session to be killed sooner.
00032, 00000, "invalid session migration password"
// *Cause: The session migration password specified in a session creation
// call was invalid (probably too long).
// *Action: Retry with a valid password (less than 30 chars).
00033, 00000, "current session has empty migration password"
// *Cause: An attempt was made to detach or clone the current session and
// it has an empty migration password. This is not allowed.
// *Action: Create the session with a non-empty migration password.
00034, 00000, "cannot %s in current PL/SQL session"
// *Cause: An attempt was made to issue a commit or rollback from a PL/SQL
// object (procedure, function, package) in a session that has this
// disabled (by 'alter session disable commit in procedure')
// *Action: Enable commits from PL/SQL in this session, or do not attempt
// to use commit or rollback in PL/SQL when they are disabled
// in the current session.
00035, 00000, "LICENSE_MAX_USERS cannot be less than current number of users"
// *Cause:
// *Action:
00036, 00000, "maximum number of recursive SQL levels (%s) exceeded"
// *Cause: An attempt was made to go more than the specified number
// of recursive SQL levels.
// *Action: Remove the recursive SQL, possibly a recursive trigger.
00037, 00000, "cannot switch to a session belonging to a different server group"
// *Cause: An attempt was made to switch to a session in a different server
// group. This is not allowed.
// *Action: Make sure the server switches to a session that belongs to its
// server group.
00038, 00000, "Cannot create session: server group belongs to another user"
// *Cause: An attempt was made to create a non-migratable session in a server
// group that is owned by a different user.
// *Action: A server group is owned by the first user who logs into a server
// in the server group in non-migratable mode. All subsequent
// non-migratable mode logins must be made by the user who owns
// the server group. To have a different user login in non-migratable
// mode, the ownership of the server group will have to be changed.
// This can be done by logging off all current sessions and detaching
// from all existing servers in the server group and then having the
// new user login to become the new owner.
00039, 00000, "error during periodic action"
// *Cause: An unexpected error occurred while executing a periodically invoked
// action.
// *Action: Check the error stack for detailed error information.
00040, 00000, "active time limit exceeded - call aborted"
// *Cause: The Resource Manager SWITCH_TIME limit was exceeded.
// *Action: Reduce the complexity of the update or query, or contact your
// database administrator for more information.
00041, 00000, "active time limit exceeded - session terminated"
// *Cause: The Resource Manager SWITCH_TIME limit was exceeded.
// *Action: Reduce the complexity of the update or query, or contact your
// database administrator for more information.
00042, 0000, "Unknown Service name %s"
// *Cause: An attempt was made to use an invalid application service.
// *Action: Use a valid service name from SERVICE$ or add a new
// service using the DBMS_SERVICE package.
00043, 00000, "remote operation failed"
// *Cause: Execution of the inter-instance operation failed.
// *Action: Check the status of the target instance. The operation may
// have partially executed. Verify the result of the intended
// operation.
00044, 00000, "timed_statistics must be TRUE when statistics_level is not BASIC"
// *Cause: The user attempted to set timed_statistics to FALSE when
// statistics_level was not BASIC. timed_statistics is required to be
// TRUE to collect meaningful statistics when statistics_level is
// set to TYPICAL or ALL.
// *Action: Either set timed_statistics to TRUE or set statistics_level to
// BASIC.
00045, 00000, "Your session has been terminated with no replay."
// *Cause: A privileged user terminated your session and you were no longer
// logged on to the database. Your session will not be replayed by
// Application Continuity or Transparent Application Failover (TAF).
// *Action: Log in again if you wish to continue working.
00046, 00000, "cannot modify sessions parameter"
// *Cause: An attempt was made to alter the sessions parameter in the
// root container or non-consolidated database.
// *Action: The sessions parameter behaves like a static parameter in
// root containers and non-consolidated databases and hence cannot
// be altered. It can only be altered from a pluggable database.
00047, 00000, "cannot set sessions parameter to this value"
// *Cause: An attempt was made to alter the sessions parameter to a value
// greater than the root container's session value.
// *Action: The sessions parameter can only be set to a value less
// than or equal to the root container's session value.
00048, 00000, "Internal connect time error"
// *Document: NO
// *Cause: This is an internal error
// *Action: N/A
00050, 00000, "operating system error occurred while obtaining an enqueue"
// *Cause: Could not obtain the operating system resources necessary
// to cover an oracle enqueue. This is normally the result
// of an operating system user quota that is too low.
// *Action: Look up the operating system error in your system documentation
// and perform the needed action.
00051, 00000, "timeout occurred while waiting for a resource"
// *Cause: Usually due to a dead instance.
// *Action: Check for any dead, unrecovered instances and recover them.
00052, 00000, "maximum number of enqueue resources (%s) exceeded"
// *Cause: Ran out of enqueue resources.
// *Action: Increase the value of the ENQUEUE_RESOURCES initialization parameter.
00053, 00000, "maximum number of enqueues exceeded"
// *Cause: Ran out of enqueue state objects.
// *Action: Increase the value of the ENQUEUES initialization parameter.
00054, 00000, "resource busy and acquire with NOWAIT specified or timeout expired"
// *Cause: Interested resource is busy.
// *Action: Retry if necessary or increase timeout.
00055, 00000, "maximum number of DML locks exceeded"
// *Cause: Ran out of DML lock state objects.
// *Action: Increase the value of the DML_LOCKS initialization parameter
// and warm start.
00056, 00000, "DDL lock on object '%s.%s' is already held in an incompatible mode"
// *Cause: An attempt was made to acquire a DDL lock that is already locked.
// *Action: This happens if you attempt to drop a table that has parse locks
// on it.
00057, 00000, "maximum number of temporary table locks exceeded"
// *Cause: The number of temporary tables equals or exceeds the number of
// temporary table locks. Temporary tables are often created by
// large sorts.
// *Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization
// parameter and warm start.
00058, 00000, "DB_BLOCK_SIZE must be %s to mount this database (not %s)"
// *Cause: DB_BLOCK_SIZE initialization parameter is wrong for the database
// being mounted. It does not match the value used to create the
// database.
// *Action: Fix the value of the DB_BLOCK_SIZE parameter or mount a database
// that matches the value.
00059, 00000, "maximum number of DB_FILES exceeded"
// *Cause: The value of the DB_FILES initialization parameter was exceeded.
// *Action: Increase the value of the DB_FILES parameter and warm start.
00060, 00000, "deadlock detected while waiting for resource"
// *Cause: Transactions deadlocked one another while waiting for resources.
// *Action: Look at the trace file to see the transactions and resources
// involved. Retry if necessary.
00061, 00000, "another instance has a different DML_LOCKS setting"
// *Cause: The shared instance being started is using DML locks, and the
// running instances are not, or vice-versa.
// *Action: Ensure that all instances' INIT.ORA files specify
// the DML_LOCKS parameter as 0 or all as non-zero.
00062, 00000, "DML full-table lock cannot be acquired; DML_LOCKS is 0"
// *Cause: The instance was started with DML_LOCKS = 0, and the statement
// being executed needs a full-table lock (S, X, or SSX).
// *Action: Restart the instance with DML_LOCKS not equal to zero, and
// reexecute the statement.
00063, 00000, "maximum number of log files exceeded %s"
// *Cause: The number of log files specificied exceeded the maximum number
// of log files supported in this release.
// *Action: Re-create the control file with the highest number of log files
// no greater than the maximum supported in this release.
00064, 00000, "object is too large to allocate on this O/S (%s,%s,%s)"
// *Cause: An initialization parameter was set to a value that required
// allocating more contiguous space than can be allocated on this
// operating system.
// *Action: Reduce the value of the initialization parameter.
00065, 00000, "initialization of FIXED_DATE failed"
// *Cause: The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss.
// *Action: Make sure the initialization parameter is in the correct date
// format.
00066, 00000, "SID '%s' contains an illegal character or is too long"
// *Cause: The specified SID contained an illegal character or the SID
// specified was too long, which cannot occur in an SPFILE setting.
// Illegal characters include ,#"'=() and whitespace.
// *Action: Use a SID that does not contain a special character or whitespace.
// Check platform specific documentation for the maximum length of
// SID.
00067, 00000, "invalid value %s for parameter %s; must be at least %s"
// *Cause: The value for the initialization parameter is invalid.
// *Action: Choose a value as indicated by the message.
00068, 00000, "invalid value %s for parameter %s, must be between %s and %s"
// *Cause: The value for the initialization parameter is invalid.
// *Action: Choose a value as indicated by the message.
00069, 00000, "cannot acquire lock -- table locks disabled for %s"
// *Cause: A command was issued that tried to lock the table indicated in
// the message. Examples of commands that can lock tables are:
// LOCK TABLE, ALTER TABLE ... ADD (...), and so on.
// *Action: Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry
// the command.
/
/ 70 .. 90 generic debugger errors
/
00070, 00000, "command %s is not valid"
// *Cause: An invalid debugger command was specified.
// *Action: Type HELP to see the list of available commands.
00071, 00000, "process number must be between 1 and %s"
// *Cause: An invalid process number was specified.
// *Action: Specify a valid process number.
00072, 00000, "process \"%s\" is not active"
// *Cause: An invalid process was specified.
// *Action: Specify a valid process.
00073, 00000, "command %s takes between %s and %s argument(s)"
// *Cause: An incorrect number of arguments was specified.
// *Action: Specify the correct number of arguments. Type HELP
// to see the list of commands and their syntax.
00074, 00000, "no process has been specified"
// *Cause: No debug process has been specified.
// *Action: Specify a valid process.
00075, 00000, "process \"%s\" not found in this instance"
// *Cause: The specified process was not logged on to the current instance.
// *Action: Specify a valid process.
00076, 00000, "dump %s not found"
// *Cause: An attempt was made to invoke a dump that does not exist.
// *Action: Type DUMPLIST to see the list of available dumps.
00077, 00000, "dump %s is not valid"
// *Cause: An attempt was made to invoke an invalid dump.
// *Action: Try another dump.
00078, 00000, "cannot dump variables by name"
// *Cause: An attempt was made to dump a variable by name on a system that
// does not support this feature.
// *Action: Try the PEEK command.
00079, 00000, "variable %s not found"
// *Cause: An attempt was made to dump a variable that does not exist.
// *Action: Use a valid variable name.
00080, 00000, "invalid global area specified by level %s"
// *Cause: An attempt was made to dump an invalid global area.
// *Action: Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA.
// Use <extra + level> to dump global area <level> as well as <extra>
// bytes for every pointer; <extra> must be a multiple of 4.
00081, 00000, "address range [%s, %s) is not readable"
// *Cause: An attempt was made to read/write an invalid memory address range.
// *Action: Try another address or length.
00082, 00000, "memory size of %s is not in valid set of [1], [2], [4]%s%s%s%s%s"
// *Cause: An invalid length was specified for the POKE command.
// *Action: Use a valid length (either 1, 2, 4, or possibly 8).
00083, 00000, "warning: possibly corrupt SGA mapped"
// *Cause: Even though there may be SGA corruptions, the SGA was mapped.
// *Action: Use the DUMPSGA command to dump the SGA.
00084, 00000, "global area must be PGA, SGA, or UGA"
// *Cause: An attempt was made to dump an invalid global area.
// *Action: Specify either PGA, SGA, or UGA.
00085, 00000, "current call does not exist"
// *Cause: An invalid attempt was made to dump the current call heap.
// *Action: Wait until the process starts a call.
00086, 00000, "user call does not exist"
// *Cause: An invalid attempt was made to dump the user call heap.
// *Action: Wait until the process starts a call.
00087, 00000, "command cannot be executed on remote instance"
// *Cause: Cluster database command issued for non cluster database
// ORADEBUG command.
// *Action: Issue the command without the cluster database syntax.
00088, 00000, "command cannot be executed by shared server "
// *Cause: Debug command issued on shared server.
// *Action: Reissue the command using a dedicated server.
00089, 00000, "invalid instance number in ORADEBUG command "
// *Cause: An invalid instance number was specified in a cluster database
// ORADEBUG command.
// *Action: Reissue the command with valid instance numbers.
00090, 00000, "failed to allocate memory for cluster database ORADEBUG command "
// *Cause: Could not allocate memory needed to execute cluster database
// oradebug.
// *Action: Reissue the command on each instance with single-instance oradebug.
/ 91 .. 95 ksm large_pool_size and large_pool_min_alloc size errors
00091, 00000, "LARGE_POOL_SIZE must be at least %s"
// *Cause: The value of LARGE_POOL_SIZE is below the minimum size.
// *Action: Increase the value of LARGE_POOL_SIZE past the minimum size.
00092, 00000, "LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC"
// *Cause: The value of LARGE_POOL_SIZE is less than the value of
// LARGE_POOL_MIN_ALLOC.
// *Action: Increase the value of LARGE_POOL_SIZE past the value of
// LARGE_POOL_MIN_ALLOC.
00093, 00000, "%s must be between %s and %s"
// *Cause: The parameter value is not in a valid range.
// *Action: Modify the parameter value to be within the specified range.
00094, 00000, "%s requires an integer value"
// *Cause: The parameter value is not an integer.
// *Action: Modify the parameter value to be an integer.
/
00096, 00000, "invalid value %s for parameter %s, must be from among %s"
// *Cause: The value for the initialization parameter is invalid.
// *Action: Choose a value as indicated by the message.
/
00097, 00000, "use of Oracle SQL feature not in SQL92 %s Level"
// *Cause: Usage of Oracle's SQL extensions.
// *Action:
00098, 00000, "creating or mounting the database requires a parameter file"
// *Cause: An attempt was made to create or mount the database when the
// instance was started without a parameter file.
// *Action: Restart the instance with a parameter file.
00099, 00000, "warning: no parameter file specified for %s instance"
// *Cause: Even though no parameter file was specified, the instance was
// started with all default values.
// *Action: None.
00100, 00000, "no data found"
// *Cause: An application made reference to unknown or inaccessible data.
// *Action: Handle this condition within the application or make appropriate
// modifications to the application code.
// NOTE: If the application uses Oracle-mode SQL instead of
// ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100.
/
/ 101 .. 149 shared server errors
/
00101, 00000, "invalid specification for system parameter DISPATCHERS"
// *Cause: The syntax for the DISPATCHERS parameter is incorrect.
// *Action: Refer to the manual for correct syntax.
00102, 00000, "network protocol %s cannot be used by dispatchers"
// *Cause: The network specified in DISPATCHERS does not have the
// functionality required by the dispatchers.
// *Action: Refer to the manual on network protocols supported by the
// dispatchers.
00103, 00000, "invalid network protocol; reserved for use by dispatchers"
// *Cause: The network specified in the SQL*Net connect string is reserved
// for use by the dispatchers.
// *Action: Specify other network protocols in the connection string.
00104, 00000, "deadlock detected; all public servers blocked waiting for resources"
// *Cause: All available public servers are servicing requests that require
// resources locked by a client which is unable to get a public
// server to release the resources.
// *Action: Increase the limit for the system parameter MAX_SHARED_SERVERS
// as the system will automaticaly start
// up new servers to break the deadlock until the number of
// servers reaches the value specified in MAX_SHARED_SERVERS.
00105, 00000, "too many dispatcher configurations"
// *Cause: Too many dispatcher configurations have been specified.
// No more can be added.
// *Action: Consolidate the dispatcher configurations if possible.
00106, 00000, "cannot startup/shutdown database when connected to a dispatcher"
// *Cause: An attempt was made to startup/shutdown database when connected to
// a shared server via a dispatcher.
// *Action: Re-connect as user INTERNAL without going through the dispatcher.
// For most cases, this can be done by connect to INTERNAL without
// specifying a network connect string.
00107, 00000, "failed to connect to ORACLE listener process"
// *Cause: Most likely due to the fact that ORACLE listener has not been
// started.
// *Action: Start ORACLE listener if it has not been started. Or else
// contact your ORACLE representative.
00108, 00000, "failed to set up dispatcher to accept connection asynchronously"
// *Cause: Most likely due to the fact that the network protocol used by the
// the dispatcher does not support aynchronous operations.
// *Action: Contact your ORACLE representative.
00109, 00000, "invalid value for attribute %s: %s"
// *Cause: The value specified for the attribute was incorrect.
// *Action: Refer to the manual for the proper values.
00110, 00000, "invalid value %s for attribute %s, must be between %s and %s"
// *Cause: The value specified for the attribute was incorrect.
// *Action: Specify a value within the range allowed.
00111, 00000, "invalid attribute %s"
// *Cause: The specified attribute was not recognized.
// *Action: Refer to the manual for the proper keyword to use to specify
// a dispatcher attribute.
00112, 00000, "value of %s is null"
// *Cause: The attribute was specified with no value.
// *Action: Specify a non-null value.
00113, 00000, "protocol name %s is too long"
// *Cause: A protocol name specified in the DISPATCHERS system parameter
// is too long.
// *Action: Use a valid protocol name for the DISPATCHERS value.
00114, 00000, "missing value for system parameter SERVICE_NAMES"
// *Cause: No value was specified for the SERVICE_NAMES system parameter,
// nor for the DB_NAME parameter.
// *Action: Add an SERVICE_NAMES or DB_NAME definition to the INIT.ORA file.
// By default, SERVICE_NAMES is the value of DB_NAME unless
// SERVICE_NAMES is explicitly specified.
00115, 00000, "connection refused; dispatcher connection table is full"
// *Cause: A connection request was refused by a dispatcher because the
// dispatcher cannot support any more connections.
// *Action: Connect to a different dispatcher, or use a dedicated server.
00116, 00000, "SERVICE_NAMES name is too long"
// *Cause: A service name specified in the SERVICE_NAMES system parameter
// is too long.
// *Action: Use a shorter name in the SERVICE_NAMES value (<= 255 chars).
00117, 00000, "PROTOCOL, ADDRESS or DESCRIPTION must be specified"
// *Cause: PROTOCOL, ADDRESS or DESCRIPTION was not specified.
// *Action: Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION
// to specify the listening address for dispatchers.
00118, 00000, "Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified"
// *Cause: More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.
// *Action: Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION
// to specify the listening address for dispatchers.
00119, 00000, "invalid specification for system parameter %s"
// *Cause: The syntax for the specified parameter is incorrect.
// *Action: Refer to the Oracle Reference Manual for the correct syntax.
00120, 00000, "invalid 'shared_servers' value for the PDB"
// *Cause: 'shared_servers' cannot be set to a non-zero value in a non-ROOT
// pluggable database (PDB).
// *Action: In a multitenant container database (CDB) setup, shared servers can
// be configured only in ROOT. A non-ROOT PDB can disable shared
// servers for the PDB by setting 'shared_servers' to 0. No other
// values are allowed. To reenable within the PDB, use
// 'alter system reset shared_servers'.
00122, 00000, "cannot initialize network configuration"
// *Cause: ORACLE could not initialize SQL*Net version 2.
// *Action: Check the error stack for detailed information.
00123, 00000, "idle public server terminating"
// *Cause: Too many idle servers were waiting on the common queue.
// *Action: This error is used internally, no action is required.
00125, 00000, "connection refused; invalid presentation"
// *Cause: The PRESENTATION in the CONNECT_DATA of the TNS address
// DESCRIPTION is not correct or is not supported.
// *Action: Correct the PRESENTATION specified in the TNS address.
00126, 00000, "connection refused; invalid duplicity"
// *Cause: The DUPLICITY in the CONNECT_DATA of the TNS address
// DESCRIPTION is not correct or is not supported.
// *Action: Correct the DUPLICITY specified in the TNS address.
00127, 00000, "dispatcher %s does not exist"
// *Cause: There is currently no dispatcher running with the specified
// name.
// *Action: Retry with a name of the form "D###" denoting an existing
// dispatcher process.
00128, 00000, "this command requires a dispatcher name"
// *Cause: Wrong syntax for ALTER SYSTEM SHUTDOWN
// *Action: Use correct syntax:
// ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] 'dispatcher name'
00129, 00000, "listener address validation failed '%s'"
// *Cause: An error was encountered while validating the listener address.
// *Action: Resolve error or contact your ORACLE representative.
00130, 00000, "invalid listener address '%s'"
// *Cause: The listener address specification is not valid.
// *Action: Make sure that all fields in the listener address
// (protocol, port, host, key, ...) are correct.
00131, 00000, "network protocol does not support registration '%s'"
// *Cause: The specified protocol does not support async notification.
// *Action: Refer to the manual for information on supported network
// protocols.
00132, 00000, "syntax error or unresolved network name '%s'"
// *Cause: Listener address has syntax error or cannot be resolved.
// *Action: If a network name is specified, check that it corresponds
// to an entry in TNSNAMES.ORA or other address repository
// as configured for your system. Make sure that the entry
// is syntactically correct.
00133, 00000, "value of %s is too long"
// *Cause: The value specified for the attribute was too long.
// *Action: Use shorter names and keywords or remove unneeded blanks.
00134, 00000, "invalid DISPATCHERS specification #%s"
// *Cause: The syntax for the n-th DISPATCHERS specification was incorrect.
// *Action: Refer to the Oracle Reference Manual for the correct syntax.
00135, 00000, "missing attribute %s"
// *Cause: The indicated mandatory attribute was not specified.
// *Action: Specify a non-null value for the attribute.
00136, 00000, "invalid LISTENER_NETWORKS specification #%s"
// *Cause: The syntax for the nth LISTENER_NETWORKS specification was invalid.
// *Action: Refer to the Oracle Reference Manual for the correct syntax.
00137, 00000, "invalid LISTENER_NETWORKS specification with NAME=%s"
// *Cause: The syntax for the LISTENER_NETWORKS specification with the
// indicated NAME was invalid.
// *Action: Refer to the Oracle Reference Manual for the correct syntax.
00138, 00000, "all addresses specified for attribute %s are invalid"
// *Cause: All of the specified addresses or aliases for the attribute were
// invalid.
// *Action: Specify at least one valid address or alias.
00139, 00000, "duplicate attribute %s"
// *Cause: The indicated attribute was specified more than once.
// *Action: Specify the attribute at most once.
00140, 00000, "LISTENER_NETWORKS specification with NAME=%s not allowed"
// *Cause: An internal network name has been specified.
// *Action: Specify a different network name.
00141, 00000, "all addresses specified for parameter %s are invalid"
// *Cause: All of the specified addresses or aliases for the parameter were
// invalid.
// *Action: Specify at least one valid address or alias.
00142, 00000, "FORWARD_LISTENER and LOCAL_LISTENER are on the same network."
// *Cause: FORWARD_LISTENER was used with LOCAL_LISTENER for the same network.
// *Action: Do not use FORWARD_LISTENER with LOCAL_LISTENER in the same network.
00143, 00000, "The registration of a remote port is not supported without the registration of a local port."
// *Cause: The remote HTTP/HTTPS port could not be registered without the
// local HTTP/HTTPS port.
// *Action: Register the local HTTP/HTTPS port first.
/
/ 150 .. 159 Oracle*XA errors
/
00150, 00000, "duplicate transaction ID"
// *Cause: Attempted to start a new transaction with an ID already in use
// by an existing transaction.
// *Action: Check your application.
00151, 00000, "invalid transaction ID"
// *Cause: The specified transaction ID does not correspond to an existing
// valid transaction.
// *Action: Check your application.
00152, 00000, "current session does not match requested session"
// *Cause: The current session is not the same as the session that was
// passed into a upixado() call.
// *Action: Check your application.
00153, 00000, "internal error in XA library"
// *Cause: The XA library could not access thread-specific pointers.
// *Action: Contact customer support.
00154, 00000, "protocol error in transaction monitor"
// *Cause: The transaction monitor returned TMJOIN on an AX_REG call but
// the transaction was locally suspended.
// *Action: Contact the transaction monitor customer support.
00155, 00000, "cannot perform work outside of global transaction"
// *Cause: The application tried to perform some work on either an Oracle
// 7.3 server or an Oracle8 server with local transactions disabled
// while outside of a global transaction.
// *Action: Check if the application is connected to an Oracle 7.3 server. The
// Transaction monitor must not return a NULL XID on an AX_REG call
// when the resource manager is Oracle 7.3. If the application is
// connected to an Oracle8 server, either set nolocal=f in the
// xa_open string or start a global transaction prior to attempting
// the work.
//
/
/ 160 .. 199 Distributed transaction errors (continued)
/
00160, 00000, "global transaction length %s is illegal (maximum allowed %s)"
// *Cause: An external global transaction ID with a length either too large
// or 0 was passed in in a distributed transaction.
// *Action: Report the problem to your external transaction coordinator
// vendor.
00161, 00000, "transaction branch length %s is illegal (maximum allowed %s)"
// *Cause: An external transaction branch ID with a length either too large
// or 0 was passed in.
// *Action: Report the problem to your external transaction coordinator
// vendor.
00162, 00000, "external dbid length %s is greater than maximum (%s)"
// *Cause: An external database name with too large a length field
// was passed in.
// *Action: Report the problem to your external transaction coordinator
// vendor.
00163, 00000, "internal database name length %s is greater than maximum (%s)"
// *Cause: An internal database name with a too large length field
// was passed in.
// *Action: Report the problem to your external transaction coordinator
// vendor.
00164, 00000, "distributed autonomous transaction disallowed within migratable distributed transaction"
// *Cause: A request was made by the application to start a distributed
// autonomous transaction when the application was in a migratable
// distributed transaction.
// *Action: Roll back or commit the current distributed transaction first.
00165, 00000, "migratable distributed autonomous transaction with remote operation is not allowed"
// *Cause: A request was made by the application to start a migratable
// distributed autonomous transaction with remote operation.
// *Action:
/
00166, 00000, "remote/local nesting level is too deep"
// *Cause: Too many remote table operations required a reverse trip
// back to the local site, for example to execute a local
// function on a remote table.
// *Action: Rearrange the query or co-locate the functions with the tables.
/
/ 200 .. 249 control file management errors
/
00200, 00000, "control file could not be created"
// *Cause: It was not possible to create the control file.
// *Action: Check that there is sufficient disk space and no conflicts in
// filenames and try to create the control file again.
00201, 00000, "control file version %s incompatible with ORACLE version %s"
// *Cause: The control file was created by incompatible software.
// *Action: Either restart with a compatible software release or use
// CREATE CONTROLFILE to create a new control file that is
// compatible with this release.
00202, 00000, "control file: '%s'"
// *Cause: This message reports the name file involved in other messages.
// *Action: See associated error messages for a description of the problem.
00203, 00000, "using the wrong control files"
// *Cause: The mount ID in the control file is not the same as the
// mount ID in the control file used by the first instance to
// mount this database. The control files are for the same database
// but they are not the same files. Most likely one instance is using
// a backup control file.
// *Action: Check that the correct control files were specified.
00204, 00000, "error in reading (block %s, # blocks %s) of control file"
// *Cause: A disk I/O failure was detected on reading the control file.
// *Action: Check if the disk is online, if it is not, bring it online and try
// a warm start again. If it is online, then you need to recover
// the disk.
00205, 00000, "error in identifying control file, check alert log for more info"
// *Cause: The system could not find a control file of the specified name and
// size.
// *Action: Check that ALL control files are online and that they are the same
// files that the system created at cold start time.
00206, 00000, "error in writing (block %s, # blocks %s) of control file"
// *Cause: A disk I/O failure was detected on writing the control file.
// *Action: Check if the disk is online, if it is not, bring it online and try
// a warm start again. If it is online, then you need to
// recover the disk.
00207, 00000, "control files are not for the same database"
// *Cause: The database ID in the control file is not the same as the
// database ID in the control file used by the first instance to
// mount this database. Most likely one of the mounts used the wrong
// control file or there are two databases with the same name.
// *Action: Check that the control file is for the correct database and is
// not an old version.
00208, 00000, "number of control file names exceeds limit of %s"
// *Cause: An attempt was made to use more control files than Oracle supports.
// *Action: Shut down Oracle. Reduce the number of control files specified in
// the CONTROL_FILES parameter in the initialization parameter
// file, and restart Oracle. Delete usused files.
00209, 00000, "control file blocksize mismatch, check alert log for more info"
// *Cause: The block size in the control file header does not match the
// size specified in the DB_BLOCK_SIZE parameter.
// *Action: Look at the alert log for more information.
00210, 00000, "cannot open the specified control file"
// *Cause: Cannot open the control file.
// *Action: Check to make sure the control file exists and is not locked by
// some other program.
00211, 00000, "control file does not match previous control files"
// *Cause: A control file was specified that belongs to another database.
// *Action: Find and install the correct control file.
00212, 00000, "block size %s below minimum required size of %s bytes"
// *Cause: The block size specified was too small. Space for the
// system overhead is required.
// *Action: Specify a larger block size and retry the operation.
00213, 00000, "cannot reuse control file; old file size %s, %s required"
// *Cause: To reuse a control file, it must be the same size as
// the one previously used.
// *Action: Either do not specify REUSE, or specify a matching combination of
// MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and
// MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE
// statement.
00214, 00000, "control file '%s' version %s inconsistent with file '%s' version %s"
// *Cause: An inconsistent set of control files, datafiles/logfiles, and redo
// files was used.
// *Action: Use a consistant set of control files, datafiles/logfiles, and redo
// log files. That is, all the files must be for the same database
// and from the same time period.
00215, 00000, "must be at least one control file"
// *Cause: No control file is specified or the control file specified does
// not exist.
// *Action: Specify at least one valid control file and retry the operation.
00216, 00000, "control file could not be resized for migration from 8.0.2"
// *Cause: The control file created by release 8.0.2 was missing some record
// types. These record types are automatically added by resizing
// the control file during mount. The resize has failed.
// *Action: Look in the alert log for the reason that the resize has failed.
// If indicated in the alert log, give the control file more space.
// Otherwise, use the CREATE CONTROLFILE script dumped to the trace
// file to create a new control file.
00217, 00000, "control file could not be resized for new record types"
// *Cause: The control file was missing some new record types supported
// by this release. These record types are automatically added
// by resizing the contol file during mount. The resize has failed.
// *Action: Look in the alert log for the reason that the resize has failed.
// If indicated in the alert log, give the control file more space.
// Otherwise, use the CREATE CONTROLFILE script dumped to the trace
// file to create a new control file.
00218, 00000, "block size %s of control file '%s' does not match DB_BLOCK_SIZE (%s)"
// *Cause: The block size as stored in the control file header is
// different from the value of the initialization parameter
// DB_BLOCK_SIZE. This might be due to an incorrect setting of
// DB_BLOCK_SIZE, or else might indicate that the control file has
// either been corrupted or belongs to a different database.
// *Action: Restore a good copy of the control file. If the control file is
// known to be clean set the DB_BLOCK_SIZE to match control file
// headers block size value.
00219, 00000, "required control file size (%s logical blocks) exceeds maximum allowable size (%s logical blocks)"
// *Cause: An invocation of CREATE DATABASE or CREATE CONTROLFILE
// was executed specifying a combination of parameters that would
// require the control file size in blocks to exceed the maximum
// allowable value.
// *Action: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a
// different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS,
// MAXLOGHISTORY, and MAXINSTANCES clauses.
00220, 00000, "control file not mounted by first instance, check alert log for more info"
// *Cause: The specified control file has a different mount ID than the
// other control files that are being mounted. This means that
// the first instance to mount the database did not use this
// control file.
// *Action: Find and install the correct control file.
00221, 00000, "error on write to control file"
// *Cause: An error occurred when writing to one or more of the control files.
// *Action: See accompanying messages.
00222, 00000, "operation would reuse name of a currently mounted control file"
// *Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP
// CONTROLFILE command or to cfileSetSnapshotName matches the
// name of the specified currently mounted control file.
// *Action: Retry the operation with a different filename.
00223, 00000, "convert file is invalid or incorrect version"
// *Cause: An Oracle7 to Oracle8 convert file contains invalid data
// or was created with an different version of the migration utility.
// This error can also be caused by incorrect ORACLE_HOME environment
// variable when ALTER DATABASE CONVERT command is issued.
// *Action: Use a correct version of the convert file or regenerate it with
// the migration utility. Make sure that the migration utility is the
// same version as the Oracle8 RDBMS executable and that the
// ORACLE_HOME environment variable is properly set.
00224, 00000, "control file resize attempted with illegal record type (%s)"
// *Cause: An attempt was made to expand or shrink the control file by calling
// cfileResizeSection using an invalid value for the RECORD_TYPE
// parameter.
// *Action: Use a value for the RECORD_TYPE parameter that specifies a
// valid record type other than type 0 (valid range is 1-16).
00225, 00000, "expected size %s of control file differs from actual size %s"
// *Cause: The expected size of the control file as stored in its
// header was different than the actual operating system file size.
// This usually indicates that the control file was corrupted.
// *Action: Restore a good copy of the control file.
00226, 00000, "operation disallowed while alternate control file open"
// *Cause: The attempted operation could not be executed at this time because
// this process had an alternate control file open for fixed table
// access.
// *Action: Retry the operation after calling cfileUseCurrent.
00227, 00000, "corrupt block detected in control file: (block %s, # blocks %s)"
// *Cause: A block header corruption or checksum error was detected on reading
// the control file.
// *Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP
// CONTROLFILE command.
00228, 00000, "length of alternate control file name exceeds maximum of %s"
// *Cause: The specified filename, which was supplied as a parameter
// to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum
// filename length for this operating system.
// *Action: Retry the operation with a shorter filename.
00229, 00000, "operation disallowed: already hold snapshot control file enqueue"
// *Cause: The attempted operation cannot be executed at this time because
// this process currently holds the snapshot control file enqueue.
// *Action: Retry the operation after calling cfileUseCurrent to release the
// snapshot control file enqueue.
00230, 00000, "operation disallowed: snapshot control file enqueue unavailable"
// *Cause: The attempted operation cannot be executed at this time because
// another process currently holds the snapshot control file enqueue.
// *Action: Retry the operation after the concurrent operation that is holding
// the snapshot control file enqueue terminates.
00231, 00000, "snapshot control file has not been named"
// *Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot
// it was detected that no filename for the snapshot control file had
// previously been specified.
// *Action: Specify a name for the snapshot control file by calling
// cfileSetSnapshotName.
00232, 00000, "snapshot control file is nonexistent, corrupt, or unreadable"
// *Cause: The snapshot control file was found to be nonexistent, corrupt,
// or unreadable during an invocation of cfileUseSnapshot.
// *Action: Call cfileMakeAndUseSnapshot again (or for the first time).
00233, 00000, "copy control file is corrupt or unreadable"
// *Cause: The specified copy control file was found to be corrupt or
// unreadable during an invocation of cfileUseCopy.
// *Action: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP
// CONTROLFILE command and specify the same filename that was
// specified for cfileUseCopy.
00234, 00000, "error in identifying or opening snapshot or copy control file"
// *Cause: A snapshot or copy control file of the specified name
// could not be found or opened during an invocation of
// cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.
// *Action: Re-create the snapshot or copy control file using
// cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE,
// respectively.
00235, 00000, "control file read without a lock inconsistent due to concurrent update"
// *Cause: Concurrent update activity on a control file caused a process
// to read inconsistent information from the control file
// without a lock.
// *Action: Retry the operation.
00236, 00000, "snapshot operation disallowed: mounted control file is a backup"
// *Cause: Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot,
// or cfileUseSnapshot when the currently mounted control file is a
// backup control file.
// *Action: Mount a current control file and retry the operation.
00237, 00000, "snapshot operation disallowed: control file newly created"
// *Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently
// mounted control file that was newly created with CREATE CONTROLFILE
// was made.
// *Action: Mount a current control file and retry the operation.
00238, 00000, "operation would reuse a filename that is part of the database"
// *Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP
// CONTROLFILE command or to cfileSetSnapshotName matches the name of
// a file that is currently part of the database.
// *Action: Retry the operation with a different filename.
00239, 00000, "timeout waiting for control file enqueue: held by '%s' for more than %s seconds"
// *Cause: The specified process waited the maximum allowed time for the control file enqueue.
// *Action: Restart the blocking instance indicated in the incident trace file
// or reboot the blocking node.
00240, 00000, "control file enqueue held for more than %s seconds"
// *Cause: The current process did not release the control file enqueue within
// the maximum allowed time.
// *Action: Reissue any commands that failed and contact Oracle Support
// Services with the incident information.
00241, 00000, "operation disallowed: control file is not yet checked against data dictionary"
// *Cause: Either the control file was recently created by using CREATE
// CONTROLFILE, an incomplete recovery was done, or some previous
// operations require the control file to be re-checked against
// the data dictionary.
// *Action: Shut down and restart the database or the pluggable database so
// that the check is performed, and then retry the operation.
00242, 00000, "maximum allowed filename records used up in control file"
// *Cause: Failed to create a new filename record entry in the control file
// because the maximum allowed filename records have been allocated
// and are in use.
// *Action: Free up controlfile filename section entries by dropping unwanted
// tablespaces/datafiles/redofiles.
00243, 00000, "failed to expand control file filename section by %s records"
// *Cause: Failed to expand control file filename section. See alert log for
// more details.
// *Action: Retry the operation after increasing disk space for controlfile
// expansion.
00244, 00000, "concurrent control file backup operation in progress"
// *Cause: Failed to create a control file backup because concurrent control
// file backup operation was in progress.
// *Action: Retry backup creation later.
00245, 00000, "control file backup failed; in Oracle RAC, target might not be on shared storage"
// *Cause: Failed to create a control file backup because some process
// signaled an error during backup creation. This is likely caused
// by the backup target (i.e., RMAN snapshot controlfile) being on
// a local file system so it could not be accessed by other instances.
// It can also be caused by other I/O errors to the backup target.
// Any process of any instance that starts a read/write control file
// transaction must have access to the backup control file during
// backup creation.
// *Action: Check whether RMAN snapshot controlfile is on shared storage.
// Also, check alert files of all instances for further information.
00246, 00000, "control file backup failed; error accessing backup target"
// *Cause: An attempt to create a control file backup failed because some process
// signaled an I/O error when accessing the backup target.
// *Action: Check alert and trace files for further information.
/
/ 250 .. 299 archival & media recovery errors
/
00250, 00000, "archiver not started"
// *Cause: An attempt was made to stop automatic archiving, but the
// archiver process was not running.
// *Action: No action required.
00251, 00000, "LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string %s"
// *Cause: The destination specified by the LOG_ARCHIVE_DUPLEX_DEST
// parameter is the same as the destination specified by an ALTER
// SYSTEM ARCHIVE LOG START TO command.
// *Action: Specify a different destination for parameter
// LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the
// ALTER SYSTEM command.
00252, 00000, "log %s of thread %s is empty, cannot archive"
// *Cause: A log must be used for redo generation before it can be archived.
// The specified redo log was not been used since it was introduced
// to the database. However it is possible that instance death during
// a log switch left the log empty.
// *Action: Empty logs do not need to be archived. Do not attempt to
// archive the redo log file.
00253, 00000, "character limit %s exceeded by archive destination string %s"
// *Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO
// command was too long.
// *Action: Retry the ALTER SYSTEM command using a string shorter than the
// limit specified in the error message.
00254, 00000, "error in archive control string '%s'"
// *Cause: The specified archive log location is invalid in the archive
// command or the LOG_ARCHIVE_DEST initialization parameter.
// *Action: Check the archive string used to make sure it refers to a valid
// online device.
00255, 00000, "error archiving log %s of thread %s, sequence # %s"
// *Cause: An error occurred during archiving.
// *Action: Check the accompanying message stack for more detailed
// information.
//
// If the online log is corrupted,
// then the log can be cleared using the UNARCHIVED option. This will
// make any existing backups useless for recovery to any time after
// the log was created, but will allow the database to generate redo.
00256, 00000, "cannot translate archive destination string %s"
// *Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO
// command could not be translated.
// *Action: Check the accompanying message stack for more detailed information.
// Then, retry the ALTER SYSTEM command using a different string.
00257, 00000, "Archiver error. Connect AS SYSDBA only until resolved."
// *Cause: The archiver process received an error while trying to archive
// a redo log. If the problem is not resolved soon, the database
// will stop executing transactions. The most likely cause of this
// message is that the destination device is out of space to store the
// redo log file. Another possible cause is that a destination marked
// as MANDATORY has failed.
// *Action: Check the alert log and trace files for detailed error
// information.
00258, 00000, "manual archiving in NOARCHIVELOG mode must identify log"
// *Cause: The database is in NOARCHIVELOG mode and a command to manually
// archive a log did not specify the log explicitly by sequence
// number, group number or filename.
// *Action: Specify log by filename, by group number or by thread and
// sequence number.
00259, 00000, "log %s of open instance %s (thread %s) is the current log, cannot archive"
// *Cause: An attempt was made to archive the current log of an open
// thread. This is not allowed because the redo log file may
// still be in use for the generation of redo entries.
// *Action: Force a log switch in the instance where the thread is open.
// If no instances are open, open the database so that instance
// recovery can recover the thread.
00260, 00000, "cannot find online log sequence %s for thread %s"
// *Cause: The log sequence number supplied to the archival command does
// not match any of the online logs for the thread. The log might
// have been reused for another sequence number, it might have been
// dropped, the sequence number might be greater than the current
// log sequence number, or the thread might not have any logs.
// *Action: Check the ARCHIVE statement, then specify a valid log sequence
// number. Specify a valid log sequence number.
00261, 00000, "log %s of thread %s is being archived or modified"
// *Cause: The log is either being archived by another process or an
// administrative command is modifying the log. Operations that
// modify the log include clearing, adding a member, dropping a
// member, renaming a member, and dropping the log.
// *Action: Wait for the current operation to complete and try again.
00262, 00000, "current log %s of closed thread %s cannot switch"
// *Cause: The log cannot be cleared or manually archived because it is
// the current log of a closed thread, and it is not possible to
// switch logs so another log is current. All other logs for the
// thread need to be archived, or cleared, and cannot be reused.
// *Action: Archive another log in the same thread first, or complete the
// clearing. See attached errors for the reason the switch cannot
// be completed.
00263, 00000, "there are no logs that need archiving for thread %s"
// *Cause: An attempt was made to manually archive the unarchived logs in this
// thread but no logs needed archiving.
// *Action: No action required.
00264, 00000, "no recovery required"
// *Cause: An attempt was made to perform media recovery on files that do not // need any type of recovery.
// *Action: Do not attempt to perform media recovery on the selected
// files. Check to see that the filenames were entered properly.
// If not, retry the command with the proper filenames.
00265, 00000, "instance recovery required, cannot set ARCHIVELOG mode"
// *Cause: The database either crashed or was shutdown with the ABORT
// option. Media recovery cannot be enabled because the online
// logs may not be sufficient to recover the current datafiles.
// *Action: Open the database and then enter the SHUTDOWN command with the
// NORMAL or IMMEDIATE option.
00266, 00000, "name of archived log file needed"
// *Cause: During media recovery, the name of an archived redo log file
// was requested, but no name was entered.
// *Action: Mount the correct redo log file and enter its name when it
// is requested.
00267, 00000, "name of archived log file not needed"
// *Cause: During media recovery, the name of an archived redo log file
// was entered, but no name was requested.
// *Action: Continue media recovery, but do not enter a new log name.
00268, 00000, "specified log file does not exist '%s'"
// *Cause: The given redo log file does not exist.
// *Action: Check the spelling and capitalization of the filename and
// retry the command.
00269, 00000, "specified log file is part of thread %s not %s"
// *Cause: The given redo log file is not part of the given thread
// *Action: Check that the thread of the redo log file matches the
// thread on the command line. If not, use a redo log file
// from the appropriate thread. Retry the command after
// correcting the error.
00270, 00000, "error creating archive log %s"
// *Cause: An error was encountered when either creating or opening
// the destination file for archiving.
// *Action: Check that the archive destination is valid and that there
// is sufficient space on the destination device.
00271, 00000, "there are no logs that need archiving"
// *Cause: An attempt was made to archive the unarchived redo log
// files manually, but there are no files that need to be archived.
// *Action: No action required.
00272, 00000, "error writing archive log %s"
// *Cause: An I/O error occurred while archiving a redo log file.
// *Action: Check that the output device is still available and correct
// any device errors that may have occurred. Also, make certain
// that sufficient space for archiving is available on the
// output device.
00273, 00000, "media recovery of direct load data that was not logged"
// *Cause: A media recovery session encountered a table that was loaded
// by the direct loader without logging any redo information. Some
// or all of the blocks in this table are now marked as corrupt.
// *Action: The table must be dropped or truncated so that the corrupted
// blocks can be reused. If a more recent backup of the file is
// available, try to recover this file to eliminate this error.
00274, 00000, "illegal recovery option %s"
// *Cause: An illegal option was specified for a recovery command.
// *Action: Correct the syntax and retry the command.
00275, 00000, "media recovery has already been started"
// *Cause: An attempt was made to start a second media recovery operation
// in the same session.
// *Action: Complete or cancel the first media recovery session or
// start another session to perform media recovery.
00276, 00000, "CHANGE keyword specified but no change number given"
// *Cause: The CHANGE keyword was specified on the command line, but
// no change number was given.
// *Action: Retry the command using a valid change number after the CHANGE
// keyword.
00277, 00000, "illegal option to the UNTIL recovery flag %s"
// *Cause: Only CANCEL, CHANGE, CONSISTENT and TIME can be used with the
// UNTIL keyword.
// *Action: Correct the syntax.
00278, 00000, "log file '%s' no longer needed for this recovery"
// *Cause: The specified redo log file is no longer needed for the current
// recovery.
// *Action: No action required. The archived redo log file may be removed
// from its current location to conserve disk space, if needed.
// However, the redo log file may still be required for another
// recovery session in the future.
00279, 00000, "change %s generated at %s needed for thread %s"
// *Cause: The requested log is required to proceed with recovery.
// *Action: Please supply the requested log with "ALTER DATABASE RECOVER
// LOGFILE <file_name>" or cancel recovery with "ALTER DATABASE
// RECOVER CANCEL".
00280, 00000, "change %s for thread %s is in sequence #%s"
// *Cause: This message helps to locate the redo log file with the
// specified change number requested by other messages.
// *Action: Use the information provided in this message to specify the
// required archived redo log files for other errors.
00281, 00000, "media recovery may not be performed using dispatcher"
// *Cause: An attempt was made to use a dispatcher process for media
// recovery. Memory requirements disallow this recovery method.
// *Action: Connect to the instance via a dedicated server process to
// perform media recovery.
00282, 00000, "UPI %s call not supported, use ALTER DATABASE RECOVER"
// *Cause: The given UPI call is no longer supported.
// *Action: Use the ALTER DATABASE RECOVER command for all recovery actions.
00283, 00000, "recovery session canceled due to errors"
// *Cause: An error during recovery was determined to be fatal enough to end
// the current recovery session.
// *Action: More specific messages will accompany this message. Refer to
// the other messages for the appropriate action.
00284, 00000, "recovery session still in progress"
// *Cause: An error during recovery was determined to be minor enough to allow
// the current recovery session to continue.
// *Action: More specific messages will accompany this message. Refer to
// the other messages for the appropriate action.
00285, 00000, "TIME not given as a string constant"
// *Cause: TIME was not followed by a string constant for the time.
// *Action: Enter the time enclosed in single quotation marks.
00286, 00000, "no members available, or no member contains valid data"
// *Cause: None of the members of a redo log file group are available, or
// the available members do not contain complete data.
// *Action: If a member is temporarily offline, attempt to make it available.
// Make sure that the correct filenames are being used, especially
// if the redo log file is being accessed from a remote location.
00287, 00000, "specified change number %s not found in thread %s"
// *Cause: The given change number does not appear in any of the online
// redo logs for the given thread.
// *Action: Check the statement to make certain a valid change number
// is given. Perhaps try to use the NEXT option for archiving logs.
00288, 00000, "to continue recovery type ALTER DATABASE RECOVER CONTINUE"
// *Cause: During media recovery, a new log is not required but the
// continuation command is necessary to do a checkpoint and
// report errors.
// *Action: Type ALTER DATABASE RECOVER CONTINUE and recovery will resume.
00289, 00000, "suggestion : %s"
// *Cause: This message reports the next redo log filename that is needed,
// according to the initialization parameters LOG_ARCHIVE_DEST and
// LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST
// and LOG_ARCHIVE_FORMAT are the same now as when the required redo
// log file was archived.
// *Action: Consider using this filename for the next log needed for recovery.
00290, 00000, "operating system archival error occurred. See error below"
// *Cause: While attempting to archive to a redo log file, the server
// encountered an unexpected operating system error.
// *Action: Correct the operating system error given in the messages and
// retry the operation. See also your operating system-specific
// Oracle documentation.
00291, 0000, "numeric value required for PARALLEL option"
// *Cause: A recovery command was specified incorrectly. The PARALLEL option
// must be followed by a numeric argument that specifies the degree
// of parallelism.
// *Action: Re-enter the command with a numeric argument specifying the
// degree of parallelism desired.
00292, 00000, "parallel recovery feature not installed"
// *Cause: A parallel recovery was requested when the parallel
// recovery option is not installed.
// *Action: Delete the PARALLEL clause from the RECOVER command. Also,
// delete the RECOVERY_PARALLELISM parameter in the initialization
// file.
00293, 00000, "control file out of sync with redo log"
// *Cause: The redo log file and control file are out of sync because a
// non-current controle file was specified when the instance
// was started.
// *Action: Retry the RECOVER command using the current control file, or retry
// the RECOVER command using the USING BACKUP CONTROLFILE clause.
00294, 00000, "invalid archivelog format specifier '%s'"
// *Cause: An invalid format specifier was found in the LOG_ARCHIVE_FORMAT
// initialization parameter. The only characters permitted
// following the % symbol are s, S, t, and T.
// *Action: Correct the initialization file and re-start the instance.
00295, 00000, "datafile/tempfile number %s is invalid, must be between 1 and %s"
// *Cause: An invalid file number was specified.
// *Action: Specify a valid datafile or tempfile number
// and retry the operation.
00296, 00000, "maximum number of files (%s) exceeded for RECOVER DATAFILE LIST"
// *Cause: The RECOVER DATAFILE LIST command specified more datafiles than
// are allowed by the DB_FILES initialization parameter.
// This error occurs when doing recovery with Recovery Manager, and
// the instance has been started with a DB_FILES parameter specifying
// fewer datafiles than recovery manager needs to recover to satisfy
// the user's RECOVER command.
// *Action: Re-start the instance with a higher value for DB_FILES.
00297, 00000, "must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START"
// *Cause: The RECOVER DATAFILE START command was issued, but no RECOVER
// DATAFILE LIST commands had been issued. This only happens when
// doing recovery with Recovery Manager, and is an internal error in
// Recovery Manager, because Recovery Manager should always issue
// RECOVER DATAFILE LIST before RECOVER DATAFILE START.
// *Action: Contact customer support
00298, 00000, "Missing or invalid attribute value"
// *Cause: A non-zero integer value is required when the following keyword
// attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT
// *Action: Correct the syntax and retry the command.
00299, 00000, "must use file-level media recovery on data file %s"
// *Cause: The control file does not contain an entry for this file, so
// block media recovery cannot be done.
// *Action: Restore the data file and perform file-level media recovery.
/
/ 300..369 - Redo File errors
/
00300, 00000, "illegal redo log block size %s specified - exceeds limit of %s"
// *Cause: The specified block size of the redo log is greater than the
// maximum block size for the operating system.
// *Action: Create the redo log on a device with a smaller block size
00301, 00000, "error in adding log file '%s' - file cannot be created"
// *Cause: The creation of the redo log file failed
// *Action: Check: 1) there is enough storage space on the device
// 2) the name of the file is valid
// 3) the device is online
// 4) an IO error occurred
// Also, it is possible REUSE was specified on the command line and
// a file of the incorrect size exists. Either do not specify REUSE
// or use a file of the correct size.
00302, 00000, "limit of %s logs exceeded"
// *Cause: The maximum number of redo log files has been exceeded.
// *Action: Use the CREATE CONTROLFILE command with a larger value
// for MAXLOGFILES if the compatibility is lower than 10.2.0.
// Otherwise, allocate more storage space for the control file.
00303, 00000, "cannot process Parallel Redo"
// *Cause: A redo log containing Parallel Redo has been detected.
// The current Oracle release cannot process this format of redo.
// *Action: Use a later release that supports Parallel Redo.
// to process this log.
00304, 00000, "requested INSTANCE_NUMBER is busy"
// *Cause: An instance tried to start by using a value of the
// initialization parameter INSTANCE_NUMBER that is already in use.
// *Action: Either
// a) specify another INSTANCE_NUMBER,
// b) shut down the running instance with this number
// c) wait for instance recovery to complete on the instance with
// this number.
00305, 00000, "log %s of thread %s inconsistent; belongs to another database"
// *Cause: The database ID in the redo log file does not match the database
// ID in the control file. This redo log file is not from the
// current database.
// *Action: Specify the correct redo log file, then retry the operation.
00306, 00000, "limit of %s instances in this database"
// *Cause: Starting this instance would exceed the maximum number
// of instances allowed for this database. This message occurs
// only with STARTUP shared and multiple instances.
// *Action: You cannot start more than the lower of
// a) port-specific limit as to the number of instances
// b) the number of instances specified at create-database time
00307, 00000, "requested INSTANCE_NUMBER out of range, maximum is %s"
// *Cause: The initialization parameter INSTANCE_NUMBER specified a
// number that was out of range.
// *Action: Change INSTANCE_NUMBER to a valid range and restart the
// instance. The minimum value is one and the maximum value is
// the lower of the operating system-specific maximum or
// the MAXINSTANCES option specified in the CREATE DATABASE
// statement. See also your operating system-specific Oracle
// documentation.
00308, 00000, "cannot open archived log '%s'"
// *Cause: The system cannot access a required archived redo log file.
// *Action: Check that the off line log exists, the storage device is
// online, and the archived file is in the correct location.
// Then attempt to continue recovery or restart the recovery
// session.
00309, 00000, "log belongs to wrong database"
// *Cause: The system cannot access the archived redo log because it
// belongs to another database.
// *Action: Specify the correct redo log file, then retry the operation.
00310, 00000, "archived log contains sequence %s; sequence %s required"
// *Cause: The archived log was out of sequence, probably because it
// was corrupt or the wrong redo log file name was specified
// during recovery.
// *Action: Specify the correct redo log file; then retry the operation.
00311, 00000, "cannot read header from archived log"
// *Cause: An I/O error occurred when attempting to read the log file header
// from the specified archived redo log file.
// *Action: Other messages will accompany this message. See the
// associated messages for the appropriate action to take.
00312, 00000, "online log %s thread %s: '%s'"
// *Cause: This message reports the filename for details of another message.
// *Action: Other messages will accompany this message. See the
// associated messages for the appropriate action to take.
00313, 00000, "open failed for members of log group %s of thread %s"
// *Cause: The online log cannot be opened. May not be able to find file.
// *Action: See accompanying errors and make log available.
00314, 00000, "log %s of thread %s, expected sequence# %s doesn't match %s"
// *Cause: The online log is corrupted or is an old version.
// *Action: Find and install correct version of log or reset logs.
00315, 00000, "log %s of thread %s, wrong thread # %s in header"
// *Cause: The online log is corrupted or is an old version.
// *Action: Find and install correct version of log or reset logs.
00316, 00000, "log %s of thread %s, type %s in header is not log file"
// *Cause: The online log is corrupted or is an old version.
// *Action: Find and install correct version of log or reset logs.
00317, 00000, "file type %s in header is not log file"
// *Cause: This is not an archived log file.
// *Action: Find the correct file and try again.
00318, 00000, "log %s of thread %s, expected file size %s doesn't match %s"
// *Cause: On header read the file size indicated in the control
// file did not match the file size contained in the log file.
// *Action: Restore correct file or reset logs.
00319, 00000, "log %s of thread %s has incorrect log reset status"
// *Cause: Check of log file header at database open found that an online
// log has log reset data that is different from the control file.
// The log is probably an incorrectly restored backup.
// *Action: Restore correct file or reset logs.
00320, 00000, "cannot read file header from log %s of thread %s"
// *Cause: The file is not available.
// *Action: Restore the log file.
00321, 00000, "log %s of thread %s, cannot update log file header"
// *Cause: Cannot write to the log file.
// *Action: Restore the access to the file.
00322, 00000, "log %s of thread %s is not current copy"
// *Cause: Check of log file header at database open found that an online
// log appears to be an incorrectly restored backup.
// *Action: Restore correct file or reset logs.
00323, 00000, "Current log of thread %s not useable and all others need archiving"
// *Cause: Attempt to open thread failed because it is necessary to switch
// redo generation to another online log, but all the other logs
// need to be archived before they can be used.
// *Action: Archive the logs for the thread then retry open.
00324, 00000, "log file '%s' translated name '%s' too long, %s characters exceeds %s limit"
// *Cause: the translated name for a log file is too long.
// *Action: Choose a untranslated name that yields a shorter translated name.
00325, 00000, "archived log for thread %s, wrong thread # %s in header"
// *Cause: The archived log is corrupted or for another thread. Can not
// use the log for applying redo.
// *Action: Find correct archived log.
00326, 00000, "log begins at change %s, need earlier change %s"
// *Cause: The archived log supplied for recovery was generated after the
// log that is needed. Can not yet use the log for applying redo.
// *Action: Find correct archived log.
00327, 00000, "log %s of thread %s, physical size %s less than needed %s"
// *Cause: A log file has shrunk in size. This is likely
// to have been caused by operator or operating system error.
// *Action: Restore the log file from backup. If backup is not available,
// drop this log and re-create. If the database was shut down
// cleanly, no further action should be required; otherwise
// incomplete recovery may be required.
00328, 00000, "archived log ends at change %s, need later change %s"
// *Cause: The archived log supplied for recovery was generated before the
// log that is needed. Can not use the log for applying redo.
// *Action: Find correct archived log.
00329, 00000, "archived log begins at change %s, need change %s"
// *Cause: The archived log is not the correct log. An earlier log is needed.
// *Action: Restore the correct log file.
00330, 00000, "archived log ends at change %s, need change %s"
// *Cause: The archived log is not the correct log. A later log is needed.
// *Action: Restore the correct log file.
00331, 00000, "log version %s incompatible with ORACLE version %s"
// *Cause: The log was written by incompatible version of Oracle.
// *Action: Recover the database with the compatible software, shut it
// down cleanly, then restart with current software.
00332, 00000, "archived log is too small - may be incompletely archived"
// *Cause: The log is smaller than the space allocated in it. May be the
// result of a shutdown abort while it was being written by the
// archiver.
// *Action: Get a complete version of this log and use it for recovery. There
// should either be an online version of it or a copy that was
// successfully archived.
00333, 00000, "redo log read error block %s count %s"
// *Cause: An IO error occurred while reading the log described in the
// accompanying error.
// *Action: Restore accessibility to file, or get another copy of the file.
00334, 00000, "archived log: '%s'"
// *Cause: Reporting filename for details of another error
// *Action: See associated error messages
00335, 00000, "online log %s: No log with this number, log does not exist"
// *Cause: Reporting filename for details of another error
// *Action: See associated error messages
00336, 00000, "log file size %s blocks is less than minimum %s blocks"
// *Cause: The log file size as specified in create database is too small.
// *Action: Increase the log file size.
00337, 00000, "log file '%s' does not exist and no size specified"
// *Cause: An attempt to add a log found neither an existing file
// nor a size for creating the file.
// *Action: Specify a size for the log file.
00338, 00000, "log %s of thread %s is more recent than control file"
// *Cause: The control file change sequence number in the log file is
// greater than the number in the control file. This implies that
// the wrong control file is being used. Note that repeatedly causing
// this error can make it stop happening without correcting the real
// problem. Every attempt to open the database will advance the
// control file change sequence number until it is great enough.
// *Action: Use the current control file or do backup control file recovery to
// make the control file current. Be sure to follow all restrictions
// on doing a backup control file recovery.
00339, 00000, "archived log does not contain any redo"
// *Cause: The archived log is not the correct log. It is a copy of a log file
// that has never been used for redo generation, or was an online
// log being prepared to be the current log.
// *Action: Restore the correct log file.
00340, 00000, "IO error processing online log %s of thread %s"
// *Cause: An IO error occurred on the named online log.
// *Action: Restore accessibility to file, or restore file from backup.
00341, 00000, "log %s of thread %s, wrong log # %s in header"
// *Cause: The internal information in an online log file does not
// match the control file.
// *Action: Restore correct file or reset logs.
00342, 00000, "archived log does not have expected resetlogs SCN %s"
// *Cause: Recovery was given a log that does not belong to current
// incarnation or one of the parent incarnation. There should be
// another log that contains the correct redo.
// *Action: Supply the correct log file.
00344, 00000, "unable to re-create online log '%s'"
// *Cause: An I/O failure occurred when attempting to re-create an online as
// part of either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE
// CLEAR LOGFILE command.
// *Action: Correct the file/device as indicated by accompanying errors.
00345, 00000, "redo log write error block %s count %s"
// *Cause: An IO error has occurred while writing the log
// *Action: Correct the cause of the error, and then restart the system.
// If the log is lost, apply media/incomplete recovery.
00346, 00000, "log member marked as STALE and closed"
// *Cause: A log file member was no longer complete.
// *Action: Correct the underlying problem by referring to the other error
// messages found with this one.
00347, 00000, "log %s of thread %s, expected block size %s doesn't match %s"
// *Cause: On header read the blocksize indicated in the control
// file did not match the blocksize contained in the log file.
// *Action: Restore correct file or reset logs.
00348, 00000, "single-process redo failure. Must abort instance"
// *Cause: A failure occurred during a critical portion of the log code
// during single process operation. This error does not occur
// during normal multi-process operation.
// *Action: Shutdown abort and warmstart the database.
00349, 00000, "failure obtaining block size for '%s'"
// *Cause: The operating system was unable to determine the blocksize
// for the given filename.
// *Action: Consult the accompanying error message, and correct the
// device or specify another filename.
00350, 00000, "log %s of instance %s (thread %s) needs to be archived"
// *Cause: The command cannot be done because the log has not been archived,
// and media recovery has been enabled.
// *Action: Archive the log or disable media recovery. If the command supports
// an UNARCHIVED option then it can be used. However this may result
// in making backups unuseable, and forcing the drop of some offline
// files.
00351, 00000, "recover-to time invalid"
// *Cause: The time specified in a recover-until statement must
// be after January 1st 1988.
// *Action: Specify a time after January 1st 1988.
00352, 00000, "all logs for thread %s need to be archived - cannot enable"
// *Cause: Attempting to enable a thread with all logs needing to be
// archived, and media recovery has been enabled. There is no log
// that can be made the new current log for the thread.
// *Action: Archive a log for the thread or disable media recovery.
00353, 00000, "log corruption near block %s change %s time %s"
// *Cause: Some type of redo log corruption has been discovered. This error
// describes the location of the corruption. Accompanying errors
// describe the type of corruption.
// *Action: Do recovery with a good version of the log or do incomplete
// recovery up to the indicated change or time.
00354, 00000, "corrupt redo log block header"
// *Cause: The block header on the redo block indicated by the accompanying
// error, is not reasonable.
// *Action: Do recovery with a good version of the log or do time based
// recovery up to the indicated time. If this happens when archiving,
// archiving of the problem log can be skipped by clearing the log
// with the UNARCHIVED option. This must be followed by a backup of
// every datafile to insure recoverability of the database.
00355, 00000, "change numbers out of order"
// *Cause: A change number found in the redo log is lower than a previously
// encountered change number. The log is corrupted in some way. The
// corruption may be at the earlier change or at this one.
// *Action: Do recovery with a good version of the log or do time based
// recovery up to the indicated time.
00356, 00000, "inconsistent lengths in change description"
// *Cause: A change record in the redo log contains lengths that do not add
// up to a consistent value. The log is corrupted in some way.
// *Action: Do recovery with a good version of the log or do time based
// recovery up to the indicated time.
00357, 00000, "too many members specified for log file, the maximum is %s"
// *Cause: An add logfile or add logfile member command would result in a
// log with too many members. The number of members is set when the
// database is created.
// *Action: Use fewer log file members.
00358, 00000, "Too many file members specified, the maximum is %s"
// *Cause: A create or alter statement specified too many members in a
// parenthesised file list.
// *Action: Specify a number of file members that is within the port-defined
// limit.
00359, 00000, "logfile group %s does not exist"
// *Cause: An add logfile member or drop logfile request specified a logfile
// group number that does not exist.
// *Action: Check the configuration of the log files and reissue the command.
00360, 00000, "not a logfile member: %s"
// *Cause: A filename was given to drop logfile member that is not a
// part of the database, or which is a data file.
// *Action: Supply a valid logfile member name.
00361, 00000, "cannot remove last log member %s for group %s"
// *Cause: An attempt has been made to remove the last member of a log file
// group.
// *Action: If desired, delete the entire log, by using DROP LOGFILE.
00362, 00000, "member is required to form a valid logfile in group %s"
// *Cause: A request to drop a logfile member was denied because it would
// remove data required to form a complete logfile.
// *Action: If desired, delete the entire log (after archiving if required),
// by using DROP LOGFILE;
00363, 00000, "log is not the archived version"
// *Cause: The log given to recovery is a backup of the online version from
// the time it was the current log. The archived version of the log
// would not be marked as end of thread. This error can also be
// caused by failing to list the current log of an enabled thread
// in a CREATE CONTROLFILE command.
// *Action: Find the archived version of the log and supply its name. If this
// is media recovery immediately following a CREATE CONTROLFILE, be
// sure the current log for this thread was included.
00364, 00000, "cannot write header to new log member"
// *Cause: An i/o error occurred when attempting to write the header to a
// log member that is being added to an existing group.
// *Action: See accompanying errors. Fix problem or use another file.
00365, 00000, "the specified log is not the correct next log"
// *Cause: The specified log failed to pass checks to ensure it corresponds
// to the log that was just applied. This is probably the result
// of using a log that was generated against a cold backup image
// of the database.
// *Action: Find the log that was generated by this copy of the database
// and give that filename to recovery.
00366, 00000, "log %s of thread %s, checksum error in the file header"
// *Cause: The file header for the redo log contains a checksum that does
// not match the value calculated from the file header as read from
// disk. This means the file header is corrupted
// *Action: Find and install correct version of log or reset logs.
00367, 00000, "checksum error in log file header"
// *Cause: The file header for the redo log contains a checksum that does
// not match the value calculated from the file header as read from
// disk. This means the file header is corrupted
// *Action: Find the correct file and try again.
00368, 00000, "checksum error in redo log block"
// *Cause: The redo block indicated by the accompanying error, is not
// vaild. It has a checksum that does not match the block contents.
// *Action: Do recovery with a good version of the log or do time based
// recovery up to the indicated time. If this happens when archiving,
// archiving of the problem log can be skipped by clearing the log
// with the UNARCHIVED option. This must be followed by a backup of
// every datafile to insure recoverability of the database.
// *Action: Restore correct file or reset logs.
00369, 00000, "Current log of thread %s not useable and other log being cleared"
// *Cause: Attempt to open thread failed because it is necessary to switch
// redo generation to another online log, but all the other logs are
// being cleared or need to be archived before they can be used.
// *Action: If the ALTER DATABASE CLEAR LOGFILE command is still active then
// wait for it to complete. Otherwise reissue the CLEAR command. If
// there are other online logs for the thread, that are not being
// cleared, then archive the logs.
/
/ 370-389 kcb external errors
/
00370, 00000, "potential deadlock during kcbchange operation"
// *Cause: Error code used internally by software. Should never be reported
// *Action: Treat as internal error. See error 600.
00371, 00000, "not enough shared pool memory, should be at least %s bytes"
// *Cause: The SHARED_POOL_SIZE initialization parameter was too small.
// *Action: Increase the parameter value.
00372, 00000, "file %s cannot be modified at this time"
// *Cause: attempting to modify the contents of a file that cannot be
// modified. The file is most likely part of a read only tablespace
// but may be in the process of going offline, or the database may
// be in the process of closing.
// *Action: check the status of the file and its tablespace
00373, 00000, "online log version %s incompatible with ORACLE version %s"
// *Cause: The online log was written by incompatible version of Oracle.
// Can occur when the log file was created by either a new or
// older version of Oracle.
// *Action: Recover the database with the compatible software, shut it
// down cleanly, then restart with current software.
00374, 00000, "parameter db_block_size = %s invalid ; must be a multiple of %s in the range [%s..%s]"
// *Cause: invalid value for db_block_size parameter
// *Action: adjust parameter and restart
00375, 00000, "Cannot allocate buffer cache state object"
// *Document: NO
// *Cause: No state obeject elements on freelist
// *Action: None.
00376, 00000, "file %s cannot be read at this time"
// *Cause: attempting to read from a file that is not readable. Most likely
// the file is offline.
// *Action: Check the state of the file. Bring it online
00377, 00000, "Frequent backups of file %s causing write operation to stall"
// *Cause: Backups are occurring too frequently on this file. Each time a new
// backup is started for a file, any writes which have been previously
// issued (but not completed) have to be re-issued. If hot backups
// are started very, very frequently, it is possible that some writes
// will be re-issued repeatedly and never complete.
// *Action: Increase the interval between begin hot-backup commands for this
// file.
//
00378, 00000, "buffer pools cannot be created as specified"
// *Cause: Either the number of buffers or the number of lru latches is
// too small to satisfy the specified buffer pool configuration.
// *Action: Either increase the number of buffers and/or number of lru latches
// or configure smaller buffer pools.
//
00379, 00000, "no free buffers available in buffer pool %s for block size %sK"
// *Cause: All buffers in the specified buffer pool for the specified block size
// are in use and no free buffers are available.
// *Action: Increase the number of buffers in the specified pool for the specified
// block size
//
00380, 00000, "cannot specify db_%sk_cache_size since %sK is the standard block size"
// *Cause: User specified the parameter db_nk_cache_size (where n is one of
// 2,4,8,16,32), while the standard block size for this database is
// equal to n Kbytes. This is illegal.
// *Action: Specify the standard block size cache using db_cache_size (DEFAULT
// pool) (and db_recycle_cache_size, db_keep_cache_size if additional
// buffer pools are required). Do NOT use the corresponding
// db_nk_cache_size parameter for the standard block size.
//
00381, 00000, "cannot use both new and old parameters for buffer cache size specification"
// *Cause: User specified one or more of { db_cache_size ,
// db_recycle_cache_size, db_keep_cache_size,
// db_nk_cache_size (where n is one of 2,4,8,16,32),
// db_cache_advice } AND one or more of { db_block_buffers,
// buffer_pool_keep , buffer_pool_recycle }. This is illegal.
// *Action: Use EITHER the old (pre-Oracle_8.2) parameters OR the new
// ones. Don't specify both. If old size parameters are specified in
// the parameter file, you may want to replace them with new parameters
// since the new parameters can be modified dynamically and allow
// you to configure additional caches for additional block sizes.
// Cache advisory can only be enabled with the new cache parameters.
//
00382, 00000, "%s not a valid block size, valid range [%s..%s]"
// *Cause: User specified a value for db_nk_cache_size where n is one of
// {2, 4, 8, 16, 32}, but nk is not a valid block size for this
// platform.
// *Action: Remove corresponding parameter from the "init.ora" file and
// restart the instance.
00383, 00000, "DEFAULT cache for blocksize %s cannot be reduced to zero"
// *Cause: User attempted to reduce db_cache_size to zero, or attempted to
// to reduce db_<n>K_cache_size to zero while there were still online
// tablespaces with blocksize <n>K. Note that since the SYSTEM tablespace
// cannot be taken offline, it is always illegal to set db_cache_size to zero.
// *Action: Offline any tablespaces with the corresponding blocksize and then
// perform the operation again.
00384, 00000, "Insufficient memory to grow cache"
// *Cause: The system could not allocate sufficient memory to grow the
// cache to the specified size.
// *Action: Attempt a smaller increase in the value of the parameter.
00387, 00000, "version of the block on disk may be stale"
// *Document: NO
// *Cause: Error code used internally by software. Used during flashback
// before image logging to to indicate that on-disk version of the
// block may be stale. This error is not expected to be user visible.
// *Action: None.
00388, 00000, "dependent redo for buffers is lost"
// *Cause: The instance contained buffers that had non-durable changes
// and depended on redo in another thread that was lost because
// of that thread crash. No data are lost because changes to
// such buffers cannot be commited while they are non-durable.
// *Action: Restart the instance.
//
//
/
/ 390-399: more Redo log errors
/
00390, 00000, "log %s of thread %s is being cleared, cannot become current log"
// *Cause: An attempt to switch to a new online log for the redo thread
// failed because no reusable log could be found. This log is being
// cleared and will be useable when the clearing completes. The
// command that began the clearing may have terminated without
// completing the clearing.
// *Action: If the clear command is still executing then wait for its
// completion. If it terminated then reissue the clear command, or
// drop the log.
00391, 00000, "All threads must switch to new log format at the same time"
// *Cause: An attempt to switch the current log of a single thread is not
// allowed because the compatiblity requirements force a new log
// format version number. When changing log formats, all threads
// must switch to the new format at the same time.
// *Action: Open the database to cause the coordinated log switch. If that
// is not possible then return to the same software version and
// compatibility setting last used to open the database.
00392, 00000, "log %s of thread %s is being cleared, operation not allowed"
// *Cause: An operation encountered this online log in the middle of being
// cleared. The command that began the clearing may have terminated
// without completing the clearing.
// *Action: If the clear command is still executing then wait for its
// completion. If it terminated then reissue the clear command, or
// drop the log.
00393, 00000, "log %s of thread %s is needed for recovery of offline datafiles"
// *Cause: Log cannot be cleared because the redo in it is needed to recover
// offline datafiles. It has not been archived so there is no
// other copy available. If the log is cleared the tablespaces
// containing the files will have to be dropped.
// *Action: Archive the log then repeat the clear command. If archiving is not
// possible, and dropping the tablespaces is acceptible, then add the
// clause UNRECOVERABLE DATAFILE at the end of the clear command.
00394, 00000, "online log reused while attempting to archive it"
// *Cause: It has been detected that an online log that is being archived
// has been reused
// *Action: Cannot archive the logfile anymore since it has been overwritten
00395, 00000, "online logs for the clone database must be renamed"
// *Cause: A clone database open forces logfile renaming to avoid
// overwriting the primary logfiles
// *Action Rename the logfiles manually or using the log_file_name_convert
// initialization parameter
00396, 00000, "error %s required fallback to single-pass recovery"
// *Cause: The indicated error caused two-pass instance or
// crash recovery to fail. Recovery was retried with an
// alternate (slower) method to avoid the error.
// *Action Correct the cause of the indicated error (also recorded)
// so that future instance or crash recovery can succeed with the
// two-pass algorithm. This usually requires making more main
// memory available to the recovery process.
00397, 00000, "instance recovery process terminated with error"
// *Cause: The foreground process doing instance recovery died.
// *Action: Check the foreground trace file for the cause of recovery failure.
00398, 00000, "abort thread recovery due to reconfiguration"
// *Cause: Global enqueue service reconfiguration occurred during
// instance/crash recovery.
// *Action: This is used internally, no action is required.
00399, 0000, "corrupt change description in redo log"
// *Cause: A change vector in the redo log failed validation checks.
// *Action: Do recovery with a good version of the log or do time based
// recovery up to the indicated time.
/
/ 400-420: KCK errors
/
00400, 00000, "invalid release value %s for parameter %s"
// *Cause: The release level given for the specified init parameter is
// invalid.
// *Action: Correct the parameter value in the parameter file and retry.
00401, 00000, "the value for parameter %s is not supported by this release"
// *Cause: The value specified cannot be supported by this release of
// the software.
// *Action: Choose an appropriate value, or remove the parameter value to
// use the default value.
00402, 00000, "database changes by release %s cannot be used by release %s"
// *Cause: Changes have been made to the database that require a newer
// software release or that violate the compatibility parameters.
// *Action: Use a version of the software that can understand the changes or
// relax the compatibility requirements in the init file.
00403, 00000, "%s (%s) is not the same as other instances (%s)"
// *Cause: Another instance has set the compatible or compatible no
// recovery parameters differently than this instance.
// *Action: Change the parameters of the current instance to match other
// instances already running.
00404, 00000, "Convert file not found: '%s'"
// *Cause: The file used for converting the database from V7 to V8 could
// not be found.
// *Action: Verify that the migration process has been started on this
// database and that the convert filename is accessable.
00405, 00000, "compatibility type \"%s\""
// *Cause: Reporting a type associated with another error.
// *Action: See accompanying error
00406, 00000, "COMPATIBLE parameter needs to be %s or greater"
// *Cause: The COMPATIBLE initialization parameter is not high
// enough to allow the operation. Allowing the command would make
// the database incompatible with the release specified by the
// current COMPATIBLE parameter.
// *Action: Shutdown and startup with a higher compatibility setting.
00407, 00000, "rolling upgrade from release %s.%s to %s.%s is not allowed"
// *Cause: Another instance executing software at a different point release
// already has the database mounted.
// *Action: Shutdown all instances then startup with the new software.
00408, 00000, "parameter %s is set to TRUE"
// *Cause: Reporting the parameter that resulted in the compatibility error.
// *Action: Shutdown and startup with a higher compatibility setting.
00409, 00000, "COMPATIBLE needs to be %s or higher to use AUTO SEGMENT SPACE MANAGEMENT"
// *Cause: This is due to migrating from an older release of Oracle with
// tablespaces created using AUTO SEGMENT SPACE MANAGEMENT.
// To open the database, the COMPATIBLE parameter needs to
// be set to the specified value.
// *Action: Shutdown and startup with the specified compatibility setting.
00421, 00000, "failure in creating the required number of sessions for %s processes"
// *Cause: The required number of sessions for the PROCESSES parameter was
// greater than the maximum supported value.
// *Action: Decrease the required number of processes and start the instance.
/
/ 436-439: Oracle licensing ercs
/
00436, 00000, "ORACLE is not licensed. Contact Oracle Corp. for assistance"
// *Cause:
// *Action:
00437, 00000, "ORACLE feature is not licensed. Contact Oracle Corp. for assistance"
// *Cause: ORACLE feature is not licensed.
// *Action: Contact ORACLE for assistance.
00438, 00000, "%s Option not installed"
// *Cause: The specified option is not installed.
// *Action: Purchase and install the option.
00439, 00000, "feature not enabled: %s"
// *Cause: The specified feature is not enabled.
// *Action: Do not attempt to use this feature.
/
/ 440-460 Detached process startup errors
/
00442, 0000,"Oracle Database Express Edition (XE) single instance violation error"
// *Cause: An attempt was made to start more than one Oracle Database Express
// Edition (XE) instance.
// *Action: Upgrade to Oracle Database Standard Edition (SE) or Oracle Database
// Enterprise Edition (EE) if you want to run more than one instance.
00443, 00000, "background process \"%s\" did not start"
// *Cause: The specified process did not start.
// *Action: Ensure that the executable image is in the correct place with
// the correct protections, and that there is enough memory.
00444, 00000, "background process \"%s\" failed while starting"
// *Cause: Usually due to a bad (or non-existent) background process image.
// *Action: Get a good background process image.
00445, 00000, "background process \"%s\" did not start after %s seconds"
// *Cause: The specified process did not start after the specified time.
// *Action: Ensure that the background did not die and leave a trace file.
00446, 00000, "background process started when not expected"
// *Cause: The background process specified started up AFTER the RDBMS was
// already running.
// *Action: If nobody at your site started the process, then this is an
// internal error.
00447, 00000, "fatal error in background process"
// *Cause: One of the background processes died unexpectedly.
// *Action: Warm start the system.
00448, 00000, "normal completion of background process"
// *Cause: One of the background processes completed normally (i.e. exited).
// The background process thinks that somebody asked it to exit.
// *Action: Warm start the system.
00449, 00000, "background process '%s' unexpectedly terminated with error %s"
// *Cause: A foreground process needing service from a background
// process has discovered the process died.
// *Action: Consult the error code, and the trace file for the process.
00450, 00000, "background process '%s' did not start"
// *Cause: The specified process did not start.
// *Action: Consult the error code, and the trace file for the process.
00451, 00000, "foreground process died unexpectedly"
// *Cause: The foreground process for the new connection did not start.
// *Action: Reconnect to Oracle.
00452, 00000, "foreground process unexpectedly terminated with error %s"
// *Cause: The foreground process for the new connection did not start.
// *Action: Reconnect to Oracle.
00453, 00000, "backgroud process '%s' is dead"
// *Cause: The background process that was being messaged was dead
// or its incarnation was invalid.
// *Action: Restart the background process.
00454, 00000, "The background process '%s' is running"
// *Cause: An attempt to spawn a background process that was already running failed.
// *Action: None.
00455, 00000, "timeout waiting for background process '%s' cleanup"
// *Cause: The state of the background process was not cleaned up.
// *Action: None.
00456, 00000, "prespawn not enabled"
// *Cause: Prespawn was not enabled.
// *Action: None.
00457, 00000, "process pool not found"
// *Cause: The process pool was not found.
// *Action: Verify the process pool name.
00458, 00000, "process pool is already started"
// *Cause: The process pool was already started.
// *Action: None.
00459, 00000, "process pool is not started"
// *Cause: The process pool was not started.
// *Action: None.
00460, 00000, "process pool invalid configuration value(s)"
// *Cause: Invalid configuration values were specified for the process pool.
// *Action: Verify the configuration values.
00461, 00000, "MGA namespace already opened."
// *Cause: Managed Global Area(MGA) namespace was already opened.
// *Action: None.
00462, 00000, "MGA namespace shared handle not valid."
// *Cause: Managed Global Area(MGA) namespace shared handle was not valid.
// *Action: None.
00463, 00000, "MGA namespace private handle not valid."
// *Cause: Managed Global Area(MGA) namespace private handle was not valid.
// *Action: None.
00464, 00000, "Processes are still attached to MGA namespace."
// *Cause: Processes were still attached to Managed Global Area(MGA) namespace.
// *Action: None.
00465, 00000, "Segments are still attached to MGA namespace."
// *Cause: Segments were still attached to Managed Global Area(MGA) namespace.
// *Action: None.
00466, 00000, "MGA invalid segment information."
// *Cause: Managed Global Area(MGA) segment information was not valid.
// *Action: None.
00467, 00000, "Already attached to MGA handle."
// *Cause: There was already an attachement to the Managed Global Area(MGA) handle.
// *Action: None.
00468, 00000, "Not attached to MGA handle."
// *Cause: There was no attachement to the Managed Global Area(MGA) handle.
// *Action: None.
/
/ 469-525 Detached process death errors (signaled in foreground)
/
00469, 00000, "CKPT process terminated with error"
// *Cause: The checkpoint process died
// *Action: Warm start instance
00470, 00000, "LGWR process terminated with error"
// *Cause: The log writer process died
// *Action: Warm start instance
00471, 00000, "DBWR process terminated with error"
// *Cause: The database writer process died
// *Action: Warm start instance
00472, 00000, "PMON process terminated with error"
// *Cause: The process cleanup process died
// *Action: Warm start instance
00473, 00000, "ARCH process terminated with error"
// *Cause: The archive process died
// *Action: Warm start instance
00474, 00000, "SMON process terminated with error"
// *Cause: The system cleanup process died
// *Action: Warm start instance
00475, 00000, "TRWR process terminated with error"
// *Cause: The system tracing process died
// *Action: Warm start instance
00476, 00000, "RECO process terminated with error"
// *Cause: The distributed transaction (two-phase commit) recovery process
// died.
// *Action: Warm start instance
00477, 00000, "SNP* process terminated with error"
// *Cause: A materialized view refresh process died
// *Action: PMON will restart SNP process shortly. If SNP process does not
// get started, contact Oracle support.
00478, 00000, "SMON process terminated due to error %s"
// *Cause: SMON was unable to service the requests due to error in
// cleanup of resources
// *Action: Warm start instance
00479, 00000, "RVWR process terminated with error %s"
// *Cause: The RVWR process died
// *Action: Warm start instance
00480, 00000, "LCK* process terminated with error"
// *Cause: A system lock process died
// *Action: Warm start instance
00481, 00000, "LMON process terminated with error"
// *Cause: The global enqueue service monitor process died
// *Action: Warm start instance
00482, 00000, "LMD* process terminated with error"
// *Cause: A global enqueue service daemon process died
// *Action: Warm start instance
00483, 00000, "During shutdown a process abnormally terminated"
// *Cause: One of the background processes did not exit normally at or near
// the time of shutdown.
// *Action: Use shutdown abort.
00484, 00000, "LMS* process terminated with error"
// *Cause: A global cache service process died
// *Action: Warm start instance
00485, 00000, "DIAG process terminated with error %s"
// *Cause: A global diagnostic process died
// *Action: Wait for process to restart
00486, 00000, "ASMB process terminated with error"
// *Cause: An ASM background process died.
// *Action: Warm start instance. Also check that ASM Instance is running.
00487, 00000, "CTWR process terminated with error"
// *Cause: The change tracking process died
// *Action: Warm start instance
00488, 00000, "RBAL process terminated with error"
// *Cause: The ASM rebalance coordinator process died.
// *Action: Warm start instance.
00489, 00000, "ARB* process terminated with error"
// *Cause: An ASM rebalance worker process died.
// *Action: Wait for process to restart.
00490, 00000, "PSP process terminated with error"
// *Cause: The process spawner died
// *Action: Warm start instance
00491, 00000, "RMS0 process terminated with error"
// *Cause: The RAC Management Process died
00492, 00000, "GTX* process terminated with error"
// *Cause: A global transaction background process died.
// *Action: Warm start instance
00493, 00000, "GMON process terminated with error"
// *Cause: The ASM disk group monitor process died
// *Action: Warm start instance
00494, 00000, "enqueue %s held for too long (more than %s seconds) by 'inst %s, osid %s'"
// *Cause: The specified process did not release the enqueue within
// the maximum allowed time.
// *Action: Reissue any commands that failed and contact Oracle Support
// Services with the incident information.
00495, 00000, "GEN0 process terminated with error"
// *Cause: The generic background processing process died.
// *Action: Warm start the instance.
00496, 00000, "LMHB process terminated with error"
// *Cause: The LM heartbeat monitor process died.
// *Action: Warm start the instance.
00497, 00000, "XDMG process terminated with error"
// *Cause: The Cell automation manager process terminated with error.
// *Action: PMON will restart XDMG process shortly. If XDMG process does not
// restart, contact Oracle Support Services.
00498, 00000, "XDWK process terminated with error"
// *Cause: The Cell automation worker actions process terminated with error.
// *Action: PMON will restart XDWK process shortly. If XDWK process does not
// restart, contact Oracle Support Services.
00499, 00000, "XDMG repeatedly failed to initialize terminating the instance."
// *Cause: The Cell automation manager process repeatedly failed to
// initialize.
// *Action: Examine the alert log for the reason prior attempts to start
// XDMG failed. If it is due to user error or bad configuration,
// fix it and restart the instance. Otherwise, contact Oracle
// Support Services.
00500, 00000, "Listener registration process terminated with an error."
// *Cause: The listener registration process died.
// *Action: Warm start the instance.
00501, 00000, "CLMN process terminated with error"
// *Cause: The cleanup process died.
// *Action: Warm start the instance.
00502, 00000, "PMAN process terminated with error"
// *Cause: The manager process died.
// *Action: Warm start the instance.
00503, 00000, "CL** process terminated with error"
// *Cause: A cleanup slave died.
// *Action: Warm start the instance.
00504, 00000, "Service monitor background process terminated with error"
// *Cause: The service monitor background process died.
// *Action: PMON will restart the background process shortly.
00505, 00000, "GEN1 process terminated with error"
// *Cause: The generic background processing process 1 died.
// *Action: Warm start the instance.
00510, 00000, "not a valid MGA heap index"
// *Cause: The given Managed Global Area (MGA) index was not of the heap type.
// *Action: None.
00511, 00000, "Cluster flash cache background process terminated with error"
// *Cause: The cluster flash cache process died.
// *Action: Warm start the instance.
/
/ 00526-00565
/
00566, 00000, "cannot request processor group - NUMA not enabled"
// *Cause: Cannot start process in a requested processor group when
// the NUMA feature is disabled.
// *Action: Start the process without requesting a NUMA processor group.
/
00567, 00000, "Requested processor group %s is too large (maximum %s)"
// *Cause: The process could not be started in the requested processor group.
// *Action: Start the process in another processor group.
/
00568, 00000, "Maximum number of interrupt handlers exceeded"
// *Cause: User specified too many ^c handlers
// *Action: Remove some old handlers.
/
00569, 00000, "Failed to acquire global enqueue."
// *Cause: A prior error occurred on one of the instances in the cluster.
// Typically errors are caused by shared pool resource contention.
// *Action: Check for and resolve prior errors on all instances in the cluster.
// If there is shared pool resource contention, increase the
// SHARED_POOL_SIZE, DML_LOCKS, PROCESSES, TRANSACTIONS,
// CLUSTER_DATABASE_INSTANCES and PARALLEL_MAX_SERVERS initialization
// parameters.
/
/ 00570-00599 SQL*Connect Opening & Reading Files
/
00574, 00000, "osndnt: $CANCEL failure (break)"
// *Cause:
// *Action:
00575, 00000, "osndnt: $QIO failure (send out-of-band break)"
// *Cause:
// *Action:
00576, 00000, "in-band break protocol error"
// *Cause:
// *Action:
00577, 00000, "out-of-band break protocol error"
// *Cause:
// *Action:
00578, 00000, "reset protocol error"
// *Cause:
// *Action:
00579, 00000, "osndnt: server received malformed connection request"
// *Cause:
// *Action:
00580, 00000, "protocol versions do not match"
// *Cause:
// *Action:
00581, 00000, "osndnt: cannot allocate context area"
// *Cause:
// *Action:
00582, 00000, "osndnt: cannot deallocate context area"
// *Cause:
// *Action:
00583, 00000, "osndnt: $TRNLOG failure"
// *Cause:
// *Action:
00584, 00000, "cannot close connection"
// *Cause:
// *Action:
00585, 00000, "host name has incorrect form"
// *Cause:
// *Action:
00586, 00000, "osndnt: LIB$ASN_WTH_MBX failure"
// *Cause:
// *Action:
00587, 00000, "cannot connect to remote host"
// *Cause:
// *Action:
00588, 00000, "message from host was too short"
// *Cause:
// *Action:
00589, 00000, "message from host had incorrect data length"
// *Cause:
// *Action:
00590, 00000, "message from host had incorrect message type"
// *Cause:
// *Action:
00591, 00000, "incorrect number of bytes written"
// *Cause:
// *Action:
00592, 00000, "osndnt: $QIO failure (mailbox queue)"
// *Cause:
// *Action:
00593, 00000, "osndnt: $DASSGN failure (network device)"
// *Cause:
// *Action:
00594, 00000, "osndnt: $DASSGN failure (mailbox)"
// *Cause:
// *Action:
00595, 00000, "osndnt: $QIO failure (receive)"
// *Cause:
// *Action:
00596, 00000, "osndnt: $QIO failure (send)"
// *Cause:
// *Action:
00597, 00000, "osndnt: $QIO failure (mailbox requeue)"
// *Cause:
// *Action:
00598, 00000, "osndnt: $QIO failure (mailbox read)"
// *Cause:
// *Action:
00600, 00000, "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"
// *Cause: This is the generic internal error number for Oracle program
// exceptions. It indicates that a process has encountered a low-level,
// unexpected condition. The first argument is the internal message
// number. This argument and the database version number are critical in
// identifying the root cause and the potential impact to your system.
//
// *Action: Visit My Oracle Support to access the ORA-00600 Lookup tool
// (reference Note 600.1) for more information regarding the specific
// ORA-00600 error encountered.
//
// An Incident has been created for this error in the Automatic
// Diagnostic Repository (ADR). When logging a service request, use
// the Incident Packaging Service (IPS) from the Support Workbench
// or the ADR Command Interpreter (ADRCI) to automatically package the
// relevant trace information (reference My Oracle Support Note 411.1).
//
// The following information should also be gathered to help determine
// the root cause:
// - changes leading up to the error
// - events or unusual circumstances leading up to the error
// - operations attempted prior to the error
// - conditions of the operating system and databases at the time
// of the error
//
// Note: The cause of this message may manifest itself as different
// errors at different times. Be aware of the history of errors that
// occurred before this internal error.
00601, 00000, "cleanup lock conflict"
// *Cause: The process monitor (PMON) database process ran into a lock
// conflict while trying to recover the processes.
// *Action: This is an internal issue. No action required.
00602, 00000, "internal programming exception: [PC:%s] [ADDR:%s]"
// *Cause: An address violation was encountered.
// *Action: Report the issue as a bug.
/ Caution: following error code not relocatable
00603, 00000, "ORACLE server session terminated by fatal error"
// *Cause: An Oracle server session was in an unrecoverable state.
// *Action: Log in to Oracle again so a new server session will be created
// automatically. Examine the session trace file for more
// information.
00604, 00000, "error occurred at recursive SQL level %s"
// *Cause: An error occurred while processing a recursive SQL statement
// (a statement applying to internal dictionary tables).
// *Action: If the situation described in the next error on the stack
// can be corrected, do so; otherwise contact Oracle Support.
/
/0605 reserved for v2 compatibility
/
00606, 00000, "Internal error code"
// *Cause: A call to deferred upi functions was made in non deferred mode
// *Action: Report as a bug.
00607, 00000, "Internal error occurred while making a change to a data block"
// *Cause: An internal error or memory exception occurred while Oracle was
// applying redo to a data block.
// *Action: call Oracle Support
00608, 00000, "testing error [%s] [%s] [%s] [%s] [%s]"
// *Cause: Internal error reserved for testing.
// *Action: call Oracle Support
00609, 00000, "could not attach to incoming connection"
// *Cause: Oracle process could not answer incoming connection
// *Action: If the situation described in the next error on the stack
// can be corrected, do so; otherwise contact Oracle Support.
00610, 00000, "Internal error code"
// *Cause: Oracle process started too late
// *Action: This error should never be seen by the customer. Contact
// Oracle Support
00614, 00000, "quarantine limit has been reached"
// *Cause: A quarantine limit was reached and the instance was aborted.
// *Action: Restart the instance.
00700, 00000, "soft internal error, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"
// *Cause: Internal inconsistency that will not crash a process
// *Action: Report as a bug - the first argument is the internal error.
00701, 00000, "object necessary for warmstarting database cannot be altered"
// *Cause: Attempt to alter or drop a database object (table, cluster, or
// index) which are needed for warmstarting the database.
// *Action: None.
00702, 00000, "bootstrap verison '%s' inconsistent with version '%s'"
// *Cause: The reading version of the boostrap is incompatible with
// the current bootstrap version.
// *Action: Restore a version of the software that is compatible with this
// bootstrap version.
00703, 00000, "maximum number of row cache instance locks exceeded"
// *Cause: There are not enough row cache enqueues.
// *Action: Increase the row cache enqueue parameter and warm start the system.
00704, 00000, "bootstrap process failure"
// *Cause: Failure in processing bootstrap data - see accompanying error.
// *Action: Contact your customer support representative.
00705, 00000, "inconsistent state during start up; shut down the instance, then restart it"
// *Cause: A previous attempt to start an instance was terminated.
// *Action: Shut down the instance completely, then restart it.
00706, 00000, "error changing format of file '%s'"
// *Cause: An attempt to change the block0 format of the specified file
// failed because the file is read-only or offline.
// *Action: Make the file read-write or bring the file online and set
// the BLK0_FMTCHG event.
/
/ 00710 - 00719 reserved for tablespace rename feature
/
00710, 00000, "new tablespace name is the same as the old tablespace name"
// *Cause: An attempt to rename a tablespace failed because the new
// name is the same as the old name.
// *Action: No action required.
00711, 00000, "new tablespace name is invalid"
// *Cause: An attempt to rename a tablespace failed because the new name
// is invalid.
// *Action: Choose a valid new name and retry the command.
00712, 00000, "cannot rename system tablespace"
// *Cause: An attempt to rename the system tablespace failed.
// *Action: No action required.
/
/ event 720 - 739 is reserved for compatibility issues
/
00720, 00000, "ALTER DATABASE RESET COMPATIBILITY command has been de-supported"
// *Cause: ALTER DATABASE RESET COMPATIBILITY command has been de-supported
// since Oracle 10i.
// *Action: No action required.
00721, 00000, "changes by release %s cannot be used by release %s"
// *Cause: An attempt to import a tablespace failed because the tablespace
// contains changes that require a newer software release or that
// violate the compatibility parameters.
// *Action: Use a version of the software that can understand the changes or
// relax the compatibility requirements in the initialization
// parameter file.
00722, 00000, "Feature \"%s\""
// *Cause: Reporting name of the feature for details of another error.
// *Action: See associated error message.
00723, 00000, "Initialization parameter COMPATIBLE must be explicitly set"
// *Cause: Oracle detected that the initialization parameter COMPATIBLE was
// not explicitly specified, and the compatibility of the database is
// lower than the default value of the COMPATIBLE parameter. In order
// to use the new compatible setting, the intialization parameter
// must be explicitly set by the user.
// *Action: Explicitly set the value of COMPATIBLE parameter either in PFILE
// or SPFILE, whichever is used.
00724, 00000, "ALTER DATABASE CONVERT command has been de-supported"
// *Cause: ALTER DATABASE CONVERT command has been de-supported since
// Oracle 10i.
// *Action: No action required.
00725, 00000, "Desupported ALTER DATABASE SET STANDBY clause specified: %s"
// *Cause: A deprecated ALTER DATABASE SET STANDBY was specified.
// *Action: No action required.
/
/ event 740 - 741 is reserved for file size overflow issues
/
00740, 00000, "datafile size of (%s) blocks exceeds maximum file size"
// *Cause: The user specified datafile size exceeded maximum file size.
// *Action: Please check REFERENCE for maximum size. Reduce the size and retry.
00741, 00000, "logfile size of (%s) blocks exceeds maximum logfile size"
// *Cause: The user specified logfile size exceeded maximum logfile size.
// *Action: Please check REFERENCE for maximum size. Reduce the size and retry.
/
/ event 742 - 815 is reserved for recovery issues
/
00742, 00000, "Log read detects lost write in thread %s sequence %s block %s"
// *Cause: Either a write issued by Oracle was lost by the underlying
// operating system or storage system or an Oracle internal error
// occurred.
// *Action: The trace file shows the lost write location. Dump the problematic
// log file to see whether it is a real lost write. Contact Oracle
// Support Services.
00750, 00000, "database has been previously mounted and dismounted"
// *Cause: The instance has already mounted and dismounted the database,
// which is only allowed once in its lifetime.
// *Action: Shut down the database.
00751, 00000, "could not obtain resilvering status for file"
// *Cause: An error occurred while obtaining the mirror resilvering status
// of a file.
// *Action: Refer to other error messages shown for additional details of
// the problem.
00752, 00000, "recovery detected a lost write of a data block"
// *Cause: A data block write to storage was lost during
// normal database operation on the primary database.
// *Actions: Shutdown the primary database and activate the physical
// standby database to failover. Call Oracle Support Services.
// See the Data Guard documentation for details.
00753, 00000, "recovery detected a lost write of a data block"
// *Cause: A data block write to storage was lost during
// normal redo database operation on the standby database or during
// recovery on a primary database.
// *Action: Close the database and try the RECOVER MANAGED STANDBY
// DATABASE (on the standby database) or RECOVER DATABASE
// ... FORCE START AT (on the primary database) statement
// starting at the SCN of the bad block that was printed already.
// See the Administrator's Guide for details.
00754, 00000, "recovery detected a data block with invalid SCN"
// *Cause: An error caused a data block mismatch with a log record.
// *Actions: If running on a primary database in recovery mode, you may perform
// a point-in-time recovery to an earlier time. Otherwise,
// call Oracle Support Services. See the Administrator's Guide
// for details.
00756, 00000, "recovery detected a lost write of a data block"
// *Cause: A data block write to storage was lost during
// normal redo database operation on the standby database or during
// recovery on a primary database.
// *Action: Close the database and try the RECOVER MANAGED STANDBY
// DATABASE (on the standby database) or RECOVER DATABASE ...
// FORCE START AT (on the primary database) statement starting
// at the SCN of the bad block that was printed already.
// See the Administrator's Guide for details.
00758, 00000, "recovery detected a block with inconsistent flag values set"
// *Cause: An internal error occurred.
// *Actions: If running on a primary database in recovery mode, you may
// perform a point-in-time recovery to an earlier time. Otherwise,
// call Oracle Support Services. See the Administrator's Guide
// for details.
00759, 00000, "session suspension timed out during switchover or failover"
// *Cause: The standby database was going through a role transition and
// the new primary database was not reopened in the configured timeout
// duration after switchover.
// *Actions: Open the new primary database and try to connect again.
00760, 0000, "could not remove lost write tracking from data file - check log"
// *Cause: An error occurred while trying to remove lost write tracking.
// *Actions: Check the system log for ERROR: or WARNING: for further
// information.
00761, 0000, "could not suspend lost write tracking for data file - check log"
// *Cause: An error occurred while trying to suspend lost write tracking.
// *Actions: Check the alert log for ERROR: or WARNING: for further
// information.
00762, 0000, "could not change lost write protection - out of memory"
// *Cause: Memory allocation failed.
// *Actions: Ensure that enough memory including stack memory is available
00763, 0000, "could not add lost write tracking to data file"
// *Cause: An error occurred while trying to add lost write tracking; could not
// lookup target data file.
// *Actions: This may be an internal error if the target data file exists.
00764, 00000, "The current transaction started on standby database and attempted to make an update after role transition."
// *Cause: The session, which started a transaction on the standby database and
// stayed alive after a role transition, attempted to do an update.
// *Actions: The client should catch the exception and retry the transaction.
//
00816, 00000, "error message translation failed"
// *Cause:
// *Action:
/
/ event 820-850 reserved for sga auto management issues
00820, 00000, "Specified value of sga_max_size is too small, needs to be at least %sM"
// *Cause: The specified value of sga_max_size is too small for the SGA to
// accommodate all of the necessary SGA components such as the
// log buffer, buffer pools, shared pool, etc.
// *Action: Set sga_max_size to the recommended value or reduce the values
// of any SGA component size parameters you have specified.
00821, 00000, "Specified value of sga_target %sM is too small, needs to be at least %sM"
// *Cause: The specified value of sga_target is too small for the SGA to
// accommodate all of the necessary SGA components such as the
// log buffer, buffer pools, shared pool, etc.
// *Action: Set sga_target to the recommended value or reduce the values
// of any SGA component size parameters you have specified.
00822, 00000, "MMAN process terminated with error"
// *Cause: The Memory Management process died.
// *Action: Warm start instance
00823, 00000, "Specified value of sga_target greater than sga_max_size"
// *Cause: The specified value of sga_target is greater than sga_max_size.
// *Action: Increase sga_max_size to match up with sga_target or decrease
// sga_target to match up with sga_maxsize.
00824, 00000, "cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings"
// *Cause: Could not set SGA_TARGET or MEMORY_TARGET due to current parameter settings.
// *Action: Check the other error messages for additional information.
00825, 00000, "cannot set DB_BLOCK_BUFFERS if SGA_TARGET or MEMORY_TARGET is set"
// *Cause: SGA_TARGET or MEMORY_TARGET set with DB_BLOCK_BUFFERS set.
// *Action: Do not set SGA_TARGET, MEMORY_TARGET or use new cache parameters,
// and do not use DB_BLOCK_BUFFERS which is an old cache parameter.
00826, 00000, "cannot set SGA_TARGET or MEMORY_TARGET for an ASM instance"
// *Cause: SGA_TARGET or MEMORY_TARGET set for an ASM instance.
// *Action: Do not set SGA_TARGET or MEMORY_TARGET.
00827, 00000, "could not shrink sga_target to specified value"
// *Cause: Attempted to shrink the SGA to the specified value but did not
// succeed because the SGA components could not be shrunk as they
// were already at their minimum sizes.
// *Action: Do not set sga_target to a value below the current value without
// first shrinking the individual SGA components.
00828, 00000, "specified value of shared_pool_reserved_size inconsistent with internal settings"
// *Cause: Unable to set shared_pool_reserved_size to specified value if
// SGA_TARGET set, either because the specified value is too
// small, or because it is too large for the current internal
// size of shared pool. More details can be found in the alert log.
// *Action: If possible, do not set shared_pool_reserved_size without setting
// shared_pool_size if SGA_TARGET set. Examine the alert log for
// information about current internal size of shared pool, and valid
// range of values for shared_pool_reserved_size.
00829, 00000, "event to stress test self tuning SGA feature by forcing partial granules transfers"
// *Document: NO
// *Cause:
// *Action:
00830, 00000, "cannot set statistics_level to BASIC with auto-tune SGA enabled"
// *Cause: The user attempted to set statistics_level to BASIC with auto-tune
// SGA enabled which cannot be done because auto-tune SGA cannot work
// with statistics_level set to BASIC.
// *Action: Disable auto-tune SGA and try setting the statistics_level to
// BASIC again.
00831, 00000, "event to stress test self tuning SGA feature by doing random memory broker resizes"
// *Document: NO
// *Cause:
// *Action:
00832, 00000, "no streams pool created and cannot automatically create one"
// *Cause: A database feature which needs STREAMS SGA was being used, however,
// the streams_pool_size parameter was not defined and the value of
// db_cache_size was too small to permit an automatic transfer of SGA
// to the streams pool from the buffer cache.
// *Action: Please set the parameter streams_pool_size or set SGA_TARGET.
00833, 00000, "event to test cancellation and cache protection by pinning buffers for deferred mode requests"
// *Document: NO
// *Cause:
// *Action:
00834, 00000, "Simulate 4031 during an immediate mode request in auto-sga"
// *Document: NO
// *Cause:
// *Action: Set _memory_management_tracing=23 to track this event.
00835, 00000, "Simulate memory broker disabling for code coverage"
// *Document: NO
// *Cause:
// *Action: It will be reenabled on next SGA_TARGET resize
00836, 00000, "Simulate memory transfer from system memory for startup request"
// *Document: NO
// *Cause: For code coverage.
// *Action: None.
00837, 00000, "Specified value of MEMORY_TARGET greater than MEMORY_MAX_TARGET"
// *Cause: The specified value of MEMORY_TARGET was greater than MEMORY_MAX_TARGET.
// *Action: Set MEMORY_TARGET less than or equal to MEMORY_MAX_TARGET.
00838, 00000, "Specified value of MEMORY_TARGET is too small, needs to be at least %sM"
// *Cause: The specified value of MEMORY_TARGET was less than the sum of the
// specified values for SGA_TARGET and PGA_AGGREGATE_TARGET.
// *Action: Set MEMORY_TARGET to at least the recommended value.
00839, 00000, "SGA_TARGET cannot be modified to the specified value"
// *Cause: The specified value of SGA_TARGET was not compatible with current settings of PGA_AGGREGATE_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET.
// *Action: Set SGA_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and PGA_AGGREGATE_TARGET. Also ensure that the current PGA memory used for non-auto workareas is low.
00840, 00000, "PGA_AGGREGATE_TARGET cannot be modified to the specified value"
// *Cause: The specified value of PGA_AGGREGATE_TARGET was not compatible with current settings of SGA_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET.
// *Action: Set PGA_AGGREGATE_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and SGA_TARGET.
00841, 00000, "MEMORY_TARGET not supported on this system"
// *Cause: MEMORY_TARGET parameter was not supported on this system as
// shmfs was disabled.
// *Action: Refer to documentation for a list of supported systems.
00842, 00000, "DB_BLOCK_BUFFERS cannot be set with SGA_TARGET or MEMORY_TARGET"
// *Cause: DB_BLOCK_BUFFERS was incompatible with SGA_TARGET and MEMORY_TARGET.
// *Action: Remove the incompatible parameter setting.
00843, 00000, "Parameter not taking MEMORY_MAX_TARGET into account"
// *Cause: The parameter was larger than MEMORY_MAX_TARGET.
// *Action: Check the other error messages for additional information about the parameter. Set the parameter to a lower value than MEMORY_MAX_TARGET.
00844, 00000, "Parameter not taking MEMORY_TARGET into account"
// *Cause: The parameter was larger than MEMORY_TARGET.
// *Action: Check the other error messages for additional information about the parameter. Set the parameter to a lower value than MEMORY_TARGET.
00845, 00000, "MEMORY_TARGET not supported on this system"
// *Cause: The MEMORY_TARGET parameter was not supported on this operating system or /dev/shm was not sized correctly on Linux.
// *Action: Refer to documentation for a list of supported operating systems. Or, size /dev/shm to be at least the SGA_MAX_SIZE on each Oracle instance running on the system.
00846, 00000, "could not shrink MEMORY_TARGET to specified value"
// *Cause: Attempted to shrink MEMORY_TARGET to the specified value but did not
// succeed because the PGA and SGA components could not be shrunk.
// *Action: Do not set MEMORY_TARGET to a value below the current value without
// first shrinking the individual memory components.
00847, 00000, "MEMORY_TARGET/MEMORY_MAX_TARGET and LOCK_SGA cannot be set together"
// *Cause: MEMORY_TARGET/MEMORY_MAX_TARGET was set to a non-zero value and LOCK_SGA was also set
// *Action:Do not set MEMORY_TARGET or MEMORY_MAX_TARGET if LOCK_SGA is set to TRUE.
00848, 00000, "STATISTICS_LEVEL cannot be set to BASIC with SGA_TARGET or MEMORY_TARGET"
// *Cause: STATISTICS_LEVEL of BASIC was incompatible with SGA_TARGET and MEMORY_TARGET.
// *Action: Fix the incompatible parameter setting. Set STATISTICS_LEVEL to TYPICAL or ALL to use SGA_TARGET or MEMORY_TARGET.
00849, 00000, "SGA_TARGET %s cannot be set to more than MEMORY_MAX_TARGET %s."
// *Cause: SGA_TARGET value was more than MEMORY_MAX_TARGET value.
// *Action: Set SGA_TARGET to be less than MEMORY_MAX_TARGET.
00850, 00000, "PGA_AGGREGATE_TARGET %s cannot be set to more than MEMORY_MAX_TARGET %s."
// *Cause: PGA_AGGREGATE_TARGET value was more than MEMORY_MAX_TARGET value.
// *Action: Set PGA_AGGREGATE_TARGET to be less than MEMORY_MAX_TARGET.
00851, 00000, "SGA_MAX_SIZE %s cannot be set to more than MEMORY_TARGET %s."
// *Cause: SGA_MAX_SIZE value was more than MEMORY_TARGET value.
// *Action: Set SGA_MAX_SIZE to be less than MEMORY_TARGET.
00852, 00000, "Rolling migration monitor process terminated."
// *Cause: The ASM rolling migration monitor process died.
// *Action: Warm start the instance.
00853, 00000, "SGA_MAX_SIZE %s cannot be set to more than MEMORY_MAX_TARGET %s."
// *Cause: SGA_MAX_SIZE value was more than MEMORY_MAX_TARGET value.
// *Action: Set SGA_MAX_SIZE to be less than MEMORY_MAX_TARGET.
00854, 00000, "ASM IOServer Instance Fence monitor process terminated."
// *Cause: The ASM IOServer Fence monitor process died.
// *Action: Warm start the instance.
00855, 00000, "PGA_AGGREGATE_TARGET cannot be set because of insufficient physical memory."
// *Cause: PGA_AGGREGATE_TARGET value was too high for the current system global area (SGA) size and amount of physical memory available.
// *Action: Reduce the SGA size or increase the physical memory size.
00856, 00000, "PGA_AGGREGATE_TARGET cannot be set higher 50 percent of PGA_AGGREGATE_LIMIT."
// *Cause: PGA_AGGREGATE_TARGET value was greater than 50 percent the current value of PGA_AGGREGATE_LIMIT.
// *Action: Increase PGA_AGGREGATE_LIMIT or use a lower PGA_AGGREGATE_TARGET.
/
/ event 865-874 reserved for cancel_sql and dequeue_parallel_statement errors
00865, 00000, "cannot perform the current operation on the same session"
// *Cause: The current operation could not be performed on the same session.
// *Action: None.
00866, 00000, "invalid or non-existent SQL ID"
// *Cause: The SQL ID specified was invalid or did not exist.
// *Action: Retry with a valid SQL ID.
00867, 00000, "invalid instance ID"
// *Cause: The instance ID specified was invalid.
// *Action: Retry with a valid instance ID.
/
/ Event Range 875 - 899 is reserved for connection broker
/
00875, 00000, "failed to %s the dedicated connection broker"
// *Cause: The dedicated connection broker could not be enabled or disabled.
// *Action: Check the process trace file for the reason for failure.
00876, 00000, "invalid CONNECTION_BROKERS specification #%s"
// *Cause: The syntax for the nth CONNECTION_BROKERS specification was invalid.
// *Action: See the additional errors that were reported. Refer to the Oracle
// Database Reference manual for the correct syntax.
00877, 00000, "TYPE=%s appears in multiple CONNECTION_BROKERS specifications"
// *Cause: Multiple CONNECTION_BROKER specifications contained the same TYPE.
// *Action: Specify only one specification for each TYPE.
/ MODIFIED
/ rankalik 04/10/17 - BUG25256476: Adding error message for XE
/ smangala 03/21/17 - bug 24926757: circular transaction queue
/ pkapil 10/13/15 - bug 21964339 : Correct ORA 00972 for password
/ identifier
/ mrajm 08/19/15 - bug 21298713 : ORA-1063
/ pkapil 04/15/14 - bug 20887157 : Correct error ORA 00972
/ ygu 10/02/14 - do not support redo compat lower than 10
/ vjanardh 08/01/14 - bug 17157952: remove reference to utl_file_dir
/ and modify the error for 01308
/ smangala 12/09/13 - bug 17889871: correct 1303 message format code
/ anidash 12/06/13 - new error for controlfile autoconvert check fail
/ jgalanes 07/22/13 - 16787540 ensure mining character set compatible with
/ source CS
/ vpantele 07/03/13 - fix typo in ORA-1176
/ yuli 05/13/13 - better error message for 1274
/ gkulkarn 08/23/12 - bug-13861626 : Add LogMiner public event #2
/ cchui 01/27/12 - update cause and action for error mesg 1031
/ msingams 04/19/11 - bug 9729398: INCORRECT ACTION SPECIFIED FOR ORA-1346
/ smangala 03/24/11 - bug11679567: correct 1280 action
/ akruglik 02/17/11 - DB Consolidation: alter message 1219 so it can be used
/ to inform a user that a pluggable database is not open
/ akruglik 02/07/11 - DB Consolidation: alter messages 1094 and 1089 so they
/ can be used to report state of a PDB as well as of a
/ DB
/ gshegalo 09/17/10 - Bug6834079: ORA-01161
/ avaliani 04/09/10 - reuse ORA-01088
/ sslim 02/16/10 - Add 1379 testing event
/ ineall 08/12/09 - Bug 8658899: Add ORA-1366: failed to find all redo
/ logs required for terminal apply
/ jjlee 03/03/09 - change 1110 and 1156
/ yohu 11/20/08 - update 1086
/ aamor 10/02/08 - bug 6793044: update 976 error
/ rlong 09/25/08 -
/ smangala 09/17/08 - bug7114186: fix PSBY terminal log handling
/ shsong 08/07/08 -
/ jgalanes 08/06/08 - Add 1362 and 1363 for invalid parameters to mine_value
/ & column_present
/ jjlee 07/15/08 - comment change
/ shsong 03/05/08 - Update 1188
/ jgalanes 01/11/07 - Add 1357 & 1358 for LogMiner logs version < dictionary
/ version
/ gviswana 10/13/06 - Update Cause, Action for 980
/ smangala 09/21/04 - update 1345 text and remove unused messages
/ jgalanes 09/14/06 - Add error # 1339 for LogMiner build error
/ abrown 05/10/06 - add KRVX_STATUS_UNSUPPORTED_DDL
/ abrown 06/08/05 - bug 3776830: unwind dictionary
/ mtao 03/25/05 - add 1375/1376, Reader detected redo log corruption
/ gmulagun 02/20/05 - bug 4140708 cannot audit SYS users
/ mjstewar 01/26/05 - Add 1148
/ psuvarna 09/28/04 - #3909055: rectify error message ORA-01438
/ jnesheiw 11/04/04 - Add global name mismatch error
/ abrown 08/04/04 - better error msg when supplemental logging off
/ jnesheiw 05/06/04 - revise 1341
/ smangala 04/16/04 - add 1346: LogMiner missed a branch
/ jnesheiw 03/01/04 - fix tense in 1329
/ lilin 01/21/04 - add 912 input too long
/ jwlee 11/16/03 - fix typo in ORA-1167
/ abrown 08/26/03 - fix logmnr 9i specific actions
/ banand 02/27/03 - bug 2707377
/ jkundu 12/06/02 - change log-based replication to Streams
/ sdizdar 10/28/02 -
/ molagapp 07/26/02 - recovery area project
/ rjanders 10/02/02 - Enhance 1154 cause/action
/ dvoss 10/07/02 - add 1355 and 1356
/ rjenkins 07/31/02 - reuse 911 for alternative quotes
/ ajadams 05/30/02 - purge unused LogMiner messages
/ rjanders 05/24/02 - Fix ORA-1126 message.
/ mtao 06/04/02 - logminer message 1301
/ ajadams 05/28/02 - LogMiner 10i status enhancements
/ mdilman 05/09/02 - DB begin/end backup: change 1140, 1232 and 1260
/ molagapp 04/23/02 - change 1264, 1269
/ bgarin 08/05/02 - Change text for logminer corrupt redo log
/ jkundu 01/23/02 - logminer error messages 1373, 1374
/ jkundu 11/20/01 - adding logminer error message
/ abrown 10/23/01 - dbms_logmnr_d.set_tablespace needs real error msgs
/ tcondie 11/07/01 - grabtrans 'ycao_ora904'
/ ycao 11/05/01 - change ora-904 message
/ aime 10/09/01 -
/ ajadams 10/08/01 - logminer messages
/ asundqui 10/04/01 - bug 2029014: added 1279
/ tcondie 10/18/01 - Modify ORA-932 to take 2 args.
/ mjstewar 08/28/01 - Add file name to ORA-1276
/ qiwang 08/08/01 - more logmnr error msg
/ bsinha 08/02/01 - extend 1010 for autonomous txn
/ smangala 07/02/01 - add 1344.
/ ygu 06/18/01 - add more err msg for logminer
/ qiwang 06/04/01 - more logmnr error msgs
/ eyho 07/26/01 - remove obsoleted messages
/ mdilman 07/02/01 - bug 1815522: added 1277, 1278
/ msusaira 06/14/01 - modify 1257 error mesg
/ mjstewar 04/04/01 - New OMF message.
/ jingliu 03/06/01 - fix error in message 1298, 1466
/ eyho 03/06/01 - RAC name changes
/ dgprice 01/11/01 - bug 1394096 define buffer size limits error
/ yuli 01/18/01 - 1539879: change Cause and Action part of 1114
/ amsrivas 12/12/00 - 1029386: modify 1153 - resetlogs/backup conflict.
/ mjstewar 12/13/00 - Automated standby file management
/ nlee 11/13/00 - Forward merge fix for bug 553250.
/ gkulkarn 10/30/00 - Add LogMiner Out-of-Memory Error
/ rpang 09/15/00 - Updated the cause of "unsupported character set" error
/ yuli 10/24/00 - Update message of 1092
/ gkulkarn 08/01/00 - Reserve more error numbers for LogMiner
/ ajadams 07/07/00 - logminer dictionary message
/ aime 06/29/00 - Fix compile error
/ mjstewar 06/13/00 - OMF errors
/ ajadams 06/26/00 - even more Logminer errors
/ ajadams 06/21/00 - more LogMiner messages
/ jkundu 06/09/00 - adding Logminer trace event
/ apareek 04/14/00 - change 1162 text
/ gkulkarn 05/14/00 - Update Error #01312
/ rjenkins 03/29/00 - change 1441
/ ajadams 03/31/00 - add error code 1315 for logmnr
/ robermar 04/18/00 - Inspection Comments
/ apadmana 01/19/00 - changed SNAPSHOT to MATERIALIZED VIEW
/ gkulkarn 02/01/00 - Add LogMiner sql function error messgaes
/ mjstewar 01/18/00 - Automatic removal of OS files.
/ robermar 01/27/00 - DB End Backout
/ msusaira 12/19/99 - add err 1257
/ vsrihari 07/14/99 - add file locks error message
/ jkundu 07/06/99 - adding more LogMiner messages
/ nireland 04/14/99 - Imporove action text for ORA-1220. #863107
/ swerthei 10/28/98 - noarchivelog -> NOARCHIVELOG in 1108
/ swerthei 10/20/98 - modify 1108 for bug 719176 - online/backup conflict
/ vsrihari 08/29/98 - modifying file identify error message
/ fsanchez 08/19/98 - fix_kcv_mig
/ mcusson 05/29/98 - adding error message for LogMiner
/ swerthei 04/21/98 - messages for Oracle-managed hot-backup mode
/
/ 900-999 parse errors -
/ carried over from V5 - desirable to add arguments wherever possible
/
00900, 00000, "invalid SQL statement"
// *Cause:
// *Action:
00901, 00000, "invalid CREATE command"
// *Cause:
// *Action:
00902, 00000, "invalid datatype"
// *Cause:
// *Action:
00903, 00000, "invalid table name"
// *Cause:
// *Action:
00904, 00000, "%s: invalid identifier"
// *Cause:
// *Action:
00905, 00000, "missing keyword"
// *Cause:
// *Action:
00906, 00000, "missing left parenthesis"
// *Cause:
// *Action:
00907, 00000, "missing right parenthesis"
// *Cause:
// *Action:
00908, 00000, "missing NULL keyword"
// *Cause:
// *Action:
00909, 00000, "invalid number of arguments"
// *Cause:
// *Action:
00910, 00000, "specified length too long for its datatype"
// *Cause: for datatypes CHAR and RAW, the length specified was > 2000;
// otherwise, the length specified was > 4000.
// *Action: use a shorter length or switch to a datatype permitting a
// longer length such as a VARCHAR2, LONG CHAR, or LONG RAW
00911, 00000, "invalid character"
// *Cause: The identifier name started with an ASCII character other than a
// letter or a number. After the first character of the identifier
// name, ASCII characters are allowed including "$", "#" and "_".
// Identifiers enclosed in double quotation marks may contain any
// character other than a double quotation. Alternate quotation
// marks (q'#...#') cannot use spaces, tabs, or carriage returns as
// delimiters. For all other contexts, consult the SQL Language
// Reference Manual.
// *Action: Check the Oracle identifier naming convention. If you are
// attempting to provide a password in the IDENTIFIED BY clause of
// a CREATE USER or ALTER USER statement, then it is recommended to
// always enclose the password in double quotation marks because
// characters other than the double quotation are then allowed.
00912, 00000, "input parameter too long"
// *Cause: one of your input strings was too long
// *Action:shorten the input parameter length
00913, 00000, "too many values"
// *Cause:
// *Action:
00914, 00000, "missing ADD keyword"
// *Cause:
// *Action:
00915, 00000, "network access of dictionary table not currently allowed"
// *Cause:
// *Action:
00917, 00000, "missing comma"
// *Cause:
// *Action:
00918, 00000, "column ambiguously defined"
// *Cause:
// *Action:
00919, 00000, "invalid function"
// *Cause:
// *Action:
00920, 00000, "invalid relational operator"
// *Cause:
// *Action:
00921, 00000, "unexpected end of SQL command"
// *Cause:
// *Action:
00922, 00000, "missing or invalid option"
// *Cause:
// *Action:
00923, 00000, "FROM keyword not found where expected"
// *Cause:
// *Action:
00924, 00000, "missing BY keyword"
// *Cause:
// *Action:
00925, 00000, "missing INTO keyword"
// *Cause:
// *Action:
00926, 00000, "missing VALUES keyword"
// *Cause:
// *Action:
00927, 00000, "missing equal sign"
// *Cause:
// *Action:
00928, 00000, "missing SELECT keyword"
// *Cause:
// *Action:
00929, 00000, "missing period"
// *Cause:
// *Action:
00930, 00000, "missing asterisk"
// *Cause:
// *Action:
00931, 00000, "missing identifier"
// *Cause:
// *Action:
00932, 00000, "inconsistent datatypes: expected %s got %s"
// *Cause:
// *Action:
00933, 00000, "SQL command not properly ended"
// *Cause:
// *Action:
00934, 00000, "group function is not allowed here"
// *Cause:
// *Action:
00935, 00000, "group function is nested too deeply"
// *Cause:
// *Action:
00936, 00000, "missing expression"
// *Cause:
// *Action:
00937, 00000, "not a single-group group function"
// *Cause:
// *Action:
00938, 00000, "not enough arguments for function"
// *Cause:
// *Action:
00939, 00000, "too many arguments for function"
// *Cause:
// *Action:
00940, 00000, "invalid ALTER command"
// *Cause:
// *Action:
00941, 00000, "missing cluster name"
// *Cause:
// *Action:
00942, 00000, "table or view does not exist"
// *Cause:
// *Action:
00943, 00000, "cluster does not exist"
// *Cause:
// *Action:
00944, 00000, "insufficient number of clustered columns"
// *Cause:
// *Action:
00945, 00000, "specified clustered column does not exist"
// *Cause:
// *Action:
00946, 00000, "missing TO keyword"
// *Cause:
// *Action:
00947, 00000, "not enough values"
// *Cause:
// *Action:
00948, 00000, "ALTER CLUSTER statement no longer supported"
// *Cause:
// *Action:
00949, 00000, "illegal reference to remote database"
// *Cause:
// *Action:
00950, 00000, "invalid DROP option"
// *Cause:
// *Action:
00951, 00000, "cluster not empty"
// *Cause:
// *Action:
00952, 00000, "missing GROUP keyword"
// *Cause:
// *Action:
00953, 00000, "missing or invalid index name"
// *Cause: An index name of the form [ <identifier> . ] <identifier> is
// expected but not present. If OIDINDEX clause, index name must be
// <identifier>
// *Action: Enter an appropriate index name.
00954, 00000, "missing IDENTIFIED keyword"
// *Cause:
// *Action:
00955, 00000, "name is already used by an existing object"
// *Cause:
// *Action:
00956, 00000, "missing or invalid auditing option"
// *Cause: AUDIT or NOAUDIT statement contains an invalid auditing option.
// *Action: Use a valid option.
00957, 00000, "duplicate column name"
// *Cause:
// *Action:
00958, 00000, "missing CHECK keyword"
// *Cause:
// *Action:
00959, 00000, "tablespace '%s' does not exist"
// *Cause:
// *Action:
00960, 00000, "ambiguous column naming in select list"
// *Cause: A column name in the order-by list matches more than one select
// list columns.
// *Action: Remove duplicate column naming in select list.
00961, 00000, "bad datetime/interval value"
// *Cause:
// *Action:
00962, 00000, "too many group-by / order-by expressions"
// *Cause: The group-by or order-by column list contain more than 1000
// expressions.
// *Action: Use 1000 or less expressions in the group-by or order-by list.
00963, 00000, "unsupported interval type"
// *Cause:
// *Action:
00964, 00000, "table name not in FROM list"
// *Cause: The table name referred in the select list is not specified in the
// from list.
// *Action: Make sure the name is correctly specified and matches one of the
// names in the from list.
00965, 00000, "column aliases not allowed for '*'"
// *Cause: The statement is trying to alias the * expression in the select
// list which is not legal.
// *Action: Remove the alias.
00966, 00000, "missing TABLE keyword"
// *Cause:
// *Action:
00967, 00000, "missing WHERE keyword"
// *Cause:
// *Action:
00968, 00000, "missing INDEX keyword"
// *Cause:
// *Action:
00969, 00000, "missing ON keyword"
// *Cause:
// *Action:
00970, 00000, "missing WITH keyword"
// *Cause:
// *Action:
00971, 00000, "missing SET keyword"
// *Cause:
// *Action:
00972, 00000, "identifier is too long"
// *Cause: An identifier with more than 128 bytes was specified,
// or a password identifier longer than 30 bytes was specified.
// *Action: Specify at most 128 bytes for identifiers,
// and at most 30 bytes for password identifiers.
00973, 00000, "invalid row count estimate"
// *Cause:
// *Action:
00974, 00000, "invalid PCTFREE value (percentage)"
// *Cause:
// *Action:
00975, 00000, "date + date not allowed"
// *Cause:
// *Action:
00976, 00000, "Specified pseudocolumn or operator not allowed here."
// *Cause: LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF or
// CONNECT_BY_ISCYCLE was specified at an illegal location.
// *Action: Remove LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF or
// CONNECT_BY_ISCYCLE.
00977, 00000, "duplicate auditing option"
// *Cause: AUDIT or NOAUDIT statement specifies an option more than once
// *Action: Either use ALL with no other auditing options or make sure
// no option is listed more than once.
00978, 00000, "nested group function without GROUP BY"
// *Cause:
// *Action:
00979, 00000, "not a GROUP BY expression"
// *Cause:
// *Action:
00980, 00000, "synonym translation is no longer valid"
// *Cause: A synonym did not translate to a legal target object. This
// could happen for one of the following reasons:
// 1. The target schema does not exist.
// 2. The target object does not exist.
// 3. The synonym specifies an incorrect database link.
// 4. The synonym is not versioned but specifies a versioned
// target object.
// *Action: Change the synonym definition so that the synonym points at
// a legal target object.
00981, 00000, "cannot mix table and system auditing options"
// *Cause: Table and system-wide auditing options were specified in the
// same AUDIT or NOAUDIT statement.
// *Action: You must issue table and system options in separate
// statements.
00982, 00000, "missing plus sign"
// *Cause:
// *Action:
00983, 00000, "cannot audit or noaudit SYS user actions"
// *Cause: An attempt was made to AUDIT or NOAUDIT SYS user actions.
// *Action: Execute the statement again with a valid user.
00984, 00000, "column not allowed here"
// *Cause:
// *Action:
00985, 00000, "invalid program name"
// *Cause:
// *Action:
00986, 00000, "missing or invalid group name(s)"
// *Cause:
// *Action:
00987, 00000, "missing or invalid username(s)"
// *Cause:
// *Action:
00988, 00000, "missing or invalid password(s)"
// *Cause:
// *Action:
00989, 00000, "too many passwords for usernames given"
// *Cause:
// *Action:
00990, 00000, "missing or invalid privilege"
// *Cause:
// *Action:
00991, 00000, "only MAC privileges may be granted to procedures"
// *Cause: Object privileges or non-MAC system privileges
// were granted to the procedure.
// *Action: Only grant MAC privileges using the PROCEDURE clause.
00992, 00000, "invalid format for REVOKE command"
// *Cause:
// *Action:
00993, 00000, "missing GRANT keyword"
// *Cause:
// *Action:
00994, 00000, "missing OPTION keyword"
// *Cause:
// *Action:
00995, 00000, "missing or invalid synonym identifier"
// *Cause:
// *Action:
00996, 00000, "the concatenate operator is ||, not |"
// *Cause:
// *Action:
00997, 00000, "illegal use of LONG datatype"
// *Cause:
// *Action:
00998, 00000, "must name this expression with a column alias"
// *Cause:
// *Action:
00999, 00000, "invalid view name"
// *Cause:
// *Action:
/
/ parse errors continue at 1700
/
/ 1000-1099 program interface errors
/
01000, 00000, "maximum open cursors exceeded"
// *Cause:
// *Action:
01001, 00000, "invalid cursor"
// *Cause:
// *Action:
01002, 00000, "fetch out of sequence"
// *Cause: This error means that a fetch has been attempted from a cursor
// which is no longer valid. Note that a PL/SQL cursor loop
// implicitly does fetches, and thus may also cause this error.
// There are a number of possible causes for this error, including:
// 1) Fetching from a cursor after the last row has been retrieved
// and the ORA-1403 error returned.
// 2) If the cursor has been opened with the FOR UPDATE clause,
// fetching after a COMMIT has been issued will return the error.
// 3) Rebinding any placeholders in the SQL statement, then issuing
// a fetch before reexecuting the statement.
// *Action: 1) Do not issue a fetch statement after the last row has been
// retrieved - there are no more rows to fetch.
// 2) Do not issue a COMMIT inside a fetch loop for a cursor
// that has been opened FOR UPDATE.
// 3) Reexecute the statement after rebinding, then attempt to
// fetch again.
01003, 00000, "no statement parsed"
// *Cause:
// *Action:
01004, 00000, "default username feature not supported; logon denied"
// *Cause:
// *Action:
01005, 00000, "null password given; logon denied"
// *Cause:
// *Action:
01006, 00000, "bind variable does not exist"
// *Cause:
// *Action:
01007, 00000, "variable not in select list"
// *Cause:
// *Action:
01008, 00000, "not all variables bound"
// *Cause:
// *Action:
01009, 00000, "missing mandatory parameter"
// *Cause:
// *Action:
01010, 00000, "invalid OCI operation"
// *Cause: One of the following:
// 1) You attempted an invalid OCI operation.
// 2) You are using an Oracle client application linked with
// version 7.1 (or higher) libraries, the environment variable
// ORA_ENCRYPT_LOGIN is set to TRUE, and you attempted to
// connect to a version 7.0 (or lower) Oracle Server.
// 3) You are connected to a version 7.1 (or higher) Oracle Server,
// the initialization parameter DBLINK_ENCRYPT_LOGIN is set to
// TRUE, and you attempted to use a database link pointing to a
// version 7.0 (or lower) Oracle Server.
// 4) You are connected to a version 9.0.2(or higher) Oracle Server
// and you attempted to use a database link pointing to a version
// 9.0.1(or lower) Oracle Server for distributed autonomous
// transaction.
// *Action: For the above causes:
// 1) Do not use the invalid OCI operation.
// 2) If you do not wish to use encrypted connect passwords in your
// distributed database, set ORA_ENCRYPT_LOGIN to FALSE.
// If you wish to use encrypted connect passwords, you must upgrade
// all Oracle Servers to version 7.1 (or higher).
// 3) If you do not wish to use encrypted database links in your
// distributed database, set DBLINK_ENCRYPT_LOGIN to FALSE.
// If you wish to use encrypted database links, you must upgrade
// all Oracle Servers to version 7.1 (or higher).
// 4) Do not attempt distributed autonomous transaction on version
// 9.0.1(or lower) Oracle Server.
01011, 00000, "Cannot use v7 compatibility mode when talking to v6 server"
// *Cause:
// *Action: Use v6 sql language type. You may need to use the
// 'SET COMPATIBILITY V6' command
01012, 00000, "not logged on"
// *Cause:
// *Action:
01013, 00000, "user requested cancel of current operation"
// *Cause:
// *Action:
01014, 00000, "ORACLE shutdown in progress"
// *Cause:
// *Action:
01015, 00000, "logon called recursively"
// *Cause:
// *Action:
01016, 00000, "This function can be called only after a fetch"
// *Cause: Cursor in an invalid state.
// *Action: Make sure that the oci/upi function is called after fetch.
01017, 00000, "invalid username/password; logon denied"
// *Cause:
// *Action:
01018, 00000, "column does not have a LONG datatype"
// *Cause:
// *Action:
01019, 00000, "unable to allocate memory in the user side"
// *Cause: The user side memory allocator returned error.
// *Action: Increase the processes heap size or switch to the old set of calls.
01020, 00000, "unknown context state"
// *Cause:
// *Action:
01021, 00000, "invalid context size specified"
// *Cause:
// *Action:
01022, 00000, "database operation not supported in this configuration"
// *Cause: The attempted database operation does not conform to the user
// programming interface (UPI) for the two communicating
// ORACLE servers.
// *Action: You may need to upgrade one or more of your ORACLE servers or
// re-link your user side application with new libraries. Report
// the problem to Worldwide Customer Support.
01023, 00000, "Cursor context not found (Invalid cursor number)"
// *Cause: The cursor number is not a valid open cursor.
// *Action: Make sure that the cursor is open.
01024, 00000, "invalid datatype in OCI call"
// *Cause:
// *Action:
01025, 00000, "UPI parameter out of range"
// *Cause: An integer parameter to a upi function is out of range.
// *Action: This usually indicates an error in a tool built on top
// of the oracle dbms. Report the error to your customer
// support representative.
01026, 00000, "multiple buffers of size > 4000 in the bind list"
// *Cause: More than one long buffer in the bind list.
// *Action: Change the buffer size to be less than 4000 for the bind variable
// bound to a normal column.
01027, 00000, "bind variables not allowed for data definition operations"
// *Cause: An attempt was made to use a bind variable in a SQL data definition
// operation.
// *Action: Such bind variables are not allowed.
01028, 00000, "internal two task error"
// *Cause: Received send long message but don't have the cursor context.
// *Action: Report as a bug.
01029, 00000, "internal two task error"
// *Cause: Received a request to send the long again when there is no long
// *Action: Report as a bug
01030, 00000, "SELECT ... INTO variable does not exist"
// *Cause: The SELECT... INTO specified in the bind call does not
// correspond to a variable in the SQL statement.
// *Action: If it is not possible to correct the statement, call customer
// support.
01031, 00000, "insufficient privileges"
// *Cause: An attempt was made to perform a database operation without
// the necessary privileges.
// *Action: Ask your database administrator or designated security
// administrator to grant you the necessary privileges
01032, 00000, "no such userid"
// *Cause: This is an internal error message related to Export/Import.
// *Action: Contact customer support.
01033, 00000, "ORACLE initialization or shutdown in progress"
// *Cause: An attempt was made to log on while Oracle is being started up
// or shutdown.
// *Action: Wait a few minutes. Then retry the operation.
01034, 00000, "ORACLE not available"
// *Cause: Oracle was not started up. Possible causes include the following:
// - The SGA requires more space than was allocated for it.
// - The operating-system variable pointing to the instance is
// improperly defined.
// *Action: Refer to accompanying messages for possible causes and correct
// the problem mentioned in the other messages.
// If Oracle has been initialized, then on some operating systems,
// verify that Oracle was linked correctly. See the platform
// specific Oracle documentation.
01035, 00000, "ORACLE only available to users with RESTRICTED SESSION privilege"
// *Cause: Logins are disallowed because an instance started in restricted
// mode. Only users with RESTRICTED SESSION system privilege can
// log on.
// *Action: Request that Oracle be restarted without the restricted option or
// obtain the RESTRICTED SESSION system privilege.
01036, 00000, "illegal variable name/number"
// *Cause: Unable to find bind context on user side
// *Action: Make sure that the variable being bound is in the sql statement.
01037, 00000, "maximum cursor memory exceeded"
// *Cause: Attempting to process a complex sql statement which consumed all
// available memory of the cursor.
// *Action: Simplify the complex sql statement.
01038, 00000, "cannot write database file version %s with ORACLE version %s"
// *Cause: Attempting to write datafile headers in an old format. The new
// format can not be used until after the database has been verified
// as being compatible with this software version.
// *Action: Open the database to advance to the new file formats, then repeat
// the operation. If the operation is required before the database
// can be opened, then use the previous software release to do the
// operation.
01039, 00000, "insufficient privileges on underlying objects of the view"
// *Cause: Attempting to explain plan on other people's view without
// the necessary privileges on the underlying objects of the view.
// *Action: Get necessary privileges or do not perform the offending operation.
01040, 00000, "invalid character in password; logon denied"
// *Cause: There are multibyte characters in the password or some characters
// in the password are not in US7ASCII range.
// *Action: Resubmit password with valid characters.
01041, 00000, "internal error. hostdef extension doesn't exist"
// *Cause: Pointer to hstdef extension in hstdef is null.
// *Action: Report as a bug
01042, 00000, "detaching a session with open cursors not allowed"
// *Cause: An attempt was made to detach a seesio n which had open cursors.
// *Action: Close all the cursors before detaching the session.
01043, 00000, "user side memory corruption [%s], [%s], [%s], [%s]"
// *Cause: The application code corrupted some of the usr memory used by oracle
// *Action: Make sure that the application code is not overwriting memory.
01044, 00000, "size %s of buffer bound to variable exceeds maximum %s"
// *Cause: An attempt was made to bind a buffer whose total size would exceed
// the maximum size allowed. Total array size for arrays is
// calculated as: (element_size)*(number of elements)
// *Action: Reduce buffer size.
01045, 00000, "user %s lacks CREATE SESSION privilege; logon denied"
// *Cause: A connect was attempted to a userid which does not have
// create session privilege.
// *Action: Grant the user CREATE SESSION privilege.
01046, 00000, "cannot acquire space to extend context area"
// *Cause:
// *Action:
01047, 00000, "The above error occurred in schema=%s, package=%s, procedure=%s"
// *Cause:
// *Action: Informational message
01048, 0000, "Couldn't find the specified procedure in the given context"
// *Cause: The procedure user specified in deferred RPC doesn't exist.
// *Action: Check to make sure that the procedure exists and is visible to the
// replication process.
01049, 00000, "Bind by name is not spupportted in streamed RPC"
// *Cause: A newer version of server is talking with this version requesting an
// operation not supported in this version.
// *Action:
01050, 00000, "cannot acquire space to open context area"
// *Cause:
// *Action:
01051, 00000, "deferred rpc buffer format invalid"
// *Cause: The deferred rpc data in sys.def$_call is corrupted.
// *Action: Contact your customer support representive.
01052, 00000, "required destination LOG_ARCHIVE_DUPLEX_DEST is not specified"
// *Cause: A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not
// specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to
// two.
// *Action: Either specify a value for parameter LOG_ARCHIVE_DUPLEX_DEST, or
// reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to one.
01053, 00000, "user storage address cannot be read"
// *Cause:
// *Action:
01054, 00000, "user storage address cannot be written"
// *Cause:
// *Action:
01055, 00000, "Object datatypes not supported for bind or define in this mode"
// *Cause: Bind or Define used for objects with an invalid mode
// *Action: Change the mode.
01057, 00000, "invalid or ambiguous block.field reference in user exit"
// *Cause:
// *Action:
01058, 00000, "internal New Upi interface error"
// *Cause: Attempt to delete non existant hstdef extension.
// *Action: Report as a bug.
01059, 00000, "parse expected before a bind or execute"
// *Cause: The client application attempted to bind a variable or execute
// a cursor opened in a PL/SQL block before the statement was parsed.
// *Action: Ensure the statement is parsed before a bind or execute.
01060, 00000, "array binds or executes not allowed"
// *Cause: The client application attempted to bind an array of cursors or
// attempted to repeatedly execute against a PL/SQL block with a bind
// variable of type cursor.
// *Action: Bind a single cursor or execute the PL/SQL block once.
01061, 00000, "cannot start up a V8 server using a V7 client application"
// *Cause: You are using an Oracle client application linked with version 7
// (or lower) libraries and you attempted to start up a V8 (or
// higher) server.
// *Action: Use a client application linked with V8 (or higher) libraries.60
01062, 00000, "unable to allocate memory for define buffer"
// *Cause: Exceeded the maximum buffer size for current plaform
// *Action: Use piecewise fetch with a smaller buffer size
01063, 00000, "fetch row count exceeds MINSWORDMAXVAL"
// *Cause: The total number of rows requested from the server exceeded the
// maximum specified in MINSWORDMAXVAL.
// *Action: Fix the number of rows to fetch or prefetch for the fetch
// interface call.
01064, 0000, "invalid value '%s' for parameter INSTANCE_TYPE in XE Edition"
// *Cause : A value other than RDBMS was specified for the INSTANCE_TYPE
// parameter in Oracle Database Express Edition (XE).
// *Action : Upgrade to Oracle Database Standard Edition (SE) or Oracle
// Database Enterprise Edition (EE) to bring up any other
// instance type.
/ 1070 - 1099: V6 program interface errors
01070, 00000, "Using an old version of Oracle for the server"
// *Cause: Using pre 7.0.10.1 version of oracle for server
// *Action: Upgrade server to post 7.0.10.1 version
01071, 00000, "cannot perform operation without starting up ORACLE"
// *Cause: Obvious
// *Action:
01072, 00000, "cannot stop ORACLE; ORACLE not running"
// *Cause: Obvious
// *Action:
01073, 00000, "fatal connection error: unrecognized call type"
// *Cause: An illegal internal operation was attempted.
// *Action: Contact your customer support representative.
01074, 00000, "cannot shut down ORACLE; inside a login session - log off first"
// *Cause: Obvious
// *Action:
01075, 00000, "you are currently logged on"
// *Cause: Attempt to login while logged in.
// *Action:
01076, 00000, "multiple logons per process not yet supported"
// *Cause: Obvious
// *Action:
01077, 00000, "background process initialization failure"
// *Cause: Failure during initialization of ORACLE background processes.
// *Action: Further diagnostic information should be in the error stack
// or in the trace file.
01078, 00000, "failure in processing system parameters"
// *Cause: Failure during processing of INIT.ORA parameters during
// system startup.
// *Action: Further diagnostic information should be in the error stack.
01079, 00000, "ORACLE database was not properly created, operation aborted"
// *Cause: There was an error when the database or control file was created.
// *Action: Check what error was signaled when the database was first
// created or when the control file was recreated. Take appropriate
// actions to recreate the database or a new control file.
01080, 00000, "error in shutting down ORACLE"
// *Cause: Failure during system shutdown.
// *Action: Further diagnostic information should be in the error stack.
01081, 00000, "cannot start already-running ORACLE - shut it down first"
// *Cause: Obvious
// *Action:
01082, 00000, "'row_locking = always' requires the transaction processing option"
// *Cause: "row_locking = always" is specified in INIT.ORA file.
// This feature is not supported by ORACLE without the
// transaction processing option.
// *Action: Remove it from INIT.ORA file or set it to "default" or "intent".
01083, 00000, "value of parameter \"%s\" is inconsistent with that of other instances"
// *Cause: The value of the given parameter is required to be the same for all
// instances in the cluster database configuration. ROW_LOCKING and
// SERIALIZABLE are 2 examples.
// *Action: Change the value of the parameter in INIT.ORA file to match
// that of other cluster database instances.
01084, 00000, "invalid argument in OCI call"
// *Cause: The failing OCI call contains an argument with an invalid value.
// *Action: Use valid argument values. For more information, see the
// Programmer's Guide to the Oracle Call Interfaces and the
// appropriate programming language supplement.
01085, 00000, "preceding errors in deferred rpc to \"%s.%s.%s\""
// *Cause: Errors were encountered when the named procedure was executed
// as a deferred remoted procedure call.
// *Action: Correct the cause of the preceding errors.
01086, 00000, "savepoint '%s' never established in this session or is invalid"
// *Cause: An attempt was made to roll back to a savepoint that was never
// established in this session, or was invalid.
// *Action: Try rolling back to the savepoint from the session where it is established.
01087, 00000, "cannot start up ORACLE - currently logged on"
// *Cause:
// *Action: Logoff and then issue the STARTUP command.
01088, 00000, "shutdown in progress - operation not permitted until restart"
// *Cause: The SHUTDOWN command was used to shut down a running Oracle
// instance but the shutdown operation was not complete.
// *Action: Wait for the instance to be restarted or contact your
// database administrator.
01089, 00000, "immediate shutdown or close in progress - no operations are permitted"
// *Cause: The SHUTDOWN IMMEDIATE command was used to shut down
// a running Oracle instance, or CLOSE IMMEDIATE was used to shut down
// a pluggable database, so your operations have been
// terminated.
// *Action: Wait for the instance to be restarted, or contact your DBA.
01090, 00000, "shutdown in progress - connection is not permitted"
// *Cause: The SHUTDOWN command was used to shut down a running
// ORACLE instance, so you cannot connect to ORACLE.
// *Action: Wait for the instance to be restarted, or contact your DBA.
01091, 00000, "failure during startup force"
// *Cause: Unable to destroy the old SGA.
// *Action: Manually remove the old SGA and reissue the STARTUP command
01092, 00000, "ORACLE instance terminated. Disconnection forced"
// *Cause: The instance this process was connected to was terminated
// abnormally, probably via a shutdown abort. This process
// was forced to disconnect from the instance.
// *Action: Examine the alert log for more details. When the instance has been
// restarted, retry action.
01093, 00000, "ALTER DATABASE CLOSE only permitted with no sessions connected"
// *Cause: There is at least one more session other than the current one
// logged into the instance. ALTER DATABASE CLOSE is not permitted.
// *Action: Find the other sessions and log them out and resubmit the command
01094, 00000, "ALTER DATABASE or ALTER PLUGGABLE DATABASE CLOSE in progress. Connections not permitted"
// *Cause:
// *Action:
01095, 00000, "DML statement processed zero rows"
// *Cause: During a call to OTEX, an update, delete, or insert statement
// being executed processed zero rows. The execution
// of statements by OTEX was halted at this point.
// *Action:
01096, 00000, "program version (%s) incompatible with instance (%s)"
// MERGE: 1095 RENUMBERED TO 1096
// *Cause: A program is trying to connect to an instance using a different
// version of code than the database was started with. This is
// not allowed.
// *Action: Either relink the program with the same version as the database or
// restart the database using the old version of code.
01097, 00000, "cannot shutdown while in a transaction - commit or rollback first"
// *Cause: Obvious
// *Action:
01098, 00000, "program Interface error during Long Insert"
// *Cause:
// *Action:
01099, 00000, "cannot mount database in SHARED mode if started in single process mode"
// *Cause: Obvious
// *Action:
/
/ 1100 to 1279: db file errors (continue at 63000)
/
01100, 00000, "database already mounted"
// *Cause: A database is already mounted in this instance.
// *Action:
01101, 00000, "database being created currently mounted by some other instance"
// *Cause: Some other instance has the database of same name currently mounted
// and you are trying to create it.
// *Action: Either change the database name or shutdown the other instance.
01102, 00000, "cannot mount database in EXCLUSIVE mode"
// *Cause: Some other instance has the database mounted exclusive or shared.
// *Action: Shutdown other instance or mount in a compatible mode.
01103, 00000, "database name '%s' in control file is not '%s'"
// *Cause: The database name in the control file does not match your
// database name.
// *Action: Either find the correct control file or change your database name.
01104, 00000, "number of control files (%s) does not equal %s"
// *Cause: The number of control files used by this instance disagrees with
// the number of control files in an existing instance.
// *Action: Check to make sure that all control files are listed.
01105, 00000, "mount is incompatible with mounts by other instances"
// *Cause: An attempt to mount the database discovered that another instance
// mounted a database by the same name, but the mount is not
// compatible. Additional errors are reported explaining why.
// *Action: See accompanying errors.
01106, 00000, "database must be closed before dismounting"
// *Cause: Obvious
// *Action:
01107, 00000, "database must be mounted for media recovery"
// *Cause: An attempt to perform media recovery was made but the database is
// not mounted.
// *Action: Mount the database.
01108, 00000, "file %s is in backup or media recovery"
// *Cause: Either media recovery is actively being applied to the file, or
// it is being backed up while the database is in NOARCHIVELOG mode.
// It cannot be used for normal database access or crash recovery.
// *Action: Complete or cancel the media recovery session or backup.
01109, 00000, "database not open"
// *Cause: A command was attempted that requires the database to be open.
// *Action: Open the database and try the command again
01110, 00000, "data file %s: '%s'"
// *Cause: Reporting file name for details of another error. The reported
// name can be of the old file if a data file move operation is
// in progress.
// *Action: See associated error message.
01111, 00000, "name for data file %s is unknown - rename to correct file"
// *Cause: The data file was missing from a CREATE CONTROLFILE command or
// backup control file recovery was done with a control file that
// was saved before the file was created.
// *Action: Rename the MISSING file to the name of the real file.
01112, 00000, "media recovery not started"
// *Cause: An attempt to continue media recovery is being made but media
// recovery was not started.
// *Action: None.
01113, 00000, "file %s needs media recovery"
// *Cause: An attempt was made to online or open a database with a file that
// is in need of media recovery.
// *Action: First apply media recovery to the file.
01114, 00000, "IO error writing block to file %s (block # %s)"
// *Cause: The device on which the file resides is probably offline. If the
// file is a temporary file, then it is also possible that the device
// has run out of space. This could happen because disk space of
// temporary files is not necessarily allocated at file creation time.
// *Action: Restore access to the device or remove unnecessary files to free
// up space.
01115, 00000, "IO error reading block from file %s (block # %s)"
// *Cause: Device on which the file resides is probably offline
// *Action: Restore access to the device
01116, 00000, "error in opening database file %s"
// *Cause: Usually the file is not accessible.
// *Action: Restore the database file.
01117, 00000, "adding file '%s' with illegal block size: %s; limit is %s"
// *Cause: An attempt was made to add a database file with a block size
// that is greater than the maximum block size allowed.
// *Action: Retry the DDL command with a smaller block size.
01118, 00000, "cannot add any more database files: limit of %s exceeded"
// *Cause: There is no more room in the control file for adding database
// files.
// *Action: Resize the control file or drop other tablespaces.
01119, 00000, "error in creating database file '%s'"
// *Cause: Usually due to not having enough space on the device.
// *Action:
01120, 00000, "cannot remove online database file %s"
// *Cause: Attempting to drop a datafile when it is online
// *Action: Take file offline before dropping.
01121, 00000, "cannot rename database file %s - file is in use or recovery"
// *Cause: Attempted to use ALTER DATABASE RENAME to rename a
// datafile that is online in an open instance or is being recovered.
// *Action: Close database in all instances and end all recovery sessions.
01122, 00000, "database file %s failed verification check"
// *Cause: The information in this file is inconsistent with information
// from the control file. See accompanying message for reason.
// *Action: Make certain that the db files and control files are the correct
// files for this database.
01123, 00000, "cannot start online backup; media recovery not enabled"
// *Cause: An attempt to start backup of an on-line tablespace failed because
// media recovery is not enabled.
// *Action: Enable media recovery and retry this operation.
01124, 00000, "cannot recover data file %s - file is in use or recovery"
// *Cause: An attempt to do media recovery found that the file was not
// available for recovery. Either it is online and the database is
// open in some instance, or another process is curently doing
// media recovery on the file.
// *Action: Do not do media recovery.
01125, 00000, "cannot disable media recovery - file %s has online backup set"
// *Cause: An attempt to disable media recovery found that an online backup is
// still in progress.
// *Action: End the backup of the offending tablespace and retry this command.
01126, 00000, "database must be mounted in this instance and not open in any instance"
// *Cause: Obvious
// *Action:
01127, 00000, "database name '%s' exceeds size limit of %s characters"
// *Cause: Obvious
// *Action:
01128, 00000, "cannot start online backup - file %s is offline"
// *Cause: An attempt to start an online backup found that one of the files is
// offline.
// *Action: Bring the offending files online and retry this command or do a
// cold backup.
01129, 00000, "user's default or temporary tablespace does not exist"
// *Cause: The user's default or temporary tablespace was dropped.
// *Action: Reassign the default or temporary tablespace.
01130, 00000, "database file version %s incompatible with ORACLE version %s"
// *Cause:
// *Action:
01131, 00000, "DB_FILES system parameter value %s exceeds limit of %s"
// *Cause:
// *Action:
01132, 00000, "length of database file name '%s' exceeds limit of %s characters"
// *Cause:
// *Action:
01133, 00000, "length of log file name '%s' exceeds limit of %s characters"
// *Cause:
// *Action:
01134, 00000, "database mounted exclusive by another instance"
// *Cause:
// *Action:
01135, 00000, "file %s accessed for DML/query is offline"
// *Cause: Attempted to access a data file that is offline
// *Action: Bring the data file back online
01136, 00000, "specified size of file %s (%s blocks) is less than original size of %s blocks"
// *Cause: A file size was specified in the AS clause of ALTER DATABASE
// CREATE DATAFILE, and the size was smaller the the size needed
// *Action: Create the file with a larger size.
01137, 00000, "data file %s is still in the middle of going offline"
// *Cause: It was not possible to get the lock for a file that is offline when
// attempting to bring it online. The most likely cause is that the
// lock is still held by the instance that is took it offline.
// *Action: Wait a bit and try to online the file again.
01138, 00000, "database must either be open in this instance or not at all"
// *Cause: The requested operation can not be done when the database is
// mounted but not open in this instance, and another instance has
// the database open.
// *Action: Execute the operation in an open instance, open the datbase in
// this instance, or close the database in the other instances.
01139, 00000, "RESETLOGS option only valid after an incomplete database recovery"
// *Cause: The RESETLOGS option was given in ALTER DATABASE OPEN, but there
// has been no incomplete recovery session.
// *Action: Retry the ALTER DATABASE OPEN without specifying RESETLOGS
01140, 00000, "cannot end online backup - all files are offline or readonly"
// *Cause: All the files were found to be offline or readonly when attempting
// to end an online backup.
// *Action: None. Online backup does not need to be ended for this tablespace.
01141, 00000, "error renaming data file %s - new file '%s' not found"
// *Cause: An attempt to change a data file's name in the control file
// failed because no file was found with the new name.
// *Action: Make sure that the data file has been properly renamed by the
// operating system and retry.
01142, 00000, "cannot end online backup - none of the files are in backup"
// *Cause: None of the files were found to be in online backup when attempting
// to end an online backup.
// *Action: None. Online backup does not need to be ended for this tablespace.
01143, 00000, "cannot disable media recovery - file %s needs media recovery"
// *Cause: An attempt to disable media recovery found a file that needs media
// recovery, thus media recovery cannot be disabled.
// *Action: Recover the offending file or drop the tablespace it belongs to
// and retry this command.
01144, 00000, "File size (%s blocks) exceeds maximum of %s blocks"
// *Cause: Specified file size is larger than maximum allowable size value.
// *Action: Specify a smaller size.
01145, 00000, "offline immediate disallowed unless media recovery enabled"
// *Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE
// ... OFFLINE is only allowed if database is in ARCHIVELOG mode.
// *Action:Take tablespace offline normally or shutdown abort. Reconsider your
// backup strategy. You could do this if you were archiving your logs.
01146, 00000, "cannot start online backup - file %s is already in backup"
// *Cause: When starting an online backup it was noticed that an online backup
// was already started for one of the data files.
// *Action:End the first backup before beginning another.
01147, 00000, "SYSTEM tablespace file %s is offline"
// *Cause: A file belonging to the SYSTEM tablespace has been marked offline
// by the DBA. The database cannot be started until all SYSTEM
// tablespace files are online and openable.
// *Action: Bring the file online.
01148, 00000, "cannot refresh file size for datafile %s"
// *Cause: An operating system or device error occurred when retrieving the
// file's size. The device on which the file resides may have been
// offline.
// *Action: Restore access to the device.
01149, 00000, "cannot shutdown - file %s has online backup set"
// *Cause: An attempt to shutdown normally found that an online backup is
// still in progress.
// *Action: End the backup of the offending tablespace and retry this command.
01150, 00000, "cannot prevent writes - file %s has online backup set"
// *Cause: An attempt to make a tablespace read only or offline normal found
// that an online backup is still in progress. It will be necessary
// to write the file header to end the backup, but that would not
// be allowed if this command succeeded.
// *Action: End the backup of the offending tablespace and retry this command.
01151, 00000, "use media recovery to recover block, restore backup if needed"
// *Cause: Error 1172 occurred.
// *Action: This is additional information for error 1172.
01152, 00000, "file %s was not restored from a sufficiently old backup "
// *Cause: An incomplete recovery session was started, but an insufficient
// number of logs were applied to make the database consistent. This
// file is still in the future of the last log applied. The most
// likely cause of this error is forgetting to restore the file
// from a backup before doing incomplete recovery.
// *Action: Either apply more logs until the database is consistent or
// restore the database file from an older backup and repeat recovery.
01153, 00000, "an incompatible media recovery is active"
// *Cause: Attempted to start an incompatible media recovery or open resetlogs
// during media recovery or RMAN backup . Media recovery sessions
// are incompatible if they attempt to recover the same data file.
// Incomplete media recovery or open resetlogs is incompatible with
// any media recovery. Backup or restore by RMAN is incompatible
// with open resetlogs
// *Action: Complete or cancel the other media recovery session or RMAN backup
01154, 00000, "database busy. Open, close, mount, and dismount not allowed now"
// *Cause: Some operation is in progress that expects the opened/mounted state
// of this instance to remain the same.
// *Action: Wait for the operation to complete then retry. If attempting to
// do a shutdown, SHUTDOWN ABORT will work. If this is a shutdown
// of a standby database that is operating in NO DATA LOSS mode, you
// must shutdown the primary database first.
01155, 00000, "the database is being opened, closed, mounted or dismounted"
// *Cause: The requested operation needs the instance to be in a particular
// state but the state is being changed.
// *Action: Wait for the open, close, mount, or dismount to complete then
// retry the operation. If necessary, a SHUTDOWN ABORT will always
// work.
01156, 00000, "recovery or flashback in progress may need access to files"
// *Cause: Either media recovery, instance recovery, or flashback was
// in progress. The recovery or flashback in progress may need
// the files to which this operation is being applied.
// *Action: Wait for recovery or flashback to complete.
01157, 00000, "cannot identify/lock data file %s - see DBWR trace file"
// *Cause: The background process was either unable to find one of the data
// files or failed to lock it because the file was already in use.
// The database will prohibit access to this file but other files will
// be unaffected. However the first instance to open the database will
// need to access all online data files. Accompanying error from the
// operating system describes why the file could not be identified.
// *Action: Have operating system make file available to database. Then either
// open the database or do ALTER SYSTEM CHECK DATAFILES.
01158, 00000, "database %s already mounted"
// *Cause: Another instance has a database by this name mounted.
// *Action: Find which instance is still running. Perhaps you have not lost
// the control files after all.
01159, 00000, "file is not from same database as previous files - wrong database id"
// *Cause: Not all of the files specified in CREATE CONTROLFILE are from the
// same database. The database ID of this file does not match that
// from the first file specified.
// *Action: Please double check the list of files provided to the CREATE
01160, 00000, "file is not a %s"
// *Cause: The named file in the DATAFILE or LOGFILE section of the CREATE
// CONTROLFILE command does not appear to be as stated.
// *Action: Please double check the mentioned file.
01161, 00000, "Database name %s in the file header does not match %s in the DATABASE clause."
// *Cause: The database name provided in the DATABASE clause
// did not match the database name found in the file header.
// *Action: Ensure consistency of database names. Use the SET DATABASE clause if
// you are renaming the database.
01162, 00000, "block size %s in file header does not match configured block sizes"
// *Cause: CREATE CONTROLFILE discovered that the block size for this file
// is incompatible with any of the configured cache blocksizes in
// the INIT.ORA file.
// *Action:Configure the appropriate cache for this block size using one of the
// various (db_2k_cache_size, db_4k_cache_size, db_8k_cache_size,
// db_16k_cache_size, db_32K_cache_size) parameters.
01163, 00000, "SIZE clause indicates %s (blocks), but should match header %s"
// *Cause: The size specified in bytes in the SIZE clause of the CREATE
// CONTROLFILE statement does not equate to the number of blocks
// recorded in the header.
// *Action: Specify the correct filename and size ( in bytes ).
01164, 00000, "MAXLOGFILES may not exceed %s"
// *Cause: MAXLOGFILES specified on the command line too large.
// *Action: Resubmit the command with a smaller MAXLOGFILES
01165, 00000, "MAXDATAFILES may not exceed %s"
// *Cause: MAXDATAFILES specified on the command line too large.
// *Action: Resubmit the command with a smaller MAXDATAFILES
01166, 00000, "file number %s is larger than %s (%s)"
// *Cause: File mentioned in CREATE CONTROLFILE has a file number which is
// larger than that specified for MAXDATAFILES or MAXLOGFILES.
// *Action: Increase the maximum specified on the command line.
01167, 00000, "two files are the same file/group number or the same file"
// *Cause: There is an overlap of file numbers in the files specified on
// the command line or the same file is specified twice. If they are
// not the exact same file then one is likely to be a backup of the
// other. If they are two members of the same log they must be specified
// together in a group file spec. This message will also appear if
// the same control file appears more than once in the control_files
// parameter in the init.ora file. If this happens, check for
// additional error messages.
// *Action: Confirm that the file mentioned is not a repeat of a file already
// mentioned in the command. If they are different files then omit the
// earlier backup. If they are members of the same log, insure they are
// in the same group file specification. If this message appears because
// of a duplicate control file, check the control_files parameter in the
// init.ora file and see if a file is specified more than once.
// If all files names appear to be unique, check to make sure that the
// actual control files themselves are unique. For example, in UNIX
// check for a symbolic or a hard link to another control file in the list.
01168, 00000, "physical block size %s does not match size %s of other members"
// *Cause: The file is located on a device with a different physical block
// size than the other members in the group
// *Action: Use a physical device with matching block size.
01169, 00000, "DATAFILE number 1 not found. Must be present"
// *Cause: Datafile number 1 was not specified in a CREATE CONTROLFILE command.
// *Action: Locate datafile number 1 and resubmit the CREATE CONTROLFILE
// command.
01170, 00000, "file not found '%s'"
// *Cause: ALL datafiles and, if NORESETLOGS, ALL logfiles MUST be
// accessible by the process for CREATE CONTROLFILE.
// *Action: The file specified probably contains a typing error. Double
// check command and the existance of all files and then resubmit.
01171, 00000, "datafile %s going offline due to error advancing checkpoint"
// *Cause: The checkpoint in the file header could not be advanced. See
// accompanying errors for the reason. The datafile will be taken
// offline the same as for a write error of a data block.
// *Action: See accompanying errors for details. Restore access to the file,
// do media recovery, and bring it back online.
01172, 00000, "recovery of thread %s stuck at block %s of file %s"
// *Cause: Crash recovery or instance recovery could not apply a change to a
// block because it was not the next change. This can happen if the
// block was corrupted and then repaired during recovery.
// *Action: Do a RECOVER DATAFILE for the file containing the block. If this
// does not resolve the problem then restore the file from a backup
// and recover it.
01173, 00000, "data dictionary indicates missing data file from system tablespace"
// *Cause: Either the database has been recovered to a point in time in the
// future of the control file or a datafile from the system tablespace was
// omitted from the create control file command previously issued.
// *Action: For the former problem you need to recover the database from a
// more recent control file. For the latter problem, simply recreate the
// control file checking to be sure that you include all the datafiles in
// the system tablespace.
01174, 00000, "DB_FILES is %s buts needs to be %s to be compatible"
// *Cause: The maximum number of database files supported by this instance
// is not the same as for the other instances. All instances must
// be able to open all the files any instance can open.
// *Action: Change the value of the DB_FILES parameter to be compatible
01175, 00000, "data dictionary has more than the %s files allowed by the instance"
// *Cause: The data dictionary is found to have more files than that which can
// be supported by this instance.
// *Action: Shutdown the instance and restart with a larger number of db_files
01176, 00000, "data dictionary has more than the %s files allowed by the controlfile"
// *Cause: After a CREATE CONTROLFILE, the data dictionary was found to have
// more data files than that supported by the control file.
// *Action: Re-create the control file with a larger MAXDATAFILES.
01177, 00000, "data file does not match dictionary - probably old incarnation"
// *Cause: When comparing the control file with the data dictionary after
// a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this
// datafile was inconsistent with the dictionary. Most likely the
// file is a backup of a file that was dropped from the database,
// and the same file number was reused for a new file. It may also
// be that an incomplete recovery stopped at a time when this file
// number was used for another datafile.
// *Action: Do a CREATE CONTROLFILE with the correct file or none at all.
01178, 00000, "file %s created before last CREATE CONTROLFILE, cannot recreate"
// *Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a
// datafile that existed at the last CREATE CONTROLFILE command.
// The information needed to recreate the file was lost with the
// control file that existed when the file was added to the database.
// *Action: Find a backup of the file, and recover it. Do incomplete recovery
// to time before file was originally created.
01179, 00000, "file %s does not exist"
// *Cause: During datafile recovery, a file was listed which was not part
// for the database.
// *Action: Recheck the datafile name. Remember to use double quotes at the
// SQLDBA command line and remember that the file name is translated in the
// environment of the SQLDBA.
01180, 00000, "can not create datafile 1"
// *Cause: Attempting to create datafile 1 using ALTER DATABASE CREATE
// DATAFILE.
// *Action: Recover file from a backup or recreate database.
01181, 00000, "file %s created before last known RESETLOGS, cannot recreate"
// *Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a
// datafile that existed before the last known RESETLOGS.
// *Action: Find a backup of the file, and recover it. Do incomplete recovery
// to time before file was originally created.
01182, 00000, "cannot create database file %s - file is in use or recovery"
// *Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a
// datafile that is online in an open instance or is being recovered.
// *Action: Close database in all instances and end all recovery sessions
01183, 00000, "cannot mount database in SHARED mode"
// *Cause: Some other instance has the database mounted exclusive.
// *Action: Shutdown other instance then mount shared.
01184, 00000, "logfile group %s already exists"
// *Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for
// the new log which is already in use.
// *Action: Specify a different logfile number, or let the database choose
// an unused value.
01185, 00000, "logfile group number %s is invalid"
// *Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for
// the new log which is too large.
// *Action: Specify a correct logfile number.
01186, 00000, "file %s failed verification tests"
// *Cause: The data file did not pass the checks to insure it is part of the
// database. See the accompanying error messages for the reason the
// verification failed.
// *Action: Make the correct file available to the database. Then, either open
// the database, or execute ALTER SYSTEM CHECK DATAFILES.
01187, 00000, "cannot read from file %s because it failed verification tests"
// *Cause: The data file did not pass the checks to insure it is part of the
// database. Reads are not allowed until it is verified.
// *Action: Make the correct file available to the database. Then, either open
// the database, or execute ALTER SYSTEM CHECK DATAFILES.
01188, 00000, "The block size specified %s does not match header block size %s"
// *Cause: The block size specified in the BLOCKSIZE clause of the CREATE
// CONTROLFILE statement does not equate to the block size
// recorded in the log file header.
// *Action: Specify the correct block size.
01189, 00000, "file is from a different RESETLOGS than previous files"
// *Cause: In a CREATE CONTROLFILE command either this file or all previous
// files were backups from before the last RESETLOGS. This may also
// occur if this is a file that is offline and has been offline since
// before the last RESETLOGS.
// *Action: If the file was taken offline normal before the last RESETLOGS,
// and is still offline, omit it from the CREATE CONTROLFILE command.
// Rename and online the file after the database is open. Otherwise
// find the version of the mentioned file consistent with the rest
// of the datafiles and resubmit the command.
01190, 00000, "control file or data file %s is from before the last RESETLOGS"
// *Cause: Attempting to use a data file when the log reset information in
// the file does not match the control file. Either the data file
// or the control file is a backup that was made before the most
// recent ALTER DATABASE OPEN RESETLOGS.
// *Action: Restore file from a more recent backup.
01191, 00000, "file %s is already offline - cannot do a normal offline"
// *Cause: When attempting to do a normal tablespace offline it was discovered
// that one of the files in the tablespace was already offline.
// *Action: Either bring the datafile online first, or use another tablespace
// offline option.
01192, 00000, "must have at least one enabled thread"
// *Cause: You must specify at least two logfiles from at least one thread
// at the create contolfile command line.
// *Action: Find the missing logfiles and resubmit the command with the newly
// found logfiles included in the command line.
01193, 00000, "file %s is not the same file seen at start of recovery"
// *Cause: A different copy of the file was accessed the last time media
// recovery looked at the file header. A backup of the file was
// restored or the meaning of the file name changed during recovery.
// *Action:Ensure the correct file is available, then retry recovery.
01194, 00000, "file %s needs more recovery to be consistent"
// *Cause: An incomplete recovery session was started, but an insufficient
// number of logs were applied to make the file consistent. The
// reported file was not closed cleanly when it was last opened by
// the database. It must be recovered to a time when it was not being
// updated. The most likely cause of this error is forgetting to
// restore the file from a backup before doing incomplete recovery.
// *Action: Either apply more logs until the file is consistent or restore
// the file from an older backup and repeat recovery.
01195, 00000, "online backup of file %s needs more recovery to be consistent"
// *Cause: An incomplete recovery session was started, but an insufficient
// number of logs were applied to make the file consistent. The
// reported file is an online backup which must be recovered to the
// time the backup ended.
// *Action: Either apply more logs until the file is consistent or
// restore the database files from an older backup and repeat recovery.
01196, 00000, "file %s is inconsistent due to a failed media recovery session"
// *Cause: The file was being recovered but the recovery did not terminate
// normally. This left the file in an inconsistent state. No more
// recovery was successfully completed on this file.
// *Action:Either apply more logs until the file is consistent or restore
// the backup again and repeat recovery.
01197, 00000, "thread %s only contains one log"
// *Cause: During CREATE CONTROLFILE all threads represented in the logs
// must be represented by at least two logs. A "last log" and a second
// log. The named thread does not contain two such logs.
// *Action: Either find more logs from the named thread. Or use the
// RESETLOGS option to CREATE CONTROLFILE.
01198, 00000, "must specify size for log file if RESETLOGS"
// *Cause: File sizes must be given for all logfiles if doing a CREATE
// CONTROLFILE with the RESETLOGS option.
// *Action: Resubmit the command with the appropriate logfile size.
01199, 00000, "file %s is not in online backup mode"
// *Cause: Attempting to end an online backup for a file that is not in online
// backup.
// *Action: Do not enter command since it is not needed.
01200, 00000, "actual file size of %s is smaller than correct size of %s blocks"
// *Cause: The size of the file as returned by the operating system is smaller
// than the size of the file as indicated in the file header and the
// control file. Somehow the file has been truncated. Maybe it is the
// result of a half completed copy.
// *Action: Restore a good copy of the data file and do recovery as needed.
01201, 00000, "file %s header failed to write correctly"
// *Cause: An I/O error was reported for the file header. The error was
// trapped and a second attempt will be made.
// *Action: The file probably will require recovery. Further error messages
// will indicate what is needed.
01202, 00000, "wrong incarnation of this file - wrong creation time"
// *Cause: The creation time in the file header is not the same as the
// creation time in the control file. This is probably a copy of a
// file that was dropped.
// *Action: Restore a current copy of the data file and do recovery as needed.
01203, 00000, "wrong incarnation of this file - wrong creation SCN"
// *Cause: The creation SCN in the file header is not the same as the
// creation SCN in the control file. This is probably a copy of a
// file that was dropped.
// *Action: Restore a current copy of the data file and do recovery as needed.
01204, 00000, "file number is %s rather than %s - wrong file"
// *Cause: The file number in the file header is not correct. This is probably
// a restored backup of the wrong file, but from the same database.
// *Action: Restore a copy of the correct data file and do recovery as needed.
01205, 00000, "not a data file - type number in header is %s"
// *Cause: The file type in the header is not correct for a data file. This
// is probably a log file or control file. If the type is not a small
// non-zero positive number then the header is corrupted.
// *Action: Restore a copy of the correct data file and do recovery as needed.
01206, 00000, "file is not part of this database - wrong database id"
// *Cause: The database ID in the file header does not match the database id
// in the control file. The file may be from a different database, or
// it may not be a database file at all. If the database was rebuilt,
// this may be a file from before the rebuild. Note that if you see
// this error when the file is supposed to be plugged in from another
// database via the Transportable Tablespace feature, it means the
// database ID in the file header does not match the one expected.
// *Action: Restore a copy of the correct data file and do recovery as needed.
01207, 00000, "file is more recent than control file - old control file"
// *Cause: The control file change sequence number in the data file is
// greater than the number in the control file. This implies that
// the wrong control file is being used. Note that repeatedly causing
// this error can make it stop happening without correcting the real
// problem. Every attempt to open the database will advance the
// control file change sequence number until it is great enough.
// *Action: Use the current control file or do backup control file recovery to
// make the control file current. Be sure to follow all restrictions
// on doing a backup control file recovery.
01208, 00000, "data file is an old version - not accessing current version"
// *Cause: The checkpoint in the file header is less recent than in the
// control file. If opening a database that is already open by another
// instance, or if another instance just brought this file online,
// the file accessed by this instance is probably a different version.
// Otherwise, a backup of the file probably was restored
// while the file was in use.
// *Action: Make the correct file available to the database. Then, either open
// the database, or execute ALTER SYSTEM CHECK DATAFILES.
01209, 00000, "data file is from before the last RESETLOGS"
// *Cause: The reset log data in the file header does not match the
// control file. If the database is closed or the file is offline,
// the backup is old because it was taken before the last ALTER
// DATABASE OPEN RESETLOGS command. If opening a database that is
// open already by another instance, or if another instance just
// brought this file online, the file accessed by this instance is
// probably a different version. Otherwise, a backup of the file
// probably was restored while the file was in use.
// *Action: Make the correct file available to the database. Then, either open
// the database, or execute ALTER SYSTEM CHECK DATAFILES.
01210, 00000, "data file header is media corrupt"
// *Cause: The file header block is internally inconsistent. The beginning
// of the block has a header with a checksum and other data for
// insuring the consistancy of the block. It is possible that
// the last disk write did not operate correctly. The most likely
// problem is that this is not a datafile for any database.
// *Action: Have operating system make correct file available to database.
// If the trace file dump indicates that only the checksum is wrong,
// restore from a backup and do media recovery.
01211, 00000, "Oracle7 data file is not from migration to Oracle8"
// *Cause: The file is not a copy of the file LAST used under Oracle7. This
// datafile is either a backup taken from before the migration, or
// the database was opened by Oracle7 after the migration utility was
// run. When converting a database from Oracle7 to Oracle8, the migration
// program MUST be the LAST utility to access the database under Oracle7.
// Only the datafiles that were current when the migration was done
// may be accessed by Oracle8.
// *Action: Have operating system make correct data file available to database,
// or repeat the Oracle7 to Oracle8 migration. Make sure that
// database is NOT opened after migration utility is run.
01212, 00000, "MAXLOGMEMBERS may not exceed %s"
// *Cause: MAXLOGMEMBERS specified on the command line too large.
// *Action: Resubmit the command with a smaller MAXLOGMEMBERS
01213, 00000, "MAXINSTANCES may not exceed %s"
// *Cause: MAXINSTANCES specified on the command line too large.
// *Action: Resubmit the command with a smaller MAXINSTANCES
01214, 00000, "MAXLOGHISTORY may not exceed %s"
// *Cause: MAXLOGHISTORY specified on the command line too large.
// *Action: Resubmit the command with a smaller MAXLOGHISTORY
01215, 00000, "enabled thread %s is missing after CREATE CONTROLFILE"
// *Cause: A CREATE CONTROLFILE statement was given which did not
// list all the enabled threads for the database.
// *Action: Reissue the CREATE CONTROLFILE statement, including all enabled
// threads.
01216, 00000, "thread %s is expected to be disabled after CREATE CONTROLFILE"
// *Cause: A thread that was given during CREATE CONTROLFILE is enabled, but
// the datafiles indicate that it should be disabled. This is
// probably because the logs supplied to the CREATE CONTROLFILE
// are old (from before the disabling of the thread).
// *Action: This thread is not required to run the database. The CREATE
// CONTROLFILE statement can be reissued without the problem thread,
// and, if desired, the thread can be recreated after the database
// is open.
01217, 00000, "logfile member belongs to a different logfile group"
// *Cause: A member of a multiple-member logfile group specified in a
// CREATE CONTROLFILE is not part of the same group as previous
// members.
// *Action: Group together the correct members for the CREATE CONTROLFILE
// command.
01218, 00000, "logfile member is not from the same point-in-time"
// *Cause: A member of a multiple-member logfile group is from a different
// point in time. One of the members specified may be an older
// (backup) copy of the log.
// *Action: Find the correct version of the log, or leave it out of the
// CREATE CONTROLFILE command.
01219, 00000, "database or pluggable database not open: queries allowed on fixed tables or views only"
// *Cause: A query was issued against an object not recognized as a fixed
// table or fixed view before the database or pluggable database has
// been opened.
// *Action: Re-phrase the query to include only fixed objects, or open the
// database or pluggable database.
01220, 00000, "file based sort illegal before database is open"
// *Cause: A query issued against a fixed table or view required a temporary
// segment for sorting before the database was open. Only in-memory
// sorts are supported before the database is open.
// *Action: Re-phrase the query to avoid a large sort, increase the values
// of the SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE
// initialization parameters to enable the sort to be done in memory.
01221, 00000, "data file %s is not the same file to a background process"
// *Cause: When the database writer opens the data file, it is accessing a
// different physical file than the foreground doing the recovery.
// The timestamp set in the file header by the foreground was not
// found by the background. It may be that the background process
// could not read the file at all.
// *Action: Look in the DBWR trace file for the error it recieved when
// attempting to read the file header. Reconfigure the operating
// system as needed to have the file name successfully access the
// same file when opened by a background process.
01222, 00000, "MAXINSTANCES of %s requires MAXLOGFILES be at least %s, not %s"
// *Cause: Attemping to create a database or control file that does not have
// room for at least two logs per thread of redo. A thread of redo
// must have two online logs in order to be enabled. It does not make
// sense to allow more redo threads than can be supported by the logs.
// *Action: Either reduce the MAXINSTANCES argument or increase MAXLOGFILES.
01223, 00000, "RESETLOGS must be specified to set a new database name"
// *Cause: The SET database name option was specified to CREATE CONTROLFILE,
// but RESETLOGS was not specified. The database name can only be
// changed when opening the database with RESETLOGS.
// *Action: Either add the RESETLOGS option or drop the SET option to
// CREATE CONTROLFILE.
01224, 00000, "group number in header %s does not match GROUP %s"
// *Cause: Group number specified at CREATE CONTROLFILE does not match the
// group number stored in the header. Most likely the specification
// is wrong.
// *Action: Omit the GROUP option or give the correct one.
01225, 00000, "thread number %s is greater than MAXINSTANCES %s"
// *Cause: The log is for a thread greater than the MAXINSTANCES argument.
// *Action:Increase the value for MAXINSTANCES and resubmit the command.
01226, 00000, "file header of log member is inconsistent with other members"
// *Cause: The log file member in the accompanying error is for the same group
// as the previous members, but other fields in the header are
// different. Either a file header is corrupted, or some file is a
// member of a deleted log.
//*Action: Find the correct log member or omit this member from the command.
01227, 00000, "log %s is inconsistent with other logs"
// *Cause: The log file in the accompanying error is inconsistent with the
// contents of other logs given in the CREATE CONTROLFILE command.
// Either a file header is corrupted, or some file is an old copy
// rather than the current version. The problem may not be with the
// log listed since all that can be detected is that there is an
// inconsistancy. All log files listed in the command must be the
// current versions of the online logs.
//*Action: Find the correct online logs or use the RESETLOGS option.
01228, 00000, "SET DATABASE option required to install seed database"
// *Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE
// command when installing a seed database. The database does not have
// a database ID because it is intended to be installed at multiple
// sites, and each site needs to be a different database with its own
// database id. Both the SET DATABASE and RESETLOGS options must be
// specified to create the control file for this database.
//*Action: Resubmit command with the SET DATABASE and RESETLOGS options.
01229, 00000, "data file %s is inconsistent with logs"
// *Cause: The data file in the accompanying error is inconsistent with the
// contents of the logs given in the CREATE CONTROLFILE command.
// The most likely cause is that one or more of the online logs
// was missing from the command. It is also possible that one or
// more of the logs is an old copy rather than the current version.
// All online log files must be listed in the command and must be the
// current versions of the online logs.
//*Action: Find the correct online logs or use the RESETLOGS option.
01230, 00000, "cannot make read only - file %s is offline"
// *Cause: An attempt to make a tablespace read only found that one of its
// files is offline.
// *Action: Bring the file online and retry this command.
01231, 00000, "cannot make read write - file %s is offline"
// *Cause: An attempt to make a tablespace read write found that one of its
// files is offline.
// *Action: Bring the file online and retry this command.
01232, 00000, "cannot start online backup - file %s is being made read-only"
// *Cause: An attempt to start an online backup found that one of the files is
// in transition to read-only mode.
// *Action: Wait for the transition to complete and then retry the command, if
// this is an ALTER DATABASE BEGIN BACKUP command, or take the backup
// without any begin or end commands, if this is an ALTER TABLESPACE
// BEGIN BACKUP command.
01233, 00000, "file %s is read only - cannot recover using backup control file"
// *Cause: An attempt to do media recovery using a backup control file found
// that one of the files is marked read only. Read only files do not
// normally need to be recovered, but recovery with a backup
// control file must recover all online files.
// *Action: If the file really is read only, take it offline before the
// recovery, and bring the read only tablespace online after the
// database is open. If the file does need recovery use a control file
// from the time the file was read-write. If the correct control file
// is not available, use CREATE CONTROLFILE to make one.
01234, 00000, "cannot end backup of file %s - file is in use or recovery"
// *Cause: Attempted to end an online backup of file when the file is busy.
// Some operation such as recovery or rename may be active, or there
// may still be some instance that has the database open with this
// file online.
// *Action: If there is an instance with the database open then the backup
// can be ended there by using the ALTER TABLESPACE command. Otherwise
// wait for the completion of the other operation.
01235, 00000, "END BACKUP failed for %s file(s) and succeeded for %s"
// *Cause: One or more of the files in an end backup command failed. Some other
// files given in the same command may have succeeded.
// *Action: See the accompanying error messages for the reason the backups
// could not be ended. Any files not listed in the error messages were
// successful.
01236, 00000, "Error %s occurred during initialization of file header access"
// *Cause: The indicated error occurred while doing initialization
// processing of file headers.
// *Action: The error indicated should be corrected. An attempt is made to
// recover from this error by using a slower access algorithm.
01237, 00000, "cannot extend datafile %s"
// *Cause: An operating system error occurred during the resize.
// *Action: Fix the cause of the operating system error and retry the command.
01238, 00000, "cannot shrink datafile %s"
// *Cause: An operating system error occurred during the resize.
// *Action: The error is ignored, operation continues normally.
01239, 00000, "database must be in ARCHIVELOG mode to use external cache"
// *Cause: An online file uses an external cache, but the database is in
// NOARCHIVELOG mode. Since an external cache may require media
// recovery this can not be allowed.
// *Action: Change database to be in ARCHIVELOG mode or do not use an
// external cache.
01240, 00000, "too many data files to add in one command"
// *Cause: The command specifies adding more data files than can be done in
// one command. It is necessary to fit all the file names into one
// log entry, but that would make the entry too large.
// *Action: If this is a CREATE TABLESPACE command, create with fewer files
// then add the other files later. If this is an ADD DATAFILE command,
// break it up into multiple commands.
01241, 00000, "an external cache has died"
// *Cause: The external cache may have been restarted.
// *Action: Take the file mentioned in the error stack offline, perform media
// recovery, bring the file online, and retry the attempted
// operation. You may also restart all instances to make sure
// they access all data files through consistent external caches.
01242, 00000, "data file suffered media failure: database in NOARCHIVELOG mode"
// *Cause: The database is in NOARCHIVELOG mode and a database file was
// detected as inaccessible due to media failure.
// *Action: Restore accessibility to the file mentioned in the error stack
// and restart the instance.
01243, 00000, "system tablespace file suffered media failure"
// *Cause: A system tablespace file was detected as inaccessible due to
// media failure.
// *Action: Restore accessibility to the file mentioned in the error stack
// and restart the instance.
01244, 00000, "unnamed datafile(s) added to control file by media recovery"
// *Cause: Media recovery with a backup control file or a control file that
// was rebuilt, encountered the creation of a datafile that was not
// in the control file. An entry has been added to the control file
// for the new datafiles, but with the file name UNNAMEDnnnn, where
// nnnn is the file number. Attached errors describe the file names
// that were originally used to create the files.
// *Action: Rename the files to valid file names and resume recovery. If
// necessary the command ALTER DATABASE CREATE DATAFILE may be used
// to create a file suitable for recovery and do the rename. If the
// file is not going to be recovered then take it offline with the
// FOR DROP option.
01245, 00000, "offline file %s will be lost if RESETLOGS is done"
// *Cause: Attempting to do an OPEN RESETLOGS with a file that will be lost
// because it is offline. The file was not taken offline with the
// FOR DROP option.
// *Action: Either bring the file online and recover it, or take it offline
// with the FOR DROP option.
01246, 00000, "recovering files through TSPITR of tablespace %s"
// *Cause: The files named in the accompanying errors are backups that were
// made before a tablespace point in time recovery of this tablespace.
// They cannot be recovered to a time after the point in time
// recovery.
// *Action: Restore more recent backups and recover them.
01247, 00000, "database recovery through TSPITR of tablespace %s"
// *Cause: Recovery of the whole database encountered redo indicating there
// was a point in time recovery of the tablespace. The new version
// of the files in the tablespace should be included in the recovery,
// but that was not done.
// *Action: If the tablespace should not be recovered, take its file offline
// for drop. If it should be recovered, then restore or rename as
// needed and restart the recovery.
01248, 00000, "file %s was created in the future of incomplete recovery"
// *Cause: Attempting to do a RESETLOGS open with a file entry in the
// control file that was originally created after the UNTIL time
// of the incomplete recovery.
// Allowing such an entry may hide the version of the file that
// is needed at this time. The file number may be in use for
// a different file which would be lost if the RESETLOGS was allowed.
// *Action: If more recovery is desired then apply redo until the creation
// time of the file is reached. If the file is not wanted and the
// same file number is not in use at the stop time of the recovery,
// then the file can be taken offline with the FOR DROP option.
// Otherwise a different control file is needed to allow the RESETLOGS.
// Another backup can be restored and recovered, or a control file can
// be created via CREATE CONTROLFILE.
01249, 00000, "archiving not allowed in a clone database"
// *Cause: Attempting to archive an online redo log or enable archiving
// for a clone database.
// *Action: Do not attempt to archive from a clone. The archive log destination
// could easily be the same as the primary database destroying its
// archived logs. If archiving is needed then recreate database as
// not a clone.
01250, 00000, "Error %s occurred during termination of file header access"
// *Cause: The indicated error occurred while terminating the
// processing of file headers. The error was other than a write
// error.
// *Action: The indicated error should be corrected.
01251, 00000, "Unknown File Header Version read for file number %s"
// *Cause: Read of the file header returned a record but its version cannot
// be identified. Either the header has been corrupted, or the file
// is not a valid database file.
// *Action: Have the operating system make the correct file available to
// the database, or recover the file.
01252, 00000, "cannot prevent writes - file %s in recovery manager backup"
// *Cause: An attempt to make a tablespace read only or offline normal found
// that a recovery manager proxy backup is in progress. If the file
// is made offline or read-only, then the file header cannot be
// updated when the backup is complete.
// *Action: Wait for the Recovery Manager backup to complete and retry this
// command.
01253, 00000, "cannot start online backup - file %s in recovery manager backup"
// *Cause: The specified file is being backed up by Recovery Manager.
// *Action: Wait for the Recovery Manager proxy backup to complete before
// starting another backup.
01254, 00000, "cannot end online backup - file %s in recovery manager backup"
// *Cause: The specified file is being backed up by Recovery Manager.
// *Action: Wait for the Recovery Manager proxy backup to complete. Recovery
// Manager backup mode cannot be initiated or terminated manually.
01255, 00000, "cannot shutdown - file %s in recovery manager backup"
// *Cause: An attempt to shutdown normally found that a Recovery Manager
// backup is still in progress.
// *Action: Wait for the Recovery Manager proxy backup to complete and retry
// this command.
01256, 00000, "error in locking database file %s"
// *Cause: The file is in use by another database instance.
// *Action: Determine which database instance legitimately owns the file.
01257, 00000, "cannot reuse database file %s, unknown file size"
// *Cause: The size of the raw partion cannot be determined
// *Action: Add the datafile/logfile by specifying the size parameter.
01258, 00000, "unable to delete temporary file %s"
// *Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES
// or ALTER DATABASE TEMPFILE DROP INCLUDING DATAFILES
// operation was not able to delete a temporary file in the
// database.
// *Action: Subsequent errors describe the operating system error that
// prevented the file deletion. Fix the problem, if possible, and
// manually purge the file.
01259, 00000, "unable to delete datafile %s"
// *Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES operation
// was not able to delete a datafile in the tablespace.
// *Action: Subsequent errors describe the operating system error that
// prevented the file deletion. Fix the problem, if possible, and
// manually purge the file.
01260, 00000, "warning: END BACKUP succeeded but some files found not to be in backup mode"
// *Cause: END BACKUP completed successfully for all files that were in online
// backup mode. However one or more modifiable files were found not
// to be in online backup mode. Backup of those files (if it was done)
// can be invalid and, if restored, can result in an inconsistent
// database.
// *Action: Check the alert log for a list of the files that were found not
// to be in backup mode. If there is a possibility that those files
// have been modified during online backup, then replace their
// backups with new ones.
01261, 00000, "Parameter %s destination string cannot be translated"
// *Cause: The value for the specified parameter contained a destination
// string that could not be translated.
// *Action: Use a valid destination string in the specified parameter.
01262, 00000, "Stat failed on a file destination directory"
// *Cause: Unable to get information about an Oracle managed files
// destination directory.
// *Action: Check the permissions on the directory or use a different
// directory name.
01263, 00000, "Name given for file destination directory is invalid"
// *Cause: The name given for an Oracle managed files destination
// does not correspond to a directory.
// *Action: Use a different name.
01264, 00000, "Unable to create %s file name"
// *Cause: Unable to create an Oracle managed file name.
// *Action: Check previous error messages for the reason Oracle
// was unable to create the file name. Take corrective
// action, if possible, and retry the command.
01265, 00000, "Unable to delete %s %s"
// *Cause: An error prevented the file from being deleted.
// *Action: See the subsequent error messsages that describe the operating
// system error that prevented the file from being deleted. If
// possible, fix the problem and manually delete the file.
01266, 00000, "Unable to create unique file name"
// *Cause: Unable to create a unique file name for an Oracle managed file.
// Oracle tried several names but each file name was already in use
// in the default destination directory for the file type.
// *Action: Retry the operation. If that fails, also, it may be
// necessary to change the default destination directory for
// the file type and then retry.
01267, 00000, "Failure getting date/time"
// *Cause: Could not get date/time when trying to create unique
// file name.
// *Action: Internal error - contact Oracle Customer Support.
01268, 00000, "invalid TEMPFILE clause for alter of permanent TABLESPACE"
// *Cause: A TEMPFILE clause was specified for an ALTER TABLESPACE for
// a permanent tablespace.
// *Action: Retry with a DATAFILE clause.
01269, 00000, "Destination parameter string is too long"
// *Cause: The value for DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or
// DB_RECOVERY_FILE_DEST parameter was too long.
// *Action: Replace the destination value for the specified parameter with
// a shorter character string.
01270, 00000, "%s operation is not allowed if STANDBY_PRESERVES_NAMES is true"
// *Cause: An operation that renames or adds/drops a file was attempted
// at a standby database and STANDBY_PRESERVES_NAMES is true.
// *Action: Set STANDBY_PRESERVES_NAMES false if the operation must be
// performed.
01271, 00000, "Unable to create new file name for file %s"
// *Cause: During standby database recovery an error occurred when trying
// to create a new file name for the indicated file.
// *Action: Use the ALTER DATABASE CREATE DATAFILE command with a new
// unique name and then resume the standby database recovery.
01272, 00000, "REUSE only allowed when a file name is provided."
// *Cause: The REUSE parameter was specified in a command without a
// file name.
// *Action: Either supply a file name or remove the REUSE parameter.
01273, 00000, "STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = %s or higher"
// *Cause: The COMPATIBLE initialization parameter was not set to the
// correct value for setting STANDBY_FILE_MANAGEMENT to AUTO.
// *Action: Restart the instance with COMPATIBLE set to the correct release.
// *Cause: Automated standby file management was disabled, so an added file
01274, 0000, "cannot add data file that was originally created as '%s'"
// *Cause: The recovery failed to add the specified data file either because
// the recovery tried to create the specified data file but automated
// standby file management was disabled, or the recovery tried to look
// for the specified data file but the data file did not exist. In the
// former case, the recovery added a control file entry as
// 'UNNAMEDnnnnn'.
// *Action: Either use the ALTER DATABASE CREATE DATAFILE statement to create
// the file, or set STANDBY_FILE_MANAGEMENT to AUTO, or restore the
// data file to the location specified by the corresponding control
// file entry, and restart standby recovery.
01275, 00000, "Operation %s is not allowed if standby file management is automatic."
// *Cause: An operation that renames, adds, or drops a file was attempted
// at a standby database and STANDBY_FILE_MANAGEMENT was set to AUTO.
// *Action: Set STANDBY_FILE_MANAGEMENT to MANUAL if the operation must be
// performed.
01276, 00000, "Cannot add file %s. File has an Oracle Managed Files file name."
// *Cause: An attempt was made to add to the database a datafile, log file,
// control file, snapshot control file, backup control file,
// datafile copy, control file copy or backuppiece with an Oracle
// Managed Files file name.
// *Action: Retry the operation with a new file name.
01277, 00000, "file '%s' already exists"
// *Cause: An ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename'
// command specified a file name which is already in use.
// *Action: Either specify a different file name, or add the REUSE parameter
// to the command to overwrite the existing file.
01278, 00000, "error creating file '%s'"
// *Cause: An operating system error occurred while attempting to create a
// trace file specified in the command ALTER DATABASE BACKUP
// CONTROLFILE TO TRACE AS 'filename'.
// *Action: Check the error stack for more detailed information.
01279, 00000, "db_files too large"
// *Cause: db_files has been set too high to be supported by the system.
// *Action: Decrease the number of db_files.
/
/ 1280-1399 LogMiner errors
/
01280, 00000, "Fatal LogMiner error."
// *Cause: An internal error occurred inside LogMiner.
// *Action: Check the alert log and trace files for further information.
01281, 00000, "SCN range specified is invalid"
// *Cause: StartSCN may be greater than EndSCN, or the SCN specified may be
// invalid.
// *Action: Specify a valid SCN range.
01282, 00000, "date range specified is invalid"
// *Cause: startTime may be greater than endTime. startTime or endTime may be
// greater than year 2110. startTime may be less than year 1988.
// *Action: Specify a valid date range.
01283, 00000, "Options specified is invalid"
// *Cause: The specified options parameter is invalid for the procedure.
// *Action: Specify valid Options parameter.
01284, 00000, "file %s cannot be opened"
// *Cause: The file or directory may not exist or may be inaccessible.
// Pathname exceeds 256 characters.
// *Action: Ensure that the file and the directory exist and are accessible.
01285, 00000, "error reading file %s"
// *Cause: The file or directory may not exist or is inaccessible.
// *Action: Specify valid file or directory. Make sure that file and directory
// are accessible.
01286, 00000, "start interval required"
// *Cause: Options were supplied which require a starting time or starting SCN
// *Action: Specify a starting interval (time or SCN).
01287, 00000, "file %s is from a different database incarnation"
// *Cause: The logfile is produced by a different incarnation of the database.
// *Action: Add a logfile that is produced by the same incarnation.
01288, 00000, "cannot apply this DDL to the Logminer Dictionary"
// *Cause: A command that is not supported by Logminer was present in
// a logfile. Commands that change the character set of the database
// are not supported by Logminer.
// "ALTER DATABASE SET TIME_ZONE" is not supported by Logminer.
// *Action: Do not execute unsupported commands when using Streams, Logical
// Standby, or Logminer. Turn off DDL tracking in order for Logminer
// to skip unsupported commands.
01289, 00000, "cannot add duplicate logfile %s"
// *Cause: The logfile specified has already been added to the list of
// logfiles.
// *Action: Specify a different logfile.
01290, 00000, "cannot remove unlisted logfile %s"
// *Cause: The user attempted to remove a logfile that is not present in the
// list.
// *Action: Specify a valid logfile.
01291, 00000, "missing logfile"
// *Cause: Not all logfiles corresponding to the time or scn range specified
// have been added to the list.
// *Action: Check the v$logmnr_logs view to determine the missing scn
// range, and add the relevant logfiles.
01292, 00000, "no log file has been specified for the current LogMiner session"
// *Cause: No logfile has been specified for the LogMiner session.
// *Action: Specify atleast one log file.
01293, 00000, "mounted database required for specified LogMiner options"
// *Cause: Options were specified which required the database to be mounted
// *Action: Specify different options or mount the database.
01294, 00000, "error occurred while processing information in dictionary file %s, possible corruption"
// *Cause: The dictionary file is corrupt.
// *Action: Get a new dictionary file.
01295, 00000, "DB_ID mismatch between dictionary %s and logfiles"
// *Cause: The dictionary file is produced by a database that is different
// from that produced the logfiles.
// *Action: Specify a compatible dictionary file.
01296, 00000, "character set mismatch between dictionary %s and logfiles"
// *Cause: The character set of the database that produced the dictionary
// file is different from the charatcter set of the database
// that produced the logfiles.
// *Action: Specify a dictionary file with the same character set.
01297, 00000, "redo version mismatch between dictionary %s and logfiles"
// *Cause: The redo version of the database generating the dictionary is
// different from the one generating the logfiles.
// *Action:
01298, 00000, "conflicting dictionary option"
// *Cause: More than one dictionary source was specified or DDL_DICT_TRACKING
// was specified with DICT_FROM_ONLINE_CATALOG.
// *Action:
01299, 00000, "dictionary %s corresponds to a different database incarnation"
// *Cause: The dictionary file was extracted from a different incarnation of
// the database.
// *Action: Specify a dictionary file extracted from the correct database
// incarnation.
01300, 00000, "writable database required for specified LogMiner options"
// *Cause: Options were specified which required the database to be writable.
// *Action: Specify different options or open the database for write access.
01301, 00000, "error writing to file during flat file build"
// *Cause: Error writing to file during flat file build
// *Action:
01302, 00000, "dictionary build options missing or incorrect"
// *Cause: Missing dictionary build options or incorrectly specified options
// *Action: Specify either a build to redo log or to flat file. If build to
// flat file, specify filename and directory.
01303, 00000, "subordinate process error: %s. Check alert and trace logs"
// *Cause: A process subordinate to this Logminer process has exited with
// this error status.
// *Action: Search for this error in the alert log and trace files for
// additional information.
01304, 00000, "subordinate process error. Check alert and trace logs"
// *Cause: A process subordinate to this Logminer process has exited with an
// error condition.
// *Action: Look in the alert log and trace files for additional information.
01305, 00000, "incompatible database character set"
// *Cause: The database character set of the mining database was not a
// superset of the source database character set.
// *Action: Perform the mining operation on a database having a compatible
// database character set.
01306, 00000, "dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents"
// *Cause: A select was issued from v$logmnr_contents without first invoking
// the dbms_logmnr.start_logmnr() procedure.
// *Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing
// a select from the v$logmnr_contents view.
01307, 00000, "no LogMiner session is currently active"
// *Cause: A select was issued from v$logmnr_contents without first invoking
// the dbms_logmnr.start_logmnr() procedure. Otherwise,
// dbms_logmnr.end_logmnr() was called without a prior call to
// dbms_logmnr.start_logmnr() or dbms_logmnr.add_logfile()
// *Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing
// a select from the v$logmnr_contents view.
01308, 00000, "dictionary directory is not set"
// *Cause: The dictionary directory was not valid.
// *Action: Set the dictionary directory to an appropriate value.
01309, 00000, "invalid session"
// *Cause: The specified Logminer session ID or session handle is invalid.
// *Action: Use a valid Logminer session ID or session handle.
01310, 00000, "requested return type not supported by the lcr_mine function"
// *Cause: The return type requested by the user is not supported by lcr_mine"
// *Action: Pick a return type supported by the lcr_mine function"
01311, 00000, "Illegal invocation of the mine_value function"
// *Cause: An attempt was made to use mine_value function on a column
// other than redo_value or undo_value columns of SYS.X$LOGMNR_CONTENTS
// or SYS.V$LOGMNR_CONTENTS fixed table/view.
// *Action: Rewrite the SQL statement with a legal invocation of mine_value
01312, 00000, "Specified table/column does not exist"
// *Cause: The table/column specified in the lcr_mine call does not exist
// at the the specified SCN. The table/column definition has to exist
// at the start SCN specified for lcr_mine to be able to identify
// the table/column correctly.
// *Action: Create a LogMiner session at a start SCN at which the table
// definition is available.
01313, 00000, "LogMiner dictionary column type different from specified type"
// *Cause: The return type specified for the column in lcr_mine call
// is different from the actual type of the column.
// *Action: Rewrite the lcr_mine invocation with the right return type.
01314, 00000, "Name of the column to be mined should be a string literal"
// *Cause: The fully qualified name of the column to be mined
// by the LogMiner functions should be string literal.
// *Action: If the fully qualified name of the column to be mined is a.b.c.d,
// enclose the column name in quotes as in 'a.b.c.d'.
01315, 00000, "Log file has been added or removed during select"
// *Cause: A redo log file has been added or removed while selecting
// on the v$logmnr_logs fixed view.
// *Action: Re-issue the SQL select statement on the v$logmnr_logs view.
01316, 00000, "Already attached to a Logminer session"
// *Cause: A Logminer attach session was issued while already attached
// to a Logminer session.
// *Action: Detach from the current Logminer session and attach to the
// requested session.
01317, 00000, "Not attached to a Logminer session"
// *Cause: A command or procedure was issued which requires an attached
// Logminer session.
// *Action: Attach to a Logminer session before issuing the command or
// procedure.
01318, 00000, "incompatible national character set"
// *Cause: The national character set of the mining database was not a
// superset of the source database national character set.
// *Action: Perform the mining operation on a database having a compatible
// national character set.
01319, 00000, "Invalid Logminer session attribute"
// *Cause: A session attribute was supplied which is invalid.
// *Action: Re-issue with valid session attribute.
01320, 00000, "Invalid Logminer dictionar attribute"
// *Cause: A Logminer dictionary attribute was supplied which is invalid.
// *Action: Re-issue with valid dictionary attribute.
01321, 00000, "No Logminer Dictionary for requested start SCN"
// *Cause: The requested session start SCN is less than the SCN of any
// available Logminer Dictionary build. It is not possible to
// unwind a Logminer Dictionary to the requested start SCN.
// *Action: Re-issue the start_logminer request with a start SCN for
// which a Logminer Dictionary is available.
01322, 00000, "No such table"
// *Cause: An non-existent table was supplied to Logminer include_src_tbl()
// or exclude_src_table().
// *Action: Re-issue with valid table name.
01323, 00000, "Invalid state"
// *Cause: A Logminer routine was called from the wrong state.
// *Action:
01324, 00000, "cannot add file %s due to DB_ID mismatch"
// *Cause: The logfile is produced by a different database than other logfiles
// already added to the list.
// *Action: Specify a logfile produced by the same database.
01325, 00000, "archive log mode must be enabled to build into the logstream"
// *Cause: Database does not have archivelog mode enabled.
// *Action: Mount the database, then issue commands to enable archivelog mode.
// startup pfile=init.ora mount
// alter database archivelog
// alter database open
01326, 00000, "compatability of 9.0 or greater required to build into the logstream"
// *Cause: Compatibility mode set to some value less than 9.0
// *Action: Ensure that init.ora parameter establishing a compatability of
// 9.0 or greater is set. For example:
// compatible=9.0.0.0.0
01327, 00000, "failed to exclusively lock system dictionary as required by build"
// *Cause: Other users are performing DDL operations.
// *Action:
01328, 00000, "only one build operation may occur at one time"
// *Cause: Another processes is simultaneously attempting to run build();
// *Action: Wait until the other processes completes.
01329, 00000, "unable to truncate required build table"
// *Cause: The table may be missing, or locked by another user.
// *Action:
01330, 00000, "problem loading a required build table"
// *Cause:
// *Action:
01331, 00000, "general error while running build"
// *Cause:
// *Action:
01332, 00000, "internal Logminer Dictionary error"
// *Cause: Unexpected error condition
// *Action: Check trace and/or alert logs
01333, 00000, "failed to establish Logminer Dictionary"
// *Cause: No previously established Logminer Dictionary is available
// and a complete gather of a source system data dictionary was not
// found in the logstream. build() may not have been run
// to force the gathering of a source system data dictiony.
// Or add_log_file() may not have been called to add all log
// files which contain the complete gathered system data dictionary.
// *Action: If build() was not employed prior to this mining session
// the Logminer Ad Hoc user may elect to employ an alternate
// dictionary such as the current system catalog or a previously
// built flat file dictionary. Other Logminer clients must run
// build() prior to mining. If build() has been run, ensure that
// all logfiles which comprise the gathered system dictionary
// have beed added. The following query, run on the system which
// build() was run, can be helpful in identifying the requried files.
//
// select DICTIONARY_BEGIN, DICTIONARY_END, name from v$archived_log;
//
// Minimally a set of files beginning with one which has
// DICTIONARY_BEGIN = 'YES' and all following log files through
// one marked DICTIONARY_END = 'YES' must be added.
01334, 00000, "invalid or missing logminer dictionary processes context"
// *Cause: Unexpected internal error condition
// *Action:
01335, 00000, "feature not yet implemented"
// *Cause:
// *Action:
01336, 00000, "specified dictionary file cannot be opened"
// *Cause: The dictionary file or directory does not exist or is inaccessible.
// *Action: Make sure that the dictionary file and directory exist and are
// accessible.
01337, 00000, "log file has a different compatibility version"
// *Cause: The logfile has a different compatibility version then the rest
// of the logfile in the session"
// *Action: Make sure that the logfile has the same compatibility version
// as the rest of the logfiles in the session.
//
01338, 00000, "Other process is attached to LogMiner session"
// *Cause: Can not do this when other process is attached to LogMiner session.
// *Action:
01339, 0000, "LogMiner BUILD: Error copying system catalog metadata to LogMiner dictionary"
// *Cause: Unexpected result while accessing system catalog metadata.
// *Action: Check the alert log.
01340, 00000, "NLS error"
// *Cause: Could not load NLS package.
// *Action:
01341, 00000, "LogMiner out-of-memory"
// *Cause: The LogMiner session requires more system resources than is
// currently available.
// *Action: Allocate more SGA for LogMiner.
01342, 00000, "LogMiner can not resume session due to inability of staging checkpointed data"
// *Cause: Logmnr can not resume session because there is not enough SGA
// memory available to read in checkpointed data. Logminer
// periodically checkpoints data to enable faster crash recovery.
// *Action: Specify a bigger max_sga for the given LogMiner session and
// try again.
01343, 00000, "LogMiner encountered corruption in the logstream"
// *Cause: Log file is missing a range of scn values.
// *Action: Verify the contiguity of the scn range reprented by the log files
// added to LogMiner.
01344, 00000, "LogMiner coordinator already attached"
// *Cause: A coordinator process is already attached to the specified
// logminer context.
// *Action: Detach from the active coordinator session and retry the attach.
01345, 00000, "Must be a LogMiner coordinator process"
// *Cause: A LogMiner client attempted to perform a privileged operation.
// *Action: Issue the operation from the coordinator process.
01346, 00000, "Oracle LogMiner processed redo beyond primary reset log SCN %s"
// *Cause: Oracle LogMiner detected a new branch with reset log SCN information
// prior to redo already mined.
// *Action: If running inside SQL Apply, retrieve standby reset SCN by executing
// DBMS_LOGSTDBY.MAP_PRIMARY_SCN (primary reset log SCN). And, execute
// FLASHBACK STANDBY DATABASE [<database_name>] TO BEFORE SCN <standby reset SCN>.
// Note: If the primary reset log SCN is 0, then intermediary log files
// are missing. Check the primary database for missing log files.
//
// In other scenarios, contact Oracle Support Services.
01347, 00000, "Supplemental log data no longer found"
// *Cause: The source database instance producing log files for this LogMiner
// session was altered to no longer log supplemental data.
// *Action: Destroy this Logminer session. Re-enable supplemental log data
// on the source system and create a new LogMiner session.
01348, 00000, "LogMiner testing event"
// *Cause:
// *Action:
01349, 00000, "LogMiner tracing event"
// *Cause:
// *Action:
01350, 00000, "must specify a tablespace name"
// *Cause: Invocation failed to specify a valid tablespace
// *Action: Reformat invocation of DBMS_LOGMNR_D.SET_TABLESPACE to include
// the name of a valid tablespace.
01351, 00000, "tablespace given for Logminer dictionary does not exist"
// *Cause: The tablespace name given as a parameter to
// DBMS_LOGMNR_D.SET_TABLESPACE
// does not exist.
// *Action: Check spelling of the tablespace name. If spelling is correct
// verify that the named tablespace has already been created.
// DBMS_LOGMNR_D.SET_TABLESPACE does not create a tablespace.
01352, 00000, "tablespace given for Logminer spill does not exist"
// *Cause: The tablespace name given as the parameter to
// DBMS_LOGMNR_D.SET_TABLESPACE
// does not exist.
// *Action: Check spelling of the tablespace name. If spelling is correct
// verify that the named tablespace has already been created.
// DBMS_LOGMNR_D.SET_TABLESPACE does not create a tablespace.
01353, 00000, "existing Logminer session"
// *Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while
// a Logminer session(s) was active.
// *Action: First cause all Logminer sessions to be closed. A Logminer
// session can exist as a result of executing DBMS_LOGMNR.START_LOGMNR
// or as the result of using Oracle features such as
// Data Guard SQL Apply or Streams which use Logminer.
// Next, execute DBMS_LOGMNR_D.SET_TABLESPACE.
01354, 00000, "Supplemental log data must be added to run this command"
// *Cause: An attempt was made to perform an operation that required
// that supplemental log data be enabled.
// *Action: Execute a command such as
// ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
// and then reissue the command that failed with this error.
01355, 00000, "logminer tablespace change in progress"
// *Cause: The tables used by logminer are in the process of being
// moved to another tablespace.
// *Action: Wait until the move is complete and try again.
01356, 00000, "active logminer sessions found"
// *Cause: Logminer sessions are currently active.
// *Action: End all logminer sessions and retry.
01357, 00000, "LogMiner transaction queue is full"
// *Cause: LogMiner ran out of space in the transaction queue.
// *Action: Increase the LogMiner transaction queue size and LogMiner
// system global area (SGA) parameters.
01358, 00000, "LogMiner version is less than mined dictionary version"
// *Cause: An attempt was made to mine a LogMiner dictionary from redo logs.
// The version of the Oracle database that created the logs was higher
// than the Oracle database version that attempted to mine the logs.
// *Action: Mine the logs using a newer version of the Oracle database having a
// version number that is equal to or greater than the dictionary
// version.
01360, 00000, "invalid token"
// *Cause:
// *Action:
01361, 00000, "global name mismatch"
// *Cause : The database global name where the log file was generated did not
// match the user-specified global name of the Streams Capture process.
// *Action: Start a new capture process and ensure that the user-specified
// global name matches that of the database that generated the log
// file.
//
01362, 00000, "Specified SQL_REDO_UNDO parameter is invalid"
// *Cause: The specified input value for the parameter was not a valid number.
// *Action: Specify a valid number and try again.
//
01363, 00000, "Specified COLUMN_NAME parameter is NULL"
// *Cause: NULL was specified for input value of parameter.
// *Action: Specify a non-NULL value and try again.
//
01364, 00000, "waiting for branch at SCN %s"
// *Cause: LogMiner reader process has completed mining of physical standby
// terminal logs up to the stop SCN. LogMiner reader is now waiting
// for logs from the new branch.
// *Action: No action necessary. This informational statement is provided
// to record the event for diagnostic purposes. If there is a problem
// with log transport, the files can be registered manually using the
// ALTER DATABASE REGISTER LOGICAL LOGFILE statement.
//
01365, 00000, "waiting for new branch registration"
// *Cause: LogMiner reader process has completed mining of physical standby
// terminal logs up to the stop SCN. The builder process is now
// waiting for logs from the new branch to be registered before
// continuing.
// *Action: No action necessary. This informational statement is provided
// to record the event for diagnostic purposes. If there is a problem
// with log transport, the files may be registered manually using the
// ALTER DATABASE REGISTER LOGICAL LOGFILE statement.
//
01366, 00000, "failed to find redo logs required for terminal apply"
// *Cause: LogMiner failed to find all the expected log files required
// to complete the terminal apply, requested using the
// FINISH APPLY clause. During terminal apply, LogMiner does not
// wait for logs to be registered. It expects all logs between
// the starting point and the last log on any redo branch
// that it will or could mine through, to be present at the
// mining site.
// *Action: Examine system.logmnr_log$ to see which logs are known to
// LogMiner. Then, locate or restore any missing logs and use the
// ALTER DATABASE REGISTER LOGICAL LOGFILE statement to register
// them. Alternatively, do not use the FINISH APPLY clause, but if
// activating a logical standby, only do this when you are sure that
// the missing log files can not be located and registered as this
// can lead to data loss.
//
01370, 00000, "Specified restart SCN is too old"
// *Cause: specified restart scn is too old, logmnr could not
// find a proper checkpoint.
// *Action: Specify a bigger restart SCN to try again
//
01371, 00000, "Complete LogMiner dictionary not found"
// *Cause: One or more log files containing the LogMiner dictionary was not
// found.
// *Action: Add into LogMiner all log files containing the dictionary.
//
01372, 00000, "Insufficient processes for specified LogMiner operation"
// *Cause: The number of processes requested by the caller can not
// be allocated
// *Action: Increase number of parallel servers allocated to the instance
//
01373, 00000, "insufficient memory for staging persistent LogMiner session"
// *Cause: The maximum number of concurrent persistent LogMiner sessions
// allowed is limited by LOGMNR_MAX_PERSISTENT_SESSIONS parameter.
// Not enough memory has been set aside at instance startup to
// allocate the new LogMiner session.
// *Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance.
//
01374, 00000, "_log_parallelism_max greater than 1 not supported in this release"
// *Cause: LogMiner does not mine redo records generated with
// _log_parallelism_max set to a value greater than 1.
// *Action:
//
01375, 00000, "Corrupt logfile %s recovered"
// *Cause: A corrupt logfile has been recovered by RFS
// *Action: None. Logical Standby should automatically restart. If logfile is
// still corrupt, may need to manually copy and reregister the logfile
// on the standby.
//
01376, 00000, "cannot add file %s due to unsupported redo compatibility setting"
// *Cause: The redo compatibility setting of the log file was unsupported by
// LogMiner.
// *Action: Specify a log file produced with a redo compatibility setting
// supported by LogMiner.
//
01377, 00000, "Invalid log file block size"
// *Cause: An invalid value was specified in the BLOCKSIZE clause.
// *Action: Use correct syntax.
01378, 00000, "The logical block size (%s) of file %s is not compatible with the disk sector size (media sector size is %s and host sector size is %s)"
// *Cause: One of the following occurred:
// (1) An attempt was made to create a file.
// (2) A file was moved to disks with different sector size.
// *Action: Create file or move file to the proper disk.
01379, 00000, "LogMiner testing event"
// *Cause:
// *Action:
01380, 00000, "Instance %s (thread %s) has less than two %s block size log files"
// *Cause: One of the following occurred:
// (1) An attempt was made to switch to specified block size logs for
// all threads.
// (2) An attemp was made to open a thread.
// *Action: Add log files to the thread that signals error, and try again.
01381, 00000, "Dropping log %s would leave less than two log files with block size %s for instance %s (thread %s)"
// *Cause: The database was migrated to use a specified log block size.
// Dropping all the logs specified would leave fewer than the required
// two log files with the specified block size per enabled thread.
// *Action: Either drop fewer logs or disable the thread before deleting the
// logs. It may be possible to clear the log rather than drop it.
01382, 00000, "Thread %s failed to open log file %s. The log file's block size (%s) is larger than the disk sector size (%s)"
// *Cause: Log file was created on bigger sector disks, and moved to smaller
// sector disks.
// *Action: Move the log file back to bigger sector disks.
01383, 00000, "Thread %s failed to open %s block size log file '%s' on %s sector native-mode disks"
// *Cause: Log file was copied from smaller sector disks to larger sector
// native-mode disks.
// *Action: Move the log file back to smaller sector disks.
/
/ 1384 - 1396 Reserved for 4K block size log file errors
/
/
01397, 00000, "file name too long to shrink without truncation"
// *Cause: An attempt was made to automatically convert the control file created with maximum file name size value of 512 to 256. This
// could result in truncation of file names leading to loss of uniqueness among file names.
// *Action: One of the following can be done:
// 1) Change the _kccacb parameter value to 'reject' which will ignore the automatic conversion without returning this error.
// 2) Shorten the file names in the system where the control file was created to conform to the maximum file name length
// in the current system.
01398, 00000, "LogMiner public event"
// *Cause:
// *Action:
/
/
01399, 00000, "LogMiner public event"
// *Cause:
// *Action:
/
/ 1380-1399 KST tracing errors renumbered at 2480-2499 for MERGE
/
/ 1400-1499 SQL execute phase errors
/
01400, 00000, "cannot insert NULL into (%s)"
// *Cause: An attempt was made to insert NULL into previously listed objects.
// *Action: These objects cannot accept NULL values.
01401, 00000, "inserted value too large for column"
// *Cause: The value inserted was too large for the given column.
// *Action: Do not insert a value greater than what the column can hold.
01402, 00000, "view WITH CHECK OPTION where-clause violation"
// *Cause:
// *Action:
01403, 00000, "no data found"
// *Cause: No data was found from the objects.
// *Action: There was no data from the objects which may be due to end of fetch.
01404, 00000, "ALTER COLUMN will make an index too large"
// *Cause:
// *Action:
01405, 00000, "fetched column value is NULL"
// *Cause:
// *Action:
01406, 00000, "fetched column value was truncated"
// *Cause: The fetched column values were truncated.
// *Action: Use the right data types to avoid truncation.
01407, 00000, "cannot update (%s) to NULL"
// *Cause:
// *Action:
01408, 00000, "such column list already indexed"
// *Cause:
// *Action:
01409, 00000, "NOSORT option may not be used; rows are not in ascending order"
// *Cause: Creation of index with NOSORT option when rows were not ascending.
// For non-unique indexes the rowid is considered part of the index
// key. Therefore, if you create an index nosort and two of the rows
// in the table have the same key and are stored in ascending order,
// but get split accross two extents where the dba of the first block
// in the second extent is less than the dba of the last block in the
// first extent, then the create index nosort may fail.
// *Action: Create the index without the NOSORT option, or ensure table is
// stored in one extent.
01410, 00000, "invalid ROWID"
// *Cause:
// *Action:
01411, 00000, "cannot store the length of column in the indicator"
// *Cause: Tried to fetch a column of size more than 64K and couldn't store
// the length of the column in the given indicator of size 2 bytes.
// *Action: Use the new bind type with call backs to fetch the long column.
01412, 00000, "zero length not allowed for this datatype"
// *Cause: The length for type 97 is 0
// *Action: Specify the correct length.
01413, 00000, "illegal value in packed decimal number buffer"
// *Cause: The user buffer bound by the user as packed decimal number
// contained an illegal value.
// *Action: Use a legal value.
01414, 00000, "invalid array length when trying to bind array"
// *Cause: An attempt was made to bind an array without either a current
// array length pointer or a zero maximum array length.
// *Action: Sepcify a valid length.
01415, 00000, "too many distinct aggregate functions"
// *Cause: The query contains more distinct aggregates than can be processed.
// The current limit is 255.
// *Action: Reduce the number of distinct aggregate functions in the query.
01416, 00000, "two tables cannot be outer-joined to each other"
// *Cause:
// *Action:
01417, 00000, "a table may be outer joined to at most one other table"
// *Cause: a.b (+) = b.b and a.c (+) = c.c is not allowed
// *Action: Check that this is really what you want, then join b and c first
// in a view.
01418, 00000, "specified index does not exist"
// *Cause:
// *Action:
01419, 00000, "datdts: illegal format code"
// *Cause:
// *Action:
01420, 00000, "datstd: illegal format code"
// *Cause:
// *Action:
01421, 00000, "datrnd/dattrn: illegal precision specifier"
// *Cause:
// *Action:
01422, 00000, "exact fetch returns more than requested number of rows"
// *Cause: The number specified in exact fetch is less than the rows returned.
// *Action: Rewrite the query or change number of rows requested
01423, 00000, "error encountered while checking for extra rows in exact fetch"
// *Cause:
// *Action: See the following error and take appropriate action.
01424, 00000, "missing or illegal character following the escape character"
// *Cause: The character following the escape character in LIKE pattern is
// missing or not one of the escape character, '%', or '_'.
// *Action: Remove the escape character or specify the missing character.
01425, 00000, "escape character must be character string of length 1"
// *Cause: Given escape character for LIKE is not a character string of
// length 1.
// *Action: Change it to a character string of length 1.
01426, 00000, "numeric overflow"
// *Cause: Evaluation of an value expression causes an overflow/underflow.
// *Action: Reduce the operands.
01427, 00000, "single-row subquery returns more than one row"
// *Cause:
// *Action:
01428, 00000, "argument '%s' is out of range"
// *Cause:
// *Action:
01429, 00000, "Index-Organized Table: no data segment to store overflow row-pieces"
// *Cause: No overflow segment defined.
// *Action: Add overflow segment.
01430, 00000, "column being added already exists in table"
// *Cause:
// *Action:
01431, 00000, "internal inconsistency in GRANT command"
// *Cause:
// *Action:
01432, 00000, "public synonym to be dropped does not exist"
// *Cause:
// *Action:
01433, 00000, "synonym to be created is already defined"
// *Cause:
// *Action:
01434, 00000, "private synonym to be dropped does not exist"
// *Cause:
// *Action:
01435, 00000, "user does not exist"
// *Cause:
// *Action:
01436, 00000, "CONNECT BY loop in user data"
// *Cause:
// *Action:
01437, 00000, "cannot have join with CONNECT BY"
// *Cause:
// *Action:
01438, 00000, "value larger than specified precision allowed for this column"
// *Cause: When inserting or updating records, a numeric value was entered
// that exceeded the precision defined for the column.
// *Action: Enter a value that complies with the numeric column's precision,
// or use the MODIFY option with the ALTER TABLE command to expand
// the precision.
01439, 00000, "column to be modified must be empty to change datatype"
// *Cause:
// *Action:
01440, 00000, "column to be modified must be empty to decrease precision or scale"
// *Cause:
// *Action:
01441, 00000, "cannot decrease column length because some value is too big"
// *Cause:
// *Action:
01442, 00000, "column to be modified to NOT NULL is already NOT NULL"
// *Cause:
// *Action:
01443, 00000, "internal inconsistency; illegal datatype in resultant view column"
// *Cause:
// *Action:
01444, 00000, "internal inconsistency; internal datatype maps to invalid external type"
// *Cause:
// *Action:
01445, 00000, "cannot select ROWID from, or sample, a join view without a key-preserved table"
// *Cause:
// *Action:
01446, 00000, "cannot select ROWID from, or sample, a view with DISTINCT, GROUP BY, etc."
// *Cause:
// *Action:
01447, 00000, "ALTER TABLE does not operate on clustered columns"
// *Cause:
// *Action:
01448, 00000, "index must be dropped before changing to desired type"
// *Cause:
// *Action:
01449, 00000, "column contains NULL values; cannot alter to NOT NULL"
// *Cause:
// *Action:
01450, 00000, "maximum key length (%s) exceeded"
// *Cause:
// *Action:
01451, 00000, "column to be modified to NULL cannot be modified to NULL"
// *Cause: the column may already allow NULL values, the NOT NULL constraint
// is part of a primary key or check constraint.
// *Action: if a primary key or check constraint is enforcing the NOT NULL
// constraint, then drop that constraint.
01452, 00000, "cannot CREATE UNIQUE INDEX; duplicate keys found"
// *Cause:
// *Action:
01453, 00000, "SET TRANSACTION must be first statement of transaction"
// *Cause: self-evident
// *Action: commit (or rollback) transaction, and re-execute
01454, 00000, "cannot convert column into numeric datatype"
// *Cause:
// *Action:
01455, 00000, "converting column overflows integer datatype"
// *Cause:
// *Action:
01456, 00000, "may not perform insert/delete/update operation inside a READ ONLY transaction"
// *Cause: A non-DDL insert/delete/update or select for update operation
// was attempted
// *Action: commit (or rollback) transaction, and re-execute
01457, 00000, "converting column overflows decimal datatype"
// *Cause:
// *Action:
01458, 00000, "invalid length inside variable character string"
// *Cause:
// *Action:
01459, 00000, "invalid length for variable character string"
// *Cause:
// *Action:
01460, 00000, "unimplemented or unreasonable conversion requested"
// *Cause:
// *Action:
01461, 00000, "can bind a LONG value only for insert into a LONG column"
// *Cause:
// *Action:
01462, 00000, "cannot insert string literals longer than 4000 characters"
// *Cause:
// *Action:
01463, 00000, "cannot modify column datatype with current constraint(s)"
// *Cause: An attempt was made to modify the datatype of column which
// has referential constraints; or has check constraints which
// only allows changing the datatype from CHAR to VARCHAR or
// vise versa.
// *Action: Remove the constraint(s) or do not perform the offending operation.
01464, 00000, "circular grant (granting to grant ancestor) of table or view"
// *Cause:
// *Action:
01465, 00000, "invalid hex number"
// *Cause:
// *Action:
01466, 00000, "unable to read data - table definition has changed"
// *Cause: Query parsed after tbl (or index) change, and executed
// w/old snapshot
// *Action: commit (or rollback) transaction, and re-execute
01467, 00000, "sort key too long"
// *Cause:
// *Action:
01468, 00000, "a predicate may reference only one outer-joined table"
// *Cause:
// *Action:
01469, 00000, "PRIOR can only be followed by a column name"
// *Cause: Attempting to specify "PRIOR <something>" where <something> is not
// a column name.
// *Action: Only a column name can follow PRIOR. Replace with a column name.
01470, 00000, "In-list iteration does not support mixed operators"
// *Cause: Constants of different types are specified in an in-list.
// *Action: Use constants of same type for in-lists.
01471, 00000, "cannot create a synonym with same name as object"
// *Cause:
// *Action:
01472, 00000, "cannot use CONNECT BY on view with DISTINCT, GROUP BY, etc."
// *Cause:
// *Action:
01473, 00000, "cannot have subqueries in CONNECT BY clause"
// *Cause:
// *Action:
01474, 00000, "cannot have START WITH or PRIOR without CONNECT BY"
// *Cause:
// *Action:
01475, 00000, "must reparse cursor to change bind variable datatype"
// *Cause:
// *Action:
01476, 00000, "divisor is equal to zero"
// *Cause:
// *Action:
01477, 00000, "user data area descriptor is too large"
// *Cause:
// *Action:
01478, 00000, "array bind may not include any LONG columns"
// *Cause: User is performing an array bind with a bind variable whose
// maximum size is greater than 2000 bytes.
// *Action: Such bind variables cannot participate in array binds.
// Use an ordinary bind operation instead.
01479, 00000, "last character in the buffer is not Null"
// *Cause: A bind variable of type 97 does not contain null at the last
// position
// *Action: Make the last character null
01480, 00000, "trailing null missing from STR bind value"
// *Cause: A bind variable of type 5 (null-terminated string) does
// not contain the terminating null in its buffer.
// *Action: Terminate the string with a null character
01481, 00000, "invalid number format model"
// *Cause: The user is attempting to either convert a number to a string
// via TO_CHAR or a string to a number via TO_NUMBER and has
// supplied an invalid number format model parameter.
// *Action: Consult your manual.
01482, 00000, "unsupported character set"
// *Cause: The character set used to perform the operation, such as
// the CONVERT function, is not a supported character set.
// *Action: Use one of the supported character sets.
01483, 00000, "invalid length for DATE or NUMBER bind variable"
// *Cause: A bind variable of type DATE or NUMBER is too long.
// *Action: Consult your manual for the maximum allowable length.
01484, 00000, "arrays can only be bound to PL/SQL statements"
// *Cause: You tried to bind an array to a non-PL/SQL statement.
// *Action:
01485, 00000, "compile bind length different from execute bind length"
// *Cause: You bound a buffer of type DTYVCS (VARCHAR with the two byte
// length in front) and at execute time the length in the first two
// bytes is more than the maximum buffer length (given in the bind
// call). The number of elements in the array and the current number
// of elements in the array cannot be more than the maximum size of
// the array.
// *Action:
01486, 00000, "size of array element is too large"
// *Cause: You tried to bind a data value which was either too large for the
// datatype (for example, NUMBER) or was greater than 4000 bytes
// (for example, VARCHAR or LONG).
// *Action:
01487, 00000, "packed decimal number too large for supplied buffer"
// *Cause: An impossible request for decimal to oracle number conversion was
// made
// *Action: This conversion cannot be performed
01488, 00000, "invalid nibble or byte in the input data"
// *Cause: An impossible request for decimal to oracle number conversion was
// made
// *Action: This conversion cannot be performed
01489, 00000, "result of string concatenation is too long"
// *Cause: String concatenation result is more than the maximum size.
// *Action: Make sure that the result is less than the maximum size.
/
/ 1490 - 1499 Analyze Parse and Execution Errors
/
01490, 00000, "invalid ANALYZE command"
// *Cause: Incorrect syntax specified
// *Action: Retry the command
01491, 00000, "CASCADE option not valid"
// *Cause: The CASCADE option is only valid for tables or clusters.
// *Action: Do not specify CASCADE
01492, 00000, "LIST option not valid"
// *Cause: The LIST option is only valid for tables or clusters.
// *Action: Do not specify LIST
01493, 00000, "invalid SAMPLE size specified"
// *Cause: The specified SAMPLE size is out of range
// *Action: Specify a value within the proper range.
01494, 00000, "invalid SIZE specified"
// *Cause: The specified histogram SIZE value was out of range.
// *Action: Specify a value within the proper range.
01495, 00000, "specified chain row table not found"
// *Cause: The specified table either does not exist or user does not have
// the proper privleges.
// *Action: Specify the correct table to use.
01496, 00000, "specified chain row table form incorrect"
// *Cause: The specified table does not have the proper field definitions.
// *Action: Specify the correct table to use.
01497, 000000, "illegal option for ANALYZE CLUSTER"
// *Cause: The FOR COLUMNS <column-list> clause may not be used with
// ANALYZE CLUSTER.
// *Action: Retry with a legal syntax.
01498, 00000, "block check failure - see trace file"
// *Cause:
// *Action:
01499, 00000, "table/index cross reference failure - see trace file"
// *Cause:
// *Action:
/
/ Copyright (c) 2001, 2017, Oracle and/or its affiliates. All rights reserved.
/
/ NAME
/ e1500.msg
/ DESCRIPTION
/ Error messages for Oracle
/ NOTES
/ Language : American
/ Character set : US7ASCII
/
/ List of ORACLE errors
/
/ This file is converted to header/message files using lmsgen.c.
/
/ The first col is the ORACLE error number.
/ The second column is reserved and must (for now) be x00000.
/ The remainder of the line is the error text (max 76 characters).
/
/ Adding an error:
/ Check out this file, add the error, and check it back in.
/ Error numbers should always be ordered.
/ The second column should always be x00000.
/ Pseudo-error debugging events:
/ Error codes 10000 .. 10999 are reserved for debug event codes
/ that are not really errors.
/
/ MODIFIED
/ adalee 03/08/16 - Bug 22808010: update ORA-1916 for temp file
/ sumkumar 12/10/15 - Bug 22337415 : Update ORA-1999 for 12.2 format of
/ password file
/ adalee 09/29/15 - proj 62528 update ORA-1916
/ jarnett 08/11/15 - 21354456 - add additional explanation for 2049
/ wesmith 05/26/15 - Bug 21040212: add cause/action for ora-1753
/ ssonawan 02/19/15 - Proj 58069: updated 1997 error message
/ sumkumar 12/12/14 - Bug 20134352: for ORA-1931, add SoD privileges to
/ Cause and various restrictions to Action
/ nrcorcor 12/02/14 - Bug 13539672/Project 41272 New lost write protection
/ wesmith 11/24/14 - Project 47511: data-bound collation
/ hmohanku 11/05/14 - bug 4436441: Remove ORA-1925
/ xutian 10/21/14 - Bug 17888633: edit ORA-1516
/ sumkumar 10/14/14 - Bug 19815127 : Add identified globally to ora-1997
/ vperiwal 09/30/14 - bug 19669825: add cause and action for ora-1773
/ sksamudr 05/12/14 - bug 18479466
/ wwdai 02/04/14 - Bug 18178385: enhance ORA-1578 error mesg.
/ yiru 07/09/13 - Proj 47393: change ORA-1939 cause
/ youyang 09/18/12 - bug14543735:change ora-1924 action and cause
/ wxli 09/21/12 - add 1885: public synonym collides with user name
/ vpantele 09/19/12 - bug 14639434: fix ORA-1676 and 1677 message
/ jdavison 05/31/12 - Fix messages with incorrect action format
/ youyang 02/23/12 - change cause and action for ora-1720
/ shmubeen 01/03/12 - add cause and action for error number 1990
/ sbedarka 07/13/11 - #11732612: add details for ora-2015
/ mabhatta 04/20/09 - rename us.oracle.com to example.com
/ jjlee 03/03/09 - edit ORA-1516
/ ssonawan 11/17/08 - bug 7503761: edit 1931
/ ptearle 02/05/09 - add documentation for ORA-2014
/ kquinn 02/13/09 - 5687266: ensure ora-1722 is documented
/ yohu 11/20/08 - update 2051
/ nmacnaug 10/16/08 - change error message
/ madhanap 09/12/08 - bug 7387947: removing %s and %d from timezone region
/ errors
/ mabhatta 08/06/08 - edit 1554
/ yuli 05/28/08 - edit 1679
/ mbastawa 03/26/08 - add 01805
/ dapte 03/12/08 - add documentation for err-1795
/ dkoppar 03/11/08 - #(6835153) add err mesg for divide by zero
/ yohu 02/19/08 - change ORA-01640 to for in-doubt txn only
/ yohu 03/25/07 - more information for ORA-2051
/ mabhatta 11/30/06 - changing 1535 message to include rbs using _SYSSMU
/ prefix
/ akruglik 09/17/06 - modify Cause of msg 1752 to exclude read-only views
/ since an attempt to delete from a read-only view
/ will now be reported as msg 42399
/ akruglik 09/12/06 - replace EDITIONING VIEW with Editioning View
/ akruglik 09/01/06 - Column Map Views got rechristened as Editioning
/ Views
/ akruglik 05/10/06 - correct text of CAUSE for msg 1702 per request from
/ errors_us
/ akruglik 03/01/06 - Add a mention of use of a view in a definition of an
/ Editioning View among causes of msg 1702
/ yohu 11/28/05 - change 2079
/ bemeng 04/21/05 - explicitly specify unit of size for out-of-space msg
/ gmulagun 02/14/05 - bug 4177854 change 1999
/ nireland 02/24/05 - Explicitly specify unit of size. #4050567
/ qyu 11/15/04 - change 1874
/ mdilman 09/16/04 - change 1566 to more generic
/ nmanappa 05/13/04 - change message 1994 for password file
/ molagapp 04/25/04 - change 1537
/ rjenkins 07/08/03 - add a comment
/ lilin 12/16/02 - Eliminate Thread Number add/change error messages
/ jarnett 11/21/02 - bug 2634530 - delete reference to
/ distributed_transactions
/ ddas 10/16/02 - OPTIMIZER_GOAL parameter is obsolete
/ asundqui 09/05/02 - update error 1506 to only mention init.ora parameter
/ swerthei 09/20/02 - block change tracking
/ sdizdar 09/03/02 - reuse 1586
/ mjstewar 09/29/02 - Add flashback cause to ORA-1588
/ jmuller 08/08/02 - Bug 2462292: clarify ORA-2064 documentation
/ mjstewar 07/24/02 - Add Flashback action to ORA-1507
/ yuli 04/15/02 - remove 1576
/ snutakki 10/24/01 - 1970332: Add new error mesg 1560
/ mjaeger 07/05/01 - bug 479696: 01516: alter db datafile/tempfile <fno>
/-------------------------------------------------------------------------------
/ 1500 - 1699 V6 Execution errors
/
01500, 00000, "failure in getting date/time"
// *Cause: During create database or alter tablespace, there was a failure
// in getting the date and time.
// *Action: Contact your customer support representative.
01501, 00000, "CREATE DATABASE failed"
// *Cause: An error occurred during create database
// *Action: See accompanying errors.
01502, 00000, "index '%s.%s' or partition of such index is in unusable state"
// MERGE: 1489 RENUMBERED TO 1502
// *Cause: An attempt has been made to access an index or index partition
// that has been marked unusable by a direct load or by a DDL
// operation
// *Action: DROP the specified index, or REBUILD the specified index, or
// REBUILD the unusable index partition
01503, 00000, "CREATE CONTROLFILE failed"
// *Cause: An error occurred during CREATE CONTROLFILE
// *Action: See accompanying errors.
01504, 00000, "database name '%s' does not match parameter db_name '%s'"
// *Cause: The name in a database create or mount does not match the name
// given in the INIT.ORA parameter db_name.
// *Action: correct or omit one of the two names.
01505, 00000, "error in adding log files"
// *Cause: During create or alter database, error(s) occurred when
// adding new log files.
// *Action: Check error stack for detailed error information.
01506, 00000, "missing or illegal database name"
// *Cause: No db_name INIT.ORA aprameter was specified.
// *Action: The database name must be given in the db_name
// INIT.ORA parameter.
01507, 00000, "database not mounted"
// *Cause: A command was attempted that requires the database to be mounted.
// *Action: If you are using the ALTER DATABASE statement via the SQLDBA
// startup command, specify the MOUNT option to startup;
// else if you are directly doing an ALTER DATABASE DISMOUNT,
// do nothing; else specify the MOUNT option to ALTER DATABASE.
// If you are doing a backup or copy, you must first mount the
// desired database.
// If you are doing a FLASHBACK DATABASE, you must first mount
// the desired database.
01508, 00000, "cannot create database; error in file '%s' at line %s"
// *Cause: CREATE DATABASE was unable to process the specified file.
// *Action: Check the offending line in the specified file.
01509, 00000, "specified name '%s' does not match actual '%s'"
// *Cause: The database name specified in ALTER DATABASE does not
// match the name of the currently mounted database.
// *Action: Correct the database name spelling or DISMOUNT the mounted
// database.
01510, 00000, "error in deleting log files"
// *Cause: During ALTER DATABASE, an error occurred while dropping
// log files.
// *Action: Check the error stack for detailed error information.
01511, 00000, "error in renaming log/data files"
// *Cause: An error occurred during the ALTER DATABASE RENAME FILE command.
// *Action: Check the error stack for detailed error information.
01512, 00000, "error renaming log file %s - new file %s not found"
// *Cause: An attempt to change a log file's name in the control file
// failed because no file was found with the new name.
// *Action: Make sure that the log file has been properly renamed by the
// operating system and retry.
01513, 00000, "invalid current time returned by operating system"
// *Cause: The operating system returned a time that was not between
// 1988 and 2121.
// *Action: Correct the time kept by the operating system.
01514, 00000, "error in log specification: no such log"
// *Cause: A log file name, or list of member names, did not correspond
// to an existing log.
// *Action: Specify an existing log file.
01515, 00000, "error dropping log group %s: no such log"
// *Cause: ALTER DATABASE is attempting to drop a log file which
// is not known to the database control file.
// *Action: Specify the name of an existing log file.
01516, 00000, "nonexistent log file, data file, or temporary file \"%s\" in the current container"
// *Cause: An attempt was made to use ALTER DATABASE to rename
// a log file, data file, or temporary file; or to change attributes
// of a data file or temporary file (for example, resize, autoextend,
// online or offline); or to re-create or move a data file.
// The attempt failed because the specified file
// is not known to the database's control file
// or the current container or is not of a type
// supported by the request.
// *Action: Specify the name or number of an existing file
// of the correct type, as appropriate.
// Check the relevant V$ table for a list of possible files.
01517, 00000, "log member: '%s'"
// *Cause: Used to print member names
// *Action: See top level error for information
01518, 00000, "CREATE DATABASE must specify more than one log file"
// *Cause: Only one log file was specified in the CREATE DATABASE statement.
// *Action: Specify at least two log files.
01519, 00000, "error while processing file '%s' near line %s"
// *Cause: CREATE DATABASE encountered a problem while processing
// specified file. The specified file is bad.
// *Action: Retry your system installation procedure or contact
// your customer support representative.
01520, 00000, "number of data files to add (%s) exceeds limit of %s"
// *Cause: CREATE TABLESPACE statement specifies more files than
// is permitted for this database.
// *Action: Use fewer files or re-create the database with a
// larger value of MAXDATAFILES.
01521, 00000, "error in adding data files"
// *Cause: During CREATE or ALTER TABLESPACE, an error was detected
// while adding data files.
// *Action: Check the error stack for detailed error information.
01522, 00000, "file '%s' to be renamed does not exist"
// *Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not
// found in the database control file.
// *Action: Specify the correct file name.
01523, 00000, "cannot rename data file to '%s' - file already part of database"
// *Cause: During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME,
// the new name of a file is already present in the control file.
// *Action: Rename the file to a name not already being used as part of
// the database.
01524, 00000, "cannot create data file as '%s' - file already part of database"
// *Cause: During ALTER DATABASE CREATE DATAFILE,
// the new name of a file is already present in the control file.
// *Action: Create the file as a name not already being used as part of
// the database.
01525, 00000, "error in renaming data files"
// *Cause: An error occurred when renaming files as part of ALTER TABLESPACE.
// *Action: Check the error stack for detailed information.
// All files are renamed except for those mentioned in the
// error stack.
01526, 00000, "error in opening file '%s'"
// *Cause: CREATE DATABASE was not able to open the specified file.
// This is probably due to a system installation error.
// *Action: Retry your system installation procedure or contact
// your customer support representative.
01527, 00000, "error while reading file"
// *Cause: CREATE DATABASE was not able to read the specified file.
// This is probably due to a system installation error.
// *Action: Retry your system installation procedure or contact
// your customer support representative.
01528, 00000, "EOF while processing SQL statement"
// *Cause: CREATE DATABASE unexpectedly hit EOF while reading the
// specified file. The sql.bsq file is bad.
// *Action: Retry your system installation procedure or contact
// your customer support representative.
01529, 00000, "error closing file '%s'"
// *Cause: CREATE DATABASE was not able to close the specified file.
// *Action: Retry your system installation procedure or contact
// your customer support representative.
01530, 00000, "a database already mounted by the instance"
// *Cause: During ALTER DATABASE MOUNT, an attempt is being made to mount
// a database on an instance in which a database is or has previously
// been mounted.
// *Action: If you wish to mount the database, shutdown the instance
// and then startup the instance and retry the operation.
01531, 00000, "a database already open by the instance"
// *Cause: During ALTER DATABASE, an attempt was made to open
// a database on an instance for which there is already
// an open database.
// *Action: If you wish to open a new database on the instance, first
// shutdown the instance and then startup the instance and
// retry the operation.
01532, 00000, "cannot create database; instance being started elsewhere"
// *Cause: During CREATE DATABASE, another user appears to be
// simultaneously altering the instance.
// *Action: Make sure no one else is simultaneously altering the
// instance. If no one is, contact your customer support
// representative; otherwise, retry the operation.
01533, 00000, "cannot rename file '%s'; file does not belong to tablespace"
// *Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not
// found in the argument tablespace.
// *Action: Specify the correct file name or the correct tablespace name.
01534, 00000, "rollback segment '%s' doesn't exist"
// *Cause: During ALTER or DROP ROLLBACK SEGMENT, the specified
// rollback segment name is unknown.
// *Action: Use the correct rollback segment name.
01535, 00000, "rollback segment '%s' already exists or given name has prefix _SYSSMU"
// *Cause: Specified rollback segment already exists or given name starts with
// _SYSSMU.
// *Action: Use a different name. Note that _SYSSMU is an illegal prefix to
// an RBU segment.
01536, 00000, "space quota exceeded for tablespace '%s'"
// *Cause: The space quota for the segment owner in the tablespace has
// been exhausted and the operation attempted the creation of a
// new segment extent in the tablespace.
// *Action: Either drop unnecessary objects in the tablespace to reclaim
// space or have a privileged user increase the quota on this
// tablespace for the segment owner.
01537, 00000, "cannot add file '%s' - file already part of database"
// *Cause: During CREATE or ALTER TABLESPACE, a file being added is already
// part of the database.
// *Action: Use a different file name.
01538, 00000, "failed to acquire any rollback segment"
// *Cause: Failed to acquire any rollback segment during startup in shared mode
// *Action: Startup in exclusive mode to create one more public segment or
// specify available private segments in the INIT.ORA parameter
// rollback_segments_required, then startup in shared mode
01539, 00000, "tablespace '%s' is not online"
// *Cause: Failed to either make a tablespace read-only or offline because
// it is not online. A tblespace must be online before it can
// become read-only or offline normal.
// *Action: Check the status of the tablespace. Use IMMEDIATE or TEMPORARY
// options to force all files offline. Bring the tablespace online
// before making it read-only.
01540, 00000, "tablespace '%s' is not offline"
// *Cause: Failed to bring a tablespace online because it is not offline
// *Action: Check the status of the tablespace
01541, 00000, "system tablespace cannot be brought offline; shut down if necessary"
// *Cause: Tried to bring system tablespace offline
// *Action: Shutdown if necessary to do recovery
01542, 00000, "tablespace '%s' is offline, cannot allocate space in it"
// *Cause: Tried to allocate space in an offline tablespace
// *Action: Bring the tablespace online or create the object in other
// tablespace
01543, 00000, "tablespace '%s' already exists"
// *Cause: Tried to create a tablespace which already exists
// *Action: Use a different name for the new tablespace
01544, 00000, "cannot drop system rollback segment"
// *Cause: Tried to drop system rollback segment
// *Action: None
01545, 00000, "rollback segment '%s' specified not available"
// *Cause: Either:
// 1) An attempt was made to bring a rollback segment online that is
// unavailable during startup; for example, the rollback segment
// is in an offline tablespace.
// 2) An attempt was made to bring a rollback segment online that is
// already online. This is because the rollback segment is
// specified twice in the ROLLBACK_SEGMENTS parameter in the
// initialization parameter file or the rollback segment is already
// online by another instance.
// 3) An attempt was made to drop a rollback segment that is
// currently online.
// 4) An attempt was made to alter a rollback segment that is
// currently online to use unlimited extents.
// 5) An attempt was made to online a rollback segment that is
// corrupted. This is because the rollback is specified in
// _corrupted_rollback_segments parameter in initialization
// parameter file.
// *Action: Either:
// 1) Make the rollback segment available; for example, bring an
// offline tablespace online.
// 2) Remove the name from the ROLLBACK_SEGMENTS parameter if the name
// is a duplicate or if another instance has already acquired the
// rollback segment.
// 3) Bring the rollback segment offline first. This may involve
// waiting for the active transactions to finish, or, if the
// rollback segment needs recovery, discover which errors are
// holding up the rolling back of the transactions and take
// appropriate actions.
// 4) Same as 3).
// 5) Remove the name from the _corrupted_rollback_segments parameter.
01546, 00000, "tablespace contains active rollback segment '%s'"
// *Cause: Tried to make a tablespace that contains active rollback segment(s)
// offline or read-only
// *Action: Shutdown instances that use the active rollback segments in the
// tablespace and then make the tablespace offline or read-only
01547, 00000, "warning: RECOVER succeeded but OPEN RESETLOGS would get error below"
// *Cause: Media recovery with one of the incomplete recovery options ended
// without error. However, if the ALTER DATABASE OPEN RESETLOGS command
// were attempted now, it would fail with the specified error.
// The most likely cause of this error is forgetting to restore one or
// more datafiles from a sufficiently old backup before executing the
// incomplete recovery.
// *Action: Rerun the incomplete media recovery using different datafile
// backups, a different control file, or different stop criteria.
01548, 00000, "active rollback segment '%s' found, terminate dropping tablespace"
// *Cause: Tried to drop a tablespace that contains active rollback segment(s)
// *Action: Shutdown instances that use the active rollback segments in the
// tablespace and then drop the tablespace
01549, 00000, "tablespace not empty, use INCLUDING CONTENTS option"
// *Cause: Tried to drop a non-empty tablespace
// *Action: To drop all the objects in the tablespace, use the INCLUDING
// CONTENTS option
01550, 00000, "cannot drop system tablespace"
// *Cause: Tried to drop system tablespace
// *Action: None
01551, 00000, "extended rollback segment, pinned blocks released"
// *Cause: Doing recursive extent of rollback segment, trapped internally
// by the system
// *Action: None
01552, 00000, "cannot use system rollback segment for non-system tablespace '%s'"
// *Cause: Tried to use the system rollback segment for operations involving
// non-system tablespace. If this is a clone database then this will
// happen when attempting any data modification outside of the system
// tablespace. Only the system rollback segment can be online in a
// clone database.
// *Action: Create one or more private/public segment(s), shutdown and then
// startup again. May need to modify the INIT.ORA parameter
// rollback_segments to acquire private rollback segment. If this is
// a clone database being used for tablspace point in time recovery
// then this operation is not allowed. If the non-system tablespace
// has AUTO segment space management, then create an undo tablespace.
01553, 00000, "MAXEXTENTS must be no smaller than the %s extents currently allocated"
// *Cause: The number of extents allocated is greater than the MAXEXTENTS
// specified.
// *Action: Specify a larger MAXEXTENTS value.
01554, 00000, "transaction concurrency limit reached reason:%s params:%s, %s"
// *Cause: Too many concurrent transactions
// *Action: Shutdown the system, modify the INIT.ORA parameters transactions,
// rollback_segments or rollback_segments_required, then
// startup again.
01555, 00000, "snapshot too old: rollback segment number %s with name \"%s\" too small"
// *Cause: rollback records needed by a reader for consistent read are
// overwritten by other writers
// *Action: If in Automatic Undo Management mode, increase undo_retention
// setting. Otherwise, use larger rollback segments
01556, 00000, "MINEXTENTS for rollback segment must be greater than 1"
// *Cause: Specified MINEXTENTS of less than 2 for rollback segment
// *Action: Specify larger MINEXTENTS
01557, 00000, "rollback segment extents must be at least %s blocks"
// *Cause: Specified extent of less than minimum size for rollback segment
// *Action: Specify larger extents
01558, 00000, "out of transaction ID's in rollback segment %s"
// *Cause: All the available transaction id's have been used
// *Action: Shutdown the instance and restart using other rollback segment(s),
// then drop the rollback segment that has no more transaction id's.
01559, 00000, "MAXEXTENTS for rollback segment must be greater than 1"
// *Cause: Specified MAXEXTENTS of less than 2 for rollback segment
// *Action: Specify larger MAXEXTENTS
01560, 00000, "LIKE pattern contains partial or illegal character"
// *Cause: like pattern is not formed correctly
// *Action: make sure like pattern is specified correctly
01561, 00000, "failed to remove all objects in the tablespace specified"
// *Cause: Failed to remove all objects when dropping a tablespace
// *Action: Retry the drop tablespace until all objects are dropped
01562, 00000, "failed to extend rollback segment number %s"
// *Cause: Failure occurred when trying to extend rollback segment
// *Action: This is normally followed by another error message that caused
// the failure. You may take the rollback segment offline to perform
// maintainence. Use the alter rollback segment offline command
// to take the rollback segment offline.
01563, 00000, "rollback segment is PUBLIC, need to use the keyword PUBLIC"
// *Cause: Did not use the keyword PUBLIC to identified public rollback segment
// *Action: Use the keyword PUBLIC when identifying public rollback segment
01564, 00000, "rollback segment is not PUBLIC"
// *Cause: The rollback segment segment identified is not public
// *Action: Do not use the keyword PUBLIC when identifying private rollback
// segment
01565, 00000, "error in identifying file '%s'"
// *Cause: An error occurred while trying to identify a file.
// *Action: Check the error stack for detailed information.
01566, 00000, "file specified more than once in ALTER DATABASE"
// *Cause: The list of files supplied to the command contained at least one
// duplicate.
// *Action: Remove the duplicate file specification and retry.
01567, 00000, "dropping log %s would leave less than 2 log files for instance %s (thread %s)"
// *Cause: Dropping all the logs specified would leave fewer than the required
// two log files per enabled thread.
// *Action: Either drop fewer logs or disable the thread before deleting the
// logs. It may be possible to clear the log rather than drop it.
01568, 00000, "cannot set space quota on PUBLIC"
// MERGE: 1568 PROBABLY OBSOLETE
// *Cause: Trying to set space quota on a tablespace for PUBLIC.
// *Action: If trying to grant system-wide or tablespace-wide space priviledges
// to all users, use GRANT RESOURCE [ON <tablespace>] TO PUBLIC.
01569, 00000, "data file too small for system dictionary tables"
// *Cause: The datafile specified during creation of the database is too
// small to hold the system dictionary tables.
// *Action: Recreate the database by specifying a larger file or more files.
01570, 00000, "MINEXTENTS must be no larger than the %s extents currently allocated"
// *Cause: The number of extents allocated is smaller than the MINEXTENTS
// specified.
// *Action: Specify a smaller MINEXTENTS value.
01571, 00000, "redo version %s incompatible with ORACLE version %s"
// *Cause: This software version can not read the current redo logs, and
// either crash recovery is required or there are offline database
// files that need media recovery. If a file name is listed then
// it needs media recovery.
// *Action: Shutdown and startup using the compatible software. Do any required
// media recovery, and open the database. Shutdown and then startup
// using current software. If the file is going to be dropped then
// take it offline with the DROP option to skip this check.
01572, 00000, "rollback segment '%s' cannot be brought online, %s extents exceeded"
// *Cause: The number of extents in the rollback segment exceeds the hard limit.
// It cannot be brought online for writing.
// *Action: Drop and recreate the rollback segment.
01573, 00000, "shutting down instance, no further change allowed"
// *Cause: Some process tries to make changes while the db is being shutdown
// *Action: None
01574, 00000, "maximum number of concurrent transactions exceeded"
// *Cause: the limit on the number of concurrent transactions has been hit
// *Action: shutdown the system, increase the INIT.ORA parameter 'transactions'
// , and then restart the system.
01575, 00000, "timeout waiting for space management resource"
// *Cause: failed to acquire necessary resource to do space management.
// *Action: Retry the operation.
01576, 00000, "The instance %s is not enabled"
// *Cause: The thread associated with instance is not enabled.
// *Action: Enable the thread associated with the instance using
// ALTER DATABASE ENABLE INSTANCE command.
01577, 00000, "cannot add log file '%s' - file already part of database"
// *Cause: During CREATE or ALTER DATABASE, a file being added is already
// part of the database.
// *Action: Use a different file name.
01578, 00000, "ORACLE data block corrupted (file # %s, block # %s)"
// *Cause: The data block indicated was corrupt. This was a physical
// corruption, also called a media corruption. The cause is unknown
// but is most likely external to the database. If ORA-26040 is also
// signaled, the corruption is due to NOLOGGING or UNRECOVERABLE
// operations.
// *Action: The general method to repair a media corrupt block is to restore
// a backup and recover the backup. For databases in ARCHIVELOG
// mode, use block media recovery or media recovery. In some situations,
// you can also drop the segment and re-create it. For example, you can
// drop an index and re-create the index.
01579, 00000, "write error occurred during recovery"
// *Cause: A write error occurred during recovery
// *Action: Consult trace files for the nature of the write error, and
// correct error.
01580, 00000, "error creating control backup file %s"
// *Cause: An operating system error occurred while attempting to create a
// control file backup.
// *Action: Check the error stack for more detailed information
01581, 00000, "attempt to use rollback segment (%s) new extent (%s) which is being allocated"
// *Cause: Undo generated to extend a rollback segment run out of current
// undo block space and is attempting to write into the new extent
// which has not been completely allocated.
// *Action: The rollback segment extending will be rollbacked by the system,
// no more extension will be possible untill the next extent is
// freed up by rolling back or committing other transactions.
01582, 00000, "unable to open control file for backup"
// *Cause: An operating system error occurred while attempting to open a
// control file for backup.
// *Action: Check the error stack for more detailed information
01583, 00000, "unable to get block size of control file to be backed up"
// *Cause: An operating system error occurred while attempting to
// get the block size of a control file for backup.
// *Action: Check the error stack for more detailed information
01584, 00000, "unable to get file size of control file to be backed up"
// *Cause: An operating system error occurred while attempting to
// get the file size of a control file for backup.
// *Action: Check the error stack for more detailed information
01585, 00000, "error identifying backup file %s"
// *Cause: An operating system error occurred when attempting to identify
// the file to be used for control file backup.
// *Action: Check the error stack for more detailed information
01586, 00000, "database must be mounted EXCLUSIVE and not open for this operation"
// *Cause: Attempting to DROP DATABASE when the database is not mounted
// EXCLUSIVE.
// *Action: Mount the database in EXCLUSIVE mode.
01587, 00000, "error during control file backup file copy"
// *Cause:
//
// *Action:
01588, 00000, "must use RESETLOGS option for database open"
// *Cause: An earlier attempt to open the database with the RESETLOGS option
// did not complete, or recovery was done with a control file backup,
// or a FLASHBACK DATABASE was done.
// *Action: Use the RESETLOGS option when opening the database.
01589, 00000, "must use RESETLOGS or NORESETLOGS option for database open"
// *Cause: Either incomplete or backup control file recovery has been
// performed. After these types of recovery you must specify either
// the RESETLOGS option or the NORESETLOGS option to open your
// database.
// *Action: Specify the appropriate option.
01590, 00000, "number of segment free list (%s) exceeds maximum of %s"
// *Cause: storage parameter FREELIST GROUPS is too large.
// *Action: Reduce storage parameters FREELIST GROUPS
01591, 00000, "lock held by in-doubt distributed transaction %s"
// *Cause: Trying to access resource that is locked by a dead two-phase commit
// transaction that is in prepared state.
// *Action: DBA should query the pending_trans$ and related tables, and attempt
// to repair network connection(s) to coordinator and commit point.
// If timely repair is not possible, DBA should contact DBA at commit
// point if known or end user for correct outcome, or use heuristic
// default if given to issue a heuristic commit or abort command to
// finalize the local portion of the distributed transaction.
01592, 00000, "error converting Version 7 rollback segment (%s) to Oracle 8 format"
// *Cause: Look at the accompanying internal error; Version 7 database may not
// have shutdown cleanly.
// *Action: Investigate the internal error; may have to reload the Version 7
// *Action: Investigate the internal error; may have to reload the Version 7
// database (from backup) and shutdown the database cleanly.
01593, 00000, "rollback segment optimal size (%s blks) is smaller than the computed initial size (%s blks)"
// *Cause: Specified OPTIMAL size is smaller than the cumulative size of the
// initial extents during create rollback segment.
// *Action: Specify a larger OPTIMAL size.
01594, 00000, "attempt to wrap into rollback segment (%s) extent (%s) which is being freed"
// *Cause: Undo generated to free a rollback segment extent is attempting
// to write into the same extent due to small extents and/or too
// many extents to free
// *Action: The rollback segment shrinking will be rollbacked by the system;
// increase the optimal size of the rollback segment.
01595, 00000, "error freeing extent (%s) of rollback segment (%s))"
// *Cause: Some error occurred while freeing inactive rollback segment extents.
// *Action: Investigate the accompanying error.
01596, 00000, "cannot specify system in %s parameter"
// *Cause: The system rollback segment is specified in the INIT.ORA parameter
// referred to in the error message
// *Action: change the INIT.ORA parameter
01597, 00000, "cannot alter system rollback segment online or offline"
// *Cause: Tried to online or offline the system rollback segment
// *Action: None
01598, 00000, "rollback segment '%s' is not online"
// *Cause: Could have been taken offline before by DBA or cleaned up
// by SMON.
// *Action: Check the status of rollback segment in undo$ or dba_rollback_segs
// to make sure the rollback segment is actually online.
01599, 00000, "failed to acquire rollback segment (%s), cache space is full"
// *Cause: the amount statically allocated is not enough based on
// max_rollback_segments parameter.
// *Action: For now take another rollback segment offline or increase the
// parameter max_rollback_segments
01600, 00000, "at most one \"%s\" in clause \"%s\" of %s"
// *Cause: The INIT.ORA parameter was mis-specified.
// *Action: Correct the INIT.ORA parameter and restart the instance.
01601, 00000, "illegal bucket size in clause \"%s\" of %s"
// *Cause: The bucket size was invalid for this parameter.
// *Action: Correct the INIT.ORA parameter and restart the instance.
01603, 00000, "illegal grouping size in clause \"%s\" of %s"
// *Cause: The grouping size was invalid for this parameter.
// *Action: Correct the INIT.ORA parameter and restart the instance.
01604, 00000, "illegal number range in clause \"%s\" of %s"
// *Cause: The number range was invalid for this parameter.
// *Action: Correct the INIT.ORA parameter and restart the instance.
01605, 00000, "missing numbers in clause \"%s\" of %s"
// *Cause: The numbers were missing for this parameter.
// *Action: Correct the INIT.ORA parameter and restart the instance.
01606, 00000, "parameter not identical to that of another mounted instance"
// *Cause: A parameter was different on two instances.
// *Action: Modify the initialization parameter and restart.
01607, 00000, "cannot add logfile to the specified instance"
// *Cause: The limit on the number of instances supported by the
// control file has been reached.
// *Action: Use an instance name supported by the control file, or resize
// the thread record and/or checkpoint progress record secions of the
// control file.
01608, 00000, "cannot bring rollback segment '%s' online, its status is (%s)"
// *Cause: Could have been brought online before by DBA or left as a result
// of process crash.
// *Action: Check the status of rollback segment in undo$ or dba_rollback_segs
01609, 00000, "log %s is the current log for thread %s - cannot drop members"
// *Cause: A member of the current log for a thread cannot be dropped.
// *Action: If the thread is opened, request a log switch by the instance
// that is using it. If it is not open, disable the thread, manually
// archive the log, or clear it.
01610, 00000, "recovery using the BACKUP CONTROLFILE option must be done"
// *Cause: Either an earlier database recovery session specified BACKUP
// CONTROLFILE, or the control file was recreated with the RESETLOGS
// option, or the control file being used is a backup control file.
// After that only BACKUP CONTROLFILE recovery is allowed
// and it must be followed by a log reset at the next database open.
// *Action: Perform recovery using the BACKUP CONTROFILE option.
01611, 00000, "thread number %s is invalid - must be between 1 and %s"
// *Cause: A thread number in a command is greater than the number of threads
// supported by the control file.
// *Action: Use a thread number that is valid, or resize the thread record
// and/or checkpoint progress record sections of the control file.
01612, 00000, "instance %s (thread %s) is already enabled"
// *Cause: An attempt was made to enable a thread that is already enabled.
// *Action: Either use this thread or enable another thread.
01613, 00000, "instance %s (thread %s) only has %s logs - at least 2 logs required to enable."
// *Cause: The thread cannot be enabled because it only has two online log
// files associated with it.
// *Action: Add logs to the thread or pick another thread to enable
01614, 00000, "instance %s (thread %s) is busy - cannot enable"
// *Cause: The mount enqueue for the thread could not be acquired when
// attempting to enable the thread. This probably means that another
// process has already started enabling this thread.
// *Action: Wait and try again, or find another thread to enable.
01615, 00000, "instance %s (thread %s) is mounted - cannot disable"
// *Cause: Some instance, possibly this one, has allocated the thread for its
// use. The thread can not be disabled while in use.
// *Action: Shut the instance down cleany using the thread.
01616, 00000, "instance %s (thread %s) is open - cannot disable"
// *Cause: The thread is not closed. The last instance to use the thread died
// leaving the thread open. A thread cannot be disabled until it is
// closed. It is still required for crash or instance recovery.
// *Action: If the database is open, instance recovery should close the thread
// soon - wait a few minutes. Otherwise open the database - crash
// recovery will close the thread.
01617, 00000, "cannot mount: %s is not a valid thread number"
// *Cause: The INIT.ORA parameter "thread" is not between 1 and the
// number of threads allowed by the control file.
// *Action: Shut down the instance, change the INIT.ORA parameter and
// startup, or resize the thread record and/or checkpoint progress
// record sections of the control file.
01618, 00000, "redo thread %s is not enabled - cannot mount"
// *Cause: The INIT.ORA parameter "thread" requests a thread that is not
// enabled. A thread must be enabled before it can be mounted.
// *Action: Shutdown the instance, change the INIT.ORA parameter and startup
// mounting a different thread. If the database is open in another
// instance then the thread may be enabled.
01619, 00000, "thread %s is mounted by another instance"
// *Cause: The INIT.ORA parameter "thread" requests a thread that has been
// mounted by another instance. Only one instance may use a thread.
// *Action: Shutdown the instance, change the INIT.ORA parameter and startup
// mounting a different thread.
01620, 00000, "no public threads are available for mounting"
// *Cause: The INIT.ORA parameter "thread" is zero, its default value.
// There are no threads which have been publicly enabled, and not
// mounted.
// *Action: Shutdown the instance, change the INIT.ORA parameter to a thread
// which is privately enabled and not mounted. If the database is
// open in another instance, then a thread may be publicly enabled.
01621, 00000, "cannot rename member of current log if database is open"
// *Cause: This is a rename command for a member of the current log for
// an open thread. If the database is open anywhere, the log may be
// in use, so the rename cannot be done.
// *Action: Wait until the log is not current, or mount the database
// exclusively.
01622, 00000, "thread number must be specified - default not specific"
// *Cause: The thread was not specified when adding a log, and the currently
// mounted thread was chosen by default at mount time. Since the
// current thread was not specified explicitly the user cannot know
// which thread the log will be added to.
// *Action: Explicitly specify the thread number either in the INIT.ORA
// parameter "thread", or in the add command.
01623, 00000, "log %s is current log for instance %s (thread %s) - cannot drop"
// *Cause: A thread's current log cannot be dropped even if the thread is
// closed. A disabled thread usually does not have a current log,
// but a half completed disable may need to be disabled again.
// *Action: If the database is not open then disable the thread. If the
// database is open and an instance has the thread open, then the
// instance can be requested to switch logs. If the database is
// closed the log can be archived or cleared to force a switch.
01624, 00000, "log %s needed for crash recovery of instance %s (thread %s)"
// *Cause: A log cannot be dropped or cleared until the thread's checkpoint
// has advanced out of the log.
// *Action: If the database is not open, then open it. Crash recovery will
// advance the checkpoint. If the database is open force a global
// checkpoint. If the log is corrupted so that the database cannot
// be opened, it may be necessary to do incomplete recovery until
// cancel at this log.
01625, 00000, "rollback segment '%s' does not belong to this instance"
// *Cause: Trying to shrink or take a rollback segment offline that does not
// belong to this instance.
// *Action:
01626, 00000, "rollback segment number '%s' cannot handle more transactions"
// *Cause: Too many transactions in this segment.
// *Action: Choose a different rollback segment, or reduce the number
// of concurrent transactions.
01627, 00000, "rollback segment number '%s' is not online"
// *Cause: Could have been taken offline before by DBA or cleaned up
// by SMON.
// *Action: Check the status of rollback segment in undo$ or dba_rollback_segs
// to make sure the rollback segment is actually online.
01628, 00000, "max # extents (%s) reached for rollback segment %s"
// *Cause: An attempt was made to extend a rollback segment that was
// already at the MAXEXTENTS value.
// *Action: If the value of the MAXEXTENTS storage parameter is less than
// the maximum allowed by the system, raise this value.
01629, 00000, "max # extents (%s) reached saving undo for tablespace %s"
// *Cause: Save undo for the offline tablespace at max extents
// *Action: Check the storage parameters for the system tablespace. The
// tablespace needs to be brought back online so the undo can be
// applied .
01630, 00000, "max # extents (%s) reached in temp segment in tablespace %s"
// *Cause: A temp segment tried to extend past max extents.
// *Action: If maxextents for the tablespace is less than the the system
// maximum, you can raise that. Otherwise, raise pctincrease for the
// tablespace
01631, 00000, "max # extents (%s) reached in table %s.%s"
// *Cause: A table tried to extend past maxextents
// *Action: If maxextents is less than the system maximum, raise it. Otherwise,
// you must recreate with larger initial, next or pctincrease params
01632, 00000, "max # extents (%s) reached in index %s.%s"
// *Cause: An index tried to extend past maxextents
// *Action: If maxextents is less than the system max, raise it. Otherwise,
// you must recreate with larger initial, next or pctincrease params.
01633, 00000, "Real Application Clusters Option needed for this operation"
// *Cause: System doesn't have Real Application Clusters configured
// *Action: Obtain Real Application Clusters option
01634, 00000, "rollback segment number '%s' is about to go offline"
// *Cause: The rollback segment specified was marked to go offline by DBA.
// *Action: Bring the rollback segment online first.
01635, 00000, "rollback segment #%s specified not available"
// *Cause: (same as 1545)
// *Action: (same as 1545)
01636, 00000, "rollback segment '%s' is already online"
// *Cause: The instance is trying to online an already online RS
// *Action:
01637, 00000, "rollback segment '%s' is being used by another instance (#%s)"
// *Cause: The instance is trying to online a RS already in use by another
// instance
// *Action:
01638, 00000, "parameter %s does not allow ORACLE version %s to mount cluster database"
// *Cause: The recovery compatible parameter is set too low to allow this
// software version to mount in cluster database mode.
// *Action:Either use an earlier software release or advance the
// recovery_compatible parameter. If this happens when no
// recovery_compatible parameter has been specified then set it
// to the current software release.
01639, 00000, " instance %s has no thread assigned to it"
// *Cause: There is no mapping from instance to thread for this instance in
// the control file.
// *Action:Make sure that this instance has a thread assigned to it by adding
// logfiles to this instance or by starting the instance with an
// existing thread which will automatically create a mapping.
01640, 00000, "cannot make tablespace read-only with changes by in-doubt transactions"
// *Cause: An attempt was made to alter a tablespace read-only while there were
// changes in the tablespace made by in-doubt distributed transactions.
// The in-doubt transactions must commit or rollback to ensure that
// there is no undo for a tablespace before it can be made read-only.
// *Action: Any in-doubt transactions that made changes to the tablespace must
// be resolved.
01641, 00000, "tablespace '%s' is not online - cannot add data file"
// *Cause: Attempting to add a datafile to a tablespace that has been set
// to read-only or offline.
// *Action: Make the tablespace online and read write then add the datafile.
01642, 00000, "begin backup not needed for read-only tablespace '%s'"
// *Cause: Attempting to begin or end a backup for a tablespace that has
// been set to read-only.
// *Action: Take the backup without any begin or end commands. The files
// are not being modified so the backup will be consistent.
01643, 00000, "system tablespace can not be made read-only"
// *Cause: Attempting to set the system tablespace to read-only. The system
// tablespace must remain read write for database operation.
// *Action: Leave system tablespace read write.
01644, 00000, "tablespace '%s' is already read-only"
// *Cause: Attempting to make tablespace read-only that is already read-only.
// *Action: Leave tablespace read-only, or make read write then make
// read-only again.
01645, 00000, "previous attempt to make read write is half complete"
// *Cause: A failure while making the tablespace read write left it read
// only, but the checkpoint was advanced. The tablespace will not
// be useable after a resetlogs if its files are offline.
// *Action: Repeat the command to make the tablespace read write.
01646, 00000, "tablespace '%s' is not read-only - cannot make read write"
// *Cause: Attempting to make a tablespace read write that is not read-only.
// It may be either online or offline.
// *Action: Leave tablespace read write.
01647, 00000, "tablespace '%s' is read-only, cannot allocate space in it"
// *Cause: Tried to allocate space in a read-only tablespace
// *Action: Create the object in another tablespace
01648, 00000, "log %s is the current log of disabled instance %s (thread %s)"
// *Cause: An attempt to enable the thread failed after it was half completed.
// This log was left as the current log even though the thread is still
// disabled. Since a log switch cannot be done until the thread is
// enabled, the log can not be cleared or archived.
// *Action:Complete the thread enable by issuing the enable command again.
01649, 00000, "operation not allowed with a backup control file"
// *Cause: An attempt is being made to perform a command that does not make
// sense when the control file is a restored backup.
// *Action:Wait until after the database has been opened and try again.
01650, 00000, "unable to extend rollback segment %s by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// a rollback segment in the tablespace.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
01651, 00000, "unable to extend save undo segment by %s for tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// saving undo entries for the indicated offline tablespace.
// *Action: Check the storage parameters for the SYSTEM tablespace. The
// tablespace needs to be brought back online so the undo can be
// applied.
01652, 00000, "unable to extend temp segment by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// a temporary segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
01653, 00000, "unable to extend table %s.%s by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// a table segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
01654, 00000, "unable to extend index %s.%s by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// an index segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
01655, 00000, "unable to extend cluster %s.%s by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// a cluster segment in tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
01656, 00000, "max # extents (%s) reached in cluster %s.%s"
// *Cause: A cluster tried to extend past maxextents
// *Action: If maxextents is less than the system maximum, raise it. Otherwise,
// you must recreate with larger initial, next or pctincrease params
01657, 00000, "invalid SHRINK option value"
// *Cause: The specified value must be an integer.
// *Action: Choose an appropriate integer value.
01658, 00000, "unable to create INITIAL extent for segment in tablespace %s"
// *Cause: Failed to find sufficient contiguous space to allocate INITIAL
// extent for segment being created.
// *Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the
// tablespace or retry with a smaller value for INITIAL
01659, 00000, "unable to allocate MINEXTENTS beyond %s in tablespace %s"
// *Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS
// for the segment being created.
// *Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the
// tablespace or retry with smaller value for MINEXTENTS, NEXT or
// PCTINCREASE
01660, 00000, "tablespace '%s' is already permanent"
// *Cause: Attempting to make tablespace permanent that is already permanent.
// *Action: Leave tablespace permanent.
01661, 00000, "tablespace '%s' is already temporary"
// *Cause: Attempting to make tablespace temporary that is already temporary.
// *Action: Leave tablespace permanent.
01662, 00000, "tablespace '%s' is non-empty and cannot be made temporary"
// *Cause: Tried to convert a non-empty tablespace to a temporary tablespace
// *Action: To drop all the objects in the tablespace.
01663, 00000, "the contents of tablespace '%s' is constantly changing"
// *Cause: The contents of the tablespace is always changing between PERMANENT
// and TEMPORARY.
// *Action: To decide what the tablespace contents should be and stay with it.
01664, 00000, "Transaction which has expanded the Sort Segment has aborted"
// *Cause: Internal Error.
// *Action: Contact Oracle Support.
01665, 00000, "control file is not a standby control file"
// *Cause: Attempting to mount, recover or activate a standby database
// without a standby control file.
// *Action: Create a standby control file before attempting to use the database
// as a standby database.
01666, 00000, "control file is for a standby database"
// *Cause: Attempting to mount, recover, or open a standby database without
// the appropriate command option to designate a standby database.
// *Action: Use the standby option or appropriate commands, or mount with
// the primary control file.
01667, 00000, "cannot add any more tablespaces: limit of %s exceeded"
// *Cause: There is no more room in the control file for adding tablespaces.
// *Action: Resize the control file or drop other tablespaces.
01668, 00000, "standby database requires DROP option for offline of data file"
// *Cause: Attempting to take a datafile offline in a standby database without
// specifying the DROP option. Files that are offline in a standby
// database are not recovered, and are likely to be unusable if
// the standby is activated. Note that specifying DROP does not
// prevent bringing the file online later.
// *Action: Specify the DROP option or leave the file online.
01669, 00000, "standby database control file not consistent"
// *Cause: Attempting to activate a standby database with a control file that
// has not been recovered to the same point as the data files. Most
// likely the control file was just copied from the primary database
// and has not been used for recovery.
// *Action: Recover the standby database until all the files are consistent.
01670, 00000, "new datafile %s needed for standby database recovery"
// *Cause: Standby database recovery noticed that a file was added to the
// primary database, but is not available on the standby.
// *Action: Either copy the file from the primary database or do an ALTER
// DATABASE CREATE DATAFILE command on the standby to create a
// file to recover.
01671, 00000, "control file is a backup, cannot make a standby control file"
// *Cause: The currently mounted control file is a backup control file, and
// attempting to create a control file for a standby database.
// *Action: Complete any needed recovery and open the database with the
// resetlogs option.
01672, 00000, "control file may be missing files or have extra ones"
// *Cause: Attempting to create a standby control file, but the control file
// was either recently created via CREATE CONTROLFILE or an incomplete
// recovery has been done. Thus the datafiles in the control file
// and the ones in the data dictionary may not match.
// *Action: Open the database, then retry the operation.
01673, 00000, "data file %s has not been identified"
// *Cause: This data file was not in the control file after an incomplete
// recovery or CREATE CONTROLFILE. Since information from its
// header is needed for standby database recovery, we can not
// create a standby control file.
// *Action: Find the file and bring it online. If desired it may be taken
// offline again. If you intend to drop this file, then taking it
// offline with the DROP option will avoid this error.
01674, 00000, "data file %s is an old incarnation rather than current file"
// *Cause: Recovery encountered redo that indicates this file was dropped
// from the database and another file was added using the same file
// number. This implies that a CREATE CONTROLFILE command was given
// the old file which was dropped rather than the latest file.
// *Action: Rebuild the control file using CREATE CONTROLFILE, and give the
// correct file.
01675, 00000, "max_commit_propagation_delay inconsistent with other instances"
// *Cause: The max_commit_propagation_delay INIT.ORA parameter is
// inconsistent with those in other instances.
// *Action: Make sure all instances have the same max_commit_propagation_delay.
01676, 00000, "standby file name conversion of '%s' exceeds maximum length of %s"
// *Cause: When the given file name was converted to the name used for the
// standby database, the converted name was bigger than the maximum
// allowed file name.
// *Action: Change initialization parameter DB_FILE_NAME_CONVERT or
// LOG_FILE_NAME_CONVERT to convert to a valid file name.
01677, 00000, "standby file name conversion parameters differ from other instance"
// *Cause: The DB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT
// initialization parameters were not the same as in other instances
// that already had the database mounted.
// *Action: Change initialization parameters DB_FILE_NAME_CONVERT or
// LOG_FILE_NAME_CONVERT to match other instances.
01678, 00000, "parameter %s must be pairs of pattern and replacement strings"
// *Cause: The initialization parameter does not have even number of strings
// for its value. The odd numbered strings are patterns to be found in
// file names. The even numbered strings are used to replace the
// corresponding patterns when found in file names.
// *Action:Specify even number of strings for the parameter, or omit the
// parameter.
01679, 00000, "database is being opened"
// *Cause: An attempt was made to activate a standby database when the
// database was in the middle of being opened.
// *Action: Wait for database open to finish and retry the ACTIVATE command.
01680, 00000, "unable to extend LOB segment by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// a LOB segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
01681, 00000, "max # extents (%s) reached in LOB segment in tablespace %s"
// *Cause: A LOB segment tried to extend past max extents.
// *Action: If maxextents for the tablespace is less than the the system
// maximum, you can raise that. Otherwise, raise pctincrease for the
// tablespace
01682, 00000, "read-only DB cannot allocate temporary space in tablespace %s"
// *Cause: Temporary space (usually for sorting) could not be allocated in
// either main storage or a tempfile. An attempt was made to
// allocate the space from the tablespace named, but the database is
// opened read-only. The database open requires a sort work space.
// *Action: Either allow sufficient workspace in main storage (SORT_AREA_SIZE
// initialization parameter), or create a temporary tablespace before
// making the database read-only. Use ALTER TABLESPACE ADD TEMPFILE
// statement to add temporary files to the temporary tablespace.
01683, 00000, "unable to extend index %s.%s partition %s by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// index segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
01684, 00000, "max # extents (%s) reached in table %s.%s partition %s"
// *Cause: A table tried to extend past maxextents
// *Action: If maxextents is less than the system maximum, raise it. Otherwise,
// you must recreate with larger initial, next or pctincrease params
01685, 00000, "max # extents (%s) reached in index %s.%s partition %s"
// *Cause: An index tried to extend past maxextents
// *Action: If maxextents is less than the system max, raise it. Otherwise,
// you must recreate with larger initial, next or pctincrease params.
01686, 00000, "max # files (%s) reached for the tablespace %s"
// *Cause: The number of files for a given tablespace has reached its maximum
// value
// *Action: Resize existing files in the tablespace, or partition the objects
// among multiple tablespaces, or move some objects to a different
// tablespace.
01687, 00000, "specified logging attribute for tablespace '%s' is same as the existing"
// *Cause: Attempting to change the tablespace default logging attribute
// (LOGGING or NOLOGGING) to be the same as the existing logging
// attribute
// *Action: Change the specified logging attribute
01688, 00000, "unable to extend table %s.%s partition %s by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// table segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
01689, 00000, "syntax error in clause \"%s\" of %s"
// *Cause: There was a syntax in the INIT.ORA parameter.
// *Action: Fix the syntax error and restart the instance.
01690, 00000, "sort area size too small"
// *Cause: sort area size too small to fit two records in memory
// *Action: increase sort_area_size
01691, 00000, "unable to extend lob segment %s.%s by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// LOB segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
01692, 00000, "unable to extend lob segment %s.%s partition %s by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// LOB segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
01693, 00000, "max # extents (%s) reached in lob segment %s.%s"
// *Cause: A LOB segment tried to extend past maxextents
// *Action: If maxextents is less than the system max, raise it. Otherwise,
// you must recreate with larger initial, next or pctincrease params.
01694, 00000, "max # extents (%s) reached in lob segment %s.%s partition %s"
// *Cause: A LOB segment tried to extend past maxextents
// *Action: If maxextents is less than the system max, raise it. Otherwise,
// you must recreate with larger initial, next or pctincrease params.
01695, 00000, "error converting rollback segment %s to version 8.0.2"
// *Cause: Version 8.0.1 database may not have shutdown cleanly
// *Action: May have to reload the 8.0.1 database and shutdown cleanly
01696, 00000, "control file is not a clone control file"
// *Cause: Attempting to mount, a database as a clone when it is already
// mounted by another instance not as a clone or attempting to use
// a current control file for a clone.
// *Action: Mount without the clone option or use a backup control file and
// shutdown the other instances before mounting as a clone.
01697, 00000, "control file is for a clone database"
// *Cause: Attempting to mount a clone database without the appropriate
// command option to designate a clone database.
// *Action: Use the clone option or appropriate commands, or mount with
// the primary control file.
01698, 00000, "a clone database may only have SYSTEM rollback segment online"
// *Cause: Attempting to online a rollback segment in a clone database.
// *Action: Do not use this command.
01699, 00000, "tablespace '%s' is being imported for point in time recovery"
// *Cause: Attempting to online a tablespace or begin another point in
// time import while a point in time import is already in progress
// *Action: Wait until the import complets
//
/
/ 1700 - 1799 Parse errors continued from 900 - 999
/
01700, 00000, "duplicate username in list"
// *Cause:
// *Action:
01701, 00000, "a cluster is not appropriate here"
// *Cause:
// *Action:
01702, 00000, "a view is not appropriate here"
// *Cause: Among other possible causes, this message will be produced if an
// attempt was made to define an Editioning View over a view.
// *Action: An Editioning View may only be created over a base table.
01703, 00000, "missing SYNONYM keyword"
// *Cause:
// *Action:
01704, 00000, "string literal too long"
// *Cause: The string literal is longer than 4000 characters.
// *Action: Use a string literal of at most 4000 characters.
// Longer values may only be entered using bind variables.
01705, 00000, "an outer join cannot be specified on a correlation column"
// *Cause:
// *Action:
01706, 00000, "user function result value was too large"
// *Cause:
// *Action:
01707, 00000, "missing LIST keyword"
// *Cause:
// *Action:
01708, 00000, "ACCESS or SESSION expected"
// *Cause:
// *Action:
01709, 00000, "program does not exist"
// *Cause:
// *Action:
01710, 00000, "missing OF keyword"
// *Cause:
// *Action:
01711, 00000, "duplicate privilege listed"
// *Cause:
// *Action:
01712, 00000, "you cannot grant a privilege which you do not have"
// *Cause:
// *Action:
01713, 00000, "GRANT OPTION does not exist for that privilege"
// *Cause:
// *Action:
01714, 00000, "error in execution of user function"
// *Cause:
// *Action:
01715, 00000, "UNIQUE may not be used with a cluster index"
// *Cause: An attempt was made to create a cluster index with the
// UNIQUE attribute.
// *Action: Remove UNIQUE from the CREATE INDEX statement.
01716, 00000, "NOSORT may not be used with a cluster index"
// *Cause: An attempt was made to create a cluster index using
// the NOSORT option.
// *Action: Remove NOSORT from the CREATE INDEX statement.
01717, 00000, "seccta: invalid access mode token passed"
// *Cause:
// *Action:
01718, 00000, "BY ACCESS | SESSION clause not allowed for NOAUDIT"
// *Cause: Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement.
// *Action: Remove BY ACCESS | SESSION.
01719, 00000, "outer join operator (+) not allowed in operand of OR or IN"
// *Cause: An outer join appears in an or clause.
// *Action: If A and B are predicates, to get the effect of (A(+) or B),
// try (select where (A(+) and not B)) union all (select where (B)).
01720, 00000, "grant option does not exist for '%s.%s'"
// *Cause: A grant was being performed on a view or a view was being replaced
// and the grant option was not present for an underlying object.
// *Action: Obtain the grant option on all underlying objects of the view or
// revoke existing grants on the view.
01721, 00000, "USERENV(COMMITSCN) invoked more than once in a transaction"
// *Cause: The USERENV('COMMITSCN') function can only be used once in a
// transaction.
// *Action: Re-write the transactioin to use USERENV('COMMITSCN') only once
01722, 00000, "invalid number"
// *Cause: The specified number was invalid.
// *Action: Specify a valid number.
01723, 00000, "zero-length columns are not allowed"
// *Cause: Columns with zero length were not allowed.
// *Action: Correct the use of the column.
01724, 00000, "floating point precision is out of range (1 to 126)"
// *Cause: The specified number had an invalid range.
// *Action: Use a floating point precision that is in the correct precision.
01725, 00000, "USERENV('COMMITSCN') not allowed here"
// *Cause: The function USERENV('COMMITSCN') is only allowed as a top-level
// expression in the VALUES clause of an INSERT statement, and on
// the right-hand side of an assignment in an UPDATE statement.
// *Action: Correct the use of the function.
01726, 00000, "a table is not appropriate here"
// *Cause:
// *Action:
01727, 00000, "numeric precision specifier is out of range (1 to 38)"
// *Cause:
// *Action:
01728, 00000, "numeric scale specifier is out of range (-84 to 127)"
// *Cause:
// *Action:
01729, 00000, "database link name expected"
// *Cause:
// *Action:
01730, 00000, "invalid number of column names specified"
// *Cause:
// *Action:
01731, 00000, "circular view definition encountered"
// *Cause:
// *Action:
01732, 00000, "data manipulation operation not legal on this view"
// *Cause:
// *Action:
01733, 00000, "virtual column not allowed here"
// *Cause:
// *Action:
01734, 00000, "illegal parameters - EXTENT MIN higher than EXTENT MAX"
// *Cause: A wrong value is specified for the parameter.
// *Action: Correct the parameter and reissue the statement.
01735, 00000, "invalid ALTER TABLE option"
// *Cause:
// *Action:
01736, 00000, "[NOT] SUCCESSFUL expected"
// *Cause:
// *Action:
01737, 00000, "valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE"
// *Cause:
// *Action: Valid lock modes are SHARE, ROW SHARE, EXCLUSIVE, ROW EXCLUSIVE,
// SHARE ROW EXCLUSIVE, and SHARE UPDATE.
01738, 00000, "missing IN keyword"
// *Cause:
// *Action:
01739, 00000, "missing MODE keyword"
// *Cause:
// *Action:
01740, 00000, "missing double quote in identifier"
// *Cause:
// *Action:
01741, 00000, "illegal zero-length identifier"
// *Cause:
// *Action:
01742, 00000, "comment not terminated properly"
// *Cause: The indicated comment or hint begun with the /* token did not
// have the terminating */.
// *Action: Properly terminate the comment or hint with a */.
01743, 00000, "only pure functions can be indexed"
// *Cause: The indexed function uses SYSDATE or the user environment.
// *Action: PL/SQL functions must be pure (RNDS, RNPS, WNDS, WNPS). SQL
// expressions must not use SYSDATE, USER, USERENV(), or anything
// else dependent on the session state. NLS-dependent functions
// are OK.
01744, 00000, "inappropriate INTO"
// *Cause:
// *Action:
01745, 00000, "invalid host/bind variable name"
// *Cause:
// *Action:
01746, 00000, "indicator variable not permitted here"
// *Cause:
// *Action:
01747, 00000, "invalid user.table.column, table.column, or column specification"
// *Cause:
// *Action:
01748, 00000, "only simple column names allowed here"
// *Cause:
// *Action:
01749, 00000, "you may not GRANT/REVOKE privileges to/from yourself"
// *Cause:
// *Action:
01750, 00000, "UPDATE/REFERENCES may only be REVOKEd from the whole table, not by column"
// *Cause:
// *Action:
01751, 00000, "Invalid dump undo option"
// *Cause: An invalid option is specified in the ALTER DUMP UNDO command.
// *Action: Correct and reissue the command.
01752, 00000, "cannot delete from view without exactly one key-preserved table"
// *Cause: The deleted table had
// - no key-preserved tables,
// - more than one key-preserved table, or
// - the key-preserved table was an unmerged view.
// *Action: Redefine the view or delete it from the underlying base tables.
01753, 00000, "column definition incompatible with clustered column definition"
// *Cause: An attempt was made to create a table in a cluster and one of the
// table's clustered columns is not compatible with the corresponding
// cluster key column.
// *Action: Make sure that all table columns specified in the CLUSTER clause of
// the CREATE TABLE statement are compatible with the corresponding
// columns of the cluster key, as documented. For example, the
// data type and the declared collation of a clustered table column
// must be the same as those of the corresponding cluster key column.
01754, 00000, "a table may contain only one column of type LONG"
// *Cause: An attempt was made to add a LONG column to a table which already
// had a LONG column. Note that even if the LONG column currently
// in the table has already been marked unused, another LONG column
// may not be added until the unused columns are dropped.
// *Action: Remove the LONG column currently in the table by using the ALTER
// TABLE command.
01755, 00000, "Must specify an extent number or block number"
// *Cause: Expecting an extent or block number but something else was
// specified.
// *Action: Correct the error and reissue the command.
01756, 00000, "quoted string not properly terminated"
// *Cause:
// *Action:
01757, 00000, "Must specify an object number"
// *Cause: Expecting an object number but something else was specified.
// *Action: Correct the error and reissue the command.
01758, 00000, "table must be empty to add mandatory (NOT NULL) column"
// *Cause:
// *Action:
01759, 00000, "user function is incorrectly defined"
// *Cause:
// *Action:
01760, 00000, "illegal argument for function"
// *Cause:
// *Action:
01761, 00000, "DML operation does not map to a unique table in the join"
// *Cause: The primary table is the base table against which the update,
// insert or delete operation is finally being done. For delete
// either there is no primary table in the join query or there is
// more than one. For update or insert the columns specified map
// to more than one base table.
// *Action: Change the join specification.
01762, 00000, "vopdrv: view query block not in FROM"
// *Cause:
// *Action:
01763, 00000, "update or delete involves outer joined table"
// *Cause: For deletes, the table being deleted from is outer joined to some
// other table. For updates, either the table being updated is outer-
// joined to some other table, or some table reachable from the primary
// table is being outer joined to a table not reachable from the
// primary table.
// *Action: Change the join specification.
01764, 00000, "new update value of join is not guaranteed to be unique"
// *Cause: A row of a join query table is being updated using a row of a
// table that is not guaranteed to have exactly one value for the
// row being updated.
// *Action: Change the join specification.
01765, 00000, "specifying owner's name of the table is not allowed"
// *Cause: An attempt was made to rename the object with dotted object name.
// *Action: Do not specify username.tablename in query for table name.
01766, 00000, "dictionary table not allowed in this context"
// *Cause:
// *Action:
01767, 00000, "UPDATE ... SET expression must be a subquery"
// *Cause:
// *Action:
01768, 00000, "number string too long"
// *Cause:
// *Action:
01769, 00000, "duplicate CLUSTER option specifications"
// *Cause: During a CREATE of a clustered table, the user attempted to specify
// more than one CLUSTER option.
// *Action: Remove the extra CLUSTER option.
01770, 00000, "CLUSTER option not allowed in CREATE CLUSTER command"
// *Cause:
// *Action:
01771, 00000, "illegal option for a clustered table"
// *Cause: During a CREATE or ALTER of a clustered table, the user attempted
// to enter one or more of the following options:
// INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE.
// These options may only be specified for the cluster itself.
// *Action: Remove the illegal option(s).
01772, 00000, "Must specify a value for LEVEL"
// *Cause: Expecting the value of LEVEL but something else was specified.
// *Action: Correct the error and reissue the command.
01773, 00000, "may not specify column datatypes in this CREATE TABLE"
// *Cause: Column data types or virtual columns were specified in a SELECT
// statement used to create and load a table directly.
// *Action: Remove the column data types and virtual columns.
// The data types of the SELECT list expressions are automatically
// used as the column data types.
01774, 00000, "Dump undo option specified more than once"
// *Cause: The same option for ALTER DUMP UNDO was specified twice.
// *Action: Remove the redundant options and reissue the command.
01775, 00000, "looping chain of synonyms"
// *Cause:
// *Action:
01776, 00000, "cannot modify more than one base table through a join view"
// *Cause: Columns belonging to more than one underlying table were either
// inserted into or updated.
// *Action: Phrase the statement as two or more separate statements.
01777, 00000, "WITH GRANT OPTION not allowed in this system"
// *Cause:
// *Action:
01778, 00000, "maximum subquery nesting level exceeded"
// *Cause:
// *Action:
01779, 00000, "cannot modify a column which maps to a non key-preserved table"
// *Cause: An attempt was made to insert or update columns of a join view which
// map to a non-key-preserved table.
// *Action: Modify the underlying base tables directly.
01780, 00000, "string literal required"
// *Cause:
// *Action:
/
01781, 00000, "UNRECOVERABLE cannot be specified without AS SELECT"
// *Cause: UNRECOVERABLE was specified in a CREATE TABLE statement
// without also specifying a populating subquery with an AS clause.
// *Action: Do not specify UNRECOVERABLE.
/
01782, 00000, "UNRECOVERABLE cannot be specified for a cluster or clustered table"
// *Cause: A CREATE CLUSTER, or clustered CREATE TABLE statement
// specified UNRECOVERABLE.
// *Action: Do not specify UNRECOVERABLE.
/
01783, 00000, "only one RECOVERABLE or UNRECOVERABLE clause may be specified"
// *Cause: RECOVERABLE was specified more than once, UNRECOVERABLE was specified
// more than once, or both RECOVERABLE and UNRECOVERABLE were specified
// in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement.
// *Action: Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and
// reissue the statement.
/
01784, 00000, "RECOVERABLE cannot be specified with database media recovery disabled"
// *Cause: A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE
// when the database was running in NOARCHIVELOG mode. Since logs
// are not being archived, they will be overwritten and the object
// being created cannot be recovered from a backup taken before the
// object was created.
// *Action: Do not specify RECOVERABLE, or restart the database with media
// recovery enabled.
/
01785, 00000, "ORDER BY item must be the number of a SELECT-list expression"
// *Cause:
// *Action:
01786, 00000, "FOR UPDATE of this query expression is not allowed"
// *Cause:
// *Action:
01787, 00000, "only one clause allowed per query block"
// *Cause:
// *Action:
01788, 00000, "CONNECT BY clause required in this query block"
// *Cause:
// *Action:
01789, 00000, "query block has incorrect number of result columns"
// *Cause:
// *Action:
01790, 00000, "expression must have same datatype as corresponding expression"
// *Cause:
// *Action:
01791, 00000, "not a SELECTed expression"
// *Cause:
// *Action:
01792, 00000, "maximum number of columns in a table or view is 1000"
// *Cause: An attempt was made to create a table or view with more than 1000
// columns, or to add more columns to a table or view which pushes
// it over the maximum allowable limit of 1000. Note that unused
// columns in the table are counted toward the 1000 column limit.
// *Action: If the error is a result of a CREATE command, then reduce the
// number of columns in the command and resubmit. If the error is
// a result of an ALTER TABLE command, then there are two options:
// 1) If the table contained unused columns, remove them by executing
// ALTER TABLE DROP UNUSED COLUMNS before adding new columns;
// 2) Reduce the number of columns in the command and resubmit.
01793, 00000, "maximum number of index columns is 32"
// *Cause:
// *Action:
01794, 00000, "maximum number of cluster columns is 32"
// *Cause:
// *Action:
01795, 00000, "maximum number of expressions in a list is 1000"
// *Cause: Number of expressions in the query exceeded than 1000.
// Note that unused column/expressions are also counted
// Maximum number of expressions that are allowed are 1000.
// *Action: Reduce the number of expressions in the list and resubmit.
01796, 00000, "this operator cannot be used with lists"
// *Cause:
// *Action:
01797, 00000, "this operator must be followed by ANY or ALL"
// *Cause:
// *Action:
01798, 00000, "missing EXCEPTION keyword"
// *Cause:
// *Action:
01799, 00000, "a column may not be outer-joined to a subquery"
// *Cause: <expression>(+) <relop> (<subquery>) is not allowed.
// *Action: Either remove the (+) or make a view out of the subquery.
// In V6 and before, the (+) was just ignored in this case.
/
/ parse errors continued at 2000
/
/ 1800 - 1899 Date function errors
/ 1800 - 1809 Overflow conditions
/
01800, 00000, "a literal in the date format was too large to process"
// *Cause:
// *Action:
01801, 00000, "date format is too long for internal buffer"
// *Cause:
// *Action:
01802, 00000, "Julian date is out of range"
// *Cause:
// *Action:
01803, 00000, "failure in getting date/time"
// *Cause:
// *Action:
01804, 00000, "failure to initialize timezone information"
// *Cause: The timezone information file was not properly read.
// *Action: Please contact Oracle Customer Support.
01805, 00000, "possible error in date/time operation"
// *Cause: The timezone files on client and server do not match.
// Operation can potentially result in incorrect results based on
// local timezone file.
// *Action: Please ensure client and server timezone versions are same.
/
/ 1810 - 1829 Conflicting date input format
/
01810, 00000, "format code appears twice"
// *Cause:
// *Action:
01811, 00000, "Julian date precludes use of day of year"
// *Cause:
// *Action:
01812, 00000, "year may only be specified once"
// *Cause:
// *Action:
01813, 00000, "hour may only be specified once"
// *Cause:
// *Action:
01814, 00000, "AM/PM conflicts with use of A.M./P.M."
// *Cause:
// *Action:
01815, 00000, "BC/AD conflicts with use of B.C./A.D."
// *Cause:
// *Action:
01816, 00000, "month may only be specified once"
// *Cause:
// *Action:
01817, 00000, "day of week may only be specified once"
// *Cause:
// *Action:
01818, 00000, "'HH24' precludes use of meridian indicator"
// *Cause:
// *Action:
01819, 00000, "signed year precludes use of BC/AD"
// *Cause:
// *Action:
01820, 00000, "format code cannot appear in date input format"
// *Cause:
// *Action:
01821, 00000, "date format not recognized"
// *Cause:
// *Action:
01822, 00000, "era format code is not valid with this calendar"
// *Cause:
// *Action:
/
/ 1830 - 1899 Failed input conversions
/
01830, 00000, "date format picture ends before converting entire input string"
// *Cause:
// *Action:
01831, 00000, "year conflicts with Julian date"
// *Cause:
// *Action:
01832, 00000, "day of year conflicts with Julian date"
// *Cause:
// *Action:
01833, 00000, "month conflicts with Julian date"
// *Cause:
// *Action:
01834, 00000, "day of month conflicts with Julian date"
// *Cause:
// *Action:
01835, 00000, "day of week conflicts with Julian date"
// *Cause:
// *Action:
01836, 00000, "hour conflicts with seconds in day"
// *Cause:
// *Action:
01837, 00000, "minutes of hour conflicts with seconds in day"
// *Cause:
// *Action:
01838, 00000, "seconds of minute conflicts with seconds in day"
// *Cause:
// *Action:
01839, 00000, "date not valid for month specified"
// *Cause:
// *Action:
01840, 00000, "input value not long enough for date format"
// *Cause:
// *Action:
01841, 00000, "(full) year must be between -4713 and +9999, and not be 0"
// *Cause: Illegal year entered
// *Action: Input year in the specified range
01842, 00000, "quarter must be between 1 and 4"
// *Cause:
// *Action:
01843, 00000, "not a valid month"
// *Cause:
// *Action:
01844, 00000, "week of year must be between 1 and 52"
// *Cause:
// *Action:
01845, 00000, "week of month must be between 1 and 5"
// *Cause:
// *Action:
01846, 00000, "not a valid day of the week"
// *Cause:
// *Action:
01847, 00000, "day of month must be between 1 and last day of month"
// *Cause:
// *Action:
01848, 00000, "day of year must be between 1 and 365 (366 for leap year)"
// *Cause:
// *Action:
01849, 00000, "hour must be between 1 and 12"
// *Cause:
// *Action:
01850, 00000, "hour must be between 0 and 23"
// *Cause:
// *Action:
01851, 00000, "minutes must be between 0 and 59"
// *Cause:
// *Action:
01852, 00000, "seconds must be between 0 and 59"
// *Cause:
// *Action:
01853, 00000, "seconds in day must be between 0 and 86399"
// *Cause:
// *Action:
01854, 00000, "julian date must be between 1 and 5373484"
// *Cause: An invalid Julian date was entered.
// *Action: Enter a valid Julian date between 1 and 5373484.
01855, 00000, "AM/A.M. or PM/P.M. required"
// *Cause:
// *Action:
01856, 00000, "BC/B.C. or AD/A.D. required"
// *Cause:
// *Action:
01857, 00000, "not a valid time zone"
// *Cause:
// *Action:
01858, 00000, "a non-numeric character was found where a numeric was expected"
// *Cause: The input data to be converted using a date format model was
// incorrect. The input data did not contain a number where a number was
// required by the format model.
// *Action: Fix the input data or the date format model to make sure the
// elements match in number and type. Then retry the operation.
01859, 00000, "a non-alphabetic character was found where an alphabetic was expected"
// *Cause: The input data to be converted using a date format model was
// incorrect. The input data did not contain a letter where a letter was
// required by the format model.
// *Action: Fix the input data or the date format model to make sure the
// elements match in number and type. Then retry the operation.
01860, 00000, "week of year must be between 1 and 53"
// *Cause:
// *Action:
01861, 00000, "literal does not match format string"
// *Cause: Literals in the input must be the same length as literals in
// the format string (with the exception of leading whitespace). If the
// "FX" modifier has been toggled on, the literal must match exactly,
// with no extra whitespace.
// *Action: Correct the format string to match the literal.
01862, 00000, "the numeric value does not match the length of the format item"
// *Cause: When the FX and FM format codes are specified for an input date,
// then the number of digits must be exactly the number specified by the
// format code. For example, 9 will not match the format specifier DD but
// 09 will.
// *Action: Correct the input date or turn off the FX or FM format specifier
// in the format string.
01863, 00000, "the year is not supported for the current calendar"
// *Cause: The year is not supported for the current calendar.
// *Action: Please check the documentation to find out what years are
// supported for the current calendar.
01864, 00000, "the date is out of range for the current calendar"
// *Cause: Your calendar doesn't extend to the specified date.
// *Action: Specify a date which is legal for this calendar.
01865, 00000, "not a valid era"
// *Cause: Era input does not match a known era.
// *Action: Provide a valid era on input.
01866, 00000, "the datetime class is invalid"
// *Cause: This is an internal error.
// *Action: Please contact Oracle Worldwide Support.
01867, 00000, "the interval is invalid"
// *Cause: The character string you specified is not a valid interval.
// *Action: Please specify a valid interval.
01868, 00000, "the leading precision of the interval is too small"
// *Cause: The leading precision of the interval is too small to store the
// specified interval.
// *Action: Increase the leading precision of the interval or specify an
// interval with a smaller leading precision.
01869, 00000, "reserved for future use"
// *Cause:
// *Action:
01870, 00000, "the intervals or datetimes are not mutually comparable"
// *Cause: The intervals or datetimes are not mutually comparable.
// *Action: Specify a pair of intervals or datetimes that are mutually
// comparable.
01871, 00000, "the number of seconds must be less than 60"
// *Cause: The number of seconds specified was greater than 59.
// *Action: Specify a value for seconds that is 59 or smaller.
01872, 00000, "reserved for future use"
// *Cause:
// *Action:
01873, 00000, "the leading precision of the interval is too small"
// *Cause: The leading precision of the interval is too small to store the
// specified interval.
// *Action: Increase the leading precision of the interval or specify an
// interval with a smaller leading precision.
01874, 00000, "time zone hour must be between -15 and 15"
// *Cause: The time zone hour specified was not in the valid range.
// *Action: Specify a time zone hour between -15 and 15.
01875, 00000, "time zone minute must be between -59 and 59"
// *Cause: The time zone minute specified was not in the valid range.
// *Action: Specify a time zone minute between -59 and 59.
01876, 00000, "year must be at least -4713"
// *Cause: The specified year was not in range.
// *Action: Specify a year that is greater than or equal to -4713.
01877, 00000, "string is too long for internal buffer"
// *Cause: This is an internal error.
// *Action: Please contact Oracle Worldwide Support.
01878, 00000, "specified field not found in datetime or interval"
// *Cause: The specified field was not found in the datetime or interval.
// *Action: Make sure that the specified field is in the datetime or interval.
01879, 00000, "the hh25 field must be between 0 and 24"
// *Cause: The specified hh25 field was not in the valid range.
// *Action: Specify an hh25 field between 0 and 24.
01880, 00000, "the fractional seconds must be between 0 and 999999999"
// *Cause: The specified fractional seconds were not in the valid range.
// *Action: Specify a value for fractional seconds between 0 and 999999999.
01881, 00000, "timezone region ID is invalid"
// *Cause: The region ID referenced an invalid region.
// *Action: Contact Oracle Support Services.
01882, 00000, "timezone region not found"
// *Cause: The specified region name was not found.
// *Action: Contact Oracle Support Services.
01883, 00000, "overlap was disabled during a region transition"
// *Cause: The region was changing state and the overlap flag
// was disabled.
// *Action: Please contact Oracle Customer Support.
01884, 00000, "divisor is equal to zero"
// *Cause: An attempt was made to divide by zero.
// *Action: Avoid zero divisor.
01885, 00000, "public synonym collides with Oracle-supplied schema name"
// *Cause: The public synonym was the same as the Oracle-supplied schema name.
// *Action: Use either a different synonym or a different schema name.
01890, 00000, "NLS error detected"
// *Cause: An NLS error was detected.
// *Action: Look for additional error messages and take appropriate action.
// If there are no additional errors, call Oracle Worldwide Support.
01891, 00000, "Datetime/Interval internal error"
// *Cause: Internal error.
// *Action: Please contact Oracle Worldwide Support.
01898, 00000, "too many precision specifiers"
// *Cause: While trying to truncate or round dates, extra data was found in the
// date format picture
// *Action: Check the syntax of the date format picture and retry.
01899, 00000, "bad precision specifier"
// *Cause:
// *Action:
/
/ 1900 - 1999 V6 parse errors
/
01900, 00000, "LOGFILE keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01901, 00000, "ROLLBACK keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01902, 00000, "SEGMENT keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01903, 00000, "EVENTS keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01904, 00000, "DATAFILE keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01905, 00000, "STORAGE keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01906, 00000, "BACKUP keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01907, 00000, "TABLESPACE keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01908, 00000, "EXISTS keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01909, 00000, "REUSE keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01910, 00000, "TABLES keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01911, 00000, "CONTENTS keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01912, 00000, "ROW keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01913, 00000, "EXCLUSIVE keyword expected"
// *Cause: keyword missing
// *Action: supply missing keyword
01914, 00000, "invalid auditing option for sequence numbers"
// *Cause: AUDIT or NOAUDIT on a sequence number specifies an auditing option
// that is not legal for sequence numbers.
// *Action: The following options may not be used for sequence numbers
// and should be removed: COMMENT, DELETE, INDEX, INSERT, LOCK,
// RENAME, UPDATE, REFERENCES, EXECUTE
01915, 00000, "invalid auditing option for views"
// *Cause: AUDIT or NOAUDIT on a view specifies an auditing option that is
// not legal for views.
// *Action: The following options may not be used for views
// and should be removed: ALTER, INDEX, REFERENCES, EXECUTE
01916, 00000, "keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND, END, DROP, ENABLE, REMOVE, SUSPEND, ENCRYPT, or DECRYPT expected"
// *Cause: An expected keyword was not used for the data file or the temporary
// file clause. Note the ENCRYPT and DECRYPT keywords are only
// applicable to the data file.
// *Action: Use the correct syntax.
01917, 00000, "user or role '%s' does not exist"
// *Cause: There is not a user or role by that name.
// *Action: Re-specify the name.
01918, 00000, "user '%s' does not exist"
// *Cause: User does not exist in the system.
// *Action: Verify the user name is correct.
01919, 00000, "role '%s' does not exist"
// *Cause: Role by that name does not exist.
// *Action: Verify you are using the correct role name.
01920, 00000, "user name '%s' conflicts with another user or role name"
// *Cause: There is already a user or role with that name.
// *Action: Specify a different user name.
01921, 00000, "role name '%s' conflicts with another user or role name"
// *Cause: There is already a user or role with that name.
// *Action: Specify a different role name.
01922, 00000, "CASCADE must be specified to drop '%s'"
// *Cause: Cascade is required to remove this user from the system. The
// user own's object which will need to be dropped.
// *Action: Specify cascade.
01923, 00000, "CASCADE aborted, objects locked by another user"
// *Cause: Cannot drop the user's objects; someone has them locked.
// *Action: Use the lock monitor to determine who has the objects locked.
01924, 00000, "role '%s' not granted or does not exist"
// *Cause: Either the role was not granted to the user, or the role did not exist.
// *Action: Create the role or grant the role to the user and retry
// the operation.
01925, 00000, "unused error"
// *Cause:
// *Action:
01926, 00000, "cannot GRANT to a role WITH GRANT OPTION"
// *Cause: Role cannot have a privilege with the grant option.
// *Action: Perform the grant without the grant option.
01927, 00000, "cannot REVOKE privileges you did not grant"
// *Cause: You can only revoke privileges you granted.
// *Action: Don't revoke these privileges.
01928, 00000, "GRANT option not granted for all privileges"
// *Cause: In order to grant a privilege, you must first have the privilege
// with the grant option.
// *Action: Obtain the privilege with the grant option and try again.
01929, 00000, "no privileges to GRANT"
// *Cause: "ALL" was specified but the user doesn't have any privileges
// with the grant option.
// *Action: Don't grant privileges on that object.
01930, 00000, "auditing the object is not supported"
// *Cause: AUDIT or NOAUDIT was specified for an object that cannot be audited.
// *Action: Don't attempt to AUDIT the object.
01931, 00000, "cannot grant %s to a role"
// *Cause: An attempt to grant privileges to a role failed.
// UNLIMITED TABLESPACE, REFERENCES, INDEX, Administrative Privileges
// like SYSDBA, SYSOPER, SYSASM, SYSBACKUP, SYSDG, SYSKM, and SYSRAC
// cannot be granted to a role.
// *Action: Grant privilege directly to the user. For administrative privilege
// grants, some additional restrictions apply :
// * SYSBACKUP, SYSDG or SYSKM administrative privileges can be
// granted only when the password file is in format "12" or higher.
// * SYSASM administrative privilege can be granted, only when
// connected to an ASM instance.
// * SYSRAC administrative privilege cannot be granted to a user
// because only operating system authentication is supported for
// SYSRAC privilege.
01932, 00000, "ADMIN option not granted for role '%s'"
// *Cause: The operation requires the admin option on the role.
// *Action: Obtain the grant option and re-try.
01933, 00000, "cannot create a stored object using privileges from a role"
// *Cause: An attempt was made to create a stored object using privileges
// from a role. Stored objects cannot use privileges from roles.
// *Action: Grant the privileges required to the user directly.
01934, 00000, "circular role grant detected"
// *Cause: Roles cannot be granted circularly. Also, a role cannot be
// granted to itself.
// *Action: Do not perform the grant.
01935, 00000, "missing user or role name"
// *Cause: A user or role name was expected.
// *Action: Specify a user or role name.
01936, 00000, "cannot specify owner when creating users or roles"
// *Cause: Users and roles do not have owners.
// *Action: Don't specify an owner.
01937, 00000, "missing or invalid role name"
// *Cause: A valid role name was expected.
// *Action: Specify a valid role name.
01938, 00000, "IDENTIFIED BY must be specified for CREATE USER"
// *Cause: Cannot create a user without specifying a password or
// "IDENTIFIED EXTERNALLY" for ASM instance.
// *Action: Specify one of the password clauses.
01939, 00000, "only the ADMIN OPTION can be specified"
// *Cause: System privileges and roles can only be granted with the admin
// option. The grant option cannot be used with system privileges and
// roles. The delegate option cannot be used with system privileges.
// *Action: Specify the admin option.
01940, 00000, "cannot drop a user that is currently connected"
// *Cause: Attempt was made to drop a user that is currently logged in.
// *Action: Make sure user is logged off, then repeat command.
01941, 00000, "SEQUENCE keyword expected"
// MERGE: 1917 RENUMBERED TO 1941
// *Cause: keyword missing
// *Action: supply missing keyword
01942, 00000, "IDENTIFIED BY and EXTERNALLY cannot both be specified"
// *Cause: A user cannot be specified to have and not have a password.
// *Action: Specify only one of the options.
01943, 00000, "IDENTIFIED BY already specified"
// *Cause: The identified clause has been given twice.
// *Action: Use only one identified by clause.
01944, 00000, "IDENTIFIED EXTERNALLY already specified"
// *Cause: The identified externaly clause has been given twice.
// *Action: Use only one identified clause.
01945, 00000, "DEFAULT ROLE[S] already specified"
// *Cause: The default roles clause has been given twice.
// *Action: Use only on default role clause.
01946, 00000, "DEFAULT TABLESPACE already specified"
// *Cause: The default tablespace clause has been given twice.
// *Action: Use only one default tablespace clause.
01947, 00000, "TEMPORARY TABLESPACE already specified"
// *Cause: The temporary tablespace clause has been given twice.
// *Action: Use only one temporary tablespace clause.
01948, 00000, "identifier's name length (%s) exceeds maximum (%s)"
// *Cause: A name has been specified that is too long.
// For example, dbms_session.is_role_enabled() specifies a role name
// that is too long.
// *Action: Change the application or command to use a correct identifier.
01949, 00000, "ROLE keyword expected"
// *Cause: The role keyword is required here.
// *Action: Specify the role keyword.
01950, 00000, "no privileges on tablespace '%s'"
// *Cause: User does not have privileges to allocate an extent in the
// specified tablespace.
// *Action: Grant the user the appropriate system privileges or grant the user
// space resource on the tablespace.
01951, 00000, "ROLE '%s' not granted to '%s'"
// *Cause: The role you tried to revoke was not granted to the user.
// *Action: Don't try to revoke a privilege which is not granted.
01952, 00000, "system privileges not granted to '%s'"
// *Cause: A system privilege you tried to revoke was not granted to the user.
// *Action: Make sure the privileges you are trying to revoke are granted.
01953, 00000, "command no longer valid, see ALTER USER"
// *Cause: The syntax for assigning quotas on tablespaces has changed. The
// ALTER USER command is now used to perform the functionality
// *Action: Use the alter user command instead.
01954, 00000, "DEFAULT ROLE clause not valid for CREATE USER"
// *Cause: Default roles cannot be specified for create user.
// *Action: Grant and alter the user's default roles after creating the user.
01955, 00000, "DEFAULT ROLE '%s' not granted to user"
// *Cause: The user being altered does not have the specified role granted
// directly to the user. Note, sub-roles cannot be used in the
// default role clause.
// *Action: Grant the role to the user.
01956, 00000, "invalid command when OS_ROLES are being used"
// *Cause: This command cannot be used when the INIT.ORA parameter OS_ROLES
// is TRUE.
// *Action: Grant the role to the user in the operating system.
01957, 00000, "Keyword MIN or MAX expected, not found"
// *Cause:
// *Action:
01958, 00000, "Must supply an integer for the LAYER option"
// *Cause:
// *Action:
01959, 00000, "Must supply an integer for the OPCODE option"
// *Cause:
// *Action:
01960, 00000, "Invalid dump logfile option"
// *Cause:
// *Action:
01961, 00000, "Invalid dump option"
// *Cause:
// *Action:
01962, 00000, "Must specify a file number or log sequence number"
// *Cause:
// *Action:
01963, 00000, "Must specify a block number"
// *Cause:
// *Action:
01964, 00000, "Must specify a time for the TIME option"
// *Cause:
// *Action:
01965, 00000, "Must specify a PERIOD"
// *Cause:
// *Action:
01966, 00000, "DEFAULT COLLATION already specified"
// *Cause: The default collation clause was specified twice.
// *Action: Use only one default collation clause.
01967, 00000, "invalid option for CREATE CONTROLFILE"
// *Cause: An invalid CREATE CONTROLFILE option is present.
// *Action: Specify only valid CREATE CONTROLFILE options.
01968, 00000, "Only specify RESETLOGS or NORESETLOGS once"
// *Cause: The keyword RESETLOGS or NORESETLOGS has appeared more than once
// *Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once.
01969, 00000, "You must specify RESETLOGS or NORESETLOGS"
// *Cause: Missing a RESETLOGS or a NORESETLOGS
// *Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once.
01970, 00000, "You must specify a database name for CREATE CONTROLFILE"
// *Cause: Missing a database name
// *Action: Retype CREATE CONTROLFILE command with the DATABASE keyword.
01971, 00000, "Illegal ALTER TRACING option"
// *Cause:
// *Action:
01972, 00000, "Must specify a string for ALTER TRACING ENABLE or DISABLE"
// *Cause:
// *Action:
01973, 00000, "Missing change number"
// *Cause: Keyword "CHANGE" found but change number not specified.
// *Action: Fix command line and resubmit
01974, 00000, "Illegal archive option"
// *Cause: Not a valid option to the "ALTER SYSTEM ARCHIVE" command
// *Action:
01975, 00000, "Illegal character in change number %s"
// *Cause:
// *Action:
01976, 00000, "Missing change number"
// *Cause:
// *Action:
01977, 00000, "Missing thread number"
// *Cause: Keyword "THREAD" found but thread number not specified.
// *Action: Fix command line and resubmit
01978, 00000, "Missing sequence number"
// *Cause: Keyword "SEQUENCE" found but sequence number not specified.
// *Action: Fix command line and resubmit
01979, 00000, "missing or invalid password for role '%s'"
// *Cause: An attempt was made to enable a role without giving
// the proper password.
// *Action: Use the IDENTIFIED BY clause in SET ROLE to specify
// the correct password.
01980, 00000, "error during OS ROLE initialization"
// *Cause: An OS error occurred while loading a users OS ROLES.
// *Action: Check the OS error.
01981, 00000, "CASCADE CONSTRAINTS must be specified to perform this revoke"
// *Cause: During this revoke some foreign key contraints will be removed.
// In order to perform this automatically, CASCADE CONSTRAINTS must
// be specified.
// *Action: Remove the constraints or specify CASCADE CONSTRAINTS.
01982, 00000, "invalid auditing option for tables"
// *Cause: AUDIT or NOAUDIT on a table specifies an auditing option that is
// not legal for tables.
// *Action: The following options may not be used for tables
// and should be removed: REFERENCES, EXECUTE
01983, 00000, "invalid auditing option for DEFAULT"
// *Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is
// not legal for DEFAULT.
// *Action: The following options may not be used for DEFAULT
// and should be removed: REFERENCES
01984, 00000, "invalid auditing option for procedures/packages/functions"
// *Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is
// not legal for procedures, packages, or functions.
// *Action: The following options may not be used for procedures, packages,
// and functions and should be removed: all but EXECUTE
01985, 00000, "cannot create user as LICENSE_MAX_USERS parameter exceeded"
// *Cause: Maximum users in the database license limit exceeded.
// *Action: Increase license limit.
01986, 00000, "OPTIMIZER_GOAL is obsolete"
// *Cause: An obsolete parameter, OPTIMIZER_GOAL, was referenced.
// *Action: Use the OPTIMIZER_MODE parameter.
01987, 00000, "client os username is too long"
// *Cause: A client's os username is too long for the os logon to succeed.
// *Action: Use a shorter os username.
01988, 00000, "remote os logon is not allowed"
// *Cause: Remote os login attempted when not allowed.
// *Action: Use a local client, or use the remote_os_authent system parameter
// to turn on remote os logon.
01989, 00000, "role '%s' not authorized by operating system"
// *Cause: The os role does not exist, is not granted to you, or you did not
// provide the correct password.
// *Action: Re-attempt the SET ROLE with a valid os role and password, if
// necessary.
01990, 00000, "error opening password file '%s'"
// *Cause: The password file either did not exist or was inaccessible.
// *Action: Ensure that the file exists and is accessible.
01991, 00000, "invalid password file '%s'"
// *Cause:
// *Action:
01992, 00000, "error closing password file '%s'"
// *Cause:
// *Action:
01993, 00000, "error writing password file '%s'"
// *Cause:
// *Action:
01994, 00000, "Password file missing or disabled"
// *Cause: The operation failed either because the INIT.ORA parameter
// REMOTE_LOGIN_PASSWORDFILE was set to NONE or else because the
// password file was missing.
// *Action: Create the password file using the orapwd tool and set the
// INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE.
01995, 00000, "error reading password file '%s'"
// *Cause:
// *Action:
01996, 00000, "GRANT failed: password file '%s' is full"
// *Cause:
// *Action:
01997, 00000, "GRANT failed: user '%s' is IDENTIFIED GLOBALLY"
// *Cause: An attempt was made to grant administrative privileges to a user
// account, which was created as IDENTIFIED GLOBALLY. This is only
// allowed in an ASM; not in a database instance.
// *Action: When connected to a database instance, try granting the
// administrative privilege to a user whose account is managed
// by the database (as opposed to managed by a directory server,
// as is the case with accounts which are IDENTIFIED GLOBALLY).
01998, 00000, "REVOKE failed: user SYS always has SYSOPER and SYSDBA"
// *Cause: An attempt was made to revoke SYSOPER or SYSDBA administrative
// privileges from the SYS user which is not allowed.
// *Action: Try revoking administrative privilege from users other than SYS.
01999, 00000, "password file cannot be updated in SHARED mode"
// *Cause: An attempt was made to perform one of the following operations,
// but none of these operations are allowed while the INIT.ORA
// parameter REMOTE_LOGIN_PASSWORDFILE is set to SHARED and password
// file is in READ ONLY mode.
// - Attempting to change password for an administrative privileged
// user either using ALTER USER DDL statement or SQL*Plus PASSWORD
// command, or OCIPasswordChange API.
// - Attempting to grant administrative privileges to a user.
// - Attempting to revoke administrative privileges from a user.
// - Attempting to drop an administrative privileged user.
// If the password file was created in 12.2 format, then the following
// additional operations are disallowed when REMOTE_LOGIN_PASSWORDFILE
// parameter is set to SHARED.
// - An ALTER USER DDL statement making changes to an administrative
// privileged user's account status, password profile assignment,
// identification type, password expiration timestamp.
// - An ALTER PROFILE or DROP PROFILE CASCADE DDL statement for
// a password profile, which is assigned to an administrative
// privileged user.
// *Action: Set the INIT.ORA parameter to EXCLUSIVE, shutdown and restart the
// database instance and retry the operation.
/
/ 2000 - 2099 Parse errors continued from 1700 - 1799
/
02000, 00000, "missing %s keyword"
02001, 00000, "user SYS is not permitted to create indexes with freelist groups"
// *Cause: user tried to create an index while running with sys authorization.
// *Action:
02002, 00000, "error while writing to audit trail"
// *Cause:
// *Action:
02003, 00000, "invalid USERENV parameter"
// *Cause:
// *Action:
02004, 00000, "security violation"
// *Cause: This error code is never returned to a user. It is used
// as a value for column, audit_trail.returncode, to signal that a
// security violation occurred.
// *Action: None.
02005, 00000, "implicit (-1) length not valid for this bind or define datatype"
// *Cause:
// *Action:
02006, 00000, "invalid packed decimal format string"
// *Cause:
// *Action:
02007, 00000, "can't use ALLOCATE or DEALLOCATE options with REBUILD"
// *Cause: Allocate or deallocate storage and rebuild index are not compatible.
// *Action: Choose one or the other.
02008, 00000, "non-zero scale specified for nonnumeric column"
// *Cause:
// *Action:
02009, 00000, "the size specified for a file must not be zero"
// *Cause: A value of zero was specified in a SIZE or RESIZE clause
// of a file specification.
// *Action: Use correct syntax, or, if allowed, omit the SIZE or
// RESIZE clause.
02010, 00000, "missing host connect string"
// *Cause:
// *Action:
02011, 00000, "duplicate database link name"
// *Cause:
// *Action:
02012, 00000, "missing USING keyword"
// *Cause:
// *Action:
02013, 00000, "missing CONNECT keyword"
// *Cause:
// *Action:
02014, 00000, "cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc."
// *Cause: An attempt was made to select FOR UPDATE from a view which
// had not been merged because the view used syntax (for example,
// DISTINCT or GROUP BY) preventing the merge, or because of
// initialization file parameter settings.
// *Action: Determine the reason the view will not merge and, if possible,
// make changes so that it can.
02015, 00000, "cannot select FOR UPDATE from remote table"
// *Cause: An attempt was made to select FOR UPDATE on a remote table
// (directly, or via a view) that had abstract data type columns, and
// the view or select list contained abstract data type columns or
// non-column items.
// *Action: To attempt a select FOR UPDATE, use a view or select list that
// consists only of base columns from the remote table, none of which
// may be abstract data type columns.
02016, 00000, "cannot use a subquery in a START WITH on a remote database"
// *Cause:
// *Action:
02017, 00000, "integer value required"
// *Cause:
// *Action:
02018, 00000, "database link of same name has an open connection"
// *Cause:
// *Action:
02019, 00000, "connection description for remote database not found"
// *Cause:
// *Action:
02020, 00000, "too many database links in use"
// *Cause: The current session has exceeded the INIT.ORA open_links maximum.
// *Action: Increase the open_links limit, or free up some open links by
// committing or rolling back the transaction and canceling open
// cursors that reference remote databases.
02021, 00000, "DDL operations are not allowed on a remote database"
// *Cause: An attempt was made to use a DDL operation on a remote database.
// For example, "CREATE TABLE tablename@remotedbname ...".
// *Action: To alter the remote database structure, you must connect to the
// remote database with the appropriate privileges.
02022, 00000, "remote statement has unoptimized view with remote object"
// *Cause: The local view is unoptimized and contains references to objects
// at the remote database and the statement must be executed at the
// remote database.
// *Action: Create a similar view on the remote database and modify the
// violating view in the SQL statement with the new view@remote.
02023, 00000, "START WITH or CONNECT BY predicate cannot be evaluated by remote data base"
// *Cause:
// *Action:
02024, 00000, "database link not found"
// *Cause: Database link to be dropped is not found in dictionary
// *Action: Correct the database link name
02025, 00000, "all tables in the SQL statement must be at the remote database"
// *Cause: The user's SQL statement references tables from multiple databases.
// The remote database is not Oracle V7 or above, and can perform
// updates only if it can reference all tables in the SQL statement.
// *Action:
02026, 00000, "missing LINK keyword"
// *Cause: keyword missing
// *Action: supply missing keyword
02027, 00000, "multi-row UPDATE of LONG column is not supported"
// *Cause: A bind variable with length greater than 4000 bytes is being
// used to update a column, and the update statement updates
// more than one row.
// *Action: You may only update a single row with such a bind variable.
02028, 00000, "fetching an exact number of rows is not supported by the server"
// *Cause: The server does not support UPIALL, so the fetch of an exact
// number of rows cannot be emulated on the user side.
// *Action: Connect to a valid server or do not use an exact fetch.
02029, 00000, "missing FILE keyword"
// *Cause: keyword missing
// *Action: supply missing keyword
02030, 00000, "can only select from fixed tables/views"
// *Cause: An attempt is being made to perform an operation other than
// a retrieval from a fixed table/view.
// *Action: You may only select rows from fixed tables/views.
02031, 00000, "no ROWID for fixed tables or for external-organized tables"
// *Cause: An attempt is being made to access rowid from a fixed
// table or from a external-organized table.
// *Action: Do not access ROWID from a fixed table or from a
// external-organized table.
02032, 00000, "clustered tables cannot be used before the cluster index is built"
// *Cause: User attempted to perform a DML statement on a clustered table
// for which no cluster index has yet been created.
// *Action: Create the cluster index.
02033, 00000, "a cluster index for this cluster already exists"
// *Cause: A cluster index already exists for the cluster.
// *Action: None.
02034, 00000, "speed bind not permitted"
// *Cause: Speed bind not allowed with supplied bind variables. Trapped
// internally by the system.
// *Action: none
02035, 00000, "illegal bundled operation combination"
// *Cause: User requested that the UPI bundled execution call perform an
// an illegal combination of operations.
// *Action: See documentation for legal operation combinations.
02036, 00000, "too many variables to describe with automatic cursor open"
// *Cause: User requested that the UPI bundled execution call perform
// automatic cursor open and close on a describe operation. There
// were too many select-list items or bind variables to do this.
// *Action: open and close cursor explicitly
02037, 00000, "uninitialized speed bind storage"
// *Cause: User attempted a UPI bundled execution call containing a
// standalone execute operation without first performing
// a UPI bundled execution call containing a bind operation.
// *Action: perform a UPI bundled execution call with bind before performing a
// bundled execution call with execute
02038, 00000, "define is not allowed for array type "
// *Cause: User attempted to define a select list variable of type "array".
// Arrays may only serve as host bind variables.
// *Action:
02039, 00000, "bind by value is not allowed for array type "
// *Cause: User attempted to bind an array host variable by value.
// Arrays may only be bound by reference.
// *Action:
/
/ 2040 .. 2099 - Reserved for distributed update
/ (Message range continued at 160)
/
02040, 00000, "remote database %s does not support two-phase commit"
// *Cause: the database was potentially updated but does not support prepare
// to commit (as determined by its logon transaction traits). The
// transaction was rolled back.
// *Action: Do not attempt to update the remote database unless it is the
// only database updated in one transaction.
02041, 00000, "client database did not begin a transaction"
// *Cause: internal error
// *Action: contact support
02042, 00000, "too many distributed transactions"
// *Cause: the distributed transaction table was full because too many
// distributed transactions were active.
// *Action: Run fewer transactions. If you are sure you don't have too
// many concurrent distributed transactions, this indicates an internal
// error and support should be notified. Instance shutdown/restart
// would be a work-around.
02043, 00000, "must end current transaction before executing %s"
// *Cause: a transaction is in progress and one of the following commands
// commands is issued: COMMIT FORCE, ROLLBACK FORCE, or
// ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode.
// *Action: COMMIT or ROLLBACK the current transaction and resubmit
// command.
02044, 00000, "transaction manager login denied: transaction in progress"
// *Cause: a remote transaction manager tried to log in while a distributed
// transaction is in progress.
// *Action: end the current transaction (this is a protocol error from a
// remote transaction manager)
02045, 00000, "too many local sessions participating in global transaction"
// *Cause: too many sessions at this site for this transaction.
// *Action: use an existing link so another session need not be created.
02046, 00000, "distributed transaction already begun"
// *Cause: internal error or error in external transaction manager.
// A server session received a begin_tran RPC before finishing
// with a previous distributed tran.
02047, 00000, "cannot join the distributed transaction in progress"
// *Cause: Either a transaction is in progress against a remote database
// that does not fully support two phase commit, and an update
// is attempted on another database, or updates are pending and
// and an attempt is made to update a different database that
// does not fully support two phase commit.
// *Action: complete the current transaction and then resubmit the
// update request.
02048, 00000, "attempt to begin distributed transaction without logging on"
// *Cause: client program must issue a distributed transaction login.
// *Action: contact support.
02049, 00000, "timeout: distributed transaction waiting for lock"
// *Cause: "The number of seconds specified in the distributed_lock_timeout
// initialization parameter were exceeded while waiting for a lock
// or for a begin transaction hash collision to end."
// *Action: Treat this timeout as a deadlock. Roll back the transaction and
// try again.
02050, 00000, "transaction %s rolled back, some remote DBs may be in-doubt"
// *Cause: network or remote failure in 2PC.
// *Action: Notify operations; remote DBs will automatically re-sync when the
// failure is repaired.
02051, 00000, "another session or branch in same transaction failed or finalized"
// *Cause: A session at the same site with the same global transaction ID failed.
// The failure could also be caused by an application error if an attempt
// was made to update the database while another tightly coupled transaction
// branch with the same global transaction ID was finalized or aborted.
// *Action: No action necessary as the transaction will be automatically recovered.
// In the case of an application error, make sure there are no more updates
// to the database once the transaction manager has started two-phase commit
// for tightly coupled distributed transaction.
02052, 00000, "remote transaction failure at %s"
// *Cause: error in remote transaction at given DBLINK
// *Action: retry
02053, 00000, "transaction %s committed, some remote DBs may be in-doubt"
// *Cause: network or remote failure in 2PC.
// *Action: Notify operations; remote DBs will automatically re-sync when the
// failure is repaired.
02054, 00000, "transaction %s in-doubt"
// *Cause: network or remote failure in 2PC.
// *Action: Notify operations; DBs will automatically re-sync when the
// failure is repaired. Monitor pending_trans$ for final outcome.
02055, 00000, "distributed update operation failed; rollback required"
// *Cause: a failure during distributed update operation may not have
// rolled back all effects of the operation. Since
// some sites may be inconsistent, the transaction must roll back to
// a savepoint or entirely
// *Action: rollback to a savepoint or rollback transaction and resubmit
02056, 00000, "2PC: %s: bad two-phase command number %s from %s"
// *Cause: two-phase commit protocol error.
// *Action: recovery of transaction attempted. Monitor pending_trans$ table to
// ensure correct resolution. Contact support.
02057, 00000, "2PC: %s: bad two-phase recovery state number %s from %s"
// *Cause: internal error in two-phase recovery protocol
// *Action: contact support
02058, 00000, "no prepared transaction found with ID %s"
// *Cause: no transaction with local_tran_id or global_tran_id found in the
// pending_trans$ table in prepared state.
// *Action: check the pending_trans$ table.
02059, 00000, "ORA-2PC-CRASH-TEST-%s in commit comment"
// *Cause: This is a special comment used to test the two phase commit.
// *Action: Don't use this special comment (%s a number 1-10)
02060, 00000, "select for update specified a join of distributed tables"
// *Cause: tables in a join with the for update clause must reside at the
// same DB.
02061, 00000, "lock table specified list of distributed tables"
// *Cause: tables in a lock table statement must reside at the same DB.
// *Action: issue multiple lock table commands.
02062, 00000, "distributed recovery received DBID %s, expected %s"
// *Cause: a database link at a coordinator no longer points to the expected
// database. Link may have been redefined, or a different DB mounted.
// *Action: restore link definition or remote database.
02063, 00000, "preceding %s%s from %s%s"
// *Cause: an Oracle error was received from a remote database link.
// *Action: refer to the preceding error message(s)
02064, 00000, "distributed operation not supported"
// *Cause: One of the following unsupported operations was attempted:
// 1. array execute of a remote update with a subquery that references
// a dblink, or
// 2. an update of a long column with bind variable and an update of
// a second column with a subquery that both references a dblink
// and a bind variable, or
// 3. a commit is issued in a coordinated session from an RPC procedure
// call with OUT parameters or function call.
// *Action: simplify remote update statement
02065, 00000, "illegal option for ALTER SYSTEM"
// *Cause: The option specified for ALTER SYSTEM is not supported
// *Action: refer to the user manual for option supported
02066, 00000, "missing or invalid DISPATCHERS text"
// *Cause: A character string literal was expected, but not found, following
// ALTER SYSTEM SET DISPATCHERS
// *Action: place the string literal containing the dispatcher's specification
// after ALTER SYSTEM SET DISPATCHERS
02067, 00000, "transaction or savepoint rollback required"
// *Cause: A failure (typically a trigger or stored procedure with multiple
// remote updates) occurred such that the all-or-nothing execution
// of a previous Oracle call cannot be guaranteed.
// *Action: rollback to a previous savepoint or rollback the transaction
// and resubmit.
02068, 00000, "following severe error from %s%s"
// *Cause: A severe error (disconnect, fatal Oracle error) received from
// the indicated database link. See following error text.
// *Action: Contact the remote system administrator.
02069, 00000, "global_names parameter must be set to TRUE for this operation"
// *Cause: A remote mapping of the statement is required but cannot be achieved
// because global_names should be set to TRUE for it to be achieved
// *Action: Issue alter session set global_names = true if possible
02070, 00000, "database %s%s does not support %s in this context"
// *Cause: The remote database does not support the named capability in
// the context in which it is used.
// *Action: Simplify the SQL statement.
//
02071, 00000, "error initializing capabilities for remote database %s"
// *Cause: Could not load a remote-specified capability table.
// *Action: Contact support for the remote SQL*Connect product.
//
02072, 00000, "distributed database network protocol mismatch"
// *Cause: This should never happen between different PRODUCTION releases of
// ORACLE, but may happen between alpha and beta releases, for example.
// *Action: Upgrade the older release.
//
02073, 00000, "sequence numbers not supported in remote updates"
// *Cause: Sequence numbers may not be used in INSERTS, UPDATES, or DELETES
// on remote tables.
// *Action:
02074, 00000, "cannot %s in a distributed transaction"
// *Cause: A commit or rollback was attempted from session other than
// the parent of a distributed transaction.
// *Action: Only commit or rollback from the parent session.
02075, 00000, "another instance changed state of transaction %s"
// *Cause: A commit force or rollback force was issued from a session
// in another instance.
// *Action: Check if another Oracle instance is performing recovery of pending
// transactions. Query DBA_2PC_PENDING to determine the new state
// of the transaction.
02076, 00000, "sequence not co-located with updated table or long column"
// *Cause: all referenced sequences must be co-located with the table
// with the long column.
//
02077, 00000, "selects of long columns must be from co-located tables"
// *Cause: if a select returns long columns from multiple tables, all the
// tables must be co-located
//
02078, 00000, "invalid setting for ALTER SYSTEM FIXED_DATE"
// *Cause:
// *Action:
//
02079, 00000, "cannot join a committing distributed transaction"
// *Cause: Once a transaction branch is prepared, no more new transaction
// branches are allowed to start, nor is the prepared transaction
// branch allowed to be joined.
// *Action: Check the application code as this is an XA protocol violation.
//
02080, 00000, "database link is in use"
// *Cause: a transaction is active or a cursor is open on the database link
// given in the alter session close database link <link> command.
// *Action: commit or rollback, and close all cursors
//
02081, 00000, "database link is not open"
// *Cause: dblink given is not currently open.
//
02082, 00000, "a loopback database link must have a connection qualifier"
// *Cause: An attempt was made to create a database link with the same name
// as the current database.
// *Action: a loopback database link needs a trailing qualifier, for example
// MYDB.EXAMPLE.COM@INST1 - the '@INST1' is the qualifier
//
02083, 00000, "database name has illegal character '%s'"
// *Cause: supplied database name can contain only A-Z, 0-9, '_', '#', '$'
// '.' and '@' characters.
//
02084, 00000, "database name is missing a component"
// *Cause: supplied database name cannot contain a leading '.',
// trailing '.' or '@', or two '.' or '@' in a row.
//
02085, 00000, "database link %s connects to %s"
// *Cause: a database link connected to a database with a different name.
// The connection is rejected.
// *Action: create a database link with the same name as the database it
// connects to, or set global_names=false.
//
02086, 00000, "database (link) name is too long"
// *Cause: database/database link name can have at most 128 characters.
02087, 00000, "object locked by another process in same transaction"
// *Cause: A database link is being used in the cluster database environment
// that loops back to the same instance. One session is trying
// to convert a lock that was obtained by the other session.
// *Action: Get the more restrictive lock first. For example, if
// session 1 gets a share lock and session 2 gets an exclusive lock
// on the same object, get the exclusive lock first. Or, simply
// use the same session to access the object.
02088, 00000, "distributed database option not installed"
// *Cause: Remote and distributed updates and transactions are a separately
// priced option in ORACLE V7.
//
02089, 00000, "COMMIT is not allowed in a subordinate session"
// *Cause: COMMIT was issued in a session that is not the two-phase commit
// global coordinator.
// *Action: Issue commit at the global coordinator only.
//
02090, 00000, "network error: attempted callback+passthru"
// *Cause: internal error.
//
02091, 00000, "transaction rolled back"
// *Cause: Also see error 2092. If the transaction is aborted at a remote
// site then you will only see 2091; if aborted at host then you will
// see 2092 and 2091.
// *Action: Add rollback segment and retry the transaction.
02092, 00000, "out of transaction table slots for distributed transaction"
// *Cause: The transaction is assigned to the system rollback segment and is
// trying to get into the PREPARED state, but the required number
// of non-PREPARED slots are not available, hence the transaction
// is rolled back.
// *Action: Add a rollback segment and retry the transaction.
02093, 00000, "TRANSACTIONS_PER_ROLLBACK_SEGMENT(%s) more than maximum possible(%s)"
// *Cause: Value of parameter specified is greater than allowed on this port.
// *Action: Use default or reduce it to less than max.
02094, 00000, "replication option not installed"
// *Cause: The replication option was not installed at this site. Updatable
// materialized views, deferred RPCs, and other replication features were,
// therefore, unavailable.
// *Action: Install the replication option. The replication option is not
// part of the Oracle Server product and must be purchased
// separately. Contact an Oracle Sales representative if the
// replication option needs to be purchased.
02095, 00000, "specified initialization parameter cannot be modified"
// *Cause: The specified initialization parameter is not modifiable
02096, 00000, "specified initialization parameter is not modifiable with this option"
// *Cause: Though the initialization parameter is modifiable, it cannot be
// modified using the specified command.
// *Action: Check the DBA guide for information about under what scope
// the parameter may be modified
02097, 00000, "parameter cannot be modified because specified value is invalid"
// *Cause: Though the initialization parameter is modifiable, the modified
// value is not acceptable to the parameter.
// *Action: Check the DBA guide for range of acceptable values for this
// parameter.
02098, 00000, "error parsing index-table reference (:I)"
// *Cause: An incorrect index-table (:I) syntax was encountered.
// *Action: This syntax is for oracle internal use only.
02099, 00000, "used for internal purposes, should never be printed"
/
/ MODIFIED
/ rajeekku 10/30/17 - Bug 27047449: add error 3103
/ lenovak 09/28/17 - Bug 26887766: compare shard versions
/ dmaniyan 09/20/17 - Add error message 3808, 3812-3814
/ rrungta 09/19/17 - rti20598053: ORA-4037 for remote instance encountering
/ 4031
/ zzeng 09/14/17 - Add 3807
/ dmaniyan 09/13/17 - Add error 3797
/ dmaniyan 09/06/17 - Edit error 3906
/ dcolello 08/25/17 - add 3796
/ bidu 08/16/17 - Add error 3967
/ itaranov 08/03/17 - 26161483: non-online tss error message
/ dmaniyan 08/08/17 - Add error 3805
/ dcolello 08/04/17 - add 3793 and 3794
/ saratho 07/27/17 - Bug 26400719: add error 3791-3792
/ saratho 07/23/17 - Bug 26241691: add message 3801
/ dmaniyan 07/17/17 - Add error 3800, 3804. Edit error 3945
/ zzeng 07/12/17 - Add 3943,3949,3803
/ arjusing 07/07/17 - Bug 26268089: Correct warning ORA-03783
/ dcolello 07/10/17 - bug 26314708: add error 3790
/ vbipinbh 06/26/17 - add error 2686
/ dmaniyan 06/22/17 - Add errors 3789, 3945-3948, edit 3919
/ arjusing 06/09/17 - Bug 22537284: Add error 3788
/ zzeng 06/02/17 - Add 3940-42
/ vidgovin 06/09/17 - Add error 3944
/ vidgovin 05/22/17 - Add error message 3937,3938
/ jingzhen 05/22/17 - rti 20313910: add error 3187
/ dmaniyan 05/19/17 - Add error 3936, 3939
/ zzeng 05/04/17 - Add 3933-3935
/ lenovak 05/19/17 - Bug 26105050: change message 3760
/ arjusing 05/12/17 - Bug 22494147: Add warning 3783.
/ zzeng 05/04/17 - Add 3933-3935
/ dmaniyan 05/03/17 - Add error message 3932
/ saratho 04/12/17 - Bug 25816781: add messages 3767-3768, 3770, 3773-3775,
/ 3779, 3780, 3783-3786
/ zzeng 03/30/17 - Add 3929-3931
/ dmaniyan 03/15/17 - Add errors for composite sharding indexes
/ itaranov 02/23/17 - Generalize error messages
/ dmaniyan 02/15/17 - Add error message 3924
/ saratho 02/07/17 - check for number of shards
/ jingzhen 02/07/17 - bug 25459958: disable ADG on Non-Oracle Cloud
/ dmaniyan 01/19/17 - Add error 3922, 3923
/ dmaniyan 12/08/16 - Add error messages 3918-3921
/ vakrishn 11/22/16 - bug 25114576: add 3185 IMC ADG on ENG systems and PaaS
/ nbenadja 11/21/16 - Bug# 21423676: add error# 03917.
/ lenovak 11/21/16 - Bug 25121878: duplicated table DML errors
/ dcolello 10/27/16 - bug 23152783: implement set dataguard_property
/ dmaniyan 10/15/16 - Add error message 3913, 3914
/ dmaniyan 10/14/16 - Add error message 3915
/ zzeng 10/11/16 - Add 3903
/ anidash 10/06/16 - 3962,3963 - for userdef sharding split partition
/ dcolello 09/16/16 - bug 24681708: add 3769
/ zzeng 09/08/16 - Add 3900-3902
/ zzeng 09/01/16 - Composite sharding related messages 2598-99
/ zzeng 09/01/16 - Composite sharding related messages 2599, 2669
/ dmaniyan 09/01/16 - Add error message 3905,3906
/ nbenadja 08/25/16 - Add message 02597.
/ saratho 08/15/16 - Bug 22264178: truncate of duplicated table on shard
/ vidgovin 08/17/16 - XbranchMerge vidgovin_bug-24400407 from
/ st_rdbms_12.2.0.1.0
/ saratho 08/15/16 - Bug 22264178: truncate of duplicated table on shard
/ jingzhen 08/09/16 - add test event 3184 for object lock testing
/ itaranov 08/05/16 - XbranchMerge itaranov_bug-24328811 from
/ st_rdbms_12.2.0.1.0
/ vidgovin 08/05/16 - Add 2595 - Bug 24400407
/ mrajm 07/19/16 - Bug 12763598: added 3155
/ itaranov 07/13/16 - bug 24291688: prevent double-split of the same chunk
/ lenovak 07/22/16 - project 62462 Sharding for RAC affinity
/ dcolello 07/01/16 - bug 23589416: add 3755 for primary/standby mismatch
/ dcolello 07/01/16 - bug 23711027: add 3754 for user-defined
/ dcolello 07/01/16 - bug 23644168: update error message
/ itaranov 06/17/16 - bug 23548757: shard exec whitlist check failed
/ zzeng 06/09/16 - Bug 23342654,21543020: add 2573, 2574
/ dcolello 06/09/16 - bug 23563822: add 3751
/ dcolello 06/09/16 - re-word 2542 and 2543
/ dcolello 05/25/16 - add 3749 for broker configuration
/ nbenadja 05/25/16 - bug#22277547 : add error message
/ zzeng 05/19/16 - Bug 23302885: update 2560
/ anidash 05/15/16 - Bug 23080268: msg when tablespace does not exist in
/ the correct shard
/ kmohan 05/13/16 - Reword TTC protocol errors
/ dcolello 05/05/16 - add 3746 for shard validation
/ dmaniyan 05/03/16 - Project 46694 : Add errors 2589, 2590, 2591
/ dcolello 05/03/16 - add GSM not running message for deploy
/ dcolello 05/03/16 - bug 23194420: no new shardspace if root table
/ itaranov 04/29/16 - DDL state error
/ dcolello 04/19/16 - bug 23126745: update 2649 for composite sharding
/ nbenadja 04/18/16 - add message 2582.
/ ralekra 04/15/16 - Add OGG/Sharding error messeges
/ kkverma 04/11/16 - Add error 3102
/ dcolello 04/09/16 - add 3740 and 3741
/ lenovak 04/05/16 - bugfix 23032790
/ zzeng 03/29/16 - Update 2557, add 2572
/ dmaniyan 03/18/16 - Proj. 46694 : Add error 2582
/ dcolello 03/10/16 - bug 22494157: add 3739
/ dmaniyan 03/08/16 - Project 46694 : Edit error 2581
/ lenovak 02/22/16 - gdsctl output for catalog_requests
/ dmaniyan 02/08/16 - Project 46694 : Add error 2581
/ lenovak 01/26/16 - shard error messaages
/ dmaniyan 01/25/16 - Proj. 46694 - Add errors 2579, 2580
/ dcolello 01/19/16 - add 3718 and 3719
/ vbipinbh 01/19/16 - add 2683
/ vbipinbh 01/19/16 - add 2682
/ dmaniyan 12/23/15 - Proj. 46694 : Add errors 2576, 2577, 2578
/ ralekra 12/18/15 - Sharding/OGG error messages
/ vbipinbh 12/13/15 - add 2682
/ zzeng 11/17/15 - Add 2564, 2575
/ dmaniyan 11/20/15 - Proj. 46694 : Add error 2569
/ bsprunt 11/16/15 - Bug 21877341: fwd merge SE/XE cpu-count & plan limits
/ dcolello 11/11/15 - add 2634, 2663, and 2664
/ jingzhen 10/23/15 - Add ORA-03183 for illegal dynamic parameter value
/ change on ADG
/ vidgovin 10/13/15 - Add 2546
/ zzeng 10/09/15 - Add 02560 for bugs 21602425 21616433 21602429 21602423
/ dmaniyan 09/23/15 - Add error 2567, 2568
/ dmaniyan 09/15/15 - Add error 2565
/ yapli 09/15/15 - Bug 20376005: Add profile parameter name in ORA-2377
/ dcolello 09/15/15 - fix 2635
/ dcolello 09/14/15 - fix terminology in 2654
/ vbipinbh 09/14/15 - modify error message 2678
/ dcolello 09/08/15 - add 3713
/ nbenadja 08/13/15 - Add error 2542.
/ vbipinbh 08/07/15 - add 2681
/ vidgovin 08/07/15 - Proj 46694 Error numbers for reference tables
/ dmaniyan 08/07/15 - Proj. 46694 : Add error 2549
/ dmaniyan 07/30/15 - Proj 46694 : Edit error 2507
/ vbipinbh 07/30/15 - add 2680
/ dcolello 07/28/15 - update for terminology name changes
/ zzeng 07/24/15 - More messages for disallowed operations with sharding
/ dmaniyan 07/09/15 - Proj. 46694 : Add error 2538
/ dcolello 07/08/15 - add error 2662
/ zzeng 06/29/15 - Add error message for unsupported objects for sharding
/ vbipinbh 06/29/15 - add more error msg for sharded sql
/ nbenadja 06/25/15 - Add new sharding message.
/ dcolello 06/25/15 - add error 2661
/ itaranov 06/23/15 - 2537 Add datafile name error for tablespace set
/ dcolello 06/20/15 - add errors 2651-2658
/ dcolello 06/19/15 - add errors 2659 and 2660
/ dcolello 06/18/15 - add error 2650
/ ditalian 06/17/15 - sharding method mismatch error message
/ dcolello 05/31/15 - add errors 2643-2649
/ nbenadja 05/19/15 - Proj. 46694: add error messages for indexes on sharded
/ tables.
/ ditalian 05/20/15 - error msg for user defined sharding
/ smuthuli 05/07/15 - Fix Cause for error 2187
/ ditalian 04/28/15 - error messages for table fam w/out ref partitioning
/ vbipinbh 04/18/15 - proj 56819: add error msg for sharded sql
/ ditalian 03/11/15 - Add error message for gwm_get_donum_range failure
/ nbenadja 02/18/15 - Proj 46694: add sharding message.
/ sumkumar 12/26/14 - Project 46885: Update ORA-2377 Cause/Action to mention
/ inactive_account_time parameter can't be less than 15
/ nbenadja 12/19/14 - Project 46694 : Add 2500-2515 error messages.
/ mdilman 12/11/14 - reserve 2500 - 2699 for Database Sharding
/ jstewart 09/16/14 - project 35746: long identifiers
/ kdnguyen 10/21/13 - Updated 2216 Cause msg.
/ ihonda 06/06/12 - Updated 2471
/ shiyadav 06/01/12 - modify the message for error 04017
/ jdavison 05/31/12 - Fix messages with incorrect action format
/ fuli 04/20/12 - Added 3182 for ADG global sequence
/ fuli 02/06/12 - Added 3181 for ADG global sequence
/ fuli 01/27/12 - bug 13628892: add error 03180
/ umabhat 11/11/11 - added err 03150
/ bhabeck 07/25/11 - project 32541: add 4036 for pga_aggregate_limit param
/ shiyer 02/21/11 - Add 3149
/ mbastawa 02/08/11 - add 3148
/ skiyer 11/03/08 - 7298722:add error 03223
/ jiashi 09/04/08 - add 3176
/ shiyer 06/02/08 - Add 3147
/ jiashi 04/01/08 - add ORA-3174, 3175 for ADG SLA
/ jaeblee 10/30/07 - fix bugs 6510941, 4402125
/ jiashi 10/18/07 - add ORA-3172, 3173 for ADG SLA
/ krajaman 06/01/07 - Change 4023 message
/ mvemulap 06/06/07 - error 4035
/ kigoyal 04/04/07 - add 3150, fix typos
/ shiyer 04/25/07 - add 3146
/ avaliani 04/18/07 - fix typo in cause of ORA-02391
/ nlee 03/13/07 - Add error message 4024.
/ rupsingh 01/17/07 - Add error message 3009
/ sbodagal 11/16/06 - add 4023
/ debanerj 08/09/06 - add 3145
/ rpingte 06/08/06 - add messages 3142-3144
/ jacao 06/01/06 - add message 3160
/ shiyer 04/05/06 - add new error message for TTC proto errors
/ gtarora 04/19/06 - nt equipartition event
/ chliang 03/29/06 - add message 3140 and 3141
/ avaliani 03/29/06 - incorporate erros_us feedback
/ sbedarka 11/16/05 - #(4736313) apply 4k limit for xpl pred to txt
/ mmpandey 11/02/05 - 4708558: make addition of tempfile in error 03284
/ cmlim 11/09/05 - update action text for ORA-2352 & 2353
/ yuli 10/31/05 - remove unused error numbers
/ cmlim 06/28/05 - bug 4373139 - cleanup error handling
/ chliang 04/25/05 - fix error text for 3135
/ schandra 01/31/05 - remove error 4018 and friends
/ cmlim 03/18/05 - fix comment: dpapi msgs end w/ 26099, not 26999
/ chliang 02/03/05 - add message 3135, 3136
/ nmukherj 09/25/04 - added message 3254
/ pbelknap 06/28/04 - plan diff errors
/ nmukherj 05/12/04 -
/ desinha 12/07/03 - 2531841: add 04069
/ abande 10/14/03 - add error message 3134
/ smalathe 08/19/03 - Bug#3051582: Add mesg 3133
/ pokumar 07/28/03 - add message 4034
/ cmlim 05/22/03 - bug 2885435: update cause/action of ORA-02368
/ jstenois 03/04/03 -
/ jstenois 03/03/03 - 2775869: add message for bad rows during import
/ cmlim 03/27/03 - add 2368. obsolete 2353.
/ cmlim 02/17/03 - bug 2769696
/ cmlim 02/03/03 - add 2354, 2355... for dpapi stream load/unload error
/ lilin 12/16/02 - Eliminate Thread Number, add 2188
/ aramarao 11/11/02 - Message for disabling modifying of INITRANS for
/ hashed clusters
/ cmlim 11/05/02 - add err msgs for dirpath stream load/unload (#2351,...)
/ nwhyte 10/21/02 - Change "Average" to "average" on message 3222 per
/ review comments
/ ilam 08/30/02 - Add 2487, 2488
/ porangas 10/17/02 - Fix bug#2607903
/ wyang 09/11/02 - change 2142, 2180
/ sbedarka 09/16/02 - #(2479110) handle pin deadlock error
/ nwhyte 08/21/02 - Add object growth trend and create table cost to
/ dbms_space
/ cmlim 07/01/02 - remove obsolete direct loader msgs.
/ reserve this range for 2351-2375 for direct path api.
/ bemeng 08/02/02 - add 3252 (initial extent size for LOB segment)
/ phchang 02/11/02 - #1941831: add error 2314
/ smuralid 12/22/01 - eliminate 2312, 2313 etc
/ yuli 10/23/01 - tablespace rename project
/ smuthuli 08/01/01 - locally managed SYSTEM tablespace
/ yuli 07/26/01 - change oer 2142 and 2180
/ smuthuli 06/07/01 - Change oer 3237
/ weili 06/22/01 - bug 1755749 fix - remove 3232
/ smuthuli 01/12/01 - add 3249
/ vshukla 01/17/01 - Fix error message 2262.
/ gtarora 01/16/01 - add 2348
/ dalpern 11/28/00 - privileges for kga debugger
/ smukkama 10/11/00 - add 3221 (disallow non-std block size temp segments)
/ amanikut 10/04/00 - modify 2321
/ bhirano 09/03/00 - add out-of-memory error for pool growth
/ preilly 08/14/00 - Update description to fix bug 1164753
/ lsheng 07/27/00 - update error message ORA-02204
/ preilly 07/31/00 - Update error message for bug 1164753
/ skaluska 06/23/00 - add 3119, 3132.
/ mjstewar 06/13/00 - OMF
/ bdagevil 04/18/00 - add error msg for memory management
/ nireland 03/20/00 - Amend ORA-3219 message. #1152302
/ rmurthy 03/31/00 - inheritance related changes
/ apadmana 01/06/00 - change SNAPSHOT to MATERIALIZED VIEW
/ skray 12/13/99 - modified alter tracing messages 2480-2489
/ smuthuli 04/28/99 - add 3247
/ lcprice 07/01/99 - 746805 modify 3211 message
/ mjungerm 03/23/99 - fix comment in 04044
/ weiwang 02/02/99 - add schema name to error 4098
/ akruglik 06/30/98 - incorporate Randy's comments
/ akruglik 06/30/98 - define msgs 3238 and 3239
/ ansriniv 04/13/98 - add OER(4047) - dbms_shared_pool
/ atsukerm 03/03/98 - add subpartition messages to DBMS_SPACE package.
/ tnbui 12/03/97 - Change error messages for validating a constraint
/ bgoyal 12/17/97 - error 2327 change column to expression
/ bhimatsi 03/03/98 - bitmapped ts - add error messages
/ atsukerm 02/06/98 - add dbms_space_admin errors.
/ mkcyee 11/03/97 - #(568232): add error 3206
/ lcprice 08/19/97 - Merge of bug fix 461293
/ jwlee 08/04/97 - Add error 4018
/ akruglik 07/29/97 - add msgs 3233-3236
/ mluong 06/24/97 - merge from 803
/ nireland 06/24/97 - Add error message 2475. (#324089)
/ anolan 05/21/97 - checkout
/ mjaganna 06/11/97 - Change message 02160
/ mluong 05/27/97 - fix merge problem
/ anolan 05/14/97 - Demo.
/ jbellemo 04/11/97 - remove 2343
/ jbellemo 04/08/97 - undo 2303, add types to 2344
/ thajek 03/24/97 - del 2346, modify 2303, readd 2344
/ rjenkins 03/18/97 - changing 2256
/ usundara 01/03/97 - add error 2311 for bug 434240
/ usundara 12/31/96 - incomplete and mutually-dependent types (add ora-4055)
/ bcchang 12/20/96 - error.msg split
/
/ 2100 .. 2139 - Reserved for precompiler runtime (SQLLIB)
/
02100, 00000, "PCC: out of memory (i.e., could not allocate)"
02101, 00000, "PCC: inconsistent cursor cache (uce/cuc mismatch)"
02102, 00000, "PCC: inconsistent cursor cache (no cuc entry for this uce)"
02103, 00000, "PCC: inconsistent cursor cache (out-of-range cuc ref)"
02104, 00000, "PCC: inconsistent host cache (no cuc available)"
02105, 00000, "PCC: inconsistent cursor cache (no cuc entry in cache)"
02106, 00000, "PCC: inconsistent cursor cache (OraCursor nr is bad)"
02107, 00000, "PCC: this pgm too old for run-time library: please re-PCC it"
02108, 00000, "PCC: invalid descriptor passed to run-time library"
02109, 00000, "PCC: inconsistent host cache (out-of-range sit ref)"
02110, 00000, "PCC: inconsistent host cache (invalid sqi type)"
02111, 00000, "PCC: heap consistency error"
02112, 00000, "PCC: SELECT..INTO returns too many rows"
/
/ 2140 .. 2499 - V6 parser errors continued
/ parser errors continued at 25000
/
02140, 00000, "invalid tablespace name"
// *Cause: An identifier does not follow ALTER TABLESPACE.
// *Action: Specify a tablespace name following ALTER TABLESPACE.
02141, 00000, "invalid OFFLINE option"
// *Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE.
// *Action: The user must either specify no option following OFFLINE or
// one of the options NORMAL or IMMEDIATE.
02142, 00000, "missing or invalid ALTER TABLESPACE option"
// *Cause: A valid option was not present.
// *Action: Use one of the valid options: add, rename, default, online,
// offline, read only, read write, begin, end, no, force,
// retention guarantee and retention noguarantee.
02143, 00000, "invalid STORAGE option"
// *Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or
// PCTINCREASE was specified in the STORAGE clause.
// *Action: Specify only valid options.
02144, 00000, "no option specified for ALTER CLUSTER"
// *Cause: No ALTER CLUSTER options are specified.
// *Action: Specify one or more of the following options: pctfree,
// pctused, size, storage.
02145, 00000, "missing STORAGE option"
// *Cause: No STORAGE options were specified following STORAGE (
// *Action: Specify one or more STORAGE option between the
// parentheses.
02146, 00000, "SHARED specified multiple times"
// *Cause: The SHARED option was specified in a CREATE DATABASE
// statement multiple times.
// *Action: Only specify the SHARED option once.
02147, 00000, "conflicting SHARED/EXCLUSIVE options"
// *Cause: Both the SHARED and EXCLUSIVE options were specified in a
// CREATE DATABASE statement.
// *Action: Specify SHARED or EXCLUSIVE, but not both.
02148, 00000, "EXCLUSIVE specified multiple times"
// *Cause: The EXCLUSIVE option was specified in a CREATE DATABASE
// statement multiple times.
// *Action: Only specify the EXCLUSIVE option once.
02149, 00000, "Specified partition does not exist"
// *Cause: Partition not found for the object.
// *Action: Retry with correct partition name.
02150, 00000, "invalid new tablespace name"
// *Cause: The new tablespace name specified in ALTER TABLESPACE RENAME TO
// statement was invalid.
// *Action: Retry with a valid new tablespace name.
02151, 00000, "invalid tablespace name: %s"
// *Cause: Oracle cannot create a tablespace whose name starts with
// '_$deleted$'.
// *Action: Try a different tablespace name.
02152, 00000, "Invalid ALTER TABLESPACE ... RENAME option"
// *Cause: An option other than DATAFILE or TO follows by ALTER
// TABLESPACE ... RENAME.
// *Action: The user must specify either DATAFILE or TO following ALTER
// TABLESPACE ... RENAME.
02153, 00000, "invalid VALUES password string"
// *Cause: An encoded password string does not follow the VALUES clause.
// *Action: Place a proper encoded password string after the VALUES clause.
02154, 00000, "a tablespace with the name '%s' is found"
// *Cause: An attempt to rename a tablespace to a new name failed because
// the new name is already used by some other tablespace.
// *Action: Retry with a different new name.
02155, 00000, "invalid DEFAULT tablespace identifier"
// *Cause: An identifier does not follow DEFAULT TABLESPACE.
// *Action: Place a tablespace name after DEFAULT TABLESPACE.
02156, 00000, "invalid TEMPORARY tablespace identifier"
// *Cause: An identifier does not follow TEMPORARY TABLESPACE.
// *Action: Place a tablespace name after TEMPORARY TABLESPACE.
02157, 00000, "no options specified for ALTER USER"
// *Cause: No options were specified.
// *Action: Specify at least one ALTER USER option.
02158, 00000, "invalid CREATE INDEX option"
// *Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS,
// MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE,
// UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified.
// *Action: Choose one of the valid CREATE INDEX options.
02159, 00000, "installed DLM does not support releasable locking mode"
// *Cause: The parameter file specified gc_* parameters that allow locks
// to be release by the LCK process when not in use. This mode
// requires additional support from the DLM that is not available.
// *Action: Specify configuration parameters that do not require the
// additional function.
02160, 00000, "index-organized table can not contain columns of type LONG"
// *Cause: A column of type LONG defined for index-organized table.
// *Action: Do not use columns of type LONG in index-organized tables.
02161, 00000, "invalid value for MAXLOGFILES"
// *Cause: A number does not follow MAXLOGFILES.
// *Action: Specify a number after MAXLOGFILES.
02162, 00000, "invalid value for MAXDATAFILES"
// *Cause: A number does not follow MAXDATAFILES.
// *Action: Specify a number after MAXDATAFILES.
02163, 00000, "invalid value for FREELIST GROUPS"
// *Cause: A number does not follow FREELIST GROUPS.
// *Action: Specify a number after FREELIST GROUPS.
02164, 00000, "DATAFILE clause specified more than once"
// *Cause: The CREATE DATABASE command contains more than one DATAFILE clause.
// *Action: Specify at most one DATAFILE clause.
02165, 00000, "invalid option for CREATE DATABASE"
// *Cause: An invalid CREATE DATABASE option is present.
// *Action: Specify only valid CREATE DATABASE options.
02166, 00000, "ARCHIVELOG and NOARCHIVELOG specified"
// *Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a
// CREATE DATABASE statement.
// *Action: Specify at most one of these two options.
02167, 00000, "LOGFILE clause specified more than once"
// *Cause: The CREATE DATABASE command contains more than one LOGFILE clause.
// *Action: Specify at most one LOGFILE clause.
02168, 00000, "invalid value for FREELISTS"
// *Cause: A number does not follow FREELISTS
// *Action: Specify a number after FREELISTS
02169, 00000, "FREELISTS storage option not allowed"
// *Cause: The user attempted to specify the FREELISTS storage
// option. This option may only be specified during
// create table or create index.
// *Action: Remove these options and retry the statement.
02170, 00000, "FREELIST GROUPS storage option not allowed"
// *Cause: The user attempted to specify the FREELIST GROUPS storage
// option. This option may only be specified during create
// table and when allow_freelist_groups INIT.ORA is specified.
// *Action: Remove this option and retry the statement or set the
// allow_freelist_groups INIT.ORA parameter.
02171, 00000, "invalid value for MAXLOGHISTORY"
// *Cause: A number does not follow MAXLOGHISTORY
// *Action: Specify a number after MAXLOGHISTORY
02172, 00000, "The PUBLIC keyword is not appropriate for a disable thread"
// *Cause: The PUBLIC keyword was specified for a disable.
// *Action: Remove the keyword and resubmit.
02173, 00000, "invalid option for DROP TABLESPACE"
// *Cause: Either a token other than INCLUDING was found following the
// tablespace name or some text was found following INCLUDING CONTENTS.
// *Action: Place nothing or only INCLUDING CONTENTS after the tablespace name.
02174, 00000, "Missing required thread number"
// *Cause: Must specify thread number after THREAD keyword
// *Action:
02175, 00000, "invalid rollback segment name"
// *Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier
// was not found following ROLLBACK SEGMENT.
// *Action: Place the segment name following ROLLBACK SEGMENT.
02176, 00000, "invalid option for CREATE ROLLBACK SEGMENT"
// *Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement.
// *Action: Specify one of the valid options: TABLESPACE and STORAGE.
02177, 00000, "Missing required group number"
// *Cause: Must specify group number after GROUP keyword
// *Action:
02178, 00000, "correct syntax is: SET TRANSACTION READ { ONLY | WRITE }"
// *Cause: There is a syntax error in the user's statement.
// *Action: Correct the syntax as indicated.
02179, 00000, "valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }"
// *Cause: There is a syntax error in the user's statement.
// *Action: Correct the syntax as indicated.
02180, 00000, "invalid option for CREATE TABLESPACE"
// *Cause: An invalid option appeared.
// *Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE,
// ONLINE, OFFLINE, FORCE, RETENTION, IN SHARD.
02181, 00000, "invalid option to ROLLBACK WORK"
// *Cause: A token other than TO follows ROLLBACK [WORK].
// *Action: Place nothing or TO SAVEPOINT <name> after ROLLBACK [WORK].
02182, 00000, "savepoint name expected"
// *Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT].
// *Action: Place a savepoint name following TO [SAVEPOINT].
02183, 00000, "valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }"
// *Cause: There is a syntax error in the user's statement.
// *Action: Correct the syntax as indicated.
02184, 00000, "resource quotas are not allowed in REVOKE"
// *Cause: In a revoke statement, a resource quota was specified.
// *Action: Specify resource privilege without the quota.
02185, 00000, "a token other than WORK follows COMMIT"
// *Cause: A token other than WORK follows COMMIT.
// *Action: Place either nothing or WORK after COMMIT.
02186, 00000, "tablespace resource privilege may not appear with other privileges"
// *Cause: An attempt was made to grant or revoke a resource quota in the
// same statement in which other privileges are granted or revoked.
// *Action: Use a separate grant or revoke statement for the resource
// quota privilege.
02187, 00000, "invalid quota specification"
// *Cause: The user attempted to grant a tablespace quota above the upper limit.
// *Action: Grant a smaller tablespace quota.
02188, 00000, "Cannot enable instance publicly"
// *Cause: An attempt was made to publicly enable a thread associated
// with an instance.
// *Action:Leave out the PUBLIC keyword.
02189, 00000, "ON <tablespace> required"
// *Cause: In a grant or revoke statement, the user specified a tablespace
// quota but did not follow it with the ON <tablespace> clause.
// *Action: Specify the tablespace on which the quota is to be applied
// with the ON <tablespace> clause.
02190, 00000, "keyword TABLES expected"
// *Cause: The keyword TABLES is expected following DROP CLUSTER <name>
// INCLUDING.
// *Action: Place TABLES after INCLUDING.
02191, 00000, "correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT <rbs>"
// *Cause: There is a syntax error in the user's statement.
// *Action: Correct the syntax as indicated.
02192, 00000, "PCTINCREASE not allowed for rollback segment storage clauses"
// *Cause: pctincrease was specified in a create or alter rollback segment
// *Action: reissue statement without the pctincrease clause
02194, 00000, "event specification syntax error %s (minor error %s) near '%s'"
// *Cause: There is a syntax error in an event specification.
// *Action: Fix the error.
02195, 00000, "Attempt to create %s object in a %s tablespace"
// *Cause: The object type is inconsistent with a tablespace contents.
// *Action: Create an object in a different tablespace, or change the user
// defaults.
02196, 00000, "PERMANENT/TEMPORARY option already specified"
// *Cause: In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were
// specified more than once.
02197, 00000, "file list already specified"
// *Cause: In CREATE TABLESPACE, more than one DATAFILE/TEMPFILE clause was
// specified.
// *Action: Merge the DATAFILE/TEMPFILE clauses into a single clause.
02198, 00000, "ONLINE/OFFLINE option already specified"
// *Cause: In CREATE TABLESPACE, the ONLINE and/or OFFLINE options were
// specified more than once.
// *Action: Specify at most one of ONLINE or OFFLINE.
02199, 00000, "missing DATAFILE/TEMPFILE clause"
// *Cause: A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause.
// *Action: Specify a DATAFILE/TEMPFILE clause.
02200, 00000, "WITH GRANT OPTION not allowed for PUBLIC"
// *Cause: An attempt was made to GRANT to PUBLIC WITH GRANT OPTION.
// *Action: Remove the WITH GRANT OPTION clause.
02201, 00000, "sequence not allowed here"
// *Cause: An attempt was made to reference a sequence in a from-list.
// *Action: A sequence can only be referenced in a select-list.
02202, 00000, "no more tables permitted in this cluster"
// *Cause: An attempt was made to create a table in a cluster which already
// contains 32 tables.
// *Action: Up to 32 tables may be stored per cluster.
02203, 00000, "INITIAL storage options not allowed"
// *Cause: The user attempted to alter the INITIAL
// storage option of a table, cluster, index, or rollback segment.
// These options may only be specified when the object is created.
// *Action: Remove these options and retry the statement.
02204, 00000, "ALTER, INDEX and EXECUTE not allowed for views"
// *Cause: An attempt was made to grant or revoke an invalid privilege on a view.
// *Action: Do not attempt to grant or revoke any of ALTER, INDEX, or
// EXECUTE privileges on views.
02205, 00000, "only SELECT and ALTER privileges are valid for sequences"
// *Cause: An attempt was made to grant or revoke an invalid privilege on a
// sequence.
// *Action: Do not attempt to grant or revoke DELETE, INDEX, INSERT,
// UPDATE, REFERENCES or EXECUTE privilege on sequences.
02206, 00000, "duplicate INITRANS option specification"
// *Cause: INITRANS is specified more than once.
// *Action: Specify INITRANS at most once.
02207, 00000, "invalid INITRANS option value"
// *Cause: The INITRANS value is not an integer between 1 and 255
// and less than or equal to the MAXTRANS value.
// *Action: Choose a valid INITRANS value.
02208, 00000, "duplicate MAXTRANS option specification"
// *Cause: MAXTRANS is specified more than once.
// *Action: Specify MAXTRANS at most once.
02209, 00000, "invalid MAXTRANS option value"
// *Cause: The MAXTRANS value is not an integer between 1 and 255
// and greater than or equal to the INITRANS value.
// *Action: Choose a valid MAXTRANS value.
02210, 00000, "no options specified for ALTER TABLE"
// *Cause: No ALTER TABLE option was specified.
// *Action: Specify at least one alter table option.
02211, 00000, "invalid value for PCTFREE or PCTUSED"
// *Cause: The specified value for PCTFREE or PCTUSED is not
// an integer between 0 and 100.
// *Action: Choose an appropriate value for the option.
02212, 00000, "duplicate PCTFREE option specification"
// *Cause: PCTFREE option specified more than once.
// *Action: Specify PCTFREE at most once.
02213, 00000, "duplicate PCTUSED option specification"
// *Cause: PCTUSED option specified more than once.
// *Action: Specify PCTUSED at most once.
02214, 00000, "duplicate BACKUP option specification"
// *Cause: The BACKUP option to ALTER TABLE is specified more than once.
// *Action: Specify the option at most once.
02215, 00000, "duplicate tablespace name clause"
// *Cause: There is more than one TABLESPACE clause in the CREATE TABLE,
// CREATE INDEX, or CREATE ROLLBACK SEGMENT statement.
// *Action: Specify at most one TABLESPACE clause.
02216, 00000, "tablespace name expected"
// *Cause: A tablespace name was not present where required by the
// syntax for the failing statement.
// *Action: Specify a tablespace name where required by the syntax.
02217, 00000, "duplicate storage option specification"
// *Cause: A storage option (INIITAL, NEXT, MINEXTENTS, MAXEXTENTS, PCTINCREASE)
// is specified more than once.
// *Action: Specify all storage options at most once.
02218, 00000, "invalid INITIAL storage option value"
// *Cause: The specified value must be an integer.
// *Action: Choose an appropriate integer value.
02219, 00000, "invalid NEXT storage option value"
// *Cause: The specified value must be an integer.
// *Action: Choose an appropriate integer value.
02220, 00000, "invalid MINEXTENTS storage option value"
// *Cause: The specified value must be a positive integer
// less than or equal to MAXEXTENTS.
// *Action: Specify an appropriate value.
02221, 00000, "invalid MAXEXTENTS storage option value"
// *Cause: The specified value must be a positive integer
// greater than or equal to MINEXTENTS.
// *Action: Specify an appropriate value.
02222, 00000, "invalid PCTINCREASE storage option value"
// *Cause: The specified value must be a positive integer.
// *Action: Specify an appropriate value.
02223, 00000, "invalid OPTIMAL storage option value"
// *Cause: The specified value must be an integer.
// *Action: Choose an appropriate integer value.
02224, 00000, "EXECUTE privilege not allowed for tables"
// *Cause: An attempt was made to grant or revoke an invalid privilege on
// a table.
// *Action: Do not attempt to grant or revoke EXECUTE privilege on tables.
02225, 00000, "only EXECUTE and DEBUG privileges are valid for procedures"
// *Cause: An attempt was made to grant or revoke an invalid privilege
// on a procedure, function or package.
// *Action: Do not attempt to grant or revoke any privilege besides EXECUTE
// or DEBUG on procedures, functions or packages.
02226, 00000, "invalid MAXEXTENTS value (max allowed: %s)"
// *Cause: The MAXEXTENTS specified is too large for the database
// block size. This applies only to SYSTEM rollback segment.
// *Action: Specify a smaller value.
02227, 00000, "invalid cluster name"
// *Cause: A cluster name of the form [ <identifier> . ] <identifier> is
// expected but not present.
// *Action: Enter an appropriate cluster name.
02228, 00000, "duplicate SIZE specification"
// *Cause: The SIZE option is specified more than once.
// *Action: Specify the SIZE option at most once.
02229, 00000, "invalid SIZE option value"
// *Cause: The specified value must be an integer number of bytes.
// *Action: Specify an appropriate value.
02230, 00000, "invalid ALTER CLUSTER option"
// *Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS,
// STORAGE, or SIZE is specified in an ALTER CLUSTER statement.
// *Action: Specify only legal options.
02231, 00000, "missing or invalid option to ALTER DATABASE"
// *Cause: An option other than ADD, DROP, RENAME, ARCHIVELOG, NOARCHIVELOG,
// MOUNT, DISMOUNT, OPEN, or CLOSE is specified in the statement.
// *Action: Specify only legal options.
02232, 00000, "invalid MOUNT mode"
// *Cause: A mode other than SHARED or EXCLUSIVE follows the MOUNT keyword
// in an ALTER DATABASE statement.
// *Action: Specify either SHARED, EXCLUSIVE, or nothing following MOUNT.
02233, 00000, "invalid CLOSE mode"
// *Cause: A mode other than NORMAL or IMMEDIATE follows the CLOSE keyword
// in an ALTER DATABASE statement.
// *Action: Specify either NORMAL, IMMEDIATE, or nothing following CLOSE.
02234, 00000, "changes to this table are already logged"
// MERGE: 2292 RENUMBERED TO 2234
// *Cause: the log table to be added is a duplicate of another
// *Action: Don't add this change log to the system; check that the
// replication product's system tables are consistent
02235, 00000, "this table logs changes to another table already"
// MERGE: 2293 RENUMBERED TO 2235
// *Cause: the table to be altered is already a change log for another table
// *Action: Don't log changes to the specified base table to this table; check
// that the replication product's system tables are consistent
02236, 00000, "invalid file name"
// *Cause: A character string literal was not used in the filename list
// of a LOGFILE, DATAFILE, or RENAME clause.
// *Action: Use correct syntax.
02237, 00000, "invalid file size"
// *Cause: A non-integer value was specified in the SIZE or RESIZE clause.
// *Action: Use correct syntax.
02238, 00000, "filename lists have different numbers of files"
// *Cause: In a RENAME clause in ALTER DATABASE or TABLESPACE, the
// the number of existing filenames does not equal the number of
// new filenames.
// *Action: Make sure there is a new filename to correspond to each
// existing filename.
02239, 00000, "there are objects which reference this sequence"
// MERGE: 2290 RENUMBERED TO 2239
// *Cause: the sequence to be dropped is still referenced
// *Action: Make sure the sequence name is correct, or drop the referencing
// constraint/object
02240, 00000, "invalid value for OBJNO or TABNO"
// *Cause: A number does not follow either OBJNO or TABNO.
// *Action: Specify a number after OBJNO or TABNO.
02241, 00000, "must of form EXTENTS (FILE <n> BLOCK <n> SIZE <n>, ...)"
// *Cause: bad extent storage clause
// *Action: respecify
02242, 00000, "no options specified for ALTER INDEX"
// *Cause: No options specified.
// *Action: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE.
02243, 00000, "invalid ALTER INDEX or ALTER MATERIALIZED VIEW option"
// *Cause: An option other than INITRANS, MAXTRANS,or STORAGE is
// specified in an ALTER INDEX statement or in the USING
// INDEX clause of an ALTER MATERIALIZED VIEW statement.
// *Action: Specify only legal options.
02244, 00000, "invalid ALTER ROLLBACK SEGMENT option"
// *Cause: The STORAGE option is expected but not found.
// *Action: Specify the STORAGE option.
02245, 00000, "invalid ROLLBACK SEGMENT name"
// *Cause: An identifier was expected, but not found, following
// ALTER [PUBLIC] ROLLBACK SEGMENT.
// *Action: Place a rollback segment name following SEGMENT.
02246, 00000, "missing EVENTS text"
// *Cause: A character string literal was expected, but not found, following
// ALTER SESSION SET EVENTS.
// *Action: Place the string literal containing the events text after EVENTS.
02247, 00000, "no option specified for ALTER SESSION"
// *Cause: The option SET EVENTS was expected, but not found, following
// ALTER SESSION.
// *Action: Place the SET EVENTS option after ALTER SESSION.
02248, 00000, "invalid option for ALTER SESSION"
// *Cause: Obvious.
// *Action: see SQL Language Manual for legal options.
02249, 00000, "missing or invalid value for MAXLOGMEMBERS"
// *Cause: A valid number does not follow MAXLOGMEMBERS. The value specified
// must be between 1 and the port-specific maximum number of log
// file members.
// *Action: Specify a valid number after MAXLOGMEMBERS.
02250, 00000, "missing or invalid constraint name"
// *Cause: The constraint name is missing or invalid.
// *Action: Specify a valid identifier name for the constraint name.
02251, 00000, "subquery not allowed here"
// *Cause: Subquery is not allowed here in the statement.
// *Action: Remove the subquery from the statement.
02252, 00000, "check constraint condition not properly ended"
// *Cause: The specified search condition for the check constraint is not
// properly ended.
// *Action: End the condition properly.
02253, 00000, "constraint specification not allowed here"
// *Cause: Constraint specification is not allowed here in the statement.
// *Action: Remove the constraint specification from the statement.
02254, 00000, "DEFAULT <expression> not allowed here"
// *Cause: Default value expression is not allowed for the column here in the
// statement.
// *Action: Remove the default value expression from the statement.
02255, 00000, "obsolete 7.1.5"
// *Cause: Was that defaults must not conflict with not null constraints
// *Action:
02256, 00000, "number of referencing columns must match referenced columns"
// *Cause: The number of columns in the foreign-key referencing list is not
// equal to the number of columns in the referenced list.
// *Action: Make sure that the referencing columns match the referenced
// columns.
02257, 00000, "maximum number of columns exceeded"
// *Cause: The number of columns in the key list exceeds the maximum number.
// *Action: Reduce the number columns in the list.
02258, 00000, "duplicate or conflicting NULL and/or NOT NULL specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate or conflicting specification.
02259, 00000, "duplicate UNIQUE/PRIMARY KEY specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate specification.
02260, 00000, "table can have only one primary key"
// *Cause: Self-evident.
// *Action: Remove the extra primary key.
02261, 00000, "such unique or primary key already exists in the table"
// *Cause: Self-evident.
// *Action: Remove the extra key.
02262, 00000, "ORA-%s occurs while type-checking column default value expression"
// *Cause: New column datatype causes type-checking error for existing column
// default value expression.
// *Action: Remove the default value expression or don't alter the column
// datatype.
02263, 00000, "need to specify the datatype for this column"
// *Cause: The required datatype for the column is missing.
// *Action: Specify the required datatype.
02264, 00000, "name already used by an existing constraint"
// *Cause: The specified constraint name has to be unique.
// *Action: Specify a unique constraint name for the constraint.
02265, 00000, "cannot derive the datatype of the referencing column"
// *Cause: The datatype of the referenced column is not defined as yet.
// *Action: Make sure that the datatype of the referenced column is defined
// before referencing it.
02266, 00000, "unique/primary keys in table referenced by enabled foreign keys"
// *Cause: An attempt was made to truncate a table with unique or
// primary keys referenced by foreign keys enabled in another table.
// Other operations not allowed are dropping/truncating a partition of a
// partitioned table or an ALTER TABLE EXCHANGE PARTITION.
// *Action: Before performing the above operations the table, disable the
// foreign key constraints in other tables. You can see what
// constraints are referencing a table by issuing the following
// command:
// SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam";
02267, 00000, "column type incompatible with referenced column type"
// *Cause: The data type or collation of the referencing column was
// incompatible with the data type or collation of the referenced
// column.
// *Action: Select a compatible data type for the referencing column.
// Also, the collation of a character column in a foreign key must
// match the collation of the corresponding column in the primary
// key.
02268, 00000, "referenced table does not have a primary key"
// *Cause: The referenced table does not have a primary key.
// *Action: Specify explicitly the referenced table unique key.
02269, 00000, "key column cannot be of LONG datatype"
// *Cause: Self-evident.
// *Action: Change the datatype of the column,
// or remove the column from the key.
02270, 00000, "no matching unique or primary key for this column-list"
// *Cause: A REFERENCES clause in a CREATE/ALTER TABLE statement
// gives a column-list for which there is no matching unique or primary
// key constraint in the referenced table.
// *Action: Find the correct column names using the ALL_CONS_COLUMNS
// catalog view
02271, 00000, "table does not have such constraint"
// *Cause: Self-evident.
// *Action: Make sure the specified constraint name is correct.
02272, 00000, "constrained column cannot be of LONG datatype"
// *Cause: Self-evident.
// *Action: Change the datatype of the column,
// or remove the constraint on the column.
02273, 00000, "this unique/primary key is referenced by some foreign keys"
// *Cause: Self-evident.
// *Action: Remove all references to the key before the key is to be dropped.
02274, 00000, "duplicate referential constraint specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate specification.
02275, 00000, "such a referential constraint already exists in the table"
// *Cause: Self-evident.
// *Action: Remove the extra constraint.
02276, 00000, "default value type incompatible with column type"
// *Cause: The type of the evaluated default expression is incompatible with
// the datatype of the column.
// *Action: Change the type of the column, or modify the default expression.
02277, 00000, "invalid sequence name"
// *Cause: The specified sequence name is not a valid identifier name.
// *Action: Specify a valid identifier name for the sequence name.
02278, 00000, "duplicate or conflicting MAXVALUE/NOMAXVALUE specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate or conflicting specification.
02279, 00000, "duplicate or conflicting MINVALUE/NOMINVALUE specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate or conflicting specification.
02280, 00000, "duplicate or conflicting CYCLE/NOCYCLE specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate or conflicting specification.
02281, 00000, "duplicate or conflicting CACHE/NOCACHE specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate or conflicting specification.
02282, 00000, "duplicate or conflicting ORDER/NOORDER specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate or conflicting specification.
02283, 00000, "cannot alter starting sequence number"
// *Cause: Self-evident.
// *Action: Don't alter it.
02284, 00000, "duplicate INCREMENT BY specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate specification.
02285, 00000, "duplicate START WITH specifications"
// *Cause: Self-evident.
// *Action: Remove the duplicate specification.
02286, 00000, "no options specified for ALTER SEQUENCE"
// *Cause: Self-evident.
// *Action: The statement is meaningless without any options.
02287, 00000, "sequence number not allowed here"
// *Cause: The specified sequence number (CURRVAL or NEXTVAL) is inappropriate
// here in the statement.
// *Action: Remove the sequence number.
02288, 00000, "invalid OPEN mode"
// *Cause: A token other than RESETLOGS appears following
// ALTER DATABASE <name> OPEN.
// *Action: Either nothing or RESETLOGS should be placed following OPEN.
02289, 00000, "sequence does not exist"
// *Cause: The specified sequence does not exist, or the user does
// not have the required privilege to perform this operation.
// *Action: Make sure the sequence name is correct, and that you have
// the right to perform the desired operation on this sequence.
02290, 00000, "check constraint (%s.%s) violated"
// *Cause: The values being inserted do not satisfy the named check
// constraint.
// *Action: do not insert values that violate the constraint.
02291, 00000,"integrity constraint (%s.%s) violated - parent key not found"
// *Cause: A foreign key value has no matching primary key value.
// *Action: Delete the foreign key or add a matching primary key.
02292, 00000,"integrity constraint (%s.%s) violated - child record found"
// *Cause: attempted to delete a parent key value that had a foreign
// key dependency.
// *Action: delete dependencies first then parent or disable constraint.
02293, 00000,"cannot validate (%s.%s) - check constraint violated"
// *Cause: an alter table operation tried to validate a check constraint to
// a populated table that had nocomplying values.
// *Action: Obvious
02294, 00000,"cannot enable (%s.%s) - constraint changed during validation"
// *Cause: While one DDL statement was attempting to enable this constraint,
// another DDL changed this same constraint.
// *Action: Try again, with only one DDL changing the constraint this time.
02295, 00000,"found more than one enable/disable clause for constraint"
// *Cause: a create or alter table specified more than one enable and/or
// disable clause for a given constraint.
// *Action: only one enable or disable may be specified for a given
// constraint.
02296, 00000,"cannot enable (%s.%s) - null values found"
// *Cause: an alter table enable constraint failed because the table
// contains values that do not satisfy the constraint.
// *Action: Obvious
02297, 00000,"cannot disable constraint (%s.%s) - dependencies exist"
// *Cause: an alter table disable constraint failed becuase the table has
// foriegn keys that are dpendent on this constraint.
// *Action: Either disable the foreign key constraints or use disable cascade
02298, 00000,"cannot validate (%s.%s) - parent keys not found"
// *Cause: an alter table validating constraint failed because the table has
// orphaned child records.
// *Action: Obvious
02299, 00000,"cannot validate (%s.%s) - duplicate keys found"
// *Cause: an alter table validating constraint failed because the table has
// duplicate key values.
// *Action: Obvious
/
/
/ 2300 - 2350 Object extensions to SQL
/ - 2310 - 2319 - Object columns and Object Tables
/ - 2320 - 2329 - Nested Table columns
/
02300, 00000, "invalid value for OIDGENERATORS"
// *Cause: A number was not specified for the value of OIDGENERATORS.
// *Action: Specify a number for OIDGENERATORS.
02301, 00000, "maximum number of OIDGENERATORS is 255"
// *Cause: A number greater than 255 was specified for the value of
// OIDGENERATORS.
// *Action: Make sure the number specified for OIDGENERATORS does not exceed
// 255.
02302, 00000, "invalid or missing type name"
// *Cause: An invalid or missing type name was entered in a statement.
// *Action: Enter a valid type name in the statement and retry the operation.
02303, 00000, "cannot drop or replace a type with type or table dependents"
// *Cause: An attempt was made to drop or replace a type that has
// type or table dependents.
// *Action: For DROP TYPE, drop all type(s) and table(s) depending on the
// type and then retry the operation, or use the FORCE option.
// For CREATE TYPE, drop all type(s) and table(s) depending on the
// type and then retry the operation, or drop all table(s) depending
// on the type and retry with the FORCE option.
02304, 00000, "invalid object identifier literal"
// *Cause: An attempt was made to enter an object identifier literal for
// CREATE TYPE that is either:
// - not a string of 32 hexadecimal characters
// - an object identifier that already identifies an existing
// object
// - an object identifier different from the original object
// identifier already assigned to the type
// *Action: Do not specify the object identifier clause or specify a 32
// hexadecimal-character object identifier literal that is unique
// or identical to the originally assigned object identifier. Then
// retry the operation.
02305, 00000, "only EXECUTE, DEBUG, and UNDER privileges are valid for types"
// *Cause: An attempt was made to GRANT or REVOKE an invalid privilege (not
// EXECUTE, DEBUG, or UNDER) on a type.
// *Action: GRANT or REVOKE only the EXECUTE, DEBUG, or UNDER privilege on
// types.
02306, 00000, "cannot create a type that already has valid dependent(s)"
// *Cause: An attempt was made to create a type that already has some
// valid dependent(s) (these dependents depend on the fact that
// the type does not exist).
// *Action: Drop the dependents first before creating the type, or do not
// create the type.
02307, 00000, "cannot alter with REPLACE option a type that is not valid"
// *Cause: An attempt was made to ALTER with REPLACE option a type that
// is not valid.
// *Action: Use the CREATE OR REPLACE TYPE command to modify the type.
02308, 00000, "invalid option %s for object type column"
// *Cause: An attempt was made to specify an invalid option, such as PACKED
// or UNPACKED, for the object type column.
// *Action: Remove the invalid option from column specification and retry
// the operation.
02309, 00000, "atomic NULL violation"
// *Cause: An attempt was made to acess the attributes of a NULL object
// instance.
// *Action: Ensure that the object instance is non-NULL before accessing.
02310, 00000, "exceeded maximum number of allowable columns in table"
// *Cause: The attributes in the object type column exceeded the maximum
// number of columns allowed in a table.
// *Action: Specify fewer attributes for the object type and retry the
// operation.
02311, 00000, "cannot alter with COMPILE option a valid type with type or table dependents"
// *Cause: An attempt was made to ALTER with COMPILE option a type that is
// valid and has type or table dependents.
// *Action: No need to perform this operation.
//
02313, 00000, "object type contains non-queryable type %s attribute"
// *Cause: The specified object type contains a nested attribute whose type
// is non-queryable.
// *Action: Use an object type with queryable attribute types.
02314, 00000, "illegal use of type constructor"
// *Cause: The statement contains an illegal use of a type constructor.
// *Action: Refer to the SQL Reference manual for the correct statement syntax.
02315, 00000, "incorrect number of arguments for default constructor"
// *Cause: The number of arguments specified for the default constructor
// doesn't match the number of attributes of the object type.
// *Action: Specify the correct number of arguments for the default
// constructor and retry the operation.
02320, 00000, "failure in creating storage table for nested table column %s"
// *Cause: An error occurred while creating the storage table for the
// specified nested table column.
// *Action: See the messages that follow for more details. If the situation
// they describe can be corrected, do so; otherwise contact Oracle
// Support.
02321, 00000, "event for nested table equipartition"
// *Document: NO
// *Cause:
// *Action:
02322, 00000, "failure in accessing storage table of the nested table column"
// *Cause: An error occured while performing DML on the storage table of the
// nested table column.
// *Action: If the situation described in the following messages can be
// corrected, do so; otherwise contact Oracle Support.
02324, 00000, "more than one column in the SELECT list of THE subquery"
// *Cause: More than one column was selected in the THE subquery.
// *Action: Specify only one column in the SELECT list of the THE subquery and
// retry the operation.
02327, 00000, "cannot create index on expression with datatype %s"
// *Cause: An attempt was made to create an index on a non-indexable
// expression.
// *Action: Change the column datatype or do not create the index on an
// expression whose datatype is one of VARRAY, nested table, object,
// LOB, or REF.
02329, 00000, "column of datatype %s cannot be unique or a primary key"
// *Cause: An attempt was made to place a UNIQUE or a PRIMARY KEY constraint
// on a column of datatype VARRAY, nested table, object, LOB, FILE
// or REF.
// *Action: Change the column datatype or remove the constraint. Then retry
// the operation.
02330, 00000, "datatype specification not allowed"
// *Cause: An attempt was made to specify the data type in the column
// constraint specification of an object table.
// *Action: Remove data type specification and retry the operation.
02331, 00000, "cannot create constraint on column of datatype %s"
// *Cause: An attempt was made to create a constraint on a column
// posessing a non-constrainable datatype -- VARRAY, nested table,
// object, LOB, FILE, or REF.
// *Action: Change the column datatype, or remove the constraint.
02332, 00000, "cannot create index on attributes of this column"
// *Cause: An attempt was made to create an index on an attributes of an
// object type column.
// *Action: Do not specify the index on the attribute.
02333, 00000, "cannot create constraints on attributes of this column"
// *Cause: An attempt was made to create a constraint on an attribute of
// an object type column.
// *Action: Remove the constraint or change the object type.
02334, 00000, "cannot infer type for column"
// *Cause: A datatype was not declared for this column (in the CREATE TABLE)
// and an attempt was made to create a constraint on an attribute of
// this column.
// *Action: Declare a datatype for the column.
02335, 00000, "invalid datatype for cluster column"
// *Cause: An attempt was made to declare a CLUSTER column of datatype
// object, REF, nested table, VARRAY, LOB, or FILE.
// *Action: Remove the CLUSTER column or change the datatype of the column.
02336, 00000, "column attribute cannot be accessed"
// *Cause: An attempt was made to extract an attribute of an object type
// column.
// *Action: Change the object type for the column and retry the operation.
02337, 00000, "not an object type column"
// *Cause: An attempt was made to use dotted notation on a non-ADT column;
// that is, "a.b.c" where "a" is not an object type.
// *Action: Either change the column type to an object type or do not
// perform this operation.
02338, 00000, "missing or invalid column constraint specification"
// *Cause: A column constraint was not specified.
// *Action: Remove the column specification or specify a column constraint.
// Then retry the operation.
02339, 00000, "invalid column specification"
// *Cause: An attempt was made to specify the PACKED or UNPACKED keyword
// for a non-object type column.
// *Action: Remove the PACKED or UNPACKED keyword in the column
// specification and retry the operation.
02340, 00000, "invalid column specification"
// *Cause: An attempt was made to specify an UNPACKED column within a
// packed table.
// *Action: Remove the UNPACKED keyword in the column specification.
02342, 00000, "replacement type has compilation errors"
// *Cause: The use of the ALTER...REPLACE statement on a valid type caused
// a compilation error.
// *Action: Use the ALTER...REPLACE statement to replace the type with a valid
// type which does not cause compilation errors.
02344, 00000, "cannot revoke execute on a type with table dependents"
// *Cause: An attempt was made to revoke execute on a type that has
// dependents.
// *Action: Drop all table(s) depending on the type, then retry
// the operation, or use the FORCE option.
02345, 00000, "cannot create a view with column based on CURSOR operator"
// *Cause: A CURSOR operator was used as one of the SELECT elements in the
// subquery of a CREATE VIEW or CREATE TABLE ... AS SELECT statement.
// *Action: Remove the CURSOR operator and replace it with the CAST operator.
02347, 00000, "cannot grant privileges on columns of an object table"
// *Cause: An attempt was made to grant privileges on the columns of an
// object table.
// *Action:
02348, 00000, "cannot create VARRAY column with embedded LOB"
// *Cause: An attempt was made to create a column of a VARRAY type which
// has an embedded LOB attribute. The LOB could be an attribute of
// a subtype of the declared type of VARRAY's element.
// *Action: Remove offending attribute from type. If it is a subtype attribute
// then declare the VARRAY column NOT SUBSTITUTABLE.
02349, 00000, "invalid user-defined type - type is incomplete"
// *Cause: An attempt was made to use an incomplete type definition as a
// column or table datatype.
// *Action: Complete the type definition and retry the operation.
/
/
/
/ 2351 - 2375 Directh Path API errors
/ - 2356, 2366, 2371, & 2373: direct loader errors
/ - 2351 - 2355,
/ 2357 - 2365,
/ 2367 - 2370,
/ 2372,
/ 2374 - 2375:
/ see also range 2476 - 2479 for Parallel Direct Loader errors
/ and range 26000 - 26099 for additional Direct Path Load errors
/
02351, 00000, "internal error: %s\n"
// *Cause: An unexpected error condition was detected.
// *Action: Make a note of the error number and message and contact
// Oracle Support Services.
02352, 00000, "error setting an OCI attribute: %s\n"
// *Cause: An OCI error has occurred.
// *Action: The table or column referenced may not be accessible. Contact
// Oracle Support Services if the problem cannot be resolved.
02353, 00000, "error fetching an OCI attribute: %s\n"
// *Cause: An OCI error has occurred.
// *Action: The table or column referenced may not be accessible. Contact
// Oracle Support Services if the problem cannot be resolved.
02354, 00000, "error in exporting/importing data\n%s"
// *Cause: An error has occurred in a stream export or import operation.
// This message will be followed by another message giving more
// details about this error.
// *Action: See export/import documentation for an explanation of the second
// error message.
02355, 00000, "error opening file: %s\n"
// *Cause: An attempt to open the specified file for data export/import failed.
// *Action: Review the error message. Resolve the problem and retry the
// the operation. Contact Oracle Support Services if
// the problem cannot be resolved.
02356, 00000, "The database is out of space. The load cannot continue"
// *Cause: The load was discontinued due to space exhaustion in the database.
// *Action: Add space for the specified table.
02357, 00000, "header in file %s may not contain correct information\n"
// *Cause: The header may be corrupted.
// *Action: Contact Oracle Support Services.
02358, 00000, "error in exporting or importing data\n"
// *Cause: An error has occurred in a stream export or import operation.
// *Action: Contact Oracle Support Services.
02359, 00000, "database version in file %s is not valid\n"
// *Cause: The specified file could not be used for this load because
// its database version was not compatible with the database version
// in the other files in the DUMPFILE clause.
// *Action: Verify all the files in the DUMPFILE clause are from
// the same unload operation.
02360, 00000, "fatal error during data export/import initialization\n"
// *Cause: An unexpected error occurred during initialization for data
// export/import.
// *Action: Contact Oracle Support Services.
02361, 00000, "error while attempting to allocate %d bytes of memory\n"
// *Cause: An error occurred while trying to allocate memory. This is likely
// caused by insufficient memory.
// *Action: Reconnect to the instance and retry the operation.
02362, 00000, "error closing file: %s\n"
// *Cause: An attempt to close the specified file for data export/import failed.
// *Action: Review the error message. Resolve the problem and retry the
// the operation. Contact Oracle Support Services if
// the problem cannot be resolved.
02363, 00000, "error reading from file: %s\n"
// *Cause: An attempt to read from the specified file for data export/import
// failed.
// *Action: Review the error message. Resolve the problem and retry the
// the operation. Contact Oracle Support Services if
// the problem cannot be resolved.
02364, 00000, "error writing to file: %s\n"
// *Cause: An attempt to write to the specified file for data export or import
// failed.
// *Action: Review the error message. Resolve the problem and retry the
// the operation. Contact Oracle Support Services if
// the problem cannot be resolved.
02365, 00000, "error seeking in file: %s\n"
// *Cause: An attempt to seek to the specified position in file failed.
// *Action: Review the error message. Resolve the problem and retry the
// the operation. Contact Oracle Support Services if
// the problem cannot be resolved.
02366, 00000, "The following index(es) on table %s were processed:"
// *Cause: The table had some indexes which were loaded if there were no errors.
// *Action: none.
02367, 00000, "read ended but had expected more data from file %s\n"
// *Cause: A truncated or incomplete file was used for the load operation.
// *Action: Verify unload operation completed successfully and that the
// files had not been accidentally truncated.
02368, 00000, "the following file is not valid for this load operation\n"
// *Cause: A file could not be used for this load.
// See the following message for more information.
// *Action: Verify all the files in the DUMPFILE clause are from
// the same unload operation and that the unload was successful.
02369, 00000, "internal number in header in file %s is not valid\n"
// *Cause: The specified file could not be used for this load because the
// internal number in the header was not valid.
// *Action: If the dump files were transferred over, verify the
// transfer operation was done correctly.
02370, 00000, "internal metadata in file %s is not valid\n"
// *Cause: The specified file could not be used for this load because the
// internal metadata stored in this file does not match the metadata
// stored in the first file piece set.
// *Action: Verify all the files in the DUMPFILE clause are from
// the same unload operation.
02371, 00000, "Loader must be at least version %s.%s.%s.%s.%s for direct path"
// *Cause: The loader being used is incompatible with this version of the
// kernel.
// *Action: Upgrade your loader to at least the specified version or use the
// conventional path.
02372, 00000, "data for row: %*.*s \n"
// *Cause: A conversion error occurred while loading data into a table. The
// message shows values for the field in the row that had
// the conversion error.
// *Action: None. This is only an informational message.
02373, 00000, "Error parsing insert statement for table %s."
// *Cause: self-evident.
// *Action: Check the error given below this one.
02374, 00000, "conversion error loading table %*.*s.%*.*s"
// *Cause: A row could not be loaded into the table because there was a
// conversion error for one or more columns in a row.
// *Action: See the message that follows for more information about the row
// that could not be loaded. To avoid this error, make sure the
// definition of the table being imported matches the definition of
// the table being exported.
02375, 0, "conversion error loading table %*.*s.%*.*s partition %*.*s"
// *Cause: A row could not be loaded into the table because there was a
// conversion error for one or more columns in a row.
// *Action: See the message that follows for more information about the row
// that could not be loaded. To avoid this error, make sure the
// definition of the table being imported matches the definition of
// the table being exported.
/
/ 2376 - 2399 Resource limit errors
/
02376, 00000, "invalid or redundant resource"
// *Cause: a create, or alter profile command which names a resource not
// yet defined, or try to specify same resource twice.
// *Action: define resource first
02377, 00000, "invalid profile limit %s"
// *Cause: A value of 0 or lower was specified for the limit.
// *Action: Specify a limit greater than 0. For password profile parameters,
// some additional restrictions apply:
// * For the INACTIVE_ACCOUNT_TIME profile parameter, the specified
// limit cannot be less than 15 days.
// * For the PASSWORD_GRACE_TIME profile parameter, 0 is allowed
// as a permissible value.
02378, 00000, "duplicate resource name %s"
// *Cause:
// *Action:
02379, 00000, "profile %s already exists"
// *Cause: Try to create a profile which already exist
// *Action:
02380, 00000, "profile %s does not exist"
// *Cause: Try to assign a user to a non-existant profile
// *Action:
02381, 00000, "cannot drop PUBLIC_DEFAULT profile"
// *Cause: Try to drop PUBLIC_DEFAULT profile
// *Action:
02382, 00000, "profile %s has users assigned, cannot drop without CASCADE"
// *Cause:
// *Action:
02383, 00000, "illegal cost factor"
// *Cause: Negative or UNLIMITED cost for this resourc
// *Action:
02390, 00000, "exceeded COMPOSITE_LIMIT, you are being logged off"
// *Cause:
// *Action:
02391, 00000, "exceeded simultaneous SESSIONS_PER_USER limit"
// *Cause: An attempt was made to exceed the maximum number of
// concurrent sessions allowed by the SESSION_PER_USER clause
// of the user profile.
// *Action: End one or more concurrent sessions or ask the database
// administrator to increase the SESSION_PER_USER limit of
// the user profile.
02392, 00000, "exceeded session limit on CPU usage, you are being logged off"
// *Cause:
// *Action:
02393, 00000, "exceeded call limit on CPU usage"
// *Cause:
// *Action:
02394, 00000, "exceeded session limit on IO usage, you are being logged off"
// *Cause:
// *Action:
02395, 00000, "exceeded call limit on IO usage"
// *Cause:
// *Action:
02396, 00000, "exceeded maximum idle time, please connect again"
// *Cause: as stated
// *Action:
02397, 00000, "exceeded PRIVATE_SGA limit, you are being logged off"
// *Cause: Only when using TP monitor
// *Action: expand limit
02398, 00000, "exceeded procedure space usage"
// *Cause: Stored procedured used up too much space in SYSTEM Tablespace
// *Action: Use less stored procedure
02399, 00000, "exceeded maximum connect time, you are being logged off"
// *Cause: As stated
// *Action:
/
/ 2400 - 2479 EXPLAIN facility errors
/
02400, 00000, "explain plan output buffer size limit exceeded"
// *Cause: Internally this error is raised and caught to handle cases where
// the plan output exceeds te buffer size. The output is truncated in
// cases.
// *Action: This error should never be seen externally.
02401, 00000, "cannot EXPLAIN view owned by another user"
// *Cause: The view specified in the SQL statement belongs to another user
// and cannot be explained.
// *Action: Create a view with the same definition that belongs to
// current user.
02402, 00000, "PLAN_TABLE not found"
// *Cause: The table used by EXPLAIN to store row source information does
// not exist in the current schema.
// *Action: Create a plan table in the current schema or use the INTO clause
// of the statement to put the results of the explain command in an
// existing plan table.
02403, 00000, "plan table does not have correct format"
// *Cause: The explicit plan table does not have the appropriate field
// definitions.
// *Action: Redefine the plan table to have the appropriate field definitions.
02404, 00000, "specified plan table not found"
// *Cause: The specified plan table does cannot be found.
// *Action: Create the specified plan table or use an existing plan table.
02405, 00000, "invalid sql plan object provided"
// *Cause: The user provided a NULL, empty, or malformed object of type
// SQL_PLAN_TABLE_TYPE
// *Action: Provide a new, properly formed object to the function
/
/ 2420 - 2429 Schema errors
/
02420, 00000, "missing schema authorization clause"
// *Cause: the AUTHORIZATION clause is missing from a create schema
// statement.
// *Action: Preceed the schema authorization identifier with the
// AUTHORIZATION keyword.
02421, 00000, "missing or invalid schema authorization identifier"
// *Cause: the schema name is missing or is incorrect in an authorization
// clause of a create schema statement.
// *Action: If the name is present, it must be the same as the current
// schema.
02422, 00000, "missing or invalid schema element"
// *Cause: A statement other than a create table, create view, or grant
// privilege appears in a create schema statement.
// *Action: Self-evident.
02423, 00000, "schema name does not match schema authorization identifier"
// *Cause: a table definition with a schema name prepended to the table
// name does not match the schema name provided in the authorization
// clause of a create schema statement.
// *Action: make sure the schema names match.
02424, 00000, "potential circular view references or unknown referenced tables"
// *Cause: the create schema statement contains views that depend on other
// views in the containing create schema statement or they contain
// references to unknown tables.
// *Action: create the dependent views in a separate create schema statement
// and make sure all referenced tables are either defined in the
// create schema statement or exist outside the statement.
02425, 00000, "create table failed"
// *Cause: a create table statement failed in the create schema statement.
// *Action: the cause for failure will be presented below this error message.
// Follow appropriate action(s) as suggested by the subsequent error
// message.
02426, 00000, "privilege grant failed"
// *Cause: a grant privilege statement failed inthe create schema statement.
// *Action: the cause for failure will be presented below this error message.
// Follow appropriate action(s) as suggested by the subsequent error
// message.
02427, 00000, "create view failed"
// *Cause: a create view statement failed in the create schema statement.
// *Action: the cause for failure will be presented below this error message.
// Follow appropriate action(s) as suggested by the subsequent error
// message.
02428, 00000, "could not add foreign key reference"
// *Cause: could not add a foreign key reference because of error in
// declaration. Either referenced table does not exist or
// table does not have an unique key.
// *Action: make sure referenced table exists and/or has unique key
02429, 00000, "cannot drop index used for enforcement of unique/primary key"
// *Cause: user attempted to drop an index that is being used as the
// enforcement mechanism for unique or primary key.
// *Action: drop the constraint instead of the index.
/
/ 2430 - Enable/Disable Constraint Error Messages - continued
/
02430, 00000, "cannot enable constraint (%s) - no such constraint"
// *Cause: the named constraint does not exist for this table.
// *Action: Obvious
02431, 00000, "cannot disable constraint (%s) - no such constraint"
// *Cause: the named constraint does not exist for this table.
// *Action: Obvious
02432, 00000, "cannot enable primary key - primary key not defined for table"
// *Cause: Attempted to enable a primary key that is not defined for the table.
// *Action: Need to add a primary key definition for the table.
02433, 00000, "cannot disable primary key - primary key not defined for table"
// *Cause: Attempted to disable a primary key tht is not defined for the
// table.
// *Action: None
02434, 00000, "cannot enable unique(%s) - unique key not defined for table"
// *Cause: attempted to enable a unique key that is not defined for the table.
// *Action: None
02435, 00000, "cannot disable unique(%s) - unique key not defined for table"
// *Cause: attempted to disable a unique key that is not deined for the table.
// *Action: None
02436, 00000, "date or system variable wrongly specified in CHECK constraint"
// *Cause: An attempt was made to use a date constant or system variable,
// such as USER, in a check constraint that was not completely
// specified in a CREATE TABLE or ALTER TABLE statement. For
// example, a date was specified without the century.
// *Action: Completely specify the date constant or system variable.
// Setting the event 10149 allows constraints like "a1 > '10-MAY-96'",
// which a bug permitted to be created before version 8.
02437, 00000, "cannot validate (%s.%s) - primary key violated"
// *Cause: attempted to validate a primary key with duplicate values or null
// values.
// *Action: remove the duplicates and null values before enabling a primary
// key.
02438, 00000, "Column check constraint cannot reference other columns"
// *Cause: attempted to define a column check constraint that references
// another column.
// *Action: define it as a table check constriant.
02439, 00000, "Unique index on a deferrable constraint is not allowed"
// *Cause: attempted to enable a deferrable primary key/unique constraint
// that has an existing unique index on the constraint columns.
// *Action: Drop the index on the constraint columns or make the constraint
// not deferrable.
02440, 00000, "Create as select with referential constraints not allowed"
// *Cause: create table foo (... ref. con. ...) as select ...;
// *Action: Create the table as select, then alter the table to add the
// constraints afterwards.
02441, 00000, "Cannot drop nonexistent primary key"
// *Cause: alter table drop primary key - primary key does not exist.
// *Action: None
02442, 00000, "Cannot drop nonexistent unique key"
// *Cause: alter table drop unique (<col list>) - unique specification
// does not exist.
// *Action: make sure column list for unique constraint is correct.
02443, 00000, "Cannot drop constraint - nonexistent constraint"
// *Cause: alter table drop constraint <constraint_name>
// *Action: make sure you supply correct constraint name.
02444, 00000, "Cannot resolve referenced object in referential constraints"
// *Cause: attempted to define foreign key referencing an object which
// cannot be resolved to a base table reference
// *Action: referential constraints can only be defined on objects which
// can be resolve to base table reference
02445, 00000, "Exceptions table not found"
// *Cause: the explicity or implicity declared exceptions table does not
// exist.
// *Action: Create the table then issue the enable command again.
02446, 00000, "CREATE TABLE ... AS SELECT failed - check constraint violated"
// *Cause: An attempt was made to use a CREATE TABLE ... AS SELECT statement
// when some rows violated one or more CHECK constraints.
// *Action: Do not select rows that violate constraints.
02447, 00000, "cannot defer a constraint that is not deferrable"
// *Cause: An attempt was made to defer a nondeferrable constraint
// *Action: Drop the constraint and create a new one that is deferrable
02448, 00000, "constraint does not exist"
// *Cause: The named constraint does not exist
// *Action: Stop trying to do something with a nonexistant constraint
02449, 00000, "unique/primary keys in table referenced by foreign keys"
// *Cause: An attempt was made to drop a table with unique or
// primary keys referenced by foreign keys in another table.
// *Action: Before performing the above operations the table, drop the
// foreign key constraints in other tables. You can see what
// constraints are referencing a table by issuing the following
// command:
// SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam";
/
/ 2450 - 2475 Parse and execution errors for hashed clusters
/
02450, 00000, "Invalid hash option - missing keyword IS"
// *Cause: Missing IS keyword.
// *Action: Specify HASH IS option.
02451, 00000, "duplicate HASHKEYS specification"
// *Cause: The HASHKEYS option is specified more than once.
// *Action: Only specify the HASHKEYS option once.
02452, 00000, "invalid HASHKEYS option value"
// *Cause: The specified HASHKEYS option must be an integer value.
// *Action: Specify an appropriate value.
02453, 00000, "duplicate HASH IS specification"
// *Cause: The HASH IS option is specified more than once.
// *Action: only specify the HASH IS option once.
02454, 00000, "Number of hash keys per block (%s) exceeds maximum of %s"
// *Cause: The SIZE argument is too small.
// *Action: Increase the SIZE argument.
02455, 00000, "The number of cluster key column must be 1"
// *Cause: When specifing the HASH IS option, the number of key columns
// must be 1.
// *Action: Either do not specify the HASH IS option or reduce the number
// of key columns.
02456, 00000, "The HASH IS column specification must be NUMBER(*,0)"
// *Cause: The column specification must specify an integer.
// *Action: Specify the column definition as type NUMBER(precision, 0).
02457, 00000, "The HASH IS option must specify a valid column"
// *Cause: The HASH IS column name is not specified in the cluster
// definition.
// *Action: Specify a valid column name.
02458, 00000, "HASHKEYS must be specified for a HASH CLUSTER"
// *Cause: The HASHKEYS option must be specified when creating a HASH CLUSTER.
// *Action: Specify the HASHKEYS option.
02459, 00000, "Hashkey value must be a positive integer"
// *Cause: The value of the hash key was not a positive number.
// *Action: Specify a positive integer.
02460, 00000, "Inappropriate index operation on a hash cluster"
// *Cause: An attempt to create a cluster index was issued on a hash cluster.
// *Action: Do not attempt to create such an index.
02461, 00000, "Inappropriate use of the INDEX option"
// *Cause: This option is only valid for non hash clusters.
// *Action: Do not specify this option.
02462, 00000, "Duplicate INDEX option specified"
// *Cause: The INDEX option is specified more than once.
// *Action: Only specify the INDEX option once.
02463, 00000, "Duplicate HASH IS option specified"
// *Cause: The HASH IS option is specified more than once.
// *Action: Only specify the HASH IS option once.
02464, 00000, "Cluster definition can not be both HASH and INDEX"
// *Cause: The cluster can either be a hash or indexed cluster - not both.
// *Action: Remove either the HASH IS or INDEX options.
02465, 00000, "Inappropriate use of the HASH IS option"
// *Cause: This option is only valid for clusters
// *Action: Do not specify this option
02466, 00000, "The SIZE and INITRANS options cannot be altered for HASH CLUSTERS."
// *Cause: An attempt was made to change the SIZE and INITRANS options after
// the hash cluster was created.
// *Action: Do not specify this option.
02467, 00000, "Column referenced in expression not found in cluster definition"
// *Cause: A column in the hash is expression was not present in cluster
// definition.
// *Action: Recreate the cluster and correct the error in hash expression.
02468, 00000, "Constant or system variable wrongly specified in expression"
// *Cause: A constant or system variable was specified in the hash expression.
// *Action: Recreate the cluster and correct the error in hash expression.
02469, 00000, "Hash expression does not return an Oracle Number."
// *Cause: Result of evaluating hash expression is not an Oracle Number.
// *Action: Recreate the cluster and correct the error in hash expression.
02470, 00000, "TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression."
// *Cause: An attempt was made to specify SYSDATE, UID, USER, ROWNUM, or LEVEL
// in hash expression.
// *Action: Re-create the cluster and correct the error in hash expression.
02471, 00000, "SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expression."
// *Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expressions.
// *Action: Recreate the cluster and remove the offending keywords.
02472, 00000, "PL/SQL functions not allowed in hash expressions"
// *Cause: A PL/SQL function was used in the hash expression.
// *Action: Recreate the cluster and remove the PL/SQL function.
02473, 00000, "Error while evaluating the cluster's hash expression."
// *Cause: An error occurred while evaluating the clusters hash expression.
// *Action: Correct the query and retry.
02474, 00000, "Fixed hash area extents used (%s) exceeds maximum allowed (%s)"
// *Cause: The number of extents required for creating the fixed hash
// area exceeds the maximum number allowed.
// *Action: Reduce the number of extents required by increasing the extent
// allocation sizes within the STORAGE clause.
02475, 00000, "maximum cluster chain block count of %s has been exceeded"
// *Cause: The number of blocks in a cluster chain exceeds the maximum
// number allowed.
// *Action: Increase SIZE parameter in CREATE CLUSTER statement or reconsider
// suitability of cluster key.
/
/ 2476 - 2479 Reserved for Parallel Direct Loader Errors
02476, 00000, "can not create index due to parallel direct load on table"
// *Cause: A parallel direct load is occurring to the specified table.
// *Action: Retry statement after load is complete.
02477, 00000, "can not perform parallel direct load on object %s"
// *Cause: A parallel direct load is not possible because an index is
// is being created on the table.
// *Action: Retry load after index creation is complete.
02478, 00000, "merge into base segment would overflow MAXEXTENTS limit"
// *Cause: Merge of temporary segment into base segment failed because
// MAXEXTENTS was larger than the total in the temp and base segments
// *Action: Use a larger value for MAXEXTENTS on the base segment or make the
// extents in the temporary segments larger
02479, 00000, "error while translating file name for parallel load"
// *Cause: An invalid file name was specified to load data into.
// *Action: Specify a valid database file.
/
/ 2480 - 2489 Trace facility errors
/
02481, 00000, "Too many processes specified for events (max %s)"
// *Cause: Too many processes specified than allowed per event.
// *Action: Enter fewer processes by using ranges or wildcards if possible.
02482, 00000, "Syntax error in event specification (%s)"
// *Cause: Illegal event string
// *Action: Enter a legal event string
02483, 00000, "Syntax error in process specification (%s)"
// *Cause: Illegal process string
// *Action: Enter a legal process string
02484, 00000, "Invalid _trace_buffers parameter specification (%s)"
// *Cause: Bad process or size in _trace_buffers INIT.ORA parameter.
// *Action:
02485, 00000, "Invalid _trace_options parameter specification (%s)"
// *Cause: Bad syntax for _trace_options INIT.ORA parameter.
// *Action:
02486, 00000, "Error in writing trace file %s"
// *Cause: Error occurred in creating/writing the file.
// *Action: Check file name and make sure it is constructed properly.
// Also, check permissions for directories.
02487, 00000, "Error in converting trace data"
// *Cause: Incompatible binary trace data was specified.
// *Action: Check the format of the input data.
02488, 00000, "Error encountered when accessing file [%s] for trace conversion"
// *Cause: An attempt was made to open or access the trace file during
// a trace conversion.
// *Action: Check the permissions for both input and output files.
// Also, check the file compatibility for the trace conversion.
/
/ 2490 - 2499 Reserved for Resizeable Datafiles
/
02490, 00000, "missing required file size in RESIZE clause"
// *Cause: No value was specified for the RESIZE clause.
// *Action: Use correct syntax.
02491, 00000, "missing required keyword ON or OFF in AUTOEXTEND clause"
// *Cause: The keyword ON or OFF was not specified for the AUTOEXTEND clause.
// *Action: Use correct syntax.
02492, 00000, "missing required file block increment size in NEXT clause"
// *Cause: No value was specified for the NEXT clause.
// *Action: Use correct syntax.
02493, 00000, "invalid file increment size in NEXT clause"
// *Cause: A non-integer value was used for the NEXT clause of the DATAFILE
// list.
// *Action: Use correct syntax.
02494, 00000, "invalid or missing maximum file size in MAXSIZE clause"
// *Cause: UNLIMITED was not specified, or an invalid integer value was
// specified, for the MAXSIZE clause in the DATAFILE file list.
// The MAXSIZE value cannot be smaller than the SIZE value.
// *Action: Use correct syntax.
02495, 00000, "cannot resize file %s, tablespace %s is read only"
// *Cause: An attempt was made to resize a data file in a tablespace that
// is read only.
// *Action: Change the tablespace to read/write and retry the resize operation.
02496, 00000, "cannot alter or drop an individual chunk tablespace"
// *Cause: An attempt was made to alter or drop an individual chunk tablespace
// which is part of a tablespace set.
// *Action: Use alter or drop only on the tablespace set.
/
/ 2500 - 2699 Reserved for Database Sharding errors
/
02500, 00000, "IN SHARD option already specified"
// *Cause: In the CREATE TABLESPACE, the IN SHARD option was specified more
// than once.
// *Action: Remove all but one of the IN SHARD options.
02501, 00000, "invalid option for CREATE TABLESPACE SET"
// *Cause: An invalid option IN SHARD was specified for the CREATE
// TABLESPACE SET statement.
// *Action: Remove the invalid option.
02502, 00000, "USING TEMPLATE can only be used in CREATE TABLESPACE SET"
// *Cause: An attempt to specify the TEMPLATE option without the CREATE
// TABLESPACE SET statement failed.
// *Action: Specify the USING TEMPLATE option in the CREATE TABLESPACE SET
// statement.
02503, 00000, "USING TEMPLATE option already specified"
// *Cause: In the CREATE TABLESPACE SET, the USING TEMPLATE option was
// specified more than once.
// *Action: Remove all but one of the USING TEMPLATE options.
02504, 00000, "SHARDSPACE does not exist"
// *Cause: A nonexistent SHARDSPACE was specified in the CREATE
// TABLESPACE or CREATE TABLESPACE SET statement.
// *Action: Reissue the CREATE TABLESPACE or CREATE TABLESPACE SET statement
// with valid SHARDSPACE name.
02505, 00000, "IN SHARDSPACE option already specified"
// *Cause: In the CREATE TABLESPACE SET, the IN SHARDSPACE option was
// specified more than once.
// *Action: Remove all but one of the IN SHARDSPACE options.
02506, 00000, "CREATE TABLESPACE SET statement requires the SHARDSPACE keyword"
// *Cause: The SHARDSPACE option was not specified in the CREATE TABLESPACE SET
// statement.
// *Action: Correct the syntax. Insert the missing keyword where required and
// then retry the statement.
02507, 00000, "missing SHARDSPACE keyword"
// *Cause: The SHARDSPACE keyword was omitted in the IN SHARDSPACE option.
// *Action: Correct the syntax. Insert the keyword SHARDSPACE where required and
// then retry the statement.
02508, 00000, "attempted to create a shard tablespace in a non-shard database"
// *Cause: An attempt was made to create a shard tablespace in a non-shard
// database.
// *Action: Deploy the sharding environment before creating a shard
// tablespace.
02509, 0000, " A SHARDSPACE cannot handle several PARTITIONSETS."
// *Cause: An attempt was made to define multiple PARTITIONSETS in
// the SHARDSPACE.
// *Action: Specify the different PARTITIONSETS in different SHARDSPACES.
02510, 0000, " A tablespace set cannot be referenced at the table level."
// *Cause: An attempt was made to reference a tablespace set at the table
// level.
// *Action: Remove the reference to the tablespace set at the table level.
02511, 0000, "SQL query not allowed; the shard DDL is disabled."
// *Cause: An attempt was made to run a shard DDL on a nondeployed shard
// or with the shard DDL option disabled.
// *Action: Deploy the shards or enable shard DDL before executing the
// DDL.
02512, 00000, "only one PARTITIONSET option may be specified"
// *Cause: The CREATE TABLE statement contained more than one PARTITIONSET
// option.
// *Action: Specify PARTITIONSET option at most once in the CREATE SHARDED
// TABLE statement.
02513, 00000, "invalid sharded table PARTITIONSET method"
// *Cause: An invalid PARTITIONSET method was specified in the CREATE TABLE
// statement. A table may be partitioned by RANGE or LIST.
// *Action: Modify PARTITIONSET method to RANGE or LIST in the CREATE SHARDED
// TABLE statement.
02514, 00000, "list PARTITIONSET method expects a single partitioning column"
// *Cause: The number of columns in a PARTITIONSET column list exceeded
// the legal limit of one for list partitioned tables.
// *Action: Modify PARTITIONSET column list so that it consists of at
// most one column.
02515, 00000, "cannot interval partition set a sharded table"
// *Cause: Interval PARTITIONSET was not supported for a sharded table.
// *Action: Use a LIST or RANGE PARTITIONSET instead.
02516, 00000, "invalid SHARDED type specified"
// *Cause: Only tables can have the SHARDED type.
// *Action: Remove the SHARDED option.
02517, 00000, "PARTITIONSET and CLUSTER clauses are mutually exclusive"
// *Cause: definition of a table with both PARTITIONSET and CLUSTER
// clauses which is illegal.
// *Action: Remove the PARTITIONSET or the CLUSTER clause.
02518, 00000, "invalid PARTITIONSET clause specified in a non sharded table"
// *Cause: definition of a non sharded table with PARTITIONSET clause
// is illegal.
// *Action: remove the PARTITIONSET clause.
02519, 00000, "cannot perform cross-shard operation. Chunk \"%s\" is unavailable"
// *Cause: All shards where this chunk is stored were unavailable.
// *Action: Rerun the command when the shards become avalaible.
02520, 00000, "Shard data object number exceeds UB4MAXVAL"
// *Cause: All shards where this chunk is stored were unavailable.
// *Action: Rerun the command when the shards become available.
02521, 00000, "attempted to enable shard DDL in a non-shard database"
// *Cause: An attempt was made to enable shard DDL in a non-shard database.
// *Action: Deploy the sharding environment before enabling shard DDL.
02522, 00000, "cannot get a new data object number range from the Global Data Services (GDS) catalog"
// *Cause: An attempt was made to get a new range of data object numbers which
// resulted in a failure.
// *Action: Check that the shard can connect to the catalog.
02523, 00000, "The table being created is not SHARDED."
// *Cause: PARENT clause was specified on a non-sharded table.
// *Action: Create a SHARDED table or remove the PARENT clause.
02524, 00000, "Invalid parent table specified."
// *Cause: The parent table specified was not a valid identifier.
// *Action: Check that the parent table specified is valid.
02525, 00000, "child and parent table owner mismatch."
// *Cause: The child and parent tables did not have the same owner.
// *Action: Check the owner of the child table.
02526, 00000, "child and parent table sharding method mismatch."
// *Cause: The child and parent tables did not have the same sharding method.
// *Action: Ensure the sharding method for the two tables is the same.
02527, 00000, "child and parent table shard key columns mismatch."
// *Cause: The child and parent tables did not have the same shard key columns.
// *Action: Ensure the shard key for the two tables is the same.
02528, 00000, "child and table partition set key columns mismatch."
// *Cause: The child and parent tables did not have the same partition set key
// columns.
// *Action: Ensure the partition set key for the two tables is the same.
02529, 00000, "invalid parent table."
// *Cause: The table name specified was not the one of the root table.
// *Action: Check the root table name specified.
02530, 00000, "parent table not specified"
// *Cause: An attempt was made to create a child table without specifying
// the PARENT clause.
// *Action: Specify the PARENT clause in the CREATE SHARDED TABLE command.
02531, 00000, "shard name not found"
// *Cause: An attempt was made to create a sharded table on a non-sharded
// database.
// *Action: Ensure that the sharded database was deployed correctly.
02532, 00000, "sharding columns must form a subset key of key columns of a UNIQUE index"
// *Cause: An attempt was made to create a primary key constaint on non-sharding
// columns.
// *Action: Use the sharding columns as a prefix of key columns of a UNIQUE
// index.
02533, 00000, "missing PARTITION clause"
// *Cause: The PARTITION clause was expected but was not supplied.
// *Action: Add a PARTITION clause to the CREATE SHARDED TABLE command.
02534, 00000, "invalid PARTITION clause"
// *Cause: The PARTITION clause was supplied with CONSISTENT HASH sharding.
// *Action: Remove the PARTITION specification.
02535, 00000, "missing TABLESPACE SET clause"
// *Cause: The TABLESPACE SET clause was expected but was not supplied.
// *Action: Add the TABLESPACE SET clause to the CREATE SHARDED TABLE command.
02536, 00000, "invalid TABLESPACE SET name: %s"
// *Cause: The TABLESPACE SET supplied did not exist.
// *Action: Supply a valid TABLESPACE SET.
02537, 00000, "Data file name specified but not supported by tablespace set template"
// *Cause: Data file explicit name was specified as part of the tablespace set
// template. Only Oracle Managed Files are supported by a tablespace set.
// *Action: Remove the file name from the data file definition.
02538, 00000, "invalid TABLESPACE SET clause"
// *Cause: The TABLESPACE SET clause was not expected.
// *Action: Remove the keyword SET to specify just TABLESPACE.
02539, 00000, "the operation is not supported across shards"
// *Cause: An attempt was made to perform an operation with shard DDL enabled,
// which is not supported for propagation from catalog to shards.
// *Action: Disable the shard DDL to perform the operation on the catalog and
// go to each individual shard to perform the operation locally.
02540, 00000, "global indexes are not supported for sharded tables"
// *Cause: An attempt was made to create a global index on a sharded
// table, which is not supported.
// *Action: Create a local index instead.
02541, 00000, "TABLESPACE SET is required"
// *Cause: The TABLESPACE SET clause was not supplied when creating an index
// on a system-managed sharded table.
// *Action: Add the TABLESPACE SET clause to the CREATE INDEX command, or
// use the same tablespace set as the table by not specifying
// the TABLESPACE SET clause.
02542, 00000, "invalid partitioning method specified with user-defined sharding"
// *Cause: The partitioning method specified was not compatible with user-defined sharding.
// *Action: Choose a supported partitioning method.
02543, 00000, "invalid partitioning method specified with system-managed or composite sharding"
// *Cause: The partitioning method specified was not compatible with system-managed
// or composite sharding.
// *Action: Choose a supported partitioning method.
02544, 00000, "sharding or partition set column datatype is not supported"
// *Cause: Supported data types were not used for the sharding or partition set columns.
// *Action: Use the supported data types for sharding or partition set columns.
02545, 00000, "sharding or partition set column can not be a virtual column"
// *Cause: Virtual column was used in the sharding or partition set key,
// which is not supported.
// *Action: Remove the virtual column from the sharding or partition set key.
02546, 00000, "The LONG data type is not supported for duplicated tables."
// *Cause: An invalid option was specified while creating duplicated tables.
// *Action: Verify the specified option.
02547, 00000, "Option %s is not supported for duplicated tables"
// *Cause: An invalid option was specified while creating duplicated tables.
// *Action: Verify the specified option.
02548, 00000, "Option %s is not supported for duplicated tables"
// *Cause: An invalid option was specified while altering duplicated tables.
// *Action: Verify the specified option.
02549, 00000, "cannot create a sharded table with index organization"
// *Cause: An attempt was made to create an index-organized sharded table
// under system-managed sharding or composite sharding, which is
// not supported.
// *Action: Create a heap-organized table and the primary key, or create the
// index-organized table with user-defined sharding.
/
02550, 00000, "Creating duplicated table not allowed when shard DDL is disabled"
// *Cause: Duplicated tables were created when shard DDL was disabled.
// *Action: Enable shard DDL.
02551, 00000, "Truncate table for duplicated tables is not supported"
// *Cause: Invalid operation was specified on a duplicated table.
// *Action: Use "delete from <table>" instead.
/
02552, 00000, "invalid shard name"
// *Cause: The shard name specified was not valid.
// *Action: Choose a valid shard.
/
02553, 00000, "TABLESPACE is required"
// *Cause: The TABLESPACE clause was not supplied when specifying a partition
// of a user-defined sharded table.
// *Action: Add the TABLESPACE clause.
/
02554, 00000, "invalid DROP TABLESPACE SET"
// *Cause: The DROP TABLESPACE SET command was not compatible with user-defined sharding.
// *Action: Choose a supported sharding method.
02555, 00000, "Online redefinition is not supported for sharded and duplicated tables."
// *Cause: An attempt was made to perform online redefinition on a sharded
// table or a duplicated table for sharding, which is not supported.
// *Action: Use the ALTER TABLE statement instead.
/
02556, 00000, "Only sharded or duplicated tables are supported across shards."
// *Cause: An attempt was made to create a non-sharded, non-duplicated table
// across shards, which is not supported.
// *Action: Connect to each shard and create the table locally.
/
02557, 00000, "cannot operate on sharded objects when shard DDL is disabled"
// *Cause: An attempt was made to operate on a sharded or a duplicated object
// across shards when the shard DDL was not enabled.
// *Action: Enable shard DDL to perform the operation.
/
02558, 00000, "cannot operate on non-sharded objects when shard DDL is enabled"
// *Cause: An attempt was made to ALTER or DROP a non-sharded object when
// the shard DDL was enabled.
// *Action: Disable shard DDL to perform the operation.
/
02559, 00000, "The TABLESPACE SET %s does not belong to the shardspace of the table."
// *Cause: The TABLESPACE SET supplied existed in a different shardspace from
// the one to which the table belonged.
// *Action: Supply a valid TABLESPACE SET in the shardspace of the table.
/
02560, 00000, "cannot modify partitions for system-managed or composite sharded tables."
// *Cause: An attempt was made to modify partitions on system-managed or
// composite sharded tables.
// *Action: Use the 'gdsctl split chunk' or 'move chunk' commands instead.
/
02561, 00000, "maximum number of columns in a duplicated table without primary key is 999"
// *Cause: An attempt was made to create a duplicated table with 1000
// columns when there was no primary key defined. Note that unused
// columns in the table are counted toward the 1000 column limit.
// *Action: Reduce the number of columns in the command and resubmit.
/
02562, 00000, "cannot create a duplicated table in a non-shard schema"
// *Cause: An attempt was made to create a duplicated table in a
// non-shard schema.
// *Action: Try creating the duplicated table in a sharded schema.
/
02563, 00000, "XMLType column in a duplicated table cannot be used in non-ASSM tablespace \"%s\""
// *Cause: XMLType column in a duplicated table required an automatic
// segment space management (ASSM) tablespace.
// *Action: Specify an ASSM tablespace for the XMLType column in a duplicated
// table.
02564, 00000, "rebuild outline is not supported across shards."
// *Cause: An attempt was made to rebuild an outline with shard DDL enabled,
// which is not supported.
// *Action: Connect to each shard and rebuild the outline locally.
/
02565, 00000, "cannot use individual chunk tablespace"
// *Cause: An individual chunk tablespace which was part of a tablespace set was used.
// *Action: Use a normal tablespace.
/
02566, 00000, "cannot create duplicated table - insufficient privileges"
// *Cause: An attempt was made to create a duplicated table when the user
// did not have sufficient privileges.
// *Action: Ensure that the user has CREATE DATABASE LINK and CREATE
// MATERIALIZED VIEW privileges before creating a duplicated table.
/
02567, 00000, "cannot create a sharded table with empty columns"
// *Cause: An attempt was made to create a sharded table without any columns.
// *Action: Use valid columns to create a sharded table.
/
02568, 00000, "cannot create an identity column in a sharded table"
// *Cause: An attempt was made to create a sharded table with an identity column.
// *Action: Create a sharded table without an identity column.
/
02569, 00000, "cannot drop a system tablespace %s when sharding environment is deployed"
// *Cause: An attempt was made to drop a system tablespace part of the sharding environment
// when the sharding environment was deployed.
// *Action: Do not drop a tablespace created by the system.
/
02570, 00000, "cannot alter user password - insufficient privileges"
// *Cause: An attempt was made to alter the password for a user who created
// duplicated tables but did not have the privilege to execute the
// ALTER DATABASE LINK statement.
// *Action: Ensure that the user, whose password has to be changed, has the
// ALTER DATABASE LINK privilege and try again.
/
02571, 00000, "ALTER TABLE TRUNCATE PARTITION for duplicated tables is not supported"
// *Cause: An invalid operation was specified on a duplicated table.
// *Action: Use DELETE FROM table_name PARTITION (partition_name) instead.
/
02572, 00000, "A non all-shard user cannot operate on schema objects that are sharded or duplicated on all shards."
// *Cause: An attempt was made to operate on a sharded or duplicated schema
// object by a non all-shard user.
// *Action: Operate on such objects as an all-shard user.
/
02573, 00000, "cannot enable shard DDL when current_schema has been changed"
// *Cause: Shard DDL is not supported after a session's current schema has
// been altered.
// *Action: Reconnect as the correct user to perform shard DDL operations.
/
02574, 00000, "Sharded table cannot be a nested table."
// *Cause: An attempt was made to create a nested sharded table, which is not
// supported.
// *Action: Create a non-nested sharded table.
/
02575, 00000, "Invalid sharding method for a deployed sharded database"
// *Cause: An invalid sharding method was set for a sharded database.
// *Action: Check the database configuration and correct the settings.
02576, 00000, "number of partition set specifications is not equal to the number of shardspaces"
// *Cause: Fewer or more number of partition set specifications were specified than the number of
// shardspaces in the composite sharding environment.
// *Action: Specify one partition set specification for each shardspace in the composite sharding
// environment.
/
02577, 00000, "cannot specify PARTITIONSET in a non-composite sharding environment"
// *Cause: PARTITIONSETS were specified while creating a sharded table in non-composite sharding
// environment.
// *Action: Remove the PARTITION SET specifications in the create sharded table statement.
/
02578, 00000, "missing PARTITIONSET specification"
// *Cause: PARTITIONSET specifications were missing.
// *Action: Specify PARTITIONSETS for the sharded table.
/
02579, 00000, "cannot create a tablespace set with SMALLFILE option"
// *Cause: An attempt was made to create a tablespace set with the SMALLFILE option.
// *Action: Create a tablespace set with the default BIGFILE option.
/
02580, 00000, "cannot add or drop data files from a tablespace set"
// *Cause: An attempt was made to add or drop a data file from a tablespace set.
// *Action: Do not add or drop a data file from a tablespace set.
/
02581, 00000, "cannot create foreign key constraints on columns referencing a duplicated table"
// *Cause: An attempt was made to create a foreign key constraint in a sharded table
// on a column referencing a duplicated table.
// *Action: Remove the foreign key constraint referencing a column in the duplicated table.
/
02582, 00000, "invalid tablespace set name specified for the partition set"
// *Cause: The tablespace set name specified for the partition set was either invalid or
// belonged to a different shardspace.
// *Action: Specify a tablespace set name that belongs to the same shardspace.
/
02583, 00000, "option PARALLEL not supported when creating duplicated table as select from another table"
// *Cause: An attempt was made to create a duplicated table as select from another table in parallel mode.
// *Action: Create a duplicated table as select without the PARALLEL clause.
/
02584, 00000, "INMEMORY options not supported for duplicated tables"
// *Cause: An attempt was made to create or alter a duplicated table by enabling INMEMORY options.
// *Action: Verify the specified option.
/
02585, 00000, "create tablepsace set failure, one of its tablespaces not created"
// *Cause: One of the tablespaces in the tablespace set was not created.
// *Action: Verify the creation of the tablespaces.
/
02586, 00000, "cannot change duplicated table refresh rate in a non-catalog database"
// *Cause: An attempt was made to change the dupl_table_refresh_rate in the non-catalog database.
// *Action: Connect to the catalog database to change the refresh rate of duplicated tables.
/
02587, 00000, "create duplicated table of Object Type is not supported"
// *Cause: An attempt was made to create a duplicated table of object type.
// *Action: Create a duplicated table without specifying the object type.
/
02588, 00000, "minimum refresh rate for duplicated table is 20 seconds"
// *Cause: An attempt was made to change the dupl_table_refresh_rate to less than 20 seconds.
// *Action: Set the refresh rate for duplicated tables to atleast 20 seconds.
/
02589, 00000, "invalid partition set name"
// *Cause: An invalid partition set name was specified.
// *Action: Specify a valid partition set name.
/
02590, 00000, "invalid sequence of partition sets"
// *Cause: The sequence used to specify partition sets was invalid.
// *Action: Specify the partition sets in an increasing order.
/
02591, 00000, "cannot specify a common tablespace set for indexes on a sharded table in composite sharding"
// *Cause: An attempt was made to specify a common tablespace set for indexes on a sharded table in a
// composite sharding environment which is not supported.
// *Action: Create an index on sharded tables without the TABLESPACE SET clause or use the PARTITIONSET clause
// to specify tablespace sets for each partition set.
/
02592, 00000, "cannot drop user until all shard databases are up and all gsm_requests are completed"
// *Cause: An attempt was made to drop a user who owns a duplicated table when the shard database was down or the gsm_requests were pending execution.
// *Action: Ensure that all gsm_requests are completed and all shards are up before dropping a user with duplicated table.
/
02593, 00000, "cannot drop duplicated table until all shard databases are up and all gsm_requests are completed"
// *Cause: An attempt was made to drop a duplicated table when the shard database was down or the gsm_requests were pending execution.
// *Action: Ensure that all gsm_requests are completed and all shards are up before dropping a duplicated table.
/
02594, 00000, "cannot alter shard user password until all shard databases are up and all gsm_requests are completed"
// *Cause: An attempt was made to alter shard user password when the shard database was down or the gsm_requests were pending execution.
// *Action: Ensure that all gsm_requests are completed and all shards are up before altering a shard user password.
/
02595, 00000, "Abstract data type is not supported for duplicated tables."
// *Cause: An invalid option was specified while creating duplicated tables.
// *Action: Verify the specified option.
/
02596, 00000, "cannot truncate duplicated table on a shard database"
// *Cause: An attempt was made to truncate a duplicated table on a shard database.
// *Action: Connect to the catalog database to truncate the duplicated table.
/
02597, 00000, "The read-only option is not supported for sharded tables."
// *Cause: An invalid option was specified while creating a sharded table.
// *Action: Verify the specified option.
/
02598, 00000, "tablespace specified in the SQL command does not exist in the shard"
// *Cause: A DROP or ALTER TABLESPACE operation was attempted on a shard where the tablespace does not exist.
// *Action: Create the tablespace in the shard first.
02599, 00000, "cannot drop partitionset column"
// *Cause: An attempt was made to drop a column used as the
// super-partitioning key for a sharded table.
// *Action: This action is not allowed.
/
02600, 00000, "credential name is invalid: %s"
// *Cause: An invalid credential name was specified.
// *Action: Verify credential name and retry the operation.
02601, 00000, "credential already exists: %s"
// *Cause: Credential name specified already used by an existing object.
// *Action: Verify credential name and retry the operation.
02602, 00000, "credential does not exist: %s"
// *Cause: The specified credential does not exist.
// *Action: Verify credential name and retry the operation.
02603, 00000, "file name is invalid: %s"
// *Cause: An invalid file name was specified.
// *Action: Verify credential name and retry operation.
02604, 00000, "file already exists: %s"
// *Cause: File name specified already used by an existing object.
// *Action: Verify filename and retry the operation.
02605, 00000, "file does not exist: %s"
// *Cause: The specified file does not exist.
// *Action: Verify file name and retry the operation.
02606, 00000, "destination name is invalid: %s"
// *Cause: An invalid destination name was specified.
// *Action: Verify destination name and retry the operation.
02607, 00000, "destination not specified"
// *Cause: A destination must be specified in the command.
// *Action: Provide destination and retry the operation.
02608, 00000, "destination does not exist: %s"
// *Cause: The specified destination does not exist.
// *Action: Verify destination and retry the operation.
02609, 00000, "remote scheduler agent not running"
// *Cause: The specified remote scheduler agent cannot be contacted.
// *Action: Confirm that the agent is running and retry the operation.
02610, 00000, "Remote job failed with error: %s"
// *Cause: Unable to successfully run specified job.
// *Action: Check errors returned and retry the operation.
02611, 00000, "shardgroup name is invalid: %s"
// *Cause: An invalid shardgroup name was specified.
// *Action: Verify the shardgroup name and retry the operation.
02612, 00000, "shardgroup does not exist: %s"
// *Cause: The specified shardgroup did not exist.
// *Action: Verify the shardgroup name and retry the operation.
02613, 00000, "shardspace name is invalid: %s"
// *Cause: An invalid shardspace name was specified.
// *Action: Verify the shardspace name and retry the operation.
02614, 00000, "shardspace does not exist: %s"
// *Cause: The specified shardspace did not exist.
// *Action: Verify the shardspace name and retry the operation.
02615, 00000, "Neither a shardgroup nor a shardspace name was specified."
// *Cause: A shardgroup or shardspace name was not specified.
// *Action: Update the parameters and retry the operation.
02616, 00000, "Both a shardgroup and a shardspace name were specified."
// *Cause: A shardgroup and a shardspace name were both specified.
// For this command, either a shardgroup or shardspace name
// may be specified, but not both.
// *Action: Update the parameters and retry the operation.
02617, 00000, "Neither a credential nor login information was specified"
// *Cause: Either a credential or login information must be specified.
// *Action: Update the parameters and retry the operation.
02618, 00000, "Both a credential and login information was specified"
// *Cause: For this command, either a credential or login information
// may be specified, not both.
// *Action: Update the parameters and retry the operation.
02619, 00000, "Both a file name and file contents were specified."
// *Cause: A file name and file contents were both specified.
// *Action: Update the parameters and retry the operation.
02620, 00000, "db_domain value too long: %s"
// *Cause: The value specified for db_domain exceeded the 128 character limit.
// *Action: Modify the value specified for db_domain and retry the operation.
02621, 00000, "file in use by shard '%s'"
// *Cause: The specified file was in use by an undeployed shard.
// *Action: Drop the undeployed shard and retry the operation.
02622, 00000, "Shard is not open in write mode."
// *Cause: The shard was not opened in the correct mode.
// *Action: Open the shard in write mode and retry the operation.
02623, 00000, "Failed to create broker configuration with error %s."
// *Cause: A request to create the broker configuration failed.
// *Action: Check the broker logs for details.
02624, 00000, "Failed to enable broker configuration with error %s."
// *Cause: A request to enable the broker configuration failed.
// *Action: Check the broker logs for details.
02625, 00000, "Failed to add standby shard %s to the broker configuration with error %s."
// *Cause: A request to add the shard to the broker configuration failed.
// *Action: Check the broker logs for details.
02626, 00000, "Failed to enable standby shard %s for the broker configuration with error %s."
// *Cause: A request to enable the shard for the broker configuration failed.
// *Action: Check the broker logs for details.
02627, 00000, "Shardspace '%s' does not exist."
// *Cause: The requested shardspace did not exist.
// *Action: Check the name and try again.
02628, 00000, "invalid shardgroup name '%s'"
// *Cause: The shardgroup name was invalid.
// *Action: Use a different name for the shardgroup.
02629, 00000, "cannot modify deployed shardgroup %s"
// *Cause: The shardgroup was already deployed and could no longer be
// modified.
// *Action: Do not modify a deployed shardgroup. Delete it and add it
// again.
02630, 00000, "cannot modify primary or standby status of shardgroup %s"
// *Cause: The shardgroup already contained a shard and could
// not be converted from a primary shard to a standby shard
// or from a standby shard to a primary shard.
// *Action: Do not modify the primary or standby status of this shardgroup.
02631, 00000, "The shardspace name '%s' is invalid."
// *Cause: An invalid shardspace name was provided.
// *Action: Check the name and try again.
02632, 00000, "cannot modify deployed shardspace '%s'"
// *Cause: The shardspace was already deployed and could no longer be
// modified.
// *Action: Do not modify deployed shardspaces.
02633, 00000, "The shardspace '%s' is invalid."
// *Cause: An invalid shardpsace name was provided.
// *Action: Check the name and try again.
02634, 00000, "Oracle XML DB is not installed."
// *Cause: Oracle XML DB was required for remote scheduler agent configuration
// but was not installed.
// *Action: Install Oracle XML DB in the catalog database.
02635, 00000, "The value of chunks must be greater than one."
// *Cause: An invalid value of chunks was passed.
// *Action: Set chunks to a value greater than one.
02636, 00000, "Shard is already in shardspace %s."
// *Cause: The shard was already in a shardspace.
// *Action: Remove the shard from the sharding schema before adding
// it to another shardspace.
02637, 00000, "The source and target shards are in different shardgroups."
// *Cause: The source and target shards for a chunk move operation
// were in different shardgroups.
// *Action: Chunks cannot be moved across shardgroups. Specify a source and
// target shard that are in the same shardgroup.
02638, 00000, "The shardgroup %s is not deployed."
// *Cause: The containing shardgroup for the source and target shards
// was not yet deployed.
// *Action: Chunks cannot be moved until the shardgroup has been deployed.
// Deploy the shardgroup before moving chunks.
02639, 00000, "Source and target shards are the same."
// *Cause: The source and target shards for a chunk move were the same.
// *Action: Chunks cannot be moved to the same shard. Specify a different
// source and target.
02640, 00000, "Shardspace already has a primary shardgroup."
// *Cause: An attempt was made to add a primary shardgroup to a shardspace
// that already had a primary shardgroup. When Oracle Data
// Guard replication is used, only one primary shardgroup is
// allowed in each shardspace.
// *Action: Do not add another primary shardgroup to this shardspace.
02641, 00000, "Shard %s was not deployed because it does not contain a corresponding shard in all shardgroups."
// *Cause: The shard did not have a corresponding shard in all
// shardgroups in an Oracle Data Guard configuration, therefore it
// was not deployed.
// *Action: This is only a warning and the deployment will continue without
// this shard. In order to make use of this shard, either
// remove shardgroups, or add shards to other shardgroups
// so that there are the same number of shards in all shardgroups.
02642, 00000, "There were no new shards to deploy."
// *Cause: The 'deploy' command was issued, but there were no new shards
// to deploy.
// *Action: This is only a warning. Deploy may continue to recover previous
// deployment attempts, if any exist, but no new shards will be
// deployed.
02643, 00000, "failed to enable fast-start failover with error %s"
// *Cause: A request to enable fast-start failover failed.
// *Action: Check the broker logs for details.
02644, 00000, "Shard '%s' already exists in specified rack '%s'."
// *Cause: The specified rack already contained another shard in the same
// Oracle Data Guard configuration.
// *Action: Specify a different value for the rack parameter.
02645, 00000, "only one primary shard allowed per shardspace"
// *Cause: The specified shardspace already contained a primary shard.
// *Action: Specify a different shardspace or create a standby shard instead.
02646, 00000, "Standby shards not allowed in Oracle GoldenGate configurations."
// *Cause: The Oracle GoldenGate configurations contained standby shards.
// *Action: Create a primary shard instead of a standby shard.
02647, 00000, "The rack name '%s' is invalid."
// *Cause: An invalid rack name was provided.
// *Action: Check the name and try again.
02648, 00000, "Password for SYS account was not specified."
// *Cause: A SYS password was not specified when creating a new shard
// using Oracle Database Configuration Assistant (DBCA).
// *Action: Retry the operation and specify a SYS password.
02649, 00000, "cannot change region for a system-managed or composite shard"
// *Cause: An attempt was made to change the region value for a
// system-managed or composite shard.
// *Action: Change the region value at the shardgroup level instead.
02650, 00000, "remote scheduler agent error: %s"
// *Cause: An operation failed when performed using the remote scheduler agent.
// *Action: Correct the error specified in the remote scheduler agent output.
02651, 00000, "The specified pool '%s' is not sharded."
// *Cause: The specified pool was not sharded.
// *Action: Specify a sharded pool and retry the operation.
02652, 00000, "The maximum number of sharded GDS pools has been reached."
// *Cause: The maximum number of Global Data Services (GDS) sharded pools had
// been reached.
// *Action: No more Global Data Services (GDS) sharded pools can be added
// without first removing a pool.
02653, 00000, "shardgroup already exists: %s"
// *Cause: The specified shardgroup was already in existence.
// *Action: Verify the shardgroup name and retry the operation.
02654, 00000, "Shards and shardgroups cannot exist in the same database pool."
// *Cause: The specified database pool already contained either a conflicting
// shard or shardgroup.
// *Action: Verify the database pool name and retry the operation.
02655, 00000, "not a sharded catalog"
// *Cause: The catalog was not enabled for sharding and a sharding command
// was executed.
// *Action: Re-create the catalog with 'create shardcatalog' or
// verify the command issued.
02656, 00000, "shardspace already exists: %s"
// *Cause: The specified shardspace was already in existence.
// *Action: Verify the shardspace name and retry the operation.
02657, 00000, "too few chunks specified for shardspace"
// *Cause: The number of chunks in the specified shardspace was less than
// twice the number of shards in one of its shardgroups.
// *Action: If the shardspace is not deployed, modify the shardspace to
// increase the number of chunks it contains.
02658, 00000, "shardspace already exists: %s"
// *Cause: The specified shardspace was already in existence.
// *Action: Verify the shardspace name and retry the operation.
02659, 00000, "cannot remove a shard which contains chunks"
// *Cause: An attempt was made to remove a shard which currently
// contains chunks.
// *Action: Move the chunks to another shard and then retry the operation.
02660, 00000, "Shard '%s' was also removed."
// *Cause: When a shard was removed, all other shards in the same Oracle
// Data Guard configuration were also removed.
// *Action: This is an informational message only.
02661, 00000, "shardspace and shardgroup parameters are mutually exclusive"
// *Cause: A command was issued that included both the shardspace and
// and shardgroup parameters.
// *Action: Remove one of the conflicting parameters from the command.
02662, 00000, "Chunk number '%s' does not exist on the source database."
// *Cause: An invalid chunk number or source database was provided.
// *Action: Check the number and try again.
02663, 00000, "Remote scheduler agents may be listening on previously specified port."
// *Cause: The '-agent_port' parameter specified a new agent port value.
// The already registered scheduler agents must re-register with the
// catalog database to use this new value.
// *Action: This is only a warning. Re-register the existing scheduler agents
// as necessary.
02664, 00000, "Specified port may be in use."
// *Cause: The '-agent_port' parameter specified a new agent port value.
// The port specified may already have been in use by another process
// in the system.
// *Action: This is only a warning. Confirm that there is no port
// conflict before continuing the operation.
02665, 00000, "shardspace not specified"
// *Cause: A command was issued that did not include shardspace".
// *Action: Specify shardspace.
02666, 00000, "Tablespace set required to perform this operation was not found."
// *Cause: An attempt was made to perform a chunk management operation
// before creating a tablespace set.
// *Action: Create a tablespace set before issuing the command.
02667, 00000, "Root table required to perform this operation was not found."
// *Cause: An attempt was made to perform a chunk management operation
// before creating a sharded table.
// *Action: Create a sharded table before issuing the command.
02668, 00000, "Observer cannot be started for database \"%s\""
// *Cause: One or more conditions required by Data Guard observer were not met.
// *Action: Confirm that Data Guard technology is used for replication,
// the database belongs to disaster recovery group with FSFO
// enabled, and there is an online primary database in that group.
02669, 00000, "data type or length of a partitionset column in a sharded table cannot be changed"
// *Cause: An attempt was made to issue an ALTER TABLE statement to modify the
// data type or length of a column used to super-partition the
// specified sharded table.
// *Action: Do not modify the data type or length of a sharded table super-
// partitioning column or columns.
/
/
/
/ 2670 - 2699 Reserved for cross shard SQL
/
/
02670, 00000, "unsupported SQL construct: %s"
// *Cause: The query had a construct that was not supported for inter shard query.
// *Action: Rewrite the query to avoid using an unsupported construct. Consult Oracle documentation for details.
02671, 00000, "DML are not allowed on more than one shard"
// *Cause: The DML was applied to more than one shard.
// *Action: Rewrite the DML to limit operation to a single shard.
02672, 00000, "cannot update sharding key"
// *Cause: An attempt was made to update the sharding key value using the UPDATE command.
// *Action: Drop and re-create the sharding key.
02673, 00000, "%s maps to multiple shards"
// *Cause: The aggregate, group by, semi-join, or anti-join subquery was mapped to multiple shards.
// *Action: Rewrite the query so that subqueries map to a single shard.
02674, 00000, "illegal join predicate on sharding key"
// *Cause: The query had illegal or no join predicate on the sharding key.
// *Action: Rewrite the query to include join on sharding columns.
02675, 00000, "sharded table %s outer joined with replicated table %s"
// *Cause: The query had a sharded table outer joined to the replicated table.
// *Action: Rewrite the query to remove the outer join.
02676, 00000, "non-equality join on sharding key"
// *Cause: The query had a non-equality join on the sharding key.
// *Action: Rewrite the query to remove the non-equality join.
02677, 00000, "queries not supported on objects with user-specified sharding"
// *Cause: The query had an object defined by user-specified sharding.
// *Action: None.
02678, 00000, "cross shard queries not supported on composite sharding"
// *Cause: The query had an object defined under composite sharding.
// *Action: None.
02679, 00000, "queries involving private and sharded tables not supported"
// *Cause: The query referenced a private and a sharded table.
// *Action: Rewrite the query to refer to either private tables or sharded tables, but not both.
02680, 00000, "unsupported construct referred in the query"
// *Cause: The query referenced unsupported constructs which could not be fetched from the shard.
// *Action: Rewrite the query to avoid using unsupported constructs.
02681, 00000, "array DML not supported on a sharded table"
// *Cause: The statement attempts an array DML operation on a sharded table.
// *Action: Rewrite the array DML statement as separate DML statements.
02682, 00000, "shard key missing in INSERT statement"
// *Cause: The INSERT statement was used to insert a row in the sharded table without inserting a value for the shard column.
// *Action: Insert a value for the shard key column.
02683, 00000, "inconsistent shard schema"
// *Cause: The schema definition on the shard and the coordinator did not match.
// *Action: Verify and fix the schema inconsistency between the shard and the coordinator.
02684, 00000, "invalid partition for the chunk %s"
// *Cause: A valid partition was not found for the chunk number passed to the shard database.
// *Action: Check the chunks handled by the shard database.
02685, 00000, "cannot rename a duplicated table on a shard database"
// *Cause: An attempt was made to rename a duplicated table on a shard database.
// *Action: Rename the duplicated table in the shard catalog database, if required.
02686, 00000, "query returned data from %s percent of total chunks"
// *Cause: Some of the chunks were not accessible in the system.
// *Action: Ensure that all shards are online and accessible from the query coordinator.
/
/
/ 2700 - 2899 Reserved for UNIX two-task errors
/
02700, 00000, "osnoraenv: error translating ORACLE_SID"
// *Cause: Two-task driver could not find the value of ORACLE_SID in the
// environment.
// *Action: Make sure that the ORACLE_SID environment variable has been
// properly set and exported.
02701, 00000, "osnoraenv: error translating oracle image name"
// *Cause: ORACLE_HOME environment variable not set.
// *Action: Make sure that the ORACLE_HOME environment variable has been
// properly set and exported.
02702, 00000, "osnoraenv: error translating orapop image name"
// *Cause: ORACLE_HOME environment variable not set.
// *Action: Make sure that the ORACLE_HOME environment variable has been
// properly set and exported.
02703, 00000, "osnpopipe: pipe creation failed"
// *Cause: The pipe driver failed to create pipes for communications with
// the orapop process.
// *Action: You have probably exceeded the maximum number of open file
// descriptors per user or the system file table is full. Note the
// operating system error code and contact your system administrator.
02704, 00000, "osndopop: fork failed"
// *Cause: The two-task driver could not fork orapop.
// *Action: Verify that there are enough system resources to support another
// process. The user or system process limit may have been exceeded, or
// the amount of free memory or swap space may be temporarily insufficient.
02705, 00000, "osnpol: polling of communication channel failed"
// *Cause: The pipe driver failed while polling the communications channel.
// *Action: Contact your customer support representative.
02706, 00000, "osnshs: host name too long"
// *Cause: The length of your host-string specified by the TWO_TASK
// environment variable exceeds the ORACLE system-imposed limit.
// *Action: Contact your customer support representative.
02707, 00000, "osnacx: cannot allocate context area"
// *Cause: The invoked Unix two-task driver could not allocate heap space for
// the context area.
// *Action: Contact your customer support representative.
02708, 00000, "osnrntab: connect to host failed, unknown ORACLE_SID"
// *Cause: The invoked Unix two-task driver failed to find an entry in
// oratab for the sid you supplied.
// *Action: First, check whether you have read access to oratab, and
// see if the desired sid is there. Add an entry to oratab
// for the desired sid, if necessary.
02709, 00000, "osnpop: pipe creation failed"
// *Cause: The pipe driver failed to create pipes for two-task communications
// with the oracle shadow process.
// *Action: You have probably exceeded the maximum number of open file
// descriptors per user or the system file table is full. Note the
// operating system error code and contact your system administrator.
02710, 00000, "osnpop: fork failed"
// *Cause: The pipe driver could not fork the oracle shadow process.
// *Action: Verify that there are enough system resources to support another
// process. The user or system process limit may have been exceeded, or
// the amount of free memory or swap space may be temporarily insufficient.
02711, 00000, "osnpvalid: write to validation channel failed"
// *Cause: The pipe driver failed to write to the orapop process.
// *Action: Contact your customer support representative.
02712, 00000, "osnpop: malloc failed"
// *Cause: The pipe driver failed to allocate enough heap space for its
// context area buffers.
// *Action: Contact your customer support representative.
02713, 00000, "osnprd: message receive failure"
// *Cause: The pipe driver failed to read a message from the communications
// channel.
// *Action: Contact your customer support representative.
02714, 00000, "osnpwr: message send failure"
// *Cause: The pipe driver failed to write a message to the communications
// channel.
// *Action: Contact your customer support representative.
02715, 00000, "osnpgetbrkmsg: message from host had incorrect message type"
// *Cause: The pipe driver received a message having an unrecognizable
// message type.
// *Action: Contact your customer support representative.
02716, 00000, "osnpgetdatmsg: message from host had incorrect message type"
// *Cause: The Pipe driver received a message having an unrecognizable
// message type.
// *Action: Contact your customer support representative.
02717, 00000, "osnpfs: incorrect number of bytes written"
// *Cause: The Pipe driver sent a message that was apparently successful,
// but the number of bytes transmitted did not match the number of
// bytes furnished to the driver.
// *Action: Contact your customer support representative.
02718, 00000, "osnprs: reset protocol error"
// *Cause: The two-task driver could not reset the connection.
// *Action: Contact your customer support representative.
02719, 00000, "osnfop: fork failed"
// *Cause: The fast driver could not fork the oracle shadow process.
// *Action: Verify that there are enough system resources to support another
// process. The user or system process limit may have been exceeded, or
// the amount of free memory or swap space may be temporarily insufficient.
02720, 00000, "osnfop: shmat failed"
// *Cause: When the fast driver was invoked, processes failed to attach to the
// shared memory buffer. You probably supplied an illegal shared memory
// attach address, or the system ran out of data space to accomodate the buffer.
// *Action: Try invoking the Fast driver later, or use the default attach
// address.
02721, 00000, "osnseminit: cannot create semaphore set"
// *Cause: The Fast driver failed to get a semaphore set.
// *Action: The system-imposed limit on semaphores or semaphore identifiers
// may have been exceeded. Read the returned operating system
// error code and check with your system administrator.
02722, 00000, "osnpui: cannot send break message to orapop"
// *Cause: The Pipe driver could not send a break message to orapop.
// *Action: Contact your customer support representative.
02723, 00000, "osnpui: cannot send break signal"
// *Cause: The Pipe driver could not send a break message to the ORACLE
// shadow process.
// *Action: Contact your customer support representative.
02724, 00000, "osnpbr: cannot send break message to orapop"
// *Cause: The Pipe driver could not send a break message to orapop.
// *Action: Contact your customer support representative.
02725, 00000, "osnpbr: cannot send break signal"
// *Cause: The Pipe driver could not send a break message to the ORACLE
// shadow process.
// *Action: Kill system call failed. Check errno and contact customer support.
02726, 00000, "osnpop: access error on oracle executable"
// *Cause: The Pipe driver could not access the oracle executable.
// *Action: Check the permissions on the ORACLE executable and each
// component of the ORACLE_HOME/bin path.
02727, 00000, "osnpop: access error on orapop executable"
// *Cause: The Pipe driver could not access the orapop executable.
// *Action: Check the permissions on the orapop executable and each
// component of the ORACLE_HOME/bin path.
02728, 00000, "osnfop: access error on oracle executable"
// *Cause: The Fast driver could not access the oracle executable.
// *Action: Check the permissions on the ORACLE executable and each
// component of the ORACLE_HOME/bin path.
02729, 00000, "osncon: driver not in osntab"
// *Cause: The driver you have specified is not supported.
// *Action: Check with your database administrator which drivers are supported.
02730, 00000, "osnrnf: cannot find user logon directory"
// *Cause: The driver you have specified could not find your logon directory
// while searching for your local .sqlnet file.
// *Action: Set and export the HOME environment variable to identify your
// home directory. Check with your system administrator to make sure
// that your uid and home directory are correct in the /etc/passwd file.
02731, 00000, "osnrnf: malloc of buffer failed"
// *Cause: The specified driver could not find enough heap space to malloc
// a buffer.
// *Action: Contact your customer support representative.
02732, 00000, "osnrnf: cannot find a matching database alias"
// *Cause: Database alias specified was not identified in either
// $HOME/.sqlnet or /etc/sqlnet.
// *Action: Create the alias in a file called .sqlnet in your home directory
// for personal use or ask your system administrator to create the
// alias in /etc/sqlnet for system-wide use.
02733, 00000, "osnsnf: database string too long"
// *Cause: While converting a database alias to a database ID, the resulting
// database ID string exceeded the ORACLE system-imposed limit.
// *Action: Contact your customer support representative.
02734, 00000, "osnftt: cannot reset shared memory permission"
// *Cause: The Fast driver was unable to reset shared memory permissions.
// *Action: Contact your customer support representative.
02735, 00000, "osnfpm: cannot create shared memory segment"
// *Cause: The Fast driver failed to create a shared memory segment for
// two-task communication.
// *Action: Check whether the system-imposed limit on shared memory
// identifiers has already been reached for your system.
02736, 00000, "osnfpm: illegal default shared memory address"
// *Cause: The Fast driver failed to establish a default shared memory
// address.
// *Action: Contact your customer support representative.
02737, 00000, "osnpcl: cannot tell orapop to exit"
// *Cause: The Pipe driver failed to send orapop the command to exit.
// *Action: Contact your customer support representative.
02738, 00000, "osnpwrtbrkmsg: incorrect number of bytes written"
// *Cause: The pipe driver apparently sent an imcomplete break message.
// *Action: Contact your customer support representative.
02739, 00000, "osncon: host alias is too long"
// *Cause: The alias used for a sqlnet host is longer than 161 characters.
// *Action: Use a shorter alias.
02750, 00000, "osnfsmmap: cannot open shared memory file ?/dbs/ftt_<pid>.dbf"
// *Cause: The Fast driver failed to create a shared memory file for
// two-task communication.
// *Action: Check the permissions on the directory ?/dbs
02751, 00000, "osnfsmmap: cannot map shared memory file"
// *Cause: The Fast driver failed to map a shared memory file for
// two-task communication.
// *Action: Contact your customer support representative.
02752, 00000, "osnfsmmap: illegal shared memory address"
// *Cause: The Fast driver failed to attach shared memory at the expected
// location.
// *Action: Contact your customer support representative.
02753, 00000, "osnfsmmap: cannot close shared memory file"
// *Cause: The Fast driver cannot close the shared memory file.
// *Action: Contact your customer support representative.
02754, 00000, "osnfsmmap: cannot change shared memory inheritence"
// *Cause: The Fast driver could not alter the inheritence attributes
// of the shared memory.
// *Action: Contact your customer support representative.
02755, 00000, "osnfsmcre: cannot create chared memory file ?/dbs/ftt_<pid>.dbf"
// *Cause: The Fast driver failed to create a file for shared memory.
// *Action: Check the permissions on the directory ?/dbs
02756, 00000, "osnfsmnam: name translation failure"
// *Cause: The Fast driver encountered an error translating the shared
// memory filename ?/dbs/ftt_<pid>.dbf.
// *Action: Contact your customer support representative.
02757, 00000, "osnfop: fork_and_bind failed"
// *Cause: The Fast driver failed to fork a process onto the desired
// cluster and node number.
// *Action: Check the desired node number in sercose[0] and cluster ID in
// sercose[1]. If these seem valid, contact customer support.
/
/ 2758 - 2899 Reserved for ORACLE asynchronous I/O.
02758, 00000, "Allocation of internal array failed"
// *Cause: The package was unable to allocate memory for an array because
// the system ran out of memory.
// *Action: Either reclaim memory by killing other processes or reboot the
// machine with more memory.
02759, 00000, "Not enough request descriptors available"
// *Cause: All of the package's request descriptors are in use performing
// other requests.
// *Action: Either wait until enough requests are done, or shut the package
// down and re-initialize it with more request descriptors.
02760, 00000, "Client close of file failed."
// *Cause: The client was unable to close a file after forking the servers.
// *Action: This is a system problem - contact your System Administrator.
02761, 00000, "File number to be canceled is negative."
// *Cause: The file number contained with the sfiov structure is less than
// zero.
// *Action: This may be a programming error. If it is not, contact ORACLE
// support.
02762, 00000, "file number to be cancelled is greater than the maximum."
// *Cause: The file number contained with the sfiov structure is greater
// than the maximum.
// *Action: This may be a programming error. If it is not, contact ORACLE
// support.
02763, 00000, "Unable to cancel at least one request"
// *Cause: No requests were found that could be cancelled.
// *Action: This error can occur if all the requests dealing with that file
// number have already been filled.
02764, 00000, "Invalid package mode"
// *Cause: The mode of the package can only be parallel or duplex.
// *Action: See sfa.h for the correct values.
02765, 00000, "Invalid maximum number of servers"
// *Cause: The number of servers given was less than or equal to zero.
// *Action: Use a number greater than zero.
02766, 00000, "Invalid maximum of request descriptors"
// *Cause: The number of request descriptors was less than or equal to zero.
// *Action: Use a number greater than zero.
02767, 00000, "Less than one request descriptor was allocated per server"
// *Cause: The package requires that the number of request descriptors
// be greater than or equal to the number of servers used.
// *Action: Use a higher number
02768, 00000, "Maximum number of files is invalid"
// *Cause: The maximum number of files to be used by the package was less
// than or equal to zero.
// *Action: Use a positive number.
02769, 00000, "Setting of handler for SIGTERM failed"
// *Cause: The package was unable to set up handling by the server for the
// termination signal. This is an internal error.
// *Action: Contact ORACLE support.
02770, 00000, "Total number of blocks is invalid"
// *Cause: The total number of blocks to be allocated for use by the package
// was not greater than zero.
// *Action: Use a positive number.
02771, 00000, "Illegal request time out value"
// *Cause: The number was not a positive number.
// *Action: Use a positive number.
02772, 00000, "Invalid maximum server idle time"
// *Cause: The time given was not a positive number.
// *Action: Use a positive number.
02773, 00000, "Invalid maximum client wait time"
// *Cause: The time given was not a positive number.
// *Action: Use a positive number.
02774, 00000, "Invalid request list latch time out value"
// *Cause: The time given was not a positive number.
// *Action: Use a positive number.
02775, 00000, "Invalid request done signal"
// *Cause: The signal number was not a positive number.
// *Action: Use a positive number.
02776, 00000, "Value for request done signal exceeds maximum"
// *Cause: The value sent to the package for use as the "request done"
// signal exceeds the maximum allowed by the operating system.
// *Action:
02777, 00000, "Stat failed on log directory"
// *Cause: The package was unable to get information about the directory
// in which the log files are to reside.
// *Action: Check the permissions on the directory or use a different
// directory name.
02778, 00000, "Name given for the log directory is invalid"
// *Cause: The name given for the directory in which the logs are to be kept
// does not correspond to a directory.
// *Action: Use a different name.
02779, 00000, "Stat failed on core dump directory"
// *Cause: The package was unable to get information about the directory
// into which the servers are to dump core in the event of an
// exception.
// *Action: Check the permissions on the directory or use a different
// directory name.
02780, 00000, "Name given for the core dump directory is invalid"
// *Cause: The name given for the directory in which the server processes
// are to dump core in the event of an exception does not correspond
// to a directory.
// *Action: Use a different name.
02781, 00000, "Invalid value given for the timing wanted flag"
// *Cause: The value given was not TRUE or FALSE.
// *Action:
02782, 00000, "Both read and write functions were not specified"
// *Cause: To ensure that the functions act symmetrically, pointers to both
// the read and write functions must be given.
// *Action: Either specify both functions or specify neither. The package
// will supply its own functions.
02783, 00000, "Both post and wait functions were not specified"
// *Cause: To ensure that the functions act symmetrically, pointers to both
// the posting and waiting functions must be given.
// *Action: Either specify both functions or specify neither. The package
// will supply its own functions.
02784, 00000, "Invalid shared memory ID specified"
// *Cause: The ID of the segment specified for use as the shared buffer
// region was invalid.
// *Action: Use a different ID, or let the package specify its own.
02785, 00000, "Invalid shared memory buffer size"
// *Cause: The size given for the shared memory segment to be used as the
// shared buffer region was less than or equal to zero.
// *Action: Use a positive number.
02786, 00000, "Size needed for shared region is greater than segment size"
// *Cause: The size of the shared segment that was specified for the
// shared buffer region is less than the number of bytes required.
// The first field of the "additional information" field is the
// size needed. The second is the size of the segment.
// *Action: Use a larger size segment or let the package allocate its own.
02787, 00000, "Unable to allocate memory for segment list"
// *Cause: The package cannot allocate memory for an internal segment list
// because the system has run out of memory.
// The "additional information" field is the amount of memory
// that the package attempted to allocate.
// *Action:
02788, 00000, "Unable to find kernel process pointer in async process array"
// *Cause: Internal error - Contact ORACLE support.
// *Action:
02789, 00000, "Maximum number of files reached"
// *Cause: The maximum number of files that can be used for asynchronous
// I/O has been reached.
// *Action: Shut down the servers and re-initialize the package with a higher
// number.
02790, 00000, "File name is too long"
// *Cause: The length of the name of a file that is being opened for
// asynchronous I/O is longer than the maximum.
// The "additional information" field is the maximum length.
// *Action: Use a shorter name.
02791, 00000, "Unable to open file for use with asynchronous I/O"
// *Cause: The package could not open file for some reason.
// *Action: Check the file name.
02792, 00000, "Unable to fstat() a file being used for asynchronous I/O."
// *Cause: The fstat(2) call on a file being used for asynchronous I/O
// failed.
// *Action: Check the file name.
02793, 00000, "Close of asynchronous I/O failed."
// *Cause: The client was unable to close a file being used for asynchronous
// I/O.
// *Action: Contact ORACLE support - this should not happen.
02794, 00000, "Client unable to get key for shared memory"
// *Cause: The client was unable to get a key so that it obtain shared
// memory for use with shared memory.
// *Action: Contact ORACLE support - this is an internal error.
02795, 00000, "Request list is empty"
// *Cause: The client was signalled by a server that it was done with a
// request but the "done" list was empty.
// *Action: Internal error - contact ORACLE support.
02796, 00000, "Done request is not in correct state"
// *Cause: A request is not in the right state.
// *Action: Internal error - contact ORACLE support.
02797, 00000, "No requests available"
// *Cause: No free request descriptors are available.
// *Action: Wait until some requests are filled and then retry the request,
// or shutdown the servers and initialize the package with a
// higher number of requests.
02798, 00000, "Invalid number of requests"
// *Cause: The number of operations sent to either sfard() or sfawrite()
// is less than zero.
// *Action: This is a user programming error.
02799, 00000, "Unable to arm signal handler"
// *Cause: The arming of a signal handler for the "done" signal failed.
// *Action: Internal error - contact ORACLE support.
02800, 00000, "Requests timed out"
// *Cause: Some of the requests for asynchronous input or output were not
// serviced in the required amount of time.
// *Action: If the load on the system is high, it is possible that the
// timeout limit is too low. Reset it with sfainit(). If the server
// processes are dying due to unexpected signals, this is an
// internal error, and ORACLE support should be contacted.
02801, 00000, "Operations timed out"
// *Cause: Some asynchronous operations timed out in kernel mode.
// *Action: Internal error - contact ORACLE support.
02802, 00000, "No idle servers available in parallel mode"
// *Cause: Internal error.
// *Action: Contact ORACLE support.
02803, 00000, "Retrieval of current time failed"
// *Cause: Internal error.
// *Action: Contact ORACLE support.
02804, 00000, "Allocation of memory failed for log file name"
// *Cause: The client was unable to allocated a buffer for the name of the
// log file.
// *Action: Contact your System Administrator.
02805, 00000, "Unable to set handler for SIGTPA"
// *Cause: Internal error.
// *Action: Contact ORACLE support.
02806, 00000, "Unable to set handler for SIGALRM"
// *Cause: Internal error.
// *Action: Contact ORACLE support.
02807, 00000, "Allocation of memory for I/O vectors failed."
// *Cause: The client was unable to allocate memory for the array of I/O
// vectors that the servers are to use.
// *Action: Contact your System Administrator.
02808, 00000, "Allocation of memory of open files array failed."
// *Cause: The client was unable to allocate memory for an array of flags
// that the servers are to use.
// *Action: Contact your System Administrator.
02809, 00000, "Jump buffer not valid"
// *Cause: Internal error.
// *Action: Contact ORACLE support.
02810, 00000, "Unable to make temporary file name for memory mapped file"
// *Cause:
// *Action:
02811, 00000, "Unable to attach shared memory segment"
// *Cause:
// *Action:
02812, 00000, "Bad attach address"
// *Cause:
// *Action:
02813, 00000, "Unable to make temporary file name in order to get key"
// *Cause: Internal error.
// *Action: Contact ORACLE support.
02814, 00000, "Unable to get shared memory"
// *Cause: Shmget(2) failed.
// *Action: Check the UNIX number. If you are unsure about what it means,
// contact ORACLE customer support.
02815, 00000, "Unable to attach shared memory"
// *Cause: Shmat(2) failed.
// *Action: Check the UNIX number. If you are unsure about what it means,
// contact ORACLE customer support.
02816, 00000, "Unable to kill a process"
// *Cause: A server did not die after being sent a kill signal.
// *Action: The process may be a runaway - contact ORACLE customer support.
02817, 00000, "Read failed"
// *Cause: A server could not read a requested amount of data.
// *Action: Check the call to sfard(). An incorrect file descriptor may have
// been sent to sfard().
// The number in the "additional information" field is the starting
// block number of the data segment being read in.
02818, 00000, "Less than the number of blocks requested was read in"
// *Cause: A server could not read in the request amount of data.
// The first number in the "additional information" field is the
// block number being read in. The second is the actual number
// of bytes that was read in.
// *Action: This is a programming error.
02819, 00000, "Write failed"
// *Cause: A server was unable to perform a write.
// The number in the "additional information" field is the starting
// block number of the data segment being written out.
// The first number in the "additional information" field is the
// block number being written out. The second is the actual number
// of bytes that was written out. The disk may have filled up.
// *Action: Check the UNIX error number.
02820, 00000, "Unable to write the requested number of blocks"
// *Cause: A server could not write the requested amount of data out to
// disk. The disk may have run out of space.
// *Action: Check the UNIX error number.
02821, 00000, "Unable to read the requested number of blocks."
// *Cause: A server could not read the number of blocks that was requested.
// The end of the file may have been read.
// *Action: Check the file on disk.
02822, 00000, "Invalid block offset"
// *Cause: A server was unable to seek to the designated block.
// *Action: Check the UNIX error number.
02823, 00000, "Buffer is not aligned."
// *Cause: The buffer on which an I/O is being done is not on the correct
// boundary.
// *Action: Check the calling program.
02824, 00000, "Request free list is empty"
// *Cause: The list from which the package allocates request descriptors is
// empty because all of the descriptors is in use.
// *Action: Wait until some become free, or initialize the package with
// a higher number of request descriptors.
02825, 00000, "Request on free list was not free"
// *Cause: Internal error.
// *Action: Contact ORACLE support.
02826, 00000, "Illegal block size"
// *Cause: A negative number was given for the I/O block size to be used by
// the asynchronous I/O package.
// *Action: This is a programming error - use either a positive number or
// zero to get the default value.
02827, 00000, "Invalid file number"
// *Cause: The file number upon which an operation is to done is either
// less than zero or greater than the maximum number of files than
// can be open.
// *Action: This is a programming error. Since the calling program should
// not touch this number, this is a programming error.
02828, 00000, "Segment free list is empty"
// *Cause: No segments are available to allocated.
// *Action: Free some segments or shut down the package and re-initialize it
// with a higher number of segments.
02829, 00000, "No segment of the proper size is available"
// *Cause: No segment of the proper size is ready for use by the caller.
// *Action: Free some segments and try again.
02830, 00000, "Segment could not be split - no free segments available"
// *Cause: A segment that is larger than that desired could not be split
// because no free segment was available.
// *Action: Free some segments and try again.
02831, 00000, "Segment deallocation failed - empty segment list"
// *Cause: The caller attempted to deallocate a segment but the "in use"
// list was empty. This is a programming error.
// *Action: Check the calling program.
02832, 00000, "Segment deallocation failed - segment not on list"
// *Cause: The caller attempted to deallocate a segment that was not on the
// "in use" list. This is a programming error.
// *Action: Check the calling program.
02833, 00000, "Server was unable to close file"
// *Cause: A server was unable to close a file being used for asynchronous
// I/O.
// *Action: See the UNIX error number for more information.
02834, 00000, "Server unable to open file"
// *Cause: The server was unable to open a file for use with asynchronous
// I/O.
// *Action: Check the UNIX error number for more information.
02835, 00000, "Server unable to send signal to client"
// *Cause: Internal error.
// *Action: Contact ORACLE support.
02836, 00000, "Unable to create temporary key file"
// *Cause: Internal error.
// *Action: Contact ORACLE support.
02837, 00000, "Unable to unlink temporary file"
// *Cause: Internal error.
// *Action: Contact ORACLE support.
02838, 00000, "Unable to arm signal handler for the alarm signal"
// *Cause: The arming of a signal handler for the alarmsignal failed.
// *Action: Internal error - contact ORACLE support.
02839, 00000, "Sync of blocks to disk failed."
// *Cause: The server was unable to flush its writes out to disk.
// *Action: Check the UNIX error number.
02840, 00000, "Open of log file by client failed"
// *Cause: The client process was unable to open its log file.
// *Action: Check the UNIX error number for more information.
02841, 00000, "Server died on start up"
// *Cause: A server exited during its initialization process.
// *Action: Check the servers' logs for more information.
02842, 00000, "Client unable to fork a server"
// *Cause: The client could not spawn a server. A possible reason is that
// the operating system has reached its limit on the number of
// processes that it can spawn.
// *Action: Either reduce the number of servers that are to be used,
// or reconfigure the operating system so that it can handle more
// processes.
02843, 00000, "Invalid value for kernel flag"
// *Cause: An illegal value was given for the kernel flag in the information
// structure. Only TRUE and FALSE are permitted.
// *Action: This is a programming error - check the calling routine.
02844, 00000, "Invalid value for the leave open flag"
// *Cause: A value was given for the flag that determines whether a file is
// to be left open after the client checks it to see if the servers
// can use it. Only TRUE and FALSE are supported.
// *Action: This is a programming error - check the calling routine.
02845, 00000, "Invalid value for the timing wanted flag"
// *Cause: A value was given for the flag that indicates that operations are
// to be timed out. Only TRUE and FALSE are supported.
// *Action: This is a programming error - check the calling routine.
02846, 00000, "Unkillable server"
// *Cause: A server would not respond to the termination signal.
// The first number is the number of the server. The second is its
// UNIX process number.
// This is an internal problem.
// *Action: This is an operating system problem.
02847, 00000, "Server did not terminate when posted"
// *Cause: A server did not respond to a posted request to shutdown.
// The first number is the number of the server. The second is its
// UNIX process number.
// This is an internal problem.
// *Action: Contact ORACLE support.
02848, 00000, "Asynchronous I/O package is not running"
// *Cause: An operation using the asynchronous I/O package was attempted
// without first initializing the package using sfainit().
// *Action: Call sfainit() before using the package.
02849, 00000, "Read failed because of an error"
// *Cause: A server could not read the requested amount of data from
// disk.
// *Action: Check the UNIX error number.
02850, 00000, "File is closed"
// *Cause: A file upon which an asynchronous I/O operation is to be
// performed has already been closed by the package.
// *Action: This is a programming error.
02851, 00000, "Request list is empty when it should not be"
// *Cause: This is an internal problem.
// *Action: Contact ORACLE support.
02852, 00000, "Invalid critical-section time out value"
// *Cause: The time given was not a positive number.
// *Action: Use a positive number.
02853, 00000, "Invalid server list latch time out value"
// *Cause: The time given was not a positive number.
// *Action: Use a positive number.
02854, 00000, "Invalid number of request buffers"
// *Cause: The value given for "db_slave_buffers" in your INIT.ORA file
// is less than 0.
// *Action: Use a number that is greater than or equal to 0.
02855, 00000, "Number of requests is less than the number of slaves"
// *Cause: The value given for 'db_slave_buffers' in the initialization
// parameter file was less than the number specified for the number of
// slaves, 'db_slaves.'
// *Action: Specify a number that is greater than that given for 'db_slaves.'
// Alternatively, specify 0. The kernel will supply the appropriate
// number.
/ 2875 - 2899 Reserved for IBM RS/6000
02875, 00000, "smpini: Unable to get shared memory for PGA"
// *Cause: Stated in errno.
// *Action: Resolve the problem.
02876, 00000, "smpini: Unable to attach to shared memory for PGA"
// *Cause: Stated in errno.
// *Action: Resolve the problem.
02877, 00000, "smpini: Unable to initialize memory protection"
// *Cause: The adspcinit program has not been executed.
// *Action: Execute the adscpinit program as shown in your Installation
// and Users' Guide. If the problem persists, try rebooting
// your computer.
02878, 00000, "sou2o: Variable smpdidini overwritten"
// *Cause: The variable smpdidini was overwritten, probably by client code.
// *Action: Verify client code, e.g. Pro*C, for illegal memory access.
// If the problem occurs outside Single Task operation, contact
// your customer support representative.
02879, 00000, "sou2o: Could not gain access to protected memory"
// *Cause: This is an internal error, note error code in errno.
// *Action: Report to your customer support representative. Restarting
// your application or your computer may cure the problem.
02880, 00000, "smpini: Could not register PGA for protection"
// *Cause: This is an internal error, note error code in errno.
// *Action: Report to your customer support representative. Restarting
// your application or your computer may cure the problem.
02881, 00000, "sou2o: Could not revoke access to protected memory"
// *Cause: This is an internal error, note error code in errno.
// *Action: Report to your customer support representative. Restarting
// your application or your computer may cure the problem.
02882, 00000, "sou2o: Could not register SGA for protection"
// *Cause: This is an internal error, note error code in errno.
// *Action: Report to your customer support representative. Restarting
// your application or your computer may cure the problem.
02899, 00000, "smscre: Cannot create SGA with Extended Shared Memory feature"
// *Cause: The environment variable EXTSHM was set before starting oracle.
// *Action: Unset the environment variable EXTSHM and startup oracle.
/
/ 2900 - 2999 Reserved for licensing server errors
/
/ 3000-3099 currently not implemented features
/
03001, 00000, "unimplemented feature"
// *Cause: This feature is not implemented.
// *Action: None.
03002, 00000, "operator not implemented"
// *Cause: This is an internal error.
// *Action: Contact your customer support representative.
03007, 00000, "obsolete feature"
// *Cause: User attempted to use a feature which is no longer supported.
// *Action: None.
03009, 00000, "Incompatible OCI function call"
// *Cause: An incompatible OCI function call was issued for new functionality.
// *Action: Do not use V7 OCI calls for this functionality.
/
/ 3100-3139 two task interface errors
/ some of these can eventually convert to internal ercs
/
03100, 00000, "communication area cannot be allocated; insufficient memory"
// *Cause:
// *Action:
03101, 00000, "invalid input data for %s"
// *Cause: Invalid input data was detected for the specified data type.
// *Action: Pass a valid value for the specified data type.
/
03102, 00000, "TTC detects an invalid character set."
// *Cause: A malformed TTC (Two-Task Common) packet was received.
// *Action: Contact Oracle Support Services.
/
03103, 00000, "malformed TTC packet from client rejected for TTC RPC (%s): Reason: %d"
// *Cause: An invalid input was detected for the specified Two-Task Common
// (TTC) remote procedural call (RPC).
// *Action: Contact Oracle Support Services.
/
03105, 00000, "internal protocol error"
// *Cause:
// *Action:
03106, 00000, "fatal two-task communication protocol error"
// *Cause:
// *Action:
03107, 00000, "oranet buffer underflow"
// *Cause:
// *Action:
03108, 00000, "oranet: ORACLE does not support this interface version"
// *Cause:
// *Action:
03109, 00000, "oranet buffer overflow"
// *Cause:
// *Action:
03110, 00000, "oranet: ORACLE does not support this SQL version"
// *Cause:
// *Action:
03111, 00000, "break received on communication channel"
// *Cause:
// *Action:
03112, 00000, "a server linked as single-task cannot use SQL*Net"
// Cause: A statement containing a SQL*Net connect string was issued to the
// single-task server. For example, a database link was used in a
// SQL statement.
// Action: Do not use SQL*Net connect strings in a single-task environment.
03113, 00000, "end-of-file on communication channel"
// *Cause: The connection between Client and Server process was broken.
// *Action: There was a communication error that requires further investigation.
// First, check for network problems and review the SQL*Net setup.
// Also, look in the alert.log file for any errors. Finally, test to
// see whether the server process is dead and whether a trace file
// was generated at failure time.
03114, 00000, "not connected to ORACLE"
// *Cause:
// *Action:
03115, 00000, "unsupported network datatype or representation"
// *Cause:
// *Action:
03116, 00000, "invalid buffer length passed to a conversion routine"
// *Cause:
// *Action:
03117, 00000, "two-task save area overflow"
// *Cause:
// *Action:
03118, 00000, "two-task coroutine has invalid state"
// *Cause:
// *Action:
03119, 00000, "two-task detected inconsistent datatype specification"
// *Cause: There was both a datatype, and an anonymous datatype declaration
// found.
// *Action:Correct the specification.
03120, 00000, "two-task conversion routine: integer overflow"
// *Cause:
// *Action:
03121, 00000, "no interface driver connected - function not performed"
// *Cause:
// *Action:
03122, 00000, "attempt to close ORACLE-side window on user side"
// *Cause: This is an internal error.
// *Action: Contact your customer support representative.
03123, 00000, "operation would block"
// *Cause: This is a status code that indicates that the operation
// cannot complete now.
// *Action: None; this is not an error. The operation should be retried
// again for completion.
03124, 00000, "two-task internal error"
// *Cause: Internal error.
// *Action: Contact your customer support representative.
03125, 00000, "client-server protocol violation"
// *Cause: The application received a bad escape sequence from the server and
// may indicate a problem with the client application user code.
// *Action: Contact your customer support representative.
03126, 00000, "network driver does not support non-blocking operations"
// *Cause: A non-blocking operation was attempted and the network driver
// does not support non-blocking operations.
// *Action: Use default blocking operations or use a driver supporting
// non-blocking operations.
03127, 00000, "no new operations allowed until the active operation ends"
// *Cause: An attempt was made to execute a new operation before the active
// non-blocking operation completed or a new operation was attempted
// before all the pieces of a column were inserted or fetched.
// *Action: Execute the new operation after the non-blocking operation
// completes. If piecewise binds/defines were done, execute the new
// operation after all the pieces have been inserted or fetched.
03128, 00000, "connection is in blocking mode"
// *Cause: The OCI test for non-blocking mode on a connection indicates that
// the connection is in blocking mode.
// *Action: If non-blocking mode is required use appropriate OCI calls to
// change the mode.
03129, 00000, "the next piece to be inserted is required"
// *Cause: The application performed a piecewise bind on a column.
// *Action: Provide the next piece of this bind variable.
03130, 00000, "the buffer for the next piece to be fetched is required"
// *Cause: The application performed a piecewise define on the column.
// *Action: Provide the next buffer for the next piece to be retrieved.
03131, 00000, "an invalid buffer was provided for the next piece"
// *Cause: The application either provided the length of the buffer for the
// next piece to be zero or provided a null pointer.
// *Action: Verify if the buffer pointer for the next piece is null or if the
// length is zero.
03132, 00000, "two-task default value overflow"
// *Cause: The default value specified for a record field was too large.
// *Action: Change the default value to fit the field size.
03133, 00000, "piggyback function error"
// *Document: NO
// *Cause: Piggyback function has returned an error. This is an internal
// error.
// *Action:
03134, 00000, "Connections to this server version are no longer supported."
// *Cause: An attempt was made to connect to an Oracle server of older
// version.
// *Action: Please refer to documentation for more details.
03135, 00000, "connection lost contact"
// *Cause: 1) Server unexpectedly terminated or was forced to terminate.
// 2) Server timed out the connection.
// *Action: 1) Check if the server session was terminated.
// 2) Check if the timeout parameters are set properly in sqlnet.ora.
03136, 00000, "inbound connection timed out"
// *Cause: Inbound connection was timed out by the server because
// user authentication was not completed within the given time
// specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value
// *Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections.
// 2) Configure SQL*NET with a proper inbound connect timeout value
// if necessary.
03137, 00000, "malformed TTC packet from client rejected: [%s] [%s] [%s] [%s] [%s] [%s] [%s] [%s]"
// *Cause: A malformed TTC (Two-Task Common) packet was received from the client.
// *Action: Contact Oracle Support Services.
03138, 00000, "Connection terminated due to security policy violation"
// *Cause: Connection was terminated due to a security policy violation.
// *Action: Contact the Database Administrator
03139, 00000, "This OCI call has been disabled by the DBA"
// *Cause: The SEC_DISABLE_OLDER_ORACLE_RPCS initialization parameter was enabled.
// *Action: Contact the Database Administrator
/
/ 3140 - 3159 Reserved for TTC/NET vector IO
/
03140, 00000, "I/O operation in progress"
// *Cause: The current I/O operation was not complete. The error is
// typically returned from vectored and/or asynchronous I/O calls.
// *Action: Perform the necessary operation to complete or abort the current I/O.
03141, 00000, "I/O request queue full"
// *Cause: The I/O request queue was full and no more requests could be queued.
// *Action: Perform the proper operations to complete part or all of the current
// in-progress I/O requests.
03142, 00000, "Session ID: %ld Serial number: %ld"
// *Cause: Connection was lost for the specified session and serial number.
// This is either due to session being killed or network problems.
// *Action: Reconnect and if error persists, contact Oracle Support Services.
03143, 00000, "Process ID: %s Thread ID: %s"
// *Cause: Connection was lost for the specified process ID and thread ID.
// This is either due to session being killed or network problems.
// *Action: Reconnect and if error persists, contact Oracle Support Services.
03144, 00000, "Process ID: %s"
// *Cause: Connection was lost for the specified process ID.
// This is either due to session being killed or network problems.
// *Action: Reconnect and if error persists, contact Oracle Support Services.
03145, 00000, "I/O streaming direction error"
// *Cause: Attempted to PUT data when GET streaming was in progress or
// attempted to GET data when PUT streaming was in progress.
// *Action: Complete current stream read or write I/O before attempting
// I/O in reverse direction.
03146, 00000, "invalid buffer length for TTC field"
// *Cause: A malformed TTC (Two-Task Common) packet was received.
// *Action: Contact Oracle Support Services.
03147, 00000, "missing mandatory TTC field"
// *Cause: A malformed TTC (Two-Task Common) packet was received.
// *Action: Contact Oracle Support Services.
03148, 00000, "OCI_ATTR_ROW_COUNT cannot return a row count exceeding UB4MAXVAL. The actual row count is [%s]"
// *Cause: The row count was larger than UB4MAXVAL. OCI clients using
// OCI_ATTR_ROW_COUNT cannot see row counts larger than UB4MAXVAL.
// *Action: Upgrade Oracle client to version 12 client libraries or higher and
// use OCI_ATTR_UB8_ROW_COUNT instead.
03149, 00000, "invalid Oracle error code"
// *Cause: An invalid Oracle error code was received by the server.
// *Action: Contact Oracle Support Services.
03150, 00000, "end-of-file on communication channel for database link"
// *Cause: The connection between the client and the remote server
// process was broken.
// *Action: Look in the alert.log file of the remote server for any
// errors. Also, check to see whether the remote server
// process is dead and whether a trace file was generated
// at failure time.
03151, 00000, "schema name length exceeding UB1MAXVAL"
// *Cause: The schema name length was larger than UB1MAXVAL, and clients
// older than Release 12.2 were unable to process longer names.
// *Action: Upgrade the client to Release 12.2 or higher.
03152, 00000, "object name length exceeding UB1MAXVAL"
// *Cause: The object name length was larger than UB1MAXVAL, and clients
// older than Release 12.2 wree unable to process longer names.
// *Action: Upgrade the client to Release 12.2 or higher.
03153, 00000, "column name length exceeding UB1MAXVAL"
// *Cause: The column name length was larger than UB1MAXVAL, and clients
// older than Release 12.2 were unable to process longer names.
// *Action: Upgrade the client to Release 12.2 or higher.
03154, 00000, "Deprecated TTC operation is disallowed."
// *Cause: A Deprecated Two-Task Common (TTC) remote procedural call (RPC)
// was invoked.
// *Action: Check the 'allow_deprecated_rpcs' parameter setting and set it to
// the desired configuration.
03155, 00000, "SQL statement not supported for remote execution"
// *Cause: Statement execution could not proceed because the rewritten
// statement that was issued to the remote had a different ordering
// (or number) of bind variables as compared to the original statement
// issued locally.
// *Action: Rewrite the statement issued locally to more closely match the
// rewritten statement issued to the remote (especially in terms of
// order and number of bind variables). Contact Oracle Support
// Services for further assistance.
03160, 00000, "An invalid client operation was requested by the server"
// *Cause: You are using an Oracle client application linked with
// libraries with lower version than the current server version.
// *Action: Upgrade client libraries to be same as
// or higher than the server version.
/
/ 3170 to 3199 reserved for readable physical standby
/
03170, 00000, "deadlocked on readable physical standby (undo segment %s)"
// *Cause: A new undo segment was added. A query can occasionally
// deadlock when issued around the time an undo segment is added
// and used immediately on the primary.
// *Action: Retry the query. Avoid creating new undo segments when using
// standby as a regular part of operation.
03171, 00000, "Recovery was terminated during query execution"
// *Cause: Recovery was terminated. A query can ocassionally
// deadlock when recovery is terminated because it needs a block
// with changes that are made after the point at which recovery
// was terminated.
// *Action: Retry the query. Avoid cancelling recovery on standby.
03172, 00000, "STANDBY_MAX_DATA_DELAY of %s seconds exceeded"
// *Cause: Standby recovery fell behind the STANDBY_MAX_DATA_DELAY
// requirement.
// *Action: Tune recovery and retry the query later, or switch to another
// standby database within the data delay requirement.
03173, 00000, "Standby may not be synced with primary"
// *Cause: ALTER SESSION SYNC WITH PRIMARY did not work because either the
// standby was not synchronous or in a data-loss mode with regard
// to the primary, or the standby recovery was terminated.
// *Action: Make the standby synchronous and no-data-loss with regard
// to the primary. Make the standby recovery active.
03174, 00000, "STANDBY_MAX_DATA_DELAY does not apply to SYS users"
// *Cause: ALTER SESSION SET STANDBY_MAX_DATA_DELAY did not work for SYS
// users.
// *Action: Issue ALTER SESSION SET STANDBY_MAX_DATA_DELAY for non-SYS users.
03175, 00000, "parameter %s mismatch"
// *Cause: The value of the %s parameter was not the same in all instances.
// *Action: Check %s in all instances.
03176, 00000, "%s only works on an open physical standby database"
// *Cause: The database was not an open physical standby database.
// *Action: Issue the command on an open physical standby database.
03177, 00000, "enable read-only violation logging"
// *Cause:
// *Action:
// *Comment: Used for testing only
03178, 00000, "duplicate SESSION or GLOBAL specifications"
// *Cause: Duplicate SESSION or GLOBAL specifications were specified.
// *Action: Remove the duplicate specification.
03179, 00000, "NOCACHE or ORDER sequences cannot be accessed from Active Data Guard standby"
// *Cause: NOCACHE or ORDER sequences were not supported for Active Data Guard standby.
// *Action: Alter the sequence properties.
03180, 00000, "Sequence values cannot be allocated for Oracle Active Data Guard standby."
// *Cause: Connection to the corresponding primary database failed. The primary database might be down.
// *Action: Try again later.
03181, 00000, "Sequence object no longer exists for Oracle Active Data Guard standby."
// *Cause: The sequence object might have been dropped by the primary database.
// *Action: Check the sequence status on the primary database.
03182, 00000, "The sequence object is no longer a global sequence for Oracle Active Data Guard standby database."
// *Cause: The sequence object might have been altered by the primary database.
// *Action: Check the sequence status on the primary database.
03183, 00000, "Parameter %s value change failed."
// *Cause: The parameter could not be changed during Oracle Active Data Guard (Oracle ADG) recovery.
// *Action: Stop the Oracle ADG recovery and then change the parameter value.
03184, 00000, "Simulate error during get object locks"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Used for testing only
03185, 00000, "The value change failed for parameter %s."
// *Cause: An attempt was made to enable the parameter on a non-Engineered
// system or it was not on a Platform as a Service.
// *Action: Contact Oracle Support Services.
03186, 00000, "Cannot start Oracle ADG recovery on a non-Oracle Cloud database on a server that is not a primary server."
// *Cause: An attempt was made to start Oracle Active Data Guard (Oracle ADG)
// recovery on a non-Oracle Cloud database that was not on the primary server.
// *Action: Contact Oracle Support Services.
03187, 00000, "Preplugin recovery cannot start from a backup belonging to a prior PDB incarnation."
// *Cause: An attempt was made to start preplugin recovery from a backup prior
// to the current pluggable database (PDB) incarnation.
// *Action: Contact Oracle Support Services.
/
/ 3200 - 3289 Allocate Extent and other Space Management errors
/
03200, 00000, "the segment type specification is invalid"
// *Cause: segment type is not TABLE, INDEX, or CLUSTER
// *Action: use a correct segment type
/
03201, 00000, "the group number specification is invalid"
// *Cause: the freelist group number was either negative or larger than the
// the number of freelist groups in the segment
// *Action: use a correct group number
/
03202, 00000, "the scan limit specification is invalid"
// *Cause: the scan limit did not have a positive integer value
// the number of freelist groups in the segment
// *Action: use a correct scan limit
/
03203, 00000, "concurrent update activity makes space analysis impossible"
// *Cause: high volume of user updates interfere with the space analysis
// *Action: retry the command or lock the underlying objects
/
03204, 00000, "the segment type specification should indicate partitioning"
// *Cause: partition name is specified for the space analysis, but the object
// type does not indicate parttitioning
// *Action: specify PARTITION in the segment type, if the object is
// partitioned, otherwise, omit the partition name
/
03205, 00000, "partition name is required when partitioned type is specified"
// *Cause: partition name is not specified for the space analysis, but the
// object type indicates parttitioning
// *Action: specify partition name, if the object is partitioned, otherwise,
// specify a non-partitioned type
/
03206, 00000, "maximum file size of (%s) blocks in AUTOEXTEND clause is out of range"
// *Cause: The maximum file size for an autoextendable file has
// exceeded the maximum number of blocks allowed.
// *Action: Reduce the size and retry.
/
03207, 00000, "subpartitioned type must be specified for composite object"
// *Cause: partition type is specified for the space analysis, but the
// object type indicates composite partitioning
// *Action: specify subpartition name and subpartition type
/
03208, 00000, "partitioned type must be specified for a non-composite object"
// *Cause: subpartition type is specified for the space analysis, but the
// object type indicates non-composite partitioning
// *Action: specify partition name and partition type
/
03209, 00000, "DBMS_ADMIN_PACKAGE invalid file/block specification"
// *Cause: The value of file number or block number is outside of limits or
// inconsistent
// *Action: Fix the file number/block number value
/
03210, 00000, "DBMS_ADMIN_PACKAGE invalid option specification"
// *Cause: The value of one of the option parameters is incorrect
// *Action: Fix the option value
/
03211, 00000, "The segment does not exist or is not in a valid state"
// *Cause: The segment specified in the DBMS_SPACE_ADMIN or DBMS_SPACE operation
// does not exist or is not in a state appropriate for this operation
// *Action: Fix the segment specification, or put the segment in the
// appropriate state.
/
03212, 00000, "Temporary Segment cannot be created in locally-managed tablespace"
// *Cause: Attempt to create a temporary segment for sort/hash/lobs in
// in permanent tablespace of kind locally-managed
// *Action: Alter temporary tablespace of user to a temporary tablespace
// or a dictionary-managed permanent tablespace
/
03213, 00000, "Invalid Lob Segment Name for DBMS_SPACE package"
// *Cause: The Lob Segment specified in the DBMS_SPACE operation does not
// exist.
// *Action: Fix the Segment Specification
/
03214, 00000, "File Size specified is smaller than minimum required"
// *Cause: File Size specified for add/resize datafile/tempfile does not
// allow for the minimum required of one allocation unit.
// *Action: Increase the specification for file size
/
03215, 00000, "File Size specified for resize is too small "
// *Cause: File Size specified for resize datafile/tempfile causes
// bitmap control structures to overlap
// *Action: Increase the specification for file size
/
03216, 00000, "Tablespace/Segment Verification cannot proceed"
// *Cause: Corruptions detected during verification whch cannot be dealt with
// *Action: Do manual verification
/
03217, 00000, "invalid option for alter of TEMPORARY TABLESPACE"
// *Cause: invalid option for alter of temporary tablespace was specified
// *Action: Specify one of the valid options: ADD TEMPFILE,
// TEMPFILE ONLINE, TEMPFILE OFFLINE
/
03218, 00000, "invalid option for CREATE/ALTER TABLESPACE"
// *Cause: invalid option for create/alter tablespace of type locally-managed
// *Action: Specify one of the valid options.
/
03219, 00000, "Tablespace '%s' is dictionary-managed, offline or temporary"
// *Cause: Operation which is only applicable to permanent, online,
// locally-managed tablespaces is specified for a tablespace which
// is either dictionary-managed, offline or temporary
// *Action: Reissue operation for a different tablespace, mount the
// tablespace or do not issue it at all, since it does not apply
// for the given tablespace
/
03220, 00000, "DBMS_ADMIN_PACKAGE required parameter is NULL or missing"
// *Cause: Some of the procedures was called with missing or NULL parameters
// *Action: Specify the missing parameter
/
03221, 00000, "Temporary tablespaces and temporary segments must have standard block size"
// *Cause: An attempt was made to do one of the following :
// (1) create a temporary tablespace with a non-standard block
// size or,
// (2) alter an existing permanent tablespace of non-standard
// block size to a temporary tablespace or,
// (3) issue a DDL statement that would result in the creation
// of a temporary segment in a tablespace of non-standard
// block size.
// *Action: (1) If creating a temporary tablespace, do not specify a block
// size different from the standard block size.
// (2) If altering an existing permanent tablespace to a
// temporary tablespace, ensure that it is of standard block size.
// (3) Ensure that the user's temporary tablespace is a
// tablespace having the standard block size.
/
03222, 00000, "average row size and row count must be greater than zero"
// *Cause: Either a bad value passed to dbms_space.create_table_cost()
// or explain plan did not pass through size information.
// *Action: Check the row size parameter in dbms_space.create_table_cost().
// For explain plan, make sure statistics have been computed
// for all source tables in the CREATE TABLE AS SELECT statement.
/
03223, 00000, "Bitmap index block addressable limitation reached"
// *Cause: The limitation of addressability of BMIB (Bitmap Index Block) was
// reached for the current blocksize.
// *Action: If the segment size has grown greater than addressability of BMIB
// (Bitmap Index Block), do the following:
// (1) Partition the table.
// (2) Move the segment to a tablespace having bigger blocksize.
/
03230, 00000, "segment only contains %s blocks of unused space above high water mark"
// *Cause: Attempt to preserve too many blocks.
// *Action: reduce the KEEP amount.
/
03231, 00000, "the INITIAL extent may not be deallocated"
// *Cause: Attempt to deallocate space from the segment which was truncated
// prior to the 7.3 release.
// *Action: increase the KEEP amount, or truncate the segment, and reissue
// the command.
/
03233, 00000, "unable to extend table %s.%s subpartition %s by %s in tablespace %s"
// *Cause: Failed to allocate an extent for table subpartition segment
// in tablespace.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
03234, 00000, "unable to extend index %s.%s subpartition %s by %s in tablespace %s"
// *Cause: Failed to allocate an extent for index subpartition
// segment in tablespace.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.
03235, 00000, "max # extents (%s) reached in table %s.%s subpartition %s"
// *Cause: A table subpartition tried to extend past maxextents
// *Action: If maxextents is less than the system maximum, raise it. Otherwise,
// you must recreate with larger initial, next or pctincrease params
03236, 00000, "max # extents (%s) reached in index %s.%s subpartition %s"
// *Cause: An index subpartition tried to extend past maxextents
// *Action: If maxextents is less than the system max, raise it. Otherwise,
// you must recreate with larger initial, next or pctincrease params.
03237, 00000, "Initial Extent of specified size cannot be allocated in tablespace (%s)"
// *Cause: Too large a size for an initial extent due to freelist
// group specification
// *Action: Reduce number of freelist groups specified for segment
03238, 00000, "unable to extend LOB segment %s.%s subpartition %s by %s in tablespace %s"
// *Cause: An attempt was made to allocate an extent for LOB subpartition
// segment in tablespace, but the extent could not be allocated
// because there is not enough space in the tablespace indicated.
// *Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or
// more files to the tablespace indicated.
03239, 00000, "maxextents (%s) reached in LOB segment %s.%s subpartition %s"
// *Cause: A LOB subpartition segment tried to extend past maxextents.
// *Action: If maxextents is less than the system maximum, raise it.
// Otherwise, recreate the subpartition with larger INITIAL, NEXT,
// or PCTINCREASE parameters.
/
/ Errors 3240 - 3250 reserved for tablespace migration and bitmaps relocation
/
03240, 00000, "User's temporary tablespace same as tablespace being migrated"
// *Cause: Users default temporary tablespace must be different from the
// tablespace being migrated.
// *Action: alter users default temporary tablespace to be different.
03241, 00000, "Invalid unit size"
// *Cause: User specified an invalid unit size for the tablespace
// *Action: Specify the correct unit size. To estimate unit size please
// refer to Oracle Server Administrator's Guide.
03242, 00000, "Tablespace migration retried 500 times"
// *Cause: For migration to complete, temporary segments should not be present
// in the tablespace at the time of migration.
// *Action: Avoid migrating the tablespace when there is heavy temporary
// segment creation going on as with object drops.
03243, 00000, "destination dba overlaps with existing control information"
// *Cause: Cannot overlap control information during relocation
// *Action: Please chose another destination address
03244, 00000, "No free space found to place the control information"
// *Cause: During migration of tablespace found no place to put the control
// information. If during bitmaps relocation, found no space at the
// specified destination.
// *Action: If during migration, add more space to the tablespace and retry
// migration. If during bitmaps relocation, specify a destination
// address where there is enough free space.
03245, 00000, "Tablespace has to be dictionary managed, online and permanent to be able to migrate"
// *Cause: Tablespace was not dictionary managed or online or permanent.
// *Action: Make sure the tablespace is online, permanent and dictionary managed
03246, 00000, "Invalid block number specified"
// *Cause: Control information cannot be placed at the specified dba either
// because the block number specified is beyond the file end or
// the file is not large enough to accomodate the control information
// at that location
// *Action: specify a correct block number
03247, 00000, "Invalid block number specified"
// *Cause: Relocation of bitmaps to the said destination will make
// the tablespace self descriptive
// *Action: Choose another destination dba.
03248, 00000, "Too much of segment creation activity during migration"
// *Cause: Temporary segments were attempted to be created during migration
// *Action: The error is signalled after retrying migration for 500 times.
// Run migration when there is less of segment creation activity is
// going on.
03249, 00000, "Uniform size for auto segment space managed tablespace should have atleast %s blocks"
// *Cause: For the given blocksize, uniform size specified is insufficient
// *Action: Specify larger extent size and retry
03250, 00000, "Cannot mark this segment corrupt"
// *Cause: This segment cannot be marked corrupt because it contains
// data dictionary objects
// *Action: Check the segment information and reissue the command.
03251, 00000, "Cannot issue this command on SYSTEM tablespace "
// *Cause: It is not permitted to migrate SYSTEM tablespace from locally
// managed format to dictionary managed format or relocate bitmaps.
// *Action: Check the tablespace name and procedure name
03252, 00000, "initial extent size not enough for LOB segment"
// *Cause: Fatblock size of LOB segment is too big to fit into the initial
// extent.
// *Action: Specify a smaller fatblock size or create the LOB segment in
// other tablespaces with bigger initial extent size.
03254, 00000, "unable to execute the sql in read only database"
// *Cause: Unable to create a consistent snapshot of the object in a read
// only database. Transaction recovery must be performed before opening the
// database read only.
// *Action: Open the database read write, allow dead transaction recovery
// to complete and then open the database read only.
03261, 00000, "the tablespace %s has only one file"
// *Cause: Dropping file from ts which has a single file
// extent.
// *Action: Cannot make a tablespace fileless
03262, 00000, "the file is non-empty"
// *Cause: Trying to drop a non-empty datafile
// *Action: Cannot drop a non empty datafile
03263, 00000, "cannot drop the first file of tablespace %s"
// *Cause: Trying to drop the first datafile with which ts is created
// *Action: Cannot drop the first datafile with which ts is created
03264, 00000, "cannot drop offline datafile of locally managed tablespace"
// *Cause: Trying to drop offline datafile in lmts
// *Action: Try to drop file afetr making it online
03274, 00000, "both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified"
// *Cause: The DEALLOCATE option and the ALLOCATE option are specified in
// the same command.
// *Action: Choose one of the options or issue two separate commands.
03275, 00000, "duplicate DEALLOCATE option specification"
// *Cause: The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX
// is specified more than once.
// *Action: Specify the option at most once.
03276, 00000, "duplicate ALLOCATE EXTENT option specification"
// MERGE: 2376 RENUMBERED TO 3276
// *Cause: The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX
// is specified more than once.
// *Action: Specify the option at most once.
03277, 00000, "invalid SIZE specified"
// MERGE: 2377 RENUMBERED TO 3277
// *Cause: The specified value must be an integer.
// *Action: Choose an appropriate integer value.
03278, 00000, "duplicate ALLOCATE EXTENT option specification"
// MERGE: 2378 RENUMBERED TO 3278
// *Cause: An option (DATAFILE, SIZE or INSTANCE) was specified more
// than once.
// *Action: Specify each option at most once.
03279, 00000, "invalid INSTANCE specified"
// MERGE: 2379 RENUMBERED TO 3279
// *Cause: The specified value is not recognized as a valid instance name.
// *Action: Use a valid name.
03280, 00000, "invalid DATAFILE filename specified"
// MERGE: 2380 RENUMBERED TO 3280
// *Cause: A character string literal is expected, but not found.
// *Action: Specify filenames using character string literals.
03281, 00000, "invalid ALLOCATE EXTENT option"
// MERGE: 2381 RENUMBERED TO 3281
// *Cause: An option other than DATAFILE, SIZE or INSTANCE was specified.
// *Action: Remove invalid option and retry the command.
03282, 00000, "missing ALLOCATE EXTENT option"
// MERGE: 2382 RENUMBERED TO 3282
// *Cause: No ALLOCATE EXTENT options were specified.
// *Action: Specified one or more of the following options:
// DATAFILE, SIZE or INSTANCE.
03283, 00000, "specified datafile %s does not exist"
// MERGE: 2383 RENUMBERED TO 3283
// *Cause: The datafile does not exist
// *Action: Retry the option with the correct datafile
03284, 00000, "datafile or tempfile %s is not a member of tablespace %s"
// MERGE: 2384 RENUMBERED TO 3284
// *Cause: The specified datafile or tempfile did not belong to the
// tablespace that the object resides in.
// *Action: Retry the option with the correct datafile or tempfile.
03286, 00000, "ALLOCATE EXTENT not valid for HASH CLUSTERS"
// *Cause: The cluster is a hash cluster, and can not use the
// allcoate extent option.
// Action:
03287, 00000, "invalid FREELIST GROUP specified"
// *Cause: The specified FREELIST GROUP number is invalid
// *Action: Choose a number between 1 and # freelist groups for this object
03288, 00000, "both FREELIST GROUP and INSTANCE parameters may not be specified"
// *Cause: Both FREELIST GROUP and INSTANCE were specified in clause
// *Action: Remove one of the two parameters
03289, 00000, "partition name and segment type do not match"
// *Cause: Partition name and segment type specified for space analysis do
// not match
// *Action: Specify type PARTITION if the object is partitioned, specify
// SUBPARTITION if the object is composite
/
/ 3290 - 3295 Truncate Parse and Execution Errors
/
03290, 00000, "Invalid truncate command - missing CLUSTER or TABLE keyword"
// *Cause: Invalid object specification given.
// *Action: Either specify TRUNCATE CLUSTER or TRUNCATE TABLE
03291, 00000, "Invalid truncate option - missing STORAGE keyword"
// *Cause: Expected STORAGE keyword
// *Action: Either specify DROP STORAGE or REUSE STORAGE
03292, 00000, "Table to be truncated is part of a cluster"
// *Cause: The table being truncated is a member of a cluster.
// *Action: Either use TRUNCATE CLUSTER or DROP TABLE
03293, 00000, "Cluster to be truncated is a HASH CLUSTER"
// *Cause: Only INDEX CLUSTERS can be truncated.
// *Action: Drop and recreate the HASH CLUSTER instead of using truncate.
/
/ 3296 - 3299 Reserved for Resizeable Datafiles
/
03296, 00000, "cannot resize datafile - file %s not found"
// *Cause: The specified datafile is not available for resizing.
// *Action: Ensure that the datafile name is valid, and if so, ensure the
// file is accessible.
03297, 00000, "file contains used data beyond requested RESIZE value"
// *Cause: Some portion of the file in the region to be trimmed is
// currently in use by a database object
// *Action: Drop or move segments containing extents in this region prior to
// resizing the file, or choose a resize value such that only free
// space is in the trimmed.
03298, 00000, "cannot shrink datafile - file %s is under hot backup"
// *Cause: Attempt to shrink a datafile while it is under hot backup.
// This is not allowed.
// *Action: Retry shrinking the file after the hot backup completes.
03299, 00000, "cannot create dictionary table %s"
// *Cause: A dictionary table is created upon the first execution of the
// command 'alter database datafile autoextend on' for a database.
// This operation did not succeed. The most probable cause for this
// is insufficient space in the system tablespace.
// *Action: See action for next error message in error stack.
/
/ 3300 - 3499 Reserved for Meiko
/
/ 3500 - 3699 Reserved for Native Macintosh OS-specific errors
/
/ 3700 - 3999 Reserved for Database Sharding errors
/
03700, 00000, "More than one shardspace not allowed with system-managed sharding."
// *Cause: An attempt to add a shardspace to the catalog was attempted
// when a shardspace already existed.
// *Action: Only one shardspace is allowed per system-managed catalog.
// Use the existing shardspace or re-create the catalog with a
// different sharding type.
03701, 00000, "invalid parameter combination: %s and %s"
// *Cause: Mutually exclusive parameters were specified in a command.
// *Action: Verify the parameters and retry command.
03702, 00000, "reserved word used as object name: %s"
// *Cause: A reserved word was used as the name of an object.
// *Action: Verify the parameters and retry command.
03703, 00000, "no sharded database pools exist"
// *Cause: A command was issued which required a sharded database pool,
// but none existed.
// *Action: Add a sharded database pool and retry the command.
03704, 00000, "too many sharded database pools exist"
// *Cause: A command was issued which required a sharded database pool,
// but more than one existed.
// *Action: Remove a sharded database pool and retry the command.
03705, 0000, "must explicitly specify shardgroup name because there could be multiple candidates"
// *Cause: A command was issued without specifying a shardgroup and a default
// shardgroup could not be determined.
// *Action: Do not omit '-shardgroup' when multiple shardgroups exist.
03706, 0000, "must explicitly specify shardspace name because there could be multiple candidates"
// *Cause: A command was issued without specifying a shardspace and a default
// shardspace could not be determined.
// *Action: Do not omit '-shardspace' when multiple shardspaces exist.
03707, 0000, "mandatory environment variable not set at destination: %s"
// *Cause: An environment variable required for the operation was not set
// at the specified destination.
// *Action: Provide a value for the variable and retry operation.
03708, 0000, "shard '%s' does not exist"
// *Cause: The requested shard did not exist.
// *Action: Check the name and try again.
03709, 0000, "input parameter too long"
// *Cause: The input file contained a parameter that was too long.
// *Action: Confirm the file contents and parameter being used and retry the operation.
03710, 0000, "directory does not exist or is not writeable at destination: %s"
// *Cause: A directory required for successful operation did not exist or was
// not writeable at the destination.
// *Action: Confirm that the directory exists and that permissions allow for the creation
// of files.
03711, 0000, "A shard with the same database identifier is a member of a different shardgroup."
// *Cause: A shard with the same database identifier was a member of a shardgroup in
// another shardspace.
// *Action: All shards with the same database identifier must be members of the same shardgroup.
// Specify a different shardroup and retry the operation.
03712, 0000, "A shard with the same database identifier is already in the shardgroup."
// *Cause: A shard with the same database identifier was a member of the specified shardgroup.
// *Action: All shards in a shardgroup must have unique database identifiers.
// Specify a different shardroup and retry the operation.
03713, 00000, "Shard '%s' contained %s chunks."
// *Cause: A shard that contained chunks was removed from the catalog. Those chunks are no
// longer available.
// *Action: This is an informational message only.
03714, 0000, "errors found during chunk recovery"
// *Cause: The chunk recovery procedure was not able to automatically recover
// corrupted chunks.
// *Action: Examine the trace files and manually fix the problems by altering shard
// tablespaces.
03715, 0000, "invalid user %s"
// *Cause: The specified user did not exist on this shard.
// *Action: Ensure that the shard DDL is up to date and re-try.
03716, 0000, "statement too long"
// *Cause: The statement was too long.
// *Action: Reduce the size of the statement to 3800 bytes or less.
03717, 0000, "Shard %s does not exist in the shard pool."
// *Cause: A nonexistent shard was provided for execution.
// *Action: Ensure that the shard exists and try again.
03718, 0000, "Service management is not available at this time because broker configuration %s does not have a registered primary database."
// *Cause: The primary database was not registered.
// Service management requires registration of all primary databases.
// *Action: Wait for new primary database to be registered and try again.
03719, 0000, "Shard character set does not match catalog character set."
// *Cause: The specified shard character set did not match the
// catalog character set.
// *Action: Ensure that the character sets match and try again.
03720, 0000, "Shard national character set does not match catalog national character set."
// *Cause: The specified shard national character set did not match the
// catalog national character set.
// *Action: Ensure that the national character sets match and try again.
/
03721, 0000, "Shard metadata replication."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
03722, 0000, "Target database metadata retrieval and availability check."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
03723, 0000, "Backup 0 creation."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
/
03724, 0000, "Backup 0 replication and restoration."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
/
03725, 0000, "Transition to read-only mode."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
/
03726, 0000, "Backup 1 creation, replication and restoration."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
/
03727, 0000, "User metadata export."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
/
03728, 0000, "Chunk import."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
/
03729, 0000, "Chunk migration is successful. Performing data transition and cleanup."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
03730, 0000, "Chunk migration is not successful. Performing recovery of data on source database and cleanup of target database."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
03731, 0000, "Chunk migration is scheduled."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
/
03732, 0000, "Chunk migration cleanup failed on source."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
/
03733, 0000, "Actual chunk migration failed."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
/
03734, 0000, "Chunk migration failed on target."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
03735, 0000, "Database \"%s\" status shows previous move errors. Chunk migration is scheduled."
// *Document: NO
// *Cause: Chunk migration information message
// *Action:
/
03736, 0000, "Database %s is not a part of the sharded schema."
// *Cause: The specified database was not in the sharded schema.
// *Action: Ensure that the name is correct and try again.
/
03737, 0000, "cannot suspend move for chunk number %s"
// *Cause: The specified chunk move could not be suspended.
// *Action: Either the move has already started or is no longer in the
// the queue. Check the status and try again.
03738, 0000, "cannot remove chunk number %s from the move queue"
// *Cause: The specified chunk could not be removed from the queue.
// *Action: Either the move has already started or is no
// longer in the queue. Check the status and try again.
03739, 0000, "The specified database is not configured to be a catalog."
// *Cause: The specified database was not configured to be a catalog.
// *Action: Specify a valid catalog database and retry the operation.
03740, 0000, "Deployment failed with error: %s"
// *Cause: Unable to successfully complete shard deployment.
// *Action: Check error returned and retry the operation.
03741, 0000, "Could not retrieve default template from shard."
// *Cause: Unable to retrieve default Oracle Database Configuration
// Assistant (DBCA) template from shard.
// *Action: Verify that General_Purpose.dbc exists on shard and
// retry the operation. Alternately, explicity provide
// a template via 'create shard' command options.
03742, 0000, "Move chunk conditions are not met."
// *Cause: Chunk migration pre-check failed because one of the transporting
// tablespaces was either read-only or in hot backup mode.
// *Action: Alter the tablespace to fulfill chunk migration requirements.
03743, 0000, "cannot create service, sharded services must use preferred_all option"
// *Cause: An attempt was made to create a service in a sharded pool
// that specified preferred and available databases.
// *Action: Use only preferred_all option for sharded services.
03744, 0000, "Shard DDL state is not up-to-date."
// *Cause: The requested operation required one or more involved shards to be
// up-to-date with the DDL state of the sharded system.
// *Action: Recover shards, which are in DDL Error state, wait for DDL
// execution to finish on every shard, then retry executing the operation.
03745, 0000, "global service manager not running"
// *Cause: The master global service manager was no longer connected to the catalog.
// *Action: Restart the global service manager and retry operation.
03746, 0000, "The GSMUSER account does not have SYSDG and SYSBACKUP privileges."
// *Cause: The GSMUSER account was not granted SYSDG and SYSBACKUP privileges.
// *Action: Grant the necessary privileges and retry the operation.
03747, 0000, "root table already exists"
// *Cause: New shardspaces could not be added because a root table already existed
// in the sharded database.
// *Action: Drop the root table and retry operation.
03748, 0000, "A deploy operation is already in progress."
// *Cause: A previous request for deploy operation was still in progress.
// *Action: Wait for the previous deploy operation to complete and check if
// another deploy operation is required before resubmitting the
// request.
03749, 0000, "Chunk move cannot be performed at this time."
// *Cause: A database condition that prevents chunk move was detected.
// *Action: Refer to the following error message for additional information.
// Correct the error, if possible, and try the move again.
03750, 0000, "flashback database not enabled"
// *Cause: The flashback database was not enabled on the database being configured.
// *Action: Enable flashback database and retry the operation.
03751, 0000, "user-defined sharding not supported"
// *Cause: User-defined sharding was not supported on the database being configured.
// *Action: Use either system-managed or composite sharding.
03752, 0000, "specified VNCR in use"
// *Cause: The specified valid node check for registration (VNCR) was in use by at
// least one database or shard.
// *Action: Remove any databases or shards that use the VNCR and retry the operation.
03753, 00000, "The procedure cannot be propagated."
// *Cause: SYS.EXEC_SHARD_PLSQL can only execute a limited set of PL/SQL procedures.
// *Action: Execute a procedure manually on each shard.
03754, 00000, "shardgroups not allowed with user-defined sharding"
// *Cause: An attempt was made to create a shardgroup with user-defined sharding.
// *Action: Use either system-managed or composite sharding.
03755, 00000, "current database role is incorrect: %s"
// *Cause: An attempt was made to create a primary shard from a standby database
// or a standby shard from a primary database.
// *Action: Validate the current database role and confirm that it matches the role
// of the specified shardgroup (for system-managed or composite sharding)
// or that it matches the -deploy_as parameter specified in the 'add shard'
// command (for user-defined sharding).
03756, 00000, "The chunk %s is already being split."
// *Cause: There was an incomplete split operation on the same chunk ID.
// *Action: Wait until the split finishes and try again.
03757, 00000, "cannot skip or ignore shard DDL"
// *Cause: An attempt was made to skip a system DDL request such as SPLITCHUNK.
// *Action: Fix the error at the shard, which cause the DDL to fail, and then recover.
03758, 00000, "cannot schedule split during an ongoing move"
// *Cause: There was an incomplete move operation.
// *Action: Wait until the move finishes and try again.
03759, 00000, "This procedure cannot be used to set database parameter %s."
// *Cause: An attempt was made to set a database parameter that cannot be set
// using this procedure.
// *Action: Do not set this parameter using this procedure.
03760, 00000, "Oracle RAC affinity is supported only on a non-sharded Oracle RAC database."
// *Cause: An attempt to enable affinity was made on an Oracle database that was either
// non-RAC, or shard, or shard catalog.
// *Action: Enable affinity on the Oracle RAC non-sharded database.
03761, 00000, "Table is not found."
// *Cause: The table specification was not correct.
// *Action: Specify a valid table name in the ALTER SYSTEM ENABLE AFFINITY
// statement.
03762, 00000, "Partitioned table with this name does not exist."
// *Cause: The specified table was not partitioned.
// *Action: Enable affinity for a partitioned table.
03763, 00000, "Partitioned type '%s' is not supported."
// *Cause: The specified table was not partitioned by either RANGE, LIST or HASH.
// *Action: Enable affinity for a partitioned table.
03764, 00000, "Affinity is already enabled for a different table or service."
// *Cause: A table affinity was already specified.
// Multiple table affinities are currently not supported.
// *Action: Disable affinity for existing table.
03765, 00000, "Service %s has already been deleted by another session."
// *Cause: An attempt was made to delete a service that was already deleted.
// *Action: None. The previous delete request completes and
// the service is removed.
03766, 00000, "Cannot modify service %s because it is being deleted."
// *Cause: An attempt was made to modify a service that was already deleted.
// *Action: None. The previous delete request completes and
// the service is removed.
03767, 00000, "The database to be replaced is not deployed: %s"
// *Cause: An attempt was made to replace a database that was not deployed.
// *Action: Verify that the database to be replaced is in a deployed state.
/
03768, 0000, "The database to be replaced is still up: %s"
// *Cause: An attempt was made to replace a database that was still running.
// *Action: Verify that the database is down and try again.
/
03769, 00000, "job_queue_processes setting must be greater than one"
// *Cause: The job_queue_processes initialization parameter was set to zero or one.
// *Action: Set job_queue_processes to a larger value and retry the operation.
/
03770, 0000, "incorrect shard is given for replace: %s"
// *Cause: An attempt was made to replace a shard with another shard
// that did not have the same data as the original shard.
// *Action: Copy the data correctly before attempting to replace.
// The RMAN utility can be used for this purpose.
/
03771, 00000, "parameter parsing failed with error: %s"
// *Cause: The parameter values passed to SET DATAGUARD_PROPERTY were invalid.
// *Action: Verify the parameter values and retry the operation.
03772, 00000, "attempt to set Oracle Data Guard property failed with error: %s"
// *Cause: The values passed to SET DATAGUARD_PROPERTY were invalid.
// *Action: Verify the input values and retry the operation.
03773, 00000, "SPLIT CHUNK is not supported on a user-defined sharding environment."
// *Cause: A SPLIT CHUNK command was attempted on a user-defined sharding
// environment.
// *Action: This operation is not supported.
03774, 0000, "Cannot replace shard with OGG replication setup: %s"
// *Cause: An attempt was made to replace a shard with Oracle GoldenGate (OGG) as
// replication setup.
// *Action: None. The operation is not supported.
/
03775, 0000, "The new DBID of the standby database does not match the old DBID."
// *Cause: An attempt was made to replace a standby database shard having a
// different database identifier (DBID) than the original shard. All
// members of the Oracle Data Guard configuration must have same DBID.
// *Action: Ensure that the correct shard is specified and that it has the same DBID.
/
03776, 00000, "maximum number of shards exceeded"
// *Cause: A maximum of three primary shards are supported on this platform.
// *Action: Do not attempt to use more than three primary shards.
03777, 00000, "A move operation is already in progress."
// *Cause: A move was already in progress. Multiple concurrent
// user-requested move operations are not permitted.
// *Action: Wait until the current move operation completes before starting
// another.
03778, 00000, "Chunk %s was already being moved to or from another location."
// *Cause: The chunk was already being moved. The current move request
// cannot be superceded.
// *Action: Wait until the existing move completes, or cancel it, before trying
// to move the chunk again.
/
03779, 0000, "failed to update broker configuration with error: %s"
// *Cause: A request to update the broker configuration failed.
// *Action: Check the broker logs for details.
/
03780, 0000, "failed to stop fast-start failover observers with error: %s"
// *Cause: A request to stop observers failed during an attempt to modify
// the Oracle Data Guard broker configuration.
// *Action: Ensure that the primary database shard can connect to the observer.
// Check the broker logs for details.
/
03781, 00000, "error, 'error while executing some of the DDL statements'"
// *Cause: There was an error while executing some of the DDL statements.
// *Action: Check the status of the DDL execution on shards and fix the
// problem.
03782, 00000, "error, 'time out while waiting for the DDL statement execution'"
// *Cause: The specified timeout was reached while waiting for the completion
// of the DDL statement execution.
// *Action: Check the status of the DDL execution on shards and try again.
03783, 00000, "no new shard to deploy"
// *Cause: No new shard was added to deploy.
// *Action: Add a new shard and try again.
/
03784, 0000, "failed to disable fast-start failover with error: %s"
// *Cause: A request to disable fast-start failover failed.
// *Action: Check the broker logs for details.
/
03785, 0000, "database not open"
// *Cause: An operation was attempted that requires the database to be open.
// *Action: Open the database and retry the operation.
/
03786, 0000, "failed to replace primary database shard: %s"
// *Cause: An attempt was made to replace a primary database shard when
// standby databases are alive. This is now allowed.
// *Action: Do not replace a primary when standbys are alive. Replacing a
// primary database is only allowed when all the standby databases
// are down. If this database was the primary before failure, one
// of the standbys need to transition to a primary role by a failover.
// This database can then be replaced as a standby database.
/
03787, 0000, "failed to remove standby shard %s from the broker configuration with error: %s"
// *Cause: A request to remove the shard from the broker configuration failed.
// *Action: Check the broker logs for details.
/
03788, 00000, "Shardspace '%s' does not have a primary shard group added."
// *Cause: An attempt was made to deploy without a primary shard group added
// for each shardspace.
// *Action: Add a primary shard group for each shardspace.
/
03789, 00000, "cannot move chunk when sharded tables are in inconsistent state"
// *Cause: An attempt was made to move chunk when one or more of the sharded
// tables are in inconsistent state.
// *Action: Alter the tables that are inconsistent to make them consistent with
// the root table and then try to move chunk.
/
03790, 00000, "multitenant container database (CDB) already exists: %s"
// *Cause: The specified multitenant container database (CDB)
// was already in existence.
// *Action: Verify the multitenant container database (CDB) name
// and retry the operation.
/
03791, 00000, "CDB for this PDB is not found"
// *Cause: An attempt was made to add a pluggable database (PDB) shard, but
// its container database (CDB) was not part of the sharding
// configuration or did not match the database identifier (DBID).
// *Action: Add the CDB using ADD CBD command before adding the PDB.
// Ensure that the PDB and the CDB have the same DBID.
/
03792, 00000, "CDB already has one of the PDBs as a shard"
// *Cause: One of the pluggable databases (PDB) in a container database
// (CDB) was already added as a shard.
// *Action: Do not add multiple PDBs of the same CDB as shards.
/
/
03793, 00000, "CDB name is invalid: %s"
// *Cause: An invalid multitenant container database (CDB) name was specified.
// *Action: Verify the multitenant container database (CDB) name and retry the operation.
/
03794, 00000, "CDB does not exist: %s"
// *Cause: The specified multitenant container database (CDB) did not exist.
// *Action: Verify the multitenant container database (CDB) name and retry the operation.
/
03795, 00000, "The tablespace set %s is read-only or offline."
// *Cause: Chunk operation was requested while the tablespace set was not online.
// *Action: Ensure that all tablespace sets are online and repeat the operation.
/
03796, 00000, "database already contains sharding metadata"
// *Cause: The specified database already contained sharding metadata and could not be added
// as a new shard.
// *Action: Create a new database and retry the operation.
/
03797, 00000, "cannot deploy this shard for user-defined sharding because database version is not compatible"
// *Cause: The database version was older than version 18.0 and did not support user-defined sharding.
// *Action: Upgrade the database version to deploy the shard in user-defined sharding.
/
03798, 00000, "Source and target database versions are different."
// *Cause: Target database was a different version than the source database.
// *Action: Upgrade the target or source database so that they have the same version.
/
/ Sub-Range 3800-3849 are reserved for sharding C code
/
03800, 00000, "cannot drop values from partitions and subpartitions of a user-defined sharded table"
// *Cause: An attempt was made to modify a partition or a subpartition of a user-defined sharded
// table to drop one or more values.
// *Action: Perform a split partition followed by a drop partition to remove the value from the
// partition.
/
03801, 00000, "incomplete SPLIT PARTITION or SUBPARTITION command"
// *Cause: The ALTER TABLE ... SPLIT PARTITION or SUBPARTITION command did not
// contain an UPDATE INDEXES clause for a user-defined sharded table.
// *Action: Specify the UPDATE INDEXES clause and try again.
/
03803, 00000, "Only REFRESH COMPLETE ON DEMAND USING TRUSTED CONSTRAINTS option is supported for materialized views on sharded tables created on the catalog."
// *Cause: An attempt was made to create a materialized view on a sharded
// table on the shard catalog using the unsupported REFRESH options.
// *Action: Specify the supported option to create such materialized views.
/
03804, 00000, "cannot alter the root table when there are child tables in inconsistent state"
// *Cause: An attempt was made to alter a root table when one or more of its child tables were in
// inconsistent state.
// *Action: Alter the child tables that are in the inconsistent state to make them consistent with the
// root table and then alter the root table.
/
03805, 0000, "missing tablespace clause for LOB column or columns in one or more partitions"
// *Cause: An attempt was made to split a table partition with LOB columns
// without specifying tablespaces for all LOB columns in each resulting
// partition after the split.
// *Action: Use LOB(<column names>) STORE AS clause in each partition to specify
// tablespaces for all the LOB columns in the table.
/
03807, 00000, "An all shard GRANT command cannot contain any local objects."
// *Cause: A GRANT command that contained local objects was issued with
// shard DDL enabled.
// *Action: Remove the local objects from the command, or issue it with
// shard DDL disabled.
/
/
03808, 00000, "shard key or partition set key columns cannot be columns that accept NULL values"
// *Cause: An attempt was made to create a sharded table with shard key or partition set key columns
// that accept NULL values.
// *Action: Create the sharded table with shard key or partition set key columns having a NOT NULL
// constraint.
/
03812, 00000, "cannot specify NULL as partition bound or partitionset bound in sharding"
// *Cause: An attempt was made to create a sharded table partition or partitionset with NULL value bound.
// *Action: Create the sharded table partition or partitionset with bound values that is not NULL.
/
03813, 00000, "list partition method expects a single partitioning column in user-defined sharding"
// *Cause: An attempt was made to create a sharded table with multiple columns as partitioning key.
// *Action: Create the sharded table with a single column as the partitioning key.
/
03814, 00000, "cannot set a column as UNUSED in sharded tables"
// *Cause: An attempt was made to alter a sharded table and set a column as UNUSED.
// *Action: Do not alter the sharded table to set a column as UNUSED.
/
/ Sub-Range 3900-3949 are reserved for sharding C code
/
03900, 00000, "shard internal database link cannot be altered or dropped"
// *Cause: An attempt was made to directly alter or drop an internal
// database link for sharding, which is not allowed.
// *Action: Do not alter or drop shard internal database links.
/
03901, 00000, "shard key or partition set key column cannot be renamed"
// *Cause: An attempt was made to rename a shard key column or a partition
// set key column of a sharded table, which is not allowed.
// *Action: Do not rename shard key or partition set key column of a sharded
// table.
/
03902, 00000, "cannot shrink a system-managed or composite sharded table with primary key or any sharded table with functional index"
// *Cause: An attempt was made to shrink a system-managed or composite
// sharded table with primary key or a sharded table with functional
// index, which is not allowed.
// *Action: Do not perform shrink such tables.
/
03903, 00000, "The Flashback Table operation is not supported on sharded or duplicated tables."
// *Cause: An attempt was made to perform the Flashback Table operation on a
// sharded or duplicated table, which is not allowed.
// *Action: Do not perform a Flashback Table operation on sharded or
// duplicated tables.
/
03904, 00000, "The sharding virtual colummn cannot be modified."
// *Cause: An attempt was made to modify the sharding virtual column,
// SYS_HASHVAL, which is not allowed.
// *Action: Do not modify the sharding virtual column.
/
03905, 00000, "cannot use the same tablespace for multiple partitions of a user-defined sharded table"
// *Cause: An attempt was made to use a tablespace for multiple partitions of a user-defined sharded table.
// *Action: Use different tablespaces for different partitions in a user-defined sharded table.
/
03906, 00000, "invalid tablespace name %s specified for the partition %s"
// *Cause: An attempt was made to specify a tablespace name for a partition, subpartition, or LOBs
// that did not belong to the shardspace.
// *Action: Specify a tablespace name that belongs to the same shardspace.
/
03907, 00000, "REF data type is not supported for duplicated tables."
// *Cause: An invalid option was specified while creating duplicated tables.
// *Action: Verify the specified option.
/
03908, 00000, "cannot drop duplicated table materialized views on shards"
// *Cause: An attempt was made to manually drop materialized views of a duplicated table on shard databases.
// *Action: Drop the duplicated table on the catalog database, if required.
/
03909, 00000, "cannot set parameter SHRD_DUPL_TABLE_REFRESH_RATE in SPFILE"
// *Cause: An attempt was made to set parameter SHRD_DUPL_TABLE_REFRESH_RATE in SPFILE.
// *Action: Set the parameter with SCOPE = MEMORY.
/
03910, 00000, "cannot drop duplicated table materialized view log"
// *Cause: An attempt was made to drop materialized view logs created on duplicated tables.
// *Action: Drop the duplicated table, if required.
/
03911, 00000, "column %s is not supported for duplicated tables"
// *Cause: An invalid option was specified while creating duplicated tables.
// *Action: Verify the specified option.
/
03912, 00000, "option %s is not supported for duplicated tables"
// *Cause: An invalid option was specified while creating duplicated tables.
// *Action: Verify the specified option.
/
03913, 00000, "A tablespace cannot be referenced at the table level."
// *Cause: An attempt was made to reference a tablespace at the table level.
// *Action: Verify the specified option.
/
03914, 00000, "cannot use tablespace %s for partition %s"
// *Cause: At attempt was made to specify a tablespace that was used for a different
// chunk or partition in the tables already created.
// *Action: Verify the specified option.
/
03915, 00000, "cannot purge an individual chunk tablespace"
// *Cause: An attempt was made to purge an individual chunk tablespace
// which is a part of a tablespace set.
// *Action: Verify the specified option.
/
03916, 00000, "The creation of Information Lifecycle Management (ILM) policy is not supported for duplicated tables."
// *Cause: An invalid option was specified while creating duplicated tables.
// *Action: Verify the specified option.
/
03917, 00000, "invalid partition set value"
// *Cause: The attempt to update or insert into a partition set column failed.
// *Action: Ensure that inserted partition set values are within the shard partition set values.
/
03918, 00000, "invalid number of partitions specified for the child table"
// *Cause: An attempt was made to create a child table with a number of partitions
// not equal to the number of partitions in the parent table.
// *Action: Create the child table with a number of partitions that equal the number
// of partitions in the parent table.
/
03919, 00000, "invalid list value or values specified for the partition %s"
// *Cause: The list values specified for a partition of the table could not exactly
// be matched with the list values of the corresponding partition of the parent table.
// *Action: Create the child table with the list values of a partition that matches the
// list values of the corresponding partition in the parent table.
/
03920, 00000, "invalid range value specified for the partition %s"
// *Cause: The range value specified for a partition of the table could not be
// matched with the range value of the corresponding partition of the parent table.
// *Action: Create the child table with the range values of a partition that match the
// range values of the corresponding partition in the parent table.
/
03921, 00000, "invalid number of list values specified for the partition %s"
// *Cause: The number of list values specified for a partition of the table was not equal to the
// number of list values specified for the corresponding partition of the parent table.
// *Action: Create the child table with partitions that have the same number of list values
// as the corresponding partition in the parent table.
/
03922, 00000, "invalid range or list value specified for the partitionset %s"
// *Cause: The value specified for the range or list of the partitionset did not exactly
// match the value specified for the partitionset in the parent table.
// *Action: Create the child table with partitionsets whose values for range or list
// exactly matches the values specified for the partitionset in the parent table.
/
03923, 00000, "cannot drop a tablespace set used for a composite sharded table"
// *Cause: The tablespace was used for a composite sharded table and cannot
// be dropped unless the contents are dropped manually.
// *Action: Drop the contents of the tablespace set first and then drop the tablespace set.
/
03924, 00000, "cannot alter a user-defined sharded table directly in the shard database"
// *Cause: An attempt was made to alter a user-defined sharded table directly on the shard database.
// *Action: All alter operations on a user-defined sharded table must be executed on the catalog database
// to maintain consistency in the shards.
/
03925, 00000, "duplicate partitionset name"
// *Cause: Name of a partitionset of a table being created is not unique.
// *Action: rename partitionset(s) to ensure that their names are unique among
// partitionsets of the table being created.
/
03926, 00000, "DEFAULT tablespace is not supported for sharded tables or indexes."
// *Cause: An attempt was made to use DEFAULT tablespaces for sharded tables or indexes.
// *Action: Use valid tablespace or tablespace set names for sharded tables
// and indexes on sharded tables.
/
03927, 00000, "invalid use of STORE IN clause for a sharded table or index"
// *Cause: The STORE IN (tablespace list) clause was used to specify tablespaces for partitions
// of a sharded table or for partitions of an index where the sharded table did not
// have subpartitions or the subpartition method was not hash.
// *Action: Use the TABLESPACE SET clause or SUBPARTITION TEMPLATE clause to specify tablespaces
// for table and index partitions or table subpartitions, respectively.
/
03929, 00000, "CREATE TABLE...AS SELECT statement is not supported for sharded tables."
// *Cause: An attempt was made to create a sharded table AS SELECT from another table, which is not supported.
// *Action: Do not create any sharded table AS SELECT from other tables.
/
03930, 00000, "Editions are not supported for sharded tables."
// *Cause: An attempt was made to create a sharded table using editions, which is not supported.
// *Action: Do not create any sharded table using editions.
/
03931, 00000, "maximum number of sharding columns for consistent hash is 15."
// *Cause: The number of columns in a sharding key column list exceeded
// the legal limit of 15.
// *Action: Modify the sharding key column list so that it consists of at most
// 15 columns.
/
03932, 00000, "cannot create the default shard tablespace on the catalog when shard DDL is enabled"
// *Cause: An attempt was made to create a tablespace in the catalog which is created on the
// shards by default in user-defined sharding.
// *Action: Disable shard DDL on the catalog if the tablespace has to be created on the catalog.
/
03933, 00000, "An all-shard object cannot depend on any local objects."
// *Cause: An attempt was made to create or alter an all-shard object to
// depend on a local user object, which is not allowed.
// *Action: Do not create or alter an all-shard object to depend on any local
// user objects.
/
03934, 00000, "An all-shard index cannot be created on local tables."
// *Cause: An attempt was made to create an all-shard index on a local user
// table, which is not allowed.
// *Action: Do not create such indices.
/
03935, 00000, "A sharded table cannot have columns that depend on local objects."
// *Cause: An attempt was made to create or alter a sharded table to
// contain columns that depend on local objects, which is not allowed.
// *Action: Do not create or alter sharded tables to have such columns.
/
03936, 00000, "cannot use a sharded tablespace for non-sharding purposes"
// *Cause: An attempt was made to use a sharded tablespace for non-sharding purposes.
// *Action: Use a normal tablespace instead of a sharded tablespace.
/
03937, 00000, "The creation of Information Lifecycle Management (ILM) policy is not supported for duplicated tables."
// *Cause: An invalid option was specified while altering duplicated tables.
// *Action: Verify the specified option.
/
03938, 00000, "cannot create duplicated tables on a shard database"
// *Cause: An attempt was made to create a duplicated table
// on a shard database, which is not supported.
// *Action: Connect to each shard and create the table locally.
/
03939, 00000, "cannot specify a data file name for a tablespace in a sharding setup"
// *Cause: The data file name was specified during creation of the tablespace.
// Only Oracle Managed Files are supported by a tablespace used in a sharding setup.
// *Action: Remove the file name from the data file definition.
03940, 00000, "A trigger cannot be created on any sharded table."
// *Cause: An attempt was made to create a trigger on a sharded table, which
// is not allowed.
// *Action: Do not create such triggers.
/
03941, 00000, "A shard key or partition set key column cannot be a sequence."
// *Cause: An attempt was made to create a sharded table having a shard key
// or a partition set key column based on a sequence, which is not
// allowed.
// *Action: Do not use sequences for shard key or partition set key columns.
/
03942, 00000, "cannot create temporary tablespace sets"
// *Cause: An attempt was made to create a temporary tablespace set, which is
// not allowed.
// *Action: Do not create temporary tablespace sets.
/
03943, 00000, "zone maps are not supported on sharded tables"
// *Cause: An attempt was made to create a materialized zone map on a sharded
// table, which is not supported.
// *Action: Do not create materialized zone maps on sharded tables.
03944, 00000, "cannot specify PARENT clause for duplicated tables"
// *Cause: An invalid option was specified while creating duplicated tables.
// *Action: Verify the specified option.
/
03945, 00000, "Cannot perform the operation on the child table before performing the same operation on the root table"
// *Cause: An attempt was made to alter the child table to add or drop or split a partition
// whose root partition has not been added or dropped or split yet.
// *Action: Alter the root table to add or drop or split the partition before trying to add or drop
// or split the partition in the child table.
/
03946, 00000, "Operation is not supported on a user-defined sharded table"
// *Cause: An attempt was made to perform an unsupported partition operation on
// a user-defined sharded table.
// *Action: Do not perform the operation.
/
03947, 00000, "cannot create an autolist or interval partitioned sharded table"
// *Cause: An attempt was made to create an autolist or interval partitioned
// sharded table.
// *Action: Create a sharded table that is not an autolist or interval partitioned.
/
03948, 00000, "A DEFAULT partition or partition set cannot be specified for a sharded table."
// *Cause: An attempt was made to create a partition or partition set with a DEFAULT high value
// on a sharded table.
// *Action: Do not create a partition or partition set with a DEFAULT high value.
03949, 00000, "password is required for encypted columns in a sharded table"
// *Cause: An attempt was made to create a sharded table containing an
// encrypted column without specifying a password.
// *Action: Provide a password for the encrypted column(s) in the CREATE
/ SHARDED TABLE statement.
/
/ Sub-Range 3950-3999 are reserved for OGG/DB sharding
/
3950, 00000, "GoldenGate error: %s"
// *Cause: An operation failed when performed using Oracle GoldenGate.
// *Action: Correct the error specified in Oracle GoldenGate output.
/
3951, 00000, "Invalid OGG service descriptor - OGG message: %s"
// *Cause: One or more components of the Oracle GoldenGate (OGG) service descriptor
// could not be verified.
// *Action: Refer to the Oracle GoldenGate message for the required action.
/
3952, 00000, "OGG %s URI: %s is not reachable - HTTP message: %s"
// *Cause: Oracle GoldenGate (OGG) AdminService or DistributionService could not be reached.
// *Action: Refer to the HTTP message for the required action.
/
3953, 00000, "OGG %s URI: %s failed to %s %s: %s - OGG message: %s"
// *Cause: Oracle GoldenGate (OGG) AdminService or DistributionService operation failed.
// *Action: Refer to the Oracle GoldenGate message for the required action.
/
3954, 00000, "OGG sharding function called in an invalid context: %s function called in %s"
// *Cause: Internal error. An Oracle GoldenGate (OGG) sharding functionality
// was called in an invalid context, for example, catalog function in shard or
// vice versa.
// *Action: Contact Oracle Support Services.
/
3955, 00000, "Invalid combination of OGG deployment parameters specified for shardgroup: %s (S=%s, C=%s, R=%s)"
// *Cause: The values specified for Oracle GoldenGate (OGG) deployment parameters
// (number of shards - S, number of chunks - C and replication factor - R)
// for the shardgroup were not compatible with each other.
// *Action: Ensure that the following invariants hold for the shardgroup:
// number of chunks >= number of shards
// number of shards >= replication factor
/
3956, 00000, "Invalid entry in the OGG command payload: %s"
// *Cause: Internal error. The payload for Oracle GoldenGate (OGG) command sent from
// the sharding catalog to the shard database contained an invalid entry.
// *Action: Contact Oracle Support Services.
/
3957, 00000, "Sharding configuration parameter '%s' is not set in the shard database."
// *Cause: Internal error. A database initialization parameter required by the
// shard database was not set during deployment.
// *Action: Contact Oracle Support Services.
/
3958, 00000, "Failure to remove shard: %s - %s"
// *Cause: A request to remove a shard database failed.
// *Action: Check the shard error message for details.
/
3959, 00000, "chunk allocation error in shardgroup: %s - %s"
// *Cause: Internal error. Chunk allocation algorithm for Oracle GoldenGate (OGG)
// detected inconsistencies in the sharding configuration.
// *Action: Contact Oracle Support Services.
/
3960, 00000, "Chunk number '%s' already exists on the target shard."
// *Cause: An invalid chunk number or target shard name was provided.
// *Action: Check the chunk number, shard name and try again.
/
3961, 00000, "A move chunk request already exists for chunk number '%s' from the source shard."
// *Cause: An invalid chunk number or source shard name was provided.
// *Action: Check the chunk number, shard name and try again.
/
3962, 00000, "invalid SPLIT PARTITION command for a user-defined sharded object"
// *Cause: Tablespaces for resulting partitions in a SPLIT PARTITION
// command were either unspecified or in use.
// *Action: An unused tablespace should be provided for each resulting partition
// of the SPLIT PARTITION command.
/
3964, 00000, "updated or deleted row of duplicated table is not synchronized with catalog"
// *Cause: An attempt was made to update or delete the row of a duplicated table
// that was recently inserted on this shard database. This table did not
// have primary key; therefore, any modifications of the inserted row
// cannot be performed until after the next duplicated table refresh
// (the default timeout is 1 minute).
// *Action: Wait until the duplicated table is refreshed and repeat the operation.
/
3965, 00000, "updated or deleted row of duplicated table is not found on catalog"
// *Cause: An attempt was made to update or delete the row of a materialized view
// on a shard database but the materialized view was not synchronized with the
// catalog and the affected rows were already deleted from the catalog by
// another shard database.
// *Action: Wait until the duplicated table is refreshed and repeat the operation.
/
3966, 00000, "cannot alter duplicated table materialized views on shards"
// *Cause: An attempt was made to manually alter materialized views of a duplicated table on shard databases.
// *Action: Alter the duplicated table on the catalog database, if required.
/
3967, 00000, "failed to rename the materialized view log when renaming duplicated table"
// *Cause: An attempt was made to rename the duplicated table, and the internal statement to rename the materialized view log failed.
// *Action: Drop the duplicated table, and re-create it.
/
/
/
/ 4000-4099 invalid parameter errors
/
04000, 00000, "the sum of PCTUSED and PCTFREE cannot exceed 100"
// *Cause: the sum of PCTUSED and PCTFREE for a cluster or table exceeds 100
// *Action: create the table/cluster specifying values whose sum is <= 100
04001, 00000, "sequence parameter %s must be an integer"
// *Cause: %s (a sequence parameter) specified was not an integer
// *Action: create the sequence, giving the specified parameter an integer value
04002, 00000, "INCREMENT must be a non-zero integer"
// *Cause: a sequence increment was specified to be zero
// *Action: specify the increment to be a non-zero value
04003, 00000, "sequence parameter %s exceeds maximum size allowed (%s digits)"
// *Cause: %s (a sequencer parameter) had too many digits
// *Action: specify the parameter with the allowed number of digits
04004, 00000, "MINVALUE must be less than MAXVALUE"
// *Cause: MINVALUE was specified to be greater than or equal to MAXVALUE
// *Action: specify a MINVALUE that is less than MAXVALUE
04005, 00000, "INCREMENT must be less than MAXVALUE minus MINVALUE"
// *Cause: the INCREMENT specified is >= MAXVALUE-MINVALUE
// *Action: specify an INCREMENT that is < MAXVALUE-MINVALUE
04006, 00000, "START WITH cannot be less than MINVALUE"
// *Cause: the given starting value is less than MINVALUE
// *Action: make sure that the starting value is >= MINVALUE
04007, 00000, "MINVALUE cannot be made to exceed the current value"
// *Cause: the given MINVALUE would be greater than the current value
// *Action: always make sure that MINVALUE is <= the current value
04008, 00000, "START WITH cannot be more than MAXVALUE"
// *Cause: the starting value would be larger than MAXVALUE
// *Action: make sure that the starting value is less than MAXVALUE
04009, 00000, "MAXVALUE cannot be made to be less than the current value"
// *Cause: the current value exceeds the given MAXVALUE
// *Action: make sure that the new MAXVALUE is larger than the current value
04010, 00000, "the number of values to CACHE must be greater than 1"
// *Cause: the value in the CACHE clause was one
// *Action: specify NOCACHE, or a value larger than one
04011, 00000, "sequence %s must range between %s and %s"
// *Cause: the value specified for one of the sequence parameters exceeds limits
// *Action: specify parameter within these limits
04012, 00000, "object is not a sequence"
// *Cause: the object specified cannot have sequence ddl's performed on it
// *Action: re-enter the statement being careful with the spelling of the name
04013, 00000, "number to CACHE must be less than one cycle"
// *Cause: number to CACHE given is larger than values in a cycle
// *Action: enlarge the cycle, or cache fewer values
04014, 00000, "descending sequences that CYCLE must specify MINVALUE"
// *Cause: sequences that cycle must have their wrap-wrap specified
// *Action: re-create the sequence, specifying its wrap-value
04015, 00000, "ascending sequences that CYCLE must specify MAXVALUE"
// *Cause: sequences that cycle must have their wrap-wrap specified
// *Action: re-create the sequence, specifying its wrap-value
04016, 00000, "sequence %s no longer exists"
// *Cause: sequence was dropped while processing its next value.
// *Action: re-create the sequence
04017, 00000, "invalid value %s (length = %s) for parameter MAX_DUMP_FILE_SIZE"
// *Cause: The string supplied for the parameter MAX_DUMP_FILE_SIZE was not
// an integer, an integer followed by 'K', 'M', or 'G', nor the
// special value UNLIMITED.
// *Action: Provide a proper value for this parameter.
04018, 00000, "The '%s' parameter cannot be altered in Oracle Database Standard Edition or Oracle Database Express Edition."
// *Cause: An attempt was made to alter the specified parameter in the Standard Edition
// or Express Edition.
// *Action: Do not attempt to alter the parameter in the Standard Edition
// or Express Edition.
/
/ 4020-4029 Reserved for Library Cache errors
/
04020, 00000, "deadlock detected while trying to lock object %s%s%s%s%s"
// *Cause: While trying to lock a library object, a deadlock is detected.
// *Action: Retry the operation later.
04021, 00000, "timeout occurred while waiting to lock object %s%s%s%s%s"
// *Cause: While waiting to lock a library object, a timeout occurred.
// *Action: Retry the operation later.
04022, 00000, "nowait requested, but had to wait to lock dictionary object"
// *Cause: Had to wait to lock a library object during a nowait request.
// *Action: Retry the operation later.
04023, 00000, "Object %s%s%s%s%s could not be validated or authorized"
// *Cause: A number of attempts were made to validate or authorize an
// object but failed.
// *Action: Please report this error to Oracle Support Services.
04024, 00000, "self-deadlock detected while trying to mutex pin cursor %s"
// *Cause: While trying to mutex pin a cursor, a self-deadlock is detected.
// *Action: Retry the operation later.
04025, 00000, "maximum allowed library object lock allocated for %s%s%s%s%s"
// *Cause: Too many active locks for the object has been allocated. This error
// can be a result of too many cursors kept open per session.
// *Action: Close cursors, reduce session_cached_cursors value.
04027, 00000, "self-deadlock during automatic validation for object %s.%s"
// *Cause: An attempt was made to validate an invalidated object but it failed
// because of a self-deadlock.
// *Action: Identify the root cause of the self-deadlock and take corrective
// action, e.g. compile the invalidated object separately.
04028, 00000, "cannot generate diana for object %s%s%s%s%s"
// *Cause: Cannot generate diana for an object because of lock conflict.
// *Action: Please report this error to your support representative.
04029, 00000, "error ORA-%s occurred when querying %s%s%s"
// *Cause: The table or view being queried might be missing. The error
// number indicates the error.
// *Action: Fix the error.
/
/ 4030-4039 Reserved for Memory Manager errors
/
04030, 00000, "out of process memory when trying to allocate %s bytes (%s,%s)"
// *Cause: Operating system process private memory was exhausted.
// *Action:
04031, 00000, "unable to allocate %s bytes of shared memory (\"%s\",\"%s\",\"%s\",\"%s\")"
// *Cause: More shared memory is needed than was allocated in the shared
// pool or Streams pool.
// *Action: If the shared pool is out of memory, either use the
// DBMS_SHARED_POOL package to pin large packages,
// reduce your use of shared memory, or increase the amount of
// available shared memory by increasing the value of the
// initialization parameters SHARED_POOL_RESERVED_SIZE and
// SHARED_POOL_SIZE.
// If the large pool is out of memory, increase the initialization
// parameter LARGE_POOL_SIZE.
// If the error is issued from an Oracle Streams or XStream process,
// increase the initialization parameter STREAMS_POOL_SIZE or increase
// the capture or apply parameter MAX_SGA_SIZE.
04032, 00000, "pga_aggregate_target must be set before switching to auto mode"
// *Cause: attempt to set workarea_size_policy to AUTO while
// pga_aggregate_target is not specified
// *Action: before setting workarea_size_policy, set pga_aggregate_target
// to a value representing the total private memory available to
// the instance. This total is generally the total physical memory
// available in the system minus what is needed for the SGA minus
// what is needed for the operating system (e.g. 500MB)
04033, 00000, "Insufficient memory to grow pool"
// *Cause: The system had insufficient memory to grow the pool to the
// specified size.
// *Action: Specify a smaller value to grow the pool.
04034, 00000, "unable to shrink pool to specified size"
// *Cause: The pool could not shrink to the specified size as it could not
// free memory.
// *Action: Specify a larger value to which to shrink the pool to.
04035, 00000, "unable to allocate %s bytes of shared memory in shared object cache \"%s\" of size \"%s\""
// *Cause: More shared memory is needed than was allocated in the shared
// object cache.
// *Action:
04036, 00000, "PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT"
// *Cause: Private memory across the instance exceeded the limit specified
// in the PGA_AGGREGATE_LIMIT initialization parameter. The largest
// sessions using Program Global Area (PGA) memory were interrupted
// to get under the limit.
// *Action: Increase the PGA_AGGREGATE_LIMIT initialization parameter or reduce
// memory usage.
04037, 00000, "unable to allocate memory on another instance in the cluster"
// *Cause: The instance ran out of memory as its allocated memory was less than
// the required memory.
// *Action: Refer to the alert log for the instance which ran out of memory.
/
/ 4040-4059 Reserved for Stored Procedure errors
/
04041, 00000, "package specification must be created first before creating package body"
// *Cause: Attempt to create a package body before creating its package
// specification.
// *Action: Create the package specification first before creating the
// package body.
04042, 00000, "procedure, function, package, or package body does not exist"
// *Cause: Attempt to access a procedure, function, package, or package body
// that does not exist.
// *Action: Make sure the name is correct.
04043, 00000, "object %s does not exist"
// *Cause: An object name was specified that was not recognized by the system.
// There are several possible causes:
// - An invalid name for a table, view, sequence, procedure, function,
// package, or package body was entered. Since the system could not
// recognize the invalid name, it responded with the message that the
// named object does not exist.
// - An attempt was made to rename an index or a cluster, or some
// other object that cannot be renamed.
// *Action: Check the spelling of the named object and rerun the code. (Valid
// names of tables, views, functions, etc. can be listed by querying
// the data dictionary.)
04044, 00000, "procedure, function, package, or type is not allowed here"
// *Cause: A procedure, function, or package was specified in an
// inappropriate place in a statement.
// *Action: Make sure the name is correct or remove it.
04045, 00000, "errors during recompilation/revalidation of %s.%s"
// *Cause: This message indicates the object to which the following
// errors apply. The errors occurred during implicit
// recompilation/revalidation of the object.
// *Action: Check the following errors for more information, and
// make the necessary corrections to the object.
04046, 00000, "results of compilation are too large to support"
// *Cause: Attempt to compile and store a large stored procedure that results
// in compilation data that is too large for the system to support
// or store.
// *Action: Reduce the size of the store procedure by splitting it into
// smaller stored procedures.
04047, 00000, "object specified is incompatible with the flag specified"
// *Cause: The object type implied by the flag does not match the type
// of object specified.
// *Action: Specify the correct object, or use the appropriate flag
04050, 00000, "invalid or missing procedure, function, or package name"
// *Cause: The required procedure, function, or package name is invalid
// or missing.
// *Action: Specify a valid name.
04051, 00000, "user %s cannot use database link %s.%s"
// *Cause: During forwarding of a remote object access, an attempt was
// made to use a non-existent database link or one owned by
// a user other than the logon user or PUBLIC.
// *Action: Change your database link structure so that all indirect remote
// accesses are done from the same userid that originates the
// request.
04052, 00000, "error occurred when looking up remote object %s%s%s%s%s"
// *Cause: An error occurred when trying to look up a remote object.
// *Action: Fix the error. Make sure the remote database system has run
// CATRPC.SQL to create necessary views used for querying or looking up
// objects stored in the database.
04053, 00000, "error occurred when validating remote object %s%s%s%s%s"
// *Cause: An error occurred when trying to validate a remote object.
// *Action: Fix the error. Make sure the remote database system has run
// CATRPC.SQL to create necessary views used for querying or looking up
// objects stored in the database.
04054, 00000, "database link %s does not exist"
// *Cause: During compilation of a PL/SQL block, an attempt was made to use
// a non-existent database link.
// *Action: Either use a different database link or create the database link.
04055, 00000, "Aborted: \"%s\" formed a non-REF mutually-dependent cycle with \"%s\"."
// *Cause: This compilation was aborted because the library unit that was
// compiled would have formed a non-REF mutually-dependent cycle with
// some other library units. This happens when an attempt is made to
// compile types that have attributes of other types that may
// participate in a cycle with this type.
// Example:
// create type t1;
// create type t2 (a t1);
// create type t1 (a t2);
// *Action: Break the cycle (possibly by adding a REF or by using another
// type).
/
/ 4060-4069 Reserved for Stored Procedure Execution errors
/
04060, 00000, "insufficient privileges to execute %s"
// *Cause: Attempt to execute a stored procedure without
// sufficient privileges.
// *Action: Get necessary privileges.
04061, 00000, "existing state of %s has been invalidated"
// *Cause: Attempt to resume the execution of a stored procedure using the
// existing state which has become invalid or inconsistent
// with the stored procedure because the procedure has been altered
// or dropped.
// *Action: Try again; this error should have caused the existing state of
// all packages to be re-initialized.
04062, 00000, "%s of %s has been changed"
// *Cause: Attempt to execute a stored procedure to serve
// an RPC stub which specifies a timestamp or signature that is
// different from the current timestamp/signature of the procedure.
// *Action: Recompile the caller in order to pick up the new timestamp.
04063, 00000, "%s has errors"
// *Cause: Attempt to execute a stored procedure or use a view that has
// errors. For stored procedures, the problem could be syntax errors
// or references to other, non-existent procedures. For views,
// the problem could be a reference in the view's defining query to
// a non-existent table.
// Can also be a table which has references to non-existent or
// inaccessible types.
// *Action: Fix the errors and/or create referenced objects as necessary.
04064, 00000, "not executed, invalidated %s"
// *Cause: Attempt to execute a stored procedure that has
// been invalidated.
// *Action: Recompile it.
04065, 00000, "not executed, altered or dropped %s"
// *Cause: Attempt to execute a stored procedure that has
// been altered or dropped thus making it not callable from the
// calling procedure.
// *Action: Recompile its dependents.
04066, 00000, "non-executable object, %s"
// *Cause: Attempt to execute a non-procedure.
// *Action: Make sure that a correct name is given.
04067, 00000, "not executed, %s does not exist"
// *Cause: Attempt to execute a non-existent stored procedure.
// *Action: Make sure that a correct name is given.
04068, 00000, "existing state of packages%s%s%s has been discarded"
// *Cause: One of errors 4060 - 4067 when attempt to execute a stored
// procedure.
// *Action: Try again after proper re-initialization of any application's
// state.
04069, 00000, "cannot drop or replace a library with table dependents"
// *Cause: An attempt was made to drop or replace a library that has
// dependents. There could be a table which depends on type which
// depends on the library being dropped.
// *Action: Drop all table(s) depending on the type, then retry.
/
/ 4070-4099 Reserved for Trigger errors
/
04070, 00000, "invalid trigger name"
// *Cause: An invalid trigger name was specified.
// *Action: Verify that trigger name is not a reserved keyword.
04071, 00000, "missing BEFORE, AFTER or INSTEAD OF keyword"
// *Cause: The trigger statement is missing the BEFORE/AFTER/INSTEAD OF clause.
// *Action: Specify either BEFORE, AFTER or INSTEAD OF.
04072, 00000, "invalid trigger type"
// *Cause: An invalid trigger type was given.
// *Action: Specify either INSERT, UPDATE or DELETE.
04073, 00000, "column list not valid for this trigger type"
// *Cause: A column list was specified for a non-update trigger type.
// *Action: Remove the column list.
04074, 00000, "invalid REFERENCING name"
// *Cause: An invalid name was given in the referencing clause.
// *Action: Verify the referencing name is not a reserved word.
04075, 00000, "invalid trigger action"
// *Cause: An statement was given for the trigger action.
// *Action: Re-specify the trigger action.
04076, 00000, "invalid NEW or OLD specification"
// *Cause: An invalid NEW or OLD specification was given for a column.
// *Action: Re-specify the column using the correct NEW or OLD specification.
04077, 00000, "WHEN clause cannot be used with table level triggers"
// *Cause: The when clause can only be specified for row level triggers.
// *Action: Remove the when clause or specify for each row.
04078, 00000, "OLD and NEW values cannot be identical"
// *Cause: The referencing clause specifies identical values for NEW and OLD.
// *Action: Re-specify either the OLD or NEW referencing value.
04079, 00000, "invalid trigger specification"
// *Cause: The create TRIGGER statement is invalid.
// *Action: Check the statement for correct syntax.
04080, 00000, "trigger '%s' does not exist"
// *Cause: The TRIGGER name is invalid.
// *Action: Check the trigger name.
04081, 00000, "trigger '%s' already exists"
// *Cause: The TRIGGER name or type already exists.
// *Action: Use a different trigger name or drop the trigger which is of the
// same name.
04082, 00000, "NEW or OLD references not allowed in table level triggers"
// *Cause: The trigger is accessing "new" or "old" values in a table trigger.
// *Action: Remove any new or old references.
04083, 00000, "invalid trigger variable '%*.s'"
// *Cause: The variable referenced in the trigger body is invalid.
// *Action: See the manual for valid trigger variable types.
04084, 00000, "cannot change NEW values for this trigger type"
// *Cause: New trigger variables can only be changed in before row
// insert or update triggers.
// *Action: Change the trigger type or remove the variable reference.
04085, 00000, "cannot change the value of an OLD reference variable"
// *Cause: Old values can only be read and not changed.
// *Action: Do not attempt to change an old variable.
04086, 00000, "trigger description too long, move comments into triggering code"
// *Cause: The trigger description is limited to 2000 characters (for
// dictionary storage reasons). The description does not include
// the text of the "when" clause or the text of the pl/sql code
// executed for the trigger.
// *Action: If the trigger description contains a large comment, move that
// comment into the pl/sql code for the trigger.
04087, 00000, "cannot change the value of ROWID reference variable"
// *Cause: Rowid's can only be read and not changed.
// *Action: Do not attempt to change an rowid value.
04088, 00000, "error during execution of trigger '%s.%s'"
// *Cause: A runtime error occurred during execution of a trigger.
// *Action: Check the triggers which were involved in the operation.
04089, 00000, "cannot create triggers on objects owned by SYS"
// *Cause: An attempt was made to create a trigger on an object owned by SYS.
// *Action: Do not create triggers on objects owned by SYS.
04090, 00000, "'%s' specifies same table, event and trigger time as '%s'"
// *Cause: Trigger is of duplicate event and trigger time.
// *Action: Combine the triggering information into one trigger which is
// fired at the given time.
04091, 00000, "table %s.%s is mutating, trigger/function may not see it"
// *Cause: A trigger (or a user defined plsql function that is referenced in
// this statement) attempted to look at (or modify) a table that was
// in the middle of being modified by the statement which fired it.
// *Action: Rewrite the trigger (or function) so it does not read that table.
04092, 00000, "cannot %s in a trigger"
// *Cause: A trigger attempted to commit or rollback.
// *Action: Rewrite the trigger so it does not commit or rollback.
04093, 00000, "references to columns of type LONG are not allowed in triggers"
// *Cause: A trigger attempted to reference a long column in the triggering
// table.
// *Action: Do not reference the long column.
04094, 00000, "table %s.%s is constraining, trigger may not modify it"
// *Cause: A trigger attempted to modify a table that was constraining for
// some referential constraint of a parent SQL statement.
04095, 00000, "trigger '%s' already exists on another table, cannot replace it"
// *Cause: Cannot replace a trigger which already exists on a different table
// than the one being replaced.
// *Action: Drop the trigger with the same name and re-create it.
04096, 00000, "trigger '%s' has a WHEN clause which is too large, limit 2K"
// *Cause: A trigger's 'when' clause is limited to 2K for dictionary storage
// reasons. The trigger being created exceeded that size.
// *Action: Use a smaller 'when' clause. Note, the trigger body could be used
// to perform the same limiting action as the 'when' clause.
04097, 00000, "DDL conflict while trying to drop or alter a trigger"
// *Cause: An attempt was made to concurrently perform two DDL operations on
// a trigger or trigger table.
// *Action: Investigate the new state of the trigger and retry the DDL
// operation, if still appropriate.
04098, 00000, "trigger '%s.%s' is invalid and failed re-validation"
// *Cause: A trigger was attempted to be retrieved for execution and was
// found to be invalid. This also means that compilation/authorization
// failed for the trigger.
// *Action: Options are to resolve the compilation/authorization errors,
// disable the trigger, or drop the trigger.
04099, 00000, "trigger '%s' is valid but not stored in compiled form"
// *Cause: A trigger was attempted to be retrieved for execution and was
// found to be valid, but not stored. This may mean the an
// upgrade was done improperly from a non-stored trigger release.
// *Action: Alter compile the trigger to create the trigger in stored form.
// Also, you may want to review that a proper upgrade was done.
/
/ MODIFIED
/ nmacnaug 07/28/16 - remove USE_INDIRECT_DATA_BUFFERS error messages
/ skayoor 08/19/14 - Bug 18480105: Change cause for 7443
/ wxli 02/01/12 - Put back error 6599 (orig 6596) for bug 5131912
/ dalpern 09/06/11 - proj 32719: INHERIT PRIVILEGES privilege
/ mmpandey 05/20/10 - 9714832: modify ADRCI Note detail, per new requirement
/ mmpandey 05/14/10 - 9714832: modify ORA-07445 Cause/Action text
/ sagrawal 11/16/09 - bug 9096821: change action for message 6548
/ jmuller 05/05/08 - XbranchMerge jmuller_bug-6805832 from st_rdbms_10.2
/ jmuller 02/08/08 - Fix bug 6805832: plsql_max_stack_size
/ dalpern 03/25/08 - 6907300: dbms_utility.name_resolve context 0
/ mvemulap 01/10/07 - bug 5727887 fix
/ desinha 08/30/06 - edit 6570 to add purge
/ jmuller 05/10/06 - Fix bug 5206360: document ORA-6501/6502
/ ssubrama 11/07/05 - bug 4292100 remove 6596 as its no longer in use
/ jmuller 04/07/05 - Fix bug 4236303: disallow deep copy of LOBs during
/ RPC
/ jmuller 03/16/05 - Fix bug 4185606: flag ref cursor parameters in
/ forwarded RPC case
/ jmuller 02/28/05 - Fix bug 4200773: handle NULL results in sped-up
/ STANDARD function calls more cleanly
/ swhitman 12/22/04 - 3841541:patched Tru64 kernels get proc starttime
/ wojeil 11/09/04 - add 7405
/ jmuller 07/02/04 - Fix bug 3711648: parameterize ORA-6500
/ jmuller 12/09/03 - Fix bug 1284461: name missing unit in
/ ORA-6508/BAD_DYN_LINK
/ avaliani 11/14/03 - add 07458-07460 (remove 07457 in 10gr2)
/ sdizdar 10/31/02 - add 7346
/ avaliani 06/19/02 - add 07457
/ mjaeger 06/10/02 - bug 2238718: chg 7247 from sfrfb to Veritas
/ shbose 04/29/02 - 2255071: change message for ora-6534
/ ssubrama 04/09/02 - bug 2200057 add 6579
/ hbergh 11/05/01 - 1980225: trace file cannot be symlink
/ kmuthukk 07/03/01 - 1720409: rope of debugger/profiler with plsql ncomp
/ mvemulap 03/08/01 - bug 1554027 fix
/ mxyang 02/28/01 - update 6514
/ kumamage 02/15/01 -
/ kumamage 02/08/01 - add message for sftdel
/ arhee 10/26/00 - add new error message for resmgr
/ mxyang 08/11/00 - 6592: CASE not found
/ mvemulap 07/19/00 - native compiler messages
/ asethi 06/23/00 - 6540: pipelined execution of PL/SQL functions
/ arhee 06/19/00 - add mesg for exceeded max est exec time
/ arhee 06/07/00 - fix error mesg 7454
/ arhee 03/28/00 - add error msg 7454
/ hbergh 03/28/00 - 993307: merge Compaq Tru64 message
/ nle 07/22/99 - swap error message number
/ nle 06/29/99 - dynamic returning clause
/ varora 07/06/99 - change 6576 error message
/ nle 06/01/99 - reserve message for runtime
/ nle 05/28/99 - bug 890206
/ astocks 05/25/99 - PL/SQL profiler errors
/ kmuthukk 10/12/98 - raise err for OPEN on non-queries
/ rdecker 09/22/98 - add substitute character to 6502 for sub msgs
/ alui 08/28/98 - Reserved error range 04930-04999 for Digital Unix.
/ arhee 07/23/98 - fix resmgr error msgs
/ arhee 04/13/98 - add dbscheduling messages
/ nikeda 04/07/98 - Add plsql error message for Pro* external procedures
/ kmuthukk 04/07/98 - update purity error
/ rtaranto 04/07/98 - Add 6538 for purity violations
/ rtaranto 04/07/98 - Add errors 6536/6537 for in/out binds
/ kmuthukk 02/24/98 - null dynamic statement
/ mluong 03/20/98 - fix comp error
/ kmuthukk 03/30/98 - pending autonmous transaction rolled back
/ varora 03/28/98 - add duplicate bind error for CALL
/ arhee 03/17/98 - add message for database scheduling
/ kquinn 03/18/98 - Add message 7345
/ jsarma 03/10/98 - Add OER 7451-55
/ varora 02/01/98 - add errors for call method statement
/ agreenbl 10/30/97 - Rename 7302 --> 7305 to match 8.0.x
/ agreenbl 06/27/97 - Remove obsolete sm errors
/ mluong 06/24/97 - merge from 803
/ anolan 05/21/97 - checkout
/ anolan 05/14/97 - Demo.
/ kmuthukk 04/14/97 - restrict access of SR pkgs in triggers (b496997)
/ usundara 12/31/96 - incomplete and mutually-dependent types
/ o add ora-6545 for pl/sql error handling)
/ bcchang 12/20/96 - error.msg split
/
/
/ Trigger errors continued at 25000-25099
/
/ 4100-4499 Reserved for MVS OSD errors
/
/ 4500-4899 Reserved for CMS OSD errors
/
/ 4900-4929 Reserved for ICL DRS6000
/
/ 4930-4999 Reserved for Digital Unix
/
/ 5000-5899 Reserved for OEM OSD errors
/
/ 5900-5999 Reserved for Wang OSD errors (OEM: GABA)
/
/ 6000-6499 Reserved for SQL*Net errors
/
/ NETASY: 6000-6029 SQL*Net ASYNC Driver errors
/
/
/ Digital Unix specific errors (04930 - 04999).
/ This error range is used, starting from release 8.0.6, and 8.1.5.
/ The DEC specific errors 08324-08329 in e7500.msg are now listed here
/ as 04930 - 04935,04940.
/
04930, 00000, "open sequence number failed or initial state is valid"
// *Cause: Either Shared Sequence Number OS component was not installed
// properly, or an MC hardware failure may have occurred or a
// previous instance was not shut down properly.
// *Action: Verify that there are no background or foreground Oracle
// processes from a previous instance on this node using the OS
// command ps -ef|grep <instance_name>. Verify that there are no
// shared memory segments belonging to the user which owns the
// Oracle installation by isuing the ipcs -b OS command. If there
// are shared memory segments or processes still on the system,
// use svrmgrl to shutdown the instance with the abort option. If
// the instance is not up, verify that the cluster software and/or
// the hardware is installed and working. Log in as superuser and
// issue the cnxshow command. Are all of the nodes in the cluster
// listed? Are they members of the cluster? Is the communications
// between nodes okay? If the answer to any of these questions is
// false, contact Digital's customer support organization.
04931, 00000, "unable to set initial sequence number value"
// *Cause: A call to the SSN failed to set the sequence number to its initial
// value, possibly caused by an MC hardware problem.
// *Action: Verify that the MC hardware is functioning properly. If it is
// not, contact Digital's customer support organization. If it is,
// contact Oracle support.
04932, 00000, "increment or adjust of sequence number failed"
// *Cause: A call to the SSN failed to increment the sequence number.
// *Action: Verify that the MC hardware is functioning properly. If it is
// not, contact Digital's customer support organization. If it is,
// contact Oracle support.
04933, 00000, "initial service identifier is non-zero"
// *Cause: A valid service identifier existed before the sequence number
// service was opened.
// *Action: Verify that the instance is completely shut down.
04934, 00000, "unable to obtain the current sequence number"
// *Cause: A call to the SSN failed to return its current value.
// Either there are many errors occurring on the MC hardware,
// or the sequence number has become invalid and cannot be
// validated.
// *Action: Verify that the MC hardware is functioning properly. If it
// is, contact Oracle Support.
04935, 00000, "unable to get/convert SCN recovery lock"
// *Cause: A process has timed out trying to get or convert the SCN
// recovery lock. Another process probably has the lock in
// EX or SHR mode, but is not releasing it.
// *Action: Contact Oracle Support.
04940, 00000, "unsupported optimization of Oracle binary, check alert log for more info"
// *Cause: ORACLE binary has been optimized with unsupported options or
// a required option has not been used.
// *Action: Check the documentation for a list of supported and required flags
// for the optimizing utility that you used to optimize ORACLE.
// Shutdown the instance, optimize ORACLE again with supported
// combination of options and restart the instance.
04941, 00000, "required operating system patch needs to be applied"
// *Cause: The operating system could not return the start time of a
// process.
// *Action: Check that the operating system kernel has been patched
// to return process start time. Apply the required operating
// system patch and restart the instance.
06000, 00000, "NETASY: port open failure"
// *Cause: Autologin unable to open port
// *Action: Check log file for OS-specific error code
06001, 00000, "NETASY: port set-up failure"
// *Cause: Autologin unable to change port attributes
// *Action: Check log file for OS-specific error code
06002, 00000, "NETASY: port read failure"
// *Cause: Autologin unable to read from port
// *Action: Check log file for OS-specific error code
06003, 00000, "NETASY: port write failure"
// *Cause: Autologin unable to write to port
// *Action: Check log file for OS-specific error code
06004, 00000, "NETASY: dialogue file open failure"
// *Cause: Autologin unable to open dialogue file
// *Action: Check connect string for accuracy/typos
06005, 00000, "NETASY: dialogue file read failure"
// *Cause: Autologin unable to read dialogue file
// *Action: Check log file for OS-specific error code
06006, 00000, "NETASY: dialogue execute failure"
// *Cause: Expected response never received
// *Action: None
06007, 00000, "NETASY: bad dialogue format"
// *Cause: Dialogue file contains syntax error
// *Action: Correct the dialogue file
06009, 00000, "NETASY: dialogue filename too long"
// *Cause: Full file spec for dialogue file exceeds 64 bytes
// *Action: Amend connect string accordingly
06010, 00000, "NETASY: dialogue file too long"
// *Cause: Dialogue file exceeds 768 bytes in length
// *Action: Simplify dialogue (e.g. remove comments, redundant white space),
// or split into two and link with "more" command
06011, 00000, "NETASY: dialogue too long"
// *Cause: One of two:
// 1. Dialogue contains more than 24 exchange blocks
// 2. Dialogue send string exceeds 84 bytes in length
// *Action: Simplify dialogue or split into two and link with "more" command
06017, 00000, "NETASY: message receive failure"
// *Cause: Async driver gets I/O error while doing network read operation
// *Action: Check log file for OS-specific error code and
// contact your customer support representative.
06018, 00000, "NETASY: message send failure"
// *Cause: Async driver gets I/O error while doing network write operation
// *Action: Check log file for OS-specific error code and
// contact your customer support representative.
06019, 00000, "NETASY: invalid login (connect) string"
// *Cause: Syntax error in login string.
// *Action: Resubmit with correct string.
06020, 00000, "NETASY: initialisation failure"
// *Cause: Async driver unable to complete initialisation
// *Action: Check log file for OS-specific error code
06021, 00000, "NETASY: connect failed"
// *Cause: Async driver unable to establish connection with partner
// *Action: Check log file for OS-specific error code
06022, 00000, "NETASY: channel open failure"
// *Cause: no free channel [should never happen]
// *Action: Contact your customer support representative.
06023, 00000, "NETASY: port open failure"
// *Cause: Async driver unable to open port
// *Action: Check log file for OS-specific error code
06024, 00000, "NETASY: VTM error"
// *Cause: Virtual Terminal Manager unable to read/write to port
// *Action: Check log file for OS-specific error code
06025, 00000, "NETASY: Configuration error"
// *Cause: Async driver genned for server-only, but client service requested
// *Action: Contact your customer support representative.
06026, 00000, "NETASY: port close failure"
// *Cause: Async driver unable to close port
// *Action: Check log file for OS-specific error code
06027, 00000, "NETASY: channel close failure"
// *Cause: Async driver unable to close channel
// *Action: Check log file for OS-specific error code
06028, 00000, "NETASY: unable to intialise for logging"
// *Cause: Async driver unable to initialise for logging I/O
// *Action: Contact your customer support representative.
06029, 00000, "NETASY: port assignment failure"
// *Cause: Async driver unable to assign port to channel [should never happen]
// *Action: Contact your customer support representative.
/
/ NETDNT: 6030-6049 SQL*Net DECnet Driver errors
/
06030, 00000, "NETDNT: connect failed, unrecognized node name"
// *Cause: Node name specified in host string is unknown (probably misspelled)
// *Action: Retry with correct node name
06031, 00000, "NETDNT: connect failed, unrecognized object name"
// *Cause: Host string contains reference to object (which doesn't exist):
// @d:<node>-<obj> => object is ORDN<obj>;
// when <node> is VMS, the object is ORDN<obj>.COM
// when <node> is UNIX, the object is ORDN<obj>
// @d:<node>::"task=<obj>" => object is <obj>;
// when <node> is VMS, the object is <obj>.COM
// when <node> is UNIX, the object is <obj>
// *Action: Retry with correct object name or create the required
// object on host node
06032, 00000, "NETDNT: connect failed, access control data rejected"
// *Cause: Host string contains invalid username/password
// *Action: Retry with correct username/password
06033, 00000, "NETDNT: connect failed, partner rejected connection"
// *Cause: Connection with partner was made but was rejected.
// *Action: Contact your network administrator.
06034, 00000, "NETDNT: connect failed, partner exited unexpectedly"
// *Cause: Connection with host node was made but partner aborted
// *Action: Make sure object (see 06031, above) is working (for VMS run the
// command file and make sure that the ORACLE server process starts
// up); sometimes happens when the network/node is under stress -
// in this case a retry often works.
06035, 00000, "NETDNT: connect failed, insufficient resources"
// *Cause: Insufficient system resources are available to complete the
// connection; for example, all DECnet channels are in use.
// *Action: Contact your network administrator.
06036, 00000, "NETDNT: connect failed, no response from object"
// *Cause:
// *Action:
06037, 00000, "NETDNT: connect failed, node unreachable"
// *Cause: Host node is down.
// *Action: Contact your network administrator.
06038, 00000, "NETDNT: connect failed, network driver not loaded"
// *Cause:
// *Action:
06039, 00000, "NETDNT: connect failed"
// *Cause: Connect failed for unexpected reason (see OSD error).
// *Action: Contact your customer support representative.
06040, 00000, "NETDNT: invalid login (connect) string"
// *Cause: Syntax error in login string.
// *Action: Resubmit with correct string.
06041, 00000, "NETDNT: disconnect failed"
// *Cause: Driver gets error while doing network close operation
// *Action: Contact your customer support representative.
06042, 00000, "NETDNT: message receive failure"
// *Cause: Driver gets I/O error while doing network read operation
// *Action: Contact your customer support representative.
06043, 00000, "NETDNT: message send failure"
// *Cause: Driver gets I/O error while doing network write operation
// *Action: Contact your customer support representative.
06044, 00000, "NETDNT: connect failed, byte count quota exceeded"
// *Cause: Connect failed because of insufficient byte count quota.
// *Action: Increase byte count quota.
/
/ NETTCP: 06100 - 6149 SQL*Net TCP/IP driver errors
/
/6100-6101 Reserved.
06102, 00000, "NETTCP: cannot allocate context area"
// *Cause: Insufficient dynamic memory available for connection
// context area.
// *Action: Contact your customer support representative.
/6103-6104 Reserved.
06105, 00000, "NETTCP: remote host is unknown"
// *Cause: Host name specified in the login (connect) string is unknown.
// *Action: Check spelling; make sure name is in the TCP/IP HOST file.
06106, 00000, "NETTCP: socket creation failure"
// *Cause: Process open file quota probably exceeded.
// *Action: Contact your customer support representative.
06107, 00000, "NETTCP: ORACLE network server not found"
// *Cause: No entry in SERVICES file for ORACLE server.
// *Action: Add ("orasrv") entry to the TCP/IP SERVICES file.
06108, 00000, "NETTCP: connect to host failed"
// *Cause: Connection attempt to remote host has failed. Probably means
// that the SQL*Net TCP/IP server on the remote host is not up,
// or the host itself is not up (check the latter by targeting
// it with Telnet).
// *Action: Start the SQL*Net TCP/IP server process on the remote host.
06109, 00000, "NETTCP: message receive failure"
// *Cause: I/O error occurred while attempting network read operation.
// *Action: Contact your customer support representative.
06110, 00000, "NETTCP: message send failure"
// *Cause: I/O error occurred while attempting network write operation.
// *Action: Contact your customer support representative.
06111, 00000, "NETTCP: disconnect failure"
// *Cause: Error occurred while closing a socket.
// *Action: Contact your customer support representative.
06112, 00000, "NETTCP: invalid buffer size"
// *Cause: The buffer size specified in the login string exceeds the
// allowed maximum (of 4096).
// *Action: Re-submit with valid buffer size.
06113, 00000, "NETTCP: Too many connections"
// *Cause: The maximum no. of concurrently open connections has been reached.
// *Action: Exit an application with an open connection which is no longer
// required.
06114, 00000, "NETTCP: SID lookup failure"
// *Cause: From the remote host's SQL*Net TCP/IP server: the database SID,
// specified in the login (connect) string, was not recognized.
// *Action: Add the appropriate SID entry to the CONFIG.ORA file on
// the remote host (and restart the SQL*Net TCP/IP server).
06115, 00000, "NETTCP: unable to create ORACLE logicals"
// *Cause: The host's SQL*Net TCP/IP server was unable to create the
// necessary logicals required by the ORACLE server process.
// See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your system administrator.
06116, 00000, "NETTCP: unable to create ORASRV process"
// *Cause: The host's SQL*Net TCP/IP server was unable to create
// the ORACLE server process.
// See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your system administrator.
06117, 00000, "NETTCP: unable to create ORASRV: quota exceeded"
// *Cause: The host's SQL*Net TCP/IP server was unable to create
// the ORACLE server process because of quota depletion.
// *Action: Increase quota allocations to the SQL*Net TCP/IP
// server process.
06118, 00000, "NETTCP: unable to complete handshake with ORASRV"
// *Cause: The ORACLE server process was started but failed to
// complete its initialization.
// *Action: Contact your customer support representative.
06119, 00000, "NETTCP: spurious client request"
// *Cause: The host's SQL*Net TCP/IP server was unable to recognize
// this connection request.
// See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06120, 00000, "NETTCP: network driver not loaded"
// *Cause: The TCP/IP network driver is not loaded.
// *Action: Check that the TCP/IP driver is loaded correctly.
06121, 00000, "NETTCP: access failure"
// *Cause: The host's SQL*Net TCP/IP server was unable to test the
// accessibility of the SID mapping file (specified in
// CONFIG.ORA) associated with this connection request.
// See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06122, 00000, "NETTCP: setup failure"
// *Cause: The host's SQL*Net TCP/IP server was unable to set up
// the appropriate environment to service this connection
// request.
// See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06123, 00000, "NETTCP: cannot set KEEPALIVE"
// *Cause: The host's SQL*Net TCP/IP server was unable to set the
// socket KEEPLIVE option.
// See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06124, 00000, "NETTCP: timeout waiting for ORASRV"
// *Cause: The ORACLE server process was started but failed to
// respond after N secs.
// *Action: For heavily loaded systems this is not an uncommon
// occurrence. Increase the value of N (the default is
// 30) by placing the following entry in the CONFIG.ORA
// file:
// SQLNET ORASRV_WAIT = <no. of secs>
// which will come into effect the next time the SQL*Net
// TCP/IP server is started.
06125, 00000, "NETTCP: ORASRV exited unexpectedly"
// *Cause: The ORACLE server process was started but exited unexpectedly.
// Possible causes:
// 1. Insufficient quotas to run ORASRV
// 2. ORACLE is not installed
// See the ORASRV output file for more details; the file will be
// in the ORA_SQLNET directory and will have a name of the form:
// ORA_SRVTnn_<SID>.OUT
// *Action: If appropriate action is not obvious from the ORASRV output
// file then contact your customer support representative.
06126, 00000, "NETTCP: ORASRV unable to open network connection"
// *Cause: The ORACLE server process was started but was unable to
// open the socket passed to it by TCPSRV.
// *Action: Contact your customer support representative.
06127, 00000, "NETTCP: unable to change username"
// *Cause: The host's SQL*Net TCP/IP server could not establish a
// PROXY LOGIN connection because the client username
// is unknown (to the host OS).
// *Action: Create new user account on host.
06128, 00000, "NETTCP: unable to create mailbox"
// *Cause: The host's SQL*Net TCP/IP server was unable to create a
// mailbox (needed for IPC communication with the ORACLE
// server process).
// See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06129, 00000, "NETTCP: unable to transfer socket ownership to ORASRV"
// *Cause: The host's SQL*Net TCP/IP server was unable to transfer
// the network communication handle to the ORACLE server
// process.
// See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06130, 00000, "NETTCP: host access denied"
// *Cause: The host's SQL*Net TCP/IP server rejected this connection
// request because the client node does not have access
// privilege - as determined by the contents of the Valid
// Node Table (VNT), a component of the host's CONFIG.ORA.
// *Action: To grant access, add appropriate entry to the host's VNT.
06131, 00000, "NETTCP: user access denied"
// *Cause: The host's SQL*Net TCP/IP server rejected this connection
// request because the client user(name) does not have access
// privilege - as determined by the contents of the Username
// Mapping Table (UMT), a component of the host's CONFIG.ORA.
// *Action: To grant access, add appropriate entry to the host's UMT.
06132, 00000, "NETTCP: access denied, wrong password"
// *Cause: The host SQL*Net TCP/IP server rejected this connection
// request because the client password did not match the host
// password.
// *Action: To grant access, get passwords in sync.
06133, 00000, "NETTCP: file not found"
// *Cause: The host's SQL*Net TCP/IP server could not find the SID
// mapping file (specified in CONFIG.ORA) associated with
// this connection request.
// *Action: Check CONFIG.ORA for spelling; make correct entry.
06134, 00000, "NETTCP: file access privilege violation"
// *Cause: The host's SQL*Net TCP/IP server did not have READ/
// EXECUTE permission for the SID mapping file (specified
// in CONFIG.ORA) associated with this connection request.
// *Action: Change protection on SID mapping file.
06135, 00000, "NETTCP: connection rejected; server is stopping"
// *Cause: The host's SQL*Net TCP/IP server rejected this connection
// request because it is in the process of stopping.
// *Action: Re-start SQL*Net TCP/IP server.
06136, 00000, "NETTCP: error during connection handshake"
// *Cause: Network I/O failure occurred while communicating with the
// host's SQL*Net TCP/IP server.
// See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06137, 00000, "NETTCP: error during connection handshake"
// *Cause: Network I/O failure occurred while communicating with the
// host's SQL*Net TCP/IP server.
// See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06138, 00000, "NETTCP: error during connection handshake"
// *Cause: Network I/O failure occurred while communicating with the
// host's SQL*Net TCP/IP server.
// See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
/6139 Reserved.
06140, 00000, "NETTCP: no such user"
// *Cause: A proxy login connect attempt failed because the client
// username has no counterpart on the host.
// *Action:
06141, 00000, "NETTCP: no privilege for user"
// *Cause: A proxy login connect attempt failed because the
// SQL*Net TCP/IP server had insufficient privileges
// to access the proxy account.
// *Action: Change account protection; change server privilges.
06142, 00000, "NETTCP: error getting user information"
// *Cause: A proxy login connect attempt failed because the
// SQL*Net TCP/IP server was unable to access the
// proxy account.
// See the SQL*Net TCP/IP server log file for more details.
// *Action: Contact your customer support representative.
06143, 00000, "NETTCP: maximum connections exceeded"
// *Cause: The connect failed because the maximum conncurrent
// connections supported by the host's SQL*Net TCP/IP
// server has already been reached.
// *Action: Wait for a short period and re-try.
06144, 00000, "NETTCP: SID (database) is unavailable"
// *Cause: The database administrator on the host has varied
// the SID offline.
// *Action: Wait for it to be varied back on-line.
06145, 00000, "NETTCP: unable to start ORASRV: images not installed"
// *Cause: The host's SQL*Net TCP/IP server was unable to start
// the ORACLE server process because the ORACLE protected
// images were not installed.
// *Action: Install the images.
/6146-6149 Reserved.
/
/ TWOTASK: 06200 - 06219 VMS Two-Task driver errors
/
06200, 00000, "TWOTASK: connect failed, can't create mailbox"
// *Cause:
// *Action:
06201, 00000, "TWOTASK: connect failed, can't attach to mailbox"
// *Cause:
// *Action:
06202, 00000, "TWOTASK: connect failed, can't spawn ORASRV process"
// *Cause:
// *Action:
06203, 00000, "TWOTASK: connect failed, handshake failure"
// *Cause:
// *Action:
06204, 00000, "TWOTASK: connect failed, can't access ORASRV2.COM"
// *Cause:
// *Action:
06205, 00000, "TWOTASK: connect failed, can't create logical name"
// *Cause:
// *Action:
06206, 00000, "TWOTASK: message receive failure"
// *Cause:
// *Action:
06207, 00000, "TWOTASK: message send failure"
// *Cause:
// *Action:
06208, 00000, "TWOTASK: invalid login (connect) string"
// *Cause:
// *Action:
06209, 00000, "TWOTASK: connect failed, mailbox already exists"
// *Cause:
// *Action:
06210, 00000, "TWOTASK: connect failed, ORASRV exited unexpectedly"
// *Cause:
// *Action:
06211, 00000, "TWOTASK: connect failed, timeout waiting for ORASRV"
// *Cause:
// *Action:
06212, 00000, "TWOTASK: connect failed, logical name table is full"
// *Cause:
// *Action:
06213, 00000, "TWOTASK: connect failed"
// *Cause:
// *Action:
06214, 00000, "TWOTASK: connect failed, insufficient quotas to create ORASRV"
// *Cause:
// *Action:
06215, 00000, "TWOTASK: connect failed, ORASRV protected image not installed"
// *Cause:
// *Action:
06216, 00000, "TWOTASK: connect failed, can't find ORASRV image file"
// *Cause:
// *Action:
/6217-6219 Reserved.
/
/ NETNTT: 6250 - 6274 SQL*Net nCUBE Two-Task errors
/
06250, 00000, "NETNTT: cannot allocate send and receive buffers"
// *Cause: Two-task driver could not allocate data buffers.
// *Action: There is insufficient memory to run your program. Kill
// off other processes to free up memory.
06251, 00000, "NETNTT: cannot translate address file name"
// *Cause: ORACLE_HOME environment variable not set.
// *Action: Make sure that the ORACLE_HOME environment variable has been
// properly set and exported.
06252, 00000, "NETNTT: cannot open address file"
// *Cause: The NTT two-task driver could not open a file containing
// address information.
// *Action: Make sure that the ORACLE_HOME environment variable has been
// properly set and exported. Make sure the instance you are
// attempting to connect to is actually up and running.
06253, 00000, "NETNTT: cannot read arguments from address file"
// *Cause: The NTT two-task driver could not read addressing information
// from its addressing file.
// *Action: Make sure that the ORACLE_HOME environment variable has been
// properly set and exported. Make sure the instance you are
// attempting to connect to is actually up and running.
06254, 00000, "NETNTT: cannot share connection to cube"
// *Cause: The NTT two-task driver could not share a connection to the cube.
// *Action: Make sure that the ORACLE_HOME environment variable has been
// properly set and exported. Make sure the instance you are
// attempting to connect to is actually up and running.
06255, 00000, "NETNTT: cannot read pid of remote process"
// *Cause: An error occurred while reading the NTT communications link.
// *Action: Contact your customer support representative.
06256, 00000, "NETNTT: remote fork failed"
// *Cause: The Oracle listener process on the cube could not fork off
// a shadow process.
// *Action: The instance you are trying to connect to probably doesn't
// have enough memory to run another shadow process. Ask someone
// else to log off, or connect to a different instance.
06257, 00000, "NETNTT: cannot send command line to shadow process"
// *Cause: An error occurred while writing the NTT communications link.
// *Action: Contact your customer support representative.
06258, 00000, "NETNTT: cannot allocate context area"
// *Cause: Two-task driver could not allocate data buffers.
// *Action: There is insufficient memory to run your program. Kill
// off other processes to free up memory.
06259, 00000, "NETNTT: cannot read from remote process"
// *Cause: An error occurred while reading the NTT communications link.
// *Action: Contact your customer support representative.
06260, 00000, "NETNTT: cannot write to remote process"
// *Cause: An error occurred while writing the NTT communications linke.
// *Action: Contact your customer support representative.
06261, 00000, "NETNTT: nrange() failed"
// *Cause: The call to 'nrange()' failed while attempting to establish
// a connection.
// *Action: Contact your customer support representative.
06262, 00000, "NETNTT: nfconn() failed"
// *Cause: The call to 'nfconn()' failed while attempting to establish
// a connection.
// *Action: Contact your customer support representative.
06263, 00000, "NETNTT: out of memory in pi_connect"
// *Cause: Two-task driver could not allocate data buffers.
// *Action: There is insufficient memory to run your program. Kill
// off other processes to free up memory.
06264, 00000, "NETNTT: data protocol error"
// *Cause: The NTT two-task driver received an unexpected message type."
// *Action: Contact your customer support representative.
06265, 00000, "NETNTT: break protocol error"
// *Cause: The NTT two-task driver received an unexpected message type."
// *Action: Contact your customer support representative.
06266, 00000, "NETNTT: bad write length"
// *Cause: The NTT two-task driver failed on an internal consistency
// check.
// *Action: Contact your customer support representative.
06267, 00000, "NETNTT: bad state"
// *Cause: The NTT two-task driver failed on an internal consistency
// check.
// *Action: Contact your customer support representative.
06268, 00000, "NETNTT: cannot read /etc/oratab"
// *Cause: The NTT two-task driver could not read configuration information
// from /etc/oratab.
// *Action: Make sure /etc/oratab exists and is readable. This error may
// occur if the file is incorrectly formatted. It also may occur
// if the driver has run out of memory.
/6268-6274 Reserved
/
/ IPA: 6300 - 6323 SQL*Net IPA errors
/
06300, 00000, "IPA: Disconnect failure"
// *Cause: A fatal error occurred during the disconnect from the server.
// This was probably caused by inaccessible message queues.
// *Action: If there is no message queue, restart the SQL*Net IPA servers
// using ipactl. Otherwise contact your customer support
// representative.
06301, 00000, "IPA: Cannot allocate driver context"
// *Cause: The memory pool is exhausted.
// *Action: Check the circumstances and try to allocate less memory in your
// program or adjust the init parameters in your INIT.ORA file and
// retry.
06302, 00000, "IPA: Cannot connect to remote host"
// *Cause: The cause may be one of the following:
// - there is no ADI server defined to reflect a connection to the
// specified host.
// - the remote host is not known by the local system.
// - the ORACLE kernel on the remote host is not generated with the
// IPA driver
// *Action: Check sequentially for the above causes and eliminate the actual
// cause found.
06303, 00000, "IPA: Message send error"
// *Cause: The SQL*Net IPA driver could not write the message into the
// message queue.
// *Action: Make sure that the message queue exists and is accessible.
// If necessary rerun ipactl.
06304, 00000, "IPA: Message receive error"
// *Cause: The SQL*Net IPA driver could not read a message from the message
// queue.
// *Action: Make sure that the message queue exists and is accessible.
// If necessary rerun ipactl.
06305, 00000, "IPA: Illegal message type"
// *Cause: The communication between user and ORACLE is out of
// synchronization. This message should not normally be issued.
// *Action: Contact your customer support representative.
06306, 00000, "IPA: Message write length error"
// *Cause: The IPA driver tried to write a message in the queue that was
// too big for the queue.
// *Action: Contact your customer support representative.
06307, 00000, "IPA: Cannot reset connection"
// *Cause: A fatal error occurred during the resetting of the connection.
// *Action: Contact your customer support representative.
06308, 00000, "IPA: No more connections available"
// *Cause: You have exhausted all your connections.
// *Action: Try again when some of the current users have logged off.
06309, 00000, "IPA: No message queue available"
// *Cause: The SQL*Net IPA servers have not been started.
// *Action: Run ipactl.
06310, 00000, "IPA: Environment variable(s) not set"
// *Cause: Environment variable(s) not set correctly.
// *Action: Check and correct.
06311, 00000, "IPA: Maximum number of servers reached"
// *Cause: Maximum number of servers reached.
// *Action: Shutdown and restart with an increased maximum number of servers.
// Note that database links consume one server per link. Be sure
// to start up enough servers to support database links.
06312, 00000, "IPA: Incorrect outgoing service name supplied"
// *Cause: Incorrect outgoing service name supplied.
// *Action: Check and correct the service name.
06313, 00000, "IPA: Shared memory failed to initialise"
// *Cause: The shared memory has not been set up correctly.
// *Action: Contact your system manager.
06314, 00000, "IPA: Event set up failure"
// *Cause: Fatal interprocess communication error.
// *Action: Contact your system manager.
06315, 00000, "IPA: Invalid connect string"
// *Cause: The connect string is malformed.
// *Action: Check and correct.
06316, 00000, "IPA: Invalid database SID"
// *Cause: The SID is unknown at the remote side.
// *Action: Either the database does not exist, is not running, or
// there are no reserved servers for that SID.
06317, 00000, "IPA: Local maximum number of users exceeded"
// *Cause: The maximum number of simultaneous users of SQL*Net IPA has been
// exceeded on the local side.
// *Action: Wait for free connections to become available. If the problem
// persists, contact your system manager.
06318, 00000, "IPA: Local maximum number of connections exceeded"
// *Cause: The maximum number of simultaneous connections that SQL*Net IPA
// can handle to different hosts has been exceeded on the local side.
// *Action: Wait for free connections to become available. If the problem
// persists, contact your system manager.
06319, 00000, "IPA: Remote maximum number of users exceeded"
// *Cause: The maximum number of simultaneous users of SQL*Net IPA has been
// exceeded on the remote side.
// *Action: Wait for free connections to become available. If the problem
// persists, contact your system manager.
06320, 00000, "IPA: Remote maximum number of connections exceeded"
// *Cause: The maximum number of simultaneous connections that SQL*Net IPA
// can handle from different hosts has been exceeded on the remote
// side.
// *Action: Wait for free connections to become available. If the problem
// persists, contact your system manager.
06321, 00000, "IPA: Cannot reach the remote side"
// *Cause: There has been a timeout on an attempt to connect to a remote
// server the reason for which is most likely to be the remote
// SQL*Net IPA software is not running. An alternative reason
// could be that the remote initiator service name is incorrect.
// *Action: Check and start the remote SQL*Net software. Check that it is
// started with the correct service names supplied.
06322, 00000, "IPA: Fatal shared memory error"
// *Cause: An internal error has occurred in the shared memory handling.
// *Action: Contact customer support.
06323, 00000, "IPA: Cause event error"
// *Cause: Fatal interprocess communication error.
// *Action: Contact your system manager.
/
/ NETCMN: 6400 - 6429 SQL*Net CoMmoN errors
/
06400, 00000, "NETCMN: No default host string specified"
// *Cause: There was no default host string specified in the configuration
// and the user didn't specify any explicit connect string.
// *Action: Either reconfigure the system specifying a default connect string
// or use an explicit connect string.
06401, 00000, "NETCMN: invalid driver designator"
// *Cause: The login (connect) string contains an invalid driver designator.
// *Action: Correct the string and re-submit.
06402, 00000, "NETCMN: error receiving break message"
// *Cause: Error occurred while attempting to read a break message.
// *Action: Contact your customer support representative.
06403, 00000, "Unable to allocate memory."
// *Cause: System unable to allocate needed virtual memory.
// *Action: Configure more memory, reduce load, or simply try again.
06404, 00000, "NETCMN: invalid login (connect) string"
// *Cause: Syntax error in login string.
// *Action: Correct string and re-submit.
06405, 00000, "NETCMN: reset protocol error"
// *Cause: Unable to reset out of break state.
// *Action: Contact your customer support representative.
06406, 00000, "NETCMN: error sending break message"
// *Cause: Error occurred while attempting to send a break message.
// *Action: Contact your customer support representative.
06407, 00000, "NETCMN: unable to set up break handling environment"
// *Cause: Error occurred while attempting to set up asynchronous
// handlers for in-coming, out-of-band break messages.
// *Action: Contact your customer support representative.
06408, 00000, "NETCMN: incorrect message format"
// *Cause: Message from partner contains bad header.
// *Action: Contact your customer support representative.
/6409-6412 Reserved.
06413, 00000, "Connection not open."
// *Cause: Unable to establish connection.
// *Action: Use diagnostic procedures to ascertain exact problem.
/6414-6415 Reserved.
06416, 00000, "NETCMN: error on test"
// *Cause: Error occurred while testing I/O status of the network connection.
// *Action: Contact your customer support representative.
/6417-6429 Reserved.
/6418 Unused
06419, 0000, "NETCMN: server can not start oracle"
// *Cause: The remote server was unable to start an ORACLE process on
// behalf of the client.
// *Action: Make sure permissions on the remote ORACLE program are correctly
// set. Contact your system administrator.
06420, 0000, "NETCMN: SID lookup failure"
// *Cause: From the remote host's server: the database SID,
// specified in the login (connect) string, was not recognized.
// *Action: Add the appropriate SID entry to the CONFIG.ORA or oratab file
// on the remote host (restarting the remote server may be needed).
06421, 0000, "NETCMN: Error detected in the read-in data"
// *Cause: Error found during recomputation of checksum or CRC.
// *Action: Possible hardware failures of communication nodes.
// Contact system administrator immediately.
06422, 0000, "NETCMN: Error in sending data"
// *Cause: Unable to transmit data to remote host.
// *Action: Try reconnect to remote host, and contact your system
// administrator.
06423, 0000, "NETCMN: Error in receiving data"
// *Cause: Unable to receive data from remote host.
// *Action: Try reconnect to remote host, and contact your system
// administrator.
/
/ 6430-6449 Reserved for NCR System 3000
/
06430, 0000, "ssaio: Seals do not match"
// *Cause: A function was called with an invalid argument.
// *Action: Contact your Oracle Customer Support Representative.
06431, 0000, "ssaio: Invalid Block number"
// *Cause: The file block number is out of range of the file. The additional
// information returns the block number.
// *Action: Verify that the block number is correct. Run dbfsize and check if
// the block number is in that range. Contact your Oracle Customer
// Support Representative.
06432, 0000, "ssaio: Buffer Not Aligned"
// *Cause: The I/O buffer was not aligned on a 2K boundary.
// *Action: Contact your Oracle Customer Support Representative.
06433, 0000, "ssaio: LSEEK error, unable to seek to requested block."
// *Cause: The additional information returns the block number
// *Action: Look up the additional information returned in your operating
// system reference manual. Verify that the block number is correct.
06434, 0000, "ssaio: read error, unable to read requested block from database file."
// *Cause: The read system call returned an error.
// *Action: The additional information indicates the block number. Look up
// the additional information returned in your operating system
// manual.
06435, 0000, "ssaio: write error, unable to write requested block to database file."
// *Cause: The write system call returned an error.
// *Action: The additional information indicates the block number. Look up
// the additional information returned in your operating system
// manual.
06436, 0000, "ssaio: asynchronous I/O failed due to incorrect parameters."
// *Cause: The Asynchronous I/O system call returned an error.
// *Action: The additional information indicates the block number. Look up
// the additional information returned in your operating system
// manual.
06437, 0000, "ssaio: the asynchronous write was unable to write to the database file."
// *Cause: The Asynchronous I/O system call returned an error.
// *Action: The additional information indicates the block number. Look up
// the additional information returned in your operating system
// manual.
06438, 0000, "ssaio: the asynchronous read was unable to read from the database file."
// *Cause: The Asynchronous I/O system call returned an error.
// *Action: The additional information indicates the block number. Look up
// the additional information returned in your operating system
// manual.
06439, 0000, "ssaio: the asynchronous write returned incorrect number of bytes"
// *Cause: This write call may have been truncated. The additional
// information returns the block number and number of bytes.
// *Action: Verify that the block number and the number of bytes written are
// correct.
06440, 0000, "ssaio: the asynchronous read returned incorrect number of bytes"
// *Cause: This read call may have been truncated. The additional
// information returns the block number and number of bytes.
// *Action: Verify that the block number and the number of bytes read are
// correct.
06441, 0000, "ssvwatev: Incorrect parameter passed to function call"
// *Cause: Either the ORACLE process id, or wait time or event ID is invalid.
// *Action: The additional information indicates the process id, time and
// event id.
06442, 0000, "ssvwatev: Failed with unexpected error number."
// *Cause: Some system problems may exists on your system, please check
// error logs.
// *Action: The additional information indicates the error number. Look up
// the additional information returned in your operating system
// manual.
06443, 0000, "ssvpstev: Incorrect parameter passed to function call"
// *Cause: An invalid event ID is passed in to this routine.
// *Action: The additional information indicates the event id.
06444, 0000, "ssvpstev: Failed with unexpected error number."
// *Cause: Some system problems may exist on your system, please check error
// logs.
// *Action: The additional information indicates the error number. Look up
// the additional information returned in your operating system
// manual.
06445, 0000, "ssvpstevrg: Incorrect parameters passed to function call"
// *Cause: An invalid event id, or the low and high event ID do not exist.
// *Action: The additional information indicates the error number. It also
// contains the event id, low boundary and high boundary.
06446, 0000, "ssvpstevrg: Failed with unexpected error number."
// *Cause: Some system problems may exist on your system, please check error
// logs.
// *Action: The additional information indicates the error number. Look up
// the additional information returned in your operating system
// manual.
06447, 0000, "ssvpstp: Incorrect parameter passed to function call"
// *Cause: Invalid oracle process ID is passed in to this routine.
// *Action: The additional information indicates the process id.
06448, 0000, "ssvpstp: Failed with unexpected error number."
// *Cause: Some system problems may exists on your system, please check
// error logs.
// *Action: The additional information indicates the error number. Look up
// the additional information returned in your operating system
// manual.
06449, 0000, "The list IO or the sysvendor is not installed."
// *Cause: ORACLE tries to use the sysvendor interface (INIT.ORA parameter
// use_sysvendor=true) but the UNIX kernel does not have the ORACLE
// sysvendor interface linked in.
// *Action: Set use_sysvendor=false in INIT.ORA, if you don't want to use
// this interface or link the UNIX kernel with this interface so
// that ORACLE can use it.
/
/ 6500-6599 PL/SQL Errors
/
/ 6500-6539 are signalled by PL/SQL and owned by PL/SQL's peiexc.h
/ file. 6540-6549 are signalled by PL/SQL and are used for PL/SQL
/ error handling and appear in pcmdef.h. 6550-6599 are used by the
/ RDBMS to signal PL/SQL related errors and do not appear in PL/SQL's
/ peiexc.h file.
/
06500, 00000, "PL/SQL: storage error"
// *Cause: PL/SQL was unable to allocate additional storage. This message
// normally appears with an ORA-4030 or ORA-4031 error which gives
// additional information. Sometimes this error can be caused by
// runaway programs.
// *Action: 1) Ensure there are no issues or bugs in your PL/SQL program which
// are causing excessive amounts of memory to be used.
// 2) Programmatically cause unused objects to be freed (e.g. by
// setting them to NULL).
// 3) Increase the amount of shared or process memory (as appropriate)
// available to you.
06501, 00000, "PL/SQL: program error"
// *Cause: This is an internal error message. An error has been detected in a
// PL/SQL program.
// *Action: Contact Oracle Support Services.
06502, 00000, "PL/SQL: numeric or value error%s"
// *Cause: An arithmetic, numeric, string, conversion, or constraint error
// occurred. For example, this error occurs if an attempt is made to
// assign the value NULL to a variable declared NOT NULL, or if an
// attempt is made to assign an integer larger than 99 to a variable
// declared NUMBER(2).
// *Action: Change the data, how it is manipulated, or how it is declared so
// that values do not violate constraints.
06503, 00000, "PL/SQL: Function returned without value"
// *Cause: A call to PL/SQL function completed, but no RETURN statement was
// executed.
// *Action: Rewrite PL/SQL function, making sure that it always returns
// a value of a proper type.
06504, 00000, "PL/SQL: Return types of Result Set variables or query do not match"
// *Cause: Number and/or types of columns in a query does not match declared
// return type of a result set variable, or declared types of two Result
// Set variables do not match.
// *Action: Change the program statement or declaration. Verify what query the variable
// actually refers to during execution.
06505, 00000, "PL/SQL: variable requires more than 32767 bytes of contiguous memory"
// *Cause: A PL/SQL variable was declared with a constraint which required more
// than 32767 bytes of memory.
// PL/SQL does not currently support allocations of contiguous memory
// greater than 32767 bytes.
// *Action: Consider reducing the constraint in the variable declaration.
// If that is not possible, try changing the database or national
// character set to such, that requires less memory for the same
// constraint. Note: changing the character set will impact execution
// of all PL/SQL code.
06508, 00000, "PL/SQL: could not find program unit being called%s"
// *Cause:
// *Action:
06509, 00000, "PL/SQL: ICD vector missing for this package"
// *Cause:
// *Action:
06510, 00000, "PL/SQL: unhandled user-defined exception"
// *Cause: A user-defined exception was raised by PL/SQL code, but
// not handled.
// *Action: Fix the problem causing the exception or write an exception
// handler for this condition. Or you may need to contact your
// application administrator or DBA.
06511, 00000, "PL/SQL: cursor already open"
// *Cause: An attempt was made to open a cursor that was already open.
// *Action: Close cursor first before reopening.
06512, 00000, "at %sline %s"
// *Cause: Backtrace message as the stack is unwound by unhandled
// exceptions.
// *Action: Fix the problem causing the exception or write an exception
// handler for this condition. Or you may need to contact your
// application administrator or DBA.
06513, 00000, "PL/SQL: index for PL/SQL table out of range for host language array"
// *Cause: An attempt is being made to copy a PL/SQL table to a host language
// array. But an index in the table is either less than one or
// greater than the maximum size of the host language array.
// When copying PL/SQL tables to host language arrays, the table
// entry at index 1 is placed in the first element of the array, the
// entry at index 2 is placed in the second element of the array, etc.
// If an table entry has not been assigned then the corresponding
// element in the host language array is set to null.
// *Action: Increase size of host language array, or decrease size of PL/SQL
// table. Also make sure that you don't use index values less than 1.
//
06514, 00000, "PL/SQL: The remote call cannot be handled by the server"
// *Cause: The remote call has parameters that are cursor variables or
// lob variables. This cannot be handled by stored procedures on
// your server.
// *Action: Avoid using cursor variables or lob variables as parameters for
// stored procedures on this server or upgrade your server to a
// version that supports this.
06515, 00000, "PL/SQL: unhandled exception %s"
// *Cause: An exception was raised by PL/SQL code, but not handled.
// The exception number is outside the legal range of Oracle
// errors.
// *Action: Fix the problem causing the exception or write an exception
// handler for this condition. Or you may need to contact your
// application administrator or DBA.
// *Comment: The exception was created via a pragma exception_init with a
// value larger than MAX_OEN. This capability exists for backward
// compatibility with V1 PL/SQL.
06516, 00000, "PL/SQL: the Probe packages do not exist or are invalid"
// *Cause: A Probe operation, probably an attempt to initialize the ORACLE
// server to debug PL/SQL, could not be completed because the
// Probe packages were not loaded or have become invalid.
// *Action: DBA should load the Probe packages. This can be done by running
// the pbload.sql script supplied with the RDBMS.
// *Comment: catproc.sql should load Probe by default, but it did not do so
// in releases prior to 7.3.3.
//
06517, 00000, "PL/SQL: Probe error - %s"
// *Cause: An error occurred while passing a Probe operation to the server
// for execution.
// *Action: Refer to the entry for the embedded error message.
// *Comment: The error is most likely a UPI or network problem. The Probe
// error is just to let the user know how the error arose.
06518, 00000, "PL/SQL: Probe version %s incompatible with version %s"
// *Cause: The current version of Probe is incompatible with the version on
// the ORACLE server.
// *Action: Refer to the documentation to ensure that this degree of
// compatibility is supported.
// *Comment: This error is not currently expected. It will only occur at a
// later time if incompatible Probe changes are introduced.
06519, 00000, "active autonomous transaction detected and rolled back"
// *Cause: Before returning from an autonomous PL/SQL block, all autonomous
// transactions started within the block must be completed (either
// committed or rolled back). If not, the active autonomous
// transaction is implicitly rolled back and this error is raised.
// *Action: Ensure that before returning from an autonomous PL/SQL block,
// any active autonomous transactions are explicitly committed
// or rolled back.
//-----------------------------------------------------------------------
//
// 06520 through 06529 reserved for Foreign function errors
//
//
06520, 00000, "PL/SQL: Error loading external library"
// *Cause: An error was detected by PL/SQL trying to load the external
// library dynamically.
// *Action: Check the stacked error (if any) for more details.
//
06521, 00000, "PL/SQL: Error mapping function"
// *Cause: An error was detected by PL/SQL trying to map the mentioned
// function dynamically.
// *Action: Check the stacked error (if any) for more details.
//
06522, 00000, "%s"
// *Cause: ORA-06520 or ORA-065211 could stack this error with
// a system specific error string.
// *Action: This error string should give the cause for errors
// ORA-06520 or ORA-065211
//
06523, 00000, "Maximum number of arguments exceeded"
// *Cause: There is an upper limit on the number of arguments that one
// can pass to the external function.
// *Action: Check the port specific documentation on how to calculate the
// upper limit.
//
06524, 00000, "Unsupported option : %s"
// *Cause: The option specified is an unsupported feature for external procedures.
//
// *Action: Correct the syntax in the external specification
//
06525, 00000, "Length Mismatch for CHAR or RAW data"
// *Cause: The length specified in the length variable has an illegal
// value. This can happen if you have requested requested a PL/SQL
// INOUT, OUT or RETURN raw variable to be passed as a RAW with
// no corresponding length variable. This error can also happen
// if there is a mismatch in the length value set in the length
// variable and the length in the orlvstr or orlraw.
//
// *Action: Correct the external procedure code and set the length variable
// correctly.
//
06526, 00000, "Unable to load PL/SQL library"
// *Cause: PL/SQL was unable to instantiate the library referenced by this
// referenced in the EXTERNAL syntax. This is a serious error and
// should normally not happen.
//
// *Action: Report this problem to customer support.
//
06527, 00000, "External procedure SQLLIB error: %s"
// *Cause: An error occurred in sqllib during execution of a Pro* external
// procedure.
//
// *Action: The message text indicates the actual SQLLIB error that
// occurred. Consult the Oracle Error Messages and Codes manual
// for a complete description of the error message and follow
// the appropriate action.
//
06528, 00000, "Error executing PL/SQL profiler"
// *Cause: An error occurred in during execution of a PL/SQL profiler
// procedure.
//
// *Action: Check the stacked errors for more details.
//
06529, 00000, "Version mismatch - PL/SQL profiler"
// *Cause: The PL/SQL profiler package (dbmspb.sql, prvtpbp.plb) does not
// match the version of the code in the server implementing the
// profiler.
//
// *Action: Run the package profload.sql in $ORACLE_HOME/rdbms/admin to load
// the correct version of the PL/SQL profiler packages
//
06530, 00000, "Reference to uninitialized composite"
// *Cause: An object, LOB, or other composite was referenced as a
// left hand side without having been initialized.
// *Action: Initialize the composite with an appropriate constructor
// or whole-object assignment.
//
06531, 00000, "Reference to uninitialized collection"
// *Cause: An element or member function of a nested table or varray
// was referenced (where an initialized collection is needed)
// without the collection having been initialized.
// *Action: Initialize the collection with an appropriate constructor
// or whole-object assignment.
//
06532, 00000, "Subscript outside of limit"
// *Cause: A subscript was greater than the limit of a varray
// or non-positive for a varray or nested table.
// *Action: Check the program logic and increase the varray limit
// if necessary.
//
06533, 00000, "Subscript beyond count"
// *Cause: An in-limit subscript was greater than the count of a varray
// or too large for a nested table.
// *Action: Check the program logic and explicitly extend if necessary.
//
06534, 00000, "Cannot access Serially Reusable package %s"
// *Cause: The program attempted to access a Serially Reusable package in
// PL/SQL called from SQL context (trigger or otherwise). Such an
// access is currently unsupported.
// *Action: Check the program logic and remove any references to Serially Reusable
// packages (procedure, function or variable references) which might happen
// in PL/SQL called from sql context (trigger or otherwise).
//
06535, 00000, "statement string in %s is NULL or 0 length"
// *Cause: The program attempted to use a dynamic statement string that
// was either NULL or 0 length.
// *Action: Check the program logic and ensure that the dynamic statement
// string is properly initialized.
//
06536, 00000, "IN bind variable bound to an OUT position"
// *Cause: The program attempted to bind an IN bind variable to a
// statement that was expecting an OUT bind variable at
// that position.
// *Action: Make sure that an OUT or IN OUT bind mode is specified
// for the bind argument.
//
06537, 00000, "OUT bind variable bound to an IN position"
// *Cause: The program attempted to bind an OUT bind variable to a
// statement that was expecting an IN bind variable at
// that position.
// *Action: Make sure that an IN or IN OUT bind mode is specified
// for the bind argument.
//
06538, 00000, "statement violates %s RESTRICT_REFERENCES pragma"
// *Cause: The program attempted to execute a dynamic statement which
// does not meet the purity level specified (in the pragma
// RESTRICT_REFERENCES directive) for the module executing the
// statement.
// *Action: Ensure that the dynamic statement meets the purity level
// specified for the module executing the statement.
//
06539, 00000, "target of OPEN must be a query"
// *Cause: The program attempted to perform an OPEN cursor operation
// on a dynamic statement that was not a query.
// *Action: Ensure that the OPEN cursor operation is done on a
// dynamic query statement.
//
//--------------------------------------------------------
// 06540 through 06549 reserved for pl/sql error handling
//
06540, 00000, "PL/SQL: compilation error"
// *Cause: A pl/sql compilation error occurred.
// However, the user generally will not see this error message.
// Instead, there will be accompanying PLS-nnnnn error messages.
// *Action:See accompanying PLS-nnnnn error messages.
//
06541, 00000, "PL/SQL: compilation error - compilation aborted"
// *Cause: A pl/sql compilation error occurred and the compilation was aborted;
// but the compilation unit was written out to the backing store.
// However, unlike ora-06545, the user generally will not see this error
// message. Instead, there will be accompanying PLS-nnnnn error messages.
// *Action:See accompanying PLS-nnnnn error messages.
//
06542, 00000, "PL/SQL: execution error"
// Currently unused. Reserved for future use.
//
06543, 00000, "PL/SQL: execution error - execution aborted"
//
//
06544, 00000, "PL/SQL: internal error, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"
// *Cause: A pl/sql internal error occurred.
// *Action:Report as a bug; the first argument is the internal error nuber.
//
06545, 00000, "PL/SQL: compilation error - compilation aborted"
// *Cause: A pl/sql compilation error occurred and the compilation was
// aborted completely without the compilation unit being written
// out to the backing store. Unlike ora-06541, the user will always
// see this error along with the accompaning PLS-nnnnn error messages.
// *Action:See accompanying PLS-nnnnn error messages.
//
06546, 00000, "DDL statement is executed in an illegal context"
// *Cause: DDL statement is executed dynamically in illegal PL/SQL context.
// - Dynamic OPEN cursor for a DDL in PL/SQL
// - Bind variable's used in USING clause to EXECUTE IMMEDIATE a DDL
// - Define variable's used in INTO clause to EXECUTE IMMEDIATE a DDL
// *Action: Use EXECUTE IMMEDIATE without USING and INTO clauses to execute
// the DDL statement.
06547, 00000, "RETURNING clause must be used with INSERT, UPDATE, or DELETE statements"
// *Cause: EXECUTE IMMEDIATE with a RETURNING clause is used to execute
// dynamic UPDATE, INSERT, or DELETE statements only.
// *Action: use RETURNING clause in EXECUTE IMMEDIATE for INSERT, UPDATE,
// or DELETE statements only. For other statements, use USING clause
// instead.
06548, 00000, "no more rows needed"
// *Cause: The caller of a pipelined function did not need more rows
// to be produced by the pipelined function.
// *Action: Do not catch the NO_DATA_NEEDED exception in an exception handling
// block.
//
06549, 00000, "PL/SQL: failed to dynamically open shared object (DLL): %s:%s"
// *Cause: One possible cause might be there are too many DLLs open at the
// same time.
// *Action:
//
//--------------------------------------------------------
//
06550, 00000, "line %s, column %s:\n%s"
// *Cause: Usually a PL/SQL compilation error.
// *Action:
06551, 00000, "PL/SQL: Unhandled exception"
// *Cause:
// *Action:
06552, 00000, "PL/SQL: %s"
// *Cause:
// *Action:
06553, 00000, "PLS-%s: %s"
// *Cause:
// *Action:
06554, 00000, "package DBMS_STANDARD must be created before using PL/SQL"
// *Cause: The DBMS specific extensions to PL/SQL's package "STANDARD"
// are in package "DBMS_STANDARD". This package must be
// created before using PL/SQL.
// *Action: Create package "DBMS_STANDARD". The source for this
// PL/SQL stored package is provided with the distribution.
06555, 00000, "this name is currently reserved for use by user SYS"
// *Cause: You tried to create a package named "STANDARD",
// "DBMS_STANDARD" or "DEBUG_IO". These are currently
// reserved for use by user SYS.
// *Action: Choose another name for your package.
06556, 00000, "the pipe is empty, cannot fulfill the unpack_message request"
// *Cause: There are no more items in the pipe.
// *Action: Check that the sender and receiver agree on the number and types
// of items placed on the pipe.
06557, 00000, "null values are not allowed for any parameters to pipe icd's"
// *Cause: Internal error from the dbms_pipe package.
// *Action:
06558, 00000, "buffer in dbms_pipe package is full. No more items allowed"
// *Cause: The pipe buffer size has been exceeded.
// *Action:
06559, 00000, "wrong datatype requested, %s, actual datatype is %s"
// *Cause: The sender put different datatype on the pipe than that being
// requested (package 'dbms_pipe'). The numbers are: 6 - number,
// 9 - char, 12 - date.
// *Action: Check that the sender and receiver agree on the number and types
// of items placed on the pipe.
06560, 00000, "pos, %s, is negative or larger than the buffer size, %s"
// *Cause: Internal error from the dbms_pipe package.
// *Action:
06561, 00000, "given statement is not supported by package DBMS_SQL"
// *Cause: Attempting to parse an unsupported statement using procedure
// PARSE provided by package DBMS_SQL.
// *Action: Only statements which begin with SELECT, DELETE, INSERT, UPDATE,
// LOCK, BEGIN, DECLARE or << (PL/SQL label delimiter) are supported.
06562, 00000, "type of out argument must match type of column or bind variable"
// *Cause: Attempting to get the value of a column or
// a bind variable by calling procedure COLUMN_VALUE or
// VARIABLE_VALUE of package DBMS_SQL but the type of
// the given out argument where to place the value is different
// from the type of the column or bind variable that was previously
// defined by calling procedure DEFINE_COLUMN (for defining a column)
// or BIND_VARIABLE (for binding a bind variable) of package DBMS_SQL.
// *Action: Pass in an out argument of the correct type when calling
// procedure COLUMN_VALUE or VARIABLE_VALUE. The right
// type is the type that was provided when defining the column or
// binding the bind variable.
06563, 00000, "name has too many parts"
// *Cause: The name to be resolved was specified as one of the following:
// - With three parts (A.B.C) but the A.B parts resolved to an object
// that did not expose visible nested procedures; the C part could
// not be resolved.
// - With two parts (A.B) and the A part resolved to an object that
// did not expose visible nested procedures; the B part could not be
// resolved.
// *Action: Specify the valid name of an object or of a packaged procedure
// or function without specifying any additional trailing parts.
06564, 00000, "object %s does not exist"
// *Cause: The named object could not be found. Either it does not exist
// or you do not have permission to access it.
// *Action: Create the object or get permission to access it.
06565, 00000, "cannot execute %s from within stored procedure"
// *Cause: The named procedure cannot be executed from within a stored
// procedure, function or package. This function can only be
// used from pl/sql anonymous blocks.
// *Action: Remove the procedure from the calling stored procedure.
06566, 00000, "invalid number of rows specified"
// *Cause: An invalid number of rows was specified in a call to the
// procedure DEFINE_COLUMN in the package DBMS_SQL. For a given
// parsed statement in a given cursor, all columns must be
// defined to have the same number of rows, so all the calls
// to DEFINE_COLUMN must specify the same number of rows.
// *Action: Specify a number that matches that for previously defined
// columns.
06567, 00000, "invalid number of values specified"
// *Cause: An invalid number of values to be bound was specified in a
// call to the procedure BIND_VARIABLE in the package DBMS_SQL.
// In order to execute a given parsed statement in a given cursor,
// the same number of values must have been bound for all bind
// variables, so when EXECUTE is called, the latest calls to
// BIND_VARIABLE must must have specified the same number of values
// to be bound for all bind variables.
// *Action: Make sure that the same number of values have been bound for all
// of the bind variables.
06568, 00000, "obsolete ICD procedure called"
// *Cause: An obsolete ICD procedure was called by a PL/SQL program.
// The PL/SQL program was probably written for an eralier release of
// RDBMS.
// *Action: Make sure that all PL/SQL programs have been upgraded to the latest
// release of the RDBMS. This can be accomplished by following
// upgrade instructions in the README file, or by running
// the catproc.sql script supplied with the RDBMS.
06569, 00000, "Collection bound by bind_array contains no elements"
// *Cause: A collection with zero elements was bound to a bind variable
// in a call to procedure BIND_ARRAY in the package DBMS_SQL.
// In order to execute a bind of a collection, the collection must
// contain at least one element. If no elements are present then
// at execute time there will be no value for this bind and the
// statement is meaningless.
// *Action: Fill the collection with the elements you want to bind and
// try the bind call again.
/
/
06570, 00000, "shared pool object does not exist, cannot be pinned/purged"
// *Cause: The specified shared pool shared cursor could not be found,
// therefore it cannot be pinned/purged.
// *Action: Make sure that a correct shared cursor name is given. Names
// are a string of the form 'HHHHHHHH,SDDDDDDDDDD' where the H's
// are an 8 digit hex number from the 'address' column of v$sqlarea,
// and the D's are a 1 to 10 digit decimal number with an optional
// leading sign (from the 'hash_value' column)
// *Action: Remove the procedure from the calling stored procedure.
/
/ 6571-6579 Reserved for Plsql functions called from Sql
/
06571, 00000, "Function %s does not guarantee not to update database"
// *Cause: There are two possible causes for this message:
// * A SQL statement references a packaged, PL/SQL function
// that does not contain a pragma that prevents the database
// from being updated.
// * A SQL statement references a stand-alone, PL/SQL function
// that contains an instruction to update the database.
// *Action: If the referenced function is a packaged, PL/SQL function:
// Recreate the PL/SQL function with the required pragma; be
// certain to include the 'Write No Database State' (WNDS)
// argument in the argument list of the pragma.
// If the referenced function is a stand-alone, PL/SQL function:
// Do not use the function.
06572, 00000, "Function %s has out arguments"
// *Cause: A SQL statement references either a packaged, or a stand-alone,
// PL/SQL function that contains an OUT parameter in its argument
// list. PL/SQL functions referenced by SQL statements must not
// contain the OUT parameter.
// *Action: Recreate the PL/SQL function without the OUT parameter in the
// argument list.
06573, 00000, "Function %s modifies package state, cannot be used here"
// *Cause: There are two possible causes for this message:
// * A SQL statement references a packaged, PL/SQL function that
// does not contain a pragma containing the 'Write no Package
// State' (WNPS).
// * A SQL statement references a stand-alone, PL/SQL function
// that modifies a package state. A stand-alone, PL/SQL function
// referenced by a SQL statement cannot modify a package state.
// *Action: If the function is a packaged, PL/SQL function: Recreate
// the function and include a pragma containing the 'Write no
// Package State' (WNPS).
// If the function is a stand-alone, PL/SQL function: Delete
// the function from the SQL statement.
06574, 00000, "Function %s references package state, cannot execute remotely"
// *Cause: There are two possible causes for this message:
// * A remote, packaged function or a remote-mapped, local,
// packaged function that does not contain a pragma with the
// 'Write no Package State' (WNPS) and 'Read no Package State'
// (RNPS) arguments references a package state.
// * A remote, stand-alone function or a remote-mapped, local,
// stand-alone function contains a reference to a package
// state (reads or writes a package variable).
// Only local functions that are referenced in a SELECT list, VALUES
// clause of an INSERT statement, or SET clause of an UPDATE
// statement can modify a package state.
// *Action: If the function is a packaged function: Recreate the function
// and include a pragma containing the 'Write no Package State'
// (WNPS) and 'Read no Package State' (RNPS) arguments.
// If the function is a stand-alone function: Do not call the
// function.
06575, 00000, "Package or function %s is in an invalid state"
// *Cause: A SQL statement references a PL/SQL function that is in an
// invalid state. Oracle attempted to compile the function, but
// detected errors.
// *Action: Check the SQL statement and the PL/SQL function for syntax
// errors or incorrectly assigned, or missing, privileges for a
// referenced object.
06576, 00000, "not a valid function or procedure name"
// *Cause: Could not find a function (if an INTO clause was present) or
// a procedure (if the statement did not have an INTO clause) to
// call.
// *Action: Change the statement to invoke a function or procedure
06577, 00000, "output parameter not a bind variable"
// *Cause: The argument corresponding to an IN/OUT or OUT parameter
// for a function or a procedure or a function return value in
// a CALL statement must be a bind variable.
// *Action: Change the argument to a bind variable
06578, 00000, "output parameter cannot be a duplicate bind"
// *Cause: The bind variable corresponding to an IN/OUT or OUT parameter
// for a function or a procedure or a function return value in a
// CALL statement cannot be a duplicate bind variable.
// *Action: Change the bind variable to be unique
/
06579, 00000, " Bind variable not big enough to hold the output value"
// *Cause: The bind variable specified by the user is not large enough to
// hold the output returned by the function or a procedure.
// *Action: Specify a bind variable of larger size.
/
06580, 00000, "Hash Join ran out of memory while keeping large rows in memory"
// *Cause: Hash Join reserves 3 slots (each slot size = DB_BLOCK_SIZE *
// HASH_JOIN_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than
// that, this error will be raised.
// *Action: Increase HASH_JOIN_MULTIBLOCK_IO_COUNT so that each joined row
// fits in a slot. HASH_AREA_SIZE may also need to be increaed.
/
/ 6581-6591 Reserved for European OEM Ports (contact: egroenen.nl)
/
06592, 00000, "CASE not found while executing CASE statement"
// *Cause: A CASE statement must either list all possible cases or have an
// else clause.
// *Action: Add all missing cases or an else clause.
/
06593, 00000, "%s is not supported with natively compiled PL/SQL modules"
// *Cause: Specified feature is not yet supported for natively compiled
// PL/SQL modules yet.
// *Action: Recompile the relevant PL/SQL modules in non-native mode by
// setting the parameter plsql_compiler_flags to INTERPRETED.
/
06594, 00000, "ICD is unable to compute a result"
// *Document: NO
// *Cause: This exception is internal to PL/SQL, and should not be seen by
// customers.
// *Action: Contact Oracle Support Services.
/
06595, 00000, "REF CURSOR parameters are not supported in forwarded RPC calls"
// *Cause: An attempt was made to make a forwarded RPC call with a REF CURSOR
// parameter.
// *Action: Either call the remote function directly (i.e., not by way of
// forwarding), or move the remote function to a database where it can
// be called directly.
/
06596, 00000, "object cannot be purged, object is permanently kept in shared pool"
// *Cause: The specified object was permanently kept, therefore, cannot be
// purged.
// *Action: Use DBMS_SHARED_POOL.UNKEEP procedure to unkeep the object and then
// purge it.
/
06597, 00000, "Failed to increase the session's call stack memory to %s bytes at a depth of %s calls. (The current maximum is %s bytes.)"
// *Cause: PL/SQL program execution used more call stack memory than permitted.
// *Action: * Ask your DBA to increase the maximum allowed call stack memory.
// * Decrease the amount of call stack used by the program. This may
// be accomplished by using fewer, smaller local variables, or by
// limiting the depth of function call nesting.
/
06598, 00000, "insufficient INHERIT PRIVILEGES privilege"
// *Cause: An attempt was made to run an AUTHID CURRENT_USER function or
// procedure, or to reference a BEQUEATH CURRENT_USER view, and the
// owner of that function, procedure, or view lacks INHERIT PRIVILEGES
// privilege on the calling user.
// *Action: Either do not call the function or procedure or reference the view,
// or grant the owner of the function, procedure, or view
// INHERIT PRIVILEGES privilege on the calling user.
/
06599, 00000, "unsupported LOB operation in RPC call"
// *Cause: An attempt was made to perform certain large object (LOB) date type
// operations (for example, deep copying of a temporary or abstract
// LOB on the client side) while performing a remote procedural call
// (RPC). This is not currently supported.
// *Action: Perform the LOB operation in question before starting the RPC. Or,
// perform those LOB operations on the server side instead of the
// client side.
/
/ 6600-6699 Reserved for more SQL*Net errors
/
/ 6700-6899 Reserved for TLI SQL*NET driver errors
/
/ 6900-6999 Reserved for more SQL*Net errors
/
/
/ 6600 - 6622: SQL*Net LU6.2 driver errors
/
06600, 00000, "LU6.2 Driver: SNA software is not loaded"
// *Cause: The SNA software is not running.
// *Action: Start the SNA software and try again.
06601, 00000, "LU6.2 Driver: Invalid database ID string"
// *Cause: The database string in the connect was invalid.
// *Action: Provide a valid database string, as defined in documentation.
06602, 00000, "LU6.2 Driver: Error allocating context area"
// *Cause: Context area failure.
// *Action: Contact your local service representative.
06603, 00000, "LU6.2 Driver: Error allocating memory"
// *Cause: Operating system refused request for memory.
// *Action: Contact you local service representative.
06604, 00000, "LU6.2 Driver: Unable to allocate session with remote LU"
// *Cause: Allocate system call failed.
// *Action: Ensure that the SNA software is running and that sessions are free.
// If this is the case, then check your SNA configuration data for
// errors. You may have entered an incorrect parameter.
06605, 00000, "LU6.2 Driver: Unexpected line turnaround"
// *Cause: SNA software switched from send to receive unexpectedly.
// *Action: Check the SNA configuration data, particularly parameters
// associated with a session.
06606, 00000, "LU6.2 Driver: Unexpected response from SNA"
// *Cause: A parameter in an SNA call returned an unexpected value.
// *Action: Attempt to reproduce problem, debug and record the value of the
// 'what' data parameter at the time of error. Then contact your
// service representative.
06607, 00000, "LU6.2 Driver: Reset occurred in send state"
// *Cause: A reset was issued whilst in send state.
// *Action: Check the SNA LOG data, if relevent, for further information.
06608, 00000, "LU6.2 Driver: Reset occurred in receive state"
// *Cause: A reset was received from the partner whilst in receive
// state. This may be because the partner deallocated.
// *Action: Check the SNA LOG data, if relevent, for further information.
/
/ 06609 is not used by the LU6.2 Driver.
/
06610, 00000, "LU6.2 Driver: Failed during deallocation"
// *Cause: LU6.2 driver was unable to deallocate gracefully.
// *Action: Check the reason for deallocation. Consult the SNA
// LOG data.
06611, 00000, "LU6.2 Driver: Request to send error"
// *Cause:
// *Action:
06612, 00000, "LU6.2 Driver: Send data error"
// *Cause:
// *Action:
06613, 00000, "LU6.2 Driver: Receive and wait error"
// *Cause:
// *Action:
06614, 00000, "LU6.2 Driver: Receive Immediate error"
// *Cause:
// *Action:
06615, 00000, "LU6.2 Driver: Send error"
// *Cause:
// *Action:
06616, 00000, "LU6.2 Driver: Attach to LU failed"
// *Cause: The SQL*Net LU6.2 driver was unable to attach to the
// LU specified in the connect string, or was unable to
// attach to the default LU.
// *Action: Check that the LU name specified in the connect string,
// or the default LU name if no LU was specified, is
// correctly configured and operational.
06617, 00000, "LU6.2 Driver: Attach to PU failed"
// *Cause:
// *Action:
06618, 00000, "LU6.2 Driver: Activation of subnetwork failed"
// *Cause:
// *Action:
06619, 00000, "LU6.2 Driver: Unable to activate remote partner"
// *Cause:
// *Action:
06620, 00000, "LU6.2 Driver: Invalid remote partner"
// *Cause:
// *Action:
06621, 00000, "LU6.2 Driver: Allocation error"
// *Cause:
// *Action:
06622, 00000, "LU6.2 Driver: Unable to attach to SNA"
// *Cause: The SQL*Net LU6.2 driver could not attach to the SNA
// software on your machine. The most likely cause is that the SNA
// software is not operational.
// *Action: Check the status of the SNA software, ensure that it is
// operational and then try again.
/
/ 6700-6899 Reserved for TLI SQL*NET driver errors
/
06700, 00000, "TLI Driver: incorrect message type from host"
// *Cause: TLI received a message with an unrecognizable message type.
// *Action: Contact your customer support representative.
06701, 00000, "TLI Driver: incorrect number of bytes written"
// *Cause: TLI sent a message that was apparently successful, but the
// number of bytes transmitted did not match the number
// of bytes supplied to the driver.
// *Action: Contact your customer support representative.
06702, 00000, "TLI Driver: cannot allocate context area"
// *Cause: TLI could not allocate heap space for the context area.
// *Action: Contact your customer support representative.
06703, 00000, "TLI Driver: send break message failed"
// *Cause: TLI failed to send a break message across the connection.
// *Action: Contact your customer support representative.
06704, 00000, "TLI Driver: receive break message failed"
// *Cause: TLI failed to receive an expected break message.
// *Action: Contact your customer support representative.
06705, 00000, "TLI Driver: remote node is unknown"
// *Cause: TLI could not find your remote host information.
// *Action: Make sure you specified the hostname correctly on the command
// line. (Also, check your capitalization and spelling.)
06706, 00000, "TLI Driver: service not found"
// *Cause: TLI could not find service information for the specified service
// name.
// *Action: If you specified the service name on the command line or with the
// environment variable TLI_SERVER, make sure you specified it
// correctly. If the service name is not in the SERVICES file for
// your protocol, ask your system adminstrator to add it.
06707, 00000, "TLI Driver: connection failed"
// *Cause: TLI failed to establish the connection to a SQL*Net TCP/IP server
// due to an error encountered by the remote server, which has
// supplied a string describing the remote error.
// *Action: See the SQL*Net TCP/IP User's Guide section "orasrv Messages" for
// the specific cause and action.
06708, 00000, "TLI Driver: message receive failure"
// *Cause: TLI encountered an error receiving a message from the communication
// channel.
// *Action: Contact your customer support representative.
06709, 00000, "TLI Driver: message send failure"
// *Cause: TLI encountered an error sending a message across the communication
// channel.
// *Action: Contact your customer support representative.
06710, 00000, "TLI Driver: send interrupt break message failed"
// *Cause: TLI failed to send a break message while handling an interrupt
// signal from the user.
// *Action: Contact your customer support representative.
06711, 00000, "TLI Driver: error on bind"
// *Cause: TLI failed to assign a network address to the communication channel.
// *Action: Contact your customer support representative.
06712, 00000, "TLI Driver: error on accept"
// *Cause: TLI failed to accept a connection request from the client.
// *Action: Contact your customer support representative.
06713, 00000, "TLI Driver: error on connect"
// *Cause: TLI failed to connect the client to the remote server. The network
// line to the remote host may be down.
// *Action: Use other network login programs to make sure that the remote
// host is accessible.
06720, 00000, "TLI Driver: SID lookup failure"
// *Cause: The database SID supplied in the database login string was not
// recognized by the remote host.
// *Action: Ask your system administrator to add the appropriate SID entry
// to oratab on the remote host.
06721, 00000, "TLI Driver: spurious client req"
// *Cause: The remote TLI server received an undefined request.
// *Action: Contact your customer support representative.
06722, 00000, "TLI Driver: connection setup failure"
// *Cause: The remote TLI server rejected the connection request, and the
// client was unable to retrieve an error code or message.
// *Action: Contact your customer support representative.
06730, 00000, "TLI Driver: unable to open clone device"
// *Cause: TLI failed to open the Streams clone device associated with the
// transport provider.
// *Action: Contact your customer support representative.
06731, 00000, "TLI Driver: cannot alloc t_call"
// *Cause: TLI cannot allocate space for the client's connection information.
// *Action: Contact your customer support representative.
06732, 00000, "TLI Driver: cannot alloc t_discon"
// *Cause: TLI cannot allocate space for the client's disconnection
// information.
// *Action: Contact your customer support representative.
06733, 00000, "TLI Driver: failed to receive disconnect"
// *Cause: TLI failed to receive an expected disconnection message during
// connection release.
// *Action: Contact your customer support representative.
06734, 00000, "TLI Driver: cannot connect"
// *Cause: TLI failed to connect the client to the remote server.
// *Action: Check that the remote TLI server is running.
06735, 00000, "TLI Driver: client failed to close error conn"
// *Cause: TLI failed to properly close a connection after an error was
// received.
// *Action: Contact your customer support representative.
06736, 00000, "TLI Driver: server not running"
// *Cause: TLI timed out while attempting to connect to the remote TLI server.
// *Action: Check that the remote TLI server is running with the status utility
// for the transport provider you are using. If it is not, ask
// your system adminstrator to start it.
06737, 00000, "TLI Driver: connection failed"
// *Cause: TLI could not establish a connection to the remote TLI server.
// *Action: Check that the remote TLI server is running with the status
// utility for the transport provider you are using.
06741, 00000, "TLI Driver: unable to open protocol device"
// *Cause: The TLI server failed to open the Streams device associated with
// the transport provider.
// *Action: Contact your customer support representative.
06742, 00000, "TLI Driver: cannot alloc t_bind"
// *Cause: The TLI server cannot allocate space for its requested network
// address.
// *Action: Contact your customer support representative.
06743, 00000, "TLI Driver: cannot alloc t_bind"
// *Cause: The TLI server cannot allocate space for its actual network
// address.
// *Action: Contact your customer support representative.
06744, 00000, "TLI Driver: listener cannot bind"
// *Cause: The TLI server failed to assign the correct network address on
// which to listen for connections.
// *Action: Contact your customer support representative.
06745, 00000, "TLI Driver: listener already running"
// *Cause: The network address on which the TLI server awaits connection
// requests is in use, possibly because the server is already running.
// *Action: Ensure that the TLI server is not already running. If it is
// not running and this error message recurs, contact your customer
// support representative.
06746, 00000, "TLI Driver: cannot alloc t_call"
// *Cause: TLI cannot allocate space for the TLI server's connection
// information.
// *Action: Contact your customer support representative.
06747, 00000, "TLI Driver: error in listen"
// *Cause: The TLI server encountered an error while listening for
// connection requests.
// *Action: Contact your customer support representative.
06748, 00000, "TLI Driver: cannot allocate t_discon"
// *Cause: TLI cannot allocate space for the TLI server's disconnection
// information.
// *Action: Contact your customer support representative.
06749, 00000, "TLI Driver: option not allowed across network"
// *Cause: The requested TLI server command must be issued from the same
// host on which the server is running.
// *Action: Log in to the remote host and try again.
06750, 00000, "TLI Driver: sync failed"
// *Cause: The ORACLE process started by the TLI server was unable to
// synchronize its inherited connection.
// *Action: Contact your customer support representative.
06751, 00000, "TLI Driver: bound addresses unequal"
// *Cause: The osn check server address failed. The bound server address was
// not the same as the requested binding address.
// *Action: Contact your customer support representative.
06752, 00000, "TLI: error in signal setup"
// *Cause: A call to sigaction() returned with a system error.
// *Action: Contact your customer support representative.
06753, 00000, "TLI Driver: name-to-address mapping failed"
// *Cause: For SVR4, the netdir_getbyname() call failed for some
// unknown reason.
// *Action: Contact your custumer service representative.
06754, 00000, "TLI Driver: unable to get local host address"
// *Cause: The name of the remote host to connect to was not specified, and
// the name of the local host cannot be retrieved from the HOSTS file.
// *Action: Contact your system administrator.
06755, 00000, "TLI Driver: cannot close transport endpoint"
// *Cause: The TLI server was unable to close a connection after passing it
// to an ORACLE process.
// *Action: Contact your customer support representative.
06756, 00000, "TLI Driver: cannot open oratab"
// *Cause: The TLI server could not open the file used to define the locations
// of remotely accessible databases.
// *Action: Ask your system administrator to check that the file exists and
// has the correct permissions.
06757, 00000, "TLI Driver: server got bad command"
// *Cause: The TLI server received an invalid command.
// *Action: Contact your customer support representative.
06760, 00000, "TLI Driver: timeout reading orderly release"
// *Cause: TLI was not able to retreive an expected disconnect message while
// closing the communication channel.
// *Action: Contact your customer support representative.
06761, 00000, "TLI Driver: error sending orderly release"
// *Cause: TLI encountered an error sending a disconnect message closing the
// communication channel.
// *Action: Contact your customer support representative.
06762, 00000, "TLI Driver: error reading orderly release"
// *Cause: TLI encountered an error receiving an expected disconnect message
// while closing the communication channel.
// *Action: Contact your customer support representative.
06763, 00000, "TLI Driver: error sending disconnect"
// *Cause: TLI encountered an error sending a disconnect message closing the
// communication channel.
// *Action: Contact your customer support representative.
06764, 00000, "TLI Driver: error reading disconnect"
// *Cause: TLI was not able to retreive an expected disconnect message while
// closing the communication channel.
// *Action: Contact your customer support representative.
06765, 00000, "TLI Driver: error awaiting orderly release"
// *Cause: TLI encountered an error awaiting a disconnect message while
// closing the communication channel.
// *Action: Contact your customer support representative.
06766, 00000, "TLI Driver: close failed during release"
// *Cause: TLI failed to close the communication channel after receiving
// a disconnect message.
// *Action: Contact your customer support representative.
06767, 00000, "TLI Driver: alloc failed during release"
// *Cause: TLI cannot allocate space for disconnection information while
// closing the communication channel.
// *Action: Contact your customer support representative.
06770, 00000, "TLI Driver: error sending version"
// *Cause: TLI encountered an error while sending its version information
// during connection establishment.
// *Action: Contact your customer support representative.
06771, 00000, "TLI Driver: error reading version"
// *Cause: TLI encountered an error while awaiting the expected version
// information during connection establishment.
// *Action: Contact your customer support representative.
06772, 00000, "TLI Driver: error sending command"
// *Cause: TLI encountered an error while sending a command message during
// connection establishment.
// *Action: Contact your customer support representative.
06773, 00000, "TLI Driver: error reading command"
// *Cause: TLI encountered an error while awaiting the expected command
// message during connection establishment.
// *Action: Contact your customer support representative.
06774, 00000, "TLI Driver: error sending break mode"
// *Cause: TLI encountered an error while sending break-mode message during
// connection establishment.
// *Action: Contact your customer support representative.
06775, 00000, "TLI Driver: error reading break mode"
// *Cause: TLI encountered an error while awaiting the expected break-mode
// message during connection establishment.
// *Action: Contact your customer support representative.
06776, 00000, "TLI Driver: error sending parms"
// *Cause: TLI encountered an error while sending the connection parameters
// during connection establishment.
// *Action: Contact your customer support representative.
06777, 00000, "TLI Driver: error reading parms"
// *Cause: TLI encountered an error while awaiting the expected connection
// parameter message during connection establishment.
// *Action: Contact your customer support representative.
06778, 00000, "TLI Driver: error sending ccode"
// *Cause: TLI encountered an error while sending the completion status message
// during connection establishment.
// *Action: Contact your customer support representative.
06779, 00000, "TLI Driver: error reading ccode"
// *Cause: TLI encountered an error while awaiting the expected completion
// status message during connection establishment.
// *Action: Contact your customer support representative.
06780, 00000, "TLI Driver: recv error code failed"
// *Cause: TLI encountered an error while awaiting an expected error message
// during connection establishment.
// *Action: Contact your customer support representative.
06781, 00000, "TLI Driver: error reading negotation string"
// *Cause: TLI encountered an error while awaiting the expected negotiation
// message during connection establishment.
// *Action: Contact your customer support representative.
06790, 00000, "TLI Driver: poll failed"
// *Cause: TLI was unable to poll the communication channel for possible
// incoming messages.
// *Action: Contact your customer support representative.
06791, 00000, "TLI Driver: poll returned error event"
// *Cause: TLI received an unexpected event while polling the communication
// channel for possible incoming messages.
// *Action: Contact your customer support representative.
06792, 00000, "TLI Driver: server cannot exec oracle"
// *Cause: The remote TLI server was unable to start an ORACLE process on
// behalf of the client.
// *Action: Note the operating system error message or number and contact
// your system adminstrator. The permissions on the remote ORACLE
// program may be set incorrectly.
06793, 00000, "TLI Driver: server cannot create new process"
// *Cause: The remote TLI server was unable to start an ORACLE process on
// behalf of the client.
// *Action: Note the operating system error message or number and contact
// your system adminstrator. The remote host may be unable to create
// any new processes due to a full process table.
06794, 00000, "TLI Driver: shadow process could not retrieve protocol info"
// *Cause: The ORACLE process either failed to allocate memory to store
// the protocol information record, or the protocol rejected the
// request for some unknown reason.
// *Action: Contact your customer support representative.
06800, 00000, "TLI Driver: SQL*Net SPX client went away during reconnect"
// *Cause: The client process was aborted by the system or the user, and
// was unable to complete the connection establishment with the
// server listener process.
// *Action: Determine cause of client exit, and reattempt connection.
06801, 00000, "TLI Driver: listen for SPX server reconnect failed"
// *Cause: An unknown event occurred on the client's listening socket.
// *Action: Contact your customer support representative.
06802, 00000, "TLI Driver: could not open the /etc/netware/yellowpages file"
// *Cause: The /etc/netware/yellowpages file does not exist, or is not
// readable by the TLI listener process.
// *Action: Insure the file exists and is readable. Make sure that the
// server machine's node name, network number, ethernet address,
// and listening socket number are encoded in the file.
06803, 00000, "TLI Driver: the IPX device file could not be opened"
// *Cause: The /dev/ipx file does not exist, or the driver has not been
// installed in the kernel correctly.
// *Action: Reinvoke the Oracle root installation. If problem continues,
// contact your customer support representative.
06804, 00000, "TLI Driver: could not bind an IPX address at initialization"
// *Cause: The IPX driver has not been correctly installed.
// *Action: Reinvoke the Oracle root installation. If problem continues,
// contact your customer support representative.
06805, 00000, "TLI Driver: could not send datagram SAP packet for SPX"
// *Cause: The socket endpoint for sending SAP packet was corrupted for
// some unknown reason.
// *Action: Contact your customer support representative.
06806, 00000, "TLI Driver: could not complete protocol initialization for SPX"
// *Cause: A step in the SPX/IPX protocol initialization failed.
// *Action: Check the previous error reported, and follow corrective action.
06807, 00000, "TLI Driver: could not open ethernet device driver file"
// *Cause: The file /dev/eth does not exist, or the driver it references
// could not be opened.
// *Action: The system's real ethernet device file, for example /dev/wd, for
// the Western Digital ethernet driver, should be linked to the
// file /dev/eth. If this has been done, insure that the ethernet
// driver has been installed by completing the TCP/IP installation
// on your system, and testing a connection. If problem continues,
// contact your customer support representative for a list of
// supported ethernet drivers.
06808, 00000, "TLI Driver: could not link IPX and ethernet streams"
// *Cause: Either the ethernet driver has not been installed in the system
// correctly, or the ethernet driver is not supported.
// *Action: Insure that the ethernet driver has been installed by completing
// the TCP/IP installation on your system, and testing a connection.
// If problem continues, contact your customer support representative
// for a list of supported ethernet drivers.
06809, 00000, "TLI Driver: could not clear the IPX ethernet SAP at init"
// *Cause: The IPX driver has not been correctly installed.
// *Action: Reinvoke the Oracle root installation. If problem continues,
// contact your customer support representative.
06810, 00000, "TLI Driver: could not set the IPX ethernet SAP at init"
// *Cause: The IPX driver has not been correctly installed.
// *Action: Reinvoke the Oracle root installation. If problem continues,
// contact your customer support representative.
06811, 00000, "TLI Driver: could not set the IPX network number at init"
// *Cause: The IPX driver has not been correctly installed, or the
// network number encoded in the /etc/netware/yellowpages file
// is invalid.
// *Action: The network number in the yellowpages file should match the
// four-byte network number of your Novell file server. If this
// is configured correctly, reinvoke the Oracle root installation.
// If problem continues, contact your customer support representative.
06812, 00000, "TLI Driver: could not read the ethernet driver's node address"
// *Cause: The ethernet driver is not installed correctly, or does not
// support this operation.
// *Action: Contact your customer support representative for a list of
// supported ethernet drivers.
06813, 00000, "TLI Driver: the configured ethernet address is incorrect"
// *Cause: The node address read from the ethernet driver does not match
// the value encoded in the /etc/netware/yellowpages file for this
// server.
// *Action: Confirm the correct ethernet node address for your LAN card, and
// enter this value in the yellowpages file.
06814, 00000, "TLI Driver: the SPX device file could not be opened"
// *Cause: The /dev/nspxd file does not exist, or the driver has not been
// installed in the kernel correctly.
// *Action: Reinvoke the Oracle root installation. If problem continues,
// contact your customer support representative.
06815, 00000, "TLI Driver: could not link SPX and IPX streams"
// *Cause: The SPX driver has not been correctly installed.
// *Action: Reinvoke the Oracle root installation. If problem continues,
// contact your customer support representative.
06816, 00000, "TLI Driver: could not set the SPX SAP address"
// *Cause: The SPX driver has not been correctly installed.
// *Action: Reinvoke the Oracle root installation. If problem continues,
// contact your customer support representative.
06817, 00000, "TLI Driver: could not read the Novell network address"
// *Cause: The file $ORACLE_HOME/spx/address could not be opened for
// reading and writing.
// *Action: Make sure ORACLE_HOME is set, and the permissions on
// the ORACLE_HOME are read, write. If this file has been
// unintentially deleted, run spxctl (net option) to reset
// the configured Novell network number for SQL*Net SPX.
/
/ 6900-6999 Reserved for more SQL*Net errors
/
/ 6900-6939 CMX errors
/
06900, 00000, "CMX: cannot read tns directory"
// *Cause: CMX is not started on your system.
// *Action: Install and/or start CMX on your system.
06901, 00000, "CMX: no local name assigned to local application"
// *Cause: Local application oracmx has no local name assigned
// *Action: Enter unique local name for oracmx in the tns directory
06902, 00000, "CMX: cannot attach to cmx subsystem"
// *Cause: ccp-xxxx is not started
// *Action: start your ccp software on the communication controller
06903, 00000, "CMX: cannot read transport address of remote application"
// *Cause: remote application not entered in tns directory
// *Action: enter remote application in tns directory
06904, 00000, "CMX: no transport address available for remote application"
// *Cause: no local name assigned to remote application
// *Action: assign local name to remote application
06905, 00000, "CMX: connect error"
// *Cause: remote partner not listening
// *Action: make sure remote node has CMX installed and running
// make sure oracmx is running on remote host
06906, 00000, "CMX: cannot get maximum packet size from CMX"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06907, 00000, "CMX: error during connect confirmation"
// *Cause: remote partner aborted
// *Action: contact your customer support representative
06908, 00000, "CMX: error during transfer of ORACLE_SID"
// *Cause: remote partner aborted
// *Action: contact your customer support representative
06909, 00000, "CMX: error during acknowledge of ORACLE_SID"
// *Cause: remote partner aborted
// *Action: contact your customer support representative
06910, 00000, "CMX: Cannot start oracle process on remote machine"
// *Cause: oracle process not found or wrong mode (should be 4751)
// *Action: change /etc/oratab or set mode to 4751
06911, 00000, "CMX: t_event returns ERROR"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06912, 00000, "CMX: write error in datarq"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06913, 00000, "CMX: error during redirection of connection"
// *Cause: oracmx has been stopped, or user process has been aborted
// *Action: contact your customer support representative
06914, 00000, "CMX: unexepected event during start of oracle"
// *Cause: connect sequence out of sync
// *Action: contact your customer support representative
06915, 00000, "CMX: unknown t_event in datarq"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06916, 00000, "CMX: error in data read (t_datain)"
// *Cause: remote partner aborted
// *Action: contact your customer support representative
06917, 00000, "CMX: error in data read (too many bytes read)"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06918, 00000, "CMX: T_NOEVENT during wait for read event"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06919, 00000, "CMX: error during write request (unknown event)"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06920, 00000, "CMX: getbrkmsg illegal datatype"
// *Cause: received packets are corrupted
// *Action: contact your customer support representative
06921, 00000, "CMX: getdatmsg illegal datatype"
// *Cause: received packets are corrupted
// *Action: contact your customer support representative
06922, 00000, "CMX: bad write length"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06923, 00000, "CMX: illegal break condition"
// *Cause: break handling out of sync
// *Action: contact your customer support representative
06924, 00000, "CMX: wrong break message length"
// *Cause: received packets are corrupted
// *Action: contact your customer support representative
06925, 00000, "CMX: disconnect during connect request"
// *Cause: partner is not responding
// *Action: make sure partner is up and running and reachable
06926, 00000, "CMX: T_ERROR during read data"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06927, 00000, "CMX: T_DATAIN received before all data written"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06928, 00000, "CMX: wrong ORACLE_SID"
// *Cause: ORACLE_SID is not entered in remote oratab
// *Action: add ORACLE_SID to remote oratab
06929, 00000, "CMX: error when sending ORACLE_SID"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06930, 00000, "CMX: error when checking ORACLE_SID"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06931, 00000, "CMX: error during read_properties for server"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06932, 00000, "CMX: error in local name"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
06933, 00000, "CMX: error during attach"
// *Cause: internal error in CMX
// *Action: contact your customer support representative
/
// 6950 - 6999 Reserved for SQL*Net Appletalk errors
/
06950, 00000, "No error"
// *Cause: SQL*Net AppleTalk error codes base. This is not an error.
// *Action: None.
06951, 00000, "Operating system call error"
// *Cause: AppleTalk API received error in VMS system service.
// *Action: Contact Oracle Customer Support representative.
06952, 00000, "Remote end of the communication issued a forward-reset packet. "
// *Cause: Peer program may have aborted
// *Action: Investigate network problems and try again.
06953, 00000, "Not enough virtual memory"
// *Cause: Not enough memory available.
// *Action: Check VMS process quotas and/or sysgen parameters
06954, 00000, "Illegal file name"
// *Cause: Erroneous file name
// *Action: Check path name for server output file, or SQL*Net Appletalk
// Logical names and symbols.
06955, 00000, "Number of database servers exceed limit"
// *Cause: Too many database connections.
// *Action: Check ATKSRV_MAXCONparameter in configuration file.
06956, 00000, "Failed to get local host name"
// *Cause: Unable to get Appletalk host name.
// *Action: Check Appletalk configuration.
06957, 00000, "No SID is currently available"
// *Cause: Incoming SQL*Net connection specified invalid SID name.
// *Action: Specify correct SID in connect string and retry.
06958, 00000, "Failed to access configuration file"
// *Cause: Unable to access CONFIG.ATK
// *Action: Check file protections.
06959, 00000, "Buffer I/O quota is too small"
// *Cause: Buffered I/O quota exceeded.
// *Action: Increase BIOlm using AUTHORIZE utility and retry.
06960, 00000, "Failed to access log file"
// *Cause: SQL*Net Appletalk listener could not create log file.
// *Action: Check directory path and protections.
06961, 00000, "Insufficient privilege for attempted operation"
// *Cause:
// *Action: Check process privileges and retry.
/
/ 6970 - 6989 X.25 Driver Errors
/
06970, 00000, "X.25 Driver: remote host is unknown"
// *Cause: Host name specified in the login (connect string) is unknown.
// *Action: Check spelling; make sure name is in the X.25 HOST file.
06971, 00000, "X.25 Driver: error while receiving data"
// *Cause:
// *Action:
06972, 00000, "X.25 Driver: error while sending data"
// *Cause:
// *Action:
06973, 00000, "X.25 Driver: invalid buffer size"
// *Cause: The buffer size specified in the login string must be between
// 5 and 4096.
// *Action: Re-submit with valid buffer size.
06974, 00000, "X.25 Driver: SID lookup failure"
// *Cause: From the remote host's SQL*Net X.25 server: the database SID,
// specified in the login (connect) string, was not recognized.
// *Action: Add the appropriate SID entry to the CONFIG.ORA file on
// the remote host (and restart the SQL*Net X.25 server).
06975, 00000, "X.25 Driver: connect to host failed"
// *Cause: Connection attempt to remote host has failed. Probably means
// that the SQL*Net X.25 server on the remote host is not up,
// or the host itself is not up.
// *Action: Start the SQL*Net X.25 server process on the remote host.
06976, 00000, "X.25 Driver: endpoint creation failure"
// *Cause: Process open file quota probably exceeded.
// *Action: Contact your customer support representative.
06977, 00000, "X.25 Driver: X.25 Level 2 failure"
// *Cause: X.25 level 2 is down. X.25 link is not working.
// *Action: Run system checks to verify functioning of X.25 software.
// Contact your hardware vendor.
06978, 00000, "X.25 Driver: Too many callback tries"
// *Cause: Call back address probably same as called address.
// *Action: Verify that callback address and called address are different.
06979, 00000, "X.25 Driver: server cannot start oracle"
// *Cause: The remote X.25 server was unable to start an ORACLE process on
// behalf of the client.
// *Action: Make sure permissions on the remote ORACLE program are correctly
// set. Contact your system administrator.
/
/ 7000-7099 Reserved for SQL*CONNECT/DB2 errors
/
/ 7100-7199 Reserved for SQL*CONNECT/IMS errors
/
/ 7200 - 7499 Reserved for UNIX OSD errors
/
07200, 00000, "slsid: oracle_sid not set."
// *Cause: The environment variable $(ORACLE_SID) is not set.
// *Action: Set ORACLE_SID environment variable.
07201, 00000, "slhom: oracle_home variable not set in environment."
// *Cause: $(ORACLE_HOME) environment variable not set.
// *Action: Set ORACLE_HOME.
07202, 00000, "sltln: invalid parameter to sltln."
// *Cause: The sltln name translation routine was called with invalid
// arguments. The input, or output stings were either NULL or 0 length.
// *Action: Probable internal oracle error. Contact customer support.
07203, 00000, "sltln: attempt to translate a long environment variable."
// *Cause: A string was passed to sltln containing a long environment
// variable. sltln accepts environment names of 30 or less characters.
// *Action: Shorten environment variable name to less than 30 characters.
07204, 00000, "sltln: name translation failed due to lack of output buffer space."
// *Cause: The sltln routine is given a maximum length buffer to expand
// the name into. An overflow of this buffer occurred.
// *Action: Possible internal error. Check output buffer length stored in
// sercose[0]. Pathnames are limited to 255 characters.
07205, 00000, "slgtd: time error, unable to obtain time."
// *Cause: Time() system call returned an error. Possible OS error.
// *Action: Check additional information returned. Contact customer support.
07206, 00000, "slgtd: gettimeofday error, unable to obtain time."
// *Cause: Gettimeofday() system call returned an error. Possible OS error.
// *Action: Check additional information returned. Contact customer support.
07207, 00000, "sigpidu: process ID string overflows internal buffer."
// *Cause: The sigpidu routine is given a maximum length buffer to hold
// process ID string. An overflow of this buffer occurred.
// *Action: Internal error. Contact customer support.
07208, 00000, "sfwfb: failed to flush dirty buffers to disk."
// *Cause: The fsync system call returned an error. Possible OS error.
// *Action: Check additional information returned. Contact customer support.
07209, 00000, "sfofi: file size limit was exceeded."
// *Cause: The size of the file to be opened exceeded the OS limit imposed
// on this process.
// *Action: Run osh to increase the file size limit.
07210, 00000, "slcpu: getrusage error, unable to get cpu time."
// *Cause: Getrusage system call returned an error. Possible OS error.
// *Action: Check additional information returned. Contact customer support.
07211, 00000, "slgcs: gettimeofday error, unable to get wall clock."
// *Cause: Gettimeofday system call returned an error. Possible OS error.
// *Action: Check additional information returned in OS reference manual.
// Contact customer support.
07212, 00000, "slcpu: times error, unable to get cpu time."
// *Cause: times system call returned an error. Possible OS error.
// *Action: Check additional information returned. Contact customer support.
07213, 00000, "slgcs: times error, unable to get wall clock."
// *Cause: times system call returned an error. Possible OS error.
// *Action: Check additional information returned in OS reference manual.
// Contact customer support.
07214, 00000, "slgunm: uname error, unable to get system information."
// *Cause: uname system call returned an error. Possible OS error.
// *Action: Check additional information returned in OS reference manual.
// Contact customer support.
07215, 00000, "slsget: getrusage error."
// *Cause: Getrusage system call returned an error. Possible OS error.
// *Action: Check additional information returned. Look for information in
// OS reference. Contact customer support.
07216, 00000, "slghst: gethostname error, unable to get name of current host."
// *Cause: gethostname system call returned an error. Possible OS error.
// *Action: Check additional information returned in OS reference manual.
// Contact customer support.
07217, 00000, "sltln: environment variable cannot be evaluated."
// *Cause: getenv call returned a null pointer.
// *Action: Set the environment variable and try again.
07218, 00000, "slkhst: could not perform host operation"
// *Cause: Unix system() call failed
// *Action: Examine system error message
07219, 00000, "slspool: unable to allocate spooler argument buffer."
// *Cause: Malloc failed to allocate space to hold spooler arguments.
// *Action: Check additional information returned in OS reference manual.
// The process may have run out of heap space. Contact customer
// support.
07220, 00000, "slspool: wait error."
// *Cause: Wait returned an error, when waiting for spool job to complete.
// Possible spooler program error.
// *Action: Check additional information returned. Refer to OS reference
// manual. Contact customer support.
07221, 00000, "slspool: exec error, unable to start spooler program."
// *Cause: Exec failed when starting line printer spooler command. Likely
// that either the default line printer command, or ORACLE_LPPROG,
// is incorrectly set.
// *Action: Verify default line printer command and ORACLE_LPPROG are set
// correctly. Set ORACLE_LPPROG to working line printer spooler.
07222, 00000, "slspool: line printer spooler command exited with an error."
// *Cause: The line printer spooler exited with a non-zero return value.
// This probably indicates an error in spooling file.
// *Action: Verify that line printer spooler is up. Verify that
// ORACLE_LPPROG, and ORACLE_LPARG are set properly. Check exit
// value returned as additional informatin.
07223, 00000, "slspool: fork error, unable to spawn spool process."
// *Cause: Fork system call failed to create additional process.
// Probable resource limit reached.
// *Action: Check additional information returned. Retry operation.
// Contact system administrator.
07224, 00000, "sfnfy: failed to obtain file size limit; errno = %s."
// *Cause: The ulimit system call returned an error.
// *Action: Check errno and contact customer support.
07225, 00000, "sldext: translation error, unable to expand file name."
// *Cause: Additional information returned is error returned from sltln.
// *Action: Check additional information.
07226, 00000, "rtneco: unable to get terminal mode."
// *Cause: The ioctl call returned an error. Possible OS error.
// *Action: Check additional information for errno. Contact customer support.
07227, 00000, "rtneco: unable to set noecho mode."
// *Cause: The ioctl call returned an error. Possible OS error.
// *Action: Check additional information for errno. Contact customer support.
07228, 00000, "rtecho: unable to restore terminal to echo mode."
// *Cause: The ioctl call returned an error. Possible OS error.
// *Action: Check additional information for errno. Contact customer support.
07229, 0000, "slcpuc: error in getting number of CPUs."
// *Cause: error in mpcntl system call
// *Action: check errno and contact system administrator
07230, 00000, "slemcr: fopen error, unable to open error file."
// *Cause: Fopen failed to open file.
// *Action: Try to determine which file was not opened. Check that file
// exists and is accessible.
07231, 00000, "slemcc: invalid file handle, seals do not match."
// *Cause: Function was called with an invalid argument. The file handle
// used was not obtained be slemcr.
// *Action: Internal error. Contact customer support.
07232, 00000, "slemcc: fclose error."
// *Cause: An error was encountered when closing the file. Possible OS error.
// *Action: Contact system administator.
07233, 00000, "slemcw: invalid file handle, seals do not match."
// *Cause: Function was called with an invalid file handle. File handle
// was not obtained by slemcr.
// *Action: Internal error. Contact customer support.
07234, 00000, "slemcw: fseek error."
// *Cause: Unable to seek to desired position in file. Possible OS error.
// Possible internal error.
// *Action: Verify that error message file is intact. Try to regenerate
// error message file. Contact customer support.
07235, 00000, "slemcw: fwrite error."
// *Cause: Unable to write item to file. Possible OS error.
// Possible permissions problem.
// *Action: Retry operation.
07236, 00000, "slemop: open error."
// *Cause: Unable to open error file. Possible permissions problem.
// *Action: Verify permission on error message file. Check additional
// information for errno.
07237, 00000, "slemcl: invalid file handle, seals do not match."
// *Cause: Function was called with an invalid file handle. Handle was not
// obtained by previous call to slemop.
// *Action: Internal error.
07238, 00000, "slemcl: close error."
// *Cause: Unable to close file. Possible OS error.
// *Action: Contact system administator. Check additional information
// for errno.
07239, 00000, "slemrd: invalid file handle, seals do not match."
// *Cause: Function was called with invalid file handle. Handle was not
// obtained by call to slemop.
// *Action: Internal error. Contact customer support.
07240, 00000, "slemrd: seek error."
// *Cause: Unable to seek to desired position in file. Possible OS error.
// *Action: Check that error file is still intact. Verify space on device.
// Contact system administrator. Check additional information for
// errno.
07241, 00000, "slemrd: read error."
// *Cause: Unable to read file. Possible OS error.
// *Action: Verify that error file is intact. Regenerate error message file.
// Contact customer support. Check additional information for errno.
07242, 00000, "slembfn: translation error, unable to translate error file name."
// *Cause: Additional information indicates error returned from sltln.
// *Action: Check additional information.
07243, 00000, "supplied buffer not big enough to hold entire line"
// *Cause: supplied buffer was not big enough
// *Action: Internal error. Contact customer support. Additional information
// indicates how big the supplied buffer was.
07244, 00000, "ssfccf: create file failed, file size limit reached."
// *Cause: An attempt was made to create a file that exceeds the process's file
// size limit.
// *Action: Run osh to raise the file size limit.
07245, 00000, "sfccf: unable to lseek and write the last block."
// *Cause: An attempt was made to move and write to a bad device address.
// *Action: Check errno. Possible lack of space on device.
07246, 00000, "sfofi: open error, unable to open database file."
// *Cause: sfofi returns an error.
// *Action: This is an oracle internal error.
07247, 00000, "skgfrfms, skgfrnms: read error, unable to read block from database file"
// *Cause: The ioctl() system call returned an error doing VOL_READ_MIRRORS.
// *Action: Check errno.
07248, 00000, "sfwfb: write error, unable to write database block."
// *Cause: sfwfb returns an error.
// *Action: This is an oracle internal error.
07249, 00000, "slsget: open error, unable to open /proc/pid."
// *Cause: The open() system call returned an error.
// *Action: Check that /proc has the right permissions.
07250, 00000, "spcre: semget error, unable to get first semaphore set."
// *Cause: An error occurred when trying to get first semaphore set.
// *Action: Check errno. Verify that system is configured to have semaphores.
// Verify that enough semaphores are available. Additional
// information indicates how many semaphores were requested.
07251, 00000, "spcre: semget error, could not allocate any semaphores."
// *Cause: Semget failed to even allocate a single semaphore. Either they are
// all in use or the system is not configured to have any semaphores.
// *Action: Check to see if all semaphores are in use. Check to see if
// system is configured to have semaphores. Check errno.
07252, 00000, "spcre: semget error, could not allocate semaphores."
// *Cause: Semget system call returned an error. Possible resource limit
// problem.
// *Action: Check errno. Verify that enough semaphores are available in system.
// If additional errors occur in destroying the semaphore sets then sercose[0]
// will be non-zero. If this occurs, remove the semaphore sets using ipcrm.
07253, 00000, "spdes: semctl error, unable to destroy semaphore set."
// *Cause: Semctl system call returned an error.
// *Action: Check semaphore sets. May require manual cleanup. Check additional
// information returned. Consult OS reference manual.
07254, 00000, "spdcr: translation error while expanding ?/bin/oracle."
// *Cause: An error occurred while translating the name of the oracle
// executable.
// *Action: Check sercose[0] for error returned from sltln. Perhaps
// $(ORACLE_HOME) is not set correctly.
07255, 00000, "spini: cannot set up signal handler."
// *Cause: System failed to set up signal handler.
// *Action: Check errno and sercose[0] for the signal number that failed.
07256, 00000, "sptrap: cannot set up signal handler to catch exceptions."
// *Cause: System failed to set up signal handler to catch exceptions.
// *Action: Check errno and sercose[0] for the signal number that failed.
07257, 00000, "spdcr: translation error expanding program name."
// *Cause: Error ocurred when expanding program name ora_PNAME_@. The result
// of this translation is put in argv[0] of oracle process.
// *Action: Check error returned by sltln returned in sercose[0].
07258, 00000, "spdcr: fork error, unable to create process."
// *Cause: An error occurred when creating a new process.
// *Action: Check errno. Perhaps a system limit on the number of processes
// has been exceeded.
07259, 00000, "spdcr: exec error, detached process failed in startup."
// *Cause: An oracle detached process died shortly after startup. Wait()
// indicated that a child process terminated.
// *Action: Check ?/dbs directory for trace or core files. Check errno.
07260, 00000, "spdcr: wait error."
// *Cause: Wait system call returned an error.
// *Action: Check errno.
07261, 00000, "spdde: kill error, unable to send signal to process."
// *Cause: Kill system call returned an error. Possibly an attempt to
// destroy an already gone process.
// *Action: Check errno.
07262, 00000, "sptpa: sptpa called with invalid process id."
// *Cause: This is an internal error.
// *Action: This is an oracle internal error.
07263, 00000, "sptpa: kill error."
// *Cause: Kill system call returned an error. Possible OS error.
// *Action: Check errno. Additional information indicates the process
// ID tested.
07264, 00000, "spwat: semop error, unable to decrement semaphore."
// *Cause: Semop system call returned an error. Semaphore set may not exist.
// *Action: Check errno. Semaphore ID is returned in sercose[0]. Verify
// semaphore set exists. A possible cause for this error is that a
// "shutdown abort" was done while this process was running.
07265, 00000, "sppst: semop error, unable to increment semaphore."
// *Cause: Semop system call returned an error. Semaphore set may not exist.
// *Action: Check errno. Semaphore ID is returned in sercose[0]. Check
// semaphore set existence. A possible cause for this error is that a
// "shutdown abort" was done while this process was running.
07266, 00000, "sppst: invalid process number passed to sppst."
// *Cause: Function was passed an invalid oracle process id.
// *Action: Internal error.
07267, 00000, "spwat: invalid process number."
// *Cause: Function was passed an invalid oracle process id.
// *Action: Internal error. Additional information indicates the invalid
// process id.
07268, 00000, "szguns: getpwuid error."
// *Cause: Getpwuid() could not find an entry in the passwd file for a
// user.
// *Action: Add an entry for the user in the passwd file.
07269, 00000, "spdcr: detached process died after exec."
// *Cause: Detached process succesfully execed, but died shortly thereafter.
// Additional information indicates exit code, and termination status.
// *Action: Check termination code for information as to why process exited.
// Check for core dump or trace file.
07270, 00000, "spalck: setitimer error, unable to set interval timer."
// *Cause: An error occurred while trying to set an interval timer.
// Probable porting problem.
// *Action: Check errno.
07271, 00000, "spwat: invalid oracle process number."
// *Cause: Function was called with an invalid oracle process number (0).
// *Action: Internal oracle error.
07272, 00000, "spwat: invalid semaphore set id."
// *Cause: Semaphore ID fetched from SGA was not initialized to valid
// value. Additional information returned is semaphore set index,
// and oracle process number.
// *Action: Oracle internal error. Check semaphore set index.
// Check oracle process number.
07273, 00000, "sppst: invalid semaphore id."
// *Cause: Semaphore ID fetched from SGA contained an invalid value.
// Additional information returned is semaphore set index, and
// oracle process number.
// *Action: Oracle internal error. Check semaphore set index. Check oracle
// process number.
07274, 00000, "spdcr: access error, access to oracle denied."
// *Cause: Unable to access "oracle" program. Verify ?/bin/oracle or
// $ORABCKPRG exist, and are executable.
// *Action: Check errno returned.
07275, 00000, "unable to send signal to process"
// *Cause: The kill system call returned an error. Possibly an attempt to
// signal a process which does not exist.
// *Action: Check errno.
07276, 00000, "no dba group in /etc/group."
// *Cause: A group has not been set up for dba users.
// *Action: Contact system administrator. Set up dba group in /etc/group.
07277, 00000, "spdde: illegal pid passed as argument."
// *Cause: A 0 pid was passed to spdde.
// *Action: Internal error. .
07278, 00000, "splon: ops$username exceeds buffer length."
// *Cause: Splon constructed an ops$username logon which exceeded the
// alloted buffer space.
// *Action: Use a shorter Unix username, or use an oracle username.
// Contact customer support.
07279, 00000, "spcre: semget error, unable to get first semaphore set."
// *Cause: An error occurred when trying to get first semaphore set.
// *Action: Check errno. Verify that system is configured to have semaphores.
// Verify that enough semaphores are available. Additional information
// indicates how many semaphores were requested.
07280, 00000, "slsget: unable to get process information."
// *Cause: The ioctl call returned an error. Possible OS error.
// *Action: Check additional information for errno. Contact customer support.
07281, 00000, "slsget: times error, unable to get cpu time."
// *Cause: times system call returned an error. Possible OS error.
// *Action: Check additional information returned. Contact customer support.
07282, 00000, "sksaprd: string overflow."
// *Cause: The internal buffer is not big enough to hold the archive control
// string.
// *Action: Internal restriction. Try a shorter archive control string.
07283, 00000, "sksaprd: invalid volume size for archive destination."
// *Cause: An invalid volume size was specified.
// *Action: Specify a valid volume size in archive control string.
07284, 00000, "sksaprd: volume size specification not terminated properly."
// *Cause: Some non-numeric text follows the volume size specification.
// *Action: Enter a correct archive control string.
07285, 00000, "sksaprd: volume size should not be specified for a disk file."
// *Cause: Volume size was specified for a disk file.
// *Action: If you are archiving to a disk file, do not specify its volume size.
07286, 00000, "sksagdi: cannot obtain device information."
// *Cause: Stat on the log archiving device failed.
// *Action: Check the returned OSD error for the reason of failure.
07287, 00000, "sksagdi: unsupported device for log archiving."
// *Cause: Log archiving to this device is unsupported.
// *Action: Try log archiving to a supported device.
07290, 00000, "sksagdi: specified directory for archiving does not exist."
// *Cause: The specified pathname is not a directory.
// *Action: Verify that the archive destination directory exists.
07303, 00000, "ksmcsg: illegal database buffer size."
// *Cause: The database buffer size must be a multiple of the database block
// size, and less than the maximum block size.
// *Action: Verify that the db_block_size parameter is correct in INIT.ORA.
07304, 00000, "ksmcsg: illegal redo buffer size."
// *Cause: The redo buffer size must be a multiple of machine block size.
// *Action: Verify that the log_buffer INIT.ORA parameter is correctly set.
07324, 00000, "smpall: malloc error while allocating pga."
// *Cause: Malloc library routine returned an error.
// *Action: Check errno. Possibly out of swap space.
07327, 00000, "smpdal: attempt to destroy pga when it was not mapped."
// *Cause: Smpdal was called when the PGA had not been previously created.
// *Action: Internal error.
07339, 00000, "spcre: maximum number of semaphore sets exceeded."
// *Cause: The internal buffer is not big enough to hold the number of
// semaphore set identifiers requested.
// *Action: Reconfigure OS to have more semaphores per set.
07345, 00000, "The datafile name must not contain the string '..'."
// *Cause: The specified datafile name contains '..'.
// *Action: Correct the datafile name and retry the operation.
07346, 00000, "slnrm: normalized file name is too long"
// *Cause: After normalizing the specified file name, the resulting file name
// was too long.
// *Action: Specify the shorter file name and retry the operation.
07390, 00000, "sftopn: translate error, unable to translate file name."
// *Cause: An error occurred while expanding the file name to open. Additional
// information returns error generated in translation routine.
// *Action: Lookup additional error code for further information.
07391, 00000, "sftopn: fopen error, unable to open text file."
// *Cause: Fopen library routine returned an error.
// *Action: Verify existence and permissions.
07392, 00000, "sftcls: fclose error, unable to close text file."
// *Cause: Fclose library routine returned an error.
// *Action: Possible internal oracle error.
07393, 00000, "unable to delete text file"
// *Cause: An error occurred while deleting a text file.
// *Action: Verify that the file exists and check additional errors.
07394, 00000, "unable to append string to text file"
// *Cause: An error occurred while performing a string put operation.
// *Action: This is an internal error. Check additional information.
07400, 00000, "slemtr: translated name for the message file is too long."
// *Cause: The name for the message file overflows internal buffer.
// *Action: Try making the complete path-name of the message file shorter
// by reorganizing the directory hierarchy.
07401, 00000, "sptrap: cannot restore user exception handlers."
// *Cause: The system failed to restore user exception handlers.
// *Action: Check errno and sercose[0] for the signal number that failed.
07402, 00000, "sprst: cannot restore user signal handler."
// *Cause: The system failed to restore user signal handlers.
// *Action: Check errno and sercose[0] for the signal number that failed.
07403, 00000, "sfanfy: db_writers parameter not valid."
// *Cause: The db_writers parameter in INIT.ORA exceeds the
// system-dependent maximum or is less than 0.
// *Action: Change the db_writers parameter in INIT.ORA.
07404, 00000, "sfareq: Timeout occurred waiting for request to complete."
// *Cause: The master database writer timed out waiting for a write or
// close to complete. One of the database writers may have
// stopped running.
// *Action: Check all database writer trace files. Shut down the
// database and try to warm start.
07405, 00000, "sptrap: cannot setup alternate signal stack."
// *Cause: The system failed to setup an alternate signal stack.
// *Action: Check errno and sercose[0] for the location where it failed.
07406, 00000, "slbtpd: invalid number."
// *Cause: An impossible request for binary to decimal conversion was made.
// *Action: This conversion cannot be performed.
07407, 00000, "slbtpd: invalid exponent."
// *Cause: An impossible request for binary to decimal conversion was made
// *Action: This conversion cannot be performed.
07408, 00000, "slbtpd: overflow while converting to packed decimal."
// *Cause: An impossible request for binary to decimal conversion was made.
// *Action: This conversion cannot be performed.
07409, 00000, "slpdtb: invalid packed decimal nibble."
// *Cause: An impossible request for decimal to binary conversion was made.
// *Action: This conversion cannot be performed.
07410, 00000, "slpdtb: number too large for supplied buffer."
// *Cause: An impossible request for decimal to binary conversion was made.
// *Action: This conversion cannot be performed.
07411, 00000, "slgfn: full path name too big for supplied buffer."
// *Cause: The supplied buffer is not big enough to hold the full path name.
// *Action: The construction of the full path name cannot be performed.
07412, 00000, "sfaslv: Error getting entry in asynchronous write array."
// *Cause: One of the database writer processes could not locate its
// entry in the SGA.
// *Action: Contact customer support.
07415, 00000, "slpath: allocation of memory buffer failed."
// *Cause: Malloc() failed to allocate buffer for storing ORACLE_PATH.
// *Action: System has run out of heap space. Additional information
// indicates errno.
07416, 00000, "slpath: pathname construction failed; lack of output buffer space."
// *Cause: The slpath routine is given a maximum length buffer to expand
// the name into. An overflow of this buffer occurred.
// *Action: Possible internal error. Check output buffer length stored in
// sercose[0] and constructed pathname length in sercose[1].
07417, 00000, "sfareq: One or more database writers not active."
// *Cause: One or more of the database writer processes is no longer
// running.
// *Action: Check the trace files for the database writers. Shut down
// the database and try to warm start.
07418, 00000, "sfareq: Database writer got error in timing function."
// *Cause: An error occurred when the database writer called the system
// timing function.
// *Action: Check the database writer trace file. Shut down database and
// try to warm start.
07419, 00000, "sfareq: Database writer got error in timing function."
// *Cause: An error occurred when the database writer called the system
// timing function.
// *Action: Check the database writer trace file. Shut down database and
// try to warm start.
07425, 00000, "sdpri: error %s in translating dump file location."
// *Cause: An oracle error occurred when translating the location of the
// dump file.
// *Action: Check the oracle error code.
07426, 00000, "spstp: cannot obtain the location of dbs directory."
// *Cause: An oracle error occurred when translating the location of the
// dbs directory.
// *Action: Check additional information for the error returned from sltln.
07427, 00000, "spstp: cannot change directory to dbs."
// *Cause: Chdir system call returned an error. Possible permission problems.
// *Action: Check additional information for the OS error code.
07431, 00000, "fork failed"
// *Cause: The server process was unable to fork a child process.
// *Action: Verify that there are enough system resources to support another
// process. The user or system process limit may have been
// exceeded, or the amount of free memory or swap space may be
// temporarily insufficient.
07432, 00000, "unable to perform nested sleep"
// *Cause: An attempt was made to make a process sleep when it was
// already sleeping. This platform does not support this capability.
// *Action: Try the SLEEP command when the process is not sleeping.
07440, 00000, "WMON process terminated with error"
// *Cause: The wakeup monitor process died.
// *Action: Warm start instance.
07441, 00000, "function address must be aligned on %s byte boundary"
// *Cause: An improperly aligned function address was specified.
// *Action: Use a properly aligned function address.
07442, 00000, "function address must be in the range %s to %s"
// *Cause: An invalid function address was specified.
// *Action: Use a valid function address.
07443, 00000, "function %s not found"
// *Cause: A nonexistent or an invalid function name was specified.
// *Action: Use a valid function name.
07444, 00000, "function address %s is not readable"
// *Cause: An invalid function name/address was specified.
// *Action: Use a valid function name/address.
07445, 00000, "exception encountered: core dump [%s] [%s] [%s] [%s] [%s] [%s]"
// *Cause: An operating system exception occurred which should result in the
// creation of a core file. This is an internal error.
// *Action: Visit My Oracle Support to access the ORA-07445 Lookup tool
// (reference Note 7445.1) for more information regarding the specific
// ORA-07445 error encountered.
//
// An Incident has been created for this error in the Automatic
// Diagnostic Repository (ADR). When logging a service request, use
// the Incident Packaging Service (IPS) from the Support Workbench
// or the ADR Command Interpreter (ADRCI) to automatically package the
// relevant trace information (reference My Oracle Support Note 411.1).
//
// The following information should also be gathered to help determine
// the root cause:
// - changes leading up to the error
// - events or unusual circumstances leading up to the error
// - operations attempted prior to the error
// - conditions of the operating system and databases at the time
// of the error
//
// Note: The cause of this message may manifest itself as different
// errors at different times. Be aware of the history of errors that
// occurred before this internal error.
07446, 00000, "sdnfy: bad value '%s' for parameter %s."
// *Cause: The directory specified as the value for the stated parameter could
// not be used.
// *Action: Make sure the directory you have specified is a valid
// directory/file specification.
07447, 00000, "ssarena: usinit failed."
// *Cause: Oracle failed to create a shared arena file.
// *Action: Use sercerrno field to determine cause of failure.
07448, 00000, "ssarena: maximum number of shared arenas exceeded."
// *Cause: Oracle attempted to create more shared arena files than permitted.
// *Action: Raise the value for max_arena in INIT.ORA.
07449, 00000, "sc: usnewlock failed."
// *Cause: Oracle failed to acquire a shared arena lock.
// *Action: Check result code in sercerrno to determine the cause of failure.
07451, 00000, "slskstat: unable to obtain load information."
// *Cause: kstat library returned an error. Possible OS failure
// *Action: Check result code in sercose[0] for more information.
07452, 00000, "specified resource manager plan does not exist in the data dictionary"
// *Cause: User tried to load a resource manager plan that does not exist.
// *Action: Use a resource manager plan that exists in the data dictionary.
07453, 00000, "requested resource manager plan schema does not contain OTHER_GROUPS"
// *Cause: User tried to load a resource manager plan schema that does not
// contain the OTHER_GROUPS group.
// *Action: Use a resource manager plan schema that contains the
// OTHER_GROUPS group.
07454, 00000, "queue timeout, %s second(s), exceeded"
// *Cause: User session queued for longer than maximum specified queue
// queue duration time for consumer group.
// *Action: Re-submit job at a later time or increase queue timeout.
07455, 00000, "estimated execution time (%s secs), exceeds limit (%s secs)"
// *Cause: User attempted to execute an operation whose estimated
// execution time exceeds the limit specified for the
// consumer group.
// *Action: Execute job on behalf of another group, or increase limit.
07456, 00000, "cannot set RESOURCE_MANAGER_PLAN when database is closed"
// *Cause: An attempt was made to turn on the Resource Manager when the
// database was closed.
// *Action: Open the database and try again.
07457, 00000, "cannot set _INTERNAL_RESOURCE_MANAGER_PLAN because of FORCE"
// *Cause: An attempt was made to set the _INTERNAL_RESOURCE_MANAGER_PLAN
// parameter, however this failed because the current
// RESOURCE_MANAGER_PLAN has the FORCE prefix.
// *Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter.
07458, 00000, "cannot set the RESOURCE_MANAGER_PLAN parameter"
// *Cause: An attempt was made to set the RESOURCE_MANAGER_PLAN
// parameter, however, this failed because the database was
// quiesced.
// *Action: Unquiesce the database.
07459, 00000, "cannot restore the RESOURCE_MANAGER_PLAN parameter"
// *Cause: An attempt was made to internally restore the RESOURCE_MANAGER_PLAN
// parameter to the value before it was internally set. This
// failed because the current plan was set by the user and therefore
// did not need to be restored.
// *Action: No action needed.
07460, 00000, "cannot set the RESOURCE_MANAGER_PLAN parameter"
// *Cause: An attempt was made to internally set the RESOURCE_MANAGER_PLAN
// parameter, however, this failed because the current
// RESOURCE_MANAGER_PLAN has the FORCE prefix.
// *Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter.
07468, 00000, "spwat: mset error, unable to set semaphore."
// *Cause: The mset routine returned an error. Semaphore may not exist.
// *Action: Check result code in sercerrno. Semaphore number returned
// in sercose[0].
07469, 00000, "sppst: mclear error, unable to clear semaphore."
// *Cause: The mclear routine returned an error. Semaphore may not exist.
// *Action: Check result code in sercerrno. Semaphore number returned
// in sercose[0].
07470, 00000, "snclget: cannot get cluster number."
// *Cause: The cluster_status system call failed to get status information
// for the current cluster.
// *Action: Check result code in sercose[0]. Possible operating system
// failure.
07471, 00000, "snclrd: name translation error of sgadef.dbf file name."
// *Cause: Unable to expand out ?/dbs/sgadef@.dbf file name.
// *Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are properly set.
// Check error number returned from sltln in sercose[0].
07472, 00000, "snclrd: open error when opening sgadef.dbf file."
// *Cause: open failed when opening the file ?/dbs/sgadef@.dbf
// *Action: Check errno. Possible permission problem. Verify that the
// file ?/dbs/sgadef@.dbf exists.
07473, 00000, "snclrd: read error when trying to read sgadef.dbf file."
// *Cause: Read had an error when reading sgadef.dbf file.
// *Action: Check errno. Verify file exists, and is correct size.
07474, 00000, "snclrd: close error, unable to close sgadef.dbf file."
// *Cause: An error occurred in close, while closing the file
// "?/dbs/sgadef@.dbf"
// *Action: Check errno. Possible operating system error.
07475, 00000, "slsget: cannot get vm statistics."
// *Cause: The vm_statistics system call failed to get virtual memory
// statistics.
// *Action: Check result code in sercerrno. Possible operating system
// failure.
07476, 00000, "slsget: cannot get mapped memory statistics."
// *Cause: The vm_mapmem system call failed to get mapped memory
// statistics.
// *Action: Check result code in sercerrno. Possible operating system
// failure.
07477, 00000, "scgcmn: lock manager not initialized."
// *Cause: Lock manager must be initialized before converting locks.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07478, 00000, "scgcmn: cannot get lock status."
// *Cause: lm_stat_lock failed.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07479, 00000, "scgcmn: cannot open or convert lock."
// *Cause: lm_open or lm_open_convert failed.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07480, 00000, "snchmod: cannot change permissions on ?/dbs/sgalm.dbf."
// *Cause: When creating an instance, snlmini could not change the
// permissions on ?/dbs/sgalm.dbf
// *Action: Contact your customer support representative.
07481, 00000, "snlmatt: cannot attach to lock manager instance."
// *Cause: lm_attach failed to attach to lock manager instance.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07482, 00000, "snlmini: cannot create lock manager instance."
// *Cause: lm_create failed to create lock manager instance.
// *Action: Check permissions on ?/dbs, and remove ?/dbs/sgalm.dbf if
// it exists, then retry.
07483, 00000, "snlkget: cannot convert(get) lock."
// *Cause: lm_convert failed to convert(get) lock.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07484, 00000, "snlkput: cannot convert(put) lock."
// *Cause: lm_convert failed to put lock value.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07485, 00000, "scg_get_inst: cannot open instance number lock."
// *Cause: lm_open failed.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07486, 00000, "scg_get_inst: cannot convert(get) instance number lock."
// *Cause: lm_convert failed to get lock value.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07487, 00000, "scg_init_lm: cannot create lock manager instance."
// *Cause: lm_create failed.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07488, 00000, "scgrcl: lock manager not initialized."
// *Cause: Lock manager must be initialized before releasing locks.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07489, 00000, "scgrcl: cannot get lock status."
// *Cause: lm_stat_lock failed during lock release/cancel.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07490, 00000, "scgrcl: cannot convert lock."
// *Cause: lm_convert failed during lock release/cancel.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07491, 00000, "scgrcl: cannot cancel lock request."
// *Cause: lm_cancel failed during lock release/cancel.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07492, 00000, "scgrcl: cannot close lock."
// *Cause: lm_close failed during lock release/cancel.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07493, 00000, "scgrcl: lock manager error."
// *Cause: An error was encountered releasing the lock.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07494, 00000, "scgcm: unexpected error."
// *Cause: Unknown or unexpected error code.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07495, 00000, "spwat: lm_wait failed."
// *Cause: lm_wait failed.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07496, 00000, "sppst: lm_post failed."
// *Cause: lm_post failed.
// *Action: Check result code in sercerrno. Possible lock manager failure.
07497, 00000, "sdpri: cannot create trace file '%s'; errno = %s."
// *Cause: 1. The trace file could not be created for writing.
// 2. The trace file is a symbolic link.
// *Action: 1. Check if the dump directory exists and whether it is writable.
// 2. Remove the symbolic link.
07498, 00000, "spstp: Unable to open /dev/resched."
// *Cause: The rescheduling driver /dev/resched is not found or is
// not working properly.
// *Action: Check installation of the ORACLE rescheduling driver
// in the AIX kernel.
07499, 00000, "spglk: Cannot reschedule."
// *Cause: The rescheduling driver /dev/resched is not open.
// This is an internal error and should not occur.
// *Action: Contact your customer support representative.
/
/ 7500-7999 VMS OSD ERRORS
/
07500, 00000, "scglaa: $cantim unexpected return"
// *Cause: VMS system service $CANTIM returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07501, 00000, "scgtoa: $deq unexpected return"
// *Cause: VMS system service $DEQ returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07502, 00000, "scgcmn: $enq unexpected return"
// *Cause: VMS system service $ENQ returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07503, 00000, "scgcmn: $setimr unexpected return"
// *Cause: VMS system service $SETIMR returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07504, 00000, "scgcmn: $hiber unexpected return"
// *Cause: VMS system service $HIBER returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07505, 00000, "scggt: $enq parent lock unexpected return"
// *Cause: VMS system service $ENQ returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07506, 00000, "scgrl: $deq unexpected return on lockid %s"
// *Cause: VMS system service $DEQ returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07507, 00000, "scgcm: unexpected lock status condition"
// *Cause: A global locking system service returned an unexpected value.
// *Action: Check for system error message (if any) and refer to
// VMS documentation, or contact your customer support
// representative.
07508, 00000, "scgfal: $deq all unexpected return"
// *Cause: VMS system service $DEQ returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07509, 00000, "scgfal: $deq parent lock unexpected return"
// *Cause: VMS system service $DEQ returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07510, 00000, "scgbrm: $getlki unexpected return on lockid %s"
// *Cause: VMS system service $GETLKI returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07511, 00000, "sscggtl: $enq unexpected return for master termination lock"
// *Cause: VMS system service $ENQ returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07512, 00000, "sscggtl: $enq unexpected return for client termination lock"
// *Cause: VMS system service $ENQ returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07513, 00000, "sscgctl: $deq unexpected return on cancel of term. lock"
// *Cause: VMS system service $DEQ returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07514, 00000, "scgcan: $deq unexpected return while canceling lock"
// *Cause: VMS system service $DEQ returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
/
07534, 00000, "scginq: $getlki unexpected return on lockid %s"
// *Cause: VMS system service $GETLKI returned an unexpected value
// *Action: Check for system error message and refer to VMS documentation
07548, 00000, "sftopn: Maximum number of files already open"
// *Cause: Too many test files open
// *Action: This is an internal error, please report to Oracle
07549, 00000, "sftopn: $OPEN failure"
// *Cause: VMS system service $OPEN failed
// *Action: Examine system error message and refer to VMS documentation
07550, 00000, "sftopn: $CONNECT failure"
// *Cause: VMS system service $OPEN failed
// *Action: Examine system error message and refer to VMS documentation
07551, 00000, "sftcls: $CLOSE failure"
// *Cause: VMS system service $CLOSE failed
// *Action: Examine system error message and refer to VMS documentation
07552, 00000, "sftget: $GET failure"
// *Cause: VMS system service $GET failed
// *Action: Examine system error message and refer to VMS documentation
07561, 00000, "szprv: $IDTOASC failure"
// *Cause: VMS system service $IDTOASC failed
// *Action: Examine system error message and refer to VMS documentation
07562, 00000, "sldext: extension must be 3 characters"
// *Cause: An extension was found but it is of improper length
// *Action: This is an internal error, please report to Oracle
07563, 00000, "sldext: $PARSE failure"
// *Cause: VMS system service $PARSE failed
// *Action: Examine system error message and refer to VMS documentation
07564, 00000, "sldext: wildcard in filename or extension"
// *Cause: A wildcard was used in the file name
// *Action: Reenter the file name completely
07565, 00000, "sldext: $SEARCH failure"
// *Cause: VMS system service $SEARCH failed
// *Action: Examine system error message and refer to VMS documentation
07568, 00000, "slspool: $OPEN failure"
// *Cause: VMS system service $OPEN failed
// *Action: Examine system error message and refer to VMS documentation
07569, 00000, "slspool: $CLOSE failure"
// *Cause: VMS system service $CLOSE failed
// *Action: Examine system error message and refer to VMS documentation
07570, 00000, "szrfc: $IDTOASC failure"
// *Cause: VMS system service $IDTOASC failed
// *Action: Examine system error message and refer to VMS documentation
07571, 00000, "szrfc: $FIND_HELD failure"
// *Cause: VMS system service $FIND_HELD failed
// *Action: Examine system error message and refer to VMS documentation
07572, 00000, "szrfc: insufficient rolename buffer space"
// *Cause: An OS role name was too long.
// *Action: Re-define the role name to be of correct length.
07573, 00000, "slkhst: could not perform host operation"
// *Cause: VMS system service LIB$SPAWN failed
// *Action: Examine system error message and refer to VMS documentation
07574, 00000, "szrfc: $GETUAI failure"
// *Cause: VMS system service $GETUAI failed
// *Action: Examine system error message and refer to VMS documentation
07576, 00000, "sspexst: $GETJPIW failure on process ID %s"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07577, 00000, "no such user in authorization file"
// *Cause: An attempt was made to set an INTERNAL password (for either DBA
// or OPER privilege), but the corresponding VMS account (either
// ORA_<sid>_DBA or ORA_<sid>_OPER) hasn't been created yet.
// *Action: Add a VMS account for ORA_<sid>_DBA and/or ORA_<sid>_OPER before
// trying to set a password for them.
07578, 00000, "szprv: $FIND_HELD failure"
// *Cause: VMS system service $FIND_HELD failed
// *Action: Examine system error message and refer to VMS documentation
07579, 00000, "spini: $DCLEXH failure"
// *Cause: VMS system service $PARSE failed
// *Action: Examine system error message and refer to VMS documentation
07580, 00000, "spstp: $GETJPIW failure"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07581, 00000, "spstp: cannot derive SID from unexpected process name"
// *Cause: A background process did not have name of correct form
// *Action: If the job name was changed, restore it, otherwise this is
// an internal error, please report to Oracle.
07582, 00000, "spstp: ORA_SID has illegal value"
// *Cause: The ORA_SID must exist and be less than 6 characters
// *Action: Consult the VMS Installation guide for information on setting
// the SID.
07584, 00000, "spdcr: invalid value for ORA_sid_(proc_)PQL$_item"
// *Cause: A logical name used to set a detached process quota value
// has an invalid value (probably non-numeric).
// *Action: Examine the values of these logical names, correct the one
// in error, and retry.
07585, 00000, "spdcr: $PARSE failure"
// *Cause: VMS system service $PARSE failed
// *Action: Examine system error message and refer to VMS documentation
07586, 00000, "spdcr: $SEARCH failure"
// *Cause: VMS system service $SEARCH failed
// *Action: Examine system error message and refer to VMS documentation
07587, 00000, "spdcr: $CREPRC failure"
// *Cause: VMS system service $CREPRC failed
// *Action: Examine system error message and refer to VMS documentation
07588, 00000, "spdcr: $GETJPIW get image name failure"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07589, 00000, "spdde: system ID not set"
// *Cause: The logical name ORA_SID doesn't translate to a valid value.
// *Action: Check the value of ORA_SID in the process that gets the
// error, and correct the installation or command procedures
// that caused ORA_SID to be set incorrectly.
07590, 00000, "spdde: $DELPRC failure"
// *Cause: VMS system service $DELPRC failed
// *Action: Examine system error message and refer to VMS documentation
07591, 00000, "spdde: $GETJPIW failure"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07592, 00000, "sspgprv: Error obtaining required privileges"
// *Cause: While obtaining needed privileges, an error was returned from
// SYS$SETPRV.
// *Action: This is an internal error. Please report to Oracle
07593, 00000, "ssprprv: Error release privileges"
// *Cause: While releasing privileges, an error was returned from SYS$SETPRV.
// *Action: This is an internal error. Please report to Oracle
07594, 00000, "spiip: $GETJPIW failure"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07595, 00000, "sppid: $GETJPIW failure"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07596, 00000, "sptpa: $GETJPIW failure"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07597, 00000, "spguns: $GETJPIW failure"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07598, 00000, "spwat: $SETIMR failure"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07599, 00000, "spwat: $SCHDWK failure"
// *Cause: VMS system service $SCHDWK failed
// *Action: Examine system error message and refer to VMS documentation
07600, 00000, "slkmnm: $GETSYIW failure"
// *Cause: VMS system service $GETSYIW failed
// *Action: Examine system error message and refer to VMS documentation
07601, 00000, "spguno: $GETJPIW failure"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07602, 00000, "spgto: $GETJPIW failure"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07605, 00000, "szprv: $ASCTOID failure"
// *Cause: VMS system service $ASCTOID failed
// *Action: Examine system error message and refer to VMS documentation
07606, 00000, "szprv: $CHKPRO failure"
// *Cause: VMS system service $CHKPRO failed
// *Action: Examine system error message and refer to VMS documentation
07607, 00000, "szaud: $SNDOPR failure"
// *Cause: VMS system service $SNDOPR failed
// *Action: Examine system error message and refer to VMS documentation
07608, 00000, "szprv: $GETUAI failure"
// *Cause: VMS system service $GETUAI failed
// *Action: Examine system error message and refer to VMS documentation
07609, 00000, "szprv: $HASH_PASSWORD failure"
// *Cause: VMS system service $HASH_PASSWORD failed
// *Action: Examine system error message and refer to VMS documentation
07610, 00000, "$GETJPIW failed in retrieving the user's MAC priviledges"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07612, 00000, "$GETUAI failed in retrieving the user's clearance level"
// *Cause: VMS system service $GETUAI failed
// *Action: Examine system error message and refer to VMS documentation
07613, 00000, "$GETJPIW failed in retrieving the user's process label"
// *Cause: VMS system service $GETJPIW failed
// *Action: Examine system error message and refer to VMS documentation
07614, 00000, "$CHANGE_CLASS failed in retrieving the user's process label"
// *Cause: VMS system service $CHANGE_CLASS failed
// *Action: Examine system error message and refer to SEVMS documentation
07615, 00000, "$CHANGE_CLASS failed in retrieving the specified file label"
// *Cause: VMS system service $CHANGE_CLASSS failed
// *Action: Examine system error message and refer to SEVMS documentation
07616, 00000, "$CHANGE_CLASS failed in retrieving the specified device label"
// *Cause: VMS system service $CHANGE_CLASS failed
// *Action: Examine system error message and refer to SEVMS documentation
07617, 00000, "$FORMAT_CLASS failed translating the binary label to a string"
// *Cause: VMS system service $FORMAT_CLASS failed because the given binary
// classification was not valid.
// *Action: Examine system error message and refer to SEVMS documentation
07618, 00000, "$IDTOASC failed translating a secrecy level"
// *Cause: VMS system service $IDTOASC failed while looking up the string
// representation in the rights database of a secrecy level.
// *Action: Define the entry in the rights database which the binary label
// you specified references.
07619, 00000, "$IDTOASC failed translating an integrity level"
// *Cause: VMS system service $IDTOASC failed while looking up the string
// representation in the rights database of an integrity level.
// *Action: Define the entry in the rights database which the binary label
// you specified references.
07620, 00000, "smscre: illegal database block size"
// *Cause: An illegal database block size was specified in the parameter file.
// It must be positive, a multiple of 512, and less than the maximum
// physical i/o data size.
// *Action: Change db_block_size in the parameter file to conform to these
// limits.
07621, 00000, "smscre: illegal redo block size"
// *Cause: An illegal redo log buffer size was specified in the parameter file.
// It must be positive and a multiple of 512.
// *Action: Change log_buffer in the parameter file to conform to these limits.
07622, 00000, "smscre: $CREATE failure"
// *Cause: While creating the system global area (SGA) backing file, VMS
// system service $CREATE failed.
// *Action: Examine the system error message and refer to VMS documentation.
07623, 00000, "smscre: $CRMPSC failure"
// *Cause: While creating the system global area (SGA), VMS system service
// $CRMPSC failed.
// *Action: Examine the system error message and refer to VMS documentation.
07624, 00000, "smsdes: $DGBLSC failure"
// *Cause: While deleting the system global area (SGA), VMS system service
// $DGBLSC failed.
// *Action: Examine the system error message and refer to VMS documentation.
07625, 00000, "smsget: $MGBLSC failure"
// *Cause: While mapping the system global area (SGA) during logon, VMS
// system service $MGBLSC failed. The usual reason is that Oracle
// has not been started up.
// *Action: Examine the system error message and refer to VMS documentation.
// Start up Oracle if it is not already started.
07626, 00000, "smsget: sga already mapped"
// *Cause: An attempt to map the SGA during logon failed because it was
// already mapped. This is an internal error.
// *Action: Exit your program and try again, and report this to your
// customer support representative.
07627, 00000, "smsfre: $CRETVA failure"
// *Cause: While unmapping the system global area (SGA) during logoff, VMS
// system service $CRETVA failed.
// *Action: Examine the system error message and refer to VMS documentation.
07628, 00000, "smsfre: sga not mapped"
// *Cause: An attempt to unmap the SGA during logoff failed because it was
// not mapped. This is an internal error.
// *Action: Exit your program and try again, and report this to your
// customer support representative.
07629, 00000, "smpall: $EXPREG failure"
// *Cause: While extending the program global area (PGA), VMS
// system service $EXPREG failed. This often happens when the virtual
// memory page count quota is exceeded.
// *Action: Examine the system error message and refer to VMS documentation.
07630, 00000, "smpdal: $DELTVA failure"
// *Cause: While deleting the program global area (PGA) during logoff, VMS
// system service $DELTVA failed.
// *Action: Examine the system error message and refer to VMS documentation.
07631, 00000, "smcacx: $EXPREG failure"
// *Cause: While creating or extending a context area, VMS system service
// $EXPREG failed. This often happens when the virtual memory page
// count quota is exceeded.
// *Action: Examine the system error message and refer to VMS documentation.
07632, 00000, "smsrcx: $DELTVA failure"
// *Cause: While deleting a context area, VMS system service $DELTVA failed.
// *Action: Examine the system error message and refer to VMS documentation.
07633, 00000, "smsdbp: illegal protection value"
// *Cause: The buffer debug function was called with an illegal value.
// This is an internal error.
// *Action: Contact your customer support representative.
07634, 00000, "smsdbp: $CRETVA failure"
// *Cause: While attempting to set protection in the database buffer
// debug mechanism, VMS system service $CRETVA failed.
// *Action: Contact your customer support representative.
07635, 00000, "smsdbp: $SETPRT failure"
// *Cause: While attempting to set protection in the database buffer
// debug mechanism, VMS system service $SETPRT failed.
// *Action: Contact your customer support representative.
07636, 00000, "smsdbp: $MGBLSC failure"
// *Cause: While attempting to set protection in the database buffer
// debug mechanism, VMS system service $MGBLSC failed.
// *Action: Contact your customer support representative.
07637, 00000, "smsdbp: buffer protect option not specified when sga created"
// *Cause: Trying to change the buffer protect mode when the SGA was not
// created with buffer protect debug option. This is an internal error.
// *Action: Contact your customer support representative.
07638, 00000, "smsget: SGA pad area not large enough for created SGA"
// *Cause: An attempt was made to map an SGA with software in which
// the SGA pad area isn't large enough.
// *Action: Create a smaller SGA, or relink the software with a larger pad.
07639, 00000, "smscre: SGA pad area not large enough (%s bytes required)"
// *Cause: An attempt was made to create an SGA with software in which
// the SGA pad area isn't large enough.
// *Action: Create a smaller SGA, or relink the software with a larger pad.
07640, 00000, "smsget: SGA not yet valid. Initialization in progress"
// *Cause: An attempt was made to map to the SGA while it was being
// initialized.
// *Action: Wait until initialization is complete, and try again.
07641, 00000, "smscre: Unable to use the system pagefile for the SGA"
// *Cause: The system global area (SGA) backing file could not be allocated
// using the system pagefile because the system-wide limit on
// global pages has been exceeded.
// *Action: Either increase the VMS system parameter GBLPAGFIL or use a disk
// file as the SGA backing file.
07642, 00000, "smprtset: $CMKRNL failure"
// *Cause: While attempting to set the protection of a region of memory,
// an error was returned from the $CMKRNL system service.
// *Action: Examine the system error message and refer to VMS documentation.
07643, 00000, "smsalo: SMSVAR is invalid"
// *Cause: an internal error
// *Action: Report this error to Oracle Support Services, provide your
// INIT.ORA file.
07645, 00000, "sszfsl: $CHANGE_CLASS failure"
// *Cause: While attempting to set the label on a file, SEVMS service
// $CHANGE_CLASS failed.
// *Action: Examine the system message and refer to SEVMS system documentation.
07646, 00000, "sszfck: $CREATE failure"
// *Cause: While attempting to create a file, VMS system service $CREATE
// failed.
// *Action: Examine the system message and refer to VMS system documentation.
07647, 00000, "sszfck: $OPEN failure"
// *Cause: While attempting to reopen a file, VMS system service $OPEN failed.
// *Action: Examine the system message and refer to VMS system documentation.
07650, 00000, "sigunc: $GETJPIW failure"
// *Cause: While attempting to get the user's terminal device name,
// user name, user program name, or process name
// during logon, VMS system service $GETJPIW failed.
// *Action: Examine the system error message and refer to VMS documentation.
07655, 00000, "slsprom:$TRNLOG failure"
// *Cause: While attempting to translate SYS$INPUT during a prompt for
// a password, VMS system service $TRNLOG failed.
// *Action: Examine the system error message and refer to VMS documentation.
07656, 00000, "slsprom:$GETDVI failure"
// *Cause: While attempting to get device characteristics during a prompt
// for a password, VMS system service $GETDVI failed.
// *Action: Examine the system error message and refer to VMS documentation.
07657, 00000, "slsprom:$ASSIGN failure"
// *Cause: While prompting for a password, VMS system service $ASSIGN failed.
// *Action: Examine the system error message and refer to VMS documentation.
07658, 00000, "slsprom:$QIOW read failure"
// *Cause: While prompting for a password, VMS system service $QIOW failed.
// *Action: Examine the system error message and refer to VMS documentation.
07665, 00000, "ssrexhd: recursive exception encountered %s %s %s %s %s %s"
// *Cause: A VMS exception occurred while executing in the Oracle exception
// handler. The message includes the signal number, first and second
// signal arguments, and exception PC, PSL and R0. This is an
// internal error.
// *Action: Contact your customer support representative.
07670, 00000, "$IDTOASC failed translating a secrecy category"
// *Cause: VMS system service $IDTOASC failed while looking up the string
// representation in the rights database of a secrecy category.
// *Action: Define the entry in the rights database which the binary label
// you specified references.
07671, 00000, "$IDTOASC failed translating an integrity category"
// *Cause: VMS system service $IDTOASC failed while looking up the string
// representation in the rights database of an integrity category.
// *Action: Define the entry in the rights database which the binary label
// you specified references.
07672, 00000, "$PARSE_CLASS failed translating the string into a binary label"
// *Cause: SEVMS system service $PARSE_CLASS failed because the given
// string did not represent a valid classification.
// *Action: Examine system error message and refer to SEVMS documentation.
07680, 00000, "sou2os: another call to Oracle currently executing"
// *Cause: A call to the Oracle shared image entry point occurred from within
// the shared image. This is an internal error.
// *Action: Contact your customer support representative.
07681, 00000, "sou2os: An error occurred while initializing Oracle"
// *Cause: While attempting to set up the dispatch vectors for the shared
// image, an error occurred. This is an internal error.
// *Action: Contact your customer support representative.
07682, 00000, "sou2os: set kernel dispatch fail err"
// *Cause: During Oracle shared image entry, a dispatch to kernel mode
// failed.
// *Action: Make sure that your shared image is installed with the CMKRNL
// privilege, then contact your customer support representative.
07683, 00000, "sou2os: $SETPRV reset error"
// *Cause: During an attempt to restore user privileges at Oracle shared
// image exit, VMS system service $SETPRV failed. This is an
// internal error.
// *Action: Contact your customer support representative.
07684, 00000, "sou2os: supervisor stack reset error"
// *Cause: During an attempt to restore the supervisor-mode stack at
// Oracle shared image exit, VMS system service $SETSTK failed.
// This is an internal error.
// *Action: Contact your customer support representative.
07685, 00000, "sou2os: supervisor stack set error"
// *Cause: During an attempt to set the Oracle supervisor-mode stack
// at Oracle shared image entry, VMS system service $SETSTK failed.
// This is an internal error.
// *Action: Contact your customer support representative.
/
/ 7700 - 7720: sksarch errors
/
07700, 00000, "sksarch: interrupt received"
// *Cause: An interrupt was received while archiving the logs
// *Action: Retry operation
07701, 00000, "sksatln: internal exception: output buffer too small"
// *Cause: Overflow of buffer for parsing archive control text string
// *Action: This is an internal error, please report to Oracle
07702, 00000, "unrecognized device type in archive text"
// *Cause: Unrecognized device type in archive text
// *Action: This is an internal error, please report to Oracle
07703, 00000, "error in archive text: need '/' after device type"
// *Cause: The archive control text in the ARCHIVE command is invalid;
// the device type (to indicate a file or tape) must be followed
// by a '/'.
// *Action: Refer to the SQLDBA Guide for the proper syntax of the text.
07704, 00000, "error in archive text: need ':' after device name"
// *Cause: The archive control text in the ARCHIVE command is invalid;
// the device name must be followed by a ':'.
// *Action: Refer to the SQLDBA Guide for the proper syntax of the text.
07705, 00000, "sksaprs: device name buffer too small"
// *Cause: The buffer supplied for the device name is too small. This is
// an internal error.
// *Action: Contact your customer support representative.
07706, 00000, "error in archive text: need disk file name"
// *Cause: The archive control text in the ARCHIVE command is invalid;
// the disk file name is missing.
// *Action: Refer to the SQLDBA Guide for the proper syntax of the text.
07707, 00000, "error in archive text: need tape label name"
// *Cause: The archive control text in the ARCHIVE command is invalid;
// the tape label name is missing.
// *Action: Refer to the SQLDBA Guide for the proper syntax of the text.
07708, 00000, "sksaprs: tape label name buffer too small"
// *Cause: The buffer supplied for the tape label is too small. This is
// an internal error.
// *Action: Contact your customer support representative.
07709, 00000, "sksaprs: archiving to a remote host is not allowed"
// *Cause: The user specified a remote disk for archiving via DECnet.
// *Action: Archive to a disk on the local host.
07710, 00000, "sksaprs: file name buffer too small"
// *Cause: The buffer supplied for the file name is too small. This is
// an internal error.
// *Action: Contact your customer support representative.
07713, 00000, "sksamtd: could not mount archival device (SYS$MOUNT failure)"
// *Cause: VMS system service SYS$MOUNT failed
// *Action: Examine system error message and refer to VMS documentation
07715, 00000, "sksadtd: could not dismount archival device (SYS$DISMNT failure)"
// *Cause: VMS system service SYS$DISMNT failed
// *Action: Examine system error message and refer to VMS documentation
07716, 00000, "sksachk: invalid device specification for ARCHIVE"
// *Cause: VMS system service SYS$GETDVI failed"
// *Action: Specify a valid device in ARCHIVE control string
07717, 00000, "sksaalo: error allocating memory"
// *Cause: VMS system service LIB$GET_VM failed"
// *Action: Examine system error message and refer to VMS documentation
07718, 00000, "sksafre: error freeing memory"
// *Cause: VMS system service LIB$FREE_VM failed
// *Action: Examine system error message and refer to VMS documentation
/
/ 7721-7729 scg overflow errors
/
07721, 00000, "scgcm: not enough OS resource to obtain system enqueue"
// *Cause: A call to sys$enq returned an error indicating that the operating
// system lacked the resources necessary to create a lock. This is
// caused by the messages SS$_EXENQLM or SS$_INSFMEM.
// *Action: Free up some of the required resource to allow the creation of the
// required lock.
/
/ 7740 - 7760 error message file errors
07740, 00000, "slemop: incorrect handle size (programming error)"
// *Cause: structures used for reading error message files do not match
// *Action: this is an internal error, please report to Oracle
07741, 00000, "slemop: $OPEN failure"
// *Cause: VMS system service $OPEN failed
// *Action: Examine system error message and refer to VMS documentation
07742, 00000, "slemop: $CONNECT failure"
// *Cause: VMS system service $CONNECT failed
// *Action: Examine system error message and refer to VMS documentation
07743, 00000, "slemop: incorrect error file attributes"
// *Cause: An error message file is of incorrect format
// *Action: Unless an error file has been changed, report this to Oracle
07744, 00000, "slemcl: invalid error message file handle"
// *Cause: seal in passed in handle does not match correct value
// *Action: this is an internal error, please report to Oracle
07745, 00000, "slemcl: $CLOSE failure"
// *Cause: VMS system service $CLOSE failed
// *Action: Check system error and refer to VMS documentation
07746, 00000, "slemrd: invalid error message file handle"
// *Cause: seal in passed in handle does not match correct value
// *Action: this is an internal error, please report to Oracle
07747, 00000, "slemrd: $READ failure"
// *Cause: VMS system service $READ failed
// *Action: Check system error and refer to VMS documentation
07750, 00000, "slemcr: fopen failure"
// *Cause: An attempt to create a message file failed. This is an
// internal error.
// *Action: Contact your customer support representative.
07751, 00000, "slemcr: malloc failure"
// *Cause: An attempt to allocate a cache for a newly-created message
// file failed. This is an internal error.
// *Action: Contact your customer support representative.
07753, 00000, "slemcf: fseek before write failure"
// *Cause: An attempt to seek before writing a message file cache
// element failed. This is an internal error.
// *Action: Contact your customer support representative.
07754, 00000, "slemcf: fwrite failure"
// *Cause: An attempt to write a message file cache element failed.
// This is an internal error.
// *Action: Contact your customer support representative.
07755, 00000, "slemcf: fseek before read failure"
// *Cause: An attempt to seek before reading a message file cache
// element failed. This is an internal error.
// *Action: Contact your customer support representative.
07756, 00000, "slemcf: fread failure"
// *Cause: An attempt to read a message file cache element failed.
// This is an internal error.
// *Action: Contact your customer support representative.
07757, 00000, "slemcc: invalid handle"
// *Cause: The seal in a passed-in handle does not match correct value.
// This is an internal error.
// *Action: Contact your customer support representative.
07758, 00000, "slemcw: invalid handle"
// *Cause: The seal in a passed-in handle does not match correct value.
// This is an internal error.
// *Action: Contact your customer support representative.
07759, 00000, "slemtr: invalid destination"
// *Cause: The destination string provided to the function is too short
// This is an internal error.
// *Action: Contact your customer support representative.
07760, 00000, "slemtr: $open failure"
// *Cause: the $open service failed. This is an internal error
// *Action: Contact your customer support representative.
07800, 00000, "slbtpd: invalid number"
// *Cause: An impossible request for binary to decimal conversion was made
// *Action: This conversion cannot be performed
07801, 00000, "slbtpd: invalid exponent"
// *Cause: An impossible request for binary to decimal conversion was made
// *Action: This conversion cannot be performed
07802, 00000, "slbtpd: overflow while converting to packed decimal"
// *Cause: An impossible request for binary to decimal conversion was made
// *Action: This conversion cannot be performed
07803, 00000, "slpdtb: invalid packed decimal nibble"
// *Cause: An impossible request for decimal to binary conversion was made
// *Action: This conversion cannot be performed
07804, 00000, "slpdtb: number too large for supplied buffer"
// *Cause: An impossible request for decimal to binary conversion was made
// *Action: This conversion cannot be performed
/
/ 7820-7839 SSP error messages
/
07820, 0000, "sspscn: SYS$CRELNM failure"
// *Cause: An error was returned from the SYS$CRELNM function
// *Action: Check system error and refer to VMS documentation
07821, 0000, "sspsdn: SYS$DELLNM failure"
// *Cause: An error was returned from the SYS$DELLNM function
// *Action: Check system error and refer to VMS documentation
07822, 0000, "sspscm: SYS$CREMBX failure"
// *Cause: An error was returned from the SYS$CREMBX function while
// trying to create the process dump mailbox.
// *Action: Check system error and refer to VMS documentation
07823, 0000, "sspsqr: $QIO failure"
// *Cause: An error was returned from $QIO while trying to
// queue a read to the process dump mailbox.
// *Action: Check system error and refer to VMS documentation
07824, 0000, "sspain: $SETIMR failure"
// *Cause: An error was returned from SYS$SETIMR while trying to
// queue a process spin-watch timer.
// *Action: Check system error and refer to VMS documentation
07825, 0000, "sspsck: $QIO failure at AST level"
// *Cause: An error was returned from SYS$QIO while trying to
// read the process dump mailbox.
// *Action: Check system error and refer to VMS documentation
07826, 0000, "sspscm: SYS$GETDVIW failure"
// *Cause: An error was returned from SYS$GETDVIW while trying to
// get information about the process dump mailbox.
// *Action: Check system error and refer to VMS documentation
/
/ 7840-7859 SLLF error messages
/
07840, 0000, "sllfop: LIB$GET_VM failure"
// *Cause: An error was returned from LIB$GET_VM while attempting to
// allocate memory for an i/o vector.
// *Action: Check system error and refer to VMS documentation
07841, 0000, "sllfop: SYS$OPEN failure"
// *Cause: An error was returned from SYS$OPEN while attempting to
// open the data file for reading
// *Action: Check system error and refer to VMS documentation
07842, 0000, "sllfcl: SYS$CLOSE failure"
// *Cause: An error was returned from SYS$CLOSE while attempting to
// close the input data file
// *Action: Check system error and refer to VMS documentation
07843, 0000, "sllfcl: LIB$FREE_VM failure"
// *Cause: An error was returned from LIB$FREE_VM while attempting to
// free the memory for the i/o vector
// *Action: Check system error and refer to VMS documentation
07844, 0000, "sllfop: LIB$GET_VM failure"
// *Cause: An error was returned from LIB$GET_VM while attempting to
// allocate memory for data and index buffers
// *Action: Check system error and refer to VMS documentation
07845, 0000, "sllfcl: LIB$FREE_VM failue"
// *Cause: An error was returned from LIB$FREE_VM while attempting to
// free memory used by data and index buffers
// *Action: Check system error and refer to VMS documentation
07846, 0000, "sllfop: %s byte record too big for %s byte user buffer"
// *Cause: The longest record in the file will not fit into the
// largest data buffer that can be allocated
// *Action: Modify the RMS file to have smaller records
07847, 0000, "sllfop: $CONNECT failure"
// *Cause: An error was returned by SYS$CONNECT while attempting
// to open the data file
// *Action: Check system error and refer to VMS documentation
07848, 0000, "sllfrb: $GET failure"
// *Cause: An error was returned by SYS$GET while attempting
// to read the data file
// *Action: Check system error and refer to VMS documentation
07849, 0000, "sllfsk: $GET failure"
// *Cause: An error was returned by SYS$GET while attempting to
// skip records in the input file
// *Action: Check system error and refer to VMS documentation
07850, 0000, "sllfop: bad option"
// *Cause: You are using a bad option to loader
// Fixed= is one legal option. Check documentation for others.
// *Action: Check documentation
07860, 0000, "osnsoi: error setting up interrupt handler"
// *Cause: An error occurred while setting up the control interrupt handler
// *Action: This is an internal error. Contact your Oracle representative.
/
/
/ 7880 - 7889 Error message for sd
/
07880, 0000, "sdopnf: internal error"
// *Cause: A list of all files open by this process could not be obtained.
// *Action: This is an internal error. Contact your customer support
// representative.
/
/ 8000 - 8174 Data layer error messages
/
08000, 00000, "maximum number of session sequence lists exceeded"
// *Cause: the sequence parent state objects for this session are all used
// *Action: an internal error; quit the session and begin a new one
08001, 00000, "Deprecated"
// *Document: NO
// *Cause: This bug has been deprecated. Do not use it.
// *Action: N/A
08002, 00000, "sequence %s.CURRVAL is not yet defined in this session"
// *Cause: sequence CURRVAL has been selected before sequence NEXTVAL
// *Action: select NEXTVAL from the sequence before selecting CURRVAL
08003, 00000, "sequence %s.NEXTVAL exceeds internal limits"
// *Cause: The sequence was created with unsafe values for some of the
// parameters. The calculation of NEXTVAL cannot be made because it
// exceeds the legal represention size.
// *Action: Alter or recreate the sequence number with legal limits.
08004, 00000, "sequence %s.NEXTVAL %s %sVALUE and cannot be instantiated"
// *Cause: instantiating NEXTVAL would violate one of MAX/MINVALUE
// *Action: alter the sequence so that a new value can be requested
08005, 00000, "specified row does not exist"
// *Cause: A row with the given rowid does not exist in any of the tables given
// *Action: check the query for misspellings of table names and the rowid
08006, 00000, "specified row no longer exists"
// *Cause: the row has been deleted by another user since the operation began
// *Action: re-try the operation
08007, 00000, "Further changes to this block by this transaction not allowed"
// *Cause: Max locks have been reached for this transaction in this block
// *Action: Commit changes
08008, 00000, "another instance is mounted with USE_ROW_ENQUEUES = %s"
// *Cause: the shared instance being started does not have the same value
// for use_row_enqueues as already running instances
// *Action: ensure that all instances' INIT.ORA files specify the same value
// for the parameter 'use_row_enqueues'
08100, 00000, "index is not valid - see trace file for diagnostics"
// *Cause: Validate Index detected an inconsistency in its argument index
// *Action: Send trace file to your customer support representative
08101, 00000, "index key does not exist file %s: (root %s, node %s) blocks (%s)"
// *Cause: Internal error: possible inconsistency in index
// *Action: Send trace file to your customer support representative, along
// with information on reproducing the error
08102, 00000, "index key not found, obj# %s, file %s, block %s (%s)"
// *Cause: Internal error: possible inconsistency in index
// *Action: Send trace file to your customer support representative, along
// with information on reproducing the error
08103, 00000, "object no longer exists"
// *Cause: The object has been deleted by another user since the operation
// began, or a prior incomplete recovery restored the database to
// a point in time during the deletion of the object.
// *Action: Delete the object if this is the result of an incomplete
// recovery.
08104, 00000, "this index object %s is being online built or rebuilt"
// *Cause: the index is being created or rebuild or waited for recovering
// from the online (re)build
// *Action: wait the online index build or recovery to complete
08105, 00000, "Oracle event to turn off smon cleanup for online index build"
// *Cause: set this event only under the supervision of Oracle development
// *Action: debugging only
08106, 00000, "cannot create journal table %s.%s"
// *Cause: The online index builder could not create its journal table
// *Action: Rename the conflicting table or rerun the SQL statement. There
// * may be a concurrent online index rebuild on the same object.
// *Action: rename your table in conflict or rerun the SQL statement
// * there may be a concurrent online index rebuild on the same object.
08108, 00000, "may not build or rebuild this type of index online "
// *Cause: only support normal index or IOT top-level index
// *Action: change your index type
08109, 00000, "nosort is not a supported option for online index build "
// *Cause: may not specify nosort for online index build
// *Action: get rid of nosort in the index creation command
08110, 00000, "Oracle event to test SMON cleanup for online index build "
// *Cause: Oracle Kernel test only
// *Action: Donot set this event(for test only)
08111, 00000, "a partitioned index may not be coalesced as a whole"
// *Cause: User attempted to coalesce a partitioned index using
// ALTER INDEX COALESCE statement, which is illegal
// *Action: Coalesce the index a (sub)partition at a time (using
// ALTER INDEX MODIFY (sub)PARTITION COALESCE)
08112, 00000, "a composite partition may not be coalesced as a whole"
// *Cause: User attempted to coalesce a composite partition
// *Action: Coalesce the index a subpartition at a time (using
// ALTER INDEX MODIFY SUBPARTITION COALESCE)
08113, 00000, "composite partition index may not be compressed"
// *Cause: User attempted to compress a composite partition index
// *Action: create uncompressed composite partition index
08114, 00000, "can not alter a fake index"
// *Cause: User attempted to alter a fake index
// *Action: drop fake index
08115, 00000, "can not online create/rebuild this index type"
// *Cause: User attempted to create index type that online doesnot support
// *Action: use offline index create/rebuild command
08116, 00000, "can not acquire dml enough lock(S mode) for online index build"
// *Cause: User attempted to create index online without allowing DML Share lock
// *Action: allow DML share lock on the base table
08117, 00000, "Index Organized Table operation released its block pin"
// *Cause: Block maintenance forced the release of a block pin
// *Action: Contact your customer support representative
08118, 00000, "Deferred FK constraints cannot be enforced, index too big (%s)"
// *Cause: Deferred Foreign Key constraints cannot be enforced due to the
// index key being too big and built on a non-default DB_BLOCK_SIZE.
// *Action: First try to drop the Foreign Key and then the primary key.
08119, 00000, "The new initrans will make the index too big"
// *Cause: Specifying the initrans need additional space to hold the index
// key which might make the index too big
// *Action: Try giving a smaller initrans value
08120, 00000, "Need to create SYS.IND_ONLINE$ table in order to (re)build index"
// *Cause: Alter index Build/Rebuild online require existing of
// SYS.IND_ONLINE$ table.
// *Action: User/DBA needs to create sys.ind_online$ before alter the index
// /rdbms/admin/catcio.sql contains script to create ind_online$.
08121, 00000, "Number of indexes need to be maintained offline exceeds limit for DML"
// *Cause: Too many indexes needed to be maintained. The limit is 2^16 indexes
// for each DML statement
// *Action: Make sure the index maintainance is online.
// If indexes need to be maintained offline, drop some indexes.
08122, 00000, "Online (re)build of index rolled back due to DML conflict"
// *Cause: The online (re)build journal is inconsistent with ongoing DML and
// cannot be used successfully to complete the online index (re)build.
// *Action: Reissue the online (re)build operation, after performing any
// cleanup, if needed.
/
/ 8175 - 8190 Discrete transaction error messages
/
08175, 00000, "discrete transaction restriction violated (%s)"
// *Cause: An attempt was made to perform an action that is not currently
// supported in a discrete transaction.
// *Action: Rollback the transaction, and retry it as a normal transaction.
/
08176, 00000, "consistent read failure; rollback data not available"
// *Cause: Encountered data changed by an operation that does not generate
// rollback data : create index, direct load or discrete transaction.
// *Action: In read/write transactions, retry the intended operation. Read
// only transactions must be restarted.
08177, 00000, "can't serialize access for this transaction"
// *Cause: Encountered data changed by an operation that occurred after
// the start of this serializable transaction.
// *Action: In read/write transactions, retry the intended operation or
// transaction.
08178, 00000, "illegal SERIALIZABLE clause specified for user INTERNAL"
// *Cause: Serializable mode is not supported for user INTERNAL.
// *Action: Reconnect as another user and retry the SET TRANSACTION
// command.
08179, 00000, "concurrency check failed"
// *Cause: Encountered data changed by an operation that occurred after
// a specific snapshot. This is usually used to indicate that a
// particular cached copy of a datablock is stale. This is used
// for internal use for now.
// *Action: refresh the cached copy of the datablock and retry operation.
08180, 00000, "no snapshot found based on specified time"
// *Cause: Could not match the time to an SCN from the mapping table.
// *Action: try using a larger time.
08181, 00000, "specified number is not a valid system change number"
// *Cause: supplied scn was beyond the bounds of a valid scn.
// *Action: use a valid scn.
08182, 00000, "operation not supported while in Flashback mode"
// *Cause: user tried to do dml or ddl while in Flashback mode
// *Action: disable Flashback and re-attempt the operation
08183, 00000, "Flashback cannot be enabled in the middle of a transaction"
// *Cause: user tried to do Flashback in the middle of a transaction
// *Action: do a commit
08184, 00000, "attempting to re-enable Flashback while in Flashback mode"
// *Cause: as stated above
// *Action: disable first before re-enabling
08185, 00000, "Flashback not supported for user SYS"
// *Cause: user logged on as SYS
// *Action: logon as a different (non SYS) user.
08186, 00000, "invalid timestamp specified"
// *Cause: as stated above
// *Action: enter a valid timestamp
08187, 00000, "snapshot expression not allowed here"
// *Cause: A snapshot expression using AS OF was specified when not allowed.
// *Action: Do not use the AS OF clause
08189, 00000, "cannot flashback the table because row movement is not enabled"
// *Cause: An attempt was made to perform Flashback Table operation on a table for
// which row movement has not been enabled. Because the Flashback Table
// does not preserve the rowids, it is necessary that row
// movement be enabled on the table.
// *Action: Enable row movement on the table
08190, 00000, "restore point %s is from a different incarnation of the database"
// *Cause: An attempt was made to perform Flashback Table operation using a
// restore point from a different incarnation of the database
// *Action: Provide a restore point from the current database incarnation
08191, 00000, "Flashback Table operation is not supported on remote tables"
// *Cause: An attempt was made to perform Flashback Table operation on a
// remote table. This is not permitted.
// *Action: Do not perform a Flashback Table operation on remote tables.
08192, 00000, "Flashback Table operation is not allowed on fixed tables"
// *Cause: An attempt was made to perform Flashback Table operation on a
// fixed table. This is not permitted.
// *Action: Do not perform a Flashback Table operation on fixed tables.
08193, 00000, "Flashback Table operation is not allowed on temporary tables"
// *Cause: An attempt was made to perform Flashback Table operation on
// a temporary table. This is not permitted.
// *Action: Do not perform a Flashback Table operation on temporary tables.
08194, 00000, "Flashback Table operation is not allowed on materialized views"
// *Cause: An attempt was made to perform Flashback Table operation on a
// materialized view. This is not permitted.
// *Action: Do not perform a Flashback Table operation on materialized views
// or snapshot logs.
08195, 00000, "Flashback Table operation is not supported on partitions"
// *Cause: An attempt was made to perform Flashback Table operation on a
// partition. This is not permitted.
// *Action: Do not perform a Flashback Table operation on partitions.
08196, 00000, "Flashback Table operation is not allowed on AQ tables"
// *Cause: An attempt was made to perform Flashback Table operation on AQ tables.
// This is not permitted.
// *Action: Do not perform a Flashback Table operation on AQ tables.
08197, 00000, "Flashback Table operation is not supported on clustered tables"
// *Cause: An attempt was made to perform Flashback Table operation on a
// clustered table. This is not permitted.
// *Action: Do not perform a Flashback Table operation on clustered tables.
08198, 00000, "Flashback Table is not supported on object tables, nested tables"
// *Cause: An attempt was made to perform Flashback Table operation on a
// object table or a nested table or a table with nested table column.
// This is not permitted.
// *Action: Do not perform a Flashback Table operation on such tables.
08199, 00000, "Flashback Table operation is not supported on this object"
// *Cause: An attempt was made to perform Flashback Table operation on an
// object on which the operation is not supported.
// *Action: Do not perform a Flashback Table operation on such objects.
/ 8200 - 8399 Reserved for NCUBE OSD errors
/
08205, 00000, "ora_addr: $ORACLE_SID not set in environment"
// *Cause: The environment variable ORACLE_SID is not set.
// *Action: Set the ORACLE_SID environment variable.
08206, 00000, "ora_addr: cannot translate address file name"
// *Cause: Cannot translate $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf.
// *Action: Ensure that ORACLE_HOME and ORACLE_SID are properly set.
08207, 00000, "ora_addr: cannot open address file"
// *Cause: The address file could not be opened.
// *Action: Check that ORACLE is up. Check that the file
// $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and has
// correct permissions.
08208, 00000, "ora_addr: cannot read from address file"
// *Cause: The address file could not be read.
// *Action: Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf
// exists and contains a single line of text.
08209, 00000, "scngrs: SCN not yet initialized"
// *Cause: The System Commit Number has not yet been initialized.
// *Action: Contact your customer support representative.
08210, 00000, "Requested I/O error"
// *Cause: Oracle requested that an I/O error be returned for this operation.
// *Action: This should not occur in normal Oracle operation. Contact support.
/
08230, 00000, "smscre: failed to allocate SGA"
// *Cause: The n_core system call failed, maybe due to insufficient memory.
// *Action: Specify a smaller number of buffers. Check INIT.ORA parameters.
08231, 00000, "smscre: unable to attach to SGA"
// *Cause: The process cannot attach to the SGA. This can happen if either
// the listener can't attach, or the process cannot communicate
// with the listener.
// *Action: Verify that the instance is up and running. Contact your
// customer support representative.
08232, 00000, "smsdes: cannot detach from SGA"
// *Cause: Probably, the listener process has died.
// *Action: Contact your customer support representative.
08233, 00000, "smsdes: cannot unmap SGA"
// *Cause: The n_core system call failed while detaching from the SGA.
// *Action: Note nCX error returned; contact your customer support
// representative.
08234, 00000, "smsget: cannot get instance listener address"
// *Cause: The instance listener address cannot be read from the sgadef file.
// *Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly.
// Additional information gives error return from ora_addr.
08235, 00000, "smsget: listener not on this node"
// *Cause: A process wishing to attach to the SGA is on a different
// node from its instance's listener.
// *Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly.
// Contact your customer support representative.
08236, 00000, "smsget: cannot share subcube with listener"
// *Cause: The n_share call failed, probably because the listener has died.
// *Action: Check if the listener is running, and contact your customer
// support representative.
08237, 00000, "smsget: SGA region not yet created"
// *Cause: Attempting to attach to an SGA which has not yet been created.
// *Action: Verify that the instance is running. Contact your customer
// support representative.
08238, 00000, "smsfre: cannot detach from SGA"
// *Cause: The n_core system call failed while detaching from the SGA.
// *Action: Check nCX error, and contact your customer support
// representative.
/8239 -8242 Reserved
/
08243, 00000, "recursive audit operation attempted"
// *Cause: A recursive operation requiring audit was attempted in the
// middle of an auditing operation or an audit table movement
// operation. The most likely reason is that space management
// operations needed to free up space in the audit tablespace or a SQL
// operation on dictionary tables directly or using database triggers
// which produced more audit records.
// *Action: Check space in the tablespace for SYS.AUD$ or SYS.FGA_LOG$
// and correct the problem. Or, if the problem was recursively
// auditing SQL operations, remove the audit configuration on such
// objects or statements.
/8252 - 8260 Reserved
08260, 00000, "ora_addr: cannot open nameserver"
// *Cause: A process could not connect to the nameserver.
// *Action: Make sure the nameserver is up and running. Additional
// information gives nameserver's returned status.
08261, 00000, "ora_addr: cannot find name in nameserver"
// *Cause: The listener nameserver entry for an instance could not be found.
// *Action: Make sure the nameserver is up and running. Additional
// information gives nameserver's returned status.
/8262 Reserved
/
08263, 00000, "ora_addr: cannot free listener address"
// *Cause: The listener nameserver entry could not be freed
// *Action: Additional information gives nameserver's returned status.
// Contact your customer support representative.
08264, 00000, "ora_addr: cannot close nameserver"
// *Cause: The connection to the nameserver could not be closed.
// *Action: Additional information gives nameserver's returned status.
// Contact your customer support representative.
08265, 00000, "create_ora_addr: cannot open nameserver"
// *Cause: A process could not connect to the nameserver.
// *Action: Make sure the nameserver is up and running. Additional
// information gives nameserver's returned status.
08266, 00000, "create_ora_addr: cannot register name in nameserver"
// *Cause: The listener's addressing information could not be registered.
// *Action: Make sure the nameserver is up and running. Additional
// information gives nameserver's returned status.
08267, 00000, "destroy_ora_addr: cannot close nameserver"
// *Cause: The connection to the nameserver could not be closed.
// *Action: Additional information gives nameserver's returned status.
// Contact your customer support representative.
08268, 00000, "create_ora_addr: cannot close nameserver"
// *Cause: The connection to the nameserver could not be closed.
// *Action: Additional information gives nameserver's returned status.
// Contact your customer support representative.
08269, 00000, "destroy_ora_addr: cannot destroy name"
// *Cause: The listener's addressing information could not be removed.
// *Action: Additional information gives nameserver's returned status.
// Contact your customer support representative.
/ 8270 - 8273 Reserved nCUBE archival
08270, 00000, "sksachk: Illegal archival control string"
// *Cause: Archive files cannot be created with the given archival control
// string.
// *Action: Check that the volume exists
08271, 00000, "sksabln: Buffer size not large enough for archive control string"
// *Cause: The given archival control string expands into too many characters.
// *Action: Reduce archive control string length.
/ 8273 - reserved nCUBE archival
08274, 00000, "Out of memory for environment variable"
// *Cause: There is insufficient memory to return the requested value
// *Action: Reduce memory usage and retry.
08275, 00000, "Environment variable unset"
// *Cause: The requested environment variable is not set
// *Action: Ensure that the variable name requested is correct.
08276, 00000, "No room in nameserver for pid"
// *Cause: There is no room to record the pid for a background process
// *Action: Shutdown abort and restart the database.
08277, 00000, "Cannot set environment variable"
// *Cause: There is insufficient memory to expand the environment.
// *Action: Reduce memory usage and retry.
08278, 00000, "Cannot get CPU statistics"
// *Cause: Could not retrieve CPU times because n_stat failed.
// *Action: Contact customer support.
08308, 00000, "sllfop: Cannot open file"
// *Cause: Oracle could not open a file.
// *Action: Check the Unix errno returned as additional information.
08309, 00000, "sllfop: Cannot fstat file"
// *Cause: Oracle could not obtain information about an open file.
// *Action: Check the Unix errno returned as additional information.
08310, 00000, "sllfop: Bad value for recsize"
// *Cause: An illegal value for the record size was specified.
// *Action: Specify a value for the recsize option that is greater than 0.
08311, 00000, "sllfop: bad value for maxrecsize"
// *Cause: An illegal value for the maximum record size was specified.
// *Action: Specify a value for the maxrecsize option that is greater
// than 0.
08312, 00000, "sllfop: unrecognized processing option"
// *Cause: An unrecognized processing option was specified.
// *Action: Check the Oracle for nCUBE 2 User's Guide for valid options.
08313, 00000, "sllfop: could not allocate buffers"
// *Cause: Memory for the load buffers could not be allocated.
// *Action: Reduce the maximum record size. Eliminate any unnecessary
// processes on your current node before running SQL*Loader again.
08314, 00000, "sllfcf: Error closing file"
// *Cause: An error occurred trying to close a file.
// *Action: Check the Unix errno returned as additional information.
08315, 00000, "sllfrb: Error reading file"
// *Cause: An error occurred trying to read from a file.
// *Action: Check the Unix errno returned as additional information.
08316, 00000, "sllfsk: Error seeking in file."
// *Cause: The lseek system call returned an error.
// *Action: Check the Unix errno returned as additional information.
08317, 00000, "sllfsk: Error seeking in file."
// *Cause: The lseek system call returned an error.
// *Action: Check the Unix errno returned as additional information.
08318, 00000, "sllfsk: Error reading file"
// *Cause: An error occurred trying to read from a file.
// *Action: Check the Unix errno returned as additional information.
08319, 00000, "sllfsk: Error reading file"
// *Cause: An error occurred trying to read from a file.
// *Action: Check the Unix errno returned as additional information.
/
/ 8320 - 8329 Reserved for scn.c
08320, 00000, "scnget: Call to scnget before scnset or scnfnd."
// *Cause: An internal error
// *Action: Contact your customer support representative.
08321, 00000, "scnmin: NOT IMPLEMENTED YET"
// *Cause: An internal error
// *Action: Contact your customer support representative.
08322, 00000, "scnmin: open/convert of bias lock failed"
// *Cause: A call to the lkmgr failed to open and convert the bias lock
// *Action: Check to make sure the lkmgr is up.
08323, 00000, "scnmin: close of bias lock failed"
// *Cause: A call to the lkmgr failed to close the bias lock
// *Action: Check to make sure the lkmgr is up.
08330, 00000, "Printing not supported"
// *Cause: An attempt was made to automatically spool a file to the printer
// *Action: none
08331, 00000, "Wait operation timed out"
// *Cause: Oracle timed out waiting for an event
// *Action: Contact your Oracle support representative
08332, 00000, "rollback segment #%s specified not available"
// *Cause: (same as 1545)
// *Action: (same as 1545). Also, make sure you have created enough rollback
// segments for the number of instances you are trying to start.
/
/ 8340-8359 Reserved for nCUBE redo server errors
/
08340, 00000, "This command not allowed on nCUBE, only one thread is ever used."
// *Cause: An illegal command was executed for the nCUBE platform.
// *Action: There is no need to issue this command.
08341, 00000, "On nCUBE, this command can only be executed from instance 1."
// *Cause: A command that can only be issued on instance 1 was issued elsewhere.
// *Action: Log on to instance 1 and repeat the command.
08342, 00000, "sropen: failed to open a redo server connection"
// *Cause: An error occurred trying to connect to the redo server.
// *Action: The OS specific error message should tell you what to do.
08343, 00000, "srclose: failed to close a redo server connection"
// *Cause: An error occurred trying to close the redo server connection.
// *Action: The OS specific error message should tell you what to do.
08344, 00000, "srapp: failed to send redo data to the redo server"
// *Cause: An error occurred trying to send redo to the redo server.
// *Action: The OS specific error message should tell you what to do.
/
/ 8362 - 8399 Reserved for nCUBE sosd errors (unassigned)
/
/ 8400 UTL_RAW and UTL_PG error and warning messages
/
/ Start UTL_RAW and UTL_PG messages
/
/
/
/
/ CONTENTS:
/ Generic Base Messages for:
/ Procedural Gateway for APPC Administration Utility: Release 3.3.0
/
/ NOTES:
/
/ These messages are include in ORAUS.MSG and translated message files
/
/ rherwadk 04/09/96 - add error message for max_dump_file_size parameter
/ hasun 04/01/96 - Add message #12028
/ aroy 03/14/96 - reserve subrange for lob calls
/ dchatter 03/13/96 - Fix 24307 error
/ rxgovind 03/06/96 - add error 22929
/ slari 03/05/96 - add kpu error 243xxx
/ gngai 02/15/96 - PDML: change PDML error 12827 to 12828
/ gngai 02/15/96 - PDML: added itl deadlock error
/ gngai 02/13/96 - PDML: added errors for parallel txns
/ ashgupta 02/08/96 - Add 12023, 12024 (missing index, missing PK info)
/ ashgupta 02/08/96 - Add 12022, 12025 (altering snapshot log)
/ ltan 02/08/96 - add 1687
/ akruglik 02/07/96 - add messages for LOGGING/NOLOGGING
/ akruglik 02/01/96 - add msg 14101
/ sdas 02/01/96 - non-key overflow
/ hasun 01/31/96 - Add 12021: snapshot is corrupt
/ akruglik 01/31/96 - add msg 14100
/ akruglik 01/31/96 - shorten message 14052
/ hasun 01/22/96 - Add 12019: master table is a remote object
/ ssamu 01/22/96 - remove unused error message
/ jwlee 01/18/96 - tablespace-relative DBAs
/ hasun 01/17/96 - Add 12018: can not create a complex, pk snapshots
/ akruglik 01/14/96 - merge up to RDBMS_PTI_SUN4_960112
/ akruglik 01/11/96 - get rid of msg 14087
/ ashgupta 01/10/96 - Adding error 12017 (alter snapshot)
/ gswart 01/10/96 - Add event to indicate presence of a debugger
/ ssamu 01/09/96 - modify partition
/ ssamu 01/09/96 - support validate INTO <table>
/ akruglik 01/05/96 - add msg 14052
/ hasun 12/29/95 - Add errors for snapshot refresh validation
/ aho 12/28/95 - duc
/ gswart 12/27/95 - Proj 2381: add event for detecting redo log errors
/ ssamu 12/26/95 - alter table exchange partition
/ akruglik 12/22/95 - merge up to RDBMS_PTI_SUN4_951220
/ akruglik 12/22/95 - renumber msgs 14083,4 to 14086,7 to avoid
/ clashes with the latest PTI version
/ atsukerm 12/21/95 - tablespace-relative DBAs.
/ sthakur 12/20/95 - add KOKA errors
/ jwijaya 12/19/95 - add ranges for object SQL
/ jhealy 12/15/95 - single partition loads: add new errors
/ ssamu 12/15/95 - disallow LONG datatype columns in partitioned tables
/ ssamu 12/15/95 - merge from /vobs/rdbms/mesg/error.msg@@/main/st_rdbm
/ akruglik 11/28/95 - remove parameter from mesg 14080
/ akruglik 11/28/95 - add message 14084
/ akruglik 11/27/95 - add messages for ALTER INDEX REBUILD PARTITION proce
/ aho 11/16/95 - iot
/ ssamu 11/11/95 - change error message 14074
/ slari 11/03/95 - add upi object extension error messages
/ msimon 11/02/95 - merge from /vobs/rdbms/mesg/error.msg@@/main/st_rdbm
/ jweisz 11/01/95 - Add pls error msgs 6515,16,17 for rhari
/ msimon 09/26/95 - Add in preliminary version of kdl subsystem
/ jboonleu 09/20/95 - update error message file with ORI errors
/ tanguyen 09/15/95 - add 21602: dropping type with dependency
/ emendez 07/23/95 - cheking RCS rev to stabilize 7-7
/ png 12/01/94 - V7.01.06:
/ 8468 replaces 8421-24
/ 8466 replaces 8425-28, 8461
/ 8467 replaces 8406-8411, 8438, 8439, 8442
/ 8401 replaces 8401-8405
/ 8435 revised
/ 8414 added
/ cddavis 10/09/94 - deleted comments with kkxg references
/ cddavis 10/09/94 - header prefixed to us version of pirg msgs
/
08401, 00000, "invalid compiler name: %s"
// *Cause: An invalid compiler name <compname> was passed to a UTL_PG
// conversion routine.
// *Action: Correct the compiler name parameter in the PL/SQL code
// that called the conversion routine.
/
08402, 00000, "error executing PL/SQL code coverage"
// *Cause: An error occurred during execution of a PL/SQL code coverage
// procedure.
//
// *Action: Check the error stack for more details.
//
08412, 00000, "error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message"
// *Cause: The WMSGBSIZ is the maximun size for warning message block,
// it is recommanded to be 1024 bytes to 8 kbytes.
// *Action: Defined WMSGBLK of size between 1k to 8k bytes and
// update the WMSGBSIZ to the sizeof(WMSGBLK).
/
08413, 00000, "invalid compiler type in FORMAT parameter at %s"
// *Cause: An invalid compiler type is defined in format control block.
// The format control block is invalid.
// *Action: Check to be sure that the format parameter was built by
// MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT,
// and that it was not accidentally overwritten or modified
// by the PL/SQL procedure.
/
08414, 00000, "error encountered in %s"
// *Cause: The function <routine> returned an error.
// Where <routine> may be:
// RAW_TO_NUMER
// NUMBER_TO_RAW
// RAW_TO_NUMBER_FORMAT
// NUMBER_TO_RAW_FORMAT
// MAKE_NUMBER_TO_RAW_FORMAT
// MAKE_RAW_TO_NUMBER_FORMAT
// *Action: This message will be preceded by messages providing details
// about the error. Check those messages to determine what
// action to take.
/
08429, 00000, "raw data has invalid digit in display type data"
// *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER
// conversion routine contained invalid data. The picture mask
// parameter specified a digit, but the corresponding input
// from the raw data did not contain a valid digit.
// *Action: Either the input data is incorrect, or the picture mask
// is incorrect. Correct the appropriate item.
/
08430, 00000, "raw data missing leading sign"
// *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER
// conversion routine had no leading sign, but the mask
// options parameter specified a leading sign.
// *Action: Correct the input raw data or the mask options so that
// they match.
/
08431, 00000, "raw data missing zero as defined in picture"
// *Cause: The picture mask parameter passed to a UTL_PG
// RAW_TO_NUMBER conversion routine contained a zero, but
// the corresponding input from the raw data was not a zero.
// *Action: Either the input data is incorrect, or the picture mask
// is incorrect. Correct the appropriate item.
/
08432, 00000, "raw data has invalid floating point data"
// *Cause: The input raw data passed to a UTL_PG RAW_TO_NUMBER
// conversion routine contained invalid floating point data.
// *Action: Correct the input raw data.
/
08433, 00000, "invalid picture type in convert raw to number"
// *Cause: The picture mask parameter passed to a UTL_PG
// RAW_TO_NUMBER conversion routine contained non-numeric
// characters, but the conversion was to a numeric data
// type.
// *Action: Correct the picture mask parameter.
/
08434, 00000, "raw data has invalid trailing sign"
// *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER
// conversion routine had no trailing sign, but the mask
// options parameter specified a trailing sign.
// *Action: Correct the input raw data or the mask options so that
// they match.
/
08435, 00000, "PICTURE MASK missing the leading sign when SIGN IS LEADING specified"
// *Cause: The input MASK passed to a UTL_PG RAW_TO_NUMBER
// conversion routine had no leading sign, but the mask
// options parameter specified a leading sign.
// *Action: Correct the input raw data or the mask options so that
// they match.
/
08436, 00000, "raw data has invalid sign digit"
// *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER
// conversion routine had an invalid sign digit in the
// position where the picture mask specified a sign.
// *Action: Correct the input raw data or the picture mask so that
// they match.
/
08437, 00000, "invalid picture type in picture mask"
// *Cause: The picture mask parameter passed to a UTL_PG
// NUMBER_TO_RAW conversion routine contained non-numeric
// characters, but the conversion was to a numeric data
// type.
// *Action: Correct the picture mask parameter.
/
08440, 00000, "raw buffer is too short to hold converted data"
// *Cause: The output raw buffer passed to a UTL_PG NUMBER_TO_RAW
// conversion routine was not large enough to contain the
// results of the conversion based on the picture mask.
// *Action: Increase the raw buffer size to the size necessary to
// hold the entire result of the conversion.
/
08441, 00000, "closed parenthesis missing in picture mask"
// *Cause: A closed parenthesis was missing from the picture mask
// passed to a UTL_PG conversion routine.
// *Action: Correct the picture mask.
/
08443, 00000, "syntax error in BLANK WHEN ZERO clause in mask options"
// *Cause: A syntax error was found in the BLANK WHEN ZERO clause in
// the mask options parameter passed to a UTL_PG conversion
// routine. Valid specifications are:
// BLANK ZERO
// BLANK ZEROS
// BLANK ZEROES
// BLANK WHEN ZERO
// BLANK WHEN ZEROS
// BLANK WHEN ZEROES
// *Action: Correct the mask options parameter.
/
08444, 00000, "syntax error in JUSTIFIED clause in mask options"
// *Cause: A syntax error was found in the JUSTIFIED clause in the
// mask options parameter passed to a UTL_PG conversion
// routine. Valid specifications are:
// JUST
// JUST RIGHT
// JUSTIFIED
// JUSTIFIED RIGHT
// *Action: Correct the mask options parameter.
/
08445, 00000, "syntax error in SIGN clause in mask options"
// *Cause: A syntax error was found in the SIGN clause in the mask
// options parameter passed to a UTL_PG conversion routine.
// Valid specifications are:
// SIGN LEADING
// SIGN LEADING SEPARATE
// SIGN LEADING SEPARATE CHARACTER
// SIGN TRAILING
// SIGN TRAILING SEPARATE
// SIGN TRAILING SEPARATE CHARACTER
// SIGN IS LEADING
// SIGN IS LEADING SEPARATE
// SIGN IS LEADING SEPARATE CHARACTER
// SIGN IS TRAILING
// SIGN IS TRAILING SEPARATE
// SIGN IS TRAILING SEPARATE CHARACTER
// *Action: Correct the mask options parameter.
/
08446, 00000, "syntax error in SYNCHRONIZED clause in mask options"
// *Cause: A syntax error was found in the SYNCHRONIZED clause in the
// mask options parameter passed to a UTL_PG conversion
// routine. Valid specifications are:
// SYNC
// SYNC LEFT
// SYNC RIGHT
// SYNCHRONIZED
// SYNCHRONIZED LEFT
// SYNCHRONIZED RIGHT
// *Action: Correct the mask options parameter.
/
08447, 00000, "syntax error in USAGE clause in mask options"
// *Cause: A syntax error was found in the USAGE clause in the mask
// options parameter passed to a UTL_PG conversion routine.
// Valid specifications are:
// USAGE DISPLAY
// USAGE COMP
// USAGE COMP-3
// USAGE COMP-4
// USAGE COMPUTATIONAL
// USAGE COMPUTATIONAL-3
// USAGE COMPUTATIONAL-4
// USAGE IS DISPLAY
// USAGE IS COMP
// USAGE IS COMP-3
// USAGE IS COMP-4
// USAGE IS COMPUTATIONAL
// USAGE IS COMPUTATIONAL-3
// USAGE IS COMPUTATIONAL-4
// *Action: Correct the mask options parameter.
/
08448, 00000, "syntax error in DECIMAL-POINT environment clause"
// *Cause: A syntax error was found in the DECIMAL-POINT environment
// clause parameter passed to a UTL_PG conversion routine.
// Valid specifications are:
// DECIMAL-POINT IS COMMA
// *Action: Correct the environment clause parameter.
/
08449, 00000, "invalid numeric symbol found in picture mask"
// *Cause: An invalid numeric symbol was found in the picture mask
// parameter passed to a UTL_PG conversion routine.
// *Action: Correct the picture mask parameter.
/
08450, 00000, "invalid specification of CR in picture mask"
// *Cause: The CR suffix was incorrectly specified in the picture mask
// parameter passed to a UTL_PG conversion routine. The CR
// suffix can only appear at the end of a picture mask.
// *Action: Correct the picture mask parameter.
/
08451, 00000, "invalid specification of DB in picture mask"
// *Cause: The DB suffix was incorrectly specified in the picture mask
// parameter passed to a UTL_PG conversion routine. The DB
// suffix can only appear at the end of a picture mask.
// *Action: Correct the picture mask parameter.
/
08452, 00000, "specification of E in picture mask is unsupported"
// *Cause: The floating point exponent symbol 'E' was specified in the
// picture mask parameter passed to a UTL_PG conversion
// routine. The floating point data type is currently not
// supported by the UTL_PG conversion routines.
// *Action: Correct the picture mask parameter, and the data, if
// necessary.
/
08453, 00000, "more than one V symbol specified in picture mask"
// *Cause: The picture mask passed to a UTL_PG conversion routine
// contained more than one decimal point indicator ('V').
// Only one decimal point indicator is allowed in the picture
// mask.
// *Action: Correct the picture mask parameter.
/
08454, 00000, "more than one S symbol specified in picture mask"
// *Cause: The picture mask passed to a UTL_PG conversion routine
// contained more than one operational sign indicator ('S').
// Only one operational sign indicator is allowed in the
// picture mask.
// *Action: Correct the picture mask parameter.
/
08455, 00000, "syntax error in CURRENCY SIGN environment clause"
// *Cause: A syntax error was found in the CURRENCY SIGN environment
// clause parameter passed to a UTL_PG conversion routine.
// Valid specifications are:
// CURRENCY SIGN IS x where x is a valid currency sign
// *Action: Correct the environment clause parameter.
/
08456, 00000, "no sign in picture mask but SIGN clause in mask options"
// *Cause: The picture mask parameter passed to a UTL_PG conversion
// routine contained no sign symbol ('S', '+', or '-'), but
// the mask options parameter contained a SIGN clause. A sign
// symbol is required in the picture mask parameter when the
// mask options parameter contains a SIGN clause.
// *Action: Correct the picture mask parameter or the mask options
// parameter.
/
08457, 00000,"syntax error in SEPARATE CHARACTER option of SIGN clause"
// *Cause: A syntax error was found in the SEPARATE CHARACTER option
// of the SIGN clause in the mask options parameter passed to
// a UTL_PG conversion routine. Valid specifications are:
// SEPARATE
// SEPARATE CHARACTER
// *Action: Correct the mask options parameter.
/
08458, 00000, "invalid format parameter"
// *Cause: The format parameter passed to a UTL_PG conversion routine
// was invalid. The format parameter should have been built by
// a prior call to either MAKE_RAW_TO_NUMBER_FORMAT or
// MAKE_NUMBER_TO_RAW_FORMAT.
// *Action: Check to be sure that the format parameter was built by
// MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT,
// and that it was not accidentally overwritten or modified
// by the PL/SQL procedure.
/
08459, 00000, "invalid format parameter length"
// *Cause: The format parameter passed to a UTL_PG conversion routine
// was not the correct length. Format parameters must be 2048
// bytes in length.
// *Action: Check to be sure that the format parameter was built by
// MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT,
// and that it was not accidentally overwritten or modified
// by the PL/SQL procedure.
/
08460, 00000, "invalid environment clause in environment parameter"
// *Cause: The environment parameter passed to a UTL_PG conversion
// routine contained an unsupported or invalid environment
// clause. Only the CURRENCY SIGN and the DECIMAL-POINT IS
// COMMA environment clauses are supported.
// *Action: Correct the environment parameter.
/
08462, 00000, "raw buffer contains invalid decimal data"
// *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER
// conversion routine contains invalid decimal data.
// *Action: Correct the input data.
/
08463, 00000, "overflow converting decimal number to Oracle number"
// *Cause: The output variable passed to a UTL_PG RAW_TO_NUMBER
// was not large enough to hold the Oracle number resulting
// from the input decimal number.
// *Action: Be sure that the input decimal number is valid, and besure
// that the output variable is large enough to hold the Oracle
// number value.
/
08464, 00000, "input raw decimal data contains more than 42 digits"
// *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER
// conversion routine contained more than 42 digits. This
// exceeds the maximum size of an Oracle number.
// *Action: Correct the raw input buffer.
/
08465, 00000, "input mask contains more than 32 characters"
// *Cause: The input mask passed to UTL_PG numeric conversion
// routine contained more the 32 characters.
// *Action: Correct the mask input buffer.
/
08466, 00000, "raw buffer length %s is too short for %s"
// *Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER
// conversion routine was less than %s bytes long, but the
// picture mask parameter specified that %s bytes of input data
// were to be converted.
// *Action: Either the input data is incorrect, or the picture mask
// is incorrect. Correct the appropriate item.
/
08467, 00000, "error converting Oracle number to %s"
// *Cause: An error occurred when converting an Oracle number to a
// COBOL <type> of:
// DISPLAY
// COMP-3
// or character variable.
// The Oracle number was not in the correct format.
// *Action: Correct the call to the conversion routine. The input
// must be a valid Oracle number variable.
/
08468, 00000, "mask option %s is not supported"
// *Cause: The mask option <clause> was passed to a UTL_PG
// conversion routine, but is not supported by UTL_PG.
// The <clause> can be:
// USAGE IS POINTER
// USAGE IS INDEX
// USAGE IS COMP-1
// USAGE IS COMP-2
// POINTER
// *Action: Remove the <clause> from the mask options parameter
// in the PL/SQL call to UTL_PG.
/
08469, 00000, "must use the SIGN IS SEPARATE clause in mask options"
// *Cause: A signed numeric entry with DISPLAY usage was converted using a
// non-defaulted character set and its PICTURE character-string
// contains an S. In these circumstances, a SIGN IS SEPARATE clause
// must be specified in the mask options.
// *Action: Either specify a valid SIGN IS SEPARATE clause in the mask options,
// use the defaulted character set, or don't specify an S in the
// PICTURE character-string.
/
08498, 00000, "Warning: picture mask '%s' overrides picture mask option 'USAGE IS %s' to 'USAGE IS DISPLAY'"
// *Cause: Picture mask USAGE option was overridden by the picture mask.
// *Action: This is an informational message only. The message may be
// eliminated by changing the USAGE option to match the picture mask.
/
08499, 00000, "Warning: picture mask options '%s' ignored by UTL_PG "
// *Cause: Picture mask options such as OCCUR, SYNC and others are not
// processed by the UTL_PG numeric conversion routines.
// *Action: This is an informational message only. The message may be
// eliminated by removing the unnecessary picture mask options
// from the parameter list passed to the UTL_PG routine.
/
/
/
/ End UTL_RAW and UTL_PG messages
/
/
/ 8401 - 8499 Reserved for APPC Gateway
/
/ 8500 - 8599 Reserved for Protocol Procedural Gateway for
/ MQ Series
/
/
/
/
/
/
/
/
/ 8600 - 8699 Reserved for ??? sql*connnect errors
/
/ 8700 - 8799 Reserved for ??? sql*connnect errors
/
/ 8800 - 8999 Reserved for Tandem sql*connnect errors
/
/ 9000 - 9099 Reserved for TERADATA sql*connnect errors
/
/ 9100 - 9199 Reserved for file-based sql*connnect errors
/
/ 9200 - 9499 Reserved for OS/2 and MSDOS OSD errors
/
// File I/O errors: 9200 - 9239
/
09200, 00000, "sfccf: error creating file"
// *Cause: Could be out of disk space
// *Action: See OSD error accompanying this message
09201, 00000, "sfcopy: error copying file"
// *Cause: Block sizes may not match
// *Action: See OSD error accompanying this message
09202, 00000, "sfifi: error identifying file"
// *Cause: db_block_size specified in init.ora could be incorrect
// *Action: See OSD error accompanying this message
09203, 00000, "sfofi: error opening file"
// *Cause: File attributes may have changed
// *Action: See OSD error accompanying this message
09204, 00000, "sfotf: error opening temporary file"
// *Cause: Incorrect path may have been specified for the file
// *Action: See OSD error accompanying this message
09205, 00000, "sfqio: error reading or writing to disk"
// *Cause: File may have been truncated or corrupted
// *Action: See OSD error accompanying this message
09206, 00000, "sfrfb: error reading from file"
// *Cause: File may have been truncated or corrupted
// *Action: See OSD error accompanying this message
09207, 00000, "sfsrd: error reading from file"
// *Cause: File may have been truncated or corrupted
// *Action: See OSD error accompanying this message
09208, 00000, "sftcls: error closing file"
// *Cause: File may have been corrupted
// *Action: See OSD error accompanying this message
09209, 00000, "sftget: error reading from file"
// *Cause: File may have been truncated or corrupted
// *Action: See OSD error accompanying this message
09210, 00000, "sftopn: error opening file"
// *Cause: Incorrect path may have been specified for the file
// *Action: See OSD error accompanying this message
09211, 00000, "sfwfb: error writing to file"
// *Cause: File may have been truncated or corrupted
// *Action: See OSD error accompanying this message
09212, 00000, "sfwfbmt: error writing to file"
// *Cause: File may have been truncated or corrupted
// *Action: See OSD error accompanying this message
09213, 00000, "slgfn: error fabricating file name"
// *Cause: Filename may be too long
// *Action: See OSD error accompanying this message
09214, 00000, "sfdone: I/O error detected"
// *Cause: File may have been truncated or corrupted
// *Action: See OSD error accompanying this message
09215, 00000, "sfqio: error detected in IOCompletionRoutine"
// *Cause: File may have been truncated or corrupted
// *Action: See OSD error accompanying this message
09216, 00000, "sdnfy: bad value '%s' for parameter %s"
// *Cause: The directory specified as the value for the stated parameter
// could not be used.
// *Action: Make sure the directory you have specified is a valid
// directory/file specification.
09217, 00000, "sfsfs: failed to resize file"
// *Cause: Could be out of disk space
// *Action: See OSD error accompanying this message
09218, 00000, "sfrfs: failed to refresh file size"
// *Cause: File may be corrupted or truncated
// *Action: See OSD error accompanying this message
/
// Memory allocation errors: 9240 - 9259
/
09240, 00000, "smpalo: error allocating PGA memory"
// *Cause: Could be out of memory
// *Action: See OSD error accompanying this message
09241, 00000, "smsalo: error allocating SGA memory"
// *Cause: Could be out of memory
// *Action: See OSD error accompanying this message
09242, 00000, "smscre: error creating SGA"
// *Action: See OSD error accompanying this message
09243, 00000, "smsget: error attaching to SGA"
// *Cause: SGA may not have been created (database not started)
// *Action: See OSD error accompanying this message
09244, 00000, "smprset: error setting memory protections"
// *Action: See OSD error accompanying this message
09245, 00000, "smcstk: error switching stacks"
// *Action: See OSD error accompanying this message
09246, 00000, "sfsmap: unable to map SGA"
// *Action: See OSD error accompanying this message
09247, 00000, "smsdes: error destroying the SGA"
// *Action: See OSD error accompanying this message
/
// Process control errors: 9260 - 9269
/
09260, 00000, "sigpidu: error obtaining process id"
// *Cause: May be out of resources
// *Action: See OSD error accompanying this message
09261, 00000, "spdcr: error creating detached (background) process"
// *Cause: Could be out of resources
// *Action: See OSD error accompanying this message
09262, 00000, "spdde: error terminating detached (background) process"
// *Cause: Could be out of resources
// *Action: See OSD error accompanying this message
09263, 00000, "spini: error initializing process"
// *Cause: Could be out of memory
// *Action: See OSD error accompanying this message
09264, 00000, "sptpa: error flagging process"
// *Cause: Could be out of resources
// *Action: See OSD error accompanying this message
09265, 00000, "spwat: error temporarily suspending process"
// *Cause: Could be out of resources
// *Action: See OSD error accompanying this message
09266, 00000, "spawn: error starting an Oracle process"
// *Cause: Could be out memory
// *Action: See OSD error accompanying this message
/
// Security errors: 9270 - 9279
/
09270, 00000, "szalloc: error allocating memory for security"
// *Cause: Could be out of memory
// *Action: See OSD error accompanying this message
09271, 00000, "szlon: error verifying user name"
// *Cause: Username may be too long
// *Action: See OSD error accompanying this message
09272, 00000, "remote os logon is not allowed"
// *Cause: Remote os login attempted when not allowed.
// *Action: See OSD error accompanying this message
09273, 00000, "szrfc: error verifying role name"
// *Cause: An OS error was returned when verifying the role name.
// *Action: See OSD error accompanying this message
09274, 00000, "szrfc: insufficient role name buffer space"
// *Cause: An OS role name was too long.
// *Action: See OSD error accompanying this message
09275, 00000, "CONNECT INTERNAL is not a valid DBA connection"
// *Cause: CONNECT INTERNAL is no longer supported for DBA connections.
// *Action: Please try to connect AS SYSDBA or AS SYSOPER.
//
09276, 00000, "All bequeath database links must be loopback database links"
// *Cause: A non-loopback bequeath connect string was supplied for a database
// link.
// *Action: Please use a connect string with a different transport protocol,
// or specify a loopback connect string (one that points to
// the instance for the current session) using
// "(PROGRAM=<this instance's ORACLE_HOME>/bin/oracle)" and,
// optionally, "(ENVS=''ORACLE_SID=<this instance's ORACLE_SID>'')".
/
// Direct loader errors: 9280 - 9289
/
09280, 00000, "sllfcf: error closing file"
// *Cause: File may be corrupted
// *Action: See OSD error accompanying this message
09281, 00000, "sllfop: error opening file"
// *Cause: Possibly incorrect path specified to the file
// *Action: See OSD error accompanying this message
09282, 00000, "sllfrb: error reading records"
// *Cause: File could be corrupted
// *Action: See OSD error accompanying this message
09283, 00000, "sllfsk: error skipping records"
// *Cause: File could be corrupted
// *Action: See OSD error accompanying this message
09284, 00000, "sllfop: cannot allocate read buffer"
// *Cause: malloc() system call returned an error. The system might have run
// out of heap space
// *Action: Check additional information for the OS error.
09285, 00000, "sllfop: unrecognizable processing option, incorrect format"
// *Cause: Processing option passed is of incorrect format
// *Action: Consult your IUG for permissible formats
/
// Archiving errors: 9290 - 9299
/
09290, 00000, "sksaalo: error allocating memory for archival"
// *Cause: Could be out of memory
// *Action: See OSD error accompanying this message
09291, 00000, "sksachk: invalid device specified for archive destination"
// *Cause: Unable to access directory
// *Action: Specify a valid device in ARCHIVE control string
09292, 00000, "sksabln: unable to build archive file name"
// *Cause: Bad directory or format specified
// *Action: Specify a valid directory in 'log_archive_format' and a valid
// format string in 'log_archive_format' in init.ora
09293, 00000, "sksasmo: unable to send message to console"
// *Cause: An error was returned while attempting to send a message
// to the console operator
// *Action: See OSD error accompanying this message
/
// Windows specific errors: 9300 - 9309
/
09300, 00000, "osncon: unable to connect, DPMI not available"
// *Cause: Unable to detect the presence of DPMI
// *Action: Restart Windows and retry
09301, 00000, "osncon: local kernel only supported in standard mode"
// *Cause: An attempt was made to connect to S: while in enhanced mode
// *Action: Restart Windows in standard mode
/
// Miscellaneous errors: 9310 - 9339
/
09310, 00000, "sclgt: error freeing latch"
// *Cause: Internal error
// *Action: See OSD error accompanying this message
09311, 00000, "slsleep: error temporarily suspending process"
// *Cause: May be out of resources
// *Action: See OSD error accompanying this message
09312, 00000, "slspool: error spooling file to printer"
// *Cause: Could be out of resources
// *Action: See OSD error accompanying this message
09313, 00000, "slsprom: error prompting user"
// *Cause: May be out of resources
// *Action: See OSD error accompanying this message
09314, 00000, "sltln: error translating logical name"
// *Cause: Internal buffer may have overflowed
// *Action: See OSD error accompanying this message
09315, 00000, "sql2tt: two-task error translating ORACLE_EXECUTABLE"
// *Cause: Internal error
// *Action: See OSD error accompanying this message
09316, 00000, "szrpc: unable to verify password for role"
// *Cause: OS roles may not be supported for this platform
// *Action: See OSD error accompanying this message
09317, 00000, "szprv: insufficient privileges"
// *Cause: The password specified is invalid
// *Action: See OSD error accompanying this message
09318, 00000, "slkhst: unable to host out to operating system"
// *Cause: There might not be enough memory for the command or hosting out
// may not be supported on this platform
// *Action: See OSD error accompanying this message
09319, 00000, "slgtd: unable to obtain the current date and time"
// *Cause: The system time might be set incorrectly
// *Action: See OSD error accompanying this message
09320, 00000, "szrfc: unable to obtain the list of valid OS roles"
// *Cause: OS roles may not be supported on this platform
// *Action: See OSD error accompanying this message
09321, 00000, "slzdtb: unable to convert zoned decimal to binary"
// *Cause: internal error
// *Action: See OSD error accompanying this message
09322, 00000, "slpdtb: unable to convert packed decimal to binary"
// *Cause: internal error
// *Action: See OSD error accompanying this message
09330, 00000, "Session terminated internally by Oracle or by an Oracle DBA"
// *Cause: A client workstation that is abnormally disconnected would
// cause Oracle to terminate that session after about a minute.
// This message also appears in the trace file if a shutdown abort
// is performed.
/9331 - 9335 Reserved
/
09340, 00000, "Specified ORACLE_SID is either invalid or too long"
// *Cause: ORACLE_SID must be at the most 4 alphanumeric characters.
09341, 00000, "scumnt: unable to mount database"
// *Cause: Another instance is currently mounting the database
09342, 00000, "Detached process terminated by Oracle during shutdown abort"
// *Cause: The user performed a shutdown abort.
09344, 00000, "spsig: error signalling thread"
// *Cause: This function may not be implemented.
/
/
// Windows 32-bit Two-Task driver: 9350 - 9359
/
09350, 00000, "Windows 32-bit Two-Task driver unable to allocate context area"
// *Cause: See OSD error accompanying this message
09351, 00000, "Windows 32-bit Two-Task driver unable to allocate shared memory"
// *Cause: See OSD error accompanying this message
09352, 00000, "Windows 32-bit Two-Task driver unable to spawn new ORACLE task"
// *Cause: See OSD error accompanying this message
09353, 00000, "Windows 32-bit Two-Task driver unable to open event semaphore"
// *Cause: See OSD error accompanying this message
09354, 00000, "Windows 32-bit Two-Task driver: ORACLE task unexpectedly died"
// *Cause: See OSD error accompanying this message
/
/
// Windows 3.1 Two-Task driver: 9360 - 9379
/
09360, 00000, "Windows 3.1 Two-Task driver unable to allocate context area"
// *Cause: See OSD error accompanying this message
09361, 00000, "Windows 3.1 Two-Task driver unable to lock context area"
// *Cause: See OSD error accompanying this message
09362, 00000, "Windows 3.1 Two-Task driver unable to deallocate context area"
// *Cause: See OSD error accompanying this message
09363, 00000, "Windows 3.1 Two-Task driver invalid context area"
// *Cause: See OSD error accompanying this message
09364, 00000, "Windows 3.1 Two-Task driver unable to create hidden window"
// *Cause: See OSD error accompanying this message
09365, 00000, "Windows 3.1 Two-Task driver unable to destroy hidden window"
// *Cause: See OSD error accompanying this message
09366, 00000, "Windows 3.1 Two-Task driver unable to allocate shared memory"
// *Cause: See OSD error accompanying this message
09367, 00000, "Windows 3.1 Two-Task driver unable to deallocate shared memory"
// *Cause: See OSD error accompanying this message
09368, 00000, "Windows 3.1 Two-Task driver unable to spawn ORACLE"
// *Cause: See OSD error accompanying this message
09369, 00000, "Windows 3.1 Two-Task driver bad instance handle"
// *Cause: See OSD error accompanying this message
09370, 00000, "Windows 3.1 Two-Task driver ORACLE task timed out"
// *Cause: See OSD error accompanying this message
/
/ 9500 - 9699 Reserved for MPE/XL OSD errors
/
/ 9700 - 9999 Reserved for UNIX OSD errors
/
09700, 00000, "sclin: maximum number of latches exceeded"
// *Cause: ORACLE wants to use more latches then available.
// *Action: increase INIT.ORA parameter latch_pages or
// decrease the amount of shared memory you are using.
09701, 00000, "scnfy: maximum number of processes exceeded"
// *Cause: PROCESSES INIT.ORA parameter exceeded.
// *Action: Decrease the PROCESSES parameter and restart.
09702, 00000, "sem_acquire: cannot acquire latch semaphore"
// *Cause: The semaphore used for accessing latches could not be seized
// *Action: Send trace file to your customer support representative,
// along with information on reproducing the error.
09703, 00000, "sem_release: cannot release latch semaphore"
// *Cause: The semaphore used for accessing latches could not be released
// *Action: Send trace file to your customer support representative,
// along with information on reproducing the error.
09704, 00000, "sstascre: ftok error in creating test and set pages."
// *Cause: the ftok() library call failed in sstastcre().
// *Action: Verify that tasdef@.dbf file exists. If it does then this is a
// possible system failure. Perhaps System V compatibility is not
// enabled.
09705, 00000, "spcre: cannot initialize latch semaphore"
// *Cause: The semaphore used for accessing latches could not be initialized
// *Action: Send trace file to your customer support representative,
// along with information on reproducing the error.
09706, 00000, "slsget: get_process_stats error."
// *Cause: get_process_stats system call returned an error. Possible OS error.
// *Action: Check additional information returned. Look for information in
// OS reference. Contact customer support.
09708, 00000, "soacon: failed to bind socket to port."
// *Cause: The bind system call failed on the socket.
// *Action: Check additional information for OS error. Try connecting again.
09709, 00000, "soacon: failed to accept a connection."
// *Cause: The accept system call failed on the socket.
// *Action: Check additional information for OS error. Try connecting again.
09710, 00000, "soarcv: buffer overflow."
// *Cause: The internal buffer is not big enough to hold the message read.
// *Action: Internal error. Contact customer support representative.
09711, 00000, "orasrv: archmon already connected."
// *Cause: An existing connection has already been made from archmon to
// orasrv.
// *Action: Stop trying to connect.
09712, 00000, "orasrv: log archiver already connected."
// *Cause: An existing connection has already been made from log archiver to
// orasrv.
// *Action: Stop trying to connect.
09714, 00000, "Two Task interface: cannot obtain puname"
// *Cause: The TXIPC driver cannot obtain the name of the PU.
// (Possible OS error)
// *Action: Check if the PUs are named (consistend).
09715, 00000, "orasrv: cannot obtain puname"
// *Cause: Orasrv cannot obtain the name of the PU.
// (Possible OS error)
// *Action: Check if the PUs are named (consistend).
09716, 00000, "kslcll: Unable to fix in-flux lamport latch."
// *Cause: One Oracle process died while still holding a lamport latch.
// *Action: Exit (kill) all Oracle user processes. Shutdown (abort) and
// restart Oracle RDBMS kernel.
09717, 00000, "osnsui: maximum number of user interrupt handlers exceeded."
// *Cause: The internal limit on the number of user interrupt handlers has
// been exceeded.
// *Action: Reduce the number of simulataneous logons or reduce the number
// of user interrupt handlers.
09718, 00000, "osnsui: cannot set up user interrupt handler."
// *Cause: Malloc() failed to allocate space to hold user interrupt handler.
// *Action: Possible memory resource shortage.
09719, 00000, "osncui: invalid handle."
// *Cause: The handle passed to osncui is out of the valid range.
// *Action: Use a valid handle.
/
/ 09720-09739 reserved for Philips MPX P9x00
/
09740, 00000, "slsget: cannot get virtual memory region statistics."
// *Cause: The vm_region system call failed to get virual memory region
// statistics.
// *Action: Check return code in sercerrno. Possible operating system
// failure.
09741, 00000, "spwat: error waiting for a post."
// *Cause: Msg_receive system call returned an error. Internal error.
// *Action: Check return code in sercerrno. Port name is returned in
// sercose[0].
09742, 00000, "sppst: error during a post."
// *Cause: Msg_send system call returned an error. Internal error.
// *Action: Check return code in sercerrno. Port name is returned in
// sercose[0].
09743, 00000, "smscre: could not attach shared memory."
// *Cause: The mmap or write system call returned an error. Internal error.
// *Action: Contact Oracle support.
09744, 00000, "smsget: mmap returned an error."
// *Cause: The mmap system call returned an error. Internal error.
// *Action: Contact Oracle support.
09745, 00000, "smscre: vm_allocate error, unable to create shared memory."
// *Cause: Error in system call vm_allocate. Failed to create SGA as a
// single shared memory segment.
// *Action: Check result code returned in sercerrno. Verify that the SGA
// attach address is valid.
09746, 00000, "smscre: shared memory attach address incorrect."
// *Cause: The vm_allocate system call attached the SGA at an incorrect
// location.
// *Action: Verify that the SGA attach address is valid.
09747, 00000, "pw_detachPorts: server call pws_detach failed."
// *Cause: The call pws_detach to (Oracle helper) failed.
// *Action: Make sure the server is still active. Check the error code
// returned in sercerrno, and look for error messages in the
// server log file.
09748, 00000, "pws_look_up: fork failed"
// *Cause: The pws_look_up call could not fork the (Oracle helper) process.
// *Action: Verify that there are enough system resources to support another
// process. The user or system process limit may have been exceeded,
// or the amount of free memory or swap space may be temporarily
// insufficient.
09749, 00000, "pws_look_up: port lookup failure"
// *Cause: The pws_look_up could not find a port to (Oracle helper).
// *Action: Make sure the (Oracle helper) server has been started correctly
// by pws_look_up, and that the network name server is still running.
09750, 00000, "pw_attachPorts: port_rename failed."
// *Cause: The port_rename system call failed; possible internal error.
// *Action: Check return code in sercerrno, report to Oracle customer support.
09751, 00000, "pw_attachPorts: server call pws_attach failed."
// *Cause: The call pws_attach to (Oracle helper) failed.
// *Action: Make sure the server is still active. Check the error code
// returned in sercerrno, and look for error messages in the
// server log file.
09752, 00000, "pw_attachPorts: port_allocate failed."
// *Cause: The port_allocate system call failed; possible resource exhaustion.
// *Action: Check return code in sercerrno, report to Oracle customer support.
09753, 00000, "spwat: invalid process number."
// *Cause: Function was passed an invalid oracle process id.
// *Action: Internal error. Additional information indicates the invalid
// process id.
09754, 00000, "sppst: invalid process number passed to sppst."
// *Cause: Function was passed an invalid oracle process id.
// *Action: Internal error. Contact Oracle support.
09755, 00000, "osngpn: port allocation failure."
// *Cause: The port_allocate system call failed.
// *Action: Possible system resource shortage; check the error code in
// sercerrno.
09756, 00000, "osnpns: no port in the name server."
// *Cause: osnpns could not find the given named port in the name server.
// *Action: Check the error code in sercerrno. Make sure the shadow process
// and network name server are still running.
09757, 00000, "osnipn: port allocation failure."
// *Cause: The port_allocate system call failed.
// *Action: Possible system resource shortage; check the error code in
// sercerrno.
09758, 00000, "osnipn: could not check port in name server."
// *Cause: The netname_check_in call failed.
// *Action: Check the error code in sercerrno. Make sure the network name
// server is running.
09759, 00000, "osnsbt: bad message received."
// *Cause: The msg_receive system call failed, or received a bad message.
// *Action: Internal error. Report the error code returned in sercerrno.
09760, 00000, "osnpui: cannot send break message"
// *Cause: The Pipe driver could not send a break message to the ORACLE
// shadow process break thread.
// *Action: Contact your customer support representative.
09761, 00000, "pw_destroyPorts: server call pws_stop_instance failed."
// *Cause: The call pws_stop_instance to (Oracle helper) failed.
// *Action: Make sure the server is still active. Check the error code
// returned in sercerrno, and look for error messages in the
// server log file.
09762, 00000, "sNeXT_instanceName: translation error."
// *Cause: A failure was detected while translating the value of ORACLE_SID.
// *Action: Make sure ORACLE_SID is defined, and that it is of legal length.
09763, 00000, "osnmpx: send/receive error exchanging Mach ports."
// *Cause: The Mach driver failed to exchange port information with the
// other side of the connection. Either msg_send (sercose[0] == 1)
// or msg_receive (sercose[0] == 2) failed.
// *Action: Check return code in sercerrno. Make sure both sides of the
// connection are still running.
09764, 00000, "osnmop: access error on oracle executable"
// *Cause: The Mach driver could not access the oracle executable.
// *Action: Check the permissions on the ORACLE executable and each
// component of the ORACLE_HOME/bin path.
09765, 00000, "osnmop: fork failed"
// *Cause: The Mach driver could not fork the oracle shadow process.
// *Action: Verify that there are enough system resources to support another
// process. The user or system process limit may have been exceeded,
// or the amount of free memory or swap space may be temporarily
// insufficient.
09766, 00000, "osnmop: buffer allocation failure."
// *Cause: The Mach driver failed to allocate enough vm space for its
// I/O buffers.
// *Action: Decrease the value of buffer_size parameter in the Two-Task
// driver hoststring.
09767, 00000, "osnmfs: bad return code from msg_send."
// *Cause: The msg_send system call failed while flushing the Mach driver's
// send buffer.
// *Action: Internal error. Contact your customer support representative.
09768, 00000, "osnmgetmsg: could not read a message"
// *Cause: The msg_receive system call returned a failure code while waiting
// for a message in the Mach driver.
// *Action: Internal error. Contact your customer support representative.
09769, 00000, "osnmbr: cannot send break message"
// *Cause: The Mach driver could not send a break message to the ORACLE
// shadow process break thread.
// *Action: Internal error. Contact your customer support representative.
09770, 00000, "pws_look_up: translation failure."
// *Cause: The pws_look_up routine failed to translate the name of the
// (Oracle helper) executable.
// *Action: Make sure ORACLE_SID and ORACLE_HOME are set and correct.
// Additional information gives the translation error code.
09771, 00000, "osnmwrtbrkmsg: bad return code from msg_send."
// *Cause: The msg_send sytem call failed while sending a Mach driver break.
// *Action: Internal error. Contact your customer support representative.
09772, 00000, "osnpmetbrkmsg: message from host had incorrect message type"
// *Cause: The Mach driver received a message having an unrecognizable
// message type.
// *Action: Internal error. Contact your customer support representative.
09773, 00000, "osnmgetdatmsg: message from host had incorrect message type"
// *Cause: The Mach driver received a message having an unrecognizable
// message type.
// *Action: Internal error. Contact your customer support representative.
09774, 00000, "osnmui: cannot send break message"
// *Cause: The Mach driver could not send a break message to the ORACLE
// shadow process break thread.
// *Action: Internal error. Contact your customer support representative.
09775, 00000, "osnmrs: reset protocol error"
// *Cause: The Mach two-task driver could not reset the connection.
// *Action: Internal error. Contact your customer support representative.
09776, 00000, "pws_look_up: access error on (Oracle helper) executable"
// *Cause: The pws_look_up call could not access the (Oracle helper)
// executable.
// *Action: Check the permissions on the (Oracle helper) executable and each
// component of the ORACLE_HOME/bin path.
09777, 00000, "osnpbr: cannot send break message"
// *Cause: The pipe driver could not send a break message to the ORACLE
// shadow process break thread.
// *Action: Internal error. Contact your customer support representative.
09778, 00000, "snynfyport: failure allocating the notify port."
// *Cause: The routine failed to allocate or set the task's notify port.
// *Action: Possible operating system error. Contact Oracle support.
09779, 00000, "snyGetPort: failure to allocate a port."
// *Cause: The port_allocate system call failed; system resources might be
// exhausted.
// *Action: Possible operating system error. Contact Oracle support.
/
/ 09786-09825 reserved for Loader V2.0
/
09786, 00000, "sllfop: open error, unable to open file."
// *Cause: Open system call returned an error.
// *Action: Check errno.
09787, 00000, "sllfop: unrecognizable processing option, incorrect format."
// *Cause: Processing option passed is of incorrect format.
// *Action: Consult your IUG for permissible formats.
09788, 00000, "sllfrb: unable to read file."
// *Cause: Read system call returned an error.
// *Action: Check errno. Verify file exists.
09789, 00000, "sllfsk: unable to read file."
// *Cause: Read system call returned an error.
// *Action: Check errno. Verify file exists.
09790, 00000, "sllfcf: unable to close file."
// *Cause: Close system call returned an error.
// *Action: Check errno.
09791, 00000, "slembdf: translation error, unable to translate error file name."
// *Cause: Additional information indicates error returned from sltln.
// *Action: Check additional information.
09792, 00000, "sllfop: cannot allocate read buffer."
// *Cause: Malloc system call returned an error. The system might have run out
// of heap space.
// *Action: Check additional information for the OS error.
09793, 00000, "szguns: length of user name is greater than buffer."
// *Cause: The length of the name of the user being looked up is longer than
// size of the buffer provided by the calling routine.
// *Action: This is an internal error. Contact Oracle Support Services.
09794, 00000, "szrbuild: length of role name is greater than buffer."
// *Cause: The length of the name of the role being looked up is longer than
// size of the buffer provided by the calling routine.
// *Action: This is an internal error. Contact Oracle Support Services.
09795, 00000, "szrbuild: malloc of role structure failed."
// *Cause: The allocation of memory for an internal structure used to
// hold a role descriptor failed.
// *Action: Check the UNIX error number for a possible operating system
// failure.
09796, 00000, "szrbuild: malloc of role name failed."
// *Cause: The allocation of memory for an internal buffer used to hold the
// name of a role failed.
// *Action: Check the UNIX error number for a possible operating system
// failure.
09797, 00000, "Failed to get O/S MAC privileges."
// *Cause: The operating system would not allow the retrieval of this
// process' privileges.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact Oracle Support Services.
09798, 00000, "Label comparison failed."
// *Cause: The comparison of two binary labels failed.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact Oracle Support Services.
09799, 00000, "File label retrieval failed."
// *Cause: ORACLE was unable to get a label attached to a file.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact Oracle Support Services.
09800, 00000, "Process sensitivity label retrieval failed."
// *Cause: ORACLE was unable to get the sensitivity label for a process.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact Oracle Support Services.
09801, 00000, "Unable to get user ID from connection"
// *Cause: ORACLE was unable to retrieve the user's ID number from
// the SQL*Net connection.
// *Action: Check the UNIX error number for a possible operating system error.
// Also check the "additional information" field for the SQL*Net
// error. If there is no error, contact Oracle Support Services.
09802, 00000, "Conversion of binary label to string failed."
// *Cause: ORACLE was unable to convert a binary label to a string.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact Oracle Support Services.
09803, 00000, "Allocation of string buffer failed."
// *Cause: a buffer used to hold the name of the file for which a label was
// to be obtained could not be allocated.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact Oracle Support Services.
// The number of bytes that ORACLE attempted to allocate is in
// the "Additional Information" field.
09804, 00000, "Class conversion from binary to ORACLE failed."
// *Cause: ORACLE was unable to convert a class component from binary
// format to ORACLE format.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact Oracle Support Services.
09805, 00000, "conversion of category number to string failed."
// *Cause: ORACLE was unable to translate a category number to its
// corresponding string representation failed.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact Oracle Support Services. The
// category number is contained in the "Additional information"
// field.
09806, 00000, "Allocation of label string buffer failed."
// *Cause: a temporary buffer used to hold a label could not be allocated.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact Oracle Support Services.
// The number of bytes that ORACLE attempted to allocate is in
// the "Additional Information" field.
09807, 00000, "Conversion of label from string to binary failed."
// *Cause: ORACLE was unable to convert the string representation of a label
// to binary format.
// *Action: Re-enter a valid label.
09808, 00000, "Could not obtain user clearance."
// *Cause: ORACLE was unable to get a user's clearance level.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact Oracle Support Services.
09809, 00000, "Unable to get user's group ID from connection"
// *Cause: ORACLE was unable to retrieve the user's group ID number from
// the SQL*Net connection.
// *Action: Check the UNIX error number for a possible operating system error.
// Also check the "additional information" field for the SQL*Net
// error. If there is no error, contact Oracle Support Services.
09810, 00000, "Unable to get process ID from connection"
// *Cause: ORACLE was unable to retrieve the user's process ID number from
// the SQL*Net connection.
// *Action: Check the UNIX error number for a possible operating system error.
// Also check the "additional information" field for the SQL*Net
// error. If there is no error, contact Oracle Support Services.
09811, 00000, "Unable to initialize package."
// *Cause: ORACLE was unable to initialize the library used to obtain
// security information.
// *Action: This is an internal error. Contact Oracle Support Services.
09812, 00000, "Unable to get user clearance from connection"
// *Cause: ORACLE was unable to retrieve the user's operating system
// session clearance from the SQL*Net connection.
// *Action: Check the UNIX error number for a possible operating system error.
// Also check the "additional information" field for the SQL*Net
// error. If there is no error, contact Oracle Support Services.
09813, 00000, "Unable to get directory status"
// *Cause: ORACLE was unable to determine if a directory is multilevel.
// *Action: Check the UNIX error number for a possible operating system error.
// If there is no error, contact Oracle Support Services.
09814, 00000, "Unable to expand file name"
// *Cause: ORACLE was unable to expand the name of a file that resides
// in multilevel directory.
// *Action: Check the UNIX error number for a possible operating system error.
// If there is no error, contact Oracle Support Services.
09815, 00000, "File name buffer overflow"
// *Cause: The buffer that ORACLE uses to hold the expanded name of a
// too small.
// *Action: This is an internal error. Contact Oracle Support Services.
09816, 00000, "Unable to set effective privileges"
// *Cause:
// *Action: This is an internal error. Contact Oracle Support Services.
09817, 00000, "Write to audit file failed."
// *Cause: ORACLE was unable to write an entry to the file used as the
// audit trail.
// *Action: Check the UNIX error number for a possible operating system error.
// If there is no error, contact Oracle Support Services.
09818, 00000, "Number is too large"
// *Cause: ORACLE was unable to convert a component string to a number because
// the number is larger than the largest possible value for an
// integer. The additional information field specifies the maximum.
// *Action: Correct the string and repeat the conversion.
09819, 00000, "Number exceeds maximum legal value"
// *Cause: the number specified for a component was greater than the maximum
// value allowed for that component.
// *Action: Change the component to a value less than the maximum and repeat
// the conversion. The maximum component number is contained in the
// "Additional information" field.
09820, 00000, "Conversion of class string to numeric representation failed."
// *Cause: ORACLE was unable to convert a class string to a number because
// all of the characters in the string were not numeric.
// *Action: Change the string to be either all numbers or all non-numeric
// characters and repeat the conversion.
09821, 00000, "Numeric label is not valid"
// *Cause: A label specified in ORACLE numeric format was found not to be
// valid.
// *Action: Re-enter a valid label. Consult your system's encodings for valid
// numeric component values.
09822, 00000, "Translation of audit file name failed."
// *Cause: Oracle was unable to translate the value of the
// AUDIT_FILE_DEST initialization parameter.
// *Action: Check the UNIX error number for a possible operating system error.
// If there is no error, contact Oracle Support Services.
09823, 00000, "device name is too long"
// *Cause: The name of a device was too long to fit into an internal buffer.
// The additional information field contains the length of the device
// name.
// *Action: This is an internal error. Contact Oracle Support Services.
09824, 0000, "Unable to enable allowmacaccess privilege."
// *Cause: ORACLE was not able to turn on allowmacaccess privilege so that it
// could do a label comparison.
// *Action: Check the UNIX error number. If it indicates that ORACLE does not
// have the allowmacaccess privilege, add the allowmacaccess privilege
// to the potential privilege set of $ORACLE_HOME/bin/oracle using
// chpriv (1M). If the executable already has the allowmacaccess
// privilege, contact Oracle Support Services.
09825, 0000, "Unable to disable allowmacaccess privilege."
// *Cause: ORACLE was not able to turn off the allowmacaccess privilege after
// doing a label comparison.
// *Action: This is an internal error. Contact Oracle Support Services.
09826, 00000, "SCLIN: cannot initialize atomic latch."
// *Cause: System call atomic_op() return error.
// *Action: Check additional information in the trace file.
09827, 00000, "SCLGT: atomic latch return unknown error."
// *Cause: System call atomic_op() return unexpected error.
// *Action: Check additional information in the trace file.
09828, 00000, "SCLFR: atomic latch return error."
// *Cause: System call atomic_op() return unexpected error.
// *Action: Check additional information in the trace file.
09829, 00000, "pw_createPorts: server call pws_start_instance failed."
// *Cause: The call pws_start_instance to (Oracle helper) failed; system
// resources might be exhausted.
// *Action: Make sure the server is still active. Check the error code
// returned in sercerrno, and look for error messages in the
// server log file.
09830, 00000, "snyAddPort: failed to perform a remote procedure call."
// *Cause: The msg_rpc system call returned an error.
// *Action: Internal error. Contact Oracle support.
09831, 00000, "snyStartThread: failed to build the server port set."
// *Cause: The routine failed to build a port set on which to listen for
// requests.
// *Action: Possible operating system failure. Contact Oracle support.
09832, 00000, "infoCallback: bad message format."
// *Cause: The routine received an incorrectly formatted request.
// *Action: Internal error. Contact Oracle support.
09833, 00000, "addCallback: bad message format."
// *Cause: The routine received an incorrectly formatted request.
// *Action: Internal error. Contact Oracle support.
09834, 00000, "snyGetPortSet: failed to collect info on a port."
// *Cause: The port_status system called failed.
// *Action: Possible operating system error. Contact Oracle support.
09835, 00000, "addCallback: callback port is already in a set."
// *Cause: The port to be added to the callback list is already in a port set.
// *Action: Internal error. Contact Oracle support.
09836, 00000, "addCallback: could not add a port to the callback set."
// *Cause: The port_set_add system called failed.
// *Action: Possible operating system error. Contact Oracle support.
09837, 00000, "addCallback: could not add allocate a callback link."
// *Cause: The malloc library call failed to allocate space for a callback link.
// *Action: Possible operating system error. Contact Oracle support.
09838, 00000, "removeCallback: failure removing the callback port."
// *Cause: The port port_set_remove system call failed.
// *Action: Possible operating system error. Contact Oracle support.
09839, 00000, "removeCallback: callback port is not in the callback set."
// *Cause: The port to be removed to the callback list is not in the
// callback port set.
// *Action: Internal error. Contact Oracle support.
09840, 00000, "soacon: Name translation failure."
// *Cause: sltln() could not translate the named pipe ?/dbs/mon2arch_@.
// *Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID
// in oratab is correct.
09841, 00000, "soacon: Name translation failure."
// *Cause: sltln() could not translate the named pipe ?/dbs/arch2mon_@.
// *Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID
// in oratab is correct.
09842, 00000, "soacon: Archmon unable to create named pipe."
// *Cause: mknod() failed to create named pipe ?/dbs/mon2arch_@.
// *Action: Your current OS login may lack write permission for the
// ORACLE_HOME/dbs directory. Only userids in the dba group of a
// given instance can run archmon for that ORACLE_SID. Make sure
// that the ORACLE_HOME directory is correct in oratab.
09843, 00000, "soacon: Archmon unable to create named pipe."
// *Cause: mknod() failed to create named pipe ?/dbs/arch2mon_@.
// *Action: Your current OS login may lack write permission for the
// ORACLE_HOME/dbs directory. Only userids in the dba group of a
// given instance can run archmon for that ORACLE_SID. Make sure
// that the ORACLE_HOME directory is correct in oratab.
09844, 00000, "soacon: Archmon unable to open named pipe."
// *Cause: open() failed to open named pipe ?/dbs/mon2arch_@.
// *Action: Only the oracle dba can run archmon. Make sure that your
// current OS login has owner or group search permission for the
// ORACLE_HOME/dbs directory. The max number of open files may have
// been exceeded.
09845, 00000, "soacon: Archmon unable to open named pipe."
// *Cause: open() failed to open named pipe ?/dbs/arch2mon_@.
// *Action: Only the oracle dba can run archmon. Make sure that your
// current OS login has owner or group search permission for the
// ORACLE_HOME/dbs directory. The max number of open files may have
// been exceeded.
09846, 00000, "soacon: ARCH unable to open named pipe."
// *Cause: open() failed to open named pipe ?/dbs/mon2arch_@.
// *Action: Make sure that the OS userid of the currently running database
// has search permission for the ORACLE_HOME/dbs directory. The max
// number of open files may have been exceeded.
09847, 00000, "soacon: ARCH unable to open named pipe."
// *Cause: open() failed to open named pipe ?/dbs/arch2mon_@.
// *Action: Make sure that the OS userid of the currently running database
// has search permission for the ORACLE_HOME/dbs directory. The max
// number of open files may have been exceeded.
09848, 00000, "soawrt: Unable to write to named pipe."
// *Cause:
// *Action:
09849, 00000, "soarcv: Unable to read from named pipe."
// *Cause:
// *Action:
09850, 00000, "soacon: Archmon unable to lock named pipe."
// *Cause: fcntl() failed to set write lock on named pipe ?/dbs/arch2mon_@.
// *Action: Make sure that archmon is not already active on another terminal
// for this ORACLE_SID. Only one archmon session is allowed at a
// time for a given instance.
09851, 00000, "soacon: Archmon unable to lock named pipe."
// *Cause: fcntl() failed to set read lock on named pipe ?/dbs/mon2arch_@.
// *Action: Make sure that archmon is not already active on another terminal
// for this ORACLE_SID. Only one archmon session is allowed at a
// time for a given instance.
09853, 00000, "snyRemovePort: bad return code from request."
// *Cause: The request to remove a port from the callback set returned a
// failure code.
// *Action: Possible operating system error. Contact Oracle support.
09854, 00000, "snyPortInfo: bad return code from request."
// *Cause: The request to collect info on a port in the callback set returned
// a failure code.
// *Action: Possible operating system error. Contact Oracle support.
09855, 00000, "removeCallback: bad message format."
// *Cause: The routine received an incorrectly formatted request.
// *Action: Internal error. Contact Oracle support.
09856, 00000, "smpalo: vm_allocate error while allocating pga."
// *Cause: The vm_allocate system call returned an error.
// *Action: Check returned error. Possibly out of system resources.
09857, 00000, "smprset: vm_protect error while protecting pga."
// *Cause: The vm_protect system call returned an error.
// *Action: Internal error. Contact Oracle support.
09858, 00000, "sfngat: the input file name is not in the OMF format"
// *Cause: The function sfngat() received a filename which is not
// an OMF file name.
// *Action: Further diagnostic information should be in the error stack.
09859, 00000, "sfngat: the input file name is not in the autobackup OMF format"
// *Cause: The function sfngat() received a filename which is not
// an autobackup OMF file name.
// *Action: Further diagnostic information should be in the error stack.
/
/ 10630-10639 Reserved for Online Segment Shrink
/
/ 09858-09859 Reserved For NeXT port
/
/ 09860-09869 Reserved For Oracle Europe
/
09870, 00000, "spini: failure initializing maximum number of open files."
// *Cause: ulimit system call returned an error.
// *Action: Check errno.
09871, 00000, "TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf."
// *Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages.
// *Action: Check additional return error for more information.
09872, 00000, "TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf."
// *Cause: Create() failed when trying to create the tasdef file.
// *Action: Verify permissions on $(ORACLE_HOME)/dbs directory.
09873, 00000, "TASDEF_OPEN: open error when opening tasdef@.dbf file."
// *Cause: Unable to open tasdef@.dbf file.
// *Action: Check errno. Possible permission problem. Verify that
// tasdef@.dbf file exists.
09874, 00000, "TASDEF_READ: read error, unable to read tasdef@.dbf file."
// *Cause: Read system call returned an error when attempting to read
// ?/dbs/tasdef@.dbf.
// *Action: Check errno returned. Sgadef file may be corrupted or
// incompatible with oracle version.
09875, 00000, "TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file."
// *Cause: Write call failed.
// *Action: Check errno returned. Possibly out of space on device.
09876, 00000, "TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file."
// *Cause: Close system call returned an error.
// *Action: Check errno returned. Possible operating system failure.
09877, 00000, "sstascre: shmget error, unable to get a shared memory segment."
// *Cause: Error in shmget.
// *Action: Check errno returned. Verify that enough shared memory is available
// on the system.
09878, 00000, "sstascre/sstasat: shmat error, unable to attach tas write page"
// *Cause: Error in shmat.
// *Action: Check errno returned.Verify that enough shared memory is available
// on the system.
09879, 00000, "sstascre/sstasat: shmat error, unable to attach tas read page"
// *Cause: Error in shmat.
// *Action: Check errno returned.Verify that enough shared memory is available
// on the system.
09880, 00000, "sstasfre/sstasdel: shmdt error, unable to detach tas write page"
// *Cause: Error in shmdt.
// *Action: Check errno returned.
09881, 00000, "sstasfre/sstasdel: shmdt error, unable to detach tas read page"
// *Cause: Error in shmdt.
// *Action: Check errno returned.
09882, 00000, "sstasfre/sstasdel: shmctl error, unable to remove tas shm page"
// *Cause: Error in shmctl.
// *Action: Check errno returned.
09883, 00000, "Two Task interface: oratab file does not exist"
// *Cause: The oratab file does not exist.
// *Action: Install oracle before you use it or recreate the oratab file.
09884, 00000, "Two Task interface: SID doens't match current PU"
// *Cause: You are trying to start oracle on another PU than you configured
// oracle on or there is no entry for this SID in oratab file.
// *Action: Start oracle with this SID on its designated PU (see oratab file).
// Or install the new database with SID.
09885, 00000, "osnTXtt: cannot create TXIPC channel"
// *Cause: The TXIPC driver failed to create pipes for two-task communications
// with the oracle shadow process.
// *Action: You have probably exceeded the maximum number of open file
// descriptors per user or the system file table is full. Note the
// operating system error code and contact your system administrator.
09886, 00000, "osnTXtt: translation error while expanding txipc@.trc."
// *Cause: Failure of sltln(txipc@.trc) while creating debug channel.
// *Action: Check additional return error for more information.
09887, 00000, "osnTXtt: Failed to create/open debug channel."
// *Cause:
// *Action:
09888, 00000, "osnTXtt: txipc channel creation failed"
// *Cause: The txipc driver failed to create channels for two-task
// communications with the oracle shadow process.
// *Action: You have probably exceeded the maximum number of open file
// descriptors per user or the system file table
// operating system error code and contact your system administrator.
09889, 00000, "osnTXtt: access error on oracle executable"
// *Cause: The txipc driver could not access the oracle executable.
// *Action: Check the permissions on the ORACLE executable and each
// component of the ORACLE_HOME/bin path.
09890, 00000, "osnTXtt: malloc failed"
// *Cause: The txipx driver failed to allocate enough heap space for its
// context area buffers.
// *Action: Contact your customer support representative.
09908, 00000, "slkmnm: gethostname returned error code."
// *Cause: The system call gethostname returned an error.
// *Action: This is most likely an internal error. Make sure gethostname
// is successful in other contexts, and if so contact Oracle support.
09909, 00000, "Malloc of scratch buffer failed."
// *Cause: Memory needed for a temporary buffer could not be allocated.
// The additional information field contains the number of bytes
// that ORACLE attempted to allocate.
// *Action: Check the UNIX error number. It is probable that the system has
// run out of memory. If there is no error, contact ORACLE support.
09910, 00000, "Unable to find ORACLE password file entry for user."
// *Cause: No entry exists for the user in the ORACLE password file.
// *Action: Have the database administrator install a password entry by
// running orapasswd.
09911, 00000, "Incorrect user password."
// *Cause: The password entered by the user was incorrect.
// *Action: Enter the correct password.
09912, 00000, "Malloc of name buffer(s) failed."
// *Cause: ORACLE was unable to allocate memory for one or both of the buffers
// that are used to hold the name of DBA and the operator users.
// *Action: Check the UNIX error number. It is probable that the system has
// run out of memory. If there is no error, contact ORACLE support.
09913, 00000, "Malloc of dummy name failed."
// *Cause: ORACLE was unable to allocate memory for the user name that is to
// to be used in the encryption of the user's password.
// *Action: Check the UNIX error number. It is probable that the system has
// run out of memory. If there is no error, contact ORACLE support.
09914, 00000, "Unable to open the ORACLE password file."
// *Cause: ORACLE could not open the password file for reading.
// *Action: Check the UNIX error number. If the error number indicates that the
// file does not exist, have the database administrator create the
// file by running orapasswd. If the error number indicates
// insufficient permissions, ask the database administrator to change
// the permissions. Otherwise, contact ORACLE customer support.
09915, 00000, "Password encryption failed."
// *Cause: ORACLE was unable to encrypt a password.
// *Action: This is an internal error - contact ORACLE customer support.
09916, 00000, "Required password was not specified."
// *Cause: A user attempted to connect as "internal," but did not specify a
// password.
// *Action: Connect as internal again and specify a password.
09918, 00000, "Unable to get user privileges from SQL*Net"
// *Cause: ORACLE was unable to retrieve the user's privilege set from the
// SQL*Net connection.
// *Action: Check the UNIX error number for a possible operating system error.
// Also check the "additional information" field for the SQL*Net
// error. If there is no error, contact ORACLE support.
09919, 00000, "Unable to set label of dedicated server"
// *Cause: ORACLE was unable to set the label of the dedicated to server
// to the required value.
// *Action: Check the UNIX error number for a possible operating system error.
// Also, check the privileges on the oracle executable. It should
// have at least "allowmacaccess" privilege.
09920, 00000, "Unable to get sensitivity label from connection"
// *Cause: ORACLE was unable to retrieve the user's sensitivity label from
// the SQL*Net connection.
// *Action: Check the UNIX error number for a possible operating system error.
// Also check the "additional information" field for the SQL*Net
// error. If there is no error, contact ORACLE support.
09921, 00000, "Unable to get information label from connection"
// *Cause: ORACLE was unable to retrieve the user's information label from
// the SQL*Net connection.
// *Action: Check the UNIX error number for a possible operating system error.
// Also check the "additional information" field for the SQL*Net
// error. If there is no error, contact ORACLE support.
09922, 00000, "Can't spawn process - background log directory not created properly"
// *Cause: ORACLE was unable to spawn a background process because the
// directory that will hold trace files of the background
// processes was not created properly.
// *Action: Examine the directory pointed to by the initialization
// parameter "background_dump_dest". Make sure that all of the
// following is true:
// 1. The directory exists.
// 2. The name indeed points to a directory, and is not a file.
// 3. The directory is accessible and writable to the ORACLE user.
09923, 00000, "Can't spawn process - user log directory not created properly"
// *Cause: ORACLE was unable to spawn a background process because the
// directory that holds the trace files of the dedicated server
// processes was not created properly.
// *Action: Examine the directory pointed to by the initialization
// parameter "user_dump_dest". Make sure that all of the
// following is true:
// 1. The directory exists.
// 2. The name indeed points to a directory, and is not a file.
// 3. The directory is accessible and writable to the ORACLE user.
09924, 00000, "Can't spawn process - core dump directory not created properly"
// *Cause: ORACLE was unable to spawn a background process because the
// directory that holds the core dumps produced by ORACLE processes
// in the event of exceptions was not created properly.
// *Action: Examine the directory pointed to by the initialization
// parameter "core_dump_dest". Make sure that all of the
// following is true:
// 1. The directory exists.
// 2. The name indeed points to a directory, and is not a file.
// 3. The directory is accessible and writable to the ORACLE user.
09925, 00000, "Unable to create audit trail file"
// *Cause: ORACLE was not able to create the file being used to hold
// audit trail records.
// *Action: Check the UNIX error number for a possible operating system error.
// If there is no error, contact ORACLE customer support.
09926, 00000, "Unable to set effective privilege set of the server"
// *Cause: A dedicated server was unable to set it's own privilege set.
// *Action: Check the privileges granted to the ORACLE executable. It must
// have at least "allowmacacess" privilege.
09927, 00000, "Unable to set label of server"
// *Cause: ORACLE was not able to set the label of a server to a new value.
// *Action: Check the privileges on $ORACLE_HOME/bin/oracle. Make sure that it
// has "allowmacaccess" privilege.
09928, 00000, "Unable to restore the label of server"
// *Cause: ORACLE was unable to restore the label of the server to the value
// that it had before raising it to database high.
// *Action: This is an internal error - contact ORACLE support.
09929, 00000, "GLB of two labels is invalid"
// *Cause: The result of a greatest lower bound operation on two labels was
// not valid.
// *Action: Repeat the operation with two different labels. Consult the
// system encoding file for the values of valid labels.
09930, 00000, "LUB of two labels is invalid"
// *Cause: The result of a least upper bound operation on two labels was
// not valid.
// *Action: Repeat the operation with two different labels. Consult the
// system encoding file for the values of valid labels.
09931, 00000, "Unable to open ORACLE password file for reading"
// *Cause: An attempt to open a password file for reading failed.
// *Action: Make sure that the permissions on the file have not been changed
// so that the ORACLE user cannot open it.
09932, 00000, "Close of ORACLE password file failed."
// *Cause: An attempt to close a password file failed.
// *Action: Check the UNIX error number for the specific reason.
09933, 00000, "Deletion of old password file failed."
// *Cause: The removal of the old password file failed.
// *Action: Check the UNIX error number for the specific reason.
09934, 00000, "Link of current password file to old failed."
// *Cause: ORACLE was unable to create a link so that the old password file
// could be saved.
// *Action: Check the UNIX error number for the specific reason.
09935, 00000, "Unlink of current password file failed."
// *Cause: ORACLE was unable to complete the saving of the current password
// file.
// *Action: Check the UNIX error number for the specific reason.
09936, 00000, "Open of ORACLE password file for write failed."
// *Cause: ORACLE was unable to create a password file.
// *Action: Check the UNIX error number for the specific reason.
09937, 00000, "Chmod of ORACLE password file failed."
// *Cause: ORACLE was unable to change a password file to be readonly.
// *Action: Check the UNIX error number for the specific reason.
09938, 00000, "Save of signal handlers failed."
// *Cause: ORACLE was unable to save the previous values of selected
// signal handlers.
// *Action: This is an internal error. Contact ORACLE support.
09939, 00000, "Restoration of signal handlers failed."
// *Cause: ORACLE was unable to restore the previous values of selected
// signal handlers.
// *Action: This is an internal error. Contact ORACLE support.
09940, 00000, "ORACLE password file header is corrupt"
// *Cause: The header of one of the password files was not in the format that
// ORACLE expected.
// *Action: Check the headers of both files. The header should be in the format
// "FILE VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N"
// where N is a number.
// Remove the corrupt file(s) and re-run "orapasswd".
09941, 00000, "Version of orapasswd or installer is older than file."
// *Cause: The version of orapasswd or installer that is being run is older
// than that of the ORACLE password file. Since the file version is
// only changed when the format is changed, this error means that the
// executable is using a different format than that with which the
// file was created.
// *Action: Run a version of the installer or orapasswd whose version is the
// same or later than that of the file.
09942, 00000, "Write of ORACLE password file header failed."
// *Cause: The attempt to write out the header of the ORACLE password file
// failed.
// *Action: Check the operating system error number. It is possible that the
// file system became full.
09943, 00000, "Allocation of memory for password list component failed."
// *Cause: When it is building a list of password file entries, ORACLE
// allocates memory for various components. One of the
// allocations failed.
// *Action: Check the operating system error number. The system has
// probably run out of memory.
09944, 00000, "Password entry is corrupt."
// *Cause: An entry in an ORACLE password file was not in the format that
// ORACLE expected.
// *Action: Removed the corrupt file(s) and re-run "orapasswd."
09945, 00000, "Unable to initialize the audit trail file"
// *Cause: ORACLE unable to write header information to the file being
// used as the audit trail.
// *Action: Check the UNIX error number for a possible operating system error.
// If there is no error, contact ORACLE customer support.
09946, 00000, "File name too long for buffer"
// *Cause: The buffer that was to be used to hold a file name was
// determined to be too short for the generated name. This will
// happen if the translated name for either a trace file or an
// audit file is longer than the maximum allowed, which on many
// ports is 256 characters.
// *Action: Use a shorter file name.
09947, 00000, "Unable to allocate connection attributes structure"
// *Cause: ORACLE was not able to allocate the memory needed to hold
// the attributes of the SQL*Net connection. The "Additional
// Information" field holds the number of bytes that ORACLE
// attempted to allocate.
// *Action: Check the UNIX error number. It is probable that the system has
// run out of memory. If there is no error, contact ORACLE
// customer support.
09948, 00000, "Process information label retrieval failed."
// *Cause: ORACLE was unable to get the information label for a process.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact ORACLE support.
09949, 00000, "Unable to get client operating system privileges"
// *Cause: ORACLE was unable to get the operating system privileges for the
// client process.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact ORACLE support.
09950, 00000, "Unable to get server operating system privileges"
// *Cause: ORACLE was unable to get its privileges from the operating system.
// *Action: This is an error that should never happen. Contact ORACLE customer
// support.
09951, 00000, "Unable to create file"
// *Cause: ORACLE was unable to create a file.
// *Action: Check the UNIX error number for a possible operating system
// failure. If there is no error, contact ORACLE support.
09952, 00000, "scgcmn: lk_open_convert unexpected return: open failed"
// *Cause: The distributed lock manager returned an unexpected value
// *Action: Check for system error message and
// refer to the distributed lock manager documentation
// or contact your customer support representative.
09953, 00000, "scggc: unexpected return of a lock convert"
// *Cause: The distributed lock manager returned an unexpected value
// *Action: Check for lock manager error message and refer to DLM documentation
// refer to the distributed lock manager documentation
// or contact your customer support representative.
09954, 00000, "scgcc: unexpected return status to callback of lock close"
// *Cause: The distributed lock manager returned an unexpected value
// *Action: Check for lock manager error message and refer to DLM documentation
// refer to the distributed lock manager documentation
// or contact your customer support representative.
09955, 00000, "scgcan: unexpected return status when canceling a lock"
// *Cause: DLM system service x returned an unexpected value
// *Action: Check for system error message and refer to DLM documentation
// refer to the distributed lock manager documentation
// or contact your customer support representative.
09956, 00000, "scgcm: unexpected lock status condition"
// *Cause: A global locking system service returned an unexpected value.
// *Action: Check for system error message (if any) and refer to
// refer to the distributed lock manager documentation
// or contact your customer support representative.
09957, 00000, "Unable to send termination request to IMON"
// *Cause: The attempt to send a termination signal to IMON failed.
// *Action: This is an internal error, contact ORACLE support.
09958, 00000, "IMON: two processes with the same ORACLE pid are active"
// *Cause: The IMON process was unable to add an entry for a server process
// because another active process occupies the slot.
// *Action: This is an internal error, contact ORACLE support.
09959, 00000, "IMON: deletion of a process failed."
// *Cause: The IMON process was unable to delete a server process from its
// process ID array because no entry for the process could be found.
// *Action: This is an internal error, contact ORACLE support.
09960, 00000, "Unable to establish signal handler for termination signal"
// *Cause: ORACLE was unable to set up a handler for the signal used to
// notify it that the instance was shutting down.
// *Action: This is an internal error, contact ORACLE support.
09961, 00000, "Unable to restore termination signal handler"
// *Cause: ORACLE failed to set the handler for the termination signal to its
// previous value.
// *Action: This is an internal error, contact ORACLE support.
09962, 00000, "lk_group_create error in scggrc"
// *Cause:
// *Action:
09963, 00000, "lk_group_attach error in scggra"
// *Cause:
// *Action:
09964, 00000, "lk_group_detach error in scggrd"
// *Cause:
// *Action:
09966, 00000, "falure in translation while expanding ?/dbs/lk for lock file"
// *Cause: Oracle failed to translate ?/dbs/lk, when creating a file name for
// the database mount lock or the instance startup/shutdown lock.
// *Action: Check additional return errors for more information.
09967, 00000, "unable to create or open lock file"
// *Cause: Oracle failed, when making an open system call, inorder to acquire
// a file lock used by the database mount lock or the instance
// startup/shutdown lock.
// *Action: Check errno for more information.
09968, 00000, "unable to lock file"
// *Cause: The system call for locking a file returned an error when trying
// to acquire a database mount lock or the instance startup/shutdown
// lock.
// *Action: Check errno for more information.
09969, 00000, "unable to close or remove lock file"
// *Cause: The close system call or unlink system call returned an error.
// *Action: Check errno for more information.
09974, 00000, "skxfidini: Error Initializing SDI Channel"
// *Cause: The process was unable to initialize the SDI channel properly.
// *Action: Correct the operating system error and retry the operation.
/
09975, 00000, "kxfspini: Error Initializing SDI Process"
// *Cause: The process was unable to attach to the SDI channel.
// *Action: Verify that the SDI process specific limits correctly configured.
// Correct the operating system error and retry the operation.
/
09976, 00000, "skxfqdini: Error Creating Port"
// *Cause: The process was unable to create a communications endpoint.
// *Action: Verify that the SDI port specific limits correctly configured.
// Correct the operating system error and retry the operation.
/
09977, 00000, "skxfqhini: Error Connecting"
// *Cause: The process was unable to connect to another endpoint.
// *Action: Verify that the SDI port specific limits correctly configured.
// Check that the other node(s) is part of the cluster and operating
// properly. Correct the operating system error and retry the
// operation.
/
09978, 00000, "skxfqhdel: Error Disconnecting from another endpoint."
// *Cause: The process was unable to disconnect cleanly from another endpoint.
// *Action: Check that the other node(s) are part of the cluster and operating
// properly. Check the instance and processes on the other node(s).
// Correct the operating system error and retry the operation.
/
09979, 00000, "skxfqhsnd: Error Sending a message to another endpoint"
// *Cause: The process was unable to send a message to an existing endpoint.
// *Action: Check that the other node(s) are part of the cluster and operating
// properly. Check the instance and processes on the other node(s).
// Correct the operating system error and retry the operation.
/
09980, 00000, "skxfqdrcv: Error Receiving a message from another endpoint"
// *Cause: The process encountered an error while trying to receive a message.
// *Action: Check that the other node(s) are part of the cluster and operating
// properly. Check the instance and processes on the other node(s).
// Correct the operating system error and retry the operation.
/
09981, 00000, "skxfqdreg: Error Adding a page to the SDI buffer pool"
// *Cause: The process was unable to add a page to the SDI buffer pool.
// *Action: Correct the operating system error and retry the operation.
/
09982, 00000, "skxfqddrg: Error Removing a page from the SDI buffer pool"
// *Cause: The process was unable to remove a page to the SDI buffer pool.
// *Action: Correct the operating system error and retry the operation.
/
09983, 00000, "skxfidsht: Error shutting down SDI channel"
// *Cause: The process was unable shut down the SDI channel
// *Action: Check the SDI persistent resources using SDI tools.
// Verify that all processes exited cleanly and the instance
// is safely shut down. Delete any remaining
// SDI channel IDs associated with the current instance.
/
09984, 00000, "SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not exist"
// *Cause: file does not exist or is not accessible
// *Action: Restart the instance to create the SGA definition file.
/
09985, 00000, "SGA definition file could not be read"
// *Cause: UNIX read() operation failed
// *Action: check errno and take appropriate action.
/
09986, 00000, "wrong number of bytes read from SGA definition file"
// *Cause: Struct skgmsdef size differs from no. of bytes read from SGA file
// *Action: Compare the two struct definitions and ensure that they are
// identical in size and structure.
/
09987, 00000, "unable to attach to SGA in READ-ONLY mode"
// *Cause: The instance is not up, or SGA segments are not read-accessible
// *Action: Verify that the instance is up and read permissions for the
// SGA segments are set.
/
09988, 00000, "error while detaching SGA"
// *Cause: skgmsdef struct is corrupted and/or segment addresses are modified
// *Action: Safely shut down instance and mount SGA segments again.
/
09989, 00000, "attempt to use invalid skgmsdef struct pointer"
// *Cause: Pointer to skgmsdef struct used without validating it
// *Action: Assign a valid address to the skgmsdef struct pointer before
// using it.
/
/ Pseudo-error debugging events:
/ Error codes 10000 .. 10999 are reserved for debug event codes that are
/ not really errors.
/
// NLS_DO_NOT_TRANSLATE [10000,10999] - Tag to indicate messages should
// not be translated.
10000, 00000, "control file debug event, name 'control_file'"
// *Document: NO
// *Cause:
// *Action:
10001, 00000, "control file crash event1"
// *Document: NO
// *Cause:
// *Action:
10002, 00000, "control file crash event2"
// *Document: NO
// *Cause:
// *Action:
10003, 00000, "control file crash event3"
// *Document: NO
// *Cause:
// *Action:
10004, 00000, "block recovery testing - internal error"
// *Document: NO
// *Cause:
// *Action:
10005, 00000, "trace latch operations for debugging"
// *Document: NO
// *Cause:
// *Action: Enable tracing for various latch operations
// *Comment:
// level 1 - trace latch gets and frees
// level 2 - protect/unprotect latch recovery areas
// level 4 - trace multiple posts by processes when latch is freed
// level 8 - signal error on bad latch waits
//
10006, 00000, "block recovery testing - external error"
// *Document: NO
// *Cause:
// *Action:
10007, 00000, "log switch debug crash after new log select, thread %s"
// *Document: NO
// *Cause:
// *Action: level 1 - closed thread only
// level 2 - open thread only
// level 3 - open or closed thread
10008, 00000, "log switch debug crash after new log header write, thread %s"
// *Document: NO
// *Cause:
// *Action: level 1 - closed thread only
// level 2 - open thread only
// level 3 - open or closed thread
10009, 00000, "log switch debug crash after old log header write, thread %s"
// *Document: NO
// *Cause:
// *Action: level 1 - closed thread only
// level 2 - open thread only
// level 3 - open or closed thread
10010, 00000, "Begin Transaction"
// *Cause:
// *Action:
10011, 00000, "End Transaction"
// *Cause:
// *Action:
10012, 00000, "Abort Transaction"
// *Cause:
// *Action:
10013, 00000, "Instance Recovery"
// *Cause:
// *Action:
10014, 00000, "Roll Back to Save Point"
// *Cause:
// *Action:
10015, 00000, "Undo Segment Recovery"
// *Cause:
// *Action:
10016, 00000, "Undo Segment extend"
// *Cause:
// *Action:
10017, 00000, "Undo Segment Wrap"
// *Cause:
// *Action:
10018, 00000, "Data Segment Create"
// *Cause:
// *Action:
10019, 00000, "Turn off data/space search cache"
// *Cause:
// *Action:
10020, 00000, "partial link restored to linked list (KSG)"
// *Cause:
// *Action:
10021, 00000, "KST event to trace control file header writes and reads"
// *Cause:
// *Action: Not set by default.
10022, 00000, "trace ktsgsp"
// *Cause:
// *Action:
10023, 00000, "Create Save Undo Segment"
// *Cause:
// *Action:
10024, 00000, "Write to Save Undo"
// *Cause:
// *Action:
10025, 00000, "Simulate block recovery errors"
// *Cause:
// *Document: NO
// *Action: The level is a bitmask that can be used as follows:
// 0x0001 -- Corruption on first attempt to get previous block version
10026, 00000, "Apply Save Undo"
// *Cause:
// *Action:
10027, 00000, "Specify Deadlock Trace Information to be Dumped"
// *Cause:
// *Action: The level is a bitmask that can be used as follows:
// 0x01 - Do NOT produce a processstate (default is to dump this)
// 0x02 - Dump a systemstate
// 0x04 - Dump short stacks of all processes
//
10028, 00000, "Dump trace information during lock / resource latch cleanup"
// *Cause:
// *Action: The level is a bitmask that can be used as follows:
// 0x01 - Dump information during resource cleanup
// 0x02 - Dump information during lock cleanup
//
10029, 00000, "session logon (KSU)"
// *Cause:
// *Action:
10030, 00000, "session logoff (KSU)"
// *Cause:
// *Action:
10031, 00000, "sort debug event (S*)"
// *Cause:
// *Document: NO
// *Action: Set this event only under the supervision of Oracle development.
// Trace level is a bitfield.
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 Trace sort auto memory management requirements
// 0x0002 Dump sort subheaps before freeing or resetting
// 0x0004 Trace use of new vs old sort
// 0x0008 Reserved for sort IO tracing
// 0x0010 Disable storing duplicates in linked list (also disables
// part of top n rank optimization)
// 0x0020 trace and debug sort spill statistics
// 0x0040 sleep 2 sec after each sort run creation for QA testing
// 0x0080 Trace cluster-by-rowid (CBRID) sort
//
10032, 00000, "sort statistics (SOR*)"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// Trace level is a bitfield.
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x01 Output sort statistics in the trace file at the end of sort.
// 0x02 Level 1 plus print more information as the sort progresses.
// 0x04 Level 2 plus dump extra information (track IOs).
//
10033, 00000, "sort run information (SRD*/SRS*)"
// *Cause:
// *Action:
10034, 00000, "access path analysis (APA*)"
// *Cause:
// *Action:
10035, 00000, "Write parse failures to alert log file"
// *Cause:
10036, 00000, "create remote row source (QKANET)"
// *Cause:
// *Action:
10037, 00000, "allocate remote row source (QKARWS)"
// *Cause:
// *Action:
10038, 00000, "dump row source tree (QBADRV)"
// *Cause:
// *Action:
10039, 00000, "type checking (OPITCA)"
// *Cause:
// *Action:
10040, 00000, "disable result-cache"
// *Cause:
// *Action:
10041, 00000, "dump undo records skipped"
// *Cause:
// *Action:
10042, 00000, "file header reads return youngest mirror"
// *Cause:
// *Action:
10043, 00000, "check consistency of owner/waiter/converter lists in KSQ"
// *Cause:
// *Action:
10044, 00000, "free list undo operations"
// *Cause:
// *Action:
10045, 00000, "free list update operations - ktsrsp, ktsunl"
// *Cause:
// *Action:
10046, 00000, "enable SQL statement timing"
// *Cause:
// *Action:
10047, 00000, "trace switching of sessions"
// *Cause:
// *Action:
10048, 00000, "Undo segment shrink"
// *Cause:
// *Action:
10049, 00000, "protect library cache memory heaps"
// *Cause:
// *Action: Use the OS memory protection (if available) to protect library
// cache memory heaps that are pinned.
10050, 00000, "sniper trace"
// *Cause:
// *Action:
10051, 00000, "trace OPI calls"
// *Cause:
// *Action:
10052, 00000, "don't clean up obj$"
// *Cause:
// *Action:
10053, 00000, "CBO Enable optimizer trace"
// *Cause:
// *Action:
10054, 00000, "CBO Enable optimizer trace for recursive statement (RPI)"
// *Cause:
// *Action:
10055, 00000, "Rowsets: turn off rowsets for various operations"
// *Document: NO
// *Cause: N/A
// *Action: Turns off rowsets for various operations
// Level:
// 0x00000001 - turn off for table scan
// 0x00000002 - turn off for hash join consume
// 0x00000004 - turn off for hash join produce
// 0x00000008 - turn off for group by
// 0x00000010 - turn off for sort
// 0x00000020 - turn off for table-queue out
// 0x00000040 - turn off for table-queue in
// 0x00000080 - turn off for identity
// 0x00000100 - turn off for granule iterator
// 0x00000200 - turn off for EVA functions
// 0x00000400 - turn off for PL/SQL
// 0x00000800 - turn off for upgrade
// 0x00001000 - turn off for database startup
// 0x00002000 - turn off for blobs and clobs
// 0x00004000 - turn off for tracing row source
// 0x00008000 - turn off rowset information in explain plan
// 0x00010000 - disable hash join rowsets fast path
// 0x00020000 - turn off for bloom create
// 0x00040000 - turn off for bloom use
// 0x00080000 - disable prefetch for hash join
// 0x00100000 - disable prefetch for bloom
// 0x00200000 - disable semi blocking hash join
// 0x00400000 - turn off rowset for fixed table
// 0x00800000 - turn off rowset for view
// 0x01000000 - turn off rowset for filter
// 0x02000000 - disable producing rowsets in scan with one-row eva
// 0x04000000 - turn off rowsets for non-inner hash join
// 0x08000000 - turn off rowsets for update
// 0x10000000 - turn off rowsets for delete
// 0x20000000 - disable prefetch for hash aggregation
// 0x40000000 - turn off rowsets for window function
// 0x80000000 - turn off rowsets for count
//
10056, 00000, "dump analyze stats (kdg)"
// *Cause:
// *Action:
10057, 00000, "suppress file names in error messages"
// *Cause:
// *Action:
10058, 00000, "use table scan cost in tab$.spare1"
// *Cause:
// *Action:
10059, 00000, "simulate error in logfile create/clear"
// *Cause:
// *Action:
10060, 00000, "CBO Enable predicate dump"
// *Cause:
// *Action:
10061, 00000, "disable SMON from cleaning temp segment"
// *Cause:
// *Action:
10062, 00000, "disable usage of OS Roles in osds"
// *Cause:
// *Action:
10063, 00000, "disable usage of DBA and OPER privileges in osds"
// *Cause:
// *Action:
10064, 00000, "thread enable debug crash level %s, thread %s"
// *Document: NO
// *Cause:
// *Action: level 1 - after new current log header written
// level 2 - after current log committed
// level 3 - after redo generation complete
10065, 00000, "limit library cache dump information for state object dump"
// *Document: NO
// *Cause:
// *Action: level 1 - minimal (only the address of state objects)
// level 2 - little more (no object details)
// level 3 - normal
10066, 00000, "simulate failure to verify file"
// *Document: NO
// *Cause:
// *Action: level is file number to fail verification
10067, 00000, "force redo log checksum errors - block number"
// *Document: NO
// *Cause:
// *Action: level is block number to corrupt
10068, 00000, "force redo log checksum errors - file number"
// *Document: NO
// *Cause:
// *Action: level is file number to corrupt
10069, 00000, "Flashback images for offline file %s are lost"
// *Document: NO
// *Cause: There was an offline data file in the flashback set which was
// not recovered. The current operation blocks further
// attempts to generate flashback before images for that file.
// *Action: Either bring the file online and recover it, or take it offline
// with the FOR DROP option.
10070, 00000, "force datafile checksum errors - block number"
// *Document: NO
// *Cause:
// *Action: level is block number to corrupt
10071, 00000, "force datafile checksum errors - file number"
// *Document: NO
// *Cause:
// *Action: level is file number to corrupt
10072, 00000, "local tempspace tracing - recovery layer"
// *Document: NO
// *Cause:
// *Action: Enable local tempspace tracing in recovery layer
10073, 00000, "latch cleanup tracing"
// *Document: NO
// *Cause:
// *Action: Enable latch cleanup tracing.
// *Comment:
// level 1 - PMON cleanup, in-flux latches only
// level 2 - PMON cleanup, all latches
// level 3 - all cleanup
//
10074, 00000, "default trace function mask for kst"
// *Cause:
// *Action:
10075, 00000, "CBO Disable outer-join to regular join conversion"
// *Cause:
// *Action:
10076, 00000, "CBO Enable cartesian product join costing"
// *Cause:
// *Action:
10077, 00000, "CBO Disable view-merging optimization for outer-joins"
// *Cause:
// *Action:
10078, 00000, "CBO Disable constant predicate elimination optimization"
// *Cause:
// *Action:
/
10079, 00000, "trace data sent/received via SQL*Net"
// *Cause:
// *Action: level 1 - trace network ops to/from client
// level 2 - in addition to level 1, dump data
// level 4 - trace network ops to/from dblink
// level 8 - in addition to level 4, dump data
/
10080, 00000, "dump a block on a segment list which cannot be exchanged"
// *Cause:
// *Action:
/ At level > 1, dump the block
/ At level > 5, dump the stack
/ At level > 10, unlink the block
10081, 00000, "segment High Water Mark has been advanced"
// *Cause:
// *Action:
10082, 00000, "free list head block is the same as the last block"
// *Cause:
// *Action:
/ At level > 1, dump the block
/ At level > 5, dump the stack
10083, 00000, "Trace IMCDT in LIMITED mode"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// Trace level is a bitfield.
10084, 00000, "free list becomes empty"
// *Cause:
// *Action:
10085, 00000, "free lists have been merged"
// *Cause:
// *Action:
10086, 00000, "CBO Enable error if kko and qka disagree on oby sort"
// *Cause:
// *Action:
10087, 00000, "disable repair of media corrupt data blocks"
// *Document: NO
// *Cause:
// *Action:
10088, 00000, "CBO Disable new NOT IN optimization"
// *Document: NO
// *Cause:
// *Action:
10089, 00000, "CBO Disable index sorting"
// *Document: NO
// *Cause:
// *Action:
10090, 00000, "invoke other events before crash recovery"
// *Document: NO
// *Cause:
// *Action:
10091, 00000, "CBO Disable constant predicate merging"
// *Cause:
// *Action:
10092, 00000, "CBO Disable hash join"
// *Cause:
// *Action:
10093, 00000, "CBO Enable force hash joins"
// *Cause:
// *Action:
10094, 00000, "before resizing a data file"
// *Document: NO
// *Cause:
// *Action:
10095, 00000, "dump debugger commands to trace file"
// *Document: NO
// *Cause:
// *Action:
10096, 00000, "after the cross instance call when resizing a data file"
// *Document: NO
// *Cause:
// *Action:
10097, 00000, "after generating redo when resizing a data file"
// *Document: NO
// *Cause:
// *Action:
10098, 00000, "after the OS has increased the size of a data file"
// *Document: NO
// *Cause:
// *Action:
10099, 00000, "after updating the file header with the new file size"
// *Document: NO
// *Cause:
// *Action:
10100, 00000, "after the OS has decreased the size of a data file"
// *Document: NO
// *Cause:
// *Action:
10101, 00000, "DBWR refresh fails on cross instance resize call"
// *Document: NO
// *Cause:
// *Action:
10102, 00000, "switch off anti-joins"
// *Cause:
// *Action:
10103, 00000, "CBO Disable hash join swapping"
// *Cause:
// *Action:
10104, 00000, "dump hash join statistics to trace file"
// *Cause:
// *Action:
10105, 00000, "CBO Enable constant pred trans and MPs w WHERE-clause"
// *Cause:
// *Action:
10106, 00000, "CBO Disable evaluating correlation pred last for NOT IN"
// *Cause:
// *Action:
10107, 00000, "CBO Always use bitmap index"
// *Cause:
// *Action:
10108, 00000, "CBO Don't use bitmap index"
// *Cause:
// *Action:
10109, 00000, "CBO Disable move of negated predicates"
// *Cause:
// *Action:
10110, 00000, "CBO Try index rowid range scans"
// *Cause:
// *Action:
10111, 00000, "Bitmap index creation switch"
// *Cause:
// *Action:
10112, 00000, "Bitmap index creation switch"
// *Cause:
// *Action:
10113, 00000, "Bitmap index creation switch"
// *Cause:
// *Action:
10114, 00000, "Bitmap index creation switch"
// *Cause:
// *Action:
10115, 00000, "CBO Bitmap optimization use maximal expression"
// *Cause:
// *Action:
10116, 00000, "CBO Bitmap optimization switch"
// *Cause:
// *Action:
10117, 00000, "CBO Disable new parallel cost model "
// *Cause:
// *Action:
10118, 00000, "CBO Enable hash join costing "
// *Cause:
// *Action:
10119, 00000, "QKA Disable GBY sort elimination"
// *Cause:
// *Action:
10120, 00000, "generate relative file # different from absolute"
// *Cause:
// *Action:
10121, 00000, "CBO Don't sort bitmap chains"
// *Cause:
// *Action:
10122, 00000, "Disable transformation of count(col) to count(*)"
// *Cause:
// *Action:
10123, 00000, "Rowsets: turn off rowsets for various operations"
// *Document: NO
// *Cause: N/A
// *Action: Turns off rowsets for various operations
// Level:
// 0x00000001 - turn off for top select
//
10124, 00000, "Force creation of segmented arrays by kscsAllocate"
// *Cause:
// *Action:
10125, 00000, "Disable remote sort elimination"
// *Cause:
// *Action:
10126, 00000, "Debug oracle java xa"
// *Cause:
// *Action:
10127, 00000, "Disable remote query block operation"
// *Cause:
// *Action:
10128, 00000, "Dump Partition Pruning Information"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 dump pruning decriptor for each partitioned object
// 0x0002 dump partition iterators
// 0x0004 dump optimizer decisions about partition-wise join
// 0x0008 dump rowid range scan pruning information
10129, 00000, "Alter histogram lookup for remote queries"
// *Cause:
// *Action:
10130, 00000, "sort disable readaheads"
// *Cause:
// *Action:
10131, 00000, "CONNECT BY debug event"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// Trace level is a bit field.
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 Enable use of CONNECT BY cost-based transformation for
// queries with subqueries in the START WITH clause
// 0x0002 Enable use of CONNECT BY cost-based transformation for
// queries with subqueries in the CONNECT BY clause
// 0x0004 Reserved for filtering only debugging mode (print rows
// produced by filtering stage)
//
10132, 00000, "dump plan after compilation"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10133, 00000, "testing for SQL Memory Management"
// *Cause:
// *Action: never set this event
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 do not unregister work areas at instance level
10134, 00000, "tracing for SQL Memory Management for session"
// *Cause:
// *Action: never set this event
//
// This event can be turned on globally by seting trace name sqlmem_tracing
// with the same set of levels with bit one set to 1
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 Not used (used for global setting)
// 0x0002 IMM level register/unregister
10135, 00000, "CBO do not count 0 rows partitions"
// *Cause:
// *Action:
10136, 00000, "CBO turn off fix for bug 1089848"
// *Cause:
// *Action:
10137, 00000, "CBO turn off fix for bug 1344111"
// *Cause:
// *Action:
10138, 00000, "CBO turn off fix for bug 1577003"
// *Cause:
// *Action:
10139, 00000, "CBO turn off fix for bug 1386119"
// *Cause:
// *Action:
10140, 00000, "CBO turn off fix for bug 1332980"
// *Cause:
// *Action:
10141, 00000, "CBO disable additional keys for inlist in bitmap optimization"
// *Cause:
// *Action:
10142, 00000, "CBO turn off advanced OR-expansion checks"
// *Cause:
// *Action:
10143, 00000, "CBO turn off hints"
// *Cause:
// *Action:
10144, 00000, "CBO turn off cost based selection of bji over bsj subquery"
// *Cause:
// *Action:
10145, 00000, "test auditing network errors"
// *Cause:
// *Action:
10146, 00000, "enable Oracle TRACE collection"
// *Cause:
// *Action:
// *Comment: This event is obsoleted, and can be reused for some other purpose
// although some customer applications which used to rely on
// Oracle Trace may still have it enabled by mistake
10147, 00000, "enable join push through UNION view"
// *Cause:
// *Action:
10148, 00000, "Quarantine trace event"
// *Document: NO
// *Cause:
// *Action:
10149, 00000, "allow the creation of constraints with illegal date constants"
// *Cause:
// *Action:
10150, 00000, "import exceptions"
// *Document: NO
// *Cause:
// *Action: This should never be set by users. It is used by import to
// allow certain commands to succeed, when for normal users they
// would fail. An example is to allow grants on invalid views.
10152, 00000, "CBO don't consider function costs in plans"
// *Cause:
// *Action:
10153, 00000, "Switch to use public synonym if private one does not translate"
// *Cause:
// *Action:
10154, 00000, "Switch to disallow synonyms in DDL statements"
// *Cause:
// *Action:
10155, 00000, "CBO disable generation of transitive OR-chains"
// *Cause:
// *Action:
10156, 00000, "CBO disable index fast full scan"
// *Cause:
// *Action:
10157, 00000, "CBO disable index access path for in-list"
// *Cause:
// *Action:
10158, 00000, "CBO preserve predicate order in post-filters"
// *Cause:
// *Action:
10159, 00000, "CBO disable order-by sort pushdown into domain indexes"
// *Cause:
// *Action:
10160, 00000, "CBO disable use of join index"
// *Cause:
// *Action:
10161, 00000, "CBO recursive semi-join on/off-switch"
// *Cause:
// *Action:
10162, 00000, "CBO join-back elimination on/off-switch"
// *Cause:
// *Action:
10163, 00000, "CBO join-back elimination on/off-switch"
// *Cause:
// *Action:
10164, 00000, "CBO disable subquery-adjusted cardinality fix"
// *Cause:
// *Action:
10165, 00000, "mark session for special handling during instance administration"
// *Document: NO
// *Cause:
// *Action: Turn on this event in a session to mark the session as special
// so that it can be either killed or ignored during instance
// administration operations such as shutdown normal and standby
// role transitions.
//
// It is provided for the Oracle Enterprise Manager an other similar
// tools.
//
// The level is interpreted as follows
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0 Treat this session as a normal session. This clears the
// special bits which may have been set by other levels of this
// event.
// 1 Kill this session during shutdown normal
// 2 Ignore this session during database close
// 3 During a standby database role transition, the switchover
// readiness check ignores this session because this session will
// be gone when the switchover occurs.
// 4 Kill this session during the physical standby database role
// transition even if the session preserving feature is enabled.
// >= 5 Reserved for future use
10166, 00000, "trace long operation statistics updates"
// *Cause:
// *Action:
10167, 00000, "CBO use old index MIN/MAX optimization"
// *Cause:
// *Action:
10168, 00000, "CBO disable single-table predicate predicate generation"
// *Cause:
// *Action:
10169, 00000, "CBO disable histograms for multi partitions"
// *Cause:
// *Action:
10170, 00000, "CBO use old bitmap costing"
// *Cause:
// *Action:
10171, 00000, "CBO disable transitive join predicates"
// *Cause:
// *Action:
10172, 00000, "CBO force hash join back"
// *Cause:
// *Action:
10173, 00000, "Dynamic Sampling time-out error"
// *Cause:
// *Action:
10174, 00000, "view join-back elimination switch"
// *Cause:
// *Action:
10175, 00000, "CBO star transformation switch"
// *Cause:
// *Action:
10176, 00000, "CBO colocated join switch"
// *Cause:
// *Action:
10177, 00000, "CBO colocated join switch"
// *Cause:
// *Action:
10178, 00000, "CBO turn off hash cluster filtering through memcmp"
// *Cause:
// *Action:
10179, 00000, "CBO turn off transitive predicate replacement"
// *Cause:
// *Action:
10180, 00000, "temp table transformation print error messages"
// *Cause:
// *Action:
10181, 00000, "CBO disable multi-column in-list processing"
// *Cause:
// *Action:
10182, 00000, "CBO disable generation of implied predicates"
// *Cause:
// *Action:
10183, 00000, "CBO disable cost rounding"
// *Cause:
// *Action:
10184, 00000, "CBO disable OR-exp if long inlist on bitmap column"
// *Cause:
// *Action:
10185, 00000, "CBO force index joins"
// *Cause:
// *Action:
10186, 00000, "CBO disable index join"
// *Cause:
// *Action:
10187, 00000, "CBO additional index join switch"
// *Cause:
// *Action:
10188, 00000, "CBO additional index join switch"
// *Cause:
// *Action:
10189, 00000, "CBO turn off FFS null fix"
// *Cause:
// *Action:
10190, 00000, "Analyze use old frequency histogram collection and density"
// *Cause:
// *Action:
10191, 00000, "Avoid conversion of in-lists back to OR-expanded form"
// *Cause:
// *Action:
10192, 00000, "nopushdown when number of groups exceed number of rows"
// *Cause:
// *Action:
10193, 00000, "Force repeatable sampling with specified seed"
// *Cause:
// *Action:
10194, 00000, "CBO disable new LIKE selectivity heuristic"
// *Cause:
// *Action:
10195, 00000, "CBO don't use check constraints for transitive predicates"
// *Cause:
// *Action:
10196, 00000, "CBO disable index skip scan"
// *Cause:
// *Action:
10197, 00000, "CBO force index skip scan"
// *Cause:
// *Action:
10199, 00000, "set parameter in session"
// *Cause:
// *Action:
10200, 00000, "consistent read buffer status"
// *Cause:
// *Action:
10201, 00000, "consistent read undo application"
// *Cause:
// *Action:
10202, 00000, "consistent read block header"
// *Cause:
// *Action:
10203, 00000, "block cleanout"
// *Cause:
// *Action:
10204, 00000, "signal recursive extend"
// *Cause:
// *Action:
10205, 00000, "row cache debugging"
// *Cause:
// *Action:
/ At level 1, KQR will dump out latch clean-up debugging traces.
/ At level 2, KQR will dump out bootstrap debugging traces.
/ At level 3, KQR will invalidate, remove from the cache and put 0xff's
/ in row cache objects that are not currently locked.
10206, 00000, "transaction table consistent read"
// *Cause:
// *Action:
10207, 00000, "consistent read transactions' status report"
// *Cause:
// *Action:
10208, 00000, "consistent read loop check"
// *Cause:
// *Action:
10209, 00000, "enable simulated error on control file"
// *Cause:
// *Action:
/ Enables event 10214 to signal an error for a specific file. Level
/ is the number of the file to enable them for (file number order from
/ INIT.ORA file). A level greater than the maximum control file multiplexing
/ factor will signal error for all files.
10210, 00000, "check data block integrity"
// *Cause:
// *Action:
10212, 00000, "check cluster integrity"
// *Cause:
// *Action:
10213, 00000, "crash after control file write"
// *Cause:
// *Action:
10214, 00000, "simulate write errors on control file"
// *Cause:
// *Action:
/ A level of 1-9 simulates write errors on physical blocks 1-9.
/ If level >= 10 every control file write will force an error.
10215, 00000, "simulate read errors on control file"
// *Cause:
// *Action:
/ For errors 10213,10214, and 10215
/ level 1 is for header
/ level 2 is for shared info
/ level >2 is any other block
/ No error 10214 will be simulated unless event 10209 is also set to enable
/ error simulation on that file
10216, 00000, "dump control file header"
// *Cause:
// *Action:
10217, 00000, "debug sequence numbers"
// *Cause:
// *Action:
10218, 00000, "dump uba of applied undo"
// *Cause:
// *Action:
10219, 00000, "monitor multi-pass row locking"
// *Cause:
// *Action:
10220, 00000, "show updates to the transaction table"
// *Cause:
// *Action:
10221, 00000, "show changes done with undo"
// *Cause:
// *Action:
10222, 00000, "row cache"
// *Cause:
// *Action:
10223, 00000, "transaction layer - turn on verification codes"
// *Cause:
// *Action:
10224, 00000, "index block split/delete trace"
// *Cause:
// *Action:
10225, 00000, "free/used extent row cache"
// *Cause:
// *Action:
10226, 00000, "trace CR applications of undo for data operations"
// *Cause:
// *Action:
10227, 00000, "verify (multi-piece) row structure"
// *Cause:
// *Action:
10228, 00000, "trace application of redo by kcocbk"
// *Cause:
// *Action:
10229, 00000, "simulate I/O error against datafiles"
// *Cause:
// *Action:
10230, 00000, "KSFD block repair test event"
// *Cause:
// *Action: Each level is dedicated to a particular ksfd client. When this
// event is set, clients corresponding to the level simulate block
// verification failure.
10231, 00000, "skip corrupted blocks on _table_scans_"
// *Cause:
// *Action: such blocks are skipped in table scans, and listed in trace files
10232, 00000, "dump corrupted blocks symbolically when kcbgotten"
// *Cause:
// *Action: puts corrupted block in trace file
10233, 00000, "skip corrupted blocks on index operations"
// *Cause:
// *Action: skip corrupted data and/or index blocks during index scans.
// information is logged to a trace file.
10234, 00000, "trigger event after calling kcrapc to do redo N times"
// *Document: NO
// *Cause:
// *Action: creates a file named 'crash'
10235, 00000, "check memory manager internal structures"
// *Cause:
// *Action:
10236, 00000, "dump redo on object no. or block type mismatch errors 1410/8103"
// *Document: NO
// *Cause:
// *Action:
10237, 00000, "simulate ^C (for testing purposes)"
// *Cause:
// *Action:
10238, 00000, "instantiation manager"
// *Cause:
// *Action:
10239, 00000, "multi-instance library cache manager"
// *Cause:
// *Action:
10240, 00000, "dump dba's of blocks that we wait for"
// *Cause:
// *Action:
10241, 00000, "remote SQL execution tracing/validation"
// *Cause:
// *Action:
// Level > 0 dump SQL generated for remote execution (OPIX)
// Level > 1 validate RPCs in SELECT statements
10242, 00000, "suppress OER 2063 (for testing distrib w/o different error log)"
// *Cause:
// *Action:
10243, 00000, "simulated error for test %s of K2GTAB latch cleanup"
// *Cause: levels 1..6 for insert, 7..11 for delete
// *Action:
10244, 00000, "make tranids in error msgs print as 0.0.0 (for testing)"
// *Cause: also makes "alter system enable distributed recovery" synchronous
// *Action:
10245, 00000, "Testing event used by server I/O ksfd/ksfq module"
// *Cause:
// *Action:
10246, 00000, "print trace of PMON actions to trace file"
// *Cause:
// *Action:
10247, 00000, "Turn on scgcmn tracing. (VMS ONLY)"
// *Cause:
// *Action:
/
/ LEVEL ACTION
/---------------------------------------------------------------------------
/ >= 1 Print lock name, action, mode, comp ast, bast, timeout, val?
/ >= 2 print Success code of request (NORMAL, SYNCH, or NOTQUEUED)
/ >= 3 print Value block
/ >= 5 Print delta CPU and elapsed times.
/ >= 100 stack dump at level 100-<given_level>.
10248, 00000, "turn on tracing for dispatchers"
// *Cause:
// *Action:
10249, 00000, "turn on tracing for multi-stated servers"
// *Cause:
// *Action:
10250, 00000, "Trace all allocate and free calls to the topmost SGA heap"
// *Cause:
// *Action:
10251, 00000, "check consistency of transaction table and undo block"
// MERGE: 10235 RENUMBERED TO 10251
// *Cause:
// *Action:
10252, 00000, "shared IO pool error simulation"
// *Cause:
// *Action: level specifies number of IOs after which an error will be simulated
10253, 00000, "limit SQL text returned from X$KGLNA[1]"
// *Cause:
// *Action: level specifies the maximum SQL string length to be returned
10254, 00000, "trace cross-instance calls"
// *Cause:
// *Action:
10255, 00000, "pl/sql parse checking"
// *Cause:
// *Action: sends all dml statements to pl/sql for parse and semantic check
10256, 00000, "shared server debug event"
// *Document: NO
// *Cause:
// *Action:
10257, 00000, "trace shared server load balancing"
// *Cause:
// *Action:
10258, 00000, "force shared servers to be chosen round-robin"
// *Cause:
// *Action:
10259, 00000, "get error message text from remote using explicit call"
// *Cause: for npigem coverage testing (normally called only for V5 remote)
// *Action:
10260, 00000, "PGA limit (%s MB) exceeded - process terminated"
// *Cause: The Resource Manager SESSION_PGA_LIMIT directive was exceeded
// because the process used too much program global area (PGA)
// memory.
// *Action: Reduce the complexity of the update or query, or contact your
// database administrator for more information.
10261, 00000, "limit the size of the PGA heap"
// *Cause: The limit was one kilobyte times the level of the event. If the
// PGA grows bigger than this, signal an external error.
// *Action:
10262, 00000, "Don't check for memory leaks"
// *Cause: Setting this event to level one causes memory leak checking to
// be disabled. Setting this event to any other non-zero number
// allows that number to be used as a threshold value when checking
// for memory leaks in the PGA, SGA, and UGA heaps.
// *Action:
10263, 00000, "Don't free empty PGA heap extents"
// *Cause: This is useful for debugging since watchpoints are lost on free
// *Action:
10265, 00000, "Keep random system generated output out of error messages"
// *Cause: so test system files don't diff
// *Action:
10266, 00000, "Trace OSD stack usage"
// *Cause: Porters should implement this to help them debug
// their stack implementations. It should be used in at least
// smcstk().
// *Action:
10267, 00000, "Inhibit KSEDMP for testing"
// *Cause: Some tests may generate internal or fatal errors on purpose.
/ This event can limit the size of tracefile produced for such
/ tests.
// *Action: LEVEL used by KSEDMP is one less than level of this event.
/
10268, 00000, "Don't do forward coalesce when deleting extents"
// *Cause: setting this event keeps kts from coalescing forward at each
// extent when dropping a temp segment.
// *Action:
10269, 00000, "Don't do coalesces of free space in SMON"
// *Cause: setting this event prevents SMON from doing free space coalesces
10270, 00000, "Debug shared cursors"
// *Cause: Enables debugging code in shared cursor management modules
// *Action:
10271, 00000, "distributed transaction after COLLECT"
// *Cause:
// *Action:
10272, 00000, "distributed transaction before PREPARE"
// *Cause:
// *Action:
10273, 00000, "distributed transaction after PREPARE"
// *Cause:
// *Action:
10274, 00000, "distributed transaction before COMMIT"
// *Cause:
// *Action:
10275, 00000, "distributed transaction after COMMIT"
// *Cause:
// *Action:
10276, 00000, "distributed transaction before FORGET"
// *Cause:
// *Action:
10277, 00000, "Cursor sharing (or not) related event (used for testing)"
// *Cause:
// *Action:
10278, 00000, "Internal testing"
// *Cause:
// *Action:
10279, 00000, "Simulate block corruption in kdb4chk"
// *Cause:
// *Action:
10280, 00000, "Internal testing - segmentation fault during crash recovery"
// *Cause:
// *Action:
10281, 00000, "maximum time to wait for process creation"
// *Cause: used to override the default SPMXWAIT, level = timeout in sec.
// *Action:
10282, 00000, "Inhibit signalling of other backgrounds when one dies"
// *Cause: Used in KSB
// *Action:
10284, 00000, "simulate zero/infinite asynch I/O buffering"
// *Cause: Used in KCF, level=1 out of space (red), level=2 infinite (green)
// *Action:
10285, 00000, "Simulate control file header corruption"
// *Cause:
// *Action: If set, will cause control file header verification to fail
10286, 00000, "Simulate control file open error"
// *Cause:
// *Action: If set, will cause the next control file open to have an error
10287, 00000, "Simulate archiver error"
// *Cause:
// *Action: If set, next archive log will generate error
10288, 00000, "Do not check block type in ktrget"
// *Cause:
// *Action: If set, don't do type check in ktrget. This is a work-around
// for databases that have 0 as block type in some data blocks.
10289, 00000, "Do block dumps to trace file in hex rather than fromatted"
// *Cause:
// *Action: If set, don't do formatted block dumps. This is a work-around
// for block dump routines that accvio when given badly corrupted
// blocks. It may also be useful for cases where the type is wrong.
10290, 00000, "Internal sequence tracing event"
// *Cause:
// *Action: Internal Event - Should not be set unless directed by RDBMS DEV
10291, 00000, "die in tbsdrv to test control file undo"
// *Cause:
// *Action: If this event is set, error OERI(10291) is signalled when
// issueing tablespace commands. The control file undo should be
// applied returning the control file to its previous state.
10292, 00000, "hang analysis trace event"
// *Document: NO
// *Cause:
// *Action: Enable validation of hang analysis callbacks
// *Comment: The following levels may be combined:
// 0x1 - dump errors to trace file through ksdwrf
// 0x2 - dump errors to trace file as ORA-600 + 0x1
// 0x4 - check for involuntary events without callbacks
10293, 0000, "trace log switch media recovery checkpoints"
// *Document: NO
// *Cause:
// *Action: Print alert log timestamps for the start and end of each log
// switch checkpoint during media recovery. This timing may prove
// useful in debugging recovery performance problems.
10294, 00000, "ksrpc tracing"
// *Cause:
// *Action: If this event is set then ksrpc module generates tracing on each
// remote transfer
10295, 00000, "die after file header update durning cf xact"
// *Document: NO
// *Cause:
// *Action: If this event is set then some file header updates will
// be followed by an error 10295 to abort the command before
// the control file xact commits.
10296, 00000, "disable ORA-379"
// *Cause:
// *Action: If this event is set then we will not signal ORA-379 for
// buffer cache deadlocks when all buffers in the cache
// are pinned.
10297, 00000, "shared I/O pool tracing"
// *Document: NO
// *Cause:
// *Action: If this event is set, then kcbi tracing is enabled. Internal use.
10298, 00000, "ksfd i/o tracing"
// *Cause:
// *Action: If this event is set then ksfd module generates tracing
// for each i/o request
10299, 00000, "Trace prefetch tracking decisions made by CKPT"
10300, 00000, "Distributed transaction tracing"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development
// *Comment: This event will trace the history of KTD actions
// level: 0 = always
/
/
// *Cause:
// *Action: If this event is set then the prefetch tracking decisions
// made by the CKPT process are traced. The trace output is
// written to that process' trace file.
10301, 0000, "Enable LCK timeout table consistency check"
// *Cause:
// *Action:
/
/ 10302 - 10318 Reserved for internal triggers
/
10302, 00000, "trace create or drop internal trigger"
// *Document: NO
// *Cause:
// *Action:
10303, 00000, "trace loading of library cache for internal triggers"
// *Document: NO
// *Cause:
// *Action:
10304, 00000, "trace replication trigger"
// *Document: NO
// *Cause:
// *Action:
10305, 00000, "trace updatable materialized view trigger"
// *Document: NO
// *Cause:
// *Action:
10306, 00000, "trace materialized view log trigger"
// *Document: NO
// *Cause:
// *Action:
10307, 00000, "trace RepCat execution"
// *Document: NO
// *Cause:
// *Action:
10308, 00000, "replication testing event"
// *Document: NO
// *Cause:
// *Action:
10309, 00000, "Trigger Debug event"
// *Document: NO
// *Cause:
// *Action:
// *Comment: This event replaces the earlier event number 10250
// which had multiple definitions
10310, 00000, "trace synchronous change table trigger"
// *Document: NO
// *Cause:
// *Action:
10311, 00000, "Disable Flashback Table Timestamp checking"
// *Document: NO
// *Cause:
// *Action:
10312, 00000, "Allow disable to log rows into the mapping table"
// *Document: NO
// *Cause:
// *Action:
10314, 00000, "Enable extra stats gathering for CR"
// *Document: NO
// *Cause:
// *Action:
10316, 00000, "Events for extensible txn header, non zero ext header size"
// *Document: NO
// *Cause:
// *Action:
10317, 00000, "Events for extensible txn header, zero ext header size"
// *Document: NO
// *Cause:
// *Action:
10318, 00000, "Trace extensible txn header movements"
// *Document: NO
// *Cause:
// *Action:
10319, 00000, "Trace PGA statistics maintenance"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 dump message in trace file when PGA stats are diverging
// 0x0002 trace top-level PGA allocation and deallocation
// 0x0004 always check if full/incremental stats are in sync
//
/
10320, 0000, "Enable data layer (kdtgrs) tracing of space management calls"
// *Cause:
// *Action:
/
10321, 0000, "Datafile header verification debug failure."
// *Document: NO
// *Cause:
// *Action: For testing purposes only. Simulates a data file header
// verification error. See levels below:
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 1 Verification error for all files
// 2 Verification error for non-system files
/
10322, 00000, "CBO don't simplify inlist predicates"
// *Cause:
// *Action:
10323, 0000, "before committing an add datafile command"
// *Cause:
// *Action:
10324, 0000, "Enable better checking of redo logs errors"
// *Cause:
// *Action: Raises internal errors when there are redo log errors
// *Comment: Raises internal errors when there are redo log errors
/
/ 10325 - 10335 reserved for recovery testing
/
10325, 0000, "Trace control file record section expand and shrink operations"
// *Document: NO
// *Cause:
// *Action: trace control file record section expand and shrink operations to
// the alert file
//
10326, 00000, "clear logfile debug crash at %s, log %s"
// *Document: NO
// *Cause:
// *Action: level 1 - after prepare, before clearing the log members
// level 2 - after clearing the log members, before final cf xaction
// level 3 - just before clearing member 1
// level 4 - just before clearing member 2
10327, 00000, "simulate ORA-00235 error for testing"
// *Document: NO
// *Cause:
// *Action:
//
10328, 00000, "disable first-to-mount split-brain error, for testing"
// *Document: NO
// *Cause:
// *Action: for testing only.
//
10329, 00000, "simulate out-of-memory error during first pass of recovery"
// *Document: NO
// *Cause:
// *Action: for testing only.
//
10330, 00000, "clear MTTR statistics in checkpoint progress record"
// *Document: NO
// *Cause:
// *Action: clear MTTR statistics in this thread
//
10331, 00000, "simulate resilvering during recovery"
// *Document: NO
// *Cause:
// *Action: for testing only.
//
10332, 00000, "force ALTER SYSTEM QUIESCE RESTRICTED command to fail"
// *Document: NO
// *Cause:
// *Action: for testing only.
//
10333, 00000, "dump MTTR statistics each time it is updated"
// *Document: NO
// *Cause:
// *Action: dump MTTR statistics in this thread each time it is updated
//
10334, 00000, "force FG to wait to be killed during MTTR advisory simulation"
// *Document: NO
// *Cause:
// *Action: for testing only.
//
10335, 00000, "trace database open status"
// *Document: NO
// *Cause:
// *Action: for debugging purpose
//
10336, 00000, "Do remote object transfer using remote SQL"
// *Cause:
// *Action:
//
10337, 00000, "enable padding owner name in slave sql"
//*Document: NO
//*Cause: owner name is not padded by default in slave sql
//*Action: pad owner name during generation of slave sql
//*Comment: applicable only for explain plan queries(for testing purposes)
/
10338, 00000, "CBO don't use inlist iterator with function-based indexes"
// *Cause:
// *Action:
10339, 00000, "CBO disable DECODE simplification"
// *Cause:
// *Action:
10340, 00000, "Buffer queues sanity check for corrupted buffers"
//*Document: NO
//*Cause:
//*Action: Check all buffer queues for corrupted buffer every 5 minutes
//
/ reserve events 10341 - 10350 for checkpoints
/
10341, 00000, "Simulate out of PGA memory in DBWR during object reuse"
// *Cause:
// *Action: checks that DBWR can still perform invalidatino
// *Comment: only used during testing
/
10342, 00000, "Raise unknown exception in ACQ_ADD when checkpointing"
// *Cause:
// *Action: should cause process to dump trace file and die
// *Comment: This event is obsoleted, and can be reused for another test.
/
10343, 00000, "Raise an out of memory exception-OER 4031 in ACQ_ADD"
// *Cause:
// *Action: For Backgrounds, try to handle checkpoint using reserved entries
// *Comment: Only enabled during testing
/
10344, 00000, "reserved for simulating object hash reorganization"
// *Document: NO
// *Cause:
// *Action: Set this to trigger obj hash table reorg to simulate large number
// of objects per hash buckets. Done by DBWR interrupt action.
/
10345, 00000, "validate queue when linking or unlinking a buffer"
// *Cause:
// *Action: checks low RBA ordering of queue associated with latch
// *Comment: Raises an error if low RBA ordering on queue is wrong
/
10346, 00000, "check that all buffers for checkpoint have been written"
// *Cause:
// *Action: Scans the cache to see that all candidate buffers are written
// *Comment: Usually only enabled for TESTING since it involves a cache scan
/
10347, 00000, "dump active checkpoint entries and checkpoint buffers"
// *Cause:
// *Action: Prints the checkpoint queue and buffers to the trace file
// *Comment: Usually only enabled for TESTING and code coverage
/
10348, 00000, "test abnormal termination of process initiating file checkpoint"
// *Document: NO
// *Cause:
// *Action: Causes abnormal termination of process starting a file checkpoint
// *Comment: Only enabled for TESTING and code coverage
/
10349, 00000, "do not allow ckpt to complete"
// *Cause:
// *Action: disables checkpoint completion
// *Comment: only enabled for TESTING
/
10350, 00000, "Simulate more than one object & tsn id in object reuse"
// *Cause:
// *Action: checks that DBWR can service multiple object id's in reuse"
// *Comment: only used during testing
/
/ reserve events 10351-10359 for direct asynchronous read path
/
10351, 00000, "size of slots"
// *Cause:
// *Action: sets the size of slots to use
// *Comment: a slot is a unit of I/O and this factor controls the size
// *Comment: of the IO.
/
10352, 00000, "report direct path statistics"
// *Cause:
// *Action: turns on direct path statistics
// *Comment: reports statistics for direct path
/
10353, 00000, "number of slots"
// *Cause:
// *Action: sets a given number of slots to use
// *Comment: a slot is a unit of I/O and this factor controls the number
// *Comment: of outstanding I/Os.
/
10354, 00000, "turn on direct read path for parallel query"
// *Cause:
// *Action: enable direct read for parallel query
/
10355, 00000, "turn on direct read path for scans"
// *Cause:
// *Action: enable direct async read for scans
/
10356, 00000, "turn on hint usage for direct read"
// *Cause:
// *Action: enables using hint for direct async reads
/
10357, 00000, "turn on debug information for direct path"
// *Cause:
// *Action: turn on debug information for direct path
/
10358, 00000, "Simulate out of PGA memory in cache advisory reset"
// *Cause:
// *Action: checks that CKPT can set the simulation to OFF
// *Comment: only used during testing
/
10359, 00000, "turn off updates to control file for direct writes"
// *Cause:
// *Action: Control files won't get updated for direct writes for LOBs
// when NOCACHE NOLOGGING is set. The only bad impact that it
// can have is that if you are using the recovery manager,
// it may affect a warning that says that the user should
// back everything up. Now the recovery manager won't know
// to tell you that the files that were updated with
// unrecoverable events should be backed up.
/
/ reserve events 10360-10362 for debugging DBWR
/
10360, 0000, "enable dbwr consistency checking"
// *Cause: internal use only
// *Action: enables consistency checking of buffers written by
// dbwriter and consistency checking of LRU working sets
/
10361, 00000, "check buffer change vector count consistency"
// *Document: No
// *Cause: internal use only
// *Action: invoke buffer change vector count consistency every 5 minutes
/
10362, 00000, "simulate a write error to take a file offline"
// *Document: No
// *Cause: internal use only
// *Action: Enables testing of DBWR taking a file offline because of a
// write error. The level is the absolute file number of the
// file to be taken offline when DBWR attemts to write to it.
/
10363, 00000, "Simulate messaging error for fast object reuse/checkpoint"
// *Document: No
// *Cause: internal use only
// *Action: Enables testing of fast object reuse/checkpoint fallback
// mechanism due to ksr message publishing issues.
/
10364, 00000, "Do not clear GIMH_STC_SHUT_BEGIN state during shutdown"
// *Document: No
// *Cause: internal use only
// *Action: Enables testing of shutdown begin event by not
// clearing GIMH_STC_SHUT_BEGIN state before shutdown completes.
/
/ reserve events 10365-10367 for direct asynchronous read path
/
10365, 00000, "turn on debug information for adaptive direct reads"
// *Cause:
// *Action: turn on debug information for adaptive direct reads
/
/
/ reserve events 10366-10367 for KGNFS/KGODM
10366, 00000, "kgnfs tracing"
// *Cause:
// *Action: If this event is set then kgnfs module generates debug tracing.
/
10367, 00000, "kgodm tracing"
// *Cause:
// *Action: If this event is set then kgodm module generates debug tracing.
//
/ reserve events 10368-10368 for KSE
10368, 00000, "maximum number of internal errors a process will tolerate"
// *Cause:
// *Action: determines the maximum number of ORA-600s after which a
// process will commit suicide.
/
10369, 00000, "test SQL monitoring feature"
// *Cause:
// *Action: crash tests
/
/ reserve events for parallel query option. Available range 10370-10399
/
10370, 00000, "parallel query server kill event"
// *Cause: internal use only
// *Action: this event should never be set externally
// *Comment: commands a slave to commit suicide, codes line
/
10371, 00000, "disable TQ hint"
// *Cause: internal use only
// *Action: this event should never be set externally
// *Comment: Stops the generation of the TQ hint (for testing purposes)
/
10372, 00000, "parallel query server kill event proc"
// *Cause: internal use only
// *Action: this event should never be set externally
// *Comment: commands a slave to commit suicide, codes proc & weapon
/
10373, 00000, "parallel query server kill event"
// *Cause: internal use only
// *Action: this event should never be set externally
// *Comment: commands a slave to commit suicide, code count & context
/
10375, 00000, "turn on checks for statistics rollups"
// *Cause:
// *Action: enables checks for stat rollup in QC
// *Comment: verify that the rollup is being done accurately
/
10376, 00000, "enable archive compression loads"
// *Cause:
// *Action: Enables archive compression
// *Comment: Temporary event
/
10377, 00000, "force slave allocation"
// *Document: No
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: for testing only--force the allocation of slaves in certain nodes
/
10378, 00000, "force hard process/range affinity"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: for testing only
/
10380, 00000, "kxfp latch cleanup testing event"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: for testing only--indicates the server to which the latch
// cleanup key applies (0 for QC)
/
10381, 00000, "kxfp latch cleanup testing event"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: for testing only--the latch cleanup key (the number of the
// LCTEST() call on which to kill the process)
/
10382, 00000, "parallel query server interrupt (reset)"
// *Cause: internal use only
// *Action: this event should never be set externally
// *Comment: commands a slave to clear its buffers and reset itself
/
10383, 00000, "auto parallelization testing event"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development
// *Comment: For testing only. Trace level bits can be used in combination:
// 1: parallelize every full table scan (kkfd.c)
// 2: create every table/cluster parallel (prsc.c)
// 4: create every table/cluster cache
// 8: create every table/cluster cache partitions (overrides 4)
/
10384, 00000, "parallel dataflow scheduler tracing"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: trace level is a bitfield (see kkrp.h)
/
10385, 00000, "parallel table scan range sampling method"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: level: 0: (default) sample by random rowid
// 1: sample by first rows of partition ranges
/
10386, 00000, "parallel SQL hash and range statistics"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: print kxfq hash and range statistics
/
10387, 00000, "parallel query server interrupt (normal)"
// *Cause: internal use only
// *Action: this event should never be set externally
// *Comment: commands a slave to leave the server group normally
/
10388, 00000, "parallel query server interrupt (failure)"
// *Cause: internal use only
// *Action: this event should never be set externally
// *Comment: commands a slave to leave the server group (query
// failed)
/
10389, 00000, "parallel query server interrupt (cleanup)"
// *Cause: internal use only
// *Action: this event should never be set externally
// *Comment: commands a slave to leave the server group (signaled
// by PMON, coordinator died)
/
10390, 00000, "Trace parallel query slave execution"
// *Cause:
// *Action: set this event only under the supervision of Oracle development.
// trace level is a bitfield
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 slave-side execution messages
// 0x0002 coordinator-side execution messages
// 0x0004 slave context state changes
// 0x0008 slave rowid range bind variables and xty
//
// 0x0010 slave fetched rows as enqueued to TQ
// 0x0020 coordinator wait reply handling
// 0x0040 coordinator wait message buffering
// 0x0080 slave dump timing
//
// 0x0100 coordinator dump timing
// 0x0200 slave dump allocation file numbers
// 0x0400 terse format for debug dumps
// 0x0800 Trace CRI random sampling
//
// 0x1000 Trace signals
// 0x2000 Trace PX granule operations
// 0x4000 Force compilation by slave 0
/
10391, 00000, "trace PX granule allocation/assignment"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 dump summary of each object scanned in parallel
// 0x0002 full dump of each object except extent map
// 0x0004 full dump of each object including extent map
//
// 0x0010 dump summary of each granule generators
// 0x0020 full dump of granule generators except granule instances
// 0x0040 full dump of granule generators including granule instances
//
// 0x0080 dump system info
// 0x0100 dump reference object for the query
// 0x0200 gives timing in kxfralo
// 0x0400 trace affinity module
// 0x0800 trace granule allocation during query execution
//
// 0x1000 trace object flush
// 0x2000 internal
// *Comment: print details of PQ parallel granule allocation
/
10392, 00000, "parallel query debugging bits"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: turn on/off various kxfp features (documentation in kxfp.c)
/
10393, 00000, "print parallel query statistics"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: print kxfp statistics after each parallel query
/
10394, 00000, "generate a fake load to test adaptive and load balancing"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: generates a fake load for testing purposes
/
10395, 00000, "adjust sample size for range table queues"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: use reduced sample size for testing only
/
10397, 00000, "suppress verbose parallel coordinator error reporting"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: disable the ORA-12801 message when a parallel query
// server gets a SQL error, instead report the slave's
// actual error as if signaled in the foreground (for
// testing, to match sequential log files)
/
10398, 00000, "enable timeouts in parallel query threads"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: level of this event indicates the number of seconds
// before timing out of a kxfpqdeq() call, after which
// an internal error will be signaled...for testing so
// that test suites don't wedge.
/
10399, 00000, "trace buffer allocation"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: level indicates verbosity of tracing
// Level1: Buffer leak checking
// Level2: trace buffer init, chunk alloc, free and recovery
// Level3: trace buffer alloc & free
/
/
10400, 00000, "turn on system state dumps for shutdown debugging"
// *Cause:
// *Action: Enables debugging code for shutdown problems (e.g., hangs)
/
10401, 00000, "turn on IPC (ksxp) debugging"
// *Cause:
// *Action: Enables debugging code for IPC service layer (ksxp)
/
10402, 00000, "turn on IPC (skgxp) debugging"
// *Cause:
// *Action: Enables debugging code for IPC layer (skgxp)
/
10403, 00000, "fake CPU number for default degree of parallelism"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: level of this event indicates the number of CPUs you want to
// set to
/
/ reserve events 10404 - 10405 for mirror resilvering testing
10404, 00000, "crash dbwr after write"
// *Cause:
// *Action: set this event only to test mirror resilvering osds
// *Comment: This event causes dbwr to crash after doing a write to
// a mirrored datafile. For use in tkbrmrt only.
/
10405, 00000, "emulate broken mirrors"
// *Cause:
// *Action: set this event to cause mirror resilvering on startup
// *Comment: This event is set when starting up after a crash caused
// by OER(10404). It is used to persuade the recovery layer
// that a mirror was broken.
/
10406, 00000, "enable datetime TIMESTAMP, INTERVAL datatype creation"
// *Cause:
// *Action: set this event to enable datetime datatype creation
// *Comment: This event is set when the user wants to create
// a datetime datatype column. The compatible=8.1.0.0.0 parameter
// must also be set.
/
10407, 00000, "enable datetime TIME datatype creation"
// *Cause:
// *Action: set this event to enable datetime datatype creation
// *Comment: This event is set when the user wants to create
// a datetime datatype column. The compatible=8.1.0.0.0 parameter
// must also be set.
/
10408, 00000, "disable OLAP builtin window function usage"
// *Cause:
// *Action: set this event to disable new OLAP builtin window functions
// *Comment: This event is set when the user has a name conflict
// with one of the OLAP window function names. This setting
// disables the builtin functions so that user functions work.
/
10409, 00000, "enable granule memset and block invalidation at startup"
// *Cause:
// *Action: set this event to enable the memset and invalidation
// *Comment: This event is created to be the safe valve for
// startup speedup transaction
/
/ Events 10410-10412 reserved for KSXP/CGS error simulation
10410, 00000, "trigger simulated communications errors in KSXP"
// *Document: NO
// *Cause:
// *Action: set this event to simulate communications errors to clients
// *Comment: This event is set as 0xCIXXNNNN where C is the client id the
// the error will be generated to, I is the instance id the error
// will be generated for and NNNN is the minimum message sequence
// number for instance I. An initial event value of C=0 indicates
// dynamic check of event
10412, 00000, "dump the call stack if an error is signaled"
// *Document: NO
// *Cause: For testing only.
// *Action: None. For testing only. Should never be set by customers.
/
10413, 00000, "force simulated error for testing purposes"
// *Document: NO
// *Cause: For testing only.
// *Action: None. For testing only. Should never be set by customers.
// *Comment:
// level 1: ALTER TABLESPACE...READ ONLY before kcftro
// level 2: ALTER TABLESPACE...READ ONLY after kcftro
// level 3: ALTER TABLESPACE...READ ONLY before kcfrdo, after waiting
// level 4: ALTER TABLESPACE...READ ONLY after kcfrdo
// level 5: ALTER TABLESPACE...READ ONLY after krcrtro
// level 6: ALTER TABLESPACE...READ ONLY after kqrpre to get lock on TS$
// level 7: ALTER TABLESPACE...READ ONLY after kqrpup to update TS$
// level 8: ALTER TABLESPACE...READ ONLY after ktucat to check other tx's
// level 9: ALTER TABLESPACE...READ ONLY after ktccrb to commit
// level 10: ALTER TABLESPACE...READ ONLY in kcfrdo, before checkpoint
//
10414, 00000, "simulated error from event %s level %s"
// *Document: NO
// *Cause: For testing only.
// *Action: None. For testing only. Should never be set by customers.
// *Comment:
//
10415, 00000, "parallel degree specified is too large, max value allowed %s"
// *Document: NO
// *Cause: User specified parallel degree is greater than DEG_INST_MAXVAL
// *Action:
// *Comment:
//
10416, 00000, "disable fix for 2736734"
// *Document: NO
// *Cause:
// *Action: Disable the fix for bug 2736734
//
10417, 00000, "limit 1 file per sbtinfo2() validation call"
// *Document: NO
// *Cause:
// *Action: Prevent Oracle from passing multiple file handles to sbtinfo2(),
// in case the Media Management Software cannot properly support
// calls with multiple file names.
10418, 00000, "disable re-creating tempfile"
// *Document: NO
// *Cause:
// *Action: Prevent Oracle from automatically re-creating tempfile
10419, 00000, "create tempfile without create_scn and time"
// *Document: NO
// *Cause: For testing only.
// *Action: None. For testing only. Should never be set by customers.
10420, 00000, "trace KSO OS-process operations"
// *Document: NO
// *Cause:
// *Action: Trace KSO operations.
10421, 00000, "enable dump from ksbwco if there is no reply"
// *Document: NO
// *Cause:
// *Action: creates an error stack dump if ksbwco does not hear back.
10422, 00000, "KSU debugging"
// *Document: NO
// *Cause:
// *Action: Helps debug KSU issues (see ksu.h).
10423, 00000, "dump the call stack if the specified error is cleared"
// *Document: NO
// *Cause: If an unknown module is clearing an error that you expected to
// be resignalled, you can use this event to aid your debugging.
// Whenever that error is cleared the call stack will be dumped to the
// trace file. This only works for non-OS Oracle errors.
// Usage: event="10423 trace name context forever, level <your-err>"
// Example:
// event="10423 trace name context forever, level 28"
// Each time ORA-28 is cleared the stack will be dumped.
// *Action: Creates a stack dump each time the specified error is cleared.
10424, 00000, "KGE debugging"
// *Document: NO
// *Cause:
// *Action: Helps debug KGE issues (see kge.c).
/ Events 10425-10450 reserved for global enqueue service tracing and debugging
10425, 00000, "enable global enqueue operations event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue operations.
10426, 00000, "enable ges/gcs reconfiguration event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for ges/gcs reconfiguration.
10427, 00000, "enable global enqueue service traffic controller event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue service traffic controller.
10428, 00000, "enable tracing of global enqueue service cached resource"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue service cached resource activities.
10429, 00000, "enable tracing of global enqueue service IPC calls"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue service IPC calls.
10430, 00000, "enable ges/gcs dynamic remastering event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for ges/gcs dynamic remastering.
10431, 00000, "enable verification messages on pi consistency"
// *Document: NO
// *Cause:
// *Action: Send verification messages to check pi consistency
10432, 00000, "enable tracing of global cache service fusion calls"
// *Document: NO
// *Cause:
// *Action: Dump trace for global cache service fusion calls.
10433, 00000, "global enqueue service testing event"
// *Document: NO
// *Cause:
// *Action:
// Level: == 6 to return out-of-memory when getting message buffer
// Level: == 7 to suspend lmd for a short period of time
// Level: == 8 to suspend lms for a short period of time
// Level: == 9 to inject out-of-order dlm messages
// Level: == 10 to delay direct sends on send proxies and
// to force indirect sends on half of the
// direct send messages
10434, 00000, "enable tracing of global enqueue service multiple LMS"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue service muliple LMS.
10435, 00000, "enable tracing of global enqueue service deadlock detetction"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue service deadlock detetction.
10436, 00000, "enable global cache service duplicate ping checking"
// *Document: NO
// *Cause:
// *Action: Enable global cache service duplicate ping checking
10437, 00000, "enable trace of global enqueue service S optimized resources"
// *Document: NO
// *Cause:
// *Action: Dump global cache service S optimized resources
10438, 00000, "force lowest node to be master of all gcs resources"
// *Document: NO
// *Cause:
// *Action: enable affinity locks by forcing lowest node to be master
10439, 00000, "enable tracing of global cache service fusion calls - part 2"
// *Document: NO
// *Cause:
// *Action: enable tracing of global cache service fusion calls - part 2
10440, 00000, "enable global enqueue service inquire resource modes trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue service resource inquiry messages.
10441, 00000, "enable diagnosibility daemon (DIAG) trace"
// *Document: NO
// *Cause:
// *Action: Dump traces for DIAG.
10442, 00000, "enable trace of kst for ORA-01555 diagnostics"
// *Document: NO
// *Cause:
// *Action: Dump trace for ORA-01555 diagnostics
10443, 00000, "reserved for data layer diagnostics and debugging"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
10444, 00000, "enable DLM timeout testing"
// *Document: NO
// *Cause:
// *Action: Simulate various scenarios for DLM/CGS timeouts testing
10445, 00000, "enable tracing of LMS priority management"
// *Document: NO
// *Cause:
// *Action: Dump trace for LMS priority management
10446, 00000, "reserved for data layer diagnostics and debugging"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
10447, 00000, "reserved for data layer diagnostics and debugging"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
10448, 00000, "Dump trace for OLTP partial compression features diagnostics"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
10449, 00000, "enable trace of kst for undo manageability features diagnostics"
// *Document: NO
// *Cause:
// *Action: Dump trace for undo manageability features diagnostics
10450, 00000, "signal ctrl-c in kdddca (drop column) after n rows"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: Set the level number to the number of rows before the error
// is signalled. The error will be ORA-1013 (ctrl-c)
10451, 00000, "Force heap segment compression bypassing compatibility checks"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
//
10452, 00000, "Cannot do block media recovery; media recovery session may be in progress"
// *Cause: A media recovery, RMAN, or flashback database session may have
// been in progress when an attempt was made to perform block media
// recovery on the standby database.
// *Action: Check for and cancel any conflicting recovery session and perform
// block media recovery on the standby database.
//
10453, 00000, "Dump compression statistics to trace file"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
//
10454, 00000, "Disable column reordering during compression"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
//
10455, 00000, "Do Compression Block Checking"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
//
10456, 00000, "cannot open standby database; media recovery session may be in progress"
// *Cause: A media recovery, RMAN, or flashback database session may have
// been in progress on a mounted instance of a standby database
// when an attempt was made to open the standby database.
// *Action: Check for and cancel any conflicting recovery session and open
// the standby database.
//
10457, 00000, "cannot close standby database due to active media recovery"
// *Cause: A media recovery session was in progress on a standby database
// when an attempt was made to close the standby database.
// *Action: Cancel the media recovery session and close the standby database.
//
10458, 00000, "standby database requires recovery"
// *Cause: A standby database was in a state requiring media recovery
// when an attempt was made to open the standby database.
// *Action: Perform the necessary recovery and open the standby database.
//
10459, 00000, "cannot start media recovery on standby database; conflicting state detected"
// *Cause: An attempt was made to perform media recovery on a standby
// database while another instance was performing recovery on
// the standby database, had the standby database open, or a data file
// move operation was in progress.
// *Action: Close the standby on all other instances, cancel any conflicting
// recovery session or data file move operation, and perform manual
// recovery.
//
10460, 00000, "Perform backward tablescans for consistent read reduction"
// *Cause:
// *Action:
//
// Events 10461 - 10489 reserved for recovery, incl debugging and tracing
//
10461, 00000, "Simulate control file corruption during write operation"
// *Cause:
// *Action: If set, will cause control file header verification to fail
//
10462, 00000, "enable recovery debug module"
// *Cause:
// *Action: Set this event to enable recovery debug module.
// Recovery debug module does extra sanity checks on redo
// generation and dumps interesting information to trace
// if certain errors occur.
//
10463, 00000, "enable controlfile test"
// *Document: NO
// *Cause:
// *Action: Set this event to enable controlfile sequence number dump
// at instance shutdown (level 1), future version controlfile
// compatibility test (level 2), or cf backup creation (level 3)
//
10464, 00000, "enable incremental checkpoint debug for split brain check"
// *Document: NO
// *Cause:
// *Action: Set this event to enable checkpoint heartbeat tracing
//
10465, 00000, "force slave death during parallel crash recovery"
// *Document: NO
// *Cause:
// *Action:
//
10466, 00000, "enable HARD check for block write"
// *Document: NO
// *Cause:
// *Action: Set this event to enable HARD check for every block write.
//
10467, 00000, "amplify control file record expansion for testing"
// *Document: NO
// *Cause:
// *Action: Set this event to amplify control file record expansion for testing
//
10468, 00000, "log writer debug module"
// *Document: NO
// *Cause:
// *Action: Set this event to the appropriate level for log writer debugging.
//
10469, 00000, "error creating control file backup, no checkpoint"
// *Cause: The control file being backed up did not
// contain a valid control file checkpoint.
// Therefore the control file could not be backed up,
// as such a backup would not be usable later for recovery.
// A common cause for this situation is that you executed
// CREATE CONTROLFILE, which mounts the database,
// but not ALTER DATABASE OPEN, to open the database.
// The latter operation generates a valid control file checkpoint.
// *Action: Open the database with ALTER DATABASE OPEN ...,
// which results in a valid control file checkpoint.
// Run the backup operation again.
10470, 00000, "Lost write detection related event"
// *Document: NO
// *Cause:
// *Action: Set this event to enable certain lost write detection related
// functionalities.
10471, 00000, "PQ slave allocation timeout test"
// *Document: NO
// *Cause:
// *Action: Set this event to enable the delay in PQ slave allocation.
// If the delay is longer than the preset threshold (currently
// 1 minute), parallel recovery should switch to serial recovery.
//
10472, 00000, "dump reading log buffer hit ratio histogram to lgwr trace file"
// *Document: NO
// *Cause:
// *Action: Set this event to dump reading log buffer hit rate histogram
// to lgwr trace file.
//
10473, 00000, "enable BRR tracing"
// *Document: NO
// *Cause:
// *Action: Set this event to enable tracing of Block Read Record generation.
//
10474, 00000, "controlfile time tracing"
// *Document: NO
// *Cause:
// *Action: Set this event to enable additional tracing of the time spent
// in different controlfile operations.
//
10475, 00000, "readable standby debug event"
// *Document: NO
// *Cause:
// *Action: Set this event to enable additional tracing of readable standby.
//
10476, 00000, "control file corruption range testing"
// *Document: NO
// *Cause:
// *Action: Set this event to enable testing of control file
// corruption ranges.
//
10477, 00000, "simulated rollback error"
// *Document: NO
// *Cause:
// *Action: Set this event to simulate a rollback failure.
//
10478, 00000, "DBW0 file identification trace event"
// *Document: NO
// *Cause:
// *Action: Set this event to enable DBW0 file identification tracing.
//
10479, 00000, "disk sector size test event"
// *Document: NO
// *Cause:
// *Action: Set this event to let OSD return a specified sector size
// level 1: OSD returns 512 as the disk sector size
// level 2: OSD returns 4096 (emulation) as the disk sector size
// level 3: OSD returns 4096 (native) as the disk sector size
//
10480, 00000, "Soft asserts for fast detection of datafile storage problems"
// *Document: NO
// *Cause:
// *Action: Set this event to enable soft asserts to fire when a corrupt or
// stale block is seen in some datafile mirrors. This event allows
// for the proactive detection of datafile storage problems.
//
10481, 00000, "Backup data block for data file has an unlogged change"
// *Cause: Flashback was enabled for the data file when the backup data block used
// for block media recovery had an unlogged change.
// *Action: Remove the data file from the flashback set or use a backup block that
// does not contain an unlogged change to perform block media recovery.
//
10482, 00000, "Automatic block repair cannot repair an offline or read-only data file"
// *Cause: Automatic block repair failed when trying to repair an offline or read-only
// data file.
// *Action: Bring the data file online in read/write mode.
//
10483, 00000, "Simulate overly advanced incremental checkpoint"
// *Document: NO
// *Cause:
// *Action: Set this event to advance the incremental checkpoint so that dirty
// buffers exist with low RBAs less than that of the checkpoint. This
// scenario will be detected and the database will be crashed in a
// recoverable state.
//
// level 1: Generate error when linking buffer
// level 2: Generate error when unlinking buffer
//
10484, 00000, "Enable tracing for online data file move operation"
// *Document: NO
// *Cause:
// *Action: Enable this event for KST tracing of online data file move operation.
//
10485, 00000, "Real-Time Query cannot be enabled while applying migration redo."
// *Cause: The Real-Time Query feature was enabled when an attempt was made
// to recover through migration redo generated during primary upgrades or
// downgrades.
// *Action: Close the standby database in order to recover through
// migration redo. Reenable the Real-Time Query feature afterwards.
10486, 00000, "Verify data file-related SGA alignment"
// *Document: NO
// *Cause:
// *Action: Enable this event to verify data file-related SGA alignment.
10487, 00000, "Dump redo memory protection information."
// *Document: NO
// *Cause:
// *Action: Enable this event to dump the details about redo memory protection.
10488, 00000, "Dump block headers read for media recovery."
// *Document: NO
// *Cause:
// *Action: Enable this event to dump the block headers read during media
// recovery before any redo application. If level is K_BTMAX+1, dump
// all block types, otherwise dump only type equal to the event level.
10489, 00000, "Generate future redo for testing"
// *Document: NO
// *Cause:
// *Action: Internal testing only. Level of non-zero generates a future
// informational redo change with opcode not known by this release.
//
/ Events 10490 - 10499 reserved for Oracle Storage Manager
/
10490, 00000, "Trace OSM misc. events"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
//
10491, 00000, "Trace OSM messaging (KFN) events"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
//
10492, 00000, "Trace OSM metadata events"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
//
10493, 00000, "Return empty define buffers on 1422"
// *cause
// *action: On error 1422 instead of returning data in define buffers
// this mimics action of version 7 and doesn't return data
// valid level = 1
//
10494, 00000, "Trace OSM metadata events"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
//
10495, 00000, "Trace OSM metadata events"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
//
10496, 00000, "Turn off fix for bug 2554178"
// *cause
// *action: Instead of checking the current schema against the owner of the
// db link revert to previous scheme
//
10497, 00000, "Trace OSM metadata events"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
//
10498, 00000, "Trim blank characters including contol characters"
// *Cause:
// *Action:
// *Comment: Set this event to any non-zero level to trim blank characters
// including control characters.
// Default behaviour: No control characters are trimmed.
//
10499, 00000, "Trace OSM metadata events"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
//
10500, 00000, "turn on traces for SMON"
// *Document: NO
// *Cause:
// *Action:
// Level: <=5 trace instance recovery
// > 5 trace posting of SMON
10501, 00000, "periodically check selected heap"
// *Cause:
// *Action:
// Level: 0x01 PGA
// 0x02 SGA
// 0x04 UGA
// 0x08 current call
// 0x10 user call
// 0x20 large allocation pool
10502, 00000, "CBO disable the fix for bug 2098120"
// *Cause:
// *Action:
10503, 00000, "enable user-specified graduated bind lengths"
// *Cause:
// *Action:
10504, 00000, "CBO disable the fix for bug 2607029"
// *Cause:
// *Action:
10505, 00000, "CBO enable dynamic sampling dump to table"
// *Cause:
// *Action:
10506, 00000, "Disable fix for bug 2588217"
// *Cause:
// *Action:
10507, 00000, "Trace bind equivalence logic"
// *Cause:
// *Action:
10508, 00000, "Enable fix for bug 14772545"
// *Cause:
// *Action:
10509, 00000, "Check kghu subheaps at call boundaries"
// *Cause:
// *Action:
// Level: 0x01 Call heap
// 0x02 Session heap
10510, 00000, "turn off SMON check to offline pending offline rollback segment"
// *Cause:
// *Action:
10511, 00000, "turn off SMON check to cleanup undo dictionary"
// *Cause:
// *Action:
10512, 00000, "turn off SMON check to shrink rollback segments"
// *Cause:
// *Action:
10513, 00000, "turn on IPC (ksmsq) debugging"
// *Document: NO
// *Cause:
// *Action: Enables debugging code for the interprocess communication (IPC)
// layer (ksmsq).
/
10515, 00000, "turn on event to use physical cleanout"
// *Cause:
// *Action:
10519, 00000, "enable ALTER TYPE RESET support"
// *Cause:
// *Action:
10520, 00000, "recreate view only if definition has changed"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development
// *Comment: Changes behaviour of create or replace view,
// comparing the new definition to the old prior to recreating the
// object. Creation is skipped if old and new definitions match
// (ie. object has not changed). No level number required.
10521, 00000, "CMON connection pool test event"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
10522, 00000, "turn off wrap source compression"
// *Cause:
// *Action: Set this event if you do not want source of wrapped PL/SQL
// objects to be concatenated and stored multiple lines to a row.
// *Comment: This event should be set if you want the source of wrapped
// PL/SQL objects to be stored one line per source row. The
// default storage method is multiple lines per row, which
// improves load and compile performance. No level number
// required.
10523, 00000, "force recreate package even if definition is unchanged"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development
// *Comment: Changes behaviour of create or replace package, procedure,
// function or type to force recreation of the object even if its new
// definition exactly matches the old definition.
// No level number required.
10524, 00000, "CMON connection pool trace event"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
10525, 00000, "Disable automatic object validation for describe"
// *Cause:
// *Action:
10526, 00000, "enables lightweight thread tracing"
// *Cause: Used in ksolt.
// *Action: Set this event only under the supervision of Oracle Support Services.
// *Comment: enables trace messages from the lightweight thread module.
// Enable this event only during testing.
10527, 00000, "enables SGA allocation tracing"
// *Cause: Used for logging events during SGA allocation.
// *Action: Set this event only under the supervision of Oracle Support Services.
// *Comment: enables trace messages from SGA allocation
// Enable this event only during testing.
10528, 00000, "enables ksmg tracing"
// *Cause: Used in ksmg module.
// *Action: Set this event only under the supervision of Oracle Support Services.
10529, 00000, "enables SGA range protection tracing"
// *Cause: Used in ksm module.
// *Action: Set this event only under the supervision of Oracle Support Services.
/
/ 10530 -10540 reserved for lightweight threads
/
10530, 00000, "lightweight thread spawn failed, error stack:"
// *Cause: A lightweight thread spawn failed.
// *Action: Check the alert or trace files for more information.
10531, 00000, "lightweight thread unit test failure error"
// *Cause: A lightweight thread unit test failed.
// *Action: Check the alert or trace files for more information.
10532, 00000, "lightweight thread encountered internal error"
// *Cause: A lighweight thread encountered an internal error.
// *Action: Check the alert or trace files for more information and contact
// Oracle Support Services.
10542, 00000, "Enable tracing for block compare"
// *Document: NO
// *Cause:
// *Action: None
10543, 00000, "Standby Block Media Recovery (bmr) and split brain testing event"
// *Document: NO
// *Cause:
// *Action: Set this event in order to test the situation where standby bmr
// does not have the necessary redo to recover a block or the situation
// where a split brain occurs during instance/crash recovery.
10544, 00000, "Inject standby autobmr failures"
// *Document: NO
// *Cause:
// *Action:
// level: 0x01 Inject block failures that will trigger standby autobmr.
// level: 0x02 Print trace information of assigning CVs to undo tbs slave to trace file.
10545, 00000, "Print standby autobmr messages in alert log"
// *Document: NO
// *Cause:
// *Action: Set this event to print standby autobmr messages in alert log.
10546, 00000, "Cannot perform block media recovery; standby database does not have requisite redo."
// *Cause: An attempt was made to perform block media recovery on the standby
// database when the necessary redo was not available.
// *Action: Wait until the necessary redo is available and reattempt block
// media recovery.
10547, 00000, "Cannot perform block media recovery; standby database is not caught up with primary."
// *Cause: An attempt was made to perform block media recovery on the standby
// database up to scn %s, which is greater than the highest scn of %s
// yet applied at the standby.
// *Action: Recover the standby up to scn %s and reattempt block media
// recovery.
10548, 00000, "Cannot perform block media recovery on a read-only plugged-in datafile."
// *Cause: An attempt was made to perform block media recovery on a read-only
// plugged-in datafile.
// *Action: Convert the plugged-in datafile to read/write and reattempt block
// media recovery.
10549, 00000, "Cannot perform block media recovery using a read-only plugged-in backup datafile."
// *Cause: An attempt was made to perform block media recovery using a backup
// of a read-only plugged-in datafile.
// *Action: Reattempt block media recovery using a backup taken after the
// plugged-in datafile has been converted to read/write.
10550, 00000, "signal error during create as select/create index after n rows"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: Set the level number to the number of rows before the error
// is signalled. The error will be ORA-1013 (ctrl-c)
//
10551, 00000, "Internal testing for ORA-1551 error handling"
// *Cause:
// *Action:
/
/ 10552 -10589 reserved for recoverable media/standby recovery
/
10552, 00000, "allow unlimited corruption during recovery"
// *Document: NO
// *Cause:
// *Action: Set this event to allow unlimited corruption work with parallel
// recovery.
10553, 00000, "Incompatible UNTIL CONSISTENT clause"
// *Cause: RECOVER UNTIL CONSISTENT required database-level recovery with
// a backup control file.
// *Action: Omit the UNTIL CONSISTENT clause and retry recovery.
10554, 00000, "Media recovery failed to bring datafile %s to a consistent point"
// *Cause: Media recovery couldn't recover database to a consistent point due
// to the specified datafile.
// *Action: Restore a backup of the datafile.
10556, 00000, "Enable tracing for multi instance Redo Apply"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables tracing of multi instance redo apply
10557, 00000, "NID clears database incarnation section in controlfile"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10558, 00000, "Disable unkeep marker handling for ADG"
// *Document: NO
// *Cause:
// *Action: Set this event on primary to disable generation of Exadata flash
// cache unkeep marker. Set this event on ADG standby to ignore
// such marker and always pass KCBF_DEF_CL_CACHE to cell.
10559, 00000, "LGWR code path debugging event for deferred log flush on ping"
// *Document: NO
// *Cause:
// *Action: Set this event to simulate delay in LGWR code path for deferred
// log flush on block ping project.
10560, 00000, "block type '%s'"
// *Cause: Report block type for details of another error.
// *Action: See associated error message.
10561, 00000, "block type '%s', data object# %s"
// *Cause: Report block type and data object number for details of
// another error.
// *Action: See associated error message.
10562, 00000, "Error occurred while applying redo to data block (file# %s, block# %s)"
// *Cause: See other errors on error stack.
// *Action: Investigate why the error occurred and how important is the data
// block. Media and standby database recovery usually can continue
// if user allows recovery to corrupt this data block.
10563, 00000, "Test recovery had to corrupt data block (file# %s, block# %s) in order to proceed"
// *Cause: Test recovery completed.
// *Action: No action is needed. Test recovery has ended successfully.
// See other messages on error stack for a summary of the result
// of the test recovery.
10564, 00000, "tablespace %s"
// *Cause: Report tablespace name for details of another error.
// *Action: See associated error message.
10565, 00000, "Another test recovery session is active"
// *Cause: There can only be one test recovery session at any time.
// Another test recovery session is active.
// *Action: Wait till the other test recovery session completes.
10566, 00000, "Test recovery has used all the memory it can use"
// *Cause: Test recovery tests redo in memory. It can no longer proceed
// because it has consumed all the memory it can use.
// *Action: No action is needed. Test recovery has ended successfully.
// See other messages on error stack for a summary result
// of the test recovery.
10567, 00000, "Redo is inconsistent with data block (file# %s, block# %s, file offset is %s bytes)"
// *Cause: There are two possible causes of this error: (1) A write issued
// by Oracle was lost by the underlying OS or storage system.
// (2) an Oracle internal error.
// *Action: Investigate why the error occurred and how important is the data
// block. Media and standby database recovery usually can continue
// if user allows recovery to corrupt this data block.
10568, 00000, "Failed to allocate recovery state object: out of SGA memory"
// *Cause: out of SGA memory
// *Action: Restart the instance. If problem persists, call Oracle support.
10569, 00000, "Trace datafile header writes"
// *Document: NO
// *Cause:
// *Action: Set this event to enable tracing of datafile header writes.
10570, 00000, "Test recovery complete"
// *Cause: Test recovery completed.
// *Action: No action is needed. Test recovery has ended successfully.
// See other messages on error stack for a summary result
// of the test recovery.
10571, 00000, "Test recovery canceled"
// *Cause: User canceled test recovery.
// *Action: No action is needed. Test recovery has ended successfully.
// See other messages on error stack for a summary of the result
// of the test recovery.
10572, 00000, "Test recovery canceled due to errors"
// *Cause: See other errors on the error stack.
// *Action: See other messages on error stack. It is possible that no
// action is needed. See other messages on error stack for a
// summary of the result of the test recovery so far.
10573, 00000, "Test recovery tested redo from change %s to %s"
// *Cause: This message show the range of test recovery have tested.
// *Action: No action is needed. See other messages on error stack.
10574, 00000, "Test recovery did not corrupt any data block"
// *Cause: This message summarizes test recovery result.
// *Action: No action is needed. See other messages on error stack.
10575, 00000, "Give up restoring recovered datafiles to consistent state: out of memory"
// *Cause: There were not enough memory to restore recovered datafiles
// to consistent state
// *Action: This error is just a warning: You may not be able to open the
// database with resetlogs immediately after this error. However,
// you may continue media/standby recovery, and that may make the
// datafiles recovered consistent again.
10576, 00000, "Give up restoring recovered datafiles to consistent state: some error occurred"
// *Cause: See alert file or other errors on the stack for a cause of the
// problem.
// *Action: This error is just a warning: You may not be able to open the
// database with resetlogs immediately after this error. However,
// you may continue media/standby recovery, and that may make the
// datafiles recovered consistent again.
//
10577, 00000, "Can not invoke test recovery for managed standby database recovery"
// *Cause: Test recovery option is used for managed standby database recovery.
// *Action: Either remove the test recovery option or invoke manual test
// standby database recovery.
10578, 00000, "Can not allow corruption for managed standby database recovery"
// *Cause: You used the allow corruption option for managed standby database
// recovery.
// *Action: Either remove the allow corruption option or invoke manual
// standby database recovery.
10579, 00000, "Can not modify control file during test recovery"
// *Cause: To proceed with recovery, test recovery needs to modify the
// control file. But test recovery is not allowed to modify
// control file.
// *Action: No action is needed. Test recovery has ended successfully.
// It can only go so far in the redo stream.
10580, 00000, "Can not modify datafile header during test recovery"
// *Cause: To proceed with recovery, test recovery needs to modify a
// datafile header. But test recovery is not allowed to modify
// datafile headers.
// *Action: No action is needed. Test recovery has ended successfully.
// It can only go so far in the redo stream.
10581, 00000, "Can not modify redo log header during test recovery"
// *Cause: To proceed with recovery, test recovery needs to modify a
// redo log header. But test recovery is not allowed to modify
// redo log headers.
// *Action: No action is needed. Test recovery has ended successfully.
// It can only go so far in the redo stream.
10582, 00000, "The control file is not a backup control file"
// *Cause: User requested backup control file test recovery, but the
// control file is not a backup control file.
// *Action: Use a backup control file, or do not use USING BACKUP
// CONTROLFILE option.
10583, 00000, "Can not recovery file %s renamed as missing during test recovery"
// *Cause: One of the files to be recovered is renamed as missing.
// *Action: Rename the file to the correct file or offline it.
10584, 00000, "Can not invoke parallel recovery for test recovery"
// *Cause: Both test recovery and parallel recovery are requested.
// *Action: Drop either one of the two recovery options.
10585, 00000, "Test recovery can not apply redo that may modify control file"
// *Cause: Test recovery has encountered a special redo that may modify
// control file.
// *Action: No action is needed. Test recovery has proceeded successfully
// as far as it could from its starting point.
10586, 00000, "Test recovery had to corrupt 1 data block in order to proceed"
// *Cause: This message summarizes test recovery result: Oracle may have
// to corrupt one block in order to apply the range of redo tested.
// *Action: See alert log for details of the problem.
10587, 00000, "Invalid count for ALLOW n CORRUPTION option"
// *Cause: The number specified in the ALLOW n CORRUPTION option is too big.
// *Action: Use a smaller number.
10588, 00000, "media recovery file header validation"
// *Cause:
// *Action: Set this event only under the supervision of Oracle Support
// Services.
// *Comment: If event 10588 is set to level N when redo is being applied,
// then every N minutes, read and sanity check the file headers.
10589, 00000, "Test recovery had to corrupt %s data blocks in order to proceed"
// *Cause: This message summarizes test recovery result: Oracle may have
// to corrupt a number of data blocks as specified in the message
// in order to apply the range of redo tested.
// *Action: See alert log for details of the problems.
10590, 00000, "kga (argus debugger) test flags"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10591, 00000, "kga (argus debugger) test flags"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10592, 00000, "kga (argus debugger) test flags"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10593, 00000, "kga (argus debugger) test flags"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10594, 00000, "kga (argus debugger) test flags"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10595, 00000, "kga (argus debugger) test flags"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10596, 00000, "kga (argus debugger) test flags"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10597, 00000, "kga (argus debugger) test flags"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10598, 00000, "kga (argus debugger) test flags"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10599, 00000, "kga (argus debugger) test flags"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
//
10600, 00000, "check cursor frame allocation"
// *Cause:
// *Action:
10601, 00000, "turn on debugging for cursor_sharing (literal replacement)"
// *Cause:
// *Action:
10603, 00000, "cause an error to occur during truncate (for testing purposes)"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: this causes kdifrb to encounter an error during truncation of a
// table with an index. it is for testing purposes only.
10604, 00000, "trace parallel create index"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables analysis of parallel create index
10605, 00000, "enable parallel create index by default"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: this causes all create index statement to by default
// occur in parallel. it is for testing purposes only.
// the level set in the event is the degree of parallelism.
// *Comment: enables analysis of parallel create index - query coordinator
10606, 00000, "trace parallel create index"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables analysis of parallel create index - kkri slaves
10607, 00000, "trace index rowid partition scan"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables analysis of rowid index scan - rix row source,
// and puts more trace on errors in range scans
10608, 00000, "trace create bitmap index"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables analysis of create bitmap index - kkrb row source
10609, 00000, "trace for array index insertion"
// *Cause:
// *Action: set this event to turn off the index array operation
// *Comment: disable the index array operation
10610, 00000, "trace create index pseudo optimizer"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10611, 00000, "causes migration to fail - testing only"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10612, 00000, "prints debug information for auto-space managed segments"
// *Cause:
// *Action:
10613, 00000, "prints debug information for auto-space managed segments"
// *Cause:
// *Action:
10614, 00000, "Operation not allowed on this segment"
// *Cause: This procedure can be used only on segments in
// tablespaces with AUTO SEGMENT SPACE MANAGEMENT
// *Action: Recheck the segment name and type and re-issue the statement
10615, 00000, "Invalid tablespace type for temporary tablespace"
// *Cause: Tablespace with AUTO SEGMENT SPACE MANAGENEMT specified cannot be
// used as a temporary tablespace
// *Action: Recheck the tablespace name and re-issue the statement
10616, 00000, "Operation not allowed on this tablespace"
// *Cause: Cannot perform the operation on tablespace with AUTO
// SEGMENT SPACE MANAGEMENT
// *Action: Recheck the tablespace name and re-issue the statement
10617, 00000, "Cannot create rollback segment in dictionary managed tablespace"
// *Cause: Rollback segments cannot be created in dictionary managed
// tablespaces when SYSTEM tablespace is locally managed
// *Action: Recheck the tablespace name and re-issue the statement
10618, 00000, "Operation not allowed on this segment"
// *Cause: This DBMS_SPACE operation is not permitted on segments in
// tablespaces with AUTO SEGMENT SPACE MANAGEMENT
// *Action: Recheck the segment name and type and re-issue the statement
10619, 00000, "Avoid assertions when possible"
// *Cause: A bug (or upgrade) hits unicode assertions (csid, csform, bfc)
// *Action: Event makes RDBMS skip assertions and patch up datastructures
10620, 00000, "Operation not allowed on this segment"
// *Cause: Cannot alter freelist storage parameter for segments in tablespaces
// with AUTO SEGMENT SPACE MANAGEMENT
// *Action: Recheck the segment name and re-issue the statement
10621, 00000, "specify retry count for online index build cleanup DML lock get"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: Change the behaviour of online index build cleanup such that
// a failed DML lock get will be reattempted. The number of retries
// is dictated by the event level. Note that an event level of 1
// means try forever. Any other event level specifies the number
// of attempts, and is internally increased to some minimum default.
10622, 00000, "test or trace online index build or rebuild"
// *Cause:
// *Document: NO
// *Action: Set this event only under the supervision of Oracle development.
10623, 00000, "test synchronized flow of SORT rows into FOR UPDATE lock phase"
// *Cause:
// *Document: NO
// *Action: Set this event only under the supervision of Oracle development.
10624, 00000, "Disable UJV invalidation on drop index"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10625, 00000, "Turn off redo log dump for the index when OERI 12700"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10626, 00000, "specify timeout for online index rebuild to wait for DML"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: Change the behaviour of an online index rebuild such that it
// will timeout, rather than wait indefinitely for existing DML
// to complete.
// The event level is the number of seconds the online index rebuild
// should wait. Values outside the legal range of 2 to 300 seconds
// will be adjusted automatically.
10627, 00000, "Dump the content of the index leaf block"
// *Cause: Generate a complete index tree dump, not just an overview
// during alter session set events immediate trace name treedump
// *Action: This event is recommended only for small table/index since it
/ dumps very detail information of every keys in the index
10628, 00000, "Turn on sanity check for kdiss index skip scan state"
// *Cause: Will do sanity checking on the kdiss state.
// *Action: set this event only under the supervision of Oracle development
10629, 00000, "force online index build to backoff and retry DML lock upgrade"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: Change the behaviour of an online index rebuild such that it
// will backoff and retry a failed DML lock upgrade.
// The event level is the number of retries the online index rebuild
// should wait. Level 1 means backoff and retry indefinitely. Any
// other value less than 32 will be adjusted automatically to be 32.
10630, 00000, "Illegal syntax specified with SHRINK clause"
// *Cause: An illegal option was specified with the SHRINK clause
// *Action: Verify the SQL Reference Manual and reissue the command
10631, 00000, "SHRINK clause should not be specified for this object"
// *Cause: It is incorrect to issue shrink on the object
// *Action: Verify the object name and type and reissue the command
/
10632, 00000, "Invalid rowid"
// *Cause: Segment Highwatermark was overwritten due to shrink and space reused
// *Action: Reissue this command.
10633, 00000, "No space found in the segment"
// *Cause: Raised while trying to find space during segment shrink
// *Action: This error should be trapped internally and treated. The user should
// not be able to see the error.
10634, 00000, "Segment is already being shrunk"
// *Cause: Only one invocation of shrink can be in progress on a segment at any time
// *Action: Reissue the command after the first shrink is over
10635, 00000, "Invalid segment or tablespace type"
// *Cause: Cannot shrink the segment because it is not in auto segment space
// managed tablespace or it is not a data, index or lob segment.
// *Action: Check the tablespace and segment type and reissue the statement
10636, 00000, "ROW MOVEMENT is not enabled"
// *Cause: To shrink a data segment, row movement must be enabled.
// *Action: Enable row movement and reissue this command.
10637, 00000, "The segment does not exist"
// *Cause: Segment to be shrunk has been dropped
// *Action:
10638, 00000, "Index status is invalid"
// *Cause: Cannot shrink an index which is being rebuilt or disabled
// is an unusable state.
// *Action:
10639, 00000, "Dump library cache during reparse loops"
// *Cause: During this error a library cache dump is necessary , so enable
// librarycache dump if event is set.
// *Action: Dump a library cache if this event is set when reparse error.
//
10640, 00000, "Operation not permitted during SYSTEM tablespace migration"
// *Cause: SYSTEM tablespace is being migrated to locally managed format.
// *Action: Reissue this command once SYSTEM tablespace migration is over.
10641, 00000, "Cannot find a rollback segment to bind to"
// *Cause: SYSTEM tablespace migration requires rollback segment in locally
// managed tablespace.
// *Action: Drop rollback segments in dictionary managed tablespaces other than
// SYSTEM and create rollback segments in locally managed tablespace
// and retry migration.
10642, 00000, "Found rollback segments in dictionary managed tablespaces"
// *Cause: When SYSTEM tablespace is migrated found rollback segments in
// dictionary managed tablespaces.
// *Action: Drop the rollback segments in dictionary managed tablespaces and
// reissue the command
10643, 00000, "Database should be mounted in restricted mode and Exclusive mode"
// *Cause: When SYSTEM tablespace is being migrated database should be mounted
// in Exclusive mode and in Restricted mode.
// *Action: Reissue this command after mounting the database in right mode.
10644, 00000, "SYSTEM tablespace cannot be default temporary tablespace"
// *Cause: When SYSTEM tablespace is being migrated no user should have
// SYSTEM as the default temporary tablespace.
// *Action: Reissue this command after altering the default temporary
// tablespace setting for all users.
10645, 00000, "Recursive Extension in SYSTEM tablespace during migration"
// *Cause: When SYSTEM tablespace is being migrated, dictionary tables tried
// to extend recursively. Must be caught and processed internally.
// Should not be thrown to the user.
// *Action: Report the error as a bug.
10646, 00000, "Too many recursive extensions during SYSTEM tablespace migration"
// *Cause: When SYSTEM tablespace is being migrated, dictionary tables tried
// to extend recursively more than 1000 times.
// *Action: If SYSTEM tablespace is very large, then simply reissue the
// tablespace migration command.
10647, 00000, "Tablespace other than SYSTEM, %s, %s not found in read only mode"
// *Cause: When SYSTEM tablespace is being migrated, tablespaces other than
// the three should be ALTERed to read only.
// *Action: Alter the tablespace status to read only and retry migration.
10648, 00000, "Tablespace SYSAUX is not offline"
// *Cause: The SYSAUX tablespace
// was online while SYSTEM tablespace was being migrated.
// *Action: Alter the SYSAUX tablespace status to offline and retry migration.
10649, 00000, "Turn off/trace lob index freelist coalesce"
// *Cause: Will turn off or trace lob index freelist coalescing
// *Action: set this event only under the supervision of Oracle development
10650, 00000, "disable cache-callback optimisation"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
10651, 00000, "incorrect file number block number specified"
// *Cause: The dba specified is not valid
// *Action: Check if the dba specified belongs to the segment and is under the
// segment HWM and reissue the statement
10652, 00000, "Object has on-commit materialized views"
// *Cause: It is illegal to issue shrink on an object with on-commit
// materialized views
// *Action:
10653, 00000, "Table is in a cluster"
// *Cause: It is illegal to shrink a table belonging to a cluster
// *Action:
10654, 00000, "Table is of type temporary or external"
// *Cause: It is illegal to shrink a temporary table or an external table
// *Action:
10655, 00000, "Segment can be shrunk"
// *Cause: Error message returned when called in probe mode by OEM
// *Action:
10656, 00000, "Table is in unusable state due to incomplete operation"
// *Cause: ALTER TABLE SHRINK operation was tried on the table which is in
// unusable state because of previously failed/incomplete operation.
// *Action: If the previous operation was
// - DROP COLUMN, resubmit DROP COLUMN CONTINUE
// - DROP TABLE, resubmit DROP TABLE <table> PURGE
10657, 00000, "Lob column to be shrunk does not exist"
// *Cause: Shrink was issued on a lob segment that did not exist
// *Action:
10658, 00000, "Lob column to be shrunk is marked unused"
// *Cause: Shrink was issued on a lob segment that is marked as unused
// *Action:
10659, 00000, "Segment being shrunk is not a lob"
// *Cause: Shrink was issued on a segment that should be a first class lob
// or other data type stored in lob
// *Action:
10660, 00000, "Segment is a shared lob segment"
// *Cause: Shrink was issued on a segment that was being shared by multiple
// lob columns
// *Action:
10661, 00000, "Invalid option specified"
// *Cause: Check option can be specified for one segment only
// *Action:
10662, 00000, "Segment has long columns"
// *Cause: Shrink was issued on a segment with long columns. This is not
// supported.
// *Action:
10663, 00000, "Object has rowid based materialized views"
// *Cause: Shrink was issued on an object with rowid based materialized
// views.
// *Action: Drop the rowid based materialized views and issue shrink on the
// object
10664, 00000, "Table has bitmap join indexes"
// *Cause: SHRINK was issued on a table with bitmap join indexes.
// *Action: Drop bitmap join indexes and reissue SHRINK on the object.
10665, 00000, "Inject Evil Literals"
// *Cause: Event 10665 is set to some number > 0, causing 1/(value-1) of all
// literals to be replaced by 2000 letter 'A's. A value of 1 does
// not corrupt anything.
// *Action: never set this event
10666, 00000, "Do not get database enqueue name"
// *Cause:
// *Action:
10667, 00000, "Cause sppst to check for valid process ids"
// *Cause:
// *Action:
10668, 00000, "Inject Evil Identifiers"
// *Cause: event 10668 is set to some number > 0, causing 1/(value-1) of all
// identifiers to be replaced by a maximum amount of x's. It is
// common for an identifier to be parsed once with a max of 30 bytes,
// then reparsed later with a max of 4000, so it may not be possible
// to inject such an identifier without the aid of this event. A
// value of 1 causes no identifiers to be corrupted.
// *Action: never set this event
10690, 00000, "Set shadow process core file dump type (Unix only)"
// *Cause: Control core file size for shadow processes
// *Action: Level 1: Detach SGA before dumping core
// Level 2: Do not produce any core
10691, 00000, "Set background process core file type (Unix only)"
// *Cause: Control core file size file for background processes
// *Action: Level 1: Detach SGA before dumping core
10692, 00000, "Trace preserving buffer across standby role transition"
// *Document: NO
// *Cause: For internal debugging only.
// *Action:
// level: 0x01 trace preserving buffer across standby role transition
// level: 0x02 trace preserving session across standby role transition
10693, 00000, "Internal event"
// *Document: NO
// *Cause:
// *Action: No action required.
10700, 00000, "Alter access violation exception handler"
// *Cause: Use this event to control what the VMS exception handler
// does when it encounters an access violation.
// *Action:
// Level: >=10 Suspend current process on access violation
// *** SET THIS EVENT ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT ***
10701, 00000, "Dump direct loader index keys"
// *Cause: Dumps index keys at various points in a direct load based on the
// value of this event.
// *Action:
// *Comment: This is bit mask, interpreted as follows:
// 0x01: dump all keys as they are being built (use judiciously,
// as this generates a lot of data!)
// 0x02: dump index keys which cause OER(1), OER(1409), OER(1452)
// errors.
//
10702, 00000, "Application continuity debugging was not enabled"
// *Cause: Enable application continuity debugging
// *Action: Level indicates details.
// Level: 0x0001: Transaction intention debugging
// 0x1000: Failure injection testing
// 0x2000: Failure injection testing
// 0x4000: Failure injection testing
10704, 00000, "Print out information about what enqueues are being obtained"
// *Cause: When enabled, prints out arguments to calls to ksqcmi and
// ksqlrl and the return values.
// *Action: Level indicates details:
// Level: 1-4: print out basic info for ksqlrl, ksqcmi
// 5-9: also print out stuff in callbacks: ksqlac, ksqlop
// 10+: also print out time for each line
10706, 00000, "Print out information about global enqueue manipulation"
// *Cause: When enabled, prints out activity in ksi routines.
// *Action: INternal system parameter (_ksi_trace) can be used in addition
// to setting this event to limit output information on selected
// set of global enqueue server enqueue type(s)
// For example:
// _ksi_trace = RTXA
// output information only for RT and XA lock types.
//
// *Action: Level indicates details:
// 0-4: show args for each main call
// 5-9: also indicate callbacks
// 10+: also printout time for each line
10707, 00000, "Simulate process death for instance registration"
// *Cause: When enabled, process commits suicide to test instance
// registration recovery code.
// *Action: Level indicates where the process will die
10708, 00000, "print out trace information from the RAC buffer cache"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
10709, 00000, "enable parallel instances in create index by default"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: this causes all create index statement to by default
// use multiple instances. it is for testing purposes only.
// the level set in the event is the number of instances.
// *Comment: enables analysis of parallel create index - query coordinator
/
/ 10710 - 10729 are Reserved for BITMAP row sources
/
10710, 00000, "trace bitmap index access"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: display the start-rowid, end-rowid of each bitmap segment - kkrbx
// row source
10711, 00000, "trace bitmap index merge"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables analysis of bitmap index merge - kkrbu row source
10712, 00000, "trace bitmap index or"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables analysis of bitmap index or - kkrbo row source
10713, 00000, "trace bitmap index and"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables analysis of bitmap index and - kkrba row source
10714, 00000, "trace bitmap index minus"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables analysis of bitmap index minus - kkrbm row source
10715, 00000, "trace bitmap index conversion to rowids"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables analysis of bitmap index merge - kkrbt row source
10716, 00000, "trace bitmap index compress/decompress"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables analysis of bitmap index compression/decompression -
// modules kdibc, kdibci, kdibco, kdibc3
/
10717, 00000, "trace bitmap index compaction trace for index creation"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables analysis of bitmap index creation -
// modules kkrbc
/
10718, 00000, "event to disable automatic compaction after index creation"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables isolation of index creation problems. ie compaction
// is an optional part of the index creation algorithem which
// improves query performance and shrinks index size
// modules kkrbc
/
10719, 00000, "trace bitmap index dml"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables analysis of inserts update and deletes into tables
// with bitmap indexes
// modules kkrbc
/
10720, 00000, "trace db scheduling"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: traces db scheduling
/
10721, 00000, "Internal testing - temp table transformation"
// *Cause:
// *Action:
/
10722, 00000, "trace server level database scheduling"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: event is passed to KSKTRC* functions
/
10723, 00000, "Internal testing - release buffer for buffer cache shrink"
// *Cause:
// *Action:
/
10724, 00000, "trace cross-instance broadcast"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables tracing of cross-instance broadcast (KSXR)
/
10725, 00000, "bitmap index version control"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// The trace level is a bitfield, so use it as you would a flag.
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 For bitmap indexes with version 0, DML on these bitmap
// indexes will be same as with 9i releases (that is, it
// simulates the bitmap index DML of previous releases).
/
10726, 00000, "frequent itemset counting"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables tracing of internal execution of frequent itemset
// counting
/
10727, 00000, "introduce failure events in IPC"
// *Document: NO
// *Cause:
// *Action: Internal testing only.
// *Comment:
/
10728, 00000, "set parameters for CPU frequency calculation (debug)"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: changes parameters for CPU frequency calculation
/
/ 10730 - 10800 general debugging events
/
10730, 00000, "trace row level security policy predicates"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
10731, 00000, "dump SQL for CURSOR expressions"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: traces SQL statements generated to execute CURSOR expressions
/
10732, 00000, "honor pctfree during insert into AQ IOTs"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: If set, then we will honor pctfree, during SQL INSERTs and direct
// kdiins0 calls from AQ, for IOTs that are used as AQ queue tables.
/
10733, 00000, "test transient-IOT metadata during PMO cleanup"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: causes an internal error to be raised if inconsistent metadata
// is detected during cleanup of transient-IOTs which were left
// behind by failed Partition Maintenance Operations. Enable this
// event only during testing.
/
10734, 00000, "reroute external procedures"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: execute external procedures using plsql
/
10735, 00000, "debug ksws operations"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: Causes debug trace to be dumped for ksws routines
/
10736, 00000, "buffer cache pin history dump"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// Trace level is a bitfield.
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 Force redo dump during buffer pin history dump
// 0x0002 Disable redo dump during buffer pin history dump
// 0x0004 Print diagnostic text for the redo dump
//
/
10737, 00000, "test block checking"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Internal testing event for block checking.
/
10738, 00000, "internal block testing"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
/
10739, 00000, "debug WLM (kywm) operations"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: Causes debug trace to be dumped for kywm routines
/
10740, 00000, "disables fix for bug 598861"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: disables fix for bug 598861. The fix changes slightly the cost
// estimations for set queries in views, and thereby
// changes query plans from previous versions
// modules vop
/
10741, 00000, "trace missing BRR generation"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// Trace level is a bit field.
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0000 Default of tracing missing BRR after 3 attempts
// 0x0001 Disable default of tracing missing BRR after 3 attempts
// 0x0002 Trace missing BRR due to Oracle RAC pings
// 0x0003 Disable default of tracing missing BRR after 3 attempts and
// trace missing BRR due to Oracle RAC pings
/
10742, 00000, "dump process state on flush buffer_cache"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Causes a process state to be dumped on ALTER SYSTEM FLUSH
// BUFFER_CACHE.
/
10743, 00000, "define the misbehaved vt dump thresholds"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: sets the misbehaved-vt and no-ksucki-vt thresholds used by
// kgskupdbalance()
/
10744, 00000, "disable LMD stale cvak traces and dumps"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: Disables stale cvak traces and dumps from kjakcai() that are
// dumped to LMD trace file
/
10745, 00000, "enable LCK1 kqlmbivg-NULL-kglhdrac dump"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Enables kqlmbivg-NULL-kglhdrac process state dump from kqlmbivg()
/
10746, 00000, "enable KGCE_DEBUG_MODE"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Enables KGCE_DEBUG_MODE to debug Generic Cryptography in server
/
10750, 00000, "test rollback segment blksize guessing for index array insert"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: causes internal error to be raised if a transaction
// repeatedly (100 times) fails to bind to a rollback segment
// because block size is too small. (Default behaviour is to
// silently assume the minimum database block size possible after
// that many failures). Enable this event only during testing.
/
10751, 00000, "override for remote row source maximum buffer size"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: To change the default value of 256000.
/
10752, 00000, "override for the Exponential Moving Average factor"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: To change the default value of 50%.
/
10753, 00000, "enforce deterministic behaviour for prefetching row source"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: prefetch will disregard buffer cache state and be deterministic
// based on level set
// Trace level is a bitfield.
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 Always enable prefetching
// 0x0002 Always disable prefetching
// 0x0004 Print diagnostic text for each of the above levels, ie
// use level 5 to trace enabling and level 6 to trace disabling.
/
10754, 00000, "disable fix for bug 14173995 for multi-table select for update"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
//
/
10755, 00000, "Event to store SIG_1551 stacks to KST"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
//
/
10756, 00000, "Event to enable svpt/autotxn tracing"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
//
/
10757, 00000, "Event to control tracing row source: rows to dump per rowset"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
//
/
10758, 00000, "Event to control tracing row source: start row number"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
//
/
10759, 00000, "Event to control tracing row source: end row number"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
//
/
10760, 00000, "Event to control tracing row source: maximum encoded operands to check"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
//
/
10761, 00000, "Event to control tracing row source: size of dictionary"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
//
/
/ 10780 - 10785 Reserved for LogMiner
10780, 00000, "LogMiner API trace event"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables kst tracing of logminer internal api
/
10781, 00000, "LogMiner reader trace event"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables kst tracing of logminer reader process
/
10782, 00000, "LogMiner preparer trace event"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables kst tracing of logminer preparer process
/
10783, 00000, "LogMiner builder trace event"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables kst tracing of logminer builder process
/
10784, 00000, "LogMiner dictionary trace event"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables kst tracing of logminer dictionary
/
10785, 00000, "LogMiner trace event"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
/
/ 10786 - 10788 Reserved for ks*
10786, 00000, "call push/pop (KSU)"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables tracing of call push/pop operations
/
10787, 00000, "trace intra-instance broadcast"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables tracing of intra-instance broadcast (KSR)
/
10788, 00000, "trace call stacks"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables tracing of call stack info
/
/ 10789 - 10790 Reserved for LogMiner
10789, 00000, "LogMiner test event"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: changes logminer behavior for testing
/
10790, 00000, "LogMiner trace event"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
/
/ 10791 - 10799 Reserved for Logical Standby
10791, 00000, "Logical Standby swithover/failover trace event"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables kst trancing of switchover and failover in logical
/
10792, 00000, "Logical Standby XDAT trace event"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: enables kst trancing os XDAT usage
/
10793, 00000, "Logical Standby trace event"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
/
10794, 00000, "Logical Standby trace event"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
/
10795, 00000, "VKTM Process trace event"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle Support Services.
// *Comment: enable ksd/kst tracing for VKTM process
/
10796, 00000, "Elevate Scheduler Priority trace event"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development
// *Comment: enable ksd tracing for elevate/revert process scheduler priority
/
10797, 00000, "Logical Standby Test Event"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: changes logical standby behavior for testing
/
10798, 00000, "debug GSM operations"
// *Document: NO
// *Cause:
// *Action: set this event only under the supervision of Oracle development
// *Comment: Causes debug trace to be dumped for gsm routines
/
10800, 00000, "disable Smart Disk scan"
// *Document: NO
// *Cause:
// *Action:
10804, 00000, "reserved for ksxb"
// *Cause:
// *Action:
10806, 00000, "Switch to 7.3 mode when detaching sessions"
// *Cause:
// *Action:
10807, 00000, "Disable user id check when switching to a global transaction"
// *Cause:
// *Action:
10808, 00000, "Enable assert when waiting without a reason"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development
// *Comment: This event will catch clients that call kslwait without providing
// any wait reason (see bug 1743159).
10809, 00000, "Trace state object allocate / free history"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle development
// *Comment: This event will trace the history of KSS allocations / deletions.
// level: 0 = disabled, 1 = cleanup only, 2 = always
/
/
/ 10810 - 10825 Reserved for OLTP
/
10810, 00000, "Trace snapshot too old"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
10811, 00000, "Trace block cleanouts"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
10812, 00000, "Trace Consistent Reads"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
/
/ 10826 - 10829 Reserved for upgrade/downgrade
/
10826, 00000, "enable upgrade/downgrade error message trace"
// *Document: NO
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
10827, 00000, "enable upgrade/downgrade diagnostics"
// *Document: NO
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
10828, 00000, "memory allocator error"
// *Cause: Error in the memory allocator
// *Action: Check the trace files and other relevant output
10829, 00000, "enable error suppression in NORMAL mode"
// *Document: NO
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR ERROR SUPPRESSION.
/
/ 10830 - 10838 Reserved for sort and aggregation row sources
/
10830, 00000, "Trace group by sort row source"
// *Cause:
// *Action: set this event only under the supervision of Oracle development.
// trace level is a bitfield
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 trace adaptive fetch usage
// 0x0002 trace exceptions during aggregation
// 0x0004 trace use of one comparison for all key columns
//
10831, 00000, "Trace group by rollup row source"
// *Cause:
// *Action: set this event only under the supervision of Oracle development.
// trace level is a bitfield
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 trace use of one comparison for all key columns
/
10832, 00000, "Trace approximate NDV row source"
// *Cause:
// *Action: set this event only under the supervision of Oracle development.
// trace level is a bitfield
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 trace
/
10833, 00000, "Runtime distribution keys for adaptive partial rollup"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// This event is only effective when adaptive mode for partial
// rollup pushdown is enabled. Trace level indicates the number of
// rollup keys used for data distribution. When this event is
// effective, counting of the number of distinct values (NDVs) is
// not performed and the distribution decision is solely based on
// the level specified. If the adaptive mode is not enabled, this
// event is ignored.
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// lvl>=1 number of composite rollup keys used for data distribution
/
10834, 00000, "Runtime behavior control for adaptive partial rollup"
// *Cause:
// *Action: Set this event only under the supervision of Oracle development.
// This event is only effective when adaptive mode for partial
// rollup pushdown is enabled. If the adaptive mode is not enabled,
// this event is ignored.
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 trace adaptive mode for partial rollup pushdown
// 0x0002 disable early decision and periodical slave-to-QC
// communication
// 0x0004 disable pass-through mode of sort2 (buffer) in rollup
// distributor even if pass-through is feasible
// 0x0008 allow only the first rollup distributor slave to make an
// early decision
/
10835, 00000, "exclude SYS_OP_CYCLED_SEQ from TQ keys for scalable percentile"
// *Document: NO
// *Cause: N/A
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Not for general purpose use.
// LEVEL ACTION
//---------------------------------------------------------------------------
// > 0 Do not attempt to include SYS_OP_CYCLED_SEQ as part of TQ keys
// for scalable computation of percentile functions.
/
10839, 00000, "trace / debug caching module (qesca.c)"
// *Cause:
// *Document: NO
// *Action: Set this event only under the supervision of Oracle Development.
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 trace / debug caching
// 0x0002 dump probe / retrieve / insert cache values
/
10840, 00000, "trace / debug pl/sql caching module (kkxmInitCache)"
// *Cause:
// *Document: NO
// *Action: Set this event only under the supervision of Oracle Development.
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 trace / debug pl/sql caching
/
/ 10841 - 10849 Reserved for OCI
/
10841, 00000, "Default un-inintialized charact set form to SQLCS_IMPLICIT"
// *Cause: client side, such as JDBC-THIN 8i client sends 0 as charset form
// *Action: This event sets charset form as SQLCS_IMPLICIT when it is 0
10842, 00000, "Event for OCI Tracing and Statistics Info"
// *Cause: This event is meant for tracing OCI Calls and getting statistics
// *Action: This event sets tracing OCI Calls and gets statistics info
10843, 00000, "Event for client result cache tracing"
// *Document: NO
// *Cause: This is an internal event.
// *Action: N/A
10844, 00000, "turn on Native Net IPC debugging (skgxp)"
// *Cause:
// *Action: Enables debugging code for Native Net IPC (skgxp)
10845, 00000, "Enable Director tracing"
// *Cause: N/A
// *Action: Enable tracing of director/workload manager packages
/
10846, 00000, "Event for non-blocking testing"
// *Document: NO
// *Cause: N/A
// *Action: Enable forced non-blocking testing
/
10847, 00000, "OCI dump action is being invoked for internal error ORA-%s"
// *Document: NO
// *Cause: An internal error was encountered, or EVENT_10847 was set to
// a level other than 2 or 0. This dumped the OCI process state,
// current state and the stack trace.
// *Action: Disable EVENT_10847. If disabled, contact Oracle Support for the
// internal error.
/
10848, 00000, "OCI Non Blocking not supported with %s"
// *Cause: Attempt made to set connection as non-blocking with another
// feature that does not support non-blocking.
// *Action: Use blocking connection.
/
10849, 00000, "Internal OCI event number"
// *Cause: N/A
// *Action: Set this event only under the supervision of Oracle Support
// or Development. This event enable compatible behavior with
// sending describe information when a cursor rebuilt.
/
/
/ 10850 - 10869 Reserved for AQ
/
10850, 00000, "Enable time manager tracing"
// *Cause:
// *Action:
10851, 00000, "Allow Drop command to drop queue tables"
// *Document: NO
// *Cause: re-enable SQL Drop DDL for queue tables.
// *Action: last resort to drop queue table if all other options fail. The
// user have to manually cleanup AQ's metadata after this operation.
10852, 00000, "Enable tracing for Enqueue Dequeue Operations"
// *Document: NO
// *Cause: NA
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
10853, 00000, "Enable tracing for Replicating AQ Operations "
// *Document: NO
// *Cause: NA
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
10854, 00000, "Sets poll count used for AQ listen code under RAC"
// *Document: NO
// *Cause: NA
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
10856, 00000, "Disable AQ propagator from using streaming"
// *Document: NO
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
10857, 00000, "Force AQ propagator to use two-phase commit"
// *Document: NO
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
10858, 00000, "Crash the AQ propagator at different stages of commit"
// *Document: NO
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
10859, 00000, "Disable updates of message retry count"
// *Document: NO
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DISABLING THE RETRY
// FEATURE IN THE EVENT THAT IT CAUSES OTHER INTERNAL ERRORS.
10860, 00000, "event for AQ admin disable new name parser"
// *Document: NO
// *Cause: NA
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
// THIS EVENT IS NOT TO BE TURNED ON BY ANY CUSTOMER. DOING SO,
// MAY CAUSE AQ DICTIONARY CORRUPTION
10861, 000000, "disable storing extended message properties"
// *Document: NO
// *Cause: NA
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY TO DISABLE STORING
// NEW MESSAGE PROPERTIES SUCH AS SENDER_ID AND ORIGINAL_MESSAGE_ID.
//
10862, 00000, "resolve default queue owner to current user in enqueue/dequeue"
// *Cause: resolve default queue owner to current user in enqueue/dequeue.
// *Action: turn on if client wish to resolve the default queue owner to the
// current user. If not turned on, the default queue owner will be
// resolved to the login user.
10863, 00000, "Control behavior of buffered background operations"
// *Document: NO
// *Cause: NA
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
10864, 00000, "event to enable AQ dedicated propagation"
// *Document: NO
// *Cause: NA
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. WHEN THIS EVENT IS SET, ONE JOB QUEUE
// PROCESS WILL PROPAGATE FOR ONLY ONE PROPAGATION SCHEDULE
10865, 00000, "Control tracing of notification operations"
// *Document: NO
// *Cause: NA
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
10866, 00000, "event to order dequeue by condition"
// *Document: NO
// *Cause: NA
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. WHEN THIS EVENT IS SET, THE DEQUEUE
// ORDER THE MESSAGES BASED ON CONDITION.
//
10867, 00000, "turn off authentication for emon to oci client and disable HA rstat"
// *Document: NO
// *Cause: NA
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. WHEN THIS EVENT IS SET, THERE IS NO
// MUTUAL AUTHENTICATION BETWEEN EMON AND OCI CLIENTS IF SET AT LEVEL 1
// AND LEVEL 2 IS USED FOR DISABLING THE UPDATION OF REGISTRATION
// STATISTICS FOR HA NOTIFICATIONS
//
10868, 00000, "event to enable interop patch for AQ enqueue options"
// *Document: NO
// *Cause: NA
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. WHEN THIS EVENT IS SET, AQ DOES NOT
// USE ENQUEUE OPTIONS FOR PROPAGATION.
//
/
/ 10870 - 10879 Reserved for recovery layer
/
10870, 00000, "Disable multi-instance standby role transition"
// *Document: No
// *Cause:
// *Action: For testing purposes
10871, 00000, "dump file open/close timestamp during media recovery"
// *Document: No
// *Cause:
// *Action: For dumping purpose.
/
10872, 00000, "Flashback Database fault insertion event #%s."
// *Document: NO
// *Cause: Causes faults to be inserted into Flashback Database code.
// This should only be enabled for internal testing.
// *Action: Level 1 - Die after restoring database, before shrinking
// fuzziness.
// Level 2 - Die after rstoring database and after shrinking
// fuzziness.
// Level 3 - Die after restoring control file.
// Level 4 - Die after set cf checkpoint during an undo of a cf change
// Level 5 - Die after restoring cf, before setting cf checkpoint
// Level 6 - Force a block checksum error on a flashback log block
// Level 7 - Force a file creation error during fb recovery
// Level 8 - Force an error after fb recovery file recreation
// Level 9 - Force and error during open resetlogs (after flashback)
//
10873, 00000, "file %s needs to be either taken out of backup mode or media recovered"
// *Cause: An attempt was made to open a database after an instance failure or
// SHUTDOWN ABORT interrupted an online backup.
// *Action: If the indicated file is not a restored backup, then issue the
// ALTER DATABASE END BACKUP command and open the database. If the
// file is a restored online backup, then apply media recovery to
// it and open the database.
10874, 00000, "Change max logfiles in hashtable in krfbVerifyRedoAvailable"
// *Document: No
// *Cause:
// *Action: For testing purposes
//
10875, 00000, "Require instance bounce after switchover to primary"
// *Document: No
// *Cause:
// *Action: For testing purposes
//
/
10876, 00000, "IDR Test event"
// *Document: No
// *Cause:
// *Action: Level 1 - x$ir_working_repair_set returns manual options.
// Should only be used when testing IR framework.
// 2 - force a failure revalidation timeout.
// 3 - force a failure in getAdviseID.
// 4-7 - simulate ADR timeout.
// 8 - simulate ADR lock busy error
// 9 - simulate OMF template name for logfile members
//
/
10877, 00000, "error signaled in parallel recovery slave %s"
// *Cause: A parallel recovery logmerger reached an exception condition.
// *Action: Check the following error message for the cause, and consult
// your error manual for the appropriate action.
//
/
10878, 00000, "parallel recovery slave died unexpectedly"
// *Cause: A parallel recovery slave died unexpectedly, PMON cleaning
// up the process.
// *Action: Check your system for anomalies and reissue the statement.
// If this error persists, contact Oracle Support Services.
// See trace file for more details.
/
10879, 00000, "error signaled in parallel recovery slave %s"
// *Cause: A parallel recovery slave reached an exception condition.
// *Action: Check the following error message for the cause, and consult
// your error manual for the appropriate action.
//
/
/ 10880 - 10882 Reserved for Java Virtual Machine
/
10880, 00000, "trace Java VM execution"
// *Document: NO
// *Cause
// *Action
//
/
10883, 00000, "Event for Fast Application Notification tracing"
// *Cause: This event sets tracing for Fast Application Notification (FAN).
// *Action: Level 5 - Set this level to dump out all FAN High Availability
// related messages to trace files. This includes event
// payloads and error messages.
// 10 - Set this level to dump out FAN Runtime Load Balancing
// related messages. This includes RLB payloads and error
// messages.
/
10884, 00000, "TTC event"
// *Document: NO
// *Cause:
// *Action:
//
/
10885, 00000, "Switchover test event"
// *Document: NO
// *Cause:
// *Action:
10886, 00000, "Recovery test event"
// *Document: NO
// *Cause:
// *Action:
/
10887, 0000, "An Oracle Active Data Guard license is required to open a pluggable database while standby recovery is applying changes."
// *Document: Yes
// *Cause: An attempt was made to open a pluggable database without the Oracle
// Active Data Guard license.
// *Action: Do not open a pluggable database or acquire the Oracle Active Data
// Guard license.
/
10888, 00000, "TTC event for optimized fetch"
// *Document: NO
// *Cause:
// *Action:
//
/
10889, 0000, "minimum number of instances needed for redo apply unavailable"
// *Document: Yes
// *Cause: An attempt was made to start multi-instance redo apply with less
// than two instances in either a mounted or open state.
// *Action: Mount or open at least two instances.
/
10890, 00000, "ADG test event"
// *Document: NO
// *Cause:
// *Action:
/
10891, 00000, "disable column pruning in ANSI join transformation"
// *Document: NO
// *Cause: N/A
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Not for general purpose use.
// LEVEL ACTION
//---------------------------------------------------------------------------
// > 0 Do not attempt to automatically prune away unreferenced
// columns during ANSI join transformation when compiling SQL
// queries.
/
10892, 00000, "multi-instance redo apply encountered nonlogged operation"
// *Document: YES
// *Cause: Multi-instance Redo Apply did not support applying invalidation
// redo. Invalidation redo is created as part of performing a
// nonlogged operation. Details of the first data block affected by
// the nonlogged operation can be found in the alert log.
// *Action: Restart recovery using single instance Redo Apply. Do not specify
// the INSTANCE keyword in the command to start recovery.
/
10893, 00000, "TTC trace event"
// *Document: NO
// *Cause
// *Action
//
/
10898, 00000, "LGWR timing event"
// *Document: NO
// *Cause:
// *Action:
/
/ 10900 - 10924 Reserved for SPACE management
/
10900, 00000, "extent manager fault insertion event #%s"
// *Cause: causes faults to be generated in instrumented extent code
// *Action: this should only be enabled for internal testing
/
/ 10901 - used in 7.3.4 for disabling extent trimming for merge
/
10901, 00000, "disable the fix for bug 1230798"
// *Cause:
// *Action:
10902, 00000, "disable seghdr conversion for ro operation"
// *Cause: causes seghdr conversion to be turned off for ro ops(#555856)
// *Action: this should be enabled only if determined that bug 555856
// has occured. Table needs to be exported subsequently
10903, 00000, "Force tablespaces to become locally managed"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
10904, 00000, "Allow locally managed tablespaces to have user allocation"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY BY IMPORT CODE.
10905, 00000, "Do cache verification (kcbcxx) on extent allocation"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
10906, 00000, "Unable to extend segment after insert direct load"
// *Cause: This is a restriction with insert direct load transactions.
// *Action: When a segment has been insert direct loaded, avoid DMLs that
// could cause more space to be consumed.
10907, 00000, "Trace extent management events"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
10908, 00000, "Trace temp tablespace events"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
10909, 00000, "Trace free list events"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
10910, 00000, "inject corner case events into the RAC buffer cache"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
10911, 00000, "Locally managed SYSTEM tablespace bitmaps can be modified only under the supervision of Oracle Support"
// *Cause: N/A
// *Action:
10912, 00000, "Used to perform admin operations on locally managed SYSTEM tablespace"
// *Cause: N/A
// *Action: The event should be used only under the supervision of
// Oracle Support
10913, 00000, "Create locally managed database if compatible > 920 by default"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR DEBUGGING.
10914, 00000, "invalid TABLESPACE GROUP clause"
// *Cause: An invalid option appears for TABLESPACE GROUP clause.
// *Action: Specify a valid tablespace group name.
10915, 00000, "TABLESPACE GROUP cannot be specified for this type of tablespace"
// *Cause: In CREATE/ALTER TABLESPACE, the TABLESPACE GROUP clause was used
// while creating/altering a tablespace that is not TEMPORARY.
// *Action: Remove the TABLESPACE GROUP clause.
/
10916, 00000, "TABLESPACE GROUP already specified"
// *Cause: In CREATE/ALTER TABLESPACE, the TABLESPACE GROUP option was
// specified more than once.
// *Action: Remove all but one of the TABLESPACE GROUP specifications.
/
10917, 00000, "TABLESPACE GROUP cannot be specified"
// *Cause: The tablespace name specified in the command
// is actually the name of a tablespace group.
// *Action: Please specify an appropriate tablespace name.
/
10918, 00000, "TABLESPACE GROUP name cannot be the same as tablespace name"
// *Cause: The tablespace group name specified in the command
// is the same as the tablespace being CREATEd/ALTERed.
// *Action: Please specify an appropriate tablespace group name.
/
10919, 00000, "Default temporary tablespace group must have at least one tablespace"
// *Cause: An attempt was made to move the only tablespace in the default
// database temporary tablespace group to another tablespace group.
// *Action: Either change the database default temporary tablespace or
// add another tablespace to the group that this tablespace belongs to.
/
10920, 00000, "Cannot offline tablespace belonging to default temporary tablespace group"
// *Cause: An attempt was made to offline a tablespace in the default
// database temporary tablespace group.
// *Action: Either change the database default temporary tablespace or
// change the tablespace group of this tablespace.
/
10921, 00000, "Cannot drop tablespace belonging to default temporary tablespace group"
// *Cause: An attempt was made to drop a tablespace in the default
// database temporary tablespace group.
// *Action: Either change the database default temporary tablespace or
// change the tablespace group of this tablespace.
/
10922, 00000, "Temporary tablespace group is empty"
// *Cause: An attempt was made to allocate a temporary segment in a group,
// which now no longer has any members.
// *Action: Either add some temporary tablespaces or change the
// temporary tablespace for this user.
/
10923, 00000, "prints debug information for object space server manageability"
// *Cause:
// *Action:
10924, 00000, "import storage parse error ignore event"
// *Cause: causes server to ignore specific error associated with freelists
// and freelist groups when parsing
// *Action: this should be enabled by import code only
/
// 10925 - 10959 Reserved for PL/SQL
//
/
10925, 00000, "trace name context forever"
// * Cause: When enabled, turns off bugfix 237911
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
10926, 00000, "trace name context forever"
// * Cause: When enabled, turns off bugfix 190119
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
10927, 00000, "trace name context forever"
// * Cause: When enabled, turns off bugfix 235190
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
/
10928, 00000, "trace name context forever"
// * Cause:
// * Action: Set this event only under the supervision of Oracle Development.
// * Comment: This event causes PL/SQL to dump out information to trace files.
10929, 00000, "trace name context forever"
// * Cause: When enabled, turns off bugfix 343966
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
/
/
10930, 00000, "trace name context forever"
// * Cause: When enabled, provides V7 behavior for fixed char binds
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
/
10931, 00000, "trace name context forever"
// * Cause: When enabled, allows normal packages to be compiled with standard
// extensions like "<ADT_1>"
// * Action: Set this event only for a short amount of time. Once the
// packages are compiled, this event should be turned off.
// Level 1 - Turn the event on
// Level > 1 - Turn the event off
/
10932, 00000, "trace name context forever"
// * Cause: When enabled, disables one or more features or bug fixes
// available only in version 8.x.
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
/
/
10933, 00000, "trace name context forever"
// * Cause: When enabled, disables one or more features or bug fixes
// available only in version 8.x.
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
/
/
10934, 00000, "trace name context forever"
// * Cause: When enabled, disables one or more features or bug fixes
// available only in version 11.x.
// * Action: Set this event only if necessary - after reading the README for
// this release or under supervision of Oracle Support Services.
/
/
10936, 00000, "trace name context forever"
// * Cause: When enabled, disables one or more features or bug fixes
// available in versions 7.x and 8.x.
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
/
/
10937, 00000, "trace name context forever"
// * Cause:
// * Action: When set, this event enables tracing of PL/SQL packages.
// * Comment: Setting this event could result in some performance slowdown.
/
/
/
10938, 00000, "trace name context forever"
// * Cause:
// * Action: When set, this event enables tracing of PL/SQL calls and exceptions.
// * Comment: Setting this event could result in some performance slowdown.
/
/
/
10939, 00000, "trace name context forever"
// * Cause:
// * Action: When set, this event turns on coverage for PL/SQL procedures and
// functions.
// * Comment: Setting this event could result in some performance slowdown.
/
/
/
10940, 00000, "trace name context forever"
// * Cause: Size of the PL/SQL tracing circular buffer, in kilobytes.
// * Action: Set this event in concert with the 10938 event and the
// _PLSQL_DUMP_BUFFER_EVENTS init.ora parameter, under supervision
// of Oracle Support.
/
/
/
10941, 00000, "trace name context forever"
// * Cause: When enabled, turns on PL/SQL profiler
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
/
10943, 00000, "trace name context forever"
// * Cause: When enabled, disables one or more features or bug fixes
// available only in version 8.x.
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
/
10944, 00000, "trace name context forever"
// * Cause: When enabled, allows or controls PL/SQL OPT code gen project.
// available only in version 8.2+.
// * Action: set this event ONLY for development of the OPT project.
// This is not for general use or deployment.
10945, 00000, "trace name context forever"
// * Cause: When enabled, disables the behaviour change introduced by the fix
// for bug 822764, which traps and handles invalidations of packages
// whereas the previous behaviour was to use stale invalidated
// instantiations of the stateful package body.
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
10946, 00000, "trace name context forever"
// * Cause: When enabled, disables one or more features or bug fixes
// available only in version 10.x.
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
/
/
10947, 00000, "trace name context forever"
// * Cause: When enabled, causes various PL/SQL warnings related debugging
// info to be written in a trace file. Useful for debugging varous
// Oracle processes. available only in version 10.x.
// * Action: set this event ONLY if necessary - after reading the README for
// this release or under supervision of Oracle Support.
10948, 00000, "trace name context forever"
// * Cause: When enabled, inflate callout argument.
// available only in version 10.x.
// * Action: internal use only.
/
/
10949, 00000, "Disable autotune direct path read for full table scan"
// *Cause:
// *Action: Disable autotune direct path read for serial full table scan.
/
//
/10960 - 10969 Reserved for Advanced Queuing
/
/
10960, 00000, "AQ tracing event"
//*Document: NO
// *Cause:
// *Action:
//
10961, 00000, "Enable tracing for Scheduler subscriber cleanup"
// *Document: NO
// *Cause: NA
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING.
/ 10970 - 10974 Reserved for Lob Access
/
/
10970, 00000, "backout event for bug 2133357"
// *Cause: 2133357 dynamically sets the varying width flag and character width.
// Lob data which is not migrated during migration from single byte to
// multibyte charater set will be displayed as special characters.
// *Action: To help migrate lob data which was not migrated during migration
// by backing out 2133357, so lob data can be selected and moved to
// multibyte character set.
// *Comment: This event is obsolete. It can be reused for some other purpose.
/
10971, 00000, "prints debugging information for LOBs"
// *Document: No
// *Cause:
// *Action: None
/
10972, 00000, "raise a 1551 exception in kdu_array_flush"
// *Document: No
// *Cause:
// *Action: None
/
10973, 00000, "backout evet for 2619509"
// *Cause: 2619509 catches offsets when not reading/writing on full character
// boundary. To facilitate backward compatiblity event is being
// introduced.
// *Action: To help upgrade/migrate issues which already have corrupt data
/
10974, 00000, "Turn on LOB integrity verification"
// *Document: No
// *Cause:
// *Action: None
/
//
/ 10975 - 10995 Reserved for Replication
/
/
10975, 00000, "trace execution of parallel propagation"
// *Document: NO
// *Cause:
// *Action:
10976, 00000, "internal package related tracing"
// *Document: NO
// *Cause:
// *Action:
/ LEVEL ACTION
//---------------------------------------------------------------------------
// > 0 trace the execution of sync procedural replication,
// error execution, $RP/$RL invocation.
// > 1 trace the loading of meta-data into library cache for ip
10977, 00000, "trace event for RepAPI"
// *Document: NO
// *Cause: N/A.
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Not for general purpose use.
10978, 00000, "general event for materialized view logs"
// *Document: NO
// *Cause: N/A
// *Action: This internal event is used to enable various actions
// associated with MV logs. The event level is interpreted
// as a bitmap of actions to enable.
//
// *Comment: Not for general purpose use.
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 use asynchronous purge
// 0x0002 use scheduled purge
// 0x0004 log commit scn when creating MV logs
/
10979, 00000, "trace flags for join index implementation"
// *Cause: This is an informational message.
// *Action: Values are as follows:
// LEVEL ACTION
//---------------------------------------------------------------------------
// > 1 Dump refresh expressions (SQL) to trace file.
// > 999 If a complete refresh is invoked, it will not be performed
// but the system will assume that a complete refresh was done,
// causing the view to be VALID and updating timestamps. This
// should be used only under Oracle Support supervision.
/
10980, 00000, "prevent sharing of parsed query during Materialized View query generation"
// *Document: NO
// *Cause: N/A.
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Not for general purpose use.
10981, 00000, "dscn computation-related event in replication"
// *Document: NO
// *Cause: N/A.
// *Action:
/ LEVEL ACTION
//---------------------------------------------------------------------------
// > 0 During replication enqueue for parallel propagation, make each
// transaction in a session depend on the transaction that
// precedes it in the same session.
/
/
10982, 00000, "event to turn off CDC-format MV Logs"
// *Document: NO
// *Cause: N/A.
// *Action:
/ LEVEL ACTION
//---------------------------------------------------------------------------
// = 999 Revert to pre-CDC original format MV Logs for all
// new MV Logs created.
/
/
10983, 00000, "event to enable Create_Change_Table debugging"
// *Document: NO
// *Cause: N/A.
// *Action:
/ LEVEL ACTION
//---------------------------------------------------------------------------
// > 0 Echo input parameter values to the trace log.
// > 1 Display trigger debug info to the trace log also.
/
/
10984, 00000, "subquery materialized view-related event"
// *Document: NO
// *Cause: N/A
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Not for general purpose use.
/ LEVEL ACTION
//---------------------------------------------------------------------------
// > 0 A REFRESH FAST subquery MATERIALIZED VIEW which
// satisfies the pre 8.2 ORACLE server requirements will be
// treated as a many-many subquery MATERIALIZED VIEW.
/
10985, 00000, "event for NULL refresh of materialized views"
// *Document: NO
// *Cause: N/A
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Not for general purpose use.
/
10986, 00000, "donot use HASH_AJ in refresh"
// *Document: NO
// *Cause: N/A
// *Action: Set this event while doing refresh if the delta snapshot is small
// *Comment: Not for general purpose use.
/ LEVEL ACTION
//---------------------------------------------------------------------------
// > 0 Refresh uses NOT EXISTS sub-query instead of HASH_AJ
/
10987, 00000, "event for the support of caching table with object feature"
// *Document: NO
// *Cause: N/A
// *Action: Set this event while caching tables with object features.
// *Comment: Not for general purpose use.
/ LEVEL ACTION
//---------------------------------------------------------------------------
// > 0 Turn off the checking of object features of a cached table
/
10988, 00000, "event to get exclusive lock during materialized view refresh in IAS"
// *Document: NO
// *Cause: N/A
// *Action: Set this event if you want to get exclusive lock on the Updatable MV container table during refresh in IAS
// *Comment: Not for general purpose use.
// LEVEL ACTION
//---------------------------------------------------------------------------
// > 0 Get exclusive lock on the updatable MV container table during
// refresh in IAS
/
10989, 00000, "event to internally create statistics MV"
// *Document: NO
// *Cause: N/A
// *Action: The event is internally used to create statsMV
// *Comment: Not for general purpose use.
// LEVEL ACTION
//---------------------------------------------------------------------------
// > 0
/
10990, 00000, "dump spreadsheet info"
// *Cause:
// *Action: set this event only under the supervision of Oracle Development
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 dump pruned rules during graph analysis
// 0x0002 dump level of the rules after ordering in graph analysis
// 0x0004 dump spreadsheet filter
/
10991, 00000, "event for optimizing the online redefinition instantiation"
/ *Document: NO
// *Cause: N/A
// *Action: control the optimizations used during online redefinition.
// *Comment: Not for general purpose use.
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 Turn off the index optimization during online redefinition
// instantiation.
// 0x0002 Turn off the ascending scn optimization during online redefinition
// instantiation
// 0x0004 Turn on the index and optimistic ascending scn optimization
// during online redefinition instantiation.
/
10992, 00000, "event to enable dbms_job instead of dbms_scheduler"
// *Cause:
// *Action: enables dbms_job instead of dbms_scheduler
// *Comment: set this event only under the supervision of Oracle Development
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 enable dbms_job instead of dbms_scheduler for MV refresh
/
/
10993, 00000, "Runtime enable IOQ batching"
// *Cause:
// *Action:
// *Comment: set this event only under the supervision of Oracle Development
/
/
10994, 00000, "Compiletime enable IOQ batching"
// *Cause:
// *Action:
// *Comment: set this event only under the supervision of Oracle Development
/
/
10995, 00000, "general event for materialized views"
// *Document: NO
// *Cause: N/A
// *Action: This internal event is used to enable various actions
// associated with MVs. The event level is interpreted
// as a bitmap of actions to enable.
//
// *Comment: Not for general purpose use.
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 enable callback-based refresh
// 0x0002 invalidate dependents for online redef
// 0x0004 allow PCT fast refresh after CONSIDER FRESH
// 0x0008 do not use an extended Merge statement during MAV fast refresh
/
/
/ 10996 - 10998 Reserved for ks*
/
10997, 00000, "another startup/shutdown operation of this instance inprogress"
// *Cause: An Oracle Instance startup or shutdown operation failed to procure
// the serialization primitive. Another foreground process may have
// attempted startup or shutdown operation in parallel.
// *Action: Check additional error messages in the alert log and the process
// trace file.
/
10998, 00000, "event to enable short stack dumps in system state dumps"
// *Document: NO
// *Cause: N/A
// *Action: enables short stack dumps for every active process in a system
// state dump
// *Comment: set this event only under the supervision of Oracle Support
10999, 00000, "do not get database enqueue name"
// *Cause:
// *Action:
/
/ 10999 End Pseudo-error debugging events
/
/ 11000 - 11999 Reserved for mvs sql*net errors
/
11000, 0000, "Force metadata read directly from dictionary."
// *Document: NO
// *Cause: There were changes in metadata query in file kqdsql.h. Force the
// read from dictionary table to make sure there is no regression.
// *Action: Farm submit SUMM_MGMT_PLUS after setting the event at system level.
//
/ 12000 - 12099 Reserved for table materialized view errors
/
12000, 00000, "a materialized view log already exists on table '%s'"
// *Cause:
// *Action:
12001, 00000, "cannot create log: table '%s' already has a trigger"
// *Cause: Materialized view logs are filled by a trigger on the master table.
// That trigger cannot be created.
// *Action: To create a materialized view log, drop the current trigger on the
// master.
12002, 00000, "there is no materialized view log on table \"%s\".\"%s\""
// *Cause: There was no materialized view log on the master table.
// *Action: Create a materialized view log on the master table.
12003, 00000, "materialized view or zonemap \"%s\".\"%s\" does not exist"
// *Cause: The database object with the given owner and name was not found.
// *Action: Verify input and retry.
12004, 00000, "REFRESH FAST cannot be used for materialized view \"%s\".\"%s\""
// *Cause: The materialized view log does not exist or cannot be used. PCT
// refresh is also not enabled on the materialized view
// *Action: Use just REFRESH, which will reinstantiate the entire table.
// If a materialized view log exists and the form of the materialized
// view allows the use of a materialized view log or PCT refresh is
// possible after a given set of changes, REFRESH FAST will
// be available starting the next time the materialized view is
// refreshed.
12005, 00000, "may not schedule automatic refresh for times in the past"
// *Cause: An attempt was made to schedule an automated materialized view
// refresh for a time in the past.
// *Action: Choose a time in the future instead.
12006, 00000, "materialized view or zonemap \"%s\".\"%s\" already exists"
// *Document: NO
// *Cause:
// *Action:
12007, 00000, "materialized view reuse parameters are inconsistent"
// *Cause: The CREATE MATERIALIZED VIEW .. or CREATE MATERIALIZED VIEW LOG ..
// REUSE command was given inconsistent parameters immediately after
// the REUSE.
// *Action: Examine the other messages on the stack to find the problem.
12008, 00000, "error in materialized view or zonemap refresh path"
// *Cause: Table SNAP$_<mview_name> reads rows from the view
// MVIEW$_<mview_name>, which is a view on the master table
// (the master may be at a remote site). Any
// error in this path will cause this error at refresh time.
// For fast refreshes, the table <master_owner>.MLOG$_<master>
// is also referenced.
// *Action: Examine the other messages on the stack to find the problem.
// See if the objects SNAP$_<mview_name>, MVIEW$_<mview_name>,
// <mowner>.<master>@<dblink>, <mowner>.MLOG$_<master>@<dblink>
// still exist.
12009, 00000, "materialized views may not contain long columns"
// *Cause:
// *Action:
12010, 00000, "cannot create materialized view log on table owned by SYS"
// *Cause: An attempt was made to create a materialized view log on the
// table owned by SYS. CREATE MATERIALIZED VIEW LOG attempts to
// create a trigger on the table, but triggers can not be created
// on SYS tables.
// *Action: Do not create a materialized view log on SYS tables.
12011, 00000, "execution of %s jobs failed"
// *Cause: An error was caught in dbms_ijob.run from one or more jobs
// which were due to be run.
// *Action: Look at the alert log for details on which jobs failed and why.
12012, 00000, "error on auto execute of job %s"
// *Cause: An error was caught while doing an automatic execution of a job.
// *Action: Look at the accompanying errors for details on why the execute
// failed.
12013, 00000, "updatable materialized view must be simple enough and have a materialized view log on its master table to do fast refresh"
// *Cause: The updatable materialized view query contained a JOIN, SUBQUERY,
// UNION, CONNECT BY, ORDER BY, or GROUP BY clause, or the master
// table did not have a materialized view log.
// *Action: Make the materialized view simpler. If a join is really needed,
// make multiple simple materialized views then put a view on top of
// them. Make sure a materialized view log is created for the master
// table.
12014, 00000, "table '%s' does not contain a primary key constraint"
// *Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the
// WITH PRIMARY KEY option and the master table did not contain
// a primary key constraint or the constraint was disabled.
// *Action: Reissue the command using only the WITH ROWID option, create a
// primary key constraint on the master table, or enable an existing
// primary key constraint.
12015, 00000, "cannot create a fast refresh materialized view from a complex query"
// *Cause: Neither ROWIDs and nor primary key constraints are supported for
// complex queries.
// *Action: Reissue the command with the REFRESH FORCE or REFRESH COMPLETE
// option or create a simple materialized view.
12016, 0000, "materialized view does not include all primary key columns"
// *Cause: The query that instantiates the materialized view did not include
// all of the columns in the master's primary key constraint.
// *Action: Include all of the master's primary key columns in the materialized
// view query or create a ROWID materialized view.
12017, 0000, "cannot alter primary key mview '%s' to a rowid mview"
// *Cause: An attempt was made to convert the primary key of a materialized
// view to a ROWID materialized view.
// *Action: Conversion of a primary key materialized view to a ROWID
// materialized view is not supported. Create a new materialized view
// with ROWIDs or drop and recreate the materialized view with ROWIDs.
12018, 0000, "following error encountered during code generation for \"%s\".\"%s\""
// *Cause: The refresh operations for the indicated materialized view could
// not be regenerated due to errors.
// *Action: Correct the problem indicated in the following error messages and
// repeat the operation.
12019, 0000, "master table is a synonym to a remote object"
// *Cause: An attempt was made to create a materialized view or a
// materialized view log on a remote synonym which is unsupported.
// *Action: Do not create a materialized view or materialized view log on a
// remote synonym.
12020, 00000, "materialized view %s is not registered"
// *Cause: An attempt was made to unregister a materialized view that is not
// registered.
// *Action: No action required.
12021, 0000, "materialized view \"%s\".\"%s\" is corrupt"
// *Cause: The materialized view indicated is no longer valid.
// *Action: Contact Oracle Customer Support.
12022, 0000, "materialized view log on \"%s\".\"%s\" already has rowid"
// *Cause: Materialized view log on the indicated table already has ROWID
// information.
// *Action: No action required.
12023, 0000, "missing index on materialized view \"%s\".\"%s\""
// *Cause: The specified ROWID materialized view did not have the required
// index on the ROWID column of its underlying table.
// *Action: Drop and recreate the materialized view.
12024, 0000, "materialized view log on \"%s\".\"%s\" does not have primary key columns"
// *Cause: Materialized view log on the indicated table does not have primary
// key information.
// *Action: Add primary keys to the materialized view log using the ALTER
// MATERIALIZED VIEW command.
12025, 0000, "materialized view log on \"%s\".\"%s\" already has primary keys"
// *Cause: Materialized view log on the indicated table already has primary
// key columns.
// *Action: No action required.
12026, 0000, "invalid filter column detected"
// *Cause: One or more of the specified filter columns did not exist or was a
// primary key column or a primary key based object identifier.
// *Action: Ensure that all specified filter columns exist in the master table
// and ensure that primary key columns or primary key based object
// identifiers are not included in the list of filter columns.
12027, 0000, "duplicate filter column"
// *Cause: One or more of the specified filter columns were already being
// recorded in the materialized view log.
// *Action: Describe the materialized view log table and reissue the SQL
// command with the filter columns that are already being
// recorded in the materialized view log.
12028, 0000, "materialized view type is not supported by master site %s"
// *Cause: Pre-Oracle8 master sites are not able to support primary key or
// subquery materialized views that are able to perform a fast
// refresh.
// *Action: Create a ROWID materialized view or use a master table from an
// Oracle8 site.
12029, 0000, "LOB columns may not be used as filter columns"
// *Cause: An attempt was made to use LOB columns as filter columns.
// *Action: Remove LOB columns from the filter columns list and retry command.
//
12030, 0000, "cannot create a fast refresh materialized view"
// *Cause: The materialized view log did not exist or did not log the
// information needed by the materialized view to perform a fast
// refresh.
// *Action: Ensure that the materialized view log exists and logs the necessary
// information.
// - For ROWID materialized views, the master table's ROWID
// must be logged.
// - For primary key materialized views, the master table's primary
// key columns must be logged.
// - For subquery materialized views, the filter columns, primary key,
// and ROWID values must be logged.
// - For object materialized views, object id must be logged.
//
12031, 0000, "cannot use primary key columns from materialized view log on \"%s\".\"%s\""
// *Cause: The materialized view log either did not have primary key columns
// logged, or the timestamp associated with the primary key columns
// was more recent than the last refresh time.
// *Action: A complete refresh is required before the next fast refresh.
// Add primary key columns to the materialized view log, if required.
//
12032, 0000, "cannot use rowid column from materialized view log on \"%s\".\"%s\""
// *Cause: The materialized view log either does not have ROWID columns
// logged, or the timestamp associated with the ROWID columns is
// more recent than the last refresh time.
// *Action: A complete refresh is required before the next fast refresh.
// Add ROWID columns to the materialized view log, if required.
//
12033, 0000, "cannot use filter columns from materialized view log on \"%s\".\"%s\""
// *Cause: The materialized view log either did not have filter columns
// logged, or the timestamp associated with the filter columns was
// more recent than the last refresh time.
// *Action: A complete refresh is required before the next fast refresh.
// Add filter columns to the materialized view log, if required.
//
12034, 0000, "materialized view log on \"%s\".\"%s\" younger than last refresh"
// *Cause: The materialized view log was younger than the last refresh.
// *Action: A complete refresh is required before the next fast refresh.
//
12035, 0000, "could not use materialized view log on \"%s\".\"%s\""
// *Cause: The materialized view log did not exist or could not be used.
// *Action: Use just REFRESH, which will reinstantiate the entire table.
// If a materialized view log exists and the form of the materialized
// view allows the use of a materialized view log, REFRESH FAST will
// be available starting the next time the materialized view is
// refreshed.
//
12036, 0000, "updatable materialized view log is not empty, refresh materialized view"
// *Cause: The updatable materialized view log was not empty. The updatable
// materialized view log must be empty before an updatable rowid
// materialized view can be altered to a primary key materialized
// view.
// *Action: Ensure that updatable materialized view log is empty by refreshing
// the materialized view before converting the updatable ROWID
// materialized view to a primary key materialized view.
//
12037, 0000, "unknown export format"
// *Cause: An attempt was made to import a materialized view exported by an
// unknown export version (e.g., from a newer release than the
// importing site)
// *Action: Re-export the file using a version of export known by the importing
// site.
//
12038, 00000, "string literal has unexpected length"
// *Cause:
// *Action:
//
12039, 00000, "unable to use local rollback segment \"%s\""
// *Cause: A local rollback segment was specified in the CREATE MATERIALIZED
// VIEW command, but automatic refresh parameters were not specified.
// Therefore a refresh group was not created to automatically
// refresh the materialized view and the local rollback segment can't
// be registered for future use.
// *Action: Either supply the automatic refresh parameters so that a refresh
// group will be created or do not specify a local rollback segment.
//
12040, 00000, "master rollback segment option not support by master site %s"
// *Cause: An attempt was made to specify master rollback segment in the
// current operation. The master site of the current materialized
// view does not allow users to specify a rollback segment to be used
// for materialized view operations. This feature is only supported
// by Oracle8 or later master sites.
// *Action: Do not specify a master rollback segment in the current operation
// or choose a new master site.
//
12041, 00000, "cannot record ROWIDs for index-organized table \"%s\".\"%s\""
// *Cause: Index-organized tables do not have ROWIDs. Therefore a materialized
// view log that records the ROWIDs of an index-organized table
// could not be created.
// *Action: Do not include the WITH ROWID option when using the
// CREATE MATERIALIZED VIEW command and do not include the ADD ROWID
// option when using the ALTER MATERIALIZED VIEW command if the master
// table is index-organized.
//
12042, 00000, "cannot alter job_queue_processes in single process mode"
// *Cause: An attempt was made to alter job_queue_processes in single process
// mode.
// *Action: Do not attempt to set job_queue_processes in single process mode.
//
12043, 00000, "invalid CREATE MATERIALIZED VIEW option"
// *Cause: An invalid option was used in a CREATE MATERIALIZED VIEW statement.
// *Action: Specify only valid options.
//
12044, 00000, "invalid CREATE MATERIALIZED VIEW LOG option"
// *Cause: An invalid option was used in a CREATE MATERIALIZED VIEW LOG
// statement.
// *Action: Specify only valid options.
//
12045, 00000, "invalid ALTER MATERIALIZED VIEW LOG option"
// *Cause: An invalid option was used in an ALTER MATERIALIZED VIEW LOG
// statement.
// *Action: Specify only valid options.
//
12046, 00000, "cannot use trusted constraints for refreshing remote MV"
// *Cause: REFRESH USING TRUSTED CONSTRAINTS specified in ALTER MATERIALIZED
// VIEW or CREATE MATERIALIZED VIEW of a remote materialized view
// *Action: remove this attribute from ALTER/ CREATE MATERIALIZED VIEW DDL
12047, 00000, "PCT FAST REFRESH cannot be used for materialized view \"%s\".\"%s\""
// *Cause: PCT refresh is either not enabled on this materialized view or not
// possible after set of the base table changes since last refresh.
// *Action: Use just REFRESH FORCE, which will reinstantiate the entire table
// and try to pick the best refresh method on the materialized view
// Do explain_mview to look at the cause why PCT refresh is not possible
// on this materialized view
12048, 00000, "error encountered while refreshing materialized view \"%s\".\"%s\""
// *Cause: Some problem occurs during refresh of multiple materialized views in
// atomic mode. The materialized view whose refresh failed has raised
// this error.
// *Action: Examine the other messages on the stack to find the refresh problem.
//
12051, 00000, "ON COMMIT attribute is incompatible with other options"
// *Cause: ON COMMIT refresh attribute, incompatible with other
// refresh options such as automatic periodic refresh, was specified.
// *Action: Specify only valid options.
//
12052, 00000, "cannot fast refresh materialized view %s.%s"
// *Cause: Either ROWIDs of certain tables were missing in the definition or
// the inner table of an outer join did not have UNIQUE constraints on
// join columns.
// *Action: Specify the FORCE or COMPLETE option. If this error is got
// during creation, the materialized view definition may have be
// changed. Refer to the documentation on materialized views.
//
12053, 00000, "this is not a valid nested materialized view"
// *Cause: The list of objects in the FROM clause of the definition of this
// materialized view had some dependencies upon each other.
// *Action: Refer to the documentation to see which types of nesting are valid.
//
12054, 00000, "cannot set the ON COMMIT refresh attribute for the materialized view"
// *Cause: The materialized view did not satisfy conditions for refresh at
// commit time.
// *Action: Specify only valid options.
//
12055, 00000, "materialized view definition contains cyclic dependencies with existing materialized views"
// *Cause: The materialized view query definition introduced a cyclic
// dependency with existing materialized view.
// *Action: Modify the materialized view query definition.
//
12056, 00000, "invalid REFRESH method"
// *Cause: The NEVER REFRESH option may not be used under the
// following conditions:
// * The materialized view is updatable
// * The materialized view refreshes ON COMMIT
// * Automatic refresh options are specified
// *Action: For updatable materialized views, reissue the SQL command using
// REFRESH FORCE, REFRESH FAST, or REFRESH COMPLETE. For read-only
// materialized views, reissue the SQL command using ON DEMAND.
//
12057, 00000, "materialized view or zonemap \"%s\".\"%s\" is invalid and must use complete refresh"
// *Cause: The status of the materialized view or zonemap was invalid and an
// attempt was made to fast refresh it.
// *Action: Perform a complete refresh of the materialized view or zonemap.
//
12058, 00000, "materialized view cannot use prebuilt table"
// *Cause: An attempt was made to use the prebuilt tables.
// *Action: Reissue the SQL command using BUILD IMMEDIATE or BUILD DEFERRED.
//
12059, 00000, "prebuilt table \"%s\".\"%s\" does not exist"
// *Cause: The specified prebuilt table did not exist.
// *Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or
// ensure that the prebuilt table exists.
//
12060, 00000, "shape of prebuilt table does not match definition query"
// *Cause: The number of columns or the type or the length semantics of a
// column in the prebuilt table did not match the materialized
// view definition query.
// *Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or
// ensure that the prebuilt table matches the materialized view
// definition query.
//
12061, 00000, "invalid ALTER MATERIALIZED VIEW option"
// *Cause: An invalid option was used in an ALTER MATERIALIZED VIEW statement.
// *Action: Specify only valid options.
//
12062, 00000, "transaction %s received out of sequence from site %s"
// *Cause: A transaction from the client site was received out of sequence.
// This implies that one or more transactions were missing.
// *Action: Ensure that the transaction queue at the client site is valid
// and has not been corrupted.
//
12063, 00000, "unable to apply transaction from site %s"
// *Cause: The current transaction from the client site could not be
// applied to the master site.
// *Action: Ensure that the client site is still valid and that it has not
// been dropped from the master site.
//
12064, 00000, "invalid refresh sequence number: %s"
// *Cause: The client site was attempting to perform a refresh with an
// invalid refresh sequence.
// *Action: Perform a complete refresh to synchronize the refresh
// sequence number.
//
12065, 00000, "unknown refresh group identifier %s"
// *Cause: The specified refresh group did not exist at the master site.
// *Action: Ensure that the client site is still valid and that it has not
// been dropped from the master site.
//
12066, 00000, "invalid CREATE MATERIALIZED VIEW command"
// *Cause: The Replication API does not support the following options and
// types of materialized view:
// o ROWID materialized views
// o REFRESH ON COMMIT
// o ON PREBUILT TABLE
// o BUILD DEFERRED
// o NEVER REFRESH
// o ENABLE QUERY REWRITE
// *Action: Create a PRIMARY KEY materialized view using REFRESH WITH PRIMARY
// KEY and/or remove the invalid options.
//
12067, 00000, "empty refresh groups are not allowed"
// *Cause: The refresh group being instantiated did not contain any
// materialized views.
// *Action: Modify the template to include at least one materialized view.
//
12068, 00000, "updatable mview log for mview \"%s\".\"%s\" does not exist"
// *Cause: The updatable materialized view was missing the updatable
// materialized view log required to track updates made to the
// materialized view.
// *Action: Create the updatable materialized view log.
//
12069, 00000, "invalid object for offline instantiation"
// *Cause: Only materialized views can be offline instantiated. The object
// being offline instantiated was not a valid materialized view.
// *Action: Remove the object from the template or replace the object
// with a valid materialized view.
//
12070, 00000, "cannot offline instantiate materialized view \"%s\".\"%s\""
// *Cause: Offline instantiation does not support materialized views using the
// following options:
// o ON PREBUILT TABLE
// o BUILD DEFERRED
// *Action: Remove the invalid options.
//
12071, 00000, "definition query of \"%s\".\"%s\" is invalid for offline instantiation"
// *Cause: Offline instantiation requires materialized view definition queries
// to observe the following constraints:
// o The database link that will be used by the materialized view site
// to connect to the master site must be included with each master
// table referenced in the query.
// o All master tables referenced must be located at the local site.
// References to other sites are not allowed.
// *Action: Modify the materialized view definition query.
//
12072, 00000, "updatable materialized view log data for \"%s\".\"%s\" cannot be created"
// *Cause: The updatable materialized view was missing the updatable
// materialized view log required to track updates made
// to the materialized view.
// *Action: Create an updatable materialized view log.
//
12073, 00000, "request cannot be processed"
// *Cause: An out-of-sequence request was made and it cannot be processed.
// *Action: Try again with a valid request.
//
12074, 00000, "invalid memory address"
// *Cause: An attempt was made to access an invalid memory region.
// *Action: Reconnect and try the command again.
//
12075, 00000, "invalid object or field"
// *Cause: An attempt was made to access an invalid field or object in the
// Java Virtual Memory.
// *Action: Retry the request.
//
12076, 00000, "invalid threshold value"
// *Cause: The result set threshold or LOB threshold value is not supported.
// *Action: Specify a threshold value below 64K.
//
12077, 00000, "temporary updatable materialized view log does not exist"
// *Cause: Temporary updatable materialized view log was not created or was
// dropped.
// *Action: Re-create the temporary updatable materialized view log.
// Warning: This will cause a complete refresh of the materialized
// view.
//
12078, 00000, "fast refresh of refresh group ID %s failed"
// *Cause: Refresh result set sent through client method REFRESH_REQ_RESULT
// returned an unknown value.
// *Action: Re-issue the refresh request.
//
12079, 00000, "do not invalidate result cache created during materialized view refresh"
// *Cause: Result cache created during materialized view refresh was not invalidated at end.
// *Action: Do not set this as an event.
//
12080, 00000, "Buffer cache miss for IOQ batching"
// *Cause:
// *Action:
// *Comment: never set this event
//
12081, 00000, "update operation not allowed on table \"%s\".\"%s\""
// *Cause: An attempt was made to update a read-only materialized view.
// *Action: No action required. Only Oracle is allowed to update a
// read-only materialized view.
//
12082, 00000, "\"%s\".\"%s\" cannot be index organized"
// *Cause: An attempt was made to create an index-organized
// materialized aggregate view or an index-organized
// updatable ROWID materialized view. This is not
// supported.
// *Action: Try to create the materialized view without the
// index organization clause.
12083, 00000, "must use DROP MATERIALIZED VIEW to drop \"%s\".\"%s\""
// *Cause: An attempt was made to drop a materialized view using
// a command other than DROP MATERIALIZED VIEW.
// *Action: Use the DROP MATERIALIZED VIEW command.
//
12084, 00000, "must use ALTER MATERIALIZED VIEW to alter \"%s\".\"%s\""
// *Cause: An attempt was made to alter a materialized view using
// a command other than ALTER MATERIALIZED VIEW.
// *Action: Use the ALTER MATERIALIZED VIEW command.
12085, 0000, "materialized view log on \"%s\".\"%s\" already has object id"
// *Cause: Materialized view log on the indicated table already has object
// id information.
// *Action: No action required.
//
12086, 00000, "table \"%s\".\"%s\" is not an object table"
// *Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the
// WITH OBJECT ID option and the master table is not an object
// table.
// *Action: Either specify the name of an object table, or remove the WITH
// OBJECT ID clause.
//
12087, 00000, "online redefinition not allowed on tables owned by \"%s\""
// *Cause: An attempt was made to online redefine a table owned by
// SYS or SYSTEM.
// *Action: Do not attempt to online redefine a table owned by SYS or SYSTEM.
//
12088, 00000, "cannot online redefine table \"%s\".\"%s\" with unsupported datatype"
// *Cause: An attempt was made to online redefine a table containing
// a LONG column, an ADT column, or a FILE column.
// *Action: Do not attempt to online redefine a table containing a LONG column,
// an ADT column, or a FILE column.
//
12089, 00000, "cannot online redefine table \"%s\".\"%s\" with no primary key"
// *Cause: An attempt was made to online redefine a table that does not have
// a primary key defined on it.
// *Action: Do not attempt to online redefine a table that does not have a
// primary key defined on it.
12090, 00000, "cannot online redefine table \"%s\".\"%s\""
// *Cause: An attempt was made to online redefine a table that is either a
// temporary table, an IOT overflow table, a table with fine-grained
// access control or row-level security enabled, a CDC change table,
// or a table with a CDC change table defined on it.
// *Action: Do not attempt to online redefine a table that is not
// supported by online redefinition.
12091, 00000, "cannot online redefine table \"%s\".\"%s\" with materialized views"
// *Cause: An attempt was made to online redefine a table that had
// materialized views defined on it or had a materialized view log
// defined on it or is a master.
// *Action: Drop all materialized views and materialized view logs before
// attempting to online redefine the table.
//
12092, 00000, "cannot online redefine replicated table \"%s\".\"%s\""
// *Cause: An attempt was made to online redefine a table that is either a
// materialized view or a replicated table.
// *Action: Do not attempt to online redefine a table that is either a
// materialized view or a replicated table.
//
12093, 00000, "invalid interim table \"%s\".\"%s\""
// *Cause: The table is not the interim table of the corresponding table
// to be online redefined.
// *Action: Pass in the valid interim table.
//
12094, 00000, "error during online redefinition"
// *Cause: There was an error during the online redefinition process.
// *Action: Abort the online redefinition process.
//
12096, 00000, "error in materialized view log on \"%s\".\"%s\""
// *Cause: There was an error originating from this materialized view log.
// One possible cause is that schema redefinition has occurred
// on the master table and one or more columns in the log is now
// a different type than corresponding master column(s). Another
// possible cause is that there is a problem accessing the
// underlying materialized view log table.
// *Action: Check further error messages in stack for more detail about
// the cause. If there has been schema redefinition, drop the
// materialized view log and recreate it.
//
12097, 00000, "changes in the master tables during refresh, try refresh again"
// *Cause: There are some changes (i.e., conventional DML, direct load,
// partition maintenance operation) in the master tables during
// materialized view refresh.
// *Action: Refresh the affected materialized views again.
//
12098, 00000, "cannot comment on the materialized view"
// *Cause: An attempt was made to issue a COMMENT ON TABLE statement
// on a materialized view.
// *Action: Issue a COMMENT ON MATERIALIZED VIEW statement instead.
//
12099, 00000, "Don't go into fast table scan (kdst) mode"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
//
12100, 0000, "materialized view log on \"%s\".\"%s\" already has sequence"
// *Cause: Materialized view log on the indicated table already has sequence
// information.
// *Action: No action required.
//
12101, 00000, "shape of materialized view does not match the base table"
// *Cause: The number of columns or the type or the length semantics of a
// column in the materialized view did not match the materialized
// view base table.
// *Action: Ensure that the materialized view column list matches with the
// base table.
//
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
/ 12100 - 12299 Reserved for Net8 errors
/
/
/ Copyright (c) 1991, 1996, 1997, 2001 by the Oracle Corporation. All rights reserved.
/
/
/ $Header: network_src/mesg/net12150.msg /main/10 2015/04/19 10:24:44 niskaush Exp $
/
/
/ NAME
/ net12150.msg - Oracle Net external message file starting from 12150 -
/ U.S. english version
/
/
/ FUNCTION
/ Network error message file, American English version.
/
/
/ NOTES
/ Only external errors are to be put into this file. Internal
/ messages are to put into netius.msg.
/
/ This file, along with netius.msg and net12500.msg, forms tnsus.msg. As a
/ result, the errors in this file may not overlap with the errors in
/ those files. Otherwise, errors will result when generating tnsus.msb.
/
/ Message text should be limited to a maximum of 76 characters.
/ Messages containing embedded % directives should not overrun
/ the 76 character limit unless they signal unusual errors
/ which do not occur as part of user applications. For example,
/ startup errors and system dependent errors can probably get
/ away with longer message text.
/
/
/ '/' at beginning-of-line for comments.
/ '//' at beginning-of-line for *Cause: and *Action: fields.
/
/
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
/////////////////////////// Please maintain this map //////////////////////
/
// 00001 - 04200 See netius.msg
/ .
/ .
/ 12150 - 12195 Reserved for OSN (Not to be used by TNS)
/ 12196 - 12285 NR errors reportable by OSN (returned by nricall())
/ 12286 - 12499 ---(Reserved)---
/ 12500 - 12699 See net12500.msg
/ .
/ .
/ .
/
/////////////////////////// Please maintain this map //////////////////////
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
/
/
/
/
/ OWNER
/ Network and Management Products - Server Technologies
/
/ MODIFIED
/ cozhang 10/30/02 - Modify msg text 12170 to include STO and RTO.
/ mclose 10/01/02 - Improve key error messages
/ cozhang 03/07/02 - Change CONNECT_TIMEOUT to INBOUND_CONNECT_TIMEOUT.
/ cozhang 12/12/01 - Add message for connect time-out (12170 NIQECTO).
/ bnanjund 04/16/01 - 1714563_bugfix
/ tmlee 08/06/97 - modify 12204
/ rwessman 03/16/97 - split from netus.msg to correct bug in building
/ oraus.msg.
/
12150, 00000, "TNS:unable to send data"
// *Cause: Unable to send data. Connection probably disconnected.
// *Action: Reestablish connection. If the error is persistent, turn
// on tracing and reexecute the operation.
/
12151, 00000, "TNS:received bad packet type from network layer"
// *Cause: Internal error.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Worldwide Customer Support.
/
12152, 00000, "TNS:unable to send break message"
// *Cause: Unable to send break message. Connection probably disconnected.
// *Action: Reestablish connection. If the error is persistent, turn
// on tracing and reexecute the operation.
/
12153, 00000, "TNS:not connected"
// *Cause: Not currently connected to a remote host.
// *Action: Reestablish connection.
/
12154, 00000, "TNS:could not resolve the connect identifier specified"
// *Cause: A connection to a database or other service was requested using
// a connect identifier, and the connect identifier specified could not
// be resolved into a connect descriptor using one of the naming methods
// configured. For example, if the type of connect identifier used was a
// net service name then the net service name could not be found in a
// naming method repository, or the repository could not be
// located or reached.
// *Action:
// - If you are using local naming (TNSNAMES.ORA file):
// - Make sure that "TNSNAMES" is listed as one of the values of the
// NAMES.DIRECTORY_PATH parameter in the Oracle Net profile
// (SQLNET.ORA)
// - Verify that a TNSNAMES.ORA file exists and is in the proper
// directory and is accessible.
// - Check that the net service name used as the connect identifier
// exists in the TNSNAMES.ORA file.
// - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA
// file. Look for unmatched parentheses or stray characters. Errors
// in a TNSNAMES.ORA file may make it unusable.
// - If you are using directory naming:
// - Verify that "LDAP" is listed as one of the values of the
// NAMES.DIRETORY_PATH parameter in the Oracle Net profile
// (SQLNET.ORA).
// - Verify that the LDAP directory server is up and that it is
// accessible.
// - Verify that the net service name or database name used as the
// connect identifier is configured in the directory.
// - Verify that the default context being used is correct by
// specifying a fully qualified net service name or a full LDAP DN
// as the connect identifier
// - If you are using easy connect naming:
// - Verify that "EZCONNECT" is listed as one of the values of the
// NAMES.DIRETORY_PATH parameter in the Oracle Net profile
// (SQLNET.ORA).
// - Make sure the host, port and service name specified
// are correct.
// - Try enclosing the connect identifier in quote marks.
//
// See the Oracle Net Services Administrators Guide or the Oracle
// operating system specific guide for more information on naming.
/
12155, 00000, "TNS:received bad datatype in NSWMARKER packet"
// *Cause: Internal error during break handling.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Worldwide Customer Support.
/
12156, 00000, "TNS:tried to reset line from incorrect state"
// *Cause: Internal error during break handling.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Worldwide Customer Support.
/
12157, 00000, "TNS:internal network communication error"
// *Cause: Internal error during network communication.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Worldwide Customer Support.
/
12158, 00000, "TNS:could not initialize parameter subsystem"
// *Cause: Unable to locate parameter file.
// *Action: Verify that a valid parameter file exists, and is readable.
/
12159, 00000, "TNS:trace file not writeable"
// *Cause: The trace file to be generated is not writeable by this user.
// *Action: If the user does not have write permissions in the directory
// to which the trace file will be written, contact an administrator to
// get the proper permissions or set the TRACE_DIRECTORY_CLIENT
// parameter in the net profile (SQLNET.ORA file) to a directory the
// user can write to.
/
12160, 00000, "TNS:internal error: Bad error number"
// *Cause: Corrupt error reporting subsystem.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Worldwide Customer Support.
/
12161, 00000, "TNS:internal error: partial data received"
// *Cause: The connection may be terminated.
// *Action: Reconnect and try again. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Worldwide Customer Support.
/
12162, 00000, "TNS:net service name is incorrectly specified"
// *Cause: The connect descriptor corresponding to the net service name in
// TNSNAMES.ORA or in the directory server (Oracle Internet Directory) is
// incorrectly specified.
// *Action: If using local naming make sure there are no syntax errors in
// the corresponding connect descriptor in the TNSNAMES.ORA file. If using
// directory naming check the information provided through the administration
// used for directory naming. If using ORACLE_SID, please check if ORACLE_SID is// set.
/
12163, 00000, "TNS:connect descriptor is too long"
// *Cause: The connect descriptor corresponding to the net service name
// specified as the connect identifier is too long. The maximum length for
// a connect descriptor is 512 bytes and this limit has been exceeded.
// *Action: Check the net service name's connect descriptor in the local
// naming file (TNSNAMES.ORA) or in the directory server (Oracle Internet
// Directory). Use a smaller connect descriptor. If this is not possible,
// contact Worldwide Customer Support.
/
12164, 00000, "TNS:Sqlnet.fdf file not present"
// *Cause: The sqlnet.fdf file doesn't exist in $ORACLE_HOME/network/admin.
// *Action: The sqlnet.fdf file is required for Oracle Tracing to occur.
// Either install the sqlnet.fdf file in $ORACLE_HOME/network/admin or
// turn off tracing in your ORA file.
/
12165, 00000, "TNS:Trying to write trace file into swap space."
// *Cause: Oracle Trace doesn't allow writing trace information into your
// swap space.
// *Action: Oracle Trace cannot write trace information into swap space
// so either disable tracing or redirect trace files to be written to another
// area of your disk.
/
12166, 00000, "TNS:Client can not connect to HO agent."
// *Cause: NVstring contained DESCRIPTION/HO.
// *Action: Call HO agent from integrating server.
/
12168, 00000, "TNS:Unable to contact LDAP Directory Server"
// *Cause: Cannot contact LDAP directory server to get Oracle Net configuration.
// *Action: Verify that the directory server is up and accessible from the network.
// Verify that directory access configuration is correct. For more
// information see the Oracle Internet Directory Administrators Guide or
// the Oracle Net Administrators Guide.
/
12169, 00000, "TNS:Net service name given as connect identifier is too long"
// *Cause: The net service name you are attempting to resolve is too long.
// *Action: The maximum length of a net service name is 255 bytes; this limit
// has been exceeded. Use a smaller net service name. If this
// is not possible, contact Worldwide Customer Support.
/
12170, 00000, "TNS:Connect timeout occurred"
// *Cause: The server shut down because connection establishment or
// communication with a client failed to complete within the allotted time
// interval. This may be a result of network or system delays; or this may
// indicate that a malicious client is trying to cause a Denial of Service
// attack on the server.
// *Action: If the error occurred because of a slow network or system,
// reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT,
// SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values.
// If a malicious client is suspected, use the address in sqlnet.log to
// identify the source and restrict access. Note that logged addresses may
// not be reliable as they can be forged (e.g. in TCP/IP).
/
12171, 00000, "TNS:could not resolve connect identifier: %s"
// *Cause: A connection to a database or other service was requested using
// a connect identifier, and the connect identifier specified could not
// be resolved into a connect descriptor using one of the naming methods
// configured. For example, if the type of connect identifier used was a
// net service name then the net service name could not be found in a
// naming method repository, or the repository could not be
// located or reached.
// *Action:
// - If you are using local naming (TNSNAMES.ORA file):
// - Make sure that "TNSNAMES" is listed as one of the values of the
// NAMES.DIRECTORY_PATH parameter in the Oracle Net profile
// (SQLNET.ORA)
// - Verify that a TNSNAMES.ORA file exists and is in the proper
// directory and is accessible.
// - Check that the net service name used as the connect identifier
// exists in the TNSNAMES.ORA file.
// - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA
// file. Look for unmatched parentheses or stray characters. Errors
// in a TNSNAMES.ORA file may make it unusable.
// - If you are using directory naming:
// - Verify that "LDAP" is listed as one of the values of the
// NAMES.DIRETORY_PATH parameter in the Oracle Net profile
// (SQLNET.ORA).
// - Verify that the LDAP directory server is up and that it is
// accessible.
// - Verify that the net service name or database name used as the
// connect identifier is configured in the directory.
// - Verify that the default context being used is correct by
// specifying a fully qualified net service name or a full LDAP DN
// as the connect identifier
// - If you are using easy connect naming:
// - Verify that "EZCONNECT" is listed as one of the values of the
// NAMES.DIRETORY_PATH parameter in the Oracle Net profile
// (SQLNET.ORA).
// - Make sure the host, port and service name specified
// are correct.
// - Try enclosing the connect identifier in quote marks.
//
// See the Oracle Net Services Administrators Guide or the Oracle
// operating system specific guide for more information on naming.
/
/ This line is an OSN Magic Cookie. Don't eat it. Last OSN error in 2.0.9.
/
/
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
/
/ 12196 - 12285 NR errors reportable to OSN.
/
12196, 00000, "TNS:received an error from TNS"
// *Cause: The navigation layer received an error from TNS.
// *Action: See the error log file for the specific TNS error.
/
12197, 00000, "TNS:keyword-value resolution error"
// *Cause: The navigation layer received an error while trying to look up a
// value for a keyword.
// *Action: Check the syntax of the connect descriptor.
/
12198, 00000, "TNS:could not find path to destination"
// *Cause: Could not navigate a path through Interchanges to the destination.
// This error occurs if an invalid community is in the address string, or
// the address includes a protocol that is not available or the
// TNSNAV.ORA file does not have a correct CMANAGER address specified or
// the Interchange is down.
// *Action: Assure that Interchanges necessary to get to the desired
// destination are up and have available capacity for an additional
// connection. Also check that the correct community and protocol have been
// specified in the CMANAGER address used.
/
12200, 00000, "TNS:could not allocate memory"
// *Cause: Out of memory on machine.
// *Action: Reconfigure machine to have more storage or run fewer applications
// while the Interchange is running.
/
12201, 00000, "TNS:encountered too small a connection buffer"
// *Cause: TNS connection buffer supplied by the application was too small
// to retrieve the data sent back.
// *Action: Supply a larger connection buffer. If problem persists, call
// Worldwide Customer Support.
/
12202, 00000, "TNS:internal navigation error"
// *Cause: Internal navigation error.
// *Action: Not normally visible to the user. For further details contact
// Worldwide Customer Support.
/
12203, 00000, "TNS:unable to connect to destination"
// *Cause: Invalid address specified or destination is not listening.
// This error can also occur because of underlying network or network
// transport problems.
// *Action: Verify that the net service name you entered was correct.
// Verify that the ADDRESS portion of the connect descriptor which
// corresponds to the net service name is correct. Ensure that the
// destination process (for example the listener) is running at the
// remote node.
/
12204, 00000, "TNS:received data refused from an application"
// *Cause: The application using Connection Manager refused the
// connection at the listener.
// *Action: Make sure that the application listener at the destination is
// functioning correctly. If it is and the problem persists, contact
// Worldwide Customer Support.
/
12205, 00000, "TNS:could not get failed addresses"
// *Cause: Internal navigation error.
// *Action: Not normally visible to the user. For further details contact
// Worldwide Customer Support.
/
12206, 00000, "TNS:received a TNS error during navigation"
// *Cause: Internal navigation error because of an unexpected TNS error.
// *Action: Look at the log file to find the TNS error. If necessary, turn
// on tracing and repeat the operation.
/
12207, 00000, "TNS:unable to perform navigation"
// *Cause: Improperly configured navigation file TNSNAV.ORA.
// *Action: Check the syntax of the TNSNAV.ORA file on the application`s
// machine, and verify that it lists the correct communities.
/
12208, 00000, "TNS:could not find the TNSNAV.ORA file"
// *Cause: Either the ORACLE environment is not set up correctly, or the
// TNSNAV.ORA file is not present.
// *Action: Ensure that the ORACLE environment is set up appropriately
// on your platform and that a TNSNAV.ORA file is present.
/
12209, 00000, "TNS:encountered uninitialized global"
// *Cause: Application calling navigation routine has not properly configured
// the global variables. There are no TNSNAV.ORA files available, or they
// are defective.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Worldwide Customer Support.
/
12210, 00000, "TNS:error in finding Navigator data"
// *Cause: Application calling navigation routine has not properly configured
// the TNSNAV.ORA file.
// *Action: Check the syntax of the TNSNAV.ORA file.
/
12211, 00000, "TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA"
// *Cause: TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined.
// *Action: Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file.
/
12212, 00000, "TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA"
// *Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file
// does not have a CMANAGER_NAME specified.
// *Action: Define the CMANAGER_NAME as part of the PREFERRED_CMANAGERS
// binding. Use of the Oracle Network Manager should eliminate this
// error.
/
12213, 00000, "TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA"
// *Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file
// does not have an ADDRESS specified.
// *Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding.
/
12214, 00000, "TNS:missing local communities entry in TNSNAV.ORA"
// *Cause: There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA.
// *Action: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA
// file.
/
12215, 00000, "TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA"
// *Cause: Address binding for PREFERRED_NAVIGATORS entry is improperly entered.
// entry.
// *Action: Check your PREFERRED_NAVIGATORS entry and fix it in TNSNAV.ORA
//
/
12216, 00000, "TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA"
// *Cause: Address binding for the PREFERRED_CMANAGERS entry in the client's
// TNSNAV.ORA file is improperly entered.
// *Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding.
/
12217, 00000, "TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA"
// *Cause: There is a syntax error in the PREFERRED_CMANAGERS entry, or
// addresses specified are wrong, or the intended Connection Managers are
// unavailable.
// *Action: Check the PREFERRED_CMANAGERS entries in the client's
// TNSNAV.ORA file and correct them or talk with your network administrator
// to determine if the specified Connection Managers are available.
// Verify that the Interchanges are active by using the INTCTL STATUS
// command.
/
12218, 00000, "TNS:unacceptable network configuration data"
// *Cause: Poorly formed network configuration data. For example, a
// PREFERRED_CMANAGERS entry may have an incorrect CMANAGER_NAME in the
// client's TNSNAV.ORA file. Or an Interchange downtime parameter
// (TIMEOUT_INTERVAL) on the Navigator may be set to zero in INTCHG.ORA.
// *Action: Check the entries in TNSNAV.ORA and the Interchange
// configuration files and correct them. If necessary, talk with your
// network administrator to determine if the specified Interchanges
// (Connection Managers) are available and properly configured.
// Use the Oracle Network Manager to generate the configuration files
// if necessary.
/
12219, 00000, "TNS:missing community name from address in ADDRESS_LIST"
// *Cause: This error occurs when an ADDRESS_LIST has some ADDRESSes in it
// that have no COMMUNITY component and others that do have a COMMUNITY
// component.
// *Action: Check that in the connect descriptors you are using either
// all the ADDRESSes have a COMMUNITY component or all do not.
/
/ All succeeding errors are a remap of NS errors in NR
/
12221, 00000, "TNS:illegal ADDRESS parameters"
// *Cause: An illegal set of protocol adapter parameters was specified. In
// some cases, this error is returned when a connection cannot be made to the
// protocol transport.
// *Action: Verify that the destination can be reached using the specified
// protocol. Check the parameters within the ADDRESS section of
// TNSNAMES.ORA or in the directory. Legal ADDRESS parameter formats may
// be found in the Oracle operating system specific documentation or the
// Oracle Net Administrator's Guide. Protocols that resolve names at the
// transport layer are vulnerable to this error if not properly configured
// or names are misspelled.
/
12222, 00000, "TNS:no support is available for the protocol indicated"
// *Cause: The protocol requested in the ADDRESS portion of the connect
// descriptor identified through the net service name is not available.
// If the supplied ADDRESS is typographically correct then support for
// that protocol is not installed.
// *Action: Install support for the protocol or correct typographical error,
// as appropriate. Note: if the supplied address was derived from
// resolving the net service name, check the address in the appropriate file
// (TNSNAMES.ORA, LISTENER.ORA) or in the directory server.
/
12223, 00000, "TNS:internal limit restriction exceeded"
// *Cause: Too many TNS connections open simultaneously.
// *Action: Wait for connections to close and re-try.
/
12224, 00000, "TNS:no listener"
// *Cause: The connection request could not be completed because the listener
// is not running.
// *Action: Ensure that the supplied destination address matches one of
// the addresses used by the listener - compare the TNSNAMES.ORA entry with
// the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to
// go by way of an Interchange). Start the listener on the remote machine.
/
12225, 00000, "TNS:destination host unreachable"
// *Cause: Contact can not be made with remote party.
// *Action: Make sure the network driver is functioning and the network is up.
/
12226, 00000, "TNS:operating system resource quota exceeded"
// *Cause: The current user has exceeded the allotted resource assigned in the
// operating system.
// *Action: Acquire more operating system resource, or perform a different
// function.
/
12227, 00000, "TNS:syntax error"
// *Cause: The supplied connect descriptor contains illegal syntax.
// *Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.
/
12228, 00000, "TNS:protocol adapter not loadable"
// *Cause: On some platforms (such as Windows) protocol support is loaded at
// run-time. If the shared library (or DLL) for the protocol adapter is
// missing or one of its supporting libraries is missing then this error is
// returned.
// *Action: For further details, turn on tracing and reexecute the operation.
// The trace file will include the name of the shared library (or DLL) that
// could not be loaded.
/
12229, 00000, "TNS:Interchange has no more free connections"
// *Cause: One or more Interchanges along the path to the destination
// desired has no more free connections available to be used for this
// call.
// *Action: Try again later when the Interchanges are less busy, or contact
// your network administrator to have him determine which interchange it is,
// and increase the number of connections available on that interchange.
/
12230, 00000, "TNS:Severe Network error occurred in making this connection"
// *Cause: This error is reported by an interchange which fails to make
// contact with the destination due to a physical network error while calling
// a destination.
// *Action: Try again later when the network service may have been fixed
// or report the problem to your Network Administrator so that he may fix
// the problem.
/
12231, 00000, "TNS:No connection possible to destination"
// *Cause: This error is reported by an interchange which fails to find a
// possible connection along the path to the destination.
// *Action: Report the problem to your Network Administrator so that he may
// fix the problem.
/
12232, 00000, "TNS:No path available to destination"
// *Cause: This error is reported by an interchange which fails to find a
// possible path to the destination.
// *Action: Report the problem to your Network Administrator so that he may
// fix the problem.
/
12233, 00000, "TNS:Failure to accept a connection"
// *Cause: This error is reported by an interchange which fails to accept
// a connection due to a redirect failure.
// *Action: Report the problem to your Network Administrator so that he may
// isolate the interchange problem.
/
12234, 00000, "TNS:Redirect to destination"
// *Cause: This error is reported by an interchange which determines that this
// interchange is not the right gateway and needs to redirect the connection
// to another gateway along the path to the destination.
// *Action: None.
/
12235, 00000, "TNS:Failure to redirect to destination"
// *Cause: This error is reported by an interchange which fails to redirect
// a connection to another interchange along the path to the destination.
// *Action: Report the problem to your Network Administrator so that he may
// fix the problem.
/
12236, 00000, "TNS:protocol support not loaded"
// *Cause: On some platforms (such as Windows) protocol support is loaded at
// run-time. If the shared library (or DLL) for the protocol adapter has not
// been loaded, then this error is returned.
// *Action: For further details, turn on tracing and reexecute the operation.
// The trace file will have the name of the shared library (or DLL) that has
// not been loaded.
/
12238, 00000, "TNS: NT Operaion is aborted"
// *Cause: The NT operation is aborted because it is interrupted by upper
// layer to cleanup the database session.
// *Action: None.
/
/ This line is an OSN Magic Cookie. Don't eat it. Last NR error in 2.0.9.
/
/
///////////////////////////////////////////////////////////////////////////
/ 12300 - 12399 Reserved for Multiple Mounts
/
/ Begin error messages for Multiple Mounts
/
12315, 00000, "database link type is invalid for the ALTER DATABASE statement"
// *Cause: The database link name you specified on the ALTER DATABASE
// statement is not an ROM: link. You must specify an ROM: link
// when using the ALTER DATABASE statement to mount or open a
// secondary database.
// *Action: Re-issue the ALTER DATABASE statement using a valid ROM: link to
// the database you want to mount or open. If a valid ROM: link does
// not exist, create one using the CREATE DATABASE LINK
// command. See the Trusted ORACLE RDBMS Guide to Security Features
// for more information about creating database links using
// the ROM: link type.
12316, 00000, "syntax error in database link's connect string"
// *Cause: The connect string in the CREATE DATABASE LINK statement
// has a syntactical error.
// *Action: Drop the database link and recreate it using valid syntax. See
// the SQL Language Reference Manual for more information about the
// connect string portion of the CREATE DATABASE LINK
// statement.
12317, 00000, "logon to database (link name %s) denied"
// *Cause: There are several possible causes for this error. First, you can
// get this error if your username (and password, if you are using
// database instead of operating system authentication) in the
// secondary database are not identical
// to your username (and password) in the primary database. Second,
// you can get this error if your username in the secondary database
// is invalid (has not been created). Third,
// you can get this error if the username/password combination
// specified in the connect string of the database link definition
// is invalid (either not created or has an invalid password).
// *Action: In the first case, ensure that the secondary database contains
// a username (and password, if you are using database authentication)
// identical to the one you are using in the primary
// database. In general, you should always use operating system
// authentication in Trusted ORACLE (see the Trusted ORACLE RDBMS
// Guide to Security Features for more information about the
// advantages of OS authentication).
// In the second case, ensure that your username in the
// secondary database has been created.
// In the third case, ensure that the username specified in the
// connect string has been created in the secondary database.
12318, 00000, "database (link name %s) is already mounted"
// *Cause: You are attempting to mount a secondary database that has already
// been mounted by your instance.
// *Action: The database is already mounted, so you need not take additional
// action to mount it. To establish access, use the
// ALTER DATABASE <linkname> OPEN command to open the database.
12319, 00000, "database (link name %s) is already open"
// *Cause: You are attempting to open a secondary database that is already
// open.
// *Action: The database is open and you need not take additional action
// to establish access.
12321, 00000, "database (link name %s) is not open and AUTO_MOUNTING=FALSE"
// *Cause: The secondary database that your instance is attempting to mount
// is not open and automatic mounting has not been enabled.
// *Action: Manually mount and open the secondary database using
// ALTER DATABASE <linkname> with the OPEN and MOUNT options.
// Alternately, to allow your instance to automatically mount and
// open secondary databases, set the AUTO_MOUNTING parameter in the
// parameter file to TRUE.
12322, 00000, "unable to mount database (link name %s)"
// *Cause: This message should be accompanied by additional error messages
// that indicate the cause of the problem.
// *Action: Follow the steps outlined in the accompanying error messages to
// resolve the problem.
12323, 00000, "unable to open database (link name %s)"
// *Cause: This message should be accompanied by additional error messages
// that indicate the cause of the problem.
// *Action: Follow the steps outlined in the accompanying error messages to
// resolve the problem.
12324, 00000, "cannot use the ROM: link type on a private database link"
// *Cause: You can only specify the ROM: link type on a public, not a
// private, database link.
// *Action: Determine if there is an existing public database link to the
// secondary database. If not, and if you wish to establish public
// access to the secondary database, create a public database link to
// the secondary database using the CREATE DATABASE LINK
// command.
12326, 00000, "database %s is closing immediately; no operations are permitted"
// *Cause: The database you attempted to access is closing, so your
// operation has been terminated.
// *Action: Wait until the database has been reopened, or contact the
// database adminstrator.
12329, 00000, "database %s is closed; no operations are permitted"
// *Cause: The database you attempted to access is closed, so your
// operation has been terminated.
// *Action: Wait until the database is reopened, or contact the database
// administrator.
12333, 00000, "database (link name %s) is not mounted"
// *Cause: You attempted to open a database that has not been mounted.
// *Action: Mount the database with the ALTER DATABASE <linkname> MOUNT
// command, then re-attempt to open the database.
12334, 00000, "database (link name %s) is still open"
// *Cause: You attempted to dismount a database that is still open.
// *Action: Close the database with the ALTER DATABASE <linkname> CLOSE
// command, then re-attempt to dismount the database.
12335, 00000, "database (link name %s) is not open"
// *Cause: You attempted to close a database that is not open.
// *Action: The database is closed; you can proceed with dismounting it.
12336, 00000, "cannot login to database (link name %s) "
// *Cause: You are tyring to login while another user is mounting or
// dismounting the same database.
// *Action: Check to see if the database is in the middle of being
// mounted or opened and try your login again once the database is
// accessible.
12341, 00000, "maximum number of open mounts exceeded"
// *Cause: The number specified on the OPEN_MOUNTS parameter in the parameter
// file exceeds the maximum allowed (255).
// *Action: Change the value of this parameter so that it reflects the actual
// number of possible open mounts to secondary databases. This must
// be less than 255.
12342, 00000, "open mounts exceeds limit set on the OPEN_MOUNTS parameter"
// *Cause: The number of currently open mounts exceeds the value you
// specified on the OPEN_MOUNTS parameter.
// *Action: Increase the value of the OPEN_MOUNTS parameter so that it
// accommodates the maximum possible number of open mounts to
// secondary databases.
12345, 00000, "user %s lacks CREATE SESSION privilege in database link (linkname %s)"
// *Cause: There are several possible causes for this message:
// First, you will get this message if your username in the
// second database specified was not granted the
// CREATE SESSION system privilege.
// Second, you will get this message if the username specified
// in the connect string of the database link definition was
// not granted the CREATE SESSION system privilege.
// *Action: The action you take depends upon the cause of the message:
// In the first case, ensure that your username in the secondary
// database was granted the CREATE SESSION system privilege.
// In the second case, ensure the username specified in the
// connect string of the database link definition was granted
// the CREATE SESSION system privilege in the secondary database.
12350, 00000, "database link being dropped is still mounted"
// *Cause: An attempt was made to drop a ROM: database link that was still
// mounted and/or opened.
// *Action: Close and dismount the database and then re-issue the drop
// statement.
12351, 00000, "cannot create view using a remote object which has a remote object reference"
// *Cause: You tried to create a view which references a remote object
// which, in turn, references an object on another database. Since
// the view that you tried to create references a remote object,
// that object cannot reference an object on another database.
// *Action: Choose a different object to reference in your view or change
// the remote object so that it does not reference another database.
12352, 00000, "object %s.%s@%s is invalid"
// *Cause: An attempt was made to reference (compile against) an object
// of a secondary database but the object is invalid and the system
// cannot validate or recompile it because it is in a secondary
// database.
// *Action: Manually recompile the invalid object in the secondary database.
12353, 00000, "secondary stored object cannot reference remote object"
// *Cause: You tried to either select from a remote view or execute a remote
// procedure which references an object on another database. Since
// the remote view or procedure is on a secondary database, an
// additional reference to another database cannot be done.
// *Action: Choose a different object to reference or change the remote
// view or procedure so that it does not reference another database.
12354, 00000, "secondary object being dropped"
// *Cause: You tried to access a object (for example, a table or view)
// on a secondary database that was in the process of being
// dropped.
// *Action: Repeat the operation. If you receive this message again, try to
// access the object from the secondary database. If you receive
// an internal error or a trace file, contact Oracle WorldWide
// Technical Support.
/ Copyright (c) 2001, 2015, Oracle and/or its affiliates. All rights reserved.
/
/ NAME
/ lbacus.msg
/ DESCRIPTION
/ Error messages for Oracle Label Security
/ Label Based Access Control Framework
/ NOTES
/ Language : American
/ Character set : US7ASCII
/ MODIFIED
/ risgupta 03/23/15 - Bug 20627049: modify 12448
/ risgupta 08/06/12 - Bug 14259254: add 12475
/ risgupta 07/03/12 - Bug 14147100: add 12474
/ jkati 02/26/12 - bug#13101068: modify cause of 12458
/ yanchuan 11/23/11 - Bug 13409157: add 12460
/ aramappa 10/24/11 - bug 13098014 : add 12459
/ risgupta 10/31/11 - Bug 12909924 - modify 12465
/ jkati 10/05/11 - bug#12776899 : add 12458
/ mjgreave 11/08/04 - add 12456 (bug #3998954)
/ mjgreave 11/08/04 - add 12457
/ cchui 07/21/04 - add error message for sessinfo table clean up
/ pthornto 05/27/03 - add no-doc param for 12499
/ shwong 11/14/02 - modify 12473 based on suggestions from errors_us
/ shwong 11/13/02 - add 12473: procedure disabled when OID is in use
/ srtata 10/21/02 - add 12472
/ vpesati 12/12/01 - fix 12465 add 12471
/ gmurphy 02/06/01 - use Oracle Label Security in comments
/ rsripada 06/07/00 - update from 8.1.7
/ rburns 08/04/99 - cleanup for RDBMS checkin
/ rburns 07/31/99 - merge Rita's edits and add rest of messages
/ rburns 07/27/99 - add comparison errors
/ shwong 07/27/99 - remove 00000, 00000
/ shwong 07/22/99 - fix errors
/ rburns 07/13/99 - Add messages for PL/SQL functions
/ rburns 06/24/99 - add ADMIN errors
/ rburns 06/21/99 - add policy name error
/ cchui 06/08/99 - Modify datatype error, add event errors
/ cchui 05/14/99 - Add LBAC new messages for datatypes and events
/ rburns 04/08/99 - use 12400 to 12499 for now
/ rburns 03/01/99 - created
/ This file is converted to header/message files using lmsgen.c.
/
/ The first col is the ORACLE error number.
/ The second column is reserved and must (for now) be x00000
/ The remainder of the line is the error text (max 76 characters)
12400, 00000, "invalid argument to facility error handling"
// *Cause: An argument to a facility error handling function exceeded
// a maximum limit or referred to an invalid product/facility.
// *Action: Specify a valid facility error handling parameter value.
/ Policy Error Codes
12401, 00000, "invalid label string: %s"
// *Cause: The policy could not convert the label string to a valid
// internal label.
// *Action: Correct the syntax of the label string.
12402, 00000, "invalid format string: %s"
// *Cause: The format string is not supported by the policy.
// *Action: Correct the syntax of the format string.
12403, 00000, "invalid internal label"
// *Cause: An internal label could not be converted to a valid label for the
// policy.
// *Action: Analyze any additional messages on the error stack
// and consult the policy documentation.
12404, 00000, "invalid privilege string: %s"
// *Cause: The policy could not interpret the privilege string.
// *Action: Specify a privilege string that is supported by the policy.
12405, 00000, "invalid label list"
// *Cause: The policy determined that the label list was invalid
// for its intended use.
// *Action: Check the policy constraints on the specific list
// of labels.
12406, 00000, "unauthorized SQL statement for policy %s"
// *Cause: The policy did not authorize the database session to
// perform the requested SQL statement.
// *Action: Grant the user or program unit the necessary policy
// privilege or additional authorizations.
12407, 00000, "unauthorized operation for policy %s"
// *Cause: The policy did not authorize the database session to
// perform the requested operation.
// *Action: Grant the user or program unit the necessary policy
// privilege or additional authorizations.
12408, 00000, "unsupported operation: %s"
// *Cause: The specified policy does not support the requested
// operation.
// *Action: Consult the policy documentation to determine the
// supported access mediation operations.
12409, 00000, "policy startup failure for %s policy"
// *Cause: The policy encountered an error during startup processing;
// access to the data protected by the policy is prohibited.
// *Action: Check the alert log for additional information, correct the
// policy error, and restart the instance.
12410, 00000, "internal policy error for policy: %s\n Error: %s"
// *Cause: The policy enforcement encountered an internal error.
// *Action: Consult the policy documentation for details.
/ General LBAC error messages
12411, 00000, "invalid label value"
// *Cause: The specified label value does not exist.
// *Action: Check the data dictionary views for the policy to identify
// valid labels.
12412, 00000, "policy package %s is not installed"
// *Cause: The policy package does not exist in the database.
// *Action: Check that the policy package name is correct or install the
// required policy package.
12413, 00000, "labels do not belong to the same policy"
// *Cause: The labels being compared belong to different policies.
// *Action: Only compare labels that belong to the same policy.
12414, 00000, "internal LBAC error: %s\n Error: %s"
// *Cause: An internal label policy framework error occurred.
// *Action: Contact Oracle Customer Support.
12415, 00000, "A column of another datatype exists on the specified table"
// *Cause: The datatype of the column present in the table is different
// from the datatype set for the policy column.
// *Action: Drop the column on the table or change the datatype for
// policy column.
12416, 00000, "policy %s not found"
// *Cause: The specified policy does not exist in the database.
// *Action: Enter the correct policy name or create the policy.
12417, 00000, "database object \"%s\" not found"
// *Cause: The specified object was not in the database.
// *Action: Enter the correct name for the database object.
12418, 00000, "user %s not found"
// *Cause: The specified user does not exist in the database.
// *Action: Correct the user name or create the user.
12419, 00000, "null binary label value"
// *Cause: A null value was provided for a binary label operation.
// *Action: Provide a valid binary label for the operation.
12420, 00000, "required procedures and functions not in policy package \"%s\""
// *Cause: The policy package did not contain all of the procedures and
// functions necessary to enforce the policy.
// *Action: Consult the label framework documentation for a list of
// required procedures and functions for a policy package.
12421, 00000, "different size binary labels"
// *Cause: The label sizes for the binary label operation were not equal.
// *Action: Provide binary labels with the same lengths for the operation.
12422, 00000, "max policies exceeded"
// *Cause: You tried to create a new policy, but the maximum number of
// policies for the instance had already been created.
// *Action: Increase the size of the MAX_LABEL_POLICIES initialization
// parameter and restart the server.
12423, 00000, "invalid position specified"
// *Cause: The position specified for a binary label operation was invalid.
// *Action: Provide a position that is within the label size limits.
12424, 00000, "length exceeds binary label size"
// *Cause: The length specified for a binary label operation exceeded the
// the size of the binary label.
// *Action: Provide a bit or byte length that is within the label size limits.
12425, 00000, "cannot apply policies or set authorizations for system schemas"
// *Cause: You tried to either apply a policy to the SYS, SYSTEM, or LBACSYS
// schema or to set user labels/privileges for the SYS, SYSTEM, or
// LBACSYS user.
// *Action: Apply policies and set authorizations only for non-system users.
12426, 00000, "invalid audit option"
// *Cause: The option specified was not a valid audit option for
// the specified policy.
// *Action: Enter a correct audit option.
12427, 00000, "invalid input value for %s parameter"
// *Cause: An input parameter was specified incorrectly.
// *Action: Correct the parameter value.
12428, 00000, ""
// *Cause:
// *Action:
12429, 00000, "label list range exceeded"
// *Cause: The specified index value was not between 1 and 6.
// *Action: Correct the index value for the label list operation.
12430, 00000, "invalid privilege number"
// *Cause: The specified privilege number was not between 1 and 32.
// *Action: Correct the privilege number.
12431, 00000, "invalid audit action"
// *Cause: The specified audit action was not a valid audit action.
// *Action: Correct the audit action number.
12432, 00000, "LBAC error: %s"
// *Cause: LBAC enforcement resulted in an error.
// *Action: Correct the problem identified in the error message.
12433, 00000, "create trigger failed, policy not applied"
// *Cause: The policy could not be applied due to errors during the
// creation of a DML trigger.
// *Action: Correct the SQL syntax of the label function specification.
12434, 00000, "invalid audit type: %s"
// *Cause: The audit type must be BY ACCESS or BY SESSION.
// *Action: Correct the audit type value.
12435, 00000, "invalid audit success: %s"
// *Cause: The audit success parameter must be SUCCESSFUL or
// NOT SUCCESSFUL.
// *Action: Correct the audit success value.
12436, 00000, "no policy options specified"
// *Cause: A NULL option string was specified, but no default schema or
// policy option string was found.
// *Action: Enter a valid option string, or alter the schema or policy to have
// a valid default option string.
12437, 00000, "invalid policy option: %s"
// *Cause: A value that was not a valid policy option was entered.
// *Action: Correct the policy option value.
12438, 00000, "repeated policy option: %s"
// *Cause: A policy option was entered more than once in the option string.
// *Action: Remove the duplicate policy option value.
12439, 00000, "invalid combination of policy options"
// *Cause: A set of contradictory policy options was entered.
// *Action: Provide a set of compatible policy options.
12440, 00000, "insufficient authorization for the SYSDBA package"
// *Cause: The use of the SYSDBA package requires the LBAC_DBA role.
// *Action: Grant the LBAC_DBA role to the database user.
12441, 00000, "policy %s already exists"
// *Cause: You tried to create a policy with the same name as an existing one.
// *Action: Use a different name or drop the existing policy.
12442, 00000, "policy column \"%s\" already used by an existing policy"
// *Cause: You tried to create a policy with the same policy column
// name as an existing policy.
// *Action: Use a different name for the policy column or drop the
// existing policy.
12443, 00000, "policy not applied to some tables in schema"
// *Cause: You applied a policy to a schema, and some of the tables in the
// schema already had the policy applied.
// *Action: No action necessary; the policy was applied to the remaining
// tables.
12444, 00000, "policy already applied to table"
// *Cause: You tried to apply a policy to a table that was already protected
// by the policy.
// *Action: To change the policy options, predicate, or label function,
// remove the policy from the table and re-apply it.
12445, 00000, "cannot change HIDDEN property of column"
// *Cause: You tried to specify a different HIDE option for a table
// with an existing policy column.
// *Action: Drop the column from the table and reapply the policy with the new
// HIDE option.
12446, 00000, "Insufficient authorization for administration of policy %s"
// *Cause: You tried to perform an administrative function for a policy, but
// you have not been granted the <policy>_DBA role.
// *Action: Grant the user the <policy>_DBA role for the specified policy.
12447, 00000, "policy role already exists for policy %s"
// *Cause: The role named <policy>_DBA already exists.
// *Action: Correct the policy name or delete the existing policy.
12448, 00000, "policy %s not applied to schema or table %s"
// *Cause: An attempt was made to alter, enable or disable a schema or table
// policy that was not applied.
// *Action: Correct the policy or schema or table name.
12449, 00000, "Labels specified for user must be of type USER"
// *Cause: You tried to set labels for a user, but the labels in the list
// were not all designated as USER labels.
// *Action: Alter the labels to be USER labels.
12450, 00000, "LOB datatype disabled in LBAC initialization file"
// *Cause: You tried to specify a LOB datatype for a column or attribute,
// but the use of the LOB datatype has been disabled.
// *Action: Change the LBAC initialization file to allow the creation
// of LOB columns and attributes.
12451, 00000, "label not designated as USER or DATA"
// *Cause: A label is either a DATA label, a USER label, or both DATA and
// USER.
// *Action: Enter TRUE for at least DATA or USER.
12452, 00000, "label tag %s already exists"
// *Cause: The label tag value you entered is already in use for another
// label.
// *Action: Enter a different value for the label tag.
12453, 00000, "label %s already exists"
// *Cause: The label value you entered already exists.
// *Action: No action necessary; alter the label to change its tag or type.
12454, 00000, "label %s does not exist for policy %s"
// *Cause: The label tag or value you entered did not identify a label
// for the policy.
// *Action: Enter a label value or tag that is in use by the policy.
12455, 00000, "internal error in Label Security MMON cleanup task"
// *Cause: An internal error occurred in the Label Security MMON cleanup task.
// *Action: Contact Oracle Customer Support.
12456, 00000, "label security startup in progress"
// *Cause: You attempted to connect to the database before the Oracle
// Label Security component was fully initialized.
// *Action: Wait until the database is fully open before attempting to
// connect.
12457, 00000, "security label exceeded maximum allowable length"
// *Cause: An operation attempted to materialize a security label
// greater than 4000 bytes in length.
// *Action: Consult the Oracle Label Security documentation for
// information on how the length of a security label is
// calculated. Re-submit the operation once the problem has
// been corrected.
12458, 00000, "Oracle Label Security not enabled"
// *Cause: A Label Security operation was attempted without enabling
// Oracle Label Security.
// *Action: Consult the Oracle Label Security documentation for information
// on how to enable Oracle Label Security.
12459, 00000, "Oracle Label Security not configured"
// *Cause: An administrative operation was attempted without configuring
// Oracle Label Security.
// *Action: Consult the Oracle Label Security documentation for information
// on how to configure Oracle Label Security.
12460, 00000, "cannot disable Oracle Label Security when Database Vault is enabled"
// *Cause: An attempt was made to disable Oracle Label Security when
// Database Vault was enabled.
// *Action: Disable Database Vault and bounce the database before attempting to
// disable Oracle Label Security.
/ SA policy messages (saus.msg) start at 12461 to 12475
/ MLS policy messages (mlsus.msg) start at 12476 to 12499
/ (and can be re-used if necessary for additional LBAC or SA errors)
/ Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.
/
/ NAME
/ saus.msg
/ DESCRIPTION
/ Error messages for Oracle Label Security
/ Oracle Secure Access Policy 12455-12475
/ NOTES
/ Language : American
/ Character set : US7ASCII
/ MODIFIED
/ rburns 04/25/99 - created
/ This file is converted to header/message files using lmsgen.c.
/
/ The first col is the ORACLE error number.
/ The second column is reserved and must (for now) be x00000
/ The remainder of the line is the error text (max 76 characters)
12461, 00000, "undefined level %s for policy %s"
// *Cause: The specified level is not defined for the policy.
// *Action: Correct the level identifier value.
12462, 00000, "undefined compartment %s for policy %s"
// *Cause: The specified compartment is not defined for the policy.
// *Action: Correct the compartment identifier value.
12463, 00000, "undefined group %s for policy %s"
// *Cause: The specified group is not defined for the policy.
// *Action: Correct the group identifier value.
12464, 00000, "invalid characters in label component %s"
// *Cause: Label components can contain only alphanumeric characters, blanks,
// and underscores.
// *Action: Correct syntax of the label component.
12465, 00000, "not authorized for read or write on specified groups or compartments"
// *Cause: Groups or compartments were included that were not in the user's
// list of groups and compartments authorized for read or write access.
// *Action: Include groups or compartments authorized for read or write access
// in the user's list of groups and compartments.
12466, 00000, "default level is greater than the user's maximum"
// *Cause: The default level cannot be greater than the user's maximum.
// *Action: Enter an authorized level.
12467, 00000, "minimum label can contain a level only"
// *Cause: You included compartments or groups in the minimum label.
// *Action: Enter only an authorized minimum level as the label.
12468, 00000, "max write level does not equal max read level"
// *Cause: The level in the max write label must equal the
// level in the max read label.
// *Action: Enter max read and max write labels with the same level component.
12469, 00000, "no user levels found for user %s and policy %s"
// *Cause: No levels have been specified for the user.
// *Action: Enter the maximum and minimum labels for the user.
12470, 00000, "NULL or invalid user label: %s"
// *Cause: The label entered is NULL or not within the user's authorizations.
// *Action: Enter the authorized labels for the user.
12471, 00000, "Specified compartment or group is not authorized for user"
// *Cause: The specified compartment or group is not in user's authorizations
// or the user does not have read on compartment or group specified
// for write.
// *Action: Enter an authorized compartment or group.
12472, 00000, "policy %s is being used"
// *Cause: The policy which was being dropped due to event propagation from
// OID was applied to some table or schema.
// *Action: Drop a policy in OID only if it is not used in any of the
// databases using the policy.
12473, 00000, "The procedure is disabled when Label Security is used with OID."
// *Cause: Using Label Security with OID disabled this procedure.
// *Action: Do not use OID with Label Security if this procedure is required to
// function.
12474, 00000, "cannot change column name for a policy in use"
// *Cause: An attempt was made to change a column name for a policy that was
// applied on user schemas or tables.
// *Action: Disable the policy for all user schemas and tables before
// changing the column name.
12475, 00000, "incompatible Oracle Label Security configuration"
// *Cause: An attempt was made to configure Oracle Label Security with OID in a
// pluggable database when Oracle Label Security without OID is
// configured in another pluggable database or vice-versa.
// *Action: Use similar configurations of Oracle Label Security in all pluggable
// databases.
/ MLS policy adaptor messages (mlsus.msg) start at 12499 and work backwards
/ Copyright (c) 1999, 2015, Oracle and/or its affiliates. All rights reserved.
/
/ NAME
/ mlscus.msg
/ DESCRIPTION
/ Error messages for Oracle Label Security
/ MLS Policy Package - not released
/ NOTES
/ Language : American
/ Character set : US7ASCII
/ MODIFIED
/ rburns 09/01/99 - add mls-specific messages for DML
/ rburns 08/20/99 - add error messages
/ rburns 08/04/99 - cleanup for RDBMS checkin
/ rburns 07/31/99 - merge Ritas edits and add rest of messages
/ shwong 07/27/99 - remove 00000, 00000
/ rburns 06/24/99 - Add messages
/ shwong 06/08/99 - typo
/ shwong 05/28/99 - additional error messages
/ rburns 05/19/99 - Add more error messages
/ rburns 03/15/99 - created
/ This file is converted to header/message files using lmsgen.c.
/
/ The first col is the ORACLE error number.
/ The second column is reserved and must (for now) be x00000
/ The remainder of the line is the error text (max 76 characters)
12476, 00000, "least upper bound resulted in an invalid OS label"
// *Cause: You tried to do an operation that generated a least upper bound
// (LUB) label which is not a valid label on your operating system.
// *Action: Consult your OS label management documentation for information
// on invalid label generation.
12477, 00000, "greatest lower bound resulted in an invalid OS label"
// *Cause: You tried to do an operation that generated a greatest lower
// bound (GLB) label which is not a valid label on your operating
// system.
// *Action: Consult your OS label management documentation for information
// on invalid label generation.
12479, 00000, "file label %s must equal DBHIGH %s"
// *Cause: A database file had an OS label that did not match
// DBHIGH. Either DBHIGH was altered or the OS file
// was relabeled.
// *Action: Relabel the file so that its label matches DBHIGH, or
// alter DBHIGH so that it matches the label on the file.
12480, 00000, "specified clearance labels not within the effective clearance"
// *Cause: You specified a clearance range that was not within your
// authorized clearance; you can only specify clearance ranges
// that are within your clearance.
// *Action: Specify clearance labels that are within your own clearance
// range.
12481, 00000, "effective label not within program unit clearance range"
// *Cause: The effective label when the program unit was invoked was
// not within the range authorized for the program unit.
// *Action: Modify the program unit clearance range or invoke the program
// unit from a session with an authorized effective clearance.
12482, 00000, "internal MLS error: %s\n Error: %s"
// *Cause: An internal MLS policy error occurred.
// *Action: Contact Oracle Customer Support.
12483, 00000, "label not in OS system accreditation range"
// *Cause: The specified label is above the OS maximum label or
// below the OS minimum label.
// *Action: Use a label that is within the accreditation range for the
// host OS.
12484, 00000, "invalid OS label"
// *Cause: The specified label does not exist in the OS host's label
// definition file.
// *Action: Use the OS label management tools to define the label.
12485, 00000, "new effective label not within effective clearance"
// *Cause: You attempted to enter a value for an effective label that
// did not dominate the effective min label or was not dominated
// by the effective max label.
// *Action: Enter a value between the min and the max labels.
12486, 00000, "effective max labels and min labels cannot be changed"
// *Cause: You attempted to enter a value for an effective min label
// or effective max label, but these labels cannot be changed.
// *Action: Enter NULL values for the effective minimum and maximum labels.
12487, 00000, "clearance labels not between DBHIGH and DBLOW"
// *Cause: You attempted to enter a value for a clearance label that was
// not dominated by DBHIGH or did not dominate DBLOW.
// *Action: Enter clearance label values between DBHIGH and DBLOW.
12488, 00000, "maximum label does not dominate minimum label"
// *Cause: You attempted to enter a value for a clearance label that did not
// preserve the dominance relationship between the minimum and
// maximum labels.
// *Action: Enter label values that preserves the dominance relationship
// between the minimum and maximum.
12489, 00000, "default label not within clearance range"
// *Cause: You attempted to enter a value for a default label that did not
// dominate the minimum clearance or was not dominated by the
// maximum clearance.
// *Action: Enter a default label value within the clearance range.
12490, 00000, "DBHIGH cannot be lowered"
// *Cause: You attempted to enter a value for DBHIGH that did not
// dominate the existing value of DBHIGH.
// *Action: Enter a value for DBHIGH that dominates the old value.
12491, 00000, "DBHIGH value does not dominate DBLOW"
// *Cause: You attempted to enter a value for DBHIGH that did not
// dominate DBLOW.
// *Action: Enter a value for DBHIGH that dominates DBLOW.
12492, 00000, "DBLOW cannot be changed"
// *Cause: You attempted to change the value of DBLOW after it had been
// set to any initial value. DBLOW can only be set once after
// initial database creation.
// *Action: To change DBLOW, you have to create a new database,
// set DBLOW to the new value, and import your data into the new
// database.
12493, 00000, "invalid MLS binary label"
// *Cause: The MLS binary label contained an invalid value, was not the
// correct size, or contained a level, category, or release
// category that was not enabled.
// *Action: Check the DBA_MLS_LABELS view for the valid MLS labels.
12494, 00000, "cannot insert or delete a level, category, or release category"
// *Cause: You attempted to insert or delete a level, category, or
// release category definition.
// *Action: If the label definition is no longer valid, change its name to
// one that identifies it as invalid. When any labels are converted
// to character strings, the new label definition will be used.
12495, 00000, "cannot disable an enabled level, category, or release category"
// *Cause: You attempted to disable a level, category, or release category
// that had previously been enabled. An enabled label definition
// may be exist in some database label, so cannot be disabled.
// *Action: If the label definition is no longer valid, change its name to
// one that identifies it as invalid. When any labels are converted
// to character strings, the new label definition will be used.
12496, 00000, "cannot change existing level, category, or release numbers"
// *Cause: You attempted to change the number assigned to level, category
// or releasability category.
// *Action: Change the character string representations, not the numbers.
12497, 00000, "maximum combined categories exceeds %s"
// *Cause: The maximum number of descriptive categories plus release
// categories supported by the MLS policy was exceeded.
// *Action: Enter numbers that do not add up to more than the maximum.
/ Used to check if add/drop column on object table should be allowed in atb.c
12498, 00000, ""
// *Cause:
// *Action:
/ Used in kztins() for RLS test suite to work ok.
12499, 00000, ""
// *Document: NO
// *Cause:
// *Action:
/ Copyright (c) 1991, 1996, 1997, 1998, 1999, 2000, 2001 by the Oracle Corporation. All rights reserved.
/
/
/ $Header: network_src/mesg/net12500.msg /st_network_18.0/1 2018/05/01 19:35:31 shubhaku Exp $
/
/
/ NAME
/ net12500.msg - Oracle Net external message file starting from 12500 -
/ U.S. english version
/
/
/ FUNCTION
/ Network error message file, American English version.
/
/
/ NOTES
/ Only external errors are to be put into this file. Internal
/ messages are to put into netius.msg.
/
/ This file, along with netius.msg and net12150.msg, forms tnsus.msg. As a
/ result, the errors in this file may not overlap with the errors in
/ those files. Otherwise, errors will result when generating tnsus.msb.
/
/ Message text should be limited to a maximum of 76 characters.
/ Messages containing embedded % directives should not overrun
/ the 76 character limit unless they signal unusual errors
/ which do not occur as part of user applications. For example,
/ startup errors and system-dependent errors can probably get
/ away with longer message text.
/
/
/ '/' at beginning-of-line for comments.
/ '//' at beginning-of-line for *Cause: and *Action: fields.
/
/
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
/////////////////////////// Please maintain this map //////////////////////
/
// 00001 - 04200 See netius.msg
/ .
/ .
/ 12150 - 12285 See net12150.msg
/ 12286 - 12499 ---(Reserved)---
/ 12500 - 12530 NSG errors reportable by OSN (returned in cndo).
/ 12531 - 12629 NS (and NT errors reported as NS errors) reportable by OSN
/ 12630 - 12699 NA errors (returned by native services)
/ .
/ .
/ .
/
/////////////////////////// Please maintain this map //////////////////////
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
/
/
/
/
/ OWNER
/ Network and Management Products - Server Technologies
/
/ MODIFIED
/ suhgarg 02/08/18 - Bug 27506774: reflect dctm feature name in errors.
/ rajeekku 11/02/17 - Bug 27027813: modify errors 12691-95
/ bhmathur 01/21/16 - Support for service rate limit.
/ bhmathur 06/18/15 - Support for error sending mechanism.
/ babandi 04/08/15 - Modify the error number for NSEAPPINTR.
/ spamu 01/22/15 - bug 20230367: rate limit reached error msg
/ babandi 08/24/14 - new mesg added.
/ msleong 10/23/12 - Services moved from ASO to EE
/ bhmathur 05/25/11 - Support listener in GSM mode.
/ sreguna 02/23/09 - Add Wallet open failure error message
/ skramas 08/30/06 - Enhance error 12504 to include default service.
/ fekhan 05/09/06 - New dhctx related errors.
/ jpullokk 12/10/02 - Change documentation for 12535
/ ppovinec 11/21/02 - 12526-12528 updated
/ ppovinec 10/08/02 - Add listener messages for RESTRICTED instance
/ mclose 10/03/02 - Improve messages
/ cozhang 07/24/02 - Msgs for 12607 NSECONNTIMEOUT, 12608 NSESENDTIMEOUT
/ & 12609 NSERECVTIMEOUT. Move NSEAPPTIMEOUT to 12606.
/ vle 07/16/02 - Modify NA error messages
/ cozhang 03/15/02 - Add msg for lsnr connect timeout (12525 NSGMOCTO).
/ cozhang 12/11/01 - Add message for app timeout (12604 NSEAPPTIMEOUT).
/ rachacos 04/04/01 - Define message for 12602 (NSECPLIMIT).
/ ppovinec 02/08/01 - Net8 --> Oracle Net rename.
/ ppovinec 07/18/00 - Listener's 8.2 error messages.
/ tclarke 02/25/00 - umcomment lost messages for oerr
/ ppovinec 07/16/99 - Make 12510 more meaningful.
/ vle 04/29/99 - fix misspelling
/ emalasky 11/10/98 - add catch-all handler error
/ emalasky 11/04/98 - add new direct handoff failure error
/ skanjila 09/04/98 - Add NAE Double Encryption Error Message.
/ emalasky 04/05/98 - add 8.1 service naming messsages
/ emalasky 12/09/97 - add NSG messages
/ emalasky 05/07/97 - 12505: no args, better cause
/ emalasky 05/01/97 - rollback 12505
/ smckinle 04/21/97 - Change 12505 to take an SID parameter.
/ rwessman 03/19/97 - Eliminated references to Secure Network Services. It
/ rwessman 03/09/97 - split from netus.msg to correct bug in building
/ oraus.msg.
/
/ Some error messages are obsolete (no longer used). They have been removed
/ from this file and their error numbers can at some point distant point
/ in the future be reused. In order to track there error numbers they are
/ listed below by what release they were removed for and the date they
/ were removed.
/
/ Removed beginning with release 10.0.0.X on 10/03/2002:
/ 12501,12506,12507,12512,12517
/
/ 12500 - 12530 Reserved for NSG errors reportable to OSN.
/
/ tnslsnr errors...
12500, 00000, "TNS:listener failed to start a dedicated server process"
// *Cause: The process of starting up a dedicated server process failed.
// The executable could not be found or the environment may be set up
// incorrectly.
// *Action: Turn on tracing at the ADMIN level and reexecute the operation.
// Verify that the ORACLE Server executable is present and has execute
// permissions enabled. Ensure that the ORACLE environment is specified
// correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being
// called may not be installed on the local hard drive. Please check that
// the correct Protocol Adapter are successfully linked.
// If error persists, contact Oracle Customer Support.
/
12502, 00000, "TNS:listener received no CONNECT_DATA from client"
// *Cause: No CONNECT_DATA was passed to the listener.
// *Action: Check that the service name resolved from TNSNAMES.ORA has
// the CONNECT_DATA component of the connect descriptor.
/
12503, 00000, "TNS:listener received an invalid REGION from client"
// *Cause: Invalid REGION was passed to the listener.
// *Action: Check the REGION name specified in the CONNECT_DATA component of
// the connect descriptor.
/
12504, 00000, "TNS:listener was not given the SERVICE_NAME in CONNECT_DATA"
// *Cause: The listener was not configured with a default service and
// SERVICE_NAME was missing from the CONNECT_DATA received by the listener.
// *Action: Possible solutions are:
// - Configure DEFAULT_SERVICE parameter in LISTENER.ORA with a valid service
// name. Reload the listener parameter file using reload [<listener_name>].
// This should be done by the LISTENER administrator.
// - If using a service name, Check that the connect descriptor corresponding
// to the service name in TNSNAMES.ORA has a SERVICE_NAME or SID component
// in the CONNECT_DATA.
/
12505, 00000, "TNS:listener does not currently know of SID given in connect descriptor"
// *Cause: The listener received a request to establish a connection to a
// database or other service. The connect descriptor received by the listener
// specified a SID for an instance (usually a database instance) that either
// has not yet dynamically registered with the listener or has not been
// statically configured for the listener. This may be a temporary condition
// such as after the listener has started, but before the database instance
// has registered with the listener.
// *Action:
// - Wait a moment and try to connect a second time.
// - Check which instances are currently known by the listener by executing:
// lsnrctl services <listener name>
// - Check that the SID parameter in the connect descriptor specifies
// an instance known by the listener.
// - Check for an event in the listener.log file.
/
12506, 00000, "TNS:listener rejected connection based on service ACL filtering"
// *Cause: The client is not present in Service Access Control List.
// *Action: Add the client's address in Service ACL.
// *Comment: The client must have its address present in service ACL for
// firewall enabled endpoints.
/
12508, 00000, "TNS:listener could not resolve the COMMAND given"
// *Cause: The COMMAND given to listener is not supported.
// *Action: This is not seen in normal use of Oracle Net.
// *Comment: Check the COMMAND given to listener. This error is probably
// caused by incompatible Oracle Net or Net8 versions.
// Do not include in error manual.
/
12509, 00000, "TNS:listener failed to redirect client to service handler"
// *Cause: The dispatcher terminated unexpectedly
// *Action: Attempt to connect again and if the same error occurs,
// contact the DBA to check the state of the dispatchers for this SID.
// If the problem persists, turn on tracing in the listener to determine
// the TNS error caused by the redirect.
/
12510, 00000, "TNS:database temporarily lacks resources to handle the request"
// *Cause: The dispatchers appear to be busy handling other requests.
// *Action: Attempt the connection again. If error persists, ask
// the DBA to increase the number of dispatchers and/or dispatchers' limit on
// number of connections/sessions that they can accept.
/
12511, 00000, "TNS:service handler found but it is not accepting connections"
// *Cause: The dispatchers notified the listener that they temporarily
// do not accept new connections.
// *Action: Attempt the connection again. If error persists, contact the DBA
// to check the state of the dispatchers and/or ask him to increase the number
// of dispatchers.
/
12513, 00000, "TNS:service handler found but it has registered for a different protocol"
// *Cause: The dispatchers registered for this service are connected to
// the listener by way of a different network protocol than that of the client.
// *Action: Contact the DBA to register a dispatcher on your protocol.
/
12514, 00000, "TNS:listener does not currently know of service requested in connect descriptor"
// *Cause: The listener received a request to establish a connection to a
// database or other service. The connect descriptor received by the listener
// specified a service name for a service (usually a database service)
// that either has not yet dynamically registered with the listener or has
// not been statically configured for the listener. This may be a temporary
// condition such as after the listener has started, but before the database
// instance has registered with the listener.
// *Action:
// - Wait a moment and try to connect a second time.
// - Check which services are currently known by the listener by executing:
// lsnrctl services <listener name>
// - Check that the SERVICE_NAME parameter in the connect descriptor of the
// net service name used specifies a service known by the listener.
// - If an easy connect naming connect identifier was used, check that
// the service name specified is a service known by the listener.
// - Check for an event in the listener.log file.
/
12515, 00000, "TNS:listener could not find a handler for this presentation"
// *Cause: None of the listener's known service handlers are registered
// as supporting the presentation protocol required by the connecting client.
// *Action: Check that the destination service is configured to accept the
// presentation protocol.
/
12516, 00000, "TNS:listener could not find available handler with matching protocol stack"
// *Cause: None of the known and available service handlers for the given
// SERVICE_NAME support the client's protocol stack: transport, session,
// and presentation protocols.
// *Action: Check to make sure that the service handlers (e.g. dispatchers)
// for the given SERVICE_NAME are registered with the listener, are accepting
// connections, and that they are properly configured to support the desired
// protocols.
/
12518, 00000, "TNS:listener could not hand off client connection"
// *Cause: The process of handing off a client connection to another process
// failed.
// *Action: Turn on listener tracing and re-execute the operation. Verify
// that the listener and database instance are properly configured for
// direct handoff. If problem persists, call Oracle Support.
// *Comment: The problem can be worked around by configuring dispatcher(s)
// to specifically handle the desired presentation(s), and connecting
// directly to the dispatcher, bypassing the listener.
/
12519, 00000, "TNS:no appropriate service handler found"
// *Cause: The listener could not find any available service handlers that
// are appropriate for the client connection.
// *Action: Run "lsnrctl services" to ensure that the instance(s) have
// registered with the listener, and are accepting connections.
/
12520, 00000, "TNS:listener could not find available handler for requested type of server"
// *Cause: None of the known and available service handlers for requested type
// of server (dedicated or shared) are appropriate for the client connection.
// *Action: Run "lsnrctl services" to ensure that the instance(s) have
// registered with the listener and that the appropriate handlers are
// accepting connections.
/
12521, 00000, "TNS:listener does not currently know of instance requested in connect descriptor"
// *Cause: The listener received a request to establish a connection to a
// database or other service. The connect descriptor received by the listener
// specified in addition to the service name an instance name for an instance
// (usually a database instance) that either has not yet dynamically registered
// with the listener or has not been statically configured for the listener.
// This may be a temporary condition such as after the listener has started,
// but before the database instance has registered with the listener.
// *Action:
// - Wait a moment and try to connect a second time.
// - Check which instances are currently known by the listener by executing:
// lsnrctl services <listener name>
// - Check that the INSTANCE_NAME parameter in the connect descriptor specifies
// an instance name known by the listener.
// - Check for an event in the listener.log file.
/
12522, 00000, "TNS:listener could not find available instance with given INSTANCE_ROLE"
// *Cause: There are not any available and appropriate database instances
// registered with the listener, that are part of the service identified by
// SERVICE_NAME given in the connect descriptor and that have the specified
// INSTANCE_ROLE (and INSTANCE_NAME, if specified).
// *Action: Check to make sure that the INSTANCE_ROLE specified is correct.
// Run "lsnrctl services" to ensure that the instance(s) have registered with
// the listener and that they are ready to accept connections.
/
12523, 00000, "TNS:listener could not find instance appropriate for the client connection"
// *Cause: The listener could not find any available (database) instances,
// that are appropriate for the client connection.
// *Action: Run "lsnrctl services" to ensure that the instance(s) are
// registered with the listener, and have status READY.
/
12524, 00000, "TNS:listener could not resolve HANDLER_NAME given in connect descriptor"
// *Cause: The HANDLER_NAME in the CONNECT_DATA was not found in the listener's
// tables for the specified SERVICE_NAME and INSTANCE_NAME.
// *Action: Check to make sure that the HANDLER_NAME specified is correct.
// *Comment: This error will be returned if the database instance and/or its
// service handlers have not been registered with the listener or they have
// been registered for different service; the instance may need to be started.
/
12525, 00000, "TNS:listener has not received client's request in time allowed"
// *Cause: The listener disconnected the client because the client failed to
// provide the necessary connect information within the allowed time interval.
// This may be a result of network or system delays; or this may indicate that a
// malicious client is trying to cause a Denial of Service attack on the
// listener.
// *Action: If the error occurred because of a slow network or system,
// reconfigure INBOUND_CONNECT_TIMEOUT to a larger value. If a malicious
// client is suspected, use the address in listener.log to identify the
// source and restrict access. Turn on tracing for more information.
// *Comment: The logged address in listener.ora may not be reliable as it
// can be forged at the lower networking layers (e.g. in the case of TCP/IP).
/
12526, 00000, "TNS:listener: all appropriate instances are in restricted mode"
// *Cause: Database instances supporting the service requested by the client
// were in restricted mode. The Listener does not allow connections to
// instances in restricted mode. This condition may be temporary, such as
// during periods when database administration is performed.
// *Action: Attempt the connection again. If error persists, then contact
// the database administrator to change the mode of the instance,
// if appropriate.
/
12527, 00000, "TNS:listener: all instances are in restricted mode or blocking new connections"
// *Cause: All appropriate database instances supporting the service requested
// by the client reported that they either were in restricted mode or were
// blocking the new connections. The Listener does not allow connections to
// such instances. This condition may be temporary, such as at instance
// startup.
// *Action: Attempt the connection again. If error persists, then contact the
// database administrator to check the status of the instances.
/
12528, 00000, "TNS:listener: all appropriate instances are blocking new connections"
// *Cause: All instances supporting the service requested by the client
// reported that they were blocking the new connections. This condition may be
// temporary, such as at instance startup.
// *Action: Attempt the connection again. If error persists, then contact the
// administrator to check the status of the instances.
/
12529, 00000, "TNS:connect request rejected based on current filtering rules"
// *Cause: Connection Manager and its listener were configured with filtering
// rules specifying that the connect request be rejected.
// *Action: If this connect request should be allowed, then contact the
// administrator to modify the filtering rules.
/
12530, 00000, "TNS:listener: rate limit reached"
// *Cause: Listener has reached connection or service rate limit and hence
// rejected the connection.
// *Action: Attempt the connection again. If the error occurs frequently,
// contact the database administrator to increase connection or service rate
// limit.
/
/ This line is an OSN Magic Cookie. Don't eat it. Last NSG error in 2.0.9.
/
/
////////////////////////////////////////////////////////////////////
/
/ 12531 - 12629 ns errors reportable to osn:
/
/ 12531 - 15609 ns primary errors
/ 12610 - 12629 ns secondary errors
/
/ A primary may (optionally) be qualified by a secondary
/ error. For example: 12531 ("invalid argument") might
/ be qualified by 12617 ("bad 'what' value").
/
12531, 00000, "TNS:cannot allocate memory"
// *Cause: Sufficient memory could not be allocated to perform the desired
// activity.
// *Action: Either free some resource for TNS, or add more memory to the
// machine. For further details, turn on tracing and reexecute the operation.
/
12532, 00000, "TNS:invalid argument"
// *Cause: An internal function received an invalid parameter.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12533, 00000, "TNS:illegal ADDRESS parameters"
// *Cause: An illegal set of protocol adapter parameters was specified. In
// some cases, this error is returned when a connection cannot be made to the
// protocol transport.
// *Action: Verify that the destination can be reached using the specified
// protocol. Check the parameters within the ADDRESS section of
// TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the
// Oracle operating system specific documentation for your platform.
// Protocols that resolve names at the transport layer (such as DECnet object
// names) are vulnerable to this error if not properly configured or names are
// misspelled.
/
12534, 00000, "TNS:operation not supported"
// *Cause: An internal function received a request to perform an
// operation that is not supported (on this machine).
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12535, 00000, "TNS:operation timed out"
// *Cause: The requested operation could not be completed within the time out
// period.
// *Action: Look at the documentation on the secondary errors for possible
// remedy. See SQLNET.LOG to find secondary error if not provided explicitly.
// Turn on tracing to gather more information.
/
12536, 00000, "TNS:operation would block"
// *Cause: An internal operation did not commence because to do so would
// block the current process and the user has requested that operations be
// non-blocking.
// *Action: None needed; this is an information message.
/
12537, 00000, "TNS:connection closed"
// *Cause: "End of file" condition has been reached; partner has disconnected.
// *Action: None needed; this is an information message.
/
12538, 00000, "TNS:no such protocol adapter"
// *Cause: The protocol adapter requested (by way of the "(PROTOCOL=..)"
// keyword-value pair in a TNS address) is unknown. If the supplied address
// is typographically correct then the protocol adapter is not installed.
// *Action: Install the protocol adapter or correct typographically error,
// as appropriate. Note: if the supplied address was derived from
// resolving the service name, check the address in the appropriate file
// (TNSNAMES.ORA, LISTENER.ORA or SQLNET.ORA).
/
12539, 00000, "TNS:buffer over- or under-flow"
// *Cause: Buffer too small for incoming data or too large for outgoing data.
// *Action: This restriction (which is associated with CONNECT DATA) is not
// normally visible to the user. For further details, turn on tracing and
// reexecute the operation; contact Oracle Customer Support.
/
12540, 00000, "TNS:internal limit restriction exceeded"
// *Cause: Too many TNS connections open simultaneously.
// *Action: Wait for connections to close and re-try.
/
12541, 00000, "TNS:no listener"
// *Cause: The connection request could not be completed because the listener
// is not running.
// *Action: Ensure that the supplied destination address matches one of
// the addresses used by the listener - compare the TNSNAMES.ORA entry with
// the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to
// go by way of an Interchange). Start the listener on the remote machine.
/
12542, 00000, "TNS:address already in use"
// *Cause: Specified listener address is already being used.
// *Action: Start your listener with a unique address.
/
12543, 00000, "TNS:destination host unreachable"
// *Cause: Contact can not be made with remote party.
// *Action: Make sure the network driver is functioning and the network is up.
/
12544, 00000, "TNS:contexts have different wait/test functions"
// *Cause: Two protocol adapters have conflicting wait/test functions.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12545, 00000, "Connect failed because target host or object does not exist"
// *Cause: The address specified is not valid, or the program being
// connected to does not exist.
// *Action: Ensure the ADDRESS parameters have been entered correctly; the
// most likely incorrect parameter is the node name. Ensure that the
// executable for the server exists (perhaps "oracle" is missing.)
// If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the
// host name to a numeric IP address and try again.
/
12546, 00000, "TNS:permission denied"
// *Cause: User has insufficient privileges to perform the requested operation.
// *Action: Acquire necessary privileges and try again.
/
12547, 00000, "TNS:lost contact"
// *Cause: Partner has unexpectedly gone away, usually during process
// startup.
// *Action: Investigate partner application for abnormal termination. On an
// Interchange, this can happen if the machine is overloaded.
/
12548, 00000, "TNS:incomplete read or write"
// *Cause: A data send or receive failed.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12549, 00000, "TNS:operating system resource quota exceeded"
// *Cause: The current user has exceeded the allotted resource assigned in the
// operating system.
// *Action: Acquire more operating system resource, or perform a different
// function.
/
12550, 00000, "TNS:syntax error"
// *Cause: The supplied connect descriptor contains illegal syntax.
// *Action: Check the syntax of the connect descriptor in TNSNAMES.ORA.
/
12551, 00000, "TNS:missing keyword"
// *Cause: The supplied connect descriptor is missing one or more TNS
// keywords.
// *Action: Check the syntax, and ensure all required keywords are present.
/
12552, 00000, "TNS:operation was interrupted"
// *Cause: An internal operation was interrupted and could not complete.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12554, 00000, "TNS:current operation is still in progress"
// *Cause: An internal operation is still in progress.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12555, 00000, "TNS:permission denied"
// *Cause: User has insufficient privileges to perform the requested operation.
// *Action: Acquire necessary privileges and try again.
/
12556, 00000, "TNS:no caller"
// *Cause: TNS detected an incoming connect request but there was no caller.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12557, 00000, "TNS:protocol adapter not loadable"
// *Cause: On some platforms (such as OS/2) protocol adapters are loaded at
// run-time. If the shared library (or DLL) for the protocol adapter is
// missing or one of its supporting libraries is missing then this error is
// returned.
// *Action: For further details, turn on tracing and reexecute the operation.
// The trace file will include the name of the shared library (or DLL) that
// could not be loaded.
/
12558, 00000, "TNS:protocol adapter not loaded"
// *Cause: On some platforms (such as OS/2) protocol adapters are loaded at
// run-time. If the shared library (or DLL) for the protocol adapter has not
// been loaded, then this error is returned.
// *Action: For further details, turn on tracing and reexecute the operation.
// The trace file will have the name of the shared library (or DLL) that has
// not been loaded.
/
12560, 00000, "TNS:protocol adapter error"
// *Cause: A generic protocol adapter error occurred.
// *Action: Check addresses used for proper protocol specification. Before
// reporting this error, look at the error stack and check for lower level
// transport errors. For further details, turn on tracing and reexecute the
// operation. Turn off tracing when the operation is complete.
/
12561, 00000, "TNS:unknown error"
// *Cause: A generic protocol error occurred.
// *Action: For further details, turn on tracing and reexecute the operation.
/
12562, 00000, "TNS:bad global handle"
// *Cause: Internal error - bad 'gbh' argument passed to TNS from caller.
// System may have been linked with old libraries.
// *Action: Not normally visible to the user, contact Oracle Customer
// Support.
/
12563, 00000, "TNS:operation was aborted"
// *Cause: NT operation was interrupted by the uppper layer.
// *Action: None.
/
12564, 00000, "TNS:connection refused"
// *Cause: The connect request was denied by the remote user (or TNS software).
// *Action: Not normally visible to the user. For further details, turn on
// tracing and reexecute the operation.
/
12566, 00000, "TNS:protocol error"
// *Cause: An unexpected TNS protocol error has occurred.
// *Action: For further details, turn on tracing and reexecute the operation.
// If error persists, contact Oracle Customer Support.
/
12569, 00000, "TNS:packet checksum failure"
// *Cause: The data received is not the same as the data sent.
// *Action: Attempt the transaction again. If the error is persistent, turn
// on tracing and reexecute the operation.
/
12570, 00000, "TNS:packet reader failure"
// *Cause: An error occurred during a data receive.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12571, 00000, "TNS:packet writer failure"
// *Cause: An error occurred during a data send.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12574, 00000, "TNS:Application generated error"
// *Cause: This error was generated by peer application.
// Please see secondary errors for the actual cause.
// *Action: Action should be taken on secondary error.
/
12575, 00000, "TNS:dhctx busy"
// *Cause: The handoff over a dhctx failed as dhctx was already busy
// with an ongoing handoff.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12576, 00000, "TNS:handoff not supported for this session"
// *Cause: Handoff of a established session was attempted which either had
// tcps as its transport or NA options were enabled for this session.
// *Action: Check the transport setting as well as NA options.
// If error persists, contact Oracle Customer Support.
/
12578, 00000, "TNS:wallet open failed"
// *Cause: An error was encountered while trying to open the specified wallet.
// *Action: For further details, turn on tracing and re-execute the operation.
/
12582, 00000, "TNS:invalid operation"
// *Cause: An internal function received an invalid request.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12583, 00000, "TNS:no reader"
// *Cause: A send operation has been requested but partner has already
// disconnected.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12585, 00000, "TNS:data truncation"
// *Cause: A receive operation has completed with insufficient data
// to satisfy the user's request.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12589, 00000, "TNS:connection not bequeathable"
// *Cause: An attempt to hand-off a connection from one process to another
// has failed because the protocol provider does not support it.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12590, 00000, "TNS:no I/O buffer"
// *Cause: An attempt to perform an I/O operation failed because no buffer
// was available.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12591, 00000, "TNS:event signal failure"
// *Cause: The TNS software is unable to signal an event occurrence.
// *Action: For further details, turn on tracing and reexecute the operation.
// If error persists, contact Oracle Customer Support.
/
12592, 00000, "TNS:bad packet"
// *Cause: An ill-formed packet has been detected by the TNS software.
// *Action: For further details, turn on tracing and reexecute the
// operation. If error persists, contact Oracle Customer Support.
/
12593, 00000, "TNS:no registered connection"
// *Cause: An attempt to solicit network event activity has failed because
// no connections are registered for event notification.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12595, 00000, "TNS:no confirmation"
// *Cause: TNS is unable to get requested confirmation acknowledgment from
// remote partner.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12596, 00000, "TNS:internal inconsistency"
// *Cause: TNS has detected an internal inconsistency.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation and contact Oracle Customer
// Support.
/
12597, 00000, "TNS:connect descriptor already in use"
// *Cause: Internal error - illegal use of connect descriptor.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12598, 00000, "TNS:banner registration failed"
// *Cause: The registration of a product banner with the Oracle server failed.
// *Action: This is an error which is not normally visible externally. Enable
// tracing and attempt to repeat the error. If it occurs
// again, contact Oracle Customer Support.
/
12599, 00000, "TNS:cryptographic checksum mismatch"
// *Cause: The data received is not the same as the data sent.
// *Action: Attempt the transaction again. If error persists, check
// (and correct) the integrity of your physical connection.
/
12600, 00000, "TNS: string open failed"
// *Cause: The creation of a string in ORACLE NLS format failed.
// *Action: This is an internal error, enable tracing and attempt to repeat the
// error. If it occurs again, contact Oracle Customer Support.
/
12601, 00000, "TNS:information flags check failed"
// *Cause: The TNS information flags set by the process prior to connection
// negotiation were not present after the negotiation was
// finished.
// *Action: This is an internal error. Enable tracing and attempt to repeat the
// error. If it occurs again, contact Oracle Customer
// Support.
/
12602, 00000, "TNS: Connection Pooling limit reached"
// *Cause: The operation failed because maximum active current connections has
// been reached. It may not be a real error when the Connection
// Pooling feature is enabled. It is possible that the application
// later reissues the operation and successfully grabs the connection
// pool slot and proceeds.
// *Action: This is an internal error. Enable tracing and attempt to repeat the
// error. If it occurs again, contact Oracle Customer
// Support.
/
/ 12606 - 12629 ns secondary errors
/
12606, 00000, "TNS: Application timeout occurred"
// *Cause: A network session did not reach an application-defined stage
// within the allowed time interval.
// *Action: This is an error which does not normally appear at the high level.
// The action to take is application specific, and is detailed in the
// higher level error description.
/
12607, 00000, "TNS: Connect timeout occurred"
// *Cause: A network session did not reach a predefined connect stage
// within the allowed time interval.
// *Action: This is an error which does not normally appear at the high level.
// The action to take is application specific, and is detailed in the
// higher level error description.
/
12608, 00000, "TNS: Send timeout occurred"
// *Cause: The send or write operation did not complete within the allowed
// time interval.
// *Action: Check if the peer host is available. Increase the send timeout
// value if necessary.
/
12609, 00000, "TNS: Receive timeout occurred"
// *Cause: The receive or read operation did not complete within the allowed
// time interval.
// *Action: Check if the peer host is available. Increase the receive timeout
// value if necessary.
/
12611, 00000, "TNS:operation is not portable"
// *Cause: Attempted operation is not portable.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12612, 00000, "TNS:connection is busy"
// *Cause: Attempted operation failed because it conflicts with an ongoing
// action or status of the connection.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12615, 00000, "TNS:preempt error"
// *Cause: A request to service an event failed because no event notification
// has yet been posted.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12616, 00000, "TNS:no event signals"
// *Cause: The TNS software is unable to enable event signals.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
/12617, 00000, "TNS:bad 'what' type"
// *Cause: The operation failed because the type of data specified is unknown.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12618, 00000, "TNS:versions are incompatible"
// *Cause: The two machines are running incompatible versions of TNS.
// *Action: Check the version numbers, and upgrade the machine with the
// smaller one.
/
12619, 00000, "TNS:unable to grant requested service"
// *Cause: The connect request failed because requested service could not be
// provided by the local TNS software.
// *Action: If appropriate, reexecute with reduced service requirements.
/
12620, 00000, "TNS:requested characteristic not available"
// *Cause: The connect request failed because a requested transport
// characteristic could not be supported by the remote TNS software.
// *Action: If appropriate, reexecute with reduced requirements.
/
12622, 00000, "TNS:event notifications are not homogeneous"
// *Cause: An attempt to register a connection for event notification failed
// because the event notification type conflicts with existing registrations.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation and contact Oracle Customer
// Support.
/
12623, 00000, "TNS:operation is illegal in this state"
// *Cause: Connection is half-duplex and a full-duplex operation was
// attempted.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation. If error persists, contact
// Oracle Customer Support.
/
12624, 00000, "TNS:connection is already registered"
// *Cause: An attempt to register a connection for event notification failed
// because the connection is already registered.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation and contact Oracle Customer
// Support.
/
12625, 00000, "TNS:missing argument"
// *Cause: An operation failed because an argument was missing"
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation and contact Oracle Customer
// Support.
/
12626, 00000, "TNS:bad event type"
// *Cause: An attempt to register a connection for event notification failed
// because the event type is unknown.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation and contact Oracle Customer
// Support.
/
12628, 00000, "TNS:no event callbacks"
// *Cause: An attempt to register a connection for event notification failed
// because asynchronous callbacks are not available.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation and contact Oracle Customer
// Support.
/
12629, 00000, "TNS:no event test"
// *Cause: An attempt to register a connection for event notification failed
// because the ability to test for events is not available.
// *Action: Not normally visible to the user. For further details, turn
// on tracing and reexecute the operation and contact Oracle Customer
// Support.
/
/ 12630 - 12699 Reserved for NA errors.
/
12630, 00000, "Native service operation not supported"
// *Cause: An operation requested by a user is not supported by the native
// services component.
// *Action: This may be an internal error if the operation should have been
// supported.
/
12631, 00000, "Username retrieval failed"
// *Cause: The authentication service failed to retrieve the name of a user.
// *Action: Enable tracing to determine which routine is failing.
/
12632, 00000, "Role fetch failed"
// *Cause: The authentication service failed to retrieve one of the user's
// roles.
// *Action: Enable tracing to determine which routine is failing.
/
12633, 00000, "No shared authentication services"
// *Cause: The list of authentication services specified by the user does not
// match those supported by the process.
// *Action: Either specify another list or relink the executable with the
// desired services.
/
12634, 00000, "Memory allocation failed"
// *Cause: Process was unable to allocate memory.
// *Action: Terminate other processes in order to reclaim needed memory.
/
12635, 00000, "No authentication adapters available"
// *Cause: The executable was not linked with any authentication service
// adapters but the sqlnet.ora parameter that determines whether or
// not authentication is required was set to true.
// *Action: Either disable the parameter or relink the executable with service
// adapters.
/
12636, 00000, "Packet send failed"
// *Cause: A process was unable to send a packet to another process.
// Possible causes are:
// 1. The other process was terminated.
// 2. The machine on which the other process is running went down.
// 3. Some other communications error occurred.
// *Action: If the cause is not obvious, contact Oracle Customer Support.
/
12637, 00000, "Packet receive failed"
// *Cause: A process was unable to receive a packet from another process.
// Possible causes are:
// 1. The other process was terminated.
// 2. The machine on which the other process is running went down.
// 3. Some other communications error occurred.
// *Action: If the cause is not obvious, contact Oracle Customer Support.
/
12638, 00000, "Credential retrieval failed"
// *Cause: The authentication service failed to retrieve the credentials of a
// user.
// *Action: Enable tracing to determine the exact error.
/
12639, 00000, "Authentication service negotiation failed"
// *Cause: No match was found between the types of authentication services
// that the client supports and those that the server is using.
// *Action: Possible solutions:
// 1. Change the entry in sqlnet.ora that determines which services
// are to be used.
// 2. Relink the client with at least one of the authentication
// service adapters that the server supports.
// 3. Relink the server with at least one of the authentication
// service adapters that the client supports.
// 4. Disable authentication on both the client and server.
/
12640, 00000, "Authentication adapter initialization failed"
// *Cause: The function specified in the authentication table entry for the
// service failed.
// *Action: Enable tracing to determine the exact error.
/
12641, 00000, "Authentication service failed to initialize"
// *Cause: The authentication service failed during initialization.
// *Action: Enable tracing to determine the exact error.
/
12642, 00000, "No session key"
// *Cause: A process has no session key associated with it because the
// authentication service being used does not use one.
// *Action: If a session key is required, use another authentication service.
/
12643, 00000, "Client received internal error from server"
// *Cause: The client process received an error from the server that indicated
// that an internal Oracle Net native services error had occurred.
// *Action: Enable tracing on both processes and attempt to recreate the
// problem. If successful in recreating the problem, contact Oracle
// Customer Support.
/
12645, 00000, "Parameter does not exist."
// *Cause: A sqlnet.ora parameter from which a value was needed does not
// exist.
// *Action: Set the parameter in the parameter file.
/
12646, 00000, "Invalid value specified for boolean parameter"
// *Cause: The value specified for a parameter was set to a value other than
// true/false or on/off.
// *Action: Correct the value of the parameter.
/
12647, 00000, "Authentication required"
// *Cause: The parameter that controls whether authentication is required was
// set to true, but the executable does not have an
// authentication service linked in.
// *Action: Either re-link the executable with an authentication service
// adapter or disable the parameter.
/
12648, 00000, "Encryption or data integrity algorithm list empty"
// *Cause: A list-of-algorithms parameter was empty, e.g.
// "()".
// *Action: Change the list to contain the name of at least one
// installed algorithm, or remove the list entirely if every
// installed algorithm is acceptable.
/
12649, 00000, "Unknown encryption or data integrity algorithm"
// *Cause: A list-of-algorithms parameter included an
// algorithm name that was not recognized.
// *Action: Either remove that algorithm name, correct it if it was
// misspelled, or install the driver for the missing
// algorithm.
/
12650, 00000, "No common encryption or data integrity algorithm"
// *Cause: The client and server have no algorithm in common for
// either encryption or data integrity or both.
// *Action: Choose sets of algorithms that overlap. In other words,
// add one of the client's algorithm choices to the server's
// list or vice versa.
/
12651, 00000, "Encryption or data integrity algorithm unacceptable"
// *Cause: The algorithm the server chose to use for encryption or
// data integrity was not one of the choices acceptable to
// the client. This is either the result of an internal
// error, of a network data transmission error, or of
// deliberate tampering with the transmitted data.
// *Action: For further details, turn on tracing, re-execute the
// operation, and contact Oracle Customer Support.
/
12652, 00000, "String truncated"
// *Cause: Not enough memory was allocated for a string so it had to be
// truncated
// *Action: If it is OK that the string is truncated, then it is not an
// error. Otherwise, call the routine that reported the error
// again with a larger string buffer.
/
12653, 00000, "Authentication control function failed"
// *Cause: The control function utilized by the authentication service driver
// failed.
// *Action: Enable tracing to determine the exact error.
/
12654, 00000, "Authentication conversion failed"
// *Cause: The authentication service was unable to convert the credentials
// of a user from the format specific to the format into the
// ORACLE format.
// *Action: Enable tracing to determine the exact error.
/
12655, 00000, "Password check failed"
// *Cause: The authentication service being used was unable to verify the
// provided password.
// *Action: Enable tracing to determine the exact error.
/
12656, 00000, "Cryptographic checksum mismatch"
// *Cause: The cryptographic checksum received with a packet of
// incoming data didn't match the checksum computed by the
// receiving end. This indicates that the packet was
// tampered with or otherwise corrupted in transit.
// *Action: Look for sources of data corruption, perhaps including
// deliberate tampering.
/
12657, 00000, "No algorithms installed"
// *Cause: The near side of the connection required the use of a
// service (either encryption or checksumming) when no
// algorithms for that service were installed.
// *Action: Remove the "ON" requirement for that service.
/
12658, 00000, "ANO service required but TNS version is incompatible"
// *Cause: A client process that is running an earlier version of TNS
// attempted to connect but the connection failed because the server
// process required that an ANO service (authentication, encryption,
// etc.) be used.
// *Action: Relink the calling executable and retry the connection or eliminate
// the requirement that the service be used on the server side.
/
12659, 00000, "Error received from other process"
// *Cause: An error was received by one or more services from the process on
// the other side of the connection.
// *Action: Enable tracing to determine the exact error(s).
// The error(s) is (are) not returned directly because an error
// generated by a server may not make sense on the client side and
// vice-versa.
/
12660, 00000, "Encryption or crypto-checksumming parameters incompatible"
// *Cause: One side of the connection specified "REQUIRED" for encryption
// or crypto-checksumming, while the other side specified "REJECTED".
// *Action: Change the "REQUIRED" side to "REQUESTED" if the
// you want encryption or crypto-checksumming to be optional, or
// change the "REJECTED" side to "ACCEPTED" if you do not
// want the service to be optional.
/
12661, 00000, "Protocol authentication to be used"
// *Cause: The authentication service has determined
// that the Oracle Net transport protocol in use is to be utilized to
// authenticate a user's identity.
// *Action: This error is used solely to communicate information between the
// authentication service and the Oracle Net session layer and should not
// normally be visible.
// If the error is seen, contact Oracle Worldwide Support.
/
12662, 00000, "proxy ticket retrieval failed"
// *Cause: The authentication adapter used by Oracle Net failed to retrieve the
// credentials needed to authenticate a database link.
// *Action: Enable tracing to determine the exact error.
/
12663, 00000, "Services required by client not available on the server"
// *Cause: Service(s) that was (were) required by the client process were not
// available on the server process.
// *Action: Configure the server with the services required by the client (best
// solution) or delete the requirement from the configuration
// file of the client (least secure).
/
12664, 00000, "Services required by server not available on the client"
// *Cause: Service(s) that was (were) required by the server process were not
// available on the client process.
// *Action: Configure the client with the services required by the server (best
// solution) or delete the requirement from the configuration
// file of the server (least secure).
/
12665, 00000, "NLS string open failed"
// *Cause: A native service was unable to make a string available for use by
// the National Language Support component.
// *Action: Make sure the National Language Support component has been
// properly. If it has, enable tracing and report the problem
// to Customer Support.
/
12666, 00000, "Dedicated server: outbound transport protocol different from inbound"
// *Cause: The protocol specified for an externally-identified outbound
// connection from a dedicated server (database link) was not the same
// as that used for the inbound connection. It is not possible for
// Oracle Net to authenticate a proxy connection that uses a protocol
// that is different from that which was used for the connection to
// the dedicated server.
// *Action: Specify the same protocol in the Oracle Net connect descriptor
// for the outbound connection as that used for the inbound
// connection.
/
12667, 00000, "Shared server: outbound transport protocol different from inbound"
// *Cause: The protocol specified for an externally-identified outbound
// connection from a shared server (database link) was not the same as
// as that used for the inbound connection. It is not possible for
// Oracle Net to authenticate a proxy connection that uses a protocol
// that is different from that which was used for the connection to
// the shared server.
// *Action: Specify the same protocol in the Oracle Net connect descriptor
// for the outbound connection as that used for the inbound
// connection
/
12668, 00000, "Dedicated server: outbound protocol does not support proxies"
// *Cause: The protocol specified to perform an externally-identified proxy
// connection (database link) from a dedicated server does
// not support proxy connections.
// *Action: Specify a protocol in the Oracle Net connect descriptor used for
// the connection that does support externally-authenticated proxy
// connections.
// NOTE: Because of a limitation in Oracle Net, the protocol used for
// the proxy connection must the same as that used for the
// connection from the client to the server.
/
12669, 00000, "Shared server: outbound protocol does not support proxies"
// *Cause: The protocol specified to perform an externally-identified proxy
// connection (database link) from a shared server does not support
// proxy connections.
// *Action: Specify a protocol in the Oracle Net connect descriptor used for
// the connection that does support externally-authenticated proxy
// connections.
// NOTE: Because of a limitation in Oracle Net, the protocol used for
// the proxy connection must the same as that used for the
// connection from the client to the server.
/
12670, 00000, "Incorrect role password"
// *Cause: A password supplied for a role could not be validated by the
// authentication service.
// *Action: Supply the correct password.
/
12671, 00000, "Shared server: adapter failed to save context"
// *Cause: The adapter for the authentication service failed when it tried to
// save the data needed for proxy connections (database
// links) through the shared server.
// *Action: Enable tracing to determine the exact error. Contact Oracle
// Customer Support if the reason is not obvious.
/
12672, 00000, "Database logon failure"
// *Cause: The authentication service adapter in use encountered an error
// it attempted to validate the logon attempt of a user.
// *Action: Enable tracing to determine the exact error encountered by the
// adapter.
/
12673, 00000, "Dedicated server: context not saved"
// *Cause: A connection was marked as being a proxy connection (database link)
// from a dedicated server but no inbound context was present.
// *Action: This error should not normally be visible to the user. Contact
// Oracle Customer Support.
/
12674, 00000, "Shared server: proxy context not saved"
// *Cause: A connection was marked as being a proxy connection (database link)
// from a shared server but no inbound context was present.
// *Action: This error should not normally be visible to the user. Contact
// Oracle Customer Support.
/
12675, 00000, "External user name not available yet"
// *Cause: The authentication service in use was not able to return the
// external name of a user of the ORACLE server because it is not
// available to the service yet.
// *Action: This is just an informational message and should not normally be
// visible to the user. If the error does appear, contact Oracle
// Customer Support.
/
12676, 00000, "Server received internal error from client"
// *Cause: The server process received an error from the client which
// indicated that an internal Oracle Net native services error had
// occurred.
// *Action: Enable tracing on both processes and attempt to recreate the
// problem. If the problem recurs, contact Oracle Customer
// Support.
/
12677, 00000, "Authentication service not supported by database link"
// *Cause: The authentication service used by the proxy process (database
// link) was unable to find the adapter being used by the client
// in its list of authentication mechanisms.
// *Action: Specify an authentication adapter that is shared by the client and
// the server being used for the database link.
/
12678, 00000, "Authentication disabled but required"
// *Cause: The configuration parameters that control whether
// authentication is disabled or required were both set to TRUE.
// *Action: Set one or both of the parameters to FALSE.
/
12679, 00000, "Native services disabled by other process but required"
// *Cause: The remote process has disabled native services but the local
// process requires them.
// *Action: Enable native services on the remote process or disable them
// locally.
/
12680, 00000, "Native services disabled but required"
// *Cause: The process has disabled native services but at least one service
// is required.
// *Action: Enable native services or change the configuration file so that
// none of the available services are required.
/
12681, 00000, "Login failed: the SecurID card does not have a pincode yet"
// *Cause: The SecurID card that is used to logon to Oracle, does not have
// a pincode assigned to it.
// *Action: Use one of the programs supplied by Security Dynamics to assign
// a pincode to the card.
/
12682, 00000, "Login failed: the SecurID card is in next PRN mode"
// *Cause: The SecurID card and the SecurID server are out of sync and the
// server requires the next cardcode to resynchronize the card.
// *Action: Use one of the programs supplied by Security Dynamics to
// resynchronize the SecurID card.
/
12683, 00000, "encryption/crypto-checksumming: no Diffie-Hellman seed"
// *Cause: The "sqlnet.crypto_seed" parameter is missing from the
// SQLNET.ORA parameters file.
// *Action: Add this line to SQLNET.ORA:
// sqlnet.crypto_seed = "randomly-chosen text"
/
12684, 00000, "encryption/crypto-checksumming: Diffie-Hellman seed too small"
// *Cause: The "sqlnet.crypto_seed" parameter in the SQLNET.ORA
// parameter file is too small.
// *Action: Add more randomly-chosen text to it, perhaps using Network
// Manager.
/
12685, 00000, "Native service required remotely but disabled locally"
// *Cause: A native service is required by the remote process but native
// services have been disabled locally.
// *Action: Enable native services locally or change the configuration
// parameters on the remote host so that no native services are
// required.
/
12686, 00000, "Invalid command specified for a service"
// *Cause: An operation which does not exist was specified for a native
// service.
// *Action: This is a programming error and should not normally be visible to
// the user. If the error does appear, contact Oracle Customer
// Support.
/
12687, 00000, "Credentials expired."
// *Cause: The credentials that are used to authenticate the user for the
// requested connection have expired.
// *Action: Renew your credentials. Refer to the documentation specific for
// your Network Authentication Adapter on how to do this.
/
12688, 00000, "Login failed: the SecurID server rejected the new pincode"
// *Cause: There are a number of reasons why the SecurID server would refuse
// a pincode:
// - The user might not have permission to make up his own pincode.
// - The pincode was either too short or too long. Valid pincodes
// consist of minimal four, but no more than eight characters.
// - The pincode contains any non alphanumeric characters.
// *Action: Reexecute the operation and make sure to use a pincode that
// satisfies the above requirements. If the problem persists, turn
// on tracing at the Oracle Server side of the connection and
// examine the trace file for the exact error.
/
12689, 00000, "Server Authentication required, but not supported"
// *Cause: Server Authentication is required for this connection, but not
// supported by both sides of the connection.
// *Action: Make sure both sides of the connection have the correct version of
// Advanced Networking Option, and that the Authentication Adapter
// supports Server Authentication.
/
12690, 00000, "Server Authentication failed, login cancelled"
// *Cause: Server Authentication is required, but the server's credentials
// were found invalid by the client.
// *Action: Make sure that the server has a valid set of credentials. Refer to
// your authentication adapter specific documentation on how to do
// this.
/
12691, 00000, "TTC RPC (%s) not supported by Oracle Connection Manager in Traffic Director mode"
// *Cause: Oracle Connection Manager in Traffic Director mode
// does not support the specified Two-Task Common (TTC) Remote
// Procedure Call(RPC).
// *Action: Do not use functionality that issues the specified TTC RPC which
// was disallowed by Oracle Connection Manager in Traffic Director mode
//
/
12692, 00000, "functionality (%s) not supported by Oracle Connection Manager in Traffic Director mode"
// *Cause: Oracle Connection Manager in Traffic Director mode
// does not support the specified functionality.
// *Action: Do not use functionality that is not supported by Oracle Connection // Manager in Traffic Director mode.
//
/
12693, 00000, "PRCP is not configured in Oracle Connection Manager in Traffic Director mode"
// *Cause: The client was attempting to connect using Proxy Resident
// Connection Pool (PRCP) while PRCP is not configured in Oracle
// Connection Manager in Traffic Director mode.
// *Action: The client should use PRCP connections only when PRCP is
// configured in Oracle Connection Manager in Traffic Director mode.
//
/
12694, 00000, "non-PRCP connection requested when PRCP is configured in Oracle Connection Manager in Traffic Director mode"
// *Cause: The client was attempting a non Proxy Resident Connection Pool
// (PRCP) connection while PRCP was configured in Oracle
// Connection Manager in Traffic Director mode.
// *Action: The client should only use PRCP connections when PRCP is configured
// in Oracle Connection Manager in Traffic Director mode.
/
12695, 00000, "This statement cannot be executed with Oracle Connection Manager in Traffic Director mode with PRCP enabled"
// *Cause: The client did not send enough information to execute the statement
// with Oracle Connection Manager in Traffic Director mode
// with Proxy Resident Connection Pooling (PRCP) enabled.
// *Action: This client needs a patch that will fix the issue. Alternatively,
// it needs to be upgraded to Oracle Database Release 18.1 or later.
// Contact Oracle Customer Support for the patch.
/
12696, 00000, "Double Encryption Turned On, login disallowed"
// *Cause: The user is using a Secure Protocol Adapter that has Encryption
// turned ON as well as ANO Encryption.
// *Action: Turn OFF either ANO Encryption or the Protocol Adapter Encryption
// if possible. Refer to the Administrator's
// Guide on how to do this.
/
12699, 00000, "Native service internal error"
// *Cause: An internal error occurred in the native services component.
// *Action: Enable tracing to determine the exact error. Contact Oracle
// Customer Support.
/
/
/ This line is an OSN Magic Cookie. Don't eat it.
/ All new error messages up to 12699 ___MUST___ be placed in this file
/ above and before and preceding the preceding Magic Cookie line.
/
/ This line is an OSN Magic Cookie. Don't eat it. Last NS error in 2.0.9.
/
/
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
/
/ 12700 - 12999: Reserved.
/
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
/
/ 12700 - 12750 Reserved for NLS
/
12700, 00000, "invalid NLS parameter value (%s)"
// *Cause: An invalid or unknown NLS configuration parameter was specified.
// *Action:
12701, 00000, "CREATE DATABASE character set is not known"
// *Cause: The character set specified when creating the database is unknown.
// *Action:
12702, 00000, "invalid NLS parameter string used in SQL function"
// *Cause: An unknown parameter name or invalid value is specified in a NLS
// parameter string.
// *Action:
12703, 00000, "this character set conversion is not supported"
// *Cause: The requested conversion between two character sets in the CONVERT
// function is not implemented
// *Action:
12704, 00000, "character set mismatch"
// *Cause: One of the following:
// - The string operands(other than an nlsparams argument) to an
// operator or built-in function do not have the same character
// set.
// - An nlsparams operand is not in the database character set.
// - String data with character set other than the database character
// set is passed to a built-in function not expecting it.
// - The second argument to CHR() or CSCONVERT() is not CHAR_CS or
// NCHAR_CS.
// - A string expression in the VALUES clause of an INSERT statement,
// or the SET clause of an UPDATE statement, does not have the
// same character set as the column into which the value would
// be inserted.
// - A value provided in a DEFAULT clause when creating a table does
// not have the same character set as declared for the column.
// - An argument to a PL/SQL function does not conform to the
// character set requirements of the corresponding parameter.
// *Action:
12705, 00000, "Cannot access NLS data files or invalid environment specified"
// *Cause: Either an attempt was made to issue an ALTER SESSION command
// with an invalid NLS parameter or value; or the environment
// variable(s) NLS_LANG, ORA_NLSxx, or ORACLE_HOME was incorrectly
// specified, therefore the NLS data files cannot be located.
// *Action: Check the syntax of the ALTER SESSION command and the NLS
// parameter, correct the syntax and retry the statement, or
// specify the correct directory path/values in the environment
// variables.
12706, 00000, "this CREATE DATABASE character set is not allowed"
// *Cause: It is not allowed to create a database on a native ASCII-based
// machine using an EBCDIC-based character set, and vice versa.
// *Action:
12707, 00000, "error while getting create database NLS parameter %s"
// *Cause: Internal error
// *Action:
12708, 00000, "error while loading create database NLS parameter %s"
// *Cause: Internal error
// *Action:
12709, 00000, "error while loading create database character set"
// *Cause: Internal error
// *Action:
12710, 00000, "CREATE CONTROLFILE character set is not known"
// *Cause: The character set specified when creating the control file is unknown.
// *Action:
12711, 00000, "this CREATE CONTROLFILE character set is not allowed"
// *Cause: It is not allowed to create a control file on a native ASCII-based
// machine using an EBCDIC-based character set, and vice versa.
12712, 00000, "new character set must be a superset of old character set"
// *Cause: When you ALTER DATABASE ... CHARACTER SET, the new
// character set must be a superset of the old character set.
// For example, WE8ISO8859P1 is not a superset of the WE8DEC.
// *Action: Specify a superset character set.
12713, 00000, "Character data loss in NCHAR/CHAR conversion"
// *Cause: When character set conversion happened between CHAR and NCHAR
// either implicitly or explicitly, some characters were lost
// due to no mapping characters in the destination character set.
// *Action: Ensure that all the characters can be mapped to characters in the
// destination character set or set NLS_NCHAR_CONV_EXCP to be FALSE.
12714, 00000, "invalid national character set specified"
// *Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national
// character set
// *Action: Ensure that the specified national character set is valid
12715, 00000, "invalid character set specified"
// *Cause: The character set specified is not allowed for this operation
// or is invalid
// *Action: Ensure that the specified character set is valid
12716, 00000, "Cannot ALTER DATABASE CHARACTER SET when CLOB data exists"
// *Cause: CLOB data changes representation to Unicode when converting to a
// multibyte character set and must be migrated
// *Action: Remove CLOB data as listed in the alert file. CLOB data can be migrated
// by methods such as import/export
12717, 00000, "Cannot issue ALTER DATABASE NATIONAL CHARACTER SET when NCLOB, NCHAR or NVARCHAR2 data exists"
// *Cause: NCLOB, NCHAR or NVARCHAR2 data changed the representation to Unicode
// when converting to a multibyte character set and must be migrated.
// *Action: Remove NCLOB, NCHAR or NVARCHAR2 data as listed in the alert file.
// The above type data can be migrated by methods such as import/export.
12718, 00000, "operation requires connection as SYS"
// *Cause: This command can only be run when connecting as SYS
// *Action: Connect as SYS to run this command
12719, 00000, "operation requires database is in RESTRICTED mode"
// *Cause: This command can only be run when the database is in RESTRICTED mode
// *Action: Ensure that the system is in RESTRICTED mode
12720, 00000, "operation requires database is in EXCLUSIVE mode"
// *Cause: This command can only be run when the database is in EXCLUSIVE mode
// *Action: Ensure that the system is in EXCLUSIVE mode
12721, 00000, "operation cannot execute when other sessions are active"
// *Cause: This command can only be run when there are no other sessions active
// *Action: Ensure there are no other connections to the database
12722, 00000, "regular expression internal error"
// *Cause: A regular expression internal error occurred.
// *Action: This is an internal error. Contact Oracle Support Services.
12723, 00000, "regular expression too complex"
// *Cause: The regular expression was too complex and could not be parsed.
// *Action: This is an internal error. Contact Oracle Support Services.
12724, 00000, "regular expression corrupt"
// *Cause: The regular expression contained an incorrect sequence of metacharacters.
// *Action: Ensure the metacharacters are correctly positioned.
12725, 00000, "unmatched parentheses in regular expression"
// *Cause: The regular expression did not have balanced parentheses.
// *Action: Ensure the parentheses are correctly balanced.
12726, 00000, "unmatched bracket in regular expression"
// *Cause: The regular expression did not have balanced brackets.
// *Action: Ensure the brackets are correctly balanced.
12727, 00000, "invalid back reference in regular expression"
// *Cause: A back references was found before a sub-expression.
// *Action: Ensure a valid sub-expression is being referenced.
12728, 00000, "invalid range in regular expression"
// *Cause: An invalid range was found in the regular expression.
// *Action: Ensure a valid range is being used.
12729, 00000, "invalid character class in regular expression"
// *Cause: An unknown character class was found in the regular expression.
// *Action: Ensure a valid characters class is being used.
12730, 00000, "invalid equivalence class in regular expression"
// *Cause: An unknown equivalence class was found in the regular expression.
// *Action: Ensure a valid equivalence class is being used.
12731, 00000, "invalid collation class in regular expression"
// *Cause: An unknown collation class was found in the regular expression.
// *Action: Ensure a valid collation class is being used.
12732, 00000, "invalid interval value in regular expression"
// *Cause: An invalid interval value was found in the regular expression.
// *Action: Ensure a valid interval value is being used.
12733, 00000, "regular expression too long"
// *Cause: The operation failed because the regular expression it used exceeds
// the maximum supported size.
// *Action: Use a shorter regular expression.
12734,00000,"Instant Client Light: unsupported client national character set %s"
// *Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national
// character set. Instant Client Light has only minimal character sets.
// *Action: Do not use Instant Client Light for this character set
12735, 00000, "Instant Client Light: unsupported client character set %s"
// *Cause: The character set specified is not allowed for this operation
// or is invalid. Instant Client Light has only minimal character sets.
// *Action: Do not use Instant Client Light for this character set
12736,00000,"Instant Client Light: unsupported server national character set %s"
// *Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national
// character set. Instant Client Light has only minimal character sets.
// *Action: Do not use Instant Client Light for this character set
12737, 00000, "Instant Client Light: unsupported server character set %s"
// *Cause: The character set specified is not allowed for this operation
// or is invalid. Instant Client Light has only minimal character sets.
// *Action: Do not use Instant Client Light for this character set
12738,00000,"Express Instant Client: unsupported client national character set %s"
// *Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national
// character set. Instant Client has only minimal character sets.
// *Action: Do not use Express Instant Client for this character set
12739, 00000, "Express Instant Client: unsupported client character set %s"
// *Cause: The character set specified is not allowed for this operation
// or is invalid. Express Instant Client has only minimal character
// sets.
// *Action: Do not use Express Instant Client for this character set
12740,00000,"Express Instant Client: unsupported server national character set %s"
// *Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national
// character set. Instant Client has only minimal character sets.
// *Action: Do not use Express Instant Client for this character set
12741, 00000, "Express Instant Client: unsupported server character set %s"
// *Cause: The character set specified is not allowed for this operation
// or is invalid. Express Instant Client has only minimal character
// sets.
// *Action: Do not use Express Instant Light for this character set
12742, 00000, "unable to create the collation key"
// *Cause: The character argument of a collation-sensitive operator was too long
// or it had too many decomposable characters to create a collation key
// for it in the available buffer space.
// *Action: Shorten the argument value or, if using a UCA-based collation,
// increase the ratio of characters with short or no Unicode
// decomposition to characters with long Unicode decomposition
// in the value.
12743, 00000, "internal LX error code, arguments: [%s], [%s], [%s]"
// *Cause: This is an internal error in a globalization support function.
// *Action: Contact Oracle Support Services.
/
12744, 00000, "Character set %s is not allowed as a database character set."
// *Cause: An attempt was made to create or alter a database using a client-only
// or conversion-only character set.
// *Action: Specify a supported database character set.
12745,00000, "KLCS debug event"
// *Document: NO
// *Cause:
// *Action: Set to trace activities related to the Kernel Loadable Character Set.
// See trace file for more details.
/
12746, 00000, "unrecognized collation name \"%s\""
// *Cause: The name of the collation that you specified was not recognized by
// the Oracle Database, because the name was misspelled, or the
// collation was user-defined but not installed in the Oracle Home
// of the database instance, or because the directory specified in
// the ORA_NLS10 environment setting, either explicitly or defaulting
// to $ORACLE_HOME/nls/data (%ORACLE_HOME%\nls\data on Microsoft
// Windows), did not contain valid NLS data files.
// *Action: Specify a valid collation name or fix your database software
// configuration.
/
12747, 00000, "unrecognized collation ID (%s)"
// *Cause: The ID of the collation that you specified was not recognized by
// the Oracle Database, because it was incorrect, or the collation was
// user-defined but not installed in the Oracle Home of the database
// instance, or because the directory specified in the ORA_NLS10
// environment setting, either explicitly or defaulting to
// $ORACLE_HOME/nls/data(%ORACLE_HOME%\nls\data on Microsoft Windows),
// did not contain valid NLS data files.
// *Action: Specify a valid collation ID or fix your database software
// configuration.
/
/=============================================================================
/ 12751 - 12799 reserved for VOS
/
/ 12760-12780 reserved for ACMS infrastructure
/
/=============================================================================
12751, 00000, "cpu time or run time policy violation"
// *Document: NO
// *Cause: A piece of code ran longer than it is supposed to
// *Action: If this error persists, contact Oracle Support Services.
/
12752, 00000, "An instance-critical process has terminated."
// *Cause: An unexpected error was encountered by an instance-critical process.
// *Action: Contact Oracle Support Services.
/
12753,00000, "The Oracle home user ID does not match the effective user ID of the local client which connected to the Oracle instance."
// *Document: YES
// *Cause: The user ID that is the owner of the Oracle home directory was not
// the same as the effective user ID of the local client that connected
// to the Oracle instance.
// *Action: Run the local client that connects to Oracle instance with the same
// user ID as the owner of the Oracle home.
/
12754, 00000, "Feature %s is disabled due to missing capability %s."
// *Document: NO
// *Cause: This feature requires specific capabilities that were not present
// in the current database instance.
// *Action: Contact Oracle Support Services to enable this feature.
/
12755, 00000, "Feature %s is disabled due to unsupported capability."
// *Document: NO
// *Cause: This feature requires specific capabilities that were not supported
// in the current database instance.
// *Action: Contact Oracle Support Services to enable this feature.
/
12760,00000, "ACMS tracing event"
// *Document: NO
// *Cause:
// *Action:
/
12761,00000, "ACMS debug event"
// *Document: NO
// *Cause:
// *Action:
/
12762,00000, "ACMS service status is unknown"
// *Document: NO
// *Cause: This is an internal status.
// *Action: None.
/
12763,00000, "ACMS service is disabled"
// *Document: NO
// *Cause: The ACMS service failed to initialize because of either variances
// in the Oracle binaries or internal error.
// *Action: Ensure all instances are using the same Oracle binary, and restart
// all instances.
/
12764,00000, "ACMS service encountered inconsistent state"
// *Document: NO
// *Cause: An internal error occured.
// *Action: Ensure all instances are using the same Oracle binary, and restart
// all instances.
/
12765,00000, "ACMS operation is pending cleanup"
// *Document: NO
// *Cause: An attempt of the same operation previously failed and has yet
// to be cleaned up by PMON.
// *Action: Wait and retry the operation.
/
12766,00000, "ACMS failed to acquire share-mode mount lock"
// *Document: NO
// *Cause: An operation was not permitted because the mount lock could
// not be acquired.
// *Action: Retry the operation.
/
12767,00000, "ACMS memory allocation failure"
// *Document: NO
// *Cause: An operation was interrupted because an ACMS background
// failed to allocate the needed SGA to stage an operation.
// *Action: Ensure the instance has sufficient memory resources.
/
12768,00000, "ACMS maximum message size exceeded"
// *Document: NO
// *Cause: An operation failed to start because the requested client data
// exceeded the maximum supported size.
// *Action: Reduce the size of the data.
/
12769,00000, "ACMS message delivery or receipt failure"
// *Document: NO
// *Cause: An operation was interrupted because a failure occured during
// message delivery or reply processing.
// *Action: This is expected if instances are leaving the cluster. Retry
// the operation.
/
12770,00000, "ACMS operation failure with error context"
// *Document: NO
// *Cause: An operation was interrupted because a failure occured at one
// or more sites.
// *Action: If supplied, check the status buffer for per-instance error
// context.
/
12771,00000, "ACMS encountered client callback exception"
// *Document: NO
// *Cause: The ACMS server encountered an exception while performing the
// client callback operation.
// *Action: If supplied, check the status buffer for the exception.
/
12772,00000, "ACMS encountered client callback failure status"
// *Document: NO
// *Cause: The ACMS server encountered a failure status from the client
// callback operation.
// *Action: If supplied, check the status buffer for the return value.
/
12773,00000, "ACMS not enabled due to instance not being mounted"
// *Document: NO
// *Cause: The ACMS server could not execute due to the instance not
// being mounted.
// *Action: If supplied, check the status buffer to identify the
// instance which experienced the error.
/
12774,00000, "error entering CDB sandbox %s: %s"
// *Document: YES
// *Cause: An attempt to enter the sandbox for a multitenant container database
// (CDB) failed.
// *Action: Check the definition of the sandbox for the CDB.
/
12775,00000, "error entering PDB sandbox %s: %s"
// *Document: YES
// *Cause: An attempt to enter the sandbox for a pluggable database (PDB)
// failed.
// *Action: Check the definition of the sandbox for the PDB.
/
12776,00000, "error exiting PDB sandbox %s: %s"
// *Document: YES
// *Cause: An attempt to exit the sandbox for a pluggable database (PDB)
// failed.
// *Action: Resolve the problem indicated by the particular error.
/
/
12777,00000, "A non-continuable error encountered. Check the error stack for additional information [%s], [%s], [%s], [%s]."
// *Cause: The error recorded before this error should not be cleared and
// should be re-signaled to the top-level error handler.
// *Action: See the previously recorded error. Contact DBA.
/
12778,00000, "path mismatch for %s expected '%s' but found '%s'"
// *Cause: The path recorded in the SGA did not match the current value.
// *Action: Clear the SGA by shutting down the instance and then restart.
/
12779,00000, "KGH testing event"
// *Document: NO
// *Cause: If heap checking finds corruption during testing, then this error
// message appears instead of an internal error.
// *Action: Internal event.
/
/ 12800 - 12893 Reserved for Parallel Query/Index Creation
/
/
12800, 00000, "system appears too busy for parallel query execution"
// *Cause: load on system is too high to perform parallel queries.
// *Action: re-execute serially or wait until system load is reduced.
/
12801, 00000, "error signaled in parallel query server %s"
// *Cause: A parallel query server reached an exception condition.
// *Action: Check the following error message for the cause, and consult
// your error manual for the appropriate action.
// *Comment: This error can be turned off with event 10397, in which
// case the server's actual error is signaled instead.
/
12802, 00000, "parallel query server lost contact with coordinator"
// *Cause: A parallel query server lost contact with the foreground
// (coordinator) process/thread.
// *Action: Check your system for anomalies and reissue the statement.
// If this error persists, contact Oracle Support Services.
/
12803, 00000, "parallel query server lost contact with another server"
// *Cause: A parallel query server lost contact with another server.
// *Action: Check your system for anomalies and reissue the statement.
// If this error persists, contact Oracle Support Services.
/
12804, 00000, "parallel query server appears to have died"
// *Cause: Cannot find process information for a parallel query
// server thread.
// *Action: Check your system for anomalies and reissue the statement.
// If this error persists, contact Oracle Support Services.
/
12805, 00000, "parallel query server died unexpectedly"
// *Cause: A parallel query server died unexpectedly, PMON cleaning
// up the process.
// *Action: Check your system for anomalies and reissue the statement.
// If this error persists, contact Oracle Support Services.
// See trace file for more details.
/
12806, 00000, "could not get background process to hold enqueue"
// *Cause: Internal error.
// *Action: This error should not normally occur. If it persists,
// contact Oracle Support Services.
/
12807, 00000, "process queue could not receive parallel query message"
// *Cause: Internal error.
// *Action: This error should not normally occur. If it persists,
// contact Oracle Support Services.
/
12808, 00000, "cannot set %s_INSTANCES greater than number of instances %s"
// *Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES
// using the ALTER SYSTEM command to a value larger than the number
// of available instances.
// *Action: See the accompanying message for the current allowable
// maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES
// to ALL.
/
12809, 00000, "cannot set %s_INSTANCES when mounted in exclusive mode"
// *Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES
// using the ALTER SYSTEM command while the database was mounted
// in exclusive mode.
// *Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless
// running Oracle Real Application Clusters mounted in
// CLUSTER_DATABASE mode.
/
12810, 00000, "PARALLEL_MAX_SERVERS must be less than or equal to %s"
// *Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter
// to a value higher than the maximum allowed by the system.
// *Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to
// the maximum specified in the accompanying message and retry.
/
12811, 00000, "PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, %s"
// *Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter
// to a value higher than PARALLEL_MAX_SERVERS.
// *Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to
// PARALLEL_MAX_SERVERS (indicated in the accompanying message)
// and retry.
/
12812, 00000, "only one PARALLEL or NOPARALLEL clause may be specified"
// *Cause: PARALLEL was specified more than once, NOPARALLEL was specified
// more than once, or both PARALLEL and NOPARALLEL were specified
// in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or
// CLUSTER statement, or in a RECOVER command.
// *Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and
// reissue the statement.
/
12813, 00000, "value for PARALLEL or DEGREE must be greater than 0"
// *Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE,
// CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement.
// *Action: Specify a degree of parallelism greater than 0 or specify
// default parallelism using PARALLEL with no degree or using
// DEGREE DEFAULT within a PARALLEL clause.
/
12814, 00000, "only one CACHE or NOCACHE clause may be specified"
// *Cause: CACHE was specified more than once, NOCACHE was specified more
// than once, or both CACHE and NOCACHE were specified in a
// CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER
// statement.
// *Action: Remove all but one of the CACHE or NOCACHE clauses and
// reissue the statement.
/
12815, 00000, "value for INSTANCES must be greater than 0"
// *Cause: PARALLEL parameter specifying number of instances must
// be a positive integer or DEFAULT
// *Action: specify a positive integer or DEFAULT for INSTANCES
// if parallelism across instances is desired.
/
12816, 00000, "parallel create index fastpath operation"
// *Cause:
// *Action: set this event only under the supervision Oracle development
// *Comment: this event permits fastpath index creation. it merges
// sub-index in a quick but suboptimal fashion wrto space usage.
// Level: the level indicates the number of rows in a branch block
// that we are willing to copy before attempting fastpath operation.
/
12817, 00000, "parallel query option must be enabled"
// *Cause: A parallel query option feature has been invoked but this option
// has not been enabled.
// *Action: Enable the parallel query option.
/
12818, 00000, "invalid option in PARALLEL clause"
// *Cause: an unrecognized option was used within a PARALLEL clause.
// *Action: specify any combination of DEGREE { <n> | DEFAULT } and
// INSTANCES { <n> | DEFAULT } within the PARALLEL clause.
/
12819, 00000, "missing options in PARALLEL clause"
// *Cause: PARALLEL clause cannot be empty.
// *Action: specify any combination of DEGREE { <n> | DEFAULT } and
// INSTANCES { <n> | DEFAULT } within the PARALLEL clause.
/
12820, 00000, "invalid value for DEGREE"
// *Cause: invalid value for DEGREE was specified within a PARALLEL
// clause.
// *Action: specify a positive integer or DEFAULT for the DEGREE
// option within a PARALLEL clause.
/
12821, 00000, "invalid value for INSTANCES"
// *Cause: invalid value for INSTANCES was specified within a PARALLEL
// clause.
// *Action: specify a positive integer or DEFAULT for the INSTANCES
// option within a PARALLEL clause.
/
12822, 00000, "duplicate option in PARALLEL clause"
// *Cause: DEGREE or INSTANCES was specified more than once within
// a PARALLEL clause.
// *Action: specify each desired PARALLEL clause option only once.
/
12823, 00000, "default degree of parallelism may not be specified here"
// *Cause: the PARALLEL keyword was used alone or DEGREE DEFAULT was
// specified in the PARALLEL clause of an ALTER DATABASE RECOVER
// command.
// *Action: respecify with an explicit degree of parallelism.
/
12824, 00000, "INSTANCES DEFAULT may not be specified here"
// *Cause: INSTANCES DEFAULT was specified in the PARALLEL clause
// of an ALTER DATABASE RECOVER command
// *Action: respecify with an explicit value for INSTANCES or omit
// the INSTANCES option if single instance recovery is desired.
/
12825, 00000, "explicit degree of parallelism must be specified here"
// *Cause: the DEGREE option was omitted from an ALTER DATABASE RECOVER
// command.
// *Action: respecify with an explicit degree of parallelism.
/
12826, 00000, "hung parallel query server was killed"
// *Cause: parallel query server was hung and subsequently killed.
// *Action: re-execute query and report suspicious events in trace
// file to Oracle Support Services if error persists.
/
12827, 00000, "insufficient parallel query slaves (requested %s, available %s, parallel_min_percent %s)"
// *Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than
// the minimum number of slaves were acquired
// *Action: Either reexecute the query with a lower PARALLEL_MIN_PERCENT or
// wait until some running queries are completed, thus freeing
// up slaves
/
12828, 00000, "Can't start parallel transaction at a remote site"
// *Cause: PDML transaction cannot be started because we are not in the
// coordinator site of the distributed transaction.
// *Action: Do not use PDML at remote sites.
/
12829, 00000, "Deadlock - itls occupied by siblings at block %s of file %s"
// *Cause: parallel statement failed because all itls in the current
// block are occupied by siblings of the same transaction.
// *Action: increase MAXTRANS of the block or reduce the degree of
// parallelism for the statement. Reexecute the statement.
// Report suspicious events in trace file to Oracle Support
// Services if error persists.
/
12830, 00000, "Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE"
// *Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a
// command other than COMMIT or ROLLBACK was issued.
// *Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
/
12831, 00000, "Must COMMIT or ROLLBACK after executing INSERT with APPEND hint"
// *Cause: After executing an INSERT statement with an APPEND hint, a
// command other than COMMIT or ROLLBACK was issued.
// *Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
/
12832, 00000, "Could not allocate slaves on all specified instances"
// *Cause: After executing a query on a global v$ fixed view, one or more
// instances failed to allocate a slave to process query
// *Action: To allow results to be returned by sucessfully allocated slaves,
// execute ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement,
// or check parameters of instances
/
12833, 00000, "Coordinator's instance not a member of parallel_instance_group"
// *Cause: The coordinator's instance must be a member of the
// parallel_instance_group in which this operation will be run.
// *Action: Either add the coordinator's instance to the current
// parallel_instance_group or change parallel_instance_group.
/
12834, 00000, "Instance group name, '%s', too long, must be less than %s characters"
// *Cause: The instance group name is too long.
// *Action: Either shorten the name or get rid of the instance group.
/
12835, 00000, "No instances are active in the GLOBAL_VIEW_ADMIN_GROUP"
// *Cause: There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP
// in order to execute a query on global views
// *Action: Change the value of GLOBAL_VIEW_ADMIN_GROUP
/
12836, 00000, "Control delayed index maintenance event"
// *Document: NO
// *Cause:
// *Action: Control whether a given index will use delayed maintenance.
/
12837, 00000, "Delayed index maintenance debugging event"
// *Document: NO
// *Cause:
// *Action: Control dumping of debugging information for dealyed maintenance
/
12838, 00000, "cannot read/modify an object after modifying it in parallel"
// *Cause: Within the same transaction, an attempt was made to add read or
// modification statements on a table after it had been modified in parallel
// or with direct load. This is not permitted.
// *Action: Rewrite the transaction, or break it up into two transactions:
// one containing the initial modification and the second containing the
// parallel modification operation.
/
12839, 00000, "cannot modify an object in parallel after modifying it"
// *Cause: Within the same transaction, an attempt was made to perform
// parallel modification operations on a table after it had been modified.
// This is not permitted.
// *Action: Rewrite the transaction or break it up into two transactions:
// one containing the parallel modification and the second containing the
// initial modification operation.
/
12840, 00000, "cannot access a remote table after parallel/insert direct load txn"
// *Cause: Within a transaction, an attempt was made to perform distributed
// access after a PDML or insert direct statement had been issued.
// *Action: Commit/rollback the PDML transaction first, and then perform
// the distributed access, or perform the distributed access before the
// first PDML statement in the transaction.
/
12841, 00000, "Cannot alter the session parallel DML state within a transaction"
// *Cause: Transaction in progress
// *Action: Commit or rollback transaction and then re-execute
/
12842, 00000, "Cursor invalidated during parallel execution"
// *Cause: The cursor was invalidated during the parse phase of deferred
// parallel processing, e.g. when set operands are parallelized.
// *Action: Depends on why the cursor was invalidated. Possible causes include
// DDL on a schema object and shared pool being flushed.
/
12843, 00000, "pdml lock not held properly on the table"
// *Cause: The coodinator crashed or released the lock on the partition which
// the slave is trying to aquire currently.
// *Action: Check if the coordinator or some of the other slaves died. Also check
// that the lock has not been corrupted. Issue the pdml again.
12844, 00000, "cluster reconfiguration in progress"
// *Cause: Internal error
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL ERROR.
12845, 00000, "failed to receive interinstance parallel execution message"
// *Cause: OS or interconnect problem receiving interinstance message
// *Action: Check OS specific diagnostics
/
12846, 00000, "turn on debug information for ADG instance recovery"
// *Document: NO
// *Cause: none
// *Action: turn on debug information for ADG instance recovery
12847, 00000, "retry parsing due to concurrent DDL operation"
// *Document: NO
// *Cause: Internal error
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL ERROR.
12850, 00000, "Could not allocate slaves on all specified instances: %s needed, %s allocated"
// *Cause: When executing a query on a gv$ fixed view, one or more
// instances failed to allocate a slave to process query.
// *Action:Check trace output for instances on which slaves failed to start.
// GV$ query can only proceed if slaves can be allocated on all
// instances.
/
12851, 00000, "PARALLEL_MAX_SERVERS must be greater than or equal to PARALLEL_MIN_SERVERS, %s"
// *Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter
// to a value less than PARALLEL_MIN_SERVERS.
// *Action: Set PARALLEL_MAX_SERVERS to a value greater than or equal to
// PARALLEL_MIN_SERVERS value specified in the accompanying message
// and retry.
/
12852, 00000, "PARALLEL_MIN_SERVERS must be less than PROCESSES minus the number of reserved processes, %s"
// *Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter
// to a value higher than PROCESSES minus the number of reserved processes.
// *Action: Set PARALLEL_MIN_SERVERS to a value less than
// PROCESSES minus the number of reserved processes specified in the
// accompanying message and retry.
/
12853, 00000, "insufficient memory for PX buffers: current %sK, max needed %sK"
// *Cause: Insufficient SGA memory for PX buffers
// *Action: Reconfigure sga to include at least (max - current) bytes of
// additional memory
/
12854, 00000, "Parallel query is not supported on temporary LOBs"
// *Cause: The parallel query statement produced a temporary LOB.
// *Action: Turn off parallelism for the query or underlying table
/
12855, 00000, "cannot run parallel or insert direct load in a loopback"
// *Cause: A loopback was created in the transaction before this operation.
// *Action: Do not use loopback when using pdml or insert direct load.
12856, 00000, "cannot run parallel query on a loopback connection"
// *Cause: A table or index in a parallel query is referenced via a loopback
// connection.
// *Action: Do not use loopback connection when running a query in parallel.
/ 12857 - 12893 unused (parallel query/index creation messages)
/
/ Not really! 12857 through 12871 is used dictionary code!!!!
/ 12874 - 12893 unused currently for PQ
/
12872, 00000, "First slave parse gave different plan"
// *Cause: First hard parse on slave given QC-supplied environment and
// parameters gave different plan from QC. Try again with outline.
// *Action: No external action. Internally used for outline-based reparse.
12874, 00000, "parallel execution monitor terminated with error"
// *Cause: The parallel execution monitor process died.
// *Action: Wait for the process to restart.
12875, 00000, "PARALLEL_MAX_SERVERS cannot be set to 0 in CDB system"
// *Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter
// to 0 in the multitenant container database (CDB) system.
// *Action: Set the PARALLEL_MAX_SERVERS parameter to non-zero value to ensure
// CDB system performance.
/
/==========================================================================
/ 12894 - 12898 are reserved for asmcmd setsparseparent error messages.
/==========================================================================
12894, 00000, "source should be a sparse file"
// *Cause: The 'setsparseparent' command specified a source file that was
// not sparse.
// *Action: Use a sparse file as the source file.
/
12895, 00000, "destination should be sparse"
// *Cause: The 'setsparseparent' command specified a destination that was
// not backed by a sparse disk group.
// *Action: Use a destination backed by a sparse disk group.
/
12896, 00000, "child %s should be a sparse file"
// *Cause: The 'setsparseparent' command specified a child file that was
// not sparse.
// *Action: Use a sparse file as the child file.
/
12897, 00000, "failure to set parent to '%0!s' for a sparse file '%1!s'"
// *Cause: The 'setsparseparent' command was not successful.
// *Action: Examine the accompanying error messages for details.
/
12898, 00000, "failure to set parent for the destination file"
// *Cause: The parent information was not copied to the destination file.
// *Action: The 'setsparseparent' command can be used to set the parent.
/
/ 12899 - Stole this one for new "value too large" message
12899, 00000, "value too large for column %s (actual: %s, maximum: %s)"
// *Cause: An attempt was made to insert or update a column with a value
// which is too wide for the width of the destination column.
// The name of the column is given, along with the actual width
// of the value, and the maximum allowed width of the column.
// Note that widths are reported in characters if character length
// semantics are in effect for the column, otherwise widths are
// reported in bytes.
// *Action: Examine the SQL statement for correctness. Check source
// and destination column data types.
// Either make the destination column wider, or use a subset
// of the source column (i.e. use substring).
/============================================================================
/ 12900 - 12919 Reserved for execution errors introduced by
/ Default Temporary Tablespace
/============================================================================
12900, 00000, "must specify a default temporary tablespace for a locally managed database"
// *Cause: a locally managed database must have a temporary tablespace other
// than SYSTEM tablespace
// *Action: specify the default temporary tablespace when creating a locally
// managed database
12901, 00000, "default temporary tablespace must be of TEMPORARY type"
// *Cause: in a locally managed database, default temporary tablespace
// must be TEMPORARY type
// *Action:
12902, 00000, "default temporary tablespace must be SYSTEM or of TEMPORARY type"
// *Cause: in a dictionary managed database, default temporary tablespace
// must be SYSTEM or TEMPORARY type
// *Action:
12903, 00000, "default temporary tablespace must be an ONLINE tablespace"
// *Cause:
// *Action:
12904, 00000, "default temporary tablespace cannot be altered to PERMANENT type"
// *Cause:
// *Action:
12905, 00000, "default temporary tablespace cannot be brought OFFLINE"
// *Cause:
// *Action:
12906, 00000, "cannot drop default temporary tablespace"
// *Cause:
// *Action:
12907, 00000, "tablespace %s is already the default temporary tablespace"
// *Cause:
// *Action:
12908, 00000, "cannot specify SYSTEM as default temporary tablespace when creating database"
// *Cause:
// *Action:
12909, 00000, "TEMPORARY keyword expected"
// *Cause:
// *Action:
12910, 00000, "cannot specify temporary tablespace as default tablespace"
// *Cause: attempt to assign a temporary tablespace to be a user's
// default tablespace
// *Action: assign a permanent tablespace to be the default tablespace
12911, 00000, "permanent tablespace cannot be temporary tablespace"
// *Cause: attempt to assign a permanent tablespace to be a user's
// temporary tablespace
// *Action: assign a temporary tablespace to be user's temporary tablespace
12912, 00000, "Dictionary managed tablespace specified as temporary tablespace"
// *Cause: attempt to assign a dictionary managed tablespace to be a user's
// temporary tablespace
// *Action: Assign a locally managed temporary tablespace to be
// user's temporary tablespace
12913, 00000, "Cannot create dictionary managed tablespace"
// *Cause: Attemp to create dictionary managed tablespace in database
// which has system tablespace as locally managed
// *Action: Create a locally managed tablespace.
12914, 00000, "Cannot migrate tablespace to dictionary managed type"
// *Cause: Attemp to migrate locally managed tablespace to dictionary managed
// type when the database has locally managed system tablespace.
// *Action: Command cannot be issued.
12915, 00000, "Cannot alter dictionary managed tablespace to read write"
// *Cause: Attemp to alter dictionary managed tablespace to read write
// in database which has system tablespace as locally managed.
// This tablespace can only be dropped.
// *Action: Command cannot be issued.
12916, 00000, "cannot shrink permanent or dictionary managed tablespace"
// *Cause: An attempt was made to shrink a permanent tablespace or a
// dictionary managed tablespace.
// *Action: Check the tablespace type and issue the statement only on
// locally managed temporary tablespaces.
12917, 00000, "Invalid option specified for default permanent tablespace"
// *Cause:
// *Action:
12918, 00000, "Invalid tablespace type for default permanent tablespace"
// *Cause: The tablespace is either dropped, temporary or undo
// *Action: Check the tablespace type and reissue the statement
12919, 00000, "Can not drop the default permanent tablespace"
// *Cause: An attemp was made to drop the default permanent tablespace
// *Action: Make a different tablespace as the default permanent tablespace
// and reissue the drop
/
/ 12920 - 12939 reserved for database/tablespace force logging mode messages
/
12920, 00000, "database is already in force logging mode"
// *Cause: ALTER DATABASE FORCE LOGGING command failed because the database
// is already in force logging mode.
// *Action:
12921, 00000, "database is not in force logging mode"
// *Cause: ALTER DATABASE NO FORCE LOGGING command failed because the
// database is not in force logging mode.
// *Action:
12922, 00000, "concurrent ALTER DATABASE [NO] FORCE LOGGING command is running"
// *Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER
// DATABASE NO FORCE LOGGING command running in the system.
// *Action: Contact the database administrator who is responsible for the
// concurrent command.
12923, 00000, "tablespace %s is in force logging mode"
// *Cause: An attempt to alter the specified tablespace temporary failed
// because the tablespace is in force logging mode.
// *Action: Put the tablespace out of force logging mode by ALTER TABLESPACE
// NO FORCE LOGGING command.
12924, 00000, "tablespace %s is already in force logging mode"
// *Cause: An attempt to alter the specified tablespace into force logging
// mode failed because it is already in force logging mode.
// *Action:
12925, 00000, "tablespace %s is not in force logging mode"
// *Cause: An attempt to alter the specified tablespace out of force logging
// mode failed because it is not in force logging mode.
12926, 00000, "FORCE LOGGING option already specified"
// *Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified more
// than once.
// *Action: Remove all but one of the FORCE LOGGING options.
12927, 00000, "RETENTION option already specified"
// *Cause: In CREATE TABLESPACE, the RETENTION option was specified more
// than once.
// *Action: Remove all but one of the RETENTION options.
12928, 00000, "ENCRYPTION option already specified"
// *Cause: In CREATE TABLESPACE, the ENCRYPTION option was specified more
// than once.
// *Action: Remove all but one of the ENCRYPTION options.
12929, 00000, "turn on debug information for reading redo logs"
// *Document: NO
// *Cause: none
// *Action: turn on debug information for reading redo logs
/
/ 12930 - 12939 Reserved for 12c Nologging Standby Project.
/
12930, 00000, "turn on debug information for nologging standby"
// *Document: NO
// *Cause: None.
// *Action: None.
12931, 00000, "FORCE LOGGING or SET STANDBY NOLOGGING already specified"
// *Cause: FORCE LOGGING or SET STANDBY NOLOGGING options were specified
// more than once.
// *Action: Remove all but one of the FORCE LOGGING or SET STANDBY NOLOGGING
// options.
12932, 00000, "sending data for a nonlogged block fetch request failed"
// *Cause: A request from a remote database in the same Oracle Data Guard
// configuration to send data blocks to avoid or replace soft corrupt
// blocks due to nonlogged operations failed.
// This error is accompanied by additional errors that
// indicate the reason for the failure.
// *Action: Use any additional errors reported to identify and rectify the
// the underlying issue.
12933, 00000, "failed to connect while serving a nonlogged block fetch request"
// *Cause: A request from a remote database in the same Oracle Data Guard
// configuration to send data blocks to avoid or replace soft corrupt
// blocks due to nonlogged operations could not connect to the
// requesting database.
// This error is accompanied by additional errors that
// indicate the reason for the failure.
// *Action: Use any additional errors reported to identify and rectify the
// the underlying issue.
12934, 00000, "replace of nonlogged blocks in file %s failed"
// *Cause: The process performing replacement of nonlogged blocks failed to
// replace one or more blocks of the file indicated due to
// unexpected reasons such as a write failure reported by the
// operating system.
// *Action: Inspect any additional error messages and check the alert log for
// any messages related to Nonlogged Block Replacement (NBR).
12935, 00000, "operation [%s] to database (service '%s') failed (error %s)"
// *Cause: The process performing replacement of nonlogged blocks received
// an error when attempting to connect (CONNECT) or make a fetch
// request (REQUEST) against the database identified by the given
// service.
// The database was expected to act as a source of replacement blocks.
// *Action: Use the reported error to identify the issue or inspect any
// additional error messages and check the alert log for
// any messages related to Nonlogged Block Replacement (NBR).
12936, 00000, "timeout waiting for data blocks from database (service '%s')"
// *Cause: The process performing replacement of nonlogged blocks waited
// too long for a request sent to the remote database for a range
// of blocks to be completed.
// *Action: Check connectivity to the remote database or check the alert log
// at the remote database for problems reported by a transport task
// process (TTnn).
12937, 00000, "data blocks received for earlier recovery session (RCVID %s)"
// *Cause: A database received data blocks requested by a recovery session
// that has now terminated. This error signals to the sending database
// that no more transfer requests should be made for the same RCVID.
// *Action: None required.
12938, 00000, "out of memory for the data transfer cache"
// *Cause: A request to use space in the data transfer cache was rejected
// because there was no free space left in the cache and space
// could not be freed up.
// *Action: Ensure that automatic SGA tuning is enabled using either
// MEMORY_TARGET or SGA_TARGET system parameters or specify a
// larger size for the system parameter DATA_TRANSFER_CACHE_SIZE.
12939, 00000, "The Data Guard environment is incomplete."
// *Cause: A request to perform Nonlogged Block Replacement (NBR) recovery
// could not identify any other database in the Data Guard environment
// from which to request replacement blocks.
// *Action: Ensure there is a LOG_ARCHIVE_DEST_n parameter configured that
// identifies the primary or standby database from which requests for
// replacement blocks can be made.
/
/ 12940 - 12949 Reserved for server side DBVerify
/
12940, 00000, "Not enough space in DBVerify text buffer"
// *Cause: DBVerify ran out of text buffer. The error was trapped internally
// by the system. DBVerify would return the result in text buffer and
// then resume checking.
// *Action: None
12941, 00000, "DBVerify exception"
// *Cause: DBVerify encountered run-time error. The error signal was trapped
// internally by the system.
// *Action: None
12942, 00000, "database incarnation at source does not match"
// *Cause: A request to send data blocks to a recovery process failed because
// the source of the blocks is not on the same database incarnation as
// the site where the recovery is being performed.
// *Action: Use standard Oracle Data Guard procedures to synchronize the
// primary and standby databases. Standby media recovery automatically
// tries to resolve many of the remaining nonlogged blocks on the
// standby database. To resolve any remaining nonlogged blocks, use the
// RMAN RECOVER ... NONLOGGED BLOCK command.
/
/ 12950 - 12960 Reserved for Space Management
12950, 00000, "SYSTEM tablespace specified as default permanent tablespace"
// *Cause: SYSTEM tablespace was specified as the default permanent during
// database creation.
// *Action: If default permanent tablespace is not specified,then SYSTEM
// will implicitly become the default permanent tablespace.
// Specify an alternate tablespace or omit the default tablespace
// clause and reissue the CREATE DATABASE statement
12951, 00000, "Attempt to change default permanent tablespace to temporary"
// *Cause: It is incorrect to alter the default permanent tablespace
// of a database to temporary type
// *Action:
12952, 00000, "Control space growth in ASSM segment under concurrency"
// *Cause:
// *Action: Set this event only under the supervision of
// Oracle Support Services.
12953, 00000, "enable space scan optimization for clusters"
// *Cause:
// *Action: Set this event only under the supervision of
// Oracle Support Services.
12954, 00000, "The request exceeds the maximum allowed database size of 12 GB."
// *Cause: The 12 GB space limit of Oracle Database Express Edition was reached.
// *Action: Delete some files to create space or upgrade the database to the
// full edition.
/12961 - 12978 Reserved for read-only instances
12961, 00000, "cannot open database in read write mode on a read-only instance"
// *Cause: An attempt was made to open the database on a read-only instance
// under the following 2 cases:
// 1) User explicitly specified read write option in the SQL command.
// 2) User forgot to explicitly specify read-only in which case,
// read write mode was assumed by default.
// *Action: User should specify the open mode as read-only.
12962, 00000, "cannot create database on a read-only instance"
// *Cause: An attempt was made to create a database on a read-only instance.
// *Action: Create database should only be attempted from a read write instance.
12963, 00000, "A read-only instance cannot be the first instance to open a database."
// *Cause: A read-only instance was the first instance to try to open a database.
// *Action: A database must have been opened by at least one read write
// instance for a read-only instance to be able to open it.
12964, 00000, "All existing read write instances have closed the database."
// *Cause: The last read write instance holding the database open closed it.
// *Action: There has to be at least one read write instance holding the database
// open for a read-only instance to hold it open.
12965, 00000, "cannot mount an enabled thread on a read-only instance"
// *Cause: An attempt was made to mount an enabled redo thread obtained as a user
// specified parameter.
// *Action: The parameter value should be changed to the thread number of a
// disabled thread.
12966, 00000, "could not find a disabled redo thread to mount"
// *Cause: There were no available disabled redo threads which could be used to
// mount on the current read-only instance.
// *Action: N/A
12967, 00000, "read-only instance cannot mount a standby database"
// *Cause: An attempt was made to mount a standby database on a read-only
// instance.
// *Action: This action is not allowed.
12968, 00000, "delayed log flush should not be enabled in a read-only instance"
// *Cause: The system parameter for ping with no log force feature was set to true.
// *Action: The parameter should be set to false on a read-only instance.
12969, 00000, "invalid alter database option for read-only instance"
// *Cause: An attempt was made to execute a disallowed ALTER DATABASE statement
// on a read-only instance.
// *Action: Only OPEN, CLOSE and CREATE TEMPFILE options are allowed for ALTER
// DATABASE statement on a read-only instance.
12970, 00000, "cannot close PDB on all read/write instances while read-only instances exist"
// *Cause: An attempt was made to close a pluggable database (PDB) on the last
// read/write instance while a read-only instance was holding it open.
// *Action: A PDB should be closed on all of the read-only instances before it
// can be closed on the last read/write instance.
12979, 00000, "general event for SQL execution"
// *Document: NO
// *Cause: N/A
// *Action: This internal event is used to enable various actions
// associated with SQL execution. The event level is
// interpreted as a bitmap of actions to enable.
//
// *Comment: Not for general purpose use.
// LEVEL ACTION
// ----------------------------------------------------------------------------
// 0x0001 evastr() outputs "INVALID NUMBER" when there is an invalid number
// 0x0002 enable data-bound collation
/
/ 12980 - 12999 Reserved for Drop Column
/
12980, 00000, "checkpoint option not allowed with SET UNUSED"
// *Cause: An attempt was made to specify checkpoint option with SET UNUSED.
// *Action: Remove checkpoint option.
12981, 00000, "cannot drop column from an object type table"
// *Cause: An attempt was made to drop a column from an object type table.
// *Action: This action is not allowed.
12982, 00000, "cannot drop column from a nested table"
// *Cause: An attempt was made to drop a column from a nested table.
// *Action: This action is not allowed.
12983, 00000, "cannot drop all columns in a table"
// *Cause: An attempt was made to drop all columns in a table.
// *Action: Ensure that at least one column remains in the table after
// the drop column operation.
12984, 00000, "cannot drop partitioning column"
// *Cause: An attempt was made to drop a column used as the partitioning key.
// *Action: This action is not allowed.
12985, 00000, "tablespace '%s' is read only, cannot drop column"
// *Cause: An attempt was made to drop column from a partition/subpartition
// on a read only tablespace.
// *Action: Set the tablespace to read write and resubmit statement.
12986, 00000, "columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE"
// *Cause: An attempt was made to access a table with columns in partially
// dropped state (i.e., drop column operation was interrupted).
// *Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop
// column operation before accessing the table.
12987, 00000, "cannot combine drop column with other operations"
// *Cause: An attempt was made to combine drop column with other
// ALTER TABLE operations.
// *Action: Ensure that drop column is the sole operation specified in
// ALTER TABLE.
12988, 00000, "cannot drop column from table owned by SYS"
// *Cause: An attempt was made to drop a column from a system table.
// *Action: This action is not allowed
12989, 00000, "invalid value for checkpoint interval"
// *Cause: An invalid checkpoint interval specified in statement.
// Checkpoint interval must be between 0 and (2^31-1).
// *Action: Correct checkpoint interval and resubmit statement
12990, 00000, "duplicate option specified"
// *Cause: Duplicate option specified in statement.
// *Action: Remove the duplicate option and resubmit statement.
12991, 00000, "column is referenced in a multi-column constraint"
// *Cause: An attempt was made to drop a column referenced by some
// constraints.
// *Action: Drop all constraints referencing the dropped column or
// specify CASCADE CONSTRAINTS in statement.
12992, 00000, "cannot drop parent key column"
// *Cause: An attempt was made to drop a parent key column.
// *Action: Drop all constraints referencing the parent key column, or
// specify CASCADE CONSTRAINTS in statement.
12993, 00000, "tablespace '%s' is offline, cannot drop column"
// *Cause: An attempt was made to drop a column from a partition/subpartition
// on an offline tablespace.
// *Action: Bring the tablespace online and resubmit statement.
12994, 00000, "drop column option only allowed once in statement"
// *Cause: An attempt was made to repeat the drop column option in
// a single statement.
// *Action: Separate drop column options into different statements and
// resubmit statements.
12995, 00000, "no columns in partially dropped state"
// *Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement
// while there are no partially dropped columns.
// *Action: Cannot submit this statement.
12996, 00000, "cannot drop system-generated virtual column"
// *Cause: An attempt was made to drop a virtual column generated by
// the system.
12997, 00000, "cannot drop primary key column from an index-organized table"
// *Cause: An attempt was made to drop a primary key column from an index-
// organized table.
// *Action: This action is not allowed.
12998, 00000, "Ignore errors during drop column from atb.c"
// *Cause:
// *Action:
12999, 00000, "cannot DROP or SET UNUSED a column that has been set unused"
// *Cause: An attempt was made to DROP or SET UNUSED a column that has
// already been 'set unused'.
// *Action: Use the DROP UNUSED COLUMNS option to remove the column.
/
/ 13000 - 13499 (Reserved for Oracle Spatial)
/ 13000 - 13199 Spatial Data Option and Spatial Cartridge 8.0
/ 13200 - 13499 Spatial Cartridge 8.1.3
/ 13200 - 13249 Extensible spatial index
/ 13250 - 13259 SDO_Metadata Package
/ 13260 - 13279 Migration utility and package
/ 13280 - 13329 New spatial operators
/ 13330 - 13339 SDO_RELATE package
/ 13340 - 13359 Validate Geometry package
/ 13360 - 13499 Reserved for future use
/
13000, 00000, "dimension number is out of range"
// *Cause: The specified dimension was either smaller than 1 or greater than
// the number of dimensions encoded in the HHCODE.
// *Action: Ensure that the dimension number is between 1 and the maximum
// number of dimensions encoded in the HHCODE.
/
13001, 00000, "dimensions mismatch error"
// *Cause: The number of dimensions in two HHCODEs involved in a binary
// HHCODE operation did not match.
// *Action: Ensure that the number of dimensions in the HHCODEs match.
/
13002, 00000, "specified level is out of range"
// *Cause: The specified level is either smaller than 1 or greater
// than the maximum level encoded in an HHCODE.
// *Action: Verify that all levels are between 1 and the maximum number of
// levels encoded in the HHCODE.
/
13003, 00000, "the specified range for a dimension is invalid"
// *Cause: The specified range for a dimension was invalid.
// *Action: Ensure that the lower bound (lb) is less than the upper bound
// (ub).
/
13004, 00000, "the specified buffer size is invalid"
// *Cause: The buffer size for a function is not valid.
// *Action: This is an internal error. Contact Oracle Support Services.
/
13005, 00000, "recursive HHCODE function error"
// *Cause: An error occurred in a recursively called HHCODE function.
// *Action: This is an internal error. Contact Oracle Support Services.
/
13006, 00000, "the specified cell number is invalid"
// *Cause: The cell identifier was either less than 0 or greater than
// (2^ndim - 1).
// *Action: Ensure that the cell identifier is between 0 and (2^ndim - 1).
/
13007, 00000, "an invalid HEX character was detected"
// *Cause: A character that is not in the range [0-9] or [A-F a-f] was
// detected.
// *Action: Verify that all characters in a string are in [0-9] or [A-F a-f].
/
13008, 00000, "the specified date format has an invalid component"
// *Cause: Part of specified date format is invalid.
// *Action: Verify that the date format is valid.
/
13009, 00000, "the specified date string is invalid"
// *Cause: The specified date string had a bad component or did not match
// the specified format string.
// *Action: Ensure that the components of the date string are valid and
// that the date and format strings match.
/
13010, 00000, "an invalid number of arguments has been specified"
// *Cause: An invalid number of arguments was specified for an SDO function.
// *Action: Verify the syntax of the function call.
/
13011, 00000, "value is out of range"
// *Cause: A specified dimension value was outside the range defined for that
// dimension.
// *Action: Ensure that all values to be encoded are within the defined
// dimension range.
/
13012, 00000, "an invalid window type was specified"
// *Cause: An invalid window type was specified.
// *Action: Valid window types are RANGE, PROXIMITY, POLYGON.
/
13013, 00000, "the specified topology was not INTERIOR or BOUNDARY"
// *Cause: A topology was specified that was not INTERIOR or BOUNDARY.
// *Action: Ensure that INTERIOR or BOUNDARY is used to describe the
// topology of the HHCODE.
/
13014, 00000, "a topology identifier outside the range of 1 to 8 was specified"
// *Cause: A topology identifier outside the range of 1 to 8 was specified.
// *Action: Specify a topology in the range of 1 to 8.
/
13015, 00000, "the window definition is not valid"
// *Cause: The number of values used to define the window does not
// correspond to the window type.
// *Action: Verify that the number of values used to defined the window is
// correct for the window type and number of dimensions.
/
13016, 00000, " specified topology [%s] is invalid"
// *Cause: The specified topology did not exist in the database,
// or some components of the topology were missing from the database.
// *Action: Check the specified topology by executing the
// SDO_TOPO.validate_topology function.
/
13017, 00000, "unrecognized line partition shape"
// *Cause: The shape of a 2-D line partition could not be determined.
// *Action: This is an internal error. Contact Oracle Support Services.
/
13018, 00000, "bad distance type"
// *Cause: The specified distance type is invalid.
// *Action: The only supported distance functions are EUCLID and MANHATTAN.
/
13019, 00000, "coordinates out of bounds"
// *Cause: Vertex coordinates lie outside the valid range for specified dimension.
// *Action: Redefine vertex coordinates within specified boundaries.
/
13020, 00000, "coordinate is NULL"
// *Cause: A vertex coordinate has a NULL value.
// *Action: Redefine vertex coordinate to have non-NULL value.
/
13021, 00000, "element not continuous"
// *Cause: The coordinates defining a geometric element are not connected.
// *Action: Redefine coordinates for the geometric element.
/
13022, 00000, "polygon crosses itself"
// *Cause: The coordinates defining a polygonal geometric element represent crossing segments.
// *Action: Redefine coordinates for the polygon.
/
13023, 00000, "interior element interacts with exterior element"
// *Cause: An interior element of a geometric object interacts with the exterior element of that object.
// *Action: Redefine coordinates for the geometric elements.
/
13024, 00000, "polygon has less than three segments"
// *Cause: The coordinates defining a polygonal geometric element represent less than three segments.
// *Action: Redefine the coordinates for the polygon.
/
13025, 00000, "polygon does not close"
// *Cause: The coordinates defining a polygonal geometric element represent an open polygon.
// *Action: Redefine the coordinates of the polygon.
/
13026, 00000, "unknown element type for element %s.%s.%s"
// *Cause: The SDO_ETYPE column in the <layer>_SDOGEOM table contains
// an invalid geometric element type value.
// *Action: Redefine the geometric element type in the <layer>_SDOGEOM table
// for the specified geometric element using one of the supported
// SDO_ETYPE values. See the Oracle Spatial documentation for
// an explanation of SDO_ETYPE and its possible values.
/
13027, 00000, "unable to read dimension definition from %s"
// *Cause: There was a problem reading the dimension definition from the
// <layer>_SDODIM table.
// *Action: Verify that the <layer>_SDODIM table exists and that the
// appropriate privileges exist on the table. Address any other
// errors that might appear with the message.
/
13028, 00000, "Invalid Gtype in the SDO_GEOMETRY object"
// *Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.
// *Action: Verify that the geometries have valid gtypes.
/
13029, 00000, "Invalid SRID in the SDO_GEOMETRY object"
// *Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object.
// The specified SRID may be outside the valid SRID range.
// *Action: Verify that the geometries have valid SRIDs.
/
13030, 00000, "Invalid dimension for the SDO_GEOMETRY object"
// *Cause: There is a mismatch between the dimension in the SDO_GTYPE and
// dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object.
// *Action: Verify that the geometries have valid dimensionality.
/
13031, 00000, "Invalid Gtype in the SDO_GEOMETRY object for point object"
// *Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the
// VARRAYs are NULL but the SDO_GTYPE is not of type POINT.
// *Action: Verify that the geometries have valid gtypes.
/
13032, 00000, "Invalid NULL SDO_GEOMETRY object"
// *Cause: There are invalid SDO_POINT_TYPE or SDO_ELEM_INFO_ARRAY or
// SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object.
// *Action: Verify that the geometries have valid fields. To specify a NULL
// geometry, specify the whole SDO_GEOMETRY as NULL instead of
// setting each field to NULL.
/
13033, 00000, "Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object"
// *Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the
// SDO_GEOMETRY object. The triplets in this field do not make up a
// valid geometry.
// *Action: Verify that the geometries have valid data.
/
13034, 00000, "Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object"
// *Cause: There is invalid data in the SDO_ORDINATE_ARRAY field of the
// SDO_GEOMETRY object. The coordinates in this field do not make up a
// valid geometry. There may be NULL values for X or Y or both.
// *Action: Verify that the geometries have valid data.
/
13035, 00000, "Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object"
// *Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the
// SDO_GEOMETRY object. There are arcs in a geometry that has
// geodetic coordinates.
// *Action: Verify that the geometries have valid data.
/
13036, 00000, "Operation [%s] not supported for Point Data"
// *Cause: The specified geometry function was not supported for point data.
// *Action: Ensure that the specified geometry function is not called
// on point data.
/
13037, 00000, "SRIDs do not match for the two geometries"
// *Cause: A spatial operation was invoked with two geometries where
// one geometry had an SRID and the other geometry did not have an SRID.
// *Action: Ensure that the spatial operations are invoked between two
// geometries with compatible SRIDs.
/
13039, 00000, "failed to update spatial index for element %s.%s.%s"
// *Cause: Another error will accompany this message that will indicate the
// problem.
// *Action: Correct any accompanying errors. If no accompanying error
// message appears, contact Oracle Support Services.
/
13040, 00000, "failed to subdivide tile"
// *Cause: This is an internal error.
// *Action: Note any accompanying errors and contact Oracle Support Services.
/
13041, 00000, "failed to compare tile with element %s.%s.%s"
// *Cause: The spatial relationship between a generated tile and the specified
// element could not be determined.
// *Action: This is an internal error. Verify the geometry using the
// VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure
// does not return any errors, note any errors that accompany ORA-13041
// and contact Oracle Support Services.
/
13042, 00000, "invalid SDO_LEVEL and SDO_NUMTILES combination"
// *Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was
// read from the <layer>_SDOLAYER table. The most likely cause is
// that the columns are NULL.
// *Action: Verify the that SDO_LEVEL and SDO_NUMTILES columns contain
// valid integer values as described in the
// Oracle Spatial documentation. Then retry the operation.
/
13043, 00000, "failed to read metadata from the <layer>_SDOLAYER table"
// *Cause: An error was encountered reading the layer metadata from the
// <layer>_SDOLAYER table.
// *Action: This error is usually the result of an earlier error which should
// also have been reported. Address this accompanying error and
// retry the current operation. If no accompanying error was
// reported, contact Oracle Support Services.
/
13044, 00000, "the specified tile size is smaller than the tolerance"
// *Cause: The tile size specified for fixed size tessellation
// is smaller than the tolerance as specified in the layer metadata.
// *Action: See the Oracle Spatial documentation for an explanation of
// tiling levels, tile size, and tiling resolution. Ensure that
// the tiling parameters are set such that any generated tile
// is always larger than or equal to a tile at the maximum level
// of resolution. This can be achieved by using a fewer number of
// tiles per geometric object or specifying a smaller tile size
// value than the current one.
/
13046, 00000, "invalid number of arguments "
// *Cause: An invalid number of arguments were specified for an
// SDO_GEOM function.
// *Action: See the Oracle Spatial documentation for a description of
// the syntax and semantics of the relevant SDO_GEOM function.
/
13047, 00000, "unable to determine ordinate count from table <layer>_SDOLAYER"
// *Cause: An SDO_GEOM function was unable to determine the number of
// ordinates for the SDO layer <layer>.
// *Action: Verify that the <layer>_SDOLAYER table has a valid value for
// the column SDO_ORDCNT. Then retry the operation.
/
13048, 00000, "recursive SQL fetch error"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13049, 00000, "unable to determine tolerance value from table <layer>_SDODIM"
// *Cause: An SDO_GEOM function was unable to determine the tolerance value
// for the SDO layer <layer>.
// *Action: Verify that the <layer>_SDODIM table has a valid value for
// the column SDO_TOLERANCE.
/
13050, 00000, "unable to construct spatial object"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13051, 00000, "failed to initialize spatial object"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13052, 00000, "unsupported geometric type for geometry %s.%s"
// *Cause: The geometry type for a specific instance in a <layer>_SDOGEOM
// table is not among the set of geometry types supported by
// Oracle Spatial.
// *Action: Check the Oracle Spatial documentation for the list of supported geometry types
// and workarounds that permit the storage and retrieval of
// non-supported geometric types with the SDO schema.
/
13053, 00000, "maximum number of geometric elements in argument list exceeded"
// *Cause: The maximum number of geometric elements that can be specified
// in the argument list for an SDO_GEOM function was exceeded.
// *Action: Check the Oracle Spatial documentation for the syntax of the SDO_GEOM function
// and use fewer arguments to describe the geometry, or
// check the description of the SDO_WINDOW package for a workaround
// that permits storing the object in a table and then using it in
// as an argument in a call to the SDO_GEOM function.
/
13054, 00000, "recursive SQL parse error"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13055, 00000, "Oracle object %s does not exist in specified table"
// *Cause: The requested object is not present in the specified table.
// *Action: Verify the syntax of the function or procedure that reported
// this error and verify that the object does indeed exist in the
// specified table. Then retry the operation.
/
13056, 00000, "Spatial Reference ID (SRID) does not exist: NULL."
// *Cause: The operation required a valid SRID but none was specified.
// *Action: Contact Oracle Support Services.
/
13057, 00000, "Spatial Reference ID (SRID) %d does not exist."
// *Cause: The specified SRID is not known.
// *Action: Ensure that the specified SRID was valid.
/
13058, 00000, "Spatial Reference ID (SRID) does not exist."
// *Cause: The SRID for the operation could not be determined.
// *Action: Ensure that the SRID for the operation is valid.
/
13059, 00000, "invalid WRK_TBLSPC parameter"
// *Cause: An invalid "WRK_TBLSPC" parameter value was specified.
// *Action: Ensure that the specified "WRK_TBLSPC" exists and is
// accessible to the current user.
/
13060, 00000, "topology with the name %s already exists"
// *Cause: The specified topology name was not unique in the database.
// *Action: Verify that the CREATE_TOPOLOGY call specifies the correct topology
// name and that the procedure is invoked from the correct schema.
/
13061, 00000, "topology with the name %s does not exist"
// *Cause: The specified topology did not exist in the database.
// *Action: Verify that the current procedure/function call specifies the
// correct schema and topology name.
/
13062, 00000, "topology IDs do not match in the feature table and the topology"
// *Cause: The specified topology ID in the feature table did not match the
// topology ID stored in the topology metadata.
// *Action: Verify that the specified topology ID matches the topology ID stored
// in the topology metadata.
/
13063, 00000, "relationship information table is missing data for feature table [%s]"
// *Cause: The topology relationship information table (xxx_RELATION$) did not
// have the matching partition corresponding to the feature table.
// *Action: Ensure the correct topology IDs and names are specified in the
// call to register the feature table with the topology.
/
13064, 00000, "relationship information table has inconsistent data for feature table [%s]"
// *Cause: The topology_id and tg_layer_id values stored in the feature
// table did not match the values stored in the topology
// relationship information table (xxx_RELATION$).
// *Action: Ensure that the correct feature tables are specified in the
// call to register the feature table with the topology.
/
13065, 00000, "cannot delete a child layer with a parent layer"
// *Cause: A call was made to delete a feature layer which has a dependent
// layer defined on it.
// *Action: Ensure that all dependent feature layers are deleted before
// deleting the current feature layer.
/
13066, 00000, "wrong feature geometry or element type"
// *Cause: The SDO_TOPO_GEOMETRY object had the wrong geometry and/or element
// type.
// *Action: Correct the geometry and/or element type in the SDO_TOPO_GEOMETRY
// object.
/
13067, 00000, "operator requires both parameters from the same topology"
// *Cause: Both SDO_TOPO_GEOMETRY parameters did not come from the same
// topology.
// *Action: Ensure that both of the parameters to the operator are from the
// same topology. If this is not possible, consider using a
// signature of the operator that does not use two
// SDO_TOPO_GEOMETRY parameters.
/
13068, 00000, "wrong table or column name in SDO_TOPO_GEOMETRY constructor"
// *Cause: An SDO_TOPO_GEOMETRY constructor was invoked with incorrect
// parameters for table name and/or column name.
// *Action: Fix the parameters in the call and try again.
/
13069, 00000, "incorrect degree value for SDO_GEOMETRY object"
// *Cause: An incorrect degree value <=1 was passed for a Non-Uniform
// Rational B-Spline curve.
// *Action: Correct the degree value for the Non-Uniform Rational B-Spline
// curve.
/
13070, 00000, "incorrect number of control points for SDO_GEOMETRY object"
// *Cause: An incorrect number of control points was passed for a
// Non-Uniform Rational B-Spline curve.
// *Action: Correct the number of control points for the Non-Uniform
// Rational B-Spline curve.
/
13071, 00000, "incorrect control points, degree for SDO_GEOMETRY object"
// *Cause: An incorrect number of control points and degree was passed
// for a Non-Uniform Rational B-Spline curve.
// *Action: Ensure that the number of control points is greater than the
// degree for a Non-Uniform Rational B-Spline curve.
/
13072, 00000, "incorrect number of knots for SDO_GEOMETRY object"
// *Cause: An incorrect number of knot values was passed for a Non-Uniform
// Rational B-Spline curve.
// *Action: Correct the number of knot values passed for the Non-Uniform
// Rational B-Spline curve.
/
13073, 00000, "incorrect control point weight value for a SDO_GEOMETRY object"
// *Cause: An incorrect value was passed for the weight of a control point
// of a Non-Uniform Rational B-Spline curve.
// *Action: Ensure all weight values for control points are positive.
/
13074, 00000, "incorrect knot value for SDO_GEOMETRY object"
// *Cause: An incorrect knot value was passed for a Non-Uniform Rational
// B-Spline curve.
// *Action: Ensure the knot values passed for the Non-Uniform Rational
// B-Spline curve are in non-decreasing order.
/
13075, 00000, "incorrect knot value sequence for SDO_GEOMETRY object"
// *Cause: An incorrect knot value sequence was passed for a Non-Uniform
// Rational B-Spline curve.
// *Action: Ensure the knot values passed for the Non-Uniform Rational
// B-Spline curve have no more than a sequence of 'k' consecutive
// identical values or no more than 'k + 1' consecutive same values
// at the beginning or end of Non-Uniform Rational B-Spline curve.
/
13076, 00000, "incorrect knot value sequence for SDO_GEOMETRY object"
// *Cause: An incorrect knot value sequence was passed for a Non-Uniform
// Rational B-Spline curve.
// *Action: Ensure the knot value sequence passed for the Non-Uniform
// Rational B-Spline curve is a normalized vector beginning at
// zero and ending at one.
/
13077, 00000, "incorrect start or end point for subelement of a compound curve"
// *Cause: The end point of a subelement for a compound curve was not equal
// to the start point of the next subelement, or the start point of
// a subelement was not equal to the end point of the previous
// subelement and one of the subelements was a NURBS curve.
// *Action: Ensure that the end point of each subelement is equal to the
// start point of the next subelement and that the start point of
// each subelement is equal to the end point of the previous
// subelement when one of the subelements is a NURBS curve.
/
13078, 00000, "cannot commit a distributed transaction involving spatial index"
// *Cause: An attempt was made to commit changes to a spatial table in
// a distributed transaction, but spatial indexes are not
// supported in distributed transactions.
// *Action: Perform all transactional changes to spatial tables (tables
// containing spatial geometry columns) in a local
// non-distributed transaction.
// For more information about this restriction, refer
// to the Oracle Spatial Data and Graph documentation.
/
13079, 00000, "invalid schema name"
// *Cause: The specified schema name was invalid.
// *Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the schema
// name is valid.
/
13080, 00000, "invalid index name"
// *Cause: The specified spatial index name was invalid.
// *Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the spatial
// index name is valid.
/
13081, 00000, "invalid index table name"
// *Cause: The specified index table name was invalid.
// *Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the index
// table name is valid. The index table name typically starts
// with "MDRT_" prefix.
/
13082, 00000, "invalid index partition name"
// *Cause: The specified index partition name was invalid.
// *Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the index
// partition name was valid.
/
13083, 00000, "invalid index parameters"
// *Cause: The specified index parameter or parameter combination was invalid.
// *Action: Check the list of index parameters to ensure that they are correctly
// specified and valid for the corresponding index operation.
/
13084, 00000, "invalid table type: index organization not supported"
// *Cause: An attempt was made to create the spatial index on an index-
// organized table (IOT).
// *Action: Spatial indexes cannot be created on index-organized tables.
/
13085, 00000, "invalid column name"
// *Cause: The specified column name was invalid.
// *Action: Check the ALL_SDO_INDEX_METADATA view to ensure that the index
// column name is valid. If the column name is a function, ensure
// the function name is properly spelled and case-sensitive.
/
13086, 00000, "geometry cannot be an optimized geodetic MBR"
// *Cause: An attempt was made to use optimized geodetic minimum bounding rectangles (MBR).
// *Action: The object tracker cannot be used on objects that are composed
// of optimized MBRs.
/
13087, 00000, "incorrect number of query columns"
// *Cause: The number of table columns specified for the PointInPolygon()
// function was incorrect.
// *Action: Ensure that there are at least two columns specified, and that the
// first two columns are of the NUMBER type, representing the X and Y
// coordinates.
/
13088, 00000, "SQL cursor rows have been pre-fetched"
// *Cause: It has been detected that 1 or more rows have been pre-fetched
// from the specified query cursor.
// *Action: One or more rows were pre-fetched from the specified query cursor.
/
13089, 00000, "invalid tolerance"
// *Cause: The specified tolerance value was invalid.
// *Action: The tolerance value must be greater than 0.0.
/
13090, 00000, "geometry must be 2D"
// *Cause: The specified geometry is not two-dimensional.
// *Action: Ensure the geometry is two-dimensional.
/
13091, 00000, "unable to process query on geodetic MBR"
// *Cause: The operation is not valid using geodetic MBRs.
// *Action: Ensure the geometry is not using geodetic MBRs.
/
13092, 00000, "unable to process query"
// *Cause: The operation failed.
// *Action: Contact Oracle Support Services.
/
13093, 00000, "polygon Rings exceeded half the area of earth"
// *Cause: The polygon ring size exceeded half the area of the earth.
// *Action: Contact Oracle Support Services.
/
13094, 00000, "invalid cursor"
// *Cause: The specified query cursor was invalid.
// *Action: Contact Oracle Support Services.
/
13095, 00000, "Element number is wrong"
// *Cause: The specified element number is incorrect.
// *Action: Ensure the specified element number is valid for the geometry.
/
13096, 00000, "Wrong geometry type"
// *Cause: The specified geometry type is incorrect.
// *Action: Ensure the specified geometry type (GTYPE) is valid for the geometry.
/
13097, 00000, "wrong element type"
// *Cause: The specified element type is incorrect.
// *Action: Ensure the specified element type (GTYPE) is valid for the geometry.
/
13098, 00000, "more elements than specified"
// *Cause: There are more elements than were specified.
// *Action: Ensure the specified number of elements is valid for the geometry.
/
13099, 00000, "wrong RING topology"
// *Cause: The geometry ring topology (inner or outer) is wrong.
// *Action: Contact Oracle Support Services.
/
13100, 00000, "feature does not exist"
// *Cause: The feature does not exist.
// *Action: Contact Oracle Support Services.
/
13101, 00000, "invalid ptn_type parameter"
// *Cause: An incorrect ptn_type parameter was specified.
// *Action: Ensure the ptn_type parameter value is correct.
/
13102, 00000, "invalid ptn_capacity parameter"
// *Cause: An incorrect ptn_capacity parameter was specified.
// *Action: Ensure the ptn_capacity parameter value is correct.
/
13103, 00000, "invalid numdim parameter"
// *Cause: An incorrect numdim parameter was specified.
// *Action: Ensure the numdim parameter value is correct.
/
13104, 00000, "null values not allowed in input data"
// *Cause: Null values cannot be specified in the supplied input data.
// *Action: Ensure that all null-values have been removed from the data.
/
13105, 00000, "invalid Parameters for Partition_Table"
// *Cause: One or more parameters for the Partition_Table() function
// are invalid.
// *Action: Ensure that the identified parameters are correctly specified.
/
13106, 00000, "invalid MASK parameter"
// *Cause: The specified MASK parameter was invalid.
// *Action: Ensure that the MASK parameter values are correctly specified.
/
13107, 00000, "operation not supported for Non-Uniform Rational B-Spline type"
// *Cause: This operation cannot be executed for Non-Uniform Rational
// B-Spline curves.
// *Action: Specify a geometry that does not contain a Non-Uniform Rational
// B-Spline curve type.
/
13108, 00000, "spatial table %s not found"
// *Cause: The specified spatial table did not exist.
// *Action: Check the spatial data dictionary to ensure
// that the table is registered.
/
13109, 00000, "spatial table %s exists"
// *Cause: The specified spatial table is registered in the Spatial
// data dictionary.
// *Action: Remove the existing table from the Spatial
// data dictionary or use a different name.
/
13110, 00000, "cannot drop topology with associated topo_geometry tables"
// *Cause: The drop_topology procedure was invoked for a topology that has
// assocated topo_geometry layers with it.
// *Action: Delete the topo_geometry layers from the topology before dropping
// the topology. Use SDO_TOPO.delete_topo_geometry_layer to delete
// topo_geometry layers from the topology.
/
13111, 00000, "cannot add topo_geometry layer [%s] to topology"
// *Cause: It was not possible to add the specified TOPO_GEOMETRY layer
// to the topology.
// *Action: Ensure that the TOPO_GEOMETRY layer table exists in the database.
/
13112, 00000, "cannot delete topo_geometry layer [%s] from topology"
// *Cause: It was not possible to delete the specified topo_geometry layer
// from the topology.
// *Action: Check USER_SDO_TOPO_METADATA to see if the specified
// topo_geometry layer is part of the topology. Only those
// topo_geometry layers which are part of the topology can be
// deleted from it.
/
13113, 00000, "invalid tg_layer_id in sdo_topo_geometry constructor"
// *Cause: An invalid layer_id was passed to the SDO_TOPO_GEOMETRY constructor.
// *Action: Valid layer_ids are obtained by adding a topo_geometry layer to
// the topology. Check USER_SDO_TOPO_METADATA to find out the
// layer_id for an existing topo_geometry layer.
/
13114, 00000, "[%s]_NODE$ table does not exist"
// *Cause: The NODE$ table for the topology did not exist in the database.
// *Action: There is a severe corruption of the topology.
// Call Oracle Support Services with the error number.
/
13115, 00000, "[%s]_EDGE$ table does not exist"
// *Cause: The EDGE$ table for the topology did not exist in the database.
// *Action: There is a severe corruption of the topology.
// Call Oracle Support Services with the error number.
/
13116, 00000, "[%s]_FACE$ table does not exist"
// *Cause: The FACE$ table for the topology did not exist in the database.
// *Action: There is a severe corruption of the topology.
// Call Oracle Support Services with the error number.
/
13117, 00000, "[%s]_RELATION$ table does not exist"
// *Cause: The RELATION$ table for the topology did not exist in the database.
// *Action: There is a severe corruption of the topology.
// Call Oracle Support Services with the error number.
/
13118, 00000, "invalid node_id [%s]"
// *Cause: A topology node operation was invoked with an invalid node_id.
// *Action: Check the topology node$ table to see if the specified node_id
// exists in the topology.
/
13119, 00000, "invalid edge_id [%s]"
// *Cause: A topology edge operation was invoked with an invalid edge_id.
// *Action: Check the topology edge$ table to see if the specified edge_id
// exists in the topology.
/
13120, 00000, "invalid face_id [%s]"
// *Cause: A topology face operation was invoked with an invalid face_id.
// *Action: Check the topology face$ table to see if the specified face_id
// exists in the topology.
/
13121, 00000, "layer type type mismatch with topo_geometry layer type"
// *Cause: The tg_type in SDO_TOPO_GEOMETRY constructor did not match the
// type specified for the layer.
// *Action: Check the USER_SDO_TOPO_METADATA view to see the layer type
// for the layer and use it in the constructor.
/
13122, 00000, "invalid topo_geometry specified"
// *Cause: The SDO_TOPO_GEOMETRY object passed into the function/operator was
// not valid.
// *Action: Check the SDO_TOPO_GEOMETRY object and verify that it is a valid
// topo_geometry object.
/
13123, 00000, "invalid <TOPOLOGY> name specified"
// *Cause: The create_topo operation requires a unique TOPOLOGY name, that
// already does not exist in the database.
// *Action: Check to see if there is already an entry in the
// USER_SDO_TOPO_METADATA (or the MDSYS.SDO_TOPO_METADATA_TABLE)
// with this topology name.
/
13124, 00000, "unable to determine column id for column %s"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13125, 00000, "partition key is already set"
// *Cause: A partition key is already set for the spatial table.
// *Action: Only one partition key can be specified per spatial table.
/
13126, 00000, "unable to determine class for spatial table %s"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13127, 00000, "failed to generate target partition"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13128, 00000, "current tiling level exceeds user specified tiling level"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13129, 00000, "HHCODE column %s not found"
// *Cause: The specified spatial column does not exist.
// *Action: Verify that the specified column is a spatial column by checking
// the Spatial data dictionary.
/
13135, 00000, "failed to alter spatial table"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13136, 00000, "null common code generated"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13137, 0000, "failed to generate tablespace sequence number"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13138, 00000, "could not determine name of object %s"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13139, 00000, "could not obtain column definition for %s"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13140, 00000, "invalid target type"
// *Cause: The specified target type is not valid.
// *Action: Substitute a valid target type. Valid target types are TABLE and
// VIEW.
/
13141, 00000, "invalid RANGE window definition"
// *Cause: The RANGE window specified is not correctly defined.
// *Action: A RANGE window is defined by specifying the lower and upper
// boundary of each dimension as a pair of values
// (e.g.: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...).
// There should be an even number of values.
/
13142, 00000, "invalid PROXIMITY window definition"
// *Cause: The PROXIMITY window specified is not correctly defined.
// *Action: A PROXIMITY window is defined by specifying a center point and a
// radius. The center point is defined by ND values. There should
// be ND+1 values.
/
13143, 00000, "invalid POLYGON window definition"
// *Cause: The POLYGON window specified is not correctly defined.
// *Action: A POLYGON window is defined by specifying N pairs of values
// that represent the vertices of the polygon. There should be
// an even number of values.
/
13144, 00000, "target table %s not found"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13145, 00000, "failed to generate range list"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13146, 00000, "could not find table substitution variable %s"
// *Cause: The partition name substitution variable %s was not found in the
// SQL filter.
// *Action: The substitution variable %s must be in the SQL filter to indicate
// where that partition name should be placed.
/
13147, 00000, "failed to generate MBR"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13148, 00000, "failed to generate SQL filter"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13149, 00000, "failed to generate next sequence number for spatial table %s"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13150, 00000, "failed to insert exception record"
// *Cause: Operation failed to insert a record into the exception table.
// *Action: Fix any other errors reported.
/
13151, 00000, "failed to remove exception record"
// *Cause: Operation failed to remove a record from the exception table.
// *Action: Fix any other errors reported.
/
13152, 00000, "invalid HHCODE type"
// *Cause: Specified HHCODE type is not valid.
// *Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT
// and LINE.
/
13153, 00000, "invalid high water mark specified"
// *Cause: The high water mark was not greater than or equal to zero.
// *Action: Ensure that the high water mark is an integer greater than
// or equal to zero.
/
13154, 00000, "invalid precision specified"
// *Cause: The precision specified is out of range.
// *Action: The precision must be an integer greater than or equal to zero.
/
13155, 00000, "invalid number of dimensions specified"
// *Cause: The number of dimensions specified is out of range.
// *Action: The number of dimension must be between 1 and 32.
/
13156, 00000, "table to be registered %s.%s is not empty"
// *Cause: The specified table contained rows.
// *Action: Ensure that the table to be registered is empty.
/
13157, 00000, "Oracle error ORA%s encountered while %s"
// *Cause: The specified Oracle error was encountered.
// *Action: Correct the Oracle error.
/
13158, 00000, "Oracle object %s does not exist"
// *Cause: The specified object does not exist.
// *Action: Verify that the specified object exists.
/
13159, 00000, "Oracle table %s already exists"
// *Cause: The specified table already exists.
// *Action: Drop the specified table.
/
13181, 00000, "unable to determine length of column %s_SDOINDEX.SDO_CODE"
// *Cause: The length of the SDO_CODE column in the <layer>_SDOINDEX table
// could not be determined.
// *Action: Ensure that the <layer>_SDOINDEX table exists with the SDO_CODE
// column. Verify that the appropriate privileges exist on the table.
// Then retry the operation.
/
13182, 00000, "failed to read element %s.%s.%s"
// *Cause: The specified element could not be read from the <layer>_SDOGEOM
// table.
// *Action: Verify that the specified element exists in the table.
// Then retry the operation.
/
13183, 00000, "unsupported geometric type for geometry %s.%s"
// *Cause: The geometry type in the <layer>_SDOGEOM table is unsupported.
// *Action: Modify the geometry type to be one of the supported types.
/
13184, 00000, "failed to initialize tessellation package "
// *Cause: Initialization of the tessellation package failed.
// *Action: Record the error messages that are returned
// and contact Oracle Support Services.
/
13185, 00000, "failed to generate initial HHCODE"
// *Cause: This is an internal error.
// *Action: Record the error messages that are returned
// and contact Oracle Support Services.
/
13186, 00000, "fixed tile size tessellation failed"
// *Cause: This is an internal error.
// *Action: Record the error messages that are returned
// and contact Oracle Support Services.
/
13187, 00000, "subdivision failed"
// *Cause: This is an internal error.
// *Action: Record the error messages that are returned
// and contact Oracle Support Services.
/
13188, 00000, "cell decode failed"
// *Cause: This is an internal error.
// *Action: Record the error messages that are returned
// and contact Oracle Support Services.
/
13189, 00000, "recursive SQL parse failed"
// *Cause: This is an internal error.
// *Action: Record the error messages that are returned
// and contact Oracle Support Services.
/
13190, 00000, "recursive SQL fetch failed"
// *Cause: This is an internal error.
// *Action: Record the error messages that are returned
// and contact Oracle Support Services.
/
13191, 00000, "failed to read SDO_ORDCNT value"
// *Cause: This is an internal error.
// *Action: Record the error messages that are returned
// and contact Oracle Support Services.
/
13192, 00000, "failed to read number of element rows"
// *Cause: This is an internal error.
// *Action: Record the error messages that are returned
// and contact Oracle Support Services.
/
13193, 00000, "failed to allocate space for geometry"
// *Cause: There was insufficient memory to read the geometry
// from the database.
// *Action: Validate the geometry. Record the error messages
// that are returned and contact Oracle Support Services.
/
13194, 00000, "failed to decode supercell"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
13195, 00000, "failed to generate maximum tile value"
// *Cause: This is an internal error.
// *Action: Record the error messages that are returned
// and contact Oracle Support Services.
/
13196, 00000, "failed to compute supercell for element %s.%s.%s"
// *Cause: The system was unable to compute the minimum bounding
// HHCODE or supercell for the geometry.
// *Action: Another error might accompany this error. Correct the
// accompanying error. Also, validate the geometry for
// correctness.
/
13197, 00000, "element %s.%s.%s is out of range"
// *Cause: Tessellation did not generate any tiles for this element.
// This error could be caused if the geometry definition
// puts the geometry outside the domain defined in the
// <layer>_SDODIM table.
// *Action: Verify that the geometry is valid and within the defined
// domain.
/
13198, 00000, "Spatial error: %s"
// *Cause: Internal error in some Oracle Spatial stored procedure.
// *Action: Record the sequence of procedure calls or events that
// preceded this error, and contact Oracle Support Services if
// the error message text does not clearly specify the cause
// of the error.
/
13199, 00000, "%s"
// *Cause: This is an internal error.
// *Action: Contact Oracle Support Services.
/
/ (13200 - 13499 Reserved for Oracle Spatial 8.1.3 and future use)
13200, 00000, "internal error [%s] in spatial indexing."
// *Cause: This is an internal error.
// Action: Contact Oracle Support Services with the exact error text.
/
13201, 00000, "invalid parameters supplied in CREATE INDEX statement"
// *cause: An error was encountered while trying to parse the parameters
// clause for the spatial CREATE INDEX statement.
// *Action: Check the Oracle Spatial documentation for the number, syntax,
// and semantics of expected parameters for spatial index creation.
/
13202, 00000, "failed to create or insert into the SDO_INDEX_METADATA table"
// *Cause: An error was encountered while trying to create the
// SDO_INDEX_METADATA table or insert data into it.
// *Action: Verify that the current user has CREATE TABLE privilege and
// that the user has sufficient quota in the default or
// specified tablespace.
/
13203, 00000, "failed to read USER_SDO_GEOM_METADATA view"
// *Cause: An error encountered while trying to read the USER_SDO_GEOM_METADATA
// view.
// *Action: Check that USER_SDO_GEOM_METADATA has an
// entry for the current geometry table.
/
13204, 00000, "failed to create spatial index table"
// *Cause: An error was encountered while trying to create the index table.
// *Action: Check that user has CREATE TABLE privilege in the current schema
// and that the user has sufficient quota in the default or
// specified tablespace.
/
13205, 00000, "internal error while parsing spatial parameters"
// *Cause: An internal error was encountered while parsing
// the spatial parameters.
// *Action: Check that the parameters passed in the parameter
// string are all valid.
/
13206, 00000, "internal error [%s] while creating the spatial index"
// *Cause: An internal error was encountered while
// creating the spatial index.
// *Action: Contact Oracle Support Services with the exact error text.
/
13207, 00000, "incorrect use of the [%s] operator"
// *Cause: An error was encountered while evaluating the specified operator.
// *Action: Check the parameters and the return type of the specified
// operator.
/
13208, 00000, "internal error while evaluating [%s] operator"
// *Cause: An internal error was encountered.
// *Action: Contact Oracle Support Services with the exact error text.
/
13209, 00000, "internal error while reading SDO_INDEX_METADATA table"
// *Cause: An internal error was encountered while trying to read the
// SDO_INDEX_METADATA table.
// *Action: Contact Oracle Support Services. Note this and accompanying
// error numbers.
/
13210, 00000, "error inserting data into the index table"
// *Cause: An error was encountered while trying to insert data into the
// index table. Likely causes are:
// - Insufficient quota in the current tablespace
// - User does not appropriate privileges
// *Action: Check the accompanying error messages.
/
13211, 00000, "failed to tessellate the window object"
// *Cause: An internal error was encountered while trying to tessellate the
// window object.
// *Action: Verify the geometric integrity of the window object using the
// VALIDATE_GEOMETRY_WITH_CONTEXT procedure.
/
13212, 00000, "failed to compare tile with the window object "
// *Cause: The spatial relationship between a generated tile and the specified
// window object could not be determined.
// *Action: This is an internal error. Verify the geometry using the
// VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure
// does not return any errors, note any accompanying errors and contact
// Oracle Support Services.
/
13213, 00000, "failed to generate spatial index for window object"
// *Cause: Another error, indicating the real cause of the problem, should
// accompany this error.
// *Action: Correct any accompanying errors. If no accompanying error
// message appears, contact Oracle Support Services.
/
13214, 00000, "failed to compute supercell for window object "
// *Cause: The system was unable to compute the minimum bounding
// tile or supercell for the geometry.
// *Action: Another error might accompany this error. Correct the
// accompanying error. Also, validate the geometry for
// correctness.
/
13215, 00000, "window object is out of range"
// *Cause: Tessellation did not generate any tiles for this geometry.
// This error could be caused if the geometry definition
// puts the geometry outside the domain defined in the
// USER_SDO_GEOM_METADATA view.
// *Action: Verify that the geometry is valid and within the defined
// domain.
/
13216, 00000, "failed to update spatial index"
// *Cause: Another error will accompany this message that will indicate the
// problem.
// *Action: Correct any accompanying errors. If no accompanying error
// message appears, contact Oracle Support Services.
/
13217, 00000, "invalid parameters supplied in ALTER INDEX statement"
// *Cause: An error was encountered while trying to parse the parameters
// clause for the spatial ALTER INDEX statement.
// *Action: Check the Oracle Spatial documentation for the number, syntax,
// and semantics of expected parameters for the spatial ALTER INDEX
// statement.
/
13218, 00000, "max number of supported index tables reached for [%s] index"
// *Cause: An add_index parameter was passed to ALTER INDEX when the number of
// existing index tables is already at maximum.
// *Action: Delete one of the index tables before adding another index table.
/
13219, 00000, "failed to create spatial index table [%s]"
// *Cause: An error was encountered while trying to create the index table.
// *Action: There is a table in the index's schema with the specified
// name. The CREATE INDEX statement will try to create an index table with
// this name. Either rename this table or change the name of the index.
/
13220, 00000, "failed to compare tile with the geometry"
// *Cause: The spatial relationship between a generated tile and the specified
// geometry could not be determined.
// *Action: This is an internal error. Validate the geometry using the
// VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure
// does not return any errors, note any errors that accompany
// ORA-13220 and contact Oracle Support Services.
/
13221, 00000, "unknown geometry type in the geometry object"
// *Cause: The SDO_GTYPE attribute in the geometry object contains
// an invalid value
// *Action: Redefine the geometric type in the geometry table
// using one of the supported SDO_GTYPE values.
// See the Oracle Spatial documentation for
// an explanation of SDO_GTYPE and its possible values.
/
13222, 00000, "failed to compute supercell for geometry in %s"
// *Cause: The system was unable to compute the minimum bounding
// tile or supercell for a geometry in the specified table.
// *Action: Another error might accompany this error. Correct the
// accompanying error. Also, validate the geometry for
// correctness.
/
13223, 00000, "duplicate entry for %s in SDO_GEOM_METADATA"
// *Cause: There are duplicate entries for the given table and column
// value pair in the USER_SDO_GEOM_METADATA view.
// *Action: Check that the specified table and geometry column names
// are correct. There should be only one entry per table, geometry
// column pair in the USER_SDO_GEOM_METADATA view.
/
13224, 00000, "zero tolerance specified for layer in USER_SDO_GEOM_METADATA"
// *Cause: A tolerance of zero or NULL was supplied for a layer in the
// USER_SDO_GEOM_METADATA view.
// *Action: Check the tolerance specified to ensure that it is a positive value.
/
13225, 00000, "specified index table name is too long for a spatial index"
// *Cause: An index table name is specified which is longer than the supported
// length of the spatial index table name.
// *Action: Check the supported size of the index table name and
// reduce the size of the index name.
/
13226, 00000, "interface not supported without a spatial index"
// *Cause: The geometry table does not have a spatial index.
// *Action: Verify that the geometry table referenced in the spatial operator
// has a spatial index on it.
/
13227, 00000, "SDO_LEVEL values for the two index tables do not match"
// *Cause: The SDO_LEVEL values for the two index tables used in the
// spatial join operator do not match.
// *Action: Verify that two compatible indexes are used for the
// spatial join operator. Quadtree indexes are compatible if they
// have the same SDO_LEVEL and SDO_NUMTILES values
/
13228, 00000, "spatial index create failed due to invalid type"
// *Cause: An attempt was made to create a spatial index on a column
// of type other than SDO_GEOMETRY.
// *Action: Ensure that the index is created on a column of type
// SDO_GEOMETRY.
/
13230, 00000, "failed to create temporary table [%s] during R-tree creation"
// *Cause: The specified temporary table either already exists or
// there is not enough tablespace.
// *Action: Delete the table if it already exists and verify if the current
// user has CREATE TABLE privileges and has sufficient space in
// the default or specified tablespace.
/
13231, 00000, "failed to create index table [%s] during R-tree creation"
// *Cause: The specified index table either already exists or
// there is not enough tablespace.
// *Action: Delete the table if it already exists and verify if the current
// user has CREATE TABLE privileges and has sufficient space in
// the default or specified tablespace.
// If that fails to correct the problem, contact Oracle Support Services.
/
13232, 00000, "failed to allocate memory during R-tree creation"
// *Cause: This feature assumes a minimum of 64K memory for bulk creation.
// *Action: Create the index for a small subset of the data. Then, use
// transactional insert operations for the rest of the data.
/
13233, 00000, "failed to create sequence number [%s] for R-tree"
// *Cause: The specified sequence number exists.
// *Action: Delete the sequence object, or contact Oracle Support Services.
/
13234, 00000, "failed to access R-tree-index table [%s]"
// *Cause: The index table is either deleted or corrupted.
// *Action: Rebuild the index or contact Oracle Support Services with
// accompanying error messages.
/
13236, 00000, "internal error in R-tree processing: [%s]"
// *Cause: An internal error occurred in R-tree processing.
// *Action: Contact Oracle Support Services with the message text.
/
13237, 00000, "internal error during R-tree concurrent updates: [%s]"
// *Cause: An inconsistency is encountered during concurrent updates,
// possibly due to the use of serializable isolation level.
// *Action: Change the isolation level to "read committed" using the ALTER
// SESSION statement, or contact Oracle Support Services with
// the message text.
/
13238, 00000, "spatial journal cache enabled; query requires transaction commit"
// *Cause: The spatial transaction journal cache was enabled.
// When enabled, spatial functions that require use of
// the spatial index could not be used when uncommitted
// transaction data existed.
// *Action: Commit or roll back the current transaction, or flush the
// spatial transaction journal cache using the PL/SQL
// "SDO_UTIL.INVALIDATE_GTT_CACHE" procedure.
/
13239, 00000, "sdo_dimensionality not specified during n-d R-tree creation"
// *Cause: An error occurred in reading the dimensionality parameter
// *Action: Check the documentation for a valid range, and specify the
// dimensionality as a parameter.
/
13240, 00000, "specified dimensionality greater than that of the query mbr"
// *Cause: An error occurred because of too few values in the query minimum
// bounding rectangle (MBR).
// *Action: Omit the dimensionality, or use the dimensionality of the query.
/
13241, 00000, "specified dimensionality does not match that of the data"
// *Cause: An error occurred because the dimensionality specified in the
// CREATE INDEX statement does not match that of the data.
// *Action: Change the statement to reflect the data dimensionality.
/
13243, 00000, "specified operator is not supported for 3- or higher-dimensional R-tree"
// *Cause: Currently, an R-tree index with three or more index dimensions can be used
// only with the SDO_FILTER operator.
// *Action: Use the SDO_FILTER operator, and check the documentation for the querytype
// parameter for SDO_FILTER; or contact Oracle Support Services.
/
13249, 00000, "%s"
// *Cause: An internal error was encountered in the extensible spatial index
// component. The text of the message is obtained from some
// other server component.
// *Action: Contact Oracle Support Services with the exact error text.
/
13250, 00000, "insufficient privileges to modify metadata table entries"
// *Cause: The user requesting the operation does not have the
// appropriate privileges on the referenced tables.
// *Action: Check that the specified feature and geometry table names
// are correct, and then verify that the current user has
// at least SELECT privilege on those tables.
/
13251, 00000, "duplicate entry %s in metadata table"
// *Cause: The specified entry already exists in the metadata table.
// *Action: Check that the specified feature and geometry table names
// are correct. A feature-geometry table association should
// be registered only once.
/
13260, 00000, "layer table %s does not exist"
// *Cause: Data migration source table <layer>_SDOGEOM does not exist.
// *Action: Ensure that the specified layer name is correct and that the
// corresponding spatial layer tables exist in the current schema.
/
13261, 00000, "geometry table %s does not exist"
// *Cause: The specified geometry table does not exist in the current schema.
// *Action: Create a table containing a column of type SDO_GEOMETRY and
// a column of type NUMBER for the GID values.
/
13262, 00000, "geometry column %s does not exist in table %s"
// *Cause: The specified table does not have a column of type SDO_GEOMETRY.
// *Action: Alter or re-create the table such that it includes a column of
// type SDO_GEOMETRY and a column of type NUMBER.
/
13263, 00000, "column %s in table %s is not of type SDO_GEOMETRY"
// *Cause: The column intended for storing the geometry is not of
// type SDO_GEOMETRY.
// *Action: Alter the column definition to be of type SDO_GEOMETRY.
/
13264, 00000, "geometry identifier column %s does not exist in table %s"
// *Cause: The specified table does not contain a GID column.
// *Action: Confirm that the GID column name was correctly specified and
// that it exists in the specified table.
/
13265, 00000, "geometry identifier column %s in table %s is not of type NUMBER"
// *Cause: GID column is not of type NUMBER.
// *Action: Alter the table definition such that the column containing the
// geometry identifier (GID) is of type NUMBER.
/
13266, 00000, "error inserting data into table %s"
// *Cause: An OCI error occurred, or the user has insufficient quota in the
// active tablespace, or the rollback segments are too small.
// *Action: There should be an accompanying error message that
// indicates the cause of the problem. Take appropriate action
// to correct the indicated problem.
/
13267, 00000, "error reading data from layer table %s"
// *Cause: There was an error reading the geometry data from the
// <layer>_SDOGEOM table.
// *Action: Verify that <layer>_SDOGEOM and <layer>_SDODIM exist. If they do
// exist, run VALIDATE_LAYER_WITH_CONTEXT on the specified layer.
/
13268, 00000, "error obtaining dimension from USER_SDO_GEOM_METADATA"
// *Cause: There is no entry in the USER_SDO_GEOM_METADATA view for the specified
// geometry table.
// *Action: Insert an entry for the destination geometry table with
// the correct dimension information.
/
13269, 00000, "internal error [%s] encountered when processing geometry table"
// *Cause: An internal error occurred.
// *Action: Contact Oracle Support Services with the exact error message text.
/
13270, 00000, "OCI error \n%s"
// *Cause: An OCI error occurred while processing the layer or geometry tables.
// *Action: Take the appropriate steps to correct the OCI-specific error.
/
13271, 00000, "error allocating memory for geometry object"
// *Cause: Insufficient memory.
// *Action: Make more memory available to the current session/process.
/
13272, 00000, "geometric object %s in table %s is invalid"
// *Cause: The specified object failed the geometric integrity checks
// performed by the validation function.
// *Action: Check the Oracle Spatial documentation for information about the
// geometric integrity checks performed by VALIDATE_GEOMETRY_WITH_CONTEXT
// and correct the geometry definition if required.
/
13273, 00000, "dimension metadata table %s does not exist"
// *Cause: The <layer>_SDODIM table does not exist.
// *Action: Verify that the specified layer name is correct and that the
// <layer>_SDODIM table exists in the current schema.
/
13274, 00000, "operator invoked with non-compatible SRIDs"
// *Cause: A spatial operator was invoked with a window geometry with an SRID
// but the layer has no SRID; or the window has no SRID but the
// layer has an SRID.
// *Action: Ensure that the layer and window both have an SRID or that they
// both do not have an SRID.
/
13275, 00000, "spatial index creation failure on unsupported type"
// *Cause: An attempt was made to create a spatial index on a column
// that was not of type SDO_GEOMETRY.
// *Action: A spatial index can only be created on a column of type
// SDO_GEOMETRY. Ensure that the indexed column is of type SDO_GEOMETRY.
/
13276, 00000, "internal error [%s] in coordinate transformation "
// *Cause: OCI internal error.
// *Action: Contact Oracle Support Services with the exact error message text.
/
13278, 00000, "failure to convert SRID to native format"
// *Cause: OCI internal error.
// *Action: Contact Oracle Support Services with the exact error message text.
/
13281, 00000, "failure in execution of SQL statement to retrieve WKT"
// *Cause: OCI internal error, or SRID does not match a table entry.
// *Action: Check that a valid SRID is being used.
/
13282, 00000, "failure on initialization of coordinate transformation"
// *Cause: Parsing error on source or destination coordinate system WKT, or
// incompatible coordinate systems.
// *Action: Check the validity of the WKT for table entries, and check if the
// requested transformation is valid.
/
13283, 00000, "failure to get new geometry object for conversion in place"
// *Cause: OCI internal error.
// *Action: Contact Oracle Support Services with the exact error message text.
/
13284, 00000, "failure to copy geometry object for conversion in place"
// *Cause: OCI internal error.
// *Action: Contact Oracle Support Services with the exact error message text.
/
13285, 00000, "Geometry coordinate transformation error"
// *Cause: A coordinate pair was out of valid range for a conversion/projection.
// *Action: Check that data to be transformed is consistent with the desired
// conversion/projection.
/
13287, 00000, "can't transform unknown gtype"
// *Cause: A geometry with a gtype of <= 0 was specified for transformation.
// Only a gtype >= 1 is allowed.
// *Action: Check the Oracle Spatial documentation for SDO_GTYPE values, and
// specify a value whose last digit is 1 or higher.
/
13288, 00000, "point coordinate transformation error"
// *Cause: An internal error occurred while transforming points.
// *Action: Check the accompanying error messages.
/
13290, 00000, "the specified unit is not supported"
// *Cause: An Oracle Spatial function was called with an unknown UNIT value.
// *Action: Check Spatial documentation for the supported units, and call the
// function with the correct UNIT parameter.
/
13291, 00000, "conversion error between the specified unit and standard unit"
// *Cause: Cannot convert the specified unit from/to standard unit
// for linear distance, angle, or area.
// *Action: Check the unit specification and respecify it.
/
13292, 00000, "incorrect ARC_TOLERANCE specification"
// *Cause: When a SDO_BUFFER or SDO_AGGR_BUFFER function is called on a
// geodetic geometry, or SDO_ARC_DENSIFY is called, ARC_TOLERANCE
// must be specified, and it should not be less than the tolerance
// specified for the geometry.
// *Action: Check the ARC_TOLERANCE specification and ensure that it is correct.
/
13293, 00000, "cannot specify unit for geometry without a georeferenced SRID"
// *Cause: An Oracle Spatial function with a UNIT parameter was called on a geometry
// without a georeferenced SRID.
// *Action: Ensure that spatial functions with UNIT parameters are only
// called on geometries with georeferenced SRIDs.
/
13294, 00000, "cannot transform geometry containing circular arcs"
// *Cause: An attempt was made to transform a 3-point representation of
// a circular arc without distortion.
// *Action: Ensure that a geometry does not contain circular arcs.
/
13295, 00000, "geometry objects are in different coordinate systems"
// *Cause: An Oracle Spatial function was called with two geometries that have different
// SRIDs.
// *Action: Transform geometry objects to be in the same coordinate system and
// call the spatial function.
/
13296, 00000, "incorrect coordinate system specification"
// *Cause: Wrong numbers in WKT for Earth radius or flattening for the
// current SRID.
// *Action: Check WKT in the MDSYS.CS_SRS table for Earth radius and inverse flattening.
/
13300, 00000, "single point transform error"
// *Cause: Low-level coordinate transformation error trap.
// *Action: Check the accompanying error messages.
/
13303, 00000, "failure to retrieve a geometry object from a table"
// *Cause: OCI internal error.
// *Action: Contact Oracle Support Services with the exact error message text.
/
13304, 00000, "failure to insert a transformed geometry object in a table"
// *Cause: OCI internal error.
// *Action: Contact Oracle Support Services with the exact error message text.
/
13330, 00000, "invalid MASK"
// *Cause: The MASK passed to the RELATE function is not valid.
// *Action: Verify that the mask is not NULL. See the Oracle Spatial documentation
// for a list of supported masks.
/
13331, 00000,"invalid LRS segment"
// *Cause: The given LRS segment was not a valid line string.
// *Action: A valid LRS geometric segment is a line string geometry in Oracle
// Spatial. It could be a simple or compound line string
// (made of lines or arcs, or both). The dimension information must
// include the measure dimension as the last element in the Oracle Spatial
// metadata. Currently, the number of dimensions for an LRS segment must
// be greater than 2 (x/y or longitude/latitude, plus measure)
/
13332, 00000,"invalid LRS point"
// *Cause: The specified LRS point was not a point geometry with measure information.
// *Action: Check the given point geometry. A valid LRS point is a point
// geometry in Oracle Spatial with an additional dimension for measure.
/
13333, 00000, "invalid LRS measure"
// *Cause: The given measure for linear referencing was out of range.
// *Action: Redefine the measure.
/
13334, 00000, "LRS segments not connected"
// *Cause: The specified geometric segments are not connected.
// *Action: Check the start/end points of the given geometric segments.
/
13335, 00000, "LRS measure information not defined"
// *Cause: The measure information of a geometric segment was
// not assigned (IS NULL).
// *Action: Assign/define the measure information. An LRS geometric segment
// is defined if its start and end measure are assigned (non-null).
/
13336, 00000, "failure in converting standard diminfo/geometry to LRS dim/geom"
// *Cause: There is no room for the measure dimension in the given diminfo, or
// the specified standard geometry is not a point a line string.
// *Action: Check if the diminfo dimensions are less than 3 or if the
// geometry type is point or line string.
/
13337, 00000, "failure in concatenating LRS polygons"
// *Cause: Referencing system (LRS) concatenation involving LRS polygons is not supported.
// *Action: Check the geometry and element types to ensure that the
// concatenate operation is not called with a polygon type.
/
13338, 00000, "failure in reversing LRS polygon/collection geometry"
// *Cause: Reversing a referencing system (LRS) polygon or collection geometry
// produced an invalid geometry.
// *Action: Check the geometry type to ensure that this operation is
// called on non-polygon geometries.
/
13339, 00000, "LRS polygon clipping across multiple rings"
// *Cause: Clipping (dynseg) a polygon across multiple rings is not allowed.
// *Action: Polygon clipping is allowed only for a single ring.
/
13340, 00000, "a point geometry has more than one coordinate"
// *Cause: A geometry, specified as being a point, has more than one
// coordinate in its definition.
// *Action: A point has only one coordinate. If this geometry is intended to
// represent a point cluster, line, or polygon, set the
// appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single
// point object, remove the extraneous coordinates from its
// definition.
/
13341, 00000, "a line geometry has fewer than two coordinates"
// *Cause: A geometry, specified as being a line, has fewer than two
// coordinates in its definition.
// *Action: A line must consist of at least two distinct coordinates.
// Correct the geometric definition, or set the appropriate
// SDO_GTYPE or SDO_ETYPE attribute for this geometry.
/
13342, 00000, "an arc geometry has fewer than three coordinates"
// *Cause: A geometry, specified as being an arc, has fewer than three
// coordinates in its definition.
// *Action: An arc must consist of at least three distinct coordinates.
// Correct the geometric definition, or set the appropriate
// SDO_GTYPE or SDO_ETYPE attribute for this geometry.
/
13343, 00000, "a polygon geometry has fewer than four coordinates"
// *Cause: A geometry, specified as being a polygon, has fewer than four
// coordinates in its definition.
// *Action: A polygon must consist of at least four distinct coordinates.
// Correct the geometric definition, or set the appropriate
// SDO_GTYPE or SDO_ETYPE attribute for this geometry.
/
13344, 00000, "an arcpolygon geometry has fewer than five coordinates"
// *Cause: A geometry, specified as being an arcpolygon, has fewer than five
// coordinates in its definition.
// *Action: An arcpolygon must consist of at least five coordinates.
// An arcpolygon consists of an ordered sequence of arcs,
// each of which must be described using three coordinates.
// Since arcs are connected the end-point of the first is the
// start of the second and does not have to be repeated.
// Correct the geometric definition, or set the appropriate
// SDO_GTYPE or SDO_ETYPE attribute for this geometry.
/
13345, 00000, "a compound polygon geometry has fewer than five coordinates"
// *Cause: A geometry, specified as being a compound polygon, has fewer
// than five coordinates in its definition.
// *Action: A compound polygon must contain at least five coordinates.
// A compound polygon consists of at least one arc and
// one line, each of which must be described using three
// and at least two distinct coordinates respectively.
// Correct the geometric definition, or set the appropriate
// SDO_GTYPE or SDO_ETYPE attribute for this geometry.
/
13346, 00000, "the coordinates defining an arc are collinear"
// *Cause: Invalid definition of an arc. An arc is defined using three
// non-collinear coordinates.
// *Action: Alter the definition of the arc, or set the SDO_ETYPE or
// SDO_GTYPE to the line type.
/
13347, 00000, "the coordinates defining an arc are not distinct"
// *Cause: Two or more of the three points defining an arc are the same.
// *Action: Alter the definition of the arc to ensure that three distinct
// coordinate values are used.
/
13348, 00000, "polygon boundary is not closed"
// *Cause: The boundary of a polygon does not close.
// *Action: Alter the coordinate values or the definition of the
// SDO_GTYPE or SDO_ETYPE attribute of the geometry.
/
13349, 00000, "polygon boundary crosses itself"
// *Cause: The boundary of a polygon intersects itself.
// *Action: Correct the geometric definition of the object.
/
13350, 00000, "two or more rings of a complex polygon touch"
// *Cause: The inner or outer rings of a complex polygon
// touch.
// *Action: All rings of a complex polygon must be disjoint.
// Correct the geometric definition of the object.
/
13351, 00000, "two or more rings of a complex polygon overlap"
// *Cause: The inner or outer rings of a complex polygon
// overlap.
// *Action: All rings of a complex polygon must be disjoint.
// Correct the geometric definition of the object.
/
13352, 00000, "the coordinates do not describe a circle"
// *Cause: The set of coordinates used to describe a circle are
// incorrect.
// *Action: Confirm that the set of coordinates actually represent points
// on the circumference of a circle.
/
13353, 00000, "ELEM_INFO_ARRAY not grouped in threes"
// *Cause: The ELEM_INFO_ARRAY in an SDO_GEOMETRY definition has more or fewer
// elements than expected.
// *Action: Confirm that the number of elements in ELEM_INFO_ARRAY is
// divisible by 3.
/
13354, 00000, "incorrect offset in ELEM_INFO_ARRAY"
// *Cause: The offset field in ELEM_INFO_ARRAY of an SDO_GEOMETRY definition
// references an invalid array subscript in SDO_ORDINATE_ARRAY.
// *Action: Confirm that the offset is a valid array subscript in
// SDO_ORDINATE_ARRAY.
/
13355, 00000, "SDO_ORDINATE_ARRAY not grouped by number of dimensions specified"
// *Cause: The number of elements in SDO_ORDINATE_ARRAY is not a multiple of
// the number of dimensions supplied by the user.
// *Action: Confirm that the number of dimensions is consistent with data
// representation in SDO_ORDINATE_ARRAY.
/
13356, 00000, "adjacent points in a geometry are redundant"
// *Cause: There are repeated points in the sequence of coordinates.
// *Action: Remove the redundant point.
/
13357, 00000, "extent type does not contain 2 points"
// *Cause: Extent type should be represented by two points:
// lower left and upper right.
// *Action: Confirm that there are only two points for an extent type.
/
13358, 00000, "circle type does not contain 3 points"
// *Cause: Circle type should be represented by three distinct points
// on the circumference.
// *Action: Confirm that there are only three points for a circle type.
/
13359, 00000, "extent does not have an area"
// *Cause: The two points representing the extent are identical.
// *Action: Confirm that the two points describing the extent type are distinct.
/
13360, 00000, "invalid subtype in a compound type"
// *Cause: This subtype is not allowed within the ETYPE specified.
// *Action: Check the Oracle Spatial documentation for type definitions.
/
13361, 00000, "not enough sub-elements within a compound ETYPE"
// *Cause: The compound type declare more sub-elements than actually defined.
// *Action: Confirm that the number of sub-elements is consistent with
// the compound type declaration.
/
13362, 00000, "disjoint sub-element in a compound polygon"
// *Cause: Compound polygon must describe an enclosed area.
// *Action: Confirm that all sub-elements are connected.
/
13363, 00000, "no valid ETYPE in the geometry"
// *Cause: None of the ETYPEs within the geometry is supported.
// *Action: Confirm that there is at least one valid ETYPE.
/
13364, 00000, "layer dimensionality does not match geometry dimensions"
// *Cause: The spatial layer had a geometry with a different dimensions than the
// dimensions specified for the layer.
// *Action: Ensure that all geometries in a layer have the same dimensions
// and that they match the dimensions in the SDO_DIM_ARRAY object
// for the layer in the USER_SDO_GEOM_METADATA view.
/
13365, 00000, "layer SRID does not match geometry SRID"
// *Cause: The spatial layer had a geometry with a different SRID than the
// SRID specified for the layer.
// *Action: Ensure that all geometries in a layer have the same SRID and that the
// SRIDs match the SRID for the layer in the USER_SDO_GEOM_METADATA view.
/
13366, 00000, "invalid combination of interior exterior rings"
// *Cause: In an Oracle Spatial geometry, interior and exterior rings were not
// used consistently.
// *Action: Ensure that the interior rings corresponding to an exterior
// ring follow the exterior ring in the ordinate array.
/
13367, 00000, "wrong orientation for interior/exterior rings"
// *Cause: In an Oracle Spatial geometry, the exterior and/or interior rings are not
// oriented correctly.
// *Action: Be sure that the exterior rings are oriented counterclockwise and the
// interior rings are oriented clockwise.
/
13368, 00000, "simple polygon type has more than one exterior ring"
// *Cause: In a polygon geometry there is more than one exterior ring.
// *Action: Set the type to be multipolygon if more than one exterior ring is
// present in the geometry.
/
13369, 00000, "invalid value for etype in the 4-digit format"
// *Cause: A 4-digit etype for a non-polygon type element is used, or
// the orientation is not a valid orientation for interior/exterior
// rings of the polygon.
// *Action: Correct the geometry definition.
/
13370, 00000, "failure in applying 3D LRS functions"
// *Cause: Only non-geodetic 3D line string geometries (made of line segments)
// are supported for 3D LRS functions.
// *Action: Check the geometry and element types and the SRID values.
/
13371, 00000, "invalid position of measure dimension"
// *Cause: LRS measure dimension has to be after spatial dimensions.
// The position has to be either 3rd or 4th in the dim_info_array.
// *Action: Check the geometry's gtype and its position in the dim_info_array.
/
13372, 00000, "failure in modifying metadata for a table with spatial index "
// *Cause: Modifying the metadata after the index is created will cause an
// inconsistency between the geometry's gtype and diminfo.
// *Action: Modify (or Prepare) metadata before creating an index on the
// SDO_GEOMETRY column.
/
13373, 00000, "invalid line segment in geodetic data"
// *Cause: A geodetic line segment was not less than half of a great circle.
// *Action: Densify the line by adding points.
/
13374, 00000, "SDO_MBR not supported for geodetic data"
// *Cause: The SDO_MBR functionality is not supported for geodetic data.
// *Action: Find an alternative function that can be used in this context.
/
13375, 00000, "the layer is of type [%s] while geometry inserted has type [%s]"
// *Cause: The layer has a type that is different or inconsistent with the
// type of the current geometry.
// *Action: Change the geometry type to agree with the layer type, or change
// the layer type to agree with the geometry type.
/
13376, 00000, "invalid type name specified for layer_gtype parameter"
// *Cause: An invalid type name is specified for the layer_gtype constraint.
// *Action: See the Spatial documentation for of valid keywords
// that can be used in defining a layer_gtype constraint.
/
13377, 00000, "invalid combination of elements with orientation"
// *Cause: An element of the geometry had orientation specified while some
// other element had no orientation specified (4-digit etype).
// *Action: Ensure that all of the polygon elements have orientation specified
// using the 4-digit etype notation.
/
13378, 00000, "invalid index for element to be extracted"
// *Cause: An invalid (or out of bounds) index was specified for extracting
// an element from a geometry.
// *Action: Ensure that the parameters to the extract function are in the
// valid range for the geometry.
/
13379, 00000, "invalid index for sub-element to be extracted"
// *Cause: An invalid (or out of bounds) index was specified for extracting
// a sub-element from a geometry.
// *Action: Ensure that the parameters to the extract function are in the
// valid range for the geometry.
/
13380, 00000, "network not found"
// *Cause: The specified network was not found in the network metadata.
// *Action: Insert the network information in the USER_SDO_NETWORK_METADATA
// view.
/
13381, 00000, "table:%s not found in network:%s"
// *Cause: The specified table was not found in the network metadata.
// *Action: Insert the table information in the USER_SDO_NETWORK_METADATA view.
/
13382, 00000, "geometry metadata (table:%s column:%s) not found in spatial network:%s"
// *Cause: The specified geometry metadata was not found in the spatial
// network metadata.
// *Action: Insert the spatial metadata information in the
// USER_SDO_NETWORK_METADATA view.
/
13383, 00000, "inconsistent network metadata: %s"
// *Cause: There was an inconsistency between the network metadata
// and the node/link information.
// *Action: Check the network metadata and the node/link information.
/
13384, 00000, "error in network schema: %s"
// *Cause: The network table(s) did not have required column(s)
// *Action: Check the network schema.
/
13385, 00000, "error in network manager: [%s]"
// *Cause: There was an internal error in network manager.
// *Action: Contact Oracle Customer Support for more help.
/
13386, 00000, "commit/rollback operation error: [%s]"
// *Cause: The index-level changes were not fully incorporated as part of
// the commit or rollback operation.
// *Action: Correct the specified error and use the following statement:
// ALTER INDEX <index-name> PARAMETERS ('index_status=synchronize');
/
13387, 00000, "sdo_batch_size for array inserts should be in the range [%d,%d]"
// *Cause: The specified value for sdo_batch_size was too high or too low.
// *Action: Change the value to be in the specified range.
/
13388, 00000, "invalid value for dst_spec parameter"
// *Cause: The dst_spec parameter was specified in the wrong format.
// *Action: Check the documentation for this parameter.
/
13389, 00000, "unable to compute buffers or intersections in analysis function"
// *Cause: There was an internal error in computing the buffers or
// intersections in the specified spatial analysis function.
// *Action: Modify the tolerance value in the USER_SDO_GEOM_METADATA
// view before invoking the spatial analysis function.
/
13390, 00000, "error in spatial analysis and mining function: [%s]"
// *Cause: There was an internal error in the specified analysis function.
// *Action: Contact Oracle Customer Support for more help.
/
/ 13391 - 13499 for all GeoRaster errors
/
/ 13391-13398 GeoRaster management errors
/ 13399-13429 general pl/sql errors -- schema and user errors
/ 13430-13479 all XML errors and other data related errors -- data errors
/ 13480-13490 external format related errors -- external data errors
/ 13491-13498 GeoRaster internal errors -- code errors and rdbms errors
/
13391, 00000, "%s"
// *Cause: An attempt was made to violate GeoRaster management restrictions.
// *Action: Check the documentation for more detailed information.
/
13392, 00000, "status report error: %s"
// *Cause: There was an error on status report related operation.
// *Action: Check the error message for details.
/
13393, 00000, "null or invalid %s parameter"
// *Cause: The operation failed because the input parameter was null or
// invalid.
// *Action: Correct the parameter and try again.
/
13397, 00000, "different dimension sizes in the input GeoRaster objects"
// *Cause: The two input GeoRaster objects had different dimension sizes.
// *Action: Check the documentation and ensure that the dimension size is the
// same for both input GeoRaster objects.
/
13398, 00000, "invalid expression parameter: %s"
// *Cause: The expression parameter was not a valid math expression.
// *Action: Check the documentation and ensure that the expression parameter is
// correct.
/
13399, 00000, "invalid condition parameter: %s"
// *Cause: The condition parameter was not a valid boolean expression.
// *Action: Check the documentation and ensure that the condition parameter is
// correct.
/
13400, 00000, "duplicate entry for %s in USER_SDO_GEOR_SYSDATA view"
// *Cause: The current operation caused a duplicate RASTER_DATA_TABLE and
// RASTER_ID combination to be inserted into the
// USER_SDO_GEOR_SYSDATA view.
// *Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID combination to
// be inserted into the USER_SDO_GEOR_SYSDATA view is unique.
/
13401, 00000, "duplicate entry for %s in USER_SDO_GEOR_SYSDATA view"
// *Cause: The RASTER_DATA_TABLE and RASTER_ID columns contained the same
// information in two or more rows in the USER_SDO_GEOR_SYSDATA view.
// *Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID columns in the
// USER_SDO_GEOR_SYSDATA view contain the correct information, and
// that the value pair is unique for each row.
/
13402, 00000, "the rasterType is null or not supported"
// *Cause: The specified rasterType was null or not supported.
// *Action: Check the documentation for the rasterType number and/or
// formats supported by GeoRaster.
/
13403, 00000, "invalid rasterDataTable specification: %s"
// *Cause: The raster data table name specified for a GeoRaster
// object was not unique among raster data table names
// in the database; or for a GeoRaster object, which was
// not empty and was not blank, or was used as an output
// GeoRaster object, one or more of the following requirements
// were not met.
// The raster data table must:
// - Exist.
// - Be visible in the current schema.
// - Be defined in the same schema as the GeoRaster data table.
// - Be an object table of SDO_RASTER type or a relational table
// with the same columns as the attributes of the SDO_RASTER type.
// *Action: Check the rasterDataTable specification and ensure that all
// relevant raster data table requirements are met.
/
13404, 00000, "invalid ultCoordinate parameter"
// *Cause: The ultCoordinate array parameter had the wrong length or
// contained an invalid value.
// *Action: Check the documentation and ensure that the ultCoordinate
// parameter is correct.
/
13405, 00000, "null or invalid dimensionSize parameter"
// *Cause: The dimensionSize array parameter was NULL, had the wrong length,
// or contained an invalid value.
// *Action: Check the documentation and ensure that the dimensionSize
// parameter is correct.
/
13406, 00000, "null or invalid GeoRaster object for output"
// *Cause: The GeoRaster object for output was NULL or invalid.
// *Action: Ensure that the GeoRaster object for output has been
// initialized properly.
/
13407, 00000, "invalid storage parameter%s"
// *Cause: The storage parameter contained an invalid specification.
// *Action: Check the documentation and ensure that the storage parameter is
// correct.
/
13408, 00000, "invalid blockSize storage parameter"
// *Cause: The blockSize storage parameter had the wrong length or
// contained an invalid value.
// *Action: Check the documentation and ensure that the blockSize storage
// parameter is correct.
/
13409, 00000, "null or invalid pyramidLevel parameter"
// *Cause: The specified pyramidLevel parameter was NULL or invalid.
// *Action: Ensure that the pyramidLevel parameter specifies a valid pyramid
// level value for the GeoRaster object.
/
13410, 00000, "invalid layerNumbers or bandNumbers parameter"
// *Cause: The layerNumbers or bandNumbers parameter was invalid.
// *Action: Check the documentation and ensure that the layerNumbers or
// bandNumbers parameter is valid.
/
13411, 00000, "subset results in null data set"
// *Cause: The intersection of cropArea and source GeoRaster object was NULL.
// *Action: Check the documentation and ensure that the cropArea parameter
// is correct.
/
13412, 00000, "invalid scale parameter%s"
// *Cause: The scale parameter contained an invalid specification.
// *Action: Check the documentation and ensure that the scale parameter is
// correct.
/
13413, 00000, "null or invalid resampling parameter"
// *Cause: The resampling parameter was NULL or invalid.
// *Action: Check the documentation and ensure that the resampling parameter
// is correct.
/
13414, 00000, "invalid pyramid parameter"
// *Cause: The pyramid parameter was invalid.
// *Action: Check the documentation and ensure that the pyramid parameter is
// correct.
/
13415, 00000, "invalid or out of scope point specification"
// *Cause: The point position specified by the <ptGeom, layerNumber> or
// <rowNumber, colNumber, bandNumber> parameter combination was
// invalid or out of scope.
// *Action: Ensure that the parameters specify a valid point that is or can
// be translated into a cell position inside the cell space of the
// GeoRaster object.
/
13416, 00000, "invalid geometry parameter"
// *Cause: The geometry parameter did not specify a valid single-point
// geometry.
// *Action: Specify a valid single-point geometry.
/
13417, 00000, "null or invalid layerNumber parameter"
// *Cause: The layerNumber parameter was null or out of scope.
// *Action: Specify a valid layerNumber parameter.
/
13418, 00000, "null or invalid parameter(s) for set functions"
// *Cause: A parameter for set metadata operations was null or invalid.
// *Action: Check the documentation for information about the parameters.
/
13419, 00000, "cannot perform mosaic or append operation: %s"
// *Cause: An attempt to perform a mosaic or append operation failed.
// *Action: Check the error message for details.
/
13420, 00000, "the SRID of the geometry parameter was not null"
// *Cause: The input geometry was not in the GeoRaster cell space,
// which had a NULL SRID value.
// *Action: Ensure that the geometry parameter has a NULL SRID.
/
13421, 00000, "NULL or invalid cell value"
// *Cause: The cell value was NULL or out-of-scope.
// *Action: Ensure that the cell value is not NULL and is in the range as
// designated by the cellDepth definition of the specified GeoRaster
// object.
/
13422, 00000, "invalid model coordinate parameter"
// *Cause: The model coordinate array parameter had the wrong length
// or had NULL ordinate element(s).
// *Action: Ensure that the model coordinate parameter is valid.
/
13423, 00000, "invalid cell coordinate parameter"
// *Cause: The cell coordinate array parameter had the wrong length
// or had NULL ordinate element(s).
// *Action: Ensure that the cell coordinate parameter is valid.
/
13424, 00000, "the GeoRaster object is not spatially referenced"
// *Cause: The GeoRaster object was not spatially referenced.
// *Action: Ensure that the GeoRaster object is spatially referenced.
/
13425, 00000, "invalid background filling value parameter"
// *Cause: The background filling value parameter was invalid either because
// the array had the wrong size or because some of the element values
// were invalid.
// *Action: Ensure that the parameter that specifies the background filling
// value is valid. The size of the array must equal either 1
// (the value is for all bands) or the exact band dimension size.
// The element values must be valid cell values as determined by
// the cell depth.
/
13426, 00000, "invalid window parameter"
// *Cause: The specified window parameter was invalid.
// *Action: Specify a valid window parameter. Check the documentation
// for details.
/
13427, 00000, "invalid bitmap mask"
// *Cause: The bitmap mask was not a valid 1-bit GeoRaster object, or it had
// the wrong dimension sizes.
// *Action: Ensure that the bitmap mask is a valid 1-bit GeoRaster object with
// only one band, and the row and column dimension sizes of the
// bitmap mask are the same as those of the target GeoRaster object.
/
13428, 00000, "invalid modelCoordinateLocation"
// *Cause: The program [or user] specified a modelCoordinateLocation
// that is not supported, or the modelCoordinateLocation of
// the GeoRaster object was wrong.
// *Action: Set or specify the modelCoordinateLocation to be
// CENTER (0) or UPPERLEFT (1).
/
13429, 00000, "invalid xCoefficients or yCoefficients parameter(s)"
// *Cause: An attempt to perform a georeference operation failed.
// Possible reasons include xCoefficients or yCoefficients having
// the wrong number of coefficients or invalid coefficients.
// *Action: Check the documentation for supported coefficient specifications.
/
13430, 00000, "the GeoRaster object has null attribute(s)"
// *Cause: The metadata or rasterType of the GeoRaster object was null.
// *Action: This object may only be used as an output parameter of
// procedures or functions. It is not valid for other purposes.
/
13431, 00000, "GeoRaster metadata rasterType error"
// *Cause: The rasterType in the metadata of the GeoRaster object
// was inconsistent with the GeoRaster rasterType attribute.
// *Action: Ensure that the rasterType in the metadata of the GeoRaster object
// and the GeoRaster rasterType attribute have the same value.
/
13432, 00000, "NULL or invalid blankCellValue"
// *Cause: The blankCellValue element could not be found in the metadata of
// a blank GeoRaster object, or the specified blankCellValue element
// value was NULL or invalid.
// *Action: Call the SDO_GEOR.setBlankCellValue package to add blankCellValue
// to the metadata whenever the isBlank element value is TRUE, and
// ensure that the specified blankCellValue element value is not NULL
// and is in the range as designated by the cellDepth definition of
// the GeoRaster object.
/
13433, 00000, "GeoRaster metadata default RGB error"
// *Cause: At least one of the defaultRed, defaultGreen, and defaultBlue
// values (logical layer numbers) was zero, negative, or out of range.
// *Action: Check the documentation for details.
/
13434, 00000, "GeoRaster metadata cellRepresentation error"
// *Cause: The cellRepresentation type was not supported.
// *Action: Check the documentation for supported cellRepresentation types.
/
13435, 00000, "GeoRaster metadata dimension inconsistent"
// *Cause: The specification of dimensions or totalDimensions
// was inconsistent with rasterType, or vice versa.
// *Action: Ensure that the dimension specifications are consistent.
/
13436, 00000, "GeoRaster metadata dimensionSize error"
// *Cause: Either the dimensionSize for each dimension was not specified,
// or an extraneous dimensionSize was specified.
// *Action: Add a dimsenionSize for each dimension of the GeoRaster
// object and delete extra dimensionSize elements.
/
13437, 00000, "GeoRaster metadata blocking error"
// *Cause: Either the wrong block number(s) or block size(s) along dimensions
// were specified, or the block numbers and sizes when taken
// together were not consistent.
// *Action: Check the documentation for details.
/
13438, 00000, "GeoRaster metadata pyramid type error"
// *Cause: The specified pyramid type was not supported.
// *Action: Check the documentation for supported pyramid types.
/
13439, 00000, "GeoRaster metadata pyramid maxLevel error"
// *Cause: The specified maxLevel exceeded the maximum level
// allowed by the specified pyramid type.
// *Action: Check the documentation for supported pyramid types
// and their total level limitations.
/
13440, 00000, "GeoRaster metadata compression type error"
// *Cause: The specified compression type was not supported.
// *Action: Check the documentation for supported compression types.
/
13441, 00000, "GeoRaster metadata SRS error: %s"
// *Cause: The specified error related to the polynomialModel element in
// the spatial reference system (SRS) metadata.
// *Action: Check the documentation and ensure that a valid polynomial
// model is specified.
/
13442, 00000, "GeoRaster object not registered: %s"
// *Cause: There was no SYSDATA entry for the specified GeoRaster object.
// *Action: Ensure that a sysdata entry has been inserted for the specified
// GeoRaster object.
/
13443, 00000, "null or invalid values in %s"
// *Cause: There were NULL or invalid component values in the specified
// metadata.
// *Action: Check the documentation and ensure that all of the component
// values are valid.
/
13444, 00000, "cannot perform mergeLayers operation"
// *Cause: The two GeoRaster objects whose layers are to be combined together
// either had different row or column dimension sizes, or their
// georeferencing information did not match.
// *Action: Ensure that the objects have the same row and column dimension
// sizes. If neither is georeferenced, their ULTCoordinate values
// must be the same. Otherwise, they must be both georeferenced
// and cover the same area in the model space.
/
13445, 00000, "NULL or invalid NODATA value or value range"
// *Cause: There was an invalid NODATA value or value range in the metadata, or
// the specified NODATA value or value range was invalid.
// *Action: Ensure that the NODATA value or value range is not NULL and is
// completely contained in the range as designated by the cellDepth
// definition of the specified GeoRaster object.
/
13446, 00000, "GeoRaster metadata TRS error"
// *Cause: The GeoRaster Temporal Reference System was not supported.
// *Action: Set isReferenced to FALSE.
/
13447, 00000, "GeoRaster metadata BRS error"
// *Cause: The GeoRaster Band Reference System was not supported.
// *Action: Set isReferenced to FALSE.
/
13448, 00000, "GeoRaster metadata BRS error"
// *Cause: The GeoRaster spectral extent specification was incorrect.
// *Action: The MIN value must be less than the MAX value
// in the spectralExtent element.
/
13449, 00000, "GeoRaster metadata ULTCoordinate error"
// *Cause: The GeoRaster rasterInfo ULTCoordinate was not correct.
// *Action: Check the documentation for restrictions.
/
13450, 00000, "GeoRaster metadata layerInfo error"
// *Cause: The GeoRaster had more than one layerInfo element,
// or the layerDimension value was not supported.
// *Action: The current release only supports one layerInfo element;
// layer can only be defined along one dimension,
// and this dimension must be BAND.
/
13451, 00000, "GeoRaster metadata scaling function error"
// *Cause: The scaling function had a zero denominator.
// *Action: Ensure that the scaling function denominator is not zero.
/
13452, 00000, "GeoRaster metadata BIN function error"
// *Cause: The bin function data did not match its type.
// *Action: For EXPLICIT type, provide a binTableName element;
// otherwise, provide a binFunctionData element.
/
13453, 00000, "GeoRaster metadata layer error"
// *Cause: Too many subLayers were defined for the GeoRaster object,
// or layerNumber or layerDimensionOrdinate was not assigned correctly.
// *Action: The total number of logical layers cannot exceed the total number
// of physical layers, and each logical layer must be assigned
// a valid physical layer number following the same order.
// Check the documentation for more details.
/
13454, 00000, "GeoRaster metadata is invalid"
// *Cause: The GeoRaster metadata was invalid against its XML Schema.
// *Action: Run the schemaValidate routine to find the errors.
/
13455, 00000, "GeoRaster metadata TRS error"
// *Cause: The beginDateTime value was later than the endDateTime value.
// *Action: Ensure that the beginDateTime value is not later than the
// endDateTime value.
/
13456, 00000, "GeoRaster cell data error: %s"
// *Cause: There was an error in the original GeoRaster cell data or in the
// cell data of the pyramids.
// *Action: If the error is related to the original GeoRaster cell data, the
// GeoRaster object is invalid and has to be deleted or manually
// repaired. If the error is related to pyramids, delete the pyramids
// and regenerate them.
/
13457, 00000, "bitmap mask cell data error: %s"
// *Cause: There was an error in the cell data of an original bitmap mask
// or in the cell data of the pyramids of a bitmap mask.
// *Action: If the error is related to an original bitmap mask, remove the
// bitmap mask. If the error is related to the pyramids of a bitmap
// mask, delete the pyramids and regenerate them.
/
13458, 00000, "GeoRaster metadata SRS error"
// *Cause: The polynomial model did not match the requirements
// of a rectified GeoRaster object.
// *Action: Check the documentation for the requirements of the
// polynomial model for a rectified GeoRaster object, or
// set isRectified to be false.
/
13459, 00000, "GeoRaster metadata SRS error"
// *Cause: The polynomial model was not an six-parameter transformation,
// or the six-parameter transformation was not valid.
// *Action: Check the documentation and ensure that the polynomial model
// is a valid six-parameter affine transformation.
/
13460, 00000, "GeoRaster metadata SRS error"
// *Cause: The referenced GeoRaster object had a zero model space SRID
// or the specified model space SRID was zero.
// *Action: Set or specify the model space SRID to be a nonzero number.
/
13461, 00000, "the interleaving type is not supported"
// *Cause: The interleaving type of the GeoRaster object was not supported.
// *Action: Check the documentation for the interleaving types
// supported by GeoRaster. Use SDO_GEOR.changeFormatCopy
// to transform the image to a supported interleaving type.
/
13462, 00000, "invalid blocking specification"
// *Cause: The specified blocking configuration was invalid.
// *Action: Check the documentation for the blocking specification supported
// by GeoRaster.
/
13463, 00000, "error retrieving GeoRaster data: %s"
// *Cause: An internal error occurred while retrieving GeoRaster data from
// the database.
// *Action: Check the error message for details.
/
13464, 00000, "error loading GeoRaster data: %s"
// *Cause: An internal error occurred while loading GeoRaster data into the
// database.
// *Action: Check the error message for details.
/
13465, 00000, "null or invalid table or column specification"
// *Cause: The specified table or column did not exist, or the column was not
// a GeoRaster column.
// *Action: Ensure that the specified table exists and the specified column is
// a GeoRaster column.
/
13466, 00000, "format not appropriate for specified compression method: %s"
// *Cause: The operation failed because the GeoRaster object had an
// inappropriate type or format for the specified compression
// method. The GeoRaster type or format is not supported for the
// specified compression.
// *Action: Check the error message for details. Check the documentation for
// the appropriate GeoRaster types and formats for each compression
// method. Use SDO_GEOR.changeFormatCopy to transform the GeoRaster
// object to an appropriate format, or apply another compression
// method.
/
13467, 00000, "unsupported GeoRaster metadata specification: %s"
// *Cause: The GeoRaster metadata specification is not supported.
// *Action: Check the documentation for the supported GeoRaster metadata
// specifications.
/
13468, 00000, "invalid blockMBR"
// *Cause: Invalid blockMBR geometries were stored in the raster data table.
// *Action: Ensure that the blockMBR geometries stored in the raster data table
// are valid, or call the SDO_GEOR.generateBlockMBR() package to
// regenerate the blockMBR geometries.
/
13469, 00000, "cannot perform updateRaster operation"
// *Cause: The data of the source GeoRaster object could not be used to update
// that of the target GeoRaster object.
// *Action: Ensure that the source and the target GeoRaster objects have the
// same cell depth, and that both objects are either georeferenced or
// not georeferenced at all. If both are georeferenced, they should
// be in the same coordinate system and have the same spatial
// resolutions.
/
13470, 00000, "target and source layers or bands mismatched"
// *Cause: The number of specified target layers or bands and source layers
// or bands did not match.
// *Action: When updating layers or bands of a target GeoRaster object to
// reflect the associated layers or bands of the source GeoRaster
// object, specify the same number of layers or bands for both the
// source and the target objects. Check the documentation for details.
/
13471, 00000, "unable to determine the owner of %s"
// *Cause: The owner of the specified raster data table could not be determined.
// *Action: Ensure that the GeoRaster object that refers to the raster data
// table has been registered by inserting the object into a GeoRaster
// table.
/
13472, 00000, "invalid geometry parameter"
// *Cause: The geometry parameter did not specify a valid geometry.
// *Action: Specify a valid 2D or 3D geometry. If the model SRID is null or
// indicates a 2D coordinate system, the geometry must be 2D. If the
// model SRID indicates a 3D coordinate system, the geometry must
// either be a 3D geometry or a 2D geometry that can be converted to
// 3D with the specified vertical axis (or vertical SRID) and
// ellipsoidal parameters.
/
13473, 00000, "invalid rasterSpec parameter"
// *Cause: The rasterSpec parameter contained an invalid specification.
// *Action: Check the documentation and ensure that the rasterSpec
// parameter contains only valid keywords and values.
/
13474, 00000, "invalid rasterDataTable name: %s"
// *Cause: The rasterDataTable name was not a valid nonquoted identifier,
// it contained a period separator, or not all of the alphanumeric
// characters were uppercase.
// *Action: Ensure that the table name is a valid nonquoted identifier
// without any period separators, and that all the alphanumeric
// characters are uppercase.
/
13475, 00000, "invalid GeoRaster object for output"
// *Cause: The output GeoRaster object had the same RASTER_DATA_TABLE
// and RASTER_ID combination as that of an input GeoRaster object.
// *Action: Ensure that the output GeoRaster object is different from any
// of the input GeoRaster objects.
/
13476, 00000, "invalid or out of scope point specification"
// *Cause: The point position specified by the point geometry parameter or
// the rowNumber/colNumber parameter combination was null or out of
// scope.
// *Action: Ensure that the parameters specify a valid point that translates
// or can be translated into a cell position inside the cell space
// of the GeoRaster object.
/
13477, 00000, "invalid GCP georeferencing specification: %s"
// *Cause: The specified functional fitting method was not supported,
// the number of GCPs was insufficient, some GCPs were invalid,
// or the distribution of the GCPs led to no solution or
// an unstable solution.
// *Action: Check the GeoRaster documentation for the supported
// functional fitting methods and the requirements of GCPs.
/
13478, 00000, "the target SRID is the same as the source GeoRaster object's SRID"
// *Cause: The target SRID was not different from the source GeoRaster object's SRID.
// *Action: Specify a different valid SRID for the target GeoRaster object.
/
13479, 00000, "cannot reproject"
// *Cause: Reprojection from source to destination projection produced
// a large distortion.
// *Action: Check the destination projection and ensure that it is suitable for
// the area covered by the source GeoRaster object. Check the GeoRaster
// documentation for more information about reprojection.
/
13480, 00000, "the Source Type is not supported"
// *Cause: The specified source type was not supported.
// *Action: Check the documentation for the source types (such as
// FILE and HTTP) supported by GeoRaster.
/
13481, 00000, "the destination type is not supported"
// *Cause: The specified destination type was not supported.
// *Action: Check the documentation for the destination types (such as
// FILE) supported by GeoRaster.
/
13482, 00000, "GeoRaster object is not initialized for the image"
// *Cause: No GeoRaster object has been initialized for the specified image.
// *Action: Initialize a GeoRaster object to hold this image before loading
// it into the database. Check the documentation for details.
/
13483, 00000, "insufficient memory for the specified GeoRaster data"
// *Cause: There was insufficient memory to hold the specified GeoRaster data
// for this operation.
// *Action: Use SDO_GEOR.subset to isolate a subset of the GeoRaster data, or
// reblock the GeoRaster data into smaller sized blocks. Check the
// documentation for details.
/
13484, 00000, "the file format or compression type is not supported: %s"
// *Cause: The file format or compression type was not supported.
// *Action: Check the documentation for formats that are currently supported
// by GeoRaster.
/
13485, 00000, "error occurred during compression or decompression: %s"
// *Cause: The operation could not be completed because an error occurred
// during compression or decompression. Check the error message
// for details.
// *Action: Check that the GeoRaster object is valid, that its metadata
// is valid for the specified compression format, and that valid
// parameters are passed into the compression or decompression
// operation.
/
13486, 00000, "invalid or insufficient GeoTIFF metadata to georeference the GeoRaster object: %s"
// *Cause: The GeoTIFF metadata of the specified input image contained invalid
// or insufficient information to georeference the GeoRaster object.
// *Action: Check the error message for details.
/
13487, 00000, "SRID not found for source coordinate system metadata"
// *Cause: No SRID was found in the Oracle Spatial CS_SRS table to match the
// source coordinate system metadata.
// *Action: Add a user-defined coordinate reference system for this coordinate
// system, as explained in the Oracle Spatial documentation.
/
13488, 00000, "cannot perform transformation: %s"
// *Cause: An attempt to perform a transformation operation failed.
// *Action: Check the error message for details.
/
13489, 00000, "GeoRaster operation failed: %s"
// *Cause: There was an error in the GeoRaster operation, parameters,
// or compression types.
// *Action: Check the error message and take the appropriate action or contact
// Oracle Support Services for further assistance.
/
13495, 00000, "The Oracle Spatial and Graph Option is needed for using this feature."
// *Cause: The specified option is not installed or enabled.
// *Action: Consider purchasing and installing the missing option or enabling the
// option if it was already installed.
/
13497, 00000, "%s"
// *Cause: This is an internal GeoRaster error.
// *Action: Contact Oracle Support Services. You may want to ensure
// that the GeoRaster object is valid before you do so.
/
13498, 00000, "%s"
// *Cause: An error related to an external plugin was encountered in the
// GeoRaster component.
// *Action: Check the documentation for the external plugin, or contact
// the plugin provider and supply the exact error text.
/
13499, 00000, "%s"
// *Cause: This is an internal Oracle Spatial error.
// *Action: Contact Oracle Support Services.
/
/=============================================================================
/ 13500 - 13999 reserved for Server Manageability Layer
/
/ 13500-13599 reserved for AWR
/ 13600-13699 reserved for the adv fmwk.
/ 13700-13749 reserved for the ADDM, ASH, general manageability
/ 13750-13799 reserved for sql tune and sql tune set
/ 19371-19390 reserved for sql tune and sql tune set (2)
/ 13800-13849 reserved for the SQL Tuning Base and for SQL profiles.
/ 13850-13899 reserved for end-to-end tracing
/ 13900-13949 reserved for threshold-based alerts
/ 13950-13969 reserved for MMON infrastructure
/ 13970-13999 reserved for the common reporting framework (KER)
/
/ ===============================================================
/ NOTE: NEXT CHUNK OF MESSAGES RESERVED BETWEEN 15500 AND 15999
/ If your project belongs to the Server Manageability layer
/ please allocate yourself a chunk in that range.
/ ================================================================
/
/=============================================================================
/
/ 13500 - 13599 reserved for AWR
/
13500, 00000, "SYSAUX DATAFILE clause specified more than once"
// *Cause: The CREATE DATABASE command contains more than one SYSAUX
// DATAFILE clause.
// *Action: Specify at most one SYSAUX DATAFILE clause.
/
13501, 00000, "Cannot drop SYSAUX tablespace"
// *Cause: Tried to drop SYSAUX tablespace
// *Action: None
/
13502, 00000, "Cannot rename SYSAUX tablespace"
// *Cause: An attempt to rename the SYSAUX tablespace failed.
// *Action: No action required.
/
13503, 00000, "Creating SYSAUX tablespace with invalid attributes"
// *Cause: An attempt to create the SYSAUX tablespace with invalid attributes.
// *Action: Create SYSAUX tablespace with ONLINE, PERMANENT,
// EXTENT MANAGEMENT LOCAL, SEGMENT SPACE MANAGEMENT AUTO
// attributes.
/
13504, 00000, "No SYSAUX datafile clause specified"
// *Cause: If Create Database has the datafile clause, then
// SYSAUX datafile clause has to be specified, unless using OMF.
// *Action: Specify the SYSAUX datafile clause.
/
13505, 00000, "SYSAUX tablespace can not be made read only"
// *Cause: Attempting to set the SYSAUX tablespace to read only. The SYSAUX
// tablespace must remain read write for database operation.
// *Action: Leave SYSAUX tablespace read write.
/
13506, 00000, "operation failed due to invalid snapshot range (%s, %s)"
// *Cause: An attempt was made to perform operation with an invalid Start/End
// Snapshot Pair.
// *Action: Choose a valid Start/End Snapshot Pair.
/
13507, 00000, "Event for Testing SYSAUX occupant view"
// *Document: NO
// *Cause:
// *Action: Display the test SYSAUX occupant in the V$SYSAUX_OCCUPANT view
/
13508, 00000, "Event to update INTERVAL and RETENTION in number of seconds"
// *Document: NO
// *Cause:
// *Action:
/
13509, 00000, "error encountered during updates to a AWR table"
// *Cause: An update error occurred during OCI operation due to an underlying
// error.
// *Action: Check associated OCI error. Correct problem and retry
// the operation.
/
13510, 00000, "invalid RETENTION %s, must be in the range (%s, %s)"
// *Cause: The user has specified a RETENTION setting that is not in the
// supported range of (MIN, MAX).
// *Action: Choose a valid RETENTION setting and retry the operation.
/
13511, 00000, "invalid INTERVAL %s, must be in the range (%s, %s)"
// *Cause: The user has specified a INTERVAL setting that is not in the
// supported range of (MIN, MAX).
// *Action: Choose a valid INTERVAL setting and retry the operation.
/
13512, 00000, "event #1 to test the top Segment Statistics"
// *Document: NO
// *Cause:
// *Action: will compute the top 10 segments based on logical reads.
/
13513, 00000, "event #2 to test the top Segment Statistics"
// *Document: NO
// *Cause:
// *Action: will compute the top 5 segments for logical reads and wait count.
/
13514, 00000, "Metric Capture too close to last capture, group %s"
// *Cause: The metric capture cannot be executed because it is too close
// to the last capture (within 1 centi-second).
// *Action: add some delay and reissue command to retry.
/
13515, 00000, "Error encountered during Database Usage Statistics capture"
// *Cause: Error occurred during OCI operation due to underlying error.
// *Action: Check associated OCI error. Correct problem and retry
// the operation.
/
13516, 00000, "AWR Operation failed: %s"
// *Cause: The operation failed because AWR is not available. The
// possible causes are: AWR schema not yet created; AWR
// not enabled; AWR schema not initialized; or database
// not open or is running in READONLY or STANDBY mode.
// *Action: check the above conditions and retry the operation.
/
13517, 00000, "Baseline (id = %s) does not exist"
// *Cause: The operation failed because the specified baseline ID
// does not exist in the Workload Repository.
// *Action: check the baseline id and retry the operation.
/
13518, 00000, "Invalid database id (%s)"
// *Cause: The operation failed because the specified database ID
// does not exist in the Workload Repository.
// *Action: check the database id and retry the operation.
/
13519, 00000, "Database id (%s) exists in the workload repository"
// *Cause: The operation failed because the specified database ID
// already exists in the Workload Repository.
// *Action: check the database id and retry the operation.
/
13520, 00000, "Database id (%s) not registered, Status = %s"
// *Cause: The operation failed because the specified database ID
// was not registered in the Workload Repository properly.
// *Action: check the status of database id and retry the operation.
/
13521, 00000, "Unregister operation on local Database id (%s) not allowed"
// *Cause: The operation failed because the local database ID
// cannot be unregistered from the Workload Repository.
// *Action: check the database id and retry the operation.
/
13522, 00000, "event to toggle checking for duplicate sql id (num)"
// *Document: NO
// *Cause:
// *Action: Event will determine whether to filter out duplicates for
// Top SQL selection.
/
13523, 00000, "unable to allocate required space for return type"
// *Cause: Out of memory to allocate the space for the return variable
// for an external procedure.
// *Action: Try operation again.
/
13524, 00000, "error encountered while retrieving baseline information"
// *Cause: A read error occurred during the OCI operation to retrieve
// the baseline information
// *Action: Check associated error. Correct problem and retry
// the operation.
/
13525, 00000, "error with computing space usage for sysaux occupant"
// *Cause: Error occurred during OCI operation due to underlying error.
// *Action: Check associated OCI error. Correct problem and retry
// the operation.
/
13526, 00000, "baseline (%s) does not exist"
// *Cause: The operation failed because the specified baseline name
// does not exist in the Workload Repository.
// *Action: check the baseline name and retry the operation.
/
13527, 00000, "invalid baseline name"
// *Cause: The operation failed because the specified baseline name
// is invalid.
// *Action: check the baseline name and retry the operation.
/
13528, 00000, "name (%s) is already used by an existing baseline"
// *Cause: The operation failed because the specified baseline name
// already exists in the Workload Repository.
// *Action: check the baseline name and retry the operation.
/
13529, 00000, "Error occurred when flushing AWR table group"
// *Cause: An error occurred during the flushing of a table group.
// Because of the error in the group, we are unable to flush
// this table.
// *Action: Check the error associated with the table group.
/
13530, 00000, "invalid TOPNSQL %s, must be in the range (%s, %s)"
// *Cause: The user has specified a TOPNSQL setting that is not in the
// supported range of (MIN, MAX).
// *Action: Choose a valid TOPNSQL setting and retry the operation.
/
13531, 00000, "SQL Text was purged from AWR before the operation completed"
// *Cause: A SQL was purged from AWR before the operation completed.
// *Action: Retry the operation.
/
13532, 00000, "SQL ID [%s] already exists"
// *Cause: The operation failed because the specified SQL ID
// already existed in the repository.
// *Action: Check the SQL ID and retry the operation.
/
13533, 00000, "invalid SQL ID"
// *Cause: The operation failed because the specified SQL ID was
// invalid.
// *Action: Check the SQL ID and retry the operation.
/
13534, 00000, "Current SQL count(%s) reached maximum allowed (%s)"
// *Cause: The operation failed because the maximum allowed colored
// SQL was exceeded.
// *Action: Check the count for colored SQL.
/
13535, 00000, "name (%s) is already used by an existing baseline template"
// *Cause: The operation failed because the specified baseline template name
// already existed in the Workload Repository.
// *Action: Check the baseline template name and retry the operation.
/
13536, 00000, "baseline template (%s) does not exist"
// *Cause: The operation failed because the specified baseline template name
// did not exist in the Workload Repository.
// *Action: Check the baseline template name and retry the operation.
/
13537, 00000, "invalid input for create baseline template (%s, %s)"
// *Cause: Invalid input was specified for the create baseline template
// routine.
// *Action: Check the argument displayed in the error message text.
/
13538, 00000, "invalid value for baseline expiration (%s)"
// *Cause: An invalid value was specified for the expiration of a baseline.
// The expiration is specified in number of days, and the expiration
// must be at least one day.
// *Action: Check the value for expiration.
/
13539, 00000, "invalid input for modify baseline window size (%s, %s)"
// *Cause: Invalid input was specified for the modify baseline window
// size routine.
// *Action: Check the argument displayed in the error message text.
/
13540, 00000, "operation not allowed on system moving window baseline (%s)"
// *Cause: The requested operation was not allowed on the system moving
// window baseline.
// *Action: Retry the operation with another baseline name.
/
13541, 00000, "system moving window baseline size (%s) greater than retention (%s)"
// *Cause: The system moving window baseline size must be less than the
// retention setting. The specified window size or retention
// violate this.
// *Action: Check the moving window baseline size or retention.
/
13542, 00000, "baseline ID (%s) does not exist"
// *Cause: The operation failed because the specified baseline ID
// did not exist in the Workload Repository.
// *Action: Check the baseline ID and retry the operation.
/
13543, 00000, "error encountered while retrieving baseline template information"
// *Cause: A read error occurred during the OCI operation to retrieve
// the baseline template information.
// *Action: Check associated error. Correct problem and retry
// the operation.
/
13544, 00000, "error encountered while automatically generating a baseline"
// *Cause: An error occurred while automatically generating a baseline
// based on the template information.
// *Action: Look in the trace file for more error information.
/
13545, 00000, "invalid baseline template name"
// *Cause: The operation failed because the specified baseline
// template name was an invalid identifier.
// *Action: Check the baseline template name and retry the operation.
/
13546, 00000, "Error encountered during maintenance of Adaptive Thresholds"
// *Cause: Error occurred during OCI operation due to underlying error.
// *Action: Check associated OCI error. Correct problem and retry
// the operation.
/
13547, 00000, "Unable to drop baseline since it is in use by %s"
// *Cause: The system is not able to drop the baseline since the baseline
// is in use by a functionality that depends on its existence.
// *Action: Note the name of the functionality using the baseline, and
// check if the functionality still needs the baseline.
/
13548, 00000, "Unable to find valid snapshot IDs for the inputted baseline time range"
// *Cause: The system is not able to find valid snapshot IDs for the inputted
// time range while attempting to create a baseline.
// *Action: Check that the inputted time range has at least two valid
// snapshots. The dba_hist_snapshot displays the snapshot id and
// time information.
/
13549, 00000, "invalid input for create baseline with time range (%s)"
// *Cause: Invalid time input was specified for the create baseline
// routine.
// *Action: Check the argument displayed in the error message text.
/
13550, 00000, "value \"%s\" of length (%s) exceeded maximum length (%s) for parameter [%s]"
// *Cause: An invalid parameter was specified for the Automatic Workload Repository
// (AWR) registration routine.
// *Action: Check the argument displayed in the error message text.
/
13551, 00000, "source database name [%s] not found in AWR"
// *Cause: An invalid parameter was specified for the Automatic Workload
// Repository (AWR) operation.
// *Action: Check the argument displayed in the error message text.
/
13552, 00000, "parameter [%s] of value [%s] mismatched with AWR registered value [%s]"
// *Cause: An invalid parameter was specified for the Automatic Workload
// Repository (AWR) operation.
// *Action: Check the argument displayed in the error message text.
/
13553, 00000, "operation failed - missing parameter [%s]"
// *Cause: The required parameter was missing for the Automatic Workload
// Repository (AWR) operation.
// *Action: Check the parameter name displayed in the error message text.
/
13554, 00000, "baseline template (%s) is a directory"
// *Cause: The operation failed because the specified baseline template name
// was a directory.
// *Action: Check the baseline template name and retry the operation.
/
13555, 00000, "purge operation failed - [%s]"
// *Cause: The purge operation failed due to the reason described
// in the error message.
// *Action: Correct the stated problem and retry the operation.
/
13556, 00000, "snapshot on remote sources not enabled"
// *Cause: The current database was not set up for snapshots on remote
// databases. See the description in the error message.
// *Action: Correct the system settings and retry the operation.
/
13557, 00000, "reset operation failed - [%s]"
// *Cause: The Automatic Workload Repository (AWR) reset operation failed
// due to the reason described in the error message.
// *Action: Correct the stated problem and retry the operation.
/
13558, 00000, "remote database registration mismatch; database ID (%s)"
// *Cause: The remote Automatic Workload Repository (AWR) operation
// failed because the remote database did not match the local
// registration data. The operation was aborted because it was
// meant for another database ID.
// Either the database or the remote database ID changed and
// needs to be updated or registered in the repository.
// *Action: Ensure that the database links for the affected database are still
// valid and point to the registered database. Use any additional
// errors reported to identify and rectify the the underlying issue.
// Correct the mismatch or unregister and register the affected
// database ID.
13559, 00000, "CPU time or run time policy violation - %s"
// *Cause: The operation ran longer than the expected time.
// *Action: If this error persists, contact Oracle Support Services.
13560, 00000, "SYSAUX tablespace cannot be brought offline; shut down if necessary"
// *Cause: An attempt was made to bring a SYSAUX tablespace offline.
// *Action: Shut down the database if necessary and do a recovery.
13561, 00000, "cannot drop SYSAUX tablespace"
// *Cause: An attempt was made to drop a SYSAUX tablespace.
// *Action: None.
/
13562, 00000, "AWR operation failed because tablespace (%s) is invalid."
// *Cause: The operation failed because the tablespace was invalid for the
// Automatic Workload Repository (AWR) or was not available.
// *Action: Provide a valid tablespace, ensure that the tablespace is
// available and retry the operation.
/
/ ========================================
/ 13600 - 13699 reserved for the adv fmwk.
/ ========================================
13600, 00000, "error encountered in Advisor\n%s"
// *Cause: An error occurred in the Advisor.
// This message will be followed by a second message giving
// more details about the nature of the error.
// *Action: See the Advisor documentation
// for an explanation of the second error message.
/
13601, 00000, "The specified Advisor %s does not exist."
// *Cause: The user specified an advisor name that has not be defined
// in the advisor repository.
// *Action: Correct the advisor name and retry the operation.
/
13602, 00000, "The specified parameter %s is not valid for task or object %s."
// *Cause: The user attempted to access a task parameter that does not
// exist for the specified advisor object. The parameter may be
// misspelled or the user has selected a parameter that is not
// supported by the particular advisor.
// *Action: Validate the parameter name and retry the operation.
/
13603, 00000, "The specified parameter %s cannot be fetched as a numeric value for task or object %s."
// *Cause: The user attempted to retrieve a string parameter as a numeric
// value.
// *Action: Check the datatype for the task parameter and retry the operation.
/
13604, 00000, "The specified parameter %s cannot be fetched as a SQL table."
// *Cause: The user attempted to retrieve a non-table parameter as a table
// name.
// *Action: Check the datatype for the task parameter and retry the operation.
/
13605, 00000, "The specified task or object %s does not exist for the current user."
// *Cause: The user attempted to reference an advisor task or object
// using a name that does not exist in the Advisor repository.
// *Action: Adjust the name and retry the operation.
/
13606, 00000, "the specified task parameter element %s is out of range for parameter %s."
// *Cause: The user attempted to reference an invalid parameter element.
// *Action: Adjust the element offset and retry the operation.
/
13607, 00000, "The specified task or object %s already exists"
// *Cause: The user attempted to create the specified task or object
// using a name that already exists in the Advisor repository.
// Task names must be unique to the database user.
// *Action: Adjust the name and retry the operation.
/
13608, 00000, "The specified name %s is invalid."
// *Cause: An attempt was made to specify a name for a task, object, execution
// or directive instance, which contained invalid characters or
// an invalid wildcard specifier.
// *Action: Adjust the name and retry the operation.
/
13609, 00000, "The specified task %s must be executing to be cancelled or interrupted."
// *Cause: The user attempted to cancel or interrupt a task that is not
// currently executing.
// *Action: Check the status of the task and retry the operation.
/
13610, 00000, "The directive %s does not exist for task %s."
// *Cause: The user attempted to access a task directive that does not exist.
// *Action: Validate the directive and retry the operation.
/
13611, 00000, "The command %s is not a valid advisor command."
// *Cause: The user attempted to specify a command that does not exist.
// *Action: Validate the command and retry the operation.
/
13612, 00000, "The recommendation action %s,%s is not valid for task %s."
// *Cause: The user attempted to access a recommendation action that does
// not exist in the task.
// *Action: Validate the recommendation-action and retry the operation.
/
13613, 00000, "The requested operation is not supported for this advisor object."
// *Cause: The user attempted to perform an operation that is not supported
// for the particular advisor or task type.
// *Action: Validate the task or object and retry the operation.
/
13614, 00000, "The template %s is not compatible with the current advisor."
// *Cause: The user attempted to create a new task or object using
// an existing task or object that was not created by the
// same advisor.
// *Action: Validate the template and retry the operation.
/
13615, 00000, "The task or object %s is greater than the maximum allowable length of 30 characters."
// *Cause: The user attempted to create a new task or object using
// a name that is too long.
// *Action: Shorten the name and retry the operation.
/
13616, 00000, "The current user %s has not been granted the ADVISOR privilege."
// *Cause: The user attempted an advisor operation that requires privilege.
// *Action: Adjust the user's privileges and retry the operation.
/
13617, 00000, "The specified task %s already executing"
// *Cause: The user attempted to execute a task that is currently executing.
// *Action: Wait for the task to finish before attempting any further task
// activities.
/
13618, 00000, "The specified value is not a valid value for procedure argument %s."
// *Cause: The user executed a procedure but failed to provide
// correct values for the argument.
// *Action: Correct the procedure arguments and retry the operation.
/
13619, 00000, "The procedure argument %s is greater than the maximum allowable length of %s characters."
// *Cause: The user attempted to pass a character argument that is too long.
// *Action: Shorten the specified character argument and retry the operation.
/
13620, 00000, "The task or object %s is read-only and cannot be deleted or modified."
// *Cause: The user attempted to perform an operation that will update
// or delete a read-only task or object.
// *Action: Adjust the READ_ONLY property for the object and retry the
// operation.
/
13621, 00000, "The task_or object %s is marked as a template and cannot perform the requested operation."
// *Cause: The user attempted perform an unsupported operation on a task or
// object that is identified as a template.
// *Action: Choose a different object and retry the operation.
/
13622, 00000, "invalid recommendation annotation"
// *Cause: The user attempted to mark a recommendation using an invalid
// annotation. Valid annotation actions are ACCEPT, REJECT and
// IGNORE.
// *Action: Correct the action and retry the operation.
/
13623, 00000, "The recommendation %s is not valid for task %s."
// *Cause: The user attempted to access a recommendation that does
// not exist in the task.
// *Action: Validate the recommendation and retry the operation.
/
13624, 00000, "The task %s is executing and cannot be deleted or modified."
// *Cause: The user attempted to access a task that currently executing.
// *Action: Wait for the task to complete and retry the operation.
/
13625, 00000, "%s is an invalid advisor object type."
// *Cause: The user has specified an invlaid object type.
// *Action: Refre to dba_advisor_object_types for all valid object types
/
13626, 00000, "The specified object %s is not valid for task %s."
// *Cause: The user specified an non-existent object for the task
// *Action: Choose a different object and retry the operation.
/
13627, 00000, "Setting of parameter %s is disallowed until the task is reset."
// *Cause: The user attempted to set the value of a parameter before the task
// was reset. This parameter cannot be changed until the task is
// reset.
// *Action: Reset the task and retry the operation.
/
13628, 00000, "Insufficient privileges to access the task belonging to the specified user"
// *Cause: The user could not access dba_* views.
// *Action: Retry operation as owner of the task or after granting new privileges.
/
13629, 00000, "The task or object %s is being used by another operation."
// *Cause: The user attempted to access a task or object that is locked by
// another session.
// *Action: Wait for the task or object activity to complete and retry
// the operation.
/
13630, 00000, "The task %s contains execution results and cannot be executed."
// *Cause: The user attempted to execute a task that already contains
// execution results.
// *Action: Reset the task to its initial state and retry the operation.
/
13631, 00000, "The most recent execution of task %s contains no results."
// *Cause: The user attempted to create a report or script from a task that
// has not successfully completed an execution.
// *Action: Execute the task and then retry the operation
/
13632, 00000, "The user cancelled the current operation."
// *Cause: The user signaled a cancel during a task or object operation.
// *Action: None
/
13633, 00000, "The task %s was interrupted and needs to be resumed."
// *Cause: The user attempted to execute a task that was interrupted.
// *Action: Resume the execution of the task via the RESUME_TASK API.
/
13634, 00000, "The task %s needs to be reset before being re-executed."
// *Cause: The task must be in an inital state to be executed.
// *Action: Reset the task to its initial state and retry the operation.
/
13635, 00000, "The value provided for parameter %s cannot be converted to a number."
// *Cause: A numeric parameter was incorrectly supplied in string form.
// *Action: Retry by supplying valid numeric value.
/
13636, 00000, "The specified value provided for parameter %s is not valid for this advisor."
// *Cause: The user supplied an invalid parameter value.
// *Action: Retry by supplying valid value.
/
13637, 00000, "Executing or modifying task %s is disallowed until the task is reset to its initial state."
// *Cause: The user attempted to execute or modify the task that is in
// not in its INITIAL state.
// *Action: Reset the task and retry the operation.
/
13638, 00000, "The user interrupted the current operation."
// *Cause: The user signaled an interrupt during a task or object operation.
// *Action: None
/
13639, 00000, "The current operation was interrupted because it timed out."
// *Cause: The task or object operation timed out.
// *Action: None
/
13640, 00000, "The current operation was cancelled because it timed out, and was not in interruptible mode."
// *Cause: The task or object operation timed out.
// *Action: None
/
13641, 00000, "Task cannot be interrupted yet. You may cancel it instead."
// *Cause: The user attempted to interrupt a task that has not
// reached interruptible mode.
// *Action: Wait until the task reaches interruptible mode, or cancel the
// task execution.
/
13642, 00000, "The specified string %s provided for %s cannot be converted to a date. The acceptable date format is %s."
// *Cause: The user supplied a date value in an incorrect format.
// *Action: Retry by supplying valid value.
/
13643, 00000, "The task can not be interrupted or cancelled."
/ *Cause: Request to interrupt or cancel task execution can not be granted
// because the task has not reached the appropriate mode.
// *Action: User should wait for a few seconds and try again.
/
13644, 00000, "The user \"%s\" is invalid."
// *Cause: Invalid user name specified to advisor framework
// *Action: User should specify a correct, case-sensitive, name
/
13645, 00000, "The specified execution %s does not exist for this task."
// *Cause: You attempted to reference an advisor task execution
// using a name that did not exist.
// *Action: Adjust the name and retry the operation.
/
13646, 00000, "The specified execution %s already exists"
// *Cause: You attempted to perform a new execution
// using a name that already exists for the specified task.
// Execution names must be unique within the same task.
// *Action: Adjust the name and retry the operation.
/
13647, 00000, "Setting of parameter %s is disallowed during task execution."
// *Cause: You attempted to set the value of a parameter while the task
// was being executed. This parameter cannot be changed until the task
// finishes its execution.
// *Action: Verify the status of the task and retry the operation.
/
13648, 00000, "The specified execution type does not exist for this advisor."
// *Cause: You attempted to use an advisor task execution type
// using a name that did not exist.
// *Action: Adjust the name and retry the operation.
/
13649, 00000, "The type of execution is not specified for this advisor or task."
// *Cause: You attempted to execute a task for a multi-execution task
// advisor without specifying the type of execution to perform.
// *Action: Set the execution type and retry the operation.
/
13650, 00000, "The specified object does not exist for this execution."
// *Cause: You attempted to associate an object to a task execution
// that id not contain the object.
// *Action: Adjust the execution name and object ID, and then retry the operation.
/
13651, 00000, "The specified list of execution parameters is invalid."
// *Cause: The list did not include pairs of (parameter_name, parameter_value)
// where every parameter is a valide task parameter. Duplicates are
// not allowed.
// *Action: Adjust the content of the list, and then retry the operation.
/
13652, 00000, "Cannot set execution parameters for this advisor"
// *Cause: You attempted to set execution parameters for an advisor
// that did not support multiple executions of its tasks.
// *Action: Adjust the property of the advisor, and then retry the operation.
/
13653, 00000, "The directive with definition id %s was not found."
// *Cause: An invalid directive identifier was specified to advisor framework.
// *Action: User should specify a correct identifier number and retry the
// operation.
/
13654, 00000, "The directive with instance id of %s was not found."
// *Cause: An invalid instance identifier was specified to advisor framework.
// *Action: User should specify a correct instance identifier number and retry the
// operation.
/
13655, 00000, "The directive document contains a syntax error and cannot be loaded."
// *Cause: An attempt was made to load an XML-based directive that does not
// conform to the documented DTD.
// *Action: Reformat the directive according the documented DTD.
/
13656, 00000, "The parameter was not found in directive %s."
// *Cause: The specified parameter name could not be located within the directive
// XML document.
// *Action: Verify the existence of the parameter in the specified directive.
/
13657, 00000, "The filter Xpath specification has invalid syntax."
// *Cause: The specified filter could not be compiled within the directive
// XML document.
// *Action: Verify the syntax of the filter and retry the operation.
/
13658, 00000, "The specified directive already has an instance"
// *Cause: An attempt was made to create multiple instances of a directive when not permitted
// *Action: Verify the parent directive identifier and the instance name.
/
13659, 00000, "A directive with domain \"%s\" and name \"%s\" already exists for advisor %s."
// *Cause: The specified directive is not unique among the directives.
// *Action: Choose a directive name and domain that is distinct for the associated advisor.
/
13660, 00000, "A directive instance with the name \"%s\" already exists."
// *Cause: The specified directive instance is not unique among instances for this directive.
// *Action: Choose an instance name that is distinct for the associated directive.
/
13661, 00000, "A directive instance with the name \"%s\" was not found."
// *Cause: An attempt was made to update or delete a non-existent directive instance.
// *Action: Verify the parent directive identifier and the instance name.
/
13662, 00000, "The specified value provided for parameter %s is not valid for this task."
// *Cause: The supplied parameter value was not valid for the current task
// configuration.
// *Action: Retry by supplying valid value. Check the current task
// configuration.
/
13663, 00000, "The task %s contains no results for execution %s."
// *Cause: An attempt was made to create a report or script from an execution
// that had not been successfully completed.
// *Action: Run a new execution and then retry the operation.
/
13664, 00000, "A task-managed \"SQL Tuning Set\" already exists for task \"%s\"."
// *Cause: An attempt was made to create a task-managed SQL Tuning Set for
// a task that already had one.
// *Action: Create a new task to use a different SQL Tuning Set.
/
13665, 00000, "Execution names are not correctly ordered."
// *Cause: The supplied execution names were not properly ordered by
// execution start date.
// *Action: Retry by supplying a valid order.
/
13666, 00000, "Task ID %s does not exist."
// *Cause: The supplied task ID was invalid.
// *Action: Check the task ID and try again.
/
13667, 00000, "Execution ID %s does not exist."
// *Cause: The supplied execution ID was invalid.
// *Action: Check the execution ID and try again.
/
13668, 00000, "The current operation was aborted because it was blocking another session."
// *Cause: The task or object operation interrupted itself when it detected
// that it was blocking some other session.
// *Action: Retry the operation when the conflicting operations are not
// running.
/
13669, 00000, "Execution provided has type \"%s\", expected \"%s\"."
// *Cause: An execution was provided whose type did not match the one
// expected by the API.
// *Action: Check the execution name, and try again.
/
13670, 00000, "No execution of type %s exists for task provided."
// *Cause: No execution of the required type existed for the given advisor
// task.
// *Action: Check the task, and try again.
/
13699, 00000, "Advisor feature is not currently implemented."
// *Cause: An attempt was made to execute an unsupported advisor operation.
// *Action: Verify the availability of the operation.
//
/
/ ========================================
/ 13700 - 13749 reserved for the ADDM, ASH
/ ========================================
/
13700, 00000, "Reserved for ADDM tracing."
// *Cause:
// *Action:
/
13701, 00000, "Snapshot pair [%s, %s] seems to be specified in reverse order."
// *Cause: The start snapshot id was greater than the end snapshot id.
// *Action: Swap the start and end snapshot ids.
/
13702, 00000, "Snapshot IDs specified by the range [%s, %s] are equal."
// *Cause: The start snapshot id and end snapshot id were identical.
// *Action: Provide different start and end snapshot ids.
/
13703, 00000, "The snapshot pair [%s, %s] for database_id %s and instance_id %s are not found in the current repository."
// *Cause: The snapshot ids or the database id or the instance id was invalid
// or the specified snapshots have already been purged.
// *Action: Set valid snapshot ids and retry.
/
13704, 00000, "Invalid value \"%s\" specified for parameter \"%s\"."
// *Cause: The parameter was not set before executing the ADDM.
// *Action: Set the parameter to a valid value and retry.
/
13705, 00000, "There was a instance shutdown/startup between the snapshots in the range [%s, %s]."
// *Cause: Instance was shut down and restarted between the
// two specified snapshots.
// *Action: Specify start and end snapshot ids that does not have a
// shutdown/startup in between them.
/
13706, 00000, "Invalid value \"%s\" specified for parameter \"%s\" in \"%s\" analysis mode."
// *Cause: The parameter was not set to an acceptable value for this
// particular mode of analysis.
// *Action: Set the parameter to a valid value and retry.
/
13707, 00000, "Either the start snapshot %s or the end snapshot %s is incomplete or missing key statistics."
// *Cause: Either the start or the end snaphots was missing or purged
// or had encountered errors while creating them.
// *Action: Verify that AWR is done taking these two snapshots, or
// Look in DBA_HIST_SNAP_ERROR to find what tables are missing
// in the start/end snapshots.
// Use the ERROR_NUMBER column in that view together with the
// alert log to identify the reason for failure and take
// necessary action to prevent such failures in the future.
// Try running ADDM on a different snapshot range that has
// valid start and end snapshots.
/
13708, 00000, "Some snapshots in the range [%s, %s] were purged before the analysis was complete."
// *Cause: One or both of the snapshots have been purged from AWR.
// *Action: Verify that the AWR auto purging is not trying to purge
// these snapshots and re-run ADDM.
/
13709, 00000, "Required parameter \"%s\" must be set before execution."
// *Cause: The parameter needs to be set before running the ADDM
// *Action: Set the parameter to a valid value and retry.
/
13710, 00000, "Parameter \"%s\" must have a higher value than parameter \"%s\". The values supplied were \"%s\" and \"%s\" respectively."
// *Cause: Invalid interaction between two parameter values.
// *Action: Set at least one of the values so the value of the first parameter
// is higher than the value of the second parameter.
/
13711, 00000, "Some snapshots in the range [%s, %s] are missing key statistics."
// *Cause: Some AWR tables encountered errors while creating one or more
// snapshots in the given range. The data present in one or more of
// these missing tables is necessary to perform an ADDM analysis.
// *Action: Look in DBA_HIST_SNAP_ERROR to find what tables are missing
// in the given snapshot range. Use the ERROR_NUMBER column in
// that view together with the alert log to identify the reason
// for failure and take necessary action to prevent such failures
// in the future.
// Try running ADDM on a different snapshot range that
// does not include any incomplete snapshots.
/
13712, 00000, "Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version \"%s\" do not match the database version \"%s\"."
// *Cause: ADDM analysis can only be performed on AWR snapshots taken in the
// current release.
// *Action: One can still generate AWR and ASH reports using
// ?/rdbms/admin/awrrpt and ?/rdbms/admin/ashrpt on these snapshots
// to analyze the data in them.
/
13713, 00000, "Finding name \"%s\" does not exist. Look in DBA_ADVISOR_FINDING_NAMES for all valid values"
// *Cause: Attempt to refer to an advisor's finding name that does not exist.
// *Action: Specify a valid value. The list of all valid values is in
// DBA_ADVISOR_FINDING_NAMES
13714, 00000, "\"%s\" is not a valid SQL_ID value"
// *Cause: The specified value of SQL_ID was not properly formatted.
// *Action: Specify a valid value consisting of a 13 character string with characters
// from '0' to '9' and from 'a' to 'z'.
13715, 00000, "\"%s\" is not recognized by ADDM as a parameter name"
// *Cause: The specified value for a system parameter was not recognized by ADDM.
// *Action: Specify a value that appears in the NAME column of V$PARAMETER.
/
13716, 00000, "Diagnostic Package License is needed for using this feature."
// *Cause: The specified value for system parameter CONTROL_MANAGEMENT_PACK_ACCESS
// indicated that the Diagnostic Package was disabled.
// *Action: Modify the parameter value if the Diagnostic Package License was
// purchased.
/
13717, 00000, "Tuning Package License is needed for using this feature."
// *Cause: The specified value for system parameter CONTROL_MANAGEMENT_PACK_ACCESS
// indicated that the Tuning Package was disabled.
// *Action: Modify the parameter value if the Tuning Package License was
// purchased.
/
13718, 00000, "Tuning Package License or Real Application Testing Option is needed for using this feature."
// *Cause: The specified package license and option were not installed.
// *Action: Consider purchasing and installing either the missing package licence
// or option. If the tuning package license was purchased, then check
// the value of system parameter CONTROL_MANAGEMENT_PACK_ACCESS.
/
13719, 00000, "Imported AWR snapshots are from a database with an incompatible character set."
// *Cause: ADDM analysis was attempted on imported Automatic Workload Repository (AWR)
// snapshots with incompatible character set.
// *Action: Perform ADDM analysis using a database with the same version and character set
// as the original database.
/
13720, 00000, "dimension name provided is too long"
// *Cause: Active Session History (ASH) dimension name provided was longer than the
// limit of 30 characters.
// *Action: Correct the dimension name and retry the operation.
//
/
13721, 00000, "dimension name provided is invalid"
// *Cause: Active Session History (ASH) dimension name provided was invalid.
// *Action: Correct the dimension name and retry the operation.
//
/
13722, 00000, "invalid input value for procedure argument %s"
// *Cause: An invalid value was passed an input for a procedure argument.
// *Action: Pass a valid value to the procedure.
//
/
13723, 00000, "input value for procedure argument %s exceeds maximum allowed length of %s"
// *Cause: The string input value was too long for the specific procedure argument.
// *Action: Pass a valid value to the procedure.
//
/
/==============================================
/= 13750 - 13799 reserved for SqlSet =
/= 19371 - 19390 reserved for sqlset/sqltune =
/==============================================
/
13750, 00000, "User \"%s\" has not been granted the \"ADMINISTER SQL TUNING SET\" privilege."
// *Cause: The user attempted an SQL Tuning Set operation that requires
// a specific privilege.
// *Action: Adjust the user's privileges and retry the operation.
/
13751, 00000, "\"SQL Tuning Set\" \"%s\" does not exist for owner \"%s\" or user \"%s\" does not have permission to access the \"SQL Tuning Set\"."
// *Cause: The user attempted to access a SQL Tuning Set that does not exist
// or the user does have permission to access the SQL Tuning Set
// *Action: Check the existence of the \"SQL Tuning Set\" or adjust the user's
// privileges and retry the operation.
/
13752, 00000, "User \"%s\" must be SYS or must have the \"ADMINISTER ANY SQL TUNING SET\" privilege."
// *Cause: The attempted to create a SQL Tuning Set in another schema without having
// the right privilege.
// *Action: Connect as SYS or adjust the user's privilege and retry
// the operation.
/
13753, 00000, "\"SQL Tuning Set\" \"%s\" already exists for user \"%s\"."
// *Cause: The user attempted to create a "\SQL Tuning"\ Set using a name
// that already exists for that owner.
// *Action: Change the name of the SQL Tuning Set and retry the operation.
/
13754, 00000, "\"SQL Tuning Set\" \"%s\" does not exist for user \"%s\"."
// *Cause: The user attempted to access a SQL Tuning Set that does not exist.
// *Action: Check the speelling of the SQL Tuning Set name and retry
// the operation.
/
13755, 00000, "invalid \"SQL Tuning Set\" name"
// *Cause: The user attempted to specify a SQL Tuning Set name that is invalid.
// A name must not contain wildcards and its length must be less than
// 30 characters.
// *Action: Adjust the name and retry the operation.
/
13756, 00000, "Cannot update attribute \"%s\"."
// *Cause: The user attempted to update an attribute element that
// cannot be modified. The only string attributes that can
// be updated are MODULE, ACTION, PARSING_SCHEMA_NAME, PRIORITY, and OTHER.
// *Action: Adjust the attribute name and retry the operation.
/
13757, 00000, "\"SQL Tuning Set\" \"%s\" owned by user \"%s\" is active."
// *Cause: The user attempted to update an active SQL Tuning Set.
// *Action: Remove all reference to the SQL Tuning Set and retry the operation.
/
13758, 00000, "\"SQL Tuning Set\" \"%s\" owned by user \"%s\" is in use."
// *Cause: The user attempted to modify a SQL Tuning Set or to add a reference
// to a SQL Tuning Set which is in use.
// *Action: Wait until the end of the previous operation and retry.
/
13759, 00000, "User \"%s\" cannot remove reference \"%s\"."
// *Cause: The user attempted to remove a SQL Tuning Set reference that
// does not exist. The user might not own the reference.
// *Action: Check the reference ID and the reference owner and retry
// the operation.
/
13760, 00000, "This operation is not supported from a physical standby database."
// *Cause: An attempt was made to execute an operation that is not supported
// from a physical standby database.
// *Action: Execute this operation from a primary database.
/
13761, 00000, "invalid filter"
// *Cause: The user attempted to select data from a data source using
// an invalid filter. A filter is a WHERE clause on data source
// content.
// *Action: Correct the filter and retry the operation.
/
13762, 00000, "The %s ranking measure is invalid."
// *Cause: The user attempted to select data from a data source
// using an invlaid ranking measure.
// A ranking measure must represent a valid numerical expression.
// *Action: Correct the ranking measure and retry the operation.
/
13763, 00000, "illegal ranking attribute \"%s\""
// *Cause: The user attempted to use an attribute element that
// is not allowed in a ranking measure.
// *Action: Check the attribute in the ranking measure and retry
// the operation.
/
13764, 00000, "Value \"%s\" is illegal as a result percentage."
// *Cause: The user attempted to select data from a SQL Tuning Set using
// an invalid result percentage. The result percentage must be
// between 0 and 1.
// *Action: Correct the result percentage value and retry the operation.
/
13765, 00000, "Value \"%s\" is illegal for a result limit."
// *Cause: The user attempted to select data from a SQL Tuning Set
// using an invalid result limit.
// A result limit must be a positive interger.
// *Action: Correct the result limit value and retry the operation.
/
13766, 00000, "A ranking measure is required."
// *Cause: The user attempted to select data from a SQL Tuning Set
// using a percentage argument without specifying a ranking measure.
// *Action: Add a ranking measure or remove the percentage argument
// and retry the operation.
/
13767, 00000, "End snapshot ID must be greater than begin snapshot ID."
// *Cause: The user attempted to select data from the workload repository
// using an invalid snaphot ID range.
// *Action: Adjust the snapshot ID range and retry the operation.
/
13768, 00000, "Snapshot ID must be between %s and %s."
// *Cause: The user attempted to select data from the workload repository
// using a snaphot ID which does not exist.
// *Action: Adjust the snapshot ID and retry the operation.
/
13769, 00000, "Snapshots %s and %s do not exist."
// *Cause: The user attempted to select data from the workload repository
// using snapshots that do not exist.
// *Action: Check the snapshot identifiers and retry the operation.
/
13770, 00000, "Baseline \"%s\" does not exist."
// *Cause: The user attempted to access a baseline that does not exsit.
// *Action: Check the speelling of the baseline name and retry the operation.
/
13771, 00000, "cannot obtain exclusive lock %s on \"SQL Tuning Set\" \"%s\" owned by user \"%s\""
// *Cause: Unexpected error from DBMS_LOCK.REQUEST.
// *Action: This error should not normally occur. Check your system for
// anomalies and retry the operation. If this error persists,
// contact Oracle Support Services.
/
13772, 00000, "unexpected deadlock on \"SQL Tuning Set\" \"%s\" owned by user \"%s\""
// *Cause: Unexpected error from DBMS_LOCK.REQUEST
// *Action: This error should not normally occur. Check your system for
// anomalies and retry the operation. If this error persists,
// contact Oracle Support Services.
/
13773, 00000, "insufficient privileges to select data from the cursor cache"
// *Cause: The user attempted to perform an operation without having the
// appropriate privileges on V$SQL and V$SQL_BIND_CAPTURE.
// *Action: Adjust the user's privileges and retry the operation.
/
13774, 00000, "insufficient privileges to select data from the workload repository"
// *Cause: The user attempted to perform an operation without having
// the appropriate privileges on views DBA_HIST_BASELINE,
// DBA_HIST_SQLTEXT, DBA_HIST_SQLSTAT, DBA_HIST_SQLBIND,
// DBA_HIST_OPTIMIZER_ENV, and DBA_HIST_SNAPSHOT.
// *Action: Adjust the user's privileges and retry the operation.
/
13775, 00000, "inconsistent datatype in input cursor"
// *Cause: The user attempted to load a SQL Tuning Set using an invalid input cursor.
// All rows in the cursor must match type SQLSET_ROW.
// *Action: Check the rows type in the cursor and retry the operation.
/
13776, 00000, "User \"%s\" has not been granted the \"SELECT\" privilege on the \"SQL tuning set\" DBA views."
// *Cause: The user attempted to read a SQL tuning set belonging to someone
// else without having SELECT privilege on the DBA views
// *Action: User should be granted the privilege or only access his own STS
/
13777, 00000, "invalid list of attribute names"
// *Cause: The user specified an attribute element that is not valid.
// The only attributes that can be selected are NULL,
// BASIC, TYPICAL, ALL or a comma separated list of the names including
// EXECUTION_STATISTICS, OBJECT_LIST, BIND_LIST and SQL_PLAN.
// *Action: Adjust the attribute list and retry the operation.
13778, 00000, "no new name or owner specified for \"SQL Tuning Set\""
// *Cause: The user attempted to call remap_stgtab_sqlset without specifying
// either a new SQL tuning set name or a new SQL tuning set owner
// *Action: Specify at least one or the other argument as non-NULL
/
13779, 00000, "invalid load option"
// *Cause: The user attempted to call load_sqlset with a load option
// that is different than INSERT, UPDATE and MERGE.
// *Action: Adjust the load option and retry the operation.
/
/======================================
/= 13780-13799 reserved for SQLTune =
/======================================
13780, 00000, "SQL statement does not exist."
// *Cause: The user attempted to tune a SQL statement that does not exist.
// *Action: Verify the sql_id and the plan hash value of the statement and
// retry the operation.
/
13781, 00000, "cannot perform test-execute and explain plan operations on the automatic SQL tuning task"
// *Cause: The user attempted to test-execute or generate explain plans for a SQL workload using the automatic SQL tuning task.
// *Action: Verify the name of the tuning task and retry the operation.
/
13782, 00000, "The argument %s to this API is only allowed for tasks created in a physical standby database."
// *Cause: "An attempt was made to pass an argument that is valid only for a
// physical standby database. "
// *Action: Remove the invalid argument and re-run the API.
/
13783, 00000, "invalid tuning scope"
// *Cause: The user attempted to specify a tuning task scope that is invalid.
// The possible values are LIMITED or COMPREHENSIVE.
// *Action: Check the scope value and retry the operation.
//
/
13784, 00000, "cannot accept SQL profiles for all statements in the \"%s\""
// *Cause: An attempt was made to accept SQL profiles for all statements in
// the input workload.
// *Action: Provide the object identifier corresponding to a statement
// in the workload and retry the operation.
/
13785, 00000, "missing target object for tuning task \"%s\""
// *Cause: The user attempted to perform an operation on a task without
// specifying a target object or by using an invalid object identifier.
// *Action: Check the identifier of the object and retry the operation.
/
13786, 00000, "missing SQL text of statement object \"%s\" for tuning task \"%s\""
// *Cause: The user attempted to accept SQL profile for an object
// that has not a SQL text associated to it.
// *Action: Check the identifier of the object and retry the operation.
/
13787, 00000, "missing SQL profile for statement object \"%s\" for tuning task \"%s\""
// *Cause: The user attempted to accept a SQL profile for an object
// that has not a SQL profile associated to it.
// *Action: Check the identifier of the object and retry the operation.
/
13788, 00000, "invalid recommendation type"
// *Cause: The user passed an invalid recommendation type in the rec_type
// argument to script_tuning_task. Possible values are ALL or any
// subset of a comma-separated list of PROFILES, STATISTICS
// and INDEXES.
// *Action: Check the rec_type arg and retry the operation.
/
13789, 00000, "invalid process action"
// *Cause: The user passed an invalid action to process a SQL statement.
// Possible value is any subset of a comma-seperated list of
// EXECUTE and EXPLAIN_PLAN.
// *Action: Check the action argument and retry the operation.
/
13790, 00000, "invalid value for time limit"
// *Cause: The user passed an invalid value for the time limit argument.
// *Action: Check the argument specified value and retry the operation.
/
13791, 00000, "cannot resume a task created to process a single statement"
// *Cause: An attempt was made to resume a task that was created
// for a single SQL statement. A task can be resumed only if it is
// used for a SQL Tuning Set.
// *Action: No action required.
/
13792, 00000, "This operation requires a database link."
// *Cause: An attempt was made to execute an operation from a physical standby database
// that requires a valid database link to access a primary database.
// *Action: Provide a valid database link to access a primary database.
/
13793, 00000, "invalid comparison metric"
// *Cause: An invalid metric to compare SQL performance was specified.
// *Action: Use execution statistics to compare the result of two executions
// and optimizer_cost to analyze performance of two explain plan
// actions.
/
13794, 00000, "execution type mismatch"
// *Cause: An attempt was made to analyze the performance of a SQL workload
// using two executions that were generated using two different
// actions.
// *Action: check the name and type of task executions to analyze
// and retry the operation.
/
13795, 00000, "missing task execution"
// *Cause: An insufficient number of valid task executions to analyze
// the performance of a SQL workload were specified.
// *Action: run the task to generate two executions of the same type
// and retry the operation.
/
13796, 00000, "invalid value %s specified for problem type"
// *Cause: An invalid problem type was specified to the SQL diagnosis
// advisor. Problem type should be one of the PROBLEM_TYPE_*
// defined in 'admin/dbmsdiag.sql'.
// *Action: Specify valid problem type.
//
/
13797, 00000, "invalid SQL Id specified, %s"
// *Cause: Invalid SQL Id specified for conversion.
// *Action: Specify valid SQL Id.
/
13798, 00000, "Parameter %s cannot be NULL."
// *Cause: A call to GET_THRESHOLD procedure was made without a required
// parameter.
// *Action: Specify a valid value for this parameter.
/
13799, 00000, "threshold not found"
// *Cause: No threshold was found with the specified threshold key.
// *Action: No action required.
/
/ ==============================================
/ 13800 - 13809 reserved for the SQL Tuning Base
/ ==============================================
13800, 00000, "concurrent DDL failure on SQL repository objects"
// *Cause: A SQL repository object was the target of two concurrent
// DDL operations.
// *Action: Check the current state of the object and retry the operation
// that failed.
13801, 00000, "invalid value for SQLTUNE_CATEGORY parameter"
// *Cause: An invalid Oracle identifier was used as the value of the
// parameter.
// *Action: Specify the parameter conforming to the rules for Oracle
// identifiers.
13802, 00000, "failed to purge SQL Tuning Base entry from sql$"
// *Cause: An error occured while try to delete a SQL Tuning Base
// object.
// *Action: Look at the underlying error(s) on the error stack.
/
/ =======================================
/ 13810 - 13824 reserved for DBOP Monitor
/ =======================================
13810, 00000, "The FORCED_TRACKING parameter can only have values of N or Y."
// *Cause: An invalid value was passed for the parameter.
// *Action: Check the value and input the correct value.
13811, 00000, "A database operation is already monitoring this session."
// *Cause: An attempt was made to start a database operation in a session that
// was already being monitored.
// *Action: No action required.
13812, 00000, "current session does not have database operation monitored"
// *Cause: An attempt was made to end a database operation that did not exist.
// *Action: Check if the database operation is being monitored.
13813, 00000, "database operation name or execution ID does not match"
// *Cause: The database operation name or execution ID did not match.
// *Action: Call the interface with the right database operation name and execution ID.
13814, 00000, "database operation name is invalid"
// *Cause: The database operation name provided was invalid.
// *Action: Supply a database operation name not exceeding 30 characters.
13815, 00000, "database operation execution ID is invalid"
// *Cause: The database operation execution ID provided was invalid.
// *Action: Supply a database operation execution ID greater than 0.
/
/ =======================================
/ 13825 - 13849 reserved for SQL profiles
/ =======================================
13825, 00000, "missing SQL statement text"
// *Cause: No SQL text was provided to the create SQL profile or patch operation.
// *Action: Retry with properly specified SQL text.
13826, 00000, "empty SQL profile or patch not allowed"
// *Cause: No attributes were specified to the create SQL profile or patch
// operation.
// *Action: Retry with at least one hint specified.
13827, 00000, "null or zero length attribute not allowed"
// *Cause: One of the attributes within the SQL profile or patch was not
// properly specified.
// *Action: Retry with a fully specified SQL profile or patch.
13828, 00000, "generated SQL profile or patch name %s already exists"
// *Cause: A SQL profile or patch already exists with the name generated by
// the system.
// *Action: Retry the operation as the generated name is time sensitive.
13829, 00000, "SQL profile or patch named %s already exists"
// *Cause: A SQL profile or patch already exists with the name specified.
// *Action: Specify a different name or drop the existing SQL profile or patch.
13830, 00000, "SQL profile or patch with category %s already exists for this SQL statement"
// *Cause: A SQL profile or patch already exists for the given SQL statement
// and category.
// *Action: Drop or update the existing SQL profile or patch.
13831, 00000, "SQL profile or patch name specified is invalid"
// *Cause: An invalid SQL profile or patch name was specified.
// *Action: Supply a name not exceeding 30 characters or
// look for the underlying error on the error message stack.
13832, 00000, "category name specified is invalid"
// *Cause: An invalid category name was specified.
// *Action: Supply a category name not exceeding 30 characters or
// look for the underlying error on the error message stack.
13833, 00000, "SQL profile or patch named %s doesn't exist"
// *Cause: A SQL profile or patch name was specified that doesn't exist.
// *Action: Verify the name of the SQL profile or patch.
13834, 00000, "name of SQL profile or patch to be cloned must be provided"
// *Cause: A SQL profile or patch name was not provided as the from target of
// a clone SQL profile or patch operation.
// *Action: Provide the name of the SQL profile or patch being cloned.
13835, 00000, "invalid attribute name specified"
// *Cause: An invalid attribute name was specified for an alter SQL profile
// or patch operation.
// *Action: Verify the name of the attribute.
13836, 00000, "invalid attribute value specified"
// *Cause: An invalid attribute value was specified for an alter SQL profile
// or patch operation.
// *Action: Verify the attribute value.
13837, 00000, "invalid HASH_VALUE"
// *Cause: An invalid HASH_VALUE was passed to a create SQL profile operation
// *Action: Verify the HASH_VALUE.
13838, 00000, "invalid ADDRESS value"
// *Cause: An invalid ADDRESS value was passed to a create SQL profile operation.
// *Action: Verify the ADDRESS value.
13839, 00000, "V$SQL row doesn't exist with given HASH_VALUE and ADDRESS."
// *Cause: A HASH_VALUE and ADDRESS combination passed to the create SQL profile
// operation doesn't coorespond to an existing V$SQL entry.
// *Action: Verify the HASH_VALUE and ADDRESS in V$SQL.
13840, 00000, "Concurrent DDL Error in create SQL profile operation."
// *Cause: A concurrent DDL operation was performed during a create or replace
// sql profile operation.
// *Action: Try operation again
13841, 00000, "SQL profile named %s already exists for a different signature/category pair"
// *Cause: A SQL profile already exists with the name specified under a
// different signature/category pair so it cannot be replaced, even
// with FORCE specified.
// *Action: Specify a different name or drop the existing SQL profile.
13842, 00000, "no SELECT privilege on DBA_SQL_PROFILES"
// *Cause: A user has tried to perform an operation that requires SELECT
// privileges on the DBA_SQL_PROFILES view.
// *Action: Either perform the operation as another user or get the privilege
13843, 00000, "no SQL profile with name like \"%s\" exists for category like \"%s\""
// *Cause: A user tried to perform an operation by specifying a profile name/
// category filter that did not target any profiles
// *Action: Try a different filter after checking the profile name/category
13844, 00000, "no new SQL profile name or category specified."
// *Cause: A user called remap_stgtab_sqlprof without specifying new values
// for the sql profile name or category. At least one is required.
// *Action: Specify either a new profile name, or a new category, or both
13845, 00000, "invalid SQL profile XML specification provided"
// *Cause: The supplied XML specification for the SQL profile did not adhere
// to the proper schema.
// *Action: Check the syntax and try again.
13846, 00000, "Cannot create SQL plan baseline on the given plan"
// *Cause: There are either multiple plans exist for the given value or the
// plan is not reproducible.
// *Action: Call Oracle Support.
13847, 00000, "The plan with plan hash value %s does not exist"
// *Cause: The give plan does not exist.
// *Action: Check the available plans.
13848, 00000, "Database link provided for the task operation was different than the one used with task creation API."
// *Cause: All SQL tuning advisor APIs executed from a physical standby database are
// required to use the same database link.
// *Action: Retry the operation by providing the database link used for
// task creation.
/
/ =============================================
/ 13850 - 13899 reserved for end-to-end tracing
/ =============================================
13850, 00000, "Tracing for client identifier %s is not enabled"
// *Cause: Attempt to disable a client identifier tracing which
// was never enabled
// *Action: Supply correct client identifier
/
13851, 00000, "Tracing for client identifier %s is already enabled"
// *Cause: Attempt to enable a client identifier tracing which
// has been already enabled
// *Action: Supply correct client identifier, or disable and re-enable
// tracing with different bind/wait options
/
13852, 00000, "Tracing for service(module/action) %s is not enabled"
// *Cause: Attempt to disable a service-level tracing which
// was never enabled
// *Action: Supply correct service(module/action) name
/
13853, 00000, "Tracing for service (module/action) %s is already enabled"
// *Cause: Attempt to enable a service-level tracing which
// has been already enabled
// *Action: Supply correct service(module/action), or disable and re-enable
// tracing with different bind/wait options
/
13854, 00000, "Tracing for service(module/action) %s on instance %s is not enabled"
// *Cause: Attempt to disable a service-level tracing which
// was never explicitly enabled on a specific instance
// *Action: Supply correct service(module/action) name
/
13855, 00000, "Tracing for service (module/action) %s on instance %s is already enabled"
// *Cause: Attempt to enable a service-level tracing which
// has been already enabled on a specific instance
// *Action: Supply correct service(module/action), or disable and re-enable
// tracing with different bind/wait options
/
13856, 00000, "Service name must be specified"
// *Cause: Omitting service name while enabling/disabling tracing or
// aggregation
// *Action: Supply the service name
/
13857, 00000, "Invalid module name"
// *Cause: Module name is too long (exceeding 48 characters)
// *Action: Supply correct name
/
13858, 00000, "Invalid action name"
// *Cause: Action name is too long (exceeding 32 characters)
// *Action: Supply correct name
/
13859, 00000, "Action cannot be specified without the module specification"
// *Cause: Action name is specified, but the module name is not
// *Action: Supply the module name
/
13860, 00000, "Invalid service name"
// *Cause: Service name is too long (exceeding 64 characters)
// *Action: Supply correct name
/
13861, 00000, "Statistics aggregation for client identifier %s is already enabled"
// *Cause: Attempt to enable a client identifier aggregation which
// has been already enabled
// *Action: Supply correct client identifier
/
13862, 00000, "Statistics aggregation for client identifier %s is not enabled"
// *Cause: Attempt to disable a client identifier statistics aggregation which
// was never enabled
// *Action: Supply correct client identifier
/
13863, 00000, "Statistics aggregation for service(module/action) %s is not enabled"
// *Cause: Attempt to disable a service-level statistics aggregation which
// was never enabled
// *Action: Supply correct service(module/action) name
/
13864, 00000, "Statistics aggregation for service (module/action) %s is already enabled"
// *Cause: Attempt to enable a service-level statistics aggregation which
// has been already enabled
// *Action: Supply correct service(module/action)
/
13865, 00000, "Module name must be specified"
// *Cause: Attempt to enable/disable a service-level statistics aggregation
// without a module specification
// *Action: Supply module name
/
13866, 00000, "Client identifier must be specified"
// *Cause: Omitting client identifier while enabling/disabling tracing or
// aggregation
// *Action: Supply the client identifier
/
13867, 00000, "Database-wide SQL tracing is already enabled"
// *Cause: Attempt to enable a database-level tracing which
// has been already enabled
// *Action: Disable and re-enable tracing with different bind/wait options
/
13868, 00000, "Instance-wide SQL tracing on instance %s is not enabled"
// *Cause: Attempt to disable a service-level tracing which
// was never explicitly enabled on a specific instance
// *Action: No action required
/
13869, 00000, "Instance-wide SQL tracing on instance %s is already enabled"
// *Cause: Attempt to enable an instance-level tracing which
// has been already enabled on a specific instance
// *Action: Disable and re-enable tracing with different bind/wait options
/
13870, 00000, "Database-wide SQL tracing is not enabled"
// *Cause: Attempt to disable a database-level tracing which
// was never enabled
// *Action: No action required
/
13871, 00000, "Invalid instance name"
// *Cause: Instance name is too long (exceeding 16 characters)
// *Action: Supply correct name
/
/ 13900 - 13949 reserved for threshold-based alert
/
13900, 00000, "missing or invalid parameter %s"
// *Cause: A call to SET_THRESHOLD procedure was either missing a parameter,
// or the parameter was invalid.
// *Action: Specify a valid value for this parameter.
/
13901, 00000, "Object %s was not found."
// *Cause: An object name was passed to SET_THRESHOLD procedure that did not
// map to a valid object.
// *Action: Specify a valid object name.
/
13902, 00000, "The specified file %s is not a data file."
// *Cause: The object name was passed to a SET_THRESHOLD procedure that did
// not map to a valid data file.
// *Action: Specify a valid data file name.
/
13903, 00000, "Invalid combination of %s threshold value and operator."
// *Cause: A non-positive number was used for "Blocked User Session
// Count" metrics while operator contains equal.
// *Action: Use a positive number for the threshold value or use "greater than"
// operator.
/
13904, 00000, "The file has been dropped and recreated during the procedure call."
// *Cause: The file on which threshold is specified was dropped and
// recreated during the procedure call.
// *Action: Retry this operation.
/
13905, 00000, "Critical or warning threshold have incorrect values"
// *Cause: The tablespace threshold values can be in the range 0 to 100
// only.
// *Action: Check the threshold values
/
13906, 00000, "The tablespace is not of the right type."
// *Cause: An attempt was made to set a threshold on dictionary-managed
// tablespaces.
// *Action: Check the tablespace type and reissue the command.
/
13907, 00000, "Threshold value is invalid."
// *Cause: An attempt was made to specify an invalid value for critical
// or warning thresholds.
// *Action: Use non-negative integers only for threshold values.
/
13908, 00000, "Invalid combination of metrics id and object type parameters."
// *Cause: An attempt was made to specify an invalid combination of metrics id // and object type parameters.
// *Action: Specify a valid combination of metrics id and object type
// parameters.
/
13909, 00000, "Invalid combination of threshold value and operator."
// *Cause: An attempt was made to specify an invalid combination of threshold
// value and operator.
// *Action: Check the operator and threshold values and reissue statement.
/
13910, 00000, "Parameter %s cannot be NULL."
// *Cause: An attempt was made to call GET_THRESHOLD procedure without a
// required parameter.
// *Action: Specify a valid value for this parameter.
/
13911, 00000, "Threshold not found"
// *Cause: The threshold did not exist with the specified threshold key.
// *Action: No action required.
/
13912, 00000, "Critical threshold value is less than warning threshold value."
// *Cause: An attempt was made to call SET_THRESHOLD procedure with the
// critical threshold value less than the warning threshold value.
// *Action: Check the threshold values and reissue the statement.
/
13913, 00000, "The threshold cannot be set when SYSAUX is offline."
// *Cause: SET_THRESHOLD procedure was called when SYSAUX tablespace was
// offline.
// *Action: Call SET_THRESHOLD procedure when SYSAUX is online.
/
13914, 00000, "Threshold notification failed."
// *Cause: An error occurred when sending notification for this threshold.
// *Action: Ensure that you have enough space on SYSAUX tablespace and retry
// this operation.
/
13915, 00000, "Critical byte based free space threshold value is greater than warning threshold value."
// *Cause: An attempt was made to call SET_THRESHOLD procedure with the bytes based
// critical threshold value greater than the warning threshold value.
// *Action: Check the threshold values and reissue the statement.
/
13916, 00000, "Invalid value \"%s\" specified for parameter \"%s\""
// *Cause: An invalid value was specified for the the given parameter.
// *Action: Correct the value being specified for the parameter.
/
13917, 0000, "Posting system alert with reason_id %s failed with code [%s] [%s]"
// *Cause: Connection to the database is dead, or invalid parameter
// to alert routine.
// *Action: If this condition repeats, please contact Oracle Support.
/
13918, 0000, "Updating system alert with reason_id %s failed; previous alert not found"
// *Cause: System Error: An attempt to update a system alert failed.
// The alert was improperly cleared from WRI$_ALERT_OUTSTANDING.
// *Action: Do not delete from WRI$_ALERT_OUTSTANDING.
// If this condition repeats, please contact Oracle Support.
/
13919, 00000, "Cannot specify values for parameter \"%s\" and for parameter \"%s\""
// *Cause: Can only specify a value for one or the other.
// *Action: Pass just one of the parameters.
/
13920, 00000, "Threshold cannot be set when database is in read-only mode."
// *Cause: SET_THRESHOLD procedure was called when database was open in read-only
// mode.
// *Action: Call SET_THRESHOLD procedure when database is open in read/write mode.
/
/
/ 13950 - 13969 reserved for MMON infrastructure
/
13950, 00000, "MMON action time limit exceeded"
// *Document: NO
// *Cause: MMON action did not complete within the system specified
// time frame.
// *Action: None.
/
13951, 00000, "MMON sub-action time limit exceeded"
// *Cause: MMON sub-action did not complete within the system specified
// time frame.
// *Action: None.
/
/
/ 13970-13998 reserved for common reporting framework
/
13970, 00000, "Invalid name of \"%s\" given"
// *Cause: Passed an invalid component, report, or transformation name
// to the framework. Names must be alphanumeric and can contain the
// underscore (_) character.
// *Action: Try again with a valid name
/
13971, 00000, "Unknown %s"
// *Cause: Passed an unknown component, report, or transformation to the
// framework.
// *Action: Give a different name
/
13972, 00000, "Unknown %s for this %s"
// *Cause: An object with the first name is unknown within the naming scope
// of the second name
// *Action: Change the parameters passed in or register the proper object
/
13973, 00000, "Unknown %s for this %s"
// *Cause: An object is unknown within the given naming scope
// *Action: Change the parameters passed in or register the proper object
/
13974, 00000, "%s with name \"%s\" already exists"
// *Cause: An object with the given name already exists
// *Action: Give a different name
/
13975, 00000, "%s with name \"%s\" already exists for %s \"%s\""
// *Cause: An object with the first name already exists within the naming
// scope of the second name
// *Action: Give a different name
/
13976, 00000, "Improperly-formed report tag"
// *Cause: The top-level report tag was not built properly.
// *Action: Ensure that the report tag is built using the common tag
// library function.
/
13977, 00000, "Invalid content type"
// *Cause: An invalid content type was passed to the register format API
// *Action: Correct your code to use the values in dbmsrep.sql
/
13978, 00000, "Invalid reference string parameter or value"
// *Cause: An invalid parameter/value was passed to a dbms_report API
// *Action: Ensure that the parameter names and values are alphanumeric.
/
13979, 00000, "Filename too long"
// *Cause: An invalid file name was passed to STORE_FILE
// *Action: Ensure that the filename is less than 500 bytes
/
13980, 00000, "Invalid file URL"
// *Cause: A URL with invalid syntax was provided, either directly to the
// function or via an XML IMPORT or INCLUDE.
// *Action: Check the URL.
/
13981, 00000, "Invalid file URL or path prefix"
// *Cause: Either a URL or path prefix with invalid syntax was provided.
// *Action: Check the URL
/
13982, 00000, "Could not find file at URL provided"
// *Cause: The file requested could not be found in the given location.
// *Action: Check the URL provided.
/
13983, 00000, "Missing <body> tag from HTML"
// *Cause: An HTML document was passed to the function missing its <body>
// tag.
// *Action: Check the HTML source.
/
13984, 00000, "Invalid reference string"
// *Cause: The given reference string could not be parsed.
// *Action: Check the reference string syntax.
/
13985, 00000, "Invalid URL provided to servlet"
// *Cause: An invalid URL was provided to the servlet.
// *Action: Check the URL.
/
13986, 00000, "Error \%s received from XPath engine"
// *Cause: An error was received from the xpath library during an xpath
// operation.
// *Action: Check xmlerr.h to understand the cause of the error.
/
13987, 00000, "Invalid input to build common <%s> tag"
// *Cause: Invalid input was given when attempting to build a common tag.
// *Action: Check the function input to ensure that all necessary information
// is given.
/
13988, 00000, "Invalid input given to variable argument list report function."
// *Cause: An invalid parameter was provided to one of the report
// framework variable argument list functions.
// *Action: Check the function input and try again.
/
13989, 00000, "Invalid input given to structured argument list report function."
// *Cause: An invalid parameter was provided to one of the report
// framework structured argument list functions.
// *Action: Check the function input and try again.
/
13990, 00000, "Invalid tag name given to common tag callout function."
// *Cause: An invalid tag name was provided to the report
// framework common tag callout function.
// *Action: Check the function input and try again.
/
13991, 00000, "failed to stop report capture on all instances"
// *Cause: The finish_report_capture procedure could not run successfully on
// all instances.
// *Action: Verify that all the database instances are active and running.
/
/13999, 00000, "%s"
// *Cause: This is an internal Server Manageability Error
// *Action: Contact Oracle Support Services
/
/
/ 14000 - 14999 reserved for Partitioned object project
/
/ 14000 - 14099 reserved for parsing new syntax introduced by the Partitioned
/ object project
14000, 00000, "only one LOCAL clause may be specified"
// *Cause: CREATE INDEX statement contained more than one LOCAL clause
// *Action: Specify LOCAL option at most once
14001, 00000, "LOCAL clause contradicts previosly specified GLOBAL clause"
// *CAUSE: CREATE INDEX statement contained a GLOBAL clause and a LOCAL
// clause
// *Action: Specify LOCAL or GLOBAL clause, but not both
14002, 00000, "only one GLOBAL clause may be specified"
// *Cause: CREATE INDEX statement contained more than one GLOBAL clause
// *Action: Specify GLOBAL option at most once
14003, 00000, "GLOBAL clause contradicts previosly specified LOCAL clause"
// *CAUSE: CREATE INDEX statement contained a LOCAL clause and a GLOBAL
// clause
// *Action: Specify GLOBAL or LOCAL clause, but not both
14004, 00000, "missing PARTITION keyword"
// *Cause: keyword PARTITION missing
// *Action: supply missing keyword
14005, 00000, "missing RANGE keyword"
// *Cause: keyword RANGE missing
// *Action: supply missing keyword
14006, 00000, "invalid partition name"
// *Cause: a partition name of the form <identifier> is
// expected but not present.
// *Action: enter an appropriate partition name.
14007, 00000, "missing LESS keyword"
// *Cause: keyword LESS missing
// *Action: supply missing keyword
14008, 00000, "missing THAN keyword"
// *Cause: keyword THAN missing
// *Action: supply missing keyword
14009, 00000, "partition bound may not be specified for a LOCAL index partition"
// *Cause: while parsing a CREATE INDEX statement to create a LOCAL
// partitioned index, <partition-description> of one of partitions
// was found to contain VALUES LESS THAN clause which is illegal since
// a LOCAL index inherits partition bounds from its base table
// *Action: remove all VALUES LESS THAN clauses from descriptions of LOCAL
// index partitions
14010, 00000, "this physical attribute may not be specified for an index partition"
// *Cause: unexpected option was encountered while parsing physical
// attributes of an index partition; valid options for Range or
// Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE,
// STORAGE, PCTFREE; only TABLESPACE may be specified for Hash
// partitions
// *Action: remove invalid option(s) from the list of physical attributes
// of an index partition
// *Comment: this error could have resulted from omission of a
// terminating (right) parenthesis following the list of
// partition descriptions
14011, 00000, "names assigned to resulting partitions must be distinct"
// *Cause: Names of partitions resulting from splitting of an
// existing table or index partition are not distinct
// *Action: rename resulting partition(s) to ensure that their names
// are distinct and different from those of any other partition
// of the table or index
14012, 00000, "resulting partition name conflicts with that of an existing partition"
// *Cause: Name of a partition resulting from splitting of an
// existing table or index partition is identical to that
// of some other existing partition of that table or index
// *Action: rename resulting partition(s) to ensure that their names
// are distinct and different from those of any other partition
// of the table or index
14013, 00000, "duplicate partition name"
// *Cause: Name of a partition of a table or index being created is
// not unique
// *Action: rename partition(s) to ensure that their names are unique
// among partitions of the table or index being created
14014, 00000, "maximum number of partitioning columns is 16"
// *Cause: number of columns in a partitioning column list exceeded
// the legal limit of 16
// *Action: modify partitioning column list so that it consists of at
// most 16 columns
14015, 00000, "too many partition descriptions"
// *Cause: CREATE TABLE or CREATE INDEX contained too many partition
// descriptions; maximum number of partitions is 1048575 (1024K-1).
// *Action: Reduce number of partitions to not exceed 1048575 (1024K -1).
14016, 00000, "underlying table of a LOCAL partitioned index must be partitioned"
// *Cause: User attempted to create a LOCAL partitioned index on a
// non-partitioned table which is illegal. Only GLOBAL indices
// (partitioned or otherwise) may be created on a
// non-partitioned table.
// *Action: Correct the statement and reenter
14017, 00000, "partition bound list contains too many elements"
// *Cause: Partition bound list contained more elements than there are
// partitioning columns
// *Action: Ensure that the number of elements in partition bound list is
// equal to the number of partitioning columns of the table or index
14018, 00000, "partition bound list contains too few elements"
// *Cause: Partition bound list contained fewer elements than there are
// partitioning columns
// *Action: Ensure that the number of elements in partition bound list is
// equal to the number of partitioning columns of the table or index
14019, 00000, "partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE"
// *Cause: Partition bound list contained an element of invalid type
// (i.e. not a number, non-empty string, datetime or interval literal,
// or MAXVALUE)
// *Action: Ensure that all elements of partition bound list are of valid type
14020, 00000, "this physical attribute may not be specified for a table partition"
// *Cause: unexpected option was encountered while parsing physical
// attributes of a table partition; valid options for Range or
// Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE,
// STORAGE, PCTFREE, and PCTUSED; only TABLESPACE may be specified
// for Hash partitions
// *Action: remove invalid option(s) from the list of physical attributes
// of a table partition
// *Comment: this error could have resulted from omission of a
// terminating (right) parenthesis following the list of
// partition descriptions
14021, 00000, "MAXVALUE must be specified for all columns"
// *Cause: In the VALUES LESS THAN clause for the highest (last) partition
// of a GLOBAL index, MAXVALUE must be specified for all columns
// *Action: Ensure that VALUES LESS THAN clause for the last partition of a
// GLOBAL index has MAXVALUE specified for all columns
14022, 00000, "creation of LOCAL partitioned cluster indices is not supported"
// *Cause: An attempt was made to create a LOCAL partitioned
// cluster index, which is currently illegal
// *Action: Remove LOCAL along with <partition description>s, if any, from
// the CREATE INDEX statement.
14023, 00000, "creation of GLOBAL partitioned cluster indices is not supported"
// *Cause: An attempt was made to create a GLOBAL partitioned
// cluster index, which is currently illegal
// *Action: Remove PARTITION BY RANGE clause along with
// <partition description>s from the CREATE INDEX statement.
14024, 00000, "number of partitions of LOCAL index must equal that of the underlying table"
// *Cause: User attempted to create a LOCAL partitioned index with a
// number of partitions which is different from that of the
// underlying table.
//* Action: Correct the CREATE INDEX statement to specify a correct
// number of partitions
14025, 00000, "PARTITION may not be specified for a materialized view or a materialized view log"
// *Cause: PARTITION option was encountered while parsing a
// definition of a materialized view or a materialized view log
// *Action: Ensure that a definition of a MATERIALIZED VIEW does not
// include invalid options
14026, 00000, "PARTITION and CLUSTER clauses are mutually exclusive"
// *Cause: definition of a table contained both PARTITION and CLUSTER clauses
// which is illegal
// *Action: Remove one of the conflicting clauses
14027, 00000, "only one PARTITION clause may be specified"
// *Cause: CREATE TABLE statement contained more than one PARTITION clause
// *Action: Specify PARTITION option at most once
14028, 00000, "missing AT or VALUES keyword"
// *Cause: keyword AT or VALUES missing
// *Action: supply missing keyword
14029, 00000, "GLOBAL partitioned index must be prefixed"
// *Cause: partitioning columns of a global partitioned index must
// form a prefix of the index' key columns
// *Action: Ensure that the GLOBAL partitioned index being created is prefixed
14030, 00000, "non-existent partitioning column in CREATE TABLE statement"
// *Cause: Partitioning column specified in CREATE TABLE statement is
// not one of columns of the table being created.
// *Action: Ensure that all columns in the partitioning column list
// are columns of the table being created.
14031, 00000, "partitioning column may not be of type LONG or LONG RAW"
// *Cause: Partitioning column specified by the user was of type LONG
// or LONG RAW, which is illegal.
// *Action: Ensure that no partitioning column is of type LONG or LONG RAW.
14032, 00000, "partition bound of partition number %s is too high"
// *Cause: High bound of the partition whose number (partitions are
// numbered starting with 1) is displayed in this message
// did not collate lower than that of the following partition,
// which is illegal.
// *Action: Ensure that high bound of every partition (except for the last
// one) collates lower than that of a following partition.
14033, 00000, "ctchvl: unexpected strdef type"
// *Document: NO
// *Cause: opndef representation of an element of partition bound list had
// strtyp set to unexpected value (must be STRTCONS or STRTMAXV)
// *Action: Ensure that prsott and prspstr agree on what constitutes a valid
// element of partition bound list
14034, 00000, "ctchvl: unexpected operand type"
// *Document: NO
// *Cause: opndef representation of an element of partition bound list had
// opntyp set to unexpected value (must be OPNTSTR)
// *Action: Ensure that prsott and prspstr agree on what constitutes a valid
// element of partition bound list
14035, 00000, "ctchvl: unexpected string data type"
// *Document: NO
// *Cause: opndef representation of a string element of partition bound list
// had opndty set to unexpected value (must be OPNCHR or OPNNUM)
// *Action: Ensure that prsott and prspstr agree on what constitutes a valid
// element of partition bound list
14036, 00000, "partition bound value too large for column"
// *Cause: Length of partition bound value is longer than that of the
// corresponding partitioning column.
// *Action: Ensure that lengths of high bound values do not exceed those of
// corresponding partitioning columns
14037, 00000, "partition bound of partition \"%s\" is too high"
// *Cause: High bound of the partition whose name (explicitly specified
// by the user) is displayed in this message did not collate
// lower than that of the following partition, which is illegal.
// *Action: Ensure that high bound of every partition (except for the last
// one) collates lower than that of a following partition.
14038, 00000, "GLOBAL partitioned index must be prefixed"
// *Cause: User attempted to create a GLOBAL non-prefixed partitioned index
// which is illegal
// *Action: If the user, indeed, desired to create a non-prefixed
// index, it must be created as LOCAL; otherwise, correct the list
// of key and/or partitioning columns to ensure that the index is
// prefixed
14039, 00000, "partitioning columns must form a subset of key columns of a UNIQUE index"
// *Cause: User attempted to create a UNIQUE partitioned index whose
// partitioning columns do not form a subset of its key columns
// which is illegal
// *Action: If the user, indeed, desired to create an index whose
// partitioning columns do not form a subset of its key columns,
// it must be created as non-UNIQUE; otherwise, correct the
// list of key and/or partitioning columns to ensure that the index'
// partitioning columns form a subset of its key columns
14040, 00000, "inadequate number of arguments passed to tbl$or$idx$part$num"
// *Document: NO
// *Cause: tbl$or$idx$part$num was supplied with fewer than 5
// arguments which is illegal
// *Action: Supply tbl$or$idx$part$num with table name, index
// dictionary object number or 0, dimension number, composite
// partition number (if dimension is 2) or 0, and as many expressions
// (e.g. column names) as there are partitioning columns
// in the table or index mapping into a partition of which
// is to be determined
14041, 00000, "partition bound may not be specified for resulting partitions"
// *Cause: while parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement,
// <partition-description> of a resulting partition was found to
// contain VALUES LESS THAN clause which is illegal
// *Action: remove VALUES LESS THAN clause from the description(s) of
// partitions resulting from splitting an existing table or
// index partition
14042, 00000, "partition bound may not be specified for a partition being moved, modified or rebuilt"
// *Cause: while parsing an ALTER {TABLE|INDEX} MODIFY PARTITION,
// ALTER TABLE MOVE PARTITION, or ALTER INDEX REBUILD PARTITION
// statement, description of new physical attributes of the
// partition being moved, modified, or rebuilt was found to
// contain VALUES LESS THAN clause which is illegal
// *Action: remove VALUES LESS THAN clause from the description of new
// attributes of the partition being moved, modified, or rebuilt
14043, 00000, "only one partition may be added"
// *Cause: ALTER TABLE ADD PARTITION contained descriptions of more than one
// partition to be added
// *Action: Ensure that the statement contains exactly one partition
// definition and that it does not contain any commas
14044, 00000, "only one partition may be moved"
// *Cause: ALTER TABLE MOVE PARTITION contained descriptions of more than one
// partition to be moved
// *Action: Ensure that the statement describes exactly one partition
// to be moved and that it does not contain any commas
14045, 00000, "only one partition may be modified"
// *Cause: ALTER TABLE|INDEX MODIFY PARTITION contained descriptions of
// more than one partition to be modified
// *Action: Ensure that the statement describes exactly one partition
// to be modified and that it does not contain any commas
14046, 00000, "a partition may be split into exactly two new partitions"
// *Cause: ALTER TABLE|INDEX SPLIT PARTITION did not contain
// descriptions of exactly two new partitions into which an existing
// table or index partition was to be split
// *Action: Ensure that the statement describes exactly two partition
// into which an existing partition is to be split
14047, 00000, "ALTER TABLE|INDEX RENAME may not be combined with other operations"
// *Cause: ALTER TABLE or ALTER INDEX statement attempted to combine
// a RENAME operation with some other operation which is illegal
// *Action: Ensure that RENAME operation is the sole operation specified in
// ALTER TABLE or ALTER INDEX statement;
14048, 00000, "a partition maintenance operation may not be combined with other operations"
// *Cause: ALTER TABLE or ALTER INDEX statement attempted to combine
// a partition maintenance operation (e.g. MOVE PARTITION) with some
// other operation (e.g. ADD PARTITION or PCTFREE which is illegal
// *Action: Ensure that a partition maintenance operation is the sole
// operation specified in ALTER TABLE or ALTER INDEX statement;
// operations other than those dealing with partitions,
// default attributes of partitioned tables/indices or
// specifying that a table be renamed (ALTER TABLE RENAME) may be
// combined at will
14049, 00000, "invalid ALTER TABLE MODIFY PARTITION option"
// *Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS,
// STORAGE, BACKUP, ALLOCATE EXTENT, or DEALLOCATE UNUSED was
// specified in an ALTER TABLE MODIFY PARTITION statement for
// a Range or Composite Range partition.
// *Action: Specify only legal options.
14050, 00000, "invalid ALTER INDEX MODIFY PARTITION option"
// *Cause: An option other than INITRANS, MAXTRANS, STORAGE,
// or DEALLOCATE UNUSED was specified in an
// ALTER INDEX MODIFY PARTITION statement.
// *Action: Specify only legal options.
14051, 00000, "invalid ALTER MATERIALIZED VIEW option"
// *Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE,
// or BACKUP was specified in an ALTER MATERIALIZED VIEW statement.
// *Action: Specify only legal options.
14052, 00000, "partition-extended table name syntax is disallowed in this context"
// *Cause: User attempted to use partition-extended table name syntax
// in illegal context (i.e. not in FROM-clause or INSERT, DELETE,
// or UPDATE statement)
// *Action: Avoid use of partition-extended table name in contexts other
// those mentioned above.
14053, 00000, "illegal attempt to modify %s in %s statement"
// *Cause: Certain attributes of objects (e.g. tables) may be
// specified at creation time, but may not be modified using ALTER
// statement. Unfortunately, user specified one of such attributes.
// *Action: Ensure that ALTER statement specifies new values only for
// attributes which may be changed once an object has been created
14054, 00000, "invalid ALTER TABLE TRUNCATE PARTITION option"
// *Cause: Name of the partition to be truncated may be followed by
// DROP STORAGE or REUSE STORAGE
// *Action: Ensure that no options besides DROP STORAGE or REUSE STORAGE
// are specified with ALTER TABLE TRUNCATE PARTITION
14055, 00000, "keyword REBUILD in ALTER INDEX REBUILD must immediately follow <index name>"
// *Cause: ALTER INDEX statement contained REBUILD keyword following
// some index attributes (e.g. INITRANS.)
// *Action: Ensure that keyword REBUILD immediately follows the name
// of the index being altered
14056, 00000, "partition number %s: sum of PCTUSED and PCTFREE may not exceed 100"
// *Cause: the sum of PCTUSED and PCTFREE for a partition whose number
// (partitions are numbered starting with 1) is displayed in this
// message exceeds 100. Note that if PCTUSED and/or PCTFREE
// values for this partition were not specified explicitly,
// default values for the partitioned table or index would be
// used. If, in turn, default PCTUSED and/or PCTFREE values
// for the partitioned table or index were not specified,
// system defaults would be used.
// *Action: ensure that a sum of PCTUSED and PCTFREE for the partition
// does not exceed 100
14057, 00000, "partition \"%s\": sum of PCTUSED and PCTFREE may not exceed 100"
// *Cause: the sum of PCTUSED and PCTFREE for a partition whose name
// (explicitly specified by the user) is displayed in this
// message exceeds 100. Note that if PCTUSED and/or PCTFREE
// values for this partition were not specified explicitly,
// default values for the partitioned table or index would be
// used. If, in turn, default PCTUSED and/or PCTFREE values
// for the partitioned table or index were not specified,
// system defaults would be used.
// *Action: ensure that a sum of PCTUSED and PCTFREE for the partition
// does not exceed 100
14058, 00000, "partition number %s: INITRANS value must be less than MAXTRANS value"
// *Cause: Value of INITRANS was found to be greater than that of MAXTRANS
// for a partition whose number (partitions are numbered starting
// with 1) is displayed in this message. Note that if INITRANS
// and/or MAXTRANS values for this partition were not specified
// explicitly, default values for the partitioned table or index
// would be used. If, in turn, default INITRANS and/or MAXTRANS
// values for the partitioned table or index were not specified,
// system defaults would be used.
// *Action: ensure that value of INITRANS (whether specified explcitly or
// derived from the default value for the partitioned table or
// index) is no greater than that of MAXTRANS
14059, 00000, "partition \"%s\": INITRANS value must be less than MAXTRANS value"
// *Cause: Value of INITRANS was found to be greater than that of MAXTRANS
// for a partition whose name (explicitly specified by the user)
// is displayed in this message. Note that if INITRANS
// and/or MAXTRANS values for this partition were not specified
// explicitly, default values for the partitioned table or index
// would be used. If, in turn, default INITRANS and/or MAXTRANS
// values for the partitioned table or index were not specified,
// system defaults would be used.
// *Action: ensure that value of INITRANS (whether specified explcitly or
// derived from the default value for the partitioned table or
// index) is no greater than that of MAXTRANS
14060, 00000, "data type or length of a table partitioning column may not be changed"
// *Cause: User issued ALTER TABLE statement attempting to modify
// data type and/or length of a column used to partition the
// table named in ALTER TABLE statement, which is illegal
// *Action: Avoid modifying data type and/or length of table
// partitioning column(s)
14061, 00000, "data type or length of an index partitioning column may not be changed"
// *Cause: User issued ALTER TABLE statement attempting to modify
// data type and/or length of a column used to partition some index
// defined on the table named in ALTER TABLE statement, which is
// illegal
// *Action: Avoid modifying data type and/or length of index
// partitioning column(s)
14062, 00000, "one or more of table's partitions reside in a read-only tablespace"
// *Cause: User issued ALTER TABLE statement attempting to modify
// an existing VARCHAR2 (or VARCHAR) column to be of type CHAR
// (or CHARACTER), increase length of an existing CHAR (or
// CHARACTER) column, or add a column with user-specified default for
// a table one or more partitions of which reside in read-only
// tablespaces, which is illegal
// *Action: Avoid performing aformentioned operations on a partitioned
// table one or more partitions of which reside in read-only
// tablespaces
14063, 00000, "Unusable index exists on unique/primary constraint key"
// *Cause: User attempted to add or enable a primary key/unique constraint
// on column(s) of a table on which there exists an index marked
// Index Unusable.
// *Action: Drop the existing index or rebuild it using ALTER INDEX REBUILD
14064, 00000, "Index with Unusable partition exists on unique/primary constraint key"
// *Cause: User attempted to add or enable a primary key/unique constraint
// on column(s) of a table on which there exists an index one or
// more partitions of which are marked Index Unusable.
// *Action: Drop the existing index or rebuild unusable partitions it
// using ALTER INDEX REBUILD PARTITION
14065, 00000, "ALLOCATE STORAGE may not be specified for a partitioned table"
// *Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement
// issued against a partitioned table which is illegal.
// *Action: Remove the illegal option. If it is desired to add
// storage to individual partitions, ALLOCATE STORAGE clause
// may be specified with ALTER TABLE MODIFY PARTITION statement.
14066, 00000, "illegal option for a non-partitioned index-organized table"
// *Cause: An attempt was made to issue a CREATE or ALTER TABLE
// command on a non-partitioned IOT, but the command contains an
// option that is legal only for partitioned index-organized tables.
// Such options are: ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT.
// *Action: Remove the illegal option(s) from the command.
14067, 00000, "duplicate TABLESPACE_NUMBER specification"
// *Cause: TABLESPACE_NUMBER clause was specified more than once for
// an table, index or an index partition
// *Action: Correct the code generating text of CREATE INDEX statement
// sent to the slaves
14068, 00000, "TABLESPACE and TABLESPACE_NUMBER may not be both specified"
// *Cause: Both TABLESPACE and TABLESPACE_NUMBER clauses were specified
// for a table, index or an index partition
// *Action: Correct the code generating text of CREATE INDEX statement
// sent to the slaves
14069, 00000, "invalid TABLESPACE_NUMBER value"
// *Cause: The TABLESPACE_NUMBER value is not an integer between 0 and
// 0x7FFFFFFF
// *Action: Correct the code generating text of CREATE INDEX statement
// sent to the slaves
14070, 00000, "option may be specified only for partitioned indices or with REBUILD"
// *Cause: User issued ALTER INDEX statament containing an option
// which is legal only for partitioned indices or in conjunction
// with REBUILD against a non-partitioned index. Such options are:
// PCTFREE, TABLESPACE, [NO]PARALLEL and INITIAL, FREELISTS, and
// FREELIST GROUPS inside STORAGE clause
// *Action: Remove illegal option(s).
14071, 00000, "invalid option for an index used to enforce a constraint"
// *Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS,
// MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE,
// UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was
// specified for an index used to enforce a constraint.
// *Action: Choose one of the valid index options.
14072, 00000, "fixed table may not be truncated"
// *Cause: User attempted to truncate a fixed table which is illegal.
// *Action: Ensure that the table being truncated is not a fixed table.
14073, 00000, "bootstrap table or cluster may not be truncated"
// *Cause: User attempted to truncate a bootstrap table or cluster which
// is illegal
// *Action: Ensure that the table (or cluster) being truncated is not a
// bootstrap table (or cluster)
14074, 00000, "partition bound must collate higher than that of the last partition"
// *Cause: Partition bound specified in ALTER TABLE ADD PARTITION
// statement did not collate higher than that of the table's
// last partition, which is illegal.
// *Action: Ensure that the partition bound of the partition to be added
// collates higher than that of the table's last partition.
14075, 00000, "partition maintenance operations may only be performed on partitioned indices"
// *Cause: Index named in ALTER INDEX partition maintenance operation
// is not partitioned, making a partition maintenance operation,
// at best, meaningless
// *Action: Ensure that the index named in ALTER INDEX statement
// specifying a partition maintenance operation is, indeed,
// partitioned
14076, 00000, "submitted alter index partition/subpartition operation is not valid for local partitioned index"
// *Cause: User attempted to either drop, split, add or coalesce a partition or
// a subpartition of a local index which is illegal.
// *Action: Ensure that the index named in such statement is a global
// partitioned index.
14078, 00000, "you may not drop the highest partition of a GLOBAL index"
// *Cause: User attempted to drop highest partition of a GLOBAL index,
// which is illegal.
// *Action: Ensure that the partition specified in ALTER INDEX DROP PARTITION
// statement is not the highest partition of the index.
14079, 00000, "illegal option for a partition marked Index Unusable"
// *Cause: ALTER INDEX MODIFY PARTITION statement against an index
// partition marked Index Unusable contained STORAGE and/or
// DEALLOCATE SPACE clauses which is illegal
// *Action: Ensure that only valid optins are specified
14080, 00000, "partition cannot be split along the specified high bound"
// *Cause: User attempted to split a partition along a bound which
// either collates higher than that of the partition to be split or
// lower than that of a partition immediately preceding the one
// to be split
// *Action: Ensure that the bound along which a partition is to be split
// collates lower than that of the partition to be split and
// higher that that of a partition immediately preceding the one
// to be split
14081, 00000, "new partition name must differ from the old partition name"
// *Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying
// <new-partition-name> which is identical to the name of the
// partition being renamed
// *Action: Ensure that the new partition name is different from the
// name of any (including the one being renamed) existing
// partition of a given table or index
14082, 00000, "New partition name must differ from that of any other partition or subpartition of the object."
// *Cause: ALTER TABLE RENAME PARTITION or ALTER INDEX RENAME PARTITION
// specifying a <new-partition-name> which is identical to the name
// of an existing partition or subpartition of the object was
// specified.
// *Action: Ensure that the new partition name is different from the
// name of any (including the one being renamed) existing
// partition or subpartition of a given table or index.
14083, 00000, "cannot drop the only partition of a partitioned table"
// *Cause: A drop partition command is being executed when there
// is only one partition in the table
// *Action: Ensure that there is at least one partition.
// Drop table to remove all partitions
14084, 00000, "you may specify TABLESPACE DEFAULT only for a LOCAL index"
// *Cause: User attempted to specify TABLESPACE DEFAULT for an
// object other than a LOCAL index, which is illegal.
// *Action: Reenter the statement without TABLESPACE DEFAULT clause.
14085, 00000, "partitioned table cannot have column with LONG datatype"
// *Cause: User tried to create a partitioned table with a LONG datatype
// or tried to add a LONG datatype column to a partitioned table.
// *Action: LONG data types are not supported with partitioned tables.
// Create table without LONG column or change table to not
// partitioned. If adding column, do not use LONG datatype.
// If modifying attributes of a column to change data type to
// LONG, it has to be a non partitioned table.
14086, 00000, "a partitioned index may not be rebuilt as a whole"
// *Cause: User attempted to rebuild a partitioned index using
// ALTER INDEX REBUILD statement, which is illegal
// *Action: Rebuild the index a partition at a time (using
// ALTER INDEX REBUILD PARTITION) or drop and recreate the
// entire index
14087, 00000, "use of <table-name> PARTITION (<partition-number>|<bind variable>) syntax"
// *Document: NO
// *Cause:
// *Action:
// Level 1+ Allow use of aforementioned syntax
14088, 00000, "second argument to tbl$or$idx$part$num must be an integer constant"
// *Document: NO
// *Cause: Second argument to tbl$or$idx$part$num (must be index
// object ID or 0) was found not to be an integer constant
// *Action: Ensure that the second argument passed to tbl$or$idx$part$num
// is an integer constant representing object ID of an index if it
// is desired that that indes' partition mapping descriptor
// be used or 0 otherwise
14089, 00000, "base table does not have an index with a specified ID defined on it"
// *Document: NO
// *Cause: Second argument to tbl$or$idx$part$num was non-zero, implying
// that the partition mapping descriptor of an index defined on
// the table whose name was supplied as the first srgument
// is to be used, but that table does not have an index with
// the specified object ID defined on it.
// *Action: Ensure that the object ID suplied as the second argument
// is that of an index defined on the table whose name was
// supplied as the first argument.
14090, 00000, "index must be partitioned"
// *Document: NO
// *Cause: Index whose ID was supplied by the user as the second
// argument to tbl$or$idx$part$num was not partitioned
// *Action: Second argument passed to tbl$or$idx$part$num must be an
// object ID of a partitioned index defined on the table whose
// name was supplied as the first argument if one desires to determine
// mapping into an index partition or 0 if one desires to
// determine mapping into a partition of the base table itself
14091, 00000, "table must be partitioned"
// *Document: NO
// *Cause: Table whose name was supplied by the user as the first
// argument to tbl$or$idx$part$num was not partitioned
// *Action: If one desires to determine mapping of rows into a
// partition of a base table, one must supply a name of
// a partitioned table as the first argument and 0 as the
// second argument. If, on the other hand, one desires to
// determine mapping of rows into a partition of an index
// defined on that table, one must supply that index' object
// ID as the second argument
14092, 00000, "number of expressions is not equal to the number of partitioning columns"
// *Document: NO
// *Cause: Number of expressions submitted to tbl$or$idx$part$num differs
// from the number of partitioning columns of the table or index
// mapping into partition(s) of which is to be determined
// *Action: Supply a correct number of expressions to be used in
// determining mapping into partition(s) of a specified
// table or index
14093, 00000, "data type of expression incompatible with that of partitioning column"
// *Document: NO
// *Cause: Data type of an expression was neiher equal to nor
// coercible into that of a corresponding partitioning column
// of a table or index mapping into partition(s) of which is
// of interest
// *Action: Ensure that data types of expressions supplied to
// tbl$or$idx$part$num are compatible with those of
// corresponding partitioning columns of a table or index
// mapping into partition(s) of which is of interest
14094, 00000, "invalid ALTER TABLE EXCHANGE PARTITION option"
// *Cause: Name of the table to be EXCHANGED has to be followed
// by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION]
// *Action: Ensure that no options besides INCLDING INDEX or EXCLUDING
// INDEX are specified with ALTER TABLE EXCHANGE PARTITION
14095, 00000, "ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table"
// *Cause: The table in the EXCHANGE operation is either clustered or
// partitioned
// *Action: Ensure that the table with which the partition is being exchanged
// for is not partitioned or clustered.
14096, 00000, "tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns"
// *Cause: The two tables specified in the EXCHANGE have different number
// of columns
// *Action: Ensure that the two tables have the same number of columns
// with the same type and size.
14097, 00000, "column type or size mismatch in ALTER TABLE EXCHANGE PARTITION"
// *Cause: The corresponding columns in the tables specified in the
// ALTER TABLE EXCHANGE PARTITION are of different type or size
// *Action: Ensure that the two tables have the same number of columns
// with the same type and size.
14098, 00000, "index mismatch for tables in ALTER TABLE EXCHANGE PARTITION"
// *Cause: The two tables specified in the EXCHANGE have indexes which are
// not equivalent
// *Action: Ensure that the indexes for the two tables have indexes which
// follow this rule
// For every non partitioned index for the non partitioned table,
// there has to be an identical LOCAL index on the partitioned
// table and vice versa. By identical, the column position, type
// and size have to be the same.
14099, 00000, "all rows in table do not qualify for specified partition"
// *Cause: There is at least one row in the non partitioned table which
// does not qualify for the partition specified in the ALTER TABLE
// EXCHANGE PARTITION
// *Action: Ensure that all the rows in the segment qualify for the partition.
// Perform the alter table operation with the NO CHECKING option.
// Run ANALYZE table VALIDATE on that partition to find out the
// invalid rows and delete them.
14100, 00000, "partition extended table name cannot refer to a remote object"
// *Cause: User attempted to use partition-extended table name syntax
// in conjunction with remote object name which is illegal
// *Action: Correct the statement and reenter
14101, 00000, "partition extended table name cannot refer to a synonym"
// *Cause: User attempted to use partition-extended table name syntax
// in conjunction with synonym name which is illegal
// *Action: Correct the statement and reenter
14102, 00000, "only one LOGGING or NOLOGGING clause may be specified"
// *Cause: LOGGING was specified more than once, NOLOGGING was specified
// more than once, or both LOGGING and NOLOGGING were specified.
// *Action: Remove all but one of the LOGGING or NOLOGGING clauses and
// reissue the statement.
14103, 00000, "LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE"
// *Cause: A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses
// which is disallowed.
// *Action: Remove one of the offending clauses.
// [UN]RECOVERABLE is being deprecated in V8 and will be
// obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause,
// create an object with NOLOGGING option and then ALTER it specifying
// LOGGING. To duplicate semantics of RECOVERABLE clause,
// create an object with LOGGING option.
14104, 00000, "RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices"
// *Cause: CREATE TABLE/INDEX statement used to create a partitioned
// table/index contained RECOVERABLE or UNRECOVERABLE clause
// which is illegal
// *Action: Remove offending clause.
// [UN]RECOVERABLE is being deprecated in V8 and will be
// obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause,
// create an object with NOLOGGING option and then ALTER it specifying
// LOGGING. To duplicate semantics of RECOVERABLE clause,
// create an object with LOGGING option.
14105, 00000, "RECOVERABLE/UNRECOVERABLE may not be specified in this context"
// *Cause: RECOVERABLE/UNRECOVERABLE clause is not allowed in this context.
// *Action: Remove offending clause. RECOVERABLE/UNRECOVERABLE may
// only be specified in CREATE TABLE/INDEX statement describing a
// non-partitioned table or index and ALTER INDEX REBUILD statement.
// [UN]RECOVERABLE is being deprecated in V8 and will be
// obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause,
// create an object with NOLOGGING option and then ALTER it specifying
// LOGGING. To duplicate semantics of RECOVERABLE clause,
// create an object with LOGGING option.
14106, 00000, "LOGGING/NOLOGGING may not be specified for a clustered table"
// *Cause: User attempted to specify LOGGING or NOLOGGING clausein
// CREATE TABLE or ALTER TABLE statement involving a
// clustered table
// *Action: Remove offending clause.
14107, 00000, "partition specification is required for a partitioned object"
// *Cause: parameter which supplies partition name is missing. This
// parameter is optional for non-partitioned objects, but is required
// for partitioned objects.
// *Action: supply missing parameter
14108, 00000, "illegal partition-extended table name syntax"
// *Cause: Partition to be accessed may only be specified using its name.
// User attempted to use a partition number or a bind variable.
// *Action: Modify statement to refer to a partition using its name
14109, 00000, "partition-extended object names may only be used with tables and editioning views"
// *Cause: An attempt was made to use a partition-extended object name
// with an object which was not a table or an editioning view.
// *Action: Avoid using partition-extended name syntax with objects
// which are not tables or editioning views
14110, 00000, "partitioning column may not be of type ROWID"
// *Cause: Partitioning column specified by the user was of type ROWID,
// which is illegal.
// *Action: Ensure that no partitioning column is of type ROWID.
14111, 00000, "creation of a GLOBAL partitioned index on clustered tables is not supported"
// *Cause: An attempt was made to create a GLOBAL partitioned index on a
// clustered table which is currently illegal.
// *Action: Remove PARTITION BY RANGE/HASH clause along with any partition
// descriptions to create a GLOBAL non-partitioned index on a
// clustered table
14112, 00000, "RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition"
// *Cause: Description of a partition or subpartition found in
// CREATE TABLE/INDEX statement contained RECOVERABLE or
// UNRECOVERABLE clause which is illegal
// *Action: Remove offending clause. Use LOGGING or NOLOGGING instead.
14113, 00000, "partitioned table cannot have column with LOB datatype"
// *Cause: User tried to create a partitioned table with a LOB datatype
// or tried to add a LOB datatype column to a partitioned table.
// *Action: LOB data types are not supported with partitioned tables.
// Create table without LOB column or change table to not
// partitioned. If adding column, do not use LOB datatype.
// If modifying attributes of a column to change data type to
// LOB, it has to be a non partitioned table.
14114, 00000, "partitioned table cannot have column with object, REF, nested table, array datatype"
// *Cause: User tried to create a partitioned table with a object datatype
// (object, REF, nested table, array)
// or tried to add a object datatype column to a partitioned table.
// *Action: object data types are not supported with partitioned tables.
// Create table without object column or change table to not
// partitioned. If adding column, do not use object datatypes.
// If modifying attributes of a column to change data type to
// object, it has to be a non partitioned table.
14115, 00000, "partition bound of partition number %s is too long"
// *Cause: Length of linear key representation of a high bound of the
// partition whose number (partitions are numbered starting with 1)
// is displayed in this message exceeded the legal limit (4K).
// *Action: Change representation of a partition high bound to bring
// its length within legal limit.
14116, 00000, "partition bound of partition \"%s\" is too long"
// *Cause: Length of linear key representation of a high bound of the
// partition whose name (explicitly specified by the user) is
// displayed in this message exceeded the legal limit (4K).
// *Action: Change representation of a partition high bound to bring
// its length within legal limit.
14117, 00000, "partition resides in offlined tablespace"
// *Cause: User attempted an operation requiring that we access data
// in a partition which resides in a tablespace which was
// taken offline. Such operations include trying to drop a
// tablespace of a table which has indices defined on it or
// is referenced by a constraint.
// *Action: Bring tablespace online before attempting the operation.
14118, 00000, "CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION"
// *Cause: The corresponding columns in the tables specified in the
// ALTER TABLE EXCHANGE PARTITION statement have CHECK constraint
// defined on them.
// *Action: Ensure that the two tables do not have CHECK constraint
// defined on any column
14119, 00000, "specified partition bound is too long"
// *Cause: Length of a linear key representation of a high bound of a table
// partition being added or along which an existing table or
// index partition is being split exceeded the legal limit (4K).
// *Action: Change representation of a partition high bound to bring
// its length within legal limit.
14120, 00000, "incompletely specified partition bound for a DATE column"
// *Cause: An attempt was made to use a date expression whose format
// does not fully (i.e. day, month, and year (including century))
// specify a date as a partition bound for a DATE column.
// The format may have been specified explicitly (using
// TO_DATE() function) or implicitly (NLS_DATE_FORMAT).
// *Action: Ensure that date format used in a partition bound for a
// DATE column supports complete specification of a date
// (i.e. day, month, and year (including century)).
// If NLS_DATE_FORMAT does not support complete
// (i.e. including the century) specification of the year,
// use TO_DATE() (e.g. TO_DATE('01-01-1999', 'MM-DD-YYYY')
// to fully express the desired date.
14121, 00000, "MODIFY DEFAULT ATTRIBUTES may not be combined with other operations"
// *Cause: ALTER TABLE or ALTER INDEX statement attempted to combine
// MODIFY DEFAULT ATTRIBUTES with some other operation
// (e.g. ADD PARTITION or PCTFREE) which is illegal
// *Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole
// operation specified in ALTER TABLE or ALTER INDEX statement;
// operations other than those dealing with partitions,
// default attributes of partitioned tables/indices or
// specifying that a table be renamed (ALTER TABLE RENAME) may be
// combined at will
14122, 00000, "only one REVERSE or NOREVERSE clause may be specified"
// *Cause: Both REVERSE and NOREVERSE were specified in CREATE INDEX
// statement.
// *Action: Remove all but one of the REVERSE or NOREVERSE clauses and
// reissue the statement.
14123, 00000, "duplicate NOREVERSE clause"
// *Cause: NOREVERSE was specified more than once in ALTER INDEX statement.
// *Action: Remove all but one of the NOREVERSE clauses and reissue
// the statement.
14124, 00000, "duplicate REVERSE clause"
// *Cause: REVERSE was specified more than once in ALTER INDEX or
// CREATE INDEX statements.
// *Action: Remove all but one of the REVERSE clauses and reissue
// the statement.
14125, 00000, "REVERSE/NOREVERSE may not be specified in this context"
// *Cause: REVERSE/NOREVERSE clause is not allowed in this context.
// *Action: Remove offending clause. REVERSE may be specified as an
// attribute of an index (not of an individual partition, if
// creating a partitioned index) in CREATE INDEX statement
// and ALTER INDEX REBUILD statement.
// NOREVERSE may be specified only in ALTER INDEX REBUILD statement.
14126, 00000, "only a <parallel clause> may follow description(s) of resulting partitions"
// *Cause: Descriptions of partition(s) resulting from splitting of a
// table or index partition may be followed by an optional
// <parallel clause> which applies to the entire statement and
// which, in turn, may not be followed by any other clause.
// *Action: Ensure that all partition attributes appear within the
// parenthesized list of descriptions of resulting partitions in
// ALTER TABLE/INDEX SPLIT PARTITION statement.
14127, 00000, "illegal index-partition-extended table name syntax"
// *Document: NO
// *Cause: Index partition may be specified using IND_PARTITION(<bind var>)
// or IND_PARTITION(<part#>).
// Internal user attempted to specify an index partition name.
// *Action: Modify statement to refer to an index partition using its number
14128, 00000, "FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION"
// *Cause: The corresponding columns in the tables specified in the
// ALTER TABLE EXCHANGE PARTITION statement have different FOREIGN KEY
// constraints.
// *Action: Ensure that the two tables do not have FOREIGN KEY constraints
// defined on any column or disable all FOREIGN KEY constraints
// on both tables. Then retry the operation.
14129, 00000, "INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints"
// *Cause: Matching UNIQUE constraints in both table are enabled and validated
// but INCLUDING INDEXES is not specified in ALTER TABLE EXCHANGE
// PARTITION|SUBPARTITION command.
// *Action: Disable currently enabled matching UNIQUE constraints on both
// tables or ensure that INCLUDING INDEXES option is used.
14130, 00000, "UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION"
// *Cause: One of the tables named in the ALTER TABLE EXCHANGE PARTITION
// command has a UNIQUE constraint for which no matching (vis-a-vis
// key columns) constraint is defined on the other table or
// a matching constraint is defined on the other table, but it
// differs from that defined on the first table vis-a-vis being
// enabled and/or validated.
// *Action: Ensure that for every UNIQUE constraint defined on one of the
// tables named in the ALTER TABLE EXCHANGE PARTITION statement there
// is a matching (vis-a-vis key columns and being enabled and/or
// validated) UNIQUE constraint defined on the other table.
// If UNIQUE constrains are enabled, UNIQUE constraints on the
// partitioned table should be enforced using local indexes.
14131, 00000, "enabled UNIQUE constraint exists on one of the tables"
// *Cause: One of the tables referenced in the ALTER TABLE EXCHANGE
// PARTITION|SUBPARTITION statement has enabled UNIQUE constraint(s)
// defined on it, which prevents EXCHANGE from proceeding.
// *Action: Disable constraints defined on tables referenced in the
// ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement and
// retry the statement.
14132, 00000, "table cannot be used in EXCHANGE"
// *Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION |
// SUBPARTITION statement, but the non-partitioned table cannot be
// used in the EXCHANGE because one or more of the following apply:
// - it is a typed table
// - it is a temporary table
// - it contains ADT columns
// - it contains nested-table columns
// - it contains REF columns
// - it contains array columns
// - it is an index-organized table
// - it contains LOB columns
// - it is a nested table
// - it is created with row dependency and the partitioned table is not
// - it is created without row dependency and the partitioned table is
// *Action: Ensure that the non-partitioned table does not violate any
// of the above restrictions for the ALTER TABLE EXCHANGE PARTITION |
// SUBPARTITION statement.
14133, 00000, "ALTER TABLE MOVE cannot be combined with other operations"
// *Cause: An attempt was made to combine an ALTER TABLE MOVE statement
// with another operation, such as MODIFY.
// *Action: Ensure that MOVE is the only operation specified in ALTER TABLE
// statement.
14134, 00000, "indexes cannot use both DESC and REVERSE"
// *Cause: An attempt was made to make a reverse index with some index
// columns marked DESC.
// *Action: Do not use DESC in reverse indexes. The rule-based optimizer can
// scan indexes backwards, which allows a normal reverse index to
// simulate a reverse index with columns marked DESC.
14135, 00000, "a LOB column cannot serve as a partitioning column"
// *Cause: An attempt was made to specify a column of type BLOB or CLOB as a
// partitioning or subpartitioning column.
// *Action: Ensure that no partitioning or subpartitioning column is of type
// BLOB or CLOB.
14136, 00000, "ALTER TABLE EXCHANGE restricted by fine-grained security"
// *Cause: User doing exchange does not have full table access due to VPD
// policies.
// *Action: Grant exempt priviliges to this user.
14137, 00000, "Table in partially dropped state, submit DROP TABLE PURGE"
// *Cause: An attempt was made to access a partitioned table in a partially
// dropped state.
// *Action: Submit DROP TABLE <table> PURGE to drop the table.
14138, 00000, "An unexpected error encountered during drop table operation"
// *Cause: Drop table encountered an unexpected error.
// *Action: a. Submit drop table <table> purge, or
// b. If the situation described in the next error on the stack
// can be corrected, do so.
// c. Contact Oracle Support.
14139, 00000, "table %s.%s is already in read-only mode"
// *Cause: an attempt was made to set a read-only table in read-only mode
// *Action: this DDL can only be executed on a read/write table
14140, 00000, "table %s.%s is already in read/write mode"
// *Cause: an attempt was made to set a read/write table in read/write mode
// *Action: this DDL can only be executed on a read-only table
14141, 00000, "ALTER INDEX VISIBLE|INVISIBLE may not be combined with other operations"
// *Cause: ALTER INDEX statement attempted to combine a VISIBLE|INVISIBLE
// operation with some other operation which is illegal
// *Action: Ensure that VISIBLE|INVISIBLE operation is the sole operation
// specified in ALTER INDEX statement
14142, 00000, "ALTER INDEX VISIBLE|INVISIBLE may not be used with certain types of index"
// *Cause: Using the ALTER INDEX VISIBLE|INVISIBLE statement on certain types
// of indexes (IOT-TOP, Cluster indexes) is illegal.
// *Action: Remove the option VISIBLE|INVISIBLE.
14143, 00000, "CREATE INDEX INVISIBLE may not be used with this type of index"
// *Cause: Certain types of indexes (IOT-TOP, Cluster indexes) cannot
// be created invisible.
// *Action: Remove the option INVISIBLE
14144, 00000, "arguments to tbl$or$idx$part$num must not be bind variables"
// *Document: NO
// *Cause: Second, third or fourth argument to tbl$or$idx$part$num was found
// to be a bind variable and not an integer constant.
// *Action: Ensure that the argument passed to tbl$or$idx$part$num
// is an integer constant and not a bind variable.
14145, 00000, "only one UNUSABLE clause may be specified"
// *Cause: UNUSABLE was specified more than once.
// *Action: Remove all but one of the UNUSABLE clauses and reissue the statement.
14146, 00000, "Old CONNECT BY does not support partitioned tables"
// *Cause: The query used the old CONNECT BY clause on a partitioned object.
// *Action: Disable old CONNECT BY by disabling the _old_connect_by_enabled parameter.
14147, 00000, "There is an existing VISIBLE index defined on the same set of columns."
// *Cause: An attempt was made to define more than one VISIBLE index on the
// same set of columns. There can be only one VISIBLE index on the
// same set of columns. Hence ALTER INDEX VISIBLE was not supported
// on this index.
// *Action: Make all the indexes defined on the same set of columns as
// INVISIBLE and then reexecute this DDL.
14148, 00000, "DML and DDL operations are not directly allowed on the guard-column."
// *Cause: An attempt was made to execute a DML or a DDL directly on the
// guard-column.
// *Action: This is not supported.
/
/ 14150-14249 reserved for parsing errors which may be generated
/ during parsing of statements added/modified by 8.1
/ partitioning project
14150, 00000, "missing SUBPARTITION keyword"
// *Cause: keyword SUBPARTITION missing
// *Action: supply missing keyword
14151, 00000, "invalid table partitioning method"
// *Cause: Invalid partitioning method was specified in CREATE TABLE
// statement. A table may be partitioned by RANGE, HASH, LIST, SYSTEM, or
// Composite Range-Hash/List/Range (R+H/L/R).
// *Action: Specify one of valid partitioning methods
14152, 00000, "invalid number of partitions specified in PARTITIONS clause"
// *Cause: number-of-partitions clause contained in CREATE TABLE or
// CREATE INDEX statement specified a number of partitions
// outside of legal range (1-1048575)
// *Action: Specify a number between 1 and 1024K-1 in the
// number-of-partitions clause
14153, 00000, "only one of STORE IN or <partition-description> clause may be specified"
// *Cause: both STORE IN and <partition-description> clauses were specified
// in a CREATE TABLE|INDEX command
// *Action: Remove one of offending clauses
14154, 00000, "only one of STORE IN or <subpartition-description> clause may be specified"
// *Cause: both STORE IN and <subpartition-description> clauses were
// specified in a CREATE TABLE|INDEX, or ALTER TABLE ADD|SPLIT
// PARTITION or ALTER TABLE MERGE PARTITIONS command for
// a Composite Range partitioned object
// *Action: Remove one of offending clauses
14155, 00000, "missing PARTITION, PARTITIONS, SUBPARTITION, or SUBPARTITIONS keyword"
// *Cause: The keyword PARTITION,PARTITIONS, SUBPARTITION, or SUBPARTITIONS was
// expected but none were supplied.
// *Action: Supply the missing keyword.
14156, 00000, "invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause"
// *Cause: number-of-subpartitions clause contained in CREATE TABLE or
// CREATE INDEX statement specified a number of subpartitions
// outside of legal range (1-1048575)
// *Action: Specify a number between 1 and 1024K-1 in the
// number-of-subpartitions clause
14157, 00000, "invalid subpartition name"
// *Cause: a subpartition name of the form <identifier> is expected
// but not present.
// *Action: enter an appropriate subpartition name.
14158, 00000, "too many subpartition descriptions"
// *Cause: CREATE TABLE or CREATE INDEX contained too many subpartition
// descriptions; maximum number of subpartitions is 1048575.
// *Action: Reduce number of subpartitions to not exceed 1024K-1.
14159, 00000, "duplicate subpartition name"
// *Cause: Name of a subpartition of a table or index being created
// is not unique
// *Action: rename subpartition(s) to ensure that their names are unique
// among subpartitions of the table or index being created
14160, 00000, "this physical attribute may not be specified for a table subpartition"
// *Cause: unexpected option was encountered while parsing physical
// attributes of a table subpartition; TABLESPACE is the only valid
// option
// *Action: remove invalid option(s)
// *Comment: this error could have resulted from omission of a
// terminating (right) parenthesis following the list of
// subpartition descriptions
14161, 00000, "subpartition number %s: sum of PCTUSED and PCTFREE may not exceed 100"
// *Cause: the sum of PCTUSED and PCTFREE for a subpartition whose number
// (subpartitions are numbered starting with 1) is displayed in this
// message exceeds 100. Note that if PCTUSED and/or PCTFREE
// values for this subpartition were not specified explicitly,
// default values at partition-level would be used. If, in turn,
// default PCTUSED and/or PCTFREE values at partition-level were not
// specified, default values for the partitioned table or index
// would be used. If those values were also not specified explicitly,
// system defaults would be used.
// *Action: ensure that a sum of PCTUSED and PCTFREE for the subpartition
// does not exceed 100
14162, 00000, "subpartition \"%s\": sum of PCTUSED and PCTFREE may not exceed 100"
// *Cause: the sum of PCTUSED and PCTFREE for a subpartition whose name
// (explicitly specified by the user) is displayed in this
// message exceeds 100. Note that if PCTUSED and/or PCTFREE
// values for this subpartition were not specified explicitly,
// default values at partition-level would be used. If, in turn,
// default PCTUSED and/or PCTFREE values at partition-level were not
// specified, default values for the partitioned table or index
// would be used. If those values were also not specified explicitly,
// system defaults would be used.
// *Action: ensure that a sum of PCTUSED and PCTFREE for the subpartition
// does not exceed 100
14163, 00000, "subpartition number %s: INITRANS value must be less than MAXTRANS value"
// *Cause: Value of INITRANS was found to be greater than that of MAXTRANS
// for a subpartition whose number (subpartitions are numbered starting
// with 1) is displayed in this message. Note that if INITRANS
// and/or MAXTRANS values for this subpartition were not specified
// explicitly, default values at partition-level would be used.
// If, in turn, default INITRANS and/or MAXTRANS values at
// partition-level were not specified, default values for the
// partitioned table or index would be used. If those values were
// also not specified explicitly, system defaults would be used.
// *Action: ensure that value of INITRANS (whether specified explicitly or
// derived from the default value at partition-level, table-level or
// index-level) is no greater than that of MAXTRANS
14164, 00000, "subpartition \"%s\": INITRANS value must be less than MAXTRANS value"
// *Cause: Value of INITRANS was found to be greater than that of MAXTRANS
// for a subpartition whose name (explicitly specified by the user)
// is displayed in this message. Note that if INITRANS
// and/or MAXTRANS values for this subpartition were not specified
// explicitly, default values at partition-level would be used.
// If, in turn, default INITRANS and/or MAXTRANS values at
// partition-level were not specified, default values for the
// partitioned table or index would be used. If those values were
// also not specified explicitly, system defaults would be used.
// *Action: ensure that value of INITRANS (whether specified explicitly or
// derived from the default value at partition-level, table-level or
// index-level) is no greater than that of MAXTRANS
14165, 00000, "MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations"
// *Cause: ALTER TABLE or ALTER INDEX statement attempted to combine
// MODIFY DEFAULT ATTRIBUTES OF PARTITION with some other operation
// (e.g. ADD PARTITION or PCTFREE) which is illegal
// *Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole
// operation specified in ALTER TABLE or ALTER INDEX statement;
// operations other than those dealing with partitions,
// default attributes of partitioned tables/indices or
// specifying that a table be renamed (ALTER TABLE RENAME) may be
// combined at will
14166, 00000, "missing INTO keyword"
// *Cause: keyword INTO missing
// *Action: supply missing keyword
14167, 00000, "only one subpartition may be moved"
// *Cause: ALTER TABLE MOVE SUBPARTITION contained descriptions of more than
// one subpartition to be moved
// *Action: Ensure that the statement describes exactly one subpartition
// to be moved and that it does not contain any commas
14168, 00000, "only one subpartition may be modified"
// *Cause: ALTER TABLE|INDEX MODIFY SUBPARTITION contained descriptions of
// more than one subpartition to be modified
// *Action: Ensure that the statement describes exactly one subpartition
// to be modified and that it does not contain any commas
14169, 00000, "invalid ALTER TABLE MODIFY SUBPARTITION option"
// *Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS,
// STORAGE, was specified in an ALTER TABLE MODIFY SUBPARTITION
// statement.
// *Action: Specify only legal options.
14170, 00000, "cannot specify <(sub)partition-description> clause in CREATE TABLE or CREATE INDEX"
// *Cause: A request was made to generate default partition description(s)
// (possibly via PARTITIONS <number-of-partitions>) while at
// the same time specified <(sub)partition-description> clause which
// is illegal.
// *Action: Remove one of offending clauses.
14171, 00000, "cannot specify <subpartition-description> clause in CREATE|ALTER TABLE"
// *Cause: User requested to generate default subpartition description(s)
// (possibly via SUBPARTITIONS) while at the same time specified
// <subpartition-description> clause which is illegal
// *Action: Remove one of offending clauses.
14172, 00000, "invalid ALTER TABLE EXCHANGE SUBPARTITION option"
// *Cause: Name of the table to be EXCHANGED has to be followed
// by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION]
// *Action: Ensure that no options besides INCLDING INDEX or EXCLUDING
// INDEX are specified with ALTER TABLE EXCHANGE SUBPARTITION
14173, 00000, "illegal subpartition-extended table name syntax"
// *Cause: Subpartition to be accessed may only be specified using its name.
// User attempted to use a subpartition number or a bind variable.
// *Action: Modify statement to refer to a subpartition using its name
14174, 00000, "only a <parallel clause> may follow COALESCE PARTITION|SUBPARTITION"
// *Cause: ALTER TABLE COALESCE PARTITION|SUBPARTITION may be followed by
// an optional <parallel clause>. No partition/subpartition
// attributes may be specified
// *Action: Ensure that no partition/subpartition attribute was specified.
14175, 00000, "a subpartition maintenance operation may not be combined with other operations"
// *Cause: ALTER TABLE or ALTER INDEX statement attempted to combine
// a subpartition maintenance operation (e.g. MOVE SUBPARTITION)
// with some other operation (e.g. MODIFY PARTITION ADD SUBPARTITION
// or PCTFREE) which is illegal
// *Action: Ensure that a subpartition maintenance operation is the sole
// operation specified in ALTER TABLE or ALTER INDEX statement;
// operations other than those dealing with subpartitions,
// default attributes of partitioned tables/indices or
// specifying that a table be renamed (ALTER TABLE RENAME) may be
// combined at will
14176, 00000, "this attribute may not be specified for a hash partition"
// *Cause: An invalid option was encountered while parsing physical
// attributes of a partition of an object partitioned using the
// HASH method. The TABLESPACE option is the only valid
// option for such partitions.
// *Action: Remove the invalid option(s).
14177, 00000, "STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table"
// *Cause: STORE-IN (Tablespace list) clause was used while creating a local
// index on a range/list/composite range list partitioned table
// *Action: Do not use the STORE_IN (Tablespace list) clause while creating
// a local index on range/list/composite range list partitioned table
14178, 00000, "STORE IN (DEFAULT) clause is not supported for hash partitioned global indexes"
// *Cause: STORE IN (DEFAULT) is valid only for local indexes.
// *Action: a) Specify a tablespace list in place of DEFAULT, or b) Remove
// STORE IN clause and specify tablespaces individually for each
// index partition.
14179, 00000, "An unsupported partitioning method was specified in this context."
// *Cause: An attempt was made to specify an unsupported partitioning method in this context.
// *Action: Remove the invalid option.
14183, 00000, "TABLESPACE DEFAULT can be specified only for Composite LOCAL index"
// *Cause: User attempted to specify TABLESPACE DEFAULT for a partition of a Range/System/Hash
// partitioned LOCAL index object, which is illegal.
// *Action: Replace TABLESPACE DEFAULT with TABLESPACE <ts_name> or remove it.
14184, 00000, "cannot create an UNIQUE partitioned index on a SYSTEM partitioned table"
// *Document: NO
// *Cause: User attempted to create a UNIQUE partitioned index on a SYSTEM
// partitioned table
// *Action: Remove UNIQUE keyword
14185, 00000, "incorrect physical attribute specified for this index partition"
// *Cause: An unexpected option was encountered while parsing physical attributes
// of a local index partition; valid options for Range or Composite Range
// partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, PCTUSED,
// LOGGING and TABLESPACE; but only TABLESPACE may be specified for Hash partitions
// STORE IN () is also disallowed for all but Hash, Interval, Autolist, Composite
// Range Hash, Composite Interval, Composite Autolist partition.
// *Action: Remove the invalid options from the list of physical attributes
// of an index partition.
14186, 0000, "number of sub-partitions of LOCAL index must equal that of the underlying table"
// *Cause: User attempted to create a LOCAL partitioned index with a
// number of sub-partitions which is different from that of the
// underlying table.
//* Action: Correct the CREATE INDEX statement to specify a correct
// number of sub-partitions
14187, 0000, "partitioning method for LOCAL index is inconsistent with that of the underlying table"
// *Cause: User attempted to create a LOCAL partitioned index that is not equi-partitioned with
// the underlying table. The partitioning types are mismatched.
// *Action: Correct the CREATE INDEX statement to ensure that the index partitionining
// method is consistent with that of the base table
14188, 0000, "sub-partitioning columns must form a subset of key columns of a UNIQUE index"
// *Cause: User attempted to create a UNIQUE partitioned index whose
// sub-partitioning columns do not form a subset of its key columns
// which is illegal
// *Action: If the user, indeed, desired to create an index whose
// subpartitioning columns do not form a subset of its key columns,
// it must be created as non-UNIQUE; otherwise, correct the
// list of key and/or subpartitioning columns to ensure that the index'
// subpartitioning columns form a subset of its key columns
14189, 00000, "this physical attribute may not be specified for an index subpartition"
// *Cause: unexpected option was encountered while parsing physical
// attributes of an index subpartition; TABLESPACE is the only valid
// option
// *Action: remove invalid option(s)
14190, 00000, "only one ENABLE/DISABLE ROW MOVEMENT clause can be specified"
// *Cause: One of three possible actions caused the error:
// 1) ENABLE ROW MOVEMENT was specified more than once.
// 2) DISABLE ROW MOVEMENT was specified more than once.
// 3) Both ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT were
// specified.
// *Action: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW
// MOVEMENT clauses; then, reissue the command.
14191, 00000, "ALLOCATE EXTENT may not be specified for composite partitioned object"
// *Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement
// issued against a composite partitioned index which is illegal.
// *Action: Remove the illegal option. If you want to add
// storage to individual [sub]partitions,the ALLOCATE EXTENT clause
// may be specified with ALTER TABLE OR INDEX MODIFY [SUB]PARTITION statement.
//
14192, 00000, "cannot modify physical index attributes of a Hash index partition"
// *Cause: User attempted to modify one of INITRANS/MAXTRANS/LOGGING/STORAGE
// clause for an index partition of a Hash partitioned index
// *Action: Remove the physical attributes one is trying to modify
//
14193, 0000, "invalid ALTER INDEX MODIFY SUBPARTITION option"
// *Cause: An option other than UNUSABLE, ALLOCATE EXTENT, DEALLOCATE UNUSED
// was specified in an ALTER INDEX MODIFY SUBPARTITION statement.
// *Action: Specify only legal options.
14194, 00000, "only one subpartition may be rebuilt"
// *Cause: ALTER INDEX REBUILD SUBPARTITION contained descriptions of more than
// one subpartition to be rebuilt
// *Action: Ensure that the statement describes exactly one subpartition
// to be rebuilt and that it does not contain any commas
14195, 00000, "ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object"
// *Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement
// issued against a range-partitioned index which is illegal.
// *Action: Remove the illegal option. If it is desired to add
// storage to individual partitions, ALLOCATE STORAGE clause
// may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement.
14196, 00000, "Specified index cannot be used to enforce the constraint."
// *Cause: The index specified to enforce the constraint is unsuitable
// for the purpose.
// *Action: Specify a suitable index or allow one to be built automatically.
14197, 00000, "dimension values 3,4 cannot be used with domain indexes"
// *Document: NO
// *Cause: A dimension value of 3 or 4 was used in conjunction with a
// domain index
// *Action: Do not use dimension value 3,4 for domain indexes in
// tbl$or$idx$part$num function
14198, 00000, "rowid column must refer to table specified in 1st parameter"
// *Document: NO
// *Cause: The table name specified in the first parameter and the table that
// the ROWID column belongs to were not the same.
// *Action: Ensure that the table name in the first parameter is the same as
// the table to which the ROWID column belongs.
14199, 000000, "Disable fix for 4900129"
// *Document: NO
// *Cause:
// *Action:
14200, 00000, "Only one parameter can be specified and it must be constant or bind"
// *Document: NO
// *Cause: The parameter specified was not a constant or bind variable when the dimension value was 5.
// *Action: Ensure that the parameter is a constant or bind variable.
/ 14201-14239 reserved for errors which may be generated during
/ processing of DDL statements specific to range-range
/ partitioned tables
14201, 00000, "specified subpartition bound is too long"
// *Cause: Length of a linear key representation of a high bound of a table
// subpartition being added or along which an existing table or
// index subpartition is being split exceeded the legal limit (4K).
// *Action: Change the representation of a subpartition high bound to bring
// its length within legal limit.
14202, 00000, "subpartition bound of subpartition \"%s\" is too high"
// *Cause: High bound of the specified subpartition displayed in this
// message did not collate lower than that of the subsequent
// subpartition.
// *Action: Ensure that high bound of every subpartition (except for the last
// one) collates lower than that of a subsequent subpartition.
14203, 00000, "subpartition bound of subpartition \"%s\" is too long"
// *Cause: Length of linear key representation of a high bound of the
// specified subpartition displayed in this message exceeded the
// legal limit (4K).
// *Action: Change the representation of a subpartition high bound to bring
// its length within legal limit.
14204, 00000, "subpartition bound of subpartition number %s is too high"
// *Cause: High bound of the specified subpartition displayed in this message
// did not collate lower than that of the subsequent subpartition.
// *Action: Ensure that high bound of every subpartition (except for the last
// one) collates lower than that of a subsequent subpartition.
14205, 00000, "subpartition bound of subpartition number %s is too long"
// *Cause: Length of linear key representation of a high bound of the
// specified subpartition displayed in this message exceeded the
// legal limit (4K).
// *Action: Change the representation of a subpartition high bound to bring
// its length within legal limit.
14206, 00000, "table is not subpartitioned by List or Range methods"
// *Cause: A subpartition maintenance operation such as ALTER TABLE DROP|SPLIT|MERGE
// SUBPARTITION can only be performed on List or Range subpartitioned objects
// *Action: Issue the command only against a List or Range subpartitioned object.
14207, 00000, "maximum number of subpartitioning columns is 16"
// *Cause: number of columns in a subpartitioning column list exceeded
// the legal limit of 16
// *Action: modify subpartitioning column list so that it consists of at
// most 16 columns
14208, 00000, "lower-bound subpartition must be specified first"
// *Cause: A higher-bound subpartition was specified before the lower-bound
// subpartition in ALTER TABLE MERGE SUBPARTITIONS statement.
// *Action: Specify lower-bound subpartition first and then higher-bound subpartition
14209, 00000, "subpartitions being merged are not adjacent"
// *Cause: Attempted to merge two subpartitions that are not adjacent
// to each other.
// *Action: Specify two subpartitions that are adjacent
14210, 00000, "cannot reuse lower-bound subpartition as resulting subpartition"
// *Cause: Attempted to reuse the lower-bound subpartition of the subpartitions
// being merged.
// *Action: Specify new resulting subpartition name or reuse the higher-bound
// subpartition only
14211, 00000, "subpartition bound must collate higher than that of the last subpartition"
// *Cause: Subpartition bound specified in ALTER TABLE MODIFY PARTITION ADD SUBPARTITION
// statement did not collate higher than that of the partition's
// last subpartition.
// *Action: Ensure that the subpartition bound of the subpartition to be added
// collates higher than that of the table partition's last subpartition.
14212, 00000, "subpartition cannot be split along the specified high bound"
// *Cause: Attempted to split a subpartition along a bound which
// either collates higher than that of the subpartition to be split or
// lower than that of a subpartition immediately preceding the one
// to be split
// *Action: Ensure that the bound along which a subpartition is to be split
// collates lower than that of the subpartition to be split and
// higher than that of a subpartition immediately preceding the one
// to be split
14213, 00000, "VALUES LESS THAN or AT clause cannot be used for List subpartitioned tables"
// *Cause: VALUES LESS THAN or AT clause was used for List
// subpartitioned tables
// *Action: Use VALUES (<value list>) clause for List subpartitioned tables
14214, 00000, "VALUES (<value list>) cannot be used for Range subpartitioned tables"
// *Cause: VALUES (<value list>) clause was used for Range
// subpartitioned tables
// *Action: Use VALUES LESS THAN or AT clause with Range subpartitioned tables
14215, 00000, "subpartition bound list contains too many elements"
// *Cause: Subpartition bound list contained more elements than there are
// subpartitioning columns
// *Action: Ensure that the number of elements in subpartition bound list is
// equal to the number of subpartitioning columns of the table or index
14216, 00000, "subpartition bound list contains too few elements"
// *Cause: Subpartition bound list contained fewer elements than there are
// subpartitioning columns
// *Action: Ensure that the number of elements in partition bound list is
// equal to the number of partitioning columns of the table or index
14217, 00000, "VALUES (<value list>) clause expected"
// *Cause: VALUES (<value list>) clause was not specified for the list
// subpartition being added
// *Action: Specify a VALUES (<value list>) clause
14218, 00000, "Invalid operation for object without a segment"
// *Cause: The object (table or index or lob) did not have a segment.
// *Action: Create segments for the object with the ALTER TABLE ALLOCATE EXTENT command.
14220, 00000, "Invalid operation for object without a segment"
// *Cause: Attempted to modify storage or allocate an extent for an object
// (table or LOB or index) without a segment.
// *Action: Create segments for the object with the ALTER TABLE ALLOCATE EXTENT command.
14221, 00000, "Dictionary managed tablespace cannot be used for this operation"
// *Cause: Attempted to create an index or add a LOB column in a dictionary
// managed tablespace to a table without a segment.
// *Action: Specify a locally managed tablespace OR create segments for the
// table with the ALTER TABLE ALLOCATE EXTENT command.
14223, 00000, "Deferred segment creation is not supported for this table"
// *Cause: The SEGMENT CREATION DEFERRED clause was specified in the
// CREATE TABLE statement.
// *Action: Remove the SEGMENT CREATION DEFERRED clause.
14224, 00000, "Deferred segment creation is not supported for this schema"
// *Cause: The SEGMENT CREATION DEFERRED clause was specified in the CREATE
// TABLE statement.
// *Action: Remove the SEGMENT CREATION DEFERRED clause.
14225, 00000, "The INDEXING clause is not supported for this table."
// *Cause: The INDEXING clause was specified for an unsupported table type.
// *Action: Remove the INDEXING clause from the statement.
14226, 00000, "unique index may not be PARTIAL"
// *Cause: INDEXING PARTIAL was specified during creation or modification of
// a unique index.
// *Action: Remove the INDEXING PARTIAL clause from the statement.
14227, 00000, "INDEXING may be specified only when the underlying table is partitioned"
// *Cause: INDEXING FULL or INDEXING PARTIAL was specified during CREATE
// INDEX or ALTER INDEX when the base table was not partitioned.
// *Action: Remove the INDEXING clause from the statement.
14228, 00000, "INDEXING may not be specified for this index"
// *Cause: INDEXING FULL or INDEXING PARTIAL was specified during CREATE
// INDEX or ALTER INDEX for an unsupported index type.
// *Action: Remove the INDEXING clause from the statement.
14229, 00000, "cannot modify the indexing attribute of a composite partition"
// *Cause: An attempt was made to perform ALTER TABLE MODIFY PARTITION INDEXING
// [ON|OFF] on a composite table partition.
// *Action: Run ALTER TABLE MODIFY SUBPARTITION INDEXING [ON|OFF] on each
// subpartition individually.
14240, 00000, "use of syntax for SYSTEM and Range Composite/System (R+S) partitioning methods"
// *Document: NO
// *Cause:
// *Action:
// Level 1+ Allow use of aforementioned syntax
14241, 00000, "invalid table partitioning method"
// *Document: NO
// *Cause: Invalid partitioning method was specified in CREATE TABLE
// statement. A table may be partitioned by RANGE, SYSTEM, LIST,
// HASH, or Composite Range (R+S or R+H)."
// *Action: Specify one of valid partitioning methods
14242, 00000, "table is not partitioned by System, or Hash method"
// *Document: NO
// *Cause: The table in the ADD PARTITIONS operation is partitioned by
// method other than System, or Hash
// *Action: Ensure that the table is partitioned by System, or
// Hash method
14243, 00000, "table is not partitioned by Range, System, List, or Hash method"
// *Document: NO
// *Cause: The table in the MOVE PARTITION operation is partitioned by
// method other than Range, System, List, or Hash method
// *Action: Ensure that the table is partitioned by Range, System, List, or
// Hash method
14244, 00000, "illegal operation for a Composite Range/System partitioned table"
// *Document: NO
// *Cause: any operation done to a Composite Range/System
// partitioned table is controlled through event 14240
// *Action: Ensure that the event is turned on
/
/ 14250-14349 reserved for errors which may be generated during
/ processing of DDL statements added/modified by 8.1
/ partitioning project
14251, 00000, "Specified subpartition does not exist"
// *Cause: Subpartition not found for the object.
// *Action: Retry with correct subpartition name.
14252, 00000, "invalid ALTER TABLE MODIFY PARTITION option for a Hash partition"
// *Cause: Only ALLOCATE EXTENT and DEALLOCATE UNUSED may be specified
// in ALTER TABLE MODIFY PARTITION for a Hash partition.
// *Action: Specify only legal options.
14253, 00000, "table is not partitioned by composite partition method"
// *Cause: One of the following occurred:
//
// - The table in a subpartition maintenance operation (ALTER TABLE
// [EXCHANGE | MODIFY | MOVE | TRUNCATE] SUBPARTITION or ALTER
// TABLE MODIFY PARTITION [ADD | COALESCE] SUBPARTITION) was not
// partitioned by the composite partition method.
//
// - The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION
// operation was partitioned by a method other than the composite
// method.
//
// - The table in the ALTER TABLE MODIFY SUBPARTITION [UNUSABLE LOCAL
// INDEXES | REBUILD UNUSABLE LOCAL INDEXES] statement was not
// partitioned by the composite partition method which is illegal.
// *Action: Ensure that the table is partitioned by composite partition method.
14254, 00000, "cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table"
// *Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement
// issued against a Range or Composite Range partitioned table
// which is illegal.
// *Action: Remove the illegal option. If it is desired to add storage to
// individual partitions/subpartitions, ALLOCATE STORAGE clause
// may be specified with ALTER TABLE MODIFY PARTITION/SUBPARTITION
// statement. If it is desired to add storage to all subpartitions
// of a Composite partition, ALLOCATE STORAGE clause may be specified
// with ALTER TABLE MODIFY PARTITION.
14255, 00000, "table is not partitioned by range, list, composite range, or composite list method"
// *Cause: The table was not partitioned by the range, list, composite range,
// or composite list method.
// *Action: The ALTER TABLE [SPLIT | DROP] PARTITION or ALTER TABLE MERGE
// PARTITIONS command is only valid for a table partitioned by range,
// list, composite range, or composite list methods. Ensure that
// the table is partitioned appropriately.
14256, 00000, "invalid resulting partition description(s)"
// *Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or
// <subpartition-description> clause in partition description(s)
// in ALTER TABLE SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS
// statement but the table in the maintenance operation is not
// a Composite Range partitioned table which is illegal
// *Action: Remove invalid clause(s), or ensure that the table is partitioned
// by Composite Range method
14257, 00000, "cannot move a partition which is a composite partition"
// *Cause: An attempt was made to move a partition that was a composite partition.
// *Action: Move the subpartitions one-by-one to move the composite partition.
14258, 00000, "invalid partition description"
// *Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or
// <subpartition-description> clause in ALTER TABLE ADD PARTITION
// statement but the table in the maintenance operation is not a
// Composite Range/Hash partitioned table which is illegal
// *Action: Remove invalid clause(s), or ensure that the table is partitioned
// by Composite Range/Hash method
14259, 00000, "table is not partitioned by Hash method"
// *Cause: ALTER TABLE COALESCE PARTITION is only valid for table partitioned
// by Hash method
// *Action: Specify valid ALTER TABLE option for the table, or ensure that
// the table is partitioned by Hash method
14260, 00000, "incorrect physical attribute specified for this partition"
// *Cause: User specified INITRANS, MAXTRANS, STORAGE, PCTFREE, PCTUSED,
// and/or [NO]LOGGING option to a Hash partition via ALTER TABLE
// ADD/MOVE PARTITION command which is illegal.
// Only TABLESPACE may be specified.
// *Action: Remove invalid option(s)
14261, 00000, "partition bound may not be specified when adding this Hash partition"
// *Cause: User specified VALUES LESS THAN clause when adding a partition
// (via ALTER TABLE ADD PARTITION) to a Hash partitioned table
// which is illegal
// *Action: Remove VALUES LESS THAN clause from the description of
// partition being added
14262, 00000, "new subpartition name must differ from the old subpartition name"
// *Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying
// <new-subpartition-name> which is identical to the name of the
// subpartition being renamed
// *Action: Ensure that the new subpartition name is different from the
// name of any (including the one being renamed) existing
// subpartition of a given table or index
14263, 00000, "New subpartition name must differ from that of any other partition or subpartition of the object."
// *Cause: ALTER TABLE RENAME SUBPARTITION or ALTER INDEX RENAME SUBPARTITION
// specifying <new-subpartition-name> which is identical to the name
// of an existing partition or subpartition of the object was
// specified.
// *Action: Ensure that the new subpartition name is different from the
// name of any (including the one being renamed) existing
// partition or subpartition of a given table or index.
14264, 00000, "partitioning diagnostic improvement event"
// *Document: NO
// *Cause:
// *Action: Event is used for adding diagnostic improvements for
// partitioning area.
14265, 00000, "data type or length of a table subpartitioning column may not be changed"
// *Cause: User issued ALTER TABLE statement attempting to modify
// data type and/or length of a column used to subpartition the
// table named in ALTER TABLE statement, which is illegal
// *Action: Avoid modifying data type and/or length of table
// subpartitioning column(s)
14266, 00000, "data type or length of an index subpartitioning column may not be changed"
// *Cause: User issued ALTER TABLE statement attempting to modify
// data type and/or length of a column used to subpartition some index
// defined on the table named in ALTER TABLE statement, which is
// illegal
// *Action: Avoid modifying data type and/or length of index
// subpartitioning column(s)
14267, 00000, "cannot specify PARALLEL clause when adding a (composite) partition"
// *Cause: The ALTER TABLE ADD PARTITION statement with PARALLEL clause for a
// partition or composite partition method other than HASH was issued.
// *Action: Remove the PARALLEL clause.
14268, 00000, "subpartition '%s' of the partition resides in offlined tablespace"
// *Cause: User attempted an operation requiring that we access data
// in a subpartition which resides in a tablespace which was
// taken offline. Such operations include trying to drop a
// tablespace of a table which has indices defined on it or
// is referenced by a constraint.
// *Action: Bring tablespace online before attempting the operation.
14269, 00000, "cannot exchange partition other than a Range,List,System, or Hash partition"
// *Cause: User attempt to exchange a partition with a non-partitioned table
// but the specified partition is not a Range,List,System, or Hash partition
// which is illegal
// *Action: Specify EXCHANGE PARTITION for a Range,List,System, or Hash partition only
14270, 00000, "table is not partitioned by Range, System, Hash or List method"
// *Cause: The table in ALTER TABLE MODIFY PARTITION { UNUSABLE LOCAL
// INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not
// partitioned by Range,List,System, or Hash method which is illegal.
// *Action: Ensure that the table is partitioned by Range,List,System, or Hash method
// 14271, 00000, "free error number"
14272, 00000, "only a partition with higher bound can be reused"
// *Cause: User attempt to reuse a lower-bound partition in ALTER TABLE
// MERGE PARTITIONS statement as the resulting partition which
// is illegal.
// *Action: Use the higher-bound partition to be the resulting partition
// or specify a new partition name
14273, 00000, "lower-bound partition must be specified first"
// *Cause: User specified higher-bound partition before lower-bound
// partition in ALTER TABLE MERGE PARTITIONS statement which is
// illegal
// *Action: Specify lower-bound partition then higher-bound partition
14274, 00000, "partitions being merged are not adjacent"
// *Cause: User attempt to merge two partitions that are not adjacent
// to each other which is illegal
// *Action: Specify two partitions that are adjacent
14275, 00000, "cannot reuse lower-bound partition as resulting partition"
// *Cause: User attempt to reuse lower-bound partition of the partitions
// being merged which is illegal
// *Action: Specify new resulting partition name or reuse the higher-bound
// partition only
14276, 00000, "EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table"
// *Cause: The table in the ALTER TABLE EXCHANGE SUBPARTITION operation
// is either clustered or partitioned
// *Action: Ensure that the table with which the subpartition is being
// exchanged for is not partitioned or clustered.
14277, 00000, "tables in EXCHANGE SUBPARTITION must have the same number of columns"
// *Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION
// have different number of columns
// *Action: Ensure that the two tables have the same number of columns
// with the same type and size.
14278, 00000, "column type or size mismatch in EXCHANGE SUBPARTITION"
// *Cause: The corresponding columns in the tables specified in the
// ALTER TABLE EXCHANGE SUBPARTITION are of different type or size
// *Action: Ensure that the two tables have the same number of columns
// with the same type and size.
14279, 00000, "index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION"
// *Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION
// have indexes which are not equivalent
// *Action: Ensure that the indexes for the two tables have indexes which
// follow this rule
// For every non partitioned index for the non partitioned table,
// there has to be an identical LOCAL index on the partitioned
// table and vice versa. By identical, the column position, type
// and size have to be the same.
14280, 00000, "all rows in table do not qualify for specified subpartition"
// *Cause: There is at least one row in the non partitioned table which
// does not qualify for the subpartition specified in the ALTER TABLE
// EXCHANGE SUBPARTITION
// *Action: Ensure that all the rows in the segment qualify for
// the subpartition. Perform the alter table operation with
// the NO CHECKING option. Run ANALYZE table VALIDATE on that
// subpartition to find out the invalid rows and delete them.
14281, 00000, "CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION"
// *Cause: The corresponding columns in the tables specified in the
// ALTER TABLE EXCHANGE SUBPARTITION statement have CHECK constraint
// defined on them.
// *Action: Ensure that the two tables do not have CHECK constraint
// defined on any column
14282, 00000, "FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION"
// *Cause: The corresponding columns in the tables specified in the
// ALTER TABLE EXCHANGE SUBPARTITION statement have different
// FOREIGN KEY constraints.
// *Action: Ensure that the two tables do not have FOREIGN KEY constraints
// defined on any column or disable all FOREIGN KEY constraints
// on both tables. Then retry the operation.
14283, 00000, "UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION"
// *Cause: One of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION
// command has a UNIQUE constraint for which no matching (vis-a-vis
// key columns) constraint is defined on the other table or
// a matching constraint is defined on the other table, but it
// differs from that defined on the first table vis-a-vis being
// enabled and/or validated.
// *Action: Ensure that for every UNIQUE constraint defined on one of the
// tables named in the ALTER TABLE EXCHANGE SUBPARTITION statement
// there is a matching (vis-a-vis key columns and being enabled and/or
// validated) UNIQUE constraint defined on the other table.
// If UNIQUE constrains are enabled, UNIQUE constraints on the
// partitioned table should be enforced using local indexes.
14284, 00000, "one or more of table's subpartitions reside in a read-only tablespace"
// *Cause: User issued ALTER TABLE statement attempting to modify
// an existing VARCHAR2 (or VARCHAR) column to be of type CHAR
// (or CHARACTER), increase length of an existing CHAR (or
// CHARACTER) column, or add a column with user-specified default for
// a table one or more subpartitions of which reside in read-only
// tablespaces, which is illegal
// *Action: Avoid performing aformentioned operations on a partitioned
// table one or more subpartitions of which reside in read-only
// tablespaces
14285, 00000, "cannot COALESCE the only partition of this hash partitioned table or index"
// *Cause: A COALESCE PARTITION command was issued when there is only
// one partition in the table or index, which is illegal
// *Action: Ensure that there is at least one partition.
// Drop the table or index to remove all partitions.
14286, 00000, "cannot COALESCE the only subpartition of this table partition"
// *Cause: A COALESCE SUBPARTITION command was issued when there is only
// one subpartition in the partition which is illegal
// *Action: Ensure that there is at least one subpartition.
// Drop partition to remove all subpartitions.
14287, 00000, "cannot REBUILD a partition of a composite partitioned index"
// *Cause: An attempt was made to rebuild a partition of a composite
// partitioned index which is illegal.
// *Action: REBUILD the index partition one subpartition at a time.
14288, 00000, "index is not partitioned by composite partition method"
// *Cause: The index in a partition or subpartition maintenance operation
// (ALTER INDEX MODIFY [SUBPARTITION|DEFAULT ATTRIBUTES
// FOR PARTITION]
// or ALTER INDEX REBUILD SUBPARTITION command was not partitioned
// by the composite partition method.
// *Action: REBUILD the index partition one at a time.
14289, 00000, "cannot make local index partition of composite partitioned table unusable"
// *Cause: An attempt was made to rebuild a partition of a composite
// partitioned index which is illegal.
// *Action: REBUILD the index partition one subpartition at a time.
14290, 00000, "PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION"
// *Cause: The corresponding columns in the tables specified in the ALTER
// TABLE EXCHANGE [SUB]PARTITION statement have different PRIMARY KEY
// constraints.
// *Action: Ensure that the two tables do not have PRIMARY KEY constraints
// defined on any column or disable all PRIMARY KEY constraints
// on both tables. Then retry the operation.
14291, 00000, "cannot EXCHANGE a composite partition with a non-partitioned table"
// *Cause: A composite partition can only be exchanged with a partitioned
// table.
// *Action: Ensure that the table being exchanged is partitioned or that
// that the partition being exchanged is non-composite.
14292, 00000, "Partitioning type of table must match subpartitioning type of composite partition"
// *Cause: When exchanging a partitioned table with a composite partition
// the partitioning type of the table must match the subpartitioning
// type of the composite partition.
// *Action: Ensure that the partitioning type of partitioned table is the
// same as the subpartitioning type of the composite partition.
14293, 00000, "Number of partitioning columns does not match number of subpartitioning columns"
// *Cause: When exchanging a partitioned table with a composite partition
// the number of partitioning columns of the table must match the
// number of subpartitioning columns of the composite partition.
// *Action: Ensure that the number of partitioning columns in the partitioned
// table is the same as the number of subpartitioning columns in the
// the composite partition.
14294, 00000, "Number of partitions does not match number of subpartitions"
// *Cause: When exchanging a partitioned table with a composite partition
// the number of partitions of the table must match the
// number of subpartitions of the composite partition.
// *Action: Ensure that the number of partitions in the partitioned
// table is the same as the number of subpartitions in the
// the composite partition.
14295, 00000, "column type or size mismatch between partitioning columns and subpartitioning columns"
// *Cause: When exchanging a partitioned table with a composite partition
// the type and size of the partitioning columns of the table must
// match the type and size of the subpartitioning columns of the
// composite partition.
// *Action: Ensure that the type and size of the partitioning columns of the
// partitioned is the same as the type and size of the
// subpartitioning columns of the composite partition.
14296, 00000, "Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION"
// *Cause: The block sizes of the two tables specified in the ALTER
// TABLE EXCHANGE [SUB]PARTITION statement are different. For
// index organized tables, either the block sizes of the index
// or the overflow (or both) do not match.
// *Action Ensure that the block sizes of the tables involved in the
// ALTER TABLE EXCHANGE [SUB]PARTITION statement are the
// same. For index organized tables, ensure that the block sizes
// of both the index and the overflow of the two tables match.
14297, 00000, "Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION"
// *Cause: The block sizes of a pair of indexes being exchanged in the ALTER
// TABLE EXCHANGE [SUB]PARTITION statement are different.
// *Action Ensure that the block sizes of the corresponding pairs of
// indexes that need to be exchanged in the ALTER TABLE EXCHANGE
// [SUB]PARTITION statement are the same.
14298, 00000, "LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION"
// *Cause: The block sizes of a pair of corresponding LOB columns of
// the two tables specified in the ALTER TABLE EXCHANGE
// [SUB]PARTITION statement are different.
// *Action Ensure that the block sizes of corresponding pairs of LOB
// columns of the tables involved in the ALTER TABLE EXCHANGE
// [SUB]PARTITION statement are the same.
14299, 00000, "total number of partitions/subpartitions exceeds the maximum limit"
// *Cause: The total number of combined fragments specified in partitions
// /subpartitions exceeds 1048575.
// *Action Reissue the statement with fewer number of fragments
14300, 00000, "partitioning key maps to a partition outside maximum permitted number of partitions"
// *Cause: The row inserted had a partitioning key that maps to a partition number greater than 1048575
// *Action Ensure that the partitioning key falls within 1048575 partitions or subpartitions.
14301, 00000, "table-level attributes must be specified before partition-level attributes"
// *Cause: While processing an ALTER TABLE ADD COLUMN statement, table-level
// attributes of LOB columns were encountered after processing
// partition-level attributes of LOB columns or
// while processing CREATE TABLE statement, table-level
// attributes of LOB columns were encountered after processing
// partition descriptions.
// *Action: Modify the SQL statement to specify table-level attributes prior
// to partition-level attributes or partition descriptions; then
// retry the statement.
14302, 00000, "only one list of added-LOB-storage-clauses can be specified in a statement"
// *Cause: While parsing an ALTER TABLE ADD COLUMN statement, one list of
// added-LOB-storage-clauses was parsed when another list of
// added-LOB-storage-clauses was encountered. There cannot be more
// than one list of added-LOB-storage-clauses in a statement; all
// added-LOB-storage-clauses must be combined into one list.
// *Action: Combine all of the lists of added-LOB-storage-clauses into one
// list and retry the statement.
14303, 00000, "partitions or subpartitions are not in the right order"
// *Cause: Descriptions of partitions or subpartitions in an
// ALTER TABLE ADD COLUMN statement were ordered differently
// from the DDL order of partitions or subpartitions.
// *Action: Re-order the partitions or subpartitions in the added LOB
// storage clause by partition or subpartition DDL order, and
// retry the statement.
// *Cause: User attempted to rebuild a partition of a Composite Range partitioned index
// which is illegal
14304, 00000, "List partitioning method expects a single partitioning column"
// *Cause: number of columns in a partitioning column list exceeded
// the legal limit of 1 for List partitioned objects
// *Action: modify partitioning column list so that it consists of at
// most 1 column
14305, 00000, "List value '%s' specified twice in partition '%s'"
// *Cause: A list value cannot be specified more that once
// *Action: Remove one of the specifications of the value
14306, 00000, "List value '%s' specified twice in partitions '%s', '%s'"
// *Cause: A list value cannot be specified more that once
// *Action: Remove one of the specifications of the value
14307, 00000, "partition contains too many list values"
// *Cause: Partition list contains more than 524288 list values
// *Action: Reduce the number of values to not exceed 524288 values
14308, 00000, "partition bound element must be one of: string, datetime or interval literal, number, or NULL"
// *Cause: Partition bound list contained an element of invalid type
// (i.e. not a number, non-empty string, datetime or interval literal,
// or NULL)
// *Action: Ensure that all elements of partition bound list are of valid type
14309, 00000, "Total count of list values exceeds maximum allowed"
// *Cause: Partitioned object contains more than 524288 list values
// *Action: Reduce number of values to less than 524288.
14310, 00000, "VALUES LESS THAN or AT clause cannot be used with List partitioned tables"
// *Cause: VALUES LESS THAN or AT clause can be used only with Range
// partitioned tables
// *Action: Use VALUES (<value list>) clause with List partitioned tables
14311, 00000, "Expecting VALUES LESS THAN or AT clause"
// *Cause: VALUES (<value list>) clause can be used only with List
// partitioned tables
// *Action: Use VALUES LESS THAN clause with Range partitioned tables
14312, 00000, "Value %s already exists in partition %s"
// *Cause: One of the list values in the ADD PARTITION or ADD VALUES
// statement already exists in another partition
// *Action: Remove the duplicate value from the statement and try again
14313, 00000, "Value %s does not exist in partition %s"
// *Cause: One of the list values in the SPLIT PARTITION or DROP VALUES
// statement does not exist in the partition
// *Action: Remove the value from the statement and try again
14314, 00000, "resulting List partition(s) must contain atleast 1 value"
// *Cause: After a SPLIT/DROP VALUE of a list partition, each resulting
// partition(as applicable) must contain at least 1 value
// *Action: Ensure that each of the resulting partitions contains atleast
// 1 value
14315, 00000, "cannot merge a partition with itself"
// *Cause: The same partition name was specified twice for the merge operation
// *Action: Re-submit operation with 2 distinct partition names
14316, 00000, "table is not partitioned by List method"
// *Cause: ALTER TABLE ADD|DROP VALUES can only be performed on List partitioned objects
// *Action: Re-issue the command against a List partitioned object.
14317, 00000, "cannot drop the last value of partition"
// *Cause: ALTER TABLE DROP VALUES tried to drop the last value of the partition
// *Action: Cannot execute the command, unless two or more values exist for partition
/
14318, 00000, "DEFAULT partition must be last partition specified"
// *Cause: A partition description follows the one describing the default
// partition
// *Action: Ensure that the DEFAULT partition is the last partition description
/
14319, 00000, "DEFAULT cannot be specified with other values"
// *Cause: DEFAULT keyword has been specified along with other
// values when specifying the values for a list partition
// *Action: Ensure that if DEFAULT is specified, it is the only value specified
/
14320, 00000, "DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT"
// *Cause: DEFAULT keyword has been specified when doing a ADD VALUES or
// DROP VALUES or SPLIT partition or subpartition.
// *Action: Ensure that DEFAULT is not specified for ADD/DROP VALUES or
// SPLIT partition/subpartition operation.
/
14321, 00000, "cannot add/drop values to DEFAULT partition"
// *Cause: A ADD/DROP VALUES operation is being done on the default partition
// *Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT partition
/
14322, 00000, "DEFAULT partition already exists"
// *Cause: A partition already exists with DEFAULT value
// *Action:
/
14323, 00000, "cannot add partition when DEFAULT partition exists"
// *Cause: An ADD PARTITION operation cannot be executed when a partition
// with DEFAULT values exists
// *Action: Issue a SPLIT of the DEFAULT partition instead
/
14324, 00000, "values being added already exist in DEFAULT partition"
// *Cause: An ADD VALUE operation cannot be executed because the values
// being added exist in the DEFAULT partition
// *Action: Issue a SPLIT of the DEFAULT partition and then MERGE the split
// partition into the partition to which values need to be added
/
14325, 00000, "only LOCAL indexes may be specified in this clause"
// *Cause: A global index has been specified in the UPDATE INDEXES (..) clause
// *Action: Only specify local indexes when using this clause
/
14326, 00000, "Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause"
// *Cause: A Primary index on an IOT, DOMAIN or LOB index has been specified
// in the UPDATE INDEXES (..) clause
// *Action: Do not specify any of these indexes when using this clause
/
14327, 00000, "Some index [sub]partitions could not be rebuilt"
// *Cause: The first phase (partition DDL and index [sub]partition placement)
// completed successfully. During the second phase, some of the index
// [sub]partitions could not be rebuilt.
// *Action: Search the alert log for the string DBMS_INDEX_UTL.
// Check the error associated with each of the [sub]partitions
// that could not be rebuilt and take the appropriate corrective
// action.
/
14328, 00000, "Allow UPDATE INDEXES clause for PIOTs. To be used for testing"
// *Document: NO
// *Cause:
// *Action:
// Level 1+ Allow UPDATE INDEXES clause for IOTs.
/
14329, 00000, "domain index [sub]partitions cannot be renamed in this clause"
// *Cause: The user tried to rename a domain index [sub]partition in the
// UPDATE INDEXES clause of a ALTER TABLE MOVE [SUB]PARTITION
// operation. This is not allowed.
// *Action: Leave the name blank or use the same name.
/
14330, 00000, "Cannot drop a partition of a global hash-partitioned index"
// *Cause: An attempt was made to drop a partition of a hash-partitioned global
// index.
// *Action: Try COALESCE PARTITION instead.
/
14331, 00000, "cannot drop all [sub]partitions of a partitioned table"
// *Cause: An attempt was made to drop all partitions of a partitioned table.
// *Action: Try DROP TABLE instead.
/
14332, 00000, "duplicate partition or subpartition names specified"
// *Cause: The list of partitions contained duplicate partition or
// subpartition names.
// *Action: Ensure that list of partition or subpartition names are distinct.
/
14333, 00000, "subpartition names specified are across multiple partitions"
// *Cause: The specified subpartitions did not belong to the same partition.
// *Action: Ensure that all subpartitions specified belong to the same
// partition.
/
14334, 00000, "guard column expected"
// *Cause: There was no guard column or the NOT NULL constraint was not
// specified for this column.
// *Action: Add a guard column or NOT NULL constraint for column.
/
14335, 00000, "number of new fragments for adding partitions or creating partitioned table exceeds the maximum limit"
// *Cause: The total number of new fragments for adding partitions or for
// creating a partitioned table exceeded 125000.
// *Action Reissue the statement with a fewer number of new fragments.
14336, 00000, "partitioning test case event"
// *Document: NO
// *Cause:
// *Action: Event is used for adding test cases for partitioning area.
14337, 00000, "index is not partitioned by range, list, composite range, or composite list method"
// *Cause: The index was not partitioned by the range, list, composite range,
// or composite list method.
// *Action: The ALTER INDEX [SPLIT | DROP] PARTITION or ALTER INDEX MERGE
// PARTITIONS command is only valid for an index partitioned by range,
// list, composite range, or composite list methods. Ensure that
// the index is partitioned appropriately.
14338, 00000, "wait event for partitioning test"
// *Document: NO
// *Cause:
// *Action: Wait event used for adding test cases for partitioning area.
14339, 00000, "JavaScript Object Notation (JSON) LOB column can only be used to partition a table with JSON_VALUE operator"
// *Cause: An attempt was made to create a partitioned table using a
// virtual column as a partitioning key column that references
// a JavaScript Object Notation (JSON) LOB column but does not
// contain a JSON_VALUE operator.
// *Action: Ensure that the virtual column used as a partition key column
// contains a JSON_VALUE operator if it references a JSON LOB column.
14340, 00000, "online DDL rolled back due to DML conflict"
// *Cause: The online build journal became inconsistent with ongoing DML and
// could not be used successfully to complete the online DDL.
// *Action: Reissue the online DDL.
//
/
/ 14350 - 14399 reserved for DMLs
/
14350, 00000, "check constraint condition has an invalid reference"
// *Cause: An attempt was made to construct a check constraint condition
// with an invalid reference, such as a hidden column created for
// a virtual column, or a guard column.
// *Action: Remove the invalid reference from the check constraint condition.
/
/ 14400 - 14499 reserved for execution errors introduced by the Partitioned
/ object project
/
14400, 00000, "inserted partition key does not map to any partition"
// *Cause: An attempt was made to insert a record into, a Range or Composite
// Range object, with a concatenated partition key that is beyond
// the concatenated partition bound list of the last partition -OR-
// An attempt was made to insert a record into a List object with
// a partition key that did not match the literal values specified
// for any of the partitions.
// *Action: Do not insert the key. Or, add a partition capable of accepting
// the key, Or add values matching the key to a partition specification
14401, 00000, "inserted partition key is outside specified partition"
// *Cause: the concatenated partition key of an inserted record is outside
// the ranges of the two concatenated partition bound lists that
// delimit the partition named in the INSERT statement
// *Action: do not insert the key or insert it in another partition
14402, 00000, "updating partition key column would cause a partition change"
// *Cause: An UPDATE statement attempted to change the value of a partition
// key column causing migration of the row to another partition.
// *Action: Do not attempt to update a partition key column or ensure that
// the new partition key is within the range containing the old
// partition key.
14403, 00000, "cursor invalidation detected after getting DML partition lock"
// *Document: NO
// *Cause: cursor invalidation was detected after acquiring a partition lock
// during an INSERT, UPDATE, DELETE statement, or cursor invalidation
// was detected after refreshing consistent read snapshot for
// SELECT FOR UPDATE or SELECT before rows are returned to the client.
// This error is never returned to user, because is caught in
// opiexe() and the statement is retried.
// *Action: nothing to be done, error should never be returned to user
14404, 00000, "partitioned table contains partitions in a different tablespace"
// *Cause: An attempt was made to drop a tablespace which contains tables
// whose partitions are not completely contained in this tablespace
// *Action: find tables with partitions which span the tablespace being
// dropped and some other tablespace(s). Drop these tables or move
// partitions to a different tablespace
14405, 00000, "partitioned index contains partitions in a different tablespace"
// *Cause: An attempt was made to drop a tablespace which contains indexes
// whose partitions are not completely contained in this tablespace,
// and which are defined on the tables which are completely contained
// in this tablespace.
// *Action: find indexes with partitions which span the tablespace being
// dropped and some other tablespace(s). Drop these indexes, or move
// the index partitions to a different tablespace, or find the tables
// on which the indexes are defined, and drop (or move) them.
14406, 00000, "updated partition key is beyond highest legal partition key"
// *Cause: At attempt was made to update a record with a concatenated
// partition key that is beyond the concatenated partition bound
// list of the last partition.
// *Action: Do not update the key. Or, add a partition capable of accepting
// the key.
14407, 00000, "partitioned table contains subpartitions in a different tablespace"
// *Cause: An attempt was made to drop a tablespace which contains tables
// whose subpartitions are not completely contained in this tablespace
// *Action: find tables with subpartitions which span the tablespace being
// dropped and some other tablespace(s). Drop these tables or move
// subpartitions to a different tablespace
14408, 00000, "partitioned index contains subpartitions in a different tablespace"
// *Cause: An attempt was made to drop a tablespace which contains indexes
// whose subpartitions are not completely contained in this tablespace,
// and which are defined on the tables which are completely contained
// in this tablespace.
// *Action: find indexes with subpartitions which span the tablespace being
// dropped and some other tablespace(s). Drop these indexes, or move
// the index partitions to a different tablespace, or find the tables
// on which the indexes are defined, and drop (or move) them.
14409, 00000, "inserted partition key is outside specified subpartition"
// *Cause: the concatenated partition key of an inserted record is outside
// the ranges of the two concatenated subpartition bound lists that
// delimit the subpartition named in the INSERT statement
// *Action: do not insert the key or insert it in another subpartition
14410, 00000, "RPI LOCK TABLE issued to table referenced through synonym"
// *Document: NO
// *Cause: RPI LOCK TABLE statement was issued to acquire DML locks before
// KGL locks for a table referenced through a synonym. This error
// is never returned to user.
// *Action: nothing to be done, error should never be returned to user
14411, 00000, "The DDL cannot be run concurrently with other DDLs"
// *Cause: Another conflicting DDL was already running.
// *Action: Retry after the conflicting DDL has finished.
14412, 00000, "Error occurred during execution of partition pruning subquery"
// *Document: NO
// *Cause: The partition pruning subquery could not be run with the SCN of
// the top level query.
// *Action: N/A. Error should never be returned to user.
14413, 00000, "ALTER INDEX UNUSABLE ONLINE cannot be used with certain types of indexes."
// *Cause: An attempt was made to use the ALTER INDEX UNUSABLE ONLINE
// statement on an index type (for example, indexed-organized table
// (IOT), cluster, LOB, domain indexes) that was not allowed.
// *Action: Using the ALTER INDEX UNUSABLE ONLINE statement on certain types of
// indexes (for example, indexed-organized table (IOT), cluster, LOB,
// domain indexes) is illegal. Remove the ONLINE keyword from the
// statement.
14414, 00000, "DROP INDEX ONLINE cannot be used with certain types of indexes."
// *Cause: An attempt was made to use the DROP INDEX ONLINE statement on an
// index type (for example, indexed-organized table (IOT), cluster,
// LOB, domain indexes) that was not allowed.
// *Action: Using the DROP INDEX ONLINE statement on certain types of indexes
// (for example, indexed-organized table (IOT), cluster, LOB,
// domain indexes) is illegal. Remove the ONLINE keyword from the
// statement.
14415, 00000, "index in partially dropped state, submit DROP INDEX"
// *Cause: An attempt was made to access an index in a partially dropped
// state.
// *Action: Submit the DROP INDEX <index> statement to drop the index.
14416, 00000, "Online DDL's cannot be used with certain types of tables."
// *Cause: An attempt was made to use the DROP INDEX ONLINE, ALTER TABLE
// DROP CONSTRAINT ONLINE, or ALTER TABLE SET UNUSED COLUMN ONLINE
// statement on an table type (for example, cluster, temporary,
// index-organized table (IOT), external tables) that was not
// allowed.
// *Action: Using online DDL's like DROP INDEX ONLINE, ALTER TABLE DROP
// CONSTRAINT ONLINE, or ALTER TABLE SET UNUSED COLUMN ONLINE
// statement on certain types of tables (for example, cluster,
// temporary, indexed-organized table (IOT), external tables) is
// illegal. Remove the ONLINE keyword from the statement.
14417, 00000, "Online DDL's cannot be used with deferrable constraints."
// *Cause: An attempt was made to use the DROP CONSTRAINT ONLINE or SET UNUSED
// COLUMN ONLINE statement on constraint states (for example,
// deferrable, deferred) that was not allowed.
// *Action: Using DROP CONSTRAINT ONLINE or SET UNUSED COLUMN ONLINE statement
// on constraints that are deferrable or deferred is illegal. Remove
// the ONLINE keyword from the statement.
14418, 00000, "Online DDL's cannot be used with this constraint type."
// *Cause: An attempt was made to use the DROP CONSTRAINT ONLINE or SET UNUSED
// COLUMN ONLINE statement on a constraint type other than check,
// primary key, unique, referential, or not null constraint.
// *Action: Using DROP CONSTRAINT ONLINE or SET UNUSED COLUMN ONLINE statement
// on any other constraint types excluding check, primary key, unique,
// referential, or not null constraints is illegal. Remove the ONLINE
// keyword from the DDL.
14419, 00000, "DROP CONSTRAINT ONLINE does not support the CASCADE option."
// *Cause: An attempt was made to use the CASCADE option with DROP CONSTRAINT
// ONLINE statement.
// *Action: Using the CASCADE option with the DROP CONSTRAINT ONLINE statement
// is illegal. Remove the CASCADE keyword from the statement. Drop
// the child key constraint in a separate DROP CONSTRAINT ONLINE
// statement on the child table.
14420, 00000, "Conditions for column replacement of nulls were not satisfied."
// *Document: NO
// *Cause: An attempt was made to use the column replacement of nulls
// statement with an unsupported condition. Only heap tables are
// supported. The column cannot have any constraints or indexes
// defined on it. The column cannot be a partitioning or
// subpartitioning column. Column replacement of nulls cannot be
// combined with any other modified column option.
// *Action: Ensure all conditions for column replacement of nulls are
// satisfied.
14421, 00000, "Column replacement of nulls event"
// *Document: NO
// *Cause: Oracle internal testing only
// *Action: Never set this event (to be used only for internal testing)
14422, 00000, "Event to control behavior of online partition maintenance operations"
// *Document: NO
// *Cause: Oracle internal testing only
// *Action: Never set this event (to be used only for internal testing)
14423, 00000, "Event to test failure handling for online partition maintenance operations"
// *Document: NO
// *Cause: Oracle internal testing only
// *Action: Never set this event (to be used only for internal testing)
14424, 00000, "CREATE TABLE FOR EXCHANGE cannot be used with certain types of tables."
// *Cause: An attempt was made to use the CREATE TABLE FOR EXCHANGE statement
// on a table type (for example, cluster, temporary,
// index-organized table (IOT), external tables) that was not
// allowed.
// *Action: Do not specify the FOR EXCHANGE clause with certain types of
// tables (for example, cluster, temporary, indexed-organized table
// (IOT), external tables).
14425, 00000, "CREATE TABLE AS SELECT disallowed along with the CREATE TABLE FOR EXCHANGE clause."
// *Cause: An attempt was made to combine the CREATE TABLE FOR EXCHANGE
// clause with a CREATE TABLE AS SELECT.
// *Action: Execute a CREATE TABLE FOR EXCHANGE followed by an INSERT AS SELECT
// into the table.
14426, 00000, "Online DDL's cannot be used inside an autonomous transaction."
// *Cause: An attempt was made to use online DDL's inside an autonomous
// transaction.
// *Action: Using online DDL's inside an autonomous transaction is not allowed.
// Remove the ONLINE keyword from the statement.
14427, 00000, "table does not support modification to a partitioned state DDL"
// *Cause: An alter table modification to a partitioned state DDL was issued
// on a table that was either not a heap table or had an object type,
// domain index or bitmap join index defined on it. This DDL is only
// supported for heap tables that are non-partitioned.
// *Action: Do not use the modification to a partitioned state DDL on a
// partitioned table.
14428, 00000, "TBL$OR$IDX$PART$NUM query on remote object not supported"
// *Cause: A TBL$OR$IDX$PART$NUM query on a remote object was attempted.
// *Action: Do not use TBL$OR$IDX$PART$NUM query on remote objects.
14429, 00000, "System partitioning is not allowed in modification to a partitioned state DDL."
// *Cause: An attempt was made to convert a non-partitioned table to system
// partitioned table, which is illegal.
// *Action: Specify a different partitioning method in the modification to a
// partitioned state DDL.
14430, 00000, "An alter table modification to a partitioned state DDL cannot be combined with other operations."
// *Cause: An attempt was made to combine an alter table modification to
// partitioned state DDL with another operation, which is illegal.
// *Action: Ensure that the modification to partitioned state operation is
// the only one specified in the alter table DDL.
14431, 00000, "A system-generated column is not allowed as a partitioning column."
// *Cause: The partitioning column specified by the user was a
// system-generated column, which is illegal.
// *Action: Ensure that the partitioning column is not a system-generated
// column.
14432, 00000, "System partitioning is not allowed in the CREATE TABLE FOR EXCHANGE DDL statement."
// *Cause: An attempt was made to create a system partitioned table using the
// CREATE TABLE FOR EXCHANGE DDL statement, which is illegal.
// *Action: Specify a different partitioning method in the CREATE TABLE FOR
// EXCHANGE DDL statement.
14433, 00000, "Reference partitioning is not allowed in the online version of modification to a partitioned state DDL."
// *Cause: An attempt was made to convert a non-partitioned table to a
// reference partitioned table using the online version of the DDL,
// which is not allowed.
// *Action: Remove the ONLINE keyword from the statement.
14434, 00000, "non-existent partitioning column in ALTER TABLE statement"
// *Cause: The partitioning column specified in the ALTER TABLE statement was
// not one of the columns of the table being altered.
// *Action: Ensure that all columns in the partitioning column list
// are columns of the table being altered.
14435, 00000, "partition bound specified when adding this system partition"
// *Cause: The user specified either a VALUES LESS THAN clause or a
// VALUES (<values_list>) clause when adding a partition to a system
// partitioned table, which is not allowed.
// *Action: Remove the VALUES LESS THAN clause and VALUES (<values_list>)
// clause from the partition being added.
14436, 00000, "During the modification to a partitioned state DDL, it is illegal to specify SUBPARTITIONS or STORE IN clause once a SUBPARTITION TEMPLATE has been specified."
// *Cause: The user specified either a SUBPARTITIONS or a STORE IN clause
// along with a subpartition template when modifiying a table to
// partitioned state, which is not allowed.
// Action: Remove either the SUBPARTITIONS | STORE IN clause or remove the
// SUBPARTITION TEMPLATE clause.
/
/ 14450 - 14499 reserved for execution errors introduced by the
/ Temporary Tables project
14450, 00000, "attempt to access a transactional temp table already in use"
// *Cause: An attempt was made to access a transactional temporary table that
// has been already populated by a concurrent transaction of the same
// session.
// *Action: do not attempt to access the temporary table until the
// concurrent transaction has committed or aborted.
14451, 00000, "unsupported feature with temporary table"
// *Cause: An attempt was made to create an IOT, specify physical attributes,
// specify partition or parallel clause.
// *Action: do not do that.
14452, 00000, "attempt to create, alter or drop an index on temporary table already in use"
// *Cause: An attempt was made to create, alter or drop an index on temporary
// table which is already in use.
// *Action: All the sessions using the session-specific temporary table have
// to truncate table and all the transactions using transaction
// specific temporary table have to end their transactions.
14453, 00000, "attempt to use a LOB of a temporary table, whose data has alreadybeen purged"
// *Cause: An attempt was made to use LOB from a temporary table whose data
// has been dropped either because table was transaction-specific and
// transaction has commited or aborted, table was truncated or session
// which created this LOB has ended.
// *Action: This LOB locator is invalid and cannot be used.
14454, 00000, "attempt to reference temporary table in a referential integrity constraint"
// *Cause: An attempt was made to reference temporary table in a referencial
// integrity constraint. This is not supported.
// *Action: Use triggers.
14455, 00000, "attempt to create referential integrity constraint on temporary table"
// *Cause: An attempt was made to create a referential integrity constraint on
// a temporary table. This is not supported.
// *Action: Use triggers.
14456, 00000, "cannot rebuild index on a temporary table"
// *Cause: An attempt was made to rebuild an index on a temp table.
// *Action: The index data is anyway lost at end of session/transaction.
14457, 00000, "disallowed Nested Table column in a Temporary table"
// *Cause: An attempt made to create a Nested Table column in a
// temporary table. This is not supported.
// *Action: Do not specify these datatypes for temporary tables.
14458, 00000, "attempt was made to create a temporary table with INDEX organization"
// *Cause: An attempt was made to create an Index Organized Temporary table.
// This is not supported.
// *Action: Create the table with HEAP organization and the primary key.
14459, 00000, "missing GLOBAL keyword"
// *Cause: keyword GLOBAL is missing while creating temporary table.
// *Action: supply keyword.
14460, 00000, "only one COMPRESS or NOCOMPRESS clause may be specified"
// *Cause: COMPRESS was specified more than once, NOCOMPRESS was specified more
// than once, or both COMPRESS and NOCOMPRESS were specified.
// *Action: specify each desired COMPRESS or NOCOMPRESS clause option only once.
14461, 00000, "cannot REUSE STORAGE on a temporary table TRUNCATE"
// *Cause: REUSE STORAGE was specified with TRUNCATE on a temporary table.
// This is unsupported as it is meaningless.
// *Action: Specify DROP STORAGE instead (which is the default).
14462, 00000, "cannot TRUNCATE temporary table in an autonomous transaction which is already in use by the parent transaction"
// *Cause: An attempt was made to TRUNCATE a temporary table in an autonomous
// transaction which was already in use by the parent transaction.
// *Action: Ensure that the temporary table is not being used by the parent
// transaction before trying to TRUNCATE in an autonomous transaction.
14463, 00000, "OPERATIONS keyword not specified"
// *Cause: OPERATIONS keyword was not specified in the Compression Clause.
// *Action: specify OPERATIONS in the Compression Clause.
14464, 00000, "Compression Type not specified"
// *Cause: Compression Type was not specified in the Compression Clause.
// *Action: specify Compression Type in the Compression Clause.
14465, 00000, "Fast-Split is not possible on these partitions"
// *Cause: The Fast-Split event was forced in this session.
// *Action: Disable the event that forces Fast-Split.
14466, 00000, "Data in a read-only partition or subpartition cannot be modified."
// *Document : Yes
// *Cause: An attempt was made to modify data residing in a read-only
// partition or subpartition.
// *Action: Modify this partition or subpartition to read/write or do not
// make the modification.
14467, 00000, "This option cannot be issued with the READ ONLY or READ WRITE clause."
// *Document : Yes
// *Cause: An attempt was made to issue a READ ONLY or READ WRITE
// clause combined with the ONLINE or the INCLUDING ROWS clause.
// *Action: Issue the READ ONLY or READ WRITE clause with the ONLINE or
// the INCLUDING ROWS clause in separate statements.
14468, 00000, "invalid INCLUDING ROWS WHERE ... clause"
// *Document : Yes
// *Cause: An invalid INCLUDING ROWS WHERE ... clause was specified.
// The INCLUDING ROWS WHERE ... clause has the following restrictions:
// - It can only refer to the target table of the DDL.
// - It cannot have subselect queries.
// - It cannot refer to the SYSDATE function.
// - It cannot refer to the ROWNUM pseudo column or the ROWID column.
// *Action: Rewrite the WHERE clause so that it does not have the restrictions
// previously listed.
14469, 00000, "ALTER TABLE MOVE INCLUDING ALL LOBS cannot be used with certain types of tables."
// *Cause: An attempt was made to use the ALTER TABLE MOVE INCLUDING ALL LOBS
// statement on a table type (for example, cluster, temporary,
// index-organized table (IOT) or external tables) that was not
// allowed.
// *Action: Do not specify the INCLUDING ALL LOBS clause with certain types of
// tables (for example, cluster, temporary, indexed-organized table
// (IOT) or external tables).
14470, 00000, "Invalid usage of the fast modification to nonpartitioned state DDL."
// *Cause: An attempt was made to use the fast modification to nonpartitioned
// state DDL with an unsupported condition. The ALTER TABLE MODIFY
// NONPARTITIONED FAST DDL has the following restrictions:
// - Only heap tables are supported.
// - Partitioned tables can have only one fragment.
// - Tables cannot be reference partitioned or have any reference
// partitioned children.
// *Action: Ensure that all of the conditions for the fast modification to
// nonpartitioned state DDL are satisfied.
/
/ 14500-14550 Analyze errors added by partitioned object project
/ not used - 14502
14500, 00000, "LOCAL option not valid without partition name"
// *Cause: Incorrect syntax specified
// *Action: Retry the command
14501, 00000, "object is not partitioned"
// *Cause: Table or index is not partitioned. Invalid syntax.
// *Action: Retry the command with correct syntax.
14503, 00000, "only one partition name can be specified"
// *Cause: More than one partition name has been specified for analyze
// *Action: Specify one partition name.
14504, 00000, "syntax not supported for analyze"
// *Cause: A partition/subpartition number or bind variable has been used
// *Action: Specify a valid partition/subpartition name.
14505, 00000, "LOCAL option valid only for partitioned indexes"
// *Cause: Incorrect syntax specified
// *Action: Retry the command
14506, 00000, "LOCAL option required for partitioned indexes"
// *Cause: Incorrect syntax specified
// *Action: Retry the command
14507, 00000, "partition corrupt. all rows do not fall within partition bounds"
// *Cause: The partition contains rows which should really be in some
// other partition. Possibly due to an exchange partition without
// validation
// *Action: Delete rows in partition which do not qualify
14508, 00000, "specified VALIDATE INTO table not found"
// *Cause: The specified table either does not exist or user does not have
// the proper privleges.
// *Action: Specify the correct table to use.
14509, 00000, "specified VALIDATE INTO table form incorrect"
// *Cause: The specified table does not have the proper field definitions.
// *Action: Specify the correct table to use. See utlvalid.sql for more information.
14510, 00000, "can specify VALIDATE INTO clause only for partitioned tables"
// *Cause: The VALIDATE INTO has been specified for a non partitioned table
// or cluster or index.
// *Action: Use syntax correctly
14511, 00000, "cannot perform operation on a partitioned object"
// *Cause: An attempt was made to perform an operation that is not allowed
// on partitioned tables or indexes.
// *Action: Retry the command with correct syntax.
14512, 00000, "cannot perform operation on a clustered object"
// *Cause: An attempt was made to perform an operation that is not allowed
// on clustered tables or indexes.
// *Action: Retry the command with correct syntax.
14513, 00000, "partitioning column may not be of object datatype"
// *Cause: Partitioning column specified by the user was an object datatype
// (object, REF, nested table, array) which is illegal.
// *Action: Ensure that no partitioning column is an object datatype.
14514, 00000, "LOCAL option not valid without subpartition name"
// *Cause: Incorrect syntax specified
// *Action: Retry the command
14515, 00000, "only one aubpartition name can be specified"
// *Cause: More than one subpartition name has been specified for analyze
// *Action: Specify one subpartition name.
14516, 00000, "subpartition corrupt. all rows do not fall within subpartition bounds"
// *Cause: The subpartition contains rows which should really be in some
// other subpartition. Possibly due to an exchange subpartition without
// validation
// *Action: Delete rows in subpartition which do not qualify
14517, 00000, "subpartition of index '%s.%s' is in unusable state"
// *Cause: An attempt has been made to access an index subpartition
// that has been marked unusable by a direct load or by a DDL
// operation
// *Action: REBUILD the unusable index subpartition
14518, 00000, "partition contains rows corresponding to values being dropped"
// *Cause: table partition contains rows for the values being dropped.
// *Action: DELETE all rows for the values being dropped and reissue statement
14519, 00000, "Conflicting tablespace blocksizes for %s %s: Tablespace %s block size %s [%s] conflicts with previously specified/implied tablespace %s block size %s [%s]"
// *Cause: An attempt has been made to create a partitioned
// object in a manner that would require the partitioned
// object to span tablespaces of more than one block size.
// *Action: Ensure that all tablespaces specified in the DDL command
// for the given object as well as any tablespaces implicitly
// assigned to partitions or subpartitions of the object being created
// are all of the same block size.
14520, 00000, "Tablespace %s block size [%s] does not match existing object block size [%s]"
// *Cause: A DDL statement was issued that would require a tablespace of a
// block size different from the block size of the specified
// partitioned object to be assigned either:
// (1) As the object's default tablespace (or one of the
// object's partition-level default tablespaces,
// if composite partitioning is being used) OR
// (2) To one of the object's partitions/subpartitions.
// *Action: Specify a tablespace of the same block size as the partitioned
// object.
14521, 00000, "Default tablespace %s block size [%s] for %s %s does not match existing %s block size [%s]"
// *Cause: A DDL statement was issued that would require creation of a new
// partition/subpartition in the object-level default
// tablespace of an existing partitioned object. However, the
// object-level default tablespace block size does not match
// the block size of the partitioned object.
// *Action: Either
// (1) Modify the default tablespace of the partitioned
// object to a tablespace of the same block size as the
// object and then retry the DDL command, OR
// (2) Ensure that tablespaces of the correct block size are
// specified for all new partitions/subpartitions being
// created.
14522, 00000, "Partition-level default tablespace %s block size [%s] for %s %s does not match existing %s block size [%s]"
// *Cause: A DDL statement was issued that would require creation of a new
// subpartition in one of the partition-level default
// tablespaces of an existing composite partitioned
// object. However, the partition-level default tablespace
// block size does not match the block size of the partitioned object.
// *Action: Either
// (1) Modify the partition-level default tablespace of the
// appropriate partition of the partitioned
// object to a tablespace of the same block size as the
// object and then retry the DDL command, OR
// (2) Ensure that tablespaces of the correct block size are
// specified for all new subpartitions being
// created.
14523, 00000, "Cannot co-locate [sub]partition of %s %s with table [sub]partition because %s block size [%s] does not match table block size [%s]"
// *Cause: A DDL statement was issued that would require
// a partition/subpartition of a local index/LOB column to
// be co-located with the corresponding partition/subpartition
// of the base table. However, this is not possible because
// the block sizes of the table and the LOB column/local
// index are different.
// *Action: Either
// (1) Specify an object-level default tablespace (or
// partition-level default tablespace for the
// appropriate partition, if composite partitioning is
// used) for the partitioned local index/LOB column
// and then retry the DDL command, OR
// (2) Ensure that tablespaces of the correct block size are
// specified for all new partitions/subpartitions being
// created.
// Also ensure that neither of TABLESPACE DEFAULT and
// STORE IN (DEFAULT) is specified for a local index whose
// block size does not match that of the base table.
14524, 00000, "Always allow partitioning. To be used only by trusted clients"
// *Document: NO
// *Cause:
// *Action:
// Level 1+ Allow partitioning irrespective of edition.
14525, 00000, "Fast Split event"
// *Document: NO
// *Cause:
// *Action:
// Level Action
// 0x0001 Dont try fast split
// 0x0002 Tracing for why fast split failed
14526, 00000, "This event is no longer used."
// *Document: NO
// *Cause:
// *Action:
// However don't reuse the event because there might be installations
// have it set.
14527, 00000, "Allow ROWID datatype for partitioning key columns"
// *Document: NO
// *Cause:
// *Action:
// Level 1+ Allow partitioning on columns having ROWID datatype.
// Note: remove this event once we fully support
// partitioning on columns with ROWID datatype in 10g+.
14528, 00000, "simulated crash during drop table optimization"
// *Document: NO
// *Cause: Oracle internal testing only
// *Action: Never set this event (to be used only for internal testing)
/
14529, 00000, "copy hakan factor during ctas at facilitate exchange partition"
// *Document: NO
// *Cause: Oracle internal testing only
// *Action: Never set this event unless running into bug 3747472
14530, 00000, "row mismatches found in table %s.%s and index %s.%s"
// *Document:YES
// *Cause: rows in table and index inconsistent
// *Action: run complete analyze to determine corrupt rows
14531, 00000, "Event to enable Hash composite partitioning for 11.0.0.0"
// *Document: NO
// *Cause: Oracle internal testing only
// *Action: Never set this event (to be used only for internal testing)
14532, 00000, "Event for bug 5618049"
// *Document: NO
// *Cause: Needs to be set to turn on fix for 5618049
// *Action:
14533, 00000, "Event for ALTER TABLE enhancements for code point semantics"
// *Document: NO
// *Cause:
// *Action: Needs to be set to turn on fix for bug 5952255. Also used
// to turn on some other special behavior for the DMU tool.
14534, 00000, "Event for bug 5996430 fix to be turned on"
// *Document: NO
// *Cause:
// *Action: Needs to be set to turn on fix for bug 5996430
14535, 00000, "Event for special handling of shared objects in the DMU tool"
// *Document: NO
// *Cause: Added for bug #23043417.
// *Action:
14536, 00000, "Event to turn on row movement during CREATE TABLE"
// *Document: NO
// *Cause:
// *Action:
14537, 00000, "Crash Event for Create table by multi transaction approach"
// *Document: NO
// *Cause:
// *Action:The only operation allowed on this table is drop table purge.
14538, 00000, "Only Drop table purge allowed"
// *Document: NO
// *Cause:
// *Action:The only operation allowed on this table is drop table purge.
14539, 00000, "Crash Event for multi transaction drop index"
// *Document: NO
// *Cause:
// *Action:The only operation allowed on this index is drop index.
/
/============================================================================
/ 14551 - 14569 Reserved for purity errors during execution
/
/ Begin messages for purity error checks
/============================================================================
/
14551, 00000, "cannot perform a DML operation inside a query "
// *Cause: DML operation like insert, update, delete or select-for-update
// cannot be performed inside a query or under a PDML slave.
// *Action: Ensure that the offending DML operation is not performed or
// use an autonomous transaction to perform the DML operation within
// the query or PDML slave.
14552, 00000, "cannot perform a DDL, commit or rollback inside a query or DML "
// *Cause: DDL operations like creation tables, views etc. and transaction
// control statements such as commit/rollback cannot be performed
// inside a query or a DML statement.
// *Action: Ensure that the offending operation is not performed or
// use autonomous transactions to perform the operation within
// the query/DML operation.
14553, 00000, "cannot perform a lob write operation inside a query "
// *Cause: A lob write operation cannot be performed inside a query or a
// PDML slave.
// *Action: Ensure that the offending lob write operation is not performed or
// use an autonomous transaction to perform the operation within
// the query or PDML slave.
14554, 00000, "cannot perform requested operation during database startup "
// *Cause: Requested operation requires the Cost Based Optimizer(CBO) which is
// not available during database startup. Features like partitioning,
// IOTs, grouping sets, and flashback cursor require the CBO.
// *Action: Retry the query after the database is open.
/============================================================================
/ 14570 - 14599 Reserved for recovery-related (internal) errors
/============================================================================
/
14570, 00000, "force log writer error"
// *Document: NO
// *Cause:
// *Action: See the function prologue for kcrfw_force_io_err() for a
// description of how the level is used to force various errors.
//
/
/============================================================================
/ 14601 - 14700 reserved for 9.0.2 partitioning project
/
/ Begin messages for 9.0.2 partitioning changes
/============================================================================
/
14601, 00000, "Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template"
// *Cause: Cannot specify these clauses while specifying a template
// *Action: Correct the subpartition template clause.
14602, 00000, "SUBPARTITION TEMPLATE is legal only for a composite partitioned table"
// *Cause: SUBPARTITION TEMPLATE can be specified only for composite
// partitioned tables
// *Action: Do not use SUBPARTITION TEMPLATE on non-partitioned or
// non-composite partitioned tables.
14603, 00000, " [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables"
// *Cause: This syntax is valid only if subpartitioning dimension is hash
// *Action:
14604, 00000, "During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified"
// *Cause: Once a subpartition template has been specified during a CREATE
// TABLE it is illegal to specify SUBPARTITIONS or STORE IN anywhere
// else
// Action: Remove either the SUBPARTITIONS | STORE IN or remove the
// SUBPARTITION TEMPLATE clause
14605, 00000, "Name missing for subpartition / lob segment in template"
// *Cause: A subpartition / lob segment was not specified a name in the
// template descriptions
// *Action: All subpartitions / lob segments must have names specified in the
// template
14607, 00000, "Tablespace was not specified for previous subpartitions in template but is specified for %s"
// *Cause: Tablespaces may either be specified for all subpartitions or must
// not be specified for any subpartitions
// *Action: Either specify tablespaces for all or for none of the subpartitions
14610, 00000, "Lob attributes not specified for lob column %s for subpartition %s"
// *Cause: Lob attributes of a column must be specified for all subpartitions
// or must not be specified at all
// *Action: Ensure lob attributes of a column are specified for all
// subpartitions or not specified at all
14611, 00000, "Duplicate subpartition name %s in template"
// *Cause: A subpartition name cannot be duplicated within the template
// *Action: Rename one of the subpartitions.
14612, 00000, "Duplicate lob segment name %s for lob column %s in template"
// *Cause: Two lob segments of the same column were given the same name in the
// template
// *Action: Rename one of the lob segments
14613, 00000, "Attempt to generate name from parent name %s and template name %s failed as the combine named would have been longer than allowed"
// *Cause: Any name generated from a partition name and template name must be
// less than the maximum permissible name for an identifier
// *Action: Shorten either partition or template name.
14614, 00000, "List value '%s' specified twice in subpartition '%s'"
// *Cause: A list value cannot be specified more that once
// *Action: Remove one of the specifications of the value
14615, 00000, "List value '%s' specified twice in subpartitions '%s', '%s'"
// *Cause: A list value cannot be specified more that once
// *Action: Remove one of the specifications of the value
14616, 00000, "table is not subpartitioned by List method"
// *Cause: A subpartition maintenance operation, such as ALTER TABLE MODIFY
// SUBPARTITION ADD|DROP VALUES, was performed on a non-List
// subpartitioned object.
// *Action: Reissue the command against a List subpartitioned object.
14617, 00000, "cannot add/drop values to DEFAULT subpartition"
// *Cause: A ADD/DROP VALUES operation is being done on the default
// subpartition
// *Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT subpartition
14618, 00000, "cannot drop the last value of subpartition"
// *Cause: ALTER TABLE DROP VALUES tried to drop the last value of the subpartition
// *Action: Cannot execute the command, unless two or more values exist for subpartition
14619, 00000, "resulting List subpartition(s) must contain at least 1 value"
// *Cause: After a SPLIT/DROP VALUE of a list subpartition, each resulting
// subpartition(as applicable) must contain at least 1 value
// *Action: Ensure that each of the resulting subpartitions contains atleast
// 1 value
14620, 00000, "DEFAULT subpartition already exists"
// *Cause: A subpartition already exists with DEFAULT value
// *Action: Remove the DEFAULT value from the list specified
14621, 00000, "cannot add subpartition when DEFAULT subpartition exists"
// *Cause: An ADD SUBPARTITION operation cannot be executed when a
// subpartition with DEFAULT values exists
// *Action: Issue a SPLIT of the DEFAULT subpartition instead
14622, 00000, "Value %s already exists in subpartition %s"
// *Cause: One of the list values in the ADD SUBPARTITION or ADD VALUES
// statement already exists in another subpartition
// *Action: Remove the duplicate value from the statement and try again
14623, 00000, "Value %s does not exist in subpartition %s"
// *Cause: One of the list values in the SPLIT PARTITION or DROP VALUES
// statement does not exist in the subpartition
// *Action: Remove the value from the statement and try again
14624, 00000, "DEFAULT subpartition must be last subpartition specified"
// *Cause: A subpartition description follows the one describing the default
// subpartition
// *Action: Ensure that the DEFAULT subpartition is the last subpartition
// description
14625, 00000, "subpartition contains rows corresponding to values being dropped"
// *Cause: table subpartition contains rows for the values being dropped.
// *Action: DELETE all rows for the values being dropped and reissue statement
14626, 00000, "values being added already exist in DEFAULT subpartition"
// *Cause: An ADD VALUE operation cannot be executed because the values
// being added exist in the DEFAULT subpartition
// *Action: Issue a SPLIT of the DEFAULT subpartition and then MERGE the split
// subpartition into the subpartition to which values need to be added
14627, 00000, "Invalid operation was specified on a GLOBAL partitioned index"
// *Cause: An invalid operation such as ALTER INDEX DROP|SPLIT SUBPARTITION
// was specified on the global index
// *Action: Ensure that subpartition level operations are not specified on a
// GLOBAL index, since these are only RANGE partitioned
14628, 00000, "specification of bounds is inconsistent with LIST method"
// *Cause: An operation such as ALTER TABLE SPLIT|ADD SUBPARTITION specified
// bounds that were inconsistent with List subpartitioning method
// *Action: Specify VALUES/subpartition descriptions correctly for SPLIT/ADD
// of List subpartitions
14629, 00000, "cannot drop the only subpartition of a partition"
// *Cause: A drop subpartition command is being executed when there
// is only one subpartition in the partition
14630, 00000, "subpartition resides in offlined tablespace"
// *Cause: User attempted an operation requiring that we access data
// in a subpartition which resides in a tablespace which was
// taken offline. Such operations include trying to drop a
// tablespace of a table which has indices defined on it or
// is referenced by a constraint.
// *Action: Bring tablespace online before attempting the operation.
14631, 00000, "the partition bounds do not match the subpartition bounds of the partition"
// *Cause: When exchanging a partitioned table with a composite partition
// the bounds that describe the partitions of the table must match
// the bounds that describe the subpartitions of the composite
// partition.
// *Action: Ensure that the bounds describing partitions in the partitioned
// table is the same as the bounds of the subpartitions in the
// the composite partition.
14632, 00000, "cannot specify PARALLEL clause when adding a List subpartition"
// *Cause: User issued ALTER TABLE ADD SUBPARTITION statement with PARALLEL
// clause for a List subpartition of a Range/List partitioned object
// which is illegal
// *Action: Remove the PARALLEL clause.
14633, 00000, "Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table"
// *Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for
// ADD hash subpartition to a composite partitioned table.
// *Action:Remove clause and reissue operation
14634, 00000, "Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table"
// *Cause: During a split or a merge of a partition of a range list
// partitioned table you cannot specify any subpartitioning
// information for the resulting partition (s)
// *Action: Remove all subpartitioning information from the DDL.
14635, 00000, "only one resulting subpartition can be specified for MERGE SUBPARTITIONS"
// *Cause: ALTER TABLE MERGE SUBPARTITIONS contained more than one resulting
// subpartition for the MERGE
// *Action: Ensure that the statement describes exactly one subpartition
// as the target that need to be MERGEd
14636, 00000, "only 2 resulting subpartition can be specified for SPLIT SUBPARTITION"
// *Cause: ALTER TABLE SPLIT SUBPARTITION contained more than 2 resulting
// subpartition for the SPLIT
// *Action: Ensure that the statement describes exactly 2 subpartitions
// as the target of the SPLIT operation
14637, 00000, "cannot merge a subpartition with itself"
// *Cause: The same subpartition name was specified twice for the merge
// operation
// *Action: Re-submit operation with 2 distinct subpartition names within the
// same composite partition
14638, 00000, "cannot MERGE subpartitions in different Range Composite partitions"
// *Cause: Attempted to MERGE subpartitions in different Range Composite
// partitions
// *Action: Reissue the command after ensuring that the 2 subpartitions being
// merged lie in the same composite partition
14639, 00000, "SUBPARTITIONS clause can be specfied only for Hash, Composite Range Hash table/partition"
// *Cause: Attempted to specify SUBPARTITIONS clause on table that is not
// partitioned by the Composite Range-Hash method
// *Action: Reissue the command after ensuring that the SUBPARTITIONS clause is
// not specified, to specify a template for a Composite Range List
// object use the SUBPARTITION TEMPLATE clause
14640, 00000, "add/coalesce index partition operation is valid only for hash partitioned global indexes"
// *Cause: User attempted to add or coalesce an index partition of a global
// index not partitioned by hash method.
// *Action: Issue the statement on a global index partitioned by hash method.
// or if the index is partitioned by range method consider using
// split/drop instead of add/coalesce.
14641, 00000, "STORE-IN clause can be specified only for a Hash, Interval, Autolist, Composite Range Hash, Composite Interval, Composite Autolist table or partition"
// *Cause: Specifying a STORE-IN clause during creation or altering of a Range,
// Composite Range List partitioned table was not allowed.
// *Action: Re-issue the statement after removing the STORE-IN clause.
14642, 00000, "Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION"
// *Cause: The two tables in the EXCHANGE have usable bitmap indexes, and the
// INCLUDING INDEXES option has been specified and the tables have
// different hakan factors.
// *Action: Perform the exchange with the EXCLUDING INDEXES option or alter the
// bitmap indexes to be unusable.
14643, 00000, "Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION"
// *Cause: Either records_per_block has been minimized for one of the tables to be
// exchanged, but not the other, or the hakan factors for the tables to be
// exchanged are not equal.
// *Action: If records_per_block has been minimized for one of the tables, but not
// the other, either perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK
// option for both tables, or perform alter table with the MINIMIZE
// RECORDS_PER_BLOCK for both tables. If the hakan factors do not match
// perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option
// for both tables.
14644, 00000, "table is not subpartitioned by Hash method"
// *Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY
// PARTITION COALESCE SUBPARTITION can only be performed on Hash
// subpartitioned objects
// *Action: Re-issue the command against a Hash subpartitioned object.
14645, 00000, "STORE IN clause cannot be specified for Range List objects"
// *Cause: A STORE IN clause was specified for Range List partitioned object
// *Action: Re-issue the command after removng the STORE IN clause
14646, 00000, "Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes"
// *Cause: The first time a table is altered to include compression, it
// cannot have a usable bitmap index (partition). Subsequent alter table
// statements involving compression do not have this same restriction.
// *Action: A) Drop any bitmap indexes defined on the table, and re-create them
// once the operation is complete or, B) Mark all index fragments of
// all bitmap indexes defined on the table UNUSABLE and rebuild them
// once the operation is complete.
14647, 00000, "cannot MERGE subpartitions in different list composite partitions"
// *Cause: An attempt was made to MERGE subpartitions in different list
// composite partitions.
// *Action: Reissue the command after ensuring that the two subpartitions being
// merged lie in the same composite partition.
/============================================================================
/ 14650 - 14689 reserved for reference-partitioning project
/
/ Begin messages for reference-partitioning changes
/============================================================================
/
14650, 00000, "operation not supported for reference-partitioned tables"
// *Cause: Attempted to perform an operation on a
// reference-partitioned table that was not supported.
// *Action: Do not perform the unsupported operation.
/
14651, 00000, "reference partitioning constraint is not supported"
// *Cause: The specified partitioning constraint was not supported
// for reference-partitioned tables. The partitioning
// constraint must be enabled, validated, and not deferrable.
// The partitioning constraint must not have ON DELETE SET
// NULL semantics.
//* Action: Correct the statement to specify a supported
// partitioning constraint.
/
14652, 00000, "reference partitioning foreign key is not supported"
// *Cause: The specified partitioning foreign key was not supported
// for reference-partitioned tables. All columns of the
// partitioning foreign key must be constrained NOT NULL with
// enabled, validated, and not deferrable constraints. Furthermore,
// a virtual column cannot be part of the partitioning foreign key.
//* Action: Correct the statement to specify a supported
// partitioning foreign key.
/
14653, 00000, "parent table of a reference-partitioned table must be partitioned"
// *Cause: Attempted to create a reference-partitioned table with a
// non-partitioned parent table.
// *Action: Correct the statement and reenter.
/
14654, 00000, "number of partitions of reference-partitioned table must equal that of the parent table"
// *Cause: Attempted to create a reference-partitioned table with a
// number of partitions which was different from that of the
// parent table.
//* Action: Correct the CREATE TABLE statement to specify a correct
// number of partitions.
/
14655, 00000, "reference partitioning constraint not found"
// *Cause: Partitioning constraint specified in CREATE TABLE ...
// PARTITION BY REFERENCE was not one of the referential
// constraints on the table being created.
// *Action: Ensure that the specified partitioning constraint is one
// of the referential constraints on the table being created.
/
14656, 00000, "cannot drop the parent of a reference-partitioned table"
// *Cause: Attempted to drop the parent of a reference-partitioned table.
// *Action: Drop all reference-partitioned child tables before dropping the
// parent table.
/
14657, 00000, "cannot cascade row migration to reference-partitioned child table"
// *Cause: Update of a parent key may require migration of rows in
// reference-partitioned child tables, however this is not
// supported because the parent key was not suitably indexed.
// *Action: Replace the existing index on the parent key with a unique index
// that does not contain any columns in addition to the parent key.
/
14658, 00000, "specified dependent table is not affected by this operation"
// *Cause: A table has been specified in the DEPENDENT TABLES clause that
// is not a reference-partitioned table affected by the operation.
// *Action: Correct the statement and reenter.
/
14659, 00000, "Partitioning method of the parent table is not supported"
// *Cause: An attempt was made to create a reference-partitioned table with an
// interval partitioned parent table.
// *Action: Do not create a reference-partitioned table with an interval
// partitioned parent table.
/
14660, 00000, "parent table of a reference-partitioned table cannot be index-organized"
// *Cause: Attempted to create a reference-partitioned table with a
// index-organized parent table.
// *Action: Correct the statement and reenter.
/
14661, 00000, "row movement must be enabled"
// *Cause: Attempted to disable row movement for a reference-partitioned
// table, although row movement was enabled for its parent table.
// *Action: Disable row movement for parent table before disabling row
// movement for the reference-partitioned table.
/
14662, 00000, "row movement cannot be enabled"
// *Cause: Attempted to enable row movement for a partitioned table,
// although row movement was disabled for a reference-partitioned
// child table.
// *Action: Enable row movement for reference-partitioned child tables
// before enabling row movement for the parent table.
/
14663, 00000, "reference partitioning parent key is not supported"
// *Cause: Parent key of the reference-partitioned table's
// partitioning constraint contained virtual columns.
// *Action: Correct the statement to specify a partitioning
// constraint with supported parent key and reenter.
/
14664, 00000, "Cannot use PL/SQL expressions in reference partitioning parent key"
// *Cause: Parent key of the reference partitioned table's
// partitioning constraint contained a virtual column
// that referenced a PL/SQL expression.
// *Action: Correct the statement to specify a partitioning
// constraint with supported parent key and reenter.
/
14665, 00000, "Cannot use expressions involving ROWID data type in reference partitioning parent key"
// *Cause: Parent key of the reference partitioned table's
// partitioning constraint contained a virtual column
// that involved the ROWID data type.
// *Action: Correct the statement to specify a partitioning
// constraint with supported parent key and reenter.
/
14666, 00000, "Cannot use expressions involving BLOB or CLOB data types in reference partitioning parent key"
// *Cause: Parent key of the reference partitioned table's
// partitioning constraint contained a virtual column
// that involved a BLOB or CLOB data type.
// *Action: Correct the statement to specify a partitioning
// constraint with supported parent key and reenter.
/
14667, 00000, "Cannot use expressions involving object data types in reference partitioning parent key"
// *Cause: Parent key of the reference partitioned table's
// partitioning constraint contained a virtual column
// that involved an object data type (object, REF, nested
// table, array).
// *Action: Correct the statement to specify a partitioning
// constraint with supported parent key and reenter.
/
14668, 00000, "Cannot drop a unique or primary key referenced by the partitioning constraint of a reference-partitioned table."
// *Cause: An attempt was made to drop a unique or primary key referenced
// by the partitioning constraint of a reference-partitioned table.
// *Action: Drop all reference-partitioned child tables before dropping the
// unique or primary key of the parent table.
/
14669, 00000, "interval partition of reference-partitioned table must correspond to interval partition of the parent table"
// *Cause: An attempt was made to create a reference-partitioned table with
// an interval partiton that does not pair with an interval partition
// in the parent table.
//* Action: Correct the CREATE TABLE statement to specify a correct
// number of partitions.
/
14670, 00000, "there is no usable index on the reference partitioning parent key"
// *Cause: An attempt was made to run an operation on a reference partitioned
// table that requires a usable index on the reference partitioning
// parent key, but no such index exists.
//* Action: Create a usable index on the reference partitioning parent key,
// or rebuild the existing unusable index on the reference
// partitioning parent key.
/
/============================================================================
/ 14690 - 14699 reserved for 32k varchar project
/
/ Begin messages for 32k VARCHAR2, NVARCHAR2, and RAW
/============================================================================
/
14690, 00000, "value too long for MIN or MAX aggregate"
// *Cause: An attempt was made to use a MIN or MAX aggregate with a value
// that was too long.
//* Action: Limit the size of MIN and MAX aggregate inputs to 32763 bytes.
/
14691, 00000, "Extended character types are not allowed in this table."
// *Cause: An attempt was made to create VARCHAR2 or NVARCHAR2 columns
// larger than 4000 bytes, or a RAW column larger than 2000 bytes,
// in a cluster, clustered table or index-organized table.
//* Action: Correct the statement and reenter.
/
14692, 00000, "STORE AS clause is not allowed for extended character type column"
// *Cause: An attempt was made to use the STORE AS clause to specify
// storage attributes for an extended character type column.
//* Action: Correct the statement and reenter.
/
14693, 00000, "The MAX_STRING_SIZE parameter must be EXTENDED."
// *Cause: An attempt was made to set the MAX_STRING_SIZE parameter
// to STANDARD in a database that has been created with,
// or migrated to, the EXTENDED setting.
// *Action: Set MAX_STRING_SIZE to EXTENDED and retry.
/
14694, 00000, "database must in UPGRADE mode to begin MAX_STRING_SIZE migration"
// *Cause: An attempt was made to update the MAX_STRING_SIZE parameter
// to EXTENDED when the database was not in UPGRADE mode.
//* Action: Restart the database in UPGRADE mode, modify the parameter,
// run the utl32k.sql script in $ORACLE_HOME/rdbms/admin, and
// restart the database in normal mode.
/
14695, 00000, "MAX_STRING_SIZE migration is incomplete"
// *Cause: An attempt was made to open the database in normal mode
// before the MAX_STRING_SIZE migration process completed.
//* Action: Restart the database in UPGRADE mode, run the utl32k.sql script
// in $ORACLE_HOME/rdbms/admin, and restart the database in
// normal mode.
/
14696, 00000, "MAX_STRING_SIZE migration is incomplete for pluggable database %s"
// *Cause: An attempt was made to open the database in normal mode
// before the MAX_STRING_SIZE migration process completed
// for the specified pluggable database.
//* Action: Restart the database in UPGRADE mode, run the utl32k.sql script
// in $ORACLE_HOME/rdbms/admin in the specified pluggable database,
// and restart the database in normal mode.
/
14697, 00000, "This connection does not support bind variables larger than 4000 bytes for SQL statements."
// *Cause: An attempt was made to use a bind variable larger than 4000 bytes
// for a SQL statement when the client initially connected to a
// container with STANDARD MAX_STRING_SIZE, and then within the
// same session switched to a container with EXTENDED MAX_STRING_SIZE.
//* Action: Initialize a new connection for the container with EXTENDED
// MAX_STRING_SIZE and retry.
/
14698, 00000, "MAX_STRING_SIZE migration to STANDARD is not allowed due to column %s in object %s.%s."
// *Cause: An attempt was made to use a bind variable larger than 4000 bytes
// for a SQL statement when the client initially connected to a
// container with STANDARD MAX_STRING_SIZE, and then within the
// same session switched to a container with EXTENDED MAX_STRING_SIZE.
//* Action: Initialize a new connection for the container with EXTENDED
// MAX_STRING_SIZE and retry.
/
14699, 00000, "long bind value is too large for column"
// *Cause: An attempt was made to bind a value larger than 4000 bytes
// for insert or update of a VARCHAR2, NVARCHAR2, or RAW column,
// and the value was too large for the destination column.
//* Action: Either make the destination column larger, or reduce the size
// of the bind value.
/
14700, 00000, "Object(s) owned by SYS cannot be locked by non-SYS user"
// *Cause: Attempt to issue a LOCK TABLE statement on SYS owned object(s)
// by a non-SYS user, user should minimally have DML privileges
// *Action: Re-issue LOCK TABLE statement for non-SYS user after granting DML
// privileges on object, or non-SYS user should connect as SYS
//
14701, 00000, "partition-extended name or bind variable must be used for DMLs on tables partitioned by the System method"
// *Cause: User attempted not to use partition-extended syntax
// for a table partitioned by the System method
// *Action: Must use of partition-extended syntax in contexts mentioned above.
14702, 00000, "The partition number is invalid or out-of-range"
// *Cause: Attempted to use nonnumerical value or the number was out of range
// of the partitions.
// *Action: Use a valid partition number.
14703, 00000, "The AFTER clause can be used to ADD PARTITION only to a System Partitioned table."
// *Cause: The table is not partitioned by the System method
// *Action: Skip the AFTER clause.
//
14704, 00000, "Create table as select disallowed for SYSTEM patitioned tables"
// *Cause: User attempted to create a SYSTEM partitioned table by doing a
// create table as select.
// *Action: Do a create table followed by an insert as select into each
// partition.
14705, 00000, "unique or primary keys referenced by enabled foreign keys in table \"%s\".\"%s\""
// *Cause: An attempt was made to truncate a table with unique or
// primary keys referenced by enabled foreign keys in another table.
// *Action: Before performing the TRUNCATE operation on the table, disable
// the foreign key constraints in other tables. You can see what
// constraints exist in a table by issuing the following command:
// SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = :1;
14706, 00000, "multiple child tables reference constraint \"%s\" in table \"%s\".\" %s\""
// *Cause: An ALTER TABLE EXCHANGE [SUB]PARTITION CASCADE command found
// that the specified parent key in the specified table was referenced
// by partitioning constraints in multiple reference partitioned
// child tables.
// *Action: Perform EXCHANGE [SUB]PARTITION without the CASCADE option.
// The CASCADE option is not supported if a parent key in the
// reference partitioned table hierarchy is referened by multiple
// partitioning constraints.
14707, 00000, "no match found for table \"%s\".\" %s\" for EXCHANGE CASCADE"
// *Cause: There was no table matching the specified table in the
// ALTER TABLE EXCHANGE [SUB]PARTITION CASCADE command.
// *Action: Perform EXCHANGE [SUB]PARTITION without the CASCADE option
// or ensure that exactly one table matches the specified table.
14708, 00000, "multiple matches found for table \"%s\".\" %s\" for EXCHANGE CASCADE"
// *Cause: There were multiple tables matching the specified table in the
// ALTER TABLE EXCHANGE [SUB]PARTITION CASCADE command.
// *Action: Perform EXCHANGE [SUB]PARTITION without the CASCADE option
// or ensure that exactly one table matches the specified table.
14709, 00000, "index mismatch for table \"%s\".\"%s\" in ALTER TABLE EXCHANGE [SUB]PARTITION"
// *Cause: An ALTER TABLE EXCHANGE [SUB]PARTITION command was attempted for
// the specified table, however, the exchange table did not have
// equivalent indexes.
// *Action: Ensure that the indexes for the two tables have indexes which
// follow this rule:
// For every nonpartitioned index for the nonpartitioned table,
// there has to be an identical LOCAL index on the partitioned
// table and vice versa. To be identical, the column position type
// and size have to be the same.
14710, 00000, "domain index \"%s\" found for table \"%s\".\"%s\" for EXCHANGE CASCADE"
// *Cause: An ALTER TABLE EXCHANGE [SUB]PARTITION CASCADE command was
// attempted for the specified table. However, there was a domain
// index on the specified table.
// *Action: Perform EXCHANGE [SUB]PARTITION without the CASCADE option
// or ensure that there is no domain index on the specified table.
/============================================================================
/ 14750 - 14799 reserved for interval-partitioning project
/
/ Begin messages for interval-partitioning changes
/============================================================================
14750, 00000, "Range partitioned table with INTERVAL clause has more than one column"
// *Cause: You attempted to create an interval partitioned table with more
// than one partitioning column.
// *Action: Use a single partitioning column.
//
14751, 00000, "Invalid data type for partitioning column of an interval partitioned table"
// *Cause: You attempted to use interval partitioning on a table partitioned
// on a column of data type other than number or date/time.
// *Action: Use only number or date/time columns as partitioning columns for
// interval partitioned tables.
14752, 00000, "Interval expression is not a constant of the correct type"
// *Cause: You attempted to use either a nonconstant interval or an interval
// whose data type does not correspond to the partitioning column
// *Action: Use only constant expressions for the interval. If the data type of
// partitioning column is numeric, the interval must be a numeric
// constant. If the data type is of type date/time, the interval must
// be a constant of interval type
14753, 00000, "Interval cannot be zero"
// *Cause: The interval mapped to zero.
// *Action: You must use a nonzero interval.
14754, 00000, "Interval string is too long"
// *Cause: The interval string was too long
// *Action: Specify interval using a shorter string
14755, 00000, "Invalid partition specification for FOR VALUES clause."
// *Cause: The [SUB]PARTITION FOR VALUES (...) clause can only take constants.
// In addition it takes as many arguments as there are
// partitioning columns and the values must be coercible to the
// partitioning columns.
// *Action: Specify a valid FOR VALUES clause.
14756, 00000, "Table is not partitioned by the interval or by the autolist method."
// *Cause: The table was not partitioned by the interval or by the autolist method.
// *Action: ALTER TABLE SET STORE IN is only valid for interval or autolist
// partitioned tables. Ensure that the table is partitioned by
// an interval or by an autolist method.
14757, 00000, "Table is already a range partitioned table"
// *Cause: SET INTERVAL () is used to convert an interval partitioned table to
// a range partitioned table. It is not legal on a range partitioned
// table
// *Action: Use SET INTERVAL () only on an interval partitioned table.
14758, 00000, "Last partition in the range section cannot be dropped"
// *Cause: An attempt was made to drop the last range partition of an interval
// partitioned table.
// *Action: Do not attempt to drop this partition.
14759, 00000, "SET INTERVAL is not legal on this table."
// *Cause: SET INTERVAL clause was specified. ALTER TABLE SET INTERVAL is
// only legal on a range partitioned table with a single partitioning
// column. Additionally, this table cannot have a MAXVALUE partition.
// *Action: Use SET INTERVAL only on a valid table.
14760, 00000, "ADD PARTITION is not permitted on Interval partitioned objects"
// *Cause: ALTER TABLE ADD PARTITION was attempted on an Interval
// partitioned object.
// *Action: Do not perform the operation on an Interval partitioned object.
// Insert a row to create the new partition.
14761, 00000, "MAXVALUE [sub]partition cannot be specified for INTERVAL [sub]partitioned objects."
// *Cause: An attempt was made to create a [sub]partition with a MAXVALUE highbound
// on an INTERVAL [sub]partitioned object.
// *Action: Do not create a [sub]partition with a MAXVALUE highbound.
14762, 00000, "Domain index creation on interval partitioned tables is not permitted"
// *Cause: An attempt was made to create a domain index on an interval
// partitioned table.
// *Action: Do not create a domain index on an interval partitioned table.
14763, 00000, "Unable to resolve FOR VALUES clause to a partition number"
// *Cause: Could not determine the partition corresponding to the FOR VALUES
// clause.
// *Action: Remove bind variables and dependencies on session parameters
// from the values specified in the FOR VALUES clause.
14764, 00000, "Partitions cannot be truncated, dropped or merged with mixed syntax."
// *Cause: An attempt was made to truncate, drop or merge partitions with mixed syntax.
// *Action: Do not use mixed syntax to truncate, drop or merge partitions.
14765, 00000, "Cannot create a partition while doing a create index"
// *Cause: An attempt was made to create a partition concurrently with index
// creation.
// *Action: Retry the statement after the index build is finished.
14766, 00000, "Unable to obtain a stable metadata snapshot"
// *Cause: This operation was not able to obtain a stable snapshot of the
// interval partitioning metadata.
// *Action: Retry the statement.
14767, 00000, "Cannot specify this interval with existing high bounds"
// *Cause: The interval specified conflicts with the existing high bound for
// the last partition. The combination might lead to invalid dates
// for high bounds in the future.
// *Action: If this is a CREATE TABLE, try specifying a different high bound
// value for the last partition, or a different interval. If this
// is an ALTER TABLE SET INTERVAL, please choose either a different
// interval, or, modify the table to change the high bound for the
// last partition.
14768, 00000, "Error Loading Versioned object"
// *Document: NO
// *Cause: Internal Error. Should never be returned to user
// *Action: If seen by user report to Oracle support.
14769, 00000, "cannot interval [sub]partition or autolist [sub]partition nested table or XMLType with object-relational storage"
// *Cause: Interval [sub] partition or autolist [sub]partition was not supported for nested table and XMLType
// with object-relational storage.
// *Action: Use a list or range partition instead.
14770, 00000, "Cannot use an XML virtual column whose expression uses EXTRACTVALUE operator to interval [sub]partition a table"
// *Cause: Interval [sub]partition is not supported with an XML virtual column
// whose expression include the EXTRACTVALUE operator
// *Action: Use XMLCAST and XMLQUERY operators to define the virtual column
// expression for the partitioning key during interval [sub]partition.
14799, 00000, "Temporary interval error %s, %s"
// *Document: NO
// *Cause: Ignore
// *Action: Ignore
/============================================================================
/ 14800 - 14849 Reserved for composite list/* partitioning
/
/ Begin messages for composite list/* partitioning
/============================================================================
14801, 00000, "Hash composite partitioning is not supported"
// *Cause: An attempt was made to partition a table using a Hash composite
// method.
// *Action: Do not partition the table by a Hash composite method.
14802, 00000, "Specified operation is not permitted on Hash composite partitioned objects"
// *Cause: An unsupported operation was attempted on a Hash composite
// partitioned object.
// *Action: Do not perform the operation on a Hash composite partitioned object.
14803, 00000, "partition bound may not be specified for hash subpartitioned tables"
// *Cause: A VALUES LESS THAN or VALUES clause was specified with a subpartition
// description.
// *Action: Remove the VALUES LESS THAN or VALUES clause from the
// subpartition description.
14804, 00000, "A partition must be split into two or more partitions"
// *Cause: An ALTER TABLE SPLIT PARTITION contained a description for only
// one resulting partition.
// *Action: Specify at least 2 resulting partitions.
14805, 00000, "last resulting partition cannot contain bounds"
// *Cause: An ALTER TABLE SPLIT PARTITION contained a description for the
// last partition which included the bounds.
// *Action: Do not specify bounds for the last resulting partition.
14806, 00000, "merging more than two partitions or subpartitions is only supported for heap tables"
// *Cause: An ALTER TABLE MERGE PARTITIONS or MERGE SUBPARTITIONS with more
// than two source partitions or subpartitions was issued. Merging
// more than two partitions or subpartitions is only supported for
// heap tables.
// *Action: Specify exactly two partitions or subpartitions to merge.
14807, 00000, "merging partitions or subpartitions using <name> TO <name> syntax is only supported for range partitioned tables"
// *Cause: An ALTER TABLE MERGE PARTITIONS <pname> TO <pname> or
// an ALTER TABLE MERGE SUBPARTITIONS <subpname> TO <subpname>
// was issued. This is only supported for range partitions or
// subpartitions.
// *Action: Specify all the partitions or subpartitions to be merged.
14808, 00000, "table does not support %s"
// *Cause: An ALTER TABLE MOVE PARTITION ONLINE or ALTER TABLE MODIFY
// PARTITION INDEXING or ALTER TABLE SPLIT PARTITION ONLINE
// statement was issued on a table that was either
// not a heap-organized table or had an object type, domain index
// or bitmap join index defined on it. Or, the source table of
// the split online has reference partitioned child tables. This
// operation is only supported for heap-organized tables.
// *Action: Do not use the ONLINE keyword or the INDEXING clause.
/
14809, 00000, "schema does not support %s"
// *Cause: An ALTER TABLE MOVE PARTITION ONLINE or an ALTER TABLE MODIFY
// PARTITION INDEXING statement was issued on a table owned by SYS,
// SYSTEM, PUBLIC, OUTLN, or XDB.
// *Action: Do not use the ONLINE keyword or the INDEXING clause.
14810, 00000, "ONLINE MOVE PARTITION not supported while database is not open or in migrate mode"
// *Cause: An ALTER TABLE MOVE PARTITION ONLINE statement was issued on a
// table while the database was not open or was in migrate mode.
// *Action: Do not use the ONLINE keyword.
14811, 00000, "Online DDL with the INCLUDING ROWS clause is not supported under supplemental logging."
// *Cause: An online DDL with an INCLUDING ROWS clause was issued on a table
// while supplemental logging was enabled.
// *Action: Do not use the ONLINE keyword.
14812, 00000, "DBMS_LOB operations not allowed on partition while it is being moved online"
// *Cause: A DBMS_LOB operation was issued on a LOB while an ALTER TABLE MOVE
// PARTITION ONLINE was concurrently executing on the partition
// containing the LOB.
// *Action: Reissue DBMS_LOB operation after MOVE PARTITION ONLINE has
// completed.
14813, 00000, "ONLINE MOVE OR SPLIT PARTITION not supported while there are too many table segments and index segments"
// *Cause: An ALTER TABLE MOVE or SPLIT PARTITION ONLINE command was issued on a
// table while the number of table segments multiplied by the number of index
// segments exceeded the maximum allowed.
// *Action: Do not use the ONLINE keyword.
/============================================================================
/ 14850 - 14869 Reserved for autolist partitioning
/
/ Begin messages for autolist partitioning
/============================================================================
14850, 00000, "Adding a partition with DEFAULT high value is not permitted on Autolist partitioned objects."
// *Cause: An attempt was made to add a DEFAULT partition to an Autolist
// partitioned object.
// *Action: Do not perform the operation on an Autolist partitioned object.
// Insert a row to create the new partition.
14851, 00000, "DEFAULT [sub]partition cannot be specified for AUTOLIST [sub]partitioned objects."
// *Cause: An attempt was made to create a [sub]partition with a DEFAULT high value
// on an AUTOLIST [sub]partitioned object.
// *Action: Do not create a [sub]partition with a DEFAULT high value.
14852, 00000, "SET [SUB]PARTITIONING AUTOMATIC is not legal on this table."
// *Cause: SET [SUB]PARTITIONING AUTOMATIC clause was specified. ALTER TABLE
// SET [SUB]PARTITIONING AUTOMATIC is only legal on a list partitioned
// table. Additionally, this table cannot have a DEFAULT partition.
// *Action: Use SET [SUB]PARTITIONING AUTOMATIC only on a valid table.
14853, 00000, "An invalid option was specified for the SET [SUB]PARTITIONING clause."
// *Cause: SET [SUB]PARTITIONING clause was used with an invalid option.
// The only valid options are AUTOMATIC and MANUAL.
// *Action: Use valid options.
14854, 00000, "SET [SUB]PARTITIONING MANUAL is not legal on this table."
// *Cause: SET [SUB]PARTITIONING MANUAL clause was specified. ALTER TABLE
// SET [SUB]PARTITIONING MANUAL is only legal on a list partitioned
// table. Additionally, this table cannot have a DEFAULT partition.
// *Action: Use SET [SUB]PARTITIONING MANUAL only on a valid table.
14855, 00000, "Table is already a list partitioned table."
// *Cause: An attempt to specify SET [SUB]PARTITIONING MANUAL on a list
// (sub)partitioned table failed. SET [SUB]PARTITIONING MANUAL is
// used to convert an autolist (sub)partitioned table to a list
// (sub)partitioned table.
// *Action: Use SET [SUB]PARTITIONING MANUAL on an autolist (sub)partitioned table.
14856, 00000, "Table is already an autolist partitioned table."
// *Cause: An attempt to specify SET [SUB]PARTITIONING AUTOLIST on an
// autolist (sub)partitioned table failed. SET [SUB]PARTITIONING
// AUTOLIST is used to convert a list (sub)partitioned table to
// an autolist (sub)partitioned table.
// *Action: Use SET [SUB]PARTITIONING AUTOLIST on an autolist (sub)partitioned
// table.
14857, 00000, "Subpartition template is expected when creating an autolist subpartitioned table."
// *Cause: An attempt was made to create an autolist subpartitioned table
// without a subpartition template.
// *Action: Use a subpartition template when creating an autolist subpartitioned
// table.
14858, 00000, "Set empty template is not legal on an autolist subpartitioned table."
// *Cause: An attempt was made to set an empty subpartition template for an
// autolist subpartitioned table.
// *Action: Convert this table to a list subpartitioned table before
// set empty template.
/
/============================================================================
/ 14870 - 14889 Reserved for interval subpartitioning
/
/ Begin messages for interval subpartitioning
/============================================================================
14870, 00000, "Range subpartitioned table with INTERVAL clause has more than one column."
// *Cause: An attempt was made to create an interval subpartitioned table with more
// than one subpartitioning column.
// *Action: Use a single subpartitioning column.
14871, 00000, "Subpartition template is expected when creating an interval subpartitioned table."
// *Cause: An attempt was made to create an interval subpartitioned table
// without a subpartition template.
// *Action: Use a subpartition template when creating an interval subpartitioned
// table.
14872, 00000, "ADD SUBPARTITION is not permitted on interval subpartitioned objects."
// *Cause: ALTER TABLE ADD SUBPARTITION was attempted on an interval
// subpartitioned object.
// *Action: Do not add a subpartition on an interval subpartitioned object.
// Insert a row to create the new subpartition.
14873, 00000, "Set empty template is not legal on an interval subpartitioned table."
// *Cause: An attempt was made to set an empty subpartition template for an
// interval subpartitioned table.
// *Action: Convert this table to a range subpartitioned table before
// set empty template.
/
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
/
/ 14900 - 14949 Reserved for KJAC error messages
/
/
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
14900, 00000, "The logical transaction ID is no longer valid."
// *Cause: The logical transaction ID has been purged and the commit failed.
// *Action: Reconnect and re-run the transaction.
14901, 00000, "Commits during replay are not permitted."
// *Cause: The transaction tried to commit during replay.
// *Action: Contact Oracle Support Services.
14902, 00000, "Instance has not been configured for Transaction Guard."
// *Cause: The partition of the transaction history table had not been created.
// *Action: Contact Oracle Support Services.
14903, 00000, "Corrupt logical transaction detected."
// *Cause: The logical transaction was corrupt. The size was incorrect.
// *Action: Verify your network configuration.
14904, 00000, "Corrupt logical transaction ID detected."
// *Cause: The logical transaction was corrupt. The database ID was incorrect.
// *Action: Verify your network configuration.
14905, 00000, "Serializable transactions cannot be replayed."
// *Cause: The transaction tried to replay a serializable transaction.
// *Action: This is not supported.
14906, 00000, "Get LTXID outcome operation is not permitted on the current session."
// *Cause: The transaction tried to execute get LTXID outcome on the current session.
// *Action: Check the parameters used to invoke get LTXID outcome.
14907, 00000, "Cannot execute get LTXID outcome for the transaction of another user."
// *Cause: The transaction tried to execute get LTXID outcome for a different user
// session.
// *Action: Check the parameters used to invoke get LTXID outcome.
14908, 00000, "Cannot invoke get LTXID outcome while a transaction is open."
// *Cause: Get LTXID outcome could not be executed because a transaction was open.
// *Action: Invoke get LTXID outcome after the transaction has been completed.
14909, 00000, "Current session has been blocked by another user with the same user name using GET_LTXID_OUTCOME."
// *Cause: Could not commit after GET_LTXID_OUTCOME was invoked.
// *Action: Contact Oracle Support Services.
14910, 00000, "Sessions with SYSDBA privilege are not allowed to connect to a service that has commit outcome enabled."
// *Cause: A session with SYSDBA privilege tried to connect to a service that has
// commit outcome enabled.
// *Action: Connect without the SYSDBA privilege.
14913, 00000, "Invalid logical transaction ID detected."
// *Cause: The logical transaction was marked invalid.
// *Action: Verify your configuration. Transaction Guard does not support XA transactions that use the two-phase commit protocol.
14914, 00000, "cannot invoke set failpoint"
// *Cause: An invalid parameter was specified.
// *Action: Specify a valid parameter.
14915, 00000, "cannot invoke set failpoint"
// *Cause: An invalid database session was specified.
// *Action: Specify a valid database session.
14916, 00000, "Switch service by DRCP clients is not supported by Transaction Guard."
// *Cause: The Database Resident Connection Pooling (DRCP) client tried to
// switch services while Transaction Guard was enabled.
// *Action: None.
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
/
/ 14950 - 14999 Reserved for KJAC PL/SQL error messages
/
/
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
14950, 0000, "Force outcome failed. Client transaction is too old."
// *Document : Yes
// *Cause : The client transaction had been commited or forced earlier.
// *Action : None
14951, 0000, "Force outcome failed. Client transaction is ahead of server logical transaction ID."
// *Document : Yes
// *Cause : The client transaction had not been seen by the server and
// could not be forced. This can happen if the server is restored
// or a flashback operation has been executed.
// *Action : None
14952, 0000, "Force outcome failed. General error occurred."
// *Document : Yes
// *Cause : The force outcome operation failed. See previous error
// for the reason.
// *Action : None
14953, 0000, "Invalid partition ID specified."
// *Document : Yes
// *Cause : The partition IDs of the transaction history table were not
// consecutive.
// *Action : Specify the next higer partition ID.
14954, 0000, "Invalid tablespace name specified."
// *Document : Yes
// *Cause : The tablespace did not exist.
// *Action : Specify an existing tablespace.
/============================================================================
/ 15000 - 15499 Reserved for Automatic Storage Management
/ 59000 - 59999 Reserved for Automatic Storage Management (e57000.msg)
/
/ Begin messages for Automatic Storage Management
/============================================================================
/
/============================================================================
/ 15000 - 15099 Used for ASM run-time errors
/============================================================================
/
15000, 00000, "command disallowed by current instance type"
// *Cause: The user has issued a command to a conventional RDBMS instance
// that is only appropriate for an ASM instance. Alternatively, the
// user has issued a command to an ASM instance that is only
// appropriate for an RDBMS instance.
// *Action: Connect to the correct instance type and re-issue the command.
//
15001, 00000, "diskgroup \"%s\" does not exist or is not mounted"
// *Cause: An operation failed because the diskgroup specified does not
// exist or is not mounted by the current ASM instance.
// *Action: Verify that the diskgroup name used is valid, that the
// diskgroup exists, and that the diskgroup is mounted by
// the current ASM instance.
//
15002, 00000, "parameter LOCK_NAME_SPACE exceeds limit of %s characters"
// *Cause: The LOCK_NAME_SPACE initialization parameter contained a
// value that is too long.
// *Action: Correct the LOCK_NAME_SPACE initialization parameter.
//
15003, 00000, "diskgroup \"%s\" already mounted in another lock name space"
// *Cause: The diskgroup could not be mounted by the ASM instance because
// it was operating in a lockspace different than another existing
// ASM instance which had already mounted the diskgroup.
// *Action: Check the LOCK_NAME_SPACE initialization parameter value, or
// dismount the diskgroup from the other ASM instances.
//
15004, 00000, "alias \"%s\" does not exist"
// *Cause: The specified alias did not exist within the diskgroup.
// *Action: Check the alias name and diskgroup name.
//
15005, 00000, "name \"%s\" is already used by an existing alias"
// *Cause: An existing alias in the diskgroup used the same name.
// *Action: Select another alias name, or drop the existing alias.
//
15006, 00000, "template \"%s\" does not exist"
// *Cause: The specified template did not exist within the diskgroup.
// *Action: Check the template name and diskgroup name.
//
15007, 00000, "name is already used by an existing template"
// *Cause: A template with the same name already exists.
// *Action: Select another template name, or drop the existing template.
//
15008, 00000, "cannot drop system template"
// *Cause: The specified template was created by the system and must
// always exist for proper operation.
// *Action: Select another template name.
//
15009, 00000, "ASM disk \"%s\" does not exist"
// *Cause: The specified ASM disk was not found.
// *Action: Check the ASM disk name.
//
15010, 00000, "name '%s' is already used by an existing ASM disk"
// *Cause: The specified name was already used in this diskgroup.
// *Action: Specify a different ASM disk name.
//
15011, 00000, "failure group \"%s\" does not exist in diskgroup \"%s\""
// *Cause: The specified name did not match the failure group of any
// disks in the diskgroup. This usually indicates that the failure
// group name was specified incorrectly.
// *Action: Check the failure group name.
//
15012, 00000, "ASM file '%s' does not exist"
// *Cause: The ASM file was not found.
// *Action: Check the ASM file name.
//
15013, 00000, "diskgroup \"%s\" is already mounted"
// *Cause: An ALTER DISKGROUP MOUNT command specified the name of a diskgroup
// which is already mounted by the current ASM instance.
// *Action: Check the name of the diskgroup.
//
15014, 00000, "path '%s' is not in the discovery set"
// *Cause: The operating system path specified was outside the set of disks
// that are discovered by the instance.
// *Action: Specify a operating system path within the set of disks that are
// discovered based upon the ASM_DISKSTRING parameter. Alternatively,
// check the setting of the ASM_DISKSTRING parameter.
//
15015, 00000, "Specified path '%s' conflicts with path '%s'"
// *Cause: The ASM instance previously discovered specified disk with an ASM
// library using a different path.
// *Action: Use the discovery string of the ASM library to add the disk.
//
15016, 00000, "inconsistent respecification of path '%s'"
// *Cause: The specified path was provided more than once with different
// properties.
// *Action: Do not provide a path more than once. Alternatively, provide
// consistent properties.
//
15017, 00000, "diskgroup \"%s\" cannot be mounted"
// *Cause: The disk group could not be mounted by the ASM instance either
// of an IO error or due to other reasons explained in alert log or
// trace files.
// *Action: Check for additional errors reported. Correct the error and
// retry the operation.
//
15018, 00000, "diskgroup cannot be created"
// *Cause: The specified diskgroup could not be created.
// *Action: Check for additional errors reported.
//
15019, 00000, "discovered duplicate path '%s' for '%s'"
// *Cause: The discovery encountered multiple paths to the same disk.
// *Action: Check that the ASM_DISKSTRING parameter specifies only a
// single path for each disk.
//
15020, 00000, "discovered duplicate ASM disk \"%s\""
// *Cause: The discovery encountered two disks claiming to be the same
// named ASM disk.
// *Action: Check that the ASM_DISKSTRING parameter specifies only a
// single path for each disk.
//
15021, 00000, "parameter \"%s\" is not valid in %s instance"
// *Cause: The specified parameter was not supported when starting an
// instance of this type.
// *Action: Delete the specified parameter from the INIT.ORA file.
//
15022, 00000, "unable to load an Oracle ASM library"
// *Cause: An Oracle instance attempted to load an Oracle ASM library
// which could not be discovered.
// *Action: Check other error messages to determine why Oracle is unable
// to retrieve the library path from the Oracle ASM instance.
//
15023, 00000, "reached maximum allowable number of disks %s"
// *Cause: An attempt was made to add another disk to a diskgroup
// which already contains the maximum number of disks allowed.
// *Action: Consider dropping existing disks from the diskgroup before
// adding additional ones, or create a new diskgroup.
//
15024, 00000, "discovered duplicately numbered ASM disk %s"
// *Cause: ASM discovered two disks claiming to have the same
// ASM disk number in the same disk group.
// *Action: Check that the ASM_DISKSTRING parameter specifies only a
// single path for each disk.
//
15025, 00000, "could not open disk \"%s\""
// *Cause: The specified disk could not be opened. If the database instance
// is running as an Operating System (OS) user different from that
// of the ASM instance, then the permissions on the database oracle
// binary may be incorrect.
// *Action: Check the additional error messages, if any. If the database
// instance is running as an OS user different from that of the
// ASM instance, use the "srvctl" command to stop and restart
// the database to fix the permissions.
//
15026, 00000, "disk '%s' is not an ASM disk"
// *Cause: The disk did not contain a valid ASM disk header.
// *Action: Check to see if the data on the disk has been changed
// by some system administrator action.
//
15027, 00000, "active use of diskgroup \"%s\" precludes its dismount"
// *Cause: An ALTER DISKGROUP ... DISMOUNT command specified a diskgroup
// which had clients with open files in the diskgroup. Diskgroups
// cannot be dismounted until all open files in the diskgroup
// are closed.
// *Action: Stop all clients that are using this diskgroup and retry
// the ALTER DISKGROUP ... DISMOUNT command. Query the V$ASM_CLIENT
// fixed view in an ASM instance or use ASMCMD LSOF to list active
// clients.
//
15028, 00000, "ASM file '%s' not dropped; currently being accessed"
// *Cause: An attempt was made to drop an ASM file, but the file was
// being accessed by one or more clients and therefore could
// not be dropped.
// *Action: Stop all clients that are using this file and retry the drop
// command. Query the V$ASM_CLIENT fixed view in an ASM instance
// or use ASMCMD LSOF to list active clients.
//
15029, 00000, "disk '%s' is already mounted by this instance"
// *Cause: An attempt was made to add to a diskgroup a disk that
// was already mounted by the current instance as part of
// some (possibly other) diskgroup.
// *Action: Specify a different disk in the command. Note that not
// even the FORCE option can be used to correct the situation
// until the diskgroup containing the disk becomes dismounted
// by this instance.
//
15030, 00000, "diskgroup name \"%s\" is in use by another diskgroup"
// *Cause: A CREATE DISKGROUP command specfied a diskgroup name that
// was already assigned to another diskgroup.
// *Action: Select a different name for the diskgroup.
//
15031, 00000, "disk specification '%s' matches no disks"
// *Cause: The instance was unable to discover any disks in the mentioned
// device specification path.
// *Action: Ensure that device specification string matches a disk on the
// system.
//
15032, 00000, "not all alterations performed"
// *Cause: At least one ALTER DISKGROUP action failed.
// *Action: Check the other messages issued along with this summary error.
//
15033, 00000, "disk '%s' belongs to diskgroup \"%s\""
// *Cause: An attempt was made to ADD to a diskgroup (or REPLACE with) a disk
// that was already part of another diskgroup, or an attempt was made
// to DROP / OFFLINE / ONLINE / CHECK a disk that was not part of
// the specified diskgroup.
// *Action: For ADD and REPLACE, check the path specifier for the disk. If it
// is certain that the disk is not in use by another diskgroup, the
// FORCE option may be used to override this check. For the other
// commands, check the name of the specified disk.
//
15034, 00000, "disk '%s' does not require the FORCE option"
// *Cause: An attempt was made to add the disk to the diskgroup using
// the FORCE option. The disk was not found to be in use at the
// present time, so the FORCE option was not permitted.
// *Action: Avoid gratuitous use of the FORCE option.
//
15035, 00000, "no disks belong to diskgroup \"%s\""
// *Cause: An attempt was made to mount a diskgroup for which no
// member disks were discovered.
// *Action: Specify a valid diskgroup name that contains disks.
//
15036, 00000, "Disk '%s' is truncated to %s MB from %s MB."
// *Cause: The size of the disk, as reported by the operating
// system, was smaller than the size of the disk as recorded in
// the disk header block on the disk.
// *Action: Check if the system configuration has changed.
//
15037, 00000, "disk '%s' size %s MB is smaller than minimum of %s MB"
// *Cause: The size of the disk, as reported by the operating
// system, was too small to allow the disk to become part of
// the diskgroup.
// *Action: Check if the system configuration is correct.
//
15038, 00000, "disk '%s' mismatch on '%s' with target disk group [%s] [%s]"
// *Cause: An attempt was made to mount into a disk group a disk whose
// recorded allocation unit size, metadata block size, physical
// sector size, logical sector size or creation time stamp was
// inconsistent with the other disk group members.
// *Action: Check if the system configuration has changed. Verify disk
// discovery string.
//
15039, 00000, "diskgroup not dropped"
// *Cause: An attempt to drop a diskgroup failed.
// *Action: See the associated messages for details about why the drop
// was not successful.
//
15040, 00000, "diskgroup is incomplete"
// *Cause: Some of the disks comprising a diskgroup were not present.
// *Action: Check the hardware to ensure that all disks are functional. Also
// check that the setting of the ASM_DISKSTRING initialization
// parameter has not changed. Alternatively, for normal or high
// redundancy diskgroups, use MOUNT FORCE to offline missing disks
// as part of mounting the diskgroup.
//
15041, 00000, "diskgroup \"%s\" space exhausted"
// *Cause: At least one disk in the diskgroup is out of space.
// *Action: If all disks are evenly balanced, add more disks to the diskgroup,
/ or delete some existing files.
// Alternatively, one or more disks in the diskgroup are out of
// space. If diskgroup is imbalanced, run rebalance to completion.
//
15042, 00000, "ASM disk \"%s\" is missing from group number \"%s\" "
// *Cause: The specified disk, which is a necessary part of a diskgroup,
// could not be found on the system.
// *Action: Check the hardware configuration.
//
15043, 00000, "ASM disk \"%s\" is not a diskgroup member"
// *Cause: The specified disk has been removed from the diskgroup, but
// a disk matching its name was found.
// *Action: Check the hardware configuration.
//
15044, 00000, "ASM disk '%s' is incorrectly named"
// *Cause: Either the specified disk had its contents changed such that
// it no longer contained an ASM disk name in its header that matches
// the diskgroup information or its FAILGROUP information
// may have become inconsistent.
// *Action: Drop the disk from the diskgroup.
//
15045, 00000, "ASM file name '%s' is not in reference form"
// *Cause: The ASM file name was not in a form that can be used to reference
// an existing file because a file/incarnation number or an
// alias name was not present or a template name was included.
// *Action: Correct the specified ASM file name.
//
15046, 00000, "ASM file name '%s' is not in single-file creation form"
// *Cause: The ASM file name was not in a form that can be used to create
// an single file because a file/incarnation number was present.
// *Action: Correct the specified ASM file name.
//
15047, 00000, "ASM file name '%s' is not in multiple-file creation form"
// *Cause: The ASM file name was not in a form that can be used to create
// multiple files because either a fully-qualified file name or an
// alias name was present.
// *Action: Correct the specified ASM file name.
//
15048, 00000, "ASM internal files cannot be deleted"
// *Cause: An attempt was made to delete a metadata file used by ASM
// to manage the diskgroup.
// *Action: Check the specified ASM file name.
//
15049, 00000, "diskgroup \"%s\" contains %s error(s)"
// *Cause: Errors were discovered by the ALTER DISKGROUP CHECK command.
// *Action: See the alert log for details of the errors.
//
15050, 00000, "disk \"%s\" contains %s error(s)"
// *Cause: Errors were discovered by the ALTER DISKGROUP CHECK DISK command.
// *Action: See the alert log for details of the errors.
//
15051, 00000, "file '%s' contains %s error(s)"
// *Cause: Errors were discovered by the ALTER DISKGROUP CHECK FILE command.
// *Action: See the alert log for details of the errors.
//
15052, 00000, "ASM file name '%s' is not in diskgroup \"%s\""
// *Cause: The ASM file name did not contain a diskgroup name that specified
// the correct diskgroup as implied by the other arguments to
// the command.
// *Action: Correct the specified ASM file name or diskgroup name.
//
15053, 00000, "diskgroup \"%s\" contains existing files"
// *Cause: An attempt was made to drop a diskgroup that still contains
// existing files.
// *Action: Specify the INCLUDING CONTENTS option to drop the diskgroup
// and all of its existing files.
//
15054, 00000, "disk \"%s\" does not exist in diskgroup \"%s\""
// *Cause: An attempt was made to alter a disk that is not part of
// the specified diskgroup.
// *Action: Check the name of the specified disk and the specified
// diskgroup.
//
15055, 00000, "unable to connect to ASM instance"
// *Cause: The relational database management system (RDBMS) instance was
// unable to connect to the required ASM instance when accessing a
// disk group.
// *Action: Check the additional error messages. Configure the correct ASM
// system identifier (SID) or ensure that the RDBMS instance has
// operating system privileges for ASM SYSDBA.
//
15056, 00000, "additional error message"
// *Cause: An operating system error occured.
// *Action: Correct the operating system error and retry the operation.
//
15057, 00000, "specified size of %s MB is larger than actual size of %s MB"
// *Cause: A disk size expression exceeded the amount of storage actually
// available, as reported by the operating system.
// *Action: Specify a valid size.
//
15058, 00000, "disk '%s' belongs to an incompatible diskgroup"
// *Cause: An attempt was made to ADD to a diskgroup a disk which was
// already part of another diskgroup. The other diskgroup was
// written by a more recent software release.
// *Action: Check the path specifier for the disk. If it is certain that
// the disk is not in use by another diskgroup, the FORCE option
// may be used to override this check.
//
15059, 00000, "invalid device type for ASM disk"
// *Cause: The device type of the discovered disk was not valid for use as
// an ASM disk.
// *Action: Check the file path and retry or exclude it from the discovery
// set. See the accompanying operating system error for additional
// information.
//
15060, 00000, "template \"%s\" does not exist"
// *Cause: A command specified a template name, either directly or
// as part of an ASM file name, which did not exist.
// *Action: Check the template specifier in the command.
//
15061, 00000, "ASM operation not supported [%s]"
// *Cause: An ASM operation was attempted that is invalid or not supported
// by this version of the ASM instance.
// *Action: This is an internal error code that is used for maintaining
// compatibility between software versions and should never be
// visible to the user; contact Oracle support Services.
//
15062, 00000, "ASM disk is globally closed"
// *Cause: The disk to which the I/O request was issued has gone offline or
// has been globally closed by the background process. Check other
// messages in the trace files for more information.
// *Action: Bring the disk online for I/Os to get through.
//
15063, 00000, "ASM discovered an insufficient number of disks for diskgroup \"%s\""
// *Cause: ASM was unable to find a sufficient number of disks belonging to the
// diskgroup to continue the operation.
// *Action: Check that the disks in the diskgroup are present and functioning,
// that the owner of the ORACLE binary has read/write permission to
// the disks, and that the ASM_DISKSTRING initialization parameter
// has been set correctly. Verify that ASM discovers the appropriate
// disks by querying V$ASM_DISK from the ASM instance.
//
15064, 00000, "communication failure with ASM instance"
// *Cause: There was a failure to communicate with the ASM instance, most
// likely because the connection went down.
// *Action: Check the accompanying error messages for more information on the
// reason for the failure. Note that database instances will always
// return this error when the ASM instance is terminated abnormally.
//
15065, 00000, "hash collision for diskgroup names '%s' and '%s'"
// *Cause: There was a collision in the group name used for the diskgroup.
// The diskgroup(s) cannot be mounted using colliding names.
// *Action: Use a different diskgroup name and also report to Oracle Support
// Services the two diskgroup names which collided.
//
15066, 00000, "offlining disk \"%s\" in group \"%s\" may result in a data loss"
// *Cause: Following I/O failures, the disks holding all copies of a data
// block were attempted to be taken offline.
// *Action: Check the accompanying error messages for more information on the
// reason for the disk I/O failures.
//
15067, 00000, "command or option incompatible with diskgroup redundancy"
// *Cause: An attempt was made to use a feature which is not
// permitted by the diskgroup's redundancy policy. Common examples
// are forcibly dropping a disk from an EXTERNAL REDUNDANCY diskgroup,
// using the FAILGROUP clause with an EXTERNAL REDUNDANCY diskgroup,
// using invalid template attributes, or mounting a HIGH or
// EXTERNAL redundancy diskgroup for recovery.
// *Action: Omit the option from the command.
//
15068, 00000, "maximum number of diskgroups %s already mounted"
// *Cause: An attempt was made to mount more diskgroups than the
// instance is capable of mounting at one time.
// *Action: Dismount a mounted diskgroup and retry the command.
//
15069, 00000, "ASM file '%s' not accessible; timed out waiting for lock"
// *Cause: An attempt was made to access an ASM file, but the file is
// currently being created, resized, or deleted and therefore
// cannot be accessed.
// *Action: No action required, or try again later, after the create or
// resize has completed.
//
15070, 00000, "maximum number of files %s exceeded in diskgroup \"%s\""
// *Cause: The diskgroup ran out of space.
// *Action: Delete some existing ASM files or create files in a new diskgroup.
//
15071, 00000, "ASM disk \"%s\" is already being dropped"
// *Cause: An attempt was made to drop or replace a disk that was already
// in the process of being dropped from the diskgroup. Alternatively,
// an attempt was made to forcibly drop a disk from a diskgroup using
// the FORCE option that was already being forcibly dropped from
// the diskgroup.
// *Action: Check the ASM disk name and FORCE option as specified in
// the command.
//
15072, 00000, "command requires at least %s regular failure groups, discovered only %s"
// *Cause: An attempt was made to create either a normal redundancy diskgroup
// for which fewer than two regular failure groups were both specified
// and discovered, or a high redundancy diskgroup for which fewer than
// three regular failure groups were both specified and discovered, or
// an external redundancy diskgroup for which only quorum disks were
// both specified and discovered.
// *Action: Check the that the command does specify the required number of
// failure groups, and that all of the specified disks are discovered
// by ASM. A query of the V$ASM_DISK fixed view will show which disks
// are discovered by ASM. Note that a quorum failure group will not be
// used as a regular failure group. An external redundancy diskgroup
// requires at least one regular disk.
//
15073, 00000, "diskgroup %s is mounted by another ASM instance"
// *Cause: An attempt was made to drop a diskgroup that is still
// mounted somewhere in the cluster by another instance.
// *Action: dismount the diskgroup from all nodes except the one
// performing the drop diskgroup command.
//
15074, 00000, "diskgroup %s requires rebalance completion"
// *Cause: An attempt was made to repeatedly add or drop disks from a
// diskgroup. ASM could not perform the operation given the
// current state of the diskgroup.
// *Action: Manually invoke the ALTER DISKGROUP REBALANCE command and allow
// the rebalance to run to completion. Alternatively, invoke the
// ALTER DISKGROUP UNDROP DISKS command and allow the rebalance to
// run to completion. After the rebalance has completed, retry the
// operation.
//
15075, 00000, "disk %s is not visible on instance number %s"
// *Cause: An ALTER DISKGROUP ADD DISK command specified a disk that could
// not be discovered.
// *Action: Check operating system permissions for the device and the
// storage subsystem configuration on the specified node.
//
15076, 00000, "Emulating I/O errors on the OSM disk"
// *Cause: The disk to which the I/O request was issued is in an error
// emulation mode.
// *Action: Bring the disk online for I/Os to get through.
//
15077, 00000, "could not locate ASM instance serving a required diskgroup"
// *Cause: The instance failed to perform the specified operation because it
// could not locate a required ASM instance.
// *Action: If you want to start a database instance, start an ASM instance
// and mount the required diskgroup. If you want to start an ASM
// instance, relink the ORACLE binary with ASM_ON or explicitly set
// INSTANCE_TYPE initialization parameter to ASM.
//
/ This legacy error message should not be used any more; use 15118 instead
/ in the future.
15078, 00000, "ASM diskgroup was forcibly dismounted"
// *Cause: The diskgroup to which the I/O request was issued was forcibly
// dismounted (with the ALTER DISKGROUP DISMOUNT FORCE command) so
// that it could not be accessed.
// *Action: Mount the diskgroup to allow access again.
//
15079, 00000, "ASM file is closed"
// *Cause: The file to which the I/O request was issued was closed. This
// could have been a consequence of the disk group being dismounted.
// *Action: Ensure that the disk group is mounted and the file is open.
//
15080, 00000, "synchronous I/O operation failed to %s block %s of disk %s in disk group %s"
// *Cause: A synchronous I/O operation invoked on a disk has failed.
// *Action: Ensure that all of the disks are operational.
//
15081, 00000, "failed to submit an I/O operation to a disk"
// *Cause: Submission of an I/O operation to a disk has failed.
// *Action: Ensure that all of the disks are operational.
//
15082, 00000, "ASM failed to communicate with client"
// *Cause: There was a failure or time out when ASM tried to communicate with
// a connected RDBMS or Oracle ASM Dynamic Volume Manager
// (Oracle ADVM) client.
// *Action: Check the accompanying error messages and alert logs
// for more information on the reason for the failure.
// Check system specific logs (/var/log/messages on Linux,
// Event Log on Windows) for Oracle ADVM messages.
//
15083, 00000, "failed to communicate with ASMB background process"
// *Cause: A database instance failed to communicate with its ASMB background
// process when attempting to access an ASM file.
// *Action: Check the alert log for more information on the reason for the
// failure.
//
15084, 00000, "ASM disk \"%s\" is offline and cannot be dropped."
// *Cause: An attempt was made to drop a disk that is offline.
// *Action: Check the ASM disk name as specified in the command; or,
// if needed, use the DROP DISK FORCE option.
//
15085, 00000, "disk \"%s\" has inconsistent sector size (expected %s, actual %s) with disk group \"%s\""
// *Cause: An attempt to mount a disk group failed because a disk reported an
// inconsistent sector size value.
// *Action: Use disks with a sector size consistent with disk group sector
// size, or ensure that the operating system can accurately report the
// disk sector size.
//
15086, 00000, "Diskgroup sector size must be specified."
// *Cause: The _disk_sector_size_override parameter was used but the
// sector disk value was not specified in the command.
// *Action: Specify the sector size value, or do not set (or do not set to
// TRUE) the _disk_sector_size_override parameter.
//
15087, 00000, "disk '%s' is formatted as an ext2/ext3 or OCFS2 file system."
// *Cause: A signature was found on the specified disk indicating that
// it is in use by an existing ext2/ext3 or OCFS2 file system.
// *Action: Adjust discovery string and device permissions to exclude
// previously formatted disks from discovery.
//
15088, 00000, "diskgroup creation incomplete"
// *Cause: A previous failure during diskgroup creation left the diskgroup
// in an inconsistent state.
// *Action: Issue DROP DISKGROUP ... FORCE INCLUDING CONTENTS to clean up
// the failed creation, then re-create the diskgroup.
//
15089, 00000, "Extent %s of ASM file %s cannot be relocated"
// *Document: NO
// *Cause: The specified extent could not be relocated because of a disk online
// that was in progress.
// *Action: No action needs to be taken. This error is caught by ASM and handled
// internally.
//
15090, 00000, "handle %s is not a valid descriptor"
// *Cause: The file handle was not valid in this session.
// *Action: Submit a handle obtained from a successful call to
// DBMS_DISKGROUP.OPEN().
//
15091, 00000, "operation incompatible with open handle in this session"
// *Cause: The current session contained an open handle from the
// DBMS_DISKGROUP PL/SQL package which precluded performing
// the command.
// *Action: Execute the command in a different session.
//
15092, 00000, "I/O request size %s is not a multiple of logical block size %s"
// *Cause: The length of the request was not a multiple of logical block size.
// *Action: Correct the error and retry the operation.
//
15093, 00000, "buffer only contains %s bytes, I/O requested is %s bytes"
// *Cause: The buffer supplied for write was too small to satisfy the request.
// *Action: Correct the error and retry the operation.
//
15094, 00000, "attempted to write to file opened in read only mode"
// *Cause: The file handle passed to DBMS_DISKGROUP.WRITE() did not have
// write privileges.
// *Action: Obtain a file handle in read-write mode and retry the write
// operation.
//
15095, 00000, "reached maximum ASM file size (%s GB) for this disk group\n"
// *Cause: An ASM file creation or file resize operation exceeded the
// maximum file size permitted by ASM for this disk group.
// *Action: Use smaller files. Alternatively, set the disk group attribute
// compatible.rdbms >= 11.1 if not set already.
//
15096, 0000, "lost disk write detected"
// *Cause: A failure either by disk hardware or disk software caused a disk
// write to to be lost, even though ASM received acknowledgement that
// the write completed. Alternatively, a clustering hardware failure
// or a clustering software failure resulted in an ASM instance
// believing that another ASM instance had crashed, when in fact it
// was still active.
// *Action: The disk group is corrupt and cannot be recovered. The disk group
// must be recreated, and its contents restored from backups.
//
15097, 00000, "cannot SHUTDOWN ASM instance with connected client (process %s)"
// *Cause: A SHUTDOWN command was issued to an ASM instance that had one or
// more connected clients.
// *Action: Stop all clients that are using this ASM instance and retry the
// SHUTDOWN command. Alternatively, use the SHUTDOWN ABORT command.
// Note that issuing the SHUTDOWN ABORT command to an ASM instance
// results in abormal termination of all RDBMS instances connected
// to that ASM instance. One of the active clients has been listed
// in the error message. Query the V$ASM_CLIENT fixed view in an
// ASM instance or use ASMCMD LSCT to list all active clients.
//
15098, 00000, "file type not recognized by ASM instance"
// *Cause: An attempt was made by DB instance to create a file for a file
// type that is not recognized by current version of ASM instance.
// *Action: Upgrade ASM to higher version that recognizes this file type.
//
15099, 00000, "disk '%s' is larger than maximum size of %s MBs"
// *Cause: The specified size of the disk was too big to allow the
// disk to become part of the diskgroup.
// *Action: Specify a smaller disk size than the maximum allowed size.
// Alternatively, set the compatible.rdbms attribute of the disk group
// to a value greater than or equal to 12.1 to allow for larger
// disk sizes.
//
/
/============================================================================
/ 15100 - 15179 Used for ASM SQL usage errors
/============================================================================
/
15100, 00000, "invalid or missing disk group name"
// *Cause: The command did not specify a valid disk group name. Disk group
// names should start with a letter, and can only contain alphanumeric
// characters and the underscore character.
// *Action: Specify a valid disk group name.
//
15101, 00000, "no action specified"
// *Cause: The ALTER DISKGROUP command did not specify any alterations.
// *Action: Specify at least one operation clause.
//
15102, 00000, "invalid POWER expression"
// *Cause: The syntax of the POWER expression was invalid.
// *Action: Specify a valid POWER expression.
//
15103, 00000, "conflicting or duplicate REPAIR options"
// *Cause: The command specified conflicting or duplicate REPAIR keywords.
// *Action: Specify only one REPAIR action.
//
15104, 00000, "conflicting CONTENTS options"
// *Cause: The command specified conflicting or duplicate INCLUDING CONTENTS
// or EXCLUDING CONTENTS options.
// *Action: Specify only one option.
//
15105, 00000, "missing or invalid FAILGROUP name"
// *Cause: The command did not specify a valid failure group name.
// *Action: Specify a valid failure group name.
//
15106, 00000, "missing or invalid operating system disk locator string"
// *Cause: The command did not specify a valid operating system path
// for the device as a string.
// *Action: Specify a valid operating system path for the device.
//
15107, 00000, "missing or invalid ASM disk name"
// *Cause: The command did not specify a valid ASM disk name identifier.
// *Action: Specify a valid ASM disk name identifier.
//
15108, 00000, "missing or invalid template name"
// *Cause: The command did not specify a valid template name identifier.
// *Action: Specify a valid template name identifier.
//
15109, 00000, "conflicting protection attributes specified"
// *Cause: The command contained an invalid combination of the UNPROTECTED,
// MIRROR, or PARITY keywords.
// *Action: Specify only one keyword.
//
15110, 00000, "no diskgroups mounted"
// *Cause: No diskgroups were specified in the ASM_DISKGROUPS parameter, so
// instance startup or the ALTER DISKGROUP ALL MOUNT command did not
// mount any diskgroups.
// *Action: Specify valid diskgroups in the ASM_DISKGROUPS parameter or ignore
// the error.
//
15111, 00000, "conflicting or duplicate STRIPE options"
// *Cause: The command contained both a FINE and COARSE keyword, or
// contained the FINE keyword more than once, or contained the
// COARSE keyword more than once.
// *Action: Specify only one keyword.
//
15112, 00000, "no diskgroups currently mounted"
// *Cause: An ALTER DISKGROUP ALL command did not find any mounted diskgroups
// upon which to operate. Either instance shutdown or an ALTER
// DISKGROUP ALL DISMOUNT command did not dismount any diskgroups,
// or an ALTER DISKGROUP ALL UNDROP DISKS command did not undrop
// any disks.
// *Action: Mount the diskgroups on which you wish to operate or ignore
// the error.
//
15113, 00000, "alias name '%s' refers to a directory"
// *Cause: The name specified referred to a directory in the alias directory
// and not a valid alias entry.
// *Action: Check the alias name and retry.
//
15114, 00000, "missing or invalid ASM file name"
// *Cause: The command did not specify a valid ASM file name identifier.
// *Action: Specify a valid ASM file name identifier.
//
15115, 00000, "missing or invalid ASM disk size specifier"
// *Cause: The command did not specify a valid ASM disk size.
// *Action: Specify a valid ASM disk size.
//
15116, 00000, "invalid combination of ALTER DISKGROUP options"
// *Cause: The ALTER DISKGROUP options may not be combined in this manner.
// *Action: Issue separate ALTER DISKGROUP commands to accomplish the
// desired action.
//
15117, 00000, "command only operates on one diskgroup"
// *Cause: An ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP command
// specified a list of diskgroups or the keyword ALL in a context
// where only a single diskgroup was permitted.
// *Action: Issue separate ALTER DISKGROUP, CREATE DISKGROUP, or DROP
// DISKGROUP commands to accomplish the desired action.
//
15118, 00000, "ASM diskgroup '%s' was forcibly dismounted."
// *Cause: The diskgroup to which the I/O request was issued was forcibly
// dismounted (with the ALTER DISKGROUP DISMOUNT FORCE command)
// so that it could not be accessed.
// *Action: Mount the diskgroup to allow access again.
//
15119, 00000, "too many disk groups (%s); maximum allowed %s"
// *Cause: An attempt was made to mount more than the maximum allowed number
// of disk groups.
// *Action: Do not attempt to mount more than the maximum allowed number of
// disk groups. Check ASM instance parameters.
//
15120, 00000, "ASM file name '%s' does not begin with the ASM prefix character"
// *Cause: A file name was specified to ASM which did not begin with the
// ASM prefix character (currently '+'). ASM uses the prefix to
// determine that a file specification is in fact an ASM file.
// *Action: Correct the file name specification.
//
15121, 00000, "ASM file name '%s' contains an invalid diskgroup name"
// *Cause: A file name was specified that did not contain a valid
// diskgroup name. The diskgroup name follows immediately after
// the ASM prefix character. It must start with an alphabetic
// character, and consist of up to 30 characters which are
// alphabetic, numeric, or the characters '$' and '_'.
// *Action: Correct the file name specification.
//
15122, 00000, "ASM file name '%s' contains an invalid file number"
// *Cause: A numeric file name was specified which did not contain a
// valid ASM file number. The ASM file number follows immediately
// after the diskgroup name. It must be preceeded by a '.' character,
// and contain only numeric characters.
// *Action: Correct the file name specification.
//
15123, 00000, "ASM file name '%s' contains an invalid incarnation number"
// *Cause: A numeric file name was specified which did not contain a
// valid ASM incarnation number. The ASM incarnation number follows
// immediately after the ASM file number. It must be preceeded by
// a '.' character, and contain only numeric characters.
// *Action: Correct the file name specification.
//
15124, 00000, "ASM file name '%s' contains an invalid alias name"
// *Cause: A file name was specified which did not contain a valid
// ASM alias name. The ASM alias name, if present, follows
// immediately after the diskgroup name, in place of the ASM
// file number. It must be preceeded by a slash, start with an
// alphabetic character, and consist of up to 48 characters which
// are alphabetic, numeric, or the characters '$', '_', '-', or '#".
// A space can separate two parts of an alias name.
// *Action: Correct the file name specification.
//
15125, 00000, "ASM file name '%s' contains an invalid template name"
// *Cause: A file name was specified to ASM which did not contain a valid
// template name. The template name, if present, follows
// immediately after the ASM incarnation number or the ASM alias
// name, if such is used in place of the ASM file number. It must
// be enclosed in parenthesis, start with an alphabetic character,
// and consist of up to 30 characters which are alphabetic, numeric,
// or the characters '$' and '_'.
// *Action: Correct the file name specification.
//
15126, 00000, "component within ASM file name '%s' exceeds maximum length"
// *Cause: The maximum identifier length of 48 characters was exceeded for
// the diskgroup name, template name, or alias name field within the
// ASM file name.
// *Action: Correct the file name specification.
//
15127, 00000, "ASM file name '%s' cannot use templates"
// *Cause: A fully qualified ASM file name was specified. Such a
// specification does not permit the inclusion of a template name
// in the ASM file name.
// *Action: Correct the file name specification.
//
15128, 00000, "ASM file name '%s' exceeds maximum length %s"
// *Cause: The maximum ASM file name length of 256 characters was exceeded for
// the combination of diskgroup name, file number, template name,
// alias name plus punctuation within the ASM file name.
// *Action: Correct the file name specification.
//
15129, 00000, "entry '%s' does not refer to a valid directory"
// *Cause: The entry indicated did not refer to a directory. Attempt was
// made to access the contents of this directory.
// *Action: Correct the error and try again.
//
15130, 00000, "diskgroup \"%s\" is being dismounted"
// *Cause: The diskgroup is being dismounted by request or because an I/O
// error was encountered that could not be handled by taking the
// disks offline. A disk cannot be offlined whenever doing so
// could result in all copies of a redundant extent being unavailable.
// *Action: Repair the hardware problem and re-mount the diskgroup.
// Refer to the alert log to determine which disks have failed.
//
15131, 00000, "block %s of file %s in diskgroup %s could not be read"
// *Cause: A block could not be read because the disk containing the block
// is either offline or an I/O error occured while reading the block.
// If this is mirrored file, then all disks that contain a copy
// of the block are either offline or received errors.
// *Action: Repair the affected disk and bring it back online. Refer to
// accompanying error messages to determine which disk has failed.
//
15132, 00000, "block %s of file %s in diskgroup %s could not be written"
// *Cause: A block could not be written because the disk containing the block
// is either offline or an I/O error occured while writing the block.
// If this is mirrored file, then insufficient disks which contain a
// copy of the block are either offline or received errors.
// *Action: Repair the affected disk and bring it back online. Refer to
// accompanying error messages to determine which disk has failed.
//
15133, 00000, "instance recovery required for diskgroup %s"
// *Cause: An instance in the cluster crashed making instance recovery
// necessary.
// *Action: None. This error should not normally be seen by an ASM client.
// ASM will trap this error and retry the operation after doing
// instance recovery automatically.
//
15134, 00000, "mirror resilvering not supported for %s"
// *Cause: The specified device requires oracle to take mirror resilvering
// responsiblity. ASM does not resilver logical volume manager (lvm)
// based mirrors.
// *Action: Disable lvm-based mirroring or set the parameter
// _asm_allow_lvm_resilvering to TRUE. One might experience
// performance degradation when lvm-based resilvering is enabled
// with ASM.
//
15135, 00000, "The %s cluster is not in rolling patch state. The patch level [%s] of instance %s is not the same as the current cluster patch level [%s]."
// *Cause: During startup, this instance found one or more other instances
// running at a different patch level, and the cluster was not in
// rolling patch state. Startup of this instance failed.
// *Action: The patch level of this instance differs from the cluster patch
// level.
// If the intention is to patch the cluster using the rolling option,
// then set the cluster in rolling patch state using the
// 'crsctl start rollingpatch' command from an active node, and
// restart Oracle Clusterware on this node.
// If the intention is to patch the cluster in a non-rolling manner,
// and the patch has been applied on the local node, then stop all of
// the active nodes in the cluster that have a patch level that does
// not match the patch level of the current node. Use the
// 'crsctl query crs softwarepatch <host>' command to retrieve the
// configured patch level of a node.
// If the intention is to patch the cluster in a non-rolling manner,
// and the patch has not been applied on the local node, then
// apply the requisite patch, and restart Oracle Clusterware on this
// node. Patches applied on a node can be obtained by issuing the
// the 'crsctl query crs releasepatch' command.
//
15136, 00000, "cluster in rolling patch from patch level [%s] to [%s]"
// *Cause: The current patch level of the instance was incompatible with
// the rolling patch operation of the cluster.
// *Action: The patch level of the new member instance must be one of the two
// patch levels involved in the rolling patch operation.
//
15137, 00000, "The %s cluster is in rolling patch state."
// *Cause: The cluster was already in the middle of rolling patch.
// *Action: Rolling patch needs to be stopped before attempting to start again.
//
15138, 00000, "cluster rolling patch incomplete"
// *Cause: The cluster was still performing rolling patch.
// *Action: Ensure that all of the instances in the cluster are patched before
// retrying the command.
//
15139, 00000, "patch level of %s instances differ in cluster"
// *Cause: Not all of the instances in the cluster had the same set
// of patches.
// *Action: Ensure that all of the instances in the cluster have the same
// patches before retrying the command. Find the configured patch
// level on a node using the 'crsctl query crs softwarepatch'
// command.
//
15140, 0000, "rolling patch prevented by %s"
// *Cause: One or more instances were blocking the rolling patch.
// *Action: Terminate or wait until the reported operation is complete before
// attempting the rolling patch to the cluster.
//
15141, 0000, "The %s cluster is not in either rolling upgrade or rolling patch state."
// *Cause: The ALTER SYSTEM STOP ROLLING MIGRATION or ALTER SYSTEM STOP
// ROLLING PATCH command was executed when the cluster was not in
// either the rolling upgrade or rolling patch state.
// *Action: The system has to be set to rolling upgrade or rolling patch
// state before attempting to execute the command.
//
15142, 0000, "either MIGRATION or PATCH keyword expected"
// *Cause: The keyword was missing.
// *Action: Supply the missing keyword.
//
15143, 0000, "either APPLY or ROLLBACK keyword expected"
// *Cause: The keyword was missing.
// *Action: Supply the missing keyword.
//
15144, 0000, "disk '%s' is about to fail"
// *Cause: An attempt was made to ADD (or REPLACE) a failing disk to a disk
// group.
// *Action: Specify a different disk in the command. Note that not even the
// FORCE option can be used to add the disk to the disk group.
//
15145, 0000, "ASM disk '%s' is online and cannot be replaced."
// *Cause: The REPLACE DISK operation specified a disk which is online.
// *Action: Check to confirm that the ASM disk is offline. Online disks can be
// replaced while maintaining redundancy by issuing ADD and DROP disk
// commands in a single SQL statement.
//
15146, 0000, "Rolling migration or patching operation failed"
// *Cause: Operation failed due to temporary issue.
// *Action: Retry the command.
//
15147, 0000, "failed to start the instance"
// *Cause: The instance could not be started during rolling upgrade from
// ASM instance versions prior to 12.1.0.0.0
// *Action: Complete the rolling upgrade process and start the instance.
//
15148, 0000, "Too many CRS users are created."
// *Cause: The number of CRS users has reached its limit of 999.
// The situation is unexpected.
// *Action: Check to see why so many CRS users are created.
//
15149, 00000, "another ASM instance found running on the host"
// *Cause: Another ASM instance found on the host. Only one ASM instance is
// supported on a host.
// *Action: Shut down the other instance before starting this ASM
// instance.
15150, 00000, "instance lock mode '%s' conflicts with other ASM instance(s)"
// *Cause: Some other ASM instance used the lock name space in a conflicting
// mode.
// *Action: Shut down the other instance or start up in compatible mode.
// Alternatively, set the DB_UNIQUE_NAME initialization parameter
// to avoid the conflict.
//
15151, 00000, "missing or invalid version number for rolling migration"
// *Cause: The command did not specify a valid version number.
// *Action: Correct the version number in the command. It should be of the
// form v#.#.#.#.# or other forms with fewer numbers delimited by
// a period. The version number must be different from the current
// software version of the instance.
//
15152, 00000, "The %s cluster is in rolling upgrade state."
// *Cause: The cluster was already in the middle of rolling upgrade.
// *Action: Rolling upgrade needs to be stopped before attempting to start
// again.
//
15153, 00000, "The %s cluster is not in rolling upgrade state. The version [%s] of instance %s is not the same as the current cluster version [%s]."
// *Cause: During startup, this instance found one or more other instances
// running at a different version, and the cluster was not in
// rolling upgrade state. Startup of this instance failed.
// *Action: The version of this instance differs from the cluster version.
// If the intention is to upgrade the cluster using the rolling
// option, then set the cluster in rolling upgrade state using the
// 'crsctl start rollingupgrade' command from an active node, and
// restart Oracle Clusterware on this node.
// If the intention is to upgrade the cluster in a non-rolling manner,
// and the local node has already been upgraded, then stop all of
// the active nodes in the cluster that have an older version than
// the current node. Use the 'crsctl query crs softwareversion <host>'
// command to retrieve the configured version of a node.
// If the intention is to upgrade the cluster in a non-rolling manner,
// and the local node has not been upgraded yet, then upgrade the
// node by running the rootupgrade.sh script.
//
15154, 00000, "cluster rolling upgrade incomplete"
// *Cause: The cluster was still performing rolling upgrade.
// *Action: Ensure that all the instances in the cluster are upgraded before
// retrying the command.
//
15155, 00000, "version incompatible with the cluster"
// *Cause: The current software version of the instance was incompatible with
// the other members of the cluster.
// *Action: Ensure that all of the members of the cluster are at the same
// version. If you are attempting to perform a rolling upgrade,
// execute the ALTER SYSTEM START ROLLING statement. Ensure that the
// version being upgraded to is compatible with the existing version
// of the cluster.
//
15156, 00000, "cluster in rolling upgrade from version [%s] to [%s]"
// *Cause: The current software version of the instance was incompatible with
// the rolling upgrade operation of the cluster.
// *Action: The version number of new member instance must be one of the two
// versions involved in the rolling upgrade.
//
15157, 00000, "rolling migration is not allowed"
// *Cause: The cluster was not capable of handling ASM rolling migration.
// *Action: The Oracle Cluster Services is using vendor clusterware. Oracle
// cannot perform rolling upgrade or downgrade using vendor cluster
// ware. Restart ASM instances using Oracle cluster ware and retry
// the operation.
//
15158, 00000, "rolling upgrade prevented by %s"
// *Cause: One or more instances were blocking the rolling upgrade.
// *Action: Terminate or wait until the reported operation is complete before
// attempting the rolling upgrade to the cluster.
//
15159, 00000, "Internal testing event"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: Traces execution of rolling upgrade. Level indicates verbosity of
// tracing.
//
//
15160, 00000, "rolling migration internal fatal error in module %s,%s"
// *Cause: Rolling migration experienced a fatal error.
// *Action: Please contact Oracle support services.
//
15161, 00000, "invalid SYS_CLUSTER_PROPERTIES parameter"
// *Cause: The parameter passed in for SYS_CLUSTER_PROPERTIES is invalid
// *Action: Pass in the correct parameter, refer to user documentation for
// a list of allowed parameter values.
//
15162, 00000, "cluster in rolling downgrade"
// *Cause: The cluster was already in the middle of rolling downgrade.
// *Action: Rolling downgrade needs to be stopped before attempting to start
// again.
//
15163, 00000, "cluster is not in the rolling downgrade to %s"
// *Cause: The cluster was not in the rolling downgrade.
// *Action: Start the rolling downgrade using the ALTER SYSTEM START ROLLING
// MIGRATION command from another ASM instance and restart this
// instance.
//
15164, 00000, "cluster rolling downgrade incomplete"
// *Cause: The cluster was still performing rolling downgrade.
// *Action: Ensure that all the instances in the cluster are downgraded before
// retrying the command.
//
15165, 00000, "rolling migration not allowed with the versions specified"
// *Cause: One of the following requirements were not met:
// - The From version is not compatible.
// - The To version is less than or equal to the From version.
// - Neither the From nor the To version matches the current version.
// - The From version is less than 12.1.0.2.0.
// *Action: Ensure that the From and the To versions specified are legitimate.
//
15166, 00000, "cluster in rolling downgrade from version [%s] to [%s]"
// *Cause: The current software version of the instance was incompatible with
// the rolling downgrade operation of the cluster.
// *Action: The version number of new member instance must be one of the two
// versions involved in the rolling downgrade.
//
15167, 00000, "command requires at least %s failure groups; found only %s"
// *Cause: An attempt to convert disk group redundancy failed because of
// insufficient failure groups.
// *Action: Add enough failure groups to the disk group and then retry
// converting the disk group redundancy to flex.
//
15168, 00000, "rolling downgrade prevented by %s"
// *Cause: One or more instances were blocking the rolling downgrade.
// *Action: Terminate or wait until the reported operation is complete before
// attempting the rolling downgrade to the cluster.
//
15169, 00000, "destination '%s' is a subdirectory of '%s'"
// *Cause: Attempt to rename directory failed because the new directory name
// was a subdirectory of the original directory.
// *Action: Correct the path of the destination and try again.
//
15170, 00000, "cannot add entry '%s' in directory '%s'"
// *Cause: Other errors prevented directory/alias creation.
// *Action: Correct the errors and try again.
//
15171, 00000, "invalid syntax in the alias path after '%s'"
// *Cause: An invalid alias/directory name syntax was specified.
// *Action: Correct the alias path and try again.
//
15173, 00000, "entry '%s' does not exist in directory '%s'"
// *Cause: The specified alias did not exist in the given directory.
// *Action: Correct the alias path and try again.
15174, 00000, "unable to create alias name"
// *Cause: An attempt to create an alias name for an ASM file failed.
// *Action: Check the alert logs and trace files of the Oracle ASM instance for
// more information on the failure, as well as checking the
// accompanying error messages.
15175, 00000, "cannot create alias for diskgroup metadata file '%s'"
// *Cause: An attempt was made to create an alias for a diskgroup
// metadata file.
// *Action: Correct the alias path and try again.
//
15176, 00000, "file '%s' already has an alias associated with it"
// *Cause: An attempt was made to create an alias for a file that already had
// an existing alias.
// *Action: Correct the file name and try again or drop existing alias.
//
15177, 00000, "cannot operate on system aliases"
// *Cause: An attempt was made to modify a system alias.
// *Action: Correct the alias name and try again.
//
15178, 00000, "directory '%s' is not empty; cannot drop this directory"
// *Cause: An attempt was made to drop a directory that contained valid
// entries.
// *Action: Correct the directory path or specify the FORCE option to drop a
// directory that is not empty.
//
15179, 00000, "missing or invalid alias name"
// *Cause: The command did not specify a valid alias identifier.
// *Action: Specify a valid alias identifier.
//
/============================================================================
/ 15180 - 15188 Used for ASMLIB related error messages
/============================================================================
/
15180, 00000, "could not open dynamic library %s, error [%s]"
// *Cause: The library was not accessible
// *Action: Correct the permissions of the library and try again.
//
15181, 00000, "symbol [%s] not found in library %s, error [%s]"
// *Cause: An error was encountered while loading the specified ASMLIB symbol.
// *Action: Correct the error reported and try again.
//
15182, 00000, "ASMLIB [%s] version mismatch, ORACLE version [%s]"
// *Cause: The ASMLIB version reported is not supported by the ORACLE binary.
// *Action: Install the correct library and try again.
//
15183, 00000, "ASMLIB initialization error [%s]"
// *Cause: Unable to initialize the ASMLIB in ORACLE.
// *Action: Check the configuration of ASMLIB or deinstall ASMLIB if not used.
//
15184, 00000, "ASMLIB error could not be determined [%s] [%s]"
// *Cause: An error was encountered which cannot be diagnosed further.
// *Action: Contact ASMLIB libary vendor for support.
/
15185, 00000, "could not close dynamic library %s, error [%s]"
// *Cause: Could not close the dynamic library.
// *Action: Contact ASMLIB libary vendor for support.
//
15186, 00000, "ASMLIB error function = [%s], error = [%s], mesg = [%s]"
// *Cause: An error occurred during a call to function listed in the error.
// *Action: The detailed message associated with the error is listed along with
// the error. Correct the error and try again or contact ASMLIB
// library vendor for support.
15187, 00000, "Incompatible RDBMS operation [%s] pushed to storage"
// *Cause: RDBMS to storage version mismatched with incompatibility operation.
// *Action: Upgrade RDBMS to match storage version.
//
15188, 00000, "process terminated due to an ASMLIB error"
// *Cause: A process was terminated as a result of an ASMLIB error.
// *Action: See the alert log for more information. Reconnect to the database
// or the ASM instance. If the process termination resulted in
// instance termination, restart the instance.
//
/============================================================================
/ 15189 - 15199 Used for ASM tracing and testing errors
/============================================================================
/
15189, 00000, "Internal ASM testing event number 15189"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: The level controls ksfdaf testing.
//
15190, 00000, "Internal ASM testing event number 15190"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: The level controls which ASM disks encounter rebalance IO errors.
//
15191, 00000, "Internal ASM testing event number 15191"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: The level controls which ASM errors are emulated.
//
15192, 00000, "invalid ASM disk header [%s] [%s] [%s] [%s] [%s]"
// *Cause: ASM encountered an invalid disk header.
// *Action: Contact Oracle Support Services.
//
15193, 00000, "Internal ASM tracing event number 15193"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: None.
//
15194, 00000, "Internal ASM-DB interaction testing event number 15194"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: The level controls which ASM-DB operation is interuppted.
//
15195, 00000, "Internal ASM testing event number 15195"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: The level controls which ASM errors are simulated.
//
15196, 00000, "invalid ASM block header [%s:%s] [%s] [%s] [%s] [%s != %s]"
// *Cause: ASM encountered an invalid metadata block.
// *Action: Contact Oracle Support Services.
//
15197, 00000, "suppressing %s additional ASM messages"
// *Cause: The ASM command generated so many erorrs that this summary
// message was reported in place of many individual messages.
// *Action: If the command contained multiple actions, try separating
// each action into its own command and executing each command
// by itself. Otherwise, try not to generate so many errors.
//
15198, 00000, "operation %s is not yet available"
// *Cause: An unimplemented operation was attempted.
// *Action: Consider upgrading to later releases as they become available.
//
15199, 00000, "Internal ASM tracing event number 15199"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: Traces execution of ASM. Level indicates verbosity of tracing.
//
/============================================================================
/ 15200 - 15206 ASM messages added in 10.2
/============================================================================
/
15200, 00000, "initialization parameter %s (%s) is not a power of two"
// *Cause: The value specified for this initialization parameter was
// not a power of two.
// *Action: Correct the initialization parameter value and restart
// the instance.
//
15201, 00000, "disk %s contains a valid RDBMS file or foreign volume"
// *Cause: A disk specified in a CREATE DISKGROUP or ALTER DISKGROUP ...
// ADD DISK command appeared to contain a file from an existing
// database or a foreign volume. By default, as a safeguard against
// damaging an existing database or foreign volume, ASM does not
// allow a disk group to be created using this disk.
// *Action: Check that the ASM disk specification is correct. Otherwise,
// when storage from a defunct database or unmounted foreign volume
// is reused as part of an ASM disk group, specify the FORCE option
// to the ASM SQL command. See the alert log for more information.
//
15202, 00000, "cannot create additional ASM internal change segment"
// *Cause: The mount of a diskgroup by an additional instance in a RAC
// cluster required more space for internal use by ASM than was
// available in the diskgroup.
// *Action: Delete unused files from the diskgroup or add additional disks
// to the diskgroup and retry the operation.
15203, 00000, "diskgroup %s contains disks from an incompatible version of ASM"
// *Cause: Diskgroup was created by an ASM instance with a higher
// compatibility setting.
// *Action: Use an ASM instance with the appropriate software version to mount
// the diskgroup.
15204, 00000, "database version %s is incompatible with diskgroup %s"
// *Cause: The COMPATIBLE parameter for the RDBMS instance is less than
// the value of the compatible.rdbms attribute for the disk group.
// *Action: Update the COMPATIBLE parameter for RDBMS instance to a version
// greater than or equal to compatible.rdbms version. The compatible
// attributes for diskgroups cannot be lowered.
//
15205, 00000, "requested mirror side unavailable"
// *Cause: The requested mirror side of a block is either unallocated or
// allocated on a disk that has been dropped from the diskgroup.
// *Action: Resubmit the request or try another mirror side.
//
15206, 00000, "duplicate diskgroup %s specified"
// *Cause: A command specified the same diskgroup twice.
// *Action: Specify each diskgroup only once.
//
15207, 00000, "Internal ASM testing event number 15207"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: The level controls which ASM errors are simulated.
//
15208, 00000, "Internal ASM testing event number 15208"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: The level controls which ASM errors are simulated.
//
15209, 00000, "invalid block type read from disk"
// *Document: NO
// *Cause: ASM read a block whose block type was KFBTYP_INVALID.
// *Action: None. This error is trapped and handled internally and will not
// be exposed to end users.
//
/============================================================================
/ 15210 - 15227 ASM SQL parsing messages added in 11.1
/============================================================================
15210, 00000, "conflicting or duplicate PERMISSION options"
// *Cause: The PERMISSION clause contained the USER, GROUP, or OTHER
// keyword more than once.
// *Action: Specify each keyword, at most, once.
//
15211, 00000, "conflicting or duplicate OWNERSHIP options"
// *Cause: The OWNERSHIP clause contained either the OWNER or the
// GROUP keyword more than once.
// *Action: Specify each keyword, at most, once.
//
15212, 00000, "missing or invalid OWNER or GROUP name"
// *Cause: The command did not specify a valid name for either the OWNER
// or the GROUP keyword.
// *Action: Specify a valid name for either the OWNER or the GROUP
// keyword.
//
15213, 00000, "command operates on only one attribute"
// *Cause: More than one disk group attribute was specified in the
// ALTER DISKGROUP statement.
// *Action: Specify only one disk group attribute per ALTER DISKGROUP
// statement.
//
15214, 00000, "missing or invalid attribute specification"
// *Cause: The command did not specify a valid attribute name
// or a valid attribute value.
// *Action: Specify a valid attribute name and value pair.
//
15215, 00000, "missing or invalid user name"
// *Cause: The command did not specify a valid user name.
// *Action: Specify a valid user name.
//
15216, 00000, "missing or invalid user group name"
// *Cause: The command did not specify a valid user group name.
// *Action: Specify a valid user group name.
//
15217, 00000, "missing or invalid timeout value after DROP AFTER"
// *Cause: The command did not specify a valid timeout value after
// the DROP AFTER clause.
// *Action: Specify a valid timeout value after the DROP AFTER clause.
//
15218, 00000, "timeout value exceeded range"
// *Cause: The OFFLINE timeout value exceeded the range of 0-136
// years, inclusive. 136 years are 49674 days, 1192176
// hours, and 71530560 minutes.
// *Action: Specify a timeout value within the range of 0-136
// years, inclusive.
//
15219, 00000, "conflicting or duplicate disk region options"
// *Cause: The command contained one or more of the following:
// - both the HOT and the COLD keywords
// - both the MIRRORHOT and the MIRRORCOLD keywords
// - the HOT keyword more than once
// - the COLD keyword more than once
// - the MIRRORHOT keyword more than once
// - the MIRRORCOLD keyword more than once
// *Action: Specify either the HOT or the COLD keyword and either the
// MIRRORHOT or the MIRRORCOLD keyword, at most, once.
//
15220, 00000, "invalid file attribute specification"
// *Cause: The keyword UNPROTECTED, MIRROR, HIGH, FINE, or COARSE
// was specified in a MODIFY FILE clause. These file attributes
// are immutable once a file is created.
// *Action: Specify a disk region keyword; for example, HOT, COLD, MIRRORHOT,
// or MIRRORCOLD.
//
15221, 00000, "ASM operation requires compatible.asm of %s or higher"
// *Cause: The ASM operation specified requires a higher disk group
// attribute value for compatible.asm.
// *Action: Set the disk group attribute compatible.asm to or above the
// requested version.
//
15222, 00000, "ASM disk \"%s\" is offline and cannot be renamed."
// *Cause: An attempt was made to rename a disk that is offline.
// *Action: Check the ASM disk name as specified in the command.
//
15223, 00000, "conflicting disk operations for %s"
// *Cause: An attempt was made to ADD and DROP the specified ASM disk
// in the same statement.
// *Action: Revise the statement to specify distinct ASM disks in the
// ADD disk and DROP disk clauses.
//
15224, 00000, "disk \"%s\" is already provisioned for ASM"
// *Cause: An attempt was made to label a disk that is already provisioned
// for ASM.
// *Action: Check the ASM disk name as specified in the command.
//
15225, 00000, "label name '%s' is already in use"
// *Cause: A LABEL SET command specified a label name that
// was already used by another ASM disk.
// *Action: Select a different name for the label.
//
15226, 00000, "label name '%s' is not used by ASM"
// *Cause: A LABEL CLEAR command specified a label name that
// was not used by ASM.
// *Action: Select a different name for the label.
//
15227, 00000, "could not perform label set/clear operation"
// *Cause: An error occurred while setting/clearing the ASM label.
// *Action: Look at the underlying error(s) on the error stack. Check other
// messages in the trace files for more information.
//
/============================================================================
/ 15228 - 15229 Used for ASM testing errors
/============================================================================
/
15228, 00000, "Internal ASM testing event number 15228"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: The level controls error simulation.
//
/============================================================================
/ 15230 - 15250 ASM runtime error messages added in 11.1
/============================================================================
15230, 00000, "diskgroup '%s' does not require the FORCE option"
// *Cause: An attempt was made to MOUNT or DROP a disk group with the FORCE
// option.
// *Action: MOUNT and DROP diskgroup with the FORCE option are only
// permitted if the diskgroup cannot be mounted normally.
//
15231, 00000, "advancing diskgroup compatibility would exclude connected clients"
// *Cause: Disk group compatibility could not be advanced because
// connected clients were at a lower compatibility than
// the target value.
// *Action: Ensure that all connected clients are at the target compatibility
// level or higher.
//
15232, 00000, "command requires all disks in diskgroup %s to be online"
// *Cause: Disk group compatibilty could not be advanced because some
// disks are offline.
// *Action: Retry the command after offline disks are dropped.
//
15233, 00000, "cannot advance diskgroup compatibility due to [%s]"
// *Cause: Disk group compatibilty could not be advanced because of errors.
// *Action: Check the alert log for more information on the reason for the
// failure.
//
15234, 00000, "target RDBMS compatibility (%s) exceeds ASM compatibility (%s)"
// *Cause: An attempt was made to advance RDBMS compatibility beyond
// the disk group's ASM compatibility.
// *Action: Advance ASM compatibility before advancing RDBMS compatibility.
//
15235, 00000, "diskgroup %s mount mode conflicts with existing mount"
// *Cause: The mode specified in the diskgroup mount command conflicted with
// the mode in which it was mounted on some other instance.
// *Action: Specify a compatible mode in the diskgroup mount command.
//
15236, 00000, "diskgroup %s mounted in restricted mode"
// *Cause: The specified diskgroup was mounted in restricted mode prohibiting
// client access.
// *Action: Dismount the diskgroup and remount it in appropriate mode.
//
15237, 00000, "invalid attribute %s to CREATE DISKGROUP command"
// *Cause: An invalid attribute was specified with the CREATE DISKGROUP
// command.
// *Action: Check the valid attributes for CREATE DISKGROUP command and specify
// a valid one.
//
15238, 00000, "%s is not a valid value for attribute %s"
// *Cause: The specified value was not valid for the attribute.
// *Action: Check the attribute name and value.
//
15239, 00000, "allocation unit size higher than %s requires RDBMS compatibility %s"
// *Cause: The allocation unit size requested exceeded the limit
// imposed by the RDBMS compatibility setting.
// *Action: Use a smaller allocation unit size or specify a
// higher RDBMS compatibility setting.
//
15240, 00000, "attribute name %s is invalid"
// *Cause: The attribute name was not valid or was not recognized.
// *Action: Check the attribute name.
//
15241, 00000, "attribute %s is read only"
// *Cause: The attribute value is read-only and cannot be changed.
// *Action: None. The attribute value cannot be changed.
//
15242, 00000, "could not set attribute %s"
// *Cause: An error occurred while setting the attribute.
// *Action: Look at the underlying error(s) on the error stack.
//
15243, 00000, "%s is not a valid version number"
// *Cause: The given version number was invalid, or not valid in this context.
// *Action: Verify that the version number is valid and is appropriate
// for this command. Check for additional errors reported.
//
15244, 00000, "new compatibility setting less than current [%s]"
// *Cause: The compatibility setting was invalid. The compatibility
// setting can only be advanced.
// *Action: Check the version number.
//
15245, 00000, "ASM disk %s is already online or being brought online."
// *Cause: An attempt was made to bring a disk online that was either already
// online or was being brought online.
// *Action: Change the ONLINE statement to exclude the disk.
//
15246, 00000, "cannot bring ASM disk %s both online and then offline in the same statement"
// *Cause: An attempt was made to bring the specified disk both online and
// offline in the same statement.
// *Action: Revise the statement to either bring the disk online or take the
// disk offline.
//
15247, 00000, "cannot specify both WAIT and NOWAIT options in the same statement"
// *Cause: An attempt was made to specify both WAIT and NOWAIT options in the
// same statement.
// *Action: Revise the statement and include at most one option.
//
15248, 00000, "ASM attributes feature not enabled"
// *Cause: The ASM attributes feature was not enabled.
// *Action: Advance disk group ASM compatibility to version 11.1.0 or newer.
//
15249, 00000, "could not locate ASM attribute %s"
// *Cause: The specified attribute could not be accessed.
// *Action: Check the attribute name and examine underlying
// error(s) on the error stack.
//
15250, 0000, "insufficient diskgroup space for rebalance completion"
// *Cause: The command attempted to reduce the available diskgroup space
// below the current space used.
// *Action: Consult V$ASM_DISK to determine the space requirements for the
// diskgroup contents, and repeat the command after making the
// required storage available.
//
15251, 00000, "only restricted mount is allowed in the ASM instance"
// *Cause: The ASM instance was started in restricted mode, and an attempt was
// made to mount a diskgroup in non-restricted mode.
// *Action: Start the ASM instance in non-restricted mode and mount the
// diskgroup again, or mount the diskgroup in restricted mode.
//
//
15252, 00000, "user name '%s' does not exist in OS user dictionary"
// *Cause: The specified user name was not a valid operating system user.
// *Action: Specify a valid operating system user.
//
15253, 00000, "user group name '%s' exceeds limit of %s characters"
// *Cause: The length of the specified user group name exceeded the
// maximum limit.
// *Action: Reduce the length of the user group name to a value within
// the limit.
//
15254, 00000, "user group '%s' already exists in disk group"
// *Cause: The specified user group name already existed in the disk group.
// *Action: Specify a different user group name.
//
15255, 00000, "user group '%s' does not exist in disk group '%s'"
// *Cause: The specified user group name did not exist in the disk group.
// *Action: Specify a valid user group name.
//
15256, 00000, "user '%s' is already a member of user group '%s'"
// *Cause: The specified user was already a member of the specified
// user group.
// *Action: Specify either an alternate user or an alternate user group.
//
15257, 00000, "exceeded %s number of members per user group"
// *Cause: The maximum number of members per user group was exceeded.
// *Action: Delete existing members of the user group to create space.
//
15258, 00000, "user group entry number must be between %s and %s, inclusive"
// *Cause: The specified user group entry number was beyond the
// acceptable range.
// *Action: Specify a valid value for the user group entry number.
//
15259, 00000, "user '%s' is not a member of user group '%s'"
// *Cause: The specified user was not a member of the specified user group.
// *Action: Specify either an alternate user or an alternate user group.
//
15260, 00000, "permission denied on ASM disk group"
// *Cause: An attempt was made to perform an operation on an ASM disk
// group without the appropriate privileges.
//
// *Action: Ask the ASM administrator to perform the operation or grant
// the required privileges.
//
15261, 00000, "user '%s' already exists in disk group '%s'"
// *Cause: The specified UID already existed in the disk group.
// *Action: Specify a different UID.
//
15262, 00000, "user '%s' does not exist in disk group '%s'"
// *Cause: The specified UID did not exist in the disk group.
// *Action: Specify a user with a valid UID.
//
15263, 00000, "user name '%s' exceeds limit of %s characters"
// *Cause: The length of the specified user name exceeded the
// maximum limit.
// *Action: Reduce the length of the user name to a value within
// the limit.
//
15264, 00000, "Operating system function returned error %s"
// *Cause: An operating system error occurred.
// *Action: Correct the operating system error and retry the operation.
//
15265, 00000, "user identification number not in range of [%s,%s]"
// *Cause: The operating system user identification number exceeded
// the maximum value.
// *Action: Change the user identification number to a value within
// the accepted range.
//
15266, 00000, "user identification number '%s' is not allowed"
// *Cause: This user identification number is used internally by ASM.
// *Action: Please choose a different user identification number.
//
15267, 00000, "Internal ASM event number 15267"
// *Document: NO
// *Cause: Do not set this event. Used internally by Oracle.
// *Action: None.
//
15268, 00000, "internal Oracle file %s already exists."
// *Cause: File was already in existence.
// *Action: This is an internal error. Contact Oracle Support Services.
//
15269, 00000, "group identification number not in range of [%s,%s]"
// *Cause: The operating system group identification number exceeded
// the maximum value.
// *Action: Change the group identification number to a value within
// the accepted range.
//
15270, 00000, "disk %s is not a quorum disk"
// *Cause: The specified disk was not a quorum disk.
// *Action: Retry the operation without the quorum attribute for the disk.
//
15271, 00000, "failgroup %s is a quorum failgroup"
// *Cause: The specified failgroup was a quorum failgroup.
// *Action: Retry the operation with the quorum attribute for the failgroup.
//
15272, 00000, "failgroup %s is not a quorum failgroup"
// *Cause: The specified failgroup was not a quorum failgroup.
// *Action: Retry the operation without the quorum attribute for the failgroup.
//
15273, 00000, "Could not create the required number of voting files."
// *Cause: The required number of voting files could not be created. See
// accompanying messages for possible causes.
// *Action: See accompanying messages for possible actions.
//
15274, 00000, "Not enough failgroups (%s) to create voting files"
// *Cause: The number of failgroups required for this redundancy were not
// present in the diskgroup to create voting files.
// *Action: Retry the operation after creating new failgroup(s).
//
15275, 00000, "Not enough contiguous space (%s AUs) in disk %s to allocate a voting file"
// *Cause: The specified disk did not have enough space to allocate a voting
// file on it.
// *Action: Ensure that there is at least 1 disk with the required space in
// atleast the required number of failgroups for the diskgroup.
//
15276, 00000, "ASM diskgroup %s has cluster voting files"
// *Cause: An attempt was made to drop a diskgroup that contained cluster
// voting files.
// *Action: Move the cluster voting files out of the diskgroup and retry the
// operation.
//
15277, 00000, "disk %s is a quorum disk"
// *Cause: The specified disk was a quorum disk.
// *Action: Retry the operation with the quorum attribute for the disk.
//
15278, 00000, "external redundancy diskgroup requires at least one regular disk"
// *Cause: An attempt was made to create an external redundancy diskgroup
// with only quorum disks.
// *Action: Specify atleast one regular disk to create an external redundancy
// diskgroup.
//
15279, 00000, "user '%s' is currently being deleted"
// *Cause: The specified user was in the process of being deleted and
// could not be used.
// *Action: Either abandon this operation or specify a different user.
//
15280, 00000, "user '%s' owns existing files"
// *Cause: An attempt was made to drop a user that still owns existing
// files.
// *Action: Specify the CASCADE option to drop the user and
// all of the owned files.
//
/============================================================================
/ 15252 - 15280 Reserved for TrailBlazer
/============================================================================
15281, 00000, "not all specified disks were brought ONLINE"
// *Cause: Some of the disks specified either experienced
// I/O errors while being brought ONLINE, or were simultaneously
// brought OFFLINE or dropped in another session, or were full.
// *Action: Query V$ASM_DISK or use ASMCMD LSDSK to determine which disks were
// not brought ONLINE. Inspect any additional error messages and
// the alert log to determine the exact cause. If some of the disks
// failed, either fix the cause of the failures or drop the disks.
// If some of the disks are full, either free space in the disk group
// or add new disks to the diskgroup.
//
15282, 00000, "Cluster Synchronization Services operation '%s' failed with error '%s'."
// *Cause: This is an internal error.
// *Action: Check the accompanying error messages. Contact Oracle Support
// Services.
//
15283, 00000, "ASM operation requires compatible.rdbms of %s or higher"
// *Cause: The ASM operation specified requires a higher disk group
// attribute value for compatible.rdbms.
// *Action: Set the disk group attribute compatible.rdbms to or above the
// requested version.
//
15284, 00000, "ASM terminated ALTER DISKGROUP ONLINE"
// *Cause: None of the disks specified by ALTER DISKGROUP ONLINE could be
// brought ONLINE.
// *Action: Inspect additional error messages and the alert log to determine
// why the specified disks cannot be brought ONLINE.
//
15285, 00000, "disk '%s' violates disk group attribute %s"
// *Cause: Including the specifed disk would violate a restriction imposed by
// the specified disk group attribute.
// *Action: Retry the operation while omitting the offending disk or
// change the attribute.
//
15286, 00000, "could not set disk group attribute %s due to offline disks"
// *Cause: The specified disk group attribute could not be set because
// the disk group includes offline disks.
// *Action: Retry the operation after the offline disks in this disk group
// are dropped or brought online.
//
15287, 00000, "could not set disk group attribute %s due to incompatible disks"
// *Cause: The specified disk group attribute could not be set because
// the disk group includes disks that conflict with the new value.
// *Action: Retry the operation after dropping the conflicting disks
// in this disk group.
//
15288, 00000, "disk(s) require disk group attribute %s clause"
// *Cause: Some of the disks specified by the command also require the
// specified disk group attribute to be stated.
// *Action: Retry the command including an ATTRIBUTE clause for the
// required disk group attribute. Alternatively, omit the disks
// that require setting the disk group attribue. See the alert log
// for additional information on the disks that require setting
// the disk group attribute.
15289, 0000, "disk %s is limited to %s MB on instance %s"
// *Cause: An ALTER DISKGROUP ADD DISK or RESIZE DISK command specified
// a disk with a size greater than the specified instance could use.
// *Action: Check the storage subsystem configuration on the specified node.
15290, 00000, "operation not permitted on offline disk %s"
// *Cause: An attempt was made to specify an operation that is only permitted
// on disks that are online. The specified disk was not online.
// *Action: Online the disk or wait for online to complete before retrying the
// operation.
15291, 00000, "ASM could not add disk \"%s\" to disk group \"%s\""
// *Cause: An attempt was made to add a disk to a disk group while the
// distribution of disks in failure groups was too uneven.
// *Action: Add or drop disks to or from failure groups to balance their
// distribution in all failure groups and retry the operation.
15292, 00000, "Disk name %s is being used by another disk"
// *Cause: The specified disk name could not be reused because an 11.1.0.6.0
// or earlier database instance had it cached in memory.
// *Action: Do one of the following
// - Specify a different name for the disk.
// - Wait for the rebalance to complete successfully.
// - Identify the database instance with the problem and shut it down
// before retrying the command.
//
15293, 00000, "operation disallowed by ASM_POWER_LIMIT"
// Cause: This operation required data movement in order to complete
// successfully. However, ASM_POWER_LIMIT was set to zero,
// thereby preventing this operation.
// Action: Repeat the operation after setting ASM_POWER_LIMIT to a
// non-zero value.
//
15294, 00000, "SYSASM privilege not allowed on database instance"
// Cause: The SYSASM privilege was not allowed on this database instance;
// it is allowed only on an ASM instance.
// Action: Use either the SYSDBA or the SYSOPER privilege.
//
15295, 00000, "ASM instance software version %s less than client version %s"
// Cause: The ASM instance software version was less than the client version.
// Action: Upgrade the ASM instance software. Check the alert log for
// more information on the reason for the failure.
//
15296, 00000, "POWER disallowed by diskgroup compatibility"
// *Document: NO
// *Cause: The rebalance power was not allowed due to the diskgroup
// compatiblity.
// *Action: None.
//
15297, 00000, "extent pointer %s for file %s block %s%s does not exist"
// Document: NO
// Cause: This is an internal error in ASM. End users will never see this
// error. It is raised when kfcInitPba attempts to extract the
// extent pointers from a locator block and finds they are KFXP_NODISK
// or KFXP_NOEXT. An external error is used because sometimes this
// error needs to be caught and ignored.
// Action: None. End users will not see this error.
//
15298, 00000, "possible lost disk write detected during crash recovery"
// Cause: ASM crash recovery read a block who's version was older than
// expected.
// Action: None. End users will not see this error. ASM automatically
// traps this error and attempts a fallback recovery.
//
15299, 00000, "FINE striping not allowed for the Staleness Registry"
// Cause: An SQL command attempted to set the striping attribute of the
// ASM_STALE template to FINE striping.
// Action: Do not modify the striping attribute of the ASM_STALE template.
//
15300, 00000, "File %s is incompatible with this operation"
// Cause: The file type was incompatible with the operation.
// Action: Use another file of the correct type.
//
15301, 00000, "cannot change %s of the open file '%s'"
// *Cause: A SET OWNERSHIP or SET PERMISSION command was attempted on
// an open file.
// *Action: Close the file and retry the SQL command.
//
15302, 00000, "active use of files owned by user '%s' precludes its drop"
// *Cause: A DROP USER command specified a user owning files that
// were in use.
// *Action: Close all files owned by this user.
//
15303, 00000, "Voting files could not be created in diskgroup %s due to small Allocation Unit size"
// *Cause: An attempt was made to create voting files in a diskgroup with a
// small Allocation Unit size.
// *Action: Create voting files in a different diskgroup whose Allocation Unit
// size is at least 1 mega byte.
15304, 00000, "operation requires ACCESS_CONTROL.ENABLED attribute to be TRUE"
// *Cause: An attempt was made to run an operation that required the
// ACCESS_CONTROL.ENABLED attribute to be set to TRUE, but its
// existing state was FALSE.
// *Action: Set the ACCESS_CONTROL.ENABLED attribute to TRUE and retry
// the operation.
//
15305, 00000, "cannot operate on ASM internal files"
// *Cause: An attempt was made to operate on Automatic Storage Management
// (ASM) metadata used to manage the diskgroup.
// *Action: Check the specified ASM file name.
//
15306, 00000, "ASM password file update failed on node %s"
// *Cause: A CREATE USER, ALTER USER, DROP USER, GRANT, or REVOKE
// command failed on the specified node of the Automatic Storage
// Management (ASM) cluster.
// *Action: Check the ASM alert logs for more information.
//
15307, 00000, "disk %s not discoverable by CSS; diskgroup %s has CSS voting files"
// *Cause: An attempt was made to add a disk which cannot be discovered by
// Cluster Synchronization Services (CSS).
// CSS has voting files in the disk group and will not be able
// to use the new disk if CSS cannot discover the disks.
// *Action: Update the Automatic Storage Management (ASM) disk string in the
// Grid Plug and Play (GPnP) profile to include the
// specified disk and retry the operation. Alternatively,
// migrate the CSS voting files out of the diskgroup and retry
// the operation
15308, 00000, "could not access ASM SPFILE in RDBMS instance"
// *Cause: A relational database management system (RDBMS) instance
// attempted to access an Automatic Storage Management (ASM) SPFILE.
// *Action: Connect to an ASM instance and reissue the command.
// Alternatively, specify an RDBMS SPFILE.
15309, 00000, "could not access database SPFILE in ASM instance"
// *Cause: An Automatic Storage Management (ASM) instance attempted to access
// a relational database management system (RDBMS) SPFILE.
// *Action: Connect to an RDBMS instance and reissue the command.
// Alternatively, specify an ASM SPFILE.
//
15310, 00000, "process terminated due to signal"
// *Cause: A process was terminated as a result of a signal in the I/O path.
// *Action: Reconnect to the database or the ASM instance. If the process
// termination resulted in instance termination, restart the
// instance.
//
15311, 00000, "process terminated due to fenced I/O"
// *Cause: A process was terminated because it was fenced from doing
// any more I/Os.
// *Action: Reconnect to the database or the ASM instance. If the process
// termination resulted in instance termination, restart the
// instance.
//
15312, 00000, "invalid file type"
// *Cause: Automatic Storage Management (ASM) could not determine the
// type of file.
// *Action: The file specified is not supported with Automatic Storage
// Management (ASM). Specify a supported file type for the
// operation.
//
15313, 00000, "Oracle ASM disk %s cannot be resized under %s M"
// *Cause: An Oracle ASM disk resize command specified a size that was less than
// the size required to support the voting file present on the disk.
// *Action: Increase the size specified for the disk.
//
15314, 00000, "Internal ASM event number 15314"
// *Document: NO
// *Cause: Do not set this event. Used internally by Oracle.
// *Action: None.
//
15315, 00000, "Write errors in disk group %s could lead to inconsistent ASM metadata."
// *Cause: One or more failures occurred while writing ASM metadata to disk.
// *Action: Repair the hardware problem and remount the disk group.
// Check the accompanying errors and alert log for the
// disks which reported the error.
//
15316, 00000, "Previous client instance %s has not fully exited."
// *Cause: One or more processes from a prior instantiation of this
// client were not fenced.
// *Action: Ensure that all processes belonging to the client instance have
// exited. Check the client alert log and the trace file of the
// process that terminated the instance.
//
15317, 00000, "user identification number '%s' does not exist in operating system user dictionary"
// *Cause: The specified user identification number did not belong to a valid
// operating system user.
// *Action: Specify a valid operating system user.
//
15318, 00000, "disks in disk group %s cannot be resized"
// *Cause: Execution of ASM Storage Reclamation Utility script was incomplete
// on the specified disk group.
// *Action: Execute ASM Storage Reclamation utility on the disk group to
// complete the operation.
15319, 00000, "ownership assignment of files to user '%s' precludes its drop"
// *Cause: A DROP USER command specified a user currently being assigned as
// the owner of one or more files with a SET OWNERSHIP command.
// *Action: Wait for the SET OWNERSHIP command to complete and then retry
// the DROP USER command
//
15320, 00000, "cannot drop user '%s' that has been assigned as the owner of one or more open files"
// *Cause: A SET OWNERSHIP command assigned this user as the owner of one
// or more files which were open at the time of assignment, and
// hence this user cannot be dropped due to possible
// inconsistencies in file ownerships.
// *Action: Restart all ASM client instances of the cluster in a rolling
// manner.
//
15321, 00000, "cannot set attribute with connected clients"
// *Cause: The disk group attribute could not be set because
// there were connected clients.
// *Action: Shut down connected clients and retry the command. Query the
// V$ASM_CLIENT fixed view in an ASM instance
// or use ASMCMD LSOF to list active clients.
15322, 00000, "cannot drop the owner '%s' of user group '%s' in disk group '%s'"
// *Cause: An attempt was made to drop the owner of a user group from the
// group's member list.
// *Action: Specify a user group member who is not the owner of the user group.
//
15323, 00000, "ASM password update has failed on local node"
// *Cause: A CREATE USER, ALTER USER, DROP USER, GRANT, or REVOKE
// command failed on the local node of the Automatic Storage
// Management (ASM) cluster.
// *Action: Check the ASM alert logs for more information.
//
15324, 00000, "requested operation is not allowed on the password file %s"
// *Cause: An attempt was made to run an operation that is not supported on
// password files.
// *Action: Specify a new file name or a file with the correct file type and
// retry the operation.
//
15325, 00000, "file %s is not a valid password file"
// *Cause: An attempt was made to open a file that had a type different from
// the password file.
// *Action: Specify correct password file name and retry the operation.
//
15326, 0000, "specified input %s is a not an ASM file"
// *Cause: The attributes could not be obtained as the specified input is
// either a disk group or a directory.
// *Action: Specify a valid Automatic Storage Management (ASM) file name.
//
15327, 0000, "remote ASM is not enabled"
// *Cause: An operation was requested that requires remote ASM to be enabled.
// *Action: Enable remote ASM.
//
15328, 0000, "user identification string '%s' exceeds limit of %s characters"
// *Cause: The user identification string provided for this operation
// exceeded the maximum number of characters allowed.
// *Action: Provide a user identification string of shorter length.
//
15329, 0000, "cluster identification string '%s' exceeds limit of %s characters"
// *Cause: The cluster identification string provided for this operation
// exceeded the maximum number of characters allowed.
// *Action: Provide a cluster identification string of shorter length.
//
15330, 0000, "ASM user name format requires COMPATIBLE.ASM of %s or higher"
// *Cause: The ASM user name format specified requires a higher disk group
// attribute value for COMPATIBLE.ASM.
// *Action: Set the disk group attribute COMPATIBLE.ASM to or above
// the requested version.
15331, 0000, "ASM proxy instance ORACLE_SID %s does not start with %s"
// *Cause: The ASM proxy instance was started with an invalid ORACLE_SID
// prefix.
// *Action: Start the ASM proxy instance with an ORACLE_SID that begins
// with the correct prefix.
//
15332, 0000, "ASM proxy instance cannot connect to an ASM server"
// *Cause: The ASM proxy instance could not find an ASM server to
// connect to during startup.
// *Action: Verify that an ASM server instance is running and accessible
// in the cluster and restart the proxy instance.
//
15333, 00000, "disk is not visible on client instance"
// *Cause: An ALTER DISKGROUP ADD DISK statement specified a disk that could
// not be discovered by all ASM client instances.
// *Action: Check the ASM alert logs for more information.
// Check operating system permissions for the device and the
// storage subsystem configuration.
//
15334, 00000, "VUBG process terminated with error"
// *Cause: The volume background process terminated with error.
// *Action: Warm start instance.
//
15335, 00000, "ASM metadata corruption detected in disk group '%s'"
// *Cause: A corruption was detected reading a block. It may be recoverable.
// *Action: The corruption could be the result of a storage problem, a
// configuration issue, or a software bug. Check the alert log for
// the result of the recovery attempt. If unsuccessful, contact Oracle
// Support Services with the incident information.
//
15336, 00000, "STRIPE_WIDTH cannot be set when STRIPE_COLUMNS equals 1"
// *Cause: An ADD VOLUME command specified a STRIPE_COLUMNS equal to 1 and
// specified the STRIPE_WIDTH argument.
// *Action: If striping is required, set STRIPE_COLUMNS to greater than 1. If
// striping is not required, do not set STRIPE_WIDTH.
//
15337, 00000, "invalid or missing database name"
// *Cause: You did not specify a valid database name for this command.
// *Action: Specify a valid database name.
//
15338, 00000, "ASM client instance %s reconnection refused"
// *Cause: The client was not found as an orphaned client and hence is not
// a legitimate candidate to reconnect to Oracle ASM.
// *Action: Shut down and restart the remote client to be considered as a
// new client in the cluster.
//
15339, 00000, "ASM client instance %s has been fenced by ASM"
// *Cause: Oracle ASM has already fenced this client.
// *Action: Shut down and restart the remote client to be considered as a
// new client in the cluster.
//
15340, 0000, "unable to create member cluster '%s'"
// *Cause: Creation of the member cluster failed.
// *Action: Check the alert logs and trace files of the Oracle ASM instance for
// more information on the reason for the failure, as well as checking
// the accompanying error messages.
//
15341, 0000, "unable to delete member cluster '%s'"
// *Cause: Deletion of the member cluster failed.
// *Action: Check the alert logs and trace files of the Oracle ASM instance for
// more information on the reason for the failure, as well as checking
// the accompanying error messages.
//
15342, 00000, "Internal ASM testing event number 15342"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: This event sets the total number of processes allowed to
// trace a disk failure.
//
15343, 0000, "Feature %s ASM is not enabled"
// *Cause: An operation was requested that requires Oracle Flex ASM to be enabled.
// *Action: Enable Oracle Flex ASM.
//
15344, 00000, "client %s not found"
// *Cause: The specified Oracle ASM client was not registered with this
// instance.
// *Action: Check the alert logs and trace files of the client for more
// information on the reason for the failure, as well as the
// accompanying error messages.
//
15345, 0000, "disconnected client instance(s) detected"
// *Cause: One or more ASM client instances were not connected to an
// ASM instance.
// *Action: Check that all of the ASM client instances are connected to an
// ASM instance and retry the operation.
//
15346, 00000, "process attempting to identify or create ASM file %s was aborted"
// *Cause: The client process attempting to identify or create the
// ASM file terminated or was interrupted.
// *Action: Correct the cause of the process interruption and retry the
// operation.
//
15347, 00000, "logical block size %s of ASM file '%s' is too small for disk group sector size %s"
// *Cause: An attempt was made to create a file on ASM whose logical
// block size was less than the sector size for the disk group.
// *Action: Check if the system configuration has changed. Correct the
// error and retry the operation.
//
15348, 00000, "ASMLIB misconfiguration error [%s]"
// *Cause: ASMLIB was found in more than one location.
// *Action: Check the configuration of ASMLIB and ensure that only one
// library is configured.
//
15349, 00000, "failed to set or get AFD_DISKSTRING parameter"
// *Cause: The operation failed because either Oracle Local Repository (OLR)
// was not available or AFD disk string attribute did not exist.
// *Action: Check that Oracle Clusterware is properly configured
// using 'ocrcheck -local' command.
//
15350, 00000, "invalid SYS_ASMFD_PROPERTIES parameter"
// *Cause: The parameter passed in for SYS_ASMFD_PROPERTIES was invalid.
// *Action: Pass in the correct parameter. Refer to the product documentation
// for a list of allowed parameter values.
//
15351, 00000, "I/O request issued to a sparse grid disk failed because the disk was out of space."
// *Cause: The sparse grid disk was out of space.
// *Action: Add more space to the disk group by adding more disks or add more
// space to existing disks by resizing them.
//
15352, 0000, "invalid client name %s specified"
// *Cause: The client name passed in was invalid.
// *Action: Pass in a valid client name. The valid client name is of format
// <instance name>:<dbunique name>:<cluster name> or
// <instance name>:<dbunique name>
//
15353, 00000, "disk '%s' cannot be added to disk group '%s'"
// *Cause: The disk type did not match the disk group sparse type.
// *Action: Ensure that the disk type matches the disk group sparse type.
//
15354, 0000, "failed to format grid disk \"%s\""
// *Cause: The grid disk format command failed.
// *Action: Check the grid disk logs and take corrective actions.
//
15355, 00000, "Internal ASM testing event number 15355"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: This event sets the configuration for read cancel.
//
15356, 00000, "Internal ASM testing event number 15356"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: This event sets the configuration for write cancel.
//
15357, 0000, "Can not create file \"%s\" on a sparse disk group"
// *Cause: An attempt was made to create fine-grained striping files on
// sparse disk groups. Fine-grained striping files cannot be created on
// sparse disk groups.
// *Action: Create the file on a regular disk group, or create a coarse-grained
// striping file on a sparse disk group.
//
15358, 0000, "query for materialized space to sparse grid disk \"%s\" of disk group \"%s\" has failed"
// *Cause: The query for materialized space to the cell server has failed.
// *Action: Check the ASM and cell alert logs and take corrective actions.
//
15359, 00000, "could not perform label scan operation"
// *Cause: An error occurred while scanning for ASM label.
// *Action: Look at the underlying errors on the error stack. Check other
// messages in the trace files for more information.
//
15360, 00000, "could not perform label filter operation"
// *Cause: An error occurred while setting AFD filter status.
// *Action: Look at the underlying errors on the error stack. Check other
// messages in the trace files for more information.
//
15361, 0000, "unable to find member cluster '%s'"
// *Cause: Looking up of the member cluster failed.
// *Action: Execute the 'asmcmd lscc' command to list all of the configured
// member clusters.
// If the member cluster listed in the message is not present, it
// might have been forcibly deleted. Refer to the product
// documentation for more information.
// If the member cluster listed in the message was present, contact
// Oracle Support Services.
//
15362, 0000, "invalid cluster name '%s' specified"
// *Cause: An invalid cluster name was supplied.
// *Action: Specify a cluster name which is at least one character but no more
// than 15 characters in length. The cluster name must be
// alphanumeric, it cannot begin with a numeric character, and it may
// contain hyphen (-) characters. However, it cannot end with a
// hyphen (-) character.
//
15363, 0000, "invalid version number '%s' specified"
// *Cause: The command did not specify a valid version number.
// *Action: Correct the version number in the command. It should be of the
// form #.#.#.#.# or other forms with fewer numbers delimited by
// a period.
//
15364, 00000, "member cluster version %s is incompatible with storage server version %s"
// Cause: The specified member cluster version was not supported by the Storage
// Server.
// Action: Upgrade or downgrade the storage server to a version that is
// compatible with member cluster and retry the operation.
// Install a member cluster using a supported version. Refer to
// product documentation for a complete list of supported releases.
//
15365, 00000, "member cluster '%s' already configured"
// Cause: The specified member cluster was already configured.
// Action: Execute the 'asmcmd lscc' command to list all of the configured
// member clusters. Reexecute the command with a member cluster name
// that has not already been configured.
//
15366, 0000, "unable to delete configuration for member cluster '%s' because the directory '%s' was not empty"
// *Cause: Deleting the member cluster configuration failed because some files
// were present.
// *Action: Deinstall the member cluster and rerun the command. If the command
// fails again, execute the 'asmcmd rmcc <member_cluster_name> -f'
// command to force deletion of the configuration for the member
// cluster.
//
15367, 00000, "member cluster '%s' not configured"
// Cause: The specified member cluster was not configured.
// Action: Execute the 'asmcmd lscc' command to list all of the configured
// member clusters. Reexecute the command with a member cluster name
// that is configured.
//
15368, 00000, "Oracle Cluster Registry operation failed with error %s.\n%s"
// Cause: This is an internal error.
// Action: Contact Oracle Support Services.
//
15369, 00000, "OCI invalid handle %s"
// Cause: An Oracle Call Interface (OCI) call returned the OCI_INVALID_HANDLE
// return code and did not store the error on the stack.
// Action: Contact Oracle Support Services.
//
15370, 00000, "database version needs to be 12.1 or higher to access a disk group number higher than 63"
// *Cause: An attempt was made to access a disk group number greater than 63
// with a database version lower than 12.1.
// *Action: Upgrade the database to version 12.1 or higher and
// retry the operation.
//
15371, 0000, "The command is not supported on a member cluster."
// *Cause: An attempt was made to run a command that is not supported on
// a member cluster.
// *Action: Rerun the command on the storage server.
//
15372, 0000, "Client version %s not supported by Oracle ASM"
// *Cause: The software version of the client is not supported by current
// release of the ASM software.
// *Action: Upgrade the client to the later release that is compatible
// with Oracle ASM and retry the operation. Refer to product
// documentation for a complete list of supported releases.
//
15373, 0000, "SYSDG, SYSKM, SYSRAC, and SYSBACKUP administrative privileges cannot be granted on an ASM instance."
// *Cause: An attempt was made to grant or revoke SYSDG, SYSKM, SYSRAC, or SYSBACKUP
// administrative privileges to a user on an ASM instance.
// *Action: Do not attempt to grant SYSDG, SYSKM, SYSRAC, or SYSBACKUP administrative privileges on
// an ASM instance.
//
15374, 00000, "invalid cluster configuration"
// *Cause: The client instance detected an invalid configuration.
// *Action: Install and configure Oracle Grid Infrastructure and retry the
// operation. Refer to product documentation for more information.
//
15375, 00000, "Physical sector size (%s) cannot be smaller than the logical sector size (%s)."
// *Cause: An attempt was made to create or modify a disk group with a physical
// sector size value smaller than its logical sector size value.
// *Action: Review the SQL statement and fix any discrepancies.
//
15376, 00000, "The existence of native disk '%s' does not allow disk group %s from changing sector sizes. Sector size of native disk is %s."
// *Cause: An attemp was made to change the physical or logical sector size
// value. Changing the sector size value is not allowed when there are
// native disks (physical sector equal to logical sector size) in the
// disk group, because this could cause invalid I/O operations.
// *Action: Drop the native disks or replace them for disks that support
// sector size emulation.
//
15377, 00000, "Block size (%s) for file '%s' is incompatible with the selected sector size (%s)."
// *Cause: The operation could not be completed because the sector size was
// incompatible for the specified file.
// *Action: Re-create or migrate the file to a block size that is compatible
// with the desired sector size, and redo the operation.
//
15378, 00000, "Grid Naming Service operation failed with error %s.\n%s"
// Cause: This is an internal error.
// Action: Check the accompanying error messages. Contact Oracle Support
// Services.
//
15379, 00000, "Cluster Credentials operation failed with error %s.\n%s"
// Cause: This is an internal error.
// Action: Check the accompanying error messages. Contact Oracle Support
// Services.
//
/============================================================================
/ 15380 - 15399 ASM File Group error messages
/============================================================================
15380, 00000, "invalid file group name specifier"
// *Cause: The file group name specified was invalid.
// *Action: Specify a valid file group name.
//
15381, 00000, "missing or invalid file group client specifier"
// *Cause: The command did not specify a valid file group client string.
// *Action: Specify a valid file group client string with alphanumeric
// characters.
//
15382, 00000, "invalid file group client name specifier"
// *Cause: The file group name specified was invalid.
// *Action: Specify a valid file group name.
//
15383, 0000, "invalid file group property '%s'"
// *Cause: An invalid property was specified for the ASM file group.
// *Action: Check documentation for valid ASM file group properties.
// The valid ASM file group property is of format
// <file type>.<property name> or
// <property name>
//
15384, 0000, "invalid file type '%s'"
// *Cause: An invalid file type was specified for the ASM file group property.
// *Action: Check documentation for valid ASM file types.
//
15385, 00000, "file group '%s' does not exist"
// *Cause: The specified file group did not exist within the disk group.
// *Action: Check the file group name and disk group name.
//
15386, 00000, "file group '%s' already exists in disk group '%s'"
// *Cause: A file group with the same name already exists.
// *Action: Select another file group name, or drop the existing file group.
// While creating non-CDB, multitenant container database (CDB),
// or pluggable database (PDB), manually create a file group for
// this non-CDB, multitenant container database (CDB), or pluggable
// database (PDB).
//
15387, 00000, "existing files are associated with file group '%s'"
// *Cause: An attempt was made to drop a file group that still contains
// existing files.
// *Action: Specify the CASCADE option to drop the file group and
// all of the associated files.
//
15388, 00000, "a file type cannot be specified for file group property '%s'"
// *Cause: The specified file group property affects the file group itself or
// all files in the file group, it is not specific to a type of file.
// *Action: Remove the file type from the name of the property.
//
15389, 00000, "missing or invalid file group property specification"
// *Cause: The command did not specify a valid file group property name
// or a valid file group property value.
// *Action: Specify a valid file group property name and value pair.
//
15390, 00000, "invalid value for file group property '%s'"
// *Cause: An invalid value was specified for the ASM file group property.
// *Action: Check documentation for acceptable values for this
// ASM file group property.
//
15391, 00000, "cannot drop the default file group"
// *Cause: The specified file group was created by the system and must
// always exist for proper operation.
// *Action: Select another file group name.
//
15392, 00000, "cannot alter the default file group"
// *Cause: The specified file group was created by the system and must
// hold the default values for proper operation.
// *Action: Select another file group name.
//
15393, 00000, "File number '%d' does not exist in file group '%s'."
// *Cause: The specified file did not exist within the file group.
// *Action: Check the file number and the file group number.
//
15394, 00000, "duplicate file group property '%s' specified"
// *Cause: A command specified the same file group property more than
// once for the same file type.
// *Action: Specify only one file group property for a file type.
//
15395, 00000, "file group redundancy incompatible with file type"
// *Cause: An attempt was made to move a file to a file group with an
// incompatible redundancy specification, or to change the
// redundancy specification of a file group in a way that is
// incompatible with existing files in that file group.
// *Action: Specify a valid redundancy property for the file group. Only
// write-once files, such as the offline archive log and backup
// set, support parity protection. Other types of files must be
// configured with an unprotected, mirror or high redundancy. The file
// group redundancy can be changed from a parity protection scheme to
// unprotected, mirror, or high, and conversely, as long as the file
// group does not contain any files.
//
15396, 00000, "command operates on only one file group property"
// *Cause: More than one file group property was specified in the ADD
// FILEGROUP or MODIFY FILEGROUP statement.
// *Action: Specify only one file group property per statement.
//
15397, 00000, "command requires all disks in disk group %s to be online"
// *Cause: The file group redundancy could not be changed to UNPROTECTED
// because some disks were offline.
// *Action: Retry the command after the offline disks are dropped.
//
15398, 00000, "file group property '%s' is read-only"
// *Cause: The specified file group property cannot be changed.
// *Action: Retry the command providing a non read-only file group property
//
15399, 00000, "new RDBMS compatibility (%s) exceeds client's RDBMS compatibility (%s)"
// *Cause: The specified value for COMPATIBLE.RDBMS attribute exceeds the
// COMPATIBLE setting for RDBMS for one or more clients.
// *Action: Verify the RDBMS compatibility for each client of this disk group.
//
/============================================================================
/ 15400 - 15439 ASM appliance error messages
/============================================================================
15400, 00000, "not running on supported ASM appliance"
// *Cause: An attempt was made to initialize the server code as an appliance
// when it was not running a supported appliance configuration.
// *Action: Check the appliance configuration and retry the operation.
//
15401, 00000, "command not supported on ASM appliance '%s'"
// *Cause: An attempt was made to run an operation that is not supported by
// the specified appliance.
// *Action: Check the documentation to see which operations are allowed or
// disallowed for the specified appliance.
//
15402, 00000, "insufficient number of disks to support ASM appliance '%s'"
// *Cause: An attempt was made to do an operation that resulted in insufficient
// number of disks required for the specified appliance.
// *Action: Check the appliance configuration and retry the operation after
// inserting disks in the appropriate slots.
//
15403, 00000, "unable to read an ASM appliance configuration file"
// *Cause: Oracle ASM was unable to read an appliance configuration file.
// *Action: Check the operating system error messages to determine the
// identity of the configuration file. Then, fix the
// configuration file.
//
15404, 00000, "Oracle ASM could not add disk \"%s\" to disk group \"%s\" on appliance %s"
// *Cause: There were too many dropping or offline disks in the specified
// disk group.
// *Action: Wait for the drop and rebalance operations to complete, or
// online the offline disks and wait for the online to complete.
// Then, retry the operation.
//
15405, 00000, "Slot %s in Oracle ASM appliance '%s' contains more than one disk"
// *Cause: An attempt was made to add a disk to a slot in the ASM appliance that
// already had a disk (possibly OFFLINE) associated with it.
// *Action: Use FORCE to drop the disk that exists in the specified slot. Then,
// retry the operation.
//
15406, 00000, "ASM disk %s is being replaced."
// *Cause: An attempt was made to either online or replace a disk that was
// already being replaced, probably by another instance.
// *Action: Change the ONLINE statement to exclude the disk.
//
15407, 00000, "Disk specification '%s' matches multiple disks."
// *Cause: More than one disk is discovered matching the specified disk string.
// *Action: Change the disk string to specify one and only one disk.
//
15408, 00000, "Replacement disk '%s' for '%s' must be at least %s MB."
// *Cause: The replacement disk must be at least of the same size of the old
// disk.
// *Action: Use a larger physical disk to replace.
//
15409, 00000, "All disks in disk group %s are not of the same type."
// *Cause: An attempt was made to add disks of a different type to the disk
// group under appliance mode.
// *Action: Check if all the disks in the disk group are of the same type. Do
// not add flash and hard disks to the same disk group.
//
15410, 00000, "Disks in disk group %s do not have equal size."
// *Cause: The disks in the disk group were not of equal size.
// *Action: Ensure that all disks in the disk group are of equal size. If
// adding new disks to the disk group, their size must be equal to
// the size of the existing disks in the disk group. If resizing, all
// disks in the disk group must be resized to the same size.
//
15411, 00000, "Failure groups in disk group %s have different number of disks."
// *Cause: An attempt was made to enable appliance mode with a different
// number of disks in each failure group.
// *Action: Check if all failure groups have an equal number of disks and try
// again.
//
15412, 00000, "Operation on disk group %s is incompatible under appliance mode."
// *Cause: An attempt was made to do an operation that resulted in dropping
// all disks in a failure group or creating a new failure group.
// *Action: Disable appliance mode, perform the operation and reenable
// appliance mode.
// WARNING: To reenable appliance mode, ensure the following
// constraints are met:
// * There are a sufficient number of disks in each failure group.
// * All failure groups have an equal number of disks.
// * There are no offline disks in the disk group.
// * Every disk in the disk group is of the same type (flash or
// hard disk).
// * All disks in the disk group have an equal size.
//
15413, 00000, "Appliance mode is disabled."
// *Cause: Appliance mode could not be set because it was explicitly disabled.
// *Action: Enable appliance mode and appliance partnering parameters.
//
15414, 00000, "Appliance mode requires at least %s failure groups and either %s or %s disks in all failure groups."
// *Cause: Appliance mode could not be enabled because it did not meet the
// minimum requirements.
// *Action: Check if there are sufficient failure groups and a sufficient
// number of disks in each failure group.
//
15415, 00000, "could not retrieve appliance properties for disk group %s"
// *Cause: Some of the appliance properties were invalid. This could be due
// to a cell software downgrade after setting the 'appliance.mode'
// attribute.
// *Action: Check the cell software on all of the cells or disable appliance
// mode.
//
15416, 00000, "ASM disk %s in disk group %s is offline."
// *Cause: An offline disk prevented the current ADD or DROP operation.
// *Action: Drop the offline disk or online the offline disk or disable
// appliance mode.
//
15417, 00000, "relocation must be retried"
// *Document: NO
// *Cause: A relocation has to be retried due to a transient condition.
// *Action: Internal event.
//
15418, 00000, "Appliance mode is not supported for compatible.asm %s."
// *Cause: Appliance mode could not be enabled for the current value of
// the compatible.asm attribute.
// *Action: Disable appliance mode if it is enabled or advance compatible.asm
// to a version that supports appliance mode.
//
15419, 00000, "disk group %s is not mounted in restricted mode"
// *Cause: The specified disk group was not mounted in restricted mode
// prohibiting the requested operation.
// *Action: Dismount the disk group, remount it in restricted mode
// and retry the operation.
//
15420, 00000, "Operation on disk group %s is disabled."
// *Cause: The current operation could not be completed because the disk group
// is in the middle of an appliance migration.
// *Action: Wait for the migration to complete and then retry the command.
//
15421, 00000, "%s is not supported when the disk group is mounted for recovery."
// *Cause: The disk group was mounted for recovery preventing the requested
// operation.
// *Action: Dismount the disk group, remount it in normal mode and retry the
// operation.
//
15422, 00000, "Disks '%s' and '%s', in failure group '%s' of disk group '%s', do not belong to the same cell"
// *Cause: It was detected that disks from different cells belong to the same
// failure group.
// *Action: Make the necessary disk swaps so only disks from the same cell
// belong to the same failure group.
//
15423, 00000, "Disk '%s' in failure group '%s' and disk '%s' in failure group '%s' of disk group '%s' belong to the same cell"
// *Cause: It was detected that disks from the same cell belong to different
// failure groups.
// *Action: Make the necessary disk swaps so disks from the same cell are not
// shared between different failure groups.
//
15424, 00000, "relocation must be restarted"
// *Document: NO
// *Cause: A relocation has to be restarted due to a transient condition.
// *Action: Internal event.
//
/============================================================================
/ 15430 - 15439 ASM Flex Disk Group Quota Group Messages
/============================================================================
15430, 00000, "missing or invalid quota group name"
// *Cause: The command did not specify a valid quota group name.
// *Action: Specify a valid quota group name.
//
15431, 00000, "missing or invalid quota group property"
// *Cause: The command did not specify a valid quota group property.
// *Action: Specify a valid quota group property.
//
15432, 00000, "missing or invalid quota"
// *Cause: The command did not specify a valid quota limit for the quota
// group.
// *Action: Specify a valid quota limit.
//
15433, 00000, "missing or invalid file group name"
// *Cause: The command did not specify a valid file group name.
// *Action: Specify a valid file group name.
//
15434, 00000, "quota group %s already exists in disk group %s"
// *Cause: The specified quota group already existed in the disk group.
// *Action: Specify a different quota group name.
//
15435, 00000, "quota group %s does not exist in disk group %s"
// *Cause: The specified quota group did not exist in the disk group.
// *Action: Specify a valid quota group name.
//
15436, 00000, "invalid operation on quota group %s"
// *Cause: The specified operation was not permitted on the quota group.
// *Action: Check the quota group specified in the command.
//
15437, 00000, "Not enough quota available in quota group %s."
// *Cause: The specified quota group did not have sufficient quota available
// to permit the operation.
// *Action: Specify a quota group with sufficient available quota or increase
// the quota limit of the specified quota group.
//
15438, 00000, "Quota group %s has one or more file groups associated."
// *Cause: One or more file groups were associated with the specified quota
// group and, therefore, the operation was not permitted.
// *Action: Drop the file groups or move the file groups to a different quota
// group.
//
/============================================================================
/ 15440 - 15499 ASM Volume Messages
/============================================================================
15440, 00000, "VIO0 process terminated with error"
// *Cause: A volume IO background process terminated with error.
// *Action: Wait for the process to restart.
//
15441, 00000, "Internal ASM testing event number 15441"
// *Document: NO
// *Cause: Set this event only under the supervision of Oracle development.
// *Action: The level controls which ASM rebalance phase must be skipped.
//
15442, 00000, "The ASM rebalance phase %s does not exist."
// *Cause: The specified ASM rebalance phase did not exist.
// *Action: Specify a valid rebalance phase.
//
15443, 00000, "The ASM rebalance phase %s cannot be skipped."
// *Cause: The specified ASM rebalance phase cannot be skipped.
// *Action: Specify a valid rebalance phase to skip.
//
15444, 00000, "Volume %s needs to be online and mounted to complete the operation."
// *Cause: The operation could not be completed with the volume offline or
// dismounted.
// *Action: Online or mount the volume and retry the operation.
//
15445, 00000, "Volume %s does not allow sector size migration."
// *Cause: Sector size migration was not allowed because Oracle ACFS accelerator
// volumes, volumes associated with an Oracle ACFS accelerator, or non
// Oracle ACFS volumes exist in the disk group.
// *Action: Move the volume to a different disk group and retry the operation.
//
//15446 available
//15447 available
//15448 available
//15449 available
15450, 00000, "invalid volume name specifier"
// *Cause: The volume name specified was invalid
// *Action: Specify a valid volume name.
//
15451, 00000, "missing or invalid volume size specifier"
// *Cause: The volume size specified was invalid.
// *Action: Specify a valid volume size.
//
15452, 00000, "missing or invalid stripe width specifier"
// *Cause: The volume stripe width specified was invalid.
// *Action: Specify a valid volume stripe width.
//
15453, 00000, "invalid STRIPE_COLUMNS specifier"
// *Cause: An ADD VOLUME command did not specify a valid number of stripe
// columns.
// *Action: Specify a valid number of stripe columns.
//
15454, 00000, "ALTER DISKGROUP ALL cannot use single volume names"
// *Cause: An ALTER DISKGROUP ALL command specified a single volume or
// a list of volumes
// *Action: Use the ALL keyword when specifying volumes on multiple diskgroups.
//
15455, 00000, "FORCE option cannot be used when specifying ALL volumes"
// *Cause: The FORCE option was used to disable ALL volumes.
// *Action: Use FORCE option to disable one volume at a time.
//
15456, 00000, "missing or invalid volume usage specifier"
// *Cause: The command did not specify a valid volume usage string.
// *Action: Specify a valid volume usage string with alphanumeric characters.
//
15457, 00000, "first letter of the volume name is not alphabetic"
// *Cause: A volume name was specified with a nonalphabetic first character.
// *Action: Set the first character of the volume name to be alphabetic.
//
15458, 00000, "invalid character in volume name"
// *Cause: A volume name was specified with an invalid character.
// *Action: Use a volume name with only alphanumeric characters.
//
15459, 00000, "STRIPE_WIDTH of %s is not a power of two"
// *Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was not
// a power of two.
// *Action: Select a STRIPE_WIDTH that is a power of two; for example,
// 4K, 8K, etc.
//
15460, 00000, "volume name '%s' is already in use"
// *Cause: An ADD VOLUME command specified a volume name that
// was already used by another volume.
// *Action: Select a different name for the volume.
//
15461, 00000, "STRIPE_WIDTH of %s bytes is less than the minimum of %s bytes"
// *Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was too
// small.
// *Action: Select a larger STRIPE_WIDTH.
//
15462, 00000, "STRIPE_WIDTH of %s bytes is greater than the maximum of %s bytes"
// *Cause: An ADD VOLUME command specified a STRIPE_WIDTH that was too
// large.
// *Action: Select a smaller STRIPE_WIDTH.
//
15463, 00000, "volume size of %sK is less than the minimum of %sM"
// *Cause: The volume size specified was too small.
// *Action: Select a larger volume size.
//
15464, 00000, "STRIPE_COLUMNS of %s is greater than the maximum of %s"
// *Cause: An ADD VOLUME command specified a STRIPE_COLUMNS that was that
// was too large.
// *Action: Select a smaller STRIPE_COLUMNS value.
//
15465, 00000, "STRIPE_COLUMNS of %s is less than the minimum of %s"
// *Cause: An ADD VOLUME command specified a STRIPE_COLUMNS that was too
// small.
// *Action: Select a larger STRIPE_COLUMNS value.
//
15466, 00000, "volume '%s' in disk group '%s' does not exist"
// *Cause: The command specified a volume name that does not exist.
// *Action: Ensure a valid volume name is used.
//
15467, 00000, "volume operation is already in progress"
// *Cause: Another command was currently operating on a volume.
// *Action: Wait a short time before retrying the command.
//
15468, 00000, "volume '%s' in diskgroup '%s' is currently being accessed"
// *Cause: An attempt was made to communicate with the volume driver.
// The volume was being accessed by another application and,
// therefore, could not be changed.
// *Action: Shut down all applications that might be accessing
// this volume and then retry the command.
//
15469, 00000, "VBG process terminated with error"
// *Cause: A volume background process terminated with error.
// *Action: Wait for process to restart.
//
15470, 00000, "VDBG process terminated with error"
// *Cause: The volume driver background process terminated with error.
// *Action: Warm start instance.
//
15471, 00000, "volume redundancy incompatible with disk group redundancy"
// *Cause: An ADD VOLUME command specified a volume redundancy that was
// incompatible with the redundancy of the disk group.
// *Action: Specify a valid volume redundancy. An unprotected
// redundancy volume cannot be added to a normal or high
// redundancy disk group, and a mirror or high redundancy
// volume cannot be added to an external redundancy disk group.
//
15472, 00000, "volume library cannot be loaded. Platform may not support volume creation."
// *Cause: The volume library could not be loaded. Either the platform
// does not support volume operations, or there is a problem with
// the library.
// *Action: Ensure that the platform supports volumes. If the platform does
// support volumes, check the alert log for library loading failure
// information.
//
15473, 00000, "access to a volume's storage through an unsupported interface"
// *Cause: An attempt was made to access or modify a volume's storage through
// an unsupported interface.
// *Action: Use supported interfaces for access to volume devices.
//
15474, 00000, "volume name is greater than %s characters"
// *Cause: An ADD VOLUME command specified a volume name that was too long.
// *Action: Select a smaller volume name.
//
15475, 00000, "usage string is greater than %s characters"
// *Cause: The usage string specified was too long.
// *Action: Select a smaller usage string.
//
15476, 00000, "ACFS volumes must be resized with the 'acfsutil size' operating system command."
// *Cause: An attempt was made using SQL to resize an ADVM volume that
// contains an ACFS file system.
// *Action: Use the 'acfsutil size' operating system command to resize
// the volume.
//
15477, 00000, "cannot communicate with the volume driver"
// *Cause: An attempt was made to communicate with the volume driver.
// *Action: Check that the ASM volume driver is loaded. If so, check the alert
// log to identify the reason for failure and take necessary action
// to prevent such failures in the future.
//
15478, 00000, "ACFS process terminated with error"
// *Cause: The ACFS background process terminated with error
// *Action: Wait for process restart
//
15479, 00000, "ASM diskgroup does not support volumes"
// *Cause: Volumes were not supported. A common example
// is having disks, such as NFS, in the diskgroup that are not
// supported by volumes.
// *Action: Remove unsupported disks in the diskgroup.
//
15480, 00000, "error reported in the ASM volume driver"
// *Cause: An error was reported in the ASM volume driver.
// *Action: Check the operating system log files to identify the reason for
// the failure and take necessary action to prevent such failures
// in the future.
//
15481, 00000, "missing or invalid volume mountpath specifier"
// *Cause: A invalid volume mountpath string was specified.
// *Action: Specify a valid volume mountpath string with alphanumeric characters.
//
15482, 00000, "failed to create/remove device file for volume %s on diskgroup %s"
// *Cause: Improper driver installation.
// *Action: Check the alert log for device file creation failure information.
// Reload the driver using the supported installation method.
//
15483, 00000, "volume driver version is not compatible with the ASM instance"
// *Cause: The version of the ASM volume driver was not supported by ASM.
// *Action: Update the volume driver or the ASM instance.
//
15484, 00000, "volume '%s' contains %s error(s)"
// *Cause: Errors were returned by the ALTER DISKGROUP CHECK VOLUME command.
// *Action: See the alert log for details of the errors.
//
15485, 00000, "number of volumes in diskgroup exceeds the maximum of %s"
// *Cause: A volume was added on a diskgroup that already contained the maximum number allowed.
// *Action: Remove volumes on the diskgroup.
//
15486, 00000, "internal error while altering volume"
// *Cause: An internal ASM error occurred while altering a volume.
// *Action: See the alert log for details of the error.
//
15487, 00000, "cannot shutdown the ASM instance with an open ASM volume"
// *Cause: One or more ASM volumes were found to be open during shutdown.
// *Action: Close the ASM volume and retry the shutdown.
//
15488, 00000, "volume %s is open on instance %s"
// *Cause: ASM volume was not closed prior to instance termination
// on node specified.
// *Action: Close the ASM volume either via unmount or node restart and
// retry the operation
//
15489, 00000, "conflicting volume already open on this node"
// *Cause: An ASM volume was not closed prior to instance shutdown
// on node specified. It is conflicting with the volume that
// is to be enabled.
// *Action: Close the ASM volume either via unmount or node restart and
// retry the operation.
//
15490, 00000, "not all instances could add/drop the volume"
// *Cause: The ASM volume cannot be added/dropped on all instances.
// *Action: See the alert log for the reason the volume could not be
// added/droped.
//
15491, 00000, "volume redundancy conflicts with disk region options"
// *Cause: Non-mirrored volumes erroneously contained the MIRRORHOT or
// MIRRORCOLD keyword.
// *Action: Remove the MIRRORHOT or MIRRORCOLD keywords from non-mirrored
// volumes.
15492, 00000, "command or option incompatible with ASM volumes"
// *Cause: An attempt was made to use a feature which is not
// compatible with existing ASM volumes. A common example is
// adding a disk to the diskgroup that is unsupported by ASM
// volumes.
// *Action: Omit the option from the command.
15493, 00000, "target ADVM compatibility (%s) exceeds ASM compatibility (%s)"
// *Cause: An attempt was made to advance ADVM compatibility beyond
// the disk group's ASM compatibility.
// *Action: Advance ASM compatibility before advancing ADVM compatibility.
15494, 00000, "compatible.advm must be %s or higher"
// *Cause: An attempt was made to set the ADVM compatibility to a version
// that was lower than the minimum supported.
// *Action: Set ADVM compatibility to at least the minimum supported
// version.
15495, 00000, "ASM operation requires compatible.advm of %s or higher"
// *Cause: The ASM operation specified required a higher disk group
// attribute value for compatible.advm.
// *Action: Set the disk group attribute compatible.advm to or above the
// requested version.
15496, 00000, "volume size is greater than the maximum of %sT"
// *Cause: The volume size specified was too large.
// *Action: Select a smaller volume size.
15497, 00000, "Volume %s uses a metadata block size (%s) smaller than the specified sector size (%s)."
// *Cause: The Oracle ACFS volume had a metadata block size incompatible with
// the specified sector size.
// *Action: Migrate Oracle ACFS to a larger metadata block size before changing
// the sector size.
15498, 00000, "Volume name '%s' would collide with existing volume(s) '%s %s'."
// *Cause: A volume name was specified that would conflict with existing
// volume device(s). A volume '<vol_name>-<dg_num>' is the name of the
// block device. Additionally, a raw device named
// 'r<vol_name>-<dg_num>' is also created. Since that name already
// existed, a name collision occurred.
// *Action: Choose another name for the volume (no leading 'r' is recommended).
15499, 00000, "Volume Membership (VMB) process terminated with error"
// *Cause: The volume driver background process terminated with error.
// *Action: Warm start the instance.
//
/ End messages for Automatic Storage Management. New range :
/ 59000 - 59999 Reserved for Automatic Storage Management (e57000.msg)
/=============================================================================
/
/===============================================================================
/ 15500 - 15999 Reserved for Server Manageability Layer
/
/ 15500-15599 Reserved for Workload Capture and Replay (KEC)
/ 15600-15649 Reserved for Automated Maintenance Tasks (KET)
/ 15650-15699 Reserved for Direct Access to Fixed Tables
/ 15700-15749 Reserved for SQL Tuning Advisor, SQL Tuning Set and SQL
/ Performance Analyzer (STA/STS/SPA)
/===============================================================================
/
/ 15500 - 15599 reserved for Workload Capture and Replay (KEC)
/
15500, 00000, "Reserved for Workload Capture and Replay tracing"
// *Document: NO
// *Cause:
// *Action:
//
15501, 00000, "cannot start workload capture on instance %s"
// *Cause: Given instance encountered unexpected errors while trying
// to start the workload capture.
// *Action: Check the alert log and other diagnostics in the given
// instance to diagnose the problem.
//
15502, 00000, "cannot stop workload capture on instance %s"
// *Cause: Given instance encountered unexpected errors while trying
// to stop the workload capture.
// *Action: Check the alert log and other diagnostics in the given
// instance to diagnose the problem.
//
15503, 00000, "cannot startup instance when procedures in \"DBMS_WORKLOAD_CAPTURE\" or \"DBMS_WORKLOAD_REPLAY\" are in the middle of their execution"
// *Cause: The new instance could not be started because the database
// was executing a procedure in either the DBMS_WORKLOAD_CAPTURE
// or DBMS_WORKLOAD_REPLAY package.
// *Action: Start the new instance after such procedures in the
// given packages have finished execution.
//
15504, 00000, "cannot start workload capture because instance %s not present in RESTRICTED SESSION mode"
// *Cause: The NO_RESTART_MODE option in DBMS_WORKLOAD_CAPTURE.START_CAPTURE
// was FALSE, therefore all the active instances were expected to be
// in the RESTRICTED SESSION mode.
// *Action: Start all instances using STARTUP RESTRICT or
// execute ALTER SYSTEM ENABLE RESTRICTED SESSION on all active
// instances before issuing DBMS_WORKLOAD_CAPTURE.START_CAPTURE.
//
15505, 00000, "cannot start workload capture because instance %s encountered errors while accessing directory \"%s\""
// *Cause: Given instance could not access the specified CAPTURE directory
// or the specified CAPTURE directory already had a workload capture
// in it.
// *Action: Provide a directory object that is valid, empty and
// accessible from all the instances in the database cluster.
//
15506, 00000, "cannot prepare instance %s for replay"
// *Cause: Given instance encountered unexpected errors while trying
// to prepare for a workload replay.
// *Action: Check the alert log and other diagnostics in the given
// instance to diagnose the problem.
//
15507, 00000, "cannot start workload replay on instance %s"
// *Cause: Given instance encountered unexpected errors while trying
// to start a workload replay.
// *Action: Check the alert log and other diagnostics in the given
// instance to diagnose the problem.
//
15508, 00000, "cannot cancel workload replay on instance %s"
// *Cause: Given instance encountered unexpected errors while trying
// to cancel a workload replay.
// *Action: Check the alert log and other diagnostics in the given
// instance to diagnose the problem.
//
15509, 00000, "workload replay has been cancelled"
// *Cause: Workload replay was cancelled.
// *Action: Restart the workload replay.
//
15510, 00000, "cannot perform operation when \"STATISTICS_LEVEL\" is \"BASIC\""
// *Cause: The STATISTICS_LEVEL initialization parameter was set to BASIC.
// *Action: Change the STATISTICS_LEVEL initialization parameter setting to either TYPICAL or ALL.
//
15511, 00000, "cannot process workload capture because no user sessions were recorded"
// *Cause: No user sessions were recorded in the given workload capture.
// Processing this capture failed because no user workload was
// captured.
// *Action: Capture a workload in which at least one user session connects and
// performs some operations.
//
15512, 00000, "directory \"%s\" does not contain a valid processed workload capture"
// *Cause: One or more files created by DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE
// were missing.
// *Action: Process the workload capture using DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE
// and then retry the command.
//
15513, 00000, "cannot access the input directory"
// *Cause: Given input directory is either invalid or inaccessible.
// *Action: Verify that the input directory is valid and accessible
// and then retry the command.
//
15514, 00000, "cannot find a match for the remote procedure call during replay"
// *Cause: The corresponding PL/SQL program was either dropped or modified.
// *Action: Verify that the corresponding PL/SQL program is defined the same
// way during replay as it was defined during workload capture.
//
15515, 00000, "error while replaying remote procedure call: \"%s.%s.%s\""
// *Cause: Error encountered during the replay of a remote procedure call.
// *Action: Correct the cause of the preceding error and restart workload replay.
//
15516, 00000, "parallel preprocessing worker hit error ORA-%s"
// *Cause: One of the parallel preprocessing workers died unexpectedly while
// processing the workload.
// *Action: Find the root cause or simply preprocess the workload using only
// one process.
//
15517, 00000, "cannot start parallel preprocessing worker"
// *Cause: One of the parallel preprocessing workers could not be started.
// *Action: Find the root cause or simply preprocess the workload using only
// one process.
//
15518, 00000, "parallel preprocessing encountered an unexpected error"
// *Cause: An unexpected error occurred during parallel preprocessing.
// *Action: Find the root cause or simply preprocess the workload using only
// one process.
//
15519, 00000, "cannot access database link \"%s\" because it is disabled"
// *Cause: For security considerations, access to external databases via
// database links were disabled during workload replay.
// *Action: Use advanced parameter for Database Replay to enable
// database links during workload replay.
//
15520, 00000, "Directory is corrupted. Two WMD files are found at \"%s\" and \"%s\""
// *Cause: Two WMD files were found in the directory.
// *Action: Check that the WMD files in capture directory were not modified,
// moved, duplicated or deleted.
//
15521, 00000, "failed to create file \"%s\" during workload processing"
// *Cause: An attempt was made to create a file during workload processing
// without the proper file permissions.
// *Action: Correct the file permissions and try again.
//
15522, 00000, "failed to generate a workload capture subset: \"%s\""
// *Cause: An attempt to generate a workload capture subset failed.
// Possible reasons are included in the error message.
// *Action: Correct the issue and try again.
//
15523, 00000, "failed to create subpath \"%s\" under path \"%s\""
// *Cause: Either the path does not exist or is inaccessible or the subpath
// specification is invalid.
// *Action: Verify that the path exists and is accessible, the subpath
// specification is valid, and retry the command.
//
15524, 00000, "force an idle session to flush in-memory captured data upon finish_capture()"
// *Document: NO
// *Cause: Idle sessions might lose in-memory workload capture data when
// the capture is about to finish.
// *Action: No external action; used internally.
//
15525, 00000, "a user call cannot be replayed because not enough information was captured; extra details: %s"
// *Cause: An attempt to replay a user call failed because the workload was
// captured with an old version of Oracle. The information needed for
// replay was not recorded.
// *Action: Capture the workload using a newer version of Oracle or use the
// replay filters to skip the user call.
//
15526, 00000, "failed to validate user password for capture"
// *Cause: One of the following occurred:
// 1- The password was not specified for the encrypted capture.
// 2- The password did not match the one used for the encrypted
// capture.
// 3- The specified password was for an unencrypted capture.
// *Action: For scenario 1 or 2 stated in the Cause, provide the correct
// password for the encrypted capture. For scenario 3, do not
// specify the client single sign-on (SSO) wallet path.
//
15527, 00000, "failed to retrieve password for Database Replay from Oracle Wallet"
// *Cause: Either the Database Replay identifier was not found in the Oracle
// wallet or the password was not set.
// *Action: Set the password for Database Replay identifier in the Oracle
// wallet.
//
15528, 00000, "failed to encrypt a workload capture: \"%s\""
// *Cause: An attempt to encrypt a workload capture failed.
// Possible reasons are included in the error message.
// *Action: Fix the issue and retry.
//
15529, 00000, "failed to decrypt a workload capture: \"%s\""
// *Cause: An attempt to decrypt a workload capture failed.
// Possible reasons are included in the error message.
// *Action: Fix the issue and retry.
//
15551, 00000, "workload replay client cannot connect to database server"
// *Cause: The server connection identifier was invalid.
// *Action: Restart the client with correct server connection identifier.
//
15552, 00000, "workload replay client cannot login to database server"
// *Cause: 1) the replay client used an invalid username or password;
// 2) the replay user does not have the privilege to switch user;
// 3) the recorded username does not exist in the replay database.
// *Action: 1) restart replay client with correct username and password
// 2) grant user switching prvilege to the replay user
// 3) verify whether the replay database was restored properly
//
15553, 00000, "workload replay client cannot execute the DBMS_WORKLOAD_REPLAY package"
// *Cause: Workload Replay Client's replay user did not have EXECUTE
// permission on the DBMS_WORKLOAD_REPLAY package.
// *Action: Grant execute permission on the DBMS_WORKLOAD_REPLAY package
// to replay user and restart the Workload Replay Client.
//
15554, 00000, "cannot start workload replay client because the database server is not in PREPARE mode"
// *Cause: The Workload Replay Client could not connect to the database
// server because the database server was not in the PREPARE mode.
// *Action: Put the database in PREPARE mode by using
// DBMS_WORKLOAD_REPLAY.PREPARE_REPLAY, and restart the
// Workload Replay Client.
//
15555, 00000, "workload replay client encountered unexpected error: \"%s\""
// *Cause: Workload Replay Client encountered an unexpected error.
// *Action: Check the Workload Replay Client's log files and the database
// server alert log to diagnose the problem.
//
15556, 00000, "invalid input specified to the workload replay client; type 'wrc HELP=Y' for help"
// *Cause: Invalid input was specified.
// *Action: Use the Workload Replay Client's HELP=Y option to know more about
// valid input options.
//
15557, 00000, "workload replay client cannot access the replay directory or the database version do not match the preprocessing one"
// *Cause: The Workload Replay Client could not access the directory that
// contained the workload to be replayed, or the workload was
// preprocessed by a different version of the database.
// *Action: Restart the workload replay after specifying the correct
// replay directory, or preprocess it with the correct database.
//
15558, 00000, "replay thread encountered unexpected error"
// *Cause: A single replay thread got disconnected from the server due to an unexpected error.
// *Action: Check the Workload Replay Client's log files and the database
// server alert log to diagnose the problem.
//
15559, 00000, "workload replay client cannot open workload capture file"
// *Cause: The Workload Replay Client could not access one or more workload
// capture files from the replay directory.
// *Action: Restart the workload replay after copying all the workload
// capture files to the replay directory.
//
15560, 00000, "workload replay client cannot access the work directory"
// *Cause: The Workload Replay Client could not access the work directory to
// write log files for debug information.
// *Action: Restart the Workload Replay Client after specifying the correct
// work directory.
15561, 00000, "workload replay client cannot connect to the remapped connection with conn_id : %s"
// *Cause: The specified connection is invalid or the specified host
// is inaccessible.
// *Action: Test the specified connection using other methods and redefine
// the connection remapping, if necessary. Consult the view
// DBA_WORKLOAD_CONNECTION_MAP to inspect connection remappings.
//
15562, 00000, "workload replay client cannot read the DBA_WORKLOAD_CONNECTION_MAP view"
// *Cause: The DBA_WORKLOAD_CONNECTION_MAP view did not exist or
// was not accessible.
// *Action: Re-create the workload capture and replay views. For additional
// information, see the documentation.
//
15563, 00000, "workload replay client cannot spawn new threads"
// *Cause: The Workload Replay Client does not have enough resource (CPU or memory)
// to spawn new threads.
// *Action: Restart the workload replay after allocating more resource
// (CPU and memory) to the Workload Replay Client or use
// more hosts as replay clients to drive the workload.
//
15564, 00000, "contents of the replay directory provided to the workload replay client do not match with the replay directory provided to the database server"
// *Cause: The processed workload capture files given to the workload replay
// client directory did not match the contents of the replay directory
// given as input to DBMS_WORKLOAD_REPLAY.INITIALIZE_REPLAY.
// *Action: Provide the same processed workload capture files to both the
// database server and all the workload replay clients and restart the
// replay. If the same workload capture files were processed more
// than once, provide a copy of the latest processed workload
// capture files to all the workload replay clients and the
// database server.
//
15566, 00000, "workload replay client cannot replay user call in the current version"
// *Cause: The workload replay client encountered a user call in the
// captured workload that was not supported for replay in the current version.
// *Action: Look in the DBA_WORKLOAD_REPLAY_DIVERGENCE view for details about the call
// that encountered this error. Refer to the documentation for more
// details on the types of workload that are not supported in the
// current version.
//
15567, 00000, "replay user %s encountered an error during a sanity check"
// *Cause: The replay user encountered an error when accessing internal objects
// for Database Replay or switching user.
// *Action: Set up the replay user appropriately at the replay database. Ensure
// that the replay user can access SYS-owned objects and has been
// granted the BECOME USER privilege.
//
15568, 00000, "login of user %s during workload replay failed with ORA-%s"
// *Cause: The recorded user did not exist in the replay database or encountered
// other problems during log in.
// *Action: Check the returned error number and set up the recorded user
// appropriately at the replay database.
//
15569, 00000, "timeout encountered during the replay of a recorded user call"
// *Cause: The replay of a recorded user call was terminated since it was
// significantly slower than the workload capture.
// *Action: Find the root cause for the performance issue. Or, use
// DBMS_WORKLOAD_REPLAY API to disable the timeout check if the
// replay is expected to be slower.
//
15570, 00000, "Directory object \"%s\" does not exist."
// *Cause: The directory object did not exist.
// *Action: Ensure that the specified directory object exists.
//
15590, 00000, "encountered incomplete workload capture files"
// *Cause: The captured workload contained one or more incomplete recording
// files. This can happen when the original workload capture's
// FINISH_CAPTURE command timed out while waiting for all the active
// sessions to close their workload capture files.
// *Action: Incomplete capture files will not interfere with the processing
// and replaying of the captured workload. This is simply a warning
// message to point out that some database calls might not have been
// recorded due to FINISH_CAPTURE command timing out. For a list
// of the incomplete files, check the alert log for lines containing
// DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE after capture processing.
//
15591, 00000, "encountered corrupt workload capture files"
// *Cause: The captured workload contained one or more corrupt recording
// files.
// *Action: For a list of the incomplete files, check the alert log for
// lines containing DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE after
// capture processing. The corrupt files will be replayed up to the
// point of the corruption. Alternatively, it is possible to
// remove the corrupt files and run
// DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE again. In this case, no
// workload from the corrupt files will be replayed.
//
15599, 00000, "Last message reserved for WCR (KEC)"
// *Document: NO
// *Cause:
// *Action:
//
/
/ 15600 - 15649 reserved for Automated Maintenance Tasks (KET)
/
15600, 00000, "Reserved for Automated Maintenance Tasks"
// *Document: NO
// *Cause:
// *Action:
//
/
15601, 00000, "Invalid value specified for parameter \"%s\""
// *Cause: An invalid value was specified for the given parameter.
// *Action: Correct the value being specified for the parameter.
/
15602, 00000, "Parameter \"%s\" cannot be NULL."
// *Cause: An attempt was made to call a procedure without a
// required parameter.
// *Action: Specify a valid value for this parameter.
/
15603, 00000, "Action cannot be performed when database is in read-only mode."
// *Cause: A procedure in DBMS_AUTO_TASK_ADMIN package was invoked when database
// was open in read-only mode.
// *Action: Retry when database is open in read/write mode.
/
15604, 00000, "Initialization parameters prevent client from being enabled."
// *Cause: An attempt was made to enable a client that was disabled
// for automatic execution by an initialization parameter.
// *Action: Check the related client parameters and try again.
/
15605, 00000, "\"%s\" is not a Maintenance Window"
// *Cause: Window name passed to DBMS_AUTO_TASK_ADMIN.ENABLE procedure must be a member of
// the MAINTENANCE_WINDOW_GROUP.
// *Action: Make the window a member of the MAINTENANCE_WINDOW_GROUP and retry the call.
/
15649, 00000, "Last message reserved for Automated Maintenance Tasks (KET)."
// *Document: NO
// *Cause:
// *Action:
//
/
/
/ 15650 - 15699 reserved for Direct Access to Fixed Tables
/
15650, 00000, "invalid DIRECT_ACCESS command"
// *Document: NO
// *Cause:
// *Action:
/
15651, 00000, "invalid option \"%s\" for \"%s\" in DIRECT_ACCESS command"
// *Document: NO
// *Cause:
// *Action:
/
15652, 00000, "Fixed table \"%s\" does not exist."
// *Document: NO
// *Cause:
// *Action:
/
15653, 00000, "Fixed table \"%s\" is not supported by DIRECT_ACCESS."
// *Document: NO
// *Cause:
// *Action:
/
15654, 00000, "No more than %s columns can be specified in a DIRECT_ACCESS SELECT query."
// *Document: NO
// *Cause:
// *Action:
/
15655, 00000, "Fixed table \"%s\" cannot be accessed safely in prelim connection."
// *Document: NO
// *Cause:
// *Action: Run ORADEBUG DIRECT_ACCESS SET MODE=UNSAFE and query again.
/
15656, 00000, "DIRECT_ACCESS statement is too long."
// *Document: NO
// *Cause:
// *Action:
/
15657, 00000, "Column \"%s\" does not have a fixed index defined."
// *Document: NO
// *Cause:
// *Action:
/
15658, 00000, "Type is not supported type for DIRECT_ACCESS filters."
// *Document: NO
// *Cause:
// *Action:
/
15659, 00000, "Multi-column indexes not supported for DIRECT_ACCESS filters."
// *Document: NO
// *Cause:
// *Action:
/
15699, 00000, "last message reserved for DIRECT_ACCESS"
// *Document: NO
// *Cause:
// *Action:
//
/
/
/ 15700-15749 Reserved for SQL Tuning Advisor, SQL Tuning Set and SQL
/ Performance Analyzer (STA/STS/SPA). We have reserved the
/ last ten error codes for SPA.
/
15700, 00000, "SQL limit already reached by prior task execution"
// *Cause: An attempt was made to resume the execution of a task when
// the prior execution already reached the SQL limit.
// *Action: Task execution is complete. Examine the report to review
// Advisor's recommendations.
/
15701, 00000, "All \"SQL Tuning Set(s)\" with name like \"%s\" and owner like \"%s\" are empty"
// *Cause: An attempt was made to pack one or more SQL Tuning Sets, none
// * of which contained any statements.
// *Action: Check the input and try again.
/
15702, 00000, "duplicate values for plan line ID in input collection"
// *Cause: An invalid input was provided containing duplicate values for
// plan line IDs causing the load of the statement to fail.
// *Action: Check the input and try again.
/
15703, 00000, "invalid version number \"%d\" for SQL tuning set staging table"
// *Cause: An invalid version number was provided for a staging table used
// to pack a SQL tuning set.
// *Action: Check the input and try again.
/
15704, 00000, "This operation is not supported for Oracle RAS users."
// *Cause: An attempt was made to execute an unsupported operation. This
// operation is not supported for Oracle Real Application Security
// (Oracle RAS) users.
// *Action: Retry the operation as a non-Oracle RAS user.
/
15705, 00000, "staging table does not exist"
// *Cause: An attempt was made to use a staging table that did not exist.
// *Action: Verify the name of the staging table and retry the operation.
/
15706, 00000, "concurrent execution of the task terminated unexpectedly"
// *Cause: Parallel slaves have died unexpectedly.
// *Action: Check your system for anomalies and resume the executing task.
/
15738, 00000, "Default parameters for SPA Quick Check are not set."
// *Cause: The required default parameters for SQL Performance Analyzer
// Quick Check (SPA Quick Check) were not set.
// *Action: Set default values for all of the required SPA Quick Check
// parameters and try again.
/
15739, 00000, "invalid name \"%s\" for SQL Performance Analyzer task"
// *Cause: An invalid SQL Performance Analyzer task name was used.
// *Action: Check the name of the SQL Performance Analyzer task to ensure
// that it is correct.
/
15740, 00000, "parameter \"%s\" not set for SQL Performance Analyzer task \"%s\""
// *Cause: Could not find the specified parameter name for the SQL Performance Analyzer task.
// *Action: Check that the specified parameter exists for the SQL Performance
// Analyzer task so that the parameter is set.
/
15741, 00000, "no COMPARE_PERFORMANCE execution exists for SQL Performance Analyzer task \"%s\""
// *Cause: Could not find an execution of type COMPARE_PERFORMANCE for
// specified SQL Performance Analyzer task.
// *Action: Ensure that the given SQL Performance Analyzer task has at least one
// execution of type COMPARE_PERFORMANCE.
/
15742, 00000, "specified execution name \"%s\" is not a valid COMPARE_PERFORMANCE execution for SQL Performance Analyzer task \"%s\"."
// *Cause: The specified execution name was not a valid execution of type
// COMPARE_PERFORMANCE for the SQL Performance Analyzer task.
// *Action: Ensure that a valid COMPARE_PERFORMANCE execution name is used for
// the SQL Performance Analyzer task.
/
15743, 00000, "need to specify the object ID if the tuning task is on a SQL set."
// *Cause: There could be multiple objects in the SQL tuning task. Specify which one.
// *Action: Add object ID to the interface.
/
15744, 00000, "The directory name is null."
// *Cause: The directory name for finding the SQL traces was null.
// *Action: Create the directory.
/
15745, 00000, "The plan type is not valid."
// *Cause: The specified plan type was not valid
// *Action: Check the existing plan types and specify the right one.
/
15746, 00000, "Missing EXECUTE privilege on DBMS_AUTO_SQLTUNE."
// *Cause: The current user was missing the necessary privileges to execute
// the API.
// *Action: Grant the privilege and try again.
/
15747, 00000, "The previous Oracle Data Masking job is unfinished. \"%s\" table is not empty."
// *Cause: The previously executed Oracle Data masking job was not
// successfully completed.
// *Action: Execute Oracle Data masking cleanup.
/
15748, 00000, "invalid container name specified"
// *Cause: The container name specified for this API was invalid.
// When this API is run at the multitenant container database (CDB) root,
// the acceptable container names are any valid containers in that CDB.
// When it is run in a pluggable database, the only
// acceptable container name is its own name.
// *Action: Specify a valid container name.
/
15749, 00000, "last message reserved for SQL tuning"
// *Document: NO
// *Cause:
// *Action:
//
/
/==============================================================================
/ 15750-15849 Reserved for Remote Manageability Framework
/==============================================================================
15750, 00000, "current node is not configured for remote operations"
// *Cause: An attempt to perform a Remote Management Framework (RMF)
// operation failed because the node performing the operation
// was not yet configured for remote operations.
// *Action: Configure the node and retry the operation.
/
15751, 00000, "The RMF operation failed."
// *Cause: An attempt to perform a Remote Management Framework (RMF)
// operation failed because an unexpected error condition
// happened.
// *Action: Retry the operation and contact Oracle Support Services
// if the condition persists.
/
15755, 00000, "current node is already configured for remote operations"
// *Cause: An attempt to configure a node failed because the node was
// already configured for Remote Management Framework (RMF)
// operations.
// *Action: Unconfigure the node and retry the operation.
/
15761, 00000, "not registered in an RMF topology"
// *Cause: An attempt to perform a Remote Management Framework (RMF)
// operation failed because the node performing the operation
// was not registered in a topology.
// *Action: Register the node in a topology or create a new topology and
// retry the operation.
/
15764, 00000, "concurrent RMF operation is in progress"
// *Cause: An attempt to perform a Remote Management Framework (RMF)
// operation failed because another conflicting operation
// was already running.
// *Action: Retry after the conflicting operation has finished.
/
15766, 00000, "already registered in an RMF topology"
// *Cause: An attempt to register the specified node failed because the node
// was already registered in a Remote Management Framework (RMF)
// topology.
// *Action: Ensure that the specified node name matches the node to be
// registered and that the database link connects to the intended node.
// Unregister the specified node before registering it into another
// topology.
/
15767, 00000, "RMF topology [%s] does not exist."
// *Cause: A topology with the specified topology name was not created
// in the Remote Management Framework (RMF).
// *Action: Verify that the topology name is valid and retry the operation.
/
15768, 00000, "RMF topology [%s] already exists."
// *Cause: A topology with the specified topology name was already
// created in the Remote Management Framework (RMF).
// *Action: Verify that the topology name is valid and retry the operation.
// Specify a different topology name that has not been used yet.
/
15769, 00000, "node [%s] is not registered in RMF topology [%s]"
// *Cause: A node with the specified node name was not registered in
// the specified Remote Management Framework (RMF) topology.
// *Action: Ensure that the specified node name and topology name is correct,
// and that the specified node is currently registered in the
// specified topology.
/
15770, 00000, "node [%s] is already registered in RMF topology [%s]"
// *Cause: A node with the specified node name was already registered
// in the specified Remote Management Framework (RMF) topology.
// *Action: Ensure that the specified node is not currently registered in
// the specified topology and that the node to be registered in
// the specified topology is configured with a unique name.
/
15771, 00000, "parameter [%s] is invalid: %s"
// *Cause: The value for the specified parameter was invalid.
// *Action: Provide a value that fulfills the requirements specified in the
// error message.
/
15772, 00000, "parameter [%s] exceeds %s characters"
// *Cause: The value for the specified string parameter was too long.
// *Action: Provide a value for the specified parameter that has a length
// below the character limit specified in the error message.
/
15773, 00000, "parameter [%s] does not allow NULL values"
// *Cause: A NULL value was provided for the specified parameter but the
// parameter only allows non-NULL values.
// *Action: Provide a non-NULL value for the specified parameter.
/
15774, 00000, "parameter [%s] conflicts with the value in the remote node [%s]"
// *Cause: An attempt to perform a Remote Management Framework (RMF)
// operation failed because the specified parameter was different
// from the actual value stored in the node performing the
// operation.
// *Action: Ensure that the database link connects to the intended node
// and that the specified parameter matches the value configured
// in the node that will perform the operation.
/
/==============================================================================
/ END Unified Manageability Framework
/==============================================================================
/==============================================================================
/ 16000 - 16499 Reserved for ORACLE HOT STANDBY
/
/ Begin messages for ORACLE Managed (aka Hot aka Automated) Standby
/==============================================================================
/
16000, 00000, "database or pluggable database open for read-only access"
// *Cause: The database or pluggable database was opened for read-only access.
// Attempts to modify the database using DML or DDL statements
// generate this error.
// *Action: In order to modify the database or pluggable database, it must
// first be shut down and reopened for read/write access.
16001, 00000, "database already open for read-only access by another instance"
// *Cause: The database has been opened for read-only access by another
// instance, and cannot be opened for read/write access by this
// instance.
// *Action: This instance must be opened for read/write access, or all other
// instances must first be shut down and reopened for read-only access.
16002, 00000, "database or pluggable database already open for read/write access by another instance"
// *Cause: The database or pluggable database has been opened for read/write
// access by another instance, and cannot be opened for read-only
// access by this instance.
// *Action: This instance must be opened for read-only access, or all other
// instances must first be shut down and reopened for read/write access.
16003, 00000, "standby database is restricted to read-only access"
// *Cause: An attempt was made to open a physical standby database in
// read/write mode.
// *Action: Reissue the ALTER DATABASE OPEN specifying READ ONLY.
//
16004, 00000, "backup database required recovery"
// *Cause: The database could not be opened for read-only access by this
// instance because it requires recovery.
// *Action: Perform the necessary recovery and reopen for read-only access.
//
16005, 00000, "database requires recovery"
// *Cause: The database required recovery, and therefore could not be opened
// for read-only access by this instance.
// *Action: If the database was terminated abnormally (possibly using a
// shutdown abort), the database first needs to be opened in
// read/write mode. Otherwise, perform the necessary recovery
// and reopen for read-only access.
/
16006, 00000, "A remote archival request was aborted due to database shutdown."
// *Cause: When opening or closing a database instance, the database may wait
// for pending remote archival requests to complete before proceeding
// with the operation. This error was reported because a shutdown was
// detected.
// *Action: This is an informational message so no action is required.
/
16007, 00000, "invalid backup control file checkpoint"
// *Cause: The database could not be opened for read-only access because its
// control file did not contain a valid control file checkpoint.
// *Action: Open the database for read/write access to create a valid control
// file checkpoint. The database can then be opened for read-only
// access.
16008, 00000, "indeterminate control file checkpoint"
// *Cause: The control file for the database being opened for read-only access
// was created using the CREATE CONTROLFILE statement. Therefore, a
// control file checkpoint could not be calculated and the database
// could not be opened for read-only access.
// *Action: First, open the database for read/write access. This creates
// a valid control file checkpoint. Then, reopen the database for
// read-only access.
16009, 00000, "invalid redo transport destination"
// *Cause: The redo transport destination could not accept redo data because
// it was not a valid redo transport destination type.
// *Action: Verify that all redo transport destinations are either standby
// databases or downstream capture databases.
16010, 00000, "disable stale RFS process extermination"
// *Document: NO
// *Cause: Disables the termination of RFS processes waiting for
// tcp_keepalive_interval to expire.
// *Action: No action is required.
16011, 00000, "Remote File Server process is in Error state."
// *Cause: The Remote File Server (RFS) process at the specified redo
// transport destination experienced an unrecoverable error and
// was unable to receive further redo data.
// *Action: Correct the problem at the redo transport destination.
16012, 00000, "database identifier mismatch"
// *Cause: The database identifier of a physical standby database did not
// match that of the primary database.
// *Action: Ensure that the database identifier of each physical standby
// database matches that of the primary database.
16013, 00000, "log %s sequence# %s does not need archiving"
// *Cause: An attempt was made to archive the named file manually, but the
// file did not require archiving. The file had previously been
// successfully archived.
// *Action: No action is required.
16014, 00000, "log %s sequence# %s not archived, no available destinations"
// *Cause: An attempt was made to archive the named log, but the archive was
// unsuccessful. The archival failed because there were no archive log
// destinations specified, or all destinations are in an error state.
// *Action: Verify that archive log destinations are specified or
// take the necessary step to correct any errors that may have
// occurred.
16015, 00000, "Log %s sequence# %s was not archived."
// *Cause: An attempt was made to archive the named log to a destination, but
// the operation did not succeed because the destination was not in
// ARCHIVELOG mode.
// *Action: Enable ARCHIVELOG mode at all destinations and retry.
16016, 00000, "archived log for thread %s sequence# %s unavailable"
// *Cause: Redo apply timed out waiting for the requested archived log
// file.
// *Action: Verify that the primary database is still archiving redo data to
// the standby database and reissue the RECOVER STANDBY DATABASE
// command.
16017, 00000, "cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination"
// *Cause: The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value
// when the primary archive destination was set to NULL explicitly.
// *Action: Set the primary archive destination to a valid non-NULL value.
16018, 00000, "cannot use %s with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST"
// *Cause: One of the following events caused an incompatibility:
// 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
// was in use when a LOG_ARCHIVE_DEST_n (n = 1...31) parameter
// was encountered while fetching initialization parameters.
// 2) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when
// a LOG_ARCHIVE_DEST_n parameter was encountered while fetching
// initialization parameters.
// 3) A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM
// command was used to define a value for either the LOG_ARCHIVE_DEST
// or LOG_ARCHIVE_DUPLEX_DEST parameter.
// 4) Parameter DB_RECOVERY_FILE_DEST was in use when an attempt
// was made to use an ALTER SYSTEM or ALTER SESSION command to
// define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST.
// *Action: Eliminate any incompatible parameter definitions.
16019, 00000, "cannot use %s with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST"
// *Cause: One of the following events caused an incompatibility:
// 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in
// use when the specified LOG_ARCHIVE_DEST_n (n = 1...31) or
// DB_RECOVERY_FILE_DEST parameter was encountered while fetching
// initialization parameters.
// 2) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in
// use when an attempt was made to use an ALTER SYSTEM or ALTER
// SESSION command to define a value for the specified
// LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST parameter.
// 3) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect
// when the specified LOG_ARCHIVE_DEST_n parameter was encountered
// while fetching initialization parameters.
// 4) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect
// when an attempt was made to use an ALTER SYSTEM or ALTER SESSION
// command to define a value for the specified LOG_ARCHIVE_DEST_n
// parameter.
// *Action: Eliminate any incompatible parameter definitions.
16020, 00000, "fewer destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST"
// *Cause: The number of archive log destinations that could be used was less
// than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.
// *Action: Either adjust the log archive destination parameters, or lower the
// value of LOG_ARCHIVE_MIN_SUCCEED_DEST.
16021, 00000, "session %s destination cannot be the same as session %s destination"
// *Cause: An attempt was made to change the first specified archive log
// parameter using ALTER SESSION to have a destination value that
// duplicates the session-level destination value of the second
// specified archive log parameter.
// *Action: Specify a different session destination value for one of the
// LOG_ARCHIVE_DEST_n parameters.
16022, 00000, "LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL"
// *Cause: An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL
// when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL.
// *Action: Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set
// parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value.
16023, 00000, "system %s destination cannot be the same as session %s destination"
// *Cause: An attempt to change the first specified LOG_ARCHIVE_DEST_n
// (n = 1...31) parameter produced a destination that duplicates
// the session destination value of the second specified
// LOG_ARCHIVE_DEST_n parameter. This error can occur when setting a
// non-NULL value with the ALTER SYSTEM command. Or, this error can
// occur when setting a NULL value with ALTER SESSION command, because
// then the associated system destination value may appear as a
// duplicate.
// *Action: Specify a different destination value for the first specified
// LOG_ARCHIVE_DEST_n parameter.
16024, 00000, "parameter %s cannot be parsed"
// *Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...31)
// parameter could not be parsed. Common causes for this error are a
// misplaced equal sign, an unrecognized attribute, or an attribute
// that is missing a required value.
// *Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
16025, 00000, "parameter %s contains repeated or conflicting attributes"
// *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...31)
// parameter contained either repeated attributes or attributes that
// conflicted with each other.
// *Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
16026, 00000, "parameter %s contains an invalid attribute value"
// *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...31)
// parameter contained an attribute with an invalid value.
// *Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
16027, 00000, "parameter %s is missing a destination option"
// *Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...31)
// parameter failed to include a destination option. A destination
// option is specified using either the LOCATION or SERVICE attrbute.
// *Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
16028, 00000, "new %s causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires"
// *Cause: An attempt was made to change the indicated LOG_ARCHIVE_DEST_n or
// LOG_ARCHIVE_DEST_STATE_n parameter (n = 1...31) to a value that
// reduces the number of archive log destinations to less than the
// specified LOG_ARCHIVE_MIN_SUCCEED_DEST value.
// *Action: Either select different options for the LOG_ARCHIVE_DEST_n or
// LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for
// parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.
16029, 00000, "cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations"
// *Cause: An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST
// parameter when there are no archive log destinations.
// *Action: Define one or more log archive destinations using parameters
// LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n
// (n = 1...31). Then, change the value of parameter
// LOG_ARCHIVE_MIN_SUCCEED_DEST.
16030, 00000, "session specific change to the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter requires a LOG_ARCHIVE_DEST_n destination"
// *Cause: The following event caused an incompatibility:
// Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use
// when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST
// parameter with an ALTER SESSION command.
// *Action: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST
// parameters with LOG_ARCHIVE_DEST_n (n = 1...31) parameters.
16031, 00000, "parameter %s destination string exceeds %s character limit"
// *Cause: The value for the specified parameter contained a destination
// string that is too long.
// *Action: Replace the destination value for the specified parameter with a
// character string that has a length below the limit specified in the
// error message.
16032, 00000, "parameter %s destination string cannot be translated"
// *Cause: The value for the specified parameter contained a destination
// string that could not be translated.
// *Action: Use a valid destination string in the specified parameter.
16033, 00000, "parameter %s destination cannot be the same as parameter %s destination"
// *Cause: An attempt was made to change the first specified archive log
// parameter to have a destination value that duplicates the
// system-level destination value of the second specified archive log
// parameter.
// *Action: Specify a different value for one of the archive log parameters.
16034, 00000, "Recovery could not be started."
// *Cause: Database recovery could not be started because the FROM and MANAGED
// STANDBY DATABASE clauses were both specifed when attempting to
// start recovery.
// *Action: Retry the command with either the FROM or MANAGED STANDBY DATABASE
// clause, but not both.
16035, 00000, "missing required keyword %s"
// *Cause: The indicated keyword is required but was not specified.
// *Action: Correct the syntax and retry the command.
16036, 00000, "invalid CANCEL option"
// *Cause: A mode other than IMMEDIATE followed the CANCEL keyword in
// RECOVER MANAGED STANDBY DATABASE statement.
// *Action: Specify either nothing or IMMEDIATE following CANCEL.
16037, 00000, "user requested cancel of managed recovery operation"
// *Cause: The managed standby database recovery operation has been
// canceled per user request.
// *Action: No action is required.
//
16038, 00000, "log %s sequence# %s cannot be archived"
// *Cause: An attempt was made to archive the named file, but the
// file could not be archived. Examine the secondary error
// messages to determine the cause of the error.
// *Action: No action is required.
16039, 00000, "RFS request version mismatch"
// *Cause: A request to archive a redo log to a redo transport destination
// failed because of an Oracle software version mismatch at the
// destination.
// *Action: Verify that a compatible version of Oracle software is running at
// the redo transport destination.
16040, 00000, "Destination archive log file is locked."
// *Cause: The target archive log file was locked. This indicates that the
// file is being archived to another Remote File Server (RFS) process.
// *Action: Ensure that each remote redo transport destination uses a unique
// network service name.
16041, 00000, "Remote File Server fatal error"
// *Cause: The Remote File Server (RFS) process at a redo transport
// destination encountered a fatal error and was no longer
// available. Further redo transmission to this destination may not be
// possible.
// *Action: Refer to the appropriate RFS trace file located at the redo
// transport destination for details regarding the error encountered
// and take corrective action.
16042, 00000, "user requested cancel immediate of redo apply"
// *Cause: Redo apply was canceled immediately per user request. Processing of
// the current archive log file has been interrupted and, therefore,
// the database is in an inconsistent state.
// *Action: No action is required.
16043, 00000, "Redo apply has been canceled."
// *Cause: Redo apply was canceled per user request or operation timeout.
// *Action: More specific messages will accompany this message.
16044, 00000, "Destination %s attribute cannot be specified at session level."
// *Cause: An attempt was made to modify a redo transport destination
// attribute using the ALTER SESSION command.
// *Action: Use the ALTER SYSTEM command to modify the destination attribute.
16045, 00000, "circular redo transport destination dependency chain"
// *Cause: An attempt was made to make a redo transport destination dependent
// on a redo transport destination that was dependent on it.
// *Action: Ensure that no redo transport destination is dependent on any
// destination that is dependent on it.
16046, 00000, "Redo transport destination failed due to failed dependent destination."
// *Cause: The redo transport destination was dependent upon another
// destination, which failed. Therefore, this destination failed.
// *Action: No action required.
16047, 00000, "DGID mismatch between destination setting and target database"
// *Cause: The DB_UNIQUE_NAME specified for the destination did not match
// the DB_UNIQUE_NAME at the target database.
// *Action: Ensure that the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n
// parameter matches the DB_UNIQUE_NAME parameter defined at the
// destination.
16048, 00000, "enable simulated error on archive log write"
// *Document: NO
// *Cause: Causes an I/O error to be signalled during the writing of
// an archival operation.
// *Action: No action is required.
16049, 00000, "simulated error on archive log write"
// *Document: NO
// *Cause: I/O error returned for a simulated archival failure during
// an archival operation.
// *Action: No action is required.
16050, 00000, "destination exceeded specified quota size"
// *Cause: An archive log was attempted to be created in a destination with
// a specified maximum quota size. The creation of the archive log
// exceeded the specified quota size. Therefore, the destination
// has been made inaccessible to future archival operations.
// *Action: No action is required.
16051, 00000, "parameter %s contains an invalid delay time"
// *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...31)
// parameter contained a DELAY attribute with an invalid numeric
// value. The valid range is 0-5760 (in minutes).
// *Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.
16052, 00000, "DB_UNIQUE_NAME attribute is required."
// *Cause: DB_UNIQUE_NAME attribute was not specified. The value of the
// LOG_ARCHIVE_DEST_n parameter for each remote redo transport
// destination must contain the DB_UNIQUE_NAME attribute if the
// LOG_ARCHIVE_CONFIG parameter value contains the DG_CONFIG
// attribute.
// *Action: Use the DB_UNIQUE_NAME attribute to specify the DB_UNIQUE_NAME for
// the destination.
16053, 00000, "DB_UNIQUE_NAME %s is not in the Data Guard Configuration"
// *Cause: The specified DB_UNIQUE_NAME is not in the Data Guard
// Configuration.
// *Action: If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter
// is enabled, you must specify a valid DB_UNIQUE_NAME. The list
// of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG
// view. This problem can also occur when specifying a non-standby
// destination with an DB_UNIQUE_NAME attribute that does not match
// the DB_UNIQUE_NAME initialization parameter for the current
// instance.
16054, 0000, "Event for automatic RFS gap sequence detection"
// *Document: NO
// *Cause: This is an Oracle internal event code. The condition is posted
// when the ARC process is about to request the remote RFS to
// detect gap sequence. The event is used to allow run time disabling
// of the automatic gap sequence detection. Such run time disable
// function allows the ORATST to test the other get gap sequence
// code path: kcrrggs()...etc
// *Action: N/A, this is an Oracle internal event code.
16055, 0000, "FAL request rejected"
// *Cause: Fetch archive log (FAL) server rejected a redo gap fetch request
// from the client. This may have various causes.
// *Action: Check the alert log on the primary database. Take the appropriate
// action to solve the problem.
16056, 00000, "Backup control file archival requires proper syntax."
// *Cause: An attempt was made to perform an online log file archival using
// a backup control file. However, the USING BACKUP CONTROLFILE syntax
// was not specified.
// *Action: Use the USING BACKUP CONTROLFILE clause to perform an online log
// file archival using a backup control file.
16057, 00000, "server not in Data Guard configuration"
// *Cause: The primary database or fetch archive log (FAL) server was not
// found in the Data Guard configuration of the standby database.
// *Action: Add the database unique name of the primary database or FAL server
// to the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database
// initialization parameter.
16058, 00000, "standby database instance is not mounted"
// *Cause: The Remote File Server (RFS) process on the standby database
// received an internal error.
// *Action: Check the standby alert log and RFS trace files for more
// information.
16059, 00000, "empty log file or invalid next available block"
// *Cause: An attempt was made to archive an empty or invalid log file.
// *Action: No action is required.
16060, 00000, "Log file is current."
// *Cause: An attempt was made to archive current log file.
// *Action: No action is required.
16061, 00000, "Log file status has changed."
// *Cause: The online log file was reclaimed as a new log file either before
// archival started or during the archival operation.
// *Action: No action is required.
16062, 00000, "standby database not in Data Guard configuration"
// *Cause: The standby database was not found in the Data Guard configuration
// of the server.
// *Action: Add the database unique name of the standby database to the
// DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG database
// initialization parameter.
16063, 00000, "destination evicted from collective process"
// *Document: NO
// *Cause: LOG_ARCHIVE_DEST_n has been deemed unsuitable for the
// collective ASYNC process.
// *Action: No action is required. The destination will be managed by a
// separate process.
16064, 00000, "Data Guard network decompression failed."
// *Cause: The incoming network buffer containing compressed redo could not be
// decompressed. See the alert log for additional information.
// *Action: As a workaround, disable compression on the database that is
// sending this redo, then call Oracle Support Services.
16065, 00000, "remote archival disabled at standby destination"
// *Cause: Receipt of remote archived REDO log files has been disabled
// at the associated standby destination host database.
// *Action: If appropriate change the associated archive log parameter to
// specify a local destination with the LOCATION keyword or defer
// the associated archive log destination. Or, if possible, set the
// standby REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the
// RECEIVE attribute of the LOG_ARCHIVE_CONFIG parameterand restart
// the standby database instance before further REDO log file
// archivals occur.
16066, 00000, "remote archival disabled"
// *Cause: An archive log destination parameter has specified a remote
// destination with the SERVICE keyword. Remote archival of REDO
// log files has been disabled for this database. The associated
// archive log destination has been disabled.
// *Action: If appropriate change the archive log parameter to specify a
// local destination with the LOCATION keyword or (if appropriate)
// set the REMOTE_ARCHIVE_ENABLE parameter to TRUE, or enable the
// SEND attribute of the LOG_ARCHIVE_CONFIG parameter and restart
// the database instance before further REDO log file archivals occur.
16067, 00000, "activation identifier mismatch in archive log %s"
// *Cause: The activation identifier contained in the archive log file
// header does not match the activation identifier of the database
// being recovered. The indicated archive log cannot be
// applied to the database.
// *Action: Locate the appropriate archive log for the database.
16068, 00000, "redo log file activation identifier mismatch"
// *Cause: The activation identifier of the indicated redo log file
// does not match the activation identifier of the database.
// *Action:
16069, 00000, "activation identifier mismatch"
// *Cause: Redo transport failed because the activation identifier of the
// primary and physical standby databases did not match. This can
// happen if the physical standby database was not created from a
// backup of the primary database.
// *Action: Create a valid configuration and re-try the failed operation.
16070, 00000, "parameter %s contains an invalid REGISTER attribute value"
// *Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...31)
// parameter contained a REGISTER attribute that specified an
// invalid file name template string. If specified, the REGISTER
// file name template string must indicate an O/S-specific file
// path name including thread and log sequence number substitution
// directives (%t, %T, %s, %S).
// *Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter.
16071, 00000, "Archived log file %s was not found at dependency destination."
// *Cause: The specified archived log file was not found at a redo tranpsort
// destination on which other destinations are dependent.
// *Action: Verify that all redo transport destinations that are dependent upon
// another destination or upon which other destinations are dependent
// are configured correctly.
16072, 00000, "a minimum of one standby database destination is required"
// *Cause: No standby database archive log destinations were specified.
// *Action: Specify a standby archive log destination in the initialization
// parameter file.
16073, 00000, "archiving must be enabled"
// *Cause: Online log file archiving is disabled.
// *Action: Enable log file archiving.
16074, 00000, "No ARCH processes are active."
// *Cause: All ARCH processes have stopped.
// *Action: Restart the instance.
16075, 00000, "standby database destination mismatch"
// *Cause: Another instance had access to a standby database destination
// that this instance did not. If the initialization parameter
// LOG_ARCHIVE_CONFIG does not define a DG_CONFIG, this
// may be due to a standby database becoming unavailable recently.
// *Action: Ensure that at each instance the set of standby databases referred
// to by LOG_ARCHIVE_DEST_n initialization parameters is the same
// and define a DG_CONFIG at each instance to identify those databases
// explicitly.
16076, 00000, "unknown standby database destination"
// *Cause: A standby database destination was specified that was not accessed
// by another instance. If the initialization parameter
// LOG_ARCHIVE_CONFIG does not define a DG_CONFIG, this mismatch
// may be due to a standby database having been restarted recently.
// *Action: Ensure that at each instance the set of standby databases referred
// to by LOG_ARCHIVE_DEST_n initialization parameters is the same
// and define a DG_CONFIG at each instance to identify those databases
// explicitly.
16077, 00000, "simulate network transmission error"
// *Document: NO
// *Cause: Used for internal testing - DO NOT USE.
// *Action: If set, value will be returned as error.
16078, 00000, "media recovery disabled"
// *Cause: The database is not in ARCHIVELOG mode.
// *Action: Place the database in ARCHIVELOG mode.
16079, 00000, "standby archival not enabled"
// *Cause: The standby database did not have archival enabled.
// *Action: In order to allow the standby database to access the standby
// log files, the standby database must be in ARCHIVELOG mode.
16080, 00000, "invalid LogMiner session %s for APPLY"
// *Cause: Logical standby apply engine was started with an invalid
// LogMiner session identifier.
// *Action: Fix the problem with the LogMiner session or create a new session.
16081, 00000, "insufficient number of processes for APPLY"
// *Cause: Logical standby apply engine was started with fewer processes
// available than needed.
// *Action: Increase the values of the initialization parameters PROCESSES and
// or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS
// view.
16082, 00000, "logical standby is not initialized correctly"
// *Cause: Logical standby apply engine was started but it found
// inconsistencies in its metadata.
// *Action: Look in the trace file for more information.
16083, 00000, "LogMiner session has not been created"
// *Cause: Logical standby apply engine was started without creating a
// LogMiner session.
// *Action: Create a LogMiner session and restart the apply engine.
16084, 00000, "an apply engine is already running"
// *Cause: A logical standby apply engine was running when another was
// created.
// *Action: Shut down the previous apply engine before starting a new one.
16085, 00000, "apply engine related event"
// *Document: NO
// *Cause:
// *Action:
16086, 0000, "Redo data cannot be written to the standby redo log"
// *Cause: The primary database was in MAXIMUM PROTECTION or MAXIMUM
// AVAILABILITY mode, but redo data could not be written to the
// standby redo log at the standby database(s).
// *Action: Check the Remote File Server (RFS) trace file for specific errors
// and reconfigure the standby redo log as appropriate.
16087, 0000, "Switchover requires standby or current control file."
// *Cause: An attempt was made to perform a switchover operation using a
// backup or clone control file.
// *Action: Convert the backup control file into a current control file prior
// to attempting a switchover operation. A clone control file cannot
// be used for a switchover operation.
16088, 0000, "archive log has not been completely archived"
// *Cause: An attempt was made to register an archive log that has not been
// completely archived. The specified archive log may be a "current"
// log file.
// *Action: Specify a completed archive log.
16089, 0000, "archive log has already been registered"
// *Cause: An attempt was made to register an archive log that already has
// a corresponding thread# and sequence# entry in the standby database
// control file. Duplicate information is not permitted.
// *Action: Use the V$ARCHIVED_LOG fixed view to verify the archive log
// information.
16090, 0000, "archive log to be replaced not created by managed standby process"
// *Cause: An attempt was made to replace an archive log entry that was not
// originally created by the managed standby operation.
// *Action: No user action required.
16091, 00000, "dependent archive log destination already archived"
// *Cause: An archive log destination contains a dependency to another
// archive log destination that has previously been archived.
// *Action: The parent archive log destination cannot be dependent on another
// archive log destination. Use the ALTER SYSTEM command to remove
// one of the dependency attributes.
16092, 00000, "dependent archive log destination is not active"
// *Cause: An archive log destination contains a dependency to another
// archive log destination that is not active"
// *Action: The child archive log destination cannot be dependent on another
// invalid archive log destination. Use the ALTER SYSTEM command to
// remove one of the dependency attributes.
16093, 00000, "dependent archive log destination is not LGWR-enabled"
// *Cause: An archive log destination contains a dependency to another
// archive log destination that is not enabled for the LGWR process"
// *Action: The child archive log destination cannot be dependent on another
// archive log destination not archived by the LGWR. Use the
// ALTER SYSTEM command to change the parent archive log to specify
// the LGWR process.
16094, 00000, "Database shut down during archival operation."
// *Cause: The database was shut down while an online log file archival was
// active.
// *Action: None required.
16095, 00000, "Dependent destination removal for inactivation"
// *Cause: A dependent archive log destination was inactivated due to the
// parent archive log destination becoming inelligible for archival.
// This may be due to the parent destination being manually
// deferred by an application user.
// *Action: None required.
16096, 00000, "ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY"
// *Cause: None
// *Action: Specify this command to switch the primary database to the physical
// standby role.
16097, 00000, "ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY"
// *Cause: None
// *Action: Specify this command to switch the physical standby database to the
// primary role.
16098, 00000, "Primary database has been shut down to prevent data loss."
// *Cause: The primary database was shut down because it was operating
// in maximum protection mode and no suitable standby databases
// were available to protect the primary database from data loss.
// *Action: Diagnose and correct whatever errors exist in the configuration
// or configure the primary database for maximum availability or
// maximum performance mode.
16099, 00000, "internal error ORA-00600 occurred at standby database"
// *Cause: The RFS process on the standby database received an internal error.
// *Action: Check the standby alert log and RFS trace files for more
// information.
//
/
/ 16100 - 16130 Reserved for Logical Standby
/
16100, 00000, "not a valid Logical Standby database"
// *Cause: This database has not been completely configured as a
// Logical Standby database.
// *Action: Verify that the database is the intended Logical Standby database.
// Ensure that you already started logical standby apply with the
// ALTER DATABASE START LOGICAL APPLY INITIAL statement.
// See the Oracle8i SQL Reference manual for the statement syntax.
16101, 00000, "a valid start SCN could not be found"
// *Cause: An SCN from which to start could not be found.
// *Action: Register the first log file following the backup from which this
// database was generated. Using the ALTER DATABASE REGISTER LOGILE
// statement to register the database is recommended. Alternatively,
// you can provide a starting SCN value with this startement.
16102, 00000, "remote information is not available on the specified primary"
// *Cause: The new primary has not completed generating the necessary
// information for the standby to begin consuming its log stream.
// *Action: Verify that the database link provided references a system that
// is about to become a new primary. Wait a short time before
// retrying the command to allow the primary some time to generate
// the necessary information.
16103, 00000, "Logical Standby apply must be stopped to allow this operation"
// *Cause: Logical Standby is currently applying changes. The apply must
// complete or be stopped to allow the requested operation.
// *Action: Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement,
// then re-enter or respecify the operation.
16104, 00000, "Invalid Logical Standby parameter"
// *Cause: The specified parameter is not valid.
// *Action: Check spelling or refer to the DBMS_LOGSTDBY PL/SQL package
// documentation for the correct statement syntax.
16105, 00000, "Logical Standby is already running in background"
// *Cause: A Logical Standby apply operation is already running.
// *Action: none
16106, 0000, "loading previously applied transaction information"
// *Cause: Logical Standby coordinator was performing a scan to identify
// previously applied transactions.
// *Action: No action necessary. This informational statement is provided
// to record the event for diagnostic purposes.
16107, 00000, "all log data from primary has been processed"
// *Cause: On the primary system, the log stream has been ended by the
// ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY command.
// *Action: Issue one of the following commands to make this standby a primary
// or resume applying changes from a new primary.
// ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL PRIMARY;
// ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;
16108, 00000, "database is no longer a standby database"
// *Cause: The current database has already been made a primary database.
// *Action: Issue the following commands to make this primary a standby.
// ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY;
// ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;
16109, 00000, "failed to apply log data from previous primary"
// *Cause: Log data from previous primary could not be completely applied.
// *Action: Check DBA_LOGSTDBY_EVENTS for failures and take corrective
// action. Then, reissue command.
16110, 00000, "user procedure processing of logical standby apply DDL"
// *Cause: A user provided stored procedure has been called to inspect
// a DDL statement prior to it being processed.
// *Action: No action necessary, this informational statement is provided
// to record user involvement in the processing of a statement.
// Additional information can be found in the DBA_LOGSTDBY_EVENTS
// and the DBA_LOGSTDBY_SKIP views.
16111, 00000, "log mining and apply setting up"
// *Cause: This logical standby process is setting up to begin processing
// changes.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16112, 00000, "log mining and apply stopping"
// *Cause: This logical standby process is cleaning up and stopping Logical
// Standby apply.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16113, 00000, "applying change to table or sequence %s"
// *Cause: The process is applying changes to a specific schema object.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16114, 00000, "applying DDL transaction with commit SCN %s"
// *Cause: The process is applying a DDL change that's committed at the given
// SCN.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16115, 00000, "%s\% of LogMiner dictionary loading is done"
// *Cause: The process is loading dictionary information from the redo stream.
// This activity may take a few minutes.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16116, 00000, "no work available"
// *Cause: The process is idle waiting for additional changes to be made
// available.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16117, 00000, "processing"
// *Cause: The process is performing its primary function and is not
// waiting on any significant event.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/16118 - formerly used to enable RFS wait event threshold identification
16119, 00000, "building transaction at SCN %s"
// *Cause: The transaction being committed at the given SCN is being
// prepared for apply.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16120, 00000, "dependencies being computed for transaction at SCN %s"
// *Cause: The transaction committed at the given SCN is being
// analyzed for dependencies.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16121, 00000, "applying transaction with commit SCN %s"
// *Cause: The transaction committed at the given SCN is being applied.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16122, 00000, "applying large dml transaction at SCN %s"
// *Cause: A large transaction is being applied before the commit has been
// seen. The current redo being applied ends as the given SCN.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16123, 00000, "transaction %s %s %s is waiting for commit approval"
// *Cause: The apply process is waiting for approval to commit a
// transaction. This transaction may depend on another or other
// synchronization activity may delay the committing of a transaction.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16124, 00000, "transaction %s %s %s is waiting on another transaction"
// *Cause: The apply process is waiting to apply additional changes.
// This transaction likely depends on another.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16125, 00000, "large transaction %s %s %s is waiting for more data"
// *Cause: The apply process is waiting until additional changes for a
// large transaction are retrieved from the log stream.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16126, 00000, "loading table or sequence %s"
// *Cause: Information on the given table or sequence is being loaded
// into an in memory cache for future use.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16127, 00000, "stalled waiting for additional transactions to be applied"
// *Cause: This process is waiting for additional memory before continuing.
// Additional log information cannot be read into memory until more
// transactions have been applied to the database, thus freeing up
// additional memory.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes. If this message
// occurs often and changes are not being applied quickly, increase
// available SGA or the number of apply processes.
16128, 00000, "User initiated stop apply successfully completed"
// *Cause: Logical standby was shutdown in an orderly fashion.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
16129, 00000, "unsupported DML encountered"
// *Cause: One or more DMLs to an unsupported table were encountered
// and skipped.
// *Action: No action necessary. This informational statement is provided
// to record the event for diagnostic purposes.
// Optionally, check the DBA_LOGSTDBY_EVENTS view for more
// information including the impacted table owner and name.
16130, 00000, "supplemental log information is missing from log stream"
// *Cause: Supplemental logging is not enabled at the primary database.
// *Action: Issue the following command to enable supplemental logging.
// ALTER DATABASE ADD
// SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;
16131, 00000, "An error occurred during a Terminal Recovery of the standby."
// *Cause: An error occurred during a Terminal Recovery of the standby.
// *Action: Check the standby alert log additional information.
16132, 00000, "An error occurred during activation of the standby."
// *Cause: An error occurred during activation of the standby database
// following a Terminal Recovery.
// *Action: Check the standby alert log additional information.
16133, 00000, "Datafile %s has incorrect terminal recovery stamp."
// *Cause: After activation of a standby database following a terminal
// recovery (recovery of standby using current logs), recovery
// of a datafile from before the activation must have completed
// the same terminal recovery to avoid corruption.
// *Action: A backup of the datafile taken after the terminal recovery
// and before activating the standby must be used for recovery.
16134, 00000, "invalid MANAGED recovery FINISH option"
// *Cause: A mode other than NOWAIT follows the FINISH keyword in
// RECOVER MANAGED STANDBY DATABASE statement.
// *Action: Specify either nothing or NOWAIT following FINISH.
16135, 00000, "Invalid LOG_ARCHIVE_CONFIG modification while in protected mode"
// *Cause: The LOG_ARCHIVE_CONFIG parameter can not be modified while any
// RAC instance is open in either maximum protection or maximum
// availability mode. Also, the parameter can not be modified in such
// way that would cause all destinations to fail while in maximum
// protection mode.
// *Action: Make the modification before the database is opened by any
// instance.
16136, 00000, "Managed Standby Recovery not active"
// *Cause: An attempt was made to cancel a managed recovery session but
// no managed recovery session was active.
// *Action: No action is necessary.
16137, 00000, "invalid state change to a managed alternate destination"
// *Cause: An attempt was made to explicitly change the state of a
// destination participating in an internally managed set of
// alternate destinations. For example, a destination in the
// ALTERNATE state was explicitly ENABLED. Doing so will thwart
// the internal mechanisms to manage these cooperating destinations.
// *Action: The destination must be reset before making this state change.
16138, 00000, "end of log stream not received from primary"
// *Cause: The standby system has not received notification that the primary
// system log stream has been terminated. A graceful switchover is not
// possible.
// *Action: Verify that the primary log stream has been terminated. Ensure that
// the standby has applied all necessary redo from the primary system
// and, if appropriate, reissue the graceful switchover command.
16139, 00000, "media recovery required"
// *Cause: An error has occurred while performing a switchover.
// *Action: If you were switching a primary database to the standby role, the
// conversion was successful, but one or more errors occurred after
// the conversion completed. See the alert log for more information.
// You can proceed with switching the target standby database to the
// primary role, but you must address the errors reported at the old
// primary database before it can protect the new primary database.
//
// If you encountered this error while switching a physical standby
// database to the primary role, the switchover did not succeed
// because additional redo must be applied. Verify that redo apply is
// active and wait until the SWITCHOVER_STATUS column of the
// V$DATABASE dynamic performance view reports TO_PRIMARY or
// SESSIONS_ACTIVE before retrying the switchover.
16140, 00000, "standby online logs have not been recovered"
// *Cause: The standby database has online logs containing redo that has
// not been recovered. Activating the standby would lose redo
// contained in the online logs.
// *Action: To recover the standby online logs issue the following command:
// ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH. Then
// reissue the ALTER DATABASE ACTIVATE STANDBY DATABASE command.
// To activate the standby without recovering the online logs,
// issue the following command:
// ALTER DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE.
16141, 00000, "enable simulated archive log error"
// *Document: NO
// *Cause: Causes an error to be signalled during the archival operation.
// *Action: No action is required.
16142, 00000, "simulated archive log error"
// *Document: NO
// *Cause: Error returned for a simulated archival failure during
// an archival operation.
// *Action: No action is required.
16143, 00000, "RFS connections not allowed during or after terminal recovery"
// *Cause: An attempt was made, by an RFS process, to access a standby online
// log file during or after a terminal recovery.
// *Action: The primary must not attempt to archive to the standby
// after a terminal recovery.
16144, 00000, "simulate RFS error while terminal recovery in progress"
// *Document: NO
// *Cause: Used for internal testing - DO NOT USE.
// *Action: If set, value will be returned as error.
16145, 00000, "archival for thread# %s sequence# %s in progress"
// *Cause: The indicated archived log file is not available for recovery
// due to the fact that it is still being archived.
// *Action: Verify that archival of the indicated log file has completed
// and reissue the RECOVER STANDBY DATABASE command.
16146, 00000, "%scontrol file enqueue unavailable"
// *Cause: The control file enqueue is currently unavailable.
// *Action: No Action is required. We will try to re-fetch it at a later time.
16147, 00000, "standby database referenced by multiple archive log destinations"
// *Cause: Multiple archive log destinations reference the same standby
// database, using different service names. This is not allowed.
// *Action: Remove one of the duplicate archive log destinations.
16148, 00000, "user requested expiration of managed recovery operation"
// *Cause: The managed standby database recovery operation has been
// canceled per user specified EXPIRE option of the RECOVER
// MANAGED STANDBY DATABASE statement.
// *Action: No action is required.
16149, 00000, "enable simulated ARCH RAC archival testing"
// *Document: NO
// *Cause: Allows ARCH archival even when RAC not enabled
// *Action: No action is required.
16150, 00000, "FINISH recovery performed on another, older standby database"
// *Cause: An archive log containing a FINISH recovery indicator was received
// by a standby database that has received archive logs in the future
// of the received archive log. Because of the possibility that these
// future archive logs have been applied to this standby database,
// the received archive log must be rejected.
// *Action: No action is required.
16151, 00000, "Managed Standby Recovery not available"
// *Cause: The attempted operation failed because of a pending CANCEL of the
// managed standby recovery operation.
// *Action: Wait for the managed standby recovery session to end. Then retry
// the operation.
16152, 00000, "standby database is in 'no-data-loss' protected mode"
// *Cause: The attempted database operation is not allowed while the
// standby database is in 'no-data-loss' protected mode.
// *Action: Verify that the attempted database operation is warranted,
// ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and reissue
// the statement.
16153, 00000, "enable ARCH Physical RFS client debugging"
// *Document: NO
// *Cause: Enables the ARCH physical RFS client callback.
// *Action: No action is required.
16154, 00000, "suspect attribute: %s"
// *Cause: Use of the indicated attribute is illegal in the given context.
// *Action: Make the appropriate changes and reissue the statement.
16155, 00000, "enable arch procs to not exceed log_archive_max_processes"
// *Document: NO
// *Cause: disallow arch processes to exceed log_archive_max_processes
// in releases prior to 9i. Note that in 9i and subsequent
// releases this event is not required. We reserve this event for 9i
// and subsequent releases to allow us to backport the new
// log_arch_max_processes behavior for earlier releases.
// *Action: No action is required.
16156, 00000, "LGWR archive log dependency not allowed if database is standby protected"
// *Cause: The use of a LGWR archive log dependency is not allowed when the
// primary is protected by a standby database, as this requires use
// of the standby redo log files.
// *Action: Remove the LGWR archive log dependency and use normal LGWR archival
// instead.
16157, 00000, "media recovery not allowed following successful FINISH recovery"
// *Cause: A RECOVER MANAGED STANDBY DATABASE FINISH command has previously
// completed successfully. Another media recovery is not allowed.
// *Action: Issue one of these operations following a FINISH recocvery:
// ALTER DATABASE OPEN READ ONLY or
// ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY.
16158, 00000, "simulated failure during terminal recovery"
// *Document: NO
// *Cause: Causes an error to be signalled during terminal recovery.
// *Action: No action is required.
16159, 00000, "Cannot change protected standby destination attributes"
// *Cause: An attempt was made to change the LGWR/ARCH or SYNC/ASYNC attributes
// for a destination that is participating in the standby protection
// mode of the database.
// *Action: No action is required.
16160, 00000, "Cannot change protected standby database configuration"
// *Cause: An attempt was made to change the standby database configuration
// when the primary database is in standby protected mode.
// *Action: The standby database must be added to the configuration before
// the primary database is opened.
16161, 00000, "Cannot mix standby and online redo log file members for group %s"
// *Cause: An attempt was made to add a log file member that did not match
// the other member types. This problem typically occurs when adding
// a standby log file member to an online redo log file group, or adding
// an online redo log file member to a standby redo log file group.
// *Action: Verify the log file group type using the TYPE column of the V$LOG
// fixed view.
16162, 00000, "Cannot add new standby databases to protected configuration"
// *Cause: An attempt was made to enable a new standby database destination
// when the primary database is in standby protected mode.
// *Action: The standby database must be added to the configuration before
// the primary database is opened.
16163, 00000, "LGWR network server host attach error"
// *Cause: The LGWR network server could not attach to remote host
// *Action: The alert log contains more problem-specific information
16164, 00000, "LGWR network server host detach error"
// *Cause: The LGWR network server could not detach from remote host
// *Action: The alert log contains more problem-specific information
16165, 00000, "LGWR failed to hear from network server"
// *Cause: The LGWR lost its connection to the network server
// *Action: The alert log contains more problem-specific information
16166, 00000, "LGWR network server failed to send remote message"
// *Cause: The LGWR network server could not communicate with the remote host
// *Action: The alert log contains more problem-specific information
16167, 00000, "LGWR network server could not switch to non-blocking mode"
// *Cause: The LGWR network server could not switch to non-blocking mode
// *Action: The alert log contains more problem-specific information
16168, 00000, "LGWR network server could not switch to blocking mode"
// *Cause: The LGWR network server could not switch to blocking mode
// *Action: The alert log contains more problem-specific information
16169, 00000, "LGWR network server invalid parameters"
// *Cause: The LGWR network server could not switch to blocking mode
// *Action: The alert log contains more problem-specific information
16170, 00000, "Terminal recovery may have left the database in an inconsistent state"
// *Cause: When terminal recovery is invoked in a standby database
// without synchronous log shipping, in the rare case of the
// recovery session being in an unrecoverable state, terminal
// recovery cannot bring the standby database to a consistent
// SCN boundary if the primary database continues to have redo
// thread(s) open.
// *Action: Continue standby recovery with additional log shipping from
// primary.
16171, 00000, "RECOVER...FINISH not allowed due to gap for thr %s, seq %s-%s"
// *Cause: See alert log for more details
// *Action: Copy missing archived logs from primary or another standby.
// Register the logs and reissue the RECOVER...FINISH command.
// If the logs are not available, issue the ALTER DATABASE
// RECOVER MANAGED STANDBY SKIP command to ignore the standby
// redo log files.
16172, 00000, "archive logs detected beyond Terminal End-Of-Redo"
// *Cause: An attempt to archive a Terminal End-Of-Redo archive log to a
// remote destination failed due the existence, at the remote site,
// of archive logs containing REDO in the future of the Terminal EOR.
// *Action:
16173, 00000, "incompatible archival network connections active"
// *Cause: One of two situations can cause this error:
// 1) An attempt to start a Terminal Incomplete Recovery operation
// failed due to an active Remote File Server process detected.
// 2) An attempt to archive a Terminal End-Of-Redo archive log
// to a remote destination failed due to an active Remote File Server
// process at the remote site.
// An active Remote File Server (RFS) process implies connectivity
// with the primary database which may indicate that a Terminal
// Incomplete Recovery operation is not warrented.
// *Action: Verify the Managed Standby environment and re-evaluate the
// necessity of a Terminal Incomplete Recovery operation.
16174, 00000, "user requested thread/sequence termination of managed recovery"
// *Cause: The managed standby database recovery operation has been
// terminated per user specified THROUGH THREAD/SEQUENCE option of
// the RECOVER MANAGED STANDBY DATABASE statement.
// *Action: No action is required.
16175, 00000, "cannot shut down database when media recovery is active"
// *Cause: An attempt was made to shut down a standby database while media
// recovery was active.
// *Action: Cancel media recovery to proceed with the shutdown.
16176, 00000, "background dictionary build cannot be running"
// *Cause: The background process dedicated to dictionary build is active.
// *Action: wait and try it later.
16177, 00000, "media recovery is not required"
// *Cause: The THROUGH LAST SWITCHOVER clause of the ALTER DATABASE RECOVER
// MANAGED STANDBY DATABASE was specified and the database has been
// recovered to the most recent End-Of-Redo marker. All known archived
// logs have been applied. Managed recovery is not required.
// *Action: No action is necessary. The standby database may be activated as
// a new primary or may continue as a standby.
16178, 00000, "Cannot specify remote destinations in manual archiving mode"
// *Cause: The database is operating in manual archiving mode.
// Remote archivelog destinations are not allowed in this mode.
// *Action: Use the ALTER DATABASE ARCHIVELOG command to place the database
// in automatic ARCHIVELOG mode, or defer the archivelog destinations
// that specify the SERVICE= attribute.
16179, 00000, "incremental changes to \"%s\" not allowed with SPFILE"
// *Cause: Incremental changes to a log_archive_dest_n parameter cannot
// be made when using an SPFILE.
// *Action: Specify either LOCATION or SERVICE plus all other attributes
// to be set in one ALTER SYSTEM/SESSION SET command.
16180, 00000, "number of processes specified is too large"
// *Cause: The number of server processes available for Logical Standby is
// currently limited to 1024 LogMiner processes and 1024 apply
// processes or a total of 2048.
// *Action: Retry with a lower value.
/
16181, 00000, "SGA specified for Logical Standby is too large"
// *Cause: MAX_SGA is larger than 75% of the larger of initialization
// parameters SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET.
// *Action: Specify the value of MAX_SGA to be less than 75% of the maximum of
// SHARED_POOL_SIZE, MEMORY_TARGET, and SGA_TARGET.
16182, 00000, "Internal error on internal channel during remote archival"
// *Cause: An internal error was encountered on the internal channel between
// LGWR and Network Server.
// *Action: No action is required, as an attempt will be made to re-archive the
// file that had this failure during archival.
16183, 00000, "Internal event for testing purposes"
// *Document: NO
// *Cause: This is an internal event used for testing purposes
// *Action: No action is necessary.
16184, 00000, "DB_UNIQUE_NAME %s hashes to the same value as DB_UNIQUE_NAME %s"
// *Cause: The internal hash value generated for one DB_UNIQUE_NAME collided
// with the hash value of another DB_UNIQUE_NAME.
// *Action: Slightly modify one of the DB_UNIQUE_NAMEs so it hashes to a
// different value.
16185, 00000, "REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive"
// *Cause: Both the REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG parameters
// are defined in the initialization file and they are mutually
// exclusive.
// *Action: The REMOTE_ARCHIVE_ENABLE parameter has been made obsolete. Use
// only the LOG_ARCHIVE_CONFIG parameter.
16186, 00000, "Modifying LOG_ARCHIVE_CONFIG requires SID='*' qualifier"
// *Cause: The setting for the LOG_ARCHIVE_CONFIG parameter must be exactly
// the same on all RAC instances so the SID='*' qualifier is required.
// *Action: Re-enter the command using the SID='*' qualifier.
16187, 00000, "LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes"
// *Cause: The LOG_ARCHIVE_CONFIG parameter was specified with duplicate,
// conflicting or invalid attributes.
// *Action: Check the documentation regarding the correct specification of the
// LOG_ARCHIVE_CONFIG parameter.
16188, 00000, "LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance"
// *Cause: The settings for the LOG_ARCHIVE_CONFIG parameter were inconsistent
// with the settings of a previously started instance. The settings
// for this parameter must be exactly the same for all instances.
// *Action: Ensure that all instances use the exact same LOG_ARCHIVE_CONFIG
// settings.
16189, 00000, "Internal event for testing RTA purposes"
// *Document: NO
// *Cause: This is an internal event used for testing purposes
// *Action: No action is necessary.
16190, 00000, "Internal event for RFS Auth testing purposes"
// *Document: NO
// *Cause: This is an internal event used for testing purposes
// *Action: No action is necessary.
16191, 0000, "Primary log shipping client not logged on standby"
// *Cause: An attempt to ship redo to standby without logging on
// to standby or with invalid user credentials.
// *Action: Check that primary and standby are using password files and that
// both primary and standby have the same SYS password.
// Restart primary and/or standby after ensuring that
// password file is accessible and REMOTE_LOGIN_PASSWORDFILE
// initialization parameter is set to SHARED or EXCLUSIVE.
/
16192, 0000, "Primary and standby network integrity mismatch"
// *Cause: Standby wants sqlnet network integrity for redo shipment
// which is not configured properly at the primary.
// *Action: Check sqlnet.ora documentation regarding how to setup
// network integrity and set it up identically on both
// primary and standby. Restart primary and/or standby.
/
16193, 0000, "Primary and standby network encryption mismatch"
// *Cause: Standby wants sqlnet network encryption for redo shipment
// which is not configured properly at the primary.
// *Action: Check sqlnet.ora documentation regarding how to setup
// network encryption and set it up identically on both
// primary and standby. Restart primary and/or standby.
/
16194, 00000, "Modifying DB_UNIQUE_NAME requires SID='*' qualifier"
// *Cause: The setting for the DB_UNIQUE_NAME parameter must be exactly the
// same on all RAC instances so the SID='*' qualifier is required.
// *Action: Re-enter the command using the SID='*' qualifier.
16195, 00000, "DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined"
// *Cause: The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can
// only be used if the DB_UNIQUE_NAME parameter has been explicitly
// defined.
// *Action: Explicitly define a valid DB_UNIQUE_NAME.
16196, 00000, "database has been previously opened and closed"
// *Cause: The instance has already opened and closed the database,
// which is allowed only once in its lifetime.
// *Action: Shut down the instance.
16197, 00000, "Invalid DB_UNIQUE_NAME parameter specification"
// *Cause: The DB_UNIQUE_NAME parameter has an invalid specification. The
// DB_UNIQUE_NAME parameter has a maximum length of 30 characters
// and the only characters allowed are alpha-numeric characters and
// "_", "$" and "#".
// *Action: Check the documentation and re-enter the parameter.
16198, 00000, "Timeout incurred on internal channel during remote archival"
// *Cause: A timeout was incurred during remote archival.
// *Action: No action is required, as an attempt will be made to re-archive the
// file that had this failure during archival.
16199, 00000, "Terminal recovery failed to recover to a consistent point"
// *Cause: See alert log for more details
// *Action: Try to resolve the problem. Retry terminal recovery.
// If the problem occurs repeatedly and cannot be resolved,
// call Oracle support.
/
/ 16200 - 16374 Reserved for Logical Standby
/
16200, 00000, "Skip procedure requested to skip statement"
// *Cause: Logical standby called a skip procedure that requested for
// a particular statement not to be applied.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/
16201, 00000, "Skip procedure requested to apply statement"
// *Cause: Logical standby called a skip procedure that requested for
// a particular statement to be applied.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/
16202, 00000, "Skip procedure requested to replace statement"
// *Cause: Logical standby called a skip procedure that requested for
// a particular statement to be replaced with a new statement.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/
16203, 00000, "Unable to interpret skip procedure return values"
// *Cause: The skip procedure returned conflicting or invalid values.
// *Action: Ensure that the new_statement output parameter is non-NULL when
// returning DBMS_LOGSTDBY.SKIP_ACTION_REPLACE and NULL otherwise.
// Also ensure SKIP_ACTION is specified correctly.
/
16204, 00000, "DDL successfully applied"
// *Cause: A DDL statement has successfully commited on the logical
// standby database.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/
16205, 00000, "DDL skipped due to skip setting"
// *Cause: A setting in the logical standby skip table indicates
// that this type of DDL should always be skipped.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/
16206, 00000, "database already configured as Logical Standby database"
// *Cause: This database has been previously configured as a Logical Standby
// database. A Logical Standby database is not capable of processing
// the requested operation.
// *Action: Ensure that you entered the command on the correct database as
// this database is a Logical Standby and is not capable of
// servicing the request.
/
16207, 00000, "Logical standby dictionary build not permitted."
// *Cause: A dictionary build is currently in progress. Only one build can be
// active at a time.
// *Action: Wait for the active build to complete before invoking a new build.
/
16208, 00000, "Logical standby dictionary build failed to start."
// *Cause: Failure to start the logical standby dictionary build process (LSP1)
// *Action: Check the accompanying messages, and the background process trace
// file. Correct the problem mentioned in the messages. Then shut down
// and restart the instance. If the trace file mentions any other
// background process messages, check the trace file for the mentioned
// process until the root message is found.
/
16209, 00000, "Logical standby dictionary build failed to complete."
// *Cause: The logical standby dictionary build process terminated abnormally.
// *Action: Check the accompanying messages, and the background process trace
// file. Correct the problem mentioned in the messages. Then shut down
// and restart the instance. If the trace file mentions any other
// background process messages, check the trace file for the mentioned
// process until the root message is found.
/
16210, 00000, "Logical standby coordinator process terminated with error"
// *Cause: The logical standby coordinator process terminated abnormally.
// *Action: Check the accompanying messages, and the background process trace
// file. Correct the problem mentioned in the messages. Then shut
// down and restart the instance. If the trace file mentions any other
// background process messages, check the trace file for the mentioned
// process until the root message is found.
/
16211, 00000, "unsupported record found in the archived redo log"
// *Cause: Log apply services encountered a record in the archived redo log
// that could not be interpreted.
// *Action: 1. Use DBMS_LOGSTDBY.INSTANTIATE_TABLE to re-create the table
// on the standby database or simply drop the table if
// it's unimportant.
// 2. ALTER DATABASE START LOGICAL STANDBY APPLY;
// 3. Examine the current_scn column in the DBA_LOGSTDBY_EVENTS view
// to determine which log file contains the unsupported record.
// 4. Provide the log file to Oracle Support Services.
/
16212, 00000, "number of processes specified for SQL Apply is too great"
// *Cause: Logical standby apply engine was started with more processes
// requested than are available.
// *Action: Adjust the values of the initialization parameters PROCESSES
// or the MAX_SERVERS parameter seen in the DBA_LOGSTDBY_PARAMETERS
// view. If you did not specify MAX_SERVERS, but instead specified
// PREPARE_SERVERS and APPLY_SERVERS through the
// dbms_logstdby.apply_set procedure, you will need to decrease either
// one or both of them.
/
16213, 00000, "ddl encountered, stopping apply engine"
// *Cause: stop_on_ddl callout specified and DDL was encountered.
// *Action: Either disable stop_on_ddl callout or remove DDL.
/
16214, 00000, "apply stalled for apply delay"
// *Cause: A delay has been specified on the primary database for this
// destination.
// *Action: Either turn off the delay on the primary or use
// DBMS_LOGSTDBY.APPLY_UNSET('APPLY_DELAY'); to override.
/
16215, 00000, "history metadata inconsistency"
// *Cause: internal error.
// *Action: This is an internal error. Contact Oracle support.
/
16216, 00000, "Log stream sequence error"
// *Cause: The log stream being processed did not follow the last
// processed stream.
// *Action: If the database is in an active configuration, issue an
// ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY command
// to synchronize log stream data with the current primary database.
// If the database is not in an active configuration, manually add
// the next dictionary-begin log file that followed the previous
// log stream.
/
16217, 00000, "prepare to switchover has not completed"
// *Cause: An ALTER DATABASE PREPARE TO SWITCHOVER command was issued, but
// the prepare activity did not complete.
// *Action: Verify that the standby was prepared properly. You may cancel
// the prepare and perform an unprepared switchover which requires
// a database link to complete. Or reissue the prepare operation
// on the standby.
/
16218, 00000, "This database is already preparing to switch over."
// *Cause: The database was already preparing to switch over and was not
// able to accomodate another prepare attempt.
// *Action: Cancel the current prepare attempt with the ALTER DATABASE
// PREPARE TO SWITCHOVER CANCEL command, then reissue the prepare
// request.
/
16219, 00000, "This database is not preparing to switch over."
// *Cause: The database was not preparing to switch over. Therefore, it was not
// possible to cancel the SWITCHOVER command.
// *Action: Preparing for the SWITCHOVER command can be accomplished with the
// ALTER DATABASE PREPARE TO SWITCHOVER command.
/
16220, 00000, "no failed transaction found"
// *Cause: No failed transaction was found.
// *Action: Retry the ALTER DATABASE START LOGICAL STANDBY APPLY command
// without the SKIP FAILED TRANSACTION option.
/
16221, 00000, "history table synchronization error"
// *Cause: internal error.
// *Action: This is an internal error. Contact Oracle support.
/
16222, 00000, "automatic Logical Standby retry of last action"
// *Cause: A failure occurred while running Logical Standby apply.
// A new attempt is automatically being made by Logical Standby apply.
// *Action: No action is necessary. This informational statement is provided
// to record the event for diagnostic purposes.
/
16223, 00000, "DDL skipped, unsupported in current version"
// *Cause: The given DDL statement was not supported in the current version of
// Logical Standby and was skipped.
// *Action: No action is necessary. This informational statement is provided
// to record the event for diagnostic purposes.
/
16224, 00000, "Database Guard is enabled"
// *Cause: Operation could not be performed because database guard is enabled
// *Action: Verify operation is correct and disable database guard
/
16225, 00000, "Missing LogMiner session name for Capture"
// *Cause: An attempt was made to register the log file for Capture without
// a specified LogMiner session name.
// *Action: Specify a valid LogMiner session name to which the log file will
// be registered.
/
16226, 00000, "DDL skipped due to lack of support"
// *Cause: Logical Standby does not support this type of DDL
// in this version, so the DDL is skipped.
// *Action: The DBA may apply the DDL explicitly at a later time or
// a procedure to handle this type of DDL can be created.
// see DBMS_LOGSTDBY.SKIP procedure for details.
/
16227, 00000, "DDL skipped due to missing object"
// *Cause: A table or other database object upon which this DDL depended
// was not defined on the Logical Standby database.
// *Action: No action is necessary. This informational statement is provided
// to record the event for diagnostic purposes.
/
16228, 00000, "Insufficient recovery for logical standby"
// *Cause: Insufficient amount of recovery was run for logical standby
// instantiation.
// *Action: Continue to recover the database using
// ALTER DATABASE RECOVER MANAGED STANDBY DATABASE.
/
16229, 00000, "PDML child %s %s %s for parent %s %s %s cannot be skipped."
// *Cause: A request was made to skip a parallel DML child transaction id.
// This is not supported.
// *Action: Using the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure, remove
// the child transaction id, then specify the parent transaction id
// using DBMS_LOGSTDBY.SKIP_TRANSACTION if appropriate.
/
16230, 00000, "committing transaction %s %s %s"
// *Cause: Logical Standby apply was committing changes for the given
// transaction.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/
16232, 00000, "adding Logical Standby skip entry for table %s.%s"
// *Cause: Table was previously unsupported due to datatype or storage
// attribute definitions. Table is now capable of being supported.
// *Action: To have Logical Standby maintain the table, import that table
// directly from the primary.
/
16233, 00000, "The table %s.%s is unsupported now"
// *Cause: Table was previously supported but now is unsupported due to
// altered datatype or storage attribute definitions.
// *Action: None.
/
16234, 00000, "restarting to reset Logical Standby apply"
// *Cause: Logical Standby encountered a work load that required a restart
// to properly reschedule.
// *Action: No action necessary. This informational statement is provided
// to record the event for diagnostic purposes.
/
16235, 00000, "DDL skipped because import has occurred"
// *Cause: An object was exported from the primary database and imported
// into the Logical Standby database. This DDL occurred before the
// export.
// *Action: No action necessary. This informational statement is provided
// to record the event for diagnostic purposes.
/
16236, 00000, "Logical Standby metadata operation in progress"
// *Cause: The requested operation failed because an incompatible
// Logical Standby metadata operation such as
// DBMS_LOGSTDBY.SET_TABLESPACE, DBMS_LOGSTDBY.APPLY_SET or
// DBMS_LOGSTDBY.INSTANTIATE_TABLE was still running.
// *Action: Wait for the incompatible Logical Standby metadata operation to
// finish, then reenter or respecify the operation.
/
16237, 00000, "SGA specified for Logical Standby is too small"
// *Cause: MAX_SGA must be at least 10 Megabytes for proper functioning
// of Logical Standby.
// *Action: Specify the value of MAX_SGA to be greater than or equal to 10Mb.
// Alternatively, increase the shared_pool_size/sga_target so that 1/4
// of it will amount to 10 Megabytes.
/
16238, 00000, "attempt to use version 9 log"
// *Cause: Version 9 log files are not supported.
// *Action: Use log files of a supported version.
/
16239, 00000, "IMMEDIATE option not available without standby redo logs"
// *Cause: The IMMEDIATE option cannot be used without standby redo logs.
// *Action: Do not specify the IMMEDIATE option unless standby redo logs are
// being used.
/
16240, 00000, "Waiting for log file (thread# %s, sequence# %s)"
// *Cause: Process is idle waiting for additional log file to be available.
// *Action: No action necessary. This informational statement is provided
// to record the event for diagnostic purposes.
/
16241, 00000, "Waiting for gap log file (thread# %s, sequence# %s)"
// *Cause: Reader process was idle waiting for the log file to fill the log
// sequence gap.
// *Action: No action necessary. This informational statement is provided
// to record the event for diagnostic purposes.
/
16242, 00000, "Processing log file (thread# %s, sequence# %s)"
// *Cause: Reader process was processing the log file.
// *Action: No action necessary. This informational statement is provided
// to record the event for diagnostic purposes.
/
16243, 00000, "paging out %s bytes of memory to disk"
// *Cause: Builder process is paging out momery to free up space in lcr
// cache.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/
16245, 00000, "change db_name to %s in the server-side parameter file (SPFILE)"
// *Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname
// command was successfully executed without a modifiable server
// parameter file (SPFILE).
// *Action: The server-side parameter file must be modified so that db_name
// is set to the given name before mounting the database again.
// You must do this by executing CREATE PFILE FROM SPFILE, editing the
// resulting text parameter file, and then executing CREATE SPFILE
// FROM PFILE.
/
16246, 00000, "User initiated abort apply successfully completed"
// *Cause: SQL Apply was stopped using the abort option.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/
16247, 00000, "DDL skipped on internal schema"
// *Cause: Logical Standby ignores DDLs on internal schemas such as
// SYS and SYSTEM. For a complete list of internal schemas ignored
// by Logical Standby perform the following query:
// SELECT owner FROM dba_logstdby_skip
// WHERE statement_opt = 'INTERNAL SCHEMA'.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/
16248, 00000, "RFS connections not permitted during Terminal Apply"
// *Cause: Writes by RFS are not permitted while Logical Standby is
// performing Terminal Apply.
// *Action: Permit any outstanding Logical Standby operations to complete.
/
16249, 00000, "Terminal apply failed to complete during failover"
// *Cause: The logical standby coordinator process terminated abnormally."
// *Action: Examine the DBA_LOGSTDBY_EVENTS view for the reason behind the
// abnormal shutdown, and resolve accordingly. Once the problem has
// been rectified, reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY
// DATABASE command to complete the failover.
/
16250, 00000, "Failed to acquire starting scn of new log stream"
// *Cause: The starting SCN for the new log stream could not be determined.
// *Action: Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command.
/
16251, 00000, "LSP1 Background Build not permitted"
// *Cause: The LSP1 background process is not permitted to start because
// it had previously been attempted.
// *Action: This is an internal error. Contact Oracle support.
/
16252, 00000, "Rebuild operation not permitted"
// *Cause: The REBUILD operation is not permitted.
// *Action: Only on a primary database that has failed to complete the LogMiner
// dictionary build may the REBUILD operation take place. Reissue
// the ACTIVATE LOGICAL STANDBY DATABASE command if it previously failed
// to complete.
/
16253, 00000, "Logical standby cannot start due to a prior, incomplete operation"
// *Cause: A failure during a prior failover or configuration-related operation
// left the logical standby in an inconsistent state.
// *Action: Identify and reissue the operation before attempting to restart the
// logical standby apply engine.
/
16254, 00000, "change db_name to %s in the client-side parameter file (pfile)"
// *Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname
// command was successfully executed without a server parameter
// file (spfile).
// *Action: The client-side parameter file must be edited so that db_name
// is set to the given name before mounting the database again.
/
16255, 00000, "Log Auto Delete conflicts with another LogMiner session"
// *Cause: Log Auto Delete cannot be on while another LogMiner
// session is running on the same database.
// *Action: Start Logical Standby without Log Auto Delete or destroy
// other LogMiner sessions first.
/
16256, 00000, "Failure to complete standby redo log file archival after failover"
// *Cause: The standby redo log files processed during the failover of a
// logical standby were not archived.
// *Action: Execute DBMS_LOGSTDBY.REBUILD to reattempt the archival.
/
16257, 00000, "Switchover initiated stop apply successfully completed"
// *Cause: SQL Apply was stopped because of a switchover.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/
16258, 00000, "marking index unusable due to a constraint violation"
// *Cause: A constraint violation occurred during the apply of a
// direct path load. The index will be marked unusable and the
// apply will be restarted.
// *Action: No action necessary. See alert log for index schema and name.
/
16259, 00000, "Switchover to logical standby requires a log archive destination"
// *Cause: A valid log archive destination was not found to which the local
// system could archive the end of redo (EOR) log file. A minimum of
// one destination is required.
// *Action: Ensure all log archive destinations are properly configured and,
// if applicable, have network connectivity before reissuing the
// ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY DDL
// operation.
/
16260, 00000, "Waiting to replace partial or corrupt log file (thread# %s, sequence# %s)"
// *Cause: LogMiner Reader process reached the end of a partial log file or
// encountered a corrupted block. It is now waiting for the log file
// to be recovered and reregistered.
// *Action: No action necessary. Once the fetch archive log (FAL) archiver
// replaces the log file, standby will automatically restart to
// process the replaced file.
/
16261, 00000, "Identification key mismatch for table \"%s\".\"%s\"."
// *Cause: Internal error in SQL Apply.
// *Action: Contact Oracle Support Services.
/
16262, 00000, "Invalid value specified for Logical Standby parameter"
// *Cause: The value specified in APPLY_SET is invalid for the parameter.
// *Action: Specify correct parameter value. Please refer to documentation on
// DBMS_LOGSTDBY PL/SQL package for details.
/
16263, 00000, "Dynamic parameters can only be set on SQL apply instance"
// *Cause: Attempt to set a Logical standby dynamic parameter on an instacne
// other than where SQL apply coordinator is running.
// *Action: Connect to the instance where SQL apply coordinator is running and
// reissue the statement.
/
16264, 00000, "invalid value for PREPARE_SERVERS parameter"
// *Cause: attempt to set PREPARE_SERVERS parameter to zero or to a
// value which would require MAX_SERVERS to be increased.
// *Action: set PREPARE_SERVERS parameter to a non zero value and or
// increase MAX_SERVERS parameter accordingly.
/
16265, 00000, "Unsupported PL/SQL procedure encountered"
// *Cause: Apply encountered an unsupported procedure from an Oracle
// supplied PL/SQL package that is otherwise supported
// *Action: Either add a skip rule for this procedure or manually apply the
// procedure and restart apply skipping the failed transaction
// Please refer to documentation on the PL/SQL package for details.
/
16266, 00000, "Cannot instantiate a Logical Standby from another Logical Standby"
// *Cause: An instantiation of a Logical Standby has been attempted for
// another database with the Logical Standby role, which is not
// supported.
// *Action: Instantiate a Logical Standby database only from a Primary
// Database.
/
16267, 00000, "Cannot instantiate a Logical Standby during a switchover"
// *Cause: An instantiation of a Logical Standby has been attempted for
// a primary database that is in the middle of a switchover.
// *Action: Execute ALTER DATABASE PREPARE TO SWITCHOVER CANCEL to cancel
// the switchover, and attempt the instantiation again.
/
16268, 00000, "user procedure processing of logical standby apply PL/SQL"
// *Cause: A user-provided stored procedure was called to inspect a
// PL/SQL statement prior to the statement being processed.
// *Action: No action necessary, this informational statement is provided
// to record user involvement in the processing of a statement.
// Additional information can be found in the DBA_LOGSTDBY_EVENTS
// and the DBA_LOGSTDBY_SKIP views.
/
16269, 00000, "PL/SQL procedure skipped due to failure on primary database"
// *Cause: Because the PL/SQL procedure failed when executed on the
// primary database, it could not be executed on the standby database.
// *Action: This informational statement is provided to record the event for
// diagnostic purposes. The failed PL/SQL procedure needs to be
// investigated to ensure it did not commit interesting data
// before it failed.
/
16270, 00000, "PL/SQL procedure skipped due to unmaintained standby objects"
// *Cause: Because the PL/SQL procedure manipulated objects not being
// maintained by the standby database, it was skipped.
// *Action: No action necessary. This informational statement is provided
// to record the event for diagnostic purposes.
/
16271, 00000, "PL/SQL successfully applied"
// *Cause: A PL/SQL procedure was successfully applied on the logical
// standby database.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/
16272, 00000, "PL/SQL procedure skipped due to skip setting"
// *Cause: A setting in the logical standby skip table indicated
// that this PL/SQL procedure should always be skipped.
// *Action: No action necessary, this informational statement is provided
// to record the event for diagnostic purposes.
/
16273, 00000, "invalid value for APPLY_SERVERS parameter"
// *Cause: attempt to set APPLY_SERVERS parameter to zero or to a
// value which would require MAX_SERVERS to be increased.
// *Action: set APPLY_SERVERS parameter to a non zero value or
// increase MAX_SERVERS parameter accordingly.
/
16274, 00000, "failure to perform operation on all Oracle RAC instances"
// *Cause: One or more instances encountered an error while performing
// an operation.
// *Action: Ensure every instance in the Oracle RAC meets the requirements
// for the operation, and retry the operation.
/
16275, 00000, "prior failed CTAS detected and pre-existing table dropped"
// *Cause: During the processing of a CTAS operation, an existing empty
// table with the same name and attributes as the CTAS source table
// was found, and the table was dropped.
// *Action: No action is necessary. This informational statement is provided
// to record the event for diagnostic purposes.
16276, 00000, "specified database link does not correspond to primary database"
// *Cause: The database link specified to DBMS_LOGSTDBY.INSTANTIATE_TABLE did
// not link to the primary database for this logical standby database.
// *Action: Specify a database link that corresponds to the primary database
// for this logical standby database. The link should have
// privileges to read and lock the table being instantiated, as well
// as the SELECT_CATALOG_ROLE.
16277, 00000, "specified table is not supported by logical standby database"
// *Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE to instantiate
// an unsupported table on the logical standby database. Tables with
// unsupported data types cannot be replicated to a logical standby
// database.
// *Action: Specify a table which is not listed in the
// DBA_LOGSTDBY_UNSUPPORTED_TABLE view.
16278, 00000, "specified table has a multi-object skip rule defined"
// *Cause: A table that is instantiated via DBMS_LOGSTDBY.INSTANTIATE_TABLE
// must not have any skip rules defined with wildcard characters.
// *Action: Remove or rewrite any skip rules defined for the specified table
// so that they no longer contain wildcard characters, or no longer
// affect the specified table.
16279, 00000, "supplied dblink does not have sufficient privileges"
// *Cause: A dblink was specified that lacked one or more of the
// CONNECT, RESOURCE, or SELECT_CATALOG_ROLE roles or that connects
// to a user with insufficient privileges to lock the table.
// *Action: Grant the necessary privileges to the dblink and the user to
// which the dblink connects and retry the operation.
/
16280, 00000, "cannot change master key on a logical standby database"
// *Cause: An attempt was made to change the master key for transparent
// data encryption on a logical standby database.
// *Action: Set GUARD to NONE and reissue the command. This prevents you
// from replicating tables with encrypted columns from the
// primary database.
/
16281, 00000, "missing identification key for table \"%s\".\"%s\"."
// *Cause: No identification key was created for specified table.
// *Action: Create a primakey key or unique index for specified table.
/
16282, 00000, "operation not permitted during rolling upgrade"
// *Cause: An operation was attempted that is not supported during a
// rolling upgrade.
// *Action: Retry the operation upon completion of the upgrade.
/
16283, 00000, "operation not permitted on non-apply instance"
// *Cause: An operation was attempted that is not supported since it
// requires a running logical apply on the local instance.
// *Action: Retry the operation on the instance on which the apply
// engine is running.
/
16284, 00000, "timed out waiting for an in-progress operation to complete"
// *Cause: An operation timed out waiting for another operation to complete.
// *Action: Retry the operation when the in-progress operation has
// completed.
/
16285, 00000, "operation not permitted due to inconsistent role state"
// *Cause: A prior attempt to change the role of this database has failed
// before the new role state could be fully committed.
// *Action: Retry the previously attempted role-related operation before
// attempting the current operation.
/
16286, 00000, "operation not permitted due to lack of synchronized destination"
// *Cause: A synchronized log archive destination was not found to which the
// end-of-redo log file could be archived.
// *Action: Before re-attempting the operation, wait at least one minute for
// the Remote File Server to automatically recover any missing log
// files or manually recover and register any missing log files with
// logical standby.
/
16287, 00000, "operation not permitted due to active apply state"
// *Cause: An operation was attempted that was not supported while the logical
// standby database had an active apply state.
// *Action: Confirm the procedures used to configure the logical standby
// database. Procedures which attempt to reconfigure a logical standby
// database for a new primary database may encounter this error if an
// error in a preliminary step was encountered.
/
16288, 00000, "DDL skipped due to missing edition \"%s\""
// *Cause: The edition in which the DDL was performed on the primary
// did not exist on the standby database.
// *Action: No action is necessary. This informational statement is provided
// to record the event for diagnostic purposes.
/
16289, 00000, "unable to access Pluggable Database \"%s\""
// *Cause: Logical standby attempted to access a Pluggable Database
// that did not exist.
// *Action: Create or plug in the specified Pluggable Database or add an
// appropriate skip rule and then restart logical standby.
/
16290, 00000, "cannot alter the session logical replication state within a transaction"
// *Cause: A transaction was already in progress.
// *Action: Commit or rollback the transaction and then reexecute.
/
16291, 00000, "operation not permitted due to incomplete setup"
// *Cause: An operation was denied due to the logical standby being in a
// transitional state.
// *Action: Perform any multistep procedures such as instantiation, switchover,
// or failover to completion as written in the documentation.
/
16292, 00000, "cannot replicate ALTER TABLE ADD COLUMN with sequence default value"
// *Cause: The logical standby database attempted to replicate an unsupported
// DDL statement. The DDL added a column with a sequence as the
// default with compatiblity set to a release earlier than 12.2.0.2.0.
// *Action: The table must be re-instantiated from the primary database using
// DBMS_LOGSTDBY.INSTANTIATE_TABLE().
16293, 00000, "cannot replicate a failed ALTER TABLE ADD COLUMN"
// *Cause: The logical standby database attempted to replicate a failed
// ALTER TABLE ADD COLUMN for an identity column, but the operation
// could not be rolled back on the target.
// *Action: The added columns must be dropped from the table on the target
// before restarting apply, or the table must be reinstantiated.
16300, 00000, "LSBY architected tracing event"
// *Cause:
// *Action:
/
16301, 00000, "LSBY debug event"
// *Cause:
// *Action:
// *Document: NO
/
16302, 00000, "extended data type support is not supported for specified table"
// *Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that
// was not supported for such an operation. The table either
// does not have a primary key or it has a data type not supported
// by this procedure.
// *Action: Specify a table for which support exists in EDS_ADD_TABLE.
/
16303, 00000, "specified table already has extended data type support"
// *Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that
// already had EDS added on the local database.
// *Action: None
/
16304, 00000, "procedure must first be called on primary database"
// *Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE on a logical
// standby database without having first called it on the primary
// database.
// *Action: Call DBMS_LOGSTDBY.EDS_ADD_TABLE on the primary database and
// then retry on the standby.
/
16305, 00000, "procedure not supported on a logical standby"
// *Cause: A call was made to DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on a logical
// standby database which can only be called on a primary database
// *Action: Call DBMS_LOGSTDBY.EDS_EVOLVE_TABLE on the primary database
/
16306, 00000, "specified table does not have a primary key"
// *Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table that
// did not have a primary key.
// *Action: Add a primary key and retry the operation.
/
16307, 00000, "TSE key %s successfully applied"
// *Cause: An ALTER SYSTEM SET ENCRYPTION KEY statement was successfully
// committed on the logical standby database.
// *Action: No action necessary. This informational statement is provided
// to record the event for diagnostic purposes.
/
16308, 00000, "specified table has extended data type support"
// *Cause: A call was made to DBMS_LOGSTDBY.INSTANTIATE_TABLE for a table
// that is being maintained by extended data type support.
// *Action: Call DBMS_LOGSTDBY.EDS_REMOVE_TABLE followed by either
// DBMS_LOGSTDBY.EDS_ADD_TABLE or a retry of the operation.
/
16309, 00000, "extended data type support evolve operation not yet started"
// *Cause: A call was made to finish an extended data type support evolve
// operation without having first started the operation.
// *Action: Call DBMS_LOGSTDBY.EDS_EVOLVE_MANUAL with START option and then
// retry.
/
16310, 00000, "extended data type support evolve operation in progress"
// *Cause: An extended data type support evolve operation was started
// but not yet completed.
// *Action: Wait a few seconds and retry the command if automatic evolve has
// been enabled or call DBMS_LOGSTDBY.EDS_EVOLVE_MANUAL with the
// FINISH option and then retry.
/
16311, 00000, "materialized view log already exists"
// *Cause: A call was made to DBMS_LOGSTDBY.EDS_ADD_TABLE for a table
// with a LOB that requires the creation of a specifically-defined
// materialized view log but one already exists.
// *Action: Drop the existing materialized view log and retry the operation.
/
16330, 00000, "error in container \"%s\""
// *Cause: An operation was attempted on a container and an error occurred.
// *Action: Address the failure condition and then retry.
/
16331, 00000, "container \"%s\" is not open"
// *Cause: An operation was attempted on a container. However, the container
// was not open.
// *Action: Open the container and then retry.
/
16332, 00000, "logical standby encountered non-fatal error ORA-%s during DDL execution"
// *Cause: Logical standby apply encountered a non-fatal error during
// DDL execution and continued to process subsequent transactions.
// *Action: This error is informational only. No user action is required.
/
16333, 00000, "_MAX_LOG_LOOKBACK parameter not sufficiently larger than MAX_SGA"
// *Cause: _MAX_LOG_LOOKBACK or MAX_SGA parameter was set to a value
// that will lead to decreased performance.
// *Action: Reset parameters such that _MAX_LOG LOOKBACK is at least 5 times
// the value of MAX_SGA.
/
16334, 00000, "skip procedure does not exist"
// *Cause: The specified skip procedure did not exist.
// *Action: Ensure that the specified skip procedure exists and is accessible
// by the calling user.
/
/ 16375 - 16499 Reserved for Physical Standby
/ Note: Please add new numbers from here downward to 16375!
/
16395, 00000, "ADG standby session terminated"
// *Cause: ADG standby session was stopped because server detected that
// the primary database connection associated with redirected
// statement execution is lost.
// *Action: Reconnect to ADG standby database and re-run the statement.
/
16396, 0000, "Internal event for Oracle Active Data Guard SQL redirection"
// *Document: NO
// *Cause: This is an Oracle internal event code. It is used to test and
// simulate redirection of SQL execution from ADG standby database
// to primary database.
// *Action: N/A, this is an Oracle internal event code.
/
16397, 00000, "statement redirection from Oracle Active Data Guard standby database to primary database failed"
// *Cause: The statement redirection failed because of one of the following reasons:
// 1. The primary database connect string was not established.
// 2. The primary database could not be reached.
// 3. The undo-mode or incarnation were not the same.
// 4. The current user and logged-in user were not the same.
// 5. Redirecting CREATE TABLE AS SELECT (CTAS) of the global temporary
// table was not supported.
// *Action: Run the statement after fixing the condition that caused the failure.
/
16398, 00000, "online log has been reused and archived log cannot be found"
// *Cause: ASYNC redo transport was unable to find either an online log or
// archived redo log that represents the current live redo sequence
// number.
// *Action: No action is required.
/
16399, 00000, "current redo has moved to a new branch"
// *Cause: A new branch was detected by ASYNC redo transport. No further redo
// will be transferred from the old branch. ASYNC redo transport will
// commence on the new branch.
// *Action: No action is required.
/
16400, 00000, "quota attributes are not allowed with DB_RECOVERY_FILE_DEST"
// *Cause: Quota attributes for the destination parameters are not allowed
// when the parameter DB_RECOVERY_FILE_DEST is defined.
// *Action: No action is required.
/
16401, 00000, "archive log rejected by Remote File Server (RFS)"
// *Cause: An attempt was made to re-archive an existing archive log.
// *Action: See alert log and trace file for more details.
// No action is necessary. This is an informational statement provided
// to record the event for diagnostic purposes.
/
16402, 00000, "TRANSPORT=ONDEMAND is unsupported."
// *Cause: The ARCHIVELOG destination TRANSPORT=ONDEMAND attribute was
// specified on the primary database.
// *Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this
// attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
16403, 00000, "shut down in progress - remote connection is not permitted"
// *Cause: A redo transport session could not be started because the database
// was shutting down.
// *Action: Wait for the remote instance to be restarted, or contact your DBA.
/
16404, 0000, "Internal event for simulating software version mismatches"
// *Document: NO
// *Cause: This is an Oracle internal event code. It is used to test software
// version mismatches between the primary and a standby database.
// Setting this event causes the software version number to be
// incremented by the value of the event level.
// *Action: N/A, this is an Oracle internal event code.
/
16405, 0000, "Internal event for simulating software version mismatches"
// *Document: NO
// *Cause: This is an Oracle internal event code. It is used to test software
// version mismatches between the primary and a standby database.
// Setting this event causes the software version number to be
// decremented by the value of the event level.
// *Action: N/A, this is an Oracle internal event code.
16406, 0000, "primary and standby database software version mismatch"
// *Cause: The primary and standby databases were not running compatible
// versions of Oracle server software.
// *Action: Install the correct Oracle server software and try again.
16407, 00000, "An archive log from an earlier redo branch has been rejected"
// *Cause: An archive log from a redo branch that is earlier than the one that
// the standby database is currently applying was rejected.
// *Action: No action is required.
16408, 00000, "An archive log from an incompatible redo branch has been rejected."
// *Cause: An archive log from a redo branch that is incompatible with the one
// that the standby database is currently applying was rejected.
// *Action: No action is required.
16409, 00000, "archive log switchover reference number mismatch"
// *Cause: The archive log switchover reference numbers of the primary
// and standby database did not match. Remote archival of redo log
// files is not allowed to incompatible standby database instances.
// *Action: No action is required.
16410, 00000, "enable simulated LGWR netslave infinite wait"
// *Document: NO
// *Cause: Causes the LGWR to wait indefinitely to simulate network
// connection indefinite stall.
// *Action: N/A, this is an Oracle internal event code.
16411, 00000, "TRANSPORT=ONDEMAND is unsupported"
// *Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was
// specified on the primary database.
// *Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this
// attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
16412, 00000, "TRANSPORT=ONDEMAND is unsupported"
// *Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was
// specified on the primary database.
// *Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this
// attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
16413, 00000, "TRANSPORT=ONDEMAND is unsupported"
// *Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was
// specified on the primary database.
// *Action: Use of the TRANSPORT=ONDEMAND is no longer supported. Remove this
// attribute from the LOG_ARCHIVE_DEST_n initialization parameter.
16414, 0000, "Event to prevent MRP from clearing online redo log files"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used to
// prevent the MRP process from automatically creating or clearing
// the online redo log files (ORLs) on a standby database.
// *Action: N/A, this is an Oracle internal event code.
/
16415, 0000, "Event to enable lock dumping"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used
// to enable dumping of lock structures when desired.
// *Action: N/A, this is an Oracle internal event code.
/
16416, 00000, "No viable %sswitchover targets available"
// *Cause: Switchover failed because no standby databases of the appropriate
// type were available.
// *Action: Check the alert log for errors, correct the problem and retry the
// switchover.
/
16417, 00000, "Activation occurred after recovery from standby redo log files; a full database backup is required"
// *Cause: Activation occurred after recovery from standby redo log files.
// *Action: Take a full database backup.
/
16418, 0000, "Event to simulate idle RFS process in Physical Standby"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used
// to simulate idle RFS process in Physical Standby
// *Action: N/A, this is an Oracle internal event code.
/
16419, 00000, "Snapshot standby must be converted to a physical standby database."
// *Cause: The database was not a physical standby database.
// *Action: Convert to physical standby database and retry the operation.
/
16420, 00000, "fast-start failover target cannot be converted to snapshot standby"
// *Cause: The database chosen for conversion to a snapshot standby was
// the fast-start failover target standby database.
// *Action: Choose another physical standby database and retry the operation.
/
16421, 00000, "Event to disable streaming network I/O for Data Guard"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used
// to disable streaming I/O for vaious Data Guard processes.
// *Action: N/A, this is an Oracle internal event code.
/
16422, 0000, "Event to disable archive process functions"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used
// to disable archive process functions
// *Action: N/A, this is an Oracle internal event code.
/
16423, 0000, "Event to test ASM mirrors in Physical Standby"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used
// to test ASM mirrors in Physical Standby.
// *Action: N/A, this is an Oracle internal event code.
/
16424, 0000, "RECOVER FINISH cannot complete due to a redo gap."
// *Cause: RECOVER FINISH failed because there was a redo gap on the standby
// database.
// *Action: Resolve redo gap or issue ALTER DATABASE ACTIVATE STANDBY DATABASE
// to perform an immediate failover with some data loss.
/
16425, 0000, "RECOVER FINISH cannot be issued when recovery branch %s is not the target branch %s."
// *Cause: RECOVER FINISH failed because a new branch existed on the physical
// standby database.
// *Action: Issue real-time apply recovery and see if recovery can proceed
// on the new branch by checking if logs on the new branch are
// applied by recovery. If so, issue another RECOVER FINISH.
// Otherwise, issue ALTER DATABASE ACTIVATE STANDBY DATABASE.
/
16426, 0000, "Recovery requested an incorrect log from which to apply redo data."
// *Cause: Media recovery selected an incorrect log.
// *Action: Verify that the appropriate log has been properly registered
// and restart media recovery.
/
16427, 0000, "Redo gap is too large to resolve."
// *Cause: The redo transport lag at this database was too large for
// automatic redo gap detection to take place.
// *Action: Re-create this standby database from a current backup copy of the
// primary database.
/
16428, 0000, "Event to set timeout value for ORA-19528 error"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used
// to set the timeout value for the ORA-19528 error.
// *Action: N/A, this is an Oracle internal event code.
/
16429, 0000, "Event to disable Redo Transport Compression (RTC) back-off logic"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used to
// disable Redo Transport Compression (RTC) back-off logic.
// *Action: N/A, this is an Oracle internal event code.
/
16430, 00000, "Event to kick off krs*.c error path tests"
// *Document: NO
// *Cause: Oracle internal testing only
// *Action: N/A, this is an Oracle internal event for test purposes (valid
// values are 1-26, 1 for krsa.c up through 26 for krsz.c)
/
16431, 00000, "cannot expand control file"
// *Cause: Additional redo log threads were added on the primary database
// after the standby control file was created.
// *Action: Shut down the standby database and replace the control file with a
// new standby control file from the primary database or change the
// COMPATIBLE parameter to 10.2.0 or above and restart the standby
// database.
/
16432, 00000, "inconsistent set of logs applied at a standby database"
// *Cause: Redo apply stopped because it detected an inconsistency in the
// progression of the SCNs. If this database is a bystander standby
// database, this is most likely due to a failover operation in which
// incompatible logs were applied from the old and new primary
// databases.
// *Action: Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from
// V$DATABASE on the new primary database. Then, flashback the target
// database to this SCN and use RMAN to delete all archive logs at or
// beyond this SCN. Finally, fetch all terminal end of redo (EOR) logs
// corresponding to the failover operation from the new primary and
// register all these logs at the target database. Restart redo apply.
/
16433, 00000, "The database or pluggable database must be opened in read/write mode."
// *Cause: An attempt was made to open the database or pluggable database in
// read-only mode after an operation that requires the database or
// pluggable database be opened in read/write mode.
// *Action: Open the database in read/write mode. The database can then be
// opened in read-only mode.
16434, 00000, "archive log for branch %s thread %s sequence %s cannot be queued"
// *Cause: An archive log needed by the standby database to resolve a redo gap
// was not found on the source database. This is a fatal situation
// during a switchover or far sync instance assisted failover because
// the source database waits for the target standby to be clear of
// all archive log gaps before allowing the operation to proceed. If
// a redo gap cannot be resolved during these operations, the
// operation cannot succeed so it must be failed.
// *Action: If the specified log is listed in V$ARCHIVED_LOG for the DEST_ID
// of the local destination on the source database but no longer
// exists at that location on disk, the archived log can be copied
// back to that location to allow gap processing to automatically
// resolve the gap. If the specified log has been purged from
// V$ARCHIVED_LOG, the archived log can be copied to disk on either
// the source or destination database and registered using the
// ALTER DATABASE REGISTER OR REPLACE LOGFILE command.
/
16436, 00000, "ALTER DATABASE ... RECOVER FINISH could not start"
// *Cause: ALTER DATABASE ... RECOVER FINISH failed to start because the
// standby database was missing redo changes below the checkpoint of
// data files.
// *Action: Issue ALTER DATABASE ACTIVATE STANDBY DATABASE command instead.
/
16437, 00000, "No active coordinator RFS for current operation"
// *Cause: The coordinator Remote File Server (RFS) for this parallel archival
// either abnormally terminated or ran down before this subordinate
// RFS could begin its leg of the operation.
// *Action: No explicit user action is required.
/
16438, 00000, "Switchover to primary cannot be executed at this time"
// *Cause: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY could not be
// executed because an incompatible operation such as
// RMAN restore or flashback was in progress. See the database alert
// log for details.
// *Action: Wait for the incompatible operation to complete. The files that
// have been flashed back or restored need recovery before you
// can reissue ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
// statement. Start redo apply and verify that the
// SWITCHOVER_STATUS column of the V$DATABASE view reports TO_PRIMARY
// or SESSIONS_ACTIVE before retrying ALTER DATABASE COMMIT TO
// SWITCHOVER TO PRIMARY.
/
16439, 00000, "Standby not ready to receive redo at this time"
// *Cause: A logical standby or down stream capture database was not in a
// state where it could accept a request to receive redo from
// another database. This was likely due to the database not being
// open.
// *Action: See the database alert log at the receiving side of the transfer
// for details of why the database was not ready.
// If the database was mounted but not open, open it to clear
// the problem. The initialization parameter
// LOG_ARCHIVE_DEST_STATE_n at the sending site may need to be
// set to ENABLE.
//
/ NOTE: 16440 - 16447 are reserved for Flush Redo To Standby project.
/
16440, 00000, "Control file is corrupt."
// *Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the control file
// was corrupt.
// *Action: Restore the current control file at the primary database and then
// reissue ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted
// primary instance.
/
16441, 00000, "Current log %s for thread %s sequence %s is invalid."
// *Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the current redo
// log file was corrupt.
// *Action: Restore the current log at the primary database, and then reissue
// ALTER SYSTEM FLUSH REDO TO STANDBY from a mounted
// primary instance.
/
16442, 00000, "ALTER SYSTEM FLUSH REDO TO STANDBY succeeded, but some redo has not been applied."
// *Cause: The target standby database did not apply all received redo.
// *Action: Allow the target standby database to apply all redo and then
// reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement.
/
16443, 00000, "could not switch out of log %s thread %s"
// *Cause: ALTER SYSTEM FLUSH REDO TO STANDBY could not switch out of the
// current log.
// *Action: This can happen if there are one or more errors during archival of
// the current log at the primary database. Reissue ALTER SYSTEM FLUSH
// REDO TO STANDBY after resolving the archiving errors.
/
16444, 00000, "ALTER SYSTEM FLUSH REDO TO STANDBY failed due to a corrupted control file or online log file."
// *Cause: A flush redo operation discovered SCNs greater than a previously
// failed flush redo operation.
// *Action: This can happen if there are one or more errors that have
// corrupted the control file or online redo logs. In these cases,
// flush redo operation is not possible.
/
16445, 00000, "Database has to be mounted and cannot be open"
// *Cause: ALTER SYSTEM FLUSH REDO TO STANDBY required that the database be
// mounted, but not opened.
// *Action: Mount the database and then reissue the operation.
/
16446, 00000, "Target database was not a standby database"
// *Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because the target
// database is not a standby database.
// *Action: Reissue the ALTER SYSTEM FLUSH REDO TO STANDBY statement and
// specify a standby database as the target database.
/
16447, 00000, "Redo apply was not active at the target standby database"
// *Cause: ALTER SYSTEM FLUSH REDO TO STANDBY failed because redo apply
// is not active at the target database.
// *Action: Start redo apply at the standby database and reissue the
// ALTER SYSTEM FLUSH REDO TO STANDBY statement, or reissue the
// ALTER SYSTEM FLUSH REDO TO STANDBY statement with the
// NO CONFIRM APPLY clause.
/
16448, 00000, "media recovery is still active after %s seconds"
// *Cause: The media recovery did not stop after the timeout.
// *Action: Look at the alert log or trace file for more information.
/
16449, 00000, "incomplete redo thread enable operation"
// *Cause: The switchover operation could not continue because it failed to
// disable a thread that was left in an incomplete thread enable
// state.
// *Action: Check alert log for more details.
/
16450, 00000, "Internal event for disabling ignoring of destination during open"
// *Document: NO
// *Cause: This is an internal event used for testing purposes. It is use
// for disabling the ability to ignore max perf destinations during
// open of database. It is used for testing various situations
// with foreground death performing the open as it pertains to
// ignoring max perf destinations.
// *Action: No action is necessary.
/
16451, 00000, "A remote archival request has timed out."
// *Cause: When opening or closing a database instance, the database may wait
// for up to 1 minute for pending remote archival requests to be
// performed before proceeding with the operation. This error was
// reported because that time limit was exceeded.
// *Action: This is an informational message so no action is required.
/
16452, 00000, "internal event for SRL-related testing"
// *Document: NO
// *Cause: This is an internal event code. This event is used
// for SRL-related testing.
// *Action: NA. This is an Oracle internal event code.
/
16453, 0000, "Event for the first Timing Measurement Interface (TMI)"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used
// to measure the difference in performance of Physical Standby
// across different labels.
// *Action: N/A, this is an Oracle internal event code.
/
16454, 0000, "Standby redo log could not be selected"
// *Document: NO
// *Cause: Selection of standby redo log failed. Check the trace
// file for the exact cause.
// *Action: This is used internally. No action is required.
/
16455, 00000, "switchover to standby failed"
// *Cause: An attempt to switchover to a physical standby database failed.
// *Action: Check alert log for more details. Issue the SHUTDOWN ABORT command
// on the database before issuing another ALTER DATABASE COMMIT TO
// SWITCHOVER TO STANDBY command.
/
16456, 00000, "switchover to standby in progress or completed"
// *Cause: The requested operation was not allowed because a switchover to
// standby operation was either in progress or had completed.
// *Action: Issue the SHUTDOWN ABORT command on the database after switchover
// operation completes.
/
16457, 00000, "Event to inject CFTXN errors during testing"
// *Document: NO
// *Cause: Oracle internal testing only.
// *Action: None. This is an Oracle internal event for test purposes.
/
16458, 00000, "Event to invoke I/O hangs during testing"
// *Document: NO
// *Cause: Oracle internal testing only.
// *Action: None. This is an Oracle internal event for test purposes.
16459, 00000, "recovery already beyond standby failover"
// *Cause: Redo Apply stopped because it detected that it had proceeded
// beyond a standby failover operation.
// *Action: Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from
// V$DATABASE on the new primary database. Then, flashback the target
// database to this SCN and use RMAN to delete all archive logs at or
// beyond this SCN. Finally, fetch all terminal end-of-redo (EOR) logs
// corresponding to the failover operation from the new primary
// database and register all these logs at the target database.
// Restart Redo Apply.
16460, 00000, "Event for general use with redo transport testing"
// *Document: NO
// *Cause: Oracle internal testing only.
// *Action: None. This is an Oracle internal event for test purposes.
16461, 00000, "database not flashed back or recovered to a consistent point"
// *Cause: ALTER DATABASE CONVERT TO STANDBY command failed because either
// the database was not properly flashed back to
// STANDBY_BECAME_PRIMARY_SCN, or at least one of the online data
// files was not current.
// *Action: Flashback database to STANDBY_BECAME_PRIMARY_SCN and retry the
// ALTER DATABASE CONVERT TO STANDBY command.
16462, 00000, "Event to generate a testing log file header"
// *Document: NO
// *Cause: Oracle internal testing only.
// *Action: None. This is an Oracle internal event for test purposes.
/
16463, 00000, "invalid target database name"
// *Cause: ALTER DATABASE FAILOVER TO <target_db_name> or ALTER DATABASE
// SWITCHOVER TO <target_db_name> FORCE command failed because the
// target_db_name was invalid. The target_db_name must be the same
// as the name of the database on which the SQL command is issued.
// *Action: Change the target database name and reissue the command.
/
16464, 00000, "operation must be initiated on a physical standby database"
// *Cause: An attempt was made to issue the ALTER DATABASE FAILOVER TO
// <target_db_name> or the ALTER DATABASE SWITCHOVER TO
// <target_db_name> FORCE command on a database other than a physical
// standby database.
// *Action: Issue the command on a physical standby database.
/
16465, 0000, "operation must be initiated on an open primary database"
// *Cause: An attempt was made to issue the ALTER DATABASE SWITCHOVER TO
// <target_db_name> [VERIFY] or ALTER DATABASE COMMIT TO SWITCHOVER
// TO STANDBY command on a database other than an open
// primary database.
// *Action: Issue the command on an open primary database.
/
16466, 0000, "invalid switchover target"
// *Cause: The switchover target was not a valid, enabled, or active
// standby database.
// *Action: Fix the problem in the switchover target and reissue the command.
/
16467, 0000, "switchover target is not synchronized"
// *Cause: The switchover target was not synchronized with the primary
// database.
// *Action: Wait until the switchover target is synchronized with the primary
// database, then reissue the command.
/
16468, 0000, "error connecting to switchover target %s"
// *Cause: The primary database could not connect to the switchover target.
// *Action: Check the alert log for detailed errors.
/
16469, 0000, "switchover target version number is lower than 12"
// *Cause: The switchover target version number was lower than 12.
// *Action: Upgrade the switchover target to a higher release.
/
16470, 0000, "Redo Apply is not running on switchover target"
// *Cause: The switchover target was not running Redo Apply.
// *Action: Start Redo Apply on the switchover target and reissue the command.
/
16471, 0000, "cannot convert switchover target %s to a primary database"
// *Cause: Switchover failed because the switchover target could not convert
// to a primary database.
// *Action: Check the database role of the switchover target.
// If the switchover target database role is standby, do one of the
// following:
// - Fix the problem shown in the alert log.
// - Issue the remedial ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE
// command to convert the switchover target to a primary database.
// - If the problem in the switchover target cannot be fixed, issue
// the remedial ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE
// command on the old primary database to convert the old primary
// database back to a primary database.
//
// If the switchover target database role is primary, the switchover
// has completed. Open the switchover target and startup the old primary
// database to finish the switchover process.
/
/
16472, 0000, "failover failed due to data loss"
// *Cause: The database was in MaxAvailability or MaxProtection mode but
// terminal recovery finished with data loss.
// *Action: For a data loss failover, issue ALTER DATABASE ACTIVATE STANDBY
// DATABASE command.
/
16473, 0000, "database is not in limbo"
// *Cause: The ALTER DATABASE SWITCHOVER TO <target_db_name> FORCE statement
// could not proceed because the database was in an active state.
// *Action: Ensure that the SWITCHOVER_STATUS column in the V$DATABASE view has
// the value TO PRIMARY or SESSIONS ACTIVE. If needed, start managed
// standby recovery and reissue the statement after the
// SWITCHOVER_STATUS column value changes to one of the above values.
/
16474, 0000, "target_db_name not found in the LOG_ARCHIVE_DEST_n parameter"
// *Cause: ALTER DATABASE SWITCHOVER TO <target_db_name> or ALTER SYSTEM
// FLUSH REDO TO <target_db_name> statement failed because the
// target_db_name was not defined in the LOG_ARCHIVE_DEST_n parameter.
// *Action: Ensure that the target_db_name is defined in the
// LOG_ARCHIVE_DEST_n parameter.
/
16475, 0000, "succeeded with warnings, check alert log for more details"
// *Cause: The ALTER DATABASE SWITCHOVER TO <target_db_name> VERIFY command
// succeeded but with warnings.
// *Action: Check alert log for more details.
/
16476, 00000, "far sync instance does not allow %s operation"
// *Cause: The specified operation was invalid on a far sync instance.
// *Action: Do not attempt the specified operation on a far sync instance.
/
16477, 00000, "destination is being serviced by another viable source"
// *Cause: An attempt was made by a far sync instance to perform gap analysis
// with a remote destination that already had connectivity with a
// different viable source of live redo.
// *Action: No action is required. This exception code is informational and
// is used by the far sync instance to remain idle with respect to
// this destination until it establishes connectivity with the primary
// database.
/
16478, 0000, "cannot locate far sync instance connect string"
// *Cause: The connect string for the far sync instance that is flagged as
// the source of live redo for this database could not be located.
// *Action: Define a LOG_ARCHIVE_DEST_n parameter for the far sync instance
// using the SERVICE attribute to define the connect string for
// the far sync instance destination. This destination should be
// set to DEFER using the corresponding LOG_ARCHIVE_DEST_STATE_n
// parameter. Once the connect string is defined, retry the
// failover operation. Using the FORCE option on the failover
// command allows the operation to proceed and bypass the
// far sync instance but bypassing the far sync instance increases
// the potential for data loss.
/
16479, 0000, "cannot connect to the far sync instance"
// *Cause: An attempt was made to connect to the far sync instance to help
// facilitate the failover operation but the connection attempt
// failed.
// *Action: Ensure that the far sync instance is mounted. Check the alert log
// and trace files on both the current database and the far sync
// instance for further details. Retry the operation if a problem is
// identified and corrected. Using the FORCE option on the failover
// command allows the operation to proceed and bypass the
// far sync instance but bypassing the far sync instance increases the
// potential for data loss.
/
16480, 0000, "operational error during far sync instance assisted failover"
// *Cause: After successfully connecting to the far sync instance, an error
// was encountered when polling the far sync instance for progress.
// *Action: Check the alert log and traces of both the current database and
// the far sync instance for further details. Retry the operation
// if a problem is identified and corrected. Using the FORCE option
// on the failover command allows the operation to proceed and
// bypass the far sync instance but bypassing the far sync instance
// increases the potential for data loss.
/
16481, 0000, "destination error during far sync instance assisted failover"
// *Cause: After successfully connecting to the far sync instance, an error
// was encountered when managing the failover target destination
// on the far sync instance.
// *Action: Check the alert log and traces of both the current database and
// the far sync instance for further details. Retry the operation
// if a problem is identified and corrected. Using the FORCE option
// on the failover command allows the operation to proceed and
// bypass the far sync instance but bypassing the far sync instance
// increases the potential for data loss.
/
16482, 00000, "a role transition is in progress"
// *Cause: The operation failed because a role transition was in progress.
// *Action: None.
/
16483, 00000, "unable to set a LOG_ARCHIVE_DEST_n parameter to the switchover target"
// *Cause: An attempt was made to set a LOG_ARCHIVE_DEST_n parameter to the
// switchover target failed.
// *Action: Manually set a LOG_ARCHIVE_DEST_n parameter to the switchover
// target.
/
16484, 00000, "compatibility setting is too low"
// *Cause: The compatibility setting in the redo log transported to this
// standby database exceeded the current compatibility setting.
// *Action: Check the compatibility setting on the primary and standby
// database, and increase the compatibility setting in the
// initialization parameter file on the standby database accordingly.
/
16485, 00000, "redo log is already received at destination"
// *Cause: A copy of this redo log was already received at the destination.
// *Action: None.
/
16486, 00000, "redo log is rejected by the destination"
// *Cause: The destination was not allowed to receive this redo log.
// *Action: Ensure the source database is registered at the destination,
// the destination is up and running, and storage is available.
// Or, examine the trace file of the Remote File Server (RFS) process.
/
16487, 00000, "the destination database is not writable"
// *Cause: The destination database was in read-only mode.
// *Action: Ensure the destination database is open for write.
/
16488, 00000, "cannot create a bookkeeping entry in database"
// *Cause: The destination database failed to create an entry in the
// table used to track the redo log file.
// *Action: Examine the trace file of the Remote File Server (RFS) process.
// Ensure that space is available in your database.
/
16489, 00000, "cannot register the redo log at the destination database"
// *Cause: Registering the redo log file to the destination database failed.
// *Action: Examine the trace file of the Remote File Server (RFS) process.
// Ensure that space is available in your database.
/
16490, 00000, "logging invalidated blocks on standby due to invalidation redo"
// *Document: NO
// *Cause: Event set to turn on logging invalidated blocks on standby due to invalidation redo"
// *Action: None.
/
16491, 00000, "operation not allowed due to insufficient online redo log files %s"
// *Cause: A minimum of two online redo log files per active thread were not supplied.
// *Action: Add the required redo log files and reissue the command.
/
16492, 00000, "switchover target local destination has error"
// *Cause: The switchover target local destination either exceeded quota size
// or had an error.
// *Action: Fix the problem in the switchover target and reissue the command.
/
16493, 00000, "using SYSDBA, SYSOPER, SYSDG, or SYSBKUP user for redo shipping to Recovery Appliance is not supported"
// *Cause: An attempt was made to use a SYSDBA, SYSOPER, SYSDG, or SYSBKUP user
// to ship redo logs to a Recovery Appliance.
// *Action: Use a user without the SYSDBA, SYSOPER, SYSDG, or SYSBKUP privilege
// to ship redo logs to a Recovery Appliance.
/
16494, 00000, "process started from pluggable database (PDB)"
// *Cause: The Remote File Server (RFS) process or Remote Message Interface
// (RMI) process or Fetch Archive Log (FAL) process was started from
// the PDB.
// *Action: Check the service name that the RFS or RMI or FAL client
// connected to. Ensure the service is not from PDB.
/
16495, 00000, "Using fast recovery area to receive redo log files on Recovery Appliance is not supported."
// *Cause: An attempt was made to use fast recovery area to receive redo log
// file on a Recovery Appliance.
// *Action: Do not configure fast recovery area for receiving redo log files
// on a Recovery Appliance.
16496, 00000, "corruption in network metadata packet"
// *Cause: Invalid or corrupt metadata was encountered in a network packet.
// *Action: No user action is required.
/
16497, 0000, "LOG_ARCHIVE_DEST_%s DELAY attribute is not 0"
// *Cause: The DELAY attribute was not 0 for the LOG_ARCHIVE_DEST_n parameter.
// Since the DELAY attribute delays standby database recovery,
// the switchover will be prolonged by that amount of time.
// *Action: Remove the DELAY attribute from the LOG_ARCHIVE_DEST_n parameter,
// then reissue the command.
/
16498, 00000, "Cancellation of managed recovery operation cannot be performed"
// *Cause: Cancellation of managed recovery was invoked when the Oracle
// Active Data Guard (Oracle ADG) instance recovery was running.
// *Action: None.
/
16499, 00000, "Event to dump redo transport information"
// *Document: NO
// *Cause: Oracle internal testing only.
// *Action: None. This is an Oracle internal event for diagnostic purposes.
/
/
/ 16500 - 16699 Reserved for Data Guard Broker
/
16501, 00000, "The Oracle Data Guard broker operation failed."
// *Cause: The Oracle Data Guard broker operation failed.
// *Action: See accompanying messages for details.
/
16502, 00000, "The Oracle Data Guard broker operation succeeded with warnings."
// *Cause: The Oracle Data Guard broker operation succeeded with warnings.
// *Action: See accompanying messages for details.
/
16503, 00000, "cannot exceed the maximum number of members in this configuration"
// *Cause: The Oracle Data Guard broker configuration already contained the
// maximum number of members that could be configured and managed
// by the broker.
// *Action: Select and remove an existing member from the broker
// configuration, then reissue the command to add another member
// to the configuration. Note that when COMPATIBLE is set lower
// than 11.2.0.0.0, the broker can configure and manage up to 10
// databases. When COMPATIBLE is set to 11.2.0.0.0 but less than
// 12.0.0.0.0, this limit is increased to 31. When COMPATIBLE is
// set to 12.0.0.0.0 or higher, this limit is increased to 254.
/
16504, 00000, "The Oracle Data Guard configuration already exists."
// *Cause: A request to create an Oracle Data Guard configuration was made
// while connected to a database that is part of an existing
// configuration.
// *Action: To create a new configuration, the existing configuration must be
// deleted.
/
16505, 00000, "site identifier is invalid"
// *Document: NO
// *Cause: The request contained an invalid site identifier. The was an
// internal error.
// *Action: Contact Oracle Support Services.
/
16506, 00000, "out of memory"
// *Cause: Process exceeded private or shared memory limits.
// *Action: Check for memory leaks, increase system parameters and restart.
/
16507, 00000, "unrecognized request identifier"
// *Document: NO
// *Cause: The specified request identifier was not recognized by
// the Oracle Data Guard broker. This was an internal error.
// *Action: Contact Oracle Support Services.
/
16508, 00000, "channel handle not initialized"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16509, 00000, "request timed out"
// *Cause: The Oracle Data Guard broker timed out the request.
// *Action: Check the Oracle Data Guard broker log file for more information.
// Ensure that the network connections between the databases are
// functioning properly and retry the request.
/
16510, 00000, "messaging error using ksrwait"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16511, 00000, "messaging error using ksrget"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16512, 00000, "parameter exceeded maximum size limit"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16513, 00000, "maximum requests exceeded"
// *Cause: The maximum number of requests that the broker can service
// on the database instance was exceeded.
// *Action: Wait for the broker to complete processing the requests before
// issuing more requests.
/
16514, 00000, "request was not found"
// *Document: NO
// *Cause: An attempt was made to read a response but a matching request
// was not found. This was an internal error.
// *Action: Contact Oracle Support Services.
/
16515, 00000, "no receive channel"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16516, 00000, "current state is invalid for the attempted operation"
// *Cause: The broker may have returned this error for either switchover
// operations or for database state change operations.
// If this error was returned for a switchover operation, the broker
// determined that either:
//
// - The databases changing roles were shut down.
// - The primary database was not shipping redo data.
// - The standby database that will become the primary database
// was not applying redo data.
//
// If this error was returned for database state change operations,
// the database state specified was invalid.
// *Action: If this error is returned when attempting a switchover operation,
// ensure that:
//
// - The databases changing roles are started.
// - The primary database is shipping redo data.
// - The standby database is applying redo data.
//
// If this error is returned when attempting a database state
// change operation, ensure that a valid database state is
// specified.
/
16517, 00000, "object handle is invalid"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16518, 00000, "unable to allocate virtual instance ID"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16519, 00000, "resource handle is invalid"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16520, 00000, "unable to allocate resource ID"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16521, 00000, "Service name specified in connect identifier connects to a pluggable database."
// *Cause: The connect identifier specified resulted in a connection to a
// pluggable database and not to the multitenant container database
// root.
// *Action: Check the connect identifier and confirm that it specifies a
// service name that results in a connection to the multitenant
// container database root.
/
16522, 00000, "configuration is part of Global Data Services pool"
// *Cause: The attempted command was not allowed because the configuration
// was part of a Global Data Services pool.
// *Action: Remove the configuration from the Global Data Services pool using
// GDSCTL. Then, retry the broker command. If the command was
// attempting to repair a database, disable or remove the individual
// database from the configuration and fix the issue. After the issue
// is resolved, reenable the database, or add the database back to
// the configuration if it had been removed.
/
16523, 00000, "operation requires the client to connect to instance \"%s\""
// *Cause: The switchover or failover operation required the client to
// connect to the apply instance of the target database.
// *Action: Connect to the indicated instance and reissue the SWITCHOVER or
// FAILOVER command.
/
16524, 00000, "unsupported command, option, or argument"
// *Cause: A command, option, or fast-start failover condition argument
// was specified that is not supported in this release.
// *Action: If trying to enable or disable a fast-start failover condition,
// try a different Oracle error number. Otherwise, contact Oracle
// Support Services.
/
16525, 00000, "The Oracle Data Guard broker is not yet available."
// *Cause: The Oracle Data Guard broker process was either not yet started,
// was initializing, or failed to start.
// *Action: If the broker has not been started, set the DG_BROKER_START
// initialization parameter to true and allow the broker to finish
// initializing before making the request. If the broker failed to
// start, check the Oracle Data Guard log for possible errors.
// Otherwise, retry the operation.
/
16526, 00000, "unable to allocate memory to process request"
// *Cause: The Oracle Data Guard broker was unable to allocate memory for a
// request.
// *Action: Increase the size of the System Global Area (SGA).
/
16527, 00000, "unable to allocate broker System Global Area (SGA) memory"
// *Cause: The Oracle Data Guard broker was unable to allocate memory within
// the System Global Area (SGA).
// *Action: Increase the size of the System Global Area (SGA) memory.
/
16528, 00000, "unable to allocate Program Global Area (PGA) memory"
// *Cause: There was insufficient space in Program Global Area (PGA) to
// allocate memory.
// *Action: Increase process virtual memory.
/
16529, 00000, "bad sender ID"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16530, 00000, "invalid buffer or length"
// *Cause: A NULL buffer or a length of zero was specified.
// *Action: Correct the command parameters and retry the command.
/
16531, 00000, "unable to post message"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16532, 00000, "Oracle Data Guard broker configuration does not exist"
// *Cause: A broker operation was requested that required a broker
// configuration to already be created.
// *Action: Create a Data Guard broker configuration prior to performing
// other broker operations. If only one instance of a RAC
// database is reporting this error, ensure that the
// DG_BROKER_CONFIG_FILE[1|2] initialization parameters are
// set to file locations that are shared by all instances of
// the RAC database.
/
16533, 00000, "inconsistent Data Guard broker state"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16534, 00000, "switchover, failover or convert operation in progress"
// *Cause: The Oracle Data Guard broker returned this status because a
// switchover, failover or convert operation was in progress. The
// broker could not accept new commands until the operation finished.
// *Action: Wait until the operation is complete and reissue the command.
/
16535, 00000, "Oracle Restart or Oracle Clusterware prevented completion of broker operation"
// *Cause: The broker could not complete the operation because Oracle Restart
// (for single instance databases) or Oracle Clusterware (for RAC
// databases) could not stop services or instances on this database.
// *Action: Check the Oracle Data Guard broker log file for more information
// and stop the appropriate services or instances using SRVCTL. Then
// retry the broker operation.
/
16536, 00000, "unknown object type"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16537, 00000, "child count exceeded"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16538, 00000, "no match on requested item"
// *Cause: The Oracle Data Guard broker did not recognize the specified
// property or state name, or a fast-start failover condition
// was specified that is not enabled.
// *Action: Verify the command parameters and reissue the command.
/
16539, 00000, "task element not found"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16540, 00000, "invalid argument"
// *Cause: One of the arguments for the specified command was invalid.
// *Action: Verify the arguments and then reissue the command.
/
16541, 00000, "member is not enabled"
// *Cause: The member specified in the command was not enabled.
// *Action: Select an enabled member and reissue the command.
/
16542, 00000, "unrecognized operation"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16543, 00000, "invalid request made to broker"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16544, 00000, "modifying DG_BROKER_START requires SID='*' qualifier"
// *Cause: The setting for the DG_BROKER_START parameter must be exactly
// the same on all RAC database instances. The SID='*' qualifier
// was required in the command.
// *Action: Reenter the command using the SID='*' qualifier.
/
16545, 00000, "unable to get response"
// *Document: NO
// *Cause: The Oracle Data Guard broker was unable to return the result of
// a previous request. This was an internal error.
// *Action: Contact Oracle Support Services.
/
16546, 00000, "missing or invalid value"
// *Document: NO
// *Cause: The value of the request to return was not specified or was
// invalid. This was an internal error.
// *Action: Contact Oracle Support Services.
/
16547, 00000, "cannot disable or remove the primary database"
// *Cause: An attempt was made to disable broker management of the primary
// database or remove the primary database from the broker
// configuration while the configuration was enabled.
// *Action: If you wish to disable broker management of the primary
// database when the configuration is enabled, you must instead
// disable broker management of the entire broker configuration.
// If you wish to remove the primary database from the broker
// configuration while the configuration is enabled, you must
// instead remove the entire broker configuration.
/
16548, 00000, "member not enabled"
// *Cause: An attempt was made to modify or query a disabled member.
// This error is also returned on an attempt to enable, modify,
// or query a member that the broker has disabled because of a
// switchover or failover operation. The broker disables its
// management of a member when it detects that the database needs
// to be re-created because of a failover or switchover operation.
// *Action: If broker management of the member is disabled, enable it
// and reissue the command.
/
16549, 00000, "invalid string"
// *Cause: An invalid or NULL string value was specified.
// *Action: Correct command parameters and retry.
/
16550, 00000, "truncated result"
// *Cause: A string property value was truncated due to insufficient
// buffer size.
// *Action: Specify a larger receive buffer.
/
16551, 00000, "short string copied"
// *Cause: A string property value that did not fill the receive buffer
// was placed in the receive buffer.
// *Action: This is an informational message only.
/
16552, 00000, "error occurred while generating directives for client"
// *Cause: The operation could not be completed because the broker
// required assistance from the client that it was unable to
// provide because of the accompanying error.
// *Action: See the accompanying error message for more information and
// follow the directions provided in the Action section of that
// message. Then retry the operation.
/
16553, 00000, "The Oracle Data Guard broker process (DMON) failed to shutdown."
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16554, 00000, "translation not valid"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16555, 00000, "member is not active"
// *Cause: An operation was attempted on a member that was not active.
// *Action: Verify that the member is active and retry the operation.
/
16556, 00000, "observer version mismatch"
// *Cause: This version of the observer was incompatible with the version
// of the specified Oracle database server to which the observer
// had been connected. This observer client cannot be used to
// observe the specified Oracle server.
// *Action: Use a version of the observer that is compatible with the
// Oracle database server to be observed.
/
16557, 00000, "member is already in use"
// *Cause: An attempt was made to create a duplicate member in the
// broker configuration, or to add a duplicate instance (SID)
// for an existing member in the broker configuration.
// *Action: Check the member to be added to ensure there are no duplicates.
/
16558, 00000, "database specified for switchover is not a standby database"
// *Cause: An attempt was made to switchover to a database that was not a
// standby database.
// *Action: Locate an enabled standby database and select that database as
// the target of the switchover.
/
16559, 00000, "out of memory at %s"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16560, 00000, "unable to convert document, syntax error at \"%s\" "
// *Document: NO
// *Cause: There was an error in the specified sting.
// *Action: Correct the errors and submit the request again.
/
16561, 00000, "cannot remove an active instance"
// *Cause: The instance to be removed was running.
// *Action: Shut down the instance and reissue the REMOVE command.
/
16562, 00000, "INTENDED_STATE not used here, syntax error at \"%s\""
// *Document: NO
// *Cause: There was an error in the specified string.
// *Action: Correct the errors and submit the request again.
/
16563, 00000, "unable to add value, syntax error at \"%s\""
// *Document: NO
// *Cause: There was an error in the specified string.
// *Action: Correct the errors and submit the request again.
/
16564, 00000, "lookup failed, syntax error at %s"
// *Document: NO
// *Cause: There was an error in the specified string.
// *Action: Correct the errors and submit the request again.
/
16565, 00000, "duplicate property, syntax error at \"%s\""
// *Document: NO
// *Cause: There was an error in the specified string.
// *Action: Correct the errors and submit the request again.
/
16566, 00000, "unsupported document type"
// *Document: NO
// *Cause: The XML document type was not supported.
// *Action: Correct the errors and submit the request again.
/
16567, 00000, "Oracle Data Guard broker internal parser error at \"%s\""
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16568, 00000, "cannot set property %s"
// *Cause: The specified property could not be modified because it was
// either a monitorable property or a property that did not exist.
// *Action: Retry the command with a valid configurable property.
/
16569, 00000, "Oracle Data Guard configuration is not enabled"
// *Cause: The requested operation required that broker management of the
// Data Guard configuration must be enabled.
// *Action: Enable the Oracle Data Guard configuration and reissue the command.
/
16570, 00000, "database needs restart"
// *Cause: The Oracle Data Guard broker operation required this database
// instance to be shut down and restarted.
// *Action: If DGMGRL or Enterprise Manager has not already done so,
// shut down the Oracle instance and then restart it.
/
16571, 00000, "Oracle Data Guard configuration file creation failure"
// *Cause: The Oracle Data Guard broker was unable to create the configuration
// file on permanent storage.
// *Action: Verify space, permissions and file name as indicated by the
// DG_BROKER_CONFIG_FILE[1|2] initialization parameters and retry
// the operation.
/
16572, 00000, "Oracle Data Guard configuration file not found"
// *Cause: The Oracle Data Guard broker configuration file was either
// unavailable or did not exist.
// *Action: Verify that the configuration file was successfully created.
// If the DG_BROKER_CONFIG_FILE[1|2] initialization parameters were
// changed, ensure the file name on disk and the parameter value
// match, there is space on the device, and the proper permissions
// are granted. For a RAC database, ensure that these initialization
// parameters are set to file locations that are shared by all
// instances of the RAC database.
/
16573, 00000, "attempt to change or access configuration file for an enabled broker configuration"
// *Cause: The operation was rejected because the Oracle Data Guard broker
// configuration file was in use. The attempted operation
// was unsafe while broker management of the configuration was
// enabled. For example:
// - An attempt was made to alter the DG_BROKER_CONFIG_FILE[1|2]
// initialization parameters while the broker was running.
// - Non-broker access (such as DBMS_FILE_TRANSFER) to the
// configuration files was attempted. See the alert log for
// additional information.
// *Action: Disable the broker configuration and shut down the
// Oracle Data Guard broker, then retry the operation. If the
// operation includes altering the DG_BROKER_CONFIG_FILE[1|2]
// initialization parameters, be sure that the new parameter values
// correctly specify the files at their expected location before
// reenabling broker management of the configuration.
/
16574, 00000, "switchover disallowed when required databases are shut down"
// *Cause: Switchover failed because either the primary database or the
// designated standby database were shut down.
// *Action: Ensure that the primary and standby databases are running and
// that primary database is shipping redo data to the designated
// standby database. Also ensure that that the designated standby
// database is applying the redo data received from the primary
// database.
/
16575, 00000, "LOG_ARCHIVE_DEST_n parameter conflicts with the new member to be added"
// *Cause: One or more LOG_ARCHIVE_DEST_n initialization parameters on
// existing members were already set for the new member to be added
// when attempting to add a standby database, far sync instance,
// Backup Appliance, or external destination to the configuration.
// *Action: Clear the LOG_ARCHIVE_DEST_n initialization parameter
// that specifies the standby database, far sync instance,
// Backup Appliance, or external destination to be added.
/
16576, 00000, "failed to update Data Guard broker configuration file"
// *Cause: A failure was encountered while the broker was updating
// the Oracle Data Guard broker configuration file on permanent
// storage.
// *Action: Verify space, permissions and file name as indicated by the
// DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
/
16577, 00000, "corruption detected in Data Guard configuration file"
// *Cause: The Oracle Data Guard broker detected errors while loading the
// configuration file.
// *Action: Verify space, permissions and file name as indicated by the
// DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
// Contact Oracle Support Services.
/
16578, 00000, "failed to read Data Guard configuration file"
// *Cause: A failure was encountered while the broker was reading
// the configuration file on permanent storage.
// *Action: Verify space, permissions and file name as indicated by the
// DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
// *Action: Verify space, permissions and file name as indicated by the
// DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
/
16579, 00000, "bad network state detected"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16580, 00000, "bad network link"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16581, 00000, "Oracle Data Guard broker could not reach remote member"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16582, 00000, "cannot change instance-specific property"
// *Cause: An attempt was made to change an instance-specific property
// for a member that had more than one instance.
// *Action: Retry the command and identify a specific instance whose
// property value is to be changed.
/
16583, 00000, "bad Data Guard broker connection process state"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16584, 00000, "operation cannot be performed on a standby database"
// *Cause: The database specified for the operation was a standby database,
// or the operation was attempted on a standby database.
// *Action: Check the database type and retry the operation. If the command
// must be executed on a primary database, connect to the primary
// database and retry the operation.
/
16585, 00000, "operation cannot be performed on a primary database"
// *Cause: The database specified for the operation was a primary database,
// or the operation was attempted on a primary database.
// *Action: Check the database type and retry the operation. If the command
// must be executed on a standby database, connect to a standby
// database and retry the operation.
/
16586, 00000, "cannot change member property with EDIT INSTANCE command"
// *Cause: An attempt was made to change a non-instance level property using
// an EDIT INSTANCE command instead of an EDIT DATABASE, EDIT
// FAR_SYNC, or EDIT RECOVERY_APPLIANCE command.
// *Action: Use the EDIT DATABASE, EDIT FAR_SYNC, or EDIT RECOVERY_APPLIANCE
// command to change non-instance level properties.
/
16587, 00000, "ambiguous object specified to Data Guard broker"
// *Cause: An object was specified that the broker could not uniquely
// distinguish from other objects in the configuration.
// *Action: Try to further distinguish the object specified for the operation
// and reissue the command.
/
16588, 00000, "no more internal buffers"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16589, 00000, "Oracle Data Guard broker detected network transfer error"
// *Cause: The Oracle Data Guard broker detected an error while transferring
// data from one member to another. This may happen when either:
// - The broker detects an inconsistency in the block count of the
// configuration file when the file is transmitted between
// members.
// - The broker encounters an error when writing the configuration
// file.
// - A broker member receives an incorrect message from another
// member.
// *Action: Contact Oracle Support Services.
/
16590, 00000, "Oracle Data Guard configuration does not contain a primary database"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16591, 00000, "unknown field \"%s\" in document"
// *Document: NO
// *Cause: There was an error in the specified string.
// *Action: Correct the errors and submit the request again.
/
16592, 00000, "missing field \"%s\" in document"
// *Document: NO
// *Cause: There was an error in the specified string.
// *Action: Correct the errors and submit the request again.
/
16593, 00000, "XML conversion failed"
// *Document: NO
// *Cause: There was an error in the XML document.
// *Action: Correct the errors and submit the request again.
/
16594, 00000, "DMON background process is not running"
// *Cause: The Oracle Data Guard broker background process, DMON, was not
// running.
// *Action: Check the Oracle Data Guard broker log file and DMON process trace
// file to determine why the DMON process is not running.
/
16595, 00000, "process %s failed to terminate"
// *Cause: The specified process did not terminate at the request of the Data
// Guard broker.
// *Action: Contact Oracle Support Services.
/
16596, 00000, "member not part of the Oracle Data Guard broker configuration"
// *Cause: The specified member was not in the Oracle Data Guard broker
// configuration.
// *Action: Retry the command with a member that is in the broker
// configuration.
/
16597, 00000, "Oracle Data Guard broker detects two or more primary databases"
// *Cause: The Oracle Data Guard broker detected two or more primary
// databases in the broker configuration and could not continue.
// *Action: Contact Oracle Support Services.
/
16598, 00000, "Oracle Data Guard broker detected a mismatch in configuration"
// *Cause: The Oracle Data Guard broker detected a significant mismatch while
// performing configuration membership validation between two
// or more members in the broker configuration. This can occur
// when the primary database has stale broker configuration files.
// *Action: Contact Oracle Support Services.
/
16599, 00000, "Oracle Data Guard broker detected a stale configuration"
// *Cause: The Oracle Data Guard broker detected a stale configuration during
// initialization for this member.
// *Action: The broker will automatically resolve this situation once the
// primary database completes its initialization.
/
16600, 00000, "not connected to target standby database for failover"
// *Cause: The failover command failed because the client was not connected
// to the target standby database.
// *Action: Explicitly connect to the standby database to be failed over to and
// retry the failover command.
/
16601, 00000, "site contains required resources that are disabled"
// *Document: NO
// *Cause: Resources required to complete this command were disabled.
// *Action: Enable all required resources and reissue the command.
/
16602, 00000, "member must be disabled to perform this operation"
// *Cause: An attempt was made to edit a member property while the member
// was enabled.
// *Action: Disable the member and retry the command.
/
16603, 00000, "member is part of another Data Guard broker configuration"
// *Cause: The member was part of another Data Guard broker configuration.
// This could occur if the original configuration was re-created
// while this member was disconnected from the network or the
// same member was added to two different Data Guard broker
// configurations.
// *Action: Ensure that the member belongs to only one broker configuration.
// Shut down the broker by setting the DG_BROKER_START initialization
// parameter to 'false'. Then, remove the Oracle Data Guard broker
// configuration files. Finally, restart the broker by setting the
// DG_BROKER_START initialization parameter to 'true'.
/
16604, 00000, "Data Guard broker configuration file inaccessible"
// *Cause: The Oracle Data Guard broker was unable to access the
// configuration file specified by the DG_BROKER_CONFIG_FILE[1|2]
// initialization parameters.
// *Action: Verify space, permissions and file name as indicated by the
// DG_BROKER_CONFIG_FILE[1|2] initialization parameters.
/
16605, 00000, "event to control fast-start failover diagnostic tracing"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used
// to control fast-start failover diagnostic tracing.
// DO NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
16606, 00000, "unable to find property \"%s\""
// *Cause: The specified property did not exist.
// *Action: Specify a valid property name and reissue the command.
/
16607, 00000, "one or more members have failed"
// *Cause: A failure was detected for one or more members in the Data
// Guard broker configuration.
// *Action: Locate the member or members with a failure status and correct it.
/
16608, 00000, "one or more members have warnings"
// *Cause: A warning was detected for one or more members in the Data
// Guard broker configuration.
// *Action: Locate the member or members with a warning status and correct it.
/
16609, 00000, "database is being disabled"
// *Cause: A command was attempted on a database that was being disabled.
// For example, attempting to reinstate the old primary database,
// the database that was the primary database prior to the most
// recent failover, before it was ready to be reinstated.
// *Action: Wait for the Oracle Data Guard broker to disable the database and
// then retry the command.
/
16610, 00000, "command \"%s\" in progress"
// *Cause: The specified broker command was already running and the
// command issued could not be completed.
// *Action: Wait for the specified command to finish and then retry the
// command.
/
16611, 00000, "command aborted at user request"
// *Cause: The command was aborted at the user's request.
// *Action: No action required.
/
16612, 00000, "string value too long for attribute \"%s\""
// *Cause: The string value for the named attribute was too long.
// *Action: Specify a shorter string value.
/
16613, 00000, "initialization in progress for member"
// *Cause: A request was made that required access to the Oracle Data Guard
// broker configuration before the Oracle Data Guard broker had
// completed initialization.
// *Action: Wait until the Oracle Data Guard broker has completed
// initialization, then reissue the command.
/
16614, 00000, "Oracle Data Guard broker configuration is disabled"
// *Cause: An attempt to enable a member failed because
// the Oracle Data Guard broker configuration was disabled.
// *Action: Enable the Oracle Data Guard broker configuration and issue the
// DGMGRL CLI SHOW CONFIGURATION command to see if there are any
// members that are still disabled. If the member you tried to
// enable is still disabled, issue the DGMGRL CLI SHOW command to
// check the status of the member. If the member is a database whose
// status indicates that the database needs to be reinstated, then
// issue the DGMGRL CLI REINSTATE DATABASE command to reinstate and
// enable the database. If the member does not require reinstatement,
// then issue the DGMGRL CLI ENABLE command to enable the member.
/
16615, 00000, "event for Data Guard NetSlave testing"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used for
// verifying NetSlave functionality in Data Guard. DO NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
16616, 00000, "event for Data Guard monitor testing"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used for
// verifying Monitor functionality in Data Guard. DO NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
16617, 00000, "unknown object identifier specified in request"
// *Cause: Object identifier specified in the request was invalid or
// unknown.
// *Action: Verify that a valid object identifier is specified and reissue
// the command.
/
16618, 00000, "response document of size \"%s\" bytes is too large"
// *Document: NO
// *Cause: The document response could not be returned because the size
// of the document was too large.
// *Action: View the broker log file for the given member directly.
/
16619, 00000, "condition for fast-start failover is already enabled"
// *Cause: The condition specified for fast-start failover was already
// enabled.
// *Action: No action is required. Use the DGMGRL CLI SHOW FAST_START FAILOVER
// command to see the conditions that are enabled.
/
16620, 00000, "one or more members could not be reached for a remove operation"
// *Cause: One or more members could not be reached for either
// a DGMGRL CLI REMOVE DATABASE, REMOVE FAR_SYNC or a REMOVE
// CONFIGURATION command.
// *Action: This typically indicates a network problem where the member is
// unable to respond to the primary database. If this is the case,
// examine the primary database Data Guard broker log file to
// determine which members could not be reached. For each mmeber not
// reached, connect to that member and shut down the broker by
// setting the DG_BROKER_START initialization parameter to 'false'.
// After the broker has been shut down for the member, locate the
// Data Guard broker configuration files from the member's
// DG_BROKER_CONFIG_FILE[1|2] initialization parameter values and
// delete them. Then restart the broker by setting DG_BROKER_START to
// 'true'.
/
16621, 00000, "member name for ADD command must be unique"
// *Cause: An attempt was made to add a member to the broker configuration
// that already included a member with the specified name. The
// member names must be unique.
// *Action: Verify that a unique name is specified for the new member
// to be added. Also, the member name must match the DB_UNIQUE_NAME
// initialization parameter of the member.
/
16622, 00000, "two or more broker member objects resolve to the same member"
// *Cause: Multiple member objects referred to the same member.
// *Action: Examine the details of all members in the broker configuration
// and verify that two or more members are not referring to the same
// member. If two or more members in the broker configuration have
// the same value for the DGConnectIdentifier configurable property,
// either:
// - Remove and re-add the erroneously defined member or members to
// resolve the ambiguity.
// - Ensure that the DGConnectIdentifier configurable property for
// each member allows the broker to properly connect to that member.
/
16623, 00000, "member detected role change"
// *Cause: A successful switchover or failover operation had been completed
// and was detected during member startup or broker health check.
// If this member was a database that was unavailable during a
// switchover or failover operation, it may not be a viable standby
// database for the new primary database and was disabled by the
// Oracle Data Guard broker.
// *Action: Connect to the new primary database and examine the broker
// configuration for databases that were disabled and that may require
// reinstatement or re-creation.
/
16624, 00000, "broker protocol version mismatch detected"
// *Cause: A network protocol version number mismatch was detected.
// This could happen if the members in the broker configuration
// were not running the same version of Oracle. The broker would
// disable members that were not running the same version of Oracle
// as the primary database if this situation was detected.
// *Action: Examine the version of Oracle installed on all members in
// the broker configuration to ensure they are identical. Once all
// of the members in the broker configuration are running the same
// version of Oracle, reenable the members that were disabled.
/
16625, 00000, "cannot reach member \"%s\""
// *Cause: The command could not be executed because the member noted
// in the error text was not reachable from the member where
// the command was issued.
// *Action: See accompanying messages for more information. Check the network
// connections to the specified member. Alternatively, connect to
// a different member in the Oracle Data Guard broker configuration
// and retry the command.
/
16626, 00000, "failed to enable specified member"
// *Cause: This status was returned when attempting to enable a member that:
// - Could not locate itself in the broker configuration file.
// - Failed to distinguish itself from two or more members in
// the configuration file.
// - Determined it missed a role change within the configuration.
// *Action: To correct the problem, try one of these actions:
// - Confirm that the host and SID names for the member exactly
// match the values in the HOST_NAME and INSTANCE_NAME columns
// of the V$INSTANCE view.
// - Confirm that two or more members do not have the same connect
// identifier. That is, multiple members in the broker configuration
// should not reach the same member.
// - If a failover has been performed and the old primary database
// has been re-created (or a standby database has been re-created),
// ensure that the Oracle Data Guard broker configuration files have
// been removed for that database. Do not remove the configuration
// files that are in use by the new primary database.
/
16627, 00000, "operation disallowed since no member would remain to support protection mode"
// *Cause: This status was returned because of one of the following:
// - The broker rejected an attempt to change the overall
// configuration protection mode since it could not find any
// enabled members that supported the proposed protection mode,
// or could not find any enabled members that were synchronized.
// - The broker rejected an attempt to enable the configuration
// if it determined that there were no enabled members that
// supported the overall protection mode.
// - The broker rejected an attempt to disable or remove a member
// that, if disabled or deleted, would result in no remaining
// member that could support the overall configuration protection
// mode.
// - The broker rejected an attempt to switchover if doing so would
// violate the overall configuration protection mode.
// - Performing automatic health check if the broker determined that
// no members supported the overall protection mode.
// *Action: - If changing the overall protection mode, confirm that at least
// one member satisfies the new protection mode and is synchronized
// with the primary database.
// - For enable failures, confirm that at least one member receives
// redo data in a mode that supports the current overall protection
// mode.
// - For delete and disable failures, confirm that at least one
// other member receives redo data in a mode that suppports the
// the overall protection mode.
// - For switchover failures that occur when the configuration
// is operating in maximum protection or maximum availability
// mode, confirm that at least one other member receives redo
// data in synchronous mode. If the configuration contains a
// primary database and a single standby database and is operating
// in either maximum protection or maximum availability mode,
// ensure that the LogXptMode configurable property of the primary
// database is set to the value "SYNC". Since the old primary
// database will become the standby database after switchover
// completes, its LogXptMode configurable property setting must
// support the configuration protection mode.
// - For a health check error, confirm that at least one member
// receives redo data in a mode that supports the current overall
// protection mode.
/
16628, 00000, "broker protection mode inconsistent with the database setting"
// *Cause: The Oracle Data Guard broker protection mode saved in the broker
// configuration file was inconsistent with the actual database
// setting.
// *Action: Reset the protection mode through the Oracle Data Guard broker.
/
16629, 00000, "database reports a different protection level from the protection mode"
// *Cause: The current database protection level was different from the
// configured protection mode. This typically was caused by redo
// transport problems, or the primary database was not open.
// *Action: Check the database alert log files and Data Guard broker log files
// for more details. Also, check the redo transport status. Ensure
// that one standby database supports the configured protection
// mode and that the network to that standby database is working
// properly. Ensure the primary database is open.
/
16630, 00000, "configurable property has been deprecated"
// *Cause: The property that was specified in the command was deprecated.
// *Action: Check the broker documentation to identify a replacement property
// or DGMGRL CLI command for the deprecated property.
/
16631, 00000, "operation requires shutdown of database or instance \"%s\""
// *Cause: The Oracle Data Guard broker operation required a shutdown of the
// database or instance.
// *Action: If database or instance has not been shutdown by the DGMGRL CLI
// or Enterprise Manager, shutdown the database or instance
// manually.
/
16632, 00000, "instance being added to member profile"
// *Cause: The Oracle Data Guard broker determined that an instance
// successfully found its member profile within the broker
// configuration file, but lacked an instance-specific profile.
// The broker automatically created an instance-specific
// profile and associated the instance with its database profile.
// *Action: No user action is required. The broker will automatically
// associate the instance with its member profile and incorporate
// the instance into broker activity.
/
16633, 00000, "the only instance of a member cannot be removed"
// *Cause: The instance to be removed was the only instance of the
// corresponding member that was known to the broker.
// *Action: Remove the corresponding member from the broker configuration
// instead of the individual instance of the member.
/
16634, 00000, "Event for Data Guard NetSlave tracing"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used to
// control trace output of the Oracle Data Guard NetSlave process. DO
// NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
16635, 00000, "network connection failed during transmission"
// *Cause: The Oracle Data Guard broker detected a connection failure to a
// member in the broker configuration. This failure happened
// in the middle of a transmission session. A transmission session
// usually requires more than one send operation for sending a large
// amount of data (for example, the broker configuration file) to
// another member in the configuration.
// *Action: In most cases, no user action is required. The Oracle Data Guard
// broker always tries to resend the data. This error will be reported
// if the problem persists. This error indicates there are some
// problems with the network connection between broker managed
// members.
// Further network troubleshooting should be done to identify and
// correct the actual problem.
/
16636, 00000, "fast-start failover target standby in error state, cannot stop observer"
// *Cause: A STOP OBSERVER operation could not be completed when fast-start
// failover was enabled because the target standby database could
// not participate in the STOP OBSERVER operation.
// *Action: Additional information about this failure is recorded in the
// Data Guard broker log file for the primary database. This
// information helps to identify the reason why the target standby
// database was unable to participate in the STOP OBSERVER operation.
// If the problem can be corrected by the information in the broker
// log file, retry the operation. Alternatively, fast-start failover
// may be forcibly disabled by connecting to the primary database
// and issuing the DISABLE FAST_START FAILOVER FORCE command from
// the DGMGRL CLI. Once fast-start failover has been forcibly
// disabled, the observer can be stopped regardless of the current
// state of the target standby database.
/
16637, 00000, "maximum number of Oracle error numbers for fast-start failover already reached"
// *Cause: The broker could not enable any more Oracle error numbers for
// initiating a fast-start failover.
// *Action: Use the DGMGRL CLI SHOW FAST_START FAILOVER command to help
// identify an Oracle error number that can be disabled before
// attempting to enable an additional error number for initiating
// a fast-start failover.
/
16638, 00000, "could not obtain instance status"
// *Cause: The broker could not determine whether the specified instance was
// running.
// *Action: See the next error message in the error stack for more detailed
// information. If the situation described in the next error in the
// stack can be corrected, do so; otherwise, contact Oracle Support
// Services.
/
16639, 00000, "specified instance inactive or currently unavailable"
// *Cause: An attempt was made to perform an operation on an instance that
// was not running or was unavailable.
// *Action: Ensure that the instance specified in the operation is running
// and then retry the operation.
/
16640, 00000, "Oracle Clusterware was unable to shutdown database instances"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16641, 00000, "failure to acquire broker configuration metadata lock"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16642, 00000, "DB_UNIQUE_NAME mismatch"
// *Cause: The expected DB_UNIQUE_NAME value did not match the actual
// DB_UNIQUE_NAME value for the member that the broker contacted
// using the connect identifier that was associated with that
// member.
// *Action: Verify that the connect identifier correctly connects to the
// intended member. Verify that the name of the member the
// broker expects to find by that connect identifier matches the
// actual DB_UNIQUE_NAME for that member.
/
16643, 00000, "unable to determine location of broker configuration files"
// *Cause: The Oracle Data Guard broker was unable to determine the location
// of its configuration files from the DG_BROKER_CONFIG_FILE[1|2]
// initialization parameters.
// *Action: Retry the operation and, if the error persists, contact Oracle
// Support Services.
/
16644, 00000, "apply instance not available"
// *Cause: The broker operation could not finish, because it requires
// a running apply instance for the standby database, and either
// there was no such instance designated for the standby database
// or the designated apply instance was not currently available.
// *Action: Start the designated apply instance or wait until the broker
// specifies an instance to be the apply instance and reissue the
// command.
/
16645, 00000, "startup of an instance interrupted current operation"
// *Cause: The startup of an instance that is not part of the broker
// configuration prevented the operation from completing.
// *Action: Reissue the operation after the new instance has joined the
// Data Guard configuration.
/
16646, 00000, "fast-start failover is disabled"
// *Cause: The operation was not allowed because fast-start failover was
// disabled.
// *Action: Enable fast-start failover and retry the operation.
/
16647, 00000, "could not start more than three observers"
// *Cause: The observer could not start because there were three observers
// already observing the Oracle Data Guard configuration for which
// fast-start failover may have been enabled.
// *Action: Stop one of the existing observers and retry the command.
/
16648, 00000, "a new observer registered with identifier %s"
// *Cause: The observer was registered with the Oracle Data Guard broker and
// will begin observing the Oracle Data Guard configuration for
// conditions that warrant doing a fast-start failover.
// *Action: None
/
16649, 00000, "possible failover to another database prevents this database from being opened"
// *Cause: An attempt to open the primary database was made either after
// a failover occurred, or when it was likely to have occurred as
// the result of the primary being isolated from the fast-start
// failover target standby database and from the fast-start failover
// observer.
// *Action: Check if a failover did occur. If fast-start failover is enabled,
// and a failover did not occur, ensure that connectivity exists
// between the primary database and either the observer or the
// target standby database. Then, try opening the database again.
/
16650, 00000, "unrecognized object specified"
// *Cause: An unrecognized database or far sync instance was specified in the
// command.
// *Action: Try the command again using a valid object name. Use the SHOW
// CONFIGURATION command to identify the members in the configuration.
/
16651, 00000, "upgrade to maximum protection mode not possible"
// *Cause: An upgrade to maximum protection mode was attempted when the
// current protection mode was maximum performance mode.
// *Action: To upgrade the protection mode to maximum protection mode, first
// upgrade the protection mode to maximum availability mode, then
// upgrade the protection mode to maximum protection mode.
/
16652, 00000, "fast-start failover target standby database is disabled"
// *Cause: The command to enable or disable fast-start failover could not be
// completed because Data Guard broker management of the fast-start
// failover target standby database is currently disabled.
// *Action: Enable broker management of the target standby database and
// reissue the command. If an attempt was made to disable fast-start
// failover when this error was reported, disable fast-start failover
// forcibly using the DGMGRL DISABLE FAST_START FAILOVER FORCE
// command. Consult the documentation for more information.
/
16653, 00000, "failed to reinstate database"
// *Cause: The Oracle Data Guard broker failed to reinstate the specified
// database because the reinstatement could not be completed or the
// database was already enabled.
// *Action: Additional information about this failure is recorded in the
// primary database or the specified database Data Guard
// broker log files. This information is helpful in determining
// how to proceed.
/
16654, 00000, "fast-start failover is enabled"
// *Cause: The attempted command was not allowed while fast-start failover
// was enabled:
// - The FastStartFailoverTarget property may not be modified.
// - The LogXptMode property for either the primary database or the
// fast-start failover target standby database may not be modified.
// - The configuration's protection mode may not be modified.
// - Neither the broker configuration nor the fast-start failover
// target standby database may be disabled using the DGMGRL CLI
// DISABLE command.
// - Neither the broker configuration nor the fast-start failover
// target standby database may be removed using the DGMGRL CLI
// REMOVE command.
// - The FAILOVER IMMEDIATE command is not allowed.
// - The DG_BROKER_START initialization parameter may not be
// set to FALSE.
// *Action: Disable fast-start failover, using the FORCE option if required.
// Then retry the attempted command.
/
16655, 00000, "specified standby database not the current fast-start failover target standby"
// *Cause: The attempted command was not allowed because fast-start failover
// was enabled for this Data Guard broker configuration and the
// standby database specified in the command was not the current
// fast-start failover target standby associated with the current
// primary database.
// *Action: Retry the attempted command by specifying the current fast-start
// failover target standby database. Alternatively, disable
// fast-start failover and retry the command using the originally
// specified target standby database.
/
16656, 00000, "Oracle Data Guard broker detected role change"
// *Cause: The Oracle Data Guard broker detected a role change during
// database startup or health check.
// *Action: Additional information about this failure is recorded in the
// Oracle Data Guard broker log files, one for the primary database
// and one for each standby database in the Oracle Data Guard
// configuration. This information is helpful in determining how best
// to proceed from this failure.
/
16657, 00000, "reinstatement of database in progress"
// *Cause: Reinstatement of this database was in progress.
// *Action: None
/
16658, 00000, "unobserved fast-start failover configuration"
// *Cause: The fast-start failover configuration was currently unobserved
// therefore failover was disallowed.
// *Action: Ensure that the observer is running and has connectivity to both
// the primary and the target standby databases. Otherwise, disable
// fast-start failover to perform a failover in the absence of the
// observer process.
/
16659, 00000, "failover operation in progress"
// *Cause: A primary database that restarted contacted a standby database
// that is being failed over to.
// *Action: Shut down the primary database and wait for failover to complete
// on the standby database. Once failover is complete, restart the
// old primary database. If the failover occurred due to fast-start
// failover, restarting the primary database after failover is
// complete allows it to be automatically reinstated as a standby
// database to the new primary database.
/
16660, 00000, "fast-start failover operation attempted in absence of a broker configuration"
// *Cause: An attempt was made to enable or disable fast-start failover when
// connected to a standby database for which broker configuration
// details are currently unavailable. For instance, the standby
// database may currently require re-creation (or flashback
// reinstantiation) before it may respond to broker client commands.
// *Action: 1) An attempt to enable or disable (non-FORCE) fast-start failover
// at this standby database will be rejected until such time that the
// broker configuration details have been made available to that
// standby database from the primary database. This normally occurs
// when the standby database is successfully re-created or flashed
// back, and then reenabled at the primary database.
// 2) Use the FORCE option to override fast-start failover that
// has been enabled at the standby database even when the broker
// configuration details are currently unavailable to the standby
// database. In this case, this status message is only a warning.
// Note that fast-start failover is not formally disabled in the
// broker configuration. The effect of this command issued under these
// circumstances may or may not be permanent, depending upon when
// the primary and standby databases regain full communication
// between each other and if the state of fast-start failover has
// been altered at the primary database in the meantime.
/
16661, 00000, "the standby database needs to be reinstated"
// *Cause: A role change has caused this database to require reinstatement.
// *Action: Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to
// reinstate the database. Reinstate the database as soon as
// possible, because the database will have to be re-created if
// another role change occurs while it is in this state.
/
16662, 00000, "network timeout when contacting a member"
// *Cause: In response to the issued command, the Oracle Data Guard broker
// attempted to contact a member in the Oracle Data Guard
// configuration. That attempt failed because there was no response
// from that member after the period of time specified by the
// CommunicationTimeout configuration property.
// *Action: Check the Oracle Data Guard broker log file for the details of the
// failure. Fix the problem and try the command again.
/
16663, 00000, "event to control broker actions in the development environment"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used
// to control the broker actions in the development environment.
// DO NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
16664, 00000, "unable to receive the result from a member"
// *Cause: During execution of a command, a member in the Oracle Data Guard
// broker configuration failed to return a result.
// *Action: Check Oracle Data Guard broker log files for the details of the
// failure. Ensure network communication is working properly amongst
// the members of the configuration. Fix any possible network problems
// and reissue the command.
/
16665, 00000, "time out waiting for the result from a member"
// *Cause: The Oracle Data Guard broker was forced to time out a network
// connection to a remote member because:
// - The network call to the remote member did not complete in
// a timely manner.
// - The remote member was unable to execute the command due to
// an instance failure.
// *Action: Check Data Guard broker log files for the details of the failure.
// If the network call did not complete in a timely manner, increase
// the CommunicationTimeout configuration property value and reissue
// the command.
/
16666, 00000, "unable to initiate fast-start failover on a bystander standby database"
// *Cause: The request to initiate a fast-start failover using
// DBMS_DG.INITIATE_FS_FAILOVER was made on a bystander standby
// database. DBMS_DG.INITIATE_FS_FAILOVER can only be called on
// either the primary or fast-start failover target standby database.
// *Action: Call DBMS_DG.INITIATE_FS_FAILOVER on either the primary or
// fast-start failover target standby database.
/
16667, 00000, "request Oracle Data Guard broker client to reissue command"
// *Cause: The Oracle Data Guard broker operation required the same command be
// issued again from the client.
// *Action: If DGMGRL or Enterprise Manager has not already done so,
// reissue the same command to the Oracle Data Guard broker manually.
/
16668, 00000, "operation cannot be performed on the fast-start failover target standby database"
// *Cause: The database specified for the operation was the fast-start
// failover target standby database.
// *Action: Retry the operation on a different database. Alternatively, disable
// fast-start failover and retry the operation.
/
16669, 00000, "instance cannot be opened because the Oracle Active Data Guard option is disabled"
// *Cause: The attempt to open the instance failed because the Oracle Active
// Data Guard option was not enabled and Redo Apply was either running
// or was about to be started by the Oracle Data Guard broker.
// *Action: Stop Redo Apply or set the database state to APPLY-OFF and then
// open the database.
/
/16670, 00000, "file was opened with incorrect block size"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16671, 00000, "instance-specific property must be set uniquely for instances of an Oracle RAC database"
// *Cause: An attempt was made to set an instance-specific property to the
// same value for all instances of an Oracle RAC database for a
// property whose value must be unique for each instance.
// *Action: Use the EDIT INSTANCE command and specify the SID of each
// instance whose instance-specific property value is to be changed.
/
16672, 00000, "switchover not permitted to standby database with non-zero DelayMins"
// *Cause: Switchover was attempted to a standby database that has a non-zero
// value for its DelayMins configurable property.
// *Action: Set the DelayMins configurable property to zero for the standby
// database to switchover to, wait for its apply lag to become zero
// seconds, and then retry the switchover command.
/
16673, 00000, "member running different Oracle version"
// *Cause: The standby member was running a different version of Oracle than
// the primary database.
// *Action: Ensure that all members of the configuration are running the same
// versions of Oracle.
/
16674, 00000, "standby database type has changed"
// *Cause: An attempt to enable a database whose standby type changed from
// physical or snapshot to logical (or vice versa) was disallowed.
// *Action: If the intention is to retain the database conversion to the
// new type, the database must be removed and re-added to the
// configuration in order to obtain correct values for database
// properties specific to the new standby type.
/
16675, 00000, "database instance restart required for property value modification to take effect"
// *Cause: One or more properties that correspond to static initialization
// parameters were modified, but the database instances were not
// restarted. Or, a static initialization parameter that corresponds
// to a broker property was modified using an ALTER SYSTEM SQL*Plus
// statement.
// *Action: Restart the database instances for the modified property values
// to take effect. If the error persists after having restarted the
// instance, use the DGMGRL CLI or Enterprise Manager to modify the
// property the static initialization parameter corresponds to.
/
16676, 00000, "RedoRoutes property for two or more members contains a circular route"
// *Cause: The value of a RedoRoutes property for two or more members was
// set such that a member that sends redo also receives redo data
// data in the same route. For example, A sends to B, B sends to C,
// and C sends to A.
// *Action: Correct the setting of the RedoRoutes propety on one or more
// members to eliminate the circular route.
/
16677, 00000, "Standby database has the same or higher priority than other members specified in the RedoRoutes group."
// *Cause: A standby database with the same or higher priority than other
// members in the group was specified in the RedoRoutes property.
// *Action: Check the Oracle Data Guard broker log file for the reason for the
// failure and reissue the command. Ensure that a standby database was
// not specified to have the same or higher priority than other
// members in the group for the RedoRoutes property.
/
16678, 00000, "unrecognized or duplicate attribute specified"
// *Cause: The specified value contained an unrecognized or duplicated
// attribute.
// *Action: Ensure the property string does not contain any undefined or
// duplicate attributes. See the Oracle Data Guard broker
// documentation for supported attributes.
/
16679, 00000, "one or more illegal keywords found"
// *Cause: The specified value contained one or more illegal keywords.
// *Action: See the Oracle Data Guard broker documentation for the supported
// keywords.
/
16680, 00000, "value contains unbalanced set of parentheses"
// *Cause: The specified value contained an unbalanced set of parentheses or
// a missing set of parentheses.
// *Action: Ensure the parentheses are correctly matched and specify
// parentheses when required. See the Oracle Data Guard broker
// documentation for more information.
/
16681, 00000, "value does not contain a colon"
// *Cause: The specified value did not contain a colon (:).
// *Action: Include the colon (:) in the value.
/
16682, 00000, "value contains duplicate databases or far sync instances"
// *Cause: The specified value contained the same database or far sync
// instance multiple times.
// *Action: Ensure that a database or far sync instance is specified only once.
/
16683, 00000, "illegal, empty substring specified in property value"
// *Cause: The value specified contained an illegal, empty string or
// substring, e.g. "()".
// *Action: Remove the illegal empty strings and retry the command.
/
16684, 00000, "maximum number of destinations exceeded"
// *Cause: The value specified for the RedoRoutes property contained more
// than the 30 destinations.
// *Action: Ensure that no more than 30 destinations are specified.
/
16685, 00000, "database does not receive redo data"
// *Cause: The RedoRoutes property for all members of the configuration
// were set such that this database did not receive redo data.
// Or, the transport state of the database that sends redo data
// to this database is not valid.
// *Action: Check the setting of the RedoRoutes property for all members of
// the configuration. Ensure that at least one member's RedoRoutes
// property value is set to ship redo data to this database. Also
// check the transport state of the database that sends redo data
// to this database.
/
16686, 00000, "database may not receive redo data if redo source is an alternate destination"
// *Cause: This database may not receive redo data if the redo source is an
// alternate destination that does not ship redo to this database.
// *Action: Ensure that any alternates for the redo source for this database
// includes this database in its send to list.
/
16687, 00000, "database has multiple redo sources"
// *Cause: Using the RedoRoutes properties, multiple redo sources were
// shipping redo to the standby.
// *Action: Using the RedoRoutes properties, ensure that only one redo source
// ships redo to the standby.
/
16688, 00000, "command cannot be issued on a disabled member"
// *Cause: The command was issued on a member that was disabled.
// *Action: Connect to an enabled member of the configuration and retry
// the command.
/
16689, 00000, "illegal sender specified for RedoRoutes property"
// *Cause: A far sync instance or a recovery appliance was specified as the
// redo source in a RedoRoutes property rule.
// *Action: Check the setting of the RedoRoutes property and confirm that a far
// sync instance or a recovery appliance is not specified as the redo
// source in the RedoRoutes property rule.
/
16690, 00000, "illegal destination specified for RedoRoutes"
// *Cause: A specified destination in a RedoRoutes rule either appears
// in the primary setting of the same rule or is the local database
// itself.
//
// *Action: Ensure that any specfifed destination in a RedoRoutes rule
// neither appears in the primary setting of the same rule nor
// be the local database itself.
/
16691, 00000, "cannot remove a configuration member that is specified in a RedoRoutes property"
// *Cause: An attempt was made to remove a database or far sync instance that
// is specified in another configuration member's RedoRoutes property.
// *Action: First remove the database or far sync instance from all other
// member's RedoRoutes property values. Then retry the remove command.
/
16692, 00000, "operation disallowed for a member that has a value set for its RedoRoutes property"
// *Cause: An attempt was made to delete, disable, or convert (physical
// standby database) a member that has a non-empty value set for its
// RedoRoutes property.
// *Action: Reset the value of the RedoRoutes property for the member to be
// deleted, disabled, or converted (physical standby database) to
// the empty string and then retry the operation.
/
16693, 00000, "requirements not met for enabling fast-start failover"
// *Cause: The attempt to enable fast-start failover could not be completed
// because one or more requirements were not met:
// - The effective redo transport mode for both the primary database
// and the fast-start failover target standby database must be set
// to either SYNC or FASTSYNC if the configuration protection mode
// is set to MaxProtection or MaxAvailability mode.
// - The effective redo transport mode for both the primary database
// and the fast-start failover target standby database must be
// set to ASYNC if the configuration protection mode is set to
// MaxPerformance mode.
// - No valid target standby database was specified in the primary
// database FastStartFailoverTarget property prior to the attempt
// to enable fast-start failover, and more than one standby
// database exists in the Oracle Data Guard configuration.
// - fast-start failover target standby database did not receive redo
// data directly from the primary database when the protection mode
// was set to MaxPerformance mode.
// - The primary database has multiple routes to the fast-start
// failover target standby database.
// - Logical standby databases could not be the fast-start failover
// targets because the configuration protection mode was set to
// MaxProtection mode.
// *Action: Retry the command after correcting the issue:
// - Ensure that the effective redo transport mode for both the
// primary database and the fast-start failover target standby
// database are either SYNC or FASTSYNC if the configuration
// protection mode is set to MaxProtection or MaxAvailability mode.
// - Ensure that the LogXptMode property for both the primary
// database and the fast-start failover target standby database
// are set to ASYNC if the configuration protection mode is set to
// MaxPerformance mode.
// - Ensure the RedoRoutes property of the primary includes the name
// of the fast-start failover target standby database when the
// protection mode is set to maximum performance mode.
// - Ensure the RedoRoutes property of the primary database has only
// one route to the fast-start failover target standby database.
/
16694, 00000, "one or more databases involved in switchover need to be restarted"
// *Cause: An error occurred during the restart of either the old and the new
// primary databases or both in a switchover operation.
// *Action: Manually restart both the old and new primary databases, including
// all their Oracle RAC instances if it is an Oracle RAC database.
/
16695, 00000, "a RedoRoutes rule requires asynchronous redo transport mode"
// *Cause: The member could not receive redo data from another standby
// database or a far sync instance because either a RedoRoutes rule
// for that standby or far sync instance did not specify asynchronous
// redo transport mode or the LogXptMode property of the receiving
// member was not set to asynchronous redo transport mode.
// *Action: A standby database or far sync instance can only send redo data in
// asynchronous mode. Set the LogXptMode for the receiving member
// to ASYNC before changing the RedoRoutes of the standby database or
// far sync instance that is to send redo data. Or, specify ASYNC in
// the RedoRoutes property of either the sending standby database or
// far sync instance to override the value specified in the LogXptMode
// property of the receiving member.
/
16696, 00000, "redo source is disabled"
// *Cause: An attempt was made to enable a member whose redo source was
// disabled.
// *Action: Enable the redo source first and then retry the command.
/
16697, 00000, "wrong standby type specified for RedoRoutes property modification"
// *Cause: A logical standby database or snapshot standby database was
// specified to send redo data.
// *Action: Check the setting of the RedoRoutes property and confirm that
// a primary database, physical standby database, or far sync
// instance is specified to send the redo data.
/
16698, 00000, "member has a LOG_ARCHIVE_DEST_n parameter with SERVICE attribute set"
// *Cause: One or more LOG_ARCHIVE_DEST_n initialization parameters that
// contain a SERVICE attribute for another member in the
// configuration were set on the new member when attempting to add a
// standby database or far sync instance to the configuration.
// *Action: Clear all LOG_ARCHIVE_DEST_n initialization parameters that
// contain a SERVICE attribute for another member in the configuration
// on the new member to be added.
/
16699, 00000, "connect identifier not specified"
// *Cause: The connect identifier was not specified for the DGMGRL CLI ADD
// command.
// *Action: Retry the ADD command with a connect identifier for the object to
// be added.
/
/ 16700 - 16899 reserved for Data Guard Broker RSM errors
/
16700, 00000, "the standby database has diverged from the primary database"
// *Cause: The primary database may have been flashed back or restored
// from a backup set and then reopened with the RESETLOGS
// option.
// *Action: Re-create the standby database from the primary database or
// flash back the standby database to the same point the primary
// database had been flashed back to.
/
16701, 00000, "Oracle Data Guard broker command failed"
// *Cause: The command to modify or query the member failed.
// *Action: Check the Oracle Data Guard broker log file for the reason for the
// failure and reissue the command.
/
16702, 00000, "Oracle Data Guard broker command warning"
// *Cause: The command to modify or query the member resulted in a warning.
// *Action: Check the Oracle Data Guard broker log file for the warning and, if
// necessary, reissue the command.
/
16703, 00000, "cannot set property while the member is enabled"
// *Cause: An attempt was made to change a member property while the
// member was enabled.
// *Action: Disable the member first, update the property, and then reenable
// the member.
/
16704, 00000, "standby database not valid for primary database"
// *Cause: The standby database was not added to the Oracle Data Guard broker
// configuration because it was not a valid standby database for
// the primary database.
// *Action: Add a database to the Oracle Data Guard broker configuration that
// is a valid standby database to the primary database.
/
16705, 00000, "internal error in Data guard broker"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16706, 00000, "Oracle Data Guard broker worker process not available"
// *Cause: The Oracle Data Guard broker worker process was not available to
// service the request.
// *Action: Contact Oracle Support Services.
/
16707, 00000, "the value of the property %s is invalid, valid values are %s"
// *Cause: An invalid property value was specified while broker management of
// the member was disabled.
// *Action: Reset the property to a valid value.
/
16708, 00000, "the state supplied to broker is invalid"
// *Cause: The state name specified was invalid for the database.
// *Action: Check the state name and reissue the command.
/
16709, 00000, "standby archived log location settings conflict with database recovery area"
// *Cause: The StandbyArchiveLocation or AlternateLocation property was set
// to USE_DB_RECOVERY_FILE_DEST, but the initialization
// parameter DB_RECOVERY_FILE_DEST did not specify a valid
// destination.
// *Action: Use a value other than USE_DB_RECOVERY_FILE_DEST for
// StandbyArchiveLocation or AlternateLocation, or set up a valid
// database recovery area by setting DB_RECOVERY_FILE_DEST to
// a valid destination.
/
16710, 00000, "snapshot standby database should be converted back to a physical standby database as soon as possible"
// *Cause: A failover causes this snapshot standby database to enter a state
// that requires it to be re-created if another failover occurs before
// it is converted back to a physical standby database.
// *Action: Reenable the snapshot standby database if it is disabled and
// convert it back to a physical standby database as soon as possible
// because the snapshot standby database will have to be re-created
// if another failover occurs while it is in this state.
/
16711, 00000, "resource manager service function not defined"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16712, 00000, "the resource handle is invalid"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16713, 00000, "The Oracle Data Guard broker command timed out."
// *Cause: The Oracle Data Guard broker timed out the command.
// *Action: Verify that the command is valid for the member and then
// retry the command.
/
16714, 00000, "the value of property %s is inconsistent with the member setting"
// *Cause: The value of the specified configuration property was inconsistent
// with member's in-memory settings or server parameter file
// settings. This may be caused by changing an initialization
// parameter that corresponds to a configuration property.
// *Action: Query the InconsistentProperties property on the member to
// determine the which properties are set inconsistently and set the
// properties to make them consisent.
/
16715, 00000, "redo transport-related property %s of member \"%s\" is inconsistent"
// *Cause: The value of the specified redo transport-related configuration
// property of the given member was inconsistent with the primary
// database redo transport service setting. This may be caused by
// changing an initialization parameter that corresponds to a
// configuration property.
// *Action: Query the InconsistentLogXptProps property on the primary database
// to determine which redo transport properties are set
// inconsistently. Reset the properties on the member to make them
// consistent with the primary database redo transport settings.
/
16716, 00000, "clearing parameter LOG_ARCHIVE_DEST failed"
// *Cause: An attempt to clear the LOG_ARCHIVE_DEST parameter failed.
// *Action: Contact Oracle Support Services.
/
16717, 00000, "clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed"
// *Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST parameter failed.
// *Action: Contact Oracle Support Services.
/
16718, 00000, "failed to locate member"
// *Cause: The Oracle Data Guard broker was unable to locate the member in
// the broker configuration.
// *Action: Add the member to the broker configuration and then reissue
// the command.
/
16719, 00000, "unable to query V$ARCHIVE_DEST fixed view"
// *Cause: The broker failed to query the V$ARCHIVE_DEST fixed view."
// *Action: Test and clear the problem using SQL*Plus.
/
16720, 00000, "no LOG_ARCHIVE_DEST_n initialization parameters available"
// *Cause: All LOG_ARCHIVE_DEST_n initialization parameters were in use, or
// all initialization parameters from LOG_ARCHIVE_DEST_1 through
// LOG_ARCHIVE_DEST_10 that can support SYNC were in use.
// *Action: Clear one or more LOG_ARCHIVE_DEST_n initialization parameters
// so that Data Guard broker can use them to set up the primary
// database redo transport.
/
16721, 00000, "unable to set LOG_ARCHIVE_DEST_n initialization parameters"
// *Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_n
// initialization parameters.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log files for more details.
/
16722, 00000, "unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters"
// *Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_STATE_n
// initialization parameters.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log files for more details.
/
16723, 00000, "setting AlternateLocation property conflicts with the redo transport setting"
// *Cause: The standby database was not using standby redo logs, and
// the redo transport service to the standby database is set to a
// nonzero value for the ReopenSecs property and a value of zero for
// the MaxFailure property. In this case, the redo transport service
// will attempt to send redo data to the standby database
// indefinitely and never switch to the alternate destination.
// *Action: Any one of the following actions will solve the problem:
// - add standby redo logs to the standby database.
// - set ReopenSecs property to zero.
// - set MaxFailure property to a nonzero value.
// After performing one of the above actions, reset the standby
// database AlternateLocation property.
/
16724, 00000, "cannot resolve gap for one or more members"
// *Cause: The primary database could not resolve a gap request from one or
// more members.
// *Action: To see which member has an unresolvable gap, check the status of
// the primary database using either Enterprise Manager or
// the DGMGRL CLI SHOW DATABASE command. Copy the missing archived
// log files from either backups or from another member in the
// configuration that has the files for the member that is missing the
// files.
/
16725, 00000, "the phase supplied to Data Guard broker worker process is invalid"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16726, 00000, "the external condition supplied to Data Guard broker worker process is invalid"
// *Document: NO
// *Cause: This was an internal error.
// *Action: Contact Oracle Support Services.
/
16727, 00000, "cannot close database"
// *Cause: The Oracle Data Guard broker could not close the database.
// *Action: Terminate any active sessions connected to the database and
// then reissue the command.
/
16728, 00000, "consistency check for property %s found %s error"
// *Cause: The consistency check for the specified property failed
// due to the error shown.
// *Action: Check the error message and clear the error.
/
16729, 00000, "validation of value for property %s found %s error"
// *Cause: The property value validation failed due to the error shown.
// *Action: Check the error message and clear the error.
/
16730, 00000, "SQL Apply was not started"
// *Cause: SQL Apply was not started because there were no pluggable
// databases opened in read/write mode.
// *Action: Open at least one pluggable database in read/write mode. Data Guard
// will then automatically start SQL Apply.
/
16731, 00000, "No pluggable databases are opened in read/write mode"
// *Cause: The operation failed because there were no pluggable databases
// opened in read/write mode.
// *Action: Open at least one pluggable database in read/write mode and retry
// the command.
/
16732, 00000, "Oracle Clusterware is restarting the database instance"
// *Cause: The Oracle Data Guard broker operation required this database
// instance to be shut down and restarted.
// *Action: If Oracle Clusterware has not already done so, shut down the
// Oracle instance and then restart it.
/
16733, 00000, "member has previously posted a phase done message for the task"
// *Document: NO
// *Cause: A phase done message was already posted for this task.
// *Action: No action necessary.
/
16734, 00000, "OnlineArchiveLocation and StandbyArchiveLocation contain conflicting attributes."
// *Cause: An attempt was made to set the OnlineArchiveLocation and
// StandbyArchiveLocation configurable properties to the same
// destination with different attributes.
// *Action: Ensure that the OnlineArchiveLocation and StandbyArchiveLocation
// configurable properties specify the same attributes when they
// specify the same destination.
/
16735, 0000, "primary redo generation suspended"
// *Cause: Redo generation on the primary database was suspended because
// either the fast-start failover target was unavailable or the
// network connection between both databases was disrupted.
// *Action: Ensure that the fast-start failover target standby database is
// running and the network connection between both databases is
// restored.
/
16736, 00000, "unable to find the destination entry of member \"%s\" in V$ARCHIVE_DEST"
// *Cause: Either the destination was manually changed or deleted out of
// Oracle Data Guard broker, or no entry was available for the Oracle
// Data Guard broker to use.
// *Action: Clean up the destination setting, remove the unused settings,
// and reset the redo transport service.
/
16737, 00000, "the redo transport service for member \"%s\" has an error"
// *Cause: A communication problem with the member caused the redo transport
// to fail.
// *Action: Query the LogXptStatus property to see the error message.
// Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16738, 00000, "redo transport service for member \"%s\" is not running"
// *Cause: The redo transport service for the specified member was not
// running.
// *Action: Check the Oracle Data Guard broker log file or the Oracle alert
// log file for more details. If necessary, start the redo transport
// service for the member.
/
16739, 00000, "redo transport service for member \"%s\" is running"
// *Cause: The redo transport service for the member was running.
// *Action: Check the Oracle Data Guard broker log file for more details. If
// necessary, stop the redo transport service for the member.
/
16740, 00000, "redo transport service for member \"%s\" incorrectly set to ALTERNATE"
// *Cause: The redo transport service to the member was set to ALTERNATE when
// no other destination was set to alternate to this destination.
// *Action: Reenable the member or the entire configuration to allow
// the configuration property settings to be propagated to the
// initialization parameters.
/
16741, 00000, "the destination parameter of member \"%s\" has incorrect syntax"
// *Cause: The destination defined in the server parameter file of the
// primary database had incorrect syntax and Data Guard broker
// failed to update the destination when redo transport services
// were enabled.
// *Action: Fix the syntax error in the primary database server parameter
// file or remove the entry from the server parameter file. Also,
// check the values of the redo transport-related properties for
// the specified member.
/
16742, 00000, "The member \"%s\" has exhausted its quota."
// *Cause: The member exhausted its quota for storing archived redo logs.
// *Action: Remove some archived redo logs from the member or increase its
// quota.
/
16743, 00000, "cannot determine status of redo transport service for member \"%s\""
// *Cause: The status of redo transport to the specified member could not be
// determined.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16744, 00000, "The DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full."
// *Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full
// and the Oracle Data Guard broker was not able to add a new
// DB_UNIQUE_NAME to the list.
// *Action: Remove some unused entries in the DG_CONFIG list, then reenable
// the member.
/
16745, 00000, "unable to add DB_UNIQUE_NAME \"%s\" into the DG_CONFIG list because it is full"
// *Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full
// and the Oracle Data Guard broker was not able to add the specified
// DB_UNIQUE_NAME to the list.
// *Action: Remove some unused entries in the DG_CONFIG list then reenable
// the member.
/
16746, 00000, "Oracle Data Guard broker cannot mount the database"
// *Cause: The Oracle Data Guard broker failed to mount the database.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16747, 00000, "logical standby database guard could not be turned on"
// *Cause: The Oracle Data Guard broker could not turn on the logical standby
// database guard.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16748, 00000, "Oracle Data Guard broker cannot open the primary database"
// *Cause: The Oracle Data Guard broker failed to open the primary database.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16749, 00000, "switchover to logical standby database failed"
// *Cause: The Oracle Data Guard broker failed to switch a logical standby
// database over to a primary database.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16750, 00000, "failed to activate logical standby database"
// *Cause: The Oracle Data Guard broker failed to activate a logical standby
// database.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16751, 00000, "failed to switchover to physical standby database"
// *Cause: The Oracle Data Guard broker failed to switch a physical standby
// database over to a primary database.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16752, 00000, "Dump System State"
// *Document: NO
// *Cause: The Oracle Data Guard broker detected an internal problem and
// request a system state dump.
// *Action: N/A, this is an Oracle internal event code.
/
16753, 00000, "Oracle Data Guard broker cannot open standby database"
// *Cause: The Oracle Data Guard broker failed to open the standby database.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16754, 00000, "failed to activate physical standby database"
// *Cause: The Oracle Data Guard broker failed to activate the physical
// standby database.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16755, 00000, "failed to set initialization parameter"
// *Cause: The Oracle Data Guard broker failed to set an initialization
// parameter using either the ALTER SYSTEM SET or ALTER SYSTEM RESET
// command.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16756, 00000, "Dump Hang Analysis"
// *Document: NO
// *Cause: The Oracle Data Guard broker detected an internal problem and
// request a hang analysis dump.
// *Action: N/A, this is an Oracle internal event code.
/
16757, 00000, "unable to get the value of this property"
// *Cause: The Oracle Data Guard broker failed to get the value for the
// specified property because the value for the specified property
// is not available for the current database role.
// *Action: If the value of the specified property is not available for the
// current role of the database, specify this property for a
// database for which the value is available. Otherwise, check the
// Oracle Data Guard broker log file for more details.
/
16758, 00000, "the specified apply instance is not running"
// *Cause: The Oracle Data Guard broker could not start apply services on the
// specified instance because that instance was not running.
// *Action: Start the instance and then retry the command.
/
16759, 00000, "cannot start SQL Apply with initial SCN"
// *Cause: The Oracle Data Guard broker failed to start SQL Apply with an
// initial system change number (SCN).
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16760, 00000, "cannot start SQL Apply"
// *Cause: The Oracle Data Guard broker failed to start SQL Apply.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16761, 00000, "cannot stop SQL Apply"
// *Cause: The Oracle Data Guard broker failed to stop SQL Apply.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16762, 00000, "invalid database state"
// *Cause: Database was not in the intended state.
// *Action: Determine the reason why the database is not running in the
// intended state and reissue the command.
/
16763, 00000, "redo transport service for a member is running"
// *Cause: The redo transport service for a member was running.
// *Action: For more details, check the status of the primary database using
// either Oracle Enterprise Manager or the DGMGRL CLI SHOW DATABASE
// command. If necessary, stop the redo transport service to the
// member.
/
16764, 00000, "redo transport service to a member is not running"
// *Cause: The redo transport service to a member was not running.
// *Action: For more details, check the status of the primary database using
// either Oracle Enterprise Manager or the DGMGRL CLI SHOW DATABASE
// command. If necessary, start the redo transport service to the
// member.
/
16765, 00000, "Redo Apply is running"
// *Cause: Redo Apply was running when it should have been stopped.
// *Action: If necessary, stop Redo Apply.
/
16766, 00000, "Redo Apply is stopped"
// *Cause: Redo Apply was stopped when it should have been running.
// *Action: Check the alert log to see why Redo Apply terminated, correct any
// problems that may exist, and restart Redo Apply by setting the
// physical standby database state to APPLY-ON.
/
16767, 00000, "SQL Apply is running"
// *Cause: SQL Apply was running when it should have been stopped."
// *Action: If necessary, stop SQL Apply.
/
16768, 00000, "SQL Apply is stopped"
// *Cause: SQL Apply was stopped when it should have been running."
// *Action: Check the alert log to see why SQL Apply terminated, correct any
// problems that may exist, and restart SQL Apply by setting the
// logical standby database state to APPLY-ON.
/
16769, 00000, "the physical standby database is open read-only"
// *Cause: All instances in the physical standby database were put into
// a read-only state instead of APPLY-OFF.
// *Action: Issue the EDIT DATABASE SET STATE command to set the database
// to the APPLY-OFF state.
/
16770, 00000, "Redo Apply not started since physical standby database is opening"
// *Cause: Redo Apply services could not be started on the physical standby
// database because it was being opened. The Oracle Data Guard broker
// will start Redo Apply services once the physical standby database
// has been opened.
// *Action: No action required.
/
16771, 00000, "failover to a physical standby database failed"
// *Cause: The Oracle Data Guard broker encountered errors when converting a
// physical standby database to a primary database.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16772, 00000, "switchover to a standby database failed"
// *Cause: The Oracle Data Guard broker encountered errors when switching over
// to the specified standby database.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16773, 00000, "cannot start Redo Apply"
// *Cause: The Oracle Data Guard broker failed to start Redo Apply.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details. If the database is already open, the
// broker will not start Redo Apply if the Oracle Active Data Guard
// option is not enabled.
/
16774, 00000, "cannot stop Redo Apply"
// *Cause: The Oracle Data Guard broker failed to stop Redo Apply.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16775, 00000, "target standby database in broker operation has potential data loss"
// *Cause: The target standby database specified for the broker operation
// did not have all the redo data from the primary database.
// *Action: Confirm that the redo transport service on the primary database
// is functioning correctly by checking its status using either
// Enterprise Manager or the DGMGRL CLI SHOW DATABASE command.
// Reissue the broker command once all redo data is available on
// the target standby database.
/
16776, 00000, "health check of the redo transport service failed"
// *Cause: The Oracle Data Guard broker could not complete the health check
// for the redo transport service.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16777, 00000, "unable to find the destination entry of a member in V$ARCHIVE_DEST"
// *Cause: Either a destination was manually deleted or no entry was available
// for Oracle Data Guard.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details. The redo transport service may need to
// be reset.
/
16778, 00000, "redo transport error for one or more members"
// *Cause: The redo transport service was unable to send redo data to one
// or more members.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details. Query the LogXptStatus property to see
// the errors.
/
16779, 00000, "The destination parameter of a member is set incorrectly."
// *Cause: The destination was defined in the LOG_ARCHIVE_DEST_n
// server parameter file with incorrect syntax.
// The Oracle Data Guard broker failed to update the destination when
// the redo transport was turned on.
// *Action: Check the Oracle Data Guard broker log file to see which member
// has the problem. Fix the syntax error in the server parameter file
// or remove the entry from the server parameter file. Check if the
// syntax of the redo transport-related properties is correct.
/
16780, 00000, "A member has exhausted its archived redo log storage quota."
// *Cause: A member has exhausted its quota for storing archived redo logs.
// *Action: Check the Oracle Data Guard broker log file to see which member
// has the problem. Remove some archived redo logs or increase the
// quota on the storage the member is using for archived redo logs.
/
16781, 00000, "cannot determine status of redo transport service for member"
// *Cause: The status of redo transport to the specified member could not be
// determined.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more details.
/
16782, 00000, "instance not open for read and write access"
// *Cause: The database was mounted on an instance but not opened for read
// and write access.
// *Action: For more details, check the status of the database using either
// Enterprise Manager or the DGMGRL CLI SHOW DATABASE command.
// If possible, open the instance manually.
/
16783, 00000, "cannot resolve gap for member %s"
// *Cause: The primary database could not resolve a gap request from the
// specified member or members.
// *Action: Copy the missing archived redo log files from either backups or
// from another member in the configuration that has the files for
// the member or members missing the files.
/
16784, 00000, "member name specified by Dependency property is incorrect"
// *Cause: The member name that should be the value of the
// DB_UNIQUE_NAME initialization parameter specified in the
// Dependency property was incorrect.
// *Action: Reset the Dependency property to the correct name of the member.
/
16785, 00000, "the database is in NOARCHIVELOG mode"
// *Cause: The database was in NOARCHIVELOG mode when it was either a
// primary database or when it was a standby database that was
// being switched over to be a primary database.
// *Action: Set the database to ARCHIVELOG mode by issuing the ALTER DATABASE
// ARCHIVELOG command.
/
16786, 00000, "unable to access Oracle Data Guard broker configuration files"
// *Cause: The Oracle Data Guard broker configuration files did not exist or
// or could not be accessed.
// *Action: Check the Oracle Data Guard broker log file for more details.
/
16787, 00000, "event for Oracle Data Guard broker worker process testing"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is used for
// verifying Oracle Data Guard broker worker process functionality.
// DO NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
16788, 00000, "unable to set one or more member configurable property values"
// *Cause: This situation occurred when the broker attempted to set member
// configurable property values into the member by issuing
// ALTER SYSTEM or ALTER DATABASE commands.
// Typical causes of this error are:
// - The values of redo transport-related properties contain syntax
// syntax errors.
// - The value of the LogArchiveTrace property was out of range.
// *Action: Check the Oracle Data Guard broker log file to see which property
// has the problem and set the property to the correct value.
/
16789, 00000, "standby redo logs configured incorrectly"
// *Cause: Standby redo logs were not configured or were configured
// incorrectly for the member.
// *Action: Standby redo logs are required when the redo transport mode is
// set to SYNC or ASYNC. Check the Oracle Data Guard documentation to
// find more information about the correct configuration of standby
// redo logs.
/
16790, 00000, "the value of the configurable property is invalid"
// *Cause: An invalid property value was entered, or a RESET was attempted
// on a property for which no Broker default value exists.
// *Action: Set the property to a correct value.
/
16791, 00000, "unable to check the existence of the standby redo logs"
// *Cause: The member may not be mounted, or the query of the V$STANDBY_LOG
// fixed view failed.
// *Action: Ensure the member is mounted and query the V$STANDBY_LOG fixed
// view to see if the problem has been corrected, and retry the
// operation.
/
16792, 00000, "configurable property value is inconsistent with member setting"
// *Cause: The values of one or more configurable properties were
// inconsistent with the in-memory settings or server parameter
// file settings. This may happen by directly altering initialization
// parameters instead of editing configurable property values using
// Oracle Data Guard broker.
// *Action: Query the InconsistentProperties property on the member or check
// the Oracle Data Guard broker log file to find which properties are
// set inconsistently. Reset these properties to make them consistent
// with the database settings. Alternatively, enable the member
// or the entire configuration to allow the configurable property
// settings to be propagated to the initialization parameters.
/
16793, 00000, "logical standby database guard is off"
// *Cause: The logical standby database guard was turned off.
// *Action: Issue the ALTER DATABASE GUARD ALL command to turn the guard on
// and verify that Data Guard health check error or warning is
// cleared.
/
16794, 00000, "database guard is on for primary database"
// *Cause: The database guard was turned on for the primary database.
// *Action: Issue the ALTER DATABASE GUARD NONE command to turn off the guard
// and verify that Data Guard health check error or warning is
// cleared.
/
16795, 00000, "the standby database needs to be re-created"
// *Cause: A switchover or failover operation caused this database to
// require re-creation. The database was marked for re-creation
// because it was not a viable standby database for the new primary
// database.
//
// Until this error status is resolved for this database, information
// about this database and the broker configuration to which it
// belongs is unavailable to a broker client that is connected to
// this database. Therefore, all commands directed by that client to
// this database cannot be completed.
//
// *Action: Re-create (or flash back) the standby database. Connect to the
// primary database in the broker configuration and reenable broker
// management of that database. Once enabled, it is possible
// to connect to that standby database and manage it with the broker.
//
// Alternatively, many client commands that cannot be completed at
// the standby database when in this error state can be completed
// successfully when issued to the primary database. In this case,
// simply reconnect to the primary database and retry the command.
/
16796, 00000, "one or more properties could not be imported from the member"
// *Cause: The broker was unable to import property values for the member
// being added to the broker configuration. This error indicates:
// - The Oracle Net service name specified in DGMGRL CREATE
// CONFIGURATION, ADD DATABASE, ADD FAR_SYNC, or ADD
// RECOVERY_APPLIANCE command was not one that provides
// access to the member being added.
// - There were no instances running for the member being added.
// *Action: Remove the member from the configuration using the REMOVE
// CONFIGURATION, REMOVE DATABASE, REMOVE FAR_SYNC, or REMOVE
// RECOVERY_APPLIANCE command. Ensure that the member to be added
// has at least one instance running and that the Oracle Net service
// name provides access to the running instance. Also, check the
// broker log file for additional information. Then, reissue the
// CREATE CONFIGURATION, ADD DATABASE, ADD FAR_SYNC, or ADD
// RECOVERY_APPLIANCE command.
/
16797, 00000, "member is not using a server parameter file"
// *Cause: The member was not using a server parameter file or the broker
// was unable to access the server parameter file.
// *Action: Issue the CREATE SPFILE='..' FROM PFILE='...' command to create
// a server parameter file and then restart the member to use it.
/
16798, 00000, "unable to complete recovery during failover"
// *Cause: The physical standby database could not complete recovery
// during failover.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log files to see more details on the reason for the failure.
/
16799, 00000, "Redo Apply is not running"
// *Cause: Either the Oracle Data Guard broker configuration indicated that
// Redo Apply was turned off, or the MRP0 recovery process was not
// running. As a result, Redo Apply-related properties could not be
// set.
// *Action: Turn on Redo Apply through Oracle Data Guard broker and reissue the
// command to set a Redo Apply-related property.
/
16800, 00000, "redo transport service for a standby database incorrectly set to ALTERNATE"
// *Cause: The redo transport service for a standby database was set to
// ALTERNATE when no other destination is set to alternate to this
// destination.
// *Action: Reenable the standby database or the entire configuration to allow
// the configuration property settings to be propagated to the
// initialization parameters.
/
16801, 00000, "redo transport-related property is inconsistent with member setting"
// *Cause: The values of one or more redo transport-related configuration
// properties were inconsistent with the in-memory settings or
// server parameter file settings. This may happen by directly
// altering initialization parameters instead of editing configurable
// property values using Oracle Data Guard broker.
// *Action: Query the InconsistentLogXptProps property on the primary database
// or check the Oracle Data Guard broker log file to find which
// properties are set inconsistently. Reset these properties to make
// them consistent. Alternatively, enable the member or the entire
// configuration to allow the configurable property settings to be
// propagated to the initialization parameters.
/
16802, 00000, "Database role change operation permitted only by Data Guard broker when fast-start failover is enabled."
// *Cause: Fast-start failover was enabled and a role change was not initiated
// from a Data Guard broker interface.
// *Action: Use a Data Guard broker interface to perform a role change.
/
16803, 00000, "unable to query a database table or fixed view"
// *Cause: Querying a database table or fixed view failed. The database
// may not be opened or mounted.
// *Action: Check the Oracle Data Guard broker log file for more details.
/
16804, 00000, "one or more configuration properties have invalid values"
// *Cause: Oracle Data Guard broker health check detected that one or more
// configuration properties in the broker configuration had
// invalid values. The property values were changed while
// broker management of the member was disabled.
// *Action: Check Data Guard broker log file for more details on which
// properties have invalid values and reset them through the Oracle
// Data Guard broker.
/
16805, 00000, "operation required wait for sessions to drain"
// *Document: NO
// *Cause: The Oracle Data Guard broker operation was required to wait
// for sessions to drain.
// *Action: No action necessary.
/
16806, 00000, "supplemental logging is not turned on"
// *Cause: Supplemental logging was not turned on while there was a logical
// standby database in the configuration. This could happen either
// on the primary database or on the logical standby database that
// was being switched over to become the primary database.
// *Action: Check the Oracle Data Guard broker log file for more details.
// Issue the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY,
// UNIQUE INDEX) COLUMNS to add supplemental logging.
/
16807, 00000, "unable to change configuration protection mode"
// *Cause: An attempt to issue the ALTER DATABASE SET STANDBY TO MAXIMIZE
// {PROTECTION | AVAILABILITY | PERFORMANCE} failed.
// *Action: Check the Oracle Data Guard broker log file and the Oracle alert
// log file for more information.
/
16808, 00000, "primary database is not open"
// *Cause: A prior attempt to open the primary database was disallowed
// because the primary had shut itself down earlier after being
// isolated from both the fast-start failover observer and the
// target standby database for more than FastStartFailoverThreshold
// seconds. It was assumed that a fast-start failover was underway.
// Since that time, re-contact with either the observer or the target
// standby database indicates that no such failover had actually
// occurred. The primary database can now be opened.
// *Action: Open the database by issuing the SQL*Plus ALTER DATABASE OPEN
// command.
/
16809, 00000, "multiple warnings detected for the member"
// *Cause: The broker detected multiple warnings for the member.
// *Action: To get a detailed status report, check the status of the member
// specified using either Enterprise Manager or the DGMGRL CLI SHOW
// command.
/
16810, 00000, "multiple errors or warnings detected for the member"
// *Cause: The broker detected multiple errors or warnings for the member.
// *Action: To get a detailed status report, check the status of the database
// specified using either Enterprise Manager or the DGMGRL CLI SHOW
// command.
/
16811, 00000, "apply instance not recorded by the Oracle Data Guard broker"
// *Cause: The broker did not register an apply instance for a standby
// database.
// *Action: Reenable the standby database to clear the error.
/
16812, 00000, "log apply service not running on apply instance recorded by the broker"
// *Cause: Log apply services were not running on the instance the
// Data Guard broker expected them to be running upon.
// *Action: Reenable the standby database to clear the error.
/
16813, 00000, "log apply service not running on apply instance %s recorded by the broker"
// *Cause: Log apply services were not running on the instance the
// Data Guard broker expected them to be running upon.
// *Action: Reenable the standby database to clear the error.
/
16814, 00000, "duplicate name specified for observer"
// *Cause: The observer was not started because an observer with that name
// was already started.
// *Action: Use the DGMGRL CLI SHOW OBSERVER command to check the names of the
// observers that have already been started. Then, reissue the
// START OBSERVER command and specify a different observer name.
/
16815, 00000, "member does not need to be reinstated"
// *Cause: The member specified was either already reinstated or does not
// need to be reinstated.
// *Action: No action necessary. Any stale reinstate required status will be
// cleared after the next health check has completed.
/
16816, 00000, "incorrect database role"
// *Cause: The Oracle Data Guard broker detected that the specified database
// had a different database role than that recorded in the Oracle Data
// Guard broker configuration. This could be the result of a
// failed switchover or failover operation, or a switchover or
// failover operation performed with SQL*Plus.
// *Action: Check the Oracle Data Guard broker documentation to see how to
// recover from failed role change operations, or from role changes
// that were performed using SQL*Plus for databases managed by
// Oracle Data Guard broker.
/
16817, 00000, "unsynchronized fast-start failover configuration"
// *Cause: The fast-start failover target standby database was not
// synchronized with the primary database. As a result, a fast-start
// failover could not happen automatically in case of a primary
// database failure.
// *Action: Ensure that the fast-start failover target standby database is
// running and that the primary database can ship redo data to it.
// When the standby database has received all of the redo data from
// the primary database, the primary and standby databases will then
// be synchronized. The Oracle Data Guard configuration may then fail
// over automatically to the standby database in the event of loss of
// the primary database.
/
16818, 00000, "fast-start failover suspended"
// *Cause: The primary database was intentionally shutdown. As a result,
// a fast-start failover could not happen automatically.
// *Action: Start the primary database. This effectively restores the
// ability to automatically perform a fast-start failover in the
// event of a failure of the primary database.
/
16819, 00000, "fast-start failover observer not started"
// *Cause: The observer for fast-start failover was not started. As a
// result, fast-start failover could not happen in the case of
// a primary database failure.
// *Action: Start the fast-start failover observer by using, for example, the
// DGMGRL START OBSERVER command.
/
16820, 00000, "fast-start failover observer is no longer observing this database"
// *Cause: A previously started observer was no longer actively observing this
// database. A significant amount of time elapsed since this
// database last heard from the observer.
// Possible reasons were:
// - The host where the observer was running was not available.
// - The network connection between the observer and this database
// was not available.
// - The observer process was terminated unexpectedly.
// *Action: Check the reason why the observer cannot contact this database.
// If the problem cannot be corrected, stop the current observer by
// connecting to the Oracle Data Guard configuration and issue the
// DGMGRL STOP OBSERVER command. Then, restart the observer on another
// host. Finally, use the DGMGRL START OBSERVER command to start the
// observer on the other host.
/
16821, 00000, "logical standby database dictionary not yet loaded"
// *Cause: The logical standby database had not loaded the dictionary.
// This status was detected by the broker health check mechanism.
// Alternatively, this status may be returned when attempting to
// switch or fail over to a logical standby database that had not
// yet loaded its dictionary.
// *Action: Start SQL Apply on the logical standby database, if it is not
// already running, and wait for it to reach the APPLYING state.
/
16822, 00000, "new primary database not yet ready for standby database reinstatement"
// *Cause: The new primary database, as a result of a logical standby
// database failover operation, had not fully completed the failover
// operation. An attempt to reinstate a disabled standby database
// could not be completed until failover completed on the new
// primary database.
// *Action: Wait until the failover operation has completed on the new primary
// database. Then retry the reinstate operation.
/
16823, 00000, "redo transport mode is incompatible for current operation"
// *Cause: The redo transport mode of this member was incompatible for this
// broker operation.
// *Action: Reset the LogXptMode member property for this member and retry the
// broker operation.
/
16824, 00000, "multiple warnings, including fast-start failover-related warnings, detected for the database"
// *Cause: The broker detected multiple warnings for the database.
// At least one of these warnings may have prevented fast-start
// failover from occurring.
// *Action: To get a detailed status report, check the status of the database
// specified using either Enterprise Manager or the DGMGRL CLI SHOW
// DATABASE command.
/
16825, 00000, "multiple errors or warnings, including fast-start failover-related errors or warnings, detected for the database"
// *Cause: The broker detected multiple errors or warnings for the
// database. At least one of these errors or warnings
// may have prevented a fast-start failover from occurring.
// *Action: To get a detailed status report, check the status of the database
// specified using either Enterprise Manager or the DGMGRL CLI SHOW
// DATABASE command.
/
16826, 00000, "apply service state is inconsistent with the DelayMins property"
// *Cause: This warning was caused by one of the following reasons:
// - The apply service was started without specifying the real-time
// apply option or without the NODELAY option when the DelayMins
// property was set to zero.
// - The apply service was started with the real-time apply option or
// with the NODELAY option when the DelayMins property was set to
// a value greater than zero.
// *Action: Reenable the standby database to allow the broker to restart
// the apply service with the apply options that are consistent
// with the specified value of the DelayMins property.
/
16827, 00000, "Flashback Database is disabled"
// *Cause: The broker detected that the Flashback Database feature was
// disabled. With Flashback Database disabled, the broker would not
// be able to:
// - reinstate a database that required reinstatement.
// - convert a physical standby database to a snapshot standby
// database.
// - convert a snapshot standby database to a physical standby
// database.
// Flashback Database may been disabled manually with the ALTER
// DATABASE FLASHBACK DATABASE OFF command or automatically by the
// database in the event of an error.
// *Action: Check the database alert log to determine whether Flashback
// Database was disabled due to errors and then correct the
// problem. If Flashback Database had been manually disabled,
// reenable Flashback Database with the ALTER DATABASE FLASHBACK
// DATABASE ON command. If, after enabling Flashback Database,
// the database still cannot be reinstated or converted, you must
// re-create the database from a copy of the primary database.
/
16828, 00000, "invalid value specified for REDO_TRANSPORT_USER initialization parameter"
// *Cause: An invalid value was specified for the REDO_TRANSPORT_USER
// initialization parameter. The length of the user name exceeded
// 30 characters.
// *Action: Check the documentation and specify a new value for the
// REDO_TRANSPORT_USER initialization parameter.
/
16829, 00000, "fast-start failover configuration is lagging"
// *Cause: The fast-start failover target standby database was not
// within the lag limit specified by the FastStartFailoverLagLimit
// configuration property. As a result, a fast-start failover
// could not happen in the event of a primary database failure.
// *Action: Ensure that the fast-start failover target standby database is
// running and applying redo data and that the primary database
// is successfully transmitting redo data. If this condition persists
// consider raising the value of the FastStartFailoverLagLimit
// configuration property.
/
16830, 00000, "primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down"
// *Cause: The primary database was isolated from both the observer and
// target standby database for longer than the seconds specified
// by the FastStartFailoverThreshold property. A fast-start failover
// probably occurred. If the FastStartFailoverPmyShutdown
// configuration property was set to TRUE, the broker will shut down
// the primary database in this situation.
// *Action: Ensure one instance of this database is running and the database
// is mounted on that instance so that the broker may reinstate
// the old primary database.
/
16831, 00000, "operation not allowed on this member"
// *Cause: The Oracle Data Guard broker operation was not allowed for the
// specified member of the Oracle Data Guard broker configuration.
// *Action: Check the documentation for the Oracle Data Guard broker command
// and then reissue the command with the correct member.
/
16832, 00000, "user-configurable fast-start failover initiated: shutting down"
// *Cause: The broker initiated a fast-start failover to the target standby
// database because a user-configurable condition was detected on the
// primary database. In addition, the broker shut down the primary
// database.
// *Action: Correct the problem on the old primary database that caused the
// broker to initiate a fast-start failover, then reinstate the old
// primary database.
/
16833, 00000, "no logging operations detected on database"
// *Cause: The broker detected that no logging operations were performed
// on this database. The data modified by these operations may be
// lost if failover or switchover was performed.
// *Action: Use Data Repair Advisor to determine which operations were not
// logged before attempting a switchover or failover.
/
16834, 00000, "control file corruptions detected on database"
// *Cause: The broker detected control files corruptions. Many database
// operations, including switchover and failover, may not be possible.
// *Action: Use Data Repair Advisor to determine the extent of the corruptions
// and how to repair them.
/
16835, 00000, "member has one or more unavailable standby redo log groups"
// *Cause: The broker detected that the member had one or more unavailable
// standby redo log groups.
// *Action: Use Data Repair Advisor to determine which standby redo log groups
// are unavailable and how the log groups can be made available.
/
16836, 00000, "one or more system data files are missing"
// *Cause: The broker detected that one or more system data files were
// missing.
// *Action: Use Data Repair Advisor to determine which system data files are
// missing and how the files can be restored.
/
16837, 00000, "one or more system data files are corrupt"
// *Cause: The broker detected that one or more system data files were
// corrupt.
// *Action: Use Data Repair Advisor to determine which system data files are
// corrupt and how the files can be restored.
/
16838, 00000, "one or more system data files are offline"
// *Cause: The broker detected that one or more system data files were
// offline.
// *Action: Use Data Repair Advisor to determine which system data files are
// offline and how the files can be made online.
/
16839, 00000, "one or more user data files are missing"
// *Cause: The broker detected that one or more user data files were missing.
// *Action: Use Data Repair Advisor to determine which user data files are
// missing and how the files can be restored.
/
16840, 00000, "one or more user data files are corrupt"
// *Cause: The broker detected that one or more user data files were corrupt.
// *Action: Use Data Repair Advisor to determine which user data files are
// corrupt and how the files can be restored.
/
16841, 00000, "one or more user data files are offline"
// *Cause: The broker detected that one or more user data files were offline.
// *Action: Use Data Repair Advisor to determine which user data files are
// offline and how the files can be made online.
/
16842, 00000, "block corruptions detected"
// *Cause: The broker detected block corruptions on this database.
// *Action: Use Data Repair Advisor to determine which files are affected by
// block corruptions and how the files can be repaired.
/
16843, 00000, "errors discovered in diagnostic repository"
// *Cause: The broker detected one or more errors in the Automatic Diagnostic
// Repository.
// *Action: Use Data Repair Advisor to see the errors that were discovered
// and how they can be repaired.
/
16844, 0000, "database does not have a valid fast-start failover target standby database"
// *Cause: Fast-Start failover was enabled and the current primary database did
// not have a value set for the FastStartFailoverTarget configurable
// property or the value specified for this property was not a valid
// fast-start failover target standby database.
// *Action: Disable fast-start failover or ensure that the primary database has
// a valid fast-start failover target standby database specified by
// setting the FastStartFailoverTarget configurable property value to
// a valid standby database.
/
16845, 00000, "unsupported attribute specified for the local destination property"
// *Cause: The value specified for the local destination property contained
// unsupported attributes.
// *Action: Ensure that the value specified for the local destination
// property does not contain any of these attributes: SERVICE,
// ALTERNATE, or VALID_FOR.
/
16846, 00000, "OnlineArchiveLocation and StandbyArchiveLocation should specify different destinations when OnlineAlternateLocation and StandbyAlternateLocation specify different destinations."
// *Cause: An attempt was made to set the OnlineArchiveLocation and
// StandbyArchiveLocation configurable properties to the same
// destination when the OnlineAlternateLocation and
// StandbyAlternateLocation configurable properties were set to
// different destinations. Or, an attempt was made to set
// OnlineAlternateLocation and StandbyAlternateLocation configurable
// properties to a different destination when the
// OnlineArchiveLocation and StandbyArchiveLocation configurable
// properties were set to the same destination.
// *Action: Ensure that the OnlineArchiveLocation and StandbyArchiveLocation
// configurable properties specify different destinations when
// OnlineAlternateLocation and StandbyAlternateLocation configurable
// properties specify different destinations.
/
16847, 00000, "A previous switchover from this database failed with error %s."
// *Cause: A previous switchover operation from this database failed.
// *Action: Fix the underlying problem and reissue the switchover command
// again.
/
16848, 00000, "A previous switchover to this database failed with error %s."
// *Cause: A previous switchover operation to this database failed.
// *Action: Fix the underlying problem and reissue the switchover command
// again.
/
16849, 00000, "A previous switchover from this database was interrupted and aborted."
// *Cause: A previous switchover operation from this database was interrupted
// by the user. It may be caused by a hang.
// *Action: Fix the underlying problem and reissue the switchover command
// again.
/
16850, 00000, "A previous switchover to this database was interrupted and aborted."
// *Cause: A previous switchover operation to this database was interrupted by
// the user. It may be caused by a hang.
// *Action: Fix the underlying problem and reissue the switchover command
// again.
/
16851, 00000, "A previous failover to this database failed with error %s."
// *Cause: A previous failover operation to this database failed.
// *Action: Fix the underlying problem and reissue the failover command again.
/
16852, 00000, "A previous failover to this database was interrupted and aborted."
// *Cause: A previous failover operation to this database was interrupted by
// the user. It may be caused by a hang.
// *Action: Fix the underlying problem and reissue the failover command again.
/
16853,0000, "apply lag has exceeded specified threshold"
// *Cause: The current apply lag exceeded the value specified by the
// ApplyLagThreshold configurable property. It may be caused either by
// a large transport lag or poor performance of apply services on the
// standby database.
// *Action: Check for gaps on the standby database. If no gap is present, tune
// the apply services.
/
16854, 00000, "apply lag could not be determined"
// *Cause: Apply lag could not be determined because either apply services
// were not running or there was no connectivity between the redo
// source and standby database.
// *Action: Start apply services if they are not running. Also, ensure that
// there is network connectivity between the redo source and standby
// databases and the redo source is sending redo data to the standby.
/
16855,0000, "transport lag has exceeded specified threshold"
// *Cause: The current transport lag exceeded the value specified by the
// TransportLagThreshold configurable property. It is caused by either
// poor network performance between the redo source and the member
// or a network disconnection.
// *Action: Check the network connection between the redo source and the
// member. If they are connected, check the network performance
// between the redo source and the member and tune it if necessary.
/
16856, 00000, "transport lag could not be determined"
// *Cause: Transport lag could not be determined because there was no
// connectivity between the redo source and the member.
// *Action: Ensure that there is network connectivity between the redo source
// and the members and that the redo source is working properly.
/
16857, 00000, "member disconnected from redo source for longer than specified threshold"
// *Cause: The amount of time the member was disconnected from the redo source
// exceeded the value specified by the TransportDisconnectedThreshold
// configurable database property. It is caused by a lack of network
// connectivity between the redo source and the member.
// *Action: Ensure that there is network connectivity between the redo source
// and the member and that the redo source is working properly.
/
16858, 00000, "last communication time from redo source could not be determined"
// *Cause: The member was never contacted by the redo source.
// *Action: Ensure that there is network connectivity between the redo source
// and the member and that the redo source is working properly.
/
16859, 00000, "request terminated because delete, disable, or failover operation is in progress"
// *Cause: The broker terminated a request because it was processing a delete,
// disable, or failover operation.
// *Action: Wait for the operation to complete and then retry the request.
/
16860, 00000, "invalid member specified as the fast-start failover target"
// *Cause: The member specified as the fast-start failover target was either
// a far sync instance or snapshot standby database, or does not
// exist in the configuration.
// *Action: Only a physical or logical standby database can be specified as a
// fast-start failover target. Check the database name and retry the
// command.
/
16861, 00000, "ExternalDestination property requires DB_UNIQUE_NAME attribute"
// *Cause: The value specified for the ExternalDestination property did not
// contain the DB_UNIQUE_NAME attribute.
// *Action: Ensure that DB_UNIQUE_NAME is specified as the value for the
// ExternalDestination property.
/
16862, 00000, "unsupported attribute specified for the ExternalDestination property"
// *Cause: The value specified for the ExternalDestination property contained
// unsupported attributes.
// *Action: Ensure that the value specified for the ExternalDestination
// property does not contain any of these attributes: LOCATION,
// ALTERNATE, MAX_FAILURE, SYNC, TEMPLATE, MANDATORY, DELAY,
// NET_TIMEOUT, and VALID_FOR.
/
16863, 00000, "A member whose MaxFailure property is set to zero cannot be part of a RedoRoutes group."
// *Cause: A member was specified to be part of a RedoRoutes group when the
// MaxFailure configurable property was set to zero.
// *Action: Set the MaxFailure property to a nonzero value and retry the
// command.
/
16864, 00000, "The MaxFailure property cannot be set to zero for a member that is part of a RedoRoutes group."
// *Cause: An attempt was made to set the MaxFailure configurable property to
// zero when it was part of a RedoRoutes group.
// *Action: Set the MaxFailure configurable property to a nonzero value.
/
16865, 00000, "database is closing or is not mounted on the instance"
// *Cause: Broker health check was unable to complete because the database
// was closing or was not mounted on the instance.
// *Action: No action is required if the database is closing. Mount the
// database if it is not yet mounted on the instance.
/
16866, 0000, "database converted to transient logical standby database for rolling database maintenance"
// *Cause: This database was converted to a logical standby database because
// a rolling database maintenance operation was in progress.
// *Action: No action is required. The database will be converted to a primary
// database when the DBMS_ROLLING.SWITCHOVER procedure is executed or
// to a physical standby database when the DBMS_ROLLING.FINISH
// procedure is executed.
/
16867, 0000, "cannot remove a database that is specified in a FastStartFailoverTarget configuration property"
// *Cause: An attempt was made to remove a database that was specified in
// the FastStartFailoverTarget configuration property of another
// database.
// *Action: First, remove the database from all other database's
// FastStartFailoverTarget configuration property values. Then, retry
// the REMOVE command.
/
16868, 0000, "Fast-Start Failover target standby database not viable"
// *Cause: The Fast-Start Failover target standby database was not viable.
// As a result, a Fast-Start Failover to this database could not
// happen automatically.
// *Action: After the standby database has been re-created from a copy of
// the new primary database, disable and then reenable the standby
// database.
/
16869, 0000, "fast-start failover target not initialized"
// *Cause: The standby database was not yet ready to be a Fast-Start Failover
// target standby database. Consequently, Fast-Start Failover cannot
// be initiated to this database in the event of a primary database
// failure.
// *Action: Ensure that the network connection between the primary and the
// Fast-Start Failover target standby is functioning properly.
/
16870, 00000, "rolling database maintenance is in progress"
// *Document: NO
// *Cause: This is an Oracle internal status code. This status is used by the
// primary database to convey to the standby database during startup,
// that rolling database maintenance is in progress within the
// configuration.
// *Action: N/A, this is an Oracle internal status code.
/
16871, 00000, "fast-start failover target switch is not supported"
// *Cause: Automatic switch of the fast-start failover target was not
// possible because the release of the observer was earlier than
// 12.2. Consequently, the fast-start failover target switch will not
// occur even though the primary database has more than one
// fast-start failover target configured.
// *Action: Upgrade the Oracle client home to release 12.2 and then stop and
// restart the observer using the DGMGRL CLI in that Oracle home.
/
16872, 00000, "OnlineAlternateLocation and StandbyAlternateLocation contain conflicting attributes."
// *Cause: An attempt was made to set the OnlineAlternateLocation and
// StandbyAlternateLocation configurable properties to the same
// destination with different attributes.
// *Action: Ensure that the OnlineAlternateLocation and StandbyAlternateLocation
// configurable properties specify the same attributes when they
// specify the same destination.
/
16873, 0000, "The observer with the specified name is not started."
// *Cause: The operation was not allowed because the observer corresponding
// to the specified name was not started.
// *Action: Issue the command again after ensuring that the observer
// corresponding to the specified name is started.
/
16874, 0000, "The specified observer host is invalid."
// *Cause: The operation was not allowed because there was no registered
// observer running on the specified host.
// *Action: Issue the command again after ensuring that there is a registered
// observer running on the specified host.
/
16875, 00000, "master observer switch is in progress"
// *Cause: The operation was not allowed because a master observer
// switch was already in progress.
// *Action: Wait for a few seconds and retry the operation.
/
16876, 00000, "observer name not specified"
// *Cause: The operation was not allowed because an observer name was not
// specified and there was more than one observer registered.
// *Action: Specify the observer name or clause ALL in the failed commmand
// when more than one observer is registered.
/
16877, 00000, "no registered observers"
// *Cause: The operation was not allowed because there were no registered
// observers.
// *Action: None.
/
16878, 00000, "master observer cannot be stopped"
// *Cause: The master observer cannot be stopped when another observer is
// registered.
// *Action: Use the SET MASTEROBSERVER command to establish another
// observer as the master observer. Then use the STOP OBSERVER command
// to stop the former master observer.
/
16879, 00000, "fast-start failover cannot be initiated by a non-master observer"
// *Cause: Fast-start failover was initiated by a non-master observer. This
// can occur if Data Guard Broker starts to switch master observer
// when fast-start failover is being initiated.
// *Action: Check the DRC log files of the primary database to see why a master
// observer switch occurred.
/
16880, 00000, "fast-start failover target switch is in progress"
// *Cause: The operation was not allowed because a fast-start failover target
// switch was already in progress.
// *Action: Wait for a few seconds and retry the operation.
/
16881, 00000, "standby database is not protecting the current primary database during rolling database maintenance"
// *Cause: This standby database was a member of the leading group standby
// databases protecting the future primary database, or was a member
// of the trailing group standby databases protecting the original
// primary database during the rolling database maintenance operation.
// *Action: This issue will be resolved once all the databases have completed
// the maintenance operation and the DBMS_ROLLING.FINISH procedure is
// executed.
/
16882, 00000, "rolling database maintenance processing is managing apply services"
// *Cause: Apply services were stopped because a rolling database maintenance
// operation was in progress.
// *Action: No action is required. Apply services will be restarted by Oracle.
/
16883, 00000, "unable to translate DGConnectIdentifier property"
// *Cause: The DGConnectIdentifier property value could not be translated to a
// valid connect descriptor.
// *Action: Ensure that the DGConnectIdentifier property value translates to a
// valid connect descriptor.
/
16884, 00000, "unable to start more than one observer"
// *Cause: More than one observer could not be started because the release
// of the observer was earlier than 12.2.
// *Action: Upgrade the Oracle client home to release 12.2 and start the
// observer using the DGMGRL CLI in that home.
/
16885, 00000, "A member whose RedoCompression property is set to LZO cannot receive redo data in SYNC or FASTSYNC mode."
// *Cause: A member was specified to receive redo data in SYNC or FASTSYNC
// mode when the RedoCompression configurable property was set to LZO.
// *Action: Set the RedoCompression property to a value other than LZO and then
// retry the command.
/
16886, 00000, "The RedoCompression property cannot be set to LZO for a member that receives redo data in SYNC or FASTSYNC mode."
// *Cause: An attempt was made to set the RedoCompression configurable
// property to LZO when it receives redo data in SYNC or FASTSYNC mode.
// *Action: Set the RedoCompression configurable property to a value other than
// LZO and then retry the command.
/
/ 16900 - 16949 Reserved for Data Guard Broker
/
16900, 00000, "change of LogXptMode or RedoRoutes property violates overall protection mode"
// *Cause: The broker did not allow the attempt to change the LogXptMode or
// RedoRoutes configurable property for the standby database or far
// sync instance because, if allowed, the overall protection mode for
// the configuration would have been violated.
// *Action: If the LogXptMode or RedoRoutes configuration property must be
// changed for the specified standby database or far sync instance,
// first downgrade the overall protection mode for the broker
// configuration. After that operation has completed, the LogXptMode
// or RedoRoutes configuration property for the standby database can
// be changed.
/
16901, 00000, "A rolling database maintenance operation is in progress."
// *Cause: The attempted operation was not allowed because a rolling
// database maintenance operation was in progress.
// *Action: Wait for the rolling database maintenance operation to complete.
// Then retry the operation.
/
/
/============================================================================
/ 16950 - 16999 Reserved for SQL Analyze
/
/ Begin messages for SQL Analyze errors
/============================================================================
/
16950, 00000, "Remote mapped cursors are not supported by this feature."
// *Cause: This cursor is a remote mapped cursor which could not be processed locally.
// *Action: Try to process this statement directly on the remote site.
16951, 00000, "Too many bind variables supplied for this SQL statement."
// *Cause: Binding this SQL statement failed because too many bind variables were supplied.
// *Action: Pass the correct number of bind variables.
16952, 00000, "Failed to bind this SQL statement."
// *Cause: Binding this SQL statement failed.
// *Action: Check if bind variables for that statement are properly specified.
16953, 00000, "Type of SQL statement not supported."
// *Cause: This type of SQL statement could not be processed.
// *Action:
16954, 00000, "SQL parse error."
// *Cause: The specified SQL statement failed to be parsed.
// *Action: Check if syntax is correct and ensure that this
// statement can be parsed by the specified user name.
16955, 00000, "Unknown error during SQL analyze."
// *Cause: The specified SQL statement failed to be analyzed.
// *Action: This is an internal error, please contact Oracle support.
16956, 00000, "Only SELECT or DML statements are supported for test execute."
// *Cause: The specified SQL statement cannot be tested for execute.
// *Action:
16957, 00000, "SQL Analyze time limit interrupt"
// *Cause: This is an internal error code used indicate that SQL analyze has
// reached its time limit.
// *Action:
16958, 00000, "DML statements running parallel are not supported for test execute."
// *Cause: The specified DML statement cannot be tested for execute because part of it is running parallel.
// *Action:
16959, 00000, "Statement type has been disabled for SQL Analyze"
// *Cause: The system attempted to analyze a type of statement that
// was disabled by the current feature.
// *Action: Try a different feature capable of analyzing this statement type.
16960, 00000, "SQL Analyze could not reproduce the desired plan."
// *Cause: SQL Analyze failed to reproduce a particular plan using an
// outline.
// *Action: Check the outline data.
16961, 00000, "SQL statement with SQL patch is ignored"
// *Cause: SQL statements with SQL patches are not supported by SQL tuning advisor.
// *Action: Check the SQL patch information. Rerun SQL repair advisor on
// that SQL statement for a potential better SQL patch.
/
16962, 00000, "SQL statement attempted to begin an autonomous transaction"
// *Cause: The SQL statement being analyzed attempted to begin an
// autonomous transaction, which is not supported.
// *Action: Analyze another statement or remove the autonomous transaction
// from the current statement.
16963, 00000, "The given user or schema is not supported by this feature."
// *Cause: The SQL statement being analyzed had a parsing user or schema
// which is not currently supported for SQL Analyze.
// *Action: Analyze another statement.
/
/
/ 17000 - 17499 Reserved for JDBC
/
/ 17500 - 18000 Reserved for I/O subsystem
/
17500, 00000, "ODM err:%s"
// *Cause: An error returned by ODM library
// *Action: Look at error message and take appropriate action or contact
// Oracle Support Services for further assistance
/
17501, 00000, "logical block size %s is invalid"
// *Cause: logical block size for oracle files must be a multiple of the
// physical block size, and less than the maximum
// *Action: check INIT.ORA file parameters
/
17502, 00000, "ksfdcre:%s Failed to create file %s"
// *Cause: file creation failed due to either insufficient OS permission or
// the file already exists
// *Action: check additional error messages
/
17503, 00000, "ksfdopn:%s Failed to open file %s"
// *Cause: file open failed due to either insufficient OS permission or
// the name of file exceeds maximum file name length.
// *Action: check additional error messages
/
17504, 00000, "ksfddel:Failed to delete file %s"
// *Cause: The file that was being deleted is still in use or the process
// has insufficient permission to delete file.
// *Action: check additional error messages
/
17505, 00000, "ksfdrsz:%s Failed to resize file to size %s blocks"
// *Cause: There is insufficient space left on the device or the process
// has insufficient permission to resize file.
// *Action: check additional error messages
/
17506, 00000, "I/O error simulation"
// *Cause: The I/O request was marked with an error because the I/O error
// simulation event was turned on.
// *Action:
/
17507, 00000, "I/O request size %s is not a multiple of logical block size."
// *Cause: I/O's were done in a multiple of the logical block size.
// *Action: Check additional error messages.
/
17508, 00000, "I/O request buffer pointer is not aligned."
// *Cause: I/O request buffer was not aligned. Check additional
// information for a buffer pointer value.
// *Action: Contact Oracle Support Services.
/
17509, 00000, "An attempt to do I/O beyond block1 offset."
// *Cause: When a file is identified with logical block size of 0, only I/O's
// to block1 is allowed.
// *Action: Check additional error messages and contact Oracle Support Services.
/
17510, 00000, "An attempt to do I/O of size %s to block %s is beyond file size %s. Logical block size: %s."
// *Cause: The I/O request pointed to a block beyond the end of the file.
// *Action: Check additional error messages and contact Oracle Support Services.
/
17511, 00000, "Event used internally for farm testing using RMAN seed database"
// *Document: NO
// *Cause: This event fixes db_name and file names in control file so that
// files restored from RMAN seed database works in another view.
// *Action:
/
17512, 00000, "Block Verification Failed"
// *Cause: Block Verification after a read operation on a database file
// failed since the block is media corrupt.
// *Action: check additional error messages in the trace file and call
// Oracle Support Services
/
17513, 00000, "dNFS package call failed"
// *Cause: An attempt was made to call a Direct NFS (dNFS) package in a
// non-dNFS environment.
// *Action: Ensure that dNFS is enabled and the file can be accessed using dNFS.
/
17514, 00000, "Access to clonedb bitmap file failed"
// *Cause: Accessing the bitmap block file in clonedb environment has
// encountered an error
// *Action: check additional error messages in the trace file and call
// Oracle Support Services
/
17515, 00000, "Creation of clonedb failed using snapshot file %s"
// *Cause: Creating a data file in a CloneDB environment failed.
// *Action: Ensure that the snapshot file passed to CloneDB is not from another
// CloneDB instance and call Oracle Support Services for further
// assistance.
/
17516, 00000, "dNFS asynchronous I/O failure"
// *Cause: The asynchronous I/O request failed due to storage server reboot.
// *Action: Ensure that the storage server does not reboot repeatedly during
// database operations.
/
17517, 00000, "Database cloning using storage snapshot failed on file %s:%s"
// *Cause: An invocation of the storage clone command was returned with an error.
// *Action: Ensure that all necessary steps are performed for storage cloning
// and check the Oracle trace file for additional information.
/
17518, 00000, "backup file %s cannot be found"
// *Cause: Access to the specified backup file was required for Instant Restore.
// *Action: Ensure that the path and file name are correct for the backup file
// and the path to the backup file can be accessed from the node of
// the instance.
/
17519, 00000, "Reason(%s): data file %s cannot be prepared"
// *Cause: The snapshot layer could not prepare the specified data file.
// *Action: Ensure that the file does not already exist, is already part of a
// clone setup, or is being repopulated by an Instant Restore
// background process. Ensure that the path specified is accessible
// and writable by the instance.
/
17520, 00000, "data file %s cannot be added to repopulation"
// *Cause: Instant Restore could not add the file to the repopulation work queue.
// *Action: The repopulation process may be working on too many files for the
// system. Try waiting for some files to complete and try again.
/
17521, 00000, "Instant Restore is not enabled"
// *Cause: The initialization parameters for Instant Restore were not set.
// *Action: Ensure that Instant Restore initialization parameters are set as
// required for this feature.
/
17522, 00000, "file %s is already being repopulated"
// *Cause: The file was already being repopulated from a previous restore.
// *Action: Ensure that the file completes restore before you start another
// restore.
/
17523, 00000, "Instance %d cannot spawn repopulation (RPOP) process"
// *Cause: The instance had too many running processes.
// *Action: Ensure that the maxmimum number of processes initialization
// parameter is set properly for this feature.
/
17524, 00000, "Repopulation cannot take place - no RPOP processes"
// *Cause: The maxmimum processes initialization parameter was not set
// properly.
// *Action: Ensure that the maxmimum number of processes initialization
// parameter is set properly for this feature. Check the alert log
// for other related errors.
17525, 00000, "Database clone using storage snapshot not supported on file %s"
// *Cause: Cloning a database using storage level snapshot is not supported
// on the underlying storage.
// *Action: Use storage product that has snapshot based cloning support
// for Oracle.
17526, 00000, "Block size of file %s is too small %s. Must be >= %s."
// *Cause: Files with block sizes smaller than a minimum size cannot be used
// for clones backed by snapshot file.
// *Action: Use files with larger block size.
17527, 00000, "Creation of a snapshot failed because the destination %s was not a sparse disk group."
// *Cause: Creating a snapshot failed because the destination disk group was not a sparse disk group.
// *Action: Ensure that the CREATE_FILE_DEST clause passed to the snapshot copy
// is in a sparse disk group.
17528, 00000, "A read-only file or a file opened read-only cannot be written to: %s."
// *Cause: The file was read-only or was opened read-only and an attempt was
// made to write to the file, or there was an internal error.
// *Action: If the file is a parent of a snapshot, then you cannot open
// read/write, drop or unplug the database. Otherwise, look at the trace
// file and contact Oracle Support Services.
/
17529, 00000, "creation of compressed file failed"
// *Cause: An attempt was made to create a compressed file on an instance
// that was not a CloneDB instance.
// *Action: Set CLONEDB parameter to TRUE and retry the operation.
/
17530, 00000, "snapshot (parent), %s, modified after clone (child) created, %s"
// *Cause: The snapshot referred to by the clone was incompatible with what the
// clone was created.
// *Action: Locate the appropriate snapshot and place it in the named
// location.
/
17531, 00000, "snapshot (parent)=%s modification time %s is different from snapshot creation time %s recorded in file %s"
// *Cause: The clone (child) referred to a snapshot at a specific point in
// time. The snapshot (parent) currently in that place is at the
// wrong time.
// *Action: Locate the appropriate snapshot (parent) and place it in the named
// location.
/
17532, 00000, "snapshot (parent)=%s checkpoint SCN %s is different from snapshot checkpoint SCN %s recorded in file %s"
// *Cause: The clone (child) referred to an SCN at a specific point in time.
// The snapshot (parent) currently in that place is at the wrong SCN.
// *Action: Locate the appropriate snapshot (parent) and place it in the named
// location.
/
17533, 00000, "sparse merge copy operation failure because %s and %s do not share a valid relationship"
// *Cause: Files specified with the 'sparse_merge_begin' and 'sparse_merge_end' options
// did not share a valid relationship.
// *Action: Check additional error messages.
/
17534, 00000, "sparse merge copy operation failure because request to change file access permissions for file %s failed"
// *Cause: File access permissions for the file could not be modified.
// *Action: Check additional error messages.
/
17535, 00000, "sparse merge copy operation failure because it tried to merge to the base parent %s"
// *Cause: The sparse merge copy operation was not successful because it tried to merge to the base parent.
// *Action: Check additional error messages.
/
17610, 00000, "file '%s' does not exist and no size specified"
// *Cause: An attempt to create a file found neither an existing file
// nor a size for creating the file.
// *Action: Specify a size for the file.
/
17611, 00000, "ksfd: file '%s' cannot be accessed, global open closed"
// *Cause: An attempt to write to a file which has gone offline/unidentified
// *Action: Check for other errno in the stack
/
17612, 00000, "Failed to discover Oracle Disk Manager library, return value %s"
// *Cause: Discovery of the odm library by calling odm_discover() failed
// *Action: Contact your storage vendor who has provided the ODM
// library or call Oracle Support
/
17613, 00000, "Failed to initialize Oracle Disk Manager library: %s"
// *Cause: Initialization of the Oracle Disk Manager (ODM) for the thread
// failed due to insufficient privilege or memory.
// *Action: Ensure that there is enough system resources available for the
// Oracle process and that it has access to the ODM library.
17614, 00000, "Event to cause disk subsystem to require pre-allocation"
// *Document: NO
// *Cause:
// *Action:
17615, 00000, "Event to disable pre-allocation algorithm during backup"
// *Document: NO
// *Cause:
// *Action:
17616, 00000, "Event to disable pupulating V$RMAN_STATUS"
// *Document: NO
// *Cause: This event disables the dbsm_backup_restore functions
// createRmanStatusRow, updateRmanStatusRow, and commitRmanStatusRow
// (the functions will be no op).
// In order to limit size of rows in V$RMAN_STATUS and to delete the
// entire V$RMAN_STATUS use the named event KRBMRSR_LIMIT. If the
// level of that event is 1, then size of the V$RMAN_STATUS view
// will be zero so the above functions will signal ORA-19901. If the
// level is bigger than 1, then it sets the maximum number of rows in
// the V$RMAN_STATUS fixed view.
// *Action:
17617, 00000, "Event to disable populating V$RMAN_OUTPUT"
// *Document: NO
// *Cause: This event disables the dbsm_backup_restore function
// createRmanOutputRow (the function will be no op).
// In order to limit size of rows in V$RMAN_OUTPUT and to delete the
// entire V$RMAN_OUTPUT, use the named event KRBMROR_LIMIT. If the
// level of that event is 1, then size of the V$RMAN_OUTPUT view will
// be zero, so the function createRmanOutputRow will signal ORA-19901.
// If the level is bigger than 1, then level*256 is maximum number of
// the rows in the V$RMAN_OUTPUT fixed view.
// *Action:
/
17618, 00000, "Unable to update block 0 to version 10 format"
// *Cause: An attempt was made to update block 0 to version 10 format.
// *Action: Check additional error messages and call Oracle Support Services
17619, 00000, "max number of processes using I/O slaves in a instance reached"
// *Cause: An attempt was made to start large number of processes
// requiring I/O slaves.
// *Action: There can be a maximum of 35 processes that can have I/O
// slaves at any given time in a instance.
/
17620, 00000, "failed to register the network adapter with Oracle Disk Manager library: %s"
// *Cause: The Oracle Disk Manager (ODM) library returned an error while
// trying to register the network adapter.
// *Action: Ensure that the network adapter name specified in the
// FILEIO_NETWORK_ADAPTERS initialization parameter is a valid name,
// and that the Oracle user has the correct access privileges.
17621, 00000, "failed to register the memory with Oracle Disk Manager library"
// *Cause: The ODM library returned an error while trying to register the
// memory.
// *Action: Contact the Oracle Disk Manager Library provider.
/
17622, 00000, "failed to deregister the memory with Oracle Disk Manager library"
// *Cause: The ODM library returned an error while trying to deregister the
// memory.
// *Action: Contact the Oracle Disk Manager Library provider
17623, 00000, "Event to enable compression debugs in backup and restore"
// *Document: NO
// *Cause:
// *Action:
17624, 00000, "Failed to delete directory %s"
// *Cause: The directory that was being deleted is still in use or the process
// had insufficient permission to delete the directory.
// *Action: check additional error messages.
17625, 00000, "Event to test delete directory"
// *Document: NO
// *Cause: For internal use only.
// *Action:
17626, 00000, "ksfdcre: %s file exists"
// *Cause: trying to create a database file, but file by that name already
// exists
// *Action: verify that name is correct, specify REUSE if necessary
17627, 00000, "%s"
// *Cause: An error returned by OCI while sending/receiving message from
// remote instance
// *Action: Look at error message and take appropriate action or contact
// Oracle Support Services for further assistance
17628, 00000, "Oracle error %s returned by remote Oracle server"
// *Cause: Oracle server on the remote instance has returned an error.
// *Action: Look at remote instance alert log/trace file for more information
// and take appropriate action or contact Oracle Support Services
// for further assistance
17629, 00000, "Cannot connect to the remote database server"
// *Cause: Connecting to the remote server specified by database connect
// string for netowrk file transfer failed.
// *Action: Check additional error messages
17630, 00000, "Mismatch in the remote file protocol version client %s server %s"
// *Cause: Cannot communicate with the remote database server as
// there is a mismatch in the Oracle file protocol version.
// *Action: Check additional error messages
17631, 00000, "dbname '%s' specified by remote server does not match the instance name '%s'"
// *Cause: The dbname specified by the remote server is not intended
// for this instance.
// *Action: Check the dbname specified in the command of the remote instance
// and look for further error messages.
17632, 0000, "file '%s' is a formatted ASM disk"
// *Cause: An attempt to create a datafile on a device that was formatted
// for ASM disk failed.
// *Action: Check that the device specified is not an ASM disk. If you would
// like to use the disk for datafiles, please clear the disk before
// you retry the operation.
17633, 0000, "Operation not supported as one of the servers involved is not capable of performing the requested operation"
// *Cause: An attempt was made to perform an operation involving
// two Oracle servers where both servers did not have
// the capability required for carrying out the operation.
// It is likely that one of the servers needs a patch or an
// upgrade to successfully participate in the operation.
// *Action: Apply the required fix or update on the lower version
// server. Contact Oracle Support Services for further
// assistance.
17634, 0000, "network file transfer operation aborted"
// *Cause: An error occurred during network file transfer operation.
// *Action: Check addtional error messages.
17635, 0000, "failure in obtaining physical sector size for '%s'"
// *Cause: An error occurred while determining the physical sector size
// from the underlying storage (ASM/ODM/OSD).
// *Action: Check additional error messages.
17636, 0000, "Invalid sparse block format (%s). Start block=%s. Error=%s. File=%s"
// *Cause: An error occurred while reading the block on sparse media.
// *Action: Contact Oracle Support Services.
/
17637, 0000, "failed to change permission on file '%s'"
// *Cause: An error occurred while changing permission on a database file.
// *Action: Verify that Oracle user has ownership on the database file.
/
17638, 0000, "Error in accessing a compressed file %s. '%s'."
// *Cause: An error occurred while accessing a compressed file.
// *Action: Verify that the Oracle user has permission to access the
// compressed file.
/
17639, 0000, "Snapshot backing file not read-only '%s'."
// *Cause: An error occurred while opening the snapshot backing file.
// *Action: Verify that the backing file has not changed since the creation
// of the snapshot file and set the backing file permissions to
// read-only.
/
17640, 00000, "SQL statement execution failed"
// *Cause: The remote SQL statement execution failed on primary database.
// *Action: Check for the required privileges to run the SQL statement.
/
17641, 00000, "event to release BCT enqueue on Oracle RAC environment with internal error"
// *Cause: An attempt was made to release the enqueue after getting an
// internal error "krcrfr_nohist". This happens if any bitmap is not keeping in
// with its oldest_low_krcfde on Oracle RAC environment with block change
// tracking (BCT) enabled.
// *Action: None.
/
17642, 0000, "failed to get permission on file '%s'"
// *Cause: An error occurred while getting permission on a database file.
// *Action: Verify that the database file exists.
/
17643, 0000, "error while creating or opening destination file '%s'"
// *Cause: The destination file or the path provided already existed or could
// not be accessed.
// *Action: If the destination file exists, delete the file and retry.
// Alternately, try with a different destination filename or provide a
// different path.
/
17644, 00000, "clonedb_renamefile interface is not supported in a multitenant container database."
// *Cause: An attempt was made to clone a file using clonedb_renamefile interface
// in a multitenant container database (CDB).
// *Action: Use the snapshot copy option while creating the pluggable database.
/
/ 17675-18000 Reserved for OFS
/
17675, 00000, "execution of OFS procedure failed with error:'%s'"
// *Cause: Either the procedure was called on a platform where Oracle File
// System (OFS) is not supported or an invalid file system type
// was provided.
// *Action: Check additional error messages in the trace file.
/
17676, 00000, "Failed to mount '%s' with error:'%s'"
// *Cause: Mounting database file system failed with an error.
// *Action: Check additional error messages in the trace file.
/
17677, 00000, "failed to unmount '%s' with error:'%s'"
// *Cause: Unmounting database file system failed with an error.
// *Action: Check additional error messages in the trace file.
/
17678, 00000, "failed to mount '%s' with error:'%s'"
// *Cause: Mounting of the database file system failed with an error.
// *Action: Check additional error messages in the trace file.
/
17679, 00000, "failed to makefs '%s' with error:'%s'"
// *Cause: Either an invalid file system creation option was specified, the
// file system already existed, or a failure to create the tables occurred.
// *Action: Check additional error messages in the trace file.
/
17680, 00000, "failed to destroy database file system '%s' with error:'%s'"
// *Cause: Either the database file system was invalid, it was still busy,
// it did not exist, or some other error has occurred.
// *Action: Check additional error messages in the trace file.
17681, 00000, "cannot connect to the remote database server"
// *Cause: An attempt was made to connect to the remote server using a shared
// server connection. This is not supported.
// *Action: Verify the connect string and use a dedicated server to connect to
// remote database.
/
/ 18000 - 18099 Reserved for PLAN STABILITY
/
18000, 00000, "invalid outline name"
// *Cause: The parser detected a missing or invalid outline name
// *Action:
18001, 00000, "no options specified for ALTER OUTLINE"
// *Cause: The parser detected that no clause was specified on the command
// Our performance tests, which are not typical as they exercise all
// branches of the code, have shown approximately a 30% performance
// increase line for ALTER OUTLINE.
// *Action: Re-issue the command, specifying a valid ALTER OUTLINE clause.
18002, 00000, "the specified outline does not exist"
// *Cause: Either the outline did not exist to begin with, or a timing window
// allowed for another thread to drop or alter the outline midstream.
// *Action:
18003, 00000, "an outline already exists with this signature"
// *Cause: The signature generation algorithm generates signatures that are
// are 16 bytes in length so it is highly unlikely that any 2
// signatures will be identical. This message is raised in such a
// rare case.
// *Action: Either re-issue the statement that led to the outline being created
// with some whitespace added or force the outline to be created in a
// different category.
18004, 00000, "outline already exists"
// *Cause: An outline already exists, either with the specified name, or for
// the specified SQL text.
// *Action:
18005, 00000, "CREATE ANY OUTLINE privilege is required for this operation"
// *Cause:
// *Action:
18006, 00000, "DROP ANY OUTLINE privilege is required for this operation"
// *Cause:
// *Action:
18007, 00000, "ALTER ANY OUTLINE privilege is required for this operation"
// *Cause:
// *Action:
18008, 00000, "cannot find OUTLN schema"
// *Cause: The database creation script that creates this schema must not
// have been executed.
// *Action: Review the log files to see what happened when the database
// was created.
18009, 00000, "one or more outline system tables do not exist"
// *Cause: Either the database creation script that creates these tables
// was not executed or a user accidently deleted the table
// *Action: Review the log files to see what happened when the database
// was created.
18010, 00000, "command missing mandatory CATEGORY keyword"
// *Cause: User failed to specify the CATEGORY keyword
// *Action: Re-issue the command with the CATEGORY keyword included
18011, 00000, "the outline specified in the FROM clause does not exist"
// *Cause:
// *Action:
18012, 00000, "select_catalog_role role is required for this operation"
// *Cause:
// *Action:
18013, 00000, "timed out while waiting for resource %s"
// *Cause:
// *Action:
18014, 00000, "deadlock detected while waiting for resource %s"
// *Cause:
// *Action:
18015, 00000, "invalid source outline signature"
// *Cause: User imported an 8i outline into a 9i database without updating signatures
// *Action: execute dbms_outln.update_signatures
/
/============================================================================
/ 18100 - 18199 Reserved for XMLQuery Update errors
/
/ Begin messages for XQuery Update errors
/============================================================================
/
18100, 00000, "XUST0001 - Updating expression in a wrong position"
// *Cause: An updating expression was used in a position other than one of
// the following:
// - The topmost expression in the body of a query.
// - The MODIFY clause of a TRANSFORM expression.
// - The RETURN clause of a FLWOR expression.
// - The RETURN clauses of a TYPESWITCH expression in which every
// RETURN clause contains an updating expression, an empty
// expression ( ), or a call to the fn:error function.
// - The THEN and ELSE clauses of a conditional statement in which
// both the then and else clauses contain either an updating
// expression, an empty expression ( ), or a call to
// the fn:error function.
// - An operand of a comma expression in which each operand is
// either an updating expression, an empty expression ( ), or
// a call to the fn:error function.
// - The content of a parenthesized expression.
// - The body of a function declaration in which the keyword
// UPDATING is specified.
// *Action: None.
/
18101, 00000, "XUST0002 - Non-updating expression in a wrong position"
// *Cause: A non-updating expression other than an empty expression ( ) or a
// call to the fn:error function was used in one of the following
// positions:
// - The MODIFY clause of a TRANSFORM expression.
// - The top-level expression in the body of a function
// declaration in which the keyword UPDATING is specified.
// *Action: None.
/
18102, 00000, "XUST0003 - Repeated revalidation declaration"
// *Cause: Prolog contained more than one revalidation declaration.
// *Action: None.
/
18103, 00000, "XUTY0004 - Invalid attribute node in the insertion sequence"
// *Cause: The insertion sequence of an INSERT expression contained an
// attribute following a node that was not an attribute node.
// *Action: None.
/
18104, 00000, "XUTY0005 - Invalid target expression for INSERT"
// *Cause: In an INSERT expression where INTO, AS FIRST INTO, or AS LAST INTO
// was specified, the target expression returned a nonempty result
// that did not consist of a single element or document node.
// *Action: None.
/
18105, 00000, "XUTY0006 - Invalid target expression for INSERT"
// *Cause: In an INSERT expression where BEFORE or AFTER was specified, the
// target expression returned a nonempty result that did not consist
// element, text, comment, or processing instruction node.
// *Action: None.
/
18106, 00000, "XUTY0007 - Invalid target expression for DELETE"
// *Cause: The target expression of a DELETE expression did not return a
// sequence of zero or more nodes.
// *Action: None.
/
18107, 00000, "XUTY0008 - Invalid target expression for REPLACE"
// *Cause: In a REPLACE expression, the target expression returned a nonempty
// result that did not consist of a single element, attribute, text,
// comment, or processing instruction node.
// *Action: None.
/
18108, 00000, "XUDY0009 - Invalid target expression for REPLACE"
// *Cause: In a REPLACE expression where VALUE OF was not specified, the node
// returned by the target expression did not have a parent.
// *Action: None.
/
18109, 00000, "XUTY0010 - Invalid replacement sequence for REPLACE"
// *Cause: In a REPLACE expression where VALUE OF was not specified and
// the target was an element, text, comment, or processing instruction
// node, the replacement sequence did not consist of zero or more
// element, text, comment, or processing instruction nodes.
// *Action: None.
/
18110, 00000, "XUTY0011 - Invalid replacement sequence for REPLACE"
// *Cause: In a REPLACE expression where VALUE OF was not specified and
// the target is an attribute node, the replacement sequence did not
// consist of zero or more attribute nodes.
// *Action: None.
/
18111, 00000, "XUTY0012 - Invalid target expression for RENAME"
// *Cause: In a RENAME expression, the target expression returned a nonempty
// result that did not consist of a single element, attribute, or
// processing instruction node.
// *Action: None.
/
18112, 00000, "XUTY0013 - Invalid COPY expression for TRANSFORM"
// *Cause: In a TRANSFORM expression, a source expression in the copy clause
// did not return a single node.
// *Action: None.
/
18113, 00000, "XUDY0014 - Modified node was not created by the COPY clause"
// *Cause: In a TRANSFORM expression, the MODIFY clause modified a node that
// was not created by the COPY clause.
// *Action: None.
/
18114, 00000, "XUDY0015 - Duplicate RENAME for the same target node"
// *Cause: A node was the target of more than one RENAME expression within
// the same query.
// *Action: None.
/
18115, 00000, "XUDY0016 - Duplicate REPLACE for the same target node"
// *Cause: A node was the target of more than one REPLACE expression (without
// VALUE OF being specified) within the same query.
// *Action: None.
/
18116, 00000, "XUDY0017 - Duplicate REPLACE for the same target node"
// *Cause: A node was the target of more than one REPLACE VALUE OF expression
// within the same query.
// *Action: None.
/
18117, 00000, "XUDY0018 - External not updating function returns an updated value"
// *Cause: A function that was declared to be external but not updating
// returned a nonempty pending update list.
// *Action: None.
/
18118, 00000, "XUDY0019 - External updating function returns an invalid value"
// *Cause: A function that was declared to be both external and updating
// returned a nonempty data model instance.
// *Action: None.
/
18119, 00000, "XUDY0020 - Deleted node has no parent"
// *Cause: Node was deleted that had no parent before execution of the query
// began.
// *Action: None.
/
18120, 00000, "XUDY0021 - The result XDM instance violates XDM constraints"
// *Cause: XDM instance resulting from applying all the updates in a query
// violated constraint specified in [XQuery/XPath Data Model (XDM)].
// In this case, none of the updates in the query were made effective.
// *Action: None.
/
18121, 00000, "XUTY0022 - Invalid attribute insertion into a document node"
// *Cause: INSERT expression specified the insertion of an attribute node into
// a document node.
// *Action: None.
/
18122, 00000, "XUDY0023 - Updating expression introduces a namespace conflict"
// *Cause: An INSERT, REPLACE, or RENAME expression affected an element node
// by introducing a new namespace binding that conflicted with one of
// its existing namespace bindings.
// *Action: None.
/
18123, 00000, "XUDY0024 - Updating expression introduces a namespace conflict"
// *Cause: Effect of a set of updating expressions introduced conflicting
// namespace bindings into an element node.
// *Action: None.
/
18124, 00000, "XUDY0025 - Invalid QName for processing instruction RENAME"
// *Cause: Target of a RENAME expression was a processing instruction node,
// and the new name expression returned a QName with a nonempty
// namespace prefix.
// *Action: None.
/
18125, 00000, "XUST0026 Revalidation mode %s is not supported"
// *Cause: Revalidation declaration in a Prolog specified a revalidation mode
// that is not supported by the current implementation.
// *Action: None.
/
18126, 00000, "XUDY0027 - Invalid target expression"
// *Cause: Target expression of an INSERT, REPLACE, or RENAME expression
// evaluated to an empty sequence.
// *Action: None.
/
18127, 00000, "XUST0028 - Updating function should not have a return type"
// *Cause: Function declaration specified both UPDATING and a return type.
// *Action: None.
/
18128, 00000, "XUDY0029 - INSERT expression target node doesn't have a parent"
// *Cause: In an INSERT expression where BEFORE or AFTER was specified,
// a node returned by the target expression did not have a parent.
// *Action: None.
/
18129, 00000, "XUDY0030 - Invalid insertion of an attribute node"
// *Cause: INSERT expression specified the insertion of an attribute node
// before or after a child of a document node.
// *Action: None.
/
18130, 00000, "FOUP0001 - Invalid 'fn:put' first operand"
// *Cause: The first operand of fn:put was not a node of a supported kind.
// *Action: None.
/
18131, 00000, "FOUP0002 - Invalid 'fn:put' second operand"
// *Cause: The second operand of fn:put was not a valid lexical representation
// of the xs:anyURI type.
// *Action: None.
/
/============================================================================
/ 18150 - 18199 RDBMS specific XQuery Update errors
/============================================================================
/
18150, 00000, "SQL input value cannot be modified in updating expression"
// *Cause: Updating expression was specified as top-level XMLQuery expression.
// *Action: Use XQuery TRANSFORM expression to copy input value and modify it.
/
/============================================================================
/ 18160 - 18199 RDBMS specific XQuery FullText errors
/============================================================================
/
18160, 0000, "FTST0001 - FTMildNot operator not supported"
// *Cause: An attempt was made to use the mild not option when the FTMildNot operator was not supported. An implementation that does not support the FTMildNot operator must raise a static error if a full-text query contains a mild not.
// *Action: Do not use the FTMildNot full-text query operator.
/
18161, 0000, "FTST0002 - FTUnaryNot operator not supported"
// *Cause: An implementation that enforces one of the restrictions on FTUnaryNot must raise a static error if a full-text query does not obey the restriction.
// *Action: Do not use the FTUnaryNot full-text query operator.
/
18162, 0000, "FTST0003 - FTUnit and FTBigUnit not supported"
// *Cause: An implementation that does not support one or more of the choices on FTUnit and FTBigUnit must raise a static error if a full-text query contains one of those choices.
// *Action: Do not use the FTUnit or FTBigUnit option.
/
18163, 0000, "FTST0004 - FTScope not supported"
// *Cause: An implementation that does not support the FTScope operator must raise a static error if a full-text query contains a scope.
// *Action: Do not use the FTScope full-text query operator.
/
18164, 0000, "FTST0005 FTTimes not supported"
// *Cause: An implementation that does not support the FTTimes operator must raise a static error if a full-text query contains a times.
// *Action: Do not use the FTTimes full-text query operator.
/
18165, 0000, "FTST0006 FTStopwordOption not supported"
// *Cause: An implementation that restricts the use of FTStopwordOption must raise a static error if a full-text query contains a stop word option that does not meet the restriction.
// *Action: Do not use the FTStopwordOption full-text query operator.
/
18166, 0000, "FTST0007 FTIgnoreOption not supported"
// *Cause: An implementation that restricts the use of FTIgnoreOption must raise a static error if a full-text query contains an ignore option that does not meet the restriction.
// *Action: Do not use the FTIgnoreOption full-text query operator.
/
18167, 0000, "FTST0008 stop word list not found"
// *Cause: It was a static error if, during the static analysis phase, the query was found to contain a stop word option that referred to a stop word list that was not found in the statically known stop word lists.
// *Action: Ensure that the stop word list exists.
/
18168, 0000, "FTST0009 language option not supported"
// *Cause: It may be a static error if, during the static analysis phase, the query is found to contain a language identifier in a language option that the implementation does not support. The implementation may choose not to raise this error and instead provide some other implementation-defined behavior.
// *Action: Do not use the language full-text query option.
/
18169, 0000, "FTST0010 FTOrder not succeeding FTWindow or FTDistance operator"
// *Cause: It is a static error if, during the static analysis phase, an expression is found to use an FTOrder operator that does not appear directly succeeding an FTWindow or an FTDistance operator and the implementation enforces this restriction.
// *Action: Do not use the FTOrder succeeding FTWindow or FTDistance full-text query operator.
/
18170, 0000, "FTST0011 FTWindow and FTDistance restriction"
// *Cause: An implementation may restrict the use of FTWindow and FTDistance to an FTOr that is either a single FTWords or a combination of FTWords involving only the operators && and ||. If it a static error if, during the static analysis phase, an expression is found that violates this restriction and the implementation enforces this restriction.
// *Action: Follow FTWindow and FTDistance restriction.
/
18171, 0000, "FTST0012 FTContent not supported"
// *Cause: An implementation that does not support the FTContent operator must raise a static error if a full-text query contains one.
// *Action: Do not use FTContent full-text query operator.
/
18172, 0000, "FTST0013 more than one language encountered"
// *Cause: It is a static error if, during the static analysis phase, an implementation that restricts the use of FTLanguageOption to a single language, encounters more than one distinct language option.
// *Action: Do not use more than one language in FTLanguag full-text option.
/
18173, 0000, "FTST0014 score computation restriction"
// *Cause: An implementation may constrain the form of the expression used to compute scores. It is a static error if, during the static analysis phase, such an implementation encounters a scoring expression that does not meet the restriction.
// *Action:
/
18174, 0000, "FTST0015 FTCaseOption restriction"
// *Cause: It is a static error if, during the static analysis phase, an implementation that restricts the choices of FTCaseOption encounters the "lowercase" or "uppercase" option.
// *Action:
/
18175, 0000, "FTDY0016 weights invalid"
// *Cause: It is a dynamic error if an implementation that does not support negative weights encounters a weight expression that does not meet the restriction.
// *Action: Do not use invalid weights value.
/
18176, 0000, "FTDY0017 mild not selection containings StringExclude"
// *Cause: It is a dynamic error if an implementation encounters a mild not selection, one of whose operands evaluates to an AllMatches that contains a StringExclude
// *Action:
/
18177, 0000, "XQuery full text expression '%s' cannot be evaluated using XML full-text index"
// *Cause: There was no XML full-text index to evaluate the XQuery full text expression filtering XML documents that were stored in an XMLType table or column.
// *Action: Create an XML full-text index on the XML documents stored in an XMLType table or column and ensure that the XQuery full text expression can be evaluated by an XML full-text index.
/
18178, 0000, "XMLType input to XMLTABLE row expression needs to use PASSING BY REF clause"
// *Cause: The XMLTABLE column expression used the XMLTYPE(SEQUENCE) BY REF clause which requires XMLType input to the XMLTABLE row expression to use the PASSING BY REF clause.
// *Action: Specify the PASSING BY REF clause for XMLType input to the XMLTABLE row expression.
/
18179, 0000, "XMLTABLE column expression needs to be specified using XMLTYPE(SEQUENCE) BY REF clause"
// *Cause: Output of the XMLTABLE column expression was passed to an XMLTABLE row expression with PASSING BY REF clause.
// *Action: Specify the XMLTABLE column expression using XMLTYPE(SEQUENCE) BY REF clause.
/
18180, 0000, "wrong argument is passed to XMLTABLE row expression using PASSING BY REF clause"
// *Cause: An XML document that was not stored in an XMLType table or column was passed to an XMLTABLE row expression using the PASSING BY REF clause.
// *Action: Ensure that only XML documents that are stored in an XMLType table or column can be passed in as input to XMLTABLE row expression using the PASSING BY REF clause.
/
18181, 0000, "XQuery full text expression option '%s' is not supported"
// *Cause: An attempt was made to use an XQuery full text expression option that is not supported.
// *Action: Avoid using an XQuery full text expression option which is not supported.
/
18182, 0000, "FTST0018 unknown thesaurus is used"
// *Cause: During the static analysis phase, the query was found to contain a thesaurus option that referred to a thesaurus that was not found in the statically known thesauri. This is a static error.
// *Action: Avoid using unknown thesaurus.
/
18183, 0000, "FTST0019 more than one match option of any given match option group is used within a single FTMatchOptions."
// *Cause: Within the single FTMatchOptions, there was more than one match option of any given match option group. This is a static error.
// *Action: Avoid using more than one match option of any given match option group is used within a single FTMatchOptions.
/
18184, 0000, "FTDY0020 a query string violates wildcard syntax when wildcards is in effect"
// *Cause: Because wildcards were in effect, the query string violated wildcard syntax. This is a dynamic error.
// *Action: Fix wildcard syntax when wildcards is in effect.
18185, 0000, "query is not parsed correctly"
// *Cause: The query string was not parsed correctly.
// *Action: Check the syntax of the query string.
/
/============================================================================
/
/ 18200 - 18699 Reserved for Analytic View Sql (HCS) error messages
/
/============================================================================
/
/// 18200 - 18219 reserved for MDX Parser
/
18201, 00000, "The input MDX string is empty."
// *Cause: The input MDX (MultiDimensional eXpression) string was empty.
// *Action: Correct the input MDX (MultiDimensional eXpression) string.
/
18202, 00000, "MDX parser error at line %s, column %s: %s."
// *Cause: The input MDX (MultiDimensional eXpression) query had invalid syntax.
// *Action: Correct the syntax error for the MDX (MultiDimensional eXpression) query.
/
18203, 00000, "The MDX %s %s is not currently supported."
// *Cause: The input MDX (MultiDimensional eXpression) query contained an unsupported feature.
// *Action: Modify the MDX (MultiDimensional eXpression) query to use only supported features.
/
18204, 00000, "The identifier at line %s, column %s has no closing right bracket (]) character."
// *Cause: The delimited identifier had no closing right bracket (]) character.
// *Action: Correct the syntax error for the MDX (MultiDimensional eXpression) query.
/
18205, 00000, "Invalid arguments for function %s."
// *Cause: The function had invalid arguments.
// *Action: Correct the syntax error for the MDX (MultiDimensional eXpression) query.
/
/// 18220 - 18249 reserved for MDX Semantic Analysis
/
18220, 00000, "The type of the expression in %s is %s. %s is expected."
// *Cause: The MDX (MultiDimensional eXpression) query had the wrong type.
// *Action: Use an expression with a valid type.
/
18221, 00000, "The argument %s in %s has different hierarchies."
// *Cause: An argument had different hierarchies.
// *Action: Use uniform hierarchies.
/
18222, 00000, "Hierarchy %s already appears in %s."
// *Cause: A hierarchy was repeated.
// *Action: Use disjoint hierarchies.
/
18223, 00000, "Invalid identifier for dimension \"%s\"."
// *Cause: More than one hierarchy existed for dimension.
// *Action: Specify the hierarchy with the dimension.
/
18224, 00000, "invalid cube identifier \"%s\""
// *Cause: The cube identifier was specified incorrectly.
// *Action: Specify a valid cube identifier.
/
18225, 00000, "The type of argument %s of %s is %s. %s is expected."
// *Cause: An argument of the function had the wrong type.
// *Action: Use an argument with a valid type.
/
18226, 00000, "argument %s does not contain the hierarchy \"%s\" in argument %s in %s"
// *Cause: The hierarchy in one argument did not exist in the SET argument.
// *Action: Use an expression with the hierarchy from the set in the SET argument.
/
18227, 00000, "The index is out of range in %s."
// *Cause: The index was out of range.
// *Action: Use an index within the range.
/
/
18228, 00000, "The set of argument %s of %s contains multiple hierarchies. Only one hierarchy is expected."
// *Cause: The set argument had more than one hierarchy.
// *Action: Use a SET argument that contains only one hierarchy.
/
18229, 00000, "The hierarchy %s is used more than once in arguments of %s."
// *Cause: The hierarchy was used more than once.
// *Action: Use arguments that contain different hierarchies.
/
18230, 00000, "The member identifier \"%s\" cannot be resolved."
// *Cause: The member identifier could not be resolved.
// *Action: Use a valid member identifier.
/
18231, 00000, "The StrToMember argument must be a member identifier when CONSTRAINED is specified."
// *Cause: The StrToMember argument was not a member identifier and CONSTRAINED was specified.
// *Action: Replace the argument with a member identifier or remove the CONSTRAINED option.
/
18232, 00000, "A set with the name \"%s\" has already been defined."
// *Cause: More than one set was defined with the same name.
// *Action: Rename the set so that it has a unique name within the WITH clause of the multidimensional expression (MDX) query.
/
18233, 00000, "The set \"%s\" has a cycle."
// *Cause: The set definition referenced itself either directly or indirectly using another referenced set.
// *Action: Change the definition of the set so that it does not directly or indirectly refer to itself.
/
18234, 00000, "The calculated member \"%s\" has the same name as an existing member."
// *Cause: The name specified for the calculated member identified another member in the hierarchy.
// *Action: Change the name of the calculated member so that it is unique within the specified hierarchy.
/
18235, 00000, "The calculated member \"%s\" must be a member identifier qualified by hierarchy."
// *Cause: The calculated member identifier either was not a valid member identifier or does not contain a hierarchy qualification.
// *Action: Change the calculated member identifier so that it is a valid member identifier qualifying the hierarchy.
/
18236, 00000, "The calculated member \"%s\" has a cycle."
// *Cause: The calculated member referenced itself either directly or indirectly using another referenced calculated member.
// *Action: Change the definition of the calculated member so that it does not directly or indirectly refer to itself.
/
18237, 00000, "A calculated member with the name \"%s\" has already been defined."
// *Cause: More than one calculated member was defined with the same name.
// *Action: Rename the calculated member so that it has a unique name within the WITH clause of the multidimensional expression (MDX) query.
/
/// 18250 - 18279 reserved for MDX PL/SQL Functions
/
18250, 00000, "The input parameter to the MDX PL/SQL function is invalid."
// *Cause: The input parameter to the PL/SQL function was invalid.
// *Action: Correct the input parameter to the PL/SQL function.
/
/
18252, 00000, "There are no active MDX queries."
// *Cause: Either an MDX (MultiDimensional eXpression) query was not executed or all executed queries were closed.
// *Action: Execute an MDX (MultiDimensional eXpression) query.
/
18253, 00000, "invalid queryID: %s"
// *Cause: The MDX (MultiDimensional eXpression) query did not exist in the session with the given queryID.
// *Action: Specify a valid queryID obtained by calling dbms_mdx_odbo.execute.
/
18254, 00000, "invalid cellRange size: %s given, %s expected"
// *Cause: The size of the cellRange sequence was not 2 times the number of axes.
// *Action: Specify a cellRange that has the correct number of elements.
/
18255, 00000, "Invalid cellRange: start (%s) is greater than end (%s) for axis %s"
// *Cause: The start was greater than end for a particular axis in the cellRange.
// *Action: Specify start less than or equal to end for each axis in the cellRange.
/
18256, 00000, "Invalid axisIndex: %s"
// *Cause: The axisIndex was out of range.
// *Action: Specify an axisIndex greater than or equal to 0 and less than the number of axes.
/
18257, 00000, "The classification value for \"%s\" for measure \"%s\" is invalid for MDX."
// *Cause: The classification value was invalid for MultiDimensional eXpression.
// *Action: Replace the Classification value.
/
18258, 00000, "The MDX Slicer contains more than one row."
// *Cause: The set defining the Slicer resulted in more than one row.
// *Action: Correct the Slicer portion of the MultiDimensional eXpression query.
/
18259, 00000, "The MDX Schema Rowset type request is invalid."
// *Cause: The MDX (MultiDimensional eXpression) Schema Rowset type was not a valid value.
// *Action: Valid MDX (MultiDimensional eXpression) schema Rowset types are between 1 and 10.
/
18260, 00000, "The MDX Schema Rowset Restrictions array and Empty array are not the same size."
// *Cause: The MultiDimensional eXpression Schema Rowset Restrictions array and the Empty array were not the same size.
// *Action: Correct the sizes of the Restriction and Empty arrays.
/
18261, 00000, "The TREE_OP restriction value is invalid."
// *Cause: The given TREE_OP restriction value was invalid.
// *Action: Provide a valid TREE_OP restriction value.
/
18262, 00000, "invalid empty value"
// *Cause: A value in the given empty list was invalid.
// *Action: Provide a valid empty value.
/
18263, 00000, "invalid object name and log number combination"
// *Cause: The object name and log number combination did not match the value returned by DBMS_HIERARCHY.VALIDATE_HIERARCHY or VALIDATE_CUBE.
// *Action: Provide a valid combination of object name and log number and reexecute.
/
/
18264, 00000, "The 'queryProperties' sequence has an invalid length."
// *Cause: The 'queryProperties' sequence had an odd number of elements.
// *Action: Ensure that the 'queryProperties' sequence is either empty or contains an even number of elements.
/
/
18265, 00000, "fact table key column (%s) with value ('%s') not in dimension star table key column"
// *Cause: There was a row in the fact table with a key column value that was not in the corresponding dimension star table key column.
// *Action: Ensure that each fact table key column value has a corresponding row in the dimension star table key column.
/
18266, 00000, "analytic view key (%s) with value ('%s') does not determine hierarchy lowest level key"
// *Cause: The attribute references found on the analytic view keys could not determine the level key column values of the lowest level in the hierarchy.
// *Action: Ensure that the attribute references found on the analytic view keys determine the level key column values of the lowest level in the hierarchy.
/
18267, 00000, "key (%s) with value (%s) for level \"%s\" does not determine all level attributes"
// *Cause: There were rows with the level key column value where the number of distinct values of every attribute column and alternate key attribute were not zero or one.
// *Action: Ensure that the number of distinct values of every attribute column and alternate key attribute is zero or one for each level key column value.
/
18268, 00000, "alternate key (%s) with value (%s) for level \"%s\" does not determine level key column value"
// *Cause: There were rows with the alternate key attribute that had non-unique level key values.
// *Action: Ensure that the alternate key attribute rows all have the same level key value.
18269, 00000, "key or alternate key attribute \"%s\" has %s NULL values"
// *Cause: A level key column value was defined as NULL when it should be NOT NULL.
// *Action: Do not define a level key column value to NULL when it should be the NOT NULL value.
/
18270, 00000, "key or alternate key attributes \"%s\" and \"%s\" for level \"%s\" have %s mismatched NULL values"
// *Cause: There was a mismatch in the number of NULL values for a SKIP WHEN NULL level.
// *Action: Ensure that for each SKIP WHEN NULL level, either all level key column values and alternate key attributes are NULL, or all of the level key column values and alternate key attributes are not NULL.
/
/
18271, 00000, "invalid value for VisualMode query property"
// *Cause: A non-integer value, a negative value, or a value greater than 2 was specified for the VisualMode query property.
// *Action: Specify an integer value of 0, 1, or 2 for the VisualMode query property.
/
18272, 00000, "analytic view join key (%s) with value ('%s') not unique in dimension star table"
// *Cause: An analytic view join key did not determine all rows in the dimension star table.
// *Action: Ensure that the analytic view join key determines all rows in the dimension star table.
/
18273, 00000, "analytic view does not contain cache"
// *Cause: An attempt was made to create a materialized view SQL statement for an analytic view that did not contain a cache.
// *Action: Modify the analytic view to contain a cache or specify an analytic view with a cache.
/
18274, 00000, "invalid analytic view cache index"
// *Cause: The specified analytic view cache index was invalid.
// *Action: Specify a valid cache index.
/
18275, 00000, "invalid column length in log table"
// *Cause: The column size of the table did not match with the default log table.
// *Action: Ensure that the table provided has a correct column definition.
/
18276, 00000, "invalid log table version, upgrade is required"
// *Cause: There was a mismatch in the log table format that corresponds with an older version of the table.
// *Action: Call DBMS_HIERARCHY.UPGRADE_VALIDATE_LOG_TABLE in order to upgrade to the latest format and retry the operation.
/
18277, 00000, "analytic view key (%s) with value ('%s') for mesaure %s contains non-numeric data which cannot be implicitly converted to number"
// *Cause: There was data for a measure with a non-numeric data type with an aggregation method that required implicit conversion to number.
// *Action: Either correct the data in the fact table column so that all rows are able to be implicitly converted to number, or change the data type or aggregation method.
/
18278, 00000, "key (%0!s) with value (%1!s) for level \"%2!s\" has non-deterministic order by attribute values"
// *Cause: The order by of the attribute dimension for the level did not result in a deterministic order.
// *Action: Ensure that the order by of the attribute dimension for the level results in a deterministic order.
/
18279, 00000, "analytic view has been modified"
// *Cause: The analytic view for the MDX query was modified.
// *Action: Reexecute the MDX query.
/
/
/
/// 18280 - 18309 reserved for HCS DDL Compilation
/
18280, 00000, "The REFERENCES clause for analytic view dimension \"%s\" is invalid."
// *Cause: The REFERENCES clause specified for the analytic view dimension was invalid.
// *Action: Correct the REFERENCES clause for the analytic view dimension.
/
18281, 00000, "cyclic reference detected for calculated measure \"%s\""
// *Cause: A cyclic reference for a calculated measure was detected.
// *Action: Correct the cyclic reference for the calculated measure.
/
/
18282, 00000, "invalid join condition detected on join path \"%s\""
// *Cause: An invalid join condition was detected.
// *Action: Ensure that each side of the join condition comes from a different source.
/
/
18283, 00000, "invalid join path reference \"%s\" detected on hierarchy \"%s\""
// *Cause: An invalid join path reference was detected.
// *Action: Ensure that the join path on the hierarchy refers to a join path on the attribute dimension.
/
/
/
18284, 00000, "invalid join paths detected on attribute dimension \"%s\""
// *Cause: Invalid join paths were detected on the attribute dimension.
// *Action: Ensure that every dimension source is reachable starting with any source and applying join paths of the visited sources.
/
/
/
18285, 00000, "Cycle in join paths detected using join path \"%s\" when visiting source \"%s\"."
// *Cause: The current join paths defined for the attribute dimension produced a cycle.
// *Action: Ensure that every join path contains a single unique path and includes every dim source of every level in the hierarchy exactly once.
/
/
/
18286, 00000, "invalid SKIP WHEN NULL specification on a calculation expression detected on hierarchy %s"
// *Cause: An invalid SKIP WHEN NULL specification was detected on the calculation expression.
// *Action: Ensure that SKIP WHEN NULL is only specified on skip level hierarchies.
/
/
/
18287, 00000, "invalid level name \"%s\" detected on a calculation expression"
// *Cause: An invalid level name specification was detected on the calculation expression.
// *Action: Ensure the level exists on the hierarchy specified in the calculation expression.
/
/
/
18288, 00000, "parent-child hierarchy \"%s\" detected on a calculation expression level specification"
// *Cause: A parent-child hierarchy was detected on the calculation expression level specification.
// *Action: Ensure the level specifcation on the calculation expression does not reference a parent-child hierarchy.
/
/
/
18289, 00000, "parent-child member literal expression detected for level-based hierarchy %s"
// *Cause: A parent-child member literal expression was detected for a level-based hierarchy.
// *Action: Ensure that the parent-child member literal expression is used with a parent-child hierarchy.
/
/
/
18290, 00000, "positional member key mismatch detected between member literal expression and hierarchy level \"%s\" on hierarchy \"%s\""
// *Cause: The number of member keys on the member literal expression did not match those on the corresponding level.
// *Action: Ensure that the number of member keys on the member literal expression match those on the corresponding level.
/
/
/
18291, 00000, "named member key mismatch detected between member literal expression and hierarchy level \"%s\" on hierarchy \"%s\""
// *Cause: The member keys on the member literal expression did not match those on the corresponding level.
// *Action: Ensure that the member keys on the member literal expression match those on the corresponding level.
/
/
/
18294, 00000, "invalid data type detected on attribute \"%s\""
// *Cause: An invalid data type was detected on an attribute.
// *Action: Ensure that the attributes are not of LOB, BFILE, or LONG data type.
/
/
/
18295, 00000, "duplicate hierarchy %s detected in a calculation expression"
// *Cause: The same cube hierarchy was named more than once in the calculation expression.
// *Action: Specify each cube hierarchy only once in the calculation expression.
/
/
18296, 00000, "ambiguously defined hierarchy %s detected in a calculation expression"
// *Cause: An ambiguously defined hierarchy was detected in a calculation expression.
// *Action: Resolve the ambiguity on the hierarchy used in the calculation expression.
/
/
18297, 00000, "invalid data type detected on base measure \"%s\" for use with aggregation operator \"%s\""
// *Cause: An invalid data type was detected on a base measure for use with its specified aggregation operator.
// *Action: Ensure that the data type of the base measure is valid with the aggregation operator on the base measure.
/
/
/
18298, 00000, "The REFERENCES clause for the analytic view dimension \"%s\" does not determine the lowest level of every hierarchy."
// *Cause: The REFERENCES clause specified for the analytic view dimension was invalid.
// *Action: Correct the REFERENCES clause for the analytic view dimension.
/
/
18299, 00000, "level \"%s\": data type of %s expression is invalid"
// *Cause: The specified hierarchical attribute of the specified level had an invalid data type.
// *Action: Ensure that all attributes of the specified type are character expressions using the same character set.
/
/
18300, 00000, "level \"%s\": character set of %s expression does not match level \"%s\""
// *Cause: The specified hierarchical attribute of the specified level used a character set that did not match the character set of other levels.
// *Action: Ensure that all attributes of the specified type are character expressions using the same character set. An explicit ALL clause may need to be specified if the default character set of the ALL attributes does not match the character set used in other levels.
/
/
18301, 00000, "attribute dimension \"%s\".\"%s\" does not exist"
// *Cause: The attribute dimension did not exist or the user did not have the required privileges.
// *Action: Check the spelling of the attribute dimension and ensure that the required privileges are granted.
/
/
18302, 00000, "hierarchy \"%s\".\"%s\" does not exist"
// *Cause: The hierarchy did not exist or the user did not have the required privileges.
// *Action: Check the spelling of the hierarchy and ensure that the required privileges are granted.
/
/
18303, 00000, "The REFERENCES clause for the analytic view dimension \"%s\" refers to a level key where the level is marked as SKIP WHEN NULL."
// *Cause: The REFERENCES clause specified for the analytic view dimension was invalid.
// *Action: Correct the REFERENCES clause for the analytic view dimension or remove the SKIP WHEN NULL from the attribute dimension level.
/
/
18304, 00000, "non-measure \"%s\" reference in calculated measure \"%s\""
// *Cause: A non-measure was referenced in a calculated measure.
// *Action: Ensure that only a measure is referenced in a calculated measure.
/
/
18305, 00000, "non-aggregation user-defined function %s detected in window calculated measure"
// *Cause: A non-aggregation user-defined function was specified for a window calculated measure.
// *Action: Ensure that a valid user-defined aggregation function is specified for a window calculated measure.
/
/
18306, 00000, "invalid depth expression specified in a hier ancestor calculated measure"
// *Cause: An invalid depth expression was specified in a hier ancestor calculated measure.
// *Action: Ensure that the depth expression of the hier ancestor evaluates to a positive integer no greater than the number of levels in the hierarchy.
18307, 00000, "analytic view \"%s\".\"%s\" does not exist"
// *Cause: The analytic view did not exist or the user did not have the required privileges.
// *Action: Check the spelling of the analytic view and ensure that the required privileges are granted.
/
/
18308, 00000, "Source \"%s\" cannot be reached using all join paths."
// *Cause: A source could not be reached using the current join paths defined for the attribute dimension.
// *Action: Ensure that every join path includes every dim source of every level in the hierarchy exactly once.
/
/
/// 18310 - 18339 reserved for HCS DDL Parsing
/
18310, 00000, "The attribute dimension has no level specification."
// *Cause: The attribute dimension did not have a level specification.
// *Action: Specify at least one level in the attribute dimension.
/
/
18311, 00000, "MATERIALIZED or DYNAMIC keyword is missing."
// *Cause: Either the MATERIALIZED or DYNAMIC keyword was missing.
// *Action: Specify the MATERIALIZED or DYNAMIC keyword for this level group.
/
/
18312, 00000, "Dynamic caching is not enabled."
// *Cause: Analytic View (AV) dynamic caching initialization parameter was not set.
// *Action: Enable Dynamic AV caching using the appropriate initialization parameter.
/
/
/// 18340 - 18369 reserved for HCS DDL Semantic Analysis
/
18340, 00000, "Attribute \"%s\" referenced in a key on level \"%s\" does not exist."
// *Cause: The level key did not reference a valid attribute in the dimension.
// *Action: Reference an existing attribute in the level key.
/
/
18341, 00000, "Determined attribute \"%s\" referenced on level \"%s\" does not exist."
// *Cause: The determined attribute did not reference a valid attribute in the dimension.
// *Action: Reference an existing attribute in the level.
/
/
18342, 00000, "Level \"%s\" does not have a member name."
// *Cause: The level did not have a member name.
// *Action: Specify a member name for this multi-attribute key level.
/
/
18343, 00000, "Default measure \"%s\" does not exist in the cube."
// *Cause: The default measure did not reference a valid measure in the cube.
// *Action: Reference an existing measure in the cube.
/
/
18344, 00000, "Attribute \"%s\" cannot be named using a reserved word."
// *Cause: The attribute was named using a reserved word.
// *Action: Use a name for the attribute that is not a reserved word.
/
/
18345, 00000, "Duplicate metadata object %s."
// *Cause: A duplicate metadata object was specified.
// *Action: Remove or rename the duplicate metadata object specification.
/
/
18346, 00000, "Cube hierarchy \"%s\" cannot be set as the default."
// *Cause: Another default cube hierarchy was specified within the same cube dimension.
// *Action: Set only one default cube hierarchy within a cube dimension.
/
/
18347, 00000, "Duplicate level key \"%s\" was detected in level \"%s\"."
// *Cause: A duplicate level key was specified.
// *Action: Remove or replace the duplicate level key specification.
/
/
18348, 00000, "Invalid hierarchical attribute name \"%s\" specified."
// *Cause: The hierarchical attribute was named using an invalid word.
// *Action: Use a valid name for the hierarchical attribute.
/
/
18349, 00000, "Invalid skip level specification on attribute dimension \"%s\"."
// *Cause: The attribute dimension was defined with an invalid skip level specification.
// *Action: At least one level on the attribute dimension must be NOT NULL.
/
/
18350, 00000, "Attribute \"%s\" referenced on the ORDER BY clause on level \"%s\" does not exist."
// *Cause: The ORDER BY attribute did not reference a valid attribute in the dimension.
// *Action: Reference an existing attribute in the level.
/
/
18351, 00000, "Cyclic-determined attribute reference detected for level \"%s\"."
// *Cause: A cyclic-determined attribute reference for a level was detected.
// *Action: Correct the cyclic-determined attribute reference for the level.
/
/
18352, 00000, "Invalid expression \"%s\" detected on a calculated measure."
// *Cause: An invalid expression was detected on a calculated measure.
// *Action: An offset expression or member key expression cannot contain a column expression or be an analytic view SQL calculation expression.
/
/
18353, 00000, "invalid ALL member name \"%s\" detected on a hierarchy dimension \"%s\""
// *Cause: An invalid ALL member name was detected on a hierarchy dimension.
// *Action: Ensure that the ALL member name is a constant expression.
/
/
18356, 00000, "duplicate level name \"%s\" found in Cache Level List"
// *Cause: A duplicate level was found in the level list for an Analytic View Cache Level Group.
// *Action: Ensure that each Analytic View Cache Level Group contains a distinct list of levels.
/
/
18357, 00000, "duplicate measure name in Cache Measure List \"%s\""
// *Cause: A duplicate measure was found in the measure list for an Analytic View Cache Level Group.
// *Action: Ensure that each Analytic View Cache Level Group contains a distinct list of measures.
/
/
18358, 00000, "Cache Level List hierarchy not found \"%s\"."
// *Cause: A hierarchy specified in the level list for an Analytic View Cache Level Group was not found.
// *Action: Ensure that each specified hierarchy in the Analytic View Cache Level Group is defined within the Analytic View.
/
/
18359, 00000, "Cache Level List dimension not found \"%s\"."
// *Cause: A dimension specified in the level list for an Analytic View Cache Level Group was not found.
// *Action: Ensure that each specified dimension in the Analytic View Cache Level Group is defined within the Analytic View.
/
/
18360, 00000, "duplicate hierarchy found in Cache Level List"
// *Cause: Multiple levels for the same hierarchy were found in the level list for an Analytic View Cache Level Group.
// *Action: Ensure that each Analytic View Cache Level Group contains only one level per hierarchy.
/
/
18361, 00000, "duplicate Cache Object found in Analytic View Cache"
// *Cause: A duplicate Analytic View Cache Level Group and Measure List combination was found in the Analytic View Cache.
// *Action: Ensure that for each Measure List the Analytic View Cache Level Group Lists are unique.
/
18362, 00000, "The level type of level \"%s\" is inconsistent with the dimension type."
// *Cause: The level type was inconsistent with the dimension type.
// *Action: Ensure the level type is consistent with the dimension type.
/
/
18363, 00000, "Key \"%0!s\" is a subset of another key at level \"%1!s\"."
// *Cause: One key was a subset of another key at the same level.
// *Action: Ensure that no key is a subset of another key at the same level.
/
/
18364, 00000, "invalid calculated measure clause \"%s\" detected in measure \"%s\""
// *Cause: Invalid syntax was specified for a calculated measure.
// *Action: Ensure that the syntax is correct.
/
/
18365, 00000, "invalid argument count on window function \"%0!s\" detected in calculated measure \"%1!s\""
// *Cause: An invalid argument count on a window function was specified for a calculated measure.
// *Action: Ensure that a valid argument count for a window function is specified for a calculated measure.
/
/
/// 18370 - 18399 Reserved for HCS Cube SQL Query
/
18370, 00000, "The HIERARCHIES clause may only be specified for cubes."
// *Cause: A HIERARCHIES clause was used on a table or other non-cube object.
// *Action: Remove the HIERARCHIES clause.
/
/
18371, 00000, "invalid cube hierarchy qualification"
// *Cause: Cube hierarchies may only be qualified by dimension in the HIERARCHIES clause.
// *Action: Remove the additional qualification.
/
/
18372, 00000, "syntax error in HIERARCHIES list"
// *Cause: Illegal syntax was found in the HIERARCHIES clause.
// *Action: Ensure that the HIERARCHIES clause only contains a comma delimited list of cube hierarchies enclosed in parentheses.
/
/
18373, 00000, "missing hierarchy name"
// *Cause: No hierarchy was specified in the HIERARCHIES clause.
// *Action: Specify at least one hierarchy in the HIERARCHIES clause enclosed in parentheses.
/
/
18374, 00000, "duplicate hierarchies in HIERARCHIES clause"
// *Cause: The same cube hierarchy was named more than once in the HIERARCHIES clause.
// *Action: Specify each cube hierarchy only once in the HIERARCHIES clause.
/
/
18375, 00000, "Cube columns cannot be directly or indirectly referenced in ANSI named column joins."
// *Cause: A cube column was referenced in an ANSI NATURAL JOIN or USING clause.
// *Action: Use the ANSI ON clause or Oracle join syntax.
/
/
18376, 00000, "A hierarchy or analytic view is not allowed here."
// *Cause: A hierarchy or analytic view was specified in an incorrect location in a statement.
// *Action: Ensure that the name is correct or remove it.
/
/
18377, 00000, "Comments on columns of analytic view objects are not supported."
// *Cause: A comment for a column of an analytic view object was specified.
// *Action: Do not define comments for columns of analytic views. Use classifications instead.
/
/
18378, 00000, "calculated measure \"%s\" in cache measure list"
// *Cause: Calculated measures were not allowed in the cache measure list.
// *Action: Remove calculated measures from the cache measure list.
/
/
18379, 00000, "the query hint must start with \"/*+\""
// *Cause: Illegal syntax was found in the query hint session parameter.
// *Action: Ensure that the hint syntax provided is a valid SQL hint syntax.
/
/
18380, 00000, "the query hint must end with \"*/"
// *Cause: Illegal syntax was found in the query hint session parameter.
// *Action: Ensure that the hint syntax provided is a valid SQL hint syntax.
/
/
18381, 00000, "the query hint cannot contain any occurrences of \"*/\" within the text"
// *Cause: Illegal syntax was found in the query hint session parameter.
// *Action: Ensure that the hint syntax provided is a valid SQL hint syntax.
/
/
18382, 00000, "analytic view cache \"%s\" does not exist"
// *Cause: Analytic view cache for avmdx_op read did not exist.
// *Action: Change avmdx_op to read_or_write.
/
/
18383, 00000, "av_cache can only be specified for analytic views"
// *Cause: The av_cache option was specified for an object that was not an analytic view.
// *Action: Remove the av_cache option.
/
/
18384, 00000, "asymmetric condition is currently not supported for derived analyic view"
// *Cause: An asymmetric condition was specified for derived analyic view.
// *Action: Remove the asymmetric condition.
/
/
18385, 00000, "recursive WITH clause not allowed in a derived analytic view"
// *Cause: Recursive WITH clause was used in a derived analytic view.
// *Action: Do not use recursive WITH clause in a derived analytic view.
/
/
/// 18400 - 18449 HCS Validate
/
18400, 00000, "Snowflake table key (%s) with value (%s) cannot be found in joining table using join path (\"%s\")."
// *Cause: There was a row in a snow flake table with a key column value that was not in the corresponding joining table key column.
// *Action: Ensure that each snow flake key column value has a corresponding row in the table key column that you are trying to join.
/
/
18401, 00000, "Many-to-many join caused by key (%s) with value (%s) using join path (\"%s\")."
// *Cause: There was a key value in the snow flake table that was causing a many-to-many relation between two tables.
// *Action: Ensure that for a given one-to-many relation the values of the keys are unique.
/
/
/
/// 18450 - 18499 reserved for MDX PL/SQL Functions (extended from 18250-18279)
/
18450, 00000, "operation not supported in the middle of a transaction"
// *Cause: The call was made in the middle of a transaction.
// *Action: Commit or rollback the transaction.
/
/
18451, 00000, "operation not supported when flashback enabled"
// *Cause: The call was made while flashback was enabled.
// *Action: Disable flashback.
/
/
/============================================================================
/ 18700 - 18999 Reserved for JDBC (additional range)
/============================================================================
/
/
/============================================================================
/ 19000 - 19099 Reserved for XMLType error messages
/
/ Begin messages for XML errors
/============================================================================
/
19000, 00000, "missing RELATIONAL keyword"
// *Cause: The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification.
// *Action: Supply the RELATIONAL keyword in the storage clause
19001, 00000, "Invalid storage option specified"
// *Cause: An invalid storage option was specified for the XMLType.
// *Action: Supply a valid storage option.
19002, 00000, "Missing XMLSchema URL"
// *Cause: A XML schema URL must be specified in the storage option.
// *Action: Specify a URL for the XMLSchema.
19003, 00000, "Missing XML root element name"
// *Cause: A root element in the XMLSchema must be specified if the XML schema is given.
// *Action: Specify a root element in the XML schema.
19004, 00000, "Duplicate XMLType OBJECT RELATIONAL storage option"
// *Cause: A duplicate storage option for the XMLType column was specified
// *Action: Specify a single storage option for an XMLType column
19005, 00000, "Duplicate XMLType LOB storage option"
// *Cause: A duplicate storage option for the XMLType column was specified
// *Action: Specify a single storage option for an XMLType column
19006, 00000, "XMLType TYPE storage option not appropriate for storage type"
// *Cause: The TYPE option can only be used in case of OBJECT RELATIONAL storage option
// *Action: Remove the TYPE option or specify an OBJECT RELATIONAL storage for the XMLType column
19007, 00000, "Schema %s does not match expected %s."
// *Cause: The given XML document conformed to a different schema than expected.
// *Action: Insert/Update only the XML documents that conform to that particular schema.
19008, 00000, "Invalid version of the XMLType "
// *Cause: An invalid version of the XMLType was found.
// *Action: This is possibly due to data corruption or an internal error or running an older client against a newer version of the database. Ensure that the version of the client can understand the XMLType in the database.
19009, 00000, "Missing XMLSchema keyword"
// *Cause: The XMLSchema keyword is missing
// *Action: Specify the XMLSchema URL and element name.
19010, 00000, "Cannot insert XML fragments"
// *Cause: XML fragments got from extractNode cannot be inserted into the database.
// *Action: Convert the fragment into a proper XML document before insertion.
19011, 00000, "Character string buffer too small"
// *Cause: The string result asked for is too big to return back
// *Action: Get the result as a lob instead
19012, 00000, "Cannot convert XML fragment to the required datatype"
// *Cause: A conversion to a datatype was requested which cannot be performed
// *Action: The XMLType may contain fragments and other elements which cannot be converted to the appropriate datatype.
19013, 00000, "Cannot create VARRAY columns containing XMLType"
// *Cause: An attempt was made to create a VARRAY column which contains a XMLType
// *Action: You cannot store VARRAYs containing XMLTypes in tables. Use nested tables instead
19015, 00000, "Invalid XML tag identifier (%s)"
// *Cause: An invalid XML identifer was detected during XML generation
// *Action: Fix the offending tag to not contain characters or symbols that are not allowed by the XML specification
19016, 00000, "attributes cannot occur after element specifications"
// *Cause: Attributes specified using the "@" identifier can only occur before any other element definition when creating XML
// *Action: Change the order of the types so that the attributes occur in the begining
19017, 00000, "Attributes can only be simple scalars"
// *Cause: Attribute values can only be simple scalar values
// *Action: Use only simple datatypes for attribute values
19018, 00000, "Invalid character in XML tag '%s'"
// *Cause: A tag name was found to have an invalid XML character during XML generation.
// *Action: Rewrite the query so that the generated XML tag, corresponding to a column name or alias, contains only valid characters.
19019, 00000, "Invalid context passed to DBMS_XMLGEN.GETXML"
// *Cause: The value of context passed to GETXML was invalid.
// *Action: Rewrite the query so that the value of context passed to GETXML is valid.
19020, 00000, "invalid dereference of XMLType columns "
// *Cause: An attempt was made to dereference the attributes of an XMLType column which is not part of a base table
// *Action: You can only dereference the attributes of a base table XMLType column
19021, 00000, "General event for XML operations"
// *Document: NO
// *Cause: Disables functional evaluation of XML XPath operators on level 1
// *Action: N/A, this is an Oracle internal event code.
19022, 00000, "Unoptimized XML construct detected."
// *Document: YES
// *Cause: The XMLOptimizationCheck variable was enabled and an unrewritten XML construct was detected. This prevents execution of the XML construct.
// *Action: Ensure that the XML construct is being optimized. See the trace file for further information. Disable the XMLOptimizationCheck variable if you want the unoptimized XML operation to be executed.
19023, 00000, "The first argument to UPDATEXML operator has to be an XMLTYPE"
// *Cause: The first argument passed to the update value operator was not an XMLTYPE.
// *Action: Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE.
19024, 00000, "Cursor expression must be named"
// *Cause: The value of context passed to GETXML was invalid.
// *Action: Rewrite the query so that the value of context passed to GETXML is valid.
19025, 00000, "EXTRACTVALUE returns value of only one node"
// *Cause: Given XPath points to more than one node.
// *Action: Rewrite the query so that exactly one node is returned.
19026, 00000, "EXTRACTVALUE can only retrieve value of leaf node"
// *Cause: Given XPath does not point to a leaf node.
// *Action: Rewrite the query so that a leaf node is returned.
19027, 00000, "Event for supressing query rewrite with XML operators"
// *Document: NO
// *Cause: This event turns off query rewrite for XML operators
// *Action: N/A, this is an Oracle internal event code.
19028, 00000, "Invalid ADT parameter passed to toObject() function"
// *Cause: The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type.
// *Action: Pass an object of the correct type to toObject().
19029, 00000, "Cannot convert the given XMLType to the required type "
// *Cause: The passed in XMLType could not be convert to the required type
// *Action: Binary XMLtype instances or other objects cannot be converted to the required object or collection types.
19030, 00000, "Method invalid for non-schema based XML Documents."
// *Cause: The method can be invoked on only schema based xmltype objects.
// *Action: Don't invoke the method for non schema based xmltype objects.
19031, 00000, "XML element or attribute %s does not match any in type %s.%s"
// *Cause: The passed in XML tag does not match any in the object type
// *Action: Pass a valid canonical XML that can map to the given object type
19032, 00000, "Expected XML tag %s got %s"
// *Cause: When converting XML to object, a wrong tag name was present
// *Action: Pass a valid canonical XML that can map to the given object type
19033, 00000, "schema specified in the XML document does not match the schema parameter"
// *Cause: When creating schema-based XML, the schema specified in the XML document is different from the schema passed in as the 'schema' parameter.
// *Action: Change the schema parameter to match the schema specified in the XML document.
19034, 00000, "Type not supported during schema generation"
// *Cause: The object type contained a type that is not supported for schema generation.
// *Action: Use a different type or do not generate a schema.
19035, 00000, "Invalid select item of the query in newContextFromHierarchy()"
// *Cause: The query did not have a number select item followed by an XMLType select item only.
// *Action: Ensure that the result set of the query used in the newContextFromHierarchy() function has only two selected items: the first item must be number type and the second item must be XMLType.
19036, 00000, "Invalid query result set in newContextFromHierarchy()"
// *Cause: The result set of the query used in the newContextFromHierarchy() function did not have the same property as the result set generated by a CONNECT BY query.
// *Action: Ensure that the query used in the newContextFromHierarchy() function is a CONNECT BY query or that the query returns a result set having the same property as the result set generated by a CONNECT BY query.
19037, 00000, "XMLType result can not be a fragment"
// *Cause: The select item of the query in the newContextFromHierarchy() function was an XML fragment.
// *Action: Ensure that the select item of the query in the newContextFromHierarchy() function is not an XML fragment.
19038, 00000, "Invalid opertions on query context"
// *Cause: SetMaxRows, SetSkipRows, SetRowTagName opertions are applied to a query context created from newContextFromHierarchy().
// *Action: SetMaxRows, SetSkipRows, SetRowTagName opertions can not be applied to a query context created from newContextFromHierarchy().
19039, 00000, "Keyword %s reserved for future use"
// *Cause: The keyword is reserved for future use as a builtin function.
// *Action: Change the name mentioned above to a different one.
19040, 00000, "Element %s does not match expected %s."
// *Cause: The given XML document had a different root element than expected.
// *Action: Insert/Update only the XML documents that conform to that particular schema and element.
19041, 00000, "Comment data cannot contain two consecutive '-'s"
// *Cause: The given comment string expression has two consecutive '-'s.
// *Action: Modify comment string to eliminate one or both of the consevutive '-'s.
19042, 00000, "Enclosing tag %s cannot be xml in any case combination"
// *Cause: The given enclosing tag matched 'xml' in some case combination
// *Action: Modify the enclosing tag so that it is not xml in any case combination.
19043, 00000, "Multiply nested XMLROOT function disallowed"
// *Cause: An XMLROOT function has an operand that is also an XMLROOT function.
// *Action: Modify the query so that there are no multiply nested XMLROOT functions.
19044, 00000, "character length specified for XMLSerialize is too small."
// *Cause : An XMLSerialize function was called with a type of character type (e.g. VARCHAR2(27)), and the length specified (27 in the example) was too small.
// *Action : Modify the query so that the character length specified is larger.
19045, 00000, "character set id specified for XMLSerialize not valid "
// *Cause : An XMLSerialize function was called with an invalid value for the caracter set id.
// *Action : Modify the query so that the character set id is valid.
19046, 00000, "Out-of-line table cannot be shared by two top-level tables (table '%s.%s' and the current table being created)."
// *Cause : An attempt was made to share an out-of-line table between two top-level tables.
// *Action : Use the existing top-level XML table.
19047, 00000, "Cannot specify storage for individual VARRAYS"
// *Cause : An attempt was made to combine storage specification for a particular VARRAY with
// STORE ALL VARRAYS clause.
// *Action : Either specify storage for individual VARRAYs or use the STORE ALL VARRAYS clause.
19048, 00000, "Cannot specify VARRAY storage in tableProps"
// *Cause : An attempt was made to store all varrays as tables or
// LOBs in tableProps.
// *Action: Do not specify varray store as tables or LOBs in tableProps.
19049, 00000, "Event for disabling fast path insert for SQL"
// *Document: NO
// *Cause: This event turns off fast path insert for XMLType tables.
// *Action: Use if you want to turn off fast path insert for the XMLType table.
19050, 00000, "Event for adding order to SELECT from OCTs"
// *Document: NO
// *Cause: This event adds ordering by array_index when selecting from OCTs.
// *Action: N/A, this is an Oracle internal event code.
19051, 00000, "Cannot use fast path insert for this XMLType table"
// *Cause : Error while trying to insert into an XMLType table using fast path
// insert.
// *Action: Set event 19049 to disable fast path insert and try again.
19052, 00000, "Internal event"
// *Document: NO
// *Cause:
// *Action: N/A, this is an Oracle internal event code.
19053, 00000, "Internal event"
// *Document: NO
// *Cause:
// *Action: N/A, this is an Oracle internal event code.
19054, 00000, "Event for Granular Token Tables"
// *Document: NO
// *Cause:
// *Action: N/A, this is an Oracle internal event code.
19055, 00000, "Unsupported use of DISABLE XML EXCHANGE"
// *Cause: The option, DISABLE XML EXCHANGE, was specified in a
// CREATE TABLE statement.
// *Action: Do not specify DISABLE XML EXCHANGE in a CREATE TABLE statement.
19056, 00000, "Internal event"
// *Document: NO
// *Cause:
// *Action: N/A, this is an Oracle internal event code.
19057, 00000, "Internal error: binary XML [%s]"
// *Cause: The operation failed due to an internal error.
// *Action: This is an internal error. Contact Oracle Support Services.
19058, 00000, "Enabling XML exchange may cause data corruption."
// *Cause : An attempt was made to enable XML exchange for a binary XML
// column or table with a conflicting binary XML column or table.
// *Action: Use the XML exchange option only if at least one of the two
// involved tables is empty.
19059, 00000, "XML exchange has not been enabled."
// *Cause : An attempt was made to disable XML exchange on a table that
// does not have XML exchange enabled.
// *Action: Use the disable XML exchange option only if the table already
// has XML exchange enabled.
19060, 00000, "Operation disallowed on XML token set object"
// *Cause : An attempt was made to perform a disallowed operation on
// a token set object for binary XML support.
// *Action: Do not perform the attempted operation on an XML token set object.
19061, 00000, "Granular Token Set operations are not supported for tables."
// *Cause : An attempt was made to perform some Granular Token Set related
// operations on a non-binary XML table or on an older binary XML
// table.
// *Action: Do not perform the attempted operation unless tables support
// Granular Token Set options.
19062, 00000, "XML exchange is already enabled."
// *Cause : An attempt was made to enable XML exchange on a table that
// had XML exchange already enabled.
// *Action: Use the disable XML exchange option only if the table has
// XML exchange disabled.
19063, 00000, "Granular token table does not support schema-based storage."
// *Cause : An attempt was made to use granular token tables with schema-based
// storage.
// *Action: Use non-schema based storage for granular token tables.
19064, 00000, "Tablespace has XML token set objects used in another tablespace."
// *Cause : The tablespace contained an XML token set object that was used by a
// binary XML table in a different tablespace and dropping it would
// cause some data to be lost.
// *Action: Move the XML token set object to a different tablespace.
19065, 00000, "cannot drop tablespace with XML token set while XDB tablespace is offline"
// *Cause : The tablespace contained an XML token set object but the metadata
// could not be read since the XDB default tablespace was offline. By
// dropping the tablespace, some data may be lost.
// *Action: Bring XDB default tablespace online.
19066, 00000, "XML EXCHANGE is not enabled between the two tables."
// *Cause : The two tables specified in the EXCHANGE had different XML token
// sets. By exchanging partitions, some data might get corrupted.
// *Action: Enable XML EXCHANGE between the tables.
19067, 00000, "Unable to create binary granular token on user default tablespace."
// *Cause : The user default tablespace was full.
// *Action: Increase the size of the user default tablespace.
19068, 00000, "Disabling XML EXCHANGE creates token tables in the SYSTEM tablespace."
// *Cause : Either the table was in SYSTEM tablespace or it was partitioned and the
// default tablespace was SYSTEM. Granular token tables are forbidden
// on SYSTEM tablespace.
// *Action: Move the table to a different tablespace or change the default
// tablespace if the table is partitioned.
19069, 00000, "Table is already exchanging XML with itself."
// *Cause : An XML exchange was performed with the same table.
// *Action: Do not enable XML exchange with the same table.
19070, 00000, "cannot enable XML EXCHANGE in this type of table "
// *Cause : XML EXCHANGE was not allowed in global temporary tables or external tables.
// *Action: Do not use a global temporary table or external table.
19071, 00000, "Table does not have an XMLType stored as BINARY XML."
// *Cause : The table was not an XMLTable or did not have an XMLType column stored as BINARY XML.
// *Action: Use an XMLType or XMLTable stored as BINARY XML.
19072, 00000, "Only STORE AS CLOB is supported with XMLType on the sharded table."
// *Cause : STORE AS CLOB was not specified with XMLType on the sharded table.
// *Action: Specify the STORE AS CLOB clause in the query.
19073, 00000, "unsupported column type for granular token set enabled table"
// *Cause : An attempt was made to add or modify a column with an unsupported type for a
// granular token set enabled table.
// *Action: Do not use user-defined Abstract Data Types (ADTs) or an ANYDATA column with
// granular token sets.
19074, 00000, "Table does not have a granular token set."
// *Cause : The table was not used with a granular token set.
// *Action: Use an XMLType stored as BINARY XML with a granular token set.
19075, 00000, "Failed to move the token table indexes. Run dbms_csx_admin.RebuildTokenTablesIndexes before using the table."
// *Cause : An attempt to move the indexes to the given tablespace failed.
// *Action: Run dbms_csx_admin.RebuildTokenTablesIndexes.
19076, 00000, "cannot move the XML token set to tablespace where the table owner does not have privileges"
// *Cause : The table owner did not have privileges in the given tablespace.
// *Action: Use a tablespace where the table owner has privileges.
19077, 00000, "Event for Remapping CSX during TTS"
// *Document: NO
// *Cause:
// *Action: N/A, this is an Oracle internal event code.
19078, 00000, "invalid binary XML document"
// *Cause : The binary XML document was corrupted.
// *Action: None.
/
/
/============= gap for other XML error messages========
/============================================================================
/ 19100 - 19159 Reserved for XMLQuery and XMLTable error messages
/
/ Begin messages for XMLQuery and XMLTable errors
/============================================================================
19100, 00000, "PASSING or RETURNING keyword expected"
// *Cause: The keyword PASSING or RETURNING was missing.
// *Action: Specify the PASSING or RETURNING keyword.
19101, 00000, "CONTENT keyword expected"
// *Cause: The keyword CONTENT was missing.
// *Action: Specify the CONTENT keyword.
19102, 00000, "XQuery string literal expected"
// *Cause: The string literal containing the XQuery expression was missing.
// *Action: Specify the XQuery expression as a string literal.
19103, 00000, "VALUE keyword keyword"
// *Cause: The keyword VALUE was missing.
// *Action: Specify the VALUE keyword.
19104, 00000, "invalid XQueryX: missing attribute %s "
// *Cause: The XQueryX expression was not assigned the expected attribute.
// *Action: Specify a valid XQueryX.
19105, 00000, "invalid XQueryX: expected text node - got %s "
// *Cause: The XQueryX expression did not contain a text node as expected.
// *Action: Specify a valid XQueryX.
19106, 00000, "invalid XQueryX: expected %s - got %s "
// *Cause: The XQueryX expression did not contain the node as expected.
// *Action: Specify a valid XQueryX.
19107, 00000, "invalid XQueryX - unsupported construct - %s"
// *Cause: The given XQuery expression contains an unsupported construct.
// *Action: Specify a valid XQueryX.
19108, 00000, "WHITESPACE keyword expected"
// *Cause: The keyword WHITESPACE was missing.
// *Action: Specify the WHITESPACE keyword.
19109, 00000, "RETURNING keyword expected"
// *Cause: The keyword RETURNING was missing.
// *Action: Specify the RETURNING keyword.
19110, 00000, "unsupported XQuery expression"
// *Cause: The program specified an XQuery expression that is not supported.
// *Action: Rewrite the XQuery with a expression that is supported.
19111, 00000, "error during evaluation of the XQuery expression"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19112, 00000, "error raised during evaluation: %s"
// *Cause: The error function was called during evaluation of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19113, 00000, "trace function called during evaluation: %s"
// *Cause: The trace function was called during evaluation of the XQuery expression.
// *Action: Check the log file for the trace message.
19114, 00000, "XPST0003 - error during parsing the XQuery expression: %s"
// *Cause: An error occurred during the parsing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19115, 00000, "too many context items specified"
// *Cause: More than one context item was specified as input to the XMLQuery function.
// *Action: Specify a single context item for the XMLQuery function.
19116, 00000, "too many xmlspace declarations"
// *Cause: The query prolog contained multiple xmlspace declarations.
// *Action: Remove the duplicate xmlspace declarations.
19117, 00000, "XQST0070 - invalid redefinition of predefined namespace prefix '%s'"
// *Cause: The given predefined namespace was being redefined in a namespace declaration.
// *Action: Remove the namespace declaration that redefines the predefined namespace prefix.
19118, 00000, "XQST0066 - duplicate default namespace definition - %s"
// *Cause: More than one default namespace declaration used the given namespace URI.
// *Action: Remove the duplicate default namespace definition.
19119, 00000, "Event for turning on XMLQuery and XMLTable function"
// *Document: NO
// *Cause: This event turns on the XMLQuery and XMLTable functions
// *Action: N/A, this is an Oracle internal event code.
19120, 00000, "Event for changing behavior of XMLQuery and XMLTable functions"
// *Document: NO
// *Cause: This event changes the behavior of the XMLQuery and XMLTable functions
// *Action: N/A, this is an Oracle internal event code.
19121, 00000, "duplicate attribute definition - %s"
// *Cause: More than one attribute with the same name.
// *Action: Remove the duplicate attribute definition.
19122, 00000, "unsupported XQuery declaration"
// *Cause: The program specified an XQuery declaration that is not supported.
// *Action: Rewrite the XQuery with a declaration that is supported.
19123, 00000, "FORG0003: fn:zero-or-one() called with a sequence containing more than one item"
// *Cause: sequence with more than one item was passed into fn:zero-or-one() function
// *Action: correct input argument to fn:zero-or-one() function
19124, 00000, "FORG0004: fn:one-or-more() called with a sequence containing no items"
// *Cause: sequence containing no items was passed into fn:one-or-more() function
// *Action: correct input argument to fn:one-or-more() function
19125, 00000, "FORG0005: fn:exactly-one() called with a sequence containing zero or more than one item"
// *Cause: sequence containing zero or more than one item was passed into fn:exactly-one() function
// *Action: correct input argument to fn:exactly-one() function
19126, 00000, "XQuery extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces"
// *Cause: No expression was enclosed in curly braces for the extension expression or the pragma content was not recognized.
// *Action: Correct inputs to extension expression.
19127, 00000, "XQST0067: XQST0067: A static error is raised if a Prolog contains more than one construction declaration"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19128, 00000, "XQST0068: A static error is raised if a Prolog contains more than one boundary-space declaration"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19129, 00000, "XQST0069: A static error is raised if a Prolog contains more than one empty order declaration"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19130, 00000, "XQST0070: A static error is raised if the predefined namespace prefix xml or xmlns is redeclared by a namespace declaration or namespace declaration attribute"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19131, 00000, "XQST0071: A static error is raised if the namespace declaration attributes of a direct element constructor do not have distinct names"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19132, 00000, "XQDY0072: It is a dynamic error if the result of the content expression of a computed comment constructor contains two adjacent hyphens or ends with a hyphen"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19133, 00000, "XQST0073: It is a static error if the graph of module imports contains a cycle (that is, if there exists a sequence of modules M1 ... Mn such that each Mi imports Mi+1 and Mn imports M1), unless all the modules in the cycle share a common namespace"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19134, 00000, "XQDY0074: It is a dynamic error if the value of the name expression in a computed element constructor cannot be converted to an expanded QName (for example, because it contains a namespace prefix not found in statically known namespaces.)"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19135, 00000, "XQST0075: An implementation that does not support the Validation Feature must raise a static error if it encounters a validate expression"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19136, 00000, "XQST0076: It is a static error if a collation subclause in an order by clause of a FLWOR expression does not identify a collation that is present in statically known collations"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19137, 00000, "XQST0079: It is a static error if an extension expression contains neither a pragma that is recognized by the implementation nor an expression enclosed in curly braces"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19138, 00000, "The target type of a cast or castable expression must be an atomic type that is in the in-scope schema types and is not xs:NOTATION or xs:anyAtomicType, optionally followed by the occurrence indicator \"?\"; otherwise a static error is raised"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19139, 00000, "XPST0081: It is a static error if a QName used in a query contains a namespace prefix that cannot be expanded into a namespace URI by using the statically known namespaces"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19140, 00000, "XPST0083: It is a static error if the target type of a cast expression or constructor function is xs:QName or a type derived from xs:QName or xs:NOTATION, and the argument of the cast expression or constructor function is not a string literal"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19141, 00000, "XQDY0084: It is a dynamic error if the element validated by a validate statement does not have a top-level element declaration in the in-scope element declarations, if validation mode is strict"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19142, 00000, "FONC0001 = FONC0001: undefined context item"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19143, 00000, "XQTY0086: It is a type error if the typed value of a copied element or attribute node is namespace-sensitive when construction mode is preserve and copy-namespaces mode is no-preserve"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19145, 00000, "XQST0087: It is a static error if the encoding specified in a Version Declaration does not conform to the definition of EncName specified in [XML 1.0]"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19146, 00000, "XQST0088: It is a static error if the literal that specifies the target namespace in a module import or a module declaration is of zero length"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19147, 00000, "XQST0089: It is a static error if a variable bound in a for clause of a FLWOR expression, and its associated positional variable, do not have distinct names (expanded QNames)"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19148, 00000, "XQST0090: It is a static error if a character reference does not identify a valid character in the version of XML that is in use"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19149, 00000, "XQDY0091: An implementation may raise a dynamic error if an xml:id error, as defined in [XML ID], is encountered during construction of an attribute named xml:id"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19150, 00000, "XQDY0092: An implementation may raise a dynamic error if a constructed attribute named xml:space has a value other than preserve or default"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19151, 00000, "XQST0093: It is a static error to import a module M1 if there exists a sequence of modules M1 ... Mi ... M1 such that each module directly depends on the next module in the sequence (informally, if M1 depends on itself through some chain of module dependencies.)"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19152, 00000, "FOCH0001 = FOCH0001: codepoint not valid"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19153, 00000, "FOCH0002: unsupported collation"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19154, 00000, "FOCH0003: unsupported normalization form"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19155, 00000, "FOCH0004: collation does not support collation units"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19156, 00000, "FODC0001: no context document"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19157, 00000, "FODC0002: error retrieving resource"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19158, 00000, "FODC0004: invalid argument to fn:collection()"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19159, 00000, "FODC0005: invalid argument to fn:doc"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
/
/============= gap for other XQuery/XMLTable error messages========
/============================================================================
/ 19160 - 19179 Reserved for XMLQuery syntax/static type errors
/
/ Begin messages for XQuery syntax and static type errors
/============================================================================
19160, 00000, "XPST0003 - syntax error: invalid variable name %s"
// *Cause: The given XQuery variable does not begin with the '$' sign
// *Action: Fix the variable name to start with the "$" sign.
19161, 00000, "XPTY0004 - XQuery type mismatch: invalid argument type '%s' for function '%s'"
// *Cause: The type of the argument that was passed to the given function was not valid.
// *Action: Fix the argument to be of a type supported by the given function.
19162, 00000, "XPTY0004 - XQuery type mismatch: invalid argument types '%s', '%s' for function '%s'"
// *Cause: The type of the arguments that were passed to the given function was not valid.
// *Action: Fix the arguments to be of a type appropriate for the given function.
19163, 00000, "XPTY0004 - XQuery type mismatch: argument type mismatch: expected - '%s' got - '%s' for function '%s'"
// *Cause: The type of the arguments that were passed to the given function was not valid.
// *Action: Fix the arguments to be of a type appropriate for the given function.
19164, 00000, "XQST0085 - It is a static error if the namespace URI in a namespace declaration attribute is a zero-length string, and the implementation does not support [XML Names 1.1]."
// *Cause: There was a zero-length URI in namespace declaration.
// *Action: Fix the namespace declaration.
19165, 00000, "FONS0003: no prefix defined for namespace"
// *Cause: There was a zero-length URI in namespace declaration.
// *Action: Fix the namespace declaration.
19166, 00000, "FONS0003: FONS0004: no namespace found for prefix"
// *Cause: There was a zero-length URI in namespace declaration.
// *Action: Fix the namespace declaration.
19167, 00000, "FONS0005: base uri not defined in the static context"
// *Cause: There was a zero-length URI in namespace declaration.
// *Action: Fix the namespace declaration.
19168, 00000, "FORG0002: invalid argument to fn:resolve-uri()"
// *Cause: There was a zero-length URI in namespace declaration.
// *Action: Fix the namespace declaration.
19169, 00000, "FORG0006: invalid argument type in '%s'"
// *Cause: There was a zero-length URI in namespace declaration.
// *Action: Fix the namespace declaration.
19170, 00000, "Event for turning on XML Query Cost-based Rewrite"
// *Document: NO
// *Cause: This event turns on the XML Query Cost-based Rewrite.
// *Action: This is an Oracle internal event code. No action is required.
19171, 00000, "FORG0007: invalid argument to aggregate function"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19172, 00000, "FORG0008: both arguments to fn:dateTime have a specified timezone"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19173, 00000, "FORG0009: error in resolving a relative URI against a base URI in fn:resolve-uri"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19174, 00000, "FORX0001: invalid regular expression flags"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19175, 00000, "FORX0002: invalid regular expression"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19176, 00000, "FORX0003: regular expression matches zero-length string"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19177, 00000, "FORX0004: invalid replacement string"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19178, 00000, "FOTY0001: type error"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19179, 00000, "FOTY0011: Type error. Context item is not a node"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19180, 00000, "FOTY0012: argument node does not have a typed value"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19181, 00000, "FOTY0014: type exception"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19182, 00000, "FORT0001: invalid number of parameters"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19183, 00000, "FOTY0002: type definition not found"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19184, 00000, "FOTY0021: invalid node type"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19185, 00000, "FOAR0002: numeric operation overflow/unflow"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19186, 00000, "FOCA0001: input value too large for decimal"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19187, 00000, "FOCA0002: invalid lexical value"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19188, 00000, "FOCA0003: input value too large for integer"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19189, 00000, "FOCA0005: NaN supplied as float/double value"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19190, 00000, "FOER0000: Unidentified error"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19191, 00000, "FOAR0001: division by zero"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19192, 00000, "XQST0047: It is a static error if multiple module imports in the same Prolog specify the same target namespace"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19193, 00000, "XQST0045: It is a static error if the function name in a function declaration is in one of the following namespaces: http://www.w3.org/XML/1998/namespace, http://www.w3.org/2001/XMLSchema, http://www.w3.org/2001/XMLSchema-instance, http://www.w3.org/2005/04/xpath-functions, http://www.w3.org/2005/04/xpath-datatypes"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19194, 00000, "XQDY0026: It is a dynamic error if the result of the content expression of a computed processing instruction constructor contains the string \"?>\""
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19195, 00000, "Invalid policy in ora:contains"
// *Cause: An invalid policy was specified in ora:contains.
// *Action: Rename the policy name, policy schema name, or do not specify any policy to pick up default policy.
19196, 00000, "XMLType table or view is not allowed with this form of fn:collection"
// *Cause: The table or view specified in fn:collection was of XMLType.
// *Action: XMLType table or view is not allowed in the form of fn:collection('oradb:/schema/table/ROW/column'). It has to be a relational table or view.
19197, 00000, "Column not found or invalid column type with this form of fn:collection"
// *Cause: The column to be retrieved was not found or was not of XMLType.
// *Action: The column to be retrieved in the form of fn:collection('oradb:/schema/table/ROW/column') or fn:collection('oradb:/schema/table/ROW[predicate]/column') has to be of XMLType.
19198, 00000, "Column not found or invalid column specified in the predicate with this form of fn:collection"
// *Cause: The column specified in the predicate was not found or was not allowed.
// *Action: The column specified in the predicate in the form of fn:collection('oradb:/schema/table/ROW[predicate]/column') cannot be of XMLType.
19199, 00000, "too many levels of nesting"
// *Cause: An XQuery expression contained too many levels of nesting parentheses.
// *Action: Reduce the level of nesting parentheses.
/
/============= gap for other syntax error messages ========
/============================================================================
/ 19200 - 19219 Reserved for XMLGEN and XMLAGG error messages
/
/ Begin messages for DBMS_XML errors
/============================================================================
/
19200, 00000, "Invalid column specification"
// *Cause: All input arguments must be valid columns
// *Action: Specify a valid list of columns
19201, 00000, "Datatype not supported"
// *Cause: The particular datatype is not supported in the XMLGEN operator
// *Action: Specify only supported datatypes as arguments to the XMLGEN operator
19202, 00000, "Error occurred in XML processing%s"
// *Cause: An error occurred when processing the XML function
// *Action: Check the given error message and fix the appropriate problem
19203, 00000, "Error occurred in DBMS_XMLGEN processing%s"
// *Cause: An error occurred when processing the DBMS_XMLGEN functions
// *Action: Check the given error message and fix the appropriate problem
19204, 00000, "Non-scalar value '%s' is marked as XML attribute"
// *Cause: Only scalar values (i.e. values which are not of object or collection type) can be marked as XML attribute,i.e. is prefixed by '@'. In this case, a non-scalar value was prefixed with '@'
// *Action: Remove the '@' sign, or make the value a scalar.
19205, 00000, "Attribute '%s' qualifies a non-scalar value in the select list"
// *Cause: The attribute immediately follows a value of object or collection type in the select list or type definition.
// *Action: Remove the '@' sign, or make the previous value a scalar.
19206, 00000, "Invalid value for query or REF CURSOR parameter"
// *Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query, or REF CURSOR.
// *Action: Rewrite the query so that the queryString argument is a valid query or REF CURSOR.
19207, 00000, "scalar parameter %s of XMLELEMENT cannot have an alias."
// *Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.
// *Action: Remove the AS clause of the scalar element.
19208, 00000, "parameter %s of function %s must be aliased"
// *Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression.
// *Action: Specify an alias for the expression using the AS clause.
19209, 00000, "invalid or unsupported formatting argument"
// *Cause: An invalid or unsupported formatting argument was supplied
// *Action: Change the formatting argument to legal supported values
19210, 00000, "column '%s', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table '%s'"
// *Cause: The column specified using setKeyColumn()/setUpdateColumn() did not exist in the table.
// *Action: Change the column specified to be a column in the table
19211, 00000, "column '%s', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type"
// *Cause: The column specified using setKeyColumn() was a non-scalar type column.
// *Action: Change the column specified to be a scalar column in the table
19212, 00000, "no key columns specified before call to DBMS_XMLSTORE.updateXML()"
// *Cause: No columns were specified as key columns before the call to DBMS_XMLSTORE.updateXML.
// *Action: Use DBMS_XMLSTORE.setKeyColumn() to specify key columns
19213, 00000, "error occurred in XML processing at lines%s"
// *Cause: An error occurred when processing the given lines in an XML function.
// *Action: Check the given error message and fix the appropriate problem.
19214, 00000, "XMLAgg expression is not allowed with window functions or first and last expressions."
// *Cause: An attempt was made to use an XMLAgg expression with a window function or a first and last expression.
// *Action: Do not use first and last or window function with the XMLAgg expression.
/
/============================================================================
/ 19220 - 19299 Reserved for XQuery standard error messages
/
/ Begin messages for XMLQuery specification defined errors
/============================================================================
19221, 00000, "XPST0001 - XQuery static context component %s not initialized"
// *Cause: An unitialized static context component was encountered during the static analysis of the expression.
// *Action: initialize the given static context.
19222, 00000, "XPDY0002 - XQuery dynamic context component %s not initialized"
// *Cause: An unitialized dynamic context component was encountered during the evaluation of the expression.
// *Action: Initialize the particular dynamic context component.
/----------
/==== more syntax errors defined in error section 19160 and above
/-----------
19223, 00000, "XPST0003 - syntax error in XQuery expression"
// *Cause: The given XQuery expression contains syntax errors.
// *Action: Fix the syntax error in the XQuery expression.
19224, 00000, "XPTY0004 - XQuery static type mismatch: expected - %s got - %s "
// *Cause: The expression could not be used because it's static type is not appropriate for the context in which it was used.
// *Action: Fix the expression to be of the required type or add appropriate cast functions around the expression.
19225, 00000, "XPST0005 - XQuery static type error: expected non empty type got empty sequence"
// *Cause: The static type assigned to an expression other than the () expression must not be the empty type.
// *Action: Fix the expression so it does not return empty sequences.
19226, 00000, "XPTY0006 - XQuery dynamic type mismatch: expected %s got %s"
// *Cause: The expression could not be used because it's dynamic type did not match the required type as specified by XQuery sequencetype matching rules.
// *Action: Fix the expression to return the expected type or use appropriate cast functions.
19227, 00000, "XPTY0007 - fn:data function is applied to a node (type (%s)) whose type annotation denotes a complex type with non-mixed complex content."
// *Cause: The input node for atomization contained a type annotation that denoted a complex type with non-mixed complex content.
// *Action: Fix the input expression to fn:data to be a node that does not contain non-mixed complex content.
19228, 00000, "XPST0008 - undeclared identifier: prefix '%s' local-name '%s'"
// *Cause: The given identifier refers to either a type name, function name, namespace prefix, or variable name that is not defined in the static context.
// *Action: Fix the expression to remove the identifier, or declare the appropriate variable, type, function or namespace.
19229, 00000, "XQST0009 - schema import not supported"
// *Cause: A schema import was encountered in the query.
// *Action: remove the schema import.
19230, 00000, "XPST0010 - unsupported axis %s "
// *Cause: An unsupported axis was encountered in the given expression.
// *Action: Remove the unsupported axis from the expression.
19231, 00000, "XPST0011 - "
// *Cause:
// *Action:
19232, 00000, "XQST0012 - imported schemas violate validity rules"
// *Cause: The imported schemas did not satisfy the conditions for schema validity specified in the XMLSchema specification.
// *Action: Fix the imported schemas to satisfy the validity rules.In particular, the definitions must be valid, complete, and unique -- that is, the pool of definitions must not contain two or more schema components with the same name and target namespace.
19233, 00000, "XQST0013 - invalid pragma"
// *Cause: A pragma was specified whose contents are invalid.
// *Action: Specify the pragma with the correct contents.
19234, 00000, "XQST0014 - invalid or unsupported must-understand extension"
// *Cause: The must-understand extension specified was either invalid or unsupported.
// *Action: remove the unsupported must-understand extension or fix the error.
19235, 00000, "XQST0015 - unsupported must-understand extension"
// *Cause: The XQuery flagger was enabled and the query contained a must-understand extension.
// *Action: remove the unsupported must-understand extension.
19236, 00000, "XQST0016 - module declaration or import not supported"
// *Cause: The given query had a module declaration or module import.
// *Action: Remove the import module or module declaration.
19237, 00000, "XPST0017 - unable to resolve call to function - %s:%s"
// *Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.
// *Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
19238, 00000, "XPTY0018 - It is a type error if the result of the last step in a path expression contains both nodes and atomic values"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19239, 00000, "XPTY0019 - It is a type error if the result of an step (other than the last step) in a path expression contains an atomic value"
// *Cause: The step expression returned a sequence containing an atomic value.
// *Action: Fix the path expression to return only nodes.
19240, 00000, "XPTY0020 - context item must be node in an axis expression"
// *Cause: The context item that was used in the axis epression is not a node.
// *Action: Change the context item to be a node.
19241, 00000, "XPDY0021 - cast to type %s failed"
// *Cause: The value inside a cast expression could not be cast to the required type.
// *Action: Fix the input to the cast expression to be of a castable type.
19242, 00000, "XQST0022 - namespace declaration attribute must be a literal"
// *Cause: The namespace declaration attribute was not a literal string.
// *Action: Fix the namespace declaration to be a literal string.
19243, 00000, "XQTY0023 - invalid document node content in element constructor"
// *Cause: The content sequence in an element constructor contained a document node.
// *Action: Change the content of the element constructor so that it does not contain a document node.
19244, 00000, "XQTY0024 - invalid attribute node in element constructor"
// *Cause: The content sequence in an element constructor contained an attribute node following a node that was not an attribute node.
// *Action: Change the content sequence of the element constructor so that it does not contain the attribute node.
19245, 00000, "XQDY0025 - duplicate attribute name %s"
// *Cause: The content sequence of the element constructor contained more than one attribute that had the same name.
// *Action: Remove the duplicate attributes.
19246, 00000, "validation failed - element %s not found in in-scope element declarations"
// *Cause: The validation mode was strict and the element-constructor contained an element name that was not present in the in-scope element declarations.
// *Action: Fix the validation mode to be lax or import the schema definition that contains the required element declaration.
19247, 00000, "XQDY0027 - validation error"
// *Cause: An error was encountered during the validation of the expression.
// *Action: Fix the validation error.
19248, 00000, "XQTY0028 - invalid node in document constructor"
// *Cause: The content sequence in a document constructor contained either a document or an attribute node.
// *Action: Fix the content so it does not contain any of the above node types.
19249, 00000, "XQDY0029 - value does not match facet of the target type"
// *Cause: The input value to a cast expression did not satisfy the facets of the target type.
// *Action: Fix the value to conform to the facets of the target type.
19250, 00000, "XQTY0030 - too many values to validate expression"
// *Cause: The argument of a validate expression returned more than one element or document node.
// *Action: Fix the argument of the validate expression to return a single element or document node.
19251, 00000, "XQST0031 - unsupported query version"
// *Cause: The query version specified in the prolog was not supported.
// *Action: Supply the version of the query that is supported.
19252, 00000, "XQST0032 - too many declarations for base URI"
// *Cause: The query prolog contained multiple declarations for the base URI.
// *Action: Remove the duplicate definitions for the base URI.
19253, 00000, "XQST0033 - too many declarations for namespace prefix %s"
// *Cause: The query prolog contained multiple declarations for the same namespace prefix.
// *Action: Remove the duplicate definitions for the namespace prefix.
19254, 00000, "XQST0034 - too many declarations for function %s"
// *Cause: The query module contained more than one function, either declared or imported, which have the same expanded QName.
// *Action: Remove the duplicate function definitions.
19255, 00000, "XQST0035 - too many declarations of %s in imported schemas"
// *Cause: Two schemas were imported that defined the same name in the same symbol space and in the same scope.
// *Action: Fix the schema imports to remove the name conflict.
19256, 00000, "XQST0036 - missing type definitions in imported module"
// *Cause: A module was imported, which contains references to type names that are not defined in the in-scope type definitions inside the module.
// *Action: Fix the module definintion to include the in-scope type definition.
19257, 00000, "XQST0037 - function or variable %s in module already defined"
// *Cause: A module being imported contained the function or variable that is already declared in the static context of the importing module.
// *Action: Remove the conflicting declarations.
19258, 00000, "XQST0038 - unsupported or duplicate default collation specified"
// *Cause: The query prolog prolog either specified more than one default collation or the collation specified was not supported.
// *Action: Remove the duplicate definition or specify a supported collation.
19259, 00000, "XQST0039 - duplicate parameter name %s in function declaration"
// *Cause: The function declaration contained more than one parameter with the same name.
// *Action: Fix the function declaration to remove the duplicate parameters.
19260, 00000, "XQST0040 - invalid namespace node in element constructor"
// *Cause: The content sequence in an element constructor contained a namespace node node following a node that was not a namespace node.
// *Action: Remove the namespace node in the element constructor.
19261, 00000, "XQDY0041 - non empty URI in QName"
// *Cause: The name expression in a computed processing instruction or computed namespace constructor returned a QName whose URI part was not empty.
// *Action: Fix the processing instruction or computed namespace constructor to return the QName with an empty URI part.
19262, 00000, "XQST0042 - namespace constructor not inside an element constructor"
// *Cause: The enclosing expression of a computed namespace constructor was not a computed element constructor.
// *Action: Fix the namespace constructor to be inside an element constructor.
19263, 00000, "XQST0043 - duplicate namespace prefix %s"
// *Cause: Two or more computed namespace constructors within the same computed element constructor attempted to bind the same namespace prefix.
// *Action: Remove the duplicate namespace definitions.
19264, 00000, "XQDY0044 - invalid namespace in attribute constructors"
// *Cause: A computed attribute constructor returned a QName that is in the pre-defined XML namespace (corresponding to namespace prefix xmlns).
// *Action: Change the namespace for the computed attribute constructor.
19265, 00000, "XQST0045 - invalid or unknown prefix %s in function declaration"
// *Cause: The declared function name in a function declaration had no namespace prefix or had one of the predefined namespace prefixes other than local.
// *Action: Fix the function declaration to have the correct prefix.
19266, 00000, "XQST0046 - invalid URI"
// *Cause: The given URI contained a lexical form that was not valid according to the definition of xs:anyURI in XML Schema.
// *Action: Fix the URI.
19267, 00000, "module %s not found"
// *Cause: The module with the given target URI could not be found.
// *Action: Fix the prolog to import only available modules.
19268, 00000, "XQST0048 - namespace %s does not match target namespace %s"
// *Cause: The module contained a function or variable whose namespace did not match the target namespace of the module.
// *Action: Fix the namespace of the function or variable to match the target namespace of the module.
19269, 00000, "XQST0049 - variable %s defined multiple times"
// *Cause: The module defined or imported the same variable multiple times.
// *Action: Fix the import or the module definition to remove duplicate definitions.
19270, 00000, "XPDY0050 - treat failed - expected %s got %s"
// *Cause: The type of the operand to the treat expression did not match the required type.
// *Action: Fix the input operand to be of the correct type.
19271, 00000, "XPST0051 - invalid atomic type definition"
// *Cause: The QName used as an AtomicType in a SequenceType was not defined in the in-scope type definitions as an atomic type.
// *Action: Use the correct atomic type name.
19272, 00000, "XQDY0052 - invalid atomic value in attribute or element constructor"
// *Cause: The content of the element or attribute constructor included an atomic value that could not be cast into a string.
// *Action: Fix the content to contain atomic values that can be cast to a string.
19273, 00000, "XQST0053 - empty string in namespace declaration"
// *Cause: An empty string was used in a namespace declaration.
// *Action: Fix the namespace declaration to have a non-empty string.
19274, 00000, "XQST0054 - variable initialization failed due to circularity"
// *Cause: A circular definition was encountered when the variable was initialized.
// *Action: Remove the circularity in the initialization.
19275, 00000, "XQST0055 - schema path %s not found in list of in-scope schema definitions"
// *Cause: The ElementTest specified a schema path that could not be found in the list of in-scope schema definitions.
// *Action: Include the appropriate schema that can be used to resolve the ElementTest.
19276, 00000, "XPST0005 - XPath step specifies an invalid element/attribute name: (%s)"
// *Cause: The XPath step specified invalid element or attribute name that did not match any nodes according to the input XML schema or structure.
// *Action: Correct the element or attribute name as the name may be mis-spelled.
19277, 00000, "XPST0005 - XPath step specifies an item type matching no node: (%s)"
// *Cause: The XPath step specified an item type that did not match any nodes according to the input XML schema or structure.
// *Action: Correct the item type defintion as node of such type does not exit in the input XML schema or structure.
19278, 00000, "Invalid value: (%s) for type: (%s)"
// *Cause: The value was invalid for the type.
// *Action: Correct the value or change the type.
19279, 00000, "XPTY0004 - XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence"
// *Cause: The XQuery sequence passed in had more than one item.
// *Action: Correct the XQuery expression to return a single item sequence.
19280, 00000, "XQuery dynamic type mismatch: expected atomic value - got node"
// *Cause: A node was passed in to the expression where an atomic value was expected.
// *Action: Correct the XQuery expression to return an atomic value.
19281, 00000, "XQST0055 - It is a static error if a Prolog contains more than one copy-namespaces declaration"
// *Cause: The query prolog contained multiple copy-namespaces declarations.
// *Action: Remove the duplicate copy-namespaces declarations.
19282, 00000, "XQST0068 - It is a static error if a Prolog contains more than one xmlspace declaration"
// *Cause: The query prolog contained multiple xmlspace declarations.
// *Action: Remove the duplicate xmlspace declarations.
19283, 00000, "XQST0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation."
// *Cause: The query contained a version declaration not supported by this implementation.
// *Action: Change the version declaration to 1.0 which is the version supported by this implementation.
19284, 00000, "Encoding specification in version declaration not supported"
// *Cause: The query contained an encoding specification.
// *Action: Remove the encoding specification.
19285, 00000, "FODC0002 - error retrieving resource"
// *Cause: The URI provided could not be resolved to a valid resource.
// *Action: Provide a valid URI for a resource.
19286, 00000, "XPST0017 - unable to resolve call to function - %s"
// *Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.
// *Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
19287, 00000, "XPST0017 - invalid number of arguments to function - %s:%s"
// *Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.
// *Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
19288, 00000, "XPST0017 - invalid number of arguments to function - %s"
// *Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context.
// *Action: Fix the name of the function or the number of parameters to match the list of in-scope functions.
19289, 00000, "XQST0034 - function %s:%s declared or defined multiple times"
// *Cause: Multiple functions declared or imported by a module had the same expanded QName and the same number of arguments.
// *Action: Fix the function declaraction or definition to remove duplicates.
19290, 00000, "XQST0069 - more than one empty order declaration declared in the prolog"
// *Cause: A prolog had more than one empty order declaration.
// *Action: Fix the prolog to have just one empty order declaration.
19291, 00000, "XPST0081 - specified QName cannot be expanded into a namespace URI"
// *Cause: The namespace prefix of the QName could not be expanded into a namespace URI by using the statically known namespaces.
// *Action: Use a namespace prefix that can be resolved into a namespace URI from the statically known namespaces.
19292, 00000, "XQST0057: It is a static error if a schema import binds a namespace prefix but does not specify a target namespace other than a zero-length string"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19293, 00000, "XQST0058: It is a static error if multiple schema imports specify the same target namespace"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19294, 00000, "XQST0059: It is a static error if an implementation is unable to process a schema or module import by finding a schema or module with the specified target namespace"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19295, 00000, "XQST0060: It is a static error if the name of a function in a function declaration is not in a namespace (expanded QName has a null namespace URI)"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19296, 00000, "XQDY0061: It is a dynamic error if the operand of a validate expression is a document node whose children do not consist of exactly one element node and zero or more comment and processing instruction nodes, in any order"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19297, 00000, "XQDY0064: It is a dynamic error if the value of the name expression in a computed processing instruction constructor is equal to \"XML\" (in any combination of upper and lower case"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19298, 00000, "XQST0065: A static error is raised if a Prolog contains more than one ordering mode declaration"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
19299, 00000, "XQST0066: A static error is raised if a Prolog contains more than one default element/type namespace declaration, or more than one default function namespace declaration"
// *Cause: An error occurred during the processing of the XQuery expression.
// *Action: Check the detailed error message for the possible causes.
/
/============================================================================
/ 19300 - 19390 Reserved for UriType error messages
/
/ Begin messages for UriType errors
/============================================================================
/
/ 19300 - 19319 = reserved for general uri error messages
/
19300, 00000, "Error occurred in uri processing%s"
// *Cause: An error occurred when processing the URL
// *Action: Check the given error message and fix the appropriate problem
/
/ 19320 - 19329 = reserved for Httpuri error messages
/
19320, 00000, "Host name not specified in HTTP URL"
// *Cause: A host name was not specified in the HTTP url
// *Action: Specify a host name in the HTTP url when creating the URL string
19321, 00000, "Could not open HTTP connection to host (%s): port (%s)"
// *Cause: A HTTP connection could not be opened to the host
// *Action: Specify a valid host name and port to connect to
19322, 00000, "An error occurred while reading from host (%s): port (%s)"
// *Cause: An error occurred while reading from the HTTP host
// *Action: Specify a valid host name and port to read from
19323, 00000, "Invalid url string"
// *Cause: The URL must be a valid URL string
// *Action: Specify a valid url string
/
/ 19330 - 19360 = reserved for DBUri error messages
/
19330, 00000, "Type '%s'.'%s' not installed. Please install the type before using the CREATE_DBURI operator"
// *Cause: The type required for the CREATE_DBURI operator has not been installed correctly.
// *Action: Read the installation notes to install the type correctly.
19331, 00000, "Last argument to CREATE_DBURI operator must be a column"
// *Cause: The final argument to the CREATE_DBURI operator must be a column to which the reference is being created.
// *Action: Specify a valid column name in the query.
19332, 00000, "Invalid column in the CREATE_DBURI operator"
// *Cause: The argument to the CREATE_DBURI operator can only be a column.
// *Action: Specify a valid column name for the operator
19333, 00000, "Invalid flags for the CREATE_DBURI operator"
// *Cause: The flags argument given to the DBURI operator is invalid
// *Action: Specify a valid flag value (TEXT) for the DBURI operator
19334, 00000, "Invalid column specification for CREATE_DBURI operator"
// *Cause: All columns must be valid and pointing to the same table or view
// *Action: Specify valid list of columns that are from the same table or view.
19335, 00000, "Invalid format type object"
// *Cause: An invalid format type object was specified for the XML function
// *Action: Specify a valid format type object
19336, 00000, "Missing XML root element"
// *Cause: The XML being generated does not have an enclosing root element.
// *Action: The XML generated must have a root element
/
/ 19361 - 19370 = reserved for analyze parse and execution errors
/
19361, 00000, "ONLINE option not allowed with this type of index"
// *Cause: The ONLINE option was specified to validate the structure of a
// system-generated metadata index
// *Action: The ONLINE option can not be used with system-generated metadata
// indexes such as an LOB index, an IOT Top index, an Index on
// Clusters etc., Run query without using the ONLINE option.
/
/==============================================
/= 13750 - 13799 reserved for SqlSet =
/= 19371 - 19390 reserved for sqlset/sqltune =
/==============================================
/
19371, 00000, "invalid update option"
// *Cause: The user attempted to call load_sqlset with an update option
// that is different than REPLACE and ACCUMULATE.
// *Action: Adjust the update option and retry the operation.
/
19372, 00000, "invalid update condition"
// *Cause: The user attempted to call load_sqlset with an invalid update
// condition.
// *Action: Check the update condition (e.g., NEW.COL1_NAME >= OLD.COL2_NAME)
// and retry the operation.
/
19373, 00000, "invalid staging table or tablespace"
// *Cause: The user attempted to create a staging table and specified an
// invalid staging table (or one that already exists) or tablespace
// *Action: Check the arguments and try again.
/
19374, 00000, "invalid staging table"
// *Cause: The user specified an invalid staging table to one of the
// pack, unpack, or remap stgtab routines, or the user does
// not have the correct privileges on the staging table
// *Action: Provide a correct staging table or grant the
// appropriate privileges
/
19375, 00000, "no CREATE TABLE privilege on schema \"%s\""
// *Cause: The user tried to create a staging table when he is missing the
// CREATE TABLE privilege on the specified schema.
// *Action: Grant the privilege to the user and retry
//
/
19376, 00000, "no privileges on tablespace provided or tablespace is offline"
// *Cause: The user tried to create a staging table on a tablespace on which he
// does not have any space allocated, or it is offline
// *Action: Allocate space on the tablespace, bring it online, and retry
/
19377, 00000, "no \"SQL Tuning Set\" with name like \"%s\" exists for owner like \"%s\""
// *Cause: The user specified a filter to a pack/unpack function for the SQL
// Tuning Set that targets no STS in the SYS schema or the staging
// table, respectively
// *Action: Provide a different filter after checking the state of the system
/
19378, 00000, "invalid mode"
// *Cause: The user specified an invalid mode argument to the capture
// function.
// *Action: Provide a mode argument that was defined in the dbmssqlt file
/
19379, 00000, "invalid time_limit or repeat_interval"
// *Cause: Either a NULL value was specified for the time_limit or the
// repeat_interval value, or the repeat_interval value was greater
// than the time_limit value.
// *Action: Provide a non-NULL value and ensure that time_limit value is
// greater than or equal to the repeat_interval value.
/
19380, 00000, "invalid plan filter"
// *Cause: The user specified an invalid filter for the plan when calling the
// select_sqlset table function.
// *Action: Adjust the the filter to be one of the following values
// and retry the operation: MAX_ELAPSED_TIME, MAX_CPU_TIME,
// MAX_DISK_READS, MAX_OPTIMIZER_COST, MAX_BUFFER_GETS, FIRST_LOADED
// LAST_LOADED, FIRST_GENERATED, or LAST_GENERATED.
/
19381, 00000, "cannot create staging table in SYS schema"
// *Cause: The user attempted to create a staging table in the sys schema
// *Action: Create the table in another schema.
/
19382, 00000, "timeout encountered during sqltune test-execute"
// *Document: NO
// *Cause: This is an internal error code used internally to signal a
// timeout during a SQL Tune test-execute operation
/
19383, 00000, "all plans encountered errors during sqltune test-execute"
// *Document: NO
// *Cause: This is an internal error code used to signify that
// a sqltune test-execute operation in RESILIENT mode ended with
// all plans encountering errors.
// *Action: Examine the errors stored in the plans one by one.
/
19384, 00000, "cannot pack into staging table from previous version"
// *Cause: An attempt was made to perform a pack operation on a staging
// table from a previous version.
// *Action: Create a staging table in the current version and retry the
// operation.
/
19385, 00000, "staging table is empty"
// *Cause: An attempt was made to perform an operation on an empty staging
// table.
// *Action: Check the staging table to ensure that it has rows.
/
19386, 00000, "target object already exists for tuning task \"%s\""
// *Cause: An attempt was made to set a target object for a tuning task
// when one had already been set.
// *Action: Create a new task if another target object is needed.
/
19387, 00000, "\"SQL Tuning Set\" \"%s\" belongs to another tuning task"
// *Cause: The user attempted to tune a task-managed SQL Tuning Set belonging
// to one task within the scope of another task.
// *Action: Check the SQL Tuning Set and retry the operation.
/
19388, 00000, "operation not supported for \"SQL Tuning Set\" type"
// *Cause: The attempted operation was unsupported for the type
// of the given SQL Tuning Set.
// *Action: Check the SQL Tuning Set and retry the operation.
/
19389, 00000, "LOB types are not supported for SQL binds"
// *Cause: A LOB type was provided in a SQL bind list.
// *Action: Replace the LOB binds with legal bind types or try another
// SQL.
/
19390, 00000, "The profile type is not valid"
// *Cause: The profile type is not valid.
// *Action: Check the available profile types.
/
/==========================================================================
/ 19391 - 19399 are reserved for ODM (dNFS, opcodm).
/==========================================================================
/
19391, 00000, "Direct nfs - kgnfs tracing level"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is the level
// used to control trace output of Direct NFS kgnfs. DO
// NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
19392, 00000, "Direct nfs - kgnfs tracing bitmask"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is bitmask
// used to control trace output of Direct NFS kgnfs. DO
// NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
19393, 00000, "Direct nfs - skgnfs tracing level"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is the level
// used to control trace output of AutoNFS skgnfs. DO
// NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
19394, 00000, "Direct nfs - skgnfs tracing bitmask"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is bitmask
// used to control trace output of AutoNFS skgnfs. DO
// NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
19395, 00000, "Direct nfs - kgodm tracing level"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is the level
// used to control trace output of Direct NFS kgodm. DO
// NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
19396, 00000, "Direct nfs - kgodm tracing bitmask"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is bitmask
// used to control trace output of Direct NFS kgodm. DO
// NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
19397, 00000, "Direct nfs - config mask"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is bitmask
// used to control config settings for Direct NFS. DO
// NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
19398, 00000, "Direct nfs - event flags"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is bitmask
// used to control event settings for Direct NFS. DO
// NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
19399, 00000, "OPC ODM tracing level"
// *Document: NO
// *Cause: This is an Oracle internal event code. This event is bitmask
// used to control trace outout for OPC ODM library. DO
// NOT USE.
// *Action: N/A, this is an Oracle internal event code.
/
/==========================================================================
/ 19400 - 19499 are reserved for KOT.
/==========================================================================
/
19400, 00000, "System type conflict with object SYS.%s"
// *Cause: The user had an object with the same name as one of the system
// types. The system types were not initialized properly.
// *Action: Remove the conflicting object and rerun migration.
/
/ Copyright (c) 1995, 2017, Oracle and/or its affiliates. All rights reserved.
/
/ NAME
/ e19500.msg
/ DESCRIPTION
/ Error messages Reserved for Recovery Manager (RMAN).
/ NOTES
/ All errors in this file are reserved for Recovery Manager (RMAN). Please
/ do not take them for other purpose.
/
/ Error numbers
/
/ 19500 - 19998 Reserved for Server Managed Recovery
/ 19500-19524: KGF*, KSF*
/ 19525-19539: More db file errors
/ 19540-19549: KRB events
/ 19550-19699: KRB*, except KRBI
/ 19700-19719: KRBI
/ 19720-19739: Transportable Tablespace kernel errors (KCP)
/ 19740-19749: More KRBI errors
/ 19750-19799: Block change tracking
/ 19800-19829: Recovery Area Errors
/ 19830-19835: SQL Engine Errors
/ *** 19836-19850: General-use range - first free message=19844
/ 19851-19859: Auxiliary instance
/ 19860-19870: Additional KRBR Messages
/ 19871-19879: Reserved for testing events
/ 19880-19885: Unused block Compression
/ 19886-19889: For testing purposes
/ 19890-19898: Free range
/ 19899-19912: Recovery thru resetlogs project
/ 19913-19920: Encrypted backups
/ 19921-19925: KRB* errors
/ 19926-19929: Transport database errors
/ 19930-19935: More KRB* errors
/ 19936-19950: cross-platform transpotable tablespace (xtts)
/ 19951-19960: DBNEWID
/ 19965-19979: multi-instance standby switchover
/ 19980-19989: xtts backup
/ 19990-19998: Free range
/
/ MODIFIED
/ sihaldar 12/10/17 - RTI 20786659: message for 19935 is updated
/ sihaldar 09/29/17 - bug 26830394: statement for event 19828 modified
/ sihaldar 01/03/17 - bug 21209547: added event 19964
/ ppatare 05/10/17 - bug 25971150: Add level 2 to 19886
/ kinerell 03/24/17 - bug 21964483: Add 19829
/ sihaldar 01/03/17 - bug 21674528: added event 19878
/ bhaveshp 06/23/16 - bug 18180615: error message for drop database.
/ sihaldar 11/20/15 - bug 21877055: error message for datafile move/rekey
/ ardrai 08/03/15 - bug 21546479 enabling same pltfrm encrypted restore
/ molagapp 03/11/15 - Project 47808 - Phase 2
/ svrrao 03/10/15 - Adding test event for krbpd/s/a/dmp structure sizes
/ sihaldar 09/14/14 - Project 48715: Support for sparse backup & restore.
/ svrrao 10/27/14 - Adding error message for xttrestore plugin
/ panreddy 12/10/14 - Bug 19419074.
/ apadilla 12/03/14 - bug 20112646: Add unit to 19804
/ srajpuro 06/10/14 - Bug 13849436 message 19886
/ molagapp 02/26/14 - change error message 19838
/ asathyam 01/17/14 - Bug 17842729: Add message 19867
/ apadilla 11/05/13 - Bug 13117122: Enhance ORA-19625
/ debjroy 03/10/12 - add 19933
/ molagapp 03/08/12 - bug-13813257
/ molagapp 11/15/11 - add 19849, 19850
/ fsanchez 07/09/11 - bug 12613970
/ svrrao 05/13/11 - ChangeTracking: 19876:Event for testing
/ yuli 02/24/11 - add 19929
/ pkapil 02/18/11 - Bug 10409625
/ akruglik 02/03/11 - Modify "Cause" of error 19529 since it may be issued
/ when processing value of PDB_FILE_NAME_CONVERT
/ parameter
/ molagapp 11/01/10 - active network restore
/ fsanchez 01/19/11 - bug 11074876
/ fsanchez 07/15/09 - xtts_from_backup
/ pkapil 12/29/10 - Bug no : 9234538
/ molagapp 07/22/10 - project_25862: snapshot time recovery
/ fsanchez 03/30/10 - do not allow a backup controfile from rman's
/ duplicate to open the database
/ fsanchez 03/04/10 - lrg 4521736, add 19837
/ molagapp 01/07/10 - add 19824, 19825 event
/ fsanchez 01/25/10 - bug 9230148
/ molagapp 12/26/09 - add 19823 event to adjust space pressure percentage
/ molagapp 12/26/09 - add 19822 event to adjust FRA monitoring interval
/ mgirkar 12/24/09 - Add more text to 19527 error message
/ fsanchez 08/20/09 - bug 8689421
/ molagapp 06/03/09 - remove flash reference
/ molagapp 02/24/09 - bug 6489610
/ swerthei 02/13/09 - bug 8246019 - allow compressed backup of encrypted ts
/ fsanchez 08/18/08 - bug 6623413
/ fsanchez 08/10/10 - lzo support
/ molagapp 09/10/08 - fix 19932
/ fsanchez 08/18/08 - bug 6623413
/ yuli 08/25/08 - add 19972 and 19975
/ yuli 06/18/08 - deprecate ALTER DATABASE RECOVER STANDBY
/ DATAFILE|TABLESPACE
/ fsanchez 05/23/08 - add 19961
/ fsanchez 05/20/08 - bug 1690875
/ molagapp 05/12/08 - add 19943
/ jjlee 05/08/08 - add 19820 and 19821
/ yuli 04/29/08 - multi-instance standby switchover
/ ssamaran 02/19/08 - add 19780 - active data guard not enabled
/ yuli 02/09/08 - add 19899
/ shsong 12/17/07 - add 19963
/ fsanchez 10/16/06 - reword 19870
/ swerthei 08/11/06 - remove 19872
/ fsanchez 08/25/06 - add 19882, modify cause/action for unused block opt.
/ molagapp 08/14/06 - add 19546 event
/ swerthei 01/05/06 - multi-section backup messages
/ fsanchez 03/08/06 - reserve 19541 for event
/ swerthei 10/07/05 - sbt-allocated buffers
/ fsanchez 01/03/06 - improve message readability
/ fsanchez 12/08/05 - add 19941, 19942
/ molagapp 10/03/05 - add 19529
/ molagapp 08/23/05 - add 19819
/ molagapp 08/22/05 - molagapp_dbhygiene_rman_3
/ molagapp 08/16/05 - Creation
/
/19500 - 19524: Reserved for KGF*, KSF*
/
/
19500, 00000, "device block size %s is invalid"
// *Cause: the device block size returned by sequential I/O OSD is invalid
// *Action: If the block size was set by using the PARMS option of the
// Recovery Manager ALLOCATE CHANNEL command, then the specified
// block size must be changed. If no PARMS option was specified on
// the ALLOCATE CHANNEL command, then this is an internal error that
// should be reported to Oracle.
19501, 00000, "read error on file \"%s\", block number %s (block size=%s)"
// *Cause: read error on input file
// *Action: check the file
19502, 00000, "write error on file \"%s\", block number %s (block size=%s)"
// *Cause: write error on output file
// *Action: check the file
19503, 00000, "cannot obtain information on device, name=\"%s\", type=\"%s\", parms=\"%s\""
// *Cause: call to get device information returned an error
// *Action: check device name, type and parameters
19504, 00000, "failed to create file \"%s\""
// *Cause: call to create file returned an error
// *Action: check additional messages, check access permissions.
19505, 00000, "failed to identify file \"%s\""
// *Cause: call to identify the file returned an error
// *Action: check additional messages, and check if the file exists.
19506, 00000, "failed to create sequential file, name=\"%s\", parms=\"%s\""
// *Cause: call to create the sequential file returned an error
// *Action: check additional messages, check access permissions.
19507, 00000, "failed to retrieve sequential file, handle=\"%s\", parms=\"%s\""
// *Cause: call to retrieve the sequential file returned an error
// *Action: check additional messages, and check if the file exists.
19508, 00000, "failed to delete file \"%s\""
// *Cause: call to delete the file returned an error
// *Action: check additional messages.
19509, 00000, "failed to delete sequential file, handle=\"%s\", parms=\"%s\""
// *Cause: call to delete the sequential file returned an error
// *Action: check additional messages.
19510, 00000, "failed to set size of %s blocks for file \"%s\" (block size=%s)"
// *Cause: call to resize the file returned an error
// *Action: check additional messages.
19511, 00000, "non RMAN, but media manager or vendor specific failure, error text:\n %s"
// *Cause: An error occurred in the media management software which
// is linked with the Oracle server to perform backup and restore
// in cooperation with Recovery Manager.
// *Action: If the text of message 19511 does not provide enough
// information to resolve the problem, then you should contact the
// vendor of the media management software.
19512, 00000, "file search failed"
// *Cause: Recovery manager or Oracle Server attempted to discover files
// that matched the specified pattern but failed.
// *Action: Check errors on the error stack for an explanation
// why the search for files could not be successfully executed.
19513, 00000, "failed to identify sequential file"
// *Cause: Unable to identify the sequential file.
// *Action: Check additional messages, and check if the file exists on media.
/
/19514 reserved for skgfq-allocated buffer disabling event
/
/19525 - 19547: More db file errors
/
19525, 00000, "tempfile for the clone database must be renamed"
// *Cause: Opening a clone database failed because Oracle server forces the
// tempfile to be renamed, in order to avoid overwriting
// the primary tempfile.
// *Action Rename the tempfiles manually or automatically by using
// the DB_FILE_NAME_CONVERT initialization parameter.
19526, 00000, "only one location allowed for parameter %s"
// *Cause: A list of default locations was provided in an Oracle-managed
// files parameter.
// *Action Edit the parameter to include a single location.
19527, 00000, "physical standby redo log must be renamed"
// *Cause: An attempt was made to clear redo log at a physical standby
// database. Clearing an OMF redo log will not work unless
// DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or
// DB_RECOVERY_FILE_DEST parameter is specified. Clearing a non-OMF
// (or user-defined) redo log file will not work unless the
// LOG_FILE_NAME_CONVERT initialization parameter is
// set.
// *Action Set DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or
// DB_RECOVERY_FILE_DEST parameter for OMF redo log files and
// re-issue the operation that attempted to clear redo log. Set
// LOG_FILE_NAME_CONVERT parameter for non-OMF redo log files and
// re-issue the operation that attempted to clear redo log.
19528, 00000, "redo logs being cleared may need access to files"
// *Cause: The redo logs are being cleared. This procedure may need the
// files this operation is being applied to.
// *Action: Wait for the redo logs to be cleared.
19529, 00000, "Pattern %s in initialization parameter %s has an Oracle Managed Files file name."
// *Cause: An attempt was made to convert a database file name to an Oracle
// Managed Files file name using DB_FILE_NAME_CONVERT,
// PDB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT initialization
// parameter. This was not a valid operation.
// *Action: Retry the operation with a pattern template instead of a full
// Oracle Managed Files file name.
/
// Reserved errors for KRB events - do not document here the events.
// 19540
// 19541
// 19542 - crash event
// Level Description
// ----- -----------
// 1 crash process before updating file header for incr restore
// 2 crash process before cataloging file for incr restore
// 19544
// 19545
// 19546
// 19547
// 19548
// 19549
/
/
/ 19550-19699: KRB*, except KRBI
/
19550, 00000, "cannot use backup/restore functions while using dispatcher"
// *Cause: Attempted to use backup/restore functions while connected to the
// dispatcher in a shared server.
// This is not allowed because the device that is
// used for backup and restore must remain allocated to a single
// process.
// *Action: Connect directly to the instance then re-execute the backup or
// restore function.
19551, 00000, "device is busy, device type: %s, device name: %s"
// *Cause: The indicated device could not be allocated because it is
// allocated to another session, or no device was named, or all
// devices of the requested type are busy.
// *Action: Either attempt to allocate another device or wait until the
// required device is no longer busy.
19552, 00000, "device type %s is invalid"
// *Cause: The device type indicated is invalid.
// *Action: Supply a correct device type and retry the allocation.
19553, 00000, "device name %s is invalid"
// *Cause: The device name indicated is invalid.
// *Action: Supply a correct device name and retry the allocation.
19554, 00000, "error allocating device, device type: %s, device name: %s"
// *Cause: The specified device could not be allocated.
// *Action: One or more other messages should be displayed to help pinpoint
// the cause of the error. Correct the error and retry the
// allocation.
19555, 00000, "invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value"
// *Cause: The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set
// within the valid range.
// *Action: Specify a correct value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST.
// If the archive log parameters LOG_ARCHIVE_DEST or
// LOG_ARCHIVE_DUPLEX_DEST are in use, set parameter
// LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2.
19556, 00000, "required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred"
// *Cause: The destination for parameter LOG_ARCHIVE_DUPLEX_DEST was deferred
// when it was required to be enabled. The destination was
// deferred automatically when an ALTER SYSTEM command for parameter
// LOG_ARCHIVE_DEST defined a destination which duplicated an existing
// LOG_ARCHIVE_DUPLEX_DEST parameter destination.
// *Action: Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST
// parameter.
19557, 00000, "device error, device type: %s, device name: %s"
// *Cause: An error occurred in the platform-specific device code
// *Action: One or more other messages should be displayed to help pinpoint
// the cause of the error. Correct the error and retry the
// allocation.
19558, 00000, "error de-allocating device"
// *Cause: The specified device could not be de-allocated.
// *Action: One or more other messages should be displayed to help pinpoint
// the cause of the error. Correct the error and retry the
// allocation.
19559, 00000, "error sending device command: %s"
// *Cause: An error occurred while sending the indicated command to the
// session device.
// *Action: One or more other messages should be displayed to help pinpoint
// the cause of the error. Correct the error and retry the
// allocation.
19560, 00000, "%s is not a valid device limit name"
// *Cause: An invalid name of device limit was specified in a call to
// DBMS_BACKUP_RESTORE.SETLIMIT.
// *Action: Use one of the device limit names described in dbmsbkrs.sql
19561, 00000, "%s requires a DISK channel"
// *Cause: The attempted command requires that a DISK device channel be
// allocated to the session, but a non-DISK device was found.
// *Action: Deallocate the current device and allocate a DISK channel, then
// then retry the command.
19562, 00000, "file %s is empty"
// *Cause: The indicated file, which is an archived log, control file, or
// datafile was found to be empty during a copy, backup, or scan]
// operation.
// *Action: Ensure that the correct files are being specified for the copy
// or backup operation.
19563, 00000, "%s header validation failed for file %s"
// *Cause: When opening the file to be placed in a copy or backup set,
// to be inspected, or used as the target for
// an incremental restore, its header was not
// recognized as a valid file header for a file of the indicated
// type (datafile, archived log, or control file) belonging
// to the current database.
// *Action: Ensure that the correct files are being specified for the copy
// or backup operation.
19564, 00000, "error occurred writing %s bytes at block number %s"
// *Cause: An error occurred while writing to a file.
// *Action: One or more other messages should be displayed to help pinpoint
// the cause of the error. Correct the error if possible, then retry
// the copy, backup, or restore operation.
19565, 00000, "BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices"
// *Cause: An attempt was made to specify duplexing to sequential devices,
// but the BACKUP_TAPE_IO_SLAVES initialization parameter was not
// enabled.
// *Action: Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file,
// or do not specify duplexing to sequential devices.
19566, 00000, "exceeded limit of %s corrupt blocks for file %s"
// *Cause: The user specified limit of allowable corrupt blocks was exceeded
// while reading the specified datafile for a datafile copy or
// backup.
// *Action: None. The copy or backup operation fails.
// The session trace file contains detailed information
// about which blocks were corrupt.
19567, 00000, "cannot shrink file %s because it is being backed up or copied"
// *Cause: An ALTER statement attempted to reduce the size of the indicated
// file while the same file is being backed up or copied.
// *Action: Retry the resize after the backup or copy is complete.
19568, 00000, "a device is already allocated to this session"
// *Cause: A device cannot be allocated to a session if another device is
// already allocated.
// *Action: Deallocate the current device
19569, 00000, "no device is allocated to this session"
// *Cause: An operation was attempted which requires a device to be allocated
// to the current session, and there is no device allocated.
// *Action: Allocate a device then retry the operation.
19570, 00000, "file number %s is outside valid range of 1 through %s"
// *Cause: A file number used in a copy, backup, or restore operation is not
// valid for the current database.
// *Action: Specify a valid file number.
19571, 00000, "%s RECID %s STAMP %s not found in control file"
// *Cause: The input file specified for a copy or backup operation could
// not be opened because the record describing the file is not found
// in the control file.
// *Action: Specify a correct RECID/STAMP and retry the copy or backup.
19572, 00000, "cannot process file %s, file is being being resized"
// *Cause: The input file specified for a copy or backup operation could
// not be opened because the file is being resized.
// *Action: Wait for the resize to complete then retry the copy or backup.
19573, 00000, "cannot obtain %s enqueue for datafile %s"
// *Cause: The file access enqueue could not be obtained for a file
// specified in a backup, copy or restore operation.
// If the enqueue type shown is 'shared', then the file is the
// input file for a backup or copy. If the type is 'exclusive', then
// the file is the output file for a datafile copy or restore which
// is attempting to overwrite the currently active version of that
// file - in this case, the file must be offline or the database must
// be closed. If the type is 'read-only', then you are attempting
// to back up or copy this file while the database is in NOARCHIVELOG
// mode.
// *Action: Wait until the conflicting operation is complete, then retry
// the copy or backup. If the database is in NOARCHIVELOG mode, then
// all files being backed up must be closed cleanly.
19574, 00000, "output file name must be specified"
// *Cause: This type of copy or restore requires an output file name.
// *Action: Specify an output file name and retry the copy.
19575, 00000, "expected %s blocks in file %s, found %s"
// *Cause: During a backup, restore, copy, or scan operation, the indicated
// file did not contain as many blocks as were indicated in the file
// header.
// *Action: The input copy or backup piece is probably corrupt. If another
// backup or copy exists of the file that is being restored, then the
// corrupt file can be deleted from the recovery catalog and the
// operation can be restarted.
19576, 00000, "datafile %s not defined in control file"
// *Cause: The specified file number was not found in the control file.
// *Action: Specify a correct file number and retry the operation.
19577, 00000, "file %s is MISSING"
// *Cause: A COPYDATAFILECOPY, RESTOREDATAFILETO or PROXYRESTOREDATAFILE
// function specified a file number but no output file name,
// indicating that the output file name should be taken from
// the control file. However, the control file entry for this
// file indicates that it was created for a file that was present
// in the data dictionary but not named during the last CREATE
// CONTROLFILE statement, so the name in the control file cannot
// be used for restoration.
// *Action: Either specify an output file name or issue a SQL RENAME command
// to enter a valid name for this file in the control file.
19578, 00000, "end of volume while duplexing to sequential files, backup piece incomplete"
// *Cause: An end of volume (EOV) condition was detected while duplexing to
// sequential files, and this condition cannot be handled currently.
// *Action: Before retrying the backup, make sure the backup pieces will fit in
// the volume, or disable duplexing.
19579, 00000, "archived log record for %s not found"
// *Cause: No archived log record corresponding to input file could be
// found in the control file.
// *Action: Specify a valid archived log file name and retry the operation.
19580, 00000, "%s conversation not active"
// *Cause: A backup or restore operation was attempted before a conversation
// was started.
// *Action: Start a conversation then retry the operation.
19581, 00000, "no files have been named"
// *Cause: An attempt was made to proceed from the file naming phase to the
// piece processing phase of a backup or restore conversation
// before any files have been specified for backup or restore.
// *Action: Specify some files then retry the operation.
19582, 00000, "archived log file header validation for %s failed"
// *Cause: Archived log file header is corrupt and could not be validated.
// *Action: Provide a valid archived log file and retry the operation.
19583, 00000, "conversation terminated due to error"
// *Cause: An error occurred which forced the termination of the current
// backup or restore conversation.
// *Action: There should be other error messages to help identify the cause
// of the problem. Correct the error and begin another conversation.
19584, 00000, "file %s already in use"
// *Cause: The indicated file, which was specified as the target for a copy,
// restore, or delete operation is already in use by the database.
// *Action: Specify a different name and retry the operation.
19585, 00000, "premature end of volume on piece %s"
// *Cause: While creating the indicated backup piece, an end-of-volume
// condition was encountered before all of the backup set control
// data was written to the backup piece. This is most likely a media
// error, because the amount of backup set control data is very small
// in relation to the total amount of data in a backup set.
// *Action: Retry the piece with a larger piece of output media.
19586, 00000, "%s k-byte limit is too small to hold piece directory"
// *Cause: The user-specified limit for MAXPIECESIZE for this channel
// is not enough to hold the backup set control data.
// *Action: Allocate a channel specifying a larget valule for MAXPIECESIZE
// and retry the operation.
19587, 00000, "error occurred reading %s bytes at block number %s"
// *Cause: An error occurred while reading from a file.
// *Action: One or more other messages should be displayed to help pinpoint
// the cause of the error. Correct the error then retry the
// copy, backup, or restore operation.
19588, 00000, "%s RECID %s STAMP %s is no longer valid"
// *Cause: The indicated record has been marked as deleted.
// This indicates that the corresponding file has either been
// overwritten by another copy or restore, or that the copy was
// 'consumed' by a SWITCHTOCOPY operation.
// *Action: If you know the name of the file you wish to copy, then
// inspect it and then retry the copy specifying the new RECID.
19589, 00000, "%s is not a snapshot or backup control file"
// *Cause: The control file that is the source for a backup or copy operation
// is not a snapshot or backup control file.
// *Action: Specify the name of a snapshot or backup control file.
19590, 00000, "conversation already active"
// *Cause: You tried to begin a backup or restore conversation, but another
// conversation is already active in this session.
// *Action: Either continue the current conversation, or call BACKUPCANCEL or
// RESTORECANCEL to end the current conversation before starting a
// new one.
19591, 00000, "backup aborted because job time exceeded duration time"
// *Cause: You tried to backup with duration option and the time provided
// was not sufficient to complete the backup.
// *Action: Adjust the duration time and re-run the command. Or run the backup
// command without duration option.
19592, 00000, "wrong %s conversation type"
// *Cause: You attempted to specify a type of file to be backed-up or
// restored, but the current conversation cannot process this type
// of file. For example, you specified an archived log to be
// included in a datafile backup set. The specified file will
// not be included in the backup or restore operation.
// *Action: No action required - the conversation is still active, and
// more files can be specified.
19593, 00000, "datafile number %s already included as %s"
// *Cause: This datafile is already specified for inclusion in this
// backup or restore conversation.
// A backup or restore conversation may process only
// a single instance of a datafile.
// *Action: No action required - the conversation is still active, and
// more files can be specified.
19594, 00000, "control file already included as %s"
// *Cause: The control file is already specified for inclusion in this backup
// or restore conversation. A backup or restore conversation may
// process only a single instance of the control file.
// *Action: No action required - the conversation is still active, and
// more files can be specified.
19595, 00000, "archived log %s already included in backup conversation"
// *Cause: The indicated archived log has already been specified for inclusion
// in this backup conversation.
// *Action: No action required - the conversation is still active, and
// more files can be specified.
19596, 00000, "SPFILE already included"
// *Cause: The SPFILE is already specified for inclusion in this backup
// or restore conversation. A backup or restore conversation may
// process only a single instance of the SPFILE.
// *Action: No action required - the conversation is still active, and
// more files can be specified.
19597, 00000, "file %s block size %s does not match set block size of %s"
// *Cause: A file was specified for inclusion in a backup set but it has
// a logical block size different from the rest of the files in the
// backup set. All files in a backup set must have the same logical
// block size.
// *Action: Specify a file that has the same block size as the rest of the
// files in the backup set. The conversation is still active and
// more files can be specified.
19598, 00000, "can not backup SPFILE because the instance was not started with SPFILE"
// *Cause: A backup command requested a backup of the SPFILE, but no SPFILE
// was used to startup the instance.
// *Action: Create an SPFILE and re-start the instance using the SPFILE.
19599, 00000, "block number %s is corrupt in %s %s"
// *Cause: A corrupt block was found in a control file, archived log, or
// backup piece that
// is being read for a backup or copy. Corruption shall not be
// tolerated in control files, archived logs, or backup pieces.
// *Action: None. The copy or backup operation fails. Note that in the case of
// a backup set, the conversation is still active and the piece may
// be retried.
19600, 00000, "input file is %s %s (%s)"
// *Cause: This message identifies the input file for a failed copy operation.
// Both the file number and name (if the name has been determined)
// are shown. For a datafile, the file number refers to the
// datafile's absolute file number as shown in the DBA_DATA_FILES
// view.
// For a datafile copy, the file number refers to the copy's
// control file record number as shown in the RECID column of the
// V$DATAFILE_COPY view.
// For an archived log, the file number refers to the log's
// control file record number as shown in the RECID column of the
// V$ARCHIVED_LOG view.
// *Action: See other error message.
19601, 00000, "output file is %s %s (%s)"
// *Cause: This message identifies the output file for a failed copy
// operation. The fields are as described in message 19600. When
// creating a new datafile copy, its control file record number
// may not have been determined when the message is printed. In
// that case, the record number shown is zero.
// *Action: See other error message.
19602, 00000, "cannot backup or copy active file in NOARCHIVELOG mode"
// *Cause: You tried to copy or backup a file that was not closed cleanly,
// and the database was in NOARCHIVELOG mode. This is not allowed
// because when restored, the file will require redo application
// before it is usable, and redo is not currently being saved
// beyond the contents of the online redo logs.
// *Action: Take the tablespace offline clean or close the database and retry
// the copy or backup.
19603, 00000, "cannot backup or copy active file with KEEP .. UNRECOVERABLE option"
// *Cause: The user tried to copy or backup a file that was not closed cleanly,
// with KEEP .. UNRECOVERABLE option. This is not allowed
// because when restored, the file will require redo application
// before it is usable, and redo will not be saved because of
// KEEP .. UNRECOVERABLE option.
// *Action: Take the tablespace offline cleanly, or close the database and retry
// the copy or backup.
19604, 00000, "conversation file naming phase is over"
// *Cause: A call was made to specify a file to be backed up or restored after
// the first backup piece has been processed.
// *Action: You cannot specify more files to be processed during a backup or
// restore conversation after the first backup piece has been
// processed. If more files must be specified, you must begin
// a new conversation.
19605, 00000, "input file name must be specified"
// *Cause: The input file name was not specified for a control file copy
// operation.
// *Action: Specify an input file name and retry the operation.
19606, 00000, "Cannot copy or restore to snapshot control file"
// *Cause: A control file copy or restore operation specified the name of the
// snapshot control file as the output file. It is not permitted to
// overwrite the snapshot control file in this manner. Other
// methods are available to create the snapshot control file.
// *Action: Specify a different file name and retry the operation. If this
// is a restore, then the restore conversation remains active and
// more files may be specified.
19607, 00000, "%s is an active control file"
// *Cause: A control file copy, restore, or backup specified the name of a
// control file named in the INIT.ORA file as the input or output file.
// *Action: Specify a different file name and retry the operation. If this
// is a backup or restore conversation, then the conversation remains
// active and more files may be specified.
19608, 00000, "%s is not a backup piece"
// *Cause: The specified file is not a backup piece produced by the
// DBMS_BACKUP_RESTORE package. Either the first block of the
// backup piece is corrupt or this file is not a backup piece.
// *Action: Specify a different file name and retry the operation.
19609, 00000, "%s is from different backup set: stamp %s count %s"
// *Cause: The specified file is not from the backup set which is
// currently being processed. It is part of a different backup set.
// The identification of the set containing this piece is shown.
// *Action: Specify the correct backup piece and retry the operation.
19610, 00000, "directory block %s is corrupt"
// *Cause: The indicated directory block failed checksum validation.
// This backup piece is unusable.
// *Action: Supply another copy of the same backup piece, or terminate the
// restore conversation.
19611, 00000, "backup piece out of order. Expected %s but found %s"
// *Cause: This backup piece is out of sequence.
// *Action: Supply the correct backup piece.
19612, 00000, "datafile %s not restored due to %s"
// *Cause: The indicated file could not be restored, because all of its data
// blocks were not found in the backup piece.
// *Action: The restore conversation remains active, and the current piece
// must be re-processed. If the failure cannot be resolved by
// re-processing the current piece, then the restore conversation
// must be cancelled.
19613, 00000, "datafile %s not found in backup set"
// *Cause: The indicated file could not be restored, because it is not in
// this backup set. If the file number is zero, then this refers to
// the control file.
// *Action: This message is issued when the directory from the first backup
// piece is read and one or more files named for restoration were not
// found. The restore conversation is still active, but no data
// has been read and you must supply the first backup piece of
// a backup set that contains all of the requested files.
19614, 00000, "archived log thread %s sequence %s not found in backup set"
// *Cause: The indicated archived log file was named explicitly for
// restoration but is not contained in this backup set.
// *Action: This message is issued when the directory from the first backup
// piece is read and one or more files named for restoration were not
// found. The restore conversation is still active, but no data
// has been read and you must supply the first backup piece of
// a backup set that contains all of the requested files.
19615, 00000, "some files not found in backup set"
// *Cause: Some files that were specified for restoration were not found
// in the backup set directory. Message 19613 or 19614 is issued
// for each file that was not found.
// *Action: See the instructions for message 19613.
19616, 00000, "output file name must be specified if database not mounted"
// *Cause: A datafile restore specified no target file name, but the
// database is not mounted. The database must be mounted when no
// target file name is specified, so that the target file name
// can be obtained from the control file.
// *Action: The restore conversation remains active. If you wish to restore
// datafiles without their target file names, then mount the database
// before continuing. Otherwise, a target file name must be specified
// on all datafile restoration calls.
19617, 00000, "file %s contains different RESETLOGS data"
// *Cause: The indicated file contains RESETLOGS data which is different from
// the archived log files which are already included in the backup
// set. All archived log files in a backup set must have the same
// RESETLOGS data.
// *Action: The restore conversation remains active, and you may continue to
// specify archived log files for inclusion in the backup set.
19618, 00000, "cannot name files after RESTOREVALIDATE has been called"
// *Cause: A call was made to specify a file to restore from a backup set,
// but a previous call to RESTOREVALIDATE has already been made.
// *Action: You must cancel and restart the conversation if you wish to
// specify files to restore.
19619, 00000, "cannot call RESTOREVALIDATE after files have been named"
// *Cause: RESTOREVALIDATE was called after some files had already been
// specified for restoration.
// *Action: You must cancel and restart the conversation if you wish to
// call RESTOREVALIDATE.
19620, 00000, "%s is not of %s type"
// *Cause: When opening the file to be placed in a copy or backup set,
// to be inspected, or used as the target for
// an incremental restore, its header was not
// recognized as a valid file header for a file of the indicated
// type (datafile, archived log, or control file) belonging
// to the current database.
// *Action: The indicated file cannot be processed. Ensure that the correct
// files are being specified for the copy or backup operation.
19621, 00000, "archived log range has already been specified"
// *Cause: A range of logs has already been specified. Only one SCN range
// may be specified per conversation.
// *Action: The restore conversation remains active and more logs may be
// specified by thread and sequence number, if desired.
19622, 00000, "archived log thread %s sequence %s not restored due to %s"
// *Cause: The indicated file could not be restored, because all of its data
// blocks were not found in the backup piece.
// *Action: The restore conversation remains active, and the current piece
// must be re-processed. If the failure cannot be resolved by
// re-processing the current piece, then the restore conversation
// must be cancelled.
19623, 00000, "file %s is open"
// *Cause: A SWITCHTOCOPY operation specified a datafile copy whose parent
// datafile is open.
// *Action: Take the owning tablespace offline or close the database, then
// retry the operation.
19624, 00000, "operation failed, retry possible"
// *Cause: A backup, restore or image copy operation failed with an I/O
// error. If the source of the I/O error can be corrected, then
// the operation may be retried.
// *Action: This message is used by recovery manager to decide whether or not
// to retry the operation.
19625, 00000, "error identifying file %s"
// *Cause: A file specified as input to a copy or backup operation, or as
// the target for an incremental restore, could not be identified as
// an Oracle file. The file may have been deleted or moved so that it
// is no longer accessible to RMAN. An operating system-specific error
// accompanies this error to help pinpoint the problem.
// *Action: Specify a different file and retry the operation. If the problem
// file has simply been deleted or moved, you can run crosscheck to
// allow RMAN to update its metadata with the correct file status.
19626, 00000, "backup set type is %s - can not be processed by this conversation"
// *Cause: The data in the backup set is not compatible with the current
// conversation.
// *Action: Either supply the first piece from a backup set that matches
// the current conversation or start a new restore conversation which
// can process this backup set.
19627, 00000, "cannot read backup pieces during control file application"
// *Cause: This is a control file restore conversation, which is using the
// offline range information from one or more control files to update
// datafile checkpoint data. Backup sets are not used during this
// type of conversation.
// *Action: The conversation is still active and more control files may be
// applied.
19628, 00000, "invalid SCN range"
/ *Cause: The starting SCN for RESTOREREDOLOGRANGE is greater than the
// ending SCN.
// *Action: Specify a starting SCN which is less than or equal to the
// ending SCN.
19629, 00000, "no files in specified archived log SCN range"
// *Cause: This backup set contains no files in the specified range.
// *Action: Either supply a backup set that contains files in the correct
// range or start a new conversation and specify a range which will
// select some files from this backup set.
19630, 00000, "end of volume encountered while copying backup piece"
// *Cause: While copying a backup piece from the OS native file system to an
// output device, the output device encountered end-of-volume.
// *Action: The copy fails. This could happen if a tape was used which is
// not large enough to hold the entire backup piece.
19631, 00000, "archived log record contains no file name"
// *Cause: This archived log record represents a switch into an active log
// that took place without archiving its prior contents. The prior
// contents of the log file are lost.
// *Action: Specify the RECID of an archived log record that contains a file
// name. Fixed view v$archived_log can be used to examine the
// archived logs.
19632, 00000, "file name not found in control file"
// *Cause: The name passed to GETFNO was not found in the control file.
// *Action: Supply a valid file name.
19633, 00000, "control file record %s is out of sync with recovery catalog"
// *Cause: The control file record describing the file to be deleted in
// a call to DELETEBACKUPPIECE, DELETEDATAFILECOPY, PROXYDELETE or
// DELETEARCHIVEDLOG does not match the validation data supplied by
// recovery manager.
// *Action: contact Oracle support
19634, 00000, "file name required for this function"
// *Cause: The FNAME or HANDLE parameter was not specified for
// DELETEPIECE, DELETEDATAFILECOPY, DELETEREDOLOG or PROXYDELETE.
// *Action: Specify the FNAME or HANDLE parameter when calling these functions.
19635, 00000, "input and output file names are identical: %s"
// *Cause: Identical input and output file names were specified for a
// datafile copy operation.
// *Action: Specify an output file name which is different from the input
// file name.
19636, 00000, "archived log thread %s sequence %s already included"
// *Cause: The indicated archived log has already been specified for inclusion
// in this restore conversation. A restore conversation may process
// only one copy of any archived log.
// *Action: No action required - the conversation is still active, and
// more files can be specified.
19637, 00000, "BACKUPPIECECREATE requires file name when using DISK device"
// *Cause: The session device is currently allocated to disk, and so a file
// name is required.
// *Action: Supply a file name and retry the operation.
19638, 00000, "file %s is not current enough to apply this incremental backup"
// *Cause: The checkpoint of the target for this incremental backup
// is less than the start of the incremental backup. If this backup
// were applied, then any changes made between the datafile
// checkpoint and the start of the incremental backup could be lost.
// *Action: Supply a backup set that can be applied and retry the operation.
19639, 00000, "file %s is more current than this incremental backup"
// *Cause: The checkpoint of the target for this incremental backup is
// greater than or equal to the checkpoint of the file in the
// incremental backup set. This backup cannot advance the checkpoint
// of the target file, so there is no point in applying it.
// *Action: Supply a backup set that can be applied and retry the operation.
19640, 00000, "datafile checkpoint is SCN %s time %s"
// *Cause: This message identifies the datafile checkpoint for
// a datafile that was too old to take an incremental backup from,
// or the target of an incremental restore that could not be applied.
// *Action: See other error message.
19641, 00000, "backup datafile checkpoint is SCN %s time %s"
// *Cause: This message identifies the checkpoint of a datafile in an
// incremental backup set that could not be applied.
// *Action: See other error message.
19642, 00000, "start SCN of incremental backup is %s"
// *Cause: This message identifies the starting SCN
// of an incremental backup that could not be applied.
// *Action: See other error message.
19643, 00000, "datafile %s: incremental-start SCN is too recent"
// *Cause: The incremental-start SCN which was specified when starting an
// incremental datafile backup is greater than the datafile
// checkpoint SCN, which could cause some blocks to be missed.
// *Action: Specify a smaller incremental-start SCN.
19644, 00000, "datafile %s: incremental-start SCN is prior to RESETLOGS SCN %s"
// *Cause: The incremental-start SCN which was specified when starting an
// incremental datafile backup is less than the RESETLOGS SCN.
// *Action: Specify a larger incremental-start SCN.
19645, 00000, "datafile %s: incremental-start SCN is prior to creation SCN %s"
// *Cause: The incremental-start SCN which was specified when starting an
// incremental datafile backup is less than the datafile's
// creation SCN.
// *Action: Specify a larger incremental-start SCN.
19646, 00000, "cannot change size of datafile %s from %s to %s"
// *Cause: Restore needs to adjust the size of the file as indicated, but
// the file size adjustment failed.
// *Action: Examine the other messages which should be present to indicate
// the cause of the failure.
19647, 00000, "non-zero LEVEL cannot be specified when INCREMENTAL is FALSE"
// *Cause: BACKUPSETDATAFILE was called with a non-zero backup_level
// and a FALSE incremental indication.
// *Action: Either set incremental to TRUE or change backup_level to zero.
19648, 00000, "datafile %s: incremental-start SCN equals checkpoint SCN"
// *Cause: The incremental-start SCN which was specified when starting an
// incremental datafile backup is equal to the
// datafile's checkpoint SCN. Since an incremental backup can only
// be applied to a datafile whose checkpoint SCN is between the
// backup set incremental-start SCN (inclusive) and the backup set
// checkpoint SCN (exclusive), there is no datafile that this backup
// set could ever be applied to.
// *Action: Specify a smaller incremental-start SCN.
//
// NOTE that this message will usually only be encountered by the
// user while taking an incremental backup with Recovery Manager.
// Recovery Manager should intercept all usual cases of this error
// and simply ignore the incremental backup for this file. So, if
// you do encounter this error, please report it to Oracle Support.
19649, 00000, "offline-range record RECID %s STAMP %s not found in file %s"
// *Cause: APPLYOFFLINERANGE was called with a RECID/STAMP which was not
// found in the indicated control file. This probably means that the
// specified control file is no longer the same control file that
// Recovery Manager thinks it is.
// *Action: Specify the RECID/STAMP of a record that exists in the control file
// copy.
19650, 00000, "Offline-range record RECID %s STAMP %s in file %s has SCN %s"
// *Cause: This messages identifies the offline-clean SCN from the indicated
// offline-range record in the indicated file.
// *Action: See other error message.
19651, 00000, "cannot apply offline-range record to datafile %s: SCN mismatch"
// *Cause: APPLYOFFLINERANGE cannot apply an offline-range record to a
// target datafile unless the datafile's checkpoint SCN exactly
// matches the offline-clean SCN in the specified offline-range
// record.
// *Action: Specify an offline-range record whose offline-clean SCN matches
// the target datafile's checkpoint.
19652, 00000, "cannot apply offline-range record to datafile %s: file is fuzzy"
// *Cause: The target datafile for an APPLYOFFLINERANGE call is fuzzy.
// *Action: Specify a target datafile that is closed cleanly.
19653, 00000, "cannot switch to older file incarnation"
// *Cause: SWITCHTOCOPY was called with a datafile copy for a datafile that
// was dropped prior to the time this control file was backed up.
// *Action: Restore and mount an earlier control file. It is acceptable to use
// a control file that was backed up prior to the creation of the
// specified datafile.
19654, 00000, "must use backup control file to switch file incarnations"
// *Cause: This SWITCHTOCOPY operation is attempting to switch incarnations
// of a datafile, but the currently mounted control file is not a
// backup control file.
// *Action: Restore and mount a backup control file.
19655, 00000, "cannot switch to incarnation with different RESETLOGS data"
// *Cause: This SWITCHTOCOPY operation is attempting to switch to a datafile
// which comes from a different RESETLOGS version of the database.
// *Action: Either restore a backup control file that was taken from the same
// database version as the target datafile copy, or switch to a
// different datafile copy.
19656, 00000, "cannot backup, copy, or delete online log %s"
// *Cause: The indicated log file is an active log. You can only backup,
// copy, or delete archived logs.
// *Action: The indicated log file cannot be processed - select another file.
19657, 00000, "cannot inspect current datafile %s"
// *Cause: The file being inspected is already part of the currently mounted
// database.
// *Action: None - the file is already part of the database.
19658, 00000, "cannot inspect %s - file is from different RESETLOGS"
// *Cause: The RESETLOGS data in the log file being inspected does not match
// that in the currently mounted control file.
// *Action: The indicated file cannot be processed - inspect another file.
19659, 00000, "incremental restore would advance file %s past RESETLOGS"
// *Cause: This incremental backup cannot be applied to the specified
// datafile, because the datafile is from an earlier incarnation of
// the database, and its checkpoint would be advanced too far to be
// recoverable in the current incarnation of the database.
// *Action: This incremental cannot be applied to this datafile. If you wish
// to recover the file to the RESETLOGS SCN so that the database
// can be opened with the RESETLOGS option, then you must use redo-log
// recovery, not incremental restore, to continue recovering this
// file.
19660, 00000, "some files in the backup set could not be verified"
// *Cause: A restore conversation was made to verify all the files in a backup
// set, and the files which were printed in messages 19661 or 19662
// could not be verified because corrupt blocks for those files were
// found in the backup set.
// *Action: Unless the damage to the backup set can be repaired, the indicated
// files cannot be restored from this backup set.
19661, 00000, "datafile %s could not be verified"
// *Cause: Some data blocks for the indicated datafile were corrupt in the
// backup set.
// *Action: Unless the damage to the backup set can be repaired, the indicated
// datafile cannot be restored from this backup set.
19662, 00000, "archived log thread %s sequence %s could not be verified"
// *Cause: Some data blocks for the indicated archived log were corrupt in the
// backup set.
// *Action: Unless the damage to the backup set can be repaired, the indicated
// archived log cannot be restored from this backup set.
19663, 00000, "cannot apply current offline range to datafile %s"
// *Cause: An attempt was made to apply the current offline range to
// the specified datafile, but the datafile is either not current
// enough or is not at the correct SCN to apply the offline range.
// *Action: The datafile remains unchanged.
19664, 00000, "file type: %s, file name: %s"
// *Cause: This message is issued to identify the file which is the subject
// of an error.
// *Action: None - this is an informational message. There should be other
// Oracle messages explaining the cause of the error.
19665, 00000, "size %s in file header does not match actual file size of %s"
// *Cause: The size of the file as indicated in the file header does not match
// the true size of the file.
// The two differing sizes are shown in units of logical blocks.
// *Action: This file is not usable - it has most likely been truncated.
19666, 00000, "cannot do incremental restore of the control file"
// *Cause: The control file was included in an incremental restore conversation
// *Action: If you wish to restore the control file, you must do a full restore
// of the control file
19667, 00000, "cannot do incremental restore of datafile %s"
// *Cause: The backup of the datafile is a full backup
// *Action: If you wish to restore the datafile, you must do a full restore
// of the datafile
19668, 00000, "cannot do full restore of datafile %s"
// *Cause: The backup of the datafile is an incremental backup
// *Action: If you wish to restore the datafile, you must do an incremental
// restore of the datafile
19669, 00000, "proxy copy functions cannot be run on DISK channel"
// *Cause: A proxy copy procedure was called,
// but the device which is allocated to the current session has
// type DISK.
// *Action: Allocate a non-DISK channel and retry the operation. Note that
// proxy copy requires a 3rd-party media management software product
// that supports the this backup/restore feature.
19670, 00000, "file %s already being restored"
// *Cause: A proxy restore function has already named this file as a restore
// destination.
// *Action: Use a different file name. If this message occurs during a
// recovery manager job, then this is an internal error in recovery
// manager, and you should contact Oracle support.
19671, 00000, "media management software returned invalid proxy handle"
// *Cause: During a proxy backup or restore, the media management software
// returned an invalid file handle.
// *Action: This is an internal error in the media management software which
// is linked with Oracle to provide backup/restore services.
// Contact the media management software vendor.
19672, 00000, "media management software returned invalid file status"
// *Cause: During a proxy backup or restore, the media management software
// returned an invalid file status.
// *Action: This is an internal error in the media management software which
// is linked with Oracle to provide backup/restore services.
// Contact the media management software vendor.
19673, 00000, "error during proxy copy of file %s"
// *Cause: During a proxy backup or restore, an error occurred while
// copying this file, but other files may have been copied
// successfully.
// *Action: There should be other errors on the error stack which explain
// why the file could not be successfully copied.
19674, 00000, "file %s is already being backed up with proxy copy"
// *Cause: Recovery manager attempted to back up the specified file with
// proxy copy, but the file is already being backed up by another
// recovery manager job.
// *Action: Wait until the other recovery manager backup of this file is
// complete, then retry the backup.
19675, 00000, "file %s was modified during proxy copy"
// *Cause: A proxy backup of the specified file failed because the file was
// brought on-line or otherwise modified while the proxy backup was
// in progress. This file was off-line or read-only when the backup
// began, so the file was not put into hot-backup mode, therefore
// no modifications are permitted while the backup is in progress.
// *Action: Take another backup of this file.
19676, 00000, "one or more files failed during proxy backup or restore"
// *Cause: During a proxy backup or restore, errors were encountered while
// processing some files. The files for which no error messages are
// shown were processed successfully.
// *Action: Examine the messages regarding the specific files to determine
// the cause of the problems.
19677, 00000, "RMAN configuration name exceeds maximum length of %s"
// *Cause: The configuration name string exceeds maximum length.
// *Action: Supply a correct configuration name and retry the function.
19678, 00000, "RMAN configuration value exceeds maximum length of %s"
// *Cause: The configuration value string exceeds maximum length.
// *Action: Supply a correct configuration value and retry the operation.
19679, 00000, "RMAN configuration number %s is outside valid range of 1 through %s"
// *Cause: An invalid RMAN Configuration number was specified.
// *Action: Specify a correct datafile number and retry the operation.
19680, 00000, "some blocks not recovered. See trace file for details"
// *Cause: Some blocks are not recovered during block media recovery.
// *Action: See trace files for details of the problem.
19681, 00000, "block media recovery on control file not possible"
// *Cause: file number 0 specified in block media recovery
// *Action: check file number
19682, 00000, "file %s not in block media recovery context"
// *Cause: Internal error
// *Action:
19683, 00000, "real and backup block size of file %s are unequal"
// *Cause: block size changed between backup & real file
// *Action: use right backup
19684, 00000, "block media recovery failed because database is suspended"
// *Cause: Database is suspended, probably by an ALTER SYSTEM SUSPEND statement
// *Action: Execute ALTER SYSTEM RESUME then retry block media recovery
19685, 00000, "SPFILE could not be verified"
// *Cause: Some data blocks for the SPFILE were corrupt in the
// backup set.
// *Action: Unless the damage to the backup set can be repaired, the SPFILE
// cannot be restored from this backup set.
19686, 00000, "SPFILE not restored due to %s"
// *Cause: The indicated file could not be restored, because some of its data
// blocks were not found in the backup piece.
// *Action: Unless the damage to the backup set can be repaired, the SPFILE
// cannot be restored from this backup set.
19687, 00000, "SPFILE not found in backup set"
// *Cause: The SPFILE could not be restored, because it is not in this
// backup set.
// *Action: This message is issued when the directory from the first backup
// piece is read and one or more files named for restoration were not
// found in the piece.
// You must supply the first backup piece of a backup set that
// contains the requested file.
19688, 00000, "control file AUTOBACKUP format(%s) for %s does not have %F"
// *Cause: control file AUTOBACKUP format must contain %F for the device.
// *Action: Change control file format using RMAN command CONFIGURE CONTROLFILE
// BACKUP FORMAT FOR DEVICE TYPE <type> TO <format>.
19689, 00000, "cannot have more than one %F in control file AUTOBACKUP format(%0!s) for %1!s"
// *Cause: control file AUTOBACKUP format contains more than one %F for the
// device.
// *Action: Change control file format using RMAN command CONFIGURE CONTROLFILE
// BACKUP FORMAT FOR DEVICE TYPE <type> TO <format>.
19690, 00000, "backup piece release %s incompatible with Oracle release %s"
// *Cause: The backup piece was created by incompatible software.
// *Action: Either restart with a compatible software release or create another
// backup using the current release.
19691, 00000, "%s is from different database: id=%s, name=%s"
// *Cause: The database name or database id in backup piece header does not
// match the one in control file.
// *Action: Supply the correct backup piece belonging to this database.
19692, 00000, "missing creation stamp on piece %s"
// *Cause: The backup piece doesn't have information about creation stamp.
// *Action: Supply another backup piece which is created by oracle 9i or
// later version.
19693, 00000, "backup piece %s already included"
// *Cause: This backup piece was already specified for inclusion in the
// restore conversation. A restore conversation may process only
// a single instance of a backup piece.
// *Action: Remove the specified duplicate backup piece in restore steps
// and restart the conversation.
19694, 00000, "some changed blocks were not found in the change tracking file"
// *Cause: A backup or copy found that some changed blocks had not been
// recorded in the change tracking file. The details of which files
// and blocks are affected will be in an Oracle trace file.
// *Action: This indicates that there is a problem with the change tracking
// feature. Disable change tracking and re-start the backup.
19695, 00000, "fixed table X$KRBMSFT has not been populated"
// *Cause: This is an internal error. The fixed table X$KRBMAFT was not
// populated using the function DBMS_BACKUP_RESTORE.SEARCHFILES.
// *Action: Internal error - contact Oracle Customer Support.
19696, 00000, "control file not found in backup set"
// *Cause: The control file could not be restored because it is not in this
// backup set.
// *Action: This message is issued when the directory from the first backup
// piece is read and one or more files named for restoration were not
// found in the piece.
// You must supply the first backup piece of a backup set that
// contains the requested file.
19697, 00000, "standby control file not found in backup set"
// *Cause: The standby control file could not be restored because it is not
// in this backup set.
// *Action: This message is issued when the directory from the first backup
// piece is read and one or more files named for restoration were not
// found in the piece.
// You must supply the first backup piece of a backup set that
// contains the requested file.
19698, 00000, "%s is from different database: id=%s, db_name=%s"
// *Cause: Catalog failed because the database id in file header
// does not match the one in control file.
// *Action: Supply the correct file belonging to this database.
19699, 00000, "cannot make copies with compression enabled"
// *Cause: Datafile copies with compression are not supported.
// *Action: If the function DBMS_BACKUP_RESTORE.BACKUPPIECECREATE is called
// outside RMAN, then the incompatible values are being passed for
// the parameters DOCOMPRESS and IMAGCP. If this message occurs
// during an RMAN job, then this is an internal error in RMAN,
// and you should contact Oracle support.
/
/
/ 19700-19719: KRBI
/
/ **************************************************************************
/ * When adding new DBMS_BACKUP_RESTORE messages, you must decide if the *
/ * error is 'retryable' or not, and if so, add the message number to *
/ * the table in KRBRRE. *
/ **************************************************************************
19700, 00000, "device type exceeds maximum length of %s"
// *Cause: The device type indicated is invalid.
// *Action: Supply a correct device type and retry the allocation.
19701, 00000, "device name exceeds maximum length of %s"
// *Cause: The device name indicated is invalid.
// *Action: Supply a correct device name and retry the allocation.
19702, 00000, "device parameter exceeds maximum length of %s"
/ // *Cause: The device parameter exceeds the port-specific maximum length.
/ // *Action: Correct the parameter and retry the operation.
19703, 00000, "device command string exceeds maximum length of %s"
// *Cause: The device command string exceeds maximum length.
// *Action: Correct the command and retry the operation.
19704, 00000, "file name exceeds maximum length of %s"
// *Cause: The specified file name, which was a parameter to a copy, backup,
// or restore operation, exceeds the maximum file name length for
// this operating system.
// *Action: Retry the operation with a shorter file name.
19705, 00000, "tag value exceeds maximum length of %s characters"
// *Cause: During a backup or copy operation, the user supplied a tag
// value too long to fit in the file header.
// *Action: Supply a shorter tag and retry the operation.
19706, 00000, "invalid SCN"
// *Cause: The input SCN is either not a positive integer or too large.
// *Action: Check the input SCN and make sure it is a valid SCN.
19707, 00000, "invalid record block number - %s "
// *Cause: The input number is either negative or too large.
// *Action: Check the input record block number and make sure it is a valid
// number
// clauses in the create database statement.
19708, 00000, "log destination exceeds maximum length of %s characters"
// *Cause: When starting a restore conversation, the user specified a log
// restore destination longer than the port-specific maximum.
// *Action: Supply a shorter destination and retry the operation.
19709, 00000, "numeric parameter must be non-negative integer"
// *Cause: A numeric parameter to an DBMS_BACKUP_RESTORE procedure is
// negative or contains a fractional portion.
// *Action: Supply a valid numeric parameter.
19710, 00000, "unsupported character set %s"
// *Cause: When the target database is not mounted, RMAN sets the target
// database character set to the value specified in the users
// environment.
// *Action: Specify a valid character set in the environment. This is usually
// done via the NLS_LANG environment variable.
19711, 00000, "cannot use RENORMALIZEALLFILENAMES while database is open"
// *Cause: An attempt was made to re-normalize all the file names in the
// control file while the database is open.
// *Action: Close the database before using the RENORMALIZEALLFILENAMES
// procedure.
19712, 00000, "table name exceeds maximum length of %s"
// *Cause: The table name string exceeds maximum length.
// *Action: Retry the operation with a shorter table name.
19713, 00000, "invalid copy number: %s "
// *Cause: The copy number is not in a valid range or you have reached
// maximum limit.
// *Action: Report the error and other information to support.
19714, 00000, "length for generated name longer than %s"
// *Cause: The specified format exceeds the maximum length for the piece name.
// *Action: Change the format to create shorter piece names.
19715, 00000, "invalid format %s for generated name"
// *Cause: A restricted format or undefined format was used incorrectly.
// *Action: Change the format specified in the additional information
// by removing the restricted format.
19716, 00000, "error processing format %s to generate name for backup"
// *Cause: There were errors while processing the format to generate
// name for backup.
// *Action: Change the format.
19717, 00000, "for non-OMF search the pattern must be specified"
// *Cause: The procedure DBMS_BACKUP_RESTORE.SEARCHFILES was called with
// an empty pattern while the parameter OMF was set to FALSE.
// *Action: Either specify the pattern or set the parameter OMF to TRUE.
19718, 00000, "length for command id longer than %s"
// *Cause: The specified command id exceeds the maximum length for command id.
// *Action: Supply a shorter command id and retry the operation.
19719, 00000, "length for operation name longer than %s"
// *Cause: The specified operation name exceeds the maximum length for
// operation name.
// *Action: Supply a shorter operation name and retry the operation.
/
/ 19720 - 19739 reserved for Transportable tablespace kernel errors
/
/
19720, 00000, "Error occurred when converting an OCI number into an SCN"
// *Cause: This is most likely caused by an invalid SCN number that came
// from an external file, such as an export file.
// *Action: See other errors on the error stack to look for the source
// of the problem.
/
19721, 00000, "Cannot find datafile with absolute file number %s in tablespace %s"
// *Cause: Can not find one of the datafile that should be in the Pluggable
// Set.
// *Action: Make sure all datafiles are specified via import command line
// option or parameter files.
/
19722, 00000, "datafile %s is an incorrect version"
// *Cause: The datafile is an incorrect version. It contains either less or
// more changes then the desired version.
// *Action: Make sure the right datafiles are transported. Make sure the
// datafile is copied while its tablespace is read only.
/
19723, 00000, "Cannot recreate plugged in read-only datafile %s"
// *Cause: The datafile is plugged in read only. It can not recreated.
// *Action: Use ALTER DATABASE RENAME FILE command instead.
/
19724, 00000, "snapshot too old: snapshot time is before file %s plug-in time"
// *Cause: The snapshot SCN is before the SCN at which the referred datafile
// is plugged into the database.
// *Action: retry the query.
/
19725, 00000, "can not acquire plug-in enqueue"
// *Cause: There maybe another "ALTER DATABASE RESET COMPATIBILITY" command
// issued concurrently, preventing this process from acquiring
// the plug-in enqueue.
// *Action: retry the operation.
/
19726, 00000, "cannot plug data [%s] at level %s into database running at compatibility level %s"
// *Cause: Some of the data in the pluggable set requires a compatibility
// level higher than what is currently allowed by the database.
// The string in square bracket is the name of the compatibility
// type associated with the data.
// *Action: Raise the "compatible" init.ora parameter and retry the operation.
/
19727, 00000, "cannot plug data [%s] at level %s into database running Oracle %s"
// *Cause: Some of the data in the pluggable set requires a compatibility
// level higher than the release level of the Oracle executable.
// The string in square bracket is the name of the compatibility
// type associated with the data.
// *Action: Upgrade Oracle and retry the operation.
/
19728, 00000, "data object number conflict between table %s and partition %s in table %s"
// *Cause: The non-partitioned table has the same data object number as
// one of the partitions in the partitioned table. One can not
// exchange the table with the partition in this case.
// *Action: Use "alter table move partition" command to move the offending
// partition, so that the partition will get a new data object
// number. Retry the operation then.
/
19729, 00000, "File %s is not the initial version of the plugged in datafile"
// *Cause: The file is not the initial version of the plugged in datafile.
// *Action: Use the correct initial version of the plugged in datafile.
/
19730, 00000, "can not convert offline plugged-in datafile %s"
// *Cause: As part of making a tablespace read-write, we need to convert
// datafiles that are plugged in read-only. The file must be
// online.
// *Action: Online the datafile and retry the operation.
/
19731, 00000, "cannot apply change to unverified plugged-in datafile %s"
// *Cause: Recovery was not able to verify the referred datafile according
// to information in the control file. Before encountering this
// change vector for this file, somehow recovery did not
// encounter the file conversion redo that is supposed to verify
// the file. This may happen due to corrupted or incorrect
// control file used for media recovery.
// *Action: Use the correct control file and continue recovery.
/
19732, 00000, "incorrect number of datafiles for tablespace %s"
// *Cause: The number of datafiles in the export file for the referred
// tablespace is not the same as expected. This is most likely
// caused by a user editing the export file.
// *Action: Use the correct export file and retry the operation.
/
19733, 00000, "COMPATIBLE parameter needs to be %s or greater"
// *Cause: The COMPATIBLE initialization parameter is not high
// enough to allow the operation. Allowing the command would make
// the database incompatible with the release specified by the
// current COMPATIBLE parameter.
// *Action: Shutdown and startup with a higher compatibility setting.
/
19734, 00000, "wrong creation SCN - control file expects converted plugged-in datafile"
// *Cause: When a tablespace is plugged into a database, the tablespace is
// initially read-only. Oracle converts the header of the
// plugged-in datafiles (assign them a new creation SCN) when
// the tablespace is first made read-write. This error occurs
// when the creation SCN in the file header is different from the
// creation SCN in the control file, possibly because this is the
// initial version of plugged-in datafile.
// *Action: Either restore the converted datafile or continue recovering the
// datafile.
/
19735, 00000, "wrong creation SCN - control file expects initial plugged-in datafile"
// *Cause: When a tablespace is plugged into a database, the tablespace is
// initially read-only. Oracle converts the header of the
// plugged-in datafiles (assign them a new creation SCN) when
// the tablespace is first made read-write. This error occurs
// when the creation SCN in the file header is different from the
// creation SCN in the control file, possibly because this is the
// converted datafile.
// *Action: Either restore the initial version of the plugged-in datafile, or
// continue database recovery, which will recover the control file.
/
19736, 00000, "can not plug a tablespace into a database using a different national character set"
// *Cause: Oracle does not support plugging a tablespace into a database
// using a different national character set.
// *Action: Use import/export or unload/load to move data instead.
19737, 00000, "simulate read-only database connection to execute sql query"
// *Document: NO
// *Cause: Set on RMAN foreground connections when archiver was hung.
// *Action: Turn off plsql/sql statistics collection, obtaining the temp
// segment for sorting and grabbing the sequence number from disk.
/
19738, 00000, "cannot find language information for character set: '%s'"
// *Cause: The compatibility check failed because a character set name
// that was provided is not valid.
// *Action: Correct the character set name and retry.
/
/ 19740-19749: More KRBI errors
/
/
19740, 00000, "text is longer than %s"
// *Cause: The specified text exceeds the maximum length for text.
// *Action: Supply a shorter text and retry the operation.
19741, 00000, "%s exceeds maximum allowable length of %s for parameter '%s'"
// *Cause: The specified string exceeds the maximum allowable length for
// the parameter
// *Action: Supply a shorter string for the parameter and retry the operation.
19742, 00000, "control file is not a backup control file"
// *Cause: This parameter could not be set because the control file was not
// a backup control file.
// *Action: Do not use this call for this control file.
19743, 00000, "could not unmount volume %s:%s"
// *Cause: The specified server and volume combination was not found and could
// not be unmounted.
// *Action: Specify the server and volume name correctly to complete the
// operation successfully.
19744, 00000, "Volume %s:%s is currently in use and cannot be unmounted."
// *Cause: The specified volume could not be unmounted because it was in use
// and had open files.
// *Action: Retry the unmount after all open files in the volume
// have been closed.
/
/
/ 19750 - 19799 reserved for Block Change Tracking
/
19750, 00000, "change tracking file: '%s'"
// *Cause: This message reports the name of a file involved in other messages.
// *Action: See associated error messages for a description of the problem.
19751, 00000, "could not create the change tracking file"
// *Cause: It was not possible to create the change tracking file.
// *Action: Check that there is sufficient disk space and no conflicts in
// file names and try to enable block change tracking again.
19752, 00000, "block change tracking is already enabled"
// *Cause: The ALTER DATABASE ENABLE BLOCK CHANGE TRACKING command was issued,
// but block change tracking is already turned on for this database.
// *Action: None, this is an informative message only.
19753, 00000, "error writing to change tracking file"
// *Cause: An I/O error occurred while writing to the change tracking file.
// *Action: There will be other messages on the error stack that show
// details of the problem.
19754, 00000, "error reading from change tracking file"
// *Cause: An I/O error occurred while reading from the change tracking file.
// *Action: There will be other messages on the error stack that show
// details of the problem.
19755, 00000, "could not open change tracking file"
// *Cause: The change tracking file could not be opened.
// *Action: There will be other messages on the error stack that show
// details of the problem.
19756, 00000, "corrupt block number %s found in change tracking file"
// *Cause: The specified block number is corrupt in the change tracking file.
// *Action: There will be other messages on the error stack that show
// details of the problem. There will also be a trace file that
// contains a complete dump of the corrupt block.
19757, 00000, "could not resize change tracking file to %s blocks"
// *Cause: An error occurred while trying to change the size of the change
// tracking file.
// *Action: There will be other messages on the error stack that show
// details of the problem.
19758, 00000, "failed to enable/disable block change tracking: out of SGA memory"
// *Cause: out of SGA memory
// *Action: Increase SGA and restart the instance.
19759, 00000, "block change tracking is not enabled"
// *Cause: A command was entered that requires block change tracking to be
// enabled, but block change tracking is not enabled.
// *Action: None, this is an informative message only.
19760, 00000, "error starting change tracking"
// *Cause: Change tracking is enabled, but a problem was encountered while
// enabling the change tracking subsystem in this instance.
// The alert log and the trace file from the CTWR process will
// contain more information about the error.
// *Action: Examine the trace and alert files. Correct the error if possible,
// otherwise disable change tracking.
19761, 00000, "block size %s is not valid for change tracking file"
// *Cause: While opening the specified change tracking file, it was found that
// the file header did not contain a valid logical block size. This
// probably means that the file is corrupt.
// *Action: If the file can be repaired, do so, otherwise disable and re-enable
// change tracking to re-initialize the file.
19762, 00000, "invalid file type %s"
// *Cause: An invalid file type was found in the change tracking file.
// Some other file was put in place of the change tracking file, or
// the file is corrupt.
// *Action: Disable then re-enable change tracking.
19763, 00000, "compatibility version %s is higher than maximum allowed: %s"
// *Cause: The compatibility version in the change tracking file is greater
// than what can be used by the current release of Oracle.
// This can happen when you upgrade, use change tracking with a new
// release, then downgrade.
// *Action: Disable then re-enable change tracking.
19764, 00000, "database id %s does not match database id %s in control file"
// *Cause: The change tracking file is not the correct one for this database.
// This can happen when the database ID for this database has been
// changed.
// *Action: Disable then re-enable change tracking.
19765, 00000, "mount id %s does not match mount id %s in control file"
// *Cause: The change tracking file does not match the one that was present
// when this instance was opened. In RAC, this error is most likely
// caused by having a change tracking file that cannot be
// consistently updated by all instances.
// *Action: In RAC, ensure that the name specified for the change tracking
// file truly represents the same disk location for all nodes in
// the cluster. Disable then re-enable change tracking.
19766, 00000, "missing CHANGE keyword"
// *Cause: Syntax error.
// *Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING
19767, 00000, "missing TRACKING keyword"
// *Cause: Syntax error.
// *Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING
19768, 00000, "USING clause only valid with ENABLE CHANGE TRACKING"
// *Cause: The USING clause was specified with DISABLE CHANGE TRACKING
// *Action: Correct the statement.
19769, 00000, "missing FILE keyword"
// *Cause: Syntax error.
// *Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING
19770, 00000, "invalid change tracking file name"
// *Cause: The USING clause was specified with ALTER DATABASE ENABLE
// BLOCK CHANGE TRACKING, but no file name was given.
// *Action: Specify the change tracking file name, or omit the USING clause
// to allow Oracle to create a default name for the change tracking
// file.
19771, 00000, "cannot rename change tracking file while database is open"
// *Cause: The ALTER DATABASE RENAME FILE command was used to rename the
// change tracking file, and the database is open by one or more
// instances. The database must be mounted, and not open, to
// rename the change tracking file.
// *Action: Close the database and reissue the command.
19772, 00000, "change tracking file name exceeds limit of %s characters"
// *Cause: The name specified for the change tracking file is too long.
// *Action: Specify a shorter change tracking file name.
19773, 00000, "must specify change tracking file name"
// *Cause: No file name was specified with the ALTER DATABASE ENABLE
// CHANGE TRACKING command, and the DB_CREATE_FILE_DEST parameter
// was not set.
// *Action: Either specify a file name, or set the DB_CREATE_FILE_DEST
// parameter.
/
// Do not use messages 19774 and 19775. They are KRC events.
/
19776, 00000, "PROXY restore to ASM disk group \"%s\" is not supported."
// *Cause: An attempt was made to proxy restore a file to ASM disk group
// using RMAN command. This is not supported.
// *Action: Use a different file name and reissue RMAN command.
19777, 00000, "ASM file %s cannot be proxy backed up."
// *Cause: An attempt was made to proxy backup a ASM file. This is not
// supported.
// *Action: Use a different file name and reissue RMAN command.
19778, 00000, "event to be in hot backup mode for given seconds"
// *Document: NO
// *Cause: N/A
// *Action: Set to test shutdown during proxy backup
19779, 00000, "could not obtain resilvering status for change tracking file"
// *Cause: An error occurred while obtaining the mirror resilvering status
// of the change tracking file.
// *Action: Refer to other error messages shown for additional details of
// the problem.
19780, 00000, "Active Data Guard option not enabled"
// *Cause: Change tracking at a standby database required the Active Data
// Guard option.
// *Action: Enable the Active Data Guard option.
19781, 00000, "The PROXY option is not supported on sparse file %s"
// *Cause: The PROXY option was used with a sparse file.
// This is not supported.
// *Action: Do not use the PROXY option with sparse files.
/
/19800 - 19829: Reserved for Recovery Area
/
/
19800, 00000, "Unable to initialize Oracle Managed Destination"
// *Cause: The name given for an Oracle managed files destination
// cannot be initialized.
// *Action: Check previous error messages for the reason Oracle
// was unable to initialize destination. Take corrective
// action, if possible, and retry the command or use a
// different name for destination.
19801, 00000, "initialization parameter DB_RECOVERY_FILE_DEST is not set"
// *Cause: An attempt was made to create a file in DB_RECOVERY_FILE_DEST
// when DB_RECOVERY_FILE_DEST was not set. There are number of
// possible causes of this error, including:
// 1) A LOG_ARCHIVE_DEST_n parameter was specified using a
// LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and
// an archived log file creation was attempted.
// 2) STANDBY_ARCHIVE_DEST parameter was specified using a
// LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and
// an archived log file creation was attempted.
// *Action: Specify a valid destination for DB_RECOVERY_FILE_DEST in
// initialization parameter file or with the ALTER SYSTEM SET
// command.
19802, 00000, "cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE"
// *Cause: There are two possible cause for this error:
// 1) The DB_RECOVERY_FILE_DEST parameter was in use when no
// DB_RECOVERY_FILE_DEST_SIZE parameter was encountered while
// fetching initialization parameter.
// 2) An attempt was made to set DB_RECOVERY_FILE_DEST with the
// ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST_SIZE
// was in use.
// *Action: Correct the dependency parameter definitions and retry the command.
19803, 00000, "Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - %s)"
// *Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid.
// *Action: Specify a valid number within the range.
19804, 00000, "cannot reclaim %s bytes disk space from %s bytes limit"
// *Cause: Oracle cannot reclaim disk space of specified bytes from the
// DB_RECOVERY_FILE_DEST_SIZE limit.
// *Action: There are five possible solutions:
// 1) Take frequent backup of recovery area using RMAN.
// 2) Consider changing RMAN retention policy.
// 3) Consider changing RMAN archived log deletion policy.
// 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.
// 5) Delete files from recovery area using RMAN.
19805, 00000, "RECID %s of %s was deleted to reclaim disk space"
// *Cause: The file described by the record in control file was deleted
// in order to reclaim disk space from recovery area for
// other operations.
// *Action: Wait and try again.
19806, 00000, "cannot make duplex backups in recovery area"
// *Cause: Duplex backup to recovery area is not supported.
// *Action: Remove duplex option and try again.
19808, 00000, "recovery destination parameter mismatch"
// *Cause: The value of parameters DB_RECOVERY_FILE_DEST and
// DB_RECOVERY_FILE_DEST_SIZE must be same in all instances.
// instance. All databases must have same recovery destination
// parameters.
// *Action: Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE
// values in all instances.
19809, 00000, "limit exceeded for recovery files"
//*Cause: The limit for recovery files specified by the
// DB_RECOVERY_FILE_DEST_SIZE was exceeded.
// *Action: There are five possible solutions:
// 1) Take frequent backup of recovery area using RMAN.
// 2) Consider changing RMAN retention policy.
// 3) Consider changing RMAN archived log deletion policy.
// 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.
// 5) Delete files from recovery area using RMAN.
19810, 00000, "Cannot create temporary control file %s in DB_RECOVERY_FILE_DEST"
// *Cause: An attempt was made to create a control file for a temporary purpose
// in DB_RECOVERY_FILE_DEST.
// *Action: Retry the operation with a new file name.
19811, 00000, "cannot have files in DB_RECOVERY_FILE_DEST with keep attributes"
// *Cause: An attempt was made to
// 1) Create a backup piece or image copy in the recovery area with
// KEEP option.
// 2) Update the KEEP attributes of an existing backup piece or
// image copy in the recovery area.
// *Action: Reissue RMAN command without KEEP options.
19812, 00000, "cannot use %s without DB_RECOVERY_FILE_DEST"
// *Cause: There are three possible cause for this error:
// 1) The indicated parameter was in use when no
// DB_RECOVERY_FILE_DEST parameter was encountered while
// fetching the initialization parameter.
// 2) An attempt was made to set indicated the parameter with
// the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST
// was in use.
// 3) An attempt was made to clear DB_RECOVERY_FILE_DEST with
// the ALTER SYSTEM command when the indicated parameter
// was in use.
// *Action: Eliminate any incompatible parameter definitions.
19813, 00000, "cannot have unavailable file %s in DB_RECOVERY_FILE_DEST"
// *Cause: An attempt was made to change a backup piece or image copy in
// recovery area to UNAVAILABLE.
// *Action: Correct and resubmit the RMAN command.
// Do not use messages 19814; it is used for simulating crash.
19815, 00000, "WARNING: %s of %s bytes is %s%% used, and has %s remaining bytes available."
// *Cause: DB_RECOVERY_FILE_DEST is running out of disk space.
// *Action: One of the following:
// 1. Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.
// 2. Backup files to tertiary device using RMAN.
// 3. Consider changing RMAN retention policy.
// 4. Consider changing RMAN archived log deletion policy.
// 5. Delete files from recovery area using RMAN.
19816, 00000, "WARNING: Files may exist in %s that are not known to database."
// *Cause: One of the following events caused this:
// 1. A database crash happened during file creation.
// 2. A backup control file was restored.
// 3. The control file was re-created.
// 4. DB_RECOVERY_FILE_DEST has previously been enabled and then disabled.
// *Action: Use RMAN command CATALOG RECOVERY AREA to re-catalog any such
// files. If the file header is corrupted, then delete those files
// using an OS utility.
// Do not use messages 19817; it is used for simulating lock failure
// Do not use messages 19818; it is used for space reclamation before backup
// Do not use messages 19819; it is used to disable clearing file name
19820, 00000, "database must be in NOARCHIVELOG mode to disable logging"
// *Cause: Logging was disabled when ARCHIVELOG mode was used.
// *Action: Execute ALTER DATABASE NOARCHIVELOG in mount state.
19821, 00000, "an intentionally corrupt log file was found"
// *Cause: A log file that was intentionally corrupt for testing or
// benchmarking purposes was found and failed the operation.
// *Action: Remove such log files and retry or use the NOARCHIVELOG option
// if possible.
19822, 00000, "mmon recovery area usage monitoring interval"
// *Document: NO
// *Cause: Set on all instances to change recovery area usage monitoring
// interval.
// *Action: level 1 - once every 15 minutes.
// level 2 - once every 30 minutes.
// ...
// level n - once every n * 15 minutes.
19823, 00000, "soft limit recovery area space pressure percentage"
// *Document: NO
// *Cause: Set on all instances to alter recovery area space pressure
// trigger percentage.
// *Action: level 1 to 100 indicates the percentage when the space
// pressure has to be triggered.
19824, 00000, "amount of space in MB to be reclaimed on archiver IO error"
// *Document: NO
// *Cause: Set on all instances to alter recovery area reclaimation space
// on archiver IO error.
// *Action: level indicates the amount in MB.
19825, 00000, "recovery area test event level %s"
// *Document: NO
// *Cause: Event set to test various recovery area error conditions.
// *Action: None.
19826, 00000, "Continue backup in case of dropped pdb test event level %s"
// *Document: NO
// *Cause: set to test backup continuation in case of a dropped pdb.
// *Action: level is the num of seconds to sleep after backup start in krbbbdr().
19827, 00000, "Restoring preplugin files to a recovery area is not supported."
// *Cause: An attempt to resore a preplugin file in a recovery area failed.
// This is not supported.
// *Action: Use the SET ARCHVIELOG DESTINATION RMAN command to specify an
// archivelog destination and retry the RESTORE or RECOVER command.
19828, 00000, "suspend a backup or rekey process for some time"
// *Document: NO
// *Cause: Set to test backup continuation in case of a moved or
// rekeyed data file.
// *Action: Level is the num of seconds to sleep.
19829, 00000, "Skip block #1 for all of the files in the backup test event"
// *Document: NO
// *Cause: N/A
// *Action: Test event used to skip block #1 for all of the files in a
// backup to test the duplicate blocks written at the end
/
/
/
/ 19830 - 19835: reserved for SQL Engine Errors:
/
19830, 00000, "error from target database: \n%s"
// *Cause: This error should be followed by other errors indicating
// the cause of the problem.
// *Action: No action required.
19831, 00000, "incompatible %s.%s.%s.%s DBMS_BACKUP_RESTORE package: %s.%s.%s.%s required"
// *Cause: This version of database was incompatible with the the indicated
// DBMS_BACKUP_RESTORE package installed in the database.
// *Action: If the database has been upgraded from an earlier version, ensure
// that the catxxxx.sql script has been run successfully.
// Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary.
/
/19836 - 19850: General purpose. First free message=19849
/
19836, 00000, "cannot use passphrase encryption for this backup"
// *Cause: Passphrase encryption was attempted for a backup that
// contains encrypted tablespaces and uses compression.
// *Action: Do not use passphrase encryption for this backup.
// Use transparent wallet-based encryption instead.
19837, 00000, "invalid blocksize %s in backup piece header"
// *Cause: The blocksize of the backup piece obtained from the header was
// invalid.
// *Action: The backup piece is corrupted, a different backup piece should
// be used for restore.
19838, 00000, "cannot use this control file to mount or open database"
// *Cause: This control file was restored by a DUPLICATE operation used only
// to restore and recover the data files of the new database. It is
// not meant to be used for mounting or opening the database,
// as allowing so might corrupt data files or online redo logs of
// the target database or both.
// *Action: Re-create the control file manually specifying all of the names of
// the data files and online redo logs. Do not forget to use NID to
// change the name or DBID or both of the new database.
19839, 00000, "snapshot datafile checkpoint time is greater than snapshot time"
// *Cause: The snapshot time which was specified when starting the recovery
// less than data file's checkpoint time. The snapshot recovery
// is only possible with data file's whose checkpoint time is less
// than snapshot time.
// *Action: Restore the data file's associated for the specified snapshot time
// or specify the correct snapshot time associated with the data file.
19840, 00000, "SNAPSHOT TIME recovery is not enabled"
// *Cause: An attempt was made to use SNAPSHOT TIME recovery. But, the
// feature was not enabled.
// *Action: Contact Oracle Support Services to enable snapshot time recovery
// and then retry the command.
19841, 00000, "Cross-platform backups require COMPATIBLE %s or greater"
// *Cause: An attempt to create a cross-platform backup was made but the
// COMPATIBLE parameter was not set to a high enough value to
// allow this.
// *Action: Do not attempt to use this functionality or raise the
// compatibility level.
19842, 00000, "The current database incarnation changed during backup"
// *Cause: The backup failed because the current database incarnation was
// changed during the backup.
// One of the following events caused this incarnation change:
// - The database was opened using ALTER DATABASE OPEN RESETLOGS
// statement.
// - RMAN command RESET DATABASE TO INCARNATION was issued.
// - If this happened on physical standby database, then redo apply
// has applied redo data from a new database incarnation.
// *Action: Retry the backup.
19843, 00000, "Cannot obtain datafile name for datafile %s"
// *Cause: While trying to obtain the file enqueue for the datafile the
// datafile name could not be obtained.
// *Action: Examine the trace and alert files for possible causes.
// Fix underlying problem before attempting command again.
19844, 00000, "database ID is from different database: ID=%s"
// *Cause: The database ID on the remote site did not match the ID of
// the target database. This is most likely caused by a wrong
// service name for the remote connection.
// *Action: Supply the correct service name and retry the command.
19845, 00000, "error in %s while communicating with remote database server"
// *Cause: An error occurred while initiating backup on remote database
// server for network restore. Additional error messages will be
// issued to describe the failure.
// *Action: Check additional error messages.
19846, 00000, "cannot read header of datafile %s from remote site"
// *Cause: Unable to read the file header from remote site.
// *Action: Make sure the data file is accessible on remote site and retry
// the command.
19847, 00000, "cannot read header of control file from remote site"
// *Cause: Could not read the control file header from the remote site.
// *Action: Make sure the database is mounted on the remote site and retry
// the command.
19848, 00000, "cross-platform backup piece requires COMPATIBLE %s or greater"
// *Cause: An attempt was made to perform a cross-platform operation from
// a backup piece created with a higher compatibility than the
// current COMPATIBLE parameter.
// *Action: Raise the compatibility level or do not attempt a cross-platform
// restore from this backup piece.
19849, 00000, "error while reading backup piece from service %s"
// *Cause: This error should be followed by other errors indicating
// the cause of the problem.
// *Action: See other errors actions.
19850, 00000, "backup piece constructed from service %s is corrupt"
// *Cause: This error indicates that the backup piece that was constructed
// from the service is corrupt.
// *Action: See alert log for details of the corruption. Fix the corruption
// and retry the command.
/
/19851 - 19859: Reserved for Auxiliary instance
/
19851, 00000, "OS error while managing auxiliary database %s"
// *Cause: An OS error was received while managing the automatic
// auxiliary instance.
// *Action: Check the accompanying errors.
19852, 00000, "error creating services for auxiliary instance %s (error %s)"
// *Cause: An error was received while managing the services
// of the auxiliary instance.
// *Action: Check the accompanying errors.
19853, 00000, "error preparing auxiliary instance %s (error %s)"
// *Cause: An error was received while managing the automatic
// auxiliary instance.
// *Action: Check the accompanying errors.
19854, 00000, "error obtaining connect string from target"
// *Cause: Could not obtain the connect string from the target database
// *Action: Check the accompanying errors.
19855, 00000, "cannot use clone mounted control file to drop database"
// *Cause: The clone mounted control file could not be used to drop
// the database because the names of the data files and online logs
// were not fixed using the RMAN DUPLICATE command.
// This could cause the original database files to be lost.
// *Action: Manually drop the database.
/
/
/ 19860 - 19879 reserved for Additional KRB* errors
/
19860, 00000, "piece validation cannot be performed more than once"
// *Cause: The user attempted to validate a list of backup pieces
// more than once. Validation may only be performed once for
// a given validation conversation.
// *Action: Do not attempt to validate the pieces more than once.
19861, 00000, "additional backup pieces cannot be validated in this conversation"
// *Cause: The user tried to add new pieces to the list of files
// being validated after the validation had already been
// performed. In a validation conversation, the list can
// only be validated once.
// *Action: Add all the backup pieces to the list before validating,
// or start a new validation conversation for the remaining pieces.
19862, 00000, "backup pieces must be validated before accessing results"
// *Cause: The user tried to get validation results for backup pieces before
// the pieces were actually validated.
// *Action: Validate the pieces before trying to access the results.
19863, 00000, "device block size %s is larger than max allowed: %s"
// *Cause: The user specified a device BLKSIZE that is larger than the device
// BLKSIZE specified during compressed backup.
// *Action: Change the device BLKSIZE to be smaller than the maximum allowed.
19864, 00000, "%s"
// *Cause:
// *Action:
19865, 00000, "Backup piece %s has no data"
// *Cause: No data was returned for the specified backup piece.
// *Action: This normally indicates a problem with the media management
// software which is linked with Oracle to provide backup and
// restore services.
// Contact the media management software vendor.
19866, 00000, "error writing file header for datafile %s"
// *Cause: During a block recovery, the header of the datafile could not
// be updated.
// *Action: Contact Oracle Support Services.
19867, 0000, "backup piece %s is from a different container identifier %s; data file %s"
// *Cause: This backup piece container identifier did not match the supplied
// data file container identifier.
// *Action: Retry the command with the correct backup piece or the correct
// data file.
19870, 00000, "error while restoring backup piece %s"
// *Cause: This error should be followed by other errors indicating
// the cause of the problem.
// *Action: See other errors actions.
/
// Do not use message 19871; it is used by RMAN client for testing previous
// resync time when using backup/standby control file.
//
19872, 00000, "Unexpected end of file at block %s while decompressing backup piece %s"
// *Cause While reading a compressed backup piece, RMAN received an
// end-of-file without finding the end-of-compression stream.
// *Action: This is most likely caused by a corrupted backup piece.
// Consider using a different backup piece for restore.
19873, 00000, "cannot apply this backup section to file %s"
// *Cause RMAN cannot restore a multi-section backup to the indicated
// file, because this section is not a backup of this file, or
// the file was not prepared correctly for this restore.
// *Action: If this error occurs while running RMAN, then it is an internal
// error and you should contact Oracle support.
19874, 00000, "cannot finish multisection restore or copy to file %s"
// *Cause: During a multisection restore or copy, the file being restored was
// not a file in which a multisection restore or copy was in progress.
// *Action: If this error occurs while running RMAN, then it was an internal
// error and you should contact Oracle Support Services.
19875, 00000, "multisection restore or copy not complete for file %s"
// *Cause: While completing a multisection restore or copy, it was found that
// all required sections for this file were not correctly applied.
// *Action: If this error occurs while running RMAN, then it is an internal
// error and you should contact Oracle Support Services.
19876, 00000, "Change tracking, test event for dynamic resizing"
// *Document: NO
// *Cause: N/A
// *Action: Test event used for dynamic resizing of dba public buffers
19877, 00000, "test event to check sizes of krbpd1[012], krbps, krbpa, krbpdmp"
// *Document: NO
// *Cause: N/A
// *Action: Test event used for checking sizes of internal backup structures
19878, 00000, "Restore failure on block number test event"
// *Document: NO
// *Cause: N/A
// *Action: Set to test restore failure
/
/ 19879 - 19879 : Reserved for testing events.
/
/ 19880 - 19885 reserved for optimized backups
/
19880, 00000, "Corrupted space header for datafile %s, block %s"
// *Cause: When reading the space header block to use Unused Block
// Optimization for the backup of the datafile, the space header
// block had corrupted information.
// *Action: The corrupt space header must be fixed before Unused Block
// Optimization can be used for this file. Note that you should
// fix the corruption in any case because it will affect the
// availability of the data in the file, beyond just taking
// backups.
19881, 00000, "Corrupted space bitmap for datafile %s, block %s"
// *Cause: When reading a space bitmap block to use Unused Block
// Optimization for the backup of the datafile, the space bitmap
// block had corrupted information.
// *Action: The corrupt space bitmap must be fixed before Unused Block
// Optimization can be used for this file. Note that you should
// fix the corruption in any case because it will affect the
// availability of the data in the file, beyond just taking
// backups.
19882, 00000, "datafile %s checkpoint %s is ahead of space bitmap datafile %s checkpoint %s"
// *Cause: When checkpointing the datafile containing the space bitmaps
// for the datafile being backed up in order to use Unused Block
// Optimization, the checkpoint of the datafile containing the
// space bitmaps did not advance.
// *Action: Examine the trace and alert files for possible causes.
// Fix underlying problem to use Unused Block Optimization
// for datafile's backup.
19883, 00000, "Unused Block Optimization stopped for data file %s"
// *Cause: Accompanying errors detail the problem that prevented
// Unused Block Optimization from being used.
// *Action: See accompanying errors for appropriate action.
19884, 00000, "datafile %s is unable to use Unused Block Optimization because tablespace has been dropped"
// *Cause: When attempting to find information about datafile that holds
// bitmaps of migrated tablespace, the tablespace was found to have
// been dropped.
// *Action: None. This is an informational message.
19886, 00000, "used for generic testing purposes"
// *Document: NO
// *Cause: For testing only.
// *Action: None.For testing only.Should never be set by customers.
// *Comment:
// level 1: Used for testing bug 13849436.
// level 2: Used to enable use of OOB while establising remote db
// conenction at network layer. By default rman do not use OOB for
// remote db connections. Refer bug 25971150.
/
/ 19899 - 19912 reserved for recovery through RESETLOGS project
/
19899, 00000, "missing incarnation information"
// *Cause: Media recovery stopped because information of one or more ancestor
// incarnations of recovery target incarnation was not available.
// *Action: Register logs from the missing incarnations and retry recovery.
19900, 00000, "RESETLOGS must be specified after recovery to new incarnation"
// *Cause: Recovery was done to an incarnation after changing the destination
// incarnation using RMAN's RESET DATABASE command.
// *Action: Open the database with the RESETLOGS option.
19901, 00000, "database needs more recovery to create new incarnation"
// *Cause: Recovery was done to an incarnation after changing the destination
// incarnation using RMAN's RESET DATABASE command, but one or more
// of the recovered datafiles still belongs to the parent incarnation.
// This usually happens when recovery is ended before any logs from
// the desired incarnation have been applied.
// *Action: Continue recovery.
19902, 00000, "incarnation key %s not found"
// *Cause: The specified incarnation was not found in the control file.
// *Action: Resubmit request with known incarnation key.
// To see which incarnations are available for this target database,
// query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION
// command.
19903, 00000, "test recovery not allowed when recovering to new incarnation"
// *Cause: Either a new incarnation was set using RMAN's RESET
// DATABASE command for a control file that was CURRENT, or the
// control file is from a prior incarnation. As recovery to
// a new incarnation requires changing the control file, test
// recovery is not allowed.
// *Action: Perform actual recovery or RESET DATABASE to incarnation
// that was last opened using the control file to do test recovery.
19904, 00000, "test recovery not allowed for datafile %s"
// *Cause: The specified datafile has been restored from a backup that was
// taken before the last RESETLOGS. Recovering this datafile will
// require a file header update that is incompatible with test
// recovery.
// *Action: Perform actual recovery.
19905, 00000, "log_archive_format must contain %%s, %%t and %%r"
// *Cause: log_archive_format is missing a mandatory format element.
// Starting with Oracle 10i, archived log file names must contain each
// of the elements %s(sequence), %t(thread), and %r(RESETLOGS ID) to
// ensure that all archived log file names are unique.
// *Action: Add the missing format elements to log_archive_format.
19906, 00000, "recovery target incarnation changed during recovery"
// *Cause: While a media recovery was active, a new incarnation was detected
// by the server due to inspection or cataloging of archived logs
// or backup files.
// *Action: If you want recovery to use the new incarnation, restart recovery.
// This is the most common action on a standby database when RESETLOGS
// is done in primary. If you do not want recovery to use the new
// incarnation,
// change the recovery destination using RMAN's RESET DATABASE
// TO INCARNATION <incarnation#> command.
// To see which incarnations are available for this target database,
// query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION
// command.
19907, 00000, "recovery time or SCN does not belong to recovered incarnation"
// *Cause: A point-in-time recovery to an SCN or time stamp prior to the last
// RESETLOGS was requested.
// *Action: Either change the specified recovery time/SCN, or
// change the recovery destination using RMAN's RESET DATABASE
// command.
19908, 00000, "datafile %s has invalid checkpoint"
// *Cause: The specified datafile has an invalid checkpoint.
// *Action: Restore the datafile from a backup.
19909, 00000, "datafile %s belongs to an orphan incarnation"
// *Cause: Either the specified datafile was restored from a backup that was
// taken during a period of time that has already been discarded by
// a RESETLOGS operation, or Oracle cannot identify which database
// incarnation the file belongs to. The alert log contains more
// information.
// *Action: Restore a backup of this file that belongs to either the current
// or a prior incarnation of the database. If you are using RMAN
// to restore, RMAN will automatically select a correct backup.
19910, 00000, "can not change recovery target incarnation in control file"
// *Cause: The RESET DATABASE TO INCARNATION command was used while the
// database is open. This is not allowed.
// *Action: Close the database then re-issue the command.
19911, 00000, "datafile %s contains future changes at the incarnation boundary"
// *Cause: The file did not hit end backup marker redo during recovery at
// the incarnation boundary, hence may contain changes discarded
// by new incarnation.
// *Action: Use older backup of the file and then re-issue the command.
19912, 00000, "cannot recover to target incarnation %s"
// *Cause: The control file is not in the recovery path of the target
// incarnation, and does not contain enough information as to how
// to recover to the target incarnation.
// *Action: Restore the latest control file from the target incarnation and
// retry.
/
/ 19913 - 19920 reserved for encrypted backups
/
19913, 00000, "unable to decrypt backup"
// *Cause: A backup piece could not be decrypted. This message is accompanied
// with another message that indicates the name of the encrypted
// backup that could not be restored. The reason could be either
// that an invalid password was entered, or that, when using
// transparent decryption, the database external security device
// is not open.
// *Action: If password-based restore was enabled for this backup,
// then supply the correct password using the RMAN SET DECRYPTION
// command. If transparent restore was enabled for this backup,
// then ensure that the database external security device is open.
19914, 00000, "unable to encrypt backup"
// *Cause: RMAN could not create an encrypted backup. This message will
// be accompanied by other messages that give more details about
// why the encrypted backup could not be created. The most common
// reason for this message is that you are trying to create a
// backup that can be transparently decrypted, and the database
// external security device is not open.
// *Action: If the external security device is not open, then open it.
// If the external security device is not configured, then the
// only type of encrypted backup that you can create is a
// password-based backup.
19915, 00000, "unable to encrypt pre-10.2 files"
// *Cause: An RMAN encrypted backup was requested, but this backup includes
// one or more archived logs that were generated by an older
// release of Oracle. These archived logs cannot be encrypted.
// *Action: Back up the older logs without encryption. Logs created with
// Oracle release 10.2 and greater can be encrypted.
19916, 00000, "%s"
// *Cause: An error occurred when processing user request.
// *Action:
// Do not use message 19917; it is used internally for testing purpose.
// Do not use message 19918; it is an internal event used by encryption.
19919, 00000, "encrypted backups to tertiary storage require Oracle Secure Backup"
// *Cause: RMAN was configured to create encrypted backups, but the channel
// is neither a DISK channel nor an Oracle Secure Backup channel.
// *Action: Allocate a DISK channel or an Oracle Secure Backup channel to
// use backup encryption.
19920, 00000, "RMAN does not support PKI-based master key for encryption."
// *Cause: An attempt was made to use Oracle public key infrastructure (PKI)
// based master key algorithm. RMAN only supports Advanced Encryption
// Standard (AES) based encryption.
// *Action: Use AES based encryption.
/
/19921 - 19925: KRB* errors
/
/
19921, 00000, "maximum number of %s rows exceeded"
// *Cause: The maximum number of rows in the V$RMAN_STATUS or V$RMAN_OUTPUT
// table has been exceeded.
// *Action: Close some of existing and unused RMAN connections and sessions.
19922, 00000, "there is no parent row with id %s and level %s"
// *Cause: RMAN tried to add a new V$RMAN_STATUS row, but the parent row
// did not exist.
// *Action: This is an internal error. Contact Oracle Support.
19923, 00000, "the session for row with id %s is not active"
// *Cause: RMAN tried to update an V$RMAN_STATUS row but the process which
// owns this row died.
// *Action: This is an internal error. Contact Oracle Support.
19924, 00000, "there are no row with id %s"
// *Cause: RMAN tried to update an V$RMAN_STATUS row, but the row don't exist.
// *Action: This is an internal error. Contact Oracle Support.
19925, 00000, "Internal error while cleaning memory used by V$RMAN_STATUS view"
// *Cause:
// *Action: This is an internal error. Contact Oracle Support.
/
/
/ 19926 - 19929: reserved for transport database errors
/
19926, 1, "Database cannot be converted at this time"
// *Cause: Another CONVERT DATABASE operation is already in progress.
// *Action: Retry CONVERT DATABASE command later.
19927, 1, "CONVERT DATABASE operation cannot proceed"
// *Cause: An error occurred earlier during CONVERT DATABASE operation.
// *Action: Retry CONVERT DATABASE command.
19928, 1, "CONVERT of data files with undo segments between different endian is not supported."
// *Cause: Conversion of data files with undo segments was not supported between endianess.
// The only time that data files with undo segments can be converted is between the
// same endianess as part of convert database. Convert database between different
// endian is not supported.
// *Action: Do not attempt to convert data files with undo segments between different endian.
19929, 100000, "no archive log registered"
// *Cause: An error occurred during ALTER DATABASE RECOVER with the FORCE
// START AT option because there were no archive logs registered in
// the control file covering the specified start SCN or time.
// *Action: Register archive logs covering the specified SCN or time.
/
/19930 - 19935: More KRB* errors
/
19930, 00000, "file %s has invalid checkpoint SCN %s"
// *Cause: When opening the file to be placed in a copy or backup set,
// to be inspected, the file header was not recognized as a valid
// header because it contained a invalid checkpoint SCN. The
// indicated file cannot be processed.
// *Action: Ensure that the correct files are being specified for the
// catalog or backup operation.
19931, 00000, "file %s has invalid creation SCN %s"
// *Cause: When opening the file to be placed in a copy or backup set,
// to be inspected, the file header was not recognized as a valid
// header because it contained a invalid creation SCN. The indicated
// file cannot be processed.
// *Action: Ensure that the correct files are being specified for the
// catalog or backup operation.
19932, 00000, "control file is not clone, standby or backup"
// *Cause: The operation failed because the control file was not mounted as
// clone, standby or backup.
// *Action: Mount the database as clone, standby or backup and retry.
19933, 00000, "catalog backup piece %s of data pump dump file is not supported"
// *Cause: This backup piece contained data pump dump file. Cataloging such
// a backup piece is not supported.
// *Action: Do not request to catalog data pump dump file backup piece.
19934, 00000, "cannot validate block 0"
// *Cause: An attempt was made to validate block 0 of a datafile.
// *Action: Do not specify block 0 for validation.
19935, 00000, "During the back up, the data file %s is deleted, or is moved or rekeyed to %s."
// CAUSE: The data file was deleted, moved, or rekeyed.
// ACTION: Check the status of the data file and try this command again.
/
/ 19936- 19949 reserved for cross-platform transpotable tablespace (xtts)
/
19936, 00000, "some tablespaces were not found in backup set"
// *Cause: Some tablespaces that were specified for restoration were not
// found in the backup set directory. Message 19937 is issued
// for each file that was not found.
// *Action: See the instructions for message 19937.
19937, 00000, "tablespace %s was not found in backup set"
// *Cause: The indicated tablespace could not be restored because it
// was not in this backup set.
// *Action: This message is issued when the directory from the first backup
// piece is read and one or more tablespaces named for restoration
// are not found. The restore conversation is still active, but
// no data has been read and you must supply the first backup
// piece of a backup set that contains all of the requested
// files or tablespaces or both.
19938, 00000, "Data Pump dump file backup requires COMPATIBLE %s or greater"
// *Cause: Data Pump dump file backup requested but COMPATIBLE did not
// allow it.
// *Action: Do not request dump file backup or set COMPATIBLE to minimum
// value and retry backup.
19939, 00000, "Data Pump dump file can only be included in a cross-platform backup"
// *Cause: Data Pump dump file backup requested but the backup conversation
// is not a cross-platform conversation.
// *Action: Start a new cross-platform backup conversation or do not include
// a Data Pump dump file.
19940, 00000, "cannot use cross-platform backups to convert whole database to different endianess"
// *Cause: Cross-platform backups or restores of whole database between
// different endianess was requested but it is not supported.
// *Action: Revise the specified platforms for conversion before retrying
// the command.
19941, 00000, "invalid blocksize in cross-platform datafile %s"
// *Cause: Blocksize in header of datafile copy being converted at target
// was invalid. Either datafile has not been made read/write
// with compatibility 10.0 or greater at source database or
// datafile copy is corrupted.
// *Action: Make a new datafile copy taken after tablespace has been made
// read/write with compatibility 10.0 at source database and retry
// conversion.
19942, 00000, "datafile copy %s not created with compatibility 10.0 or greater"
// *Cause: The specified datafile copy to be converted at the target was
// not produced after making the tablespace in read/write mode
// with compatibility 10.0 or greater at the source database.
// *Action: Make a new datafile copy taken after tablespace has been made
// read/write with compatibility 10.0 at source database and retry
// conversion.
19943, 00000, "Data Pump dump file not found in backup set"
// *Cause: The Data Pump dump file could not be restored because it was
// not in this backup set.
// *Action: This message is issued when the directory from the first backup
// piece is read and the Data Pump dump file is not found in the
// piece. You must supply the first backup piece of a backup set
// that contains the requested file.
19944, 00000, "Specified platform: '%s' does not match piece header platform: '%s'"
// *Cause: The backup piece did not belong to the platform specified in
// FROM PLATFORM.
// *Action: Retry the restore using the correct FROM PLATFORM or without
// specifying FROM PLATFORM at all.
19945, 00000, "file %s already included to be restored to %s"
// *Cause: This file was already specified for inclusion in this
// restore conversation. The restore conversation may process only
// a single instance of a datafile.
// *Action: No action required. The conversation is still active and
// more files can be specified.
19946, 00000, "Cannot determine block size of backup piece '%s' (%s)"
// *Cause: It was not possible to determine the cross-platform
// transportable backup piece block size.
// *Action: Contact Oracle Support Services.
19947, 00000, "Invalid block size %s in backup piece '%s' from specified platform '%s'"
// *Cause: The block size obtained from the backup piece using
// the specified platform was not valid. Either the piece is
// corrupted or the specified platform is incorrect.
// *Action: Retry the restore using the correct FROM PLATFORM clause.
19948, 00000, "Backup piece does not contain a cross-platform datafile backup, reason=%s"
// *Cause: A cross-platform transportable restore was specified but
// the backup piece was not produced with the correct command.
// *Action: Produce a cross-platform transportable backup piece by using
// BACKUP ... TO PLATFORM and retry the restore.
19949, 00000, "Specified platform: '%s' has different endianess than piece '%s', cannot read"
// *Cause: The backup piece had a different endianess than the platform
// specified in FROM PLATFORM.
// *Action: Retry the restore using the correct FROM PLATFORM or without
// specifying FROM PLATFORM at all.
19950, 00000, "tablespace %s already included to be restored"
// *Cause: This tablespace was already specified for inclusion in this
// restore conversation.
// *Action: No action required. The conversation is still active and
// more tablespaces or files or both can be specified. The restore
// conversation may process only a single instance of a tablespace.
/
/ 19951- 19960 reserved for NID
/
19951, 00000, "cannot modify control file until DBNEWID is completed"
// *Cause: An operation requiring to modify the control file was
// attempted, but a NID change is in progress.
// *Action: Wait until NID completes before attempting the operation.
19952, 00000, "database should be mounted exclusively"
// *Cause: The database was started in parallel mode. To change the DBID,
// the database must be mounted exclusively.
// *Action: Shut down the database and start it in exclusive mode.
19953, 00000, "database should not be open"
// *Cause: The database was open. To change the DBID, the database must be
// mounted exclusively.
// *Action: Shut down the database and mount it in exclusive mode.
19954, 00000, "control file is not current"
// *Cause: The operation failed because a non-current, non-standby control
// file was mounted.
// *Action: Make the control file current and retry.
19955, 00000, "only one open thread is allowed to change the DBID"
// *Cause: The operation failed because there were active threads in the
// database. The most likely cause is that the database crashed the
// last time it was shut down.
// *Action: Ensure that all threads are closed before retrying
// the operation. Start and open the database
// to perform crash recovery, then shut down with the NORMAL
// or IMMEDIATE options to close it cleanly. Finally, try running
// the utility again.
19956, 00000, "database should have no offline immediate datafiles"
// *Cause: The operation failed because the database had one or more
// datafiles that were in OFFLINE IMMEDIATE mode.
// *Action: Drop the datafiles or recover them and bring them online.
19957, 00000, "database should have no datafiles in unknown state"
// *Cause: The operation failed because the database had one or more
// datafiles that were in an unknown state.
// *Action: Drop the datafiles or recover them and bring them online.
19958, 00000, "potential deadlock involving DIAG process"
// *Cause: DIAG requested a control file operation that may lead
// to a deadlock
// *Action: Try last operation later when the control file is released
19959, 00000, "DBNEWID utility only allowed in CDB$ROOT"
// *Cause: An attempt was made to use the DBNEWID utility in a
// pluggable database.
// *Action: Connect to CDB$ROOT and retry the command.
// NLS_DO_NOT_TRANSLATE [19960,19960]
19960, 00000, "Internal use only"
// *Cause: NID usage
// *Action: None
/
19961, 00000, "compression algorithm %s requires advanced compression option to be enabled"
// *Cause: Requested compression algorithm in initialization parameter
// or by RMAN configuration requires that the advanced
// compression option be enabled and it was not.
// *Action: Change initialization parameter advanced_compression_option_usable
// to true or change RMAN configurations and retry the operation.
19962, 00000, "compression algorithm %s is not valid with release %s"
// *Cause: Algorithm in initialization parameter requires a lower
// compatibility that is currently set.
// *Action: Change algorithm in initialization parameter file or lower
// compatibility.
19963, 00000, "error getting logical block size of file %s"
// *Cause: Error occurred when querying the logical block size of a file.
// *Action: None
19964, 00000, "cannot set mirror side %0!s for file %1!s"
// *Cause: An error occurred when trying to set the mirror side for a file.
// The specified mirror could be out of range.
// *Action: Use a different mirror side and retry the command.
/
/ 19965 - 19979 reserved for multi-instance standby switchover
/
19965, 00000, "ALTER DATABASE RECOVER STANDBY TABLESPACE has been deprecated"
// *Cause: The STANDBY TABLESPACE clause of the ALTER DATABASE RECOVER
// statement (partial_database_recovery clause) has been deprecated.
// *Action: If you want to recover the standby database to a consistent point,
// but no further, use the statement ALTER DATABASE RECOVER MANAGED
// STANDBY DATABASE UNTIL CONSISTENT.
19966, 00000, "ALTER DATABASE RECOVER STANDBY DATAFILE has been deprecated"
// *Cause: The STANDBY DATAFILE clause of the ALTER DATABASE RECOVER
// statement (partial_database_recovery clause) has been deprecated.
// *Action: If you want to recover the standby database to a consistent point,
// but no further, use the statement ALTER DATABASE RECOVER MANAGED
// STANDBY DATABASE UNTIL CONSISTENT.
/
19970, 00000, "multi-instance standby role transition in progress"
// *Cause: ALTER DATABASE MOUNT failed because a multi-instance standby
// role transition was in progress.
// *Action: Retry after the multi-instance standby role transition finishes.
19971, 00000, "event 10875 or 10879 is set"
// *Cause: Event 10875 or event 10879 was set which prevented the operation
// from completing with multiple instances running in Oracle RAC.
// *Action: Shutdown all but one instance, then retry the command.
19972, 00000, "ALTER DATABASE RECOVER TO LOGICAL requires one instance left"
// *Cause: ALTER DATABASE RECOVER TO LOGICAL required only one instance to
// be left running.
// *Action: Shutdown all but one instance, then retry the command.
19973, 00000, "flashback database is not enabled"
// *Cause: Physical standby transition to snapshot standby required only one
// instance left running if flashback database logging was not
// enabled.
// *Action: Shutdown all but one instance, then retry the command.
19974, 00000, "database name has changed"
// *Cause: Physical standby role transition required only one instance left
// running if database name was changed and flashback database
// logging was enabled.
// *Action: Shutdown all but one instance, then retry the command.
19975, 00000, "database must not be started in any other instance"
// *Cause: The physical standby role transition command failed because
// a certain condition required the database to be mounted in this
// instance and not started in any other instance.
// *Action: See associated error message for detailed explanation.
19976, 00000, "a concurrent standby role transition in progress"
// *Cause: The standby role transition operation failed because a
// concurrent standby role transition was already in progress.
// *Action: None
/
/ 19980- 19989 reserved for cross-platform transpotable tablespace (xtts)
/
19980, 00000, "cannot open Data Pump dump file %s"
// *Cause: When attempting to open the specified dump file, an error was
// received.
// *Action: Verify that the specified dump file exists and is accessible.
19981, 00000, "cannot read header of Data Pump dump file %s"
// *Cause: When attempting to read the header of the specified dump file,
// an error was received.
// *Action: Verify that the specified dump file is complete.
19982, 00000, "file %s is not a Data Pump dump file"
// *Cause: The specified dump file did not contain data created by Data Pump.
// *Action: Verify that the specifed dump file is really a file created by
// Data Pump.
19983, 00000, "Data Pump dump file could not be verified"
// *Cause: Some data blocks for the Data Pump dump file were corrupt in the
// backup set.
// *Action: Unless the damage to the backup set can be repaired, the
// Data Pump dump file cannot be restored from this backup set.
19984, 00000, "Data Pump dump file restore requires COMPATIBLE %s or greater"
// *Cause: Data Pump dump file restore requested but COMPATIBLE did not
// allow it.
// *Action: Do not request dump file backup or set COMPATIBLE to minimum
// value and retry backup.
19985, 00000, "Data Pump dump file can only be requested in a cross-platform restore"
// *Cause: Data Pump dump file restore requested but the restore conversation
// is not a cross-platform conversation.
// *Action: Start a new cross-platform restore conversation or do not include
// a Data Pump dump file.
19986, 00000, "archived log backup piece found for cross-platform backup"
// *Cause: A cross-platform backup was requested for a backup piece that
// contained archived logs.
// *Action: Specify a datafile backup piece for cross-platform processing.
19987, 00000, "unknown platform ID %s"
// *Cause: The platform ID obtained from a cross-platform backup was
// incorrect.
// *Action: Verify that the platform specified in the FROM PLATFORM
// clause is correct.
19988, 00000, "must specify FROM PLATFORM for cross-platform restore of backup sets with pre-12.1 compatibility"
// *Cause: A cross-platform restore was requested from a backup piece created
// with pre-12.1 compatibility without providing the platform
// name that created it.
// *Action: Reissue the command including the FROM PLATFORM clause.
//
19989, 00000, "internal usage"
//
19990, 00000, "restore from cross-platform encrypted backup is not supported"
// *Cause: A cross-platform restore was requested from an encrypted backup
// set.
// *Action: Specify a non-encrypted backup set from which to perform
// the restore.
19991, 00000, "cross-platform backup of encrypted backups to different endianess is not supported"
// *Cause: A cross-platform backup was requested for an encrypted backup
// to a different endianess from the current platform.
// *Action: Do not specify an encrypted backup or specify the same endian
// platform.
19992, 00000, "cross-platform backup of encrypted backup piece with different endianess is not supported"
// *Cause: A cross-platform backup was requested for an encrypted backup
// piece with different endianess from the current platform.
// *Action: Specify a backup piece without encryption to the backup.
19993, 00000, "must specify FROM PLATFORM for cross-platform backup of backup pieces with compatibility set prior to 12.1"
// *Cause: A cross-platform backup was requested for a backup piece created
// with compatibility prior to 12.1 without providing the platform
// name that created it.
// *Action: Reissue the command including the FROM PLATFORM clause.
19994, 00000, "cross-platform backup of compressed backups to different endianess is not supported"
// *Cause: A cross-platform backup was requested for a compressed backup
// to a different endianess from the current platform.
// *Action: Do not specify a compressed backup or specify the same endian
// platform.
19995, 00000, "controlfile cannot be restored from a cross-platform backup with different endianess"
// *Cause: A restore of the controlfile was requested from a cross-platform
// backup, but the backup did not have the same endianess and
// restore was not possible.
// *Action: Do not attempt to restore a controlfile from a cross-platform
// backup set.
19996, 00000, "cross-platform backup of backup pieces with pre-10.2 compatibility is not supported"
// *Cause: A cross-platform backup was requested for a backup created
// with pre-10.2 compatibility.
// *Action: Do not attempt to perform cross-platform backup of backups
// created with with pre-10.2 compatibility.
19997, 00000, "backup pieces prior to 10.2 cannot be operated for cross-platform"
// *Cause: A cross-platform operation was requested for a backup created
// with pre-10.2 compatibility.
// *Action: Do not attempt to perform the cross-platform operation of backups
// created with pre-10.2 compatibility.
19998, 00000, "data file %s already included to be plugged"
// *Cause: This data file was already specified for inclusion in this
// restore conversation.
// *Action: No action required. The conversation is still active and
// more files can be specified.
// 19999 is used for event
/
/ Error numbers
/
/ 21100 - 21299 Reserved for CORE
/ 21300 - 22799 Reserved for OI/KO/KG (object Interface and Subsystem)
/
/ 22800 - 22999 Reserved for object SQL:
/ 23000 - 23299 Reserved for object Management Subsystem (OMS)
/
/ 23300 - 24299 Reserved for errors from DBMS* pl/sql packages
/ 23300 - 23599: Replication Packages
/ 23600 - 23999: Log Based Replication Packages
/ 24000 - 24099: AQ admin interface
/ 24100 - 24119: DBMS_SCHEDULER package
/ 24120 - 24140: DBMS_REPAIR package
/ 24141 - 24179: DBMS_RULE package
/ 24190 - 24199: AQ JMS
/ 24200 - 24229: DBMS_AQADM package
/ 24230 - 24264: Miscellaneous DBMS* packages
/ 24265 - 24269: DBMS_SQLTUNE package
/ 24270 - 24279: DBMS_HO package
/
/ MODIFIED
/ pjayapal 07/19/17 - Bug 26277439 signal synonym mismatch during import
/ of mview with remap_schema
/ ajbatta 04/07/17 - Add length to error 22973
/ ajbatta 03/14/17 - Bug 18608595: add 22385 event
/ pjayapal 01/24/17 - bug 22747906 disallow redef on interval partitioned
/ table with ILM policy
/ skabraha 01/12/17 - add errors for non-persistable types
/ rpingte 05/10/16 - disallow insert/update of transformed image
/ skabraha 04/12/16 - add 22382 event
/ sjanardh 12/20/15 - Add AQ error 24216
/ prakumar 05/23/15 - Bug 20852285
/ yulcho 04/15/15 - bug 20526847: add a new error for DBCOMP
/ pkapil 04/14/15 - bug 20865939 : add error 24133
/ rpang 03/26/15 - Add 24263
/ vraja 03/04/15 - bug20612849: OER(21302) for object snapshot conversion
/ jstewart 01/14/15 - Changing message for OER(21611)
/ liding 10/24/14 - bug 19861936: add new error message for online redef
/ acolunga 09/19/14 - Proj 47511: add error 22381
/ srav 04/08/14 - Bug 18240704: do not regenerate deps if 22380 is set
/ srav 02/11/14 - 14346992: Bypass hashcode checking on event 22379
/ skabraha 12/10/13 - add 22378
/ srav 11/08/13 - 13255699 Add 22377
/ skabraha 10/24/13 - add event for keeping old type synonym behavior
/ ranjaysi 08/28/13 - bug15848219: new error multiple start/stop on already
/ started/stopped queue
/ mahrajag 07/15/13 - bug 17052830
/ ajbatta 01/16/13 - Add event to check for Subtypes in complete type tree
/ rbello 07/31/12 - bug 14361294, add rmt diagnostics 23548 event
/ jdavison 05/31/12 - Fix messages with incorrect action format
/ yifeng 05/22/12 - add 22847
/ rpang 04/30/12 - add 24255 for sql translation bind order restriction
/ yifeng 03/06/12 - add 22846
/ yifeng 02/21/12 - add 22845
/ rdecker 08/30/11 - alter 22352; table%rowtypes now supported
/ shbose 08/22/11 - error for non-durable subscriber rule
/ yberezin 08/09/11 - bug 12830154
/ shbose 07/13/11 - add partition support for rules
/ rbello 05/25/11 - add 23545, cannot create rmt
/ rbello 05/15/11 - redef rowid mapping table errors
/ rdecker 05/01/11 - add 22349, 22351 for plsql package type support
/ dvoss 02/08/11 - restore 24081, it is used from plsql
/ rpang 12/28/10 - add SQL translation error messages
/ gagarg 11/23/10 - Add 24206, 24207, 24208
/ atomar 10/27/10 - bug 10102731
/ atomar 10/27/10 - bug 10111363
/ yuli 09/30/10 - remove unused error numbers
/ jamferna 09/02/10 - bug 9476520: add error 22844
/ gagarg 04/01/10 - Proj:31157: ADD Sharded queue errors
/ yberezin 05/05/10 - bug 9686001
/ yifeng 06/19/10 - bug 9491716: modify error 22843
/ jstewart 05/24/10 - added error msg 21528
/ yifeng 03/26/10 - bug 9491716: add error 22843
/ shbose 11/05/09 - bug 8843855: Add errors 24174 and 24175
/ skabraha 10/02/09 - add 22350
/ yifeng 10/31/08 - add event 22842
/ kgiyer 11/11/08 - bug 6331369: new error for subset rule buffer overflow
/ skabraha 10/10/08 - add mesg 22374
/ akruglik 10/01/08 - (4227938): add msg 22841
/ yberezin 09/25/08 - bug 7112727: new error 23661 for capture
/ achoi 08/18/08 - add message 22348
/ mcoulter 07/30/08 - bug 7281890 kse/kge messages wrongly using %d
/ gagarg 04/03/08 - Change error message of 24005
/ msakayed 04/03/08 - add directory execute privilege
/ jstewart 03/31/08 - update of msg 22635
/ rpingte 02/23/08 - add 22635
/ yifeng 12/17/07 - bug 6490005, add ORA-22936
/ jstewart 10/09/07 - adding msg 22141
/ yifeng 09/26/07 - bug 2691510 remove "nested table" in ORA-22901
/ yifeng 09/25/07 - add 22866
/ atomar 09/19/07 - bug 4683748
/ tianli 08/22/07 - add ORA-23658 to ORA-23660
/ sjanardh 08/02/07 - ORA-24085 cause changes
/ yizhang 05/02/07 - Fix bug 5040073
/ skabraha 03/14/07 - add 22373
/ cschmidt 04/10/07 - add ORA-23644 to ORA-23656
/ shbose 03/30/07 - Backward compatible propagation
/ legao 03/02/07 - add ORA-23642 and ORA-23643
/ skabraha 03/01/07 - add type dict upgrade event
/ jstewart 02/27/07 - remove 22635 error
/ tianli 02/05/07 - add ORA-23637 to ORA-23641 be the reasons of ORA-23630
/ yifeng 01/10/07 - add ORA-22839 for direct updating SYS_NC columns
/ yizhang 12/21/06 - Fix bug 5394563
/ cschmidt 12/14/06 - add ORA-23630 to ORA-23634
/ juyuan 11/15/06 - add ORA-23629 for DBMS_COMPARISON
/ yifeng 11/15/06 - add ORA-22837 for relational hint or keyword for
/ user level DML. add event 22838 to avoid throwing
/ this error.
/ kchen 10/31/06 - add ORA-24277 to ORA-24279
/ rpingte 09/07/06 - add ORA-22635 for 8.0 image pickling
/ rpang 08/30/06 - add ORA-24245 for DBMS_NETWORK_ACL_ADMIN
/ slynn 08/09/06 - LOCAL to SMARTFILE
/ rpang 05/15/06 - add ORA-24243 and 24244 for DBMS_NETWORK_ACL_ADMIN
/ rvenkate 04/19/06 - add comparison error messages
/ kkunchit 11/01/05 - project-18204: inode: LOCAL/NOLOCAL support
/ mbaloglu 12/19/05 - Project 18207: Adding [A]SYNC property for LOBs
/ rpang 03/15/06 - add message ORA-24242 for embedded PL/SQL gateway
/ gtarora 12/05/05 - event 22935: ucs2 lobs
/ yuli 10/31/05 - remove unused error numbers
/ molagapp 08/22/05 - molagapp_dbhygiene_rman_3
/ molagapp 08/16/05 - split e19400.msg
/ molagapp 08/16/05 - Creation
/
19999, 00000, "skip_row procedure was called"
// *Cause: The skip_row procedure was called which raises this error
// *Action: Skip_row should only be called within a trigger or a procedure
// called by a trigger.
/
/ 20000 - 20999 Reserved for callers of the
/ system_utility.raise_application_error stored procedure. This allows
/ customers to generate their own exception numbers and deal with them
/ on the user-side.
20000, 00000, "%s"
// *Cause: The stored procedure 'raise_application_error'
// was called which causes this error to be generated.
// *Action: Correct the problem as described in the error message or contact
// the application administrator or DBA for more information.
21000, 00000, "error number argument to raise_application_error of %s%s is out of range"
// *Cause:
// *Action: Use an error number in the range of -20000 to -20999, inclusive.
21001, 00000, "error number argument to raise_system_error of %s%s is out of range"
// *Cause:
// *Action: Use an error number in the range of -23300 to -24299, or
// -29300 to -29399, inclusive.
/
/ 21100 - 21299 Reserved for CORE
/
/
/ 21300 - 22799 Reserved for OI/KO/KG (object Interface and Subsystem)
/
/ Error numbers from 21300 to 21305 are reserved for KOK (common).
/
21300, 00000, "objects option not installed"
// *Cause: The objects option is not installed at this site. object types
// and other object features are, therefore, unavailable.
// *Action: Install the objects option. The objects option is not
// part of the Oracle Server product and must be purchased
// separately. Contact an Oracle sales representative if the
// objects option needs to be purchased.
21301, 00000, "not initialized in object mode"
// *Cause: This function requires the OCI process to be initialized in object
// mode.
// *Action: Specify OCI_OBJECT mode when calling OCIInitialize().
/
21302, 00000, "object snapshot error: %s"
// *Cause: The object snapshot operation failed. Additional details are
// provided in the error message.
// *Action: Contact Oracle Support Services.
/
/ Error number 21500 is the OCI's and Cartridge Service internal error.
/ Error number 21501 is the OCI's or Cartridge Services' memory allocation error.
/ Error number 21503 is the OCI's and Cartridge Service fatal error.
/
21500, 00000, "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"
// *Cause: This is the generic error number for the OCI
// environment (client-side) internal errors. This indicates
// that the OCI environment has encountered an exceptional
// condition.
// *Action: Report as a bug - the first argument is the internal error number.
/
21501, 00000, "program could not allocate memory"
// *Cause: The operating system has run out of memory.
// *Action: Take action to make more memory available to the program.
/
21503, 00000, "program terminated by fatal error"
// *Cause: A program is in an unrecoverable error state.
// *Action: Report as a bug.
/
/
/ Error numbers from 21505 to 21519 are reserved for ORIG/KOG (general).
/
/
/ Error numbers from 21520 to 21559 are reserved for KOD/KOKD/KOUD (data).
/
21520, 00000, "database server driver not installed"
// *Cause: User attempted to access a database server through an object-mode
// OCI environment but the necessary driver for supporting such
// access to the database server is not installed or linked
// in.
// *Action: Check if the driver corresponding to the database server
// has been installed/linked in and entered in the server driver
// table.
21521, 00000, "exceeded maximum number of connections in OCI (object mode only)"
// *Cause: User exceeded the maximum number of connections (255) that can
// be supported by an OCI environment in object mode.
// *Action: Close some of existing and unused connections before
// opening more connections.
21522, 00000, "attempted to use an invalid connection in OCI (object mode only)"
// *Cause: User attempted to use an invalid connection or a connection that
// has been terminated in an OCI environment (object mode),
// or user attempted to dereference a REF obtained from a connection
// which has been terminated.
// *Action: Ensure that the connection exists and is still valid.
21523, 00000, "functionality not supported by the server (object mode only)"
// *Cause: User attempted to use a functionality that the server does not
// support.
// *Action: Upgrade the server
21524, 00000, "object type mismatch"
// *Cause: The object type of the object is different from what is specified.
// *Action: Check the type of the object and correct it.
/
21525, 00000, "attribute number or (collection element at index) %s violated its constraints"
// *Cause: Attribute value or collection element value violated its
// constraint.
// *Action: Change the value of the attribute or collection element such that
// it meets its constraints. The constraints are specified as part
// of the attribute or collection element's schema information.
21526, 00000, "initialization failed"
// *Cause: The initialization sequence failed. This can happen, for example,
// if an environment variable such as NLS_DATE_FORMAT is set to
// an invalid value.
// *Action: Check that all NLS environment variables are well-formed.
21527, 00000, "internal OMS driver error"
// *Cause: A process has encountered an exceptional condition. This is the
// generic internal error number for Oracle object management
// services exceptions.
// *Action: Report this as a bug to Oracle Support Services.
21528, 00000, "internal error, image could not be understood"
// *Cause: The format of the image passed to the pickler is incorrect and
// cannot be understood.
// *Action: Contact Oracle Support Services.
/
/
/ Error numbers from 21560 to 21599 are reserved for
/ common ORI/ORT/ORL/ORC/KO and Cartridge Service errors.
/
21560, 00000, "argument %s is null, invalid, or out of range"
// *Cause: The argument is expecting a non-null, valid value but the
// argument value passed in is null, invalid, or out of range.
// Examples include when the LOB/FILE positional or size
// argument has a value outside the range 1 through (4GB - 1),
// or when an invalid open mode is used to open a file, etc.
// *Action: Check your program and correct the caller of the routine
// to not pass a null, invalid or out-of-range argument value.
/
21561, 00000, "OID generation failed"
// *Cause: The handles passed in may not be valid
// *Action: Check the validity of the env, svc handles
/
/ Error numbers from 21600 to 21699 are reserved for ORI*/KOI* (interface).
/ and Memory/Duration Cartridge Service.
/
21600, 00000, "path expression too long"
// *Cause: The path expression that is supplied by the user is too long. The
// path expression is used to specify the position of an attribute in
// an object. This error occurs when one of the intermediate elements
// in the path expression refers to an attribute of a built-in type.
// Thus, the OCI function cannot proceed on to process the rest of the
// elements in the path expression.
// *Action: User should pass in the correct path expression to locate the
// attribute.
21601, 00000, "attribute is not an object"
// *Cause: The user attempts to perform an operation (that is valid only for
// an object) to an attribute of a built-in type.
// An example of such an illegal operation is to dynamically set
// a null structure to an attribute of a built-in type.
// *Action: User should avoid performing such operation to an attribute of
// built-in type.
21602, 00000, "operation does not support the specified typecode"
// *Cause: The user attempts to perform an operation that does not support
// the specified typecode.
// *Action: User should use the range of valid typecodes that are supported
// by this operation.
21603, 00000, "property id [%s] is invalid"
// *Cause: The specified property id is invalid.
// *Action: User should specify a valid property id. Valid property ids are
// enumerated by OCIObjectPropId.
21604, 00000, "property [%s] is not a property of transient or value instances"
// *Cause: Trying to get a property which applies only to persistent objects.
// *Action: User should check the lifetime and only get this property for
// persistent objects.
21605, 00000, "property [%s] is not a property of value instances"
// *Cause: Trying to get a property which applies only to persistent
// and transient objects.
// *Action: User should check the lifetime and only get this property for
// persistent and transient objects.
21606, 00000, "can not free this object"
// *Cause: Trying to free an object that is persistent and dirty and the
// OCI_OBJECTFREE_FORCE flag is not specified.
// *Action: Either flush the persistent object or set the flag to
// OCI_OBJECTFREE_FORCE
/
21607, 00000, "memory cartridge service handle not initialized"
// *Cause: Attempt to use the handle without initializing it.
// *Action: Initialize the memory cartridge service handle.
21608, 00000, "duration is invalid for this function"
// *Cause: Attempt to use a duration not valid for this function.
// *Action: Use a valid duration - a previously created user duration or
// OCI_DURATION_STATEMENT or OCI_DURATION_SESSION. For callout
// duration or external procedure duration, use
// OCIExtProcAllocCallMemory.
21609, 00000, "memory being resized without being allocated first"
// *Cause: Attempt to resize memory without allocating it first.
// *Action: Allocate the memory first before resizing it.
21610, 00000, "size [%s] is invalid"
// *Cause: Attempt to resize memory with invalid size.
// *Action: Pass in a valid size (must be a positive integer).
21611, 00000, "key length [%s] is invalid"
// *Cause: An attempt was made to use an invalid key length.
// *Action: Key length is invalid; a valid range is 0 to 254.
21612, 00000, "key is already being used"
// *Cause: Attempt to use a key that is already used.
// *Action: Use a new key that is not yet being used.
21613, 00000, "key does not exist"
// *Cause: Attempt to use a non-existent key
// *Action: Use a key that already exists.
21614, 00000, "constraint violation for attribute number [%s]"
// *Cause: Constraints on the attribute were violated
// *Action: Correct the value (of the attribute) so that it satisfies
// constraints
21615, 00000, "copy of an OTS (named or simple) instance failed"
// *Cause: see following message
// *Action: Check that no attribute value violates constraints.
/
/ Error numbers from 21700 to 21799 are reserved for KOC (cache).
/
21700, 00000, "object does not exist or is marked for delete"
// *Cause: User attempted to perform an inappropriate operation to
// an object that is non-existent or marked for delete.
// Operations such as pinning, deleting and updating cannot be
// applied to an object that is non-existent or marked for delete.
// *Action: User needs to re-initialize the reference to reference an
// existent object or the user needs to unmark the object.
21701, 00000, "attempt to flush objects to different servers"
// *Cause: User attempted to flush objects to different servers in one
// function call. These objects are obtained by calling a callback
// functions provided by the program.
// *Action: User should avoid performing such operation.
21702, 00000, "object is not instantiated or has been de-instantiated in cache"
// *Cause: User attempted to perform an inappropriate operation to a transient
// object that is not instantiated in the object cache.
// Operations that cannot be applied to a not-instantiated transient
// object include deleting or pinning such an object.
// *Action: User should check their code to see if they are performing
// such an operation without instantiating the object first, or
// performing such an operation after the allocation duration of
// the object has expired.
21703, 00000, "cannot flush an object that is not modified"
// *Cause: See the error message.
// *Action: The object should not be flushed.
21704, 00000, "cannot terminate cache or connection without flushing first"
// *Cause: See the error message.
// *Action: The transaction should be aborted or committed before terminating
// the cache or connection.
21705, 00000, "service context is invalid"
// *Cause: The service context that is supplied by the user is not valid.
// *Action: User needs to establish the service context.
21706, 00000, "duration does not exist or is invalid"
// *Cause: The duration number that is supplied by the user is not valid.
// *Action: User needs to establish the duration or use a correct predefined
// duration.
21707, 00000, "pin duration is longer than allocation duration"
// *Cause: The pin duration supplied by the user is longer than the allocation
// duration. This affects operations such as pinning and setting
// default parameters.
// *Action: User should use a shorter pin duration or use the null duration.
21708, 00000, "inappropriate operation on a transient object"
// *Cause: User attempted to perform an inappropriate operation on a
// transient object. Operations that cannot be applied to a
// transient object include flushing and locking.
// *Action: User should avoid performing such operation on a transient object.
21709, 00000, "cannot refresh an object that has been modified"
// *Cause: User attempted to refresh an object that has been marked for
// delete, update or insert (new).
// *Action: User should unmark the object before refreshing it.
21710, 00000, "argument is expecting a valid memory address of an object"
// *Cause: The object memory address that is supplied by the user is invalid.
// The user may have passed in a bad memory address to a function that
// is expecting a valid memory address of an object.
// *Action: User should pass in a valid memory address of an object
// to the function.
/
/
21779, 00000, "duration not active"
// *Cause: User is trying to use a duration that has been terminated.
// *Action: User should avoid performing such operation.
21780, 00000, "Maximum number of object durations exceeded."
// *Cause: This typically happens if there is infinite recursion in the PL/SQL
// function that is being executed.
// *Action: User should alter the recursion condition in order to prevent
// infinite recursion.
/
/
/ Error numbers from 21800 to 21998 are reserved.
/
/
/ Error numbers from 22000 to 22298 are reserved for ORL/KOL (language)
/ including OCIString, OCIDate, OCINumber, OCIColl, OCITable, and OCIArray.
/
22053, 00000, "overflow error"
// *Cause: This operation's result is above the range of Oracle number.
// *Action: Decrease the input value(s) so that the result is in the range
// of Oracle number.
/
22054, 00000, "underflow error"
// *Cause: This operation's result is below the range of Oracle number.
// *Action: Increase the input value(s) so that the result is in the range
// of Oracle number.
/
22055, 00000, "unknown sign flag value [%s]"
// *Cause: Signed flag used is not OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED.
// *Action: Use either OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED as sign flag.
/
22056, 00000, "value [%s] is divided by zero"
// *Cause: Given value is divied by zero.
// *Action: Modify divisor value to be non-zero.
/
22057, 00000, "bad integer length [%s]"
// *Cause: The length of the integer (ie number of bytes) to be converted
// to or from an Oracle number is invalid.
// *Action: Use integer length 1, 2, 4 or 8 bytes only.
/
22059, 00000, "buffer size [%s] is too small - [%s] is needed"
// *Cause: The buffer to hold the resulting text string is too small.
// *Action: Provide a buffer of the required size.
/
22060, 00000, "argument [%s] is an invalid or uninitialized number"
// *Cause: An invalid or uninitialized number is passed in.
// *Action: Use a valid number. To initialize number call OCINumberSetZero().
/
22061, 00000, "invalid format text [%s]"
// *Cause: The numeric format string for converting characters to or
// from an Oracle number is invalid.
// *Action: Use valid format string as documented in OCI Programmer's Guide.
/
22062, 00000, "invalid input string [%s]"
// *Cause: The text string for converting to numbers is invalid.
// *Action: Use a valid input string as documented in OCI Programmer's Guide.
/
22063, 00000, "reading negative value [%s] as unsigned"
// *Cause: Attempt to convert a negative number to an unsigned integer.
// *Action: Use the sign flag ORLTSB to convert a signed number.
/
22064, 00000, "invalid NLS parameter string [%s]"
// *Cause: The NLS parameter string for converting characters to or
// from an Oracle number is invalid.
// *Action: Use valid format string as documented in OCI Programmer's Guide.
/
22065, 00000, "number to text translation for the given format causes overflow"
// *Cause: Rounding done due to the given string format causes overflow.
// *Action: Change the string format such that overflow does not occur.
/
22130, 00000, "buffer size [%s] is less than the required size [%s]"
// *Cause: The size of the buffer into which the hexadecimal REF string
// is to be written is too small.
// *Action: Provide a buffer of the required size.
/
22131, 00000, "hexadecimal string length is zero"
// *Cause: The given hexadecimal string length must be greater than zero.
// *Action: Specify a length greater than zero.
/
22132, 00000, "hexadecimal string does not correspond to a valid REF"
// *Cause: The given hexadecimal string is invalid.
// *Action: Provide a valid hexadecimal string which was previously returned
// by a call to OCIRefToHex().
/
22140, 00000, "given size [%s] must be in the range of 0 to [%s]"
// *Cause: The given resize size is invalid.
// *Action: Ensure that the given size is in the required range.
/
22141, 00000, "given size [%s] must be even in UTF-16 environment"
// *Cause: The given resize size is odd. In a UTF-16 environment, all
// characters are 2 bytes in length.
// *Action: Ensure that the given size is even.
/
22150, 00000, "variable-length array has not been initialized"
// *Cause: An un-initialized variable-length array is being operated upon.
// *Action: Initialize the variable-length array prior to calling
// this function.
/
22151, 00000, "cannot resize non-zero variable-length array to zero elements"
// *Cause: Trying to resize a non-zero variable-length array to 0 elements.
// *Action: Specify a non-zero size.
/
22152, 00000, "destination variable-length array is not initialized"
// *Cause: The variable-length array on the right-hand-side of an
// assignment or the destination array of an append
// is not initialized.
// *Action: Initialize the destination variable-length array prior to calling
// this function.
/
22153, 00000, "source variable-length array is not initialized"
// *Cause: The variable-length array on the left-hand-side of an
// assignment or the source array of an append
// is not initialized.
// *Action: Initialize the destination variable-length array prior to calling
// this function.
/
22160, 00000, "element at index [%s] does not exist"
// *Cause: Collection element at the given index does not exist.
// *Action: Specify the index of an element which exists.
/
22161, 00000, "type code [%s] is not valid"
// *Cause: Given type code is not valid.
// *Action: Use one of the typecodes enumerated in OCITypeCode.
/
22162, 00000, "element at index [%s] has been previously deleted"
// *Cause: Trying to delete a non-existent collection element.
// *Action: Check for the existence of the element prior to calling this
// function.
/
22163, 00000, "left hand and right hand side collections are not of same type"
// *Cause: Left hand and right side collections are not of same type.
// *Action: Ensure that the same collection type is passed for both left
// hand and right hand side of this function.
/
22164, 00000, "delete element operation is not allowed for variable-length array"
// *Cause: Trying to delete an element of a variable-length array.
// *Action: Ensure that the collection is not a variable-length array prior
// to calling this function.
/
22165, 00000, "given index [%s] must be in the range of [%s] to [%s]"
// *Cause: Given index is not in the required range.
// *Action: Ensure that the given index is in the required range.
/
22166, 00000, "collection is empty"
// *Cause: Given collection is empty.
// *Action: Test if collection is empty prior to invoking this function.
/
22167, 00000, "given trim size [%s] must be less than or equal to [%s]"
// *Cause: Given trim size is greater than the current collection size.
// *Action: Ensure that the given size is less than or equal to the
// collection size prior to calling this function.
/
/ 22275 to 22279 reserved for KOLL - LOBs
/
22275, 00000, "invalid LOB locator specified"
// *Cause: There are several causes: (1) the LOB locator was never
// initialized; (2) the locator is for a BFILE and the routine
// expects a BLOB/CLOB/NCLOB locator; (3) the locator is for a
// BLOB/CLOB/NCLOB and the routine expects a BFILE locator;
// (4) trying to update the LOB in a trigger body -- LOBs in
// trigger bodies are read only; (5) the locator is for a
// BFILE/BLOB and the routine expects a CLOB/NCLOB locator;
// (6) the locator is for a CLOB/NCLOB and the routine expects
// a BFILE/BLOB locator;
// *Action: For (1), initialize the LOB locator by selecting into the locator
// variable or by setting the LOB locator to empty. For (2),(3),
// (5) and (6)pass the correct type of locator into the routine.
// For (4), remove the trigger body code that updates the LOB value.
/
22276, 00000, "invalid locator for LOB buffering"
// *Cause: There are several causes: (1) the locator was never enabled for
// buffering (2) it is not an updated locator but is being used for
// a write/flush operation
// *Action: For (1) enable the locator for buffering; (2) ensure that only
// an updated locator is used for a LOB update operation
/
22277, 00000, "cannot use two different locators to modify the same LOB"
// *Cause: LOB buffering is enabled and an attempt was made to modify the
// LOB using two different LOB locators.
// *Action: When using LOB buffering, modify the LOB through one LOB
// locator only.
/
22278, 00000, "must update the LOB only through the LOB buffers"
// *Cause: LOB buffering is enabled for this LOB and there are buffers
// for this LOB in the buffer pool. Thus, updating the LOB
// through means other than the LOB buffers is not allowed.
// *Action: Update the LOB through the LOB buffers using the locator that
// has LOB buffering enabled. If this operation is required,
// buffers associated with this LOB should either be flushed as
// necessary or buffering should be disabled. Once this is done,
// reissue the command.
/
22279, 00000, "cannot perform operation with LOB buffering enabled"
// *Cause: The operation attempted is not allowed when LOB buffering is
// enabled.
// *Action: If the operation is required, LOB buffering should not be used.
// In this case, flush buffers associated with the input LOB locator
// as necessary, disable buffering on the input LOB locator and
// reissue the command.
/
/ 22280 to 22299 reserved for LOBs - LBS(KOLB), DBMS_LOB(KKXL) and BFILE(KOLF)
/
22280, 00000, "no more buffers available for operation"
// *Cause: There are two causes: (1) All buffers in the buffer pool have been
// used up by previous operations (2) Attempt to flush a LOB without
// any previous buffered update operations.
// *Action: For (1), flush the LOB(s) through the locator that is
// being used to update the LOB. For (2), write to the LOB through a
// locator enabled for buffering before attempting to flush buffers.
/
22281, 00000, "cannot perform operation with an updated locator"
// *Cause: The input locator has buffering enabled and was used to update
// the LOB value through the LOB buffering subsystem. The
// modified buffer has not been flushed since the write that was
// performed by the the input locator; thus, the input locator is
// considered an updated locator. Updated locators cannot be the
// source of a copy operation. Only one locator per LOB may be used
// to modify the LOB value through the LOB buffering subsystem.
// *Action: Depending on whether the modifications made through the input
// locator to the LOB buffering subsystem should be written to
// the server, either flush the buffer to write the modifications,
// or, disable buffering on the locator to discard the
// modifications. Then, reissue the command.
/
22282, 00000, "non-contiguous append to a buffering enabled LOB not allowed"
// *Cause: The buffered write operation has an input offset value more
// than one byte or character past the end of the LOB.
// *Action: Specify an input offset value which is exactly one character or
// byte greater than the length of the LOB that you are attempting
// to update through a buffered write operation.
/
22283, 00000, "filename contains characters that refer to parent directory"
// *Cause: Filename contains a path "../" which references a parent directory
// *Action: Ensure that the filename does not contain characters which
// reference a parent directory.
/
22284, 00000, "duplicate LONG binds are not supported"
// *Cause: LOB access layer could not handle duplicate LONG binds.
// *Action: Provide distinct LONG or VARCHAR binds.
/
22285, 00000, "non-existent directory or file for %s operation"
// *Cause: Attempted to access a directory that does not exist, or attempted
// to access a file in a directory that does not exist.
// *Action: Ensure that a system object corresponding to the specified
// directory exists in the database dictionary, or
// make sure the name is correct.
/
22286, 00000, "insufficient privileges on file or directory to perform %s operation"
// *Cause: The user does not have the necessary access privileges on the
// directory alias and/or the file for the operation.
// *Action: Ask the database/system administrator to grant the required
// privileges on the directory alias and/or the file.
/
22287, 00000, "invalid or modified directory occurred during %s operation"
// *Cause: The directory alias used for the current operation is not valid
// if being accessed for the first time, or has been modified by
// the DBA since the last access.
// *Action: If you are accessing this directory for the first time, provide
// a valid directory name. If you have been already successful in
// opening a file under this directory before this error occured,
// then close the file and retry the operation with a valid
// directory alias as modified by your DBA. Oracle recommends that
// directories should be modified only during quiescent periods.
/
22288, 00000, "file or LOB operation %s failed\n%s"
// *Cause: The operation attempted on the file or LOB failed.
// *Action: See the next error message in the error stack for more detailed
// information. Also, verify that the file or LOB exists and that
// the necessary privileges are set for the specified operation. If
// the error still persists, report the error to the DBA.
/
22289, 00000, "cannot perform %s operation on an unopened file or LOB"
// *Cause: The file or LOB is not open for the required operation to be
// performed.
// *Action: Precede the current operation with a successful open operation
// on the file or LOB.
/
22290, 00000, "operation would exceed the maximum number of opened files or LOBs"
// *Cause: The number of open files or LOBs has reached the maximum limit.
// *Action: Close some of the opened files or LOBs and retry the operation.
/
22291, 00000, "Open LOBs exist at transaction commit time"
// *Cause: An attempt was made to commit a transaction with open LOBs at
// transaction commit time.
// *Action: Close the LOBs before committing the transaction.
/
22292, 00000, "Cannot open a LOB in read-write mode without a transaction"
// *Cause: An attempt was made to open a LOB in read-write mode before
// a transaction was started.
/ *Action: Start a transaction before opening the LOB in read-write mode.
// Ways to start a transaction include issuing a SQL DML or SELECT
// FOR UPDATE command. Opening hte LOB in read-only mode does not
// require a transaction.
/
22293, 00000, "LOB already opened in the same transaction"
// *Cause: An attempt was made to open a LOB that already is open in
// this transaction.
// *Action: Close the LOB before attempting to re-open it.
/
22294, 00000, "cannot update a LOB opened in read-only mode"
// *Cause: An attempt was made to write to or update a LOB opened
// in read-only mode.
// *Action: Close the LOB and re-open it in read-write mode before
// attempting to write to or update the LOB.
22295, 00000, "cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement"
// *Cause: An attempt was made to bind data more than 4000 bytes of data to both
// LOB and LONG columns in the same insert or update statement. You can
// bind more than 4000 bytes of data to either a LONG column or one or
// more LOB columns but not both.
// *Action: Bind more than 4000 bytes of data to either the LONG column or one or
// more LOB columns but not both.
22296, 00000, "invalid ALTER TABLE option for conversion of LONG datatype to LOB"
// *Cause: An attempt was made to specify ALTER TABLE options which are
// disallowed during conversion of LONG datatype to LOB. The only ALTER
// TABLE options allowed during conversion of LONG datatype to LOB are
// the default clause and LOB storage clause for the column being
// converted to LOB.
// *Action: Remove the disallowed options.
22297, 00000, "warning: Open LOBs exist at transaction commit time"
// *Cause: An attempt was made to commit a transaction with open LOBs at
// transaction commit time.
// *Action: This is just a warning. The transaction was commited successfully,
// but any domain or functional indexes on the open LOBs were not
// updated. You may want to rebuild those indexes.
22298, 00000, "length of directory alias name or file name too long"
// *Cause: The length of directory alias name or file name given for a BFILE
// is too long.
// *Action: Use a shorter alias or file name.
//
22299, 00000, "Synonym compile without validating base object"
// *Document: No
// *Cause:
// *Action: No validation of the base object.
/
22300, 00000, "acquiring DML lock in WAIT mode on table that is locked by KGL or KQR"
// *Document: NO
// *Cause: An attempt was made to acquire a DML lock in WAIT mode on a table
// that is locked by KGL or KQR.
// *Action: This is just a warning. The transaction was commited successfully,
// but any domain or functional indexes on the open LOBs were not
// updated. You may want to rebuild those indexes.
/
/ Error numbers from 22301 to 22599 are reserved for ORT/KOT (type).
/
22303, 00000, "type \"%s\".\"%s\" not found"
// *Cause: The user is trying to obtain information for a type that
// cannot be found.
// *Action: Check that the schema is correct and that the type has been
// created correctly.
/
22304, 00000, "input type is not an object type"
// *Cause: The user is trying to obtain the supertype information for a
// non-object type.
// *Action: Pass in only an object type.
/
22305, 00000, "attribute/method/parameter \"%s\" not found"
// *Cause: Type element with the given name is not found in the type.
// *Action: Check to make sure that the type element exists.
/
22306, 00000, "type \"%s\".\"%s\" already exists"
// *Cause: The user is trying to create a type that already
// exists.
// *Action: Check to make sure that the type has not been created prior to
// this.
/
22307, 00000, "operation must be on a user-defined type"
// *Cause: attempt to perform an operation that is allowed only on a
// user-defined type, and the type is not a user-defined type.
// *Action: Check to make sure that only user-defined types are being
// operated on.
/
22308, 00000, "operation not allowed on evolved type"
// *Cause: An attempt was made to replace a type whose attribute definition
// been been altered.
// *Action: Submit ALTER TYPE ADD/DROP statement instead of ALTER TYPE
// REPLACE.
/
22309, 00000, "attribute with name \"%s\" already exists"
// *Cause: The user is attempting to create an object type where
// more than one attributes have the same name.
// *Action: Check to make sure that all attribute names are unique.
/
22310, 00000, "ALTER TYPE error. Refer to table \"%s\".\"%s\" for errors"
// *Cause: An invalid alter type statement was submitted.
// *Action: Correct the errors listed in specified table and resubmit
// statement.
/
22311, 00000, "type for attribute \"%s\" does not exist"
// *Cause: The type of the attribute does not exist.
// *Action: No types were created/modified for this DDL transaction. Redo
// the DDL transaction and add the creation of the attribute's type
// in the DDL transaction.
/
22312, 00000, "must specify either CASCADE or INVALIDATE option"
// *Cause: An attempt was made to alter a type which has a dependent type
// or table without specifying the CASCADE or INVALIDATE option.
// *Action: Resubmit the statement with either the CASCADE or INVALIDATE
// option. Specify CASCADE if you want to cascade the type change to
// dependent types and tables; otherwise, specify INVALIDATE to
// invalidate all dependents.
/
22313, 00000, "cannot use two versions of the same type \"%s\""
// *Cause: The version of this type conflicts with the version of this
// type used by another library that was linked in with the
// application. An application may only use one version of a type.
// *Action: Check that the libraries being linked with this application and
// use the same versions of the type.
/
22314, 00000, "method information mismatch in ALTER TYPE"
// *Cause: The number of methods or the method signature do not match that
// of the original type declaration. This is not supported.
// *Action: Make sure the method signature stay identical for the previously
// declared method. Do not drop existing methods.
/
22315, 00000, "type \"%s\" does not contain a map or order function"
// *Cause: The input type does not contain a map or order function so one
// cannot be returned.
// *Action: Add a map or order function to the type or catch this error.
/
22316, 00000, "input type is not a collection type"
// *Cause: The user is trying to obtain information for collection types
// on a non-named collection type.
// *Action: Use a named collection type for the function.
/
22317, 00000, "typecode %s is not legal as a number type"
// *Cause: The user is trying to use a number typecode that is not valid.
// *Action: Use only OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER,
// OCI_TYPECODE_REAL, OCI_TYPECODE_DOUBLE, OCI_TYPECODE_FLOAT,
// OCI_TYPECODE_NUMBER, or OCI_TYPECODE_DECIMAL.
/
22318, 00000, "input type is not an array type"
// *Cause: The user is trying to obtain the number of elements for a
// non-array type.
// *Action: Pass in only a named collection type which is an array.
/
22319, 00000, "type attribute information altered in ALTER TYPE"
// *Cause: The type attribute information does not match that of the
// original type declaration when altering type. Attributes
// cannot be altered during ALTER TYPE. Only new methods can
// be added.
// *Action: Check that all type alterations are legal.
/
22320, 00000, "missing user version string"
// *Cause: The VERSION option is specified without a user version string.
// *Action: Resubmit the statement with the version string following the
// VERSION keyword.
/
22321, 00000, "method does not return any result"
// *Cause: OCITypeResult() was called on a method that does not return any
// results.
// *Action: Check that you are passing in the correct method descriptor,
// or that your method creation was done correctly.
/
22322, 00000, "error table \"%s\".\"%s\" has incorrect structure"
// *Cause: The specified error table does not have the expected table
// structure.
// *Action: Execute the DBMS_UTILITY.CREATE_ALTER_TYPE_ERROR_TABLE procedure
// to create an error table, then resubmit the statement using the
// new error table.
/
22323, 00000, "error table \"%s\".\"%s\" does not exist"
// *Cause: The error table does not exist.
// *Action: Resubmit the statement with a correct error table name.
/
22324, 00000, "altered type has compilation errors"
// *Cause: The use of the ALTER TYPE statement caused a compilation error.
// *Action: Correct the error reported and resubmit the statement.
/
22325, 00000, "event for create type with user version string"
// *Cause:
// *Action:
/
22326, 00000, "cannot change a type to FINAL if it has subtypes"
// *Cause: An attempt was made to change a type with subtypes to FINAL.
// *Action: Drop all subtypes of the target type before changing it to FINAL.
/
22327, 00000, "cannot change a type to NOT INSTANTIABLE if it has dependent tables"
// *Cause: An attempt was made to change a type with dependent tables to NOT
// INSTANTIABLE.
// *Action: Drop all dependent tables of the target type and resubmit the
// statement.
/
22328, 00000, "object \"%s\".\"%s\" has errors.\n%s"
// *Cause: Altering the target type causes errors in its dependent object.
// *Action: Correct the problem in the dependent object and resubmit the
// statement.
/
22329, 00000, "cannot alter a non-object type"
// *Cause: An attempt was made to execute ALTER TYPE on a non-object type.
// *Action: Drop the non-object type first, then re-create it as an object type.
/
22330, 00000, "cannot alter a type that is not valid"
// *Cause: An attempt was made to perform ALTER TYPE on an invalid type.
// *Action: Use the CREATE OR REPLACE TYPE command to modify the type.
/
22331, 00000, "cannot alter an incomplete type"
// *Cause: An attempt was made to perform ALTER TYPE on an incomplete type.
// *Action: Use CREATE TYPE to completely define the original type before
// executing the ALTER TYPE.
/
22332, 00000, "a dependent object in schema \"%s\" has errors.\n%s"
// *Cause: Altering the target type causes errors in its dependent object.
// *Action: Correct the problem in the dependent object and resubmit the
// statement.
/
22333, 00000, "cannot reset type \"%s\".\"%s\" due to invalid dependent types and tables"
// *Cause: An attempt was made to reset the type version with invalid
// dependent types and tables.
// *Action: Use the ALTER TYPE COMPILE statement to compile all invalid
// dependent types and use the ALTER TABLE UPGRADE INCLUDING DATA to
// upgrade all the dependent tables then resubmit the statement.
/
22334, 00000, "cannot reset type \"%s\".\"%s\". Dependent tables must be upgraded to latest version"
// *Cause: An attempt was made to reset the type version when the data in
// the dependent table has not been upgraded to the latest type
// version.
// *Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade
// the data in the dependent tables then resubmit the statement.
/
22335, 00000, "The client cannot work with an altered type"
// *Cause: A pre 8.2 client has requested a type that has been altered on the
// server.
// *Action: Only 8.2 or higher clients could access altered types
/
22336, 00000, "table contained 8.0 image format, must specify INCLUDING DATA"
// *Cause: One of the following:
// 1) An attempt was made to alter a type with a dependent table in 8.0
// image format and the NOT INCLUDING TABLE DATA option was specified.
// 2) An attempt was made to upgrade a table in 8.0 image format with
// the NOT INCLUDING DATA option specified.
// *Action: Resubmit the statement with INCLUDING DATA option.
/
22337, 00000, "the type of accessed object has been evolved"
// *Cause: The type of the accessed object has been altered and the client's
// object is based on an earlier type definition.
// *Action: The user needs to exit application and modify application to
// accommodate the type change.
// From SQL/PLUS, reconnect and resubmit statement.
/
22338, 00000, "must specify CASCADE INCLUDING DATA when altering the final property"
// *Cause: An attempt was made to alter the final property of a type with
// dependent table(s) without specifying the CASCADE INCLUDING DATA .
// option.
// *Action: Resubmit the statement with the CASCADE INCLUDING DATA option.
/
22339, 00000, "cannot alter to not final since its attribute column is substitutable"
// *Cause: An attempt was made to alter a type to not final when its
// embedded attribute is defined as substitutable in some tables.
// Note, this is a restriction in 9.0 version because when a type is
// altered to not final, column of that type is set to not
// substitutable at all levels; thus, it is an error if one of its
// embedded attribute column is already marked substitutable.
// *Action: Recreate the table and specify NOT SUBSTITUTABLE AT ALL LEVELS
// for all columns of non final type. Then resubmit the ALTER TYPE
// statement.
/
22340, 00000, "cannot %s type \"%s\".\"%s\". Dependent tables must be upgraded to latest version"
// *Cause: An attempt was made to reset the version, drop or alter a type
// when the data in dependent table has not been upgraded to
// the latest version.
// *Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade
// the data in the dependent tables then resubmit the statement.
/
22341, 00000, "cannot assign supertype instance to subtype"
// *Cause: An attempt was made to assign or copy a supertype instance to
// a container (destination) that can only hold a subtype instance.
// *Action: Make sure the runtime type of the source of the assignment or
// copy is the same type as the destination or is a subtype of the
// destination type
/
22342, 00000, "dependent VARRAY column exceeds the maximum inline column size"
// *Cause: An attempt was made to alter a type (add or modify attribute)
// which causes the size of its dependent VARRAY column to exceed the
// maximum inline column size. However, the VARRAY column was not
// specified to be stored as LOB at the table level when the table
// was created.
// *Action: Specify the VARRAY column to be stored as LOB at the table level
// when the table is created.
/
22343, 00000, "Compilation error for type invalidated by ALTER TYPE"
// *Cause: Compilation failed for a type which was invalidated by ALTER TYPE.
// We throw this error and rollback the compilation effort so that
// the user may be able to fix whatever is causing the compilation
// error and try again. It is important that we do not chnage status
// here and modify the dependency information as this will affect
// the creation of versions.
// *Action: Check what is causing teh compilation error and correct it and
// try again.
/
22344, 00000, "can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change"
// *Cause: An attempt was made to specify CONVERT TO SUBSTITUTABLE option for
// ALTER TYPE other than NOT FINAL change.
// *Action: Specify CONVERT TO SUBSTITUTABLE option only for ALTER TYPE NOT
// FINAL change.
/
22345, 00000, "recompile type %s.%s before attempting this operation"
// *Cause: An attempt was made to perform an operation which requires the
// specified datatype to be valid, but the datatype is invalid
// *Action: Recompile the specified type and retry the operation
/
22346, 00000, "Type has cyclical dependency. Should use CASCADE option"
// *Cause: An attempt was made to alter a type which has a cyclical
// dependency, with invalidate option.
// *Action: Give CASCADE option instead of INVALIDATE
/
22347, 00000, "No changes to type specified for ALTER TYPE"
// *Cause: The ALTER TYPE does not contain any changes to the type.
// *Action: If any change is required for the type, modify the ALTER TYPE to
// specify the change. Else no need for the ALTER.
/
22348, 00000, "The object type DDL is not supported in Editioned schema"
// *Cause: The object type DDL was not supported in an Editioned schema.
// *Action: Do not perform this DDL on an Editioned schema object.
/
/ Error numbers from 22350 to 22370 are reserved for ORT/KOT (Opaque Types).
/
22349, 00000, "This version of the Oracle server does not support PL/SQL package type descriptions."
// *Cause: An attempt was made to get PL/SQL package type description
// information from a version of the Oracle server that does not
// support the description of PL/SQL package types.
// *Action: Do not attempt to describe package types on this Oracle server.
/
22350, 00000, "Incomplete opaque type cannot be used here"
// *Cause: An incomplete SYS.AnyType or SYS.AnyData or SYS.AnyDataSet is
// being used inappropriately.
// *Action: Check the documentation for correct usage.
/
22351, 00000, "OCI API is not supported by this version of the Oracle server."
// *Cause: An attempt was made to call an Oracle Call Interface (OCI)
// API which is not supported by this version of the Oracle server.
// *Action: Do not call the unsupported OCI API when connected to this
// Oracle server.
/
22352, 00000, "Type is unsupported or contains an unsupported attribute or element."
// *Cause: A PL/SQL package type was not supported on the client or contained
// an attribute or element that was not supported on the client.
// Unsupported types include index by VARCHAR2 collections,
// remote types and MLSLABELs.
// *Action: Do not attempt to use unsupported PL/SQL package types or types
// that contain unsupported attributes or elements on the client.
/
/ Error numbers from 22369 to 22370 are used by SYS.DBMS_INDEXING.
/
22369, 00000, "invalid parameter encountered in method %s"
// *Cause: An invalid parameter is being passed to this method of SYS.AnyType
// ,SYS.AnyData or SYS.AnyDataSet
// *Action: Check the parameters being passed to this method and make sure
// that the parameters are allowed.
/
22370, 00000, "incorrect usage of method %s"
// *Cause: This method of SYS.AnyType or SYS.AnyData or SYS.AnyDataSet is
// being used inappropriately.
// *Action: Check the documentation for correct usage.
/
22371, 00000, "Table contains data of type %s.%s, version %s, which does not exist"
// *Cause: Some of the older versions of the type may have got deleted
// because one or more of the types it were referencing was dropped.
// *Action: These data could not be read as the whole ADT. Read the data at
// individual scalar attribute level.
/
22372, 00000, "Event for type dictionary upgrade"
// *Cause: This is an internally used event for type dictionary upgrades
// from 8.0 to 8.1.
// *Action: None.
/
22373, 00000, "Older version hashcode encountered"
// *Cause: An older version HC is encountered when creating a new version
// hahscode. Currently this is handled internally.
// *Action: None.
/
22374, 00000, "cannot reset the version of a type with table dependents"
// *Cause: The type for which reset version was requested has table
// dependents.
// *Action: None.
/
22375, 00000, "Event to check for subtypes in complete type tree"
// *Cause: This event is used to check for subtypes in
// complete type tree without any restriction on depth in the
// fix for bug# 12430142.
// *Action: None
/
22376, 00000, "Event to keep old behavior for type public synonyms"
// *Cause: A public type synonym was qualified with a schema which may
// lead to incorrect name resolution. This issue has been resolved.
// However, this event allows you to use the old behavior if desired.
// *Action: None.
/
22377, 00000, "Unpacking of ANYDATA columns is not supported for attribute columns."
// *Cause: An attribute column has been referenced in the 'modify_opaque_type'
// clause.
// *Action: Do not use an attribute column in the 'modify_opaque_type' clause.
/
22378, 00000, "cannot add, drop or modify attributes of a type with synonym dependents defined on FINAL types"
// *Cause: An attempt to ALTER TYPE [ADD | DROP | MODIFY] ATTRIBUTE on
// a type with synonym dependents defined on a FINAL type, which
// has table dependents, failed.
// *Action: None.
/
22379, 00000, "event to bypass hashcode in kottyphcequ"
// *Cause: This event is used to bypass the error \"ORA-39779\" during the
// import of table data which occurs because of the mismatch in the
// hashcodes of a user-defined type between the source and the
// target databases. The event has to be used when the source
// database has an improper hashcode for the user-defined type.
// *Action: None.
/
22380, 00000, "event to skip updating the dependencies"
// *Cause: This event is used to bypass regenerating dependencies
// during upgrade while running ALTER TABLE MOVE on type
// dictionary tables to enable storage in row. This happens on the
// upgrade path from 10.1.
// *Action: None.
/
22381, 00000, "type collation is not the same as default collation"
// *Cause: An attempt was made to ALTER TYPE COMPILE when the type collation
// was different from the current active collation. This is not
// allowed.
// *Action: Set the active collation to be the same as the type collation or
// issue the REUSE SETTINGS clause.
/
22382, 00000, "event to allow status 6 recompile to change settings"
// *Cause: This event is used to allow types in status 6 to recompile
// with current environment settings. The standard behavior is to
// reuse the current compiled settings. This is made available
// so that users can change the hashcodes of types created under
// different NLS_LANGUAGE_SEMANTICS.
// *Action: None.
/
22383, 00000, "a persistable type cannot have non-persistable attributes"
// *Cause: An attempt was made to create a persistable type with a
// non-persistable user-defined type (UDT) attribute.
// *Action: Ensure that all of the UDT attributes are persistable.
/
22384, 00000, "cannot create a column or table of a non-persistable type"
// *Cause: An attempt was made to create a column or table of a
// non-persistable type
// *Action: Ensure that the column or table type is persistable.
/
22385, 00000, "event to optimize the abort of nested table column updates"
// *Cause: This event is used to abort the unnecessary INSERT or DELETE
// of rows in the nested table storage table when the nested table
// column in the parent table does not qualify for update in the
// current row.
// *Action: None.
/
/ Error numbers from 22600 to 22699 are reserved for KOP* (pickler) and
/ Pickler Cartridge Service.
/
22600, 00000, "encountered 8.0.2 (Beta) VARRAY data that cannot be processed"
// *Cause: Production Oracle8 (8.0.3 and beyond) encounters some VARRAY data
// which was created and stored by Oracle8 8.0.2 (Beta 2).
// Production Oracle8 cannot understand or process such VARRAY data.
// *Action: Delete the VARRAY data from the table by dropping the table,
// deleting the rows, or nulling out the VARRAY columns, and then
// re-insert the VARRAY data. There is no provided
// script or tool to help automate this conversion.
/
22601, 00000, "pickler TDS context [%s] is not initialized"
// *Cause: Attempt to use the pickler TDS context without initializing it.
// *Action: Use OCIPicklerTdsCtxInit to initialize the context.
22602, 00000, "pickler TDS handle [%s] is not well-formed"
// *Cause: Attempt to use the pickler TDS handle without initializing/
// constructing it.
// *Action: Use OCIPicklerTdsInit to initialize the handle before it is
// constructed. Use OCIPicklerTdsGenerate to generate the
// TDS before its attributes can be accessed.
22603, 00000, "cannot add an attribute to the already generated TDS handle"
// *Cause: Attempt to add an attribute to the already constructed TDS.
// *Action: Use a TDS handle that is initialized but not yet constructed.
22604, 00000, "TDS handle already generated"
// *Cause: Attempt to geneate TDS that is already genearated.
// *Action: Use a TDS handle that is initialized but not yet generated.
22605, 00000, "FDO handle [%s] is not initialized"
// *Cause: Attempt to use an uninitialized FDO handle.
// *Action: Use OCIPicklerFdoInit to initialize FDO handle".
22606, 00000, "pickler image handle [%s] is not well-formed"
// *Cause: Attempt to use the image handle without initializing/
// constructing it.
// *Action: Use OCIPicklerImageInit to initialize the handle before it is
// constructed. Use OCIPicklerImageGenerate to generate the
// image before its attributes can be accessed.
22607, 00000, "image handle already generated"
// *Cause: Attempt to geneate image that is already genearated.
// *Action: Use a image handle that is initialized but not yet generated.
22608, 00000, "cannot add an attribute to the already generated image handle"
// *Cause: Attempt to add an attribute to the already constructed image.
// *Action: Use a image handle that is initialized but not yet constructed.
22609, 00000, "error %s during initialization of FDO"
// *Cause: Error during FDO initialization.
// *Action: Take an action based on the specified error.
/
22610, 00000, "error while adding a scalar to the image handle"
// *Cause: Error while adding a scalar attribute to the image handle
// *Action: Make sure image handle is initialized before adding scalar
/
22611, 00000, "TDS version is not recognized"
// *Cause: Incorrect TDS handle is passed
// *Action: Make sure image handle is initialized with the correct TDS
/
22612, 00000, "TDS does not describe a collection TDS"
// *Cause: collection construct/access routines are being on an image but
// the TDS does not describe that a collection TDS
// *Action: Make sure a collection TDS is used before invoking collection
// routines on the image handle
/
22613, 00000, "buflen does not match the size of the scalar"
// *Cause: buflen is incorrect
// *Action: Make sure buflen is correct and matches the size of the scalar
/
22614, 00000, "error while construction the collection in the image"
// *Cause: Error during the construction of collection
// *Action: Make sure image handle is initialized and
// OCIPicklerImageCollBegin is called to begin collection
/
22615, 00000, "attribute is not a collection"
// *Cause: collection routine is invoked upon a non-collection attribute
// *Action: Make sure attribute is a collection
/
22616, 00000, "image is not of Oracle 8.1 format"
// *Cause: The function being invoked is applicable only for 8.1 images
// *Action: Make sure image is of 8.1 format
/
22617, 00000, "error while accessing the image handle collection"
// *Cause: Error while accessing collection in the image handle
// *Action: Make sure image is initialized correctly and the collection
// is constructed properly.
/
22618, 00000, "attribute is a BAD NULL in the image handle"
// *Cause: attribute in question is probably the attribute of a null
// embedded image
// *Action: Make sure attribute number is valid or it is NULL or
// NOT NULL.
/
22619, 00000, "all collection elements have already been accessed"
// *Cause: Accessing a collection element after all the collection
// elements are already accessed
// *Action: This function should not be invoked any more.
/
22620, 00000, "buffer size too small to hold the value"
// *Cause: Buffer size is not enough to hold the value. Most likely
// while doing the character set conversion, a bigger buffer
// is needed.
// *Action: Pass in a bigger buffer. If the client character set format
// differs from that of server, doing the conversion may result
// in 4X expansion.
22621, 00000, "error transfering an object from the agent"
// *Cause: Any error returned from pickler routines on the agent side.
// *Action: Contact Oracle Support.
/
22625, 00000, "OCIAnyData is not well-formed"
// *Cause: Attempt to use the OCIAnyData without initializing
// constructing it.
// *Action: Use OCIAnyDataBeginConstruct to initialize the handle before it is
// adding attributes. Use OCIAnyDataEndConstruct to complete the
// construction. Or use OCIAnyDataConvert to do the construction.
// MAke sure it is properly constructed before accessing attributes.
/
22626, 00000, "Type Mismatch while constructing or accessing OCIAnyData"
// *Cause: Type supplied is not matching the type of the AnyData.
// If piece wise construction or access is being attempted, the
// type supplied is not matching the type of the current attribute.
// *Action: Make sure the type supplied matches the type of object to
// to be constucted or accessed.
/
22627, 00000, "tc [%s] must be that of object/varray/nested table"
// *Cause: Type code is not that of object/varray/nested table
// *Action: Make sure the type code is OCI_TYPECODE_OBJECT or
// OCI_TYPECODE_VARRAY or OCI_TYPECODE_TABLE
/
22628, 00000, "OCIAnyData already constructed"
// *Cause: Attempt to add attributes to OCIAnyData that is already constructed.
// *Action: Use the OCIAnyData that is initialized but not yet constructed.
/
22629, 00000, "OCIAnyData is null"
// *Cause: Attempting an operation that is not valid on null OCIAnyData
// *Action: Make sure OCIAnyData is not null.
/
22630, 00000, "attribute [%s] is null or it is not well-formed"
// *Cause: Passing an attribute that is null or not well-formed
// *Action: Make sure the attribute is not null or is well-formed.
/
22631, 00000, "attribute [%s] is is not well-formed or does not match the type"
// *Cause: Passing an attribute that is not well-formed or does not match the
// input type.
// *Action: Make sure the attribute is well-formed and matches the type specified.
/
22632, 00000, "AnyDataSet parameter is not valid for the current operation"
// *Cause: The AnyDataSet parameter is null or it is somehow invalid for
// the current operation.
// *Action: Check the documentation for the current operation.
/
22633, 00000, "Error freeing AnyDataSet"
// *Cause: AnyDataSet that is passed in may not be valid.
// *Action: Check all the AnyDataSet parameters.
/
22634, 00000, "Error adding new instance to AnyDataSet"
// *Cause: Current instance in the AnyDataSet has not been fully constructed.
// *Action: Make sure that the current instance is fully constructed before
// adding new instance.
/
22635, 00000, "time stamp with time zone type not supported "
// *Cause: OCIAnyData did not support conversion of time stamp with time
// zone when the version of time zone files differ.
// *Action: Use same version of time zone files.
/
22636, 00000, "collection unpickling failed due to corrupt image"
// *Cause: An attempt was made to convert a corrupted image.
// *Action: Ensure that the image is not corrupt.
/
22637, 00000, "A transformed image cannot be inserted or updated."
// *Cause: An attempt was made to insert or update an object column with
// transformed data. Preventing unexpected data from being written to
// disk is an internal error.
// *Action: Contact Oracle Support Services.
/
/ Error numbers from 22700 to 22799 are reserved for debugging event numbers.
/
// NLS_DO_NOT_TRANSLATE [22700,22700]
22700, 00000, "object access trace event number"
// *Cause: N/A
// *Action: If the trace event number is set to a level greater than 0 then
// all the dangling REFs are dumped.
// *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
/
/ 22799 IS THE MAXIMUM ERROR NUMBER for ORI/KO (object Interface and Subsystem)
/
/ 22800 - 22999 Reserved for object SQL:
/ 22800 - 22849 Reserved for object SQL Query/DML
/ (parse, semantics, type checkin, execution)
/ 22850 - 22879 Reserved for object SQL DDL
/ (parse, semantics, type checkin, execution)
/ 22880 - 22899 Reserved for object SQL REF/DEREF Support
/ (parse, semantics, type checkin, execution/KOKA)
/ 22900 - 22919 Reserved for SQL Nested Tables and Collections
/ (parse, semantics, type checkin, execution)
/ 22920 - 22929 Reserved for SQL LOBs
/ 22930 - 22949 Reserved for object SQL Dictionary Support
/ 22950 - 22969 Reserved for object SQL Method Support
/ 22970 - 22989 Reserved for object Views
/ 22990 - 22999 Reserved for SQL LOBs
/
/
/ 22800 - 22849 Reserved for object SQL Query/DML
/ (parse, semantics, type checkin, execution)
/
22800, 00000, "invalid user-defined type"
// *Cause: An attempt was made to use an incomplete type as a constructor.
// *Action: Complete the type definition before using it in a query.
22801, 00000, "invalid object row variable"
// *Cause: The specified object row variable is not available in the scope
// of name resolution.
// *Action: Verify the specified object row variable is correct,
// or use an object row variable visible in scope.
22802, 00000, "remote implementation type not supported"
// *Cause: Remote type reference was not supported
// with user-defined aggregate function.
// *Action: Use local implementation type with user-defined
// aggregate function.
22803, 00000, "object type contains zero attributes"
// *Cause: An attempt was made to create or specify a column or constructor
// of an object type that has no attributes. Only object types
// that have at least one attribute are allowed in this context.
// *Action: specify a valid object type
22804, 00000, "remote operations not permitted on object tables or user-defined type columns"
// *Cause: An attempt was made to perform queries or DML operations on
// remote object
// tables or on remote table columns whose type is one of object,
// REF, nested table or VARRAY.
22805, 00000, "cannot insert NULL object into object tables or nested tables"
// *Cause: An attempt was made to insert a NULL object into an object table
// or a Nested Table.
// *Action: Ensure that a non-NULL object is inserted into the table or
// insert an object with attributes whose values are NULL.
22806, 00000, "not an object or REF"
// *Cause: An attempt was made to extract an attribute from an item that is
// neither an object nor a REF.
// *Action: Use an object type or REF type item and retry the operation.
22807, 00000, "cannot resolve to a scalar type or a collection type"
// *Cause: Invalid use of a non-scalar (for example, object type) item.
// *Action: Change the item's data type and retry the operation.
22808, 00000, "REF dereferencing not allowed"
// *Cause: An attempt was made to access an object type's attributes by
// dereferencing
// a REF item.
// *Action: Make the item an object type instead of a REF to an object type.
22809, 00000, "nonexistent attribute"
// *Cause: An attempt was made to access a non-existent attribute of an
// object type.
// *Action: Check the attribute reference to see if it is valid. Then retry
// the operation.
22810, 00000, "cannot modify object attributes with REF dereferencing"
// *Cause: An attempt was made to modify the attributes an object by
// dereferencing a REF column in an UPDATE statement.
// *Action: Update the table containing the object that the REF points to, or
// change the REF column to an object type column.
22812, 00000, "cannot reference nested table column's storage table"
// *Cause: An attempt to access the nested table column's storage table is
// not allowed in the given context.
// *Action: Issue the statement against the parent table containing the
// nested table column.
22813, 00000, "operand value exceeds system limits"
// *Cause: Object or Collection value was too large. The size of the value
// might have exceeded 30k in a SORT context, or the size might be
// too big for available memory.
// *Action: Choose another value and retry the operation.
22814, 00000, "attribute or element value is larger than specified in type"
// *Cause: Value provided for the object type attribute or collection element
// exceeded the size specified in the type declaration.
// *Action: Choose another value and retry the operation.
22815, 00000, "sql name resolution event"
// *Document: NO
// *Cause: N/A
// *Action: Sets weak name resolution on for object sql
22816, 00000, "unsupported feature with RETURNING clause"
// *Cause: RETURNING clause is currently not supported for object type
// columns, LONG columns, remote tables, INSERT with subquery,
// and INSTEAD OF Triggers.
// *Action: Use separate select statement to get the values.
22817, 00000, "subquery not allowed in the default clause"
// *Cause: An attempt was made to use a subquery in the column default
// clause expression.
// *Action: Remove the subquery from the default clause.
22818, 00000, "subquery expressions not allowed here"
// *Cause: An attempt was made to use a subquery expression where these
// are not supported.
// *Action: Rewrite the statement without the subquery expression.
22819, 00000, "scope of input value does not correspond to the scope of the target"
// *Cause: An attempt to operate on a REF value scoped to a different table
// than the expected one
// *Action: Use a ref which is scoped to the expected table and retry
// the operation
22820, 00000, "Event to turn off redundant join elimination by the optimizer"
// *Document: NO
// *Cause: N/A
// *Action: Turns off redundant-join-elimination
22821, 00000, "Event to turn off common subexpression elimination"
// *Document: NO
// *Cause: N/A
// *Action: Turns off common subexpression elimination
22822, 00000, "Event to accept dot notation in the insert statement"
// *Document: NO
// *Cause: N/A
// *Action: Enables dot notation in insert statements
22824, 00000, "Event to lookup remote objects using DDFNET for snapshots"
// *Document: NO
// *Cause: N/A
// *Action: Enables lookup of remote objects through DDFNET for snapshots
// rather than using the remote transfer KGL mechanism.
22825, 00000, "event set during import/export"
// *Document: NO
// *Cause: N/A
// *Action: Enables logical transformation of opaque types
22826, 00000, "cannot construct an instance of a non instantiable type"
// *Cause: An attempt was made to use a non instantiable type
// as a constructor.
// *Action: None.
22827, 00000, "Event to lookup remote objects using KGL"
// *Document: NO
// *Cause: N/A
// *Action: Enables lookup of remote objects through the remote
// tranfer KGL mechanism instead of ddfnet.
22828, 00000, "input pattern or replacement parameters exceed 32K size limit"
// *Cause: Value provided for the pattern or replacement string in the form of
// VARCHAR2 or CLOB for LOB SQL functions exceeded the 32K size limit.
// *Action: Use a shorter pattern or process a long pattern string in multiple
// passes.
22829, 00000, "Event to allow LATERAL views"
// *Document: NO
// *Cause: N/A
// *Action: Enables usage of LATERAL views. This event can
// be removed once this feature is tested and documented.
22830, 00000, "Event enabling VARRAYs columns to be created as OCTs"
// *Document: NO
// *Cause: N/A
// *Action: Enables all VARRAY columns to be created as Ordered
// Collection in Tables (ie with table storage)
22831, 00000, "Offset or offset+amount does not land on character boundary"
// *Document: NO
// *Cause: (1) Source offset for BFILE (in bytes) does not start
// from a complete character.
// (2) Starting offset to read or write a LOB cuts into
// a surrogate pair.
// (3) The end of a LOB write (offset+amount) cuts into
// a surrogate pair.
// *Action: (1) Make sure offset land on character boundary.
// (2) Try to adjust the offset by (+/-)1 UCS2 codepoint.
// (3) Try to adjust the amount by (+/-)1 UCS2 codepoint.
22832, 00000, "Event enabling LOB columns to share the same segment"
// *Document: NO
// *Cause: N/A
// *Action: Enables all LOB columns to share the same segment
22833, 00000, "Must cast a transient type to a persistent type"
// *Cause: An attempt was made to use the transient type in the query
// result.
// *Action: Cast the transient type to a structurally equivalent persistent
// type.
22834, 00000, "Event to turn off smon cleanup for transient types"
// *Document: NO
// *Cause: N/A
// *Action: Turn off SMON cleanup for transient types.
//
22835, 00000, "Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: %s, maximum: %s)"
// *Cause: An attempt was made to convert CLOB to CHAR or BLOB to RAW, where
// the LOB size was bigger than the buffer limit for CHAR and RAW
// types.
// Note that widths are reported in characters if character length
// semantics are in effect for the column, otherwise widths are
// reported in bytes.
// *Action: Do one of the following:
// 1. Make the LOB smaller before performing the conversion,
// for example, by using SUBSTR on CLOB
// 2. Use DBMS_LOB.SUBSTR to convert CLOB to CHAR or BLOB to RAW.
22836, 00000, "Event to turn on lob to char/raw silent truncation"
// *Document: NO
// *Cause: N/A
// *Action: Do not throw error 22835 for truncation during LOB to CHAR/RAW
// conversion. Truncate the data instead.
22837, 00000, "Relational hint or keyword is disallowed for user-level DML"
// *Document: YES
// *Cause: An attempt was made to use relational hint or keyword in user-
// level DML.
// *Action: Avoid using DML with relational hint or keyword.
22838, 00000, "Event to enable to allow user-level relational hint or keyword and direct updates on SYS_NC columns"
// *Document: NO
// *Cause: N/A
// *Action: Do not throw error 22837 for user-level relational hint or
// keyword, or 22839 for direct updating SYS_NC columns.
22839, 00000, "Direct updates on SYS_NC columns are disallowed"
// *Document: YES
// *Cause: An attempt was made to update SYS_NC columns directly.
// *Action: Avoid direct updates on SYS_NC columns.
22840, 00000, "REF column being indexed is not scoped"
// *Document: NO
// *Cause: N/A
// *Action: Index creation on REF column should be scoped.
22841, 00000, "DML on PL/SQL collections not supported"
// *Document: NO
// *Cause: An attempt was made to perform a DML operation on a collection
// type in a PL/SQL block.
// *Action: Feature not supported yet.
22842, 00000, "Event to enable image conversion for evolved ADT inside an AnyData column"
// *Document: NO
// *Cause: N/A
// *Action: Convert an old version ADT image inside an AnyData column into
// its most updated version.
22843, 00000, "Renaming or direct DML on out-of-line tables is not allowed."
// *Document: NO
// *Cause: Rename or a DML was invoked directly on out-of-line tables.
// *Action: Avoid renaming out-of-line tables. Use DML on base tables.
22844, 00000, "ERROR LOGGING not supported with INSTEAD OF triggers."
// *Document: NO
// *Cause: ERROR LOGGING clause was not supported for DML operation
// on views that have an INSTEAD OF trigger defined.
// *Action: Avoid using ERROR LOGGING clause.
22845, 00000, "REF_CASCADE_CURSOR hint is not allowed in user-level queries."
// *Document: No
// *Cause: An attempt was made to use hint that is not allowed.
// *Action: Do not specify REF_CASCADE_CURSOR hint.
22846, 00000, "Relational CTAS or INSERT ... SELECT on an object table is not supported with supplemental logging turned on."
// *Document: NO
// *Cause: While supplemental logging was turned on, a CREATE TABLE AS
// SELECT (CTAS) attempt was made to create an object table with a
// relational subquery, or an INSERT ... SELECT happened on an
// object table with a relational subquery.
// *Action: Use OBJECT_VALUE or an object constructor in the subquery.
22847, 00000, "cannot generate ANYDATA with BFILE or OPAQUE TYPE inside"
// *Document: NO
// *Cause: When an XML was generated from an ANYDATA with BFILE or OPAQUE
// TYPE in it, it could not be transformed back into a valid ANYDATA.
// *Action: Avoid generating ANYDATA from such XML documents.
/
/
/ 22850 - 22879 Reserved for object SQL DDL
/ (parse, semantics, type checkin, execution)
/
22850, 00000, "duplicate LOB storage option specificed"
// *Cause: A LOB storage option (CHUNK, PCTVERSION, CACHE, NOCACHE,
// TABLESPACE, STORAGE, INDEX, SECUREFULE/BASICFILE, [A]SYNC) was
// specified more than once.
// *Action: Specify all LOB storage options only once.
/
22851, 00000, "invalid CHUNK LOB storage option value"
// *Cause: The specified CHUNK LOB storage option value must be an integer.
// *Action: Choose an appropriate integer value and retry the operation.
/
22852, 00000, "invalid PCTVERSION LOB storage option value"
// *Cause: The specified PCTVERSION LOB storage option value must be an
// integer.
// *Action: Choose an appropriate integer value and retry the operation.
/
22853, 00000, "invalid LOB storage option specification"
// *Cause: A LOB storage option was not specified
// *Action: Specify one of CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE,
// STORAGE, INDEX, [A]SYNC or DATA SYNC as part of the LOB storage
// clause.
/
22854, 00000, "invalid option for LOB storage index"
// *Cause: A valid LOB store index option was not specified.
// *Action: Specify one of (INITRANS, MAXTRANS, TABLESPACE, STORAGE) as
// part of the LOB storage index.
/
22855, 00000, "optional name for LOB storage segment incorrectly specified"
// *Cause: The optional name for LOB storage segment was specified with
// multiple columns in the column list.
// *Action: Specify each column LOB storage only with optional name(s).
/
22856, 00000, "cannot add columns to object tables"
// *Cause: An attempt was made to add columns to an object table. Object
// tables cannot be altered to add columns since its
// definition is based on an object type.
// *Action: Create a new type with additional attributes, and use the new
// type to create an object table. The new object table will have
// the desired columns.
/
22857, 00000, "cannot modify columns of object tables"
// *Cause: An attempt was made to alter the object table by modifing
// existing columns. An object table cannot be altered to modify
// existing columns since it is based on an object type. The table
// definition must be in sync with the corresponding type.
// *Action: Create a new type with the desired attribute types and use it
// to create an object table. The new object table will have the
// desired columns.
/
22858, 00000, "invalid alteration of datatype"
// *Cause: An attempt was made to modify the column type to object, REF,
// nested table, VARRAY or LOB type.
// *Action: Create a new column of the desired type and copy the current
// column data to the new type using the appropriate type
// constructor.
/
22859, 00000, "invalid modification of columns"
// *Cause: An attempt was made to modify an object, REF, VARRAY, nested
// table, or LOB column type.
// *Action: Create a new column of the desired type and copy the current
// column data to the new type using the appropriate type
// constructor.
22860, 00000, "object type expected"
// *Cause: An attempt was made to create an object table using a non-
// object type, or to create a column that is a REF to a non-object
// type.
// *Action: Use a valid object type in the table or column definition.
22861, 00000, "invalid user-defined type"
// *Cause: An attempt was made to create a column or object table of a non-
// existent type.
// *Action: Specify a valid type in the table or column definition.
22862, 00000, "specified object identifier doesn't match existing object identifier"
// *Cause: An attempt was made to specify an object identifier for the type
// that does not match the existing identifier of the incomplete
// type of the same name.
// *Action: Specify the correct object identifier or leave it out of the
// statement.
22863, 00000, "synonym for datatype %s.%s not allowed"
// *Cause: A synonym specification for a datatype is not supported
// *Action: do not use the synonym for the datatype
22864, 00000, "cannot ALTER or DROP LOB indexes"
// *Cause: An attempt was made to ALTER or DROP a LOB index.
// *Action: Do not operate directly on the system-defined LOB index.
// Perform operations on the corresponding LOB column.
22865, 00000, "more than one column specified"
// *Cause: An attempt was made to specify multiple columns where only one is
// allowed.
// *Action: Specify a single column and retry the operation.
22866, 00000, "cannot replace a type with table dependents"
// *Cause: An attempt was made to replace a type that has table dependents.
// *Action: Drop all table(s) depending on the type, then retry
// the operation.
22868, 00000, "table with LOBs contains segments in different tablespaces"
// *Cause: An attempt was made to drop a tablespace which contains the
// segment(s) for the LOB columns of a table but does not contain
// the table segment.
// *Action: Find table(s) with LOB columns which have non-table segments in
// this tablespace. Drop these tables and reissue drop tablespace.
22869, 00000, "depth of type dependency hierarchy exceeds maximum limit"
// *Cause: The type dependency hierarchy was structured to have depth greater
// than 1024.
// *Action: Re-structure the type dependency hierarchy to a shorter depth.
22870, 00000, "ALTER TYPE with REPLACE option a non-object type"
// *Cause: attempt to perform ALTER TYPE with REPLACE option a non-object type
// *Action: drop the non-object type first, then re-create it as an object type
22871, 00000, "ALTER TYPE with REPLACE is not allowed for pure incomplete types"
// *Cause: An attempt to perform ALTER TYPE with REPLACE option for a pure incomplete type
// *Action: Completely define the original type, before using the ALTER TYPE with REPLACE option.
22872, 00000, "OID INDEX clause not allowed on tables with primary key based object identifiers"
// *Cause: An attempt to create an OID INDEX on a table with primary key
// based object identifiers.
// *Action: Remove the OID INDEX clause
22873, 00000, "primary key not specified for primary key based object table"
// *Cause: An attempt to create a primary key based object table without
// specifying a primary key
// *Action: Specify a primary key and retry the operation
22874, 00000, "attribute \"%s\" is not part of the type \"%s\""
// *Cause: Attribute specified in the user_defined clause is not an
// attribute of the REF type
// *Action: Ensure that the name specified in the user_defined
// clause is the name of a valid attribute of the REF type
22875, 00000, "cannot drop primary key of an object table whose object identifier is primary key based"
// *Cause: An attempt to drop the primary key of an object table which has
// a primary key based object identifier
// *Action: Remove the drop primary key clause
22876, 00000, "this user-defined type is not allowed or it cannot be used in this context"
// *Cause: An attempt to create a kind of user-defined type which is not
// allowed, or an attempt to create table columns or use default
// constructor with a type on which these are not supported.
// *Action: Ensure that the type is permitted in this context.
22877, 00000, "invalid option specified for a HASH partition or subpartition of a LOB column"
// *Cause: One or more invalid options were encountered while parsing the
// physical attributes of a LOB partition or subpartition. Either
// the LOB partition is in a table partitioned using the HASH method,
// or the LOB subpartition is in a table subpartitioned using the
// HASH method. TABLESPACE is the only valid option for a HASH
// partition or subpartition.
// *Action: Remove the invalid option(s).
// *Comment: This error could result from omission of a
// terminating (right) parenthesis following the list of
// subpartition descriptions.
22878, 00000, "duplicate LOB partition or subpartition specified"
// *Cause: An attempt was made to specify a partition or subpartition that
// has already been specified for the LOB column.
// *Action: Remove the duplicate specification.
22879, 00000, "cannot use the LOB INDEX clause for partitioned tables"
// *Cause: An attempt was made to specify a LOB INDEX clause in a CREATE
// TABLE or ALTER TABLE statement for a partitioned table.
// *Action: Remove the LOB INDEX clause.
/
/
/ Put errors here.
/
/ 22880 - 22899 Reserved for object SQL REF/DEREF Support
/ (parse, semantics, type checkin, execution/KOKA)
/
22880, 00000, "invalid REF"
// *Cause: An invalid REF was accessed.
// *Action: Modify the REF and retry the operation.
/
22881, 00000, "dangling REF"
// *Cause: The object corresponding to the REF that was accessed does not
// exist.
// *Action: Ensure that the REF value is pointing to an existing object.
/
22882, 00000, "object creation failed"
// *Cause: The object cannot be created in the database.
// *Action: Check to see if the object table exists and the object size is
// not too big. Then retry the operation.
/
22883, 00000, "object deletion failed"
// *Cause: The object could not be deleted from the database.
// *Action: Check to see if the object table exists.Then retry the operation.
/
22884, 00000, "object modification failed"
// *Cause: The object could not be modified in the database.
// *Action: Check to see if the object table exists and the object size is
// not too big. Then retry the operation.
22885, 00000, "cannot get REF to a non-persistent object"
// *Cause: An attempt was made to get a REF for something other than an
// object in an object table. REFs can only be taken for objects
// in object tables.
// *Action: Rewrite the query to obtain REF values from object tables.
22886, 00000, "scoped table \"%s\" in schema \"%s\" is not an object table"
// *Cause: The scoped table specified for a REF column is not an object
// table.
// *Action: Ensure that the scoped table is an object table.Then retry the
// operation.
22887, 00000, "type of REF column is not the same as that of its scoped table"
// *Cause: The type specified for the REF column and the type specified
// for the scope table are different.
// *Action: Ensure that the types of a REF column and its scoped table are
// the same.
22888, 00000, "duplicate SCOPE clauses for a REF column"
// *Cause: Multiple SCOPE clauses were specified for a single REF column.
// *Action: Remove the duplicate SCOPE clauses and retry the operation.
22889, 00000, "REF value does not point to scoped table"
// *Cause: An attempt was made to insert a REF value that does not point
// to the scoped table.
// *Action: Ensure that the REF values point to the scoped table.
22890, 00000, "cannot specify name for REF column constraint"
// *Cause: An attempt was made to specify a constraint name for a
// constraint on a REF column.
// *Action: Remove the constraint name and retry the operation.
22891, 00000, "cannot have multiple columns in REF constraint"
// *Cause: An attempt was made to specify multiple columns in a single
// REF constraint.
// *Action: Specify separate constraints for each column and retry the
// operation.
22892, 00000, "scoped table \"%s\" does not exist in schema \"%s\""
// *Cause: The scoped table specified for a REF column does not exist.
// *Action: Ensure that the scoped table exists and retry the operation.
22893, 00000, "constraint can be specified only for REF columns"
// *Cause: The constraint specified does not apply to non-REF columns.
// *Action: Remove the constraint and retry the
// operation.
22894, 00000, "cannot add constraint on existing unscoped REF columns of non-empty tables"
// *Cause: An attempt was made to add a constraint to existing unscoped
// REF columns of a table which contains one or more rows.
// *Action: Remove the constraint specification or add the constraint after
// emptying the table.
22895, 00000, "referenced table \"%s\" in schema \"%s\" is not an object table"
// *Cause: The referenced table specified for a REF column is not an object
// table.
// *Action: Ensure that the referenced table is an object table.Then retry the
// operation.
22896, 00000, "cannot have both scope and referential constraint on REF column \"%s\""
// *Cause: REF column has both a referential and a scope constraint. A
// referential constraint implies a scope constraint.
// *Action: Remove either the referential or scope constraint and then
// retry the operation.
22897, 00000, "no scope clause specified for user-defined REF column \"%s\""
// *Cause: User-defined REF column does not have a scope constraint.
// *Action: Specify a scope constraint for the user-defined REF column and
// retry the operation.
22898, 00000, "existing scope clause on \"%s\" points to a table other than the one mentioned in the referential constraint"
// *Cause: Table mentioned in the referential integrity constraint is
// different from the scope table of the REF column.
// *Action: Specify the scope table of the REF column in the referential
// integrity constraint and then retry the operation.
22899, 00000, "cannot specify both scope and rowid constraint on ref column"
// *Cause: An attempt was made to specify both a scope and a rowid constraint
// on a REF column.
// *Action: Remove either the rowid or scope constraint and then
// retry the operation.
/
/
/
/ 22900 - 22919 Reserved for SQL Nested Tables and collections
/ (parse, semantics, type checkin, execution)
/
22900, 00000, "the SELECT list item of THE subquery is not a collection type"
// *Cause: The THE subquery must SELECT a nested table or VARRAY item.
// *Action: change the subquery to SELECT a nested table or VARRAY item.
/
22901, 00000, "cannot compare VARRAY or LOB attributes of an object type"
// *Cause: Comparison of VARRAY or LOB attributes of an object type
// was attempted in the absence of a MAP or ORDER method.
// *Action: Define a MAP or ORDER method for the object type.
/
22902, 00000, "CURSOR expression not allowed"
// *Cause: CURSOR on a subquery is allowed only in the top-level
// SELECT list of a query.
// *Action:
/
22903, 00000, "MULTISET expression not allowed"
// *Cause: MULTISET expressions are allowed only inside a CAST
// to a nested table or VARRAY type.
// *Action: put the MULTISET(subquery) expression inside a CAST to a
// nested table or VARRAY type.
/
22904, 00000, "invalid reference to a nested table column"
// *Cause: invalid use of a nested table column
// *Action: remove invalid reference to the nested table column
/
22905, 00000, "cannot access rows from a non-nested table item"
// *Cause: attempt to access rows of an item whose type is not known at
// parse time or that is not of a nested table type
// *Action: use CAST to cast the item to a nested table type
/
22906, 00000, "cannot perform DML on expression or on nested table view column"
// *Cause: Attempted to perform a DML on an expression or on a nested table
// view column where a nested table column of a base table is
// expected.
// *Action: Only nested table column of a base table is allowed in the DML.
/
22907, 00000, "invalid CAST to a type that is not a nested table or VARRAY"
// *Cause: Attempted to CAST to a type that is not a nested table or
// VARRAY
// *Action: Re-specify CAST to a nested table or VARRAY type.
/
22908, 00000, "reference to NULL table value"
// *Cause: The evaluation of the THE subquery or nested table column
// resulted in a NULL value implying a NULL table instance.
// The THE subquery or nested table column must identify a
// single non-NULL table instance.
// *Action: Ensure that the evaluation of the THE subquery or nested table
// column results in a single non-null table instance. If happening
// in the context of an insert statement where the THE subquery is
// the target of an insert, then ensure that an empty nested table
// instance is created by updating the nested table column of the
// parent table's row specifying an empty nested table constructor.
22909, 00000, "exceeded maximum VARRAY limit"
// *Cause: The total number of elements used in VARRAY construction
// exceeds the specified VARRAY limit.
// *Action: Don't use the more than the specified limit of elements for
// VARRAY construction.
22910, 00000, "cannot specify schema name for nested tables"
// *Cause: Table name was qualified with schema name in the nested table
// column's (or attribute's) storage clause.
// *Action: Re-specify the nested table item's storage clause without the
// schema name qualification. By default, the storage table for the
// nested table item is created in the same schema as the containing
// table.
/
22911, 00000,"duplicate storage specification for the nested table item"
// *Cause: The storage clause is specified more than once for the NESTED
// TABLE column.
// *Action: Remove the duplicate storage specification.
/
22912, 00000,"specified column or attribute is not a nested table type"
// *Cause: The storage clause is specified for a column or attribute
// that is not a nested table column or attribute.
// *Action: Specify a valid nested table column or attribute.
/
22913, 00000,"must specify table name for nested table column or attribute"
// *Cause: The storage clause is not specified for a nested table column
// or attribute.
// *Action: Specify the nested table storage clause for the nested table
// column or attribute.
/
22914, 00000,"DROP of nested tables not supported"
// *Cause: Attempted to DROP a nested table.
// *Action: nested tables cannot be explicitly dropped. nested tables can
// only be dropped by dropping their containing parent table.
/
22915, 00000,"cannot ALTER a nested table's storage table to ADD/MODIFY columns"
// *Cause: An attempt was made to ADD or MODIFY columns of a nested table's
// storage table.
// *Action: Columns cannot be added or modified for a nested table's storage
// table. You must alter the parent table's nested table column to
// cause any such change.
/
22916, 00000,"cannot do an exact FETCH on a query with Nested cursors"
// *Cause: Exact FETCH on a query was specified which is not allowed if
// the query returns any cursors.
// *Action: Do not use an exact FETCH.
/
22917, 00000,"use VARRAY to define the storage clause for this column or attribute"
// *Cause: Not using VARRAY to define storage clause for VARRAY column or
// attribute.
// *Action: Specify VARRAY before the column storage clause and resubmit
// statement.
/
22918, 00000,"specified column or attribute is not a VARRAY type"
// *Cause: Attemp to define a VARRAY storage clause for a column or
// attribute which is not VARRAY type.
// *Action: Specify VARRAY storage clause for a VARRAY column or attribute.
/
22919, 00000, "dangling REF error or lock object failed for no wait request"
// *Cause: The error could be one of the following. The object corresponding
// to the REF does not exist or the object was locked
// by another user and the lock with nowait request failed.
// *Action: Ensure that the REF value is pointing to an existing object or
// issue a lock request without the nowait option.
/
/ Put errors here.
/
/ 22920 - 22929 Reserved for SQL LOBs
/
22920, 00000, "row containing the LOB value is not locked"
// *Cause: The row containing the LOB value must be locked before
// updating the LOB value.
// *Action: Lock the row containing the LOB value before updating the LOB
// value.
22921, 00000, "length of input buffer is smaller than amount requested"
// *Cause: The buffer length is not big enough to hold the amount of data
// requested.
// *Action: Verify that the number of bytes/characters specified in the
// input amount parameter is not bigger than the number of bytes
// specified in the input buffer length parameter. Allocate more
// space for the input buffer if necessary.
22922, 00000, "nonexistent LOB value"
// *Cause: The LOB value associated with the input locator does not exist.
// The information in the locator does not refer to an existing LOB.
// *Action: Repopulate the locator by issuing a select statement and retry
// the operation.
22923, 00000, "amount of data specified in streaming LOB write is 0"
// *Cause: Trying to write LOB value via the streaming mechanism (i.e.
// unlimited write) but the input amount of data to stream was
// specified as 0. Thus, the user is trying to write 0 bytes to
// the LOB value.
// *Action: Write more than 0 bytes to the LOB value.
22924, 00000, "snapshot too old"
// *Cause: The version of the LOB value needed for the consistent read was
// already overwritten by another writer.
// *Action: Use a larger version pool.
22925, 00000, "operation would exceed maximum size allowed for a LOB value"
// *Cause: An attempt was made to write too much data to the LOB value.
// LOB size is limited to (4 gigabytes - 1) * DB_BLOCK_SIZE.
// *Action: Either start writing at a smaller LOB offset or write less data
// to the LOB value.
22926, 00000, "specified trim length is greater than current LOB value's length"
// *Cause: The input length for which to trim the LOB value to is greater
// than the current length of the LOB value.
// *Action: May not need to trim the LOB value because it's already smaller
// than the trim length specified. Or, if trimming the LOB value
// really is required, use a smaller trim length.
22927, 00000, "invalid LOB locator specified"
// *Cause: There are several causes: (1) the LOB locator was never
// initialized; (2) the locator is for a BFILE and the routine
// expects a BLOB/CLOB/NCLOB locator; (3) the locator is for a
// BLOB/CLOB/NCLOB and the routine expects a BFILE locator;
// (4) trying to update the LOB in a trigger body -- LOBs in
// trigger bodies are read only.
// *Action: For (1), initialize the LOB locator by selecting into the locator
// variable or by setting the LOB locator to empty. For (2) and (3),
// pass the correct type of locator into the routine. For (4),
// remove the trigger body code that updates the LOB value.
22928, 00000, "invalid privilege on directories"
// *Cause: An attempt was made to grant or revoke an invalid privilege on a
// directory.
// *Action: Only CREATE, DELETE, READ, WRITE and EXECUTE privileges can be
// granted or revoked on directories. Do not grant or revoke other
// privileges.
22929, 00000, "invalid or missing directory name"
// *Cause: The required directory name is invalid or missing.
// *Action: Specify a valid name.
/ Put errors here.
/
/ 22930 - 22949 Reserved for object SQL Dictionary Support
/
22930, 00000, "directory does not exist"
// *Cause: Attempt to access a directory that does not exist.
// *Action: Make sure the name is correct.
22932, 00000, "event to create tables in 8.0 image format"
// *Document: NO
// *Cause: N/A
// *Action: Causes adt columns to be stored in 8.0 format.
22933, 00000, "cannot change object with type or table dependents"
// *Cause: Attempt to replace, drop or rename an object with type
// or table dependents.
// *Action: Drop depending objects or use FORCE option if available.
22934, 00000, "event to store lob columns with very small headers"
// *Document: NO
// *Cause: N/A
// *Action: Supports LOB column with small header
22935, 00000, "event to create LOBs as UCS2"
// *Document: NO
// *Cause: N/A
// *Action: Creates LOB as UCS2 on little endian machines
22936, 00000, "cannot replace a system predefined type"
// *Cause: An attempt was made to replace a system predefined type.
// *Action: Use other names for newly created system types.
/
/ Put errors here.
/
/ 22950 - 22969 Reserved for object SQL Method Support
/
22950, 00000, "cannot ORDER objects without MAP or ORDER method"
// *Cause: an object type must have a MAP or ORDER method defined for
// all comparisons other than equality and inequality comparisons.
// *Action: Define a MAP or ORDER method for the object type
//
/
22951, 00000, "NULL returned by ORDER method"
// *Cause: ORDER method used to compare two object values returned NULL
// which is not allowed.
// *Action: Redefine the ORDER method to not return a NULL.
//
/
22952, 00000, "Nested Table equality requires a map method on the element ADT"
// *Cause: Nested Table equality was tried where the element ADT did not have
// a map method defined on it.
// *Action: Define a map method on the element ADT..
//
/
22953, 00000, "Cardinality of the input to powermultiset exceeds maximum allowed"
// *Cause: The cardinality of the input nested table to the powermultiset
// should not exceed 32 elements
// *Action: Reduce the number of elements to the input.
//
/
22954, 00000, "This multiset operation is not supported for this element type."
// *Cause: The multiset operation attempted was not supported for the
// nested table element type.
// *Action: Use a supported element type.
//
/
22955, 00000, "The cardinality parameter is not within the allowed limits"
// *Cause: The cardinality parameter has to be greater than 1 and less than
// or equal to the cardinality of the input.
// *Action: Give a valid cardinality value.
//
/
22956, 00000, "The set contains no elements"
// *Cause: An empty set was given as input to the powermultiset function.
// *Action: Give a non-empty set as input
//
/
22957, 00000, "NULL is an invalid input to powermultiset and COLLECT functions"
// *Cause: NULL was given as input to the powermultiset or COLLECT function.
// *Action: Give a non-null value as input
//
/
22958, 00000, "This operation is not allowed in check constraints or triggers"
// *Cause: An invalid operation is used in a check constraint or trigger
// *Action: Do not use the operation
//
/
/ 22970 - 22989 Reserved for object Views
/
22970, 00000, "name does not correspond to an object view"
// *Cause: Either the expression is not a view name or the name
// specified does not correspond to an object view.
// *Action: Replace the expression with the name of an object view.
//
22971, 00000, "invalid datatype for PRIMARY KEY-based object identifier"
// *Cause: When creating an object view, the datatype of an expression
// in the WITH OBJECT OID clause is not allowed for
// PRIMARY KEY-based OID.
// *Action: Replace the expression with one of appropriate scalar datatype.
//
22972, 00000, "NULL value not allowed in PRIMARY KEY-based object identifier"
// *Cause: A value constituting the PRIMARY KEY-based object identifier is
// NULL.
// *Action: Ensure the expressions in MAKE_REF system function or attributes
// in the WITH OBJECT OID clause of an object view do not evaluate
// to NULL.
//
22973, 00000, "size of object identifier (%s) exceeds maximum size allowed"
// *Cause: Size of the PRIMARY KEY-based object identifier of an object
// view exceeds the maximum size of 4000 bytes.
// *Action: Specify fewer or smaller PRIMARY KEY attributes in the WITH
// object OID clause when creating the object view.
//
22974, 00000, "missing WITH OBJECT OID clause"
// *Cause: WITH OBJECT OID clause is not specified when creating an object
// view.
// *Action: Specify the WITH OBJECT OID clause.
22975, 00000, "cannot create a PRIMARY KEY-based REF to this object view"
// *Cause: The object view specified in the MAKE_REF function does not
// have a PRIMARY KEY-based object identifier. A PRIMARY KEY-based
// REF cannot be created for such a view.
// *Action: Specify an object view that has a PRIMARY KEY-based object
// identifier in the MAKE_REF function.
22976, 00000, "incorrect number of arguments to MAKE_REF"
// *Cause: Number of arguments for MAKE_REF is different from the number
// of PRIMARY KEY attributes of the object view.
// *Action: Specify all the necessary arguments for MAKE_REF.
22977, 00000, "missing or invalid attribute"
// *Cause: Either the attribute name is missing in the WITH OBJECT OID clause
// or it is invalid.
// *Action: Specify a valid attribute of the object type of the object view.
22978, 00000, "only simple attribute name is allowed in the WITH OBJECT OID clause"
// *Cause: Attempted to specify a Nested attribute in the WITH OBJECT OID
// clause.
// *Action: Specify a top-level attribute of the object type of the object
// view.
22979, 00000, "cannot INSERT object view REF or user-defined REF"
// *Cause: Attempt to insert an object view REF or user-defined REF in a
// REF column created to store system generated REF values"
// *Action: Make sure the REF to be inserted is not from an object view
// or from a user-defined REF column
22980, 00000, "must specify a set of attributes for the WITH OBJECT OID clause"
// *Cause: The WITH OBJECT OID DEFAULT clause was used, but the underlying
// view or table does not have a OID.
// *Action: Specify attributes for the WITH OBJECT OID clause to create a
// primary key based object identifier for the object view.
22981, 00000, "must specify a table/view having system generated OID"
// *Cause: The super-view is based on a table/view having the system generated
// OID and the sub-view must also be based on a similar table/view.
// *Action: Specify table/view having system generated OID and retry the
// the operation.
22982, 00000, "cannot create sub-view under this view"
// *Cause: The view derives its OID from a table/view having primary key based
// OID and sub-views cannot be created under such views.
// *Action: Specify view having system generated OID or a view created with
// the specification of attributes in the WITH OBJECT ID clause
// and retry the operation.
22983, 00000, "not a user-defined REF"
// *Cause: Attempt to use a system generated REF value where a
// user-defined REF value should be used.
// *Action: Make sure the REF value is user-defined.
22984, 00000, "view query cannot contain references to a super view"
// *Cause: The query defining the view contains references to a super-view
// of the view being created.
// *Action: Make sure that the view query does not reference a super-view.
/
/
/
/ 22990 - 22999 Reserved for SQL LOBs
/
22990, 00000, "LOB locators cannot span transactions"
// *Cause: A LOB locator selected in one transaction cannot be used in
// a different transaction.
// *Action: Re-select the LOB locator and retry the operation.
22991, 00000, "insufficient space allocated for argument %s"
// *Cause: The data to be returned in the argument is greater than the
// amount of space allocated for the argument.
// *Action: Allocate more space for the argument.
/
22992, 00000, "cannot use LOB locators selected from remote tables"
// *Cause: A remote LOB column cannot be referenced.
// *Action: Remove references to LOBs in remote tables.
/
22993, 00000, "specified input amount is greater than actual source amount"
// *Cause: (1) For LOB write, the amount of data received is different
// from the amount that was indicated would be sent. (2) For
// LOB copy and loadfromfile, the end of the source LOB/FILE
// value was reached before the specified input amount was
// copied/loaded.
// *Action: (1) will happen when using OCI's piecewise mechanism with polling
// or with a callback function. Modify the code either to send
// the amount specified or to pass 0 as the input amount so that any
// amount of data can be sent. (2) will happen if the specified
// input amount is too large for the source LOB/FILE given the
// starting source offset. Either decrease the starting source
// offset, or decrease the amount to copy/load.
/
22994, 00000, "source offset is beyond the end of the source LOB"
// *Cause: The source offset for a LOB COPY or LOB LOADFROMFILE
// is beyond the end of the source LOB.
// *Action: Check the length of the LOB and then adjust the source offset.
/
22995, 00000, "TABLESPACE DEFAULT option is invalid in this context"
// *Cause: TABLESPACE DEFAULT option can be specified for LOB columns only in
// the following contexts:
// - at the table level for a partitioned table
// - at the partition level for a composite partition.
// An attempt was made to use the TABLESPACE DEFAULT option in a
// different context.
// *Action: Remove the TABLESPACE DEFAULT option.
/
22996, 00000, "NEXT extent size is smaller than LOB chunksize"
// *Cause: An attempt was made to create or alter a LOB segment so that its
// NEXT extent size was less than the LOB chunksize
// *Action: Specify a NEXT extent size that is
// greater than or equal to the LOB chunksize
/
22997, 00000, "VARRAY | OPAQUE stored as LOB is not specified at the table level"
// *Cause: An attempt was made to specify a VARRAY|OPAQUE column to be stored
// as LOB at the partition/subpartition/template level. However
// the VARRAY|OPAQUE column was not specified to be stored as LOB at
// the table level when the table was created.
// *Action: Specify the VARRAY | OPAQUE column to be stored as LOB at the table
// level when the table is created. Alternatively, do not specify the
// VARRAY | OPAQUE column to be stored as LOB at the
// partition/subpartition/template level if it is not
// specified at the table level when the table is created.
/
22998, 00000, "CLOB or NCLOB in multibyte character set not supported"
// *Cause: A CLOB or NCLOB in a fixed-width or varying-width multibyte
// character set was passed to a SQL character function which
// does not support multibyte LOB data.
// *Action: Use DBMS_LOB functions such as DBMS_LOB.INSTR() and DBMS_LOB.SUBSTR()
// or use PLSQL DBMS_LOB.READ/WRITE to access LOB data.
/
22999, 00000, "CLOB or NCLOB data may have been corrupted"
// *Cause: CLOB or NCLOB contains invalid character data.
// One possible cause is that the wrong csid was specified for the
// external file when calling DBMS_LOB.LOADCLOBFROMFILE or
// DBMS_XSLPROCESSOR.READ2CLOB to load CLOB or NCLOB data from
// external files.
// *Action: Reload the CLOB/NCLOB data with the correct csid specified
// for the external file.
/
/ 22999 IS THE MAXIMUM ERROR NUMBER for object SQL
/
/
/ 23000 - 23299 Reserved for object Management Subsystem (OMS)
/
/ FOR NOW 23290 to 23299 is being taken by RENAME COLUMN/CONSTRAINT
/
/
23290, 00000, "This operation may not be combined with any other operation"
// *Cause: ALTER TABLE RENAME COLUMN/CONSTRAINT operation was given in
// conjunction with another ALTER TBALE Operation. This is not
// allowed.
// *Action: Ensure that RENAME COLUMN/CONSTRAINT is the only operation
// specified in the ALTER TABLE.
/
23291, 00000, "Only base table columns may be renamed"
// *Cause: Tried to rename a column of a non-base table, like object table/
// nested table/ materialized view table.
// *Action: None. This is not allowed.
/
23292, 00000, "The constraint does not exist"
// *Cause: The given constraint name does not exist.
// *Action: Give an existing constraint's name.
/
23293, 00000, "Cannot rename a column which is part of a join index"
// *Cause: The column participates in a join index.
// *Action: If you need to rename the column, you need to drop the join index.
/
/
/ 23300 - 24299 Reserved for errors from DBMS* pl/sql pakages
/ These messages are generated from the dbms_sys_error package.
/ Messages can be given explicitly in this file or they can be passed as
/ a (single) string parameter to the
/ The dbms_sys_error.raise_system_error call.
/ If an error message is not found in this file, the string passed to the
/ call is used as the error message.
/
///////////////////////////////////////////////////////////////////////////////
// 23300-23599 Reserved for Replication PL/SQL packages
///////////////////////////////////////////////////////////////////////////////
23300, 00000, "%s"
// *Cause: The stored procedure 'raise_system_error'
// was called which causes this error to be generated.
// *Action: Correct the problem as described in the error message or contact
// the application administrator or DBA for more information.
23301, 00000, "mixed use of deferred rpc destination modes"
// *Cause: Replication catalog determined deferred RPC destinations were
// mixed with destination determined by other mechanisms in the
// same transaction.
// *Action: Do not mix destination types in the same transaction.
23302, 00000, "application raised communication failure during deferred RPC"
// *Cause: An application declared a communication failure during a
// defered RPC.
// *Action: Retry the application when communication is restored.
23303, 00000, "application raised generic exception during deferred RPC"
// *Cause: An application declared a generic failure during a
// defered RPC.
// *Action Determined by the application
23304, 00000, "malformed deferred rpc at arg %s of %s in call %s, in tid %s"
// *Cause: A deferred RPC call was issued without the correct number of
// arguments as determined by the count parameter to dbms_defer.call
// *Action: Be sure the number of actuals matches the count.
23305, 00000, "internal deferred RPC error: %s"
// *Cause: An internal error occurred in deferred rpc.
// *Action: Report the error and other information to support.
23306, 00000, "schema %s does not exist"
// *Cause: The schema name was null or misspelled, or the schema does not
// exist locally.
// *Action: Specify the schema correctly, or create it with CREATE USER.
23307, 00000, "replicated schema %s already exists"
// *Cause: The given database already replicates the given schema.
// *Action: Choose a different schema or a different database.
23308, 00000, "object %s.%s does not exist or is invalid"
// *Cause: The given name was null or misspelled, the given type was wrong,
// the object does not exist as a valid database object, or the object
// does not exist as a replicated object with the appropriate status.
// *Action: Ensure the object is valid in the database, is visible to the
// user, and, if appropriate, is a valid object in all_repobject.
23309, 00000, "object %s.%s of type %s exists"
// *Cause: An object in the same namespace exists, perhaps with a different
// type or shape, or the same object has already been registered as an
// repobject in another object group.
// *Action: Remove the offending object with the SQL DROP command, unregister
// the offending object with dbms_repcat.drop_master_repobject(), or
// reinvoke the request using TRUE for a boolean parameter such as
// retry or use_existing_object.
23310, 00000, "object group \"%s\".\"%s\" is not quiesced"
// *Cause: The requested operation requires the object group to be
// suspended.
// *Action: Invoke suspend_master_activity at the repgroup's masterdef,
// wait until the status has changed to quiesced, and then retry the
// original request.
23312, 00000, "not the masterdef according to %s"
// *Cause: The group name is null, the group name is misspelled, the
// invocation or given database is not the masterdef, or one of the
// masters does not believe the invocation database is the masterdef.
// *Action: If the given group name and masterdef were both correct,
// connect to the masterdef and retry the request, or relocate the
// masterdef at the (errant) databases using relocate_masterdef.
23313, 00000, "object group \"%s\".\"%s\" is not mastered at %s"
// *Cause: The group name is null, the group name is misspelled, the
// invocation database is not a master, or the invocation database
// does not believe the given database is a master.
// *Action: If the given group name was correct, connect to a current master
// and retry the request, make the invocation database a master
// with add_master_database, or use switch_mview_master if the
// invocation database is a materialized view site.
23314, 00000, "database is not a materialized view site for \"%s\".\"%s\""
// *Cause: The invocation database is not a materialized view database for the
// given object group.
// *Action: Connect to the desired materialized view database and retry the
// request, or make the invocation database a materialized view site
// with create_mview_repschema or create_mview_repgroup.
23315, 00000, "repcatlog version or request %s is not supported by version %s"
// *Cause: Either incompatible repcat versions are used, or a repcatlog record
// has been corrupted.
// *Action: Convert the master to a compatible version of repcat or retry
// the request.
23316, 00000, "the masterdef is %s"
// *Cause: The requested operation is not permitted on a masterdef site.
// *Action: Relocate the masterdef to another master and retry the operation.
23317, 00000, "a communication failure has occurred"
// *Cause: The remote database is inaccessible.
// *Action: Ensure the remote database is running, the communications network
// is functioning, and the appropriate database links are present.
23318, 00000, "a ddl failure has occurred"
// *Cause: User-supplied or system-generated ddl did not execute successfully.
// *Action: Examine ddl, database state, repcatlog, and all_errors to determine
// why the failure occurred.
23319, 00000, "parameter value %s is not appropriate"
// *Cause: The given value of a parameter is either null, misspelled, or not
// supported.
// *Action: Refer to the documentation and use parameter values that are
// appropriate for the given situation.
23320, 00000, "the request failed because of values %s and %s"
// *Cause: A missing ddl record for a repcatlog record, or inconsistency in
// repcat views.
// *Action: Retry the request, or make the views consistent.
//
23321, 00000, "Pipename may not be null"
// *Cause: You called dbms_pipe with a null pipe name.
// *Action: Find out the name of the pipe and call function with non-null
// pipename.
23322, 00000, "Privilege error accessing pipe"
// *Cause: You either tried to create a pipe that already existed and
// belonged to someone else, or remove a pipe that you were not
// authorized to use, or put a message into a pipe that you were
// not authorized for, or get a message from a pipe that you were
// not authorized for.
// *Action: You may have to use a different pipename.
23323, 00000, "parameter length exceeds deferred RPC limits"
// *Cause: A deferred rpc parameter was longer than the deferred rpc limits
// of 4000 bytes for char/varchar2 parameters and 2000 bytes for raw
// parameters.
// *Action: Use smaller parameters.
23324, 00000, "error %s, while creating deferror entry at \"%s\" with error %s"
// *Cause: The given error was encountered while attempting to create a
// deferor entry for the give error code and the give database.
// *Action: Correct the cause of the given error.
23325, 00000, "parameter type is not %s"
// *Cause: A conflict resolution priority function was given a type
// different than the type assigned to the priority group;
// or the priority group has no type assigned or a function;
// or dbms_defer_sys_query was called to retrieve a deferred rpc
// parameter from the deferred rpc queue, but the type of the
// parameter does not match the return type of the function.
// *Action: Use the function corresponding to the parameter type.
23326, 00000, "object group \"%s\".\"%s\" is quiesced"
// *Cause: Either suspend_master_activity has been called before the object
// group has resumed normal operation or a (deferred) rpc operation
// was attempted while the object group was quiesced.
// *Action: If suspend_master_activity has been called and a
// resume_master_activity request is pending, wait until it
// completes, and then reinvoke suspend_master_activity.
// Otherwise, resume database activity with the resume_master_activity
// call.
23327, 00000, "imported deferred rpc data does not match %s of importing db"
// *Cause: Deferred rpc queues were imported from a database with a different
// global name or operating system than importing database.
// *Action: Deferred rpc data should only be imported into a database with
// the same global name and hardware and operating system.
23328, 00000, "mview base table \"%s\".\"%s\" differs from master table \"%s\".\"%s\""
// *Cause: When creating a materialized view through repcat, the materialized
// view base table name did not match a replicated table name at the
// master.
// *Action: Change the materialized view ddl to use the same base table as the
// replicated table name at the master.
//
23329, 00000, "successful user-provided ddl but no materialized view \"%s\".\"%s\""
// *Cause: The DDL provided by the user to create a materialized view was
// executed without error, but materialized view does not exist.
// *Action: Manually back-out the DDL, and reregister with matching ddl
// and materialized view.
//
23330, 00000, "column group %s already exists"
// *Cause: The column group was already registered in the object group.
// *Action: Use a column group name not yet registered in the replicated
// object group.
//
23331, 00000, "column group %s does not exist"
// *Cause: The given column group is either null, misspelled or not registered.
// *Action: Use a registered column group.
//
23332, 00000, "group %s is in use; cannot drop"
// *Cause: The given column group or priority group is being used to
// resolve conflicts.
// *Action: Call dbms_repcat procedures drop_update_resolution,
// drop_delete_resolution, drop_unique_resolution so that the column
// group or priority group is no longer in use before dropping.
//
23333, 00000, "column %s is already part of a column group"
// *Cause: Attempted to add a column to a column group when the column was
// already a member of a column group.
// *Action: Drop the column from its existing column group before trying
// to add it to another.
//
23334, 00000, "column %s does not exist in table or column group"
// *Cause: The given column is either null, misspelled or is not part of the
// given table or column group.
// *Action: Use a column that is a member of the table or column group.
//
23335, 00000, "priority group %s already exists"
// *Cause: The priority group was already registered in the object group.
// *Action: Use a column group name not yet registered in the object group.
//
23336, 00000, "priority group %s does not exist"
// *Cause: The priority group was already registered in the object group.
// *Action: Use a priority group name not yet registered in the object group.
//
23337, 00000, "priority or value not in priority group %s"
// *Cause: The specified value or priority has not been registered
// as part of the priority group.
// *Action: Either specify a different value or priority that is already part
// of the priority group, or add the value to the priority group.
//
23338, 00000, "priority or value already in priority group %s"
// *Cause: The specified value or priority has already been registered
// as part of the priority group.
// *Action: Either specify a different value or priority that not already part
// of the priority group, or drop the value to the priority group.
//
23339, 00000, "duplicate conflict resolution information"
// *Cause: The specified combination of column group, sequence, conflict
// type and/or parameter table name, parameter column name,
// and parameter sequence number has already been registered.
// *Action: Verify that additional conflict resolution information
// needs to be added and provide a new sequence number. If
// modifying existing information, the existing information must
// be dropped first.
//
23340, 00000, "incorrect resolution method %s"
// *Cause: User function is specified when conflict resolution method was
// not "USER FUNCTION" or specified resolution method is not one of
// the predefined methods.
// *Action: If user function is specified when conflict resolution method was
// not "USER FUNCTION", either reregister function with method as
// "USER FUNCTION" or specify a NULL user function. Otherwise
// Specify one of the documented supported conflict resolution methods.
//
23341, 00000, "user function required"
// *Cause: A NULL user function was specified for the "USER FUNCTION" method.
// *Action: Provide user function name (e.g., "schema"."package"."function")
// that conforms to the documented user function specifications or
// specify one of the documented supported conflict resolution methods.
//
23342, 00000, "invalid parameter column %s"
// *Cause: The parameter column name is null or misspelled, the
// invocation database is not a master, or is of the wrong type
// for the specified conflict resolution method.
// *Action: Specify a parameter column from the specified column group
// that has a correct type for the conflict resolution method.
//
23343, 00000, "no match for specified conflict resolution information"
// *Cause: The specified combination of column group, sequence, conflict
// type has not been registered (e.g., for adding a comment).
// *Action: Specify a combination of column group, sequence, conflict
// type has been registered.
//
23344, 00000, "constraint (%s.%s) does not exist"
// *Cause: A null, misspelled or nonexistent constraint was specified
// when registering a uniqueness conflict.
// *Action: Register a named constraint for the specified table.
//
23345, 00000, "table \"%s\".\"%s\" not registered to collect statistics"
// *Cause: A procedure that deals with conflict resolution statistics-gathering
// was called for a table that was not registered to collect
// statistics.
// *Action: Call dbms_repcat.register_statistics to register the table.
//
23346, 00000, "primary key or object ID is undefined for table or materialized view %s"
// *Cause: Trying to generate replication support for a table or materialized
// view without a primary key (as defined by a constraint or
// dbms_repcat.set_columns) or an object ID.
// *Action: For a table, add a primary key constraint or define a primary
// key using dbms_repcat.set_columns or use object tables.
// For a ROWID materialized view, set min_communication to false
// or use primary key or object ID materialized views.
//
23347, 00000, "datatype %s for column %s table %s not supported"
// *Cause: The table has a column whose datatype is not supported by repcat.
// *Action: Remove the column from the table, or alter the column to have
// one of the supported datatypes.
//
23348, 00000, "cannot replicate procedure %s; only IN parameters supported"
// *Cause: Trying to generate replication support for a package that has
// a procedure with OUT or IN OUT parameters.
// *Action: Remove the procedure from the package, or remove the OUT or IN OUT
// parameters from the procedure.
//
23349, 00000, "cannot generate replication support for functions"
// *Cause: Trying to generate replication support for a package that has
// a public function, or for a stand-alone function.
// *Action: Remove the public function from the package, or alter the function
// to be a procedure.
//
23350, 00000, "maximum number of recursive calls exceeded"
// *Cause: This usually occurs when trying to resolve conflicts in a table
// while concurrent updates to the same row create more conflicts.
// *Action: Re-execute the deferred transaction from DefError using
// dbms_defer_sys.execute_error
//
23351, 00000, "parameter datatype %s for procedure %s not supported"
// *Cause: The procedure has a parameter whose datatype is not supported by
// repcat.
// *Action: Remove the parameter from the procedure, or alter the parameter
// to have one of the supported datatypes.
23352, 00000, "duplicate destination for deferred transaction"
// *Cause: A duplicate destination was specified for a deferred transaction
// either in a dbms_defer.call call or an earlier
// dbms_defer.transaction call or a dbms_defer_sys.add_default_dest
// call.
// *Action: Remove the duplicate entry
23353, 00000, "deferred RPC queue has entries for object group \"%s\".\"%s\""
// *Cause: The requested action cannot be performed until the queue is empty
// for the given object group
// *Action: Use dbms_defer_sys.execute or dbms_defer_sys.delete_tran to
// empty the queue.
23354, 00000, "deferred RPC execution disabled for \"%s\" with \"%s\""
// *Cause: Deferred RPC can not be executed at the destination with
// the specified catchup value because their propogation has
// been disabled.
// *Action: Enable deferred RPC execution with the
// dbms_defer_sys.set_disabled call.
//
23355, 00000, "object %s.%s does not exist or is invalid at master site"
// *Cause: The given name was null or misspelled, the given type was wrong,
// the object does not exist as a valid database object at the master
// site, or the object does not exist as a replicated object with
// the appropriate status.
// *Action: Ensure the object is valid in the master database, and is visible
// to the user, and, if appropriate, is a valid object in
// all_repobject.
23356, 00000, "masterdef recognizes a master which does not recognize the masterdef"
// *Cause: Possibly drop_master_repgroup was run at a master site but
// remove_master_databases was not run at master definition site
// for that master.
// *Action: Run remove_master_databases from master definition site to
// remove the appropriate master (see associated error messages).
23357, 00000, "the propagator does not exist"
// *Cause: The propagator does not exist.
// *Action: Register a new propagator.
//
23358, 00000, "invalid remote user"
// *Cause: The local user does not match the remote user connected via
// a database link.
// *Action: Drop and recreate the identified database link with the
// connect-to user identical to the owner of the database link.
//
23359, 00000, "error on creating a ddl record for a repcatlog record"
// *Cause: The userid in the repcatlog record does not match the userid
// of the connected user.
// *Action: Retry the operation with a different user.
//
23360, 00000, "only one materialized view for master table \"%s\" can be created"
// *Cause: Trying to create more than one materialized view on a given master
// table in the same rep group.
// *Action: Create these other materialized views in a different rep group at
// another site.
//
23361, 00000, "materialized view \"%s\" does not exist at master site"
// *Cause: The materialized view does not exist at the master site for offline
// instantiation of the materialized view.
// *Action: The correct procedure is to create the materialized view in a
// different schema at the master site, and then follow the
// instructions for offline instantiation of materialized views.
//
23362, 00000, "invalid user"
// *Cause: The given user does not exist.
// *Action:
//
23363, 00000, "mismatch of mview base table \"%s\" at master and mview site"
// *Cause: The name of the base table of the materialized view at the master
// site is different from the base table at the materialized view
// site. This error may arise during offline instantiation of
// materialized views.
// *Action: Retry offline instantiation with a materialized view name less than
// 24 bytes
//
23364, 00000, "Feature not enabled: Advanced replication"
// *Cause: The Advanced Replication feature is not enabled at this site.
// Updatable materialized views, deferred RPCs, and other replication
// features are, therefore, unavailable.
// *Action: Do not attempt to use this feature. Contact an Oracle Customer
// Support representative if the Advanced Replication feature has
// been purchased but not enabled.
//
23365, 00000, "site %s does not exist"
// *Cause: site specified in argument "reference_site" or argument
// "comparison_site" in call to "differences()" routine
// or "rectify()" routine does not name an existing site.
// *Action: Make sure that database sites specified really do exist,
// and re-run the routine.
//
23366, 00000, "integer value %s is less than 1"
// *Cause: Value of argument "max_missing" to routine "differences()"
// cannot be less than 1. Value of argument "commit_rows" to
// routines "differences()" and "rectify()" cannot be less than 1.
// *Action: Choose an integer value for those arguments to be 1 or greater.
//
23367, 00000, "table %s is missing the primary key"
// *Cause: Table specified in argument "oname1" or "oname2" in call
// to "differences()" routine does not contain either a primary
// key or a virtual primary key (defined through dbms_repcat package
// under symmetric replication).
// *Action: Make sure the tables specified have a primary key defined.
//
23368, 00000, "name %s cannot be null or the empty string"
// *Cause: Argument "sname1," "sname2," "oname1," "oname2,"
// "missing_rows_sname," "missing_rows_oname1,"
// "missing_rows_oname2" to "differences()" or "rectify()"
// cannot be NULL or '' (empty string).
// *Action: Change argument to non-null or non-empty string.
//
23369, 00000, "value of \"%s\" argument cannot be null"
// *Cause: Argument "max_missing" to "differences()" routine
// cannot be NULL.
// *Action: Legal values for "max_missing" are integers 1 or greater.
//
23370, 00000, "table %s and table %s are not shape equivalent (%s)"
// *Cause: The tables specified are not shape equivalent, which means
// intuitively that the number of columns, the names, their datatypes
// and lengths are not the same. Specifically, problem is
// in the parentheses and is one of the following: the number of
// columns are not equal, datatypes of columns with
// same name in different tables are different, lengths of
// varchar2 and char columns are not equal, precision and
// scale of number datatypes are not equal.
// *Action: Make sure the two tables being compared have the same
// number of columns, same column names, and same datatypes.
//
23371, 00000, "column %s unknown in table %s"
// *Cause: Some column in "array_columns" argument (or "column_list" argument)
// to "differences()" routine does not correspond to a column in
// the specified table.
// *Action: Make sure that all the columns in either "array_columns" or
// "column_list" are present in the specified table.
//
23372, 00000, "type %s in table %s is unsupported"
// *Cause: Certain types in the table comparison utility are not supported.
// *Action: Make sure that the types of columns in the tables to be compared
// are the ones supported by symmetric replication.
//
23373, 00000, "object group \"%s\".\"%s\" does not exist"
// *Cause: The group name was null or misspelled, or the group does not
// exist locally.
// *Action: Specify the group correctly, or create it with
// dbms_repcat.create_master_repgroup().
//
23374, 00000, "object group \"%s\".\"%s\" already exists"
// *Cause: The given database already replicates the given object group.
// A materialized view repgroup cannot be created at a given site
// where a master repgroup with the same name already exists.
// *Action: Choose a different group or a different database.
//
23375, 00000, "feature is incompatible with database version at %s"
// *Cause: A feature not compatible with the specified database was used
// *Action: Set or raise the value of the "compatible" INIT.ORA parameter
// to match the necessary compatibility level.
//
23376, 00000, "node %s is not compatible with replication version \"%s\""
// *Cause: A feature not compatible with the remote database was used
// *Action: Upgrade the remote database and retry the operation
//
23377, 00000, "bad name %s for missing_rows_oname1 argument"
// *Cause: An attempt was made to use the name of the reference site table
// as the name of the missing_rows_oname1 argument.
// *Action: Provide a separately created table with a different name for
// missing_rows_oname1 argument. The separately created table will
// contain the differences between the tables being compared.
//
23378, 00000, "connection qualifier \"%s\" is not valid for object group \"%s\".\"%s\""
// *Cause : The connection qualifier used in the database link for the
// specified object group does not match the qualifier specified for
// the group in create_master_repgroup.
// *Action: Use or create a database link which contains the correct connection
// qualifier.
//
23379, 00000, "connection qualifier \"%s\" is too long"
// *Cause: The maximum length of a database link, including the connection
// qualifier, is 128 bytes.
// *Action: Use a shorter connection qualifier, or shorten the name of
// the database link
//
23380, 00000, "propagation mode \"%s\" is not valid"
// *Cause: The specified propagation may be misspelled, or is not supported.
// For materialized view sites, all materialized view object groups
// at the same materialized view site with the same master object
// group must all have the same propagation method.
// *Action: Refer to the manual on replicated data for valid propagation modes.
// For materialized view sites, also ensure that the propagation modes
// of all materialized view object groups with the same master object
// group are the same.
//
23381, 00000, "generated object for base object %s.%s@%s does not exist"
// *Cause: The system generated object(s) for the specified base object
// do not exist at the specified site. The current operation
// requires the base object to have generated replication support.
// *Action: Ensure that the generated replication object(s) for the base
// object exist and are valid at the specified site.
// If the generated object(s) do not exist, then the procedure
// dbms_repcat.generate_replication_support() needs to be
// called from the master definition site for the base object.
// missing_rows_oname1 argument. The separately created table will
// contain the differences between the tables being compared.
23382, 00000, "materialized view repgroup \"%s\".\"%s\" is not registered at site %s"
// *Cause: The materialized view repgroup is not currently registered at
// the master and so cannot be unregistered.
// *Action: None
//
23383, 00000, "registration for materialized view repgroup \"%s\".\"%s\" failed at site %s"
// *Cause: Insertion into local repschema table failed.
// *Action: None
//
23384, 00000, "replication parallel push %s argument out of range"
// *Cause: Specified numeric argument to dbms_defer_sys.push is invalid.
// *Action: Fix the argument value and try again.
//
23385, 00000, "replication parallel push %s argument not valid"
// *Cause: Specified string argument to dbms_defer_sys.push is invalid.
// *Action: Fix the argument value and try again.
//
23386, 00000, "replication parallel push cannot create slave processes"
// *Cause: An error was occurred while creating slave processes for
// parallel push.
// *Action:
//
23387, 00000, "replication parallel push dequeue error"
// *Cause: An attempt to dequeue a deferred transaction failed while trying
// to assign a new queue batch number.
// *Action:
//
23388, 00000, "replication parallel push watermark error"
// *Cause: An error occurred during parallel push while trying to update
// the high-water-mark information in system.def$_destination.
// *Action:
//
23389, 00000, "obsolete procedure; drop objects and recreate using new master"
// *Cause: dbms_repcat.switch_mview_master is no longer supported.
// *Action: Drop the objects in the object group and recreate them using
// the new master.
//
23392, 00000, "could not find materialized view to be associated with \"%s\".\"%s\""
// *Cause: Could not find materialized view associated with a trigger or index
// that is being pulled from the master site.
// *Action: Ensure that materialized view, master, and master index or trigger
// is registered as replicated objects.
//
23393, 00000, "the user is already the propagator"
// *Cause: The given user is already the current propagator.
// *Action:
//
23394, 00000, "duplicate propagator"
// *Cause: More than one valid propagator exist.
// *Action: Unregister any duplicate propagator.
//
23395, 00000, "object \"%s\".\"%s\" of type \"%s\" does not exist or is invalid"
// *Cause: The given name was null or misspelled, the given type was wrong,
// the object does not exist as a valid database object, or the object
// does not exist as a replicated object with the appropriate status.
// *Action: Ensure the object is valid in the database, is visible to the
// user, and, if appropriate, is a valid object in all_repobject.
//
23396, 00000, "database link \"%s\" does not exist or has not been scheduled"
// *Cause: the database link does not exist in the schema of the replication
// propagator or has not been scheduled.
// *Action: Ensure that the database link exists in the database, is accessible
// and is scheduled for execution.
//
23397, 00000, "global name \"%s\" does not match database link name \"%s\""
// *Cause: the database link name at the local node does not match the global
// name of the database that the link accesses.
// *Action: Ensure that global names is set to true and the link name matches
// the global name.
//
23398, 00000, "user name \"%s\" at database link \"%s\" does not match local user name \"%s\""
// *Cause: the user name of the replication administration user at
// the local node and the user name at the node corresponding to the
// database link are not the same. Symmetric replication expects the
// two users to be the same.
//
// *Action: Ensure that the user ID of the replication administration user at
// the local node and the user ID at the node corresponding to the
// database link are the same.
//
23399, 00000, "generation of replication support for \"%s\".\"%s\" is not complete"
// *Cause: Replication support for the specified object has not been generated
// or the generation process is not yet complete.
// *Action: Ensure that replication support has been generated for the object.
// Use DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT() to generate
// replication support for the object.
//
23400, 00000, "invalid materialized view name \"%s\""
// *Cause: A null, misspelled, or badly formed materialized view name was given
// to dbms_mview.refresh.
// *Action: Provide a valid materialized view name to dbms_mview.refresh.
//
23401, 00000, "materialized view \"%s\".\"%s\" does not exist"
// *Cause: A materialized view name was given to dbms_mview.refresh that is not
// in sys.snap$ or its associated views.
// *Action: Provide a materialized view name that is in sys.snap$, all_mviews
// or user_mviews.
//
23402, 00000, "refresh was aborted because of conflicts caused by deferred txns"
// *Cause: There are outstanding conflicts logged in the DefError table
// at the materialized view's master.
// *Action: Resolve the conflicts in the master DefError table and
// refresh again after the table is empty. Alternatively,
// refresh with refresh_after_errors set to TRUE, which
// will proceed with the refresh even if there are conflicts
// in the master's DefError table. Proceeding despite conflicts
// can result with an updatable materialized view's changes appearing
// to be temporarily lost (until a refresh succeeds after the
// conflicts are resolved).
//
23403, 00000, "refresh group \"%s\".\"%s\" already exists"
// *Cause: Making a new refresh group when there is already a group of
// the same name in sys.rgroup$.
// *Action: Choose a diifferent refresh group name.
//
23404, 00000, "refresh group \"%s\".\"%s\" does not exist"
// *Cause: A refresh group name was given that is not in sys.rgroup$.
// *Action: Provide a refresh group name that is in sys.rgroup$ or dbs_rgroup.
//
23405, 00000, "refresh group number %s does not exist"
// *Cause: A refresh group number was given that is not in sys.rgroup$.
// *Action: Provide a refresh group number that is in sys.rgroup$ or dbs_rgroup.
//
23406, 00000, "insufficient privileges on user \"%s\""
// *Cause: The caller is not the owner of the materialized view and does not
// have ALTER ANY MATERIALIZED VIEW privileges.
// *Action: Perform the operation as the owner of the materialized view or as a
// user with ALTER ANY MATERIALIZED VIEW privileges.
//
23407, 00000, "object name %s must be shaped like \"schema\".\"object\" or \"object\""
// *Cause: The object name (e.g., the rollback segment, the materialized view
// name, the refresh group) was incorrectly specified.
// *Action: Retry the operation with the object name properly specified
// (like "schema"."object" or "object")
//
23408, 00000, "this replication operation is not supported in a mixed configuration"
// *Cause: operation is not supported if the object group is replicated at a
// pre-V8 node.
//
// *Action: Ensure that all nodes of the replicated object group are V8.
//
23409, 00000, "could not find an unused refresh group number"
// *Cause: 1000 consecutive refresh group numbers, as defined by the
// rgroupseq number, were already used by rows in sys.rgroup$.
// *Action: Alter the sequence number to be within a legal unused range
// and destroy unneeded refresh groups.
//
23410, 00000, "materialized view \"%s\".\"%s\" is already in a refresh group"
// *Cause: A materialized view of the same name is already in a refresh group.
// *Action: Subtract the materialized view from the current refresh group and
// add it to its new refresh group, or combine the two refresh
// groups into a single refresh group.
//
23411, 00000, "materialized view \"%s\".\"%s\" is not in refresh group \"%s\".\"%s\""
// *Cause: The specified materialized view is not in the specified refresh
// group.
// *Action: Try again with the proper materialized view and refresh group
// names.
//
23412, 00000, "master table's primary key columns have changed"
// *Cause: The master table's primary key constraint was modified after
// the primary key materialized view was created.
// *Action: Drop and recreate the primary key materialized view
//
23413, 00000, "table \"%s\".\"%s\" does not have a materialized view log"
// *Cause: The fast refresh can not be performed because the master table
// does not contain a materialized view log.
// *Action: Use the CREATE MATERIALIZED VIEW LOG command to create a
// materialized view log on the master table.
//
23414, 00000, "materialized view log for \"%s\".\"%s\" does not record rowid values"
// *Cause: A rowid materialized view is being fast refreshed, but the
// materialized view log does not record rowid information.
// *Action: Use the CREATE MATERIALIZED VIEW LOG...ADD ROWID command to begin
// recording rowid information in the materialized view log.
//
23415, 00000, "materialized view log for \"%s\".\"%s\" does not record the primary key"
// *Cause: A primary key materialized view is being fast refreshed, but the
// materialized view log does not record primary key information.
// *Action: Use the CREATE MATERIALIZED VIEW LOG...ADD PRIMARY KEY command to
// begin recording primary key information in the materialized view
// log.
//
23416, 00000, "table \"%s\".\"%s\" does not contain a primary key constraint"
// *Cause: The master table does not constaint a primary key constraint or
// the primary key constraint has been disabled.
// *Action: Create a primary key constraint on the master table or enable the
// existing constraint.
//
23417, 00000, "unknown materialized view type: %s"
// *Cause: A fast refresh is being performed on a materialized view of an
// unknown or unsupported type.
// *Action: Check all_mviews and ensure that the materialized view being
// refreshed a valid materialized view.
//
23418, 00000, "cannot unregister the propagator who is currently in use"
// *Cause: The propagator is currently used in propagating replication RPCs.
// *Action: Try again later when there is no transaction active in
// propagating replication RPCs.
//
23419, 00000, "regenerate replication support before resuming master activity"
// *Cause: There are tables in the object group that require regeneration
// of replication support.
// *Action: Check the generation_status column in the all_repobjects view.
// Regenerate replication support for any table in the object group
// with a 'NEEDSGEN' status. Resume master activity.
//
23420, 00000, "interval must evaluate to a time in the future"
// *Cause: The parameter "interval" evaluates to a time earlier than SYSDATE.
// *Action: Choose an expression that evaluates to a time later than SYSDATE.
//
23421, 00000, "job number %s is not a job in the job queue"
// *Cause: There is no job visible to the caller with the given job number.
// *Action: Choose the number of a job visible to the caller.
//
23422, 00000, "Oracle Server could not generate an unused job number"
// *Cause: Oracle Server could not generate a job number that was not used to
// identify another job.
// *Action: Retry the operation.
//
23423, 00000, "job number %s is not positive"
// *Cause: The given job number is less than 1.
// *Action: Choose a positive integer.
//
23424, 00000, "materialized view \"%s\".\"%s\" at %s not registered"
// *Cause: The specified materialized view has not be successfully registered
// at this site.
// *Action: Register the materialized view manually at either the master site
// or the materialized view site.
//
23425, 00000, "invalid materialized view identifier %s"
// *Cause: The argument provided to dbms_mview.purge_mview_from_log is
// an invalid materialized view identifer or it does not identify an
// Oracle 8 fast refreshable materialized view or the materialized view
// has been already purged.
// *Action: If the materialized view is an Oracle 8 fast refreshable
// materialized view then provide purge_mview_from_log with its valid
// materialized view identifier.
//
23426, 00000, "deferred RPC queue has entries for %s"
// *Cause: The requested action cannot be performed until the queue is empty
// for the given site/dblink
// *Action: Use dbms_defer_sys.push, dbms_defer_sys.purge_queue
// or dbms_defer_sys.delete_tran to empty the queue.
//
23427, 00000, "deferred purge queue argument %s out of range"
// *Cause: Specified numeric argument to dbms_defer_sys.purge_queue is invalid.
// *Action: Fix the argument value and try again.
//
23428, 00000, "job associated instance number %s is not valid"
// *Cause: A job is associated with an instance that is not running.
// *Action: Choose a running instance for job affinity, or set force
// parameter to TRUE.
//
23430, 00000, "argument \"%s\" cannot be NULL or empty string"
// *Cause: The caller has provided an argument whose value cannot be
// NULL or the empty string.
// *Action: Check that the varchar2 value provided is not NULL or the
// empty string, and retry the call.
//
23431, 00000, "wrong state: %s"
// *Cause: The routine was executed against a replicated object group
// that was in the wrong state.
// *Action: Make sure that the replicated object group is in the
// state given in the error message.
//
23432, 00000, "master site %s already exists"
// *Cause: An attempt was made to instantiate a replicated object group
// at a master site that was already a part of the object group.
// *Action: If you were trying to add this site, do nothing because it
// already exists; otherwise, pick the name of another site,
// and re-run the routine.
//
23433, 00000, "executing against wrong master site %s"
// *Cause: An attempt was made to execute the routine at a site
// that is different from the site specified in the argument
// of the routine.
// *Action: Provide an argument to the routine that correctly indicates
// the site against which the routine should be executing.
//
23434, 00000, "master site %s not known for object group"
// *Cause: The site name given as an argument to a routine was not already
// known to the replicated object group.
// *Action: Execute the dbms_offline_og.begin_instantiation() routine to
// add a new site to the replicated object group.
//
23435, 00000, "cannot create an updatable ROWID materialized view with LOB columns"
// *Cause: The propagation of LOB data from materialized view sites to the
// master site requires a primary key on the replicated table. Thus
// updatable ROWID materialized views that contain LOB columns are not
// supported.
// *Action: Create a primary key materialized view instead of a ROWID
// materialized view. If the materialized view already exists, it can
// be converted to a primary key materialized view using the ALTER
// MATERIALIZED VIEW DDL command.
//
23436, 00000, "missing template authorization for user"
// *Cause: The specified template authorization does not exist.
// *Action: Check the values for user name and refresh template name to
// ensure a valid row exists in the DBA_REPCAT_USER_AUTHORIZATIONS
// view.
//
23437, 00000, "template authorization already exists for user"
// *Cause: The specified user already has been authorized to use the
// specified refresh group template.
// *Action: Check the values for user name and refresh template name or
// query the DBA_REPCAT_USER_AUTHORIZATIONS view to ensure that
// the correct values were passed as parameters.
//
23438, 00000, "missing refresh group template"
// *Cause: The specified refresh group template does not exist.
// *Action: Verify that the refresh group template does not exist by
// querying the DBA_REPCAT_REFRESH_TEMPLATES view.
//
23439, 00000, "refresh group template already exists"
// *Cause: The specified refresh group template already exists.
// *Action: Verify that the refresh group template exists by querying
// the DBA_REPCAT_REFRESH_TEMPLATES view.
//
23440, 00000, "incorrect public template value"
// *Cause: The public template parameter is not 'Y', 'N' or NULL.
// *Action: Correct the value of the public template parameter. It must
// be 'Y','N' or NULL.
//
23441, 00000, "object does not exist for refresh group template"
// *Cause: The specified object does not exist in the refresh group template.
// *Action: Correct the object name and object type parameters. Check
// the DBA_REPCAT_TEMPLATE_OBJECTS view to verify the correct
// name and type of the object.
//
23442, 00000, "object already exists for the refresh group template"
// *Cause: The specified object already exists in the refresh group
// template.
// *Action: Change the object name and object type parameters. Query
// the DBA_REPCAT_REMPLATE_OBJECTS view to verify the correct
// name and type of the object.
//
23443, 00000, "missing template parameter"
// *Cause: The specified template parameter does not exist.
// *Action: Correct the template parameter value and execute the procedure
// again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the
// name of the refresh group template and parameter name.
//
23444, 00000, "duplicate template parameter"
// *Cause: The template parameter already exists for the specified
// refresh group template.
// *Action: Correct the template parameter value and execute the procedure
// again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the
// name of the refresh group template and parameter name.
//
23445, 00000, "missing template site"
// *Cause: The template site specified by the site name, user name and
// refresh group template name does not exist.
// *Action: Correct the invalid parameter and execute the procedure again.
// Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing
// template sites.
//
23446, 00000, "duplicate template site"
// *Cause: The template site specified by the site name, user name and
// refresh group template name already exists.
// *Action: Correct the invalid parameter and execute the procedure again.
// Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing
// template sites.
//
23447, 00000, "missing user parameter value"
// *Cause: The user parameter value specified by the user name,
// parameter name and refresh group template name does not exist.
// *Action: Correct the invalid parameter and execute the procedure again.
// Use the DBA_REPCAT_USER_PARMS view to query the existing
// user parameters.
//
23448, 00000, "duplicate user parameter value"
// *Cause: The user parameter value specified by the user name,
// parameter name and refresh group template name already exists.
// *Action: Correct the invalid parameter and execute the procedure again.
// Use the DBA_REPCAT_USER_PARMS view to query the existing
// user parameters.
//
23449, 00000, "missing user name"
// *Cause: The user specified by the user name parameter does not exist
// in the database.
// *Action: Correct an invalid user name or create the user in the
// master database. Use the DBA_USERS view to select the valid
// database users.
//
23450, 0000, "flavor already contains object \"%s\".\"%s\""
// *Cause: The flavor already contains the specified object.
// *Action: Check that the specified object is correct. To add all
// columns of a table object, delete the object from the
// flavor and then add it again.
//
23451, 0000, "flavor %s already defined for object group \"%s\".\"%s\""
// *Cause: The given object group already contains a (possibly unpublished)
// definition of the specified flavor.
// *Action: Check the spelling of the flavor name. Check for an unpublished
// flavor of the desired name.
//
23452, 0000, "flavor %s of object group \"%s\".\"%s\" is already published"
// *Cause: The given object group already contains a (published) definition
// of the specified flavor.
// *Action: Check the spelling of the flavor name.
//
//
23453, 00000, "requested operation is not supported on top flavor"
// *Cause: The TOP flavor has a NULL name and may not be directly defined
// or deleted.
// *Action: Supply the name of a flavor other than the TOP flavor or use
// dbms_repcat routines to implicitly change the TOP flavor.
//
23454, 00000, "flavor %s not defined for object group \"%s\".\"%s\""
// *Cause: The given object group does not contain a (published) definition
// of the specified flavor.
// *Action: Check the spelling of the flavor name. Ensure the flavor has
// been defined (and published) for the object group.
//
23455, 00000, "flavor %s contains object \"%s\""
// *Cause: The given flavor contains the object to be dropped.
// *Action: Purge the flavor or choose another object to drop.
//
23456, 00000, "flavor %s does not contain \"%s\""
// *Cause: The flavor does not contain the given object, column, or
// attribute.
// *Action: Either drop the flavor or choose a different object, column,
// or attribute.
//
23457, 00000, "invalid flavor ID %s"
// *Cause: The given flavor ID is invalid.
// *Action: Make sure this flavor has been instantiated. If the flavor ID is
// outside the range (-2147483647, 2147483647), contact customer
// support.
//
23458, 00000, "inappropriate flavor %s at %s"
// *Cause: The given flavor at the given database prevents the
// operation from succeeding.
// *Action: Either change the database flavor or choose a different
// operation.
//
23459, 00000, "flavor %s must contain \"%s\""
// *Cause: The flavor must contain the given object, column, or
// attribute.
// *Action: Either choose a different database flavor or ensure the
// object, column, or attribute is available.
//
23460, 00000, "missing value for column %s in resolution method \"%s\" for \"%s\".\"%s\".\"%s\""
// *Cause: before resolving conflicts, some values necessary resolving
// conflicts are not available,
// or after resolving conflicts, some values necessary for
// re-trying of the SQL are not available
// *Action: define appropriate flavors, provide necessary values through
// availability vector in USER FLAVOR FUNCTION for conflict
// resolution
23461, 00000, "fail to resolve conflict for \"%s\".\"%s\".\"%s\""
// *Cause:
//
// *Action:
//
23462, 0000, "flavor %s in use at site %s"
// *Cause: The given flavor cannot be deleted because it is being used
// at the given site.
// *Action: Change the flavor of the site, or unregister it if it is
// a materialized view site.
//
23463, 0000, "flavor incompatible with object \"%s\".\"%s\""
// *Cause: An existing flavor includes the specified object with
// an incompatible type.
// *Action: Change the type of the object, or delete the flavor if it is
// not in use.
//
23464, 0000, "flavor lacks column %s of \"%s\".\"%s\""
// *Cause: The flavor includes some columns of an object group but not
// all the required columns.
// *Action: Change the flavor definition to include all required columns.
//
23465, 0000, "flavor already includes column %s of \"%s\".\"%s\""
// *Cause: The flavor includes the specified column which
// is being added.
// *Action: Check that the specified column is correct.
//
23466, 0000, "flavor requires missing object \"%s\".\"%s\""
// *Cause: The flavor includes the specified object which
// does not exist
// *Action: Check that the specified object name is correct, and
// create the object if appropriate.
//
23467, 0000, "flavor lacks object \"%s\".\"%s\""
// *Cause: The flavor does not include the specified object which
// is being dropped.
// *Action: Check that the specified object is correct.
//
23468, 0000, "missing %s %s"
// *Cause: The template is missing the object with the specified key.
// *Action: Add the object to the template.
//
23469, 0000, "%s is different between templates"
// *Cause: The values for the specified columns are different in
// each template for the same key values.
// *Action: Correct the column values to make the templates the same.
//
23470, 0000, "invalid status"
// *Cause: The status should be DELETED, INSTALLING or INSTALLED.
// Any other status is invalid.
// *Action: Check that the specified status value is correct.
//
23471, 0000, "template not authorized for user"
// *Cause: The refresh template is private and the user has not
// been authorized to instantiate the template.
// *Action: Authorize the user to use the template.
//
23472, 0000, "materialized view \"%s\".\"%s\" must be atomically refreshed"
// *Cause: Non-atomic refresh is not supported for the specified materialized
// view.
// *Action: Set the value of the ATOMIC parameter to FALSE in the refresh
// procedure being used or remove the specified materialized view from
// the set of materialized views being refreshed.
//
23473, 0000, "replication RPC processing for \"%s\".\"%s\" is disabled"
// *Cause: The processing of replication RPCs for the object group that
// contains this object is disabled. This includes RPCs in the error
// queue.
// *Action: Processing of replication RPCs is disabled when the object group
// is being offline instantiated. Wait until offline instantiation is
// finished.
//
23474, 0000, "definition of \"%s\".\"%s\" has changed since generation of replication support"
// *Cause: The current columns in the specified table and their column types
// do not match the columns and column types when replication support
// was last generated.
// *Action: Regenerate replication support for the affected table.
// All flavors that include the specified table should be checked
// for validity. Types for any UDT columns should also be checked
// for validity.
//
23475, 0000, "key column %s must be sent and compared"
// *Cause: The specified column is a key column and must be
// sent and compared during replication propagation.
// *Action: Make sure every key column is sent and compared.
//
//
23476, 00000, "cannot import from %s to %s"
// *Cause: This object was imported from a database with a different
// global name than the importing database.
// *Action: Only import this object into a database with the
// same global name.
//
23477, 00000, "unable to alter propagation mode for object group \"%s\".\"%s\""
// *Cause: The propagation method of a materialized view object group can only
// be altered when no other object groups with the same master object
// group are sharing the materialized view site.
// *Action: Ensure that there are no other materialized view object groups at
// the local site with the same master object group.
//
23478, 00000, "object group \"%s\" is already mastered at %s"
// *Cause: There is at least one other materialized view repgroup at the local
// site with the same group name but a different master site.
// *Action: Ensure that all materialized view repgroups at the local site with
// the same group name have the same master.
23480, 00000, "Column %s is not a top-level column of \"%s\".\"%s\"."
// *Cause: The column is either not a top-level column
// or is not present in the table or materialized view.
// *Action: Ensure only valid top-level columns are used.
23481, 00000, "unexpected name string \"%s\""
// *Cause:
// *Action:
23482, 00000, "column %s of \"%s\".\"%s\": object types not allowed."
// *Cause: The column is of Object Type.
// *Action: Ensure that all the columns are not of Object Type.
23483, 00000, "object \"%s\".\"%s\" not allowed in this operation."
// *Cause: The specified operation does not support the given object.
// *Action: Do not invoke the operation for this object.
23484, 00000, "internal internet Application Server error: %s"
// *Cause: An internal error occurred in internet Application Server.
// *Action: Report the error and other information to support.
23485, 00000, "Column group \"%s\" must consist of a single numeric column only"
// *Cause: The column group doesn't contain only one numeric column.
// *Action: Use a column group containing a single numeric column.
23487, 00000, "object groups \"%s\".\"%s\" and \"%s\".\"%s\" do not have the same connection qualifier"
// *Cause: The specified two object groups do not have the same connection
// qualifier.
// *Action: Do not invoke the operation on the above object groups, or
// ensure they have the same connection qualifier.
23488, 00000, "propagation mode \"%s\" for \"%s\" is not allowed for this operation"
// *Cause: This operation does not support the specified dblink in the above
// propagation mode.
// *Action: Do not invoke the operation for this dblink, or change the
// propagation mode for this dblink.
23489, 00000, "duplicate entry \"%s\""
// *Cause: The specified value is duplicated in the parameter list.
// *Action: Remove duplicated entries in the parameter list.
23490, 00000, "extension request \"%s\" with status \"%s\" not allowed in this operation"
// *Cause: The specified operation is not allowed for the extension request
// with the specified status.
// *Action: Ensure the extension request has the appropriate status before
// retrying this operation.
23491, 00000, "no valid extension request at \"%s\""
// *Cause: The specified database does not have a valid extension request.
// *Action: Ensure there is a valid extension request in DBA_REPEXTENSIONS
// view before retrying this operation.
23492, 00000, "no new sites for extension request \"%s\""
// *Cause: There is no new site with the specified extension request.
// *Action: Ensure there is at least one new site in DBA_REPSITES_NEW view
// for this request before retrying this operation.
23493, 00000, "\"%s\" is not a new site for extension request \"%s\""
// *Cause: The specified extension request does not include the specified
// site as a new site.
// *Action: Ensure the specified site is a new site for this extension request
// before retrying this operation.
23494, 00000, "too many rows for destination \"%s\""
// *Cause: The specified destination has too many rows in
// system.def$_destination table.
// *Action: Ensure the specified destination has at most two valid rows before
// retrying this operation.
23495, 00000, "serial propagation can not be used for \"%s\""
// *Cause: The sites involved may be in the process of adding a new site
// without quiescing.
// *Action: Check the def$_destination table for this destination and
// try parallel propagation.
23496, 00000, "can not change disabled status for \"%s\" and \"%s\""
// *Cause: The disabled status for this site is set internally for
// synchronization during adding a new master without
// quiescing.
// *Action: Ensure adding a new master without quiescing finished
// before invoking this procedure.
//
23497, 00000, "repgroup name cannot be null"
// *Cause: The array of Repgroup names contains a null value.
// *Action: Ensure that the array of Repgroup names is dense and is not
// null terminated.
23498, 00000, "repgroups specified must have the same masters"
// *Cause: The Repgroup names specified do not have the same masters.
// *Action: Ensure that the Repgroup names specified have the same masters.
23500, 00000, "cannot switch master for a multi-tier materialized view repgroup \"%s\".\"%s\""
// *Cause: An attempt was made to switch master for a materialized view
// repgroup when its parent repgroup is also a materialized view
// repgroup. This is not allowed.
// *Action: Drop and recreate the materialized view repgroup based on
// a proper parent repgroup.
23501, 00000, "refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0"
// *Cause: Instantiation of a refresh template is not supported for
// database compatibility 8.0 or less.
// *Action: Be sure the database compatibility is 8.1 or above.
//
23502, 00000, "valid directory for offline instatiation is not specified"
// *Cause: An attempt was made to offline instantiate to
// a directory which is not specified or null.
// *Action: There are two ways to specify the directory:
// o As a parm offline_dirpath to the API
// o As an init.ora parm named utl_file_dir
// Make sure you have specified an appropriate
// directory in which the offline file can be created.
//
23503, 00000, "error occurred during IAS instantiation"
// *Cause: An attempt was made to instantiate a IAS site. Error occurred
// during IAS instantiation.
// *Action: See other errors on the error stack to look for the source of
// the problem. If the error still persists, contact Oracle Support.
23504, 00000, "columns added to table do not match list of columns to be added"
// *Cause: The list of columns passed as a parameter does not match the
// columns to be added to the table.
// *Action: Correct the DDL string or list of columns and rexecute.
//
23505, 00000, "Object \"%s\".\"%s\" is missing."
// *Cause: The specified object does not exist.
// *Action: Check that the specified object is correct.
//
23514, 00000, "invalid or incorrect number of arguments"
// *Cause: The arguments passed to the online redefinition API were invalid
// or missing.
// *Action: Call the online redefinition API with the right number of valid
// arguments.
//
23515, 00000, "materialized views and/or their indices exist in the tablespace"
// *Cause: An attempt was made to drop a tablespace which contains
// materialized views and/or their indices.
// *Action: Drop the materialized views in this tablespace. Also,
// find indices belonging to materialized views in this
// tablespace and drop then. Then try dropping the tablespace.
//
23531, 00000, "site owner already exists in the template."
// *Cause: Site owner for the template already exists.
// *Action: Do not create multiple siteowners for this template.
//
23532, 00000, "tables with different synchronization mechanisms are in the same group"
// *Cause: Tables belonging to the same replication group were specified to
// be cached with different synchronization mechanisms.
// *Action: Do not specify different synchronization mechanisms while caching
// tables belonging to the same replication group.
//
23533, 00000, "object \"%s\".\"%s\" can not be cached"
// *Cause: An attempt was made to cache an object which is not supported.
// *Action: Do not cache an object which is not supported.
//
23534, 00000,"missing column in materialized view container table \"%s\".\"%s\""
// *Cause: After import, the materialized view container table has missing
// columns.
// *Action: Check if materialized view container table was imported correctly.
//
23535, 00000,"instantiating templates from multiple back ends is not allowed."
// *Cause: An attempt was made to set a new non-null back end database for an
// iAS site.
// *Action: Call dbms_ias_configure.set_back_end_db procedure with null dblink.
// Then, call the same procedure with the new non-null dblink.
//
23536, 00000, "the object \"%s\".\"%s\" is not cached at the middle tier as expected."
// *Cause: The object may have been dropped or renamed at the back end
// after dbms_ias_inst.start_ias_inst was executed.
// *Action: Check the validity of the object at the back end and retry
// the instantiation.
23537, 00000,"function or procedure %s is not allowed to be invoked from this site."
// *Cause: This function or procedure is restricted to the backend or
// middle tier site
// *Action: Connect to the proper site before calling this function or procedure.
//
23538, 00000, "cannot explicitly refresh a NEVER REFRESH materialized view (\"%s\")"
// *Cause: An attempt was made to explicitly refresh a NEVER REFRESH MV.
// *Action: Do not perform this refresh operation or
// remove the MV(s) from the list.
//
23539, 00000, "table \"%s\".\"%s\" currently being redefined"
// *Cause: An attempt was made to redefine a table which is currently involved
// in an ongoing redefinition.
// *Action: Do not perform this redefinition operation on this table or wait
// till the ongoing redefinition of the table is completed.
//
23540, 00000, "Redefinition not defined or initiated"
// *Cause: An attempt was made to continue or complete a redefinition which
// was not defined or initiated.
// *Action: Define or initiate the redefinition before performing this
// operation.
23541, 00000, "tables do not match tables used while defining the redefinition"
// *Cause: An attempt was made to continue or complete a redefinition by
// providing different tables than those used while defining or
// initiating the redefinition.
// *Action: Repeat this operation and specify the same tables as those that
// were specified while defining or initiating the redefinition.
//
23542, 00000, "dependent object \"%s\".\"%s\" already registered"
// *Cause: An attempt was made to register an already registered dependent
// object to an ongoing redefinition.
// *Action: Do not attempt to register an already registered dependent object
// to an ongoing redefinition.
//
23543, 00000, "materialized view log on \"%s\".\"%s\" is in an inconsistent state"
// *Cause: There was an error while creating the materialized view log and
// the log is currently in an inconsistent state. A possible cause
// could be that schema redefinition has occurred on the master table
// while the log was being created. Another possible cause could be
// that there were DMLs being applied on the master table concurrently
// in another session at the time the materialized view log creation
// started and those DML transactions haven't committed even after a
// very long period of time.
// *Action: Drop the materialized view log and recreate it.
//
23544, 00000, "enable online redef rowid mapping table testing event"
// *Document: NO
// *Cause:
// *Action: rowid mapping table debug/testing
23545, 00000, "enable iot rmt online redef rowid mapping table testing event"
// *Document: NO
// *Cause:
// *Action: rowid mapping table debug/testing
23546, 00000, "cannot create rowid mapping table %s.%s"
// *Cause: The online partition mover could not create a rowid mappping table.
// *Action: Rename the conflicting table or rerun the SQL statement.
// * There may be a concurrent online operation on the same object.
23547, 00000, "dml_lock_timeout value is out of the permitted range"
// *Cause: The value for dml_lock_timeout was out of the permitted range of
// 0 to 1,000,000.
// *Action: Use a value within the range of 0 to 1,000,000 and reexecute the
// procedure
23548, 00000, "rmt diagnostics event, internal verification failure"
// *Document: NO
// *Cause:
// *Action: rowid mapping table diagnostics,internal use only
23549, 00000, "table \"%s\".\"%s\" involved in reference partitioning"
// *Cause: An attempt was made to redefine a table which is currently involved
// in reference partitioning.
// *Action: Do not perform this redefinition operation on this table or
// remove reference partitioning and retry the operation.
//
23550, 00000, "cannot redefine a table with interim table having identity columns that appear in column mapping"
// *Cause: An attempt was made to redefine a table where the interim table has
// identity columns that appear in column mapping.
// *Action: Do not perform this redefinition operation or avoid using identity
// columns of the interim table in column mapping.
//
23551, 00000, "unsupported UPDATE statement on an index-organized table"
// *Cause: An attempt was made to update primary key columns of an
// index-organized table.
// *Action: Do not perform this redefinition operation or avoid updating
// primary key columns.
//
23552, 00000, "cannot redefine an interval partitioned table with ILM policy"
// *Cause: An attempt was made to redefine a table that has interval
// partitioning with ILM policy defined on it.
// *Action: Do not perform this redefinition operation or avoid using
// interval partitions when ILM policy needs to be used.
//
23553, 00000, "cannot import materialized view \"%s\".\"%s\" due to synonym mismatch"
// *Cause: Synonym mismatch occurred during the import of materialized
// views when REMAP_SCHEMA option was specified.
// *Action: Do not use the REMAP_SCHEMA option for importing materialized views
// with synonyms.
//
///////////////////////////////////////////////////////////////////////////////
// 23600-23999 Reserved for Log Based Replication PL/SQL packages
///////////////////////////////////////////////////////////////////////////////
//
23600, 00000, "cannot create PROPAGATION, %s already exists"
// *Cause: The propagate_name already exists.
// *Action: Drop the propagate_name usign DROP_PROPAGATEcommand or
// specify propagate_name.
23601, 00000, "PROPAGATION_NAME %s does not exist"
// *Cause: Propagation does not exist.
// *Action: Query DBA_PROPAGATION view to find existing propagation_name
//
23602, 00000, "Invalid %s process type %s"
// *Cause: Specified GoldenGate, XStream or Streams process type is not valid.
// *Action: Specify either capture or apply.
23603, 00000, "%s enqueue aborted due to low SGA"
// *Cause: An attempt to enqueue a GoldenGate, XStream or Streams message was aborted because
// ORACLE is running low on memory allotted.
// *Action: Either start consuming messages by enabling any GoldenGate, XStream or Streams
// propagation or apply which might be disabled.
// An alternative is to allot more
// memory to STREAMS, which can be done by increasing the
// streams_pool_size initialization parameter if one was defined
// or by increasing the shared_pool_size.
23605, 00000, "invalid value \"%s\" for %s parameter %s"
// *Cause: An attempt was made to specify an invalid parameter value.
// *Action: Specify a valid value for the parameter. Check the documentation
// for valid parameter values.
23606, 00000, "invalid object %s"
// *Cause: An attempt was made to specify an invalid object.
// *Action: Specify a valid object.
23607, 00000, "invalid column \"%s\""
// *Cause: An invalid column was specified in the column list.
// *Action: Check the columns in the object and specify the right column name.
23608, 00000, "invalid resolution column \"%s\""
// *Cause: An invalid column was specified as the resolution column. The
// resolution column must belong to the list of columns specified in
// the 'column_list' parameter.
// *Action: Check the columns in the column_list and specify the right
// resolution column name.
23609, 00000, "unable to find directory object for directory %s"
// *Cause: There was no entry in ALL_DIRECTORIES corresponding to the
// specified directory.
// *Action: Grant to the current user appropriate privileges on either a new
// directory object or an existing directory object.
23610, 00000, "internal dbms_streams_tablespaces error: [%s] [%s] [%s] [%s]"
// *Cause: Streams detected an erroneous result.
// *Action: Look for information in the session trace file and contact
// customer support.
23611, 00000, "tablespace \"%s\" has more than one data file"
// *Cause: The specified tablespace had more than one data file and hence
// did not qualify as a simple tablespace.
// *Action: Choose a self-contained tablespace with a single data file, or
// use a procedure that supports any tablespace.
23612, 00000, "unable to find tablespace \"%s\""
// *Cause: Either the tablespace did not exist, or the current user did
// not have sufficient privileges on the tablespace.
// *Action: Grant appropriate privileges on the tablespace to the current
// user or choose a different tablespace.
23613, 00000, "Script %s already exists"
// *Cause: A script for the specified invoking package already existed.
// *Action: Complete the previous invocation or drop the previous invocation
// before proceeding with the current invocation.
23614, 00000, "Script %s does not exist"
// *Cause: The named script did not exist.
// *Action: Create the script.
23615, 00000, "Block number %s does not exist for script %s"
// *Cause: The specified block number did not exist for the script.
// *Action: Add the block or check the block number and reexecute.
23616, 00000, "Failure in executing block %s for script %s with \n%s"
// *Cause: The execution of specified block failed.
// *Action: Check the error. Query DBA_RECOVERABLE_SCRIPT_BLOCKS to view
// the failed block. Rectify and rerun the block or script.
23617, 00000, "Block %s for script %s has already been executed"
// *Cause: The specified block was already executed.
// *Action: Check the block number and reissue the command.
23618, 00000, "Generation of script %s is not complete."
// *Cause: Script generation for the specified script was not completed in
// a prior invocation.
// *Action: Purge the specified script by calling the RECOVER_OPERATION API
// in the package DBMS_STREAMS_ADM and reattempt the entire
// operation.
23619, 00000, "non-Oracle system error: %s"
// *Cause: A non-Oracle database has returned an error message to STREAMS
// when attempting to apply a DML statement. The non-Oracle system
// error message is a parameter to this Oracle error.
// *Action: Corrective action may or may not be possible (depending on the
// non-Oracle system error). If corrective action is possible,
// correct the problem and try applying the transaction again.
23620, 00000, "bind value size too large for PL/SQL CALL operation"
// *Cause: In a PL/SQL CALL to a stored procedure, the bind string
// size exceeded 4K.
// *Action: Either make the bind string size shorter (less than 4K) or use
// BEGIN-END to call the procedure instead of CALL.
23621, 00000, "Operation corresponding to script %s is in progress."
// *Cause: The script was already being run in a different session or was
// terminated before status for the script was updated to ERROR or
// EXECUTED.
// *Action: Make sure the script is not being run in a parallel session.
// Then call the RECOVER_OPERATION API in the DBMS_STREAMS_ADM
// package with the appropriate OPERATION_MODE argument.
23622, 00000, "Operation %s.%s.%s is in progress."
// *Cause: An attempt was made to execute a procedure which was being
// executed in a parallel session or failed execution.
// *Action: Query the DBA_RECOVERABLE_SCRIPT view to identify the operation
// that is currently in progress for the specified invoking
// procedure. Complete the operation before proceeding.
23623, 00000, "internal DBMS_COMPARISON error: [%s] [%s] [%s] [%s]"
// *Cause: DBMS_COMPARISON detected an erroneous result.
// *Action: Look for information in the session trace file and contact
// Oracle Support Services.
23624, 00000, "A comparison operation is currently in progress for %s."
// *Cause: Another session was already performing an operation on this object.
// *Action: Retry the operation once other sessions are done with the specific
// comparison object.
23625, 00000, "Table shapes of %s.%s and %s.%s@%s did not match."
// *Cause: Table shapes of local and remote tables to compare did not match.
// *Action: Retry by explicitly specifying columns that match in column_list
// or create views on the tables as appropriate.
23626, 00000, "No eligible index on table %s.%s"
// *Cause: Table did not have an eligible index to use for comparison.
// *Action: For a table to be compared using DBMS_COMPARISON, the table must
// have an appropriate index on a column of certain data types.
// Check the documentation for supported data types.
23627, 00000, "Comparison object %s already existed."
// *Cause: A comparison object by the specified name already exists.
// *Action: Retry with a different name.
//
23628, 00000, "Comparison query too long (actual %s, allowed %s)."
// *Cause: A generated query for comparison was too long.
// *Action: Comparison is unsupported for very large tables with long column
// names. Retry with a subset of columns or with shorter column names.
//
23629, 00000, "%s.%s is not an eligible index on table %s.%s for comparison"
// *Cause: The specified index was not an eligible index to use for
// comparison.
// *Action: For a table to be compared using DBMS_COMPARISON, the table must
// have an appropriate index. Please specify an eligible index for the
// table to be compared.
23630, 00000, "Cannot switch to apply-state checkpoint mode (value \"%s\", %s parameter %s), due to the following reason:"
// *Cause: Could not switch to apply-state checkpoint mode, or already in
// apply-state checkpoint mode.
// *Action: Can switch to apply-state checkpoint mode only if the capture is new
// (it never ran), the capture wasn't cloned from a capture with
// checkpoints, the capture doesn't include any extra attributes,
// and combined capture and apply is enabled.
//
23631, 00000, "apply-state checkpoint mode cannot change (value \"%s\", %s parameter %s)"
// *Cause: Could not switch to checkpoints because apply-state checkpoint mode
// was set.
// *Action: Drop the apply-state checkpoint capture and create a new one that will
/// take checkpoints.
//
23632, 00000, "Cannot force checkpoints in apply-state checkpoint mode (value \"%s\", %s parameter %s)"
// *Cause: The capture process was in apply-state checkpoint mode.
// *Action: Cannot take checkpoints in apply-state checkpoint mode.
//
23633, 00000, "Cannot turn off combined capture and apply mode in apply-state checkpoint mode (value \"%s\", %s parameter %s)"
// *Cause: The capture was running in apply-state checkpoint mode and had to run in
// combined capture and apply mode also.
// *Action: Ensure that this capture runs in combined capture and apply
// by dropping additional propagation or apply processes for the same
// queue.
//
23634, 00000, "Cannot include extra attributes in apply-state checkpoint mode"
// *Cause: The capture process was in apply-state checkpoint mode.
// *Action: Extra attributes are not supported in apply-state checkpoint mode.
//
23635, 00000, "MAINTAIN_TTS: tablespace(s) already exist(s) in target database."
// *Cause: The tablespaces were already in existence in the target database
// when the streams MAINTAIN_TTS APIs were called."
// *Action: Check whether you can drop the tablespaces to be maintained in the
// target database. If not, don't use streams MAINTAIN_TTS APIs to
// setup streams. Check the Oracle documentation on how to setup
// streams.
23636, 00000, "MAINTAIN_TTS: Invalid tablespace name, reason: %s."
// *Cause: The tablespace name was either NULL or too long when the streams
// MAINTAIN_TTS APIs were called.
// *Action: Check that the specified tablespace names are not NULL and are
// spelled correctly. If there are too many tablespaces, group them
// together and call the streams MAINTAIN_TTS APIs for the group.
//
23637, 00000, "Capture started in checkpoint mode"
// *Cause:
// *Action:
23638, 00000, "Capture cloned from a capture with checkpoints"
// *Cause:
// *Action:
23639, 00000, "Extra Attribute included"
// *Cause:
// *Action:
23640, 00000, "Combined capture and apply disabled"
// *Cause:
// *Action:
23641, 00000, "Capture started in apply-state checkpoint mode already"
// *Cause:
// *Action:
23642, 00000, "Cannot switch to checkpoint mode (value \"%s\", %s parameter %s)"
// *Cause: Capture was cloned from a capture in apply-state checkpoint mode.
// *Action: Clone from a capture with checkpoints.
23643, 00000, "Capture cloned from a capture in apply-state checkpoint mode"
// *Cause:
// *Action:
23644, 00000, "Cannot switch to apply-state checkpoint mode (Capture %s)"
// *Cause: Switch to apply-state checkpoint mode was prevented by a previous error.
// *Action: See the previous error for the appropriate action.
23645, 00000, "Cannot switch to checkpoints (Capture %s)"
// *Cause: Switch to checkpoints was prevented by a previous error.
// *Action: See the previous error for the appropriate action.
23646, 00000, "%s %s process %s does not exist"
// *Cause: Capture or Apply did not exist.
// *Action: Create a Capture or Apply process, then try again.
23647, 00000, "%s %s process %s is not running"
// *Cause: Capture or Apply were not running.
// *Action: Start Capture or Apply process, then try again
23648, 00000, "Capture %s is for Change Data Capture"
// *Cause: Capture was for Change Data Capture, and checkpoints were required.
// *Action: None.
23649, 00000, "Capture %s is for Audit Vault"
// *Cause: Capture was for Audit Vault, and checkpoints were required.
// *Action: None.
23650, 00000, "No progress Capture %s"
// *Cause: Capture was not capturing changes.
// *Action: Make sure Capture is running and capturing changes.
23651, 00000, "Capture %s is already in %s mode"
// *Cause: Capture was already in the desired mode.
// *Action: None.
23652, 00000, "The oldest SCN could not be updated at Apply %s"
// *Cause: The oldest SCN was not updated before the switch was performed.
// *Action: Make sure Apply is running and the switch package version is
// the same at both databases.
23653, 00000, "LogMiner session does not exist"
// *Cause: LogMiner session did not exist.
// *Action: Make sure the Capture process exists.
23654, 00000, "Attempting to set the oldest SCN to a greater value (%s) than the current one (%s) at Apply %s"
// *Cause: The new value for the oldest SCN was not computed correctly.
// *Action: Make sure Capture and Apply are running, and Capture is
// making progress.
23655, 00000, "The SCN range cannot be smaller than 0, (SCN range = %s)"
// *Cause: The function was invoked with a negative SCN range.
// *Action: Use a positive SCN range.
23656, 00000, "Timeout occurred while %s %s process %s"
// *Cause: The GoldenGate, XStream or Streams process could not be stopped or started.
// *Action: Call the switch procedure again.
23657, 00000, "the converted file %s already exists"
// *Cause: The converted file was already in existence.
// CONVERT FILE call does not overwrite the existing file.
// *Action: Check whether the existing file can be deleted.
// If the existing file can be deleted, delete it. Otherwise,
// specify a different directory or file extension.
23658, 00000, "Invalid character set specified when converting column '%s' in '%s.%s'"
// *Cause: The conversion between two character sets for the column in the given table
// is not supported.
// *Action: Check if the implicit conversion between source and destination column
// is supported.
23659, 00000, "Destination buffer is not large enough when converting column '%s' in '%s.%s' (actual length: %s; maximum length: %s)"
// *Cause: The conversion between two character sets failed because a source column
// value is too large for the destination column.
// *Action: Check if size of the source and destination column matches.
23660, 00000, "Unable to load NLS data object when converting column '%s' in '%s.%s'"
// *Cause: It may be caused by invalid NLS environment setting.
// *Action: Check your NLS environment setting.
23661, 00000, "Canon capture name \"%s\" not found"
// *Cause: There's no such capture process
// *Action: Pass the right parameter to the function
23662, 00000, "subset rule length exceeds maximum allowed value"
// *Cause: The length of an insert, update, or delete subset rule computed
// from the DML condition input exceeded the maximum allowed length.
// *Action: Make the DML condition shorter.
23663, 00000, "local object %s.%s is not a single table view"
// *Cause: The view was based either on another view or multiple tables or
// views.
// *Action: For comparison, specify a view based on a single table.
23664, 00000, "remote object %s.%s is not a single table view"
// *Cause: The view was based either on another view or multiple tables or
// views.
// *Action: For comparison, specify a view based on a single table.
23665, 00000, "DML conflict handler \"%s\" not found"
// *Cause: The DML conflict handler was not found for modification or removal.
// *Action: Make sure the name of the conflict handler is correct and that it
// exists.
23666, 00000, "Default column group in use by DML conflict handler \"%s\""
// *Cause: A default column group was found for the specified Apply name,
// operation name, and conflict type.
// *Action: Remove the existing default column group and retry.
23667, 00000, "Column \"%s\" already used by conflict handler \"%s\""
// *Cause: The column was already in the column group of another conflict
// handler for the specified Apply name, operation name, and conflict
// type.
// *Action: Remove the column from the other conflict handler or specify a
// different column.
23668, 00000, "Column \"%s\" does not have a numeric data type."
// *Cause: The specified column did not have a numeric data type. Delta
// conflict resolution requires numeric columns.
// *Action: Check the data type of the column and specify only numeric columns.
23669, 00000, "Duplicate conflict handler name"
// *Cause: A DML conflict handler with the specified name was found.
// *Action: Remove the current DML conflict handler or specify a different
// name.
23670, 00000, "Duplicate column name \"%s\""
// *Cause: The specified value was duplicated in the column group list.
// *Action: Remove duplicated entries from the column group list.
23671, 00000, "Default column group required"
// *Cause: A default column group was not specified. The specified Apply name,
// operation name, and conflict type is only supported on default
// column groups.
// *Action: Specify a default column group.
23672, 00000, "Column not specified in column group for DML conflict handling for table \"%s\".\"%s\""
// *Cause: The specified table contained a column that was not specified as
// part of a column group.
// *Action: Add the column to a column group.
23673, 00000, "Invalid resolution column \"%s\" for table \"%s\".\"%s\""
// *Cause: The specified resolution column was not valid.
// *Action: Set the resolution column to a valid column.
23674, 00000, "Unable to handle delta conflict resolution for table \"%s\".\"%s\""
// *Cause: The specified table or the LCR contained a null value in one of the
// columns belonging to a delta conflict group.
// *Action: Correct each delta column in the table or the error LCR if it
// currently has a null value.
23675, 00000, "Unsupported OPERATION_NAME, CONFLICT_TYPE, and METHOD_NAME"
// *Cause: The specified OPERATION_NAME, CONFLICT_TYPE, and METHOD_NAME was
// not a valid set of parameters.
// *Action: Retry with a valid set of parameters.
23676, 00000, "no eligible index on local table \"%s\".\"%s\""
// *Cause: The local table did not have an eligible index to use for
// comparison.
// *Action: For a table to be compared using DBMS_COMPARISON, the table must
// have an appropriate index on a column of certain data types.
// Check the documentation for supported data types.
23677, 00000, "no eligible index on remote table \"%s\".\"%s\""
// *Cause: The remote table did not have an eligible index to use for
// comparison.
// *Action: For a table to be compared using DBMS_COMPARISON, the table must
// have an appropriate index on a column of certain data types.
// Check the documentation for supported data types.
23678, 00000, "index \"%s\".\"%s\" on local table \"%s\".\"%s\" is not eligible for comparison"
// *Cause: The specified index was not eligible for comparison.
// *Action: For a table to be compared using DBMS_COMPARISON, the table must
// have an appropriate index. Specify an eligible index for the table
// to be compared.
23679, 00000, "index \"%s\".\"%s\" on remote table \"%s\".\"%s\" is not eligible for comparison"
// *Cause: The specified index was not eligible for comparison.
// *Action: For a table to be compared using DBMS_COMPARISON, the table must
// have an appropriate index. Specify an eligible index for the table
// to be compared.
///////////////////////////////////////////////////////////////////////////////
// 24000 - 24099 - Reserved for ADMINISTRATIVE INTERFACE FOR AQ
///////////////////////////////////////////////////////////////////////////////
24000, 00000, "invalid value %s, %s should be of the form [SCHEMA.]NAME"
// *Cause: An invalid value was specified for the paramerter.
// *Action: Specify a string of the form [SCHEMA.]NAME .
//
24001, 00000, "cannot create QUEUE_TABLE, %s already exists"
// *Cause: The queue table already exists in the queueing system.
// *Action: Drop the table first using the DROP_QUEUE_TABLE() command or
// specify another table.
//
24002, 00000, "QUEUE_TABLE %s does not exist"
// *Cause: Queue_table not exist.
// *Action: Query on the user view USER_QUEUE_TABLES to find out existing queue
// tables.
//
24003, 00000, "Queue table index %s inconsistent with queue table %s"
// *Cause: The queue table index has not yet been successfully imported.
// *Action: Import the queue table index before attempting to use the queue
// table. If the import failed, correct the problem and try to import
// the queue table index again.
//
//
24004, 00000, "invalid column name %s in SORT_LIST, should be ENQ_TIME or PRIORITY"
// *Cause: Invalid column name was specified in the SORT_LIST.
// *Action: The valid column names are ENQ_TIME and PRIORITY.
//
24005, 00000, "Inappropriate utilities used to perform DDL on AQ table %s.%s"
// *Cause: An attempt was made to use the SQL command DROP TABLE or TRUNCATE
// TABLE or ALTER TABLE on queue metadata or tables.
// *Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE to DROP TABLE,
// DBMS_AQADM.PURGE_QUEUE_TABLE to TRUNCATE TABLE.
// ALTER TABLE redefinition based on only ALTER_TABLE_PROPERTIES and
// ALTER_TABLE_PARTITIONING clauses are allowed.
//
24006, 00000, "cannot create QUEUE, %s already exists"
// *Cause: The queue requested to be created already exists.
// *Action: Specify another queue name. Query USER_QUEUES for all the exisiting
// queues in the users's schema.
//
24007, 00000, "invalid value %s, MAX_RETRIES should be non-negative integer"
// *Cause: An invalid value was specified for MAX_RETRIES.
// *Action: Specify a non-negative integer.
//
24008, 00000, "queue table %s.%s must be dropped first"
// *Cause: An error was detected when dropping a queue table in a cluster,
// tablespace, or schema.
// *Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure to drop the specified
// queue table first; then, retry the operation.
//
24009, 00000, "invalid value %s, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE"
// *Cause: Invalid queue type parameter
// *Action: Valid values are NORMAL_QUEUE for normal queue and EXCEPTION_QUEUE
// for exception queue.
//
24010, 00000, "QUEUE %s does not exist"
// *Cause: The specified queue does not exist.
// *Action: Specify a valid queue. Query USER_QUEUES for all the valid
// queues.
//
24011, 00000, "cannot drop QUEUE, %s should be stopped first"
// *Cause: The queue has not been stopped i.e. either enqueue or
// dequeue is still enabled.
// *Action: Stop the queue first using the STOP_QUEUE command and disable
// it from both enqueueing and dequeueing.
//
24012, 00000, "cannot drop QUEUE_TABLE, some queues in %s have not been dropped"
// *Cause: A queue exists in the queue table which has not been dropped.
// All queues need to be dropped first.
// *Action: Drop all queues belonging to this queue table using the drop_queue()
// command. Be sure to stop the queues appropriately before dropping
// them. Alternately, use the force option in drop_queuetable.
//
24013, 00000, "invalid value %s, RETRY_DELAY should be non-negative"
// *Cause: A negative value was specified for RETRY_DELAY.
// *Action: Specify a non-negative value for RETRY_DELAY.
24014, 00000, "invalid value %s, RETENTION_TIME should be FOREVER or non-negative"
// *Cause: Queue retention was specified, but the retention time was
// specified to be less than zero.
// *Action: Specify the retention time to be non-negative or FOREVER.
// Alternately don't specify retention.
//
24015, 00000, "cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE %s.%s does not exist"
// *Cause: An invalid QUEUE_PAYLOAD_TYPE specified during create_queue_table.
// *Action: The QUEUE_PAYLOAD_TYPE should be RAW or an object type that already
// exists in the database.
//
24016, 00000, "cannot create QUEUE_TABLE, user %s does not have execute privileges on QUEUE_PAYLOAD_TYPE %s.%s"
// *Cause: An invalid object type specified for QUEUE_PAYLOAD_TYPE during
// create_queue_table.
// *Action: The user should have execute priviliges on the object type specified
// for the queue.
//
24017, 00000, "cannot enable enqueue on QUEUE, %s is an exception queue"
// *Cause: User tried to enable enqueueing to an exception queue.
// *Action: None.
24018, 00000, "STOP_QUEUE on %s failed, outstanding transactions found"
// *Cause: There were outstanding transactions on the queue, and WAIT was set to
// false, so STOP_QUEUE was unsucessful in stopping the queue.
//
// *Action: Set WAIT to TRUE and try STOP_QUEUE again. It will hang till all
// outstanding transactions are completed.
//
24019, 00000, "identifier for %s too long, should not be greater than %s characters"
// *Cause: The identifier specified is too long.
// *Action: Try again with a shorter identifier.
//
24020, 00000, "Internal error in DBMS_AQ_IMPORT_INTERNAL, %s"
// *Cause: Internal Error occured in the package DBMS_AQ_IMPORT_INTERNAL.
// *Action: Internal error, call Oracle Support.
//
24021, 00000, "queue table definition not imported for %s.%s"
// *Cause: The queue definition is not updated because the queue table
// was not imported properly
//
// *Action: Import the queue table again.
24022, 00000, "the specified parameters has no effect on the queue"
// *Cause: The parameter combination will not cause the queue to
// be started or stoped.
// *Action: None. This is just a warning.
//
24023, 00000, "Internal error in DBMS_AQ_EXP_INTERNAL.%s [%s] [%s]"
// *Cause: Internal Error occured in the package DBMS_AQ_EXP_INTERNAL.
// *Action: Internal error, call Oracle Support.
//
24024, 00000, "Internal error in DBMS_AQ_IMP_INTERNAL.%s [%s] [%s]"
// *Cause: Internal Error occured in the package DBMS_AQ_IMP_INTERNAL.
// *Action: Internal error, call Oracle Support.
//
24025, 00000, "invalid value %s, QUEUE_PAYLOAD_TYPE should be RAW or an object type"
// *Cause: Parameter queue_payload_type has invalid value.
// *Action: Specify a valid object type or RAW.
//
24026, 00000, "operation failed, queue %s.%s has errors"
// *Cause: An attempt was made to enqueue, dequeue or administer a queue which
// has errors.
// *Action: Drop the queue table setting the force option to true.
//
24027, 00000, "AQ HTTP propagation encountered error, status-code %s, %s"
// *Cause: AQ propagation's HTTP request to the propagation servlet at the
// specified address encountered an error
// *Action: Specify a valid address in the connect string of the propagation
// destination dblink, the dblink user has the correct permissions,
// check if the AQ propagation servlet was properly installed.
24028, 00000, "cannot create a reciever non-repudiable single consumer queue"
// *Cause: Tried to create a reciever non-repudiable single consumer queue
// *Action: This feature is not supported
24029, 00000, "operation not allowed on a single-consumer queue"
// *Cause: Tried an operation not allowed on a single-consumer queue.
// *Action: Specify the operation on a multi-consumer queue.
24030, 00000, "Only one of rule or rule-set must be specified"
// *Cause: Specified both a rule and rule-set for the operation.
// *Action: Specify only one of rule or rule-set.
24031, 00000, "invalid value, %s should be non-NULL"
// *Cause: Parameter is NULL.
// *Action: Specify a non NULL value for the parameter.
//
24032, 00000, "object %s exists, index could not be created for queue table %s"
// *Cause: Oracle AQ tried to create an index with the name
// specified in the error message. The
// index could not be created for the specified queue
// table because a object exists with the same name.
// *Action: Drop the object specified in the error message and retry the
// command. You can also choose a different name for the queue table.
//
24033, 00000, "no recipients for message"
// *Cause: An enqueue was performed on a queue that has been set up for
// multiple dequeuers but there were neither explicit recipients
// specified in the call nor were any queue subscribers determined
// to be recipients for this message.
// *Action: Either pass a list of recipients in the enqueue call or add
// subscribers to the queue for receiving this message.
24034, 00000, "application %s is already a subscriber for queue %s"
// *Cause: An application name that was already a subscriber for the queue
// was specified in the dbms_aq.subscribe call.
// *Action:
24035, 00000, "AQ agent %s is not a subscriber for queue %s"
// *Cause: An AQ agent that was not a subscriber for the queue
// was specified.
// *Action: Check the name and/or address of the agent and retry the call.
//
24036, 00000, "invalid SORT_ORDER column %s specified for queue table "
// *Cause: The create queue table command was issued with
// message_grouping set to TRANSACTIONAL and a sort order column
// other than priority. Only the priority column can be specified
// in the sort order for queue tables with transactional grouping.
// *Action: Change the sort order list in the create queue table command and
// retry the call.
//
24037, 00000, "schema %s in QUEUE_NAME is not same as schema %s in QUEUE_TABLE"
// *Cause: The schema specified in the QUEUE_NAME parameter of CREATE_QUEUE
// is not the same as the schema specified in the QUEUE_TABLE
// parameter.
// *Action: Use the same schema name for both the QUEUE_NAME and QUEUE_TABLE
// parameters and retry the command.
//
24038, 00000, "RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0 compatible multiple consumer queue"
// *Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero
// RETRY_DELAY and a QUEUE_TABLE that was created for multiple
// consumers and with COMPATIBLE parameter set to '8.0'.
// *Action: Either set the RETRY_DELAY to zero or upgrade the queue table to
// 8.1 compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.
//
24039, 00000, "Queue %s not created in queue table for multiple consumers"
// *Cause: Either an ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER
// procedure, or an ENQUEUE with a non-empty recipient list, was
// issued on a queue that was not created for multiple consumers.
// *Action: Create the queue in a queue table that was created for
// multiple consumers and retry the call.
//
// NLS_DO_NOT_TRANSLATE [24040,24040]
24040, 00000, "AQ tracing event"
// *Cause: N/A
// *Action: Event used to trace operation of AQ.
// *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
//
24041, 00000, "propagation schedule exists for QUEUE %s and DESTINATION %s"
// *Cause: A SCHEDULE_PROPAGATION was issued for a queue and destination pair
// which has an existing propagation schedule.
// *Action: Issue UNSCHEDULE_PROPAGATION to remove the existing schedule and
// then reissue the SCHEDULE_PROPAGATION call.
//
24042, 00000, "no propagation schedule exists for QUEUE %s and DESTINATION %s"
// *Cause: AN UNSCHEDULE_PROPAGATION was issued for a queue and destination
// pair which has no existing propagation schedule.
// *Action: Verify the spelling of the specified QUEUE and DESTINATION and
// then reissue the call with the correct spelling.
//
24043, 00000, "destination %s uses a reserved name, names with AQ$_ prefix are not valid"
// *Cause: An attempt was made to specify a reserved name for a destination.
// *Action: Enter a different value or NULL for the local destination.
// Then retry the operation.
//
24044, 00000, "source %s and destination %s object types do not match"
// *Cause: A message recipient's queue has a different object structure
// than the sender's queue. The message cannot be propagated.
//
// *Action: Either remove the recipient from the subscriber's list for the
// sender's queue or create the destination queue with an object type
// that matches the source queue's object type.
//
24045, 00000, "invalid agent address %s, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]"
// *Cause: An invalid value was specified for the agent address parameter.
// *Action: Specify a string of the form [SCHEMA.]NAME[@DATABASE LINK].
//
24046, 00000, "protocol attribute reserved for future use"
// *Cause: The protocol attribute of the AQ agent object type is reserved for
// future use.
// *Action: Do not specify the protocol attribute in the agent object type.
//
24047, 00000, "invalid agent name %s, agent name should be of the form NAME"
// *Cause: An invalid value was specified for the agent name parameter.
// *Action: Specify a string of the form NAME. Then retry the operation.
//
24048, 00000, "cannot create QUEUE_TABLE, user does not have access to AQ object types"
// *Cause: An attempt was made to issue the CREATE_QUEUE_TABLE command, but
// the user who issued the command does not have access to internal
// AQ object types.
// *Action: Use the DBMS_AQADM.GRANT_TYPE_ACCESS procedure to grant the
// user access to the AQ object types.
//
24049, 00000, "invalid agent name %s, names with AQ$_ prefix are not valid"
// *Cause: An attempt was made to use a reserved prefix in the agent name.
// *Action: Enter a different value for the agent name. Then, retry the
// operation.
//
24050, 00000, "subscribers are not supported for exception queue %s"
// *Cause: An ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER
// procedure was issued on a queue that was created as an
// EXCEPTION_QUEUE.
// *Action: Specify a NORMAL_QUEUE in the procedure.
//
24051, 00000, "cannot propagate object type payloads that have a REF attribute"
// *Cause: An ADD_SUBSCRIBER or ENQUEUE procedure with a non-NULL address
// field in the agent type was issued on a queue whose payload has a
// REF attribute. Propagation of object type payloads
// that have a REF attribute currently is not supported.
// *Action: Specify an agent with a NULL address field so that the agent can
// dequeue from the same queue. Or, change the object type definition
// to one that does not use REF attributes.
24052, 00000, "cannot propagate object type payloads with LOB attributes to an 8.0 release"
// *Cause: The recipient of a message with LOB attributes was using an Oracle
// 8.0 release. Propagation of LOB attributes is supported only in
// Oracle 8.1 and higher releases.
// *Action: Upgrade the target release to Oracle 8.1 and retry. Or, change
// the object type definition to one that does not use LOBs.
24053, 00000, "PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative"
// *Cause: One of PRIMARY_INSTANCE or SECONDARY_INSTANCE was negative.
// *Action: Specify non-negative integers for PRIMARY_INSTANCE and SECONDARY_INSTANCE.
//
24054, 00000, "cannot propagate to an Oracle 8.0.3 release or lower release"
// *Cause: The recipient of a message was using an Oracle 8.0.3 release or
// lower release. Propagation is supported only in Oracle 8.0.4 and
// higher releases.
// *Action: Upgrade the target release to Oracle 8.0.4 or higher and retry.
//
//
24055, 00000, "cannot delete propagation status rows that are in prepared state"
// *Cause: An attempt was made to use the internal administration procedure
// to delete status rows from the SYS.AQ$_PROPAGATION_STATUS table
// that were in the prepared state.
// *Action: Wait for the propagation to complete successfully before retrying
// the operation.
24056, 00000, "internal inconsistency for QUEUE %s and destination %s"
// *Cause: The sequence numbers used in the SYS.AQ$_PROPAGATION_STATUS table
// were inconsistent for the given queue and destination.
// *Action: Contact Oracle Worldwide Support.
//
24057, 00000, "cannot define subscriber with rule for queue %s"
// *Cause: An ADD_SUBSCRIBER or ALTER_SUBSCRIBER procedure with a rule was
// issued on a queue for which rule based subscribers are not
// supported. Rule based subscribers currently are supported only
// for NORMAL (persistent) multi-consumer queues created using an
// Oracle release 8.1.0 or higher compatible queue table.
// *Action: Create a NORMAL multi-consumer queue in an Oracle release 8.1.0
// or higher compatible queue table, and retry the call.
// Or, if the queue is a normal (persistent) multi-consumer queue,
// convert the queue table to Oracle 8.1.0 or higher compatibility
// and retry.
//
24058, 00000, "cannot downgrade QUEUE_TABLE that has propagation in a prepared state"
// *Cause: An attempt was made to downgrade the queue table when there were
// messages being propagated that were in the prepared state.
// *Action: Wait for the propagation to complete before retrying the operation.
//
24059, 00000, "invalid COMPATIBLE parameter setting %s specified in DBMS_AQADM.%s"
// *Cause: An invalid compatible parameter was specified in the
// DBMS_AQADM procedure. The parameter setting must be of the form
// '8.x.y' where x is the release number and y is the update number.
// *Action: Specify a valid COMPATIBLE parameter setting, and retry the
// operation.
//
24060, 00000, "cannot convert QUEUE_TABLE, %s already is compatible with release %s"
// *Cause: The source queue table in the DBMS_AQADM procedure is
// compatible with the specified COMPATIBLE parameter setting.
// *Action: Choose a different COMPATIBLE parameter setting to convert the
// queue table to the desired compatibility.
//
24061, 00000, "cannot specify non-zero SECONDARY_INSTANCE if PRIMARY_INSTANCE was zero"
// *Cause: A non-zero value was specified for SECONDARY_INSTANCE when
// PRIMARY_INSTANCE was zero.
// *Action: Specify a non-zero primary instance before you specify a non-zero
// secondary instance.
//
//
24062, 00000, "Subscriber table %s inconsistent with queue table %s"
// *Cause: The subscriber table has not yet been successfully imported.
// *Action: Import the subscriber table before attempting to use the queue
// table. If the import failed, correct the problem and try to import
// the subscriber table again.
24063, 00000, "cannot downgrade QUEUE_TABLE that has queues with rule-based subscribers"
// *Cause: An attempt was made to downgrade the queue table when there were
// queues on which rule based subscribers are defined.
// *Action: Remove the rule based subscribers for all queues in this queue
// table and retry.
//
24064, 00000, "propagation for QUEUE %s and DESTINATION %s already enabled"
// *Cause: An ENABLE_SCHEDULE_PROPAGATION command was issued for a queue and
// destination pair whose propagation schedule already was enabled.
// *Action: Make sure the QUEUE and DESTINATION are correct when you issue
// the ENABLE_SCHEDULE_PROPAGATION command.
//
24065, 00000, "propagation for QUEUE %s and DESTINATION %s already disabled"
// *Cause: A DISABLE_SCHEDULE_PROPAGATION command was issued for a queue and
// destination pair whose propagation schedule already was disabled.
// *Action: Make sure the QUEUE and DESTINATION are correct when you issue
// the DISABLE_SCHEDULE_PROPAGATION command.
//
24066, 00000, "invalid privilege specified"
// *Cause: An invalid privilege is specified for granting or revoking
// privilege
// *Action: Specify a valid privilege.
//
24067, 00000, "exceeded maximum number of subscribers for queue %s"
// *Cause: An attempt was made to add new subscribers to the specified,
// but the number of subscribers for this queue has exceeded the
// maximum number (1024) of subscribers allowed per queue.
// *Action: Remove existing subscribers before trying to add new subscribers.
//
24068, 00000, "cannot start queue %s, queue table %s is being migrated"
// *Cause: An attempt was made to start a queue in a queue table that is
// being migrated.
// *Action: Complete the queue table migration, and retry the operation.
//
24069, 00000, "cannot downgrade queue table %s while it is being upgraded"
// *Cause: An attempt was made to downgrade a queue table, but a previous
// command to upgrade the queue table has not yet completed
// successfully.
// *Action: Complete the upragde of the queue table by re-executing the
// DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, downgrade
// the queue table.
24070, 00000, "cannot upgrade queue table %s while it is being downgraded"
// *Cause: An attempt was made to upgrade a queue table, but a previous
// command to downgrade the queue table has not yet completed
// succesfully.
// *Action: Complete the downgrade of the queue table by re-executing the
// DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, upgrade the
// queue table.
24071, 00000, "cannot perform operation %s, queue table %s is being migrated"
// *Cause: An attempt was made to perform an operation on a queue in a
// queue table that is being migrated.
// *Action: Complete the queue table migration, and retry the operation.
//
24072, 00000, "cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table"
// *Cause: An attempt was made to upgrade or downgrade a queue table
// using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure, but the
// user who executed the procedure does not own the queue.
// *Action: Reconnect as the owner of the queue table, and then execute
// the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.
//
24073, 00000, "cannot specify RETENTION_TIME on exception queue %s.%s"
// *Cause: An attempt was made to create or alter an exception queue by
// specifying a non-zero RETENTION_TIME.
// *Action: Use the default RETENTION_TIME parameter value for exception queues.
//
24074, 00000, "RETRY_DELAY and MAX_RETRIES cannot be used for exception queue %.%s"
// *Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero
// RETRY_DELAY and an exception queue.
// *Action: Do not specify RETRY_DELAY or MAX_RETRIES for exception queues.
24075, 00000, "cannot specify agent with NULL address and non-NULL protocol"
// *Cause: An ADD_SUBSCRIBER or enqueue was attemoted with an agent that had
// a NULL address and a non-NULL protocol.
// *Action: Either specify a non-NULL address or set the protocol to NULL.
//
24076, 00000, "cannot perform operation %s for NON_PERSISTENT queue %s.%s"
// *Cause: One of the operations, SCHEDULE_PROPAGATION, ALTER_QUEUE, LISTEN,
// DEQUEUE was issued for a NON_PERSISTENT queue.
// *Action: Do not specify a NON_PERSISTENT queue for these operations.
//
24077, 00000, "cannot create propagation schedule for EXCEPTION queue %s.%s"
// *Cause: A SCHEDULE_PROPAGATION was issued for an EXCEPTION queue.
// Propagation schedules can be created only for NORMAL queues.
// *Action: To propagate messages from a queue specify the queue type
// as NORMAL.
//
24078, 00000, "cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL"
// *Cause: A non-NULL value was specified for SECONDARY_INSTANCE when
// PRIMARY_INSTANCE was NULL.
// *Action: Specify a non-NULL primary instance before you specify a non-NULL
// secondary instance.
24079, 00000, "invalid name %s, names with AQ$_ prefix are not valid for %s"
// *Cause: An attempt was made to use a reserved prefix for the object name.
// *Action: Enter a different name for this object. Then, retry the operation.
24080, 00000, "unschedule_propagation pending for QUEUE %s and DESTINATION %s"
// *Cause: A propagation administration command was issued for a queue and
// destination pair whose propagation is being unscheduled.
// *Action: Do not issue propagation administration commands for a propagation
// schedule on which there is a pending unschedule request.
24081, 00000, "compatible parameter needs to be %s or greater"
// *Cause: The compatible parameter was not high enough to allow the operation.
// *Action: Shutdown and restart with a higher compatibility setting.
24082, 00000, "propagation may still be happening for the schedule for QUEUE %s and DESTINATION %s"
// *Cause: The snapshot process executing the propagation schedule did not
// respond to the disable propagation command.
// *Action: Make sure that the job for the propagation schedule has been
// ended.
24083, 00000, "cannot specify remote subscribers for %s QUEUE %s "
// *Cause: An add_subscriber call with a non-null address field was issued on a
// queue which does not support remote subscribers. Remote subscribers
// are not supported for NON_PERSISTENT QUEUES.
// *Action: Specify a null address field and retry the call.
24084, 00000, "DBLINK name in address field of agent %s is not unique within the first 24 bytes"
// *Cause: Advanced Queuing requires that the agent's dblink name should
// be unique within the first 24 bytes (for 8.0 compatible
// queuetables)
// *Action: Specify a dblink name that is unique within the first 24
// bytes or migrate to 8.1 compatible queuetables where this
// restriction is not there.
24085, 00000, "operation failed, queue %s is invalid"
// *Cause: An attempt was made to enqueue, dequeue or administer a queue which is invalid.
// This could have occured because the payload type of the queue's queue table was
// dropped or rules associated with queue subscribers got altered or dropped.
// *Action: Drop the queue table setting the force option to true.
24086, 00000, "cannot create a 8.0 compatible %s queue"
// *Cause: An attempt was made to create a 8.0 compatible queue table and
// enable a feature that is supported only on 8.1 style queue tables
// *Action: This feature is not supported
24087, 00000, "Invalid database user %s "
// *Cause: An invalid database username was specified
// *Action: Specify a valid database user
//
24088, 00000, "AQ Agent %s does not exist"
// *Cause: This AQ Agent does not exist
// *Action: Specify a valid AQ agent. Check the DBA_AQ_AGENTS view
// for a list of valid aq agents
//
24089, 00000, "AQ Agent %s already exists"
// *Cause: This AQ agent has already been created
// *Action: Specify another agent name or use the ALTER api to modify the agent
// information.
//
24090, 00000, "at least one protocol must be enabled"
// *Cause: No protocol was enabled for aq agent
// *Action: Enable one of the protocols by setting one of the enable
// parameters to true.
//
24091, 00000, "Destination queue %s is the same as the source queue"
// *Cause: Propagation cannot be scheduled when the destination queue is the
// same as the source queue.
// *Action: Specify a different destination queue.
24092, 00000, "invalid value %s specified"
// *Cause: A queue, queue table, rule, or ruleset name that requires double
// quotes was specifed when the database compatibility was less
// than 10.0.
// *Action: Specify a value that does not require double quotes and
// retry the operation.
/
24093, 00000, "AQ agent %s not granted privileges of database user %s"
// *Cause: The specified AQ agent does not have privileges of the
// specified database user
// *Action: Specify a valid combination of AQ agent and database user. Check
// the DBA_AQ_AGENT_PRIVS or USER_AQ_AGENT_PRIVS view for user/agent
// mappings
//
24094, 00000, "invalid transformation, target type does not match that of the queue"
// *Cause: The target type of the transformation specified was different
// from the type of the queue.
// *Action: Provide a valid transformation whose target type is the same
// as the queue type.
24095, 00000, "invalid transformation, source type does not match that of the queue"
// *Cause: The source type of the transformation specified was different
// from the type of the queue.
// *Action: Provide valid transformation whose source type is the same
// as the queue type.
24096, 00000, "invalid message state specified"
// *Cause: Invalid value is specified for message state
// *Action: Provide a valid message state as specified in the documentation
24097, 00000, "Invalid value %s, %s should be non-negative"
// *Cause: A negative value or NULL was specified for the parameter.
// *Action: Specify a non negative integer.
24098, 00000, "invalid value %s for %s"
// *Cause: An Invalid value or NULL was specified for the parameter.
// *Action: Check the documentation for valid values.
24099, 00000, "operation not allowed for 8.0 compatible queues"
// *Cause: The specified operation is only supported for queues with
// compatibility 8.1 or greater
// *Action: Upgrade the 8.0 compatible queue to release 8.1 using
// DBMS_AQADM.MIGRATE_QUEUE_TABLE or specify a queue with
// compatibility 8.1
/
/ 24100 - ERROR MESSAGE FOR THE TRANSACTION LAYER
/
24100, 00000, "error in ktz testing layer"
// *Cause: There is an error in the Transaction layer test ICDs
//
// *Action:
//
/ 24101 - 24119 ERROR MESSAGES FOR THE DBMS_SCHEDULER PACKAGE
/
24101, 00000, "stopped processing the argument list at: %s"
// *Cause: One of the arguments of the requested operation contained a list of
// scheduler objects. While processing this list an error was
// encountered with the specified item.
// *Action: Resolve the error for this element of the list and then re-issue
// the command with the remainder of the argument list. See the rest
// of the error stack to find out what the exact error is.
24102, 00000, "invalid prefix for generate_job_name"
// *Cause: generate_job_name was called with a prefix longer than 18 characters
// or a prefix ending in a digit.
// *Action: Re-issue the command using a prefix no longer than 18 characters
// and not ending in a digit.
24103, 00000, "job \"%s\".\"%s\" failed to be enabled after creation"
// *Cause: The job failed to be enabled after creation.
// *Action: Review the reason for the failure, correct it if possible
// and re-create the job.
/
/ 24120 - 24140 ERROR MESSAGES FOR THE DBMS_REPAIR PACKAGE
/
24120, 00000, "invalid %s parameter passed to DBMS_REPAIR.%s procedure"
// *Cause: An invalid parameter was passed to the specified DBMS_REPAIR
// procedure.
// *Action: Specify a valid parameter value or use the parameter's default.
//
24121, 00000, "both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure"
// *Cause: Both cascade and a block range were specified in a call to
// DBMS_REPAIR.CHECK_OBJECT.
// *Action: Use either cascade or a block range, or do not use either one.
//
24122, 00000, "invalid block range specification"
// *Cause: An incorrect block range was specified.
// *Action: Specify correct values for the BLOCK_START and BLOCK_END
// parameters.
//
24123, 00000, "feature %s is not yet implemented"
// *Cause: An attempt was made to use the specified feature, but the feature is
// not yet implemented.
// *Action: Do not attempt to use the feature.
//
24124, 00000, "invalid ACTION parameter passed to DBMS_REPAIR.%s procedure"
// *Cause: An invalid ACTION parameter was specified.
// *Action: Specify CREATE_ACTION, PURGE_ACTION or DROP_ACTION for the ACTION
// parameter.
//
24125, 00000, "Object %s.%s has changed"
// *Cause An attempt was made to fix corrupt blocks on an object that
// has been dropped or truncated since DBMS_REPAIR.CHECK_OBJECT was run.
// *Action Use DBMS_REPAIR.ADMIN_TABLES to purge the repair table
// and run DBMS_REPAIR.CHECK_OBJECT to determine whether there are
// any corrupt blocks to be fixed.
24126, 00000, "invalid CASCADE_FLAG passed to DBMS_REPAIR.%s procedure"
// *Cause: CASCADE_FLAG was specified for an object that is not a table.
// *Action: Use CASCADE_FLAG only for tables.
//
24127, 00000, "TABLESPACE parameter specified with an ACTION other than CREATE_ACTION"
// *Cause: The TABLESPACE parameter can only be used with CREATE_ACTION.
// *Action: Do not specify TABLESPACE when performing actions other than
// CREATE_ACTION.
//
24128, 00000, "partition name specified for a non-partitioned object"
// *Cause: A partition name was specified for an object that is not
// partitioned.
// *Action: Specify a partition name only if the object is partitioned.
//
24129, 00000, "table name %s does not start with %s prefix"
// *Cause: An attempt was made to pass a table name parameter without the
// specified prefix.
// *Action: Pass a valid table name parameter.
//
24130, 00000, "table %s does not exist"
// *Cause: An attempt was made to specify a map, repair, or sync table that
// does not exist.
// *Action: Specify a valid table name parameter.
//
24131, 00000, "table %s has incorrect columns"
// *Cause: An attempt was made to specify a map, repair, or sync table that
// does not have a correct definition.
// *Action: Specify a table name that refers to a properly created table.
//
24132, 00000, "table name %s is too long"
// *Cause: An attempt was made to specify a table name is greater than 30
// characters long"
// *Action: Specify a valid table name parameter.
//
24133, 00000, "invalid usage of DBMS_REPAIR in case of GTT table"
// *Cause: An attempt was made to specify a Global Temporary Table (GTT)
// table name while using DBMS_REPAIR.CHECK_OBJECT.
// *Action: Specify a non-GTT table name parameter.
//
/
/ 24141 - 24179 ERROR MESSAGES FOR THE DBMS_RULE PACKAGE
/
24141, 00000, "rule set %s.%s does not exist"
// *Cause: An attempt to access or modify a ruleset was made, which failed
// because the ruleset does not exist.
// *Action: Only access or modify existing rulesets.
24142, 00000, "invalid ruleset name"
// *Cause: An attempt to create a ruleset with an invalid name was made.
// The ruleset name can not be NULL, and can not be more
// than 26 characters, unless a rules_table_name is also specified,
// in which case the ruleset name may be up to 30 characters.
// *Action: Retry the create with a valid ruleset name.
24143, 00000, "invalid evaluation context name"
// *Cause: An attempt to create a rule/ruleset on an invalid evaluation name
// was made. The evaluation_context can not be more than 30
// characters. The evaluation context with the name specified must
// exist.
// *Action: Retry the create with a valid evaluation context name.
24144, 00000, "rules engine internal error, arguments: [%s], [%s] "
// *Cause: An internal error occurred in the rules engine. This indicates
// that the rules engine has encountered an exception condition.
// *Action: Please report this error as a bug. The first argument is the
// error and the second argument is the package.
24145, 00000, "evaluation context %s.%s already exists"
// *Cause: An evaluation context of the given name already exists
// *Action: Specify another name for the evaluation context being created
24146, 00000, "rule %s.%s already exists "
// *Cause: A rule of the given name already exists
// *Action: Specify another name for the rule being created.
24147, 00000, "rule %s.%s does not exist "
// *Cause: The rule of the given name does not exist
// *Action: create the rule or specify one that exists
24148, 00000, "cannot drop rule %s.%s with dependents"
// *Cause: The rule still belongs to some rulesets, cannot be dropped
// *Action: do not drop a rule that belongs to rulesets without force option
24149, 00000, "invalid rule name"
// *Cause: An attempt to create a rule with an invalid name was made.
// The rule name can not be NULL, and can not be more
// than 30 characters
24150, 00000, "evaluation context %s.%s does not exist"
// *Cause: The evaluation context of the given name does not exist
// *Action: create the evaluation context or specify one that exists
24151, 00000, "no evaluation context is associated with rule %s.%s or rule set %s.%s"
// *Cause: Whening adding a rule to a rule set, either the rule or the rule
// set must have an evaluation context associated with it
// *Action: do not add a rule without an evaluation context to a ruleset that
// does not have a default evaluation context
24152, 00000, "cannot drop evaluation context %s.%s with dependents"
// *Cause: The evaluation context still belongs to some rules or rule sets,
// cannot be dropped
// *Action: do not drop an evaluation context with dependents without force
// option
24153, 00000, "rule set %s.%s already exists "
// *Cause: A rule set of the given name already exists
// *Action: Specify another name for the rule set being created.
24154, 00000, "rule %s.%s already in rule set %s.%s"
// *Cause: a rule can be added to a rule set only once
// *Action: do not add a rule to a rule set that already contains this rule
24155, 00000, "rule %s.%s not in rule set %s.%s"
// *Cause: the rule to be removed from the rule set is not in the rule set
// *Action: do not remove a rule from a rule set that does not contain the rule
24156, 00000, "duplicate table alias %s"
// *Cause: there is a table alias of the same name in the evaluation context
// *Action: do not add two table aliases of the same name to an evaluation
// context
24157, 00000, "duplicate variable name %s"
// *Cause: there is a variable of the same name in the evaluation context
// *Action: do not add two variables of the same name to an evaluation
// context
24158, 00000, "invalid table alias"
// *Cause: table alias name or base table name is not specified in the table
// alias definiton
// *Action: specify both alias name and alias base table in the table alias
// structure
24159, 00000, "invalid variable definiton"
// *Cause: variable name or variable type is not specified in the variable
// definiton
// *Action: specify both variable name and variable type in the variable
// definition structure
24160, 00000, "name %s already exists in the name value pair list"
// *Cause: there is already a name-value pair with the same name in the NVlist
// *Action: try another name.
24161, 00000, "name %s does not exist in the name value pair list"
// *Cause: there is not such a name-value pair in the NVlist
// *Action: check the name-value pair exists in the NVList.
24162, 00000, "name value pair list is full, cannot add another entry"
// *Cause: The NVList is full (1024 elements) and cannot hold more elements
// *Action: do not add elements to a full list.
24163, 00000, "dblink is not supported in rules engine DDLs"
// *Cause: the object name has a database link in it, which is not supported
// *Action: Do not specify remote objects in rules engine DDLs.
24164, 00000, "invalid rule engine system privilege: %s"
// *Cause: no such system privilege number for rule engine objects
// *Action: check specfication of dbms_rule_adm for valid system privilege
// numbers
24165, 00000, "invalid rule engine object privilege: %s"
// *Cause: no such object privilege number for rule engine objects
// *Action: check specfication of dbms_rule_adm for valid object privilege
// numbers
24166, 00000, "evaluation context %s.%s has errors"
// *Cause: The table aliases and the variable types specified in the
// evaluation context could not be resolved.
// *Action: Make sure that all base tables exist and that all variable types
// are correct. Also, make sure that tables are not composite
// partitioned or clustered partitioned.
24167, 00000, "incompatible rule engine objects, cannot downgrade"
// *Cause: there are rule engine objects in the database that cannot be
// downgraded.
// *Action: check utlincmp.sql and remove all incompatible rules engine objects
// before downgrade.
24168, 00000, "rule %s.%s cannot have default evaluation context"
// *Cause: If a rule is added to a rule set with more than one evaluation
// contexts, it must not have an evaluation context itself.
// *Action: Do not set the evaluation context of such rules to a not-null
// value
24169, 00000, "rule condition has unrecognized variables"
// *Cause: The rule references variables not in the evaluation context.
// *Action: Modify the rule condition to remove illegal reference.
24170, 00000, "%s.%s is created by AQ, cannot be dropped directly"
// *Cause: This object is created by AQ, thus cannot be dropped directly
// *Action: use dbms_aqadm.drop_subscriber to drop the object
24171, 00000, "creation properties are only for internal use"
// *Cause: user specified not null creation properties when creating rules
// engine objects, which are not for external use
// *Action: do not set creation properties when creating rules engine objects
24172, 00000, "rule set %s.%s has errors"
// *Cause: The rule references variables not in the evaluation context.
// *Action: Modify the rule condition to remove illegal reference.
24173, 00000, "nested query not supported for rule condition"
// *Cause: user specified nested query in rule condition.
// *Action: do not use nested query in rule condition.
24174, 00000, "The number of %s per evaluation context is more than %s"
// *Cause: Number of tables or variables were more than the defined
// upper limit.
// *Action: Reduce the number of tables or variables per evaluation context.
24175, 00000, "The number of %s exceeds limit %s as there exists at least one nonsimple rule condition"
// *Cause: Upper limit of tables or variable per evaluation context exceeded
// as there exists at least one nonsimple rule condition.
// *Action: Reduce the number of tables or variables per evaluation context.
/
/
/ 24180 - 242200 ERROR MESSAGES FOR THE DBMS_TRANSFORM PACKAGE
/
24180, 00000, "invalid transformation expression, the transformation expression does not evaluate to the target type/attribute "
// *Cause: The transformation expression does not evaluate to the target type
// or the target type's specified attribute.
// *Action: Provide valid transformation expression which evaluates to the
// target type or the target type's specified attribute.
24181, 00000, "The type %s does not exist "
// *Cause: The source or destination type for the transformation does not exist
// *Action: Create the type or specify one that exists
24182, 00000, "attribute number specified does not exist "
// *Cause: The target type of the transformation does not have the attribute
// number specified in the ADD_ATTRIBUTE_TRANSFORMATION command
// *Action: check the target type definition and specify a valid attribute
// number
24183, 00000, "invalid transformation"
// *Cause: The transformation specified is invalid because the source or
// the target type have been dropped/modified.
// *Action: Drop and recreate the transformation
//
24184, 00000, "transformation %s.%s already exists "
// *Cause: The named transformation already exists.
// *Action: Specify another name for the transformation being created.
24185, 00000, "transformation %s.%s does not exist"
// *Cause: The specified transformation does not exist.
// *Action: Create the transformation before using it or specify an existing
// transformation.
24186, 00000, "wrong object type, could not transform message"
// *Cause: The object type of the message to be transformed does not match
// the source type of the specified transfomation.
// *Action: Specify another transformation, or specify a message of the
// correct type.
/
/ 24190 - 24199 ERROR MESSAGES FOR AQ JMS
/
24190, 00000, "length of payload exceeds %s"
// *Cause: the length of payload being taken exceeds the limit of varchar2 or raw.
// *Action: use clob type or blob type to call get_text or get_bytes.
24191, 00000, "the property name %s has existed"
// *Cause: the property name being set has existed.
// *Action: use another property name.
24192, 00000, "the property name cannot be null"
// *Cause: the property name cannot be null.
// *Action: make sure the property name not null.
24193, 00000, "the property value exceeds the valid range %s"
// *Cause: the property valus being set exceeds the valid range.
// *Action: make sure the property value is within the valid range.
24194, 00000, "attempt to read data in a message as the wrong type"
// *Cause: According to JMS specification, some type conversions were not allowed.
// *Action: Make sure to use the correct READ function to retrieve message data.
24195, 00000, "attemp to retrieve the name list of a map message with size exceeding 1024"
// *Cause: The GET_NAMES function returns the names in a varray with a size limit of 1024.
// *Action: Retrieve in several smaller steps using the GET_NAMES function with OFFSET and LENGTH parameters.
24196, 00000, "access the message in a wrong access mode"
// *Cause: StreamMessage and BytesMessage could not be read when they were in write only mode and vice versa.
// *Action: Change the access mode using PREPARE, CLEAR_BODY and RESET procedures.
24197, 00000, "JAVA stored procedure throws JAVA exceptions"
// *Cause: The JAVA stored procedure threw some exceptions that could not be catergorized.
// *Action: Use GET_EXCEPTION procedure to see what the exception is about.
24198, 00000, "attempt to use an invalid operation ID"
// *Cause: An attempt was made to use an invalid operation ID to access messages.
// *Action: Use the correct operation ID returned by PREPARE or CLEAR_BODY procedure.
24199, 00000, "message store is overflow"
// *Cause: An attemp was made to access too many messages at the same time.
// *Action: Use the CLEAN procedure to clean up some of the messages.
/
/ 24200 - 24229 ERROR MESSAGES FOR THE DBMS_AQADM PACKAGE
/
24201, 00000, "duplicate publisher, publisher already added to the queue"
// *Cause: Attempted to add a publisher to the queue again.
// *Action: Specify another publisher or user DBMS_AQADM.ALTER_PUBLISHER
// to alter the publisher's properties.
24202, 00000, "publisher does not exist for the queue"
// *Cause: Attempted to alter or drop a non existent publisher from a queue.
// *Action: Specify another publisher.
//
24203, 00000, "operation failed, queue table %s.%s has errors"
// *Cause: An operation attempt was made to a queue table which has errors.
// *Action: Drop the queue table setting the force option to true.
//
24204, 00000, "existing %s propagation schedules"
// *Cause: A propagation administrative interface was called when the
// existing propagation schedules were running in different
// mode (10.2/11g).
// *Action: Set appropriate internal parameter and unschedule existing
// schedules if required.
/
24205, 00000, "feature %s not supported for sharded queues"
// *Cause: An attempt was made to use a feature that is not supported for
// sharded queues.
// *Action: Specify only supported features and try again.
/
24206, 00000, "maximum limit of %s nondurable subscribers reached for queue %s.%s"
// *Cause: An attempt to add a new nondurable subscriber to the
// queue failed because the number of nondurable subscribers has
// exceeded the maximum limit.
// *Action: Remove existing subscribers and then attempt to add a new subscriber.
/
24207, 00000, "addition of a nondurable subscriber for queue %s.%s aborted due to low SGA"
// *Cause: An attempt to add a new nondurable subscriber on the
// specified queue was aborted because of memory constraints.
// *Action: Increase the shared pool size by increasing the value of the
// SHARED_POOL_SIZE parameter.
/
24208, 00000, "API not supported for non-sharded queues"
// *Cause: An attempt was made to use a sharded queue API on a
// non-sharded queue.
// *Action: Use non-sharded queue APIs.
/
24209, 00000, "nondurable subscriber rule has errors for queue %s"
// *Cause: An attempt was made to create a nondurable subscriber with a
// rule condition, but the condition had compilation errors.
// *Action: Correct the condition statement based on the error stack.
//
24210, 00000, "attempt to %s %s on queue %s.%s, %s already %s"
// *Cause: An attempt was made to start or stop a queue operation on a queue
// which is already enabled or disabled for that operation.
// *Action: Make only one attempt to start or stop the queue operation.
//
24211, 00000, "invalid value for REPLICATION_MODE"
// *Cause: There was an invalid setting of REPLICATION_MODE in the queue
// creation call.
// *Action: Specify a valid setting. DBMS_AQADM.REPLICATION_MODE or
// DBMA_AQADM.NONE are the valid options.
24212, 00000, "user operation not permitted on replicated queue %s.%s"
//*Cause: An attempt was made to run a user operation on a
// replicated queue.
//*Action: Disable replication on the queue before performing
// user operations.
24213, 00000, "unable to replicate queue %s.%s for sub-shards %d, %d"
//*Cause: An attempt to replicate enqueue failed.
//*Action: Look for information in the session trace file and contact
// Oracle Support Services.
24214, 00000, "unable to replicate queue %s.%s sequence %d, maximum sequence %d failed"
//*Cause: An attempt to replicate enqueue failed.
//*Action: Look for information in the session trace file and contact
// Oracle Support Services.
24215, 00000, "unable to modify REPLICATION_MODE, queue has to be stopped"
//*Cause: An attempt was made to modify REPLICATION_MODE on a queue open to
// user operations.
//*Action: Stop the queue first using the STOP_QUEUE command.
// Oracle Support Services.
24216, 00000, "%s not a supported payload type in sharded queue"
//*Cause: An attempt was made to create a sharded queue with an ADT type which was not
// supported in the queue_payload_type.
//*Action: Use DBMS_AQADM.JMS_TYPE as the queue_payload_type.
/
/ 24230 - 24264 ERROR MESSAGES FOR MISC DBMS_ PACKAGES
/
24230, 00000, "input to DBMS_DDL.WRAP is not a legal PL/SQL unit"
// *Cause: The input supplied to DBMS_DDL.WRAP or DBMS_DDL.CREATE_WRAPPED
// did not specify a legal PL/SQL package specification,
// package body, type specification, type body, function or
// procedure. This error can occur if you used incorrect
// syntax in the CREATE OR REPLACE statement or specified
// a unit that cannot be wrapped (e.g., a trigger or anonymous
// block).
// *Action: Provide a legal PL/SQL unit as input.
//
24231, 00000, "database access descriptor (DAD) %s not found"
// *Cause: The specified Database Access Descriptor (DAD) did not exist.
// *Action: Make sure the name of the Database Access Descriptor (DAD) is
// correct and the DAD exists.
//
24232, 00000, "unknown Embedded PL/SQL Gateway attribute %s"
// *Cause: The specified Embedded PL/SQL Gateway attribute was not known.
// *Action: Make sure the name of the Embedded PL/SQL Gateway attribute is
// correct.
//
24233, 00000, "argument passed to DBMS_UTILITY.VALIDATE is not legal"
// *Cause: One or more input arguments to the DBMS_UTILITY.VALIDATE
// routine was not legal. This error occurred because the
// object name or owner or namespace arguments (if specified)
// were NULL or illegal.
// *Action: Identify and correct the illegal argument.
/
24234, 00000, "unable to get source of %s \"%s\".\"%s\", insufficient privileges or does not exist"
// *Cause: The specified PL/SQL object in a DBMS_PREPROCESSOR subprogram
// did not exist or you did not have the privileges necessary to
// view its source.
// *Action: Make sure the specified object exists and you have the
// privileges necessary to view its source.
/
24235, 00000, "bad value for object type: %s"
// *Cause: The specified object type was not appropriate.
// *Action: Make sure the specified object type is one of the following:
// package, package body, procedure, function, trigger, type,
// and type body.
/
24236, 00000, "source text is empty"
// *Cause: The input source text supplied to a DBMS_PREPROCESSOR
// subprogram was empty.
// *Action: Pass a non-empty input source text as the input.
/
24237, 00000, "object id argument passed to DBMS_UTILITY.INVALIDATE is not legal"
// *Cause: This error occurred because the p_object_id argument passed to
// the DBMS_UTILITY.INVALIDATE routine was NULL, there was no
// object with the specified object id, or the user calling the
// routine did not have sufficient privileges to invalidate the
// object.
// *Action: Correct the illegal argument.
/
24238, 00000, "object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal"
// *Cause: This error occurred because the p_plsql_object_settings argument
// passed to the DBMS_UTILITY.INVALIDATE routine was NULL or
// malformed.
// *Action: Correct the illegal argument.
/
24239, 00000, "object could not be invalidated"
// *Cause: A call to the DBMS_UTILITY.INVALIDATE routine failed. This error
// occurred because the object type of the object specified by the
// p_object_id argument is not one of the types that can be handled
// by this routine. Alternately, the object was an object type
// specification with table dependents, or the object was the
// specification of the STANDARD, DBMS_STANDARD, DBMS_UTILITY
// package, or the body of the DBMS_UTILITY package.
// *Action: Call DBMS_UTILITY.INVALIDATE only on supported object types.
/
24240, 00000, "invalid database access descriptor (DAD) name"
// *Cause: The specified Database Access Descriptor (DAD) name was invalid.
// *Action: Make sure the name of the Database Access Descriptor (DAD) is
// valid and its length does not exceed its limit.
/
24241, 00000, "source text is in wrapped format"
// *Cause: The input source text supplied to a DBMS_PREPROCESSOR
// subprogram was in wrapped format.
// *Action: Pass a nonwrapped source text as the input.
//
/
24242, 00000, "anonymous access through a dynamically authenticated Database Access Descriptor (DAD) prohibited"
// *Cause: An attempt to allow anonymous access through a dynamically
// authenticated Database Access Descriptor (DAD) was prohibited.
// *Action: Make sure the Database Access Descriptor (DAD) is not dynamically
// authenticated before allowing anonymous access through it.
/
24243, 00000, "access control entry (ACE) already exists"
// *Cause: An access control entry (ACE) for the principal with the same
// grant or deny attribute in the IS_GRANT argument already existed.
// *Action: Add the privilege to the existing access control entry (ACE)
// instead.
/
24244, 00000, "invalid host or port for access control list (ACL) assignment"
// *Cause: The host or port to which the access control list (ACL) was
// assigned was invalid.
// *Action: Ensure the host and port to which you are assigning the access
// control list (ACL) are valid.
/
24245, 00000, "invalid network privilege"
// *Cause: The network privilege being added to the access control list
// (ACL) was invalid.
// *Action: Ensure the network privilege that you are adding to the access
// control list (ACL) is valid.
/
24246, 00000, "empty access control list (ACL) not allowed"
// *Cause: An attempt was made to store an empty access control list (ACL).
// *Action: Ensure that the access control list (ACL) has at least one
/ privilege assignment.
/
24247, 00000, "network access denied by access control list (ACL)"
// *Cause: No access control list (ACL) has been assigned to the target
// host or the privilege necessary to access the target host has not
// been granted to the user in the access control list.
// *Action: Ensure that an access control list (ACL) has been assigned to
// the target host and the privilege necessary to access the target
// host has been granted to the user.
/
24248, 00000, "XML DB extensible security not installed"
// *Cause: XML DB extensible security necessary for this operation has
// not been installed.
// *Action: Ensure that XML DB has been installed.
/
24249, 00000, "Authentication scheme \"%s\" not supported"
// *Cause: An unsupported authentication scheme was used.
// *Action: Retry with a supported authentication scheme.
/
24250, 00000, "No supported authentication scheme found"
// *Cause: A supported authentication scheme was not found.
// *Action: Retry with a supported authentication scheme.
/
24251, 00000, "This statement is not supported by EXPAND_SQL_TEXT."
// *Cause: EXPAND_SQL_TEXT supports only SELECT statements.
// *Action: Submit only a SELECT statement.
/
24252, 00000, "SQL translation profile does not exist"
// *Cause: An attempt was made to access a SQL translation profile that
// either did not exist or for which the current user did not have
// privileges on.
// *Action: Check the SQL translation profile name and verify that the
// current user has appropriate privileges on the SQL translation
// profile.
/
24253, 00000, "translation of SQL statement or error code not found"
// *Cause: An attempt to translate a SQL statement or error code or to change
// a SQL or error code translation failed because the translation was
// not found.
// *Action: Verify that the SQL statement or error code is valid and
// either a custom translation is registered or the translator
// package in the SQL translation profile can translate it.
/
24254, 00000, "appropriate SQL translation profile not set"
// *Cause: An attempt to translate a SQL statement or error code failed
// because either a SQL translation profile was not set or the
// profile could not translate the given SQL syntax.
// *Action: Set an appropriate SQL translation profile before attempting to
// translate a SQL statement or error code.
/
24255, 00000, "Implementation restriction: bind variables cannot change in the translated SQL statement"
// *Cause: An attempt to register or use a translated SQL statement failed
// because the number or the order of bind variables were changed
// in the statement.
// *Action: Do not change the number or the order of bind variables in the
// translated SQL statement.
/
24256, 00000, "EXPAND_SQL_TEXT failed with %s"
// *Cause: See the string parameter at the end of the message.
// *Action: See the string parameter at the end of the message and take
// corrective action.
/
24257, 00000, "The database role should be a primary or physical standby database."
// *Cause: The database role was not a primary database or a physical standby
// database.
// *Action: Check the database role and try this command again.
/
24258, 00000, "unable to create output file or file already exists"
// *Cause: Either a file with the same name as the specified output file
// name already exists, or file creation failed.
// *Action: Fix the incorrect output file name and try this command again.
/
24259, 00000, "Slave process or processes for this PL/SQL function terminated abnormally, or could not be created or initialized."
// *Cause: Slave process or processes failed to operate properly for one of
// the following reasons:
// - Inadequate SGA size.
// - Slave pool could not be initialized.
// - Slave process or processes were abnormally terminated.
// *Action: Ensure that the SGA size is sufficient to call this PL/SQL
// function.
/
24260, 00000, "unable to communicate with remote databases"
// *Cause: Remote database or databases were not available due to network
// connection failures.
// *Action: Check the status of the network and ensure that the database or
// databases are mounted or open.
/
24261, 00000, "unable to read data file correctly on the remote database"
// *Cause: The remote database was unable to read the data file.
// *Action: Check the status of the data file.
/
24262, 00000, "unable to read data file correctly on the local database"
// *Cause: The data file on the local database could not be accessed.
// *Action: Check the status of the data file.
/
24263, 00000, "Certificate of the remote server does not match the target address."
// *Cause: The server address on the public key certificate of the remote
// server did not match the address used to access the target server.
// *Action: Verify the identity of the remote server against fraudulent servers.
// If the identity of the remote server is valid, access the server
// again while providing the expected address to be matched against
// the certificate of the remote server.
/
24264, 00000, "The data file %s is not in the current container."
// *Cause: An attempt was made to access the data file outside of the current
// container.
// *Action: Check the current container and change it to root or a specific
// container that is able to access this data file.
/
/ 24265 - 24269 ERROR MESSAGES FOR THE DBMS_SQLTUNE PACKAGE
/
24265, 00000, "Insufficient privileges for SQL profile operation"
// *Cause: A DDL operation was attempted on a SQL profile by a session without
// the proper privileges.
// *Action: Grant the user the appropriate privilege.
/
/ 24270 - 24279 ERROR MESSAGES FOR THE DBMS_HS SUPPORT PACKAGE
/
24270, 00000, "a row already exists in the %s table for these parameters"
// *Cause: A call was made to create a new row in the specified table.
// A row already exists in the table with the specified values.
//
// *Action: Delete the existing row using the appropriate API or check
// the parameters used to create the row.
//
24271, 00000, "translation type must be either T, S or M"
// *Cause: The translation type parameter is not a T, S or an M. A value
// other than T, S or M was specified.
//
// *Action: Correct the translation type and reexecute the API call.
//
24272, 00000, "initialization value must be either F or T"
// *Cause: The initialization value must be either F or T. A value
// other than F or T was specified.
//
// *Action: Correct the initialization value and reexecute the API call.
//
24273, 00000, "translation text is required if translation type is T or S"
// *Cause: If a translation type of T or S is specified, translation text
// must be supplied.
//
// *Action: Provide translation text and reexecute the API call.
//
24274, 00000, "no row exists in the %s table for these parameters"
// *Cause: A call was made to update a row that does not exist or
// a foreign key value supplied to create a table does
// not exist.
//
// *Action: Create the row using the appropriate API or check
// the parameters used to create the new row to ensure that
// all specified values exist.
//
24275, 00000, "function '%s' parameter '%s' missing or invalid"
// *Cause: The function <pkgname.funcname> was called with a parameter
// <parmname> that was null, 0 length, or had an invalid value.
// *Action: Correct the parameter to supply values that comply with
// its datatype and limits as specified in the documentation.
//
24276, 00000, "function '%s' output '%s' maximum value exceeded"
// *Cause: The function <pkgname.funcname> computed a value for the
// output <parmname> that exceeded the maximum allowed.
// This can occur when multiple input parameters, each valid
// separately, combine to specify an invalid result.
// For example, when a length parameter multiplied by a copies
// parameter yields a total length exceeding the maximum for
// the output datatype.
// *Action: Correct the input values to produce a result that will
// comply with the limits as specified in the documentation.
24277, 00000, "invalid database link %s "
// *Cause: The database link did not exist.
// *Action: Make sure the database link name is correct.
24278, 00000, "remote table %s not found "
// *Cause: The table did not exist in the remote database.
// *Action: Make sure the remote table name is correct.
24279, 00000, "view %s is not a parallel access view"
// *Cause: The view was not created by CREATE_OR_REPLACE_VIEW API.
// *Action: Provide the correct view name that was created by CREATE_OR_REPLACE_VIEW API.
/
/
/
/ 24280 -24290 Reserved for DBMS_LOB (FILE) package
/
/
24280, 00000, "invalid input value for parameter %s"
// *Cause: The parameter has been provided a negative, out of range, or
// NULL input value.
// *Action: Correct the input value such that it is valid, and is within
// the range as specified in the documentation.
/
24281, 00000, "invalid access past the maximum size of LOB parameter %s"
// *Cause: The value of positional or size parameters exceeded the maximum
// allowed LOB size of (4 Gigabytes - 1) * DB_BLOCK_SIZE.
// *Action: Correct the input values for amount and offset such that their
// sum is less than or equal to (4 Gigabytes - 1) * DB_BLOCK_SIZE.
// If an error occurs in a read or write loop, check the looping
// conditions and offset increments.
/
/ 24291 - 24299 Reserved for Sorted Hash Clusters
/
24291, 00000, "Sort Hash Cluster error %s"
// *Cause:
// *Action:
/
24292, 00000, "no more tables permitted in this sorted hash cluster"
// *Cause: A sorted hash cluster only supports a maximum of 2 tables
// *Action:
/
24295, 00000, "max key length (%s) for sorted hash cluster exceeded"
// *Cause: Sorted hash clusters have a maximum key size
// *Action:
/
24296, 00000, "error in processing the XML configuration file %s"
// *Cause: Parameters or their values were specified incorrectly in the
// configuration file.
// *Action: Check and correct the configuration parameters or their values.
/
/ 24300 - 24999 Reserved for OCI/UPI/TTC/OPI/RPI/PSDs etc
/
/ 24500 - 24549 Reserved for OCI codepoint length semantics and UTF16
/ 24550 - 24574 Reserved for OCI et al Diagnosability
/ 24750 - 24800 Reserved for Transaction OCI
/ 24800 - 24849 Reserved for OCI Lob/File related Calls
/ 24850 - 24874 Reserved for Shared OCI
/ 24900 - 24939 Reserved for OCI Notification
/ 24940 - 24949 Reserved for Generic Notification
/ 24950 - 24959 Reserved for PL/SQL Notification
/
24300, 00000, "bad value for mode"
// *Cause: An undefined mode value was specified.
// *Action: Check that the correct mode is selected and that an allowed
// value for that mode is specified.
/
24301, 00000, "null host specified in thread-safe logon"
// *Cause: An HDA was not specified in the logon call while running in a
// thread safe environment.
// *Action: Make sure that HDA is not NULL when calling the logon routine.
/
24302, 00000, "host connection in use by another thread"
// *Cause: An attempt was made to use the host connection while it was in use
// by another thread.
// *Action: Wait for another thread to finish before using this connection.
/
24303, 00000, "call not supported in non-deferred linkage"
// *Cause: One of the calls that is supported in deferred mode
// linkage exclusively was invoked when the client was linked
// non-deferred.
// *Action: Use this call in deferred mode of linkage.
/
24304, 00000, "datatype not allowed for this call"
// *Cause: Data of this datatype cannot be sent or fetched in pieces.
// *Action: Use other bind or define calls for this datatype.
/
24305, 00000, "bad bind or define context"
// *Cause: The call was executed on a cursor for which this is invalid.
// *Action: Verify that this call is valid for this cursor. For example, Get
// piece information and set piece information are valid on a cursor
// if appropriate binds and defines have been done on this cursor.
/
24306, 00000, "bad buffer for piece"
// *Cause: A zero length buffer or a null buffer pointer was provided.
// *Action: Verify that the buffer pointing to this piece or its length is
// non-zero. The buffer pointer for the next piece or its length
// can be zero if it is the last piece to be inserted and there are
// no more data for the column.
/
24307, 00000, "invalid length for piece"
// *Cause: The length of the piece exceeded the maximum possible size.
// *Action: Verify that the length of this piece and the cumulative length of
// all the previous pieces is not more than the desired value supplied
// by the application.
/
24308, 00000, "illegal define position"
// *Cause: Call to modify attributes was done for a non-existent position
// *Action: Verify that a define has been done for this position
/
24309, 00000, "already connected to a server"
// *Cause: This server handle is already attached to a server.
// *Action: Disconnect from the server and then retry the call to establish a
// connection.
/
24310, 00000, "length specified for null connect string"
// *Cause: The connect string is null, but a length was specified for it.
// *Action: Set length to zero if connect string is null.
/
24311, 00000, "memory initialization failed"
// *Cause: Cannot initialize user memory.
// *Action: Contact customer support.
/
24312, 00000, "illegal parameters specified for allocating user memory"
// *Cause: An illegal size or null pointer was specified for user memory.
// *Action: Specify a legal size and a valid pointer for user memory.
/
24313, 00000, "user already authenticated"
// *Cause: A user has already been authenticated on this service handle.
// *Action: Terminate the service context before using it for another user.
/
24314, 00000, "service handle not initialized"
// *Cause: The server context does not done exist.
// *Action: Establish the server context in the service context.
/
24315, 00000, "illegal attribute type"
// *Cause: An illegal attribute type was specified for the handle.
// *Action: Consult user manual to specify an attribute valid for this handle.
/
24316, 00000, "illegal handle type"
// *Cause: An illegal handle type was specified.
// *Action: Consult user manual to specify a valid handle type.
/
24317, 00000, "define handle used in a different position"
// *Cause: A define was done with an existing handle on a different position.
// *Action: Specify the same position as before on a re-define.
/
24318, 00000, "call not allowed for scalar data types"
// *Cause: This call is valid only for object types.
// *Action: Verify that the data-type for this variable is an object type
/
24319, 00000, "unable to allocate memory"
// *Cause: Process was unable to allocate memory to store diagnostics.
// *Action: Terminate other processes in order to reclaim needed memory.
24320, 00000, "unable to initialize a mutex"
// *Cause: An attempt to initialize a mutex failed.
// *Action: Contact customer support.
24321, 00000, "inconsistent parameters passed"
// *Cause: One of the three memory function pointers is null or non-null.
// *Action: Verify that either all the memory functions are null or non-null.
24322, 00000, "unable to delete an initialized mutex"
// *Cause: An attempt to delete an initialized mutex failed.
// *Action: Contact customer support.
24323, 00000, "value not allowed"
// *Cause: A null value or a bogus value was passed in for a mandatory
// parameter.
// *Action: Verify that all mandatory parameters are properly initialized.
24324, 00000, "service handle not initialized"
// *Cause: An attempt was made to use an improper service context handle.
// *Action: Verify that the service context handle has all the parameters
// initialized prior to this call.
24325, 00000, "this OCI operation is not currently allowed"
// *Cause: An attempt was made to use a context handle outside its scope.
// *Action: Verify that the context handle is set to a service context handle
// that has been converted to a logon data area for other OCI calls.
// The logon data area must be converted back to a service context
// before it can be used.
24326, 00000, "handle passed in is already initialized"
// *Cause: An attempt was made to pass an initialized handle.
// *Action: Verify that the parameter passed in to retrieve a handle does
// not already point to a handle.
24327, 00000, "need explicit attach before authenticating a user"
// *Cause: A server context must be initialized before creating a session.
// *Action: Create and initialize a server handle.
24328, 00000, "illegal attribute value"
// *Cause: The attribute value passed in is illegal.
// *Action: Consult the users manual and specify a legal attribute value
// for the handle.
24329, 00000, "invalid character set identifier"
// *Cause: The character set identifier specifed is invalid
// *Action: Specify a valid character set identifier in the OCI call.
/
24330, 00000, "internal OCI error"
// *Cause: An internal OCI error has occurred.
// *Action: Please contact Oracle customer support.
24331, 00000, "user buffer too small"
// *Cause: The user buffer to contain the output data is too small.
// *Action: Specify a bigger buffer.
24332, 00000, "invalid object type"
// *Cause: An invalid object type is requested for the describe call.
// *Action: Specify a valid object type to the describe call.
/
24333, 00000, "zero iteration count"
// *Cause: An iteration count of zero was specified for the statement
// *Action: Specify the number of times this statement must be executed
/
24334, 00000, "no descriptor for this position"
// *Cause: The application is trying to get a descriptor from a handle
// for an illegal position.
// *Action: Check the position number.
/
24335, 00000, "cannot support more than 1000 columns"
// *Cause: The number of columns exceeds the maximum number supported.
// *Action:
/
24336, 00000, "invalid result set descriptor"
// *Cause: The result set descriptor should have valid data fetched into
// it before it can be converted to a statement handle
// *Action: Fetch valid data into the descriptor before attempting to
// convert it into a statement handle
/
24337, 00000, "statement handle not prepared"
// *Cause: A statement cannot be executed before making preparing a request.
// *Action: Prepare a statement before attempting to execute it.
/
24338, 00000, "statement handle not executed"
// *Cause: A fetch or describe was attempted before executing a
// statement handle.
// *Action: Execute a statement and then fetch or describe the data.
/
24339, 00000, "cannot set server group name after connecting to server"
// *Cause: An attempt was made to set the server group in a server handle
// after connecting to the server. However, once the connection
// is established to a server, the server group name cannot be
// set anymore.
// *Action: Attach to the server after setting the server group name in
// the server handle.
/
24340, 00000, "cannot support more than 255 columns"
// *Cause: The number of columns exceeds maximum supported by the server.
// *Action: Limit your operation to 255 columns.
/
24341, 00000, "bad mode specified"
// *Cause: OCI_ENV_NO_MUTEX mode was specified for a non-threaded client.
// *Action: OCI_ENV_NO_MUTEX may be specified when OCI_THREADED had been
// specified at process initialization.
/
24342, 00000, "unable to destroy a mutex"
// *Cause: An attempt to destroy a mutex failed.
/
24343, 00000, "user defined callback error"
// *Cause: The only valid return value for a user defined callback
// function is OCI_CONTINUE or OCI_ROWCBK_DONE. Any other value
// will cause this error.
// *Action: Please insure that OCI_CONTINUE or OCI_ROWCBK_DONE is returned
// from the user defined callback function.
24344, 00000, "success with compilation error"
// *Cause: A sql/plsql compilation error occurred.
// *Action: Return OCI_SUCCESS_WITH_INFO along with the error code
//
24345, 00000, "A Truncation or null fetch error occurred"
// *Cause: A truncation or a null fetch error"
// *Action: Please ensure that the buffer size is long enough to
// store the returned data.
24346, 00000, "cannot execute without binding variables"
// *Cause: None of the bind variables in the SQL statement are bound.
// *Action: Please bind all the variables before the execute is done.
//
24347, 00000, "Warning of a NULL column in an aggregate function"
// *Cause: A null column was processed by an aggregate function
// *Action: An OCI_SUCCESS_WITH_INFO is returned.
//
24348, 00000, "Update or Delete without Where"
// *Cause: An update or delete was executed without where clause
// *Action: An OCI_SUCCESS_WITH_INFO is returned.
//
24349, 00000, "Array DML row counts not available"
// *Cause: One of the following occurred:
// -The attribute in OCIAttrGet was used incorrectly.
// -The version of the database used does not support this feature
// -There was an error in the array DML for all of the
// iterations.
// *Action: Ensure that the statement is an array DML and also ensure
// that the database version is Oracle 12 or higher and the correct
// mode is used.
/
24350, 00000, "OCI call not allowed"
// *Cause: OCI used is not permitted from external procedures.
// *Action: Refer to user manual for usage restrictions.
/
24351, 00000, "invalid date passed into OCI call"
// *Cause: A bad date was passed into one of the OCI calls.
// *Action: Check your date bind values and correct them.
/
24352, 00000, "invalid COBOL display type passed into OCI call"
// *Cause: A bad COBOL display type was passed into one of the OCI calls.
// *Action: Check your COBOL display type bind values and correct them.
/
24353, 00000, "user buffer too small to accommodate COBOL display type"
// *Cause: User supplied buffer for a COBOL display type was too small
// to accommodate fetched number.
// *Action: Increase the allocation for COBOL display type buffer.
/
24354, 00000, "number fetched too large to fit in COBOL display type buffer."
// *Cause: The number fetched was beyond the range that can be displayed.
// *Action: Please check the number in the database.
/
24355, 00000, "attempt to store a negative number in an Unsigned Display type."
// *Cause: An attempt was made to convert a negative number into an unsigned
// display type.
// *Action: Please check the number in the database or change the defined
// datatype.
/
24356, 00000, "internal error while converting from to COBOL display type."
// *Cause: An internal error was encountered during conversion to
// COBOL display type.
// *Action: Contact customer support.
/
24357, 00000, "internal error while converting from to OCIDate."
// *Cause: An internal error was encountered during conversion to
// OCIDate type.
// *Action: Contact customer support.
/
24358, 00000, "OCIBindObject not invoked for a Object type or Reference"
// *Cause: OCIBindObject was not invoked resulting in an incomplete
// bind specification for a Object Type or Reference.
// *Action: Please invoke the OCIBindObject call for all Object Types and
// References.
/
24359, 00000, "OCIDefineObject not invoked for a Object type or Reference"
// *Cause: OCIDefineObject was not invoked resulting in an incomplete
// bind specification for a Object Type or Reference.
// *Action: Please invoke the OCIDefineObject call for all Object Types and
// References.
/
24360, 00000, "Type Descriptor Object not specified for Object Bind/Define"
// *Cause: Type Descriptor Object is a mandatory parameter for Object Types
// Binds and Defines.
// *Action: Please invoke the OCIBindObject() or OCIDefineObject() call
// with a valid Type Descriptor Object.
/
24361, 00000, "basic bind call not invoked before invoking advanced bind call"
// *Cause: One of the basic bind calls was not invoked on this bind handle
// before performing an advanced bind call.
// *Action: Please invoke the advanced bind call on this bind handle only
// after performing a basic bind call.
/
24362, 00000, "improper use of the character count flag"
// *Cause: When the character count flag is set, then the maximum size of
// the buffer in the server should be specified as a non-zero value.
// *Action: Please use a non-zero value for the mamimum size of the buffer
// in the server.
/
24363, 00000, "measurements in characters illegal here"
// *Cause: Measurements in characters instead of bytes are illegal if
// either the server's or client's character set is varying width.
// *Action: If either the client's or server's character set is varying
// width then do not use the OCI_ATTR_CHAR_COUNT attribute for the
// bind handle. Use OCI_ATTR_MAXDATA_SIZE instead.
/
24364, 00000, "internal error while padding blanks"
// *Cause: An internal error has occurred while attempting to blank pad
// string data. This error should not occur normally.
// *Action: Contact customer support.
/
24365, 00000, "error in character conversion"
// *Cause: This usually occurs during conversion of a multibyte
// character data when the source data is abnormally terminated
// in the middle of a multibyte character.
// *Action: Make sure that all multibyte character data is properly terminated.
/
24366, 00000, "migratable user handle is set in service handle"
// *Cause: This occurs during user authentication, a migratable user handle
// has been set in the service handle.
// *Action: Service handle must not be set with migratable user handle when it
// is used to authenticate another user.
/
24367, 00000, "user handle has not been set in service handle"
// *Cause: This occurs during authentication of a migratable user.
// the service handle has not been set with non-migratable user handle.
// *Action: Service handle must be set with non-migratable user handle when it
// is used to authenticate a migratable user.
/
24368, 00000, "OCI mutex counter non-zero when freeing a handle"
// *Cause: This is an internal OCI error.
// *Action: Contact customer support.
/
24369, 00000, "required callbacks not registered for one or more bind handles"
// *Cause: No callbacks have been registered for one or more of the bind
// handles which are part of the RETURNING clause.
// *Action: The bind handles which are to receive data in a DML statememt
// with a RETURNING clause must have their mode set as DATA_AT_EXEC
// and callback functions must be registered for these bind handles
// using OCIBindDynamic.
/
24370, 00000, "illegal piecewise operation attempted"
// *Cause: Data of a certain datatype that does not support piecewise
// operation is being sent or fetched in pieces.
// *Action: Always set the piece value to OCI_ONE_PIECE for datatypes that
// does not support piecewise operation.
/
24371, 00000, "data would not fit in current prefetch buffer"
// *Cause: An internal OCI error has occurred.
// *Action: Please contact Oracle customer support.
/
24372, 00000, "invalid object for describe"
// *Cause: The object to be described is not valid.
// It either has compilation or authorization errors.
// *Action: The object to be described must be valid.
/
24373, 00000, "invalid length specified for statement"
// *Cause: The length specified for the statement is either 0 or too large.
// *Action: Specify a valid length for the statement.
/
24374, 00000, "define not done before fetch or execute and fetch"
// *Cause: The application did not define output variables for data being
// fetched before issuing a fetch call or invoking a fetch by
// specifying a non-zero row count in an execute call.
// *Action: Issue OCI define calls for the columns to be fetched.
/
24375, 00000, "Cannot use V6 syntax when talking to a V8 server"
// *Cause: V6 syntax is no longer supported in V8 server.
// *Action: Change syntax to V7 syntax or higher.
/
24376, 00000, "cannot register/get user callback for non-environment handle"
// *Cause: A user callback registration or get was attempted on a handle which
// is not an environment handle.
// *Action: Pass the environment handle to register/get user callback.
/
24377, 00000, "invalid OCI function code"
// *Cause: An invalid function code was used.
// *Action: Use a valid OCI function code.
/
24378, 00000, "user callbacks not allowed for this call"
// *Cause: An attempt was made to register a user callback for an OCI call for
// which it not allowed to register user callbacks.
// *Action: Do not register user callback for this OCI call.
/
24379, 00000, "invalid user callback type"
// *Cause: An invalid type of user callback was specified.
// *Action: Specify a valid user callback type.
/
24380, 00000, "invalid mode specification"
// *Cause: The mode parameter in an OCI call is invalid
// *Action: Use only valid mode parameter
/
24381, 00000, "error(s) in array DML"
// *Cause: One or more rows failed in the DML.
// *Action: Refer to the error stack in the error handle.
/
24382, 00000, "statement handled already executed or described"
// *Cause: The Statement handle was executed or described successfuly before.
// *Action: Perform a OCIStmtPrepare again before OCI_PARSE_ONLY.
24383, 00000, "Overflow segment of an IOT cannot be described"
// *Cause: The name specified in the OCIDescribeAny call referred to an
// IOT overflow segment.
// *Action: Use OCIDescribeAny to describe only documented objects.
24384, 00000, "Application context size is not initialized"
// *Cause: The size of the application context must be initialized before
// populating each context element.
// *Action: Issue OCIAttrSet with OCI_ATTR_CTX_SIZE to initialize context size
24385, 00000, "Application context size or index is not valid"
// *Cause: The size or index of the application context must be non-zero and
// non-negative.
// *Action: Use an appropriate value for the size.
24386, 00000, "statement/server handle is in use when being freed"
// *Cause: This is an internal OCI error.
// *Action: The user should reset in-use flag in statement handle before
// freeing the handle.
24387, 00000, "Invalid attach driver"
// *Cause: Trying to attach using the wrong driver
// *Action: Relink the application in the right mode
24388, 00000, "Unsupported functionality in fast path mode"
// *Cause: Feature not supported in fast path mode
// *Action: Avoid using the functionality in this mode
24389, 00000, "Invalid scrollable fetch parameters"
// *Cause: All the requested rows in this fetch could not be received.
// *Action: Check the fetch orientation, scroll offset,
// OCI_ATTR_CURRENT_POSITION and number of rows in OCIStmtFetch2 call.
// If required, change some of above parameters and fetch again.
24390, 00000, "Unsupported scrollable cursor operation"
// *Cause: The scrollable cursor execute or fetch has failed.
// *Action: Check the documentation for supported types, and other restrictions
// while using scrollable cursors.
24391, 00000, "invalid fetch operation"
// *Cause: Scrollable cursor operation requested with non-scrollable cursor.
// *Action: Check if the statement was executed in the scrollable mode. Else
// the only acceptable orientation is OCI_FETCH_NEXT that ignores the
// scroll offset parameter.
/
/ Connection Pooling messages
/
24392, 00000, "no connection pool to associate server handle"
// *Cause: OCIServerAttach called in OCI_POOL mode but no connection pool
// found to associate the server handle.
// *Action: 1) Verify that OCIConnectionPoolCreate is called before calling
// OCIServerAttach.
// 2) Verify that the database link specified in OCIServerAttach
// matches with that of the connection pool database link.
24393, 00000, "invalid mode for creating connection pool"
// *Cause: Mode specified in OCIConnectionPoolCreate is invalid.
// *Action: Use a valid mode.
24394, 00000, "invalid mode for destroying connection pool"
// *Cause: Mode specified in OCIConnectionPoolDestroy is invalid.
// *Action: Use a valid mode.
24395, 00000, "cannot reinitialize non-existent pool"
// *Cause: OCIConnectionPoolCreate was not called in OCI_DEFAULT mode for this
// pool handle.
// *Action: Create a connection pool prior to reinitializing it.
24396, 00000, "invalid attribute set in server handle"
// *Cause: Attribute OCI_ATTR_NONBLOCKING_MODE has been set on the server
// handle and attached in OCI_POOL mode. Connection pooling does
// not support non blocking mode.
// *Action: Do not set the OCI_ATTR_NONBLOCKING_MODE attribute on the server
// handle while attaching in OCI_POOL mode.
24397, 00000, "error occured while trying to free connections"
// *Cause: An internal error occured while trying to free connections.
// *Action: Contact customer support.
24398, 00000, "connection pool already exists"
// *Cause: A connection pool has already been created for the specified
// pool handle.
// *Action: 1) Specify a different pool handle to create a new connection pool.
// 2) If you wish to modify the pool parameters, call
// OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode.
24399, 00000, "invalid number of connections specified"
// *Cause: An invalid combination of minimum, maximum and increment number of
// connections was specified in the OCIConnectionPoolCreate call.
// *Action: Specify a valid combination of parameters.
24400, 00000, "error occured while creating connections in the pool"
// *Cause: The database link specified in OCIConnectionPoolCreate might be an
// invalid one.
// *Action: Specify a valid database link.
24401, 00000, "cannot open further connections"
// *Cause: Sufficient number of connections are not present in the pool to
// execute the call. No new connections can be opened as the
// connMax parameter supplied in OCIConnectionPoolCreate has been
// reached.
// *Action: Call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode and
// increase the value of the connMax parameter.
24402, 00000, "error occured while creating connections in the pool"
// *Cause: The username and password specified in OCIConnectionPoolCreate
// might be invalid.
// *Action: Specify a valid username and password.
24403, 00000, "error occured while trying to destroy the connection pool"
// *Cause: Some connections in the pool were busy when an attempt to destroy
// the connection pool was made.
// *Action: Ensure no connections from the pool are being used.
24404, 00000, "connection pool does not exist"
// *Cause: An attempt was made to use the connection pool before creating it.
// *Action: Create the connection pool.
24405, 00000, "error occured while trying to create connections in the pool"
// *Cause: An internal error occured while creating connections in the pool.
// *Action: Contact customer support.
24406, 00000, "API mode switch is disallowed when a call is in progress."
// *Cause: A mode switch from OCI8 to OCI7 was attempted in a callback.
// *Action: The user should perform the API mode switch either prior to
// initiating the top call or after the main call is done.
24407, 00000, "connection pool already exists"
// *Cause: A connection pool has already been created for the specified
// pool name.
// *Action: Specify a different pool name to create a new connection pool.
24408, 00000, "could not generate unique server group name"
// *Cause: An internal error occured while generating unique server group name.
// *Action: Contact customer support.
24409, 00000, "client cannot understand the object"
// *Cause: The client cannot process all the new features in the object.
// *Action: Upgrade the client so that features like inheritance and SQLJ
// objects can be used.
24410, 00000, "scrollable cursor max size exceeded"
// *Cause: Result set size exceeded the max limits.
// *Action: Check the documentation for allowable maximum result set size for
// scrollable cursors. Re-execute with a smaller expected result set
// size or make the cursor non-scrollable.
/
/ Session Pooling OCI error messages
/
24411, 00000, "Session pool already exists."
// *Cause: A session pool has already been created for the specified
// pool handle.
// *Action: 1) Specify a different pool handle to create a new session pool.
// 2) If you wish to modify the pool parameters, call
// OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode.
24412, 00000, "Cannot reinitialize non-existent pool"
// *Cause: OCISessionPoolCreate was not called in OCI_DEFAULT mode for this
// pool handle.
// *Action: Create a session pool prior to reinitializing it.
24413, 00000, "Invalid number of sessions specified"
// *Cause: An invalid combination of minimum, maximum and increment number
// of sessions was specified in the OCISessionPoolCreate call.
// *Action: Specify a valid combination of parameters.
24414, 00000, "Only %d sessions could be started."
// *Cause: The number of sessions specified by the minSess parameter of
// OCISessionPoolCreate could not be started, possibly because the
// value supplied was larger than that supported by the server."
// *Action: This is a warning. Check the maximum number of sessions allowed
// on the server.
24415, 00000, "Missing or null username."
// *Cause: Username and password must be specified when pool is created in
// this mode.
// *Action: Specify a valid username and password.
24416, 00000, "Invalid session Poolname was specified."
// *Cause: An attempt was made to use a Session Pool that does not exist.
// *Action: Create a Session Pool before using it.
24417, 00000, "Session pool size has exceeded the maximum limit"
// *Cause: The number of sessions has exceeded the maximum size of the
// Session Pool.
// *Action: This is a warning. You can tune the session pool with
// appropriate minimum and maximum parameters.
24418, 00000, "Cannot open further sessions."
// *Cause: Sufficient number of sessions are not present in the pool to
// execute the call. No new sessions can be opened as the
// sessMax parameter supplied in OCISessionPoolCreate has been
// reached.
// *Action: Call OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode and
// increase the value of the sessMax parameter.
24419, 00000, "Proxy sessions are not supported in this mode."
// *Cause: A proxy session was requested for from a Session Pool which does
// not support proxy sessions.
// *Action: Do not specify mode OCI_CRED_PROXY.
24420, 00000, "OCISessionRelease must be used to release this session."
// *Cause: The session was retrieved using OCISessionGet, and an attempt
// has been made to release it using a call other than
// OCISessionRelease.
// *Action: Call OCISessionRelease.
24421, 00000, "OCISessionRelease cannot be used to release this session."
// *Cause: The session was not retrieved using OCISessionGet, and an attempt
// has been made to release it using OCISessionRelease.
// *Action: Release the session using an appropriate call.
24422, 00000, "error occurred while trying to destroy the Session Pool"
// *Cause: An attempt was made to destroy the session pool while some
// sessions in the pool were busy.
// *Action: Ensure that no sessions from the pool are being used OR call
// OCISessionPoolDestroy with mode set to OCI_SPD_FORCE.
/
/ ROWID define at position 0 - OCI error messages
/
24423, 00000, "Cannot set the ROWID attribute - OCI_ATTR_FETCH_ROWID"
// *Cause: An attempt was made to set the implicit ROWID attribute.
// *Action: Use a SELECT ... FOR UPDATE statement that has not previously been
// described or executed before setting this ROWID attribute.
24424, 00000,"Invalid attempt to define at position 0"
// *Cause: An invalid attempt was made to call OCIDefineByPos for position 0.
// *Action: Ensure that the implicit ROWID attribute, OCI_ATTR_FETCH_ROWID, is
// set on the statement handle before doing the execute.
24425, 00000,"Invalid mode passed when defining at position 0"
// *Cause: An invalid mode was passed to OCIDefineByPos.
// *Action: Ensure a valid mode is passed to OCIDefineByPos when defining
// at position 0.
/
/ Error message for tracing OCI Session pool.
/
24426, 00000, "Event to enable tracing in OCI Session Pool"
// *Document: NO
// *Cause: N/A
// *Action: Set this event in your environment to obtain trace information
// for OCI Session Pool.
// *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
/
/ OCISessionGet in pooled mode with security attrs
24427, 00000, "Invalid attributes on user handle"
// *Cause: Some of the attributes set on the user handle were not allowed in
// pooled mode.
// *Action: Unset the attributes on the user handle and call OCISessionGet or
// use sessions that are not pooled.
24428, 00000, "Sessions with SYSDBA privileges are not supported in this mode."
// *Cause: A session with SYSDBA privileges was requested from a Session Pool
// which does not support sessions with SYSDBA privileges.
// *Action: Do not specify mode OCI_SESSGET_SYSDBA.
24429, 00000, "External authentication is not supported in this mode."
// *Cause: An externally authenticated session was requested from a Session
// Pool which does not support external authentication.
// *Action: Do not specify mode OCI_SESSGET_CREDEXT.
/
/
/ Statement Caching OCI error messages
/
24430, 00000, "Null values for sqltext and key were specified."
// *Cause: An attempt was made to call OCIStmtPrepare2 and neither
// sqltext nor key were specified.
// *Action: Specify valid values for sqltext or key or both.
24431, 00000, "Statement does not exist in the cache"
// *Cause: The statement that was requested for does not exist in the
// statement cache.
// *Action: Please request for a valid statement.
24432, 00000, "The statement that was returned is not tagged."
// *Cause: A tagged statement was requested for, but an untagged statement
// has been returned.
// *Action: This is a warning. Please modify and tag the statement as
// desired.
24433, 00000, "This statement has already been prepared using OCIStmtPrepare2."
// *Cause: A statement that was earlier prepared using OCIStmtPrepare2 is
// now being reprepared using OCIStmtPrepare."
// *Action: Please use a different statement handle.
24434, 00000, "OCIStmtRelease called before OCIStmtPrepare2."
// *Cause: An attempt was made to release a statement without first
// preparing it using OCIStmtPrepare2.
// *Action: Call OCIStmtPrepare2 before OCIStmtRelease.
24435, 00000, "Invalid Service Context specified."
// *Cause: The statement was prepared using a service context that is
// different from the one specified in OCIStmtExecute.
// *Action: Please specify the same service context that the statement
// was prepared with.
24436, 00000, "Invalid statement Handle."
// *Cause: OCIHandleFree called on a statement that was prepared using
// OCIstmtPrepare2.
// *Action: Release the statement using OCIStmtRelease.
24437, 00000, "OCIStmtExecute called before OCIStmtPrepare2."
// *Cause: An attempt was made to execute a statement without first
// preparing it using OCIStmtPrepare2.
// *Action: Call OCIStmtPrepare2 before OCIStmtExecute.
24438, 00000, "Invalid Authentication Handle specified."
// *Cause: The statement was prepared using an authentication handle
// that is different from the one specified in OCIStmtExecute.
/
/
/ Miscellaneous OCI error messages
/
/
24439, 00000, "success with PLSQL compilation warning"
// *Cause: A plsql compilation warning occurred.
// *Action: Return OCI_SUCCESS_WITH_INFO along with the error code.
24440, 00000, "OCI Easy Install mode cannot be initialized"
// *Cause: An internal OCI error has occurred.
// *Action: Please contact Oracle customer support.
//
24441, 00000, "Invalid cookie, resend sql text"
// *Cause: An internal OCI error has occurred.
// *Action: Please contact Oracle customer support.
//
24442, 00000, "SCN exceeds the capability of the target OCI database or client"
// *Cause: An attempt was made to transfer a system change number (SCN) to
// an Oracle database or client that is older than Release 12.2 and
// the SCN exceeds the maximum value that such a system can handle.
// *Action: If needed, update the target database or client to Release 12.2
// or higher.
//
24444, 00000, "TTC RPC (%s) not allowed by the security policy configured on the database"
// *Cause: The database security policy configuration did not allow the
// specified Two-Task Common (TTC) RPC.
// *Action: Do not use functionality that issues the specified TTC RPC which
// is disallowed by the database security policy.
//
24445, 00000, "object type input parameter in TTC RPC not allowed by the security policy configured on the database"
// *Cause: The database security policy configuration did not allow object
// types as input parameters (including IN bind variables) in
// Two-Task Common (TTC) RPCs.
// *Action: Do not use the functionality that relies on object type input
// parameter usage in a TTC RPC.
//
24450, 00000, "Cannot pre-process OCI statement"
// *Cause: An error occured during statement pre-processing.
// E.g., SQL statement has invalid usage of N' or Q' literals.
// *Action: Correct the SQL statement.
//
24451, 00000, "%s, Maximum call depth exceeded"
// *Cause: Your program has too many levels of recursion.
// *Action: Restructure your program to eliminate some levels of recursion.
//
24452, 00000, "value_sz exceeding SB4MAXVAL is not supported"
// *Cause: value_sz specified in OCIBindByPos2, OCIBindByName2 or
// OCIDefineByPos2 exceeds SB4MAXVAL and is not supported in this
// release.
// *Action: Specify a value less than or equal to SB4MAXVAL for value_sz in
// OCIBindByPos2, OCIBindByName2 or OCIDefineByPos2.
//
/
24453, 0000, "number of application context settings supplied during authentication has exceeded the supported limit of %d settings"
// *Cause: The number of application context settings supplied during
// authentication exceeded the specified limit.
// *Action: Reduce the number of application context settings that are passed
// during authentication.
//
/
24454, 0000, "client host name is not set"
// *Cause: The network host name in files like /etc/hosts was not set.
// *Action: Set the host name and try again.
//
/
/
/ 24460 - 24470 Reserved for OCI Native Net
/
24460, 00000, "Native Net Internal Error"
// *Cause: Internal error .
// *Action: This error should not normally occur. If it persists,
// please contact your customer service representative.
/
/ 24471 - 24479 Reserved for OCI Objects
/
24471, 00000, "KOH tracing event"
// *Document: NO
// *Cause: N/A
// *Action: Event to trace KOH memory events
// bit 0x1: KOH_TRACE_LEVEL_MEM: trace memory alloc and free
// bit 0x2: KOH_TRACE_LEVEL_DUR: trace duration start & end
// bit 0x4: KOH_TRACE_LEVEL_ZEROCACHE: cache max & opt size = 0
// bit 0x8: KOH_TRACE_LEVEL_KOHIH: trace duration list mgmt
// bit 0x10: KOH_TRACE_LEVEL_INS: dump memory or instance
/
24472, 00000, "KOC tracing event"
// *Document: NO
// *Cause: N/A
// *Action: Event to trace KOC cache events
// bit 0x1: KOC_TRACE_EVENT_PIN: trace pin operations
// bit 0x2: KOC_TRACE_EVENT_DUR: trace duration operations
// bit 0x4: KOC_TRACE_EVENT_TXN: trace transaction operations
/
24473, 00000, "KOD tracing event"
// *Document: NO
// *Cause: N/A
// *Action: Event to trace KOD data events
// bit 0x1: KOD_TRACE_EVENT_PIC: trace pickle operations
// bit 0x2: KOD_TRACE_EVENT_UPIC: trace unpickle operations
// bit 0x4: KOD_TRACE_EVENT_TYPE: trace pickle/unpickle a type
// bit 0x00004000: KOD_TRACE_LEVEL_MEDIUM: generate medium amount of tracing
// bit 0x00008000: KOD_TRACE_LEVEL_HIGH: generate high amount of tracing
/
24474, 00000, "KOL tracing event"
// *Document: NO
// *Cause: N/A
// *Action: Event to trace KOL collection events
// bit 0x1: KOL_TRACE_EVENT_PIC: trace pickle operations
// bit 0x2: KOL_TRACE_EVENT_UPIC: trace unpickle operations
// bit 0x40: KOL_TRACE_LEVEL_MEDIUM: generate medium amount of tracing
// bit 0x80: KOL_TRACE_LEVEL_HIGH: generate high amount of tracing
/
24475, 00000, "KOKC tracing event"
// *Document: NO
// *Cause: N/A
// *Action: Event to trace KOKC events
// bit 0x1: KOkc_TRACE_LEVEL_BASIC: basic dumps
// bit 0x2: KOKC_TRACE_LEVEL_TIME: dump time
// bit 0x4: KOKC_TRACE_LEVEL_KOKCD: dump kokcd structure
// bit 0x8: KOKC_TRACE_LEVEL_ASSERT: enforce asserts
// bit 0x1000: KOKC_TRACE_LEVEL_STACK: dump short stack
// bit 0x2000: KOKC_TRACE_LEVEL_LSTACK: dump full stack
/
/ Codepoint length semantics and UTF16 related OCI error messages
/
24476, 00000, "KOPF tracing event"
// *Document: NO
// *Cause: N/A
// *Action: Event to trace KOPF operations (FDO)
// bit 0x1: KOPF_TRACE_EVENT_FDO: dump FDO's in kopfupdate()
/
/ Codepoint length semantics and UTF16 related OCI error messages
/
24480, 00000, "invalid OCI mode"
// *Cause: An attempt was made to invoke OCI API with an invalid mode.
// *Action: Provide the OCI API with legitimate mode.
24481, 00000, "Failed to initialize multithreaded environment"
// *Cause: Operating system did not support multithreaded mode.
// *Action: Use single thread mode instead.
24482, 00000, "Pool size was less than 1 in shared mode"
// *Cause: Pool size must be positive in shared mode.
// *Action: Set a positive pool size.
24483, 00000, "Invalid parameters were passed into environment creation call"
// *Cause: Invalid parameters were passed into the environment creation call.
// Check the passed in parameters for the following conditions:
// -envp should not be NULL
// -xtramem_sz should not be negative
// -Either both xtramem_sz and usrmempp have to be provided. Or, neither
// should be provided.
// *Action: Pass in legitimate parameters.
24484, 00000, "Setting authentication handle not allowed after pool create"
// *Cause: An attempt was made to set the authentication handle on session pool
// handle after OCISessionPoolCreate.
// *Action: Set the authentication handle on session pool handle before calling
// OCISessionPoolCreate.
24485, 00000, "Invalid attributes in session pool authentication handle"
// *Cause: Some of the attributes set on the authentication handle being set on
// the session pool handle are invalid.
// *Action: Unset the illegal attributes on the authentication handle being set
// on session pool handle and then call OCIAttrSet. Refer to OCI documentation
// for details.
24486, 00000, "Conflicting attributes in session pool authentication handle"
// *Cause: Some attributes could not be set both on the authentication handle
// passed to OCISessionGet and the authentication handle set on session pool
// handle.
// *Action: Unset the conflicting attributes on the authentication handle and
// call OCISessionGet.
24487, 00000, "Invalid properties or values provided for OCISessionGet"
// *Cause: Some of the properties or their values provided during
// OCISessionGet with mode OCI_SESSGET_MULTIPROPERTY_TAG were invalid.
// *Action: Provide valid properties and values when calling OCISessionGet
// with mode OCI_SESSGET_MULTIPROPERTY_TAG. Refer to Oracle Call Interface
// documentation for details.
24488, 00000, "Invalid properties or values provided for OCISessionRelease"
// *Cause: Some of the properties or their values provided during
// OCISessionRelease with mode OCI_SESSRLS_MULTIPROPERTY_TAG were invalid.
// *Action: Provide valid properties and values when calling OCISessionRelease
// with mode OCI_SESSRLS_MULTIPROPERTY_TAG. Refer to Oracle Call Interface
// documentation for details.
24489, 00000, "reserved OCI error"
// *Cause: A reserved Oracle Call Interface (OCI) error has occurred.
// *Action: Contact Oracle Support Services.
/
24490, 00000, "error while getting shard instances"
// *Cause: There was a mismatch in the shard keys or group keys with the
// corresponding connect string.
// *Action: Check if the keys are properly specified along with the
// corresponding connection string.
/
24491, 00000, "attempt to get sharding-related topology information failed"
// *Cause: An unexpected error was encountered while building and processing
// sharding-related information.
// *Action: Contact Oracle Support Services.
/
24492, 00000, "Shard library initialization failed."
// *Cause: An attempt to initialize the shard library failed.
// *Action: Contact Oracle Support Services.
/
24493, 00000, "general sharding error"
// *Cause: An unexpected error was encountered while processing sharding-related
// information.
// *Action: Contact Oracle Support Services.
/
24494, 00000, "error in constructing shard key or shard group key"
//*Cause: An invalid column value was passed.
//*Action: Pass in a column value in the appropriate format specified
// by the data type.
/
24495, 00000, "OCISessionGet() timed out waiting for a suitable writable chunk."
//*Cause: There was no instance available with a writable chunk for the
// specified shard key at the time the OCISessionGet() request was issued.
// This may be a transient condition due to chunk migration.
//*Action: Retry the request later. If needed, increase the timeout specified
// in OCI_ATTR_SPOOL_WAIT_TIMEOUT to minimize or eliminate the
// chances of running into this error during chunk migrations.
/
24496, 00000, "OCISessionGet() timed out waiting for a free connection."
//*Cause: There was no free connection as the pool reached its maximum and all
// connections were in use at the time the request was issued.
//*Action: Retry the request later. Use OCISessionGet() with
// OCI_SPOOL_ATTRVAL_TIMEDWAIT mode (with an appropriate
// OCI_ATTR_SPOOL_WAIT_TIMEOUT setting) or OCI_SPOOL_ATTRVAL_WAIT mode.
// If needed, increase the maximum size of the OCI session pool.
/
24497, 0000, "PL/SQL fix up callback name too long"
// *Cause: The PL/SQL fix up callback name was too long.
// *Action: Use a shorter PL/SQL fix up callback name.
/
24500, 00000, "invalid UTF16 mode"
// *Cause: UTF16 mode is allowed only at environment handle creation time.
// *Action: Remove UTF16 mode for functions other than OCIEnvCreate()
24501, 00000, "invalid UTF16 string passed in"
// *Cause: Non-UTF16 string is passed in while UTF16 string is expected
// *Action: Check the parameter which is actually a string
24502, 00000, "codepoint length overflows"
// *Cause: Returned buffer has more codepoints than allowed
// *Action: Set OCI_MAXCHAR_SIZE large enough to accommodate
24503, 00000, "codepoint length overflows for piecewise operation"
// *Cause: Accumulated codepoint length exceeds allowed codepoint length
// *Action: Set OCI_MAXCHAR_SIZE large enough to accommodate
24504, 00000, "data length larger than expected"
// *Cause: Incoming data larger than receiving buffer
// *Action: Set OCI_MAXDATA/MAXCHAR_SIZE appropriately or remove the setting
24505, 00000, "cannot change character set id on the handle"
// *Cause: Attempts to change character set id on non-environment handles
// *Action: Only try to change character set id on environment handles
24506, 00000, "invalid attempt to change character set id on env handle"
// *Cause: Attempts to change character set id after other handles have been
// allocated from the env handle
// *Action: Change character set id after creating environment handle
// but before allocating any handles from it.
24507, 00000, "invalid combination of character set ids"
// *Cause: Attempts to set one character set id as zero
// *Action: Set both charset and ncharset as zero or non-zero
// in OCIEnvNlsCreate()
24508, 00000, "Buffer is not aligned correctly."
// *Cause: Alignment error ocurred in buffer when converting between
// character sets.
// *Action: Align buffer appropriately. For UTF16 buffer, pass a ub2 pointer.
24509, 00000, "OCI function currently not supported in UTF16 mode."
// *Cause: Attempt to call an OCI function that was not supported in
// OCI_UTF16ID mode.
// *Action: Remove the offending function or do not create an OCI environment
// with OCI_UTF16ID mode or OCI_UTF16ID character set ID.
/
/ Column authorization Related OCI error messages (24530 - 24540)
/
24530, 00000, "User not authorized to access column value."
// *Cause: Column security is enabled and column value is not authorized.
// *Action: The program needs to handle this error and take appropriate action.
24531, 00000, "Column value authorization is unknown."
// *Cause: Column security is unknown for the column.
// *Action: Verify the fetched data. It may or may not contain a meaningful
// value because it is probably the result of an expression that
// operated on unauthorized values.
24536, 00000, "Warning - column authorization unknown."
// *Cause: Column security is unknown for one or more columns.
// *Action: Verify the fetched data. It may or may not contain a meaningful
// value because it is probably the result of an expression that
// operated on unauthorized values.
24541, 00000, "Event to test OCI attribute-level security."
// *Document: NO
// *Cause: N/A
// *Action: Set this event to get different security status for
// fetched columns.
//
24542, 00000, "PRELIM mode logon not allowed to a pluggable database"
// *Cause: PRELIM mode logon was attempted to a pluggable database.
// *Action: Create PRELIM mode connections to CDB$ROOT only.
//
24543, 00000, "instance startup or shutdown not allowed in pluggable database"
// *Cause: An instance startup or shutdown operation was attempted when
// connected to a pluggable database.
// *Action: Perform instance startup or shutdown operations by connecting to
// CDB$ROOT.
24544, 00000, "Oracle RAC One Node instance is already running."
// *Cause: An instance startup failed because an instance of the Oracle RAC
// One Node database was already running on one of the cluster nodes.
// *Action: In Oracle RAC One Node, avoid any attempt to start a second
// instance by any means while the instance is already running.
/
/ Diagnosability Related OCI error messages (24550 - 24574)
/
24550, 00000, "unhandled signal #%ld received. %s"
// *Cause: Serious error: signal received
// *Action: Refer to the platform-specific signal code, and see if the
// application code caused the error. Otherwise, record
// all error state and notify Oracle Support Services.
24551, 00000, "internal error %s"
// *Document: NO
// *Cause: There is not enough memory on the system or the application
// was leaking memory.
// *Action: Restart application. If error persists, record
// all error state and notify Oracle Support Services.
24552, 00000, "%s parameter exceeds limit of %d"
// *Document: NO
// *Cause: Number of parameters specified in OCI trace event have exceeded
// the limit.
// *Action: Record all error state and notify Oracle Support Services.
24553, 00000, "internal error parsing OCI trace event string(%s)"
// *Document: NO
// *Cause: internal use only
24554, 00000, "trace directory exceeds %d bytes(%.*s)."
// *Document: NO
// *Cause: internal use only
24555, 00000, "trace file %s cannot be opened in %s directory"
// *Document: NO
// *Cause: internal use only
24556, 00000, "invalid OCI trace event string(%s)"
// *Document: NO
// *Cause: internal use only
24557, 00000, "error %s encountered while handling error %s; exiting server process"
// *Cause: A second-level error occurred in an Oracle server process that
// required that process to exit.
// *Action: None. If an excessive number of incidents are dumped, contact
// Oracle Support Services.
/
/ OCI Driver for MySQL error messages (24600 - 24699)
/
24600, 00000, "could not create OCI environment"
// *Cause: The Oracle Client library used to communicate with the database
// failed to initialize correctly.
// *Action: Check that the Oracle environment or registry entries are
// consistent and correct. If using the Oracle Instant Client,
// make sure the Oracle driver for MySQL and Oracle libraries
// are from the same release. Make sure you have read access to
// the libraries.
24601, 00000, "bind buffer not allocated by caller"
// *Cause: A valid buffer was not provided for the bind call.
// *Action: Provide a non-NULL pointer for the bind call and a valid
// length for the buffer.
24602, 00000, "attempting to read with no fetch"
// *Cause: A column was being fetched while not in fetch state.
// *Action: Fetch the column after fetching of the result set has started.
/
/ Transaction Related OCI error messages (24750 - 24799)
/
24750, 00000, "incorrect size of attribute"
// *Cause: Transaction ID attribute size is incorrect.
// *Action: Verify that the size parameter is correct.
24752, 00000, "OCI_TRANS_NEW flag must be specified for local transactions"
// *Cause: Application attempted to start a local transaction without using
// OCI_TRANS_NEW.
// *Action: Use OCI_TRANS_NEW when starting local transactions.
24753, 00000, "local transactions cannot be detached"
// *Cause: An attempt to detach a local transaction was made.
// *Action: Local transactions may only be committed or rolled back.
24754, 00000, "cannot start new transaction with an active transaction"
// *Cause: An attempt to start a new transaction was made when there was an
// active transaction.
// *Action: Commit, rollback or detach the existing transaction before
// starting a new transaction.
24755, 00000, "OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported"
// *Cause: These flags are currently not supported.
// *Action:
24756, 00000, "transaction does not exist"
// *Cause: An invalid transaction identifier or context was used or the
// transaction has completed.
// *Action: Supply a valid identifier if the transaction has not completed
// and retry the call.
24757, 00000, "duplicate transaction identifier"
// *Cause: An attempt was made to start a new transaction with an identifier
// already in use by an existing transaction.
// *Action: Verify that the identifier is not in use.
24758, 00000, "not attached to the requested transaction"
// *Cause: An attempt was made to detach or complete a transaction that is
// not the current transaction.
// *Action: Verify that the transaction context refers to the current
// transaction.
24759, 00000, "invalid transaction start flags"
// *Cause: An invalid transaction start flag was passed.
// *Action: Verify that only one of the following values is specified:
// OCI_TRANS_NEW, OCI_TRANS_JOIN, OCI_TRANS_RESUME, or OCI_TRANS_PROMOTE.
24760, 00000, "invalid isolation level flags"
// *Cause: An invalid isolation level flag was passed.
// *Action: Verify that only one of following values - OCI_TRANS_READONLY,
// OCI_TRANS_READWRITE, OCI_TRANS_SERIALIZABLE is used.
24761, 00000, "transaction rolled back"
// *Cause:
// *Action:
24762, 00000, "server failed due to unspecified error"
// *Cause: An internal error has occured in the server commit protocol.
// *Action: Contact customer support.
24763, 00000, "transaction operation cannot be completed now"
// *Cause: The commit or rollback cannot be performed now because the
// session cannot switch to the specified transaction.
// *Action: Retry the operation later.
24764, 00000, "transaction branch has been heuristically committed"
// *Cause:
// *Action:
24765, 00000, "transaction branch has been heuristically rolled back"
// *Cause:
// *Action:
24766, 00000, "transaction branch has been partly committed and aborted"
// *Cause:
// *Action:
24767, 00000, "transaction branch prepare returns read-only"
// *Cause: The transaction is read-only, or this is the outcome of an
// optimization for two-phase commit protocol.
// *Action: None. Informational only.
24768, 00000, "commit protocol error occured in the server"
// *Cause:
// *Action: Contact customer support
24769, 00000, "cannot forget an active transaction"
// *Cause: Transaction identifier refers to an active transaction.
// *Action: Verify that the identifier of an active transaction was not
// passed as an argument.
24770, 00000, "cannot forget a prepared transaction"
// *Cause: Transaction identifier refers to a prepared transaction.
// *Action: Verify that the identifier of a prepared transaction was not
// passed as an argument.
24771, 00000, "cannot detach, prepare or forget a local transaction"
// *Cause: Service handle contains a local transaction context.
// *Action: Verify that the transaction context does not refer to a local
// transaction.
24772, 00000, "Cannot mix tightly-coupled and loosely-coupled branches"
// *Cause: Application attempted to start a transaction with a global
// transaction identifier and a wrong option.
// *Action: Verify that all branches of a global transaction are started with
// either OCI_TRANS_TIGHT or OCI_TRANS_LOOSE option. If the
// application is correct and uses distributed updates,
// contact customer support.
24773, 00000, "invalid transaction type flags"
// *Cause: OCI_TRANS_TIGHT or OCI_TRANS_LOOSE mode was not specified.
// *Action: Verify that the right parameters are being used.
24774, 00000, "cannot switch to specified transaction"
// *Cause: The transaction specified in the call refers to a transaction
// created by a different user.
// *Action: Create transactions with the same authentication so that they
// can be switched.
24775, 00000, "cannot prepare or commit transaction with non-zero lock value"
// *Cause: An attempt was made to detach the transaction with a non-zero lock
// value.
// *Action: Detach the transaction with lock value set to zero and then try to
// prepare or commit the transaction.
24776, 00000, "cannot start a new transaction"
// *Cause: An attempt was made to start a new transaction when session was
// already attached to an existing transaction.
// *Action: End the current transaction before creating a new transaction.
24777, 00000, "use of non-migratable database link not allowed"
// *Cause: The transaction, which needs to be migratable between sessions,
// tried to access a remote database from a non-multi threaded
// server process.
// *Action: Perform the work in the local database or open a connection to
// the remote database from the client. If multi threaded server
// option is installed, connect to the Oracle instance through the
// dispatcher.
24778, 00000, "cannot open connections"
// *Cause: The migratable transaction tried to access a remote database when
// the session itself had opened connections to remote database(s).
// *Action: Close the connection(s) in the session and then try to access the
// remote database from the migratable transaction. If the error
// still occurs, contact Oracle customer support.
24779, 00000, "detach not allowed with open remote cursor"
// *Cause: The migratable transaction tried to detach from the current
// session while having an open remote cursor.
// *Action: Close any open remote cursor prior to detach.
24780, 00000, "cannot recover a transaction while in an existing transaction"
// *Cause: An attempt was made to commit or roll back a transaction
// while in a different transaction, and the transaction for
// which the action is requested is in a recovery state
// (this happens if it is idle too long).
// *Action: Detach from the current transaction and retry the operation.
24781, 00000, "branches don't belong to the same global transaction"
// *Cause: The list of xids passed into kpotxmp() don't have the same gtrid
// *Action:
24782, 00000, "Cannot detach from a non-migratable transaction"
// *Cause: An attempt was made to detach from a non-migrateable transaction.
// *Action: Either commit or rollback the transaction.
24783, 00000, "Cannot switch non-migratable transactions"
// *Cause: An attempt was made to prepare/commit a txn different from current.
// *Action:
24784, 00000, "Transaction exists"
// *Cause: An attempt was made to start a transaction, while attached
// to a non-migrateable transaction
// *Action:
24785, 00000, "Cannot resume a non-migratable transaction"
// *Cause: An attempt was made to resume a non-migrateable transaction.
// *Action:
24786, 00000, "separated transaction has been completed"
// *Cause: The current transaction has been completed by another process.
// *Action: Start a new transaction
24787, 00000, "remote cursors must be closed before a call completes"
// *Cause: The previous operation did not close all the remote cursors it
// opened. Since separated transactions are enabled, this is not
// allowed.
// *Action: Close all remote cursors in each call, or start a regular
// (non-separated) transaction.
24788, 00000, "cannot switch to specified transaction (server type)"
// *Cause: The transaction specified was created by a shared server and
// the requestor is a dedicated server, or the transaction was
// created by a dedicated server and the requestor is a shared
// server.
// *Action: All parts of this application should connect as dedicated
// or as shared.
24789, 00000, "start not allowed in recursive call"
// *Cause: Oracle RM will not start/resume a branch in a recursive call
// *Action: Reconsider your application stack design
24790, 00000, "cannot mix OCI_TRANS_RESUME and transaction isolation flags"
// *Cause: An attempt was made to change the isolation level of an
// existing transaction.
// *Action: No action required
24791, 00000, "invalid transaction start flags"
// *Cause: An invalid transaction start flag was passed.
// *Action: Verify that OCI_TRANS_LOOSE was not passed along with
// OCI_TRANS_JOIN, OCI_TRANS_RESUME. Also, verify that other flags
// (such as OCI_TRANS_SEPARABLE) passed by the client are supported
// by the version of the Oracle server.
24792, 00000, "cannot mix services in a single global transaction"
// *Cause: Oracle RM will not serve global (distributed) transaction
// requests if branches are created using different services
// *Action: Configure clients such that those participating in the same
// distributed transaction use the same service name.
24793, 00000, "DTP(Distriubted Transaction Processing) test and debug"
// *Document: NO
// *Cause: internal use only
// *Action: none.
24794, 00000, "no active DTP service found"
// *Cause: Oracle RM will not serve global (distributed) transaction
// requests until DTP services are configured in RAC. It is
// possible that a service was stopped while transactions were
// in-flight.
// *Action: Provision/Start DTP services first.
24795, 00000, "Illegal %s attempt made"
// *Cause: An illegal attempt was made to commit/rollback current transaction
// *Action: Use appropriate commit/rollback mechanism
24796, 00000, "operation completed; resume of original transaction rolled back"
// *Cause: The commit, rollback, or prepare completed successfully, but
// the current transaction for this thread was rolled back.
// *Action: If desired, retry the current transaction. If the operation
// was prepare, then end transaction appropriately with a commit
// or rollback operation.
24797, 00000, "cannot promote the current transaction to a distributed transaction"
// *Cause: An illegal attempt was made to promote the current transaction.
// *Action: Verify that OCI_ATTR_XID, OCI_ATTR_INTERNAL_NAME, and OCI_ATTR_EXTERNAL_NAME
// attributes have been set properly, and verify that the current
// transaction has neither performed IDL or PDML operations, nor already
// been a distributed transaction. Also, verify that the local transaction
// is in the same isolation level if the isolation flag value is set.
24798, 00000, "cannot resume the distributed transaction branch on another instance"
// *Cause: An attempt was made to resume a distributed transaction branch that is
// physically located on another RAC instance.
// *Action: Get a connection to the instance where the transaction branch is located.
/
/
/
/ OCI Lob/File Related Error message (24800 - 24849)
/
24801, 00000, "illegal parameter value in OCI lob function"
// *Cause: One of the parameter values in the OCI lob function is illegal.
// *Action: Check every parameter in the OCI Lob function call to make sure
// they are correct. Offsets should be greater than or equal to one.
24802, 00000, "user defined lob read callback error"
// *Cause: The only valid return value for a user defined lob read callback
// function is OCI_CONTINUE. Any other value will cause this error.
// *Action: Verify that OCI_CONTINUE is returned from the user defined
// lob read callback function.
24803, 00000, "illegal parameter value in lob read function"
// *Cause: Internal error .
// *Action: This error should not normally occur. If it persists,
// please contact your customer service representative.
24804, 00000, "Lob read/write functions called while another OCI LOB read/write streaming is in progress"
// *Cause: Internal error.
// *Action: Wait for the ongoing LOB streaming call to finish before
// issuing the next server call, or use OCIBreak() abort the
// current LOB streaming call.
24805, 00000, "LOB type mismatch"
// *Cause: When copying or appending LOB locators, both source and
// desctination LOB locators should be of the same type.
// *Action: Pass the same type of LOB locators for copying or appending.
24806, 00000, "LOB form mismatch"
// *Cause: When reading from or writing into LOBs, the character set
// form of the user buffer should be same as that of the LOB.
// *Action: Make sure that the buffer you are using to read or write
// has the same form as that of the LOB.
24807, 00000, "LOB form mismatch"
// *Cause: When copying or appending LOBs, both source and
// desctination LOB locators should have the same character
// set form.
// *Action: Pass locators of the same character set form for copying
// or appending LOBs.
/
24808, 00000, "streaming of lob data is not allowed when using lob buffering"
// *Cause: Attempted to stream lob data via the polling mode or a callback
// when lob buffering was enabled for the input lob locator.
// *Action: Lob buffering is useful when reading/writing small amounts of
// lob data so streaming should not be necessary. Rewrite the
// OCILobRead/OCILobWrite call so that it does not use streaming.
// If streaming of data is required, lob buffering should not be
// used. In this case, flush buffers associated with the input
// lob locator as necessary, disable buffering on the input lob
// locator and reissue the OCILobRead/OCILobWrite call.
/
24809, 00000, "amount specified will not fit in the lob buffers"
// *Cause: LOB buffering is enabled for the input lob locator so buffering
// will be used. However, the amount of lob data to read or write
// is larger than what the lob buffers can hold.
// *Action: Either disable buffering on the input lob locator and reissue
// the command or pass a smaller amount.
/
24810, 00000, "attempting to write more data than indicated"
// *Cause: While writing into a LOB, more data was supplied than
// indicated.
// *Action: If data is written in pieces, then make sure that you
// do not provide more data in the pieces (cumulatively), than
// you indicated.
/
24811, 00000, "less data provided for writing than indicated"
// *Cause: While writing into a LOB, less data was provided than
// indicated.
// *Action: If writing data in single pieces, then make sure that the buffer
// length specified is big enough to accommodate tha data being
// provided. If data is written in pieces, then make sure that all
// the data has been provided before specifying OCI_LAST_PIECE.
/
24812, 00000, "character set conversion to or from UCS2 failed"
// *Cause: If the database character set is varying-width, the CLOB/NCLOB
// value is implicitly converted to or from UCS2. This implicit
// conversion failed.
// *Action: Contact Oracle Worldwide Support.
/
24813, 00000, "cannot send or receive an unsupported LOB"
// *Cause: An attempt was made to send a LOB across the network, but either
// the server does not support the LOB sent by the client, or the
// client does not support the LOB sent by the server. This error
// usually occurs when the client and server are running different
// versions of Oracle.
// *Action: Use a version of the Oracle that supports the LOB on both
// the client and the server.
/
24814, 00000, "operation not allowed for temporary LOBs"
// *Cause: Temporary LOB locators are not allowed in the operation.
// For example:
// OCILobAssign only takes persistent LOB locators as parameters,
// not temporary LOBs.
// *Action: Use OCILobLocatorAssign for temporary LOBs instead.
// Note that OCILobLocatorAssign can also be used for persistent
// LOBs, in which case it will behave the same as OCILobAssign.
/
24815, 00000, "Invalid character set form"
// *Cause: An invalid character set form was passed into an OCI LOB function.
// For example, the only valid cs form for OCILobCreateTemporary()
// is OCI_DEFAULT(0), SQLCS_IMPLICIT(1) or SQLCS_NCHAR(2).
// *Action: Specify a valid character set form.
24816, 00000, "Expanded non LONG bind data supplied after actual LONG or LOB column"
// *Cause: A Bind value of length potentially > 4000 bytes follows binding for
// LOB or LONG.
// *Action: Re-order the binds so that the LONG bind or LOB binds are all
// at the end of the bind list.
24817, 00000, "Unable to allocate the given chunk for current lob operation "
// *Cause: The given size is increased to accomodate the number of bytes from
// server due to varying width db char/nchar set.
// *Action: Use smaller chunk sizes when you have character set conversion
// between client/server or perform piece-wise read or write.
/
24818, 00000, "Operation not permitted on Abstract LOBs"
// *Cause: Abstract LOB locators were not allowed in the operation.
// For example, OCILobAssign only takes persistent LOB locators
// as parameters, not Abstract (i.e., client-side created) LOBs.
// *Action: Avoid the operation on Abstract LOBs.
/
24819, 00000, "Illegal reference count encountered for a temporary LOB"
// *Cause: Internal error.
// *Action: This error should not normally occur. If it persists,
// contact Oracle Support Services.
/
24820, 00000, "Differnt LOB function called while another OCI LOB call is in progress"
// *Cause: An attempt was made to execute a new OCI LOB call while
// another OCI LOB call was in progress.
// *Action: Wait for the ongoing LOB streaming call to finish before
// issuing the next server call, or use OCIBreak() to abort the
// current LOB streaming call.
/
24821, 00000, "LOB prefetch size supplied is larger than the supported limit."
// *Cause: A very large LOB prefetch size was specified during a query.
// *Action: Reduce the prefetch size to an acceptable value.
/
/ OCI Shared Structures Related Error Messages (24850 - 24874)
/
24850, 00000, "failed to startup shared subsystem"
// *Cause: While attempting to initialize OCI in shared mode, a problem
// was encountered in starting up the shared subsystem.
// *Action: Contact Oracle Customer support.
/
24851, 00000, "failed to connect to shared subsystem"
// *Cause: While attempting to initialize OCI in shared mode, a problem
// was encountered in connecting the process to the shared subsystem.
// *Action: Contact Oracle Customer Support.
/
24852, 00000, "protocol error during statement execution"
// *Cause: An internal protocol error occurred while receiving describe data
// from the server during execution of a statement.
// *Action: Contact Oracle Customer Support.
/
24853, 00000, "failed to connect thread to shared subsystem"
// *Cause: While attempting to initialize OCI in shared mode, a problem
// was encountered in connecting the thread to the shared subsystem.
// *Action: Contact Oracle Customer Support.
/
24854, 00000, "invalid pieceinfo provided"
// *Cause: While making the first call to write LOB data, an invalid
// pieceinfo value provided.
// *Action: Correct the call to use OCI_ONE_PIECE or OCI_FIRST_PIECE.
// If using OCCI, make sure to call writeBuffer before calling
// writeLastBuffer.
/
24855, 00000, "attempt to pass a LOB locator over an invalid database link"
// *Cause: There was an attempt to send a LOB locator over a database
// link which was different from the one on which it was obtained.
// *Action: Ensure that remote LOB locators are passed back on the same
// database link from which they were obtained.
/
/
/
/ OCI Notification Related Error message (24900 - 24939)
/
/
24900, 00000, "invalid or unsupported mode parameter passed in call"
// *Cause: The mode parameter passed into the OCI Client Notification call
// is incorrect.
// *Action: Please correct the mode parameter passed into OCI.
/
24901, 00000, "handles belonging to different environments passed into an OCI call"
// *Cause: All handles passed into an OCI call should belong to the same
// environment. In the call that returned this error, handles
// belonging to different environments were passed in.
// *Action: Please ensure that the handle parameters in the call to come from
// the same OCI Environment.
/
24902, 00000, "invalid subscription name or name-length in subscription handle"
// *Cause: The subscription handle passed into the OCI call does not have
// a proper name or name-length attribute.
// *Action: Please set the name and name-length attributes using the
// OCIAttrSet() call.
/
24903, 00000, "invalid namespace attribute passed into OCI call"
// *Cause: The subscription handle passed into the OCI call does not have
// a proper namespace attribute.
// *Action: Please set the namespace attribute using the OCIAttrSet()
// call.
/
24904, 00000, "invalid callback attribute passed into OCI call"
// *Cause: The subscription handle passed into the OCI call does not have
// a proper callback attribute.
// *Action: Please set the callback attribute using the OCIAttrSet()
// call.
/
24905, 00000, "invalid recipient protocol attribute passed into OCI call"
// *Cause: The subscription handle passed into the OCI call did not have
// a proper recipient protocol attribute.
// *Action: Please set the recipient protocol attribute using the OCIAttrSet()
// call.
/
24906, 00000, "invalid recipient attribute passed into OCI call"
// *Cause: The subscription handle passed into the OCI call did not have
// a proper recipient attribute.
// *Action: Please set the recipient attribute using the OCIAttrSet()
// call.
/
24907, 00000, "invalid pair of callback and recipient protocol attributes"
// *Cause: The subscription handle passed into the OCI call can't have
// both the callback defined and a recipient protocol other than
// OCI_SUBSCR_PROTO_OCI at the same time.
// *Action: Please set the appropriate callback and recipient protocol
// attributes using the OCIAttrSet() call.
24908, 00000, "invalid recipient presentation attribute"
// *Cause: The subscription handle passed into the OCI call does not have a
// valid recipient presentation attribute.
// *Action: Set the recipient presentation attribute using the OCIAttrSet()
// call
24909, 00000, "call in progress. Current operation cancelled"
// *Cause: The OCI call was invoked when another call on the connection was
// in progress.
// *Action: Check if the OCI call is supported when the call is in progress
// under special conditions; for example, if it is being used by a
// signal handler.
// NLS_DO_NOT_TRANSLATE [24910,24910]
24910, 00000, "Event to enable optimized fetch protocol"
// *Document: NO
// *Cause: N/A
// *Action: Set this event in your environment to obtain better fetch
// performance
// *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
24911, 00000, "Cannot start listener thread at specified port"
// *Cause: Thread already running at a different port.
// *Action: Set the correct port in the environment handle or let the system
// choose the port.
24912, 00000, "Listener thread failed. %s"
// *Cause: Thread listening for event notification exited because of an error.
// The error encountered is appended to the error message.
// *Action: The client needs to be restarted.
24913, 00000, "Event to enable NLS validation"
// *Cause: N/A
// *Action: Set this event in your environment to enable NLS character
// validation even when character sets are the same for client/server.
// NLS_DO_NOT_TRANSLATE [24914,24914]
24914, 00000, "Notification crash test"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
/
24915, 00000, "Cannot start Listener at specified IP address"
// *Cause: Thread was already listening at a different IP address.
// *Action: Set the correct IP address in the environment handle or
// let the system choose the correct IP address.
/
24916, 00000, "cannot use IP address attribute before release 11.2 compatible notifications"
// *Cause: An attempt was made to use OCI_ATTR_SUBSCR_IPADDR attribute
// before release 11.2 compatible notifications.
// *Action: Change the compatibility to 11.2.
/
// NLS_DO_NOT_TRANSLATE [24917,24917]
24917, 00000, "OCI notification client trace event"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
/
24918, 00000, "secure notification mode not supported"
// *Cause: An attempt was made to use OCI_SECURE_NOTIFICATION
// before release 12.0 compatible notifications.
// *Action: Change the compatibility to 12.0.
/
24919, 00000, "subscription to Fast Application Notification failed"
// *Cause: An error occurred while subscribing to Fast Application
// Notification. This could be due to problems in the Oracle
// clusterware configuration.
// *Action: Look at the client trace files for additional information.
// Ensure that the Oracle clusterware is properly configured.
/
24920, 00000, "column size too large for client"
// *Cause: Client attempted to fetch a column whose size is larger than
// the maximum size that can be handled by the client.
// *Action: Upgrade the client stack to Oracle 12c or higher.
/
// NLS_DO_NOT_TRANSLATE [24921,24921]
24921, 00000, "Event to increase default max length of BL fields"
// *Cause: N/A
// *Action: Set this event in your environment to use a different size than
// TTC_DEFAULT_MBL. THIS IS NOT A USER ERROR NUMBER/MESSAGE AND DOES
// NOT NEED TO BE TRANSLATED OR DOCUMENTED.
// *Document: NO
/
24922, 00000, "cannot send or receive an SCN value which is too high for the current compatibility setting"
// *Cause: An attempt was made to send or receive a high value system change
// number (SCN) over the network, but either the sever or client
// does not support such a high value SCN. This error usually occurs
// when either the server or client compatibility is lower than 12.2.
// *Action: Be sure the database compatibility is 12.2 or above on both
// the client and server.
/
/ Generic Notification Related Error message (24940 - 24949)
/
24940, 00000, "invalid combination of %s namespace, %s presentation and %s receive protocol"
// *Cause: An invalid combination of namespace, presentation and receive
// protocol was specified during notification registration. Currently,
// only AQ namespace is supported with XML presentation. Non-AQ
// namespace is not supported for e-mail and HTTP receive protocols.
// *Action: Please change the register call appropriately.
24941, 00000, "invalid combination of notification grouping attributes"
// *Cause: An invalid combination of notification grouping attributes was
// specified. Currently, only TIME notification grouping class is
// supported. If notification grouping class is zero, all other
// notification grouping attributes must be zero.
// *Action: Refer to documentation and change the attributes appropriately.
24942, 00000, "cannot use ntfn grouping attributes on before release 11.0 compatible ntfns"
// *Cause: An attempt was made to use notification grouping on before release
// 11.0 compatible notifications.
// *Action: Change the compatibility to 11.0.
24943, 00000, "cannot use ntfn grouping with this receive protocol, presentation and/or QoS"
// *Cause: An attempt was made to use notification grouping with e-mail or HTTP
// receive protocol or XML presentation or payload delivery or reliable
// QoS. Currently, only OCI and PLSQL receive protocols and default
// presentation are supported with notification grouping.
// *Action: Refer to documentation and change the call appropriately.
24944, 00000, "cannot use timeout or grouping with ANONYMOUS namespace"
// *Cause: An attempt was made to use timeout or grouping with ANONYMOUS
// namespace. Currently, timeout and grouping are supported only with
// AQ and DBCHANGE namespaces.
// *Action: Refer to documentation and change the call appropriately.
24945, 00000, "cannot use context, QOS and timeout attributes of notification on lower than 10.2 compatible notifications"
// *Cause: An attempt was made to use context, QOS and timeout attributes of
// notification on lower than 10.2 compatible notifications.
// *Action: Change the database compatibility to 10.2.
24946, 00000, "invalid registration callback"
// *Cause: An attempt was made to use a reserved callback for notification
// registration.
// *Action: Choose a different name for the notification callback and
// change the register call appropriately.
24947, 00000, "Invalid namespace attribute specified for the subscription %s"
// *Cause: An attempt was made to register with invalid namespace attribute.
// *Action: Refer to documentation and change the namespace appropriately.
/
/ PL/SQL Notification Related Error message (24950 - 24959)
/
24950, 00000, "unregister failed, registration not found"
// *Cause: The registration that was asked to be unregistered could
// not be found.
// *Action: Please check the callback function name and the subscription name
// in the unregister call.
/
// NLS_DO_NOT_TRANSLATE [24951,24951]
24951, 00000, "EMON tracing event"
// *Cause: N/A
// *Action: Event used to trace EMON.
// *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
24952, 00000, "register, unregister or post has incorrect collection count"
// *Cause: The register, unregister or post function was invoked with a
// collection that was smaller than the size specified by the parameter
// to the function.
// *Action: Please check the function's use and ensure that the size parameter
// is correct.
/
/
/
/ More General OCI Related messages (24960 - 24980)
/
/
24960, 00000, "the attribute %s is greater than the maximum allowable length of %d"
// *Cause: The user attempted to pass an attribute that is too long
// *Action: Shorten the specified attribute and retry the operation.
/
24961, 00000, "Event for OCI"
// *Document: NO
// *Cause: This is an internal event.
// *Action: N/A
/
24962, 00000, "connect string could not be parsed, error = %s"
// *Cause: The address portion of the connect string could not be parsed.
// The client may be using a format of the connect string that the
// server does not understand.
// *Action: Correct the connect string.
/
24963, 00000, "Event for client auto tuning"
// *Document: NO
// *Cause: This is an internal event.
// *Action: N/A
/
24964, 00000, "ALTER SESSION SET CONTAINER error"
// *Cause: An attempt to switch to a PDB with different settings
// such as character set, time zone or time zone file version
// on an Oracle 12c Release 1 (12.1) or earlier client failed.
// *Action: Upgrade client to Oracle 12 Release 2 (or later) to support such
// operations.
/
24966, 00000, "Event for kpocon internal tracing"
// *Document: NO
// *Cause: This is an internal event.
// *Action: N/A
24967, 00000, "Event for NPI internal tracing"
// *Document: NO
// *Cause: This is an internal event.
// *Action: N/A
24968, 00000, "Event for set container"
// *Document: NO
// *Cause: This is an internal event.
// *Action: N/A
24969, 00000, "iteration count of %d not supported for this statement"
// *Cause: This statement was not supported with iteration count greater
// than one.
// *Action: Execute the statement with an iteration count of one.
/
/ 24981 - 24990 Reserved for defer sga allocation errors
/
24981, 00000, "deferred SGA thread spawn failed"
// *Cause: This is an internal error.
// *Action: None
24982, 00000, "deferred SGA segment allocation failed, index = %s location = %s"
// *Cause: System-defined shared memory limits are inadequate for Oracle.
// *Action: Consult the alert file for details.
24983, 00000, "Process (%s) failed to attach to deferred SGA segments."
// *Cause: The process failed to attach to deferred SGA segments.
// *Action: Consult the alert file for details and contact Oracle Support
// Services.
24984, 00000, "SGA allocation slaves termination failed"
// *Cause: This is an internal error.
// *Action: None
/
/ 25000-25099 Reserved for Trigger errors
/
25000, 00000, "invalid use of bind variable in trigger WHEN clause"
// *Cause: A bind variable was used in the when clause of a trigger.
// *Action: Remove the bind variable. To access the table columns use
// (new/old).column_name.
25001, 00000, "cannot create this trigger type on this type of view"
// *Cause: INSTEAD OF triggers can be created on any view which is not an
// Editioning View, while BEFORE and AFTER triggers may only be
// created on Editioning Views.
// *Action: Change the trigger type to INSTEAD OF or change the view on which
// you are attempting to create a DML trigger.
25002, 00000, "cannot create INSTEAD OF triggers on tables"
// *Cause: Only BEFORE or AFTER triggers can be created on a table.
// *Action: Change the trigger type to BEFORE or AFTER.
25003, 00000, "cannot change NEW values for this column type in trigger"
// *Cause: Attempt to change NEW trigger variables of datatype object, REF,
// nested table, VARRAY or LOB datatype which is not supported.
// *Action: Do not change the NEW trigger variables in the trigger body.
25004, 00000, "WHEN clause is not allowed in INSTEAD OF triggers"
// *Cause: WHEN clause is specified in an INSTEAD OF trigger.
// *Action: Remove the WHEN clause when creating an INSTEAD OF
// trigger.
25005, 00000, "cannot CREATE INSTEAD OF trigger on a read-only view"
// *Cause: attempt to create an INSTEAD OF trigger on a view
// created with read-only option. The view cannot be
// updated using INSTEAD OF triggers.
// *Action: Do not create the trigger.
25006, 00000, "cannot specify this column in UPDATE OF clause"
// *Cause: Attempt to create a trigger on update of a column whose
// datatype is disallowed in the clause, such as LOB and
// nested table.
// *Action: Remove the UPDATE OF clause.
25007, 00000, "functions or methods not allowed in WHEN clause"
// *Cause: PLSQL function call or method invocation is not allowed
// in the WHEN clause when creating a trigger.
// *Action: Remove the function call or method invocation from
// the WHEN clause.
25008, 00000, "no implicit conversion to LOB datatype in instead-of trigger"
// *Cause: When inserting or updating a view using instead-of trigger,
// the new value for a LOB view column is of a different datatype.
// *Action: Specified a LOB value as the new value for the LOB view column.
//
25009, 00000, "Nested table clause allowed only for INSTEAD OF triggers"
// *Cause: Triggers on nested tables can only be created on view columns
// using INSTEAD OF triggers.
// *Action: Use view nested table columns for defining nested table triggers.
//
25010, 00000, "Invalid nested table column name in nested table clause"
// *Cause: The column name specified in the nested table clause of an
// INSTEAD OF trigger does not correspond to a nested table column.
// *Action: Specify a nested table column on which the trigger is to be defined.
//
25011, 00000, "cannot create trigger on internal AQ table"
// *Cause: An attempt was made to try to create a trigger on a table that is
// used internally to support the Advanced Queueing (AQ) feature.
// *Action: Do not create the trigger.
25012, 00000, "PARENT and NEW values cannot be identical"
// *Cause: The referencing clause specifies identical values for PARENT and OLD.
// *Action: Re-specify either the PARENT or NEW referencing value.
//
25013, 00000, "OLD and PARENT values cannot be identical"
// *Cause: The referencing clause specifies identical values for OLD and PARENT.
// *Action: Re-specify either the OLD or PARENT referencing value.
//
25014, 00000, "cannot change the value of a PARENT reference variable"
// *Cause: Parent values can only be read and not changed.
// *Action: Do not attempt to change a Parent variable.
//
25015, 00000, "cannot perform DML on this nested table view column"
// *Cause: DML cannot be performed on a nested table view column except through
// an INSTEAD OF trigger
// *Action: Create an INSTEAD OF trigger over the nested table view column
// and then perform the DML.
//
25016, 00000, "cannot specify column list for insert into nested table view column"
// *Cause: A column list cannot be specified for inserts into the nested table
// view column.
// *Action: Specify all the columns for insert into the nested table.
//
25017, 00000, "cannot reference NEW ROWID for movable rows in before triggers"
// *Cause: NEW ROWID was referenced in a before row trigger which is defined
// on an index-organized table, or a partitioned table with enabled
// movement of rows. The ROWID cannot be computed in a before row
// update trigger because it depends on the actual values of the row
// *Action: Remove references to NEW ROWID from the trigger definition.
//
25018, 00000, "conflicting trigger %s already exists"
// *Cause: Conflicting instead of DDL trigger on schema/database already
// exists.
// *Action: Remove the old trigger
//
25019, 00000, "too much concurreny"
// *Cause: cannot pin the database/schema because of too much concurrency
// *Action: try the operation later
//
25020, 00000, "renaming system triggers is not allowed"
// *Cause: renaming system triggers is not allowed
// *Action: Drop the trigger, and create a new one for the same
//
25021, 00000, "cannot reference a trigger defined on another table"
// *Cause: Referenced trigger in the FOLLOWS clause was defined
// on another table.
// *Action: Create the referenced trigger on the same table
25022, 00000, "cannot reference a trigger of a different type"
// *Cause: Referenced trigger in the FOLLOWS or PRECEDES clause was either
// a different type or not a compound trigger.
// *Action: Create the referenced trigger as the same type or a compound
// trigger.
25023, 00000, "Cyclic trigger dependency is not allowed"
// *Cause: A cycle of trigger dependency can be formed.
// *Action: Do not create a trigger that can formed a cyclic dependency.
25024, 00000, "cannot specify FOLLOWS for a REVERSE CROSSEDITION trigger"
// *Cause: The FOLLOWS clause was specified when creating the
// REVERSE CROSSEDITION trigger.
// *Action: Do not create a REVERSE CROSSEDITION trigger with a FOLLOWS clause.
25025, 00000, "cannot specify PRECEDES clause"
// *Cause: The PRECEDES clause was specified when creating a FORWARD
// CROSSEDITION trigger or a regular trigger.
// *Action: Do not create a FORWARD CROSSEDITION or a regular trigger with
// a PRECEDES clause.
25026, 00000, "FOR EACH ROW was specified with compound triggers"
// *Cause: FOR EACH ROW is not allowed with compound triggers.
// *Action: Remove the FOR EACH ROW clause.
//
25027, 00000, "compound triggers cannot be used as system triggers"
// *Cause: Compound trigger was defined as system trigger.
// *Action: Do not use compound trigger as system trigger.
//
25028, 00000, "regular trigger body can not start with keyword COMPOUND"
// *Cause: Regular triggers body should start with BEGIN/DECLARE etc .
// *Action: Fix the syntax and recompile.
//
25029, 00000, "compound triggers should always start with keyword COMPOUND"
// *Cause: Compound trigger body was started with incorrect keyword.
// *Action: Fix the syntax and recreate.
//
25030, 00000, "crossedition trigger cannot be owned by a non-editioned user"
// *Cause: An attempt was made to create a crossedition trigger in a
// schema where triggers were not editionable.
// *Action: Enable editions for the user for triggers and then create the
// crossedition trigger.
//
25031, 00000, "only a crossedition trigger may be specified"
// *Cause: The trigger specified was not a crossedition trigger.
// *Action: Specify a crossedition trigger.
//
25032, 00000, "crossedition trigger cannot be created in ORA$BASE"
// *Cause: An attempt was made to create crossedition trigger
// in the ORA$BASE edition.
// *Action: Do not create a crossedition trigger in the ORA$BASE edition.
//
25033, 00000, "triggers cannot be executed at this time"
// *Cause: An attempt was made to execute a trigger
// when the session was almost finished.
// *Action: Do not attempt to DML with triggers that are expected
// to execute when session has almost ended.
25034, 00000, "cannot bypass trigger owned by another user"
// *Cause: An attempt was made to do DML from a crossedition trigger on an
// object that has a non-crossedition trigger owned by another user.
// DML from a crossedition trigger bypasses the running of
// non-crossedition triggers; this cannot be allowed for triggers
// owned by other users.
// *Action: Permit the non-crossedition trigger to be bypassed by attaching it
// to the editioning view rather than the table, moving one
// of the triggers to be in the same schema as the other,
// or explicitly disabling the non-crossedition trigger.
25035, 00000, "cannot perform DML on remote object from a crossedition trigger"
// *Cause: An attempt was made to do DML from a crossedition trigger that
// would modify data in a remote database. DML from a crossedition
// trigger has special rules applied regarding what triggers will fire
// as part of that DML; these special rules cannot be applied across
// database links and therefore the DML cannot be allowed.
// *Action: Perform the DML in a helper function separate from the crossedition
// trigger itself; the special rules are not applied when the DML
// is not issued from within the crossedition trigger itself.
/
/ 25100-25199 Reserved for Parser errors (e.g. v7)
/ 25175-25199 reserved for index-organized tables ( v8 )
/ Additional parser errors begin at 30560
/
25100, 00000, "TABLESPACE option can only be used with ALTER INDEX REBUILD"
// *Cause: The TABLESPACE option to ALTER INDEX was used without the
// REBUILD option.
// *Action: Use ALTER INDEX REBUILD TABLESPACE tablespace name.
25101, 00000, "duplicate REBUILD option specification"
// *Cause: The REBUILD option to ALTER INDEX is specified more than once.
// *Action: Specify the option at most once.
25102, 00000, "PARALLEL option can only be used with ALTER INDEX REBUILD"
// *Cause: The PARALLEL option to ALTER INDEX was used without the
// REBUILD option.
// *Action: Use ALTER INDEX REBUILD.
25103, 00000, "NOPARALLEL option can only be used with ALTER INDEX REBUILD"
// *Cause: The NOPARALLEL option to ALTER INDEX was used without the
// REBUILD option.
// *Action: Use ALTER INDEX REBUILD.
25104, 00000, "UNRECOVERABLE option can only be used with ALTER INDEX REBUILD"
// *Cause: The UNRECOVERABLE option to ALTER INDEX was used without the
// REBUILD option.
// *Action: Use ALTER INDEX REBUILD.
25105, 00000, "RECOVERABLE option can only be used with ALTER INDEX REBUILD"
// *Cause: The RECOVERABLE option to ALTER INDEX was used without the
// REBUILD option.
// *Action: Use ALTER INDEX REBUILD.
25106, 00000, "only one of PARALLEL or NOPARALLEL clause may be specified"
// *Cause: PARALLEL was specified more than once, NOPARALLEL was specified
// more than once, or both PARALLEL and NOPARALLEL were specified
// in an ALTER INDEX REBUILD statement.
// *Action: Remove all but one of the PARALLEL or NOPARALLEL clauses.
25107, 00000, "duplicate TABLESPACE option specification"
// *Cause: the TABLESPACE was specified more than once
// in an ALTER INDEX REBUILD statement.
// *Action: Remove all but one of the TABLESPACE clauses.
25108, 00000, "standby lock name space exceeds size limit of %s characters"
// *Cause: The lock name space for the standby database exceeded the maximum
// string length.
// *Action: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to
// a character string of less than the specified characters.
25109, 00000, "standby lock name space has illegal character '%s'"
// *Cause: An invalid lock name space was specified for the standby database.
// The lock name space for the standby database can only contain
// A-Z, 0-9, '_', '#', '$', '.' and '@' characters.
// *Action: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to
// a valid character string.
25110, 00000, "NOSORT may not be used with a bitmap index"
// *Cause: An attempt was made to create a bitmap index using
// the NOSORT option.
// *Action: Remove NOSORT from the CREATE BITMAP INDEX statement.
25111, 00000, "creation of BITMAP cluster indices is not supported"
// *Cause: An attempt was made to create a cluster index with the
// BITMAP attribute.
// *Action: Remove BITMAP from the CREATE INDEX statement.
25112, 00000, "maximum number of BITMAP index columns is 30"
// *Cause: Too many columns were specified for the index.
// *Action: Create an index on fewer columns.
25113, 00000, "GLOBAL may not be used with a bitmap index"
// *Cause: An attempt was made to create a bitmap index using
// the GLOBAL option.
// *Action: Remove GLOBAL from the CREATE BITMAP INDEX statement,
// and/or add a LOCAL partition descriptor if the table is
// partitioned.
25114, 00000, "invalid file number specified in the DUMP DATAFILE/TEMPFILE command"
// *Cause: An invalid file number was used in dumping a datafile or tempfile.
// *Action: Specify a valid file number.
25115, 00000, "duplicate BLOCK option specification"
// *Cause: BLOCK (MIN/MAX) was specified more than once in the DUMP DATAFILE/TEMPFILE
// command.
// *Action: Specify only one BLOCK option.
25116, 00000, "invalid block number specified in the DUMP DATAFILE/TEMPFILE command"
// *Cause: An invalid block number was used in dumping a datafile or tempfile.
// *Action: Specify a valid block number.
25117, 00000, "MIN/MAX/Block Number expected"
// *Cause: A value other than MIN/MAX, or a block number was entered in the DUMP DATAFILE/TEMPFILE command.
// *Action: Correct the syntax.
25118, 00000, "invalid DUMP DATAFILE/TEMPFILE option"
// *Cause: An invalid option was specified for the DUMP DATAFILE/TEMPFILE command.
// *Action: Correct the syntax.
25119, 00000, "LOGGING/NOLOGGING option already specified"
// *Cause: In CREATE TABLESPACE, the LOGGING and/or NOLOGGING options were
// specified more than once.
// *Action: Remove all but one of the logging specifications.
25120, 00000, "MINIMUM EXTENT option already specified"
// *Cause: In CREATE TABLESPACE, the MINIMUM EXTENT option was
// specified more than once.
// *Action: Remove all but one of the MINIMUM EXTENT specifications.
25121, 00000, "MINIMUM EXTENT value greater than maximum extent size"
// *Cause: In CREATE/ALTER TABLESPACE, the value specified for the MINIMUM EXTENT
// option was greater than the maximum extent size.
// *Action: Choose a lower value for the MINIMUM EXTENT option.
25122, 00000, "Only LOCAL bitmap indexes are permitted on partitioned tables"
// *Cause: An attempt was made to create a global bitmap index on a partioned
// table.
// *Action: create a local bitmap index instead.
25123, 00000, "Too many components specified in the name."
// *Cause: Specifying more components to a name than allowed.
// *Action: Check the name specified for the operation.
25124, 00000, "Database link name not allowed."
// *Cause: Specifying a database link name when it is not permitted.
// *Action: Check the name specified for the operation.
25125, 00000, "BUFFER_POOL/FLASH_CACHE/CELL_FLASH_CACHE storage option not allowed"
// *Cause: An attempt was made to specify the BUFFER_POOL, FLASH_CACHE, or CELL_FLASH_CACHE
// storage option. This option may only be specified during
// - CREATE or ALTER TABLE
// - CREATE or ALTER CLUSTER
// - CREATE or ALTER INDEX
// *Action: Remove this option and retry the statement.
25126, 00000, "Invalid name specified for BUFFER_POOL/FLASH_CACHE/CELL_FLASH_CACHE"
// *Cause: The name of the cache hints specified by was invalid.
// The only valid names for BUFFER_POOL are KEEP, RECYCLE and DEFAULT.
// The only valid names for FLASH_CACHE and CELL_FLASH_CACHE
// are KEEP, NONE and DEFAULT.
// *Action: Use a valid name or remove the BUFFER_POOL, FLASH_CACHE, or CELL_FLASH_CACHE clause.
25127, 00000, "RELY not allowed in NOT NULL constraint"
// *Cause: An attempt to set RELY on for NOT NULL constraint.
// *Action: only NORELY may be specified for a NOT NULL constraint.
//
25128, 00000, "No insert/update/delete on table with constraint (%s.%s) disabled and validated"
// *Cause: Try to insert/update/delete on table with DISABLE VALIDATE constraint.
// *Action: Change the constraint's states.
//
25129, 00000, "cannot modify constraint (%s) - no such constraint"
// *Cause: the named constraint does not exist for this table.
// *Action: Obvious
25130, 00000, "cannot modify primary key - primary key not defined for table"
// *Cause: Attempted to modify a primary key that is not defined for the
// table.
// *Action: None
25131, 00000, "cannot modify unique(%s) - unique key not defined for table"
// *Cause: attempted to modify a unique key that is not deined for the table.
// *Action: None
25132, 00000, "UNIQUE constraint (%s.%s) disabled and validated in ALTER TABLE EXCHANGE PARTITION"
// *Cause: cannot ALTER TABLE EXCHANGE PARTITION when the partition and the
// table have a disabled and validated unique constraints AND the unique keys
// in the partion is not mutually exclusive from the rest of the table.
// *Action: Change the constraint's status.
25133, 00000, "duplicate SINGLE TABLE option specified"
// *Cause: The SINGLE TABLE option was specified more than once.
// *Action: Specify the SINGLE TABLE option only once.
25134, 00000, "keyword TABLE expected"
// *Cause: The keyword TABLE is missing from the SINGLE TABLE option.
// *Action: Place the keyword TABLE after the keyword SINGLE in the command.
25135, 00000, "cannot use the SINGLE TABLE option"
// *Cause: The SINGLE TABLE option is only valid for hash clusters.
// *Action: Do not specify the SINGLE TABLE option.
25136, 00000, "this cluster can contain only one table"
// *Cause: An attempt was made to store more than one table in a cluster
// that was created with the SINGLE TABLE option.
// *Action: Do not attempt to store more than one table in the cluster.
25137, 00000, "Data value out of range"
// *Cause: Value from cast operand is larger than cast target size.
// *Action: Increase size of cast target.
25138, 00000, "%s initialization parameter has been made obsolete"
// *Cause: An obsolete initialization parameter has been specified
// *Action: The system will come up, but parameters must be examined
25139, 00000, "invalid option for CREATE TEMPORARY TABLESPACE"
// *Cause: An invalid option appears.
// *Action: Specify one of the valid options: TEMPFILE,
// EXTENT MANAGEMENT LOCAL, UNIFORM
/
25140, 00000, "%s space policy cannot be specified for the %s extent management"
// *Cause: An invalid option appears.
// *Action: Make sure that for LOCAL extent management UNIFORM or AUTOALLOCATE
// is specified, and for DICTIONARY extent management UNIFORM or
// AUTOALLOCATE are not specified
/
25141, 00000, "invalid EXTENT MANAGEMENT clause"
// *Cause: An invalid option appears for EXTENT MANAGEMENT clause
// *Action: Specify one of the valid options: UNIFORM SIZE, AUTOALLOCATE
/
25142, 00000, "default storage clause specified twice"
// *Cause: default storage clause was specified twice for create tablespace
// *Action: Specify it once.
/
25143, 00000, "default storage clause is not compatible with allocation policy"
// *Cause: default storage clause was specified for a tablespace with
// AUTOALLOCATE or UNIFORM policy
// *Action: Omit the storage clause
/
25144, 00000, "invalid option for CREATE TABLESPACE with TEMPORARY contents"
// *Cause: An invalid option appears.
// *Action: Specify one of the valid options: EXTENT MANAGEMENT DICTIONARY,
// USER
/
25145, 00000, "allocation policy already specified"
// *Cause: In CREATE TABLESPACE, the allocation policy was specified more
// than once, for example, AUTOALLOCATE and UNIFORM.
// *Action: Remove all but one of the allocation policy specifications.
/
25146, 00000, "EXTENT MANAGEMENT option already specified"
// *Cause: In CREATE TABLESPACE, the EXTENT MANAGEMENT option was
// specified more than once.
// *Action: Remove all but one of the EXTENT MANAGEMENT specifications.
/
25147, 00000, "UNIFORM SIZE value greater than maximum extent size"
// *Cause: In CREATE/ALTER TABLESPACE, the value specified for the UNIFORM SIZE option was greater than the maximum extent size.
// *Action: Choose a lower value for the UNIFORM SIZE option.
/
25148, 00000, "ONLINE option not permitted"
// *Cause: An attempt was made to specify ONLINE for ALTER TABLE MOVE
// on a table that is not index-organized. The ONLINE option is
// currently supported only for index-organized tables.
// *Action: Remove the ONLINE option from the command.
/
25149, 00000, "Columns of UROWID type may not be indexed"
// *Cause: An attempt was made to create an index on a column of UROWID type
// *Action: Remove the column from the list of indexed columns
/
25150, 00000, "ALTERING of extent parameters not permitted"
// *Cause: An attempt was made to alter the extent parameters for a segment
// in a tablespace with autoallocate or uniform extent allocation
// policy.
// *Action: Remove the appropriate extent parameters from the command.
/
25151, 00000, "Rollback Segment cannot be created in this tablespace"
// *Cause: An attempt was made to create a rollback segment in a tablespace
// with autoallocate extent allocation policy.
// *Action: Specify a different tablespace for the rollback segment
/
25152, 00000, "TEMPFILE cannot be dropped at this time"
// *Cause: An attempt was made to drop a TEMPFILE being used by online users
// *Action: The TEMPFILE has been taken offline. Try again, later.
/
25153, 00000, "Temporary Tablespace is Empty"
// *Cause: An attempt was made to use space in a temporary tablespace with
// no files.
// *Action: Add files to the tablespace using ADD TEMPFILE command.
/
25154, 00000, "column part of USING clause cannot have qualifier"
// *Cause: Columns that are used for a named-join (either a NATURAL join
// or a join with a USING clause) cannot have an explicit qualifier.
// *Action: Remove the qualifier.
/
25155, 00000, "column used in NATURAL join cannot have qualifier"
// *Cause: Columns that are used for a named-join (either a NATURAL join
// or a join with a USING clause) cannot have an explicit qualifier.
// *Action: Remove the qualifier.
/
25156, 00000, "old style outer join (+) cannot be used with ANSI joins"
// *Cause: When a query block uses ANSI style joins, the old notation
// for specifying outer joins (+) cannot be used.
// *Action: Use ANSI style for specifying outer joins also.
/
25157, 00000, "Specified block size %s is not valid"
// *Cause: An attempt was made to create a tablespace with a block
// size which is not supported.
// *Action: Specify one of the valid blocksizes i.e the standard
// blocksize or one of (2k, 4k, 8k, 16k, 32k) subject
// to the maximum and minimum blocksizes supported by
// the platform.
/
25158, 00000, "Cannot specify RELY for foreign key if the associated primary key is NORELY"
// *Cause: RELY is specified for the foreign key contraint, when the
// associated primary key constraint is NORELY.
// *Action: Change the option of the primary key also to RELY.
/
25159, 00000, "Must specify a valid tablespace number"
// *Cause: A valid tablespace number was missing.
// *Action: Specify a valid tablespace number.
/
25160, 00000, "Must specify a valid relative data block address"
// *Cause: A valid relative data block address was missing.
// *Action: Specify a valid relative data block address.
/
25161, 00000, "Cannot have both DBA and RDBA options"
// *Cause: Both the DBA and RDBA options were passed to ALTER SYSTEM DUMP REDO.
// *Action: Use either the DBA option or the RDBA option but not both.
/
25162, 00000, "Must specify both RDBA MIN and RDBA MAX options"
// *Cause: Only one RDBA option was passed to ALTER SYSTEM DUMP REDO.
// *Action: Specify both RDBA MIN and RDBA MAX.
/
25163, 00000, "Invalid tablespace number or relative data block address"
// *Cause: The relative data block adress is invalid for the given tablespace
// number or the table space number is invalid.
// *Action: Specify a valid tablespace number or relative data block
// address.
/
25164, 00000, "The tag expression is too complex."
// *Cause: The statement tag value was not specified using a simple
// expression.
// *Action: Reduce the complexity of the statement tag expression. For
// example, assign the tag expression to a variable and reference the
// variable in the error logging clause.
/
25165, 00000, "number of passwords in statement exceeds maximum limit of %s"
// *Cause: The SQL statement had more passwords than the maximum limit allowed.
// *Action: Reconstruct the SQL statement to have a number of passwords less
// than or equal to the maximum allowed.
25175, 00000, "no PRIMARY KEY constraint found"
// *Cause: A PRIMARY KEY constraint must be defined for a table
// with this organization
// *Action: Define a PRIMARY KEY
25176, 00000, "storage specification not permitted for primary key"
// *Cause: Storage parameters cannot be defined for a PRIMARY KEY constraint
// for a table with this organization
// *Action: Remove storage specification for primary key
25177, 00000, "UNRECOVERABLE option not permitted"
// *Cause: The UNRECOVERABLE option may not be specified for a primary
// key for a table with this organization
// *Action: Remove UNRECOVERABLE option for primary key
25178, 00000, "duplicate PCTTHRESHOLD storage option specification"
// *Cause: The storage option PCTTHRESHOLD is specified more than once.
// *Action: Specify storage options at most once.
25179, 00000, "invalid PCTTHRESHOLD storage option value"
// *Cause: The specified value must be a positive integer.
// *Action: Specify an appropriate value.
25180, 00000, "PCTTHRESHOLD only valid for certain table organizations"
// *Cause: PCTTHRESHOLD can only be specified for tables with certain
// organizations.
// *Action: Remove the PCTTHRESHOLD option.
25181, 00000, "missing ON keyword for NESTED INDEX"
// *Cause: ON keyword required to specify nested index column nest
// *Action: Add ON keyword
25182, 00000, "feature not currently available for index-organized tables"
// *Cause: An attempt was made to use one or more of the following feature(s) not
// currently supported for index-organized tables:
// CREATE TABLE with LOB/BFILE/VARRAY columns,
// partitioning/PARALLEL/CREATE TABLE AS SELECT options,
// ALTER TABLE with ADD/MODIFY column options, CREATE INDEX
// *Action: Do not use the disallowed feature(s) in this release.
25183, 00000, "index-organized table top index segment is in a different tablespace"
// *Cause: An attempt was made to drop a tablespace which contains an index
// only table's overflow segment but not the top index segment"
// *Action: find index-organized tables which span the tablespace being
// dropped and some other tablespace(s). Drop these tables.
25184, 00000, "column name expected"
// *Cause: A column name is not present where required by the
// CREATE TABLE for specifying last column to be included in
// the index segment of the index-organized table
// *Action: Specify a column name where required by the syntax.
25185, 00000, "index column other than last can not be specified for INCLUDE clause"
// *Cause: An index column name other than the last is specified as
// including column
// *Action: Specify either a column name which is not part of index-organized
// table primary key index , or the last key column of the primary
// key for the INCLUDING clause.
25186, 00000, "INCLUDING clause specified for index-organized table without OVERFLOW"
// *Cause: INCLUDING clause of a CREATE TABLE is an valid option only for
// index-organized tables with OVERFLOW clause (at creation time)
// or if an OVERFLOW segment already exists (at ALTER time).
// *Action: Specify OVERFLOW clause for the index-organized table
// : For ALTER, perform ADD OVERFLOW first.
25187, 00000, "specified exceptions table form incorrect"
// *Cause: The specified table does not have the proper field definitions.
// *Action: Specify the correct table to use.
25188, 00000, "cannot drop/disable/defer the primary key constraint for index-organized tables or sorted hash cluster"
// *Cause:
// *Action:
25189, 00000, "illegal ALTER TABLE option for an index-organized table"
// *Cause: While altering an index-organized table, an attempt was made
// to enter either the PCTFREE or PCTUSED value for IOT top index segment.
// *Action: Remove the illegal option(s).
25190, 00000, "an index-organized table maintenance operation may not be combined with other operations"
// *Cause: ALTER TABLE statement attempted to combine an index-organized table
// maintenance operation (e.g. changing physical attributes) with
// some other operation (e.g. ADD constraint) which is illegal
// *Action: Ensure that a index-organized table maintenance operation is the sole
// operation specified in ALTER TABLE statement;
25191, 00000, "cannot reference overflow table of an index-organized table"
// *Cause: An attempt to directly access the overflow table of an
// index-organized table
// *Action: Issue the statement against the parent index-organized table
// containing the specified overflow table.
25192, 00000, "invalid option for an index-organized table"
// *Cause: An attempt to specify one or more of the following options for
// an index-organized table:
// [NO]CACHE, NO LOGGING, CLUSTER
// *Action: Remove the illegal option(s)
25193, 00000, "cannot use COMPRESS option for a single column key"
// *Cause: An attempt to use COMPRESS option on single column key
// *Action: Remove the COMPRESS option.
25194, 00000, "invalid COMPRESS prefix length value"
// *Cause: The specified value must be a positive integer less than the number
// of key columns
// *Action: Specify an appropriate value.
25195, 00000, "invalid option for index on an index-organized table"
// *Cause: An attempt to specify one or more of the following options for
// index on an IOT:
// BITMAP, REVERSE, PCTUSED
25196, 00000, "keyword MOVE in ALTER TABLE MOVE must immediately follow <table name>"
// *Cause: MOVE specified after one/more other ALTER options
// *Action: Change order of options, MOVE should be first
// *Action: Remove the illegal option(s)
25197, 00000, "an overflow segment already exists for the indexed-organized table"
// *Cause: An attempt was made to ADD OVERFLOW segment on an index-organized
// table that already has an overflow segment
// *Action:
25198, 00000, "partitioning method is not supported for index-organized table"
// *Cause: An unsupported partitioning method was specified.
// *Action: Select a different partitioning scheme. Consult the documentation
// for supported partitioning methods.
25199, 00000, "partitioning key of a index-organized table must be a subset of the primary key"
// *Cause: An attempt to specify a partitioning key which is not a prefix
// of the primary key of the index-organized table
// *Action: Select a different partitioning key
/
/ 25200-25699 Reserved for OLTP
/ 25200-25325 Reserved for AQ
/ 25350-25375 Reserved for V8 Transaction OCI
/ 25400-25425 Reserved for Application Failover
/ 25426-25435 Reserved for Dblink Concentration
/ 25436-25476 Reserved for Rules Engine
/
/ 25200 - 25224 Reserved for DBMS_AQ.ENQUEUE
/
25200, 00000, "invalid value %s, QUEUE_NAME should be [SCHEMA.]NAME"
// *Cause: A NULL parameter was specified for QUEUE_NAME.
// *Action: Specify a non-NULL queue name.
//
25201, 00000, "invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE"
// *Cause: An invalid value specified for parameter VISIBILITY.
// *Action: Specify either ON_COMMIT or IMMEDIATE.
//
25202, 00000, "invalid value NULL, %s should be non-NULL"
// *Cause: A NULL value was specified for the parameter.
// *Action: Specify a non-NULL value.
//
25203, 00000, "invalid value %s, DELAY should be non-negative"
// *Cause: A negative value or NULL was specified for DELAY.
// *Action: Specify a non negative integer for DELAY.
//
25204, 00000, "invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP"
// *Cause: An invalid SEQUENCE_DEVIATION was specified.
// *Action: Specify either the option 'BEFORE' or 'TOP'.
//
25205, 00000, "the QUEUE %s.%s does not exist"
// *Cause: The specified queue does not exist.
// *Action: Create the queue first before specifying it for enqueue or dequeue.
//
25206, 00000, "enqueue failed, enqueue to exception queue %s.%s not permitted"
// *Cause: An attempt was made to enqueue to an exception queue.
// *Action: Try enqueueing to another queue.
//
25207, 00000, "enqueue failed, queue %s.%s is disabled from enqueueing"
// *Cause: The queue has been stopped to prevent any further enqueueing.
// *Action: Enable the queue first by using an administrative operation.
//
25208, 00000, "RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE"
// *Cause: A relative message identifier should be specified if sequence
// deviation is specified as BEFORE.
// *Action: Either specify an existing relative message identifier or
// don't specify sequence deviation as BEFORE.
//
25209, 00000, "invalid value %s, EXPIRATION should be non-negative or NEVER"
// *Cause: The expiration is less than zero or NULL.
// *Action: Specify a valid value for expire_after which should be greater
// than or equal to zero or NEVER.
//
25210, 00000, "invalid value for RELATIVE_MSGID, no message in queue with that msgid"
// *Cause: No message inm the queue with the msgid equal to the specified
// RELATIVE_MSGID.
// *Action: Try again with a valid RELATIVE_MSGID.
//
25211, 00000, "invalid DELAY specified when using sequence deviation"
// *Cause: The DELAY specified in the enqueue is greater than the delay
// of the message with the given relative message id.
// *Action: Set the DELAY to be less than or equal to the delay of the
// message with the given relative message id. If the TOP option
// is used the delay must be less than or equal to the delay of
// all the messages in the queue.
//
25212, 00000, "invalid PRIORITY specified when using sequence deviation"
// *Cause: The PRIORITY specified in the enqueue is less than the priority
// of the message with the given relative message id.
// *Action: Set the PRIORITY to be less than the delay of the message with
// the given relative message id. If the TOP option is used the
// prioirty must be greater than or equal to the priority of
// all the messages in the queue.
25213, 00000, "message with specified RELATIVE_MSGID has been dequeued"
// *Cause: The message specified by the RELATIVE_MSGID field in the
// sequence deviation BEFORE option has been dequeued.
// *Action:
25214, 00000, "cannot specify delay or expiration for enqueue to exception queue"
// *Cause: A message was enqueued to the exception queue with either delay
// or expiration specified.
// *Action: Enqueue a message without delay or expiration.
25215, 00000, "user_data type and queue type do not match"
// *Cause: A user tries to enqueue an object to a queue that was
// created for objects of different type.
// *Action: Try enqueue again with an object of the right type.
25216, 00000, "invalid recipient, either NAME or ADDRESS must be specified"
// *Cause: Both attributes, NAME and ADDRESS, were specified null for one of
// the recipients in the recipient list.
// *Action: Specify a non-null NAME or ADDRESS for the recipient.
25217, 00000, "enqueue failed, visibility must be IMMEDIATE for queue %s.%s"
// *Cause: An attempt was made to enqueue to a non-persistent queue without
// setting visibility to IMMEDIATE.
// *Action: Set visibility to IMMEDIATE.
25218, 00000, "enqueue failed, delay must be zero for queue %s.%s"
// *Cause: An attempt was made to enqueue to a non-persistent queue with
// delay greater than zero seconds.
// *Action: Set delay to zero.
25219, 00000, "enqueue failed, sequence deviation not allowed for queue %s.%s"
// *Cause: An attempt was made to enqueue to a non-persistent queue with
// sequence deviation specified.
// *Action: Do not specify sequence deviation.
25220, 00000, "enqueue failed, signature not specified for a non-repudiable queue"
// *Cause: An attempt was made to enqueue to a non-repudiable queue without
// specifying the signature
// *Action: Give the signature
25221, 00000, "enqueue failed, signature specified queue not supporting non-repudiation"
// *Cause: An attempt was made to enqueue to a queue specifying the signature
// for a queue not supporting non-repudiation
// *Action: Remove the signature
25222, 00000, "enqueue failed, complete sender info. not provided for a queue supporting non-repudiation"
// *Cause: An attempt was made to enqueue to a queue without giving the
// complete sender information (name) for a queue supporting
// non-repudiation
// *Action: Provide the sender information
//
25223, 00000, "user_data type used is not supported"
// *Cause: An attempt was made to enqueue data into a non persistent queue
// that is of a type other than the supported raw or object type.
// *Action: Enqueue the message again with data of raw or object type.
//
25224, 00000, "sender name must be specified for enqueue into secure queues"
// *Cause: An attempt was made to enqueue into a secure queue without
// specifying a sender name.
// *Action: Enqueue the message with sender name specified.
//
/
/ 25225-25249 Reserved for DBMS_AQ.DEQUEUE
/
25225, 00000, "invalid value %s, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED"
// *Cause: An invalid parameter has been specified for DEQUEUE_MODE.
//
// *Action: Specify either REMOVE, BROWSE or LOCKED.
//
25226, 00000, "dequeue failed, queue %s.%s is not enabled for dequeue"
// *Cause: The queue has not been enabled for dequeue.
//
// *Action: Enable the queue using START_QUEUE.
//
25227, 00000, "Propagation job %s doesn't exist"
// *Cause: The job doesn't exist in AQ$_SCHEDULES or cache.
//
// *Action:
//
25228, 00000, "timeout or end-of-fetch during message dequeue from %s.%s"
// *Cause: User-specified dequeue wait time has passed or the end of the
// queue has been reached but no message has been retrieved.
// *Action: Try dequeue again with the appropriate WAIT_TIME or the
// FIRST_MESSAGE option.
//
25229, 00000, "error on transformation of message %s %s"
// *Cause: There was an error when transforming a message at enqueue,
// dequeue or propagation time.
// *Action: Correct the transformation function.
//
25230, 00000, "invalid value %s, WAIT should be non-negative"
// *Cause: A negative value has been specified for WAIT.
// *Action: specify a non negative value or FOREVER.
//
25231, 00000, "cannot dequeue because CONSUMER_NAME not specified"
// *Cause: A user tried to dequeue from a queue that has been created for
// multiple consumers but a CONSUMER_NAME was not been specified in
// the dequeue options.
// *Action: Specify the CONSUMER_NAME in the dequeue options.
//
25232, 00000, "duplicate recipients specified for message"
// *Cause: An enqueue was performed with duplicate queue agents in the
// recipients parameter.
// *Action: Remove the duplicate queue agent and retry the call.
//
25233, 00000, "invalid parameter specified for NAVIGATION"
// *Cause: An invalid parameter has been specified for NAVIGATION.
// *Action: Choose one of FIRST_MESSAGE, NEXT_MESSAGE or NEXT_TRANSACTION.
// Use FIRST_MESSAGE for dequeuing the first message that satisifies
// the criterion, NEXT_MESSAGE for dequeuing the next message
// that satisifies the criterion and NEXT_TRANSACTION for moving to a
// set of messages enqueued by another transaction.
//
25234, 00000, "NEXT_TRANSACTION navigation option invalid for queue table %s.%s"
// *Cause: The NEXT_TRANSACTION navigation option was used in a dequeue from
// a queue in a queue table that was not created for transactional
// grouping.
// *Action: Specify either FIRST_MESSAGE or NEXT_MESSAGE as the navigation
// option. If you want to dequeue messages using transactional grouping
// create the queue in a queue table that has transactional grouping
// enabled.
//
25235, 00000, "fetched all messages in current transaction from %s.%s"
// *Cause: The NEXT_TRANSACTION navigation option was used in a dequeue when
// there were no more messages that belong to the same transaction.
// *Action: Use the NEXT_TRANSACTION navigation option to move to the next
// also use the FIRST_MESSAGE option to start from the head of the
// queue again.
//
25236, 00000, "buffer too small for user data"
// *Cause: The variable or buffer used for the out parameter payload is
// too small for the user data dequeued.
// *Action: Increase the size of the buffer or the size of the variable.
// Maximum size allowed is 32K.
//
25237, 00000, "navigation option used out of sequence"
// *Cause: The NEXT_MESSAGE or NEXT_TRANSACTION option was specified after
// dequeuing all the messages.
// *Action: Reset the dequeuing position using the FIRST_MESSAGE naviagtion
// option and then specify the NEXT_MESSAGE or NEXT_TRANSACTION
// option.
//
25238, 00000, "too many recipients specified for message destination %s"
// *Cause: An ENQUEUE was performed with more than 32 recipients for
// the given destination (address).
// *Action: Reduce the number of recipients to 32 or less, and retry the call.
//
25239, 00000, "message ID not supplied when dequeuing from exception queue %s.%s"
// *Cause: An attempt was made to dequeue from a release 8.0-compatible
// exception queue without including a message ID in the dequeue
// options.
// *Action: Check the application to ensure that the queue name has been
// specified correctly. If the queue name is correct supply a message
// ID when dequeuing from a release 8.0-compatible exception queue.
// Otherwise, upgrade the queue_table containing the queue to
// release 8.1-compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE
// procedure.
//
25240, 00000, "message ID and dequeue condition/correlation ID specified in dequeue options"
// *Cause: An attempt was made to dequeue by including both a message ID and
// a dequeue condition/correlation ID in the dequeue options.
// In the dequeue options, you are permitted to specify either
// message ID or dequeue condition/correlation ID, or neither.
// *Action: To dequeue a message, specify a message ID or a dequeue
// condition/correlation ID in the dequeue options, but do not
// specify both. If you want to dequeue in the queue's sort order,
// then do not specify either the message ID or dequeue
// condition/correlation ID in the dequeue options.
25241, 00000, "cannot change correlation ID from %s to %s without FIRST_MESSAGE option"
// *Cause: An attempt was made to change the correlation ID while using the
// NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.
// *Action: To use a correlation ID that is different from the previous
// dequeue call, reset the dequeuing position by using the
// FIRST_MESSAGE navigation option.
//
25242, 00000, "cannot change subscriber name from %s to %s without FIRST_MESSAGE option"
// *Cause: An attempt was made to change the subscriber name while using the
// NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.
// *Action: To use a subscriber name that is different from the previous
// dequeue call, reset the dequeuing position by using the
// FIRST_MESSAGE navigation option.
//
25243, 00000, "CONSUMER_NAME cannot be specified when dequeuing from exception queue %s.%s"
// *Cause: An attempt was made to dequeue from an exception queue by specifying
// the CONSUMER_NAME in the dequeue options. CONSUMER_NAME can only
// be specified when dequeuing from a normal queue created for multiple
// consumers.
// *Action: Specify only the message id in the dequeue options to dequeue a
// message from an exception queue.
//
25244, 00000, "dequeue index key not found, QUEUE %s, rowid %s"
// *Cause: An internal error was encountered. There may be an inconsistency in
// the queue table index.
// *Action: Contact your Oracle customer support representative. You may need
// to provide the trace file and information about reproducing the
// error.
//
//
25245, 00000, "agent name cannot be specified if address is a single-consumer queue or an exception queue"
// *Cause: The agent name for the agent in the LISTEN call was specified
// when the agent address was a single-consumer queue or an exception
// queue.
// *Action: Do not specify the agent name.
25246, 00000, "listen failed, the address %s is an 8.0 style exception queue"
// *Cause: An 8.0 style exception queue was specified in the agent-list for
// the LISTEN call.
// *Action: Specify a normal 8.0 style queue or an 8.1 style queue in the
// agent-list.
//
25247, 00000, "%s is not a recipient of specified message"
// *Cause: The consumer name specified in the dequeue options is not a
// recipient of the message specified by the message id.
// *Action: Ensure that the agent specified by the consumer name is a
// recipient of the message specified by the message id.
//
25248, 00000, "duplicate agent specified in the agent list"
// *Cause: An agent was specified more than once in the agent list of the
// LISTEN call.
// *Action: Remove the duplicate agent specification(s), and retry the call.
25249, 00000, "dequeue failed, dequeue not allowed for queue %s.%s"
// *Cause: An attempt was made to dequeue from a non-persistent queue.
// *Action: Dequeue from a different queue.
25250, 00000, "Cannot specify a remote recipient for the message"
// *Cause: A recipient for the message enqueued to a non-persistent queue
// had a non-local address.
// *Action: Do not specify the address field or specify the queue which
// is the target of the enqueue
25251, 00000, "exceeded maximum number of recipients for message"
// *Cause: An attempt was made to issue an ENQUEUE call that exceeded the
// the maximum number (1024) of recipients per message.
// *Action: Reduce the number of recipients to 1024 or less, and retry
// the call.
25252, 00000, "listen failed, the address %s is a non-persistent queue"
// *Cause: A non-persistent queue was specified as an address for an agent in
// the LISTEN call.
// *Action: Specify a normal queue as address for the agent, and retry the
// the LISTEN call.
25253, 00000, "listen failed, queue %s.%s is not enabled for dequeue"
// *Cause: An attempt was made to specify a queue that is not enabled for
// dequeue in a LISTEN call.
// *Action: Enable the queue for dequeue using START_QUEUE, and retry
// the LISTEN call.
25254, 00000, "time-out in LISTEN while waiting for a message"
// *Cause: The specified wait time has elapsed and there were no messages for
// any of the agents in the agent-list.
// *Action: Try the LISTEN call with an appropriate time-out.
25255, 00000, "incorrect subscription string %s"
// *Cause: An incorrect subscription string was specified with OCIRegister.
// *Action: Specify a subscription string using the [CONSUMER:]SCHEMA.QUEUE
// form.
25256, 00000, "consumer cannot be specified with a single-consumer queue or an exception queue "
// *Cause: An attempt was made to specify a consumer in the subscription
// string when registering for notification on a single-consumer
// queue or an exception queue.
// *Action: Do not specify the consumer in the subscription string.
25257, 00000, "consumer must be specified with a multi-consumer queue"
// *Cause: An attempt was made to register on a multi-consumer queue without
// specifying a consumer in the subscription string.
// *Action: Specify a consumer in the subscription string.
25258, 00000, "cannot register for notifications on an 8.0 style exception queue"
// *Cause: An attempt was made to specify an 8.0 style exception queue in the
// subscription string of OCIRegister.
// *Action: Specify a normal queue or a non-persistent queue.
25259, 00000, "cannot specify protocol for agent"
// *Cause: The user specified the protocol attribute for an agent in the
// agent list.
// *Action: Do not specify the protocol attribute of the agent object type.
/
25260, 00000, "AQ latch cleanup testing event"
// *Cause: N/A.
// *Action: event used for AQ statistics latch cleanup testing.
25261, 00000, "JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation"
// *Cause: AQ Propagator encountered a setting for JOB_QUEUE_PROCESSES that
// is insufficient for AQ propagation.
// *Action: Set the number of JOB_QUEUE_PROCESSES to at least 2 for AQ
// propagation.
25262, 00000, "agent name cannot be NULL if address is a multi-consumer queue"
// *Cause: The name for the agent in the LISTEN call was not specified
// when the agent address was a multi-consumer queue.
// *Action: Specify a non-NULL name for the agent.
/
25263, 00000, "no message in queue %s.%s with message ID %s"
// *Cause: An attempt was made to dequeue a message with a specific
// message ID, but no such message exists in the queue.
// *Action: Try dequeue again with a valid message ID.
25264, 00000, "cant get signature for this queue"
// *Cause: An attempt was made to dequeue the signature from this queue, which
// is not reciever non-repidiable.
// *Action: Try dequeue again without the get signature option
25265, 00000, "specified signature for a queue which does not support reciever non-repudiation"
// *Cause: An attempt was made to dequeue the message from a queue which
// does not support reciever non-repudiation, but the signature was
// specified for verification
// *Action: Try dequeue again without the signature
25266, 00000, "didnt try to dequeue by message id. with the signature"
// *Cause: The signature was specified for a queue, but the dequeue was not
// done by message id.
// *Action: Try dequeue again by message id.
25267, 00000, "didnt specify the signature for a reciever non-repudiable queue"
// *Cause: The signature was not specified for a reciever non-repudiable queue
// *Action: Try dequeue again along with the signature
25268, 00000, "didnt dequeue in browse mode with get signature option"
// *Cause: The dequeue was not performed in browse mode with get signature option
// *Action: Try dequeue again in browse mode
25269, 00000, "cant specify sognature with get signature option"
// *Cause: The signature is not required for the dequeue with get signature
// option
// *Action: Try dequeue again without the signature in dequeue options
25270, 00000, "sender info does not match with the actual sender of the message"
// *Cause: The sender info. and the message id. do not match
// *Action: Provide the right sender info.
// *Action: Try dequeue again without the signature in dequeue options
25271, 00000, "queue table not found for the given queue"
// *Cause: The queue table does not exist for the given queue
// *Action: Provide the right queue name
25272, 00000, "Signature does not exist for the given reciever and message id."
// *Cause: Signature does not exist for the given reciever and message id.
// *Action: Check the message id. and the reciever's information
25273, 00000, "AQ QMN process alternate cleanup event"
// *Cause: N/A.
// *Action: event used for AQ QMN alternate cleanup mode.
25274, 00000, "AQ Buffered Queue event"
// *Cause: N/A.
// *Action: event used for AQ Buffered Queue mode.
25275, 00000, "Test support for buffered queues"
// *Cause: internal use only
// *Action: none.
/
/ 25276-25320 Reserved for AQ administration callouts
/
25276, 00000, "table specified is not a queue table"
// *Cause: An invalid queue table name is specified.
// *Action: Check the dictionary views to see if the table is a queue table.
//
25277, 00000, "cannot grant or revoke object privilege on release 8.0 compatible queues"
// *Cause: An attempt was made to grant or revoke object privilege on
// release 8.0 style queues.
// *Action: Convert the release 8.0 compatible queue table to release 8.1
// compatible using DBMS_AQADM.MIGRATE_QUEUE_TABLE before granting
// or revoking object privilege.
//
25278, 00000, "grantee name cannot be NULL"
// *Cause: An attempt was made to specify NULL for the grantee parameter.
// *Action: Specify a valid grantee parameter.
//
25279, 00000, "dequeue as select not supported before 8.2"
// *Cause: Dequeue as select not supported before 8.2.
// *Action: Dont use select condition while dequeuing
25280, 00000, "complete sender information not provided to non-repudiate sender"
// *Cause: complete sender information not provided to non-repudiate sender
// *Action: Provide the complete sender information
25281, 00000, "complete reciever information not provided to non-repudiate reciever"
// *Cause: complete reciever information not provided to non-repudiate reciever
// *Action: Provide the complete reciever information
25282, 00000, "message id. not provided for non-repudiation"
// *Cause: message id. was not provided
// *Action: Provide the message id.
25283, 00000, "either agent's name or address needed for non-repudiation"
// *Cause: neither agent's name nor address provided for non-repudiation"
// *Action: Provide the agent info.
25284, 00000, "Invalid value %s for %s"
// *Cause: An Invalid value or NULL was specified for the parameter.
// *Action: Check the documentation for valid values.
25285, 00000, "Invalid value %s for array_mode"
// *Cause: An Invalid value or NULL was specified for the array_mode.
// *Action: Check the documentation for valid values.
25286, 00000, "Invalid number of elements in the message properties array"
// *Cause: Number of elements in the message properties array do not match the
// number of elements in the payload array.
// *Action: Create a message property array with one element (that
// applies for all the elements in the payload array) or
// create a message property array with the same number of elements as
// there are in the payload array.
25287, 00000, "Invalid value %s, %s should be non-negative"
// *Cause: An Invalid value or NULL was specified for the parameter.
// *Action: Specify a non negative integer.
25288, 00000, "AQ HTTP propagation encountered error, status-code %d, %s"
// *Cause: AQ propagation's HTTP request to the propagation servlet at the
// specified address encountered an error
// *Action: Specify a valid address in the connect string of the propagation
// destination dblink, the dblink user has the correct permissions,
// check if the AQ propagation servlet was properly installed.
25289, 00000, "Buffer Already Exists"
// *Cause: Buffer already exists for the specified queue.
// *Action: None
25290, 00000, "Cannot complete operation on queue %s with existing messages"
// *Cause: Queue already has messages. Cannot complete operation
// *Action: Truncate the queue before adding/dropping a buffer
25291, 00000, "Buffer does not exist for the specified queue"
// *Cause: Buffer does not exist for the specified queue
// *Action: Operation on the buffer cannot be performed. create the buffer
25292, 00000, "Buffer operations are not supported on the queue"
// *Cause: Buffer operations are not supported on the specified queue type
// *Action: Buffered operations are only supported on to 8.1 style
// queues, which do not have transaction grouping.
25293, 00000, "Lob attributes must be null for buffered operations"
// *Cause: Enqueue of a buffered message with a non-null lob attribute was attempted
// *Action: Set the lob attributes to null before enqueuing the buffered message
25294, 00000, "Cannot propagate user buffered messages to a database with version lower than 10.2"
// *Cause: Propagation of user buffered messages was attempted to a database with version lower than 10.2.
// *Action: Do not propagate buffered messages to the database.
25295, 00000, "Subscriber is not allowed to dequeue buffered messages"
// *Cause: Subscriber is only allowed to dequeue persistent messages
// *Action: Drop the subscriber and re-create it, or dequeue only persistent messages for the subscriber
25296, 00000, "Queue Table %s has a buffered queue %s"
// *Cause: Cannot downgrade the queue table because it has a buffered queue
// *Action: Drop the buffer or the buffered queue
//25297, 00000, "Enqueue of buffered message failed, attempted to enqueue buffered message with %s"
// *Cause: Buffered message was enqueued by specifying delay or sequence deviation.
// *Action: Do not specify delay of sequence deviation when enqueuing buffered messages.
25298, 00000, "Only immediate visibility mode supported for buffered message enqueue or dequeue"
// *Cause: A visibility of dbms_aq.ON_COMMIT was supplied with the buffered message enqueue or dequeue
// *Action: Supply a visibility of dbms_aq.IMMEDIATE
25299, 00000, "Invalid message delivery_mode "
// *Cause: Invalid value was specified for delivery mode
// *Action: Specify dbms_aq.BUFFERED or dbms_aq.PERSISTENT during Enqueue or dbms_aq.BUFFERED, dbms_aq.PERSISTENT or dbms_aq.PERSISTENT_OR_BUFFERED during Dequeue and Listen.
25300, 00000, "Cannot drop buffer for queue with buffered subscribers"
// *Cause: Cannot drop buffer for queue with buffered subscribers
// *Action: Either drop buffered subscribers or forcibly drop the buffer
25301, 00000, "Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2"
// *Cause: Enqueue or dequeue of user buffered messages was attempted to queues in a database with version lower than 10.2.
// *Action: Do not attempt to enqueue or dequeue user buffered messages.
25302, 00000, "Operation not possible for non-buffered queue %s"
// *Cause: Last enqd/ackd message is only supported for buffered queues
// *Action: The operation is not supported.
25303, 00000, "Buffered operation allowed only on the owner instance"
// *Cause: Operation was not performed on the owner instance.
// *Action: Perform operation on the owner instance.
25304, 00000, "Cannot use priority order queues for capture LCRs"
// *Cause: Capture LCRs can only use commit time or enqueue time ordered queues.
// *Action: Use the appropriate type of queue for captured LCRs.
25305, 00000, "enqueue failed, expiration must be zero for queue %s.%s"
// *Cause: An attempt was made to enqueue to a buffered
// queue with expiration greater than zero seconds.
// *Action: Set expiration to zero.
/
25306, 00000, "Cannot connect to buffered queue's owner instance"
// *Cause: cannot connect to the owner instance of the buffered queue
// *Action: set listener information in REMOTE_LISTENERS or LOCAL_LISTENERS initialization parameter.
/
25307, 00000, "Enqueue rate too high, flow control enabled"
// *Cause: Subscribers could not keep pace with the enqueue rate.
// *Action: Try enqueue after waiting for some time.
25308, 00000, "AQ canonicalization event"
// *Document: NO
// *Cause:
// *Action:
/
25309, 00000, "Unable to lock deq IOT, skip retry count increment"
//*Document: NO
// *Cause:
// *Action:
/
25310, 00000, "Subscriber is Notification only; dequeue not supported"
// *Cause: Notification only subscribers are not allowed to dequeue.
// *Action: Recreate subscriber if necessary.
/
25311, 00000, "%s not supported for non-persistent queue"
// *Cause: Specified QOS is not supported for non-persistent queues.
// *Action: Specify the right QOS.
/
25312, 00000, "Cannot specify nonzero sender protocol"
//*Document: Yes
// *Cause: Sender protocol was specified during an enqueue operation.
// *Action: Specify the enqueue sender protocol as null or zero.
/
25313, 00000, "a queue may not subscribe to itself for propagation"
// *Cause: The specified subscriber had a NULL name and an address equal to
// the queue name.
// *Action: Provide a valid subscriber and retry the operation.
/
25314, 00000, "a commit-time queue table cannot be migrated to 8.0"
// *Cause: An attempt was made to migrate a commit-time queue table to an
// unsupported compatibility level.
// *Action: Provide an appropriate compatibility level, and retry the
// operation.
/
25315, 00000, "unsupported configuration for propagation of buffered messages"
// *Cause: An attempt was made to propagate buffered messages with the
// database link pointing to an instance in the destination database
// which is not the owner instance of the destination queue.
// *Action: Use queue to queue propagation for buffered messages.
/
25316, 00000, "Late in the current transaction to begin an Enqueue/Dequeue operation"
// *Cause: Check if the Enqueue/Dequeue operation is performed via triggers
// on Materialized Views which isn't supported.
// *Action: Triggers on materialized views aren't supported. Workarounds are
// on-demand materialized views or execution of trigger code
// within an autonomous txn.
/
25317, 00000, "Propagation stopped because of instance shutdown"
// *Cause: A propagation job has stopped because the instance is
// shutting down.
// *Action: No user action is required.
/
25318, 00000, "Propagation stopped because of instance affinity change"
// *Cause: A propagation job has stopped because its instance affinity
// has changed.
// *Action: No user action is required. The job will restart on the
// appropriate instance.
/
25319, 00000, "Queue table repartitioning aborted"
// *Cause: During instance restart in an Oracle RAC environment, queue table
// repartitioning aborted due to errors.
// *Action: Look at the incident generated for this error and report the
// problem to Oracle Support Services.
/
25320, 00000, "Failed to create, alter, or remove Subscriber"
// *Cause: There is a pending enqueue or dequeue operation on
// this queue from the same session.
// *Action: Either COMMIT or ROLLBACK pending enqueue or dequeue operation
// before attempting to create, alter, or remove the subscriber.
/
/ 25321-25325 Reserved for enq/deq user properties
/
25321, 00000, "enqueue failed, user property specified but queue %s.%s is not an 8.1 style queue"
// *Cause: user properties can only be specified when enqueueing into 8.1
// style queues.
// *Action: Specify an 8.1 style queue or pass user property as NULL.
/
25322, 00000, "message priority is out of range"
// *Cause: The message priority range of 0 to 9 was exceeded.
// *Action: Set the message priority in the range of 0 to 9.
/
/ 25326-25350 Reserved for AQ Array/Miscellaneous Errors
/
25326, 00000, "Array %s operation failed for message at index %s"
// *Cause: Array operation fails for the message at specified index. Look
// at the remainder of the error stack to see what the problem was.
// *Action: Fix cause of error and retry array operation.
25327, 00000, "Array size is invalid"
// *Cause: Array size must be a positive, non-zero integer.
// *Action: Use corrected array size and retry array operation.
25328, 00000, "%s argument size %s is smaller than array size"
// *Cause: The size of the argument is smaller than the given array size.
// *Action: Lower array size or use a larger sized input argument.
25329, 00000, "AQ array operations not allowed on 8.0 queues"
// *Cause: An array enqueue/dequeue was attempted on an 8.0 queue.
// *Action: Use single enqueue/dequeue with this queue.
25330, 00000, "PL/SQL associative arrays may not be used with AQ array operations"
// *Cause: A PL/SQL associative array was provided for the payload parameter
// in an enqueue/dequeue array operation.
// *Action: Use VARRAY or NESTED TABLE types with AQ array operations.
25331, 00000, "cannot downgrade because there are commit-time queue tables"
// *Cause: An attempt was made to downgrade a database that has commit-time
// queue tables.
// *Action: Drop all commit-time queue tables before attempting the downgrade.
25332, 00000, "Invalid release value %s for queue table compatible parameter"
// *Cause: The release level given for the queue table compatible parameter
// is invalid
// *Action: Specify a valid release value for the queue table compatible
// parameter
25333, 00000, "Buffered Queue to Queue propagation did not connect to the correct instance"
// *Cause: Queue to Queue propagation for buffered messages didn't
// connect to the correct instance, most likely because service was
// not started for the destination queue.
// *Action: No user action is required. Propagation will start the service for
// the destination queue and retry.
25334, 00000, "Buffered propagation must restart as the destination queue was recreated/moved"
// *Cause: Buffered propagation destination queue was recreated or its
// ownership was moved to another instance during propagation.
// *Action: No user action is required. Propagation will reinitialize its
// metadata and retry.
25335, 00000, "AQ array operations not allowed for buffered messages"
// *Cause: An array enqueue/dequeue was attempted for buffered messages
// *Action: Use single enqueue/dequeue for buffered messages or an array
// size of one.
25336, 00000, "Cannot contact instance %s during Streams AQ operation"
// *Cause: The specified instance was not responding to AQ requests.
// *Action: Set parameter aq_tm_processes to a non-zero value. If the problem
// persists, contact Oracle Support Services.
25337, 00000, "Cannot propagate in queue-to-queue mode to a database with version lower than 10.2"
// *Cause: Remote subscriber with queue_to_queue mode set to TRUE was added.
// The remote subscriber is on a database version lower than 10.2.
// Propagation was scheduled to a destination database with version
// lower than 10.2.
// *Action: Remove the remote subscriber with queue_to_queue mode and add the
// subscriber back with queue_to_queue set to FALSE. Unschedule the
// queue-to-queue propagation and schedule propagation in
// queue-to-dblink mode.
25338, 00000, "operation '%s' is not allowed for sync_capture '%s'"
// *Cause: An attempt was made to execute the specified operation for a
// sync_capture process.
// *Action: Remove the offending call.
25339, 00000, "STREAMS '%s' must be sync_capture"
// *Cause: The specified capture STREAMS did not exist or was not a
// sync_capture process.
// *Action: Remove the offending call.
25340, 00000, "must use commit-time queue for sync_capture"
// *Cause: An attempt was made to create a sync_capture without using
// a commit-time queue.
// *Action: Rerun statement with a commit-time queue.
25341, 00000, "sync_capture does not support \"%s\".\"%s\" because of the following reason:"
// *Cause: sync_capture encountered a table with an unsupported
// property. The most common reason is an unsupported column
// data type.
// *Action: Revise the Capture rules to skip over the table in
// question. One option is to remove the rule that captures changes
// from the unsupported table. Check DBA_STREAMS_TABLE_RULES to
// determine the rule on the table specified in the error.
//
// Also query the DBA_STREAMS_UNSUPPORTED view to determine
// which tables are not supported by STREAMS and for what
// reason.
//
// For potential workarounds to certain unsupported properties, see
// Metalink.
25342, 00000, "cannot downgrade because there are apply processes for user buffered messages"
// *Cause: An attempt was made to downgrade a database that has apply process
// for user-buffered messages.
// *Action: Drop all the apply processes for user-buffered messages before
// attempting the downgrade.
25343, 00000, "Streams error queue cannot be exported"
// *Cause: An attempt was made to export a database that has apply errors.
// *Action: Delete or reexecute errors before attempting the export.
25344, 00000, "statement has bind variables"
// *Cause: Current API could not handle a statement with bind variables.
// *Action: Use alternative API which handles bind variables.
25345, 00000, "requested AQ minimum Oracle Streams Pool size %s greater than Oracle Streams Pool size %s"
// *Cause: The minimum value requested for the Oracle Streams Advanced
// Queuing (AQ) pool size was greater than the Oracle Streams pool
// size.
// *Action: Set the minimum value for the Oracle Streams AQ pool size to
// less than or equal to the Oracle Streams pool size.
25346, 00000, "requested AQ maximum Oracle Streams Pool size %s less than AQ minimum Oracle Streams Pool size %s"
// *Cause: The maximum value requested for the Oracle Streams Advanced
// Queuing (AQ) pool size was less than the minimum value of the
// Oracle Streams (AQ) pool size.
// *Action: Set the maximum value for the Oracle Streams AQ pool size to
// greater than or equal to the minimum value of the Oracle
// Streams AQ pool size.
25347, 00000, "Dequeue operation on sharded queue is not possible."
// *Cause: Dequeue of a buffered subscriber or JMS sharded queue failed
// with OCIAQDeq().
// *Action: Use OCIAQDeq2() for buffered subscribers and JMS sharded queues.
25348, 00000, "This AQ operation can be performed only at instance %s of database %s."
// *Cause: An Advanced Queuing (AQ) operation was attempted at wrong
// database instance.
// *Action: Please connect to the suggested database instance and retry
// the operation.
/
/ 25350-25375 Reserved for V8 Transaction OCI
/
25350, 00000, "maximum number of concurrent transaction branches exceeded"
// *Cause: the limit on the number of concurrent transaction branches has
// been reached
// *Action: Increase the INIT.ORA parameter 'transactions' and restart the
// system.
25351, 00000, "transaction is currently in use"
// *Cause: The transaction is currently used by a different session.
// *Action: Do not switch to a transaction attached to some other session.
25352, 00000, "no current transaction"
// *Cause: The user session is not attached to any transaction.
// *Action: Do not attempt to detach when there is no current transaction.
25353, 00000, "branch marked for deletion"
// *Cause: The branch specified cannot be killed immediately because another
// session is using the branch, but it has been marked for kill. This
// means it will be deleted as soon as possible after the current
// uninterruptable operation is completed.
// *Action: No action is required for the branch to be deleted.
/
/ 25400-25425 Reserved for Application Failover
/
25400, 00000, "must replay fetch"
// *Cause: A failure occured since the last fetch on this statement. Failover
// was able to bring the statement to its original state to allow
// continued fetches.
// *Action: This is an internally used error message and should not be seen
// by the user.
25401, 00000, "can not continue fetches"
// *Cause: A failure occured since the last fetch on this statement. Failover
// was unable to bring the statement to its original state to allow
// continued fetches.
// *Action: Reexecute the statement and start fetching from the beginning
25402, 00000, "transaction must roll back"
// *Cause: A failure occured while a transaction was active on this
// connection.
// *Action: The client must roll back.
//
25403, 00000, "could not reconnect"
// *Cause: The connection to the database has been lost, and attempts to
// reconnect have failed.
// *Action: Manually reconnect.
//
25404, 00000, "lost instance"
// *Cause: The primary instance has died.
// *Action: This is an internally used error message and should not be seen
// by the user.
//
25405, 00000, "transaction status unknown"
// *Cause: A failure occured while a transaction was attempting to commit.
// Failover could not automatically determine instance status.
// *Action: The user must determine the transaction's status manually.
25406, 00000, "could not generate a connect address"
// *Cause: Failover was unable to generate an address for a backup instance.
// *Action: Contact Oracle customer support.
//
25407, 00000, "connection terminated"
// *Cause: The connection was lost while doing a fetch.
// *Action: This is an internally used error message and should not be seen
// by the user.
//
25408, 00000, "can not safely replay call"
// *Cause: The connection was lost while doing this call. It may not be
// safe to replay it after failover.
// *Action: Check to see if the results of the call have taken place, and then
// replay it if desired.
//
25409, 00000, "failover happened during the network operation,cannot continue"
// *Cause: The connection was lost when fetching a LOB column.
// *Action: Failover happened when fetching LOB data directly or indirectly.
// Please replay the top level statement.
/ do NOT translate or document message 25410 - it is never displayed
// NLS_DO_NOT_TRANSLATE [25410,25410]
25410,00000, "Application requested failover retry"
// *Cause: The application failover callback requested failover retry.
// *Action: None. Informational only.
25411,00000, "transaction replay was not successful"
// *Cause: Replay was not able to restore the transaction state to match
// the pre-failover state.
// *Action: Manually determine if it is safe to resubmit the transaction.
25412,00000, "transaction replay disabled by call to %s"
// *Cause: The application called an Oracle Call Interface (OCI) function
// that is not supported with transactional failover.
// *Action: Manually recover the pending transaction.
25413,00000, "transaction replay disabled by user request"
// *Cause: The application explicitly disabled transaction replay by
// setting attribute OCI_ATTR_TRANSACTIONAL_TAF=FALSE.
// *Action: This message is informational only.
25414,00000, "Uncommitted transaction detected after TAF callback."
// *Cause: The Transparent Application Failover (TAF) callback started a
// transaction and did not commit or rollback prior to exiting.
// *Action: End the transaction with a COMMIT or a ROLLBACK prior to
// exiting the TAF callback.
25415,00000, "Application Continuity replay initiation timeout exceeded."
// *Cause: Application Continuity replay was attempted after
// REPLAY_INITIATION_TIMEOUT expired. The value for
// REPLAY_INITIATION_TIMEOUT is configured for the service to which
// the application is connected.
// *Action: Manually recover the pending transaction.
/ do NOT translate or document message 25416 - it is never displayed
// NLS_DO_NOT_TRANSLATE [25416,25416]
25416,00000, "Retry current call"
// *Cause: Failover sucessfully recovered an in-flight transaction
// *Action: Re-execute the current call
25417,00000, "replay disabled; call (%s) too large to record"
// *Cause: Oracle Call Interface (OCI) Application Continuity replay was
// attempted after a large call that could not be recorded due
// to excessive memory requirements.
// *Action: Break up the call into smaller pieces and retry failover, or
// manually retry the user operation.
25418,00000, "transaction replay disabled by the use of object type in function %s"
// *Cause: The application used an Oracle Call Interface (OCI) object
// type that is not supported with transactional failover.
// *Action: Manually recover the pending transaction.
25419,00000, "transaction replay disabled in function %s by the use of unsupported type %s"
// *Cause: The application used an Oracle Call Interface (OCI)
// type that is not supported with transactional failover.
// *Action: Manually recover the pending transaction.
25420, 0000, "too many calls in request; replay disabled"
// *Cause: Application Continuity failover was attempted after executing
// a request with a large number of Oracle Call Interface (OCI)
// calls, so replay of the request was not possible.
// *Action: Resubmit and consider partitioning application work into
// more requests with fewer OCI calls in each request.
//
25425, 00000, "connection lost during rollback"
// *Cause: The connection was lost while issuing a rollback and the
// application failed over.
// *Action: The connection was lost and failover happened during rollback.
// If the transaction is not externally coordinated, then Oracle
// implicitly rolled back, so no action is required. Otherwise
// examine pending_trans$ to determine if "rollback force" is
// required.
/
/ 25426-25435 Reserved for Dblink Concentration
/
25426, 00000, "remote instance does not support shared dblinks"
// *Cause: A shared dblink is being used to connect to a remote instance
// that does not support this feature because it is an older version.
// *Action: Use a normal dblink if you need to connect to this instance.
/
25427, 00000, "cannot downgrade database links after database link data dictionary has been upgraded "
// *Cause: An attempt was made to downgrade after the upgrade of the
// database link data dictionary.
// *Action: Drop the database links before attempting the downgrade.
/
25428, 00000, "authentication failure while connecting through database link"
// *Cause: An attempt to connect using the database link failed.
// *Action: Ensure connection details for the database link are correct.
/
25429,00000, "Break request cannot be propagated over shared database link."
// *Cause: No call in progress over shared database link.
// *Action: No action required. This is an informational message only.
/
25430,00000, "connected user database links are not supported in proxy session"
// *Cause: A connected user database link is being used to connect to a
// remote database from a proxy user session.
// *Action: No action required. This was an informational message only.
/
25431,00000, "Connection with protocol %s is disallowed by the outbound_dblink_protocols parameter."
// *Cause: An attempt to connect using the database link failed
// because the network protocol used for the database link
// is disallowed.
// *Action: Either set the value of the outbound_dblink_protocols
// initialization parameter appropriately to include the required
// protocol or change the protocol used by the database link to
// conform to the protocols allowed by the outbound_dblink_protocols
// parameter.
/
25432,00000, "database link log on info tracing"
// *Document: NO
// *Cause:
// *Action:
/
25433,00000, "User %s does not have INHERIT REMOTE PRIVILEGES privilege on connected user %s."
// *Cause: An attempt was made to use a connected user database link inside
// a definer's rights function, procedure or view, and the owner
// of the function, procedure or view lacked INHERIT REMOTE PRIVILEGES
// privilege on the connected user.
// *Action: Either do not start the function, procedure or view,
// or grant the owner of the function, procedure or view
// INHERIT REMOTE PRIVILEGES privilege on the connected user.
/
25434,00000, "Connected user database link usage by the common user %s is not allowed."
// *Cause: The COMMON_SCHEMA_ACCESS lockdown profile feature was disabled.
// *Action: Either do not use the database link as a common user
// or have the administrator enable COMMON_SCHEMA_ACCESS lockdown
// profile feature.
/
/ 25436-25476 Reserved for Rules Engine
/
25436, 00000, "invalid table alias: %s"
// *Cause: An attempt to evaluate was made, which failed because
// one of the table values specified had an invalid alias.
// *Action: Check the valid table aliases in the evaluation context,
// and try again with a valid alias.
25437, 00000, "duplicate table value for table alias: %s"
// *Cause: An attempt to evaluate was made, which failed because
// some of the table values specified had the same table alias.
// *Action: Check the table values specified, and try again with only
// one value per table.
25438, 00000, "invalid variable name: %s"
// *Cause: An attempt to evaluate was made, which failed because
// one of the variable values specified had an invalid name.
// *Action: Check the valid variable names in the evaluation context,
// and try again with a valid name.
25439, 00000, "duplicate variable value for variable: %s"
// *Cause: An attempt to evaluate was made, which failed because
// some of the variable values specified had the same variable name.
// *Action: Check the variable names specified, and try again with only
// one value per variable.
25440, 00000, "invalid table alias: %s"
// *Cause: An attempt to evaluate was made, which failed because
// one of the column values specified had an invalid table alias.
// *Action: Check the valid table aliases in the evaluation context,
// and try again with a valid name.
25441, 00000, "duplicate column value for table alias: %s"
// *Cause: An attempt to evaluate was made, which failed because
// one of the column values supplied a value for a
// table alias, which already had a table value supplied.
// *Action: Check the table and column values specified, and try again with
// either a table value or column values for each table alias.
25442, 00000, "too many column values for table alias: %s"
// *Cause: An attempt to evaluate was made, which failed because
// too many column values were supplied for the specified
// table alias.
// *Action: Check the column values specified, and try again with
// the right number of column values.
25443, 00000, "duplicate column value for table alias: %s, column number: %s"
// *Cause: An attempt to evaluate was made, which failed because
// duplicate column values were supplied for the specified
// table alias and column number.
// *Action: Check the column values specified, and try again with
// only one column value for each table alias, and column number.
25444, 00000, "invalid ROWID: %s for table alias: %s"
// *Cause: An attempt to evaluate was made, which failed because
// an invalid ROWID was supplied for the specified
// table alias.
// *Action: Check the column values specified, and try again with
// only one column value for each table alias, and column number.
25445, 00000, "invalid column number: %s for table alias: %s"
// *Cause: An attempt to evaluate was made, which failed because
// an invalid column number was supplied for the specified
// table alias as a part of a column value.
// *Action: Check the column values specified, and try again with
// a valid column number.
25446, 00000, "duplicate column value for table alias: %s, column: %s"
// *Cause: An attempt to evaluate was made, which failed because
// duplicate column values were supplied for the specified
// table alias and column name.
// *Action: Check the column values specified, and try again with
// only one column value for each table alias, and column name.
25447, 00000, "encountered errors during evaluation of rule %s.%s"
// *Cause: An attempt to evaluate was made, which failed during the
// evaluation of the specified rule.
// *Action: Check the rule and the values passed to evaluate, and try
// again with valid values.
25448, 00000, "The %s %s.%s has errors."
// *Cause: An attempt to load the specified rule or expression failed due
// to errors in the rule or expression.
// *Action: Check the rule or expression and retry the operation.
25449, 00000, "invalid variable name: %s"
// *Cause: An attempt to evaluate was made, which failed because
// one of the attribute values specified had an invalid
// variable name.
// *Action: Check the valid variable names in the evaluation context,
// and try again with a valid name.
25450, 00000, "error %s during evaluation of rule set %s.%s"
// *Cause: The specified error occurred during evaluation of the
// rule set.
// *Action: Check the error and take appropriate action.
25451, 00000, "too many attribute values for variable: %s"
// *Cause: An attempt to evaluate was made, which failed because
// too many attribute values were supplied for the specified
// variable.
// *Action: Check the attribute values specified, and try again with
// the right number of attribute values.
25452, 00000, "duplicate attribute value for variable: %s, attribute: %s"
// *Cause: An attempt to evaluate was made, which failed because
// duplicate attribute values were supplied for the specified
// variable and attribute name.
// *Action: Check the attribute values specified, and try again with
// only one attribute value for each variable, and attribute name.
25453, 00000, "invalid iterator: %s"
// *Cause: An attempt to get rule hits or to close an iterator was made,
// which failed because an invalid iterator was passed in.
// *Action: Check the iterator, and try again with a valid iterator.
25454, 00000, "error during evaluation of rule set: %s.%s for iterator: %s"
// *Cause: An attempt to get rule hits for an iterator was made,
// which failed because of an error in evaluation of the specified
// rule set.
// *Action: Check the validity of the rule set and try again.
25455, 00000, "evaluation error for rule set: %s.%s, evaluation context: %s.%s"
// *Cause: An attempt to evaluate the specified rule set using the
// evaluation context specified failed due to some errors.
// *Action: Check additional errors signalled to determine the problem.
25456, 00000, "rule set was modified or evaluation terminated for iterator: %s"
// *Cause: An attempt to get rule hits was made, which failed because
// the underlying rule set was modified after the iterator was
// returned.
// *Action: Try again after re-evaluating the rule set.
25457, 00000, "evaluation function %s returns failure"
// *Cause: The specified evaluation function returned a failure during
// evaluation, causing evaluation to terminate.
// *Action: Check arguments to evaluate and retry.
25458, 00000, "Value not supplied for %s %s"
// *Cause: Variable or table column values were not supplied for evaluation.
// *Action: Supply all the required variable and column data points for
// Independent Expression Evaluation.
25459, 00000, "Data conversion for %s %s failed"
// *Cause: The attempt to convert data to the data type of the variable or
// column failed.
// *Action: Supply the correct data for variable or column.
25461, 00000, "rule set not specified"
// *Cause: An attempt to evaluate was made, which failed because
// the ruleset name specified was null.
// *Action: Check the rule set name, and try again with a valid name.
25462, 00000, "evaluation context not specified"
// *Cause: An attempt to evaluate was made, which failed because
// the evaluation context specified was null.
// *Action: Check the evaluation context name, and try again with a
// valid name.
25463, 00000, "table alias not specified"
// *Cause: An attempt to evaluate was made, which failed because
// one of the table values specified had a NULL alias name.
// *Action: Check the list of table values, and try again with a
// valid alias name.
25464, 00000, "ROWID not specified for table alias: %s"
// *Cause: An attempt to evaluate was made, which failed because
// the table value for the specified table alias had a NULL ROWID.
// *Action: Check the list of table values, and try again with a
// valid ROWID.
25465, 00000, "variable name not specified"
// *Cause: An attempt to evaluate was made, which failed because
// one of the variable values specified had a NULL variable name.
// *Action: Check the list of variable values, and try again with a
// valid variable name.
25466, 00000, "data not specified for variable name: %s"
// *Cause: An attempt to evaluate was made, which failed because
// the variable value for the specified variable name had NULL
// data.
// *Action: Check the list of variable values, and try again with
// valid data.
25467, 00000, "table alias not specified"
// *Cause: An attempt to evaluate was made, which failed because
// one of the column values specified had a NULL alias name.
// *Action: Check the list of column values, and try again with a
// valid alias name.
25468, 00000, "column name not specified for alias: %s"
// *Cause: An attempt to evaluate was made, which failed because
// one of the column values for the specified alias name
// had a NULL column name.
// *Action: Check the list of column values, and try again with a
// valid column name.
25469, 00000, "data not specified for alias: %s column name: %s"
// *Cause: An attempt to evaluate was made, which failed because
// the column value for the specified alias and column name
// had NULL data.
// *Action: Check the list of column values, and try again with
// valid data.
25470, 00000, "duplicate attribute value for variable: %s"
// *Cause: An attempt to evaluate was made, which failed because
// one of the attribute values supplied a value for a
// variable, which already had a variable value supplied.
// *Action: Check the variable and attribute values specified,
// and try again with either a variable value or
// attribute values for each variable.
25471, 00000, "attribute name not specified for variable: %s"
// *Cause: An attempt to evaluate was made, which failed because
// one of the attribute values for the specified variable
// had a NULL attribute name.
// *Action: Check the list of attribute values, and try again with a
// valid attribute name.
25472, 00000, "maximum open iterators exceeded"
// *Cause: The open rule hit iterators in the session exceeded
// 2 * OPEN_CURSORS.
// *Action: Close some rule hit iterators.
//
25473, 00000, "cannot store %s in rule action context"
// *Cause: The user attempted to put unsupported data types, such as LOBs
// and evolved ADTs, into the rule action context.
// *Action: Use only supported data types in rule action context.
/ 25474 is reserved for dumping info
/ 25475 is reserved for debug mode
25476, 00000, "use pre-5523578 behaviour when looking up enabled roles"
// *Cause: N/A
// *Action: Derive the enabled roles under the rules engine using the old
// method that existed before the fix to bug 5523578.
/
/
/ 25500-25525 Reserved for Quiesce Database Feature Errors
/
25500, 00000, "database is not open"
// *Cause: Database must be open to perform ALTER SYSTEM QUIESCE RESTRICTED
// command.
// *Action: Open the database and retry this command.
25501, 00000, "ALTER SYSTEM QUIESCE RESTRICTED command failed"
// *Cause: Database resource manager failed to change plan.
// *Action: Look at the alert logs to see detailed description of the error.
25502, 00000, "concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running"
// *Cause: There is a concurrent ALTER SYSTEM QUIESCE RESTRICTED or ALTER
// SYSTEM UNQUIESCE command running in the system.
// *Action: Contact the database administrator who is responsible for the
// concurrent command.
25503, 00000, "cannot open database because the database is being quiesced"
// *Cause: Database cannot be opened because the system is being or has
// been quiesced.
// *Action: Open the database after the system has been quiesced.
25504, 00000, "the system is already in quiesced state"
// *Cause: Cannot quiesce the system because the system is already quiesced.
// *Action:
25505, 00000, "the system is not in quiesced state"
// *Cause: Cannot unquiesce the system because the system is not in quiesced
// state.
// *Action:
25506, 00000, "resource manager has not been continuously on in some instances"
// *Cause: Cannot quiesce the system because resource manager has not been
// continuously on since startup in this or some other instances.
// *Action:
25507, 00000, "resource manager has not been continuously on"
// *Cause: Cannot quiesce the system because resource manager has not been
// continuously on since startup.
// *Action:
25508, 00000, "database is not mounted"
// *Cause: Database must be mounted to perform ALTER SYSTEM UNQUIESCE
// command.
// *Action: Mount the database and retry this command.
25509, 00000, "operation on \"%s\".\"%s\".%s not allowed"
// *Cause: A column has been added to a replicated table, but replication
// support processing has not completed.
// *Action: Wait until replication support processing has completed
// before updating the column
25510, 00000, "quiesce not supported for the root container"
// *Cause: Could not quiesce the root container.
// *Action: This operation is not supported for the root container.
25511, 00000, "quiesce not supported for pluggable databases"
// *Cause: Could not quiesce the pluggable database.
// *Action: This operation is not supported for pluggable databases.
/
/ 25526-25550 Reserved for MTTR advisory
/
25526, 00000, "bad format of _DB_MTTR_SIM_TARGET: %s"
// *Cause: One value in _DB_MTTR_SIM_TARGET is not a valid MTTR.
// *Action: Alter the value of _DB_MTTR_SIM_TARGET.
25527, 00000, "bad format of _DB_MTTR_SIM_TARGET"
// *Cause: One value in _DB_MTTR_SIM_TARGET is empty.
// *Action: Set the value of _DB_MTTR_SIM_TARGET properly.
25528, 00000, "too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET"
// *Cause: Too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET.
// *Action: Alter the value of _DB_MTTR_SIM_TARGET.
25530, 00000, "FAST_START_MTTR_TARGET is not specified"
// *Cause: An attempt to start MTTR advisory was made, which failed because
// FAST_START_MTTR_TARGET was not specified.
// *Action: Set FAST_START_MTTR_TARGET.
25531, 00000, "MTTR specified is too small: %s"
// *Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR
// setting is too small for MTTR advisory.
// *Action: Set a larger FAST_START_MTTR_TARGET or candidate MTTR.
25532, 00000, "MTTR specified is too large: %s"
// *Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR
// setting is too large for MTTR advisory.
// *Action: Set a smaller FAST_START_MTTR_TARGET or candidate MTTR.
25533, 00000, "FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified"
// *Cause: An attempt to start MTTR advisory was made, which failed because
// either FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL was
// specified.
// *Action: Set FAST_START_IO_TARGET and LOG_CHECKPOINT_INTERVAL to 0.
/
/ 25950-25999 Reserved for Join Index Errors
/
25950, 00000, "missing where clause in join index specification\n"
// *Cause: An attempt to create a join index was made, which failed
// because no valid where clause was found.
// *Action: Ensure that a where clause with valid join conditions is
// specified in the create index statement.
25951, 00000, "join index where clause cannot contain OR condition\n"
// *Cause: An attempt to create a join index was made, which failed
// because there was an OR branch in the where clause.
// *Action: Reformulate the where clause without using ORs.
25952, 00000, "join index must only contain inner equi-joins\n"
// *Cause: An attempt to create a join index was made, which failed
// because it included a predicate which wasn't an equi-inner join.
// *Action: Remove the inappropriate predicate.
25953, 00000, "join index cannot be a functional index\n"
// *Cause: An attempt to create a join index was made, which failed
// because a functional index was requested or necessary (such as
// is the case for indexing columns using timezone).
// *Action: Remove any functional indexing columns.
25954, 00000, "missing primary key or unique constraint on dimension\n"
// *Cause: An attempt to create a join index was made, which failed
// because one or more dimensions did not have an appropriate
// constraint matching the join conditions.
// *Action: Ensure that the where clause is correct (contains all of the
// constraint columns) and that an enforced constraint is on
// each dimension table.
25955, 00000, "all tables must be joined in the where clause\n"
// *Cause: An attempt to create a join index was made, which failed
// because one of the tables in the from clause did not appear
// in the where clause.
// *Action: Ensure that the where clause contains all from clause tables.
25956, 00000, "join index cannot be created on tables owned by SYS\n"
// *Cause: An attempt to create a join index was made, which failed
// because one of the tables was owned by SYS.
// *Action: Ensure that no join index related table is owned by SYS.
25957, 00000, "join index where clause cannot contain cycles\n"
// *Cause: An attempt to create a join index was made, which failed
// because the where clause contains a cycle.
// *Action: Ensure that the where clause is in the form of a star
// or snowflake schema.
25958, 00000, "join index where clause predicate may only contain column references\n"
// *Cause: An attempt to create a join index was made, which failed
// because a predicate in the where clause contained something
// other than a simple column.
// *Action: Ensure that the where clause only contains columns.
25959, 00000, "join index must be of the bitmap type\n"
// *Cause: An attempt to create a join index was made, which failed
// because no bitmap keyword was used.
// *Action: Make the index a bitmap index.
25960, 00000, "join index cannot be based on a temporary table\n"
// *Cause: An attempt to create a join index was made, which failed
// because one of the tables was temporary.
// *Action: Ensure no underlying tables are temporary.
25961, 00000, "join index prevents dml cascade constraint operation\n"
// *Cause: An attempt to execute dml resulted in the need to perform
// dml on another table because of a cascade constraint.
// The join index only allows one of its underlying tables
// to me modified at a time.
// *Action: Drop the join index or remove the constraint.
25962, 00000, "join index prevents multitable insert or merge\n"
// *Cause: An attempt to execute an merge or multitable insert on
// a table that was used to create a bitmap join index was made.
// Merge and multitable inserts are not supported on tables
// that were used to create a bitmap join index.
// *Action: Drop the join index.
25963, 00000, "join index must be created on tables\n"
// *Cause: An attempt to create a join index was made, which failed
// because the from clause contains non table object.
// *Action: Ensure that the from clause only contains tables.
25964, 00000, "column type incompatible with join column type\n"
// *Cause: The datatype of the join column is incompatible with the
// datatype of the joined column.
// *Action: Select a compatible datatype for the join column.
25965, 00000, "fact table must be included in the from clause\n"
// *Cause: An attempt to create a join index was made, which failed
// because the from clause does not contain the fact table.
// *Action: Ensure that the from clause contains the fact table.
25966, 00000, "join index cannot be based on an index organized table\n"
// *Cause: An attempt to create a join index was made, which failed
// because one of the tables was an index organized table.
// *Action: Ensure no underlying tables are index organized.
/
/ 26000-26099 Reserved for Direct Path Load Errors
/
26000, 00000, "partition load specified but table %s is not partitioned\n"
// *Cause: The Loader control file contains a PARTITION clause but the
// table being loaded is not partitioned.
// *Action: Remove the partition specification from the SQL*Loader control
// file and retry the load.
26001, 00000, "Index %s specified in SORTED INDEXES does not exist on table %s\n"
// *Cause: A nonexistent index was specified in the SORTED INDEXES clause.
// *Action: Do not specify as a SORTED INDEX.
26002, 00000, "Table %s has index defined upon it.\n"
// *Cause: Parallel load was specified into a table which has index
// defined upon it.
// *Action: Drop index(es) defined upon table, or don't use parallel load,
// or use SKIP_INDEX_MAINTENANCE option.
26003, 00000, "parallel load not supported for index-organized table %s.\n"
// *Cause: Parallel load is not supported for index-organized tables.
// *Action: load the index-organized table without the PARALLEL option.
26004, 00000, "Tables loaded through the direct path may not be clustered\n"
// *Cause: User attempted to load a clustered table via the direct path.
// *Action: Use the conventional path.
26005, 00000, "Invalid handle for direct path load\n"
// *Cause: In direct path load, the handle passed in does not match the type
// listed.
// *Action: Verify the handle and type are correct.
26006, 00000, "Incorrect bind variable in column %s's sql expression - %s\n"
// *Cause: In direct path load, the bind variables listed in the
// sql expression do not match the input argument column names.
// *Action: Verify all the input arguments are listed in the expression as
// bind variables, and all the bind variables are listed as
// input arguments to the expression. Or verify that there were
// no errors in executing the OCI statements when getting the bind
// variable list.
26007, 00000, "invalid value for SETID or OID column\n"
// *Cause: The value passed in a Direct Path API stream for a column
// containing a SETID or OID has an invalid value. SETIDs and
// Object IDs must be either 16 bytes of RAW data or 32 bytes of
// hexidecimal characters.
// *Action: Regenerate the Direct Path API stream with a valid value for the
// SETID column.
26008, 0, "Invalid syntax or bind variable in SQL string for column %s.\n%s\n"
// Cause: See following error message for more information.
// A SQL string cannot have quoted strings improperly terminated.
// A bind variable in a SQL string cannot have a length of 0, cannot
// exceed maximum length of 30 characters, and cannot be missing a
// double quote.
// Action: Fix the SQL string. See following error for more information.
26009, 00000, "stream verification error: %s\n"
// *Cause: An error has occurred in a Data Pump stream verification
// operation.
// *Action: Contact Oracle Support Services.
26010, 00000, "Column %s in table %s is NOT NULL and is not being loaded\n"
// *Cause: A column which is NOT NULL in the database is not being loaded
// and will cause every row to be rejected.
// *Action: Load the column by specifying the NOT NULL column in the
// INTO TABLE clause in the SQL*Loader control file.
26011, 00000, "Cannot load type %s into column %s in table %s\n"
// *Cause: A column can only store data of type declared for that column.
// And a substitutable column can only store data of valid subtypes
// of the supertype declared for that column.
// *Action: Check that the type or subtype specified is valid for that column.
26012, 0, "header in file %s has an incompatible version number\n"
// *Cause: A dump file was specified for a load operation whose version
// number is incompatible with the dump file version currently
// produced by the Oracle server on the system. Usually this
// message indicates that the dump file was produced by a newer
// version of the Oracle server.
// *Action: Load this dump file using the same version of the Oracle
// server that created the file.
26013, 00000, "List allocated may not be big enough\n"
// *Cause: There seems to be a discrepancy between the size for a list or
// buffer allocated by direct path api and the size needed.
// *Action: Contact Oracle Customer Support.
26014, 00000, "unexpected error on %s %s while retrieving %s\n%s"
// *Cause: The SQL error was returned from an OCIStmtExecute call.
// *Action: Correct the SQL error that was returned.
26015, 00000, "Array column %s in table %s is not supported by direct path\n"
// *Cause: User attempted to load an array column via the direct path.
// *Action: Use the conventional path.
26016, 00000, "Virtual column %s in table %s.%s cannot be loaded by direct path\n"
// *Cause: You attempted to load an virtual column using the direct path.
// *Action: Virtual columns cannot be loaded using the direct path.
26017, 00000, "global indexes not allowed for direct path load of table partition %s"
// *Cause: Global indexes are defined on a table when direct path loading a
// single partition of the table.
26018, 00000, "Column %s in table %s does not exist\n"
// *Cause: Column specified in the loader control file does not exist.
// *Action: Make sure the column exists and that you have privileges on it.
// Correct the loader control file if it is wrong.
26019, 00000, "Column %s in table %s of type %s not supported by direct path\n"
// *Cause: The Specified column of SQL column type %s is not supported by
// the direct path loader.
// *Action: If the column is NULLable, remove it from the control file
// description. Then it will be loaded as a NULL.
26020, 00000, "index %s.%s loaded successfully with %s keys"
// *Cause: Non-partitioned index information put to loader log file.
// *Action: None. Informational only.
26021, 00000, "index %s.%s partition %s loaded successfully with %s keys"
// *Cause: Partitioned index information put to loader log file.
// *Action: None. Informational only.
26022, 00000, "index %s.%s was made unusable due to:"
// *Cause: A Non-partitioned index was made index unusable due to the
// error displayed below this error.
// *Action: Depending on the error, either rebuild the index, or drop and
// re-create it.
26023, 00000, "index %s.%s partition %s was made unusable due to:"
// *Cause: A partition of a partitioned index was made index unusable due to
// error displayed below this error.
// *Action: Depending on the error, either rebuild the index partition,
// or drop and re-create the entire index.
26024, 00000, "SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable"
//* Cause: User requested SKIP_UNUSABLE_INDEXES option, and the index segment
//* was in unusable state prior to the beginning of the load.
//* Action: Informational only. User will need to either rebuild the index
//* or index partition, or re-create the index.
26025, 00000, "SKIP_INDEX_MAINTENANCE option requested"
//* Cause: User requested that index maintenance be skipped on a direct
// path load.
//* Action: The listed index was put into Index Unusable state due to the user
// requesting that index maintenance be skipped. Either rebuild the
// index or index partitions, or drop and re-create the index.
26026, 0000, "unique index %s.%s initially in unusable state"
//* Cause: A unique index is in IU state (a unique index cannot have
//* index maintenance skipped via SKIP_UNUSABLE_INDEXES).
//* Action: Either rebuild the index or index partition, or use
//* SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.
26027, 0000, "unique index %s.%s partition %s initially in unusable state"
//* Cause: A partition of a unique index is in IU state (a unique index
//* cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES).
//* Action: Either rebuild the index or index partition, or use
//* SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.
26028, 0000, "index %s.%s initially in unusable state"
//* Cause: An index is in IU state prior to the beginning of a direct
//* path load, it cannot be maintained by the loader.
//* Action: Either rebuild the index, re-create the index, or use either
//* SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only).
26029, 0000, "index %s.%s partition %s initially in unusable state"
//* Cause: A partition of an index is in IU state prior to the beginning
//* of a direct path load, it cannot be maintained by the loader.
//* Action: Either rebuild index partition, re-create the index, or use either
//* SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only).
26030, 0000, "index %s.%s had %s partitions made unusable due to:"
//* Cause: A logical index error occurred on a partitioned index which
//* affected one or more index partitions, which are listed below
//* this message.
//* Action: The affected index partitions will have to be re-built, or, the
//* entire index dropped and re-created.
26031, 0000, "index maintenance error, the load cannot continue"
//* Cause: A index errror occurred during the index maintenance phase of
//* a direct path load. The load cannot continue. See error message
//* below this message.
//* Action: See action for the error message which follows this one.
26032, 0000, "index %s.%s loading aborted after %s keys"
//* Cause: An index error occurred during direct-load of an index-organized table.
//* Loading had to be aborted. No rows were loaded.
//* Action: Check the key just following the number of keys mentioned above.
//* This key caused the index problem mentioned in an earlier message.
//*
26033, 0000, "column %s.%s encryption properties differ for source or target table"
//* Cause: The source and destination columns did not have the same
//* encryption properties.
//* Action: For security reasons, check that the source and target table have
//* the same encryption properties.
//*
26034, 00000, "Column %s does not exist in stream\n"
// *Cause: Column specified in the column list does not exist in the stream.
// *Action: Make sure the column exists or remove it from the list.
26035, 0000, "Error attempting to encrypt or decrypt column"
//* Cause: An error occurred while attemping to encrypt or decrypt
//* a database column.
// *Action: Verify correct encryption key was specified.
//*
26036, 00000, "subpartition load specified but table %s is not subpartitioned\n"
// *Cause: The Loader control file contains a PARTITION clause but the
// table being loaded is not subpartitioned.
// *Action: Remove the subpartition specification from the SQL*Loader control
// file and retry the load.
26037, 00000, "must specify partition name(s) for system partitioned table %s\n"
// *Cause: An attempt was made to load a system partitioned table with no
// partition name(s) specified.
// *Action: Specify the partition name(s) explicitly.
26038, 00000, "attempt to write audit record for SQL*Loader direct path load of %s.%s failed with error code: %d\n"
// *Cause: An attempt to write an audit record during a SQL*Loader direct path load failed.
//*Action: Contact Oracle Support Services.
26040, 00000, "Data block was loaded using the NOLOGGING option\n"
//* Cause: Trying to access data in block that was loaded without
//* redo generation using the NOLOGGING/UNRECOVERABLE option
//* Action: Drop the object containing the block.
/
// 26041 - 26044 DATETIME/INTERVAL datatypes
26041, 00000, "DATETIME/INTERVAL datatype conversion error\n"
//* Cause: The column could not be converted from DATETIME
//* datatype to internal DATETIME/CHARACTER datatype.
//*Action: Contact Oracle Customer Support.
26045, 00000, "REF column %s expects %s arguments; found %s.\n"
// *Cause: The number of arguments for the REF column is incorrect.
// *Action: Specify the correct number of input arguments for REFs.
// 1. Unscoped system-generated REFs can have exactly 1 or 2 input
// arguments. a) It has exactly 1 input argument (one for the OID
// value) if a fixed table name was specified through
// OCI_DIRPATH_EXPR_REF_TBLNAME. b) It has exactly 2 input arguments
// (one for the table name and one for the OID value) if a fixed
// table name was not specified through OCI_DIRPATH_EXPR_REF_TBLNAME.
// 2. Scoped system-generated REFs can have 1 or 2 input arguments.
// Because a table name argument is not needed for a scoped ref,
// only 1 argument (OID value) is expected. But if the table name
// argument is given, it's still accepted.
// 3. Scoped primary-key REFs with N columns in its primary-key OID
// can have N or N+1 input arguments. Because a table name argument
// is not needed for a scoped ref, only N arguments (making up the
// OID value) is expected. But if the table name argument is given,
// it's still accepted.
26046, 00000, "REF column %s expects scoped table name %s; user passed in %s.\n"
// *Cause: The scoped table name passed in by the user does not match the name
// in the schema.
// *Action: Specify the correct table name for the scoped REF column.
/
26048, 00000, "Scoped REF column has wrong table name.\n"
// *Cause: The scoped table name passed in by the user does not match the name
// in the schema.
// *Action: Specify the correct table name for the scoped REF column.
/
26049, 00000, "Unscoped REF column has non-existent table name.\n"
// *Cause: The table name passed in by the user does not exist
// in the schema.
// *Action: Specify a valid table name for the unscoped REF column.
/
26050, 00000, "Direct path load of domain index is not supported for this column type.\n"
// *Cause: Direct path can not load a domain index of that column type.
// *Action: Drop the index and try again or load using conventional path.
/
26051, 00000, "internal error parsing packed decimal format string"
// *Cause: A packed decimal field with a non-zero scale factor is mapped to
// a character column. In order to perform the datatype conversion,
// a numeric format string must be created based on the input field's
// precision and scale specifications. Direct path loader
// encountered an error in creating this format string.
// *Action: Examine the packed decimal field's precision and scale
// specifications and make sure that they contain valid values.
/
26052, 0000, "Unsupported type %d for SQL expression on column %s.\n"
//* Cause: The direct path api does not support a SQL expression on a
// column of that type.
//* Action: Make sure the types are correct.
/
/ do NOT translate or document message 26053 - it is never displayed
// NLS_DO_NOT_TRANSLATE [26053,26053]
26053, 0000, "Row was not loaded due to conversion error.\n"
/
//* Cause: The current row was not loaded due to a conversion error.
//* Action: Continue with the load anyways.
// 260xx - 260xx Direct Path API
26054, 0000, "Direct Path Context prepared for a different mode than operation requested.\n"
//* Cause: The user prepared the direct path context for one operation
// (Load, Unload, Convert), but then tried to perform a different
// operation.
//* Action: Make sure the direct path context mode and operation matches.
/
26055, 0000, "Invalid buffer specified for direct path unload\n"
//* Cause: The user specified a zero length or null buffer to be used for
// the Direct Path Unload operation.
//* Action: Specify a valid buffer and length.
/
26056, 00000, "Requested direct path operation on a view is not supported.\n"
// *Cause: An attempt was made to load into a view using direct path that has
// user-defined types, XML data, object type table or SQL expressions.
// *Action: Do not attempt to use direct path when loading a view that has
// nonscalar columns or when using SQL expressions on input columns.
/
/ do NOT translate or document message 26057 - it is for internal use only
// NLS_DO_NOT_TRANSLATE [26057,26057]
26057, 00000, "Conversion is not necessary for this direct path stream.\n"
// *Cause: User attempted to convert a direct path stream that does not
// require conversion.
// *Action: Load the stream without conversion it.
/
26058, 0000, "unexpected error fetching metadata for column %*s in table %*s\n"
//* Cause: The direct path API encountered an unexpected error while
// retrieving metadata for a column.
//* Action: Contact Oracle support.
/
26059, 0000, "Data is too large for column %s\n"
//* Cause: The direct path API encountered a column that can not be loaded
// because the input data is too large for a column.
//* Action: Make the target column larger.
/
26060, 0000, "Can not convert type identifier for column %s\n"
//* Cause: The direct path API encountered a type identifier for a column that
// can not be loaded because a mapping can not be found for the input
// value.
//* Action: Verify the input data.
/
26061, 0000, "Concurrent direct unloads is not allowed.\n"
//* Cause: User attempted a direct unload when another is still in progress.
//* Action: Complete the current direct unload before starting another.
/
26062, 0000, "Can not continue from previous errors.\n"
//* Cause: User attempted to continue a direct path load after receiving an
// error which indicates the load can not continue.
//* Action: Address the original error that was returned.
/
26063, 0000, "Can not flashback to specified SCN value - Wrap: %s Base: %s.\n"
//* Cause: User specified an SCN which occurs before the last time the
// table definition was modified.
//* Action: Specify a more recent SCN.
/
26064, 0000, "Invalid SCN specified - Wrap: %s Base: %s.\n"
//* Cause: User specified an invalid SCN.
//* Action: Specify a valid SCN.
/
26065, 0000, "check constraint cannot reference column, %s, in direct path load\n"
//* Cause: An enabled check constraint was found on a column stored as a lob.
//* Action: Either disable the check constraint before loading the table data
//* using the direct path mode, or use the conventional path mode
//* instead.
/
26076, 0000, "cannot set or reset value after direct path structure is allocated"
//* Cause: Client attempted to set or reset the number of rows in a direct path
//* structure after it has already been allocated and initialized.
//* Attributes used is one of the following:
//* - OCI_ATTR_NUM_ROWS: to set # of rows in a direct path column array
//* - OCI_ATTR_DIRPATH_DCACHE_SIZE: to set size of a date cache
//* (default is 0)
//* - OCI_ATTR_DIRPATH_DCACHE_DISABLE: to set whether date cache will be
//* disabled on overflow (default is FALSE)
//* Action: Set the following attributes before:
//* - OCI_ATTR_NUM_ROWS: before calling OCIHandleAlloc for column array
//* - OCI_ATTR_DIRPATH_DCACHE_SIZE: before calling OCIDirPathPrepare
//* - OCI_ATTR_DIRPATH_DCACHE_DISABLE: before calling OCIDirPathPrepare
26077, 0000, "direct path column array is not initialized"
//* Cause: Client attempted to allocate a column array for a direct path
//* function context before allocating a column array for the
//* table-level direct path context.
//* Action: Allocate the table-level direct path context's column array
//* via OCIHandleAlloc before allocating column arrays for
//* direct path function contexts.
26078, 0000, "file \"%s\" is not part of database being loaded\n"
//* Cause: A parallel load file was specified which is not part
//* of the database.
//* Action: Check filename and pathname for correctness.
26079, 0000, "file \"%s\" is not part of table %s.%s\n"
//* Cause: A parallel load file was specified which is not in the
//* tablespace of the table being loaded.
//* Action: Check to make sure that the specified parallel load file
//* is in the tablespace of the table being loaded.
26080, 0000, "file \"%s\" is not part of table %s.%s partition %s\n"
//* Cause: A parallel load file was specified which is not in the
//* tablespace of the table (partition, subpartition) being loaded.
//* When a partitioned table is being loaded, the file must be
//* in the tablespace of every partition or subpartition
//* (i.e. each (sub)partition must be in the same tablespace).
//* Action: Specify a different parallel load file, or no file at all.
26082, 0000, "load of overlapping segments on table %s.%s is not allowed"
//* Cause: Client application is attempting to do multiple direct path load
//* operations on the same table, but the segments overlap.
//* Action: Check the partition names (subname attribute of the direct path
//* context) being loaded. Make sure you are not loading a table,
//* and a partition of the same table. Make sure you are not
//* loading a partition, and a sub-partition within the same
//* partition.
26083, 0000, "unsupported direct path stream version %s"
//* Cause: The stream version requested is not supported by the server.
//* Action: Check to make sure that the VERSION attribute of the direct
//* stream is not being set to an invalid value.
26084, 0000, "direct path context already finished"
//* Cause: An OCIDirPathLoadStream operation was attempted after
//* OCIDirPathFinish was called. Once a direct path operaton
//* has been finished, no more data can be loaded.
//* Action: Check program logic to make sure OCIDirPathLoadStream is
//* not called after OCIDirPathFinish.
26085, 0000, "direct path operation must start its own transaction"
//* Cause: A direct path operation is being attempted within a transaction
//* that has already been started.
//* Action: Commit the transaction and Prepare the direct path operation again.
26086, 0000, "direct path does not support triggers"
//* Cause: A direct path operation is being attempted on a table which
//* has enabled triggers.
//* Action: Disable the triggers on the table and try again.
26088, 0000, "scalar column \"%s\" must be specified prior to LOB columns"
//* Cause: All scalar columns (i.e. non-LOB and non-LONG columns) must be
//* specified by the client of the direct path API prior to
//* specifying any LOB columns.
//* Action: Specify all scalar columns prior to specifying any LOB columns.
26089, 0000, "LONG column \"%s\" must be specified last"
//* Cause: A client of the direct path API specified a LONG column to be
//* loaded, but the LONG column was not the last column to be
//* specified.
//* Action: Specify the LONG column last.
26090, 0000, "row is in partial state"
//* Cause: A direct path operation is being finished or a data save request
//* has been made, but the table for which the request is being made
//* on has a row in partial state. The row must be completed before
//* the segment high water marks can be moved.
//* Action: Either complete the row, or abort the direct path operation.
26091, 0000, "requested direct path operation not supported"
//* Cause: A direct path operation was requested that is not supported
//* Action: Do not use that operation. Currently, UNLOAD is not supported.
26092, 0000, "only LONG or LOB types can be partial"
//* Cause: A column which is not a LONG or LOB had the
//* OCI_DIRPATH_COL_PARTIAL flag associated with it.
//* Only LONG or LOB type columns can be loaded in pieces.
//* Action: Do not use the OCI_DIRPATH_COL_PARTIAL flag for the column.
26093, 0000, "input data column size (%d) exceeds the maximum input size (%d)"
//* Cause: The user attempted to specify a column size (%d) that exceeded
//* the maximum allowable input size (%d)."
//* Action: Make sure the input column metadata matches the column definition.
26094, 0000, "stream format error: input column overflow"
//* Cause: An input stream contained data for more input columns
//* than specified by the client of the direct path API.
//* Action: Make sure that the stream being loaded is for the
//* correct table. Check initialization sequence.
26095, 0000, "unprocessed stream data exists"
//* Cause: Either a OCIDirPathLoadStream call was made which provided
//* more stream data prior to the server being able to fully
//* process the stream data that it already has, or a
//* OCIDirPathFinish call was made when the server had
//* unprocessed stream data.
//* Action: Most likely an application mis-use of the direct path API.
//* Make sure that the stream is not being reset inadvertently
//* prior to any previous stream data being processed, or, that
//* OCIDirPathFinish is not being called prematurely (i.e. stream
//* pushed, error encountered and LoadStream not called to process
//* the remainder of the stream before Finish is called.)
26096, 0000, "transfer size too small for row data (%lu bytes required)"
//* Cause: Either the transfer buffer size specified, or the default
//* transfer buffer size (if you did not specify a size), is
//* too small to contain a single row of the converted row data.
//* Action: Set the transfer buffer size attribute of the direct path
//* context to be larger.
26097, 0000, "unsupported conversion required for column %s"
//* Cause: The conversion required for the column was not supported. For
//* example, conversion from date to number was not supported.
//* Action: Ensure that the type is correct for the source and destination.
//*
26098, 0000, "direct path context is not prepared"
//* Cause: A direct path api function was called with a direct path
//* context which has not been prepared.
//* Action: Make sure all necessary attributes in the direct path
//* context have been set, and the context is prepared via
//* OCIDirPathPrepare.
26099, 0000, "direct path context is already prepared"
//* Cause: OCIDirPathPrepare was called with a context that has already
//* been prepared.
//* Action: Free the direct path context, set necessary attributes, and
//* call OCIDirPathPrepare.
/
// 26100 - 26110 reserved for tablespace-relative DBA Errors
//
26100, 00000, "unused error"
// *Cause:
// *Action:
26101, 00000, "tablespace # in file header is %s rather than %s for file %s"
// *Cause: The tablespace number in the file header is inconsistent
// with that in the control file.
// *Action: Check if the control file has been migrated correctly. Retry
// with the correct control file and data file.
26102, 00000, "relative file # in file header is %s rather than %s for file %s"
// *Cause: The relative file number in the file header is inconsistent
// with that in the control file.
// *Action: Check if the control file has been migrated correctly. Retry
// with the correct control file and data file.
26103, 00000, "V6 or V7 data file used to create control file"
// *Cause: The file header of the referenced file is in V6 or V7 format.
// *Action: Either remove the file from the create control file command, or
// somehow migrate the file header to V8 format.
/
/
/ 26500 - 26649 Reserved for Replication (KN)
/
/
26500, 00000, "error on caching \"%s\".\"%s\""
// *Cause: Attempt to cache the replication information which is unavailable
// in the catalog for the object.
// *Action: Use dbms_reputil.sync_up_rep to validate the replication catalog,
// or use dbms_reputil.make_internal_pkg to validate internal
// package.
26501, 00000, "RepAPI operation failure"
// *Cause: An external RepAPI operation failed.
// *Action: consult detail error message.
26502, 00000, "error resignal"
// *Cause: An internal service failed and signalled an error"
// *Action: consult detail error message.
26503, 00000, "internal RepAPI operation failure on object %s.%s"
// *Cause: An unexpected internal RepAPI failure was detected
// *Action: Contact Oracle support.
26504, 00000, "operation not implemented"
// *Cause: The caller requested a RepAPI operation that was not implemented
// *Action: Do not issue this call.
26505, 00000, "unexpected internal null"
// *Cause: An internal buffer control structure was NULL
// *Action: Verify that sufficient memory resources are available to RepAPI.
26506, 00000, "null global context"
// *Cause: An internal buffer control structure was NULL
// *Action: Verify that sufficient memory resources are available to RepAPI.
26507, 00000, "null master connection"
// *Cause: The master connection handle was or became invalid.
// *Action: Verify that the master connection is valid.
26508, 00000, "null materialized view connection"
// *Cause: The client connection handle was or became invalid.
// *Action: Verify that the client connection is valid.
26509, 00000, "null materialized view control structure"
// *Cause: An internal materialized view control structure could not be
// obtained.
// *Action: Check that the owner and users provided are correct.
26510, 00000, "materialized view name: '%s' is greater than max. allowed length of %s bytes"
// *Cause: The specified materialized view name was too long.
// *Action: Shorten the materialized view name.
26511, 00000, "master table '%s.%s' not found"
// *Cause: A RepAPI operation was attempted against a non-existent or
// invalid master table
// *Action: Verify that the master table object exists.
26512, 00000, "error pushing transaction to def$error"
// *Cause: An unexpected error occurred while sending an def$error rpc to
// the master site
// *Action: Verify that the DBMS_DEFER package is valid and executable
// by the RepAPI client. Contact the local or master site
// administrator, if necessary.
26513, 00000, "push error: master proc. %s$RP.%s failed for trans:%s seq:%s"
// *Cause: A conflict/error occurred at the master site while executing
// a $RP.rep_insert(), rep_update(), or rep_delete() function which
// was not handled by conflict resolution logic at the master.
// *Action: Notify master site system adminstrator or DBA.
26514, 00000, "object '%s.%s' not found"
// *Cause: The specified object was expected but not found.
// *Action: Verify that the specified object exists and is valid.
26515, 00000, "no master log available for '%s.%s'"
// *Cause: The specified master log was not found or available for the
// named table.
// *Action: Create the master log at the master site or correct any problems
// that may exist with the log.
26516, 00000, "no push transaction acknowledgement"
// *Cause: RepAPI was unable to confirm that the last pushed transaction
// was successfully commited by the master site.
// *Action: Verify that the communications link between the local site and
// the master site is still valid. If the transaction has not been
// committed at the master, repush the transaction.
26517, 00000, "materialized view control entry for '%s.%s' was not found"
// *Cause: The specified materialized view catalog control reocrd was not
// found.
// *Action: Verify that the local materialized view catalog is valid and that
// the local materialized view is properly defined.
26518, 00000, "push queue synchronization error detected"
// *Cause: Client tried to repush a transaction has already been committed at
// the master site. A common cause of this problem is an error at the
// local site in initializing or updating the local site transaction
// sequence mechanism.
// *Action: Verify that transaction data that RepAPI was attempting to
// repushed to the master site exists at the master table and is
// valid and consistent with the local site. If this error occurs,
// redundantly identified transactions are ignored and then purged
// from the local updatable materialized view logs. Check that the
// local site is correctly assigning new transactionIDs and is not
// accidently generating non-unique values.
//
26519, 00000, "no memory available to allocate"
// *Cause: There was no memory left for the RepAPI process. This error
// may occur when RepAPI is trying to allocate a new table buffer
// area.
// *Action: Shutdown one or more local applications to attempt to free
// heap memory and retry the RepAPI operation.
26520, 00000, "internal memory failure"
// *Cause: An internal memory error was detected.
// *Action: Check if other errors have occurred or determine if any local
// application may have corrupted the memory subsystem.
26521, 00000, "rpc initialization error"
// *Cause: An error occurred during the initialization of a PL/SQL rpc.
// *Action: Verify that the procudure to be invoked exists and is valid
// at the master site and is executable by the RepAPI user.
26522, 00000, "rpc execution error"
// *Cause: An error occurred during the execution of a PL/SQL rpc.
// *Action: Check the error messages from the remote procedure and fix any
// remote site problems that may be preventing the execution of the
// invoked rpc.
26523, 00000, "rpc termination error"
// *Cause: An error occurred during the termination of a PL/SQL rpc. This
// is usually caused by master site being unable to close an
// opened cursor or if RepAPI cannot deallocate internal memory.
// *Action: Fix any server side problems first, determine if the RepAPI
// memory subsystem has been corrupted.
26524, 00000, "nls subsystem initialization failure for product=%s, facility=%s"
// *Cause: The NLS product/facility error message file could not be located or
// properly initialized.
// *Action: Check that the error message directory and file(s) have been
// properly installed.
26525, 00000, "session connection attempt failed for %s (@%s)"
// *Cause: A connection could not be established to the specified database
// using the provided connection string.
// *Action: Check that the user, password, connect string, names services,
// network, and any remote site listener process are properly
// installed and working.
26526, 00000, "materialized view sql ddl parse/expansion failed for %s.%s"
// *Cause: The client sql materialized view definition query could not be
// properly parsed by the master Oracle site.
// *Action: Check that materialized view ddl sql is compatible with the
// currently connected version of Oracle and does not violate any of
// the RepAPI sql limitations or restrictions.
26527, 00000, "local store callback init phase failed for '%s.%s'"
// *Cause: The client callback failed during its INIT phase for the
// named object.
// *Action: Verify that the objects referenced by the client callback exist
// and are valid. Refer to the vendor-specific callback error code
// reference to diagnose the local problem. Record all error state
// and notify Oracle support.
26528, 00000, "local store callback proc phase failed for '%s.%s'"
// *Cause: The client callback failed during its PROC phase for the
// named object.
// *Action: Refer to the vendor-specific callback error code
// reference to diagnose the local problem. Record all error state
// and notify Oracle support.
26529, 00000, "local store callback term phase failed for '%s.%s'"
// *Cause: The client callback failed during its TERM phase for the
// named object.
// *Action: Refer to the vendor-specific callback error code
// reference to diagnose the local problem. Record all error state
// and notify Oracle support.
26530, 00000, "unable to build materialized view refresh control list"
// *Cause: The materialized view control list could not be constructed. This
// is generally the result of an error while accessing the local
// materialized view catalog.
// *Action: Verify that the named materialized view(s) are properly defined
// and valid.
26531, 00000, "replication parallel push failure recovery test event"
// *Document: NO
// *Cause: N/A.
// *Action: event used to simulate site failure for parallel push testing.
26532, 00000, "replication parallel push simulated site failure"
// *Cause: A parallel push executed with event 26531 enabled raises this
// error to simulation failure of network or destination site.
// *Action: Do not enable the event for normal operation.
26534, 00000, "collision: tranID %ld ignored and purged"
// *Cause: A transaction that was pushed had a transaction ID that collided
// with a transaction that was previously pushed and committed
// at the master site.
// *Action: See the action section for E_QUEUESYNC (26518).
26535, 00000, "%ud byte row cache insufficient for table with rowsize=%ud"
// *Cause: A transaction that was pushed had a transaction ID that collided
// with a transaction that was previously pushed and committed
// at the master site.
// *Action: Increase the RepAPI row buffer size or reduce the width of the
// replicated tables.
26536, 00000, "refresh was aborted because of conflicts caused by deferred transactions"
// *Cause: There are outstanding conflicts logged in the DEFERROR table at
// the materialized view's master site.
// *Action: Resolve the conflicts in the master DEFERROR table and refresh
// again after the table is empty. Alternatively, refresh with
// REFRESH_AFTER_ERRORS, even if there are conflicts in the master's
// DEFERROR table. Proceeding despite conflicts can result in an
// updatable materialized view's changes appearing to be temporarily
// lost, until a refresh succeeds after the conflicts are resolved.
26562, 00000, "last RepAPI error"
26563, 00000, "renaming this table is not allowed"
// *Cause: Attempt to rename a replicated table, an updatable materialized view
// table or the master table of a materialized view for which a
// materialized view log has beencreated.
// *Action: If desired, unregister the replicated table with
// dbms_repcat.drop_master_repobject, or use the recommended
// procedure to rename the master table of a materialized view.
26564, 00000, "%s argument is not of specified type"
// *Cause: User passed type of the given argument number doesn't match
// with the type of the argument in the stored arguments.
// *Action: Invoke correct type procedure (i.e. get_XXX_arg)
26565, 00000, "Call to <type>_arg made before calling dbms_defer.call"
// *Cause: User invoked <type>_arg procedure before starting a deferred call
// *Action: Invoke various procedures in the correct order.
26566, 00000, "Couldn't open connect to %s"
// *Cause: Failed to open connection using given dblink
// *Action: Make sure that the dblink is valid and remote m/c is up.
26571, 00000, "%s.%s.%s: number of arguments (%s) does not match replication catalog"
// *Cause: number of arguments does not match replication catalog
// *Action: examine total number of arguments for the rpc call
26572, 00000, "%s.%s.%s: argument %s does not match replication catalog"
// *Cause: the (rpc) call is corrupted
// *Action: examine total number of arguments and each argument for
// the rpc call
26575, 00000, "remote database does not support replication parallel propagation"
// *Cause: The remote database has a version lower than Oracle 8.0 and hence
// does not understand replication parallel propagation.
// *Action: Use serial propagation or upgrade the remote database to
// Oracle 8.0 or above.
26576, 00000, "cannot acquire SR enqueue"
// *Cause: An attempt to acquire the SR enqueue in exclusive mode failed.
// *Action:
26577, 00000, "PRESERVE TABLE can not be used when dropping old style materialized view %s.%s\n"
// *Cause: The materialized view consists of a view and a container table.
// *Action: Drop the materialized view without PRESERVE TABLE option.
26578, 00000, "No capture in this multitenant container database associated with queue \"%s\"."
// *Cause: An outbound server's queue was not associated with a capture from the same multitenant container database (CDB) before adding or starting an outbound server.
// *Action: Execute the DBMS_STREAMS_ADM.CREATE_CAPTURE procedure to create a capture before adding or starting an outbound server.
/
/
/ 26650 - 26999 Reserved for Log Based Replication Replication (KN)
/
26650, 00000, "%s %s background process %s might not be started successfully"
// *Cause: An error occurred during creation of a capture or apply
// background process.
// *Action: Review V$STREAMS_CAPTURE and V$STREAMS_APPLY_COORDINATOR views for
// the status of these processes. Also check the trace file for more
// information.
26651, 00000, "Unable to start or stop capture process %s"
// *Cause: An attempt was made to start or stop a capture process while
// another capture process was concurrently starting or stopping.
// *Action: You cannot concurrently start or stop capture processes. Wait
// before attempting to start or stop additional capture processes.
26652, 00000, "Capture %s did not start properly and is currently in state %s"
// *Cause: An attempt to restart a capture process failed.
// *Action: Review V$STREAMS_CAPTURE view for the state of the capture
// process. Also check the trace files for more information.
26653, 00000, "Apply %s did not start properly and is currently in state %s"
// *Cause: An attempt to restart an apply process failed.
// *Action: Streams: Review V$STREAMS_APPLY% views for the state of the apply
// process. Also check the trace files for more information.
// XStream: Review V$XSTREAM_APPLY% views for the state of the apply
// process. Also check the trace files for more information.
// GoldenGate: Review V$GG_APPLY% views for the state of the apply
// process. Also check the trace files for more information.
26654, 00000, "Capture %s attempted to connect to apply %s already configured for %s"
// *Cause: An attempt was made by a GoldenGate, XStream or Streams Capture or XStream In to connect to an
// Apply that is already connected in the other mode.
// *Action: You cannot connect a capture to an apply already configured for
// another apply mode. Create or connect to another apply.
26655, 00000, "Invalid %s specified for %s procedure"
// *Cause: An attempt was made to execute the specified procedure with an
// invalid SCN value.
// *Action: Resubmit procedure with a valid SCN value.
26656, 00000, "supplemental logging version error: %s"
// *Cause: The supplemental logging versions of capture side and apply side
// are incompatible.
// *Action: For incompatibility caused by a newer apply side, please bypass or
// migrate the incompatible logs manually and consider upgrading or
// patching the capture side. For incompatibility caused by an
// unrecognizable version group or an older apply side, please
// upgrade or patch the apply side. For invalid versions, the
// logs might have been corrupted; please verify the integrity of
// the supplemental logging data on the capture side.
26660, 00000, "Invalid action context value for %s"
// *Cause: The value specified in the action context is invalid for
// use in GoldenGate, XStream or Streams.
// *Action: Check that the type and value are correct.
26661, 00000, "STREAMS tracing event"
// *Document: NO
// *Cause:
// *Action: Check that the type and value are correct.
26662, 00000, "unable to process %s Data Dictonary information for object"
// *Cause: The database is unable to process GoldenGate, XStream or Streams Data
// Dictionary for this object.
// *Action: Check that the compatibility for the database supports the object,
// and check the trace file for information about the object.
26663, 00000, "error queue for apply process %s must be empty"
// *Cause: The error queue for this apply process contains error entries.
// *Action: Execute or delete errors in the error queue.
26664, 00000, "cannot create %s process %s"
// *Cause: An attempt was made to create a GoldenGate, XStream or Streams process
// when another was being created concurrently.
// *Action: Wait for the creation of the other GoldenGate, XStream or Streams
// process to finish before attempting to create the process.
26665, 00000, "%s process %s already exists"
// *Cause: An attempt was made to create a GoldenGate, XStream or Streams process
// that already exists.
// *Action: Either specify another process or remove the existing
// GoldenGate, XStream or Streams process.
26666, 00000, "cannot alter %s process %s"
// *Cause: An attempt was made to alter a GoldenGate, XStream or Streams process
// that is currently running.
// *Action: Stop the GoldenGate, XStream or Streams process with FORCE parameter
// set to TRUE and reissue the command.
26667, 00000, "invalid %s parameter %s"
// *Cause: An attempt was made to specify an invalid parameter.
// *Action: Check the documentation for valid parameters.
26668, 00000, "%s process %s exists"
// *Cause: An attempt to remove the component failed because it
// is associated with the GoldenGate, XStream or Streams process.
// *Action: Either remove the process manually or specify the "cascade"
// option in dbms_streams_adm.remove_queue.
26669, 00000, "parameter %s inconsistent with parameter %s"
// *Cause: An attempt was made to specify a subprogram parameter value
// that is inconsistent with another parameter value.
// *Action: Check the documentation for valid parameter values.
26670, 00000, "No capture is found for queue '%s'"
// *Cause: An attempt was made to add an XStream outbound server to a
// queue using uncommitted data mode when no co-located XStream capture
// was configured for that queue.
// *Action: Change to committed data mode or configure a local XStream capture
// for the specified queue then retry the operation.
26671, 00000, "maximum number of %s processes exceeded"
// *Cause: Cannot create additional GoldenGate, XStream or Streams processes since
// the maximum number of processes has been reached.
// *Action: Remove existing GoldenGate, XStream or Streams processes and retry the operation.
26672, 00000, "timeout occurred while stopping %s process %s"
// *Cause: Timeout occurred while waiting for a GoldenGate, XStream or Streams
// process to shut down.
// *Action: Retry the operation. If the error persists, try stopping the
// process with the FORCE option, or contact Oracle Support Services.
26673, 00000, "duplicate column name %s"
// *Cause: An attempt was made to specify a duplicate column name in an LCR.
// *Action: Remove the duplicate column and retry the operation.
26674, 00000, "Column mismatch in '%s.%s' (LCR: %s type=%s; DB: %s type=%s)"
// *Cause: The columns in the LCR were not the same or not found in the
// database table.
// *Action: Alter the database table.
26675, 00000, "cannot create %s capture process %s"
// *Cause: GoldenGate, XStream or Streams capture process could not be created
// because one or more parameters contain invalid value.
// *Action: Refer to trace file for more details.
26676, 00000, "Table '%s.%s' has %s columns in the LCR and %s columns in the replicated site"
// *Cause: The number of columns in the LCR was not the same as the
// the replicated site.
// *Action: Alter the table structure
26677, 00000, "%s downstream capture process %s cannot proceed"
// *Cause: Database global name has been set to a value which is same as the
// source database name of the downstream capture process.
// *Action: Change database global name to a value other than
// the source database name for the downstream capture.
26678, 00000, "%s downstream capture process for source database %s must be created at database %s first"
// *Cause: A GoldenGate, XStream or Streams downstream capture process was
// nonexistent when this operation was attempted.
// *Action: Create a GoldenGate, XStream or Streams downstream capture process,
// then retry the operation.
26679, 00000, "operation not allowed on LOB or LONG columns in LCR"
// *Cause: Certain operations on LOB/LONG columns of the LCR
// through rule-based transformations, DML handlers, or error
// handlers were not allowed.
// *Action: Do not perform restricted operations on LOB or LONG columns in
// LCRs. See the documentation for operations that are restricted
// on LOB/LONG columns in LCRs.
26680, 00000, "object type not supported"
// *Cause: The specified object type is not supported.
// *Action: Retry with a supported object type.
26681, 00000, "command type not supported"
// *Cause: The specified command type is not supported.
// *Action: Retry with a supported command type.
26682, 00000, "invalid value for publication_on"
// *Cause: The publication_on parameter should be either 'Y' or 'N'
// *Action: Retry with a proper value for publication_on.
26683, 00000, "invalid value for value_type"
// *Cause: The value_type parameter should be either 'OLD' or 'NEW'
// *Action: Retry with proper value_type.
26684, 00000, "invalid value for value_type"
// *Cause: The value_type parameter should be one of 'OLD', 'NEW' or '*'
// *Action: Retry with proper value_type.
26685, 00000, "cannot apply transactions from multiple sources"
// *Cause: Transactions from multiple sources were sent to the same apply
// process.
// *Action: Create multiple apply processes and create appropriate rules
// so that transactions from only one source reach an apply
// process.
26686, 00000, "cannot capture from specified SCN"
// *Cause: An attempt was made to specify an invalid SCN.
// *Action: Retry with a valid SCN.
26687, 00000, "no instantiation SCN provided for \"%s\".\"%s\" in source database \"%s\""
// *Cause: Object SCN was not set. If the object is a table,
// then both fields will be filled, for example "SCOTT"."EMP".
// If the object is a schema, only one field will be set, for
// example "SCOTT"."". And if the object is the entire
// database, no fields will be set, for example ""."".
// *Action: Set the SCN by calling DBMS_APPLY_ADM.SET_%_INSTANTIATION_SCN
26688, 00000, "missing key in LCR"
// *Cause: Metadata mismatch, or not enough information in the user
// generated LCR.
// *Action: Alter the database object, or provide all defined keys
// in the LCR.
26689, 00000, "column datatype mismatch in LCR"
// *Cause: The datatypes of columns in the LCR are not the same as
// the datatypes in the database object.
// *Action: Alter the database object.
26690, 00000, "datatype not supported at non-Oracle system"
// *Cause: One of the columns of the LCR being applied was of a datatype
// not supported by either the target non-Oracle system or by the
// Oracle transparent gateway through which the apply is being done.
// *Action: Do not apply data of this type. If possible, filter out
// columns containing such datatypes before applying.
26691, 00000, "operation not supported at non-Oracle system"
// *Cause: The apply process attempted an operation that is either
// not supported by the non-Oracle system or by the Oracle
// transparent gateway through which the apply is being done. Some
// kinds of DML (like procedure and function calls) and all DDL
// will cause this error to be raised.
// *Action: Do not attempt to apply such LCRs to non-Oracle systems. If
// possible, filter out such LCRs before applying.
26692, 00000, "invalid value %s, %s should be in %s format"
// *Cause: The parameter specified was not in the correct format.
// *Action: Specify the parameter value in the correct format.
26693, 00000, "%s %s process dropped successfully, but error occurred while dropping rule set %s"
// *Cause: An attempt to drop an unused rule set failed after dropping the
// GoldenGate, XStream or Streams proccess successfully.
// *Action: Check existence of rule set and manually drop if necessary.
26694, 00000, "error while enqueueing into queue %s.%s"
// *Cause: An error occurred while enqueueing a message.
// *Action: If the situation described in the next error on the stack
// can be corrected, do so.
26695, 00000, "error on call to %s: return code %s"
// *Cause: A locking related call failed.
// *Action: Try the call again after fixing the condition indicated by
// the return code.
26696, 00000, "no %s data dictionary for object with number %s and version number %s from source database %s"
// *Cause: An attempt to access the database object failed because the
// data dictionary for the object was either never populated
// or it was purged.
// *Action: Make sure the GoldenGate, XStream or Streams data dictionary is created by calling
// DBMS_CAPTURE_ADM.PREPARE_%_INSTANTIATION.
26697, 00000, "LCR contains extra column '%s'"
// *Cause: The LCR contained more columns than the replicated table.
// *Action: Alter the database object.
26698, 00000, "%s did not have a %s rule set"
// *Cause: The GoldenGate, XStream or Streams client does not have a rule set of the indicated type.
// *Action: Verify that the GoldenGate, XStream or Streams client has a rule set of the specified
// type, and retry the operation.
26699, 00000, "%s message consumer %s already exists"
// *Cause: An attempt was made to create a GoldenGate, XStream or Streams
// message consumer that already exists.
// *Action: Either specify another message consumer or remove the
// existing GoldenGate, XStream or Streams message consumer.
26700, 00000, "STREAMS tracing event"
// *Document: NO
// *Cause:
// *Action:
26701, 00000, "%s process %s does not exist"
// *Cause: An attempt was made to access a GoldenGate, XStream or Streams process
// which does not exist.
// *Action: Check with the relevant security views for the correct name of
// the object.
26702, 00000, "shut the STREAMS/CDC apply engine down"
// *Document: NO
// *Cause:
// *Action:
26703, 00000, "event for configuring STREAMS rules cache"
// *Document: NO
// *Cause: Not Applicable
// *Action: Set this event only under the supervision of Oracle support.
26704, 00000, "The Owner instance %s of the queue table is not up or the QMN0 process is down."
// *Cause:
// *Action: Try again once the owner instance is up, and the QMN0 process on
// that instance is up.
26705, 00000, "cannot downgrade capture process after Streams data dictionary has been upgraded"
// *Cause: An attempt was made to downgrade a capture process after it has
// upgraded the GoldenGate, XStream or Streams data dictionary.
// *Action: Drop the capture process before attempting the downgrade.
26706, 00000, "cannot downgrade capture process"
// *Cause: An attempt was made to downgrade a capture process that has a
// higher version than the downgrade release version.
// *Action: Drop the capture process after capture has finished consuming all
// the redo logs before attempting the downgrade.
26707, 00000, "STREAMS or_expand complexity"
// *Document: NO
// *Cause: Not Applicable.
// *Action: Set this event only under the supervision of Oracle Support.
26708, 00000, "remote DDL not supported by STREAMS : dblink %s"
// *Cause: The apply process attempted to apply a DDL LCR via a dblink.
// This is not supported.
// *Action: Do not attempt to apply DDL LCRs via a dblink. If
// possible, filter out DDL LCRs before applying.
26709, 00000, "Downstream Capture RFS restart"
// *Cause: Remote file server (RFS) process was restarted to reflect a change
// in DOWNSTREAM_REAL_TIME_MINE option of the GoldenGate, XStream or Streams capture process.
// *Action: No action required. This is an informational message only.
26710, 00000, "incompatible version marker encountered during Capture"
// *Cause: Capture process cannot mine redo from a version higher than the
// current software release version.
// *Action: Drop and recreate the capture process.
26711, 00000, "remote table does not contain a primary key constraint"
// *Cause: The master table for remote apply does not constain a primary key
// constraint or the primary key constraint has been disabled.
// *Action: Create a primary key constraint on the master table or enable the
// existing constraint.
26712, 00000, "remote object is \"%s\".\"%s\"\@\"%s\""
// *Cause: See the preceding error message to identify the cause.
// This message names the remote object, usually a table or view,
// for which an error occurred when GoldenGate, XStream or Streams tried to access it
// for remote apply.
// *Action: See the preceding error message.
26713, 00000, "remote object does not exist or is inaccessible"
// *Cause: GoldenGate, XStream or Streams replication could not access the named table
// or view at a remote database to apply changes.
// *Action: Confirm that the given remote table or view exists and is
// accessible through the given database link. When using a
// Heterogeneous Services database link to access a non-Oracle system,
// it may be necessary to check administration details for
// network connections at the non-Oracle system.
26714, 00000, "User Error %s encountered during apply process"
// *Cause: An error was encountered during an apply process.
// *Action: Query the DBA_APPLY_ERROR view to determine the error and
// take the appropriate action.
26715, 00000, "time limit reached"
// *Cause: The specified time limit was reached for the GoldenGate, XStream or Streams process.
// *Action: Restart the GoldenGate, XStream or Streams process, increasing the TIME_LIMIT
// parameter if necessary.
26716, 00000, "message limit reached"
// *Cause: The specified message limit was reached for the Capture process.
// *Action: Restart the Capture process, increasing the MESSAGE_LIMIT
// parameter if necessary.
26717, 00000, "SCN limit reached"
// *Cause: The specified SCN limit was reached for the GoldenGate, XStream or Streams process.
// *Action: Change the MAXIMUM_SCN parameter, then restart the
// GoldenGate, XStream or Streams process.
26718, 00000, "transaction limit reached"
// *Cause: The specified transaction limit was reached for the Apply process.
// *Action: Restart the Apply process, increasing the
// TRANSACTION_LIMIT parameter if necessary.
26719, 00000, "STREAMS tracing event"
// *Document: NO
// *Cause:
// *Action:
26720, 00000, "STREAMS assemble lobs event"
// *Document: NO
// *Cause:
// *Action:
26721, 00000, "enqueue of the LCR not allowed"
// *Cause: An apply process attempted to enqueue an LCR with a LONG column.
// This is not supported.
// *Action: Modify rules or unset the enqueue destination to prevent
// LCRs with LONG columns from being enqueued by the apply process.
26722, 00000, "STREAMS canonicalization event"
// *Document: NO
// *Cause:
// *Action:
26723, 00000, "user \"%s\" requires the role \"%s\""
// *Cause: The caller did not have the specified role or called the procedure
// from a definer's rights package or procedure.
// *Action: Grant the specified role to the caller. If the procedure is called
// from a definer's rights package or procedure, change the definer's
// rights package or procedure to an invoker's rights package or
// procedure.
// Or grant all the privileges for the specified role explicitly.
26724, 00000, "only SYS is allowed to set the Capture or Apply user to SYS."
// *Cause: The Capture or Apply user was specified as SYS by a user other
// than SYS.
// *Action: Set SYS as the Capture or Apply user while logged in as SYS.
26725, 00000, "cannot downgrade apply handlers"
// *Cause: An attempt was made to downgrade apply handlers that are not
// associated with a local database object, or the apply handlers
// are associated with a specific apply process.
// *Action: Drop the associated apply handlers before attempting the downgrade.
26726, 00000, "standby and DOWNSTREAM_REAL_TIME_MINE are incompatible"
// *Cause: An attempt was made to set the standby database and
// DOWNSTREAM_REAL_TIME_MINE option of the Oracle GoldenGate, XStream
// or Oracle Streams capture process on the same database.
// *Action: Do not attempt to set the DOWNSTREAM_REAL_TIME_MINE option for a
// Oracle GoldenGate, XStream or Oracle Streams capture process on a
// standby database. Do not attempt to change a database role to
// standby if there exists a capture process with the
// DOWNSTREAM_REAL_TIME_MINE parameter set to Y.
26727, 00000, "Cannot alter queue_to_queue property of existing propagation."
// *Cause: The queue_to_queue property was specified for an existing
// propagation.
// *Action: Pass NULL for the queue_to_queue argument.
26728, 00000, "event for configuring STREAMS apply segcol mapping cache"
// *Document: NO
// *Cause: Not Applicable
// *Action: Set this event only under the supervision of Oracle support.
26729, 00000, "event for configuring STREAMS apply destination object cache"
// *Document: NO
// *Cause: Not Applicable
// *Action: Set this event only under the supervision of Oracle support.
26730, 00000, "%s '%s' already exists"
// *Cause: An attempt to use FILE GROUP, FILE GROUP VERSION, or FILE GROUP
// FILE failed because the item in question already exists.
// *Action: Remove the object if appropriate and re-attempt the operation.
26731, 00000, "%s '%s' does not exist"
// *Cause: A FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE was
// specified that does not exist.
// *Action: Make sure the object exists and re-attempt the operation.
26732, 00000, "invalid file group %s privilege"
// *Cause: The specified privilege number that was specified is invalid.
// *Action: Check specification of dbms_file_group for valid privileges.
26733, 00000, "timed-out waiting for file group lock"
// *Cause: The procedure waited too long while getting a lock to perform a
// file group repository operation.
// *Action: Retry the operation.
26734, 00000, "different datafiles_directory_object parameter must be specified"
// *Cause: The attempted operation involved datafiles platform conversion
// which required the datafiles_directory_object parameter to be
// specified for placing the converted data files.
// *Action: Retry the operation after specifying a valid
// datafiles_directory_object parameter. This directory must be
// different from the directory objects for any of the datafiles for
// the specified file group version.
26735, 00000, "operation not allowed on the specified file group version"
// *Cause: One or more datafiles or export dump file(s) were missing from
// the specified file group version.
// *Action: Retry the operation after adding all the data files and Data Pump
// dump file(s) to the specified version.
26736, 00000, "Data Pump error"
// *Cause: A Data Pump error occurred when the procedure performed a
// File Group Repository operation.
// *Action: Check the error stack and trace file for error details.
26737, 00000, "version %s already has an export dump file"
// *Cause: A Data Pump dump file was added to a file group version that already
// has a dump file.
// *Action: Remove the existing dump file if appropriate, and retry the
// operation.
26738, 00000, "%s '%s' is not empty"
// *Cause: The FILE GROUP or FILE GROUP VERSION being dropped contained
// objects.
// *Action: Remove the child objects, then retry the operation.
26739, 00000, "FILE GROUP tracing event"
// *Document: NO
// *Cause:
// *Action:
26740, 00000, "cannot downgrade because there are file groups"
// *Cause: An attempt was made to downgrade a database that has file groups.
// *Action: Drop all file groups before attempting the downgrade.
26741, 00000, "cannot assemble lobs"
// *Cause: An attempt was made to assemble lobs, but the compatibility
// of the source database for the LOB information is lower than 10.2.0.
// *Action: Set ASSEMBLE_LOBS to FALSE in the DML or error handler while
// this handler is processing LOB information from a source
// database with a compatibility level lower than 10.2.0.
26742, 00000, "Maximum number of ignored transactions exceeded"
// *Cause: An attempt was made to add more than the allowed number of ignored
// transactions.
// *Action: Please clear the current list of ignored transactions.
26743, 00000, "Streams tracing event"
// *Document: NO
// *Cause:
// *Action:
26744, 00000, "%s capture process \"%s\" does not support \"%s\".\"%s\" because of the following reason: %s"
// *Cause: GoldenGate, XStream or Streams capture encountered a table with an unsupported
// property. The most common reason is an unsupported column
// data type.
// *Action: Revise the Capture rules to skip over the table in
// question. One way might be to add a negative rule
// excluding changes from the unsupported table from being
// captured.
//
// Streams: Also query the DBA_STREAMS_UNSUPPORTED view to determine
// which tables are not supported by Streams and for what
// reason. Consider adding negative rules for any tables
// that may be captured, but are present in this view.
// XStream: Also query the DBA_XSTREAM_OUT_SUPPORT_MODE view to determine
// which tables are not supported by XStream and for what
// reason. Consider adding negative rules for any tables
// that may be captured, but are present in this view.
// GoldenGate: Also query the DBA_GOLDENGATE_SUPPORT_MODE view to determine
// which tables are not supported by GoldenGate and for what
// reason. Consider adding EXCLUDETABLE statements for any tables
// that may be captured, but are present in this view.
//
// For potential workarounds to certain unsupported properties, see
// Metalink.
26745, 00000, "cursors (%s) are not sufficient"
// *Cause: The maximum number of open cursors was too small for GoldenGate, XStream or Streams Apply.
// *Action: Increase the value of open_cursors.
26746, 00000, "DDL rule \"%s\".\"%s\" not allowed for this operation"
// *Cause: A DDL rule was specified for this operation.
// *Action: Specify a non-DDL rule for this operation.
26747, 00000, "The one-to-many transformation function %s encountered the following error: %s"
// *Cause: The specified transformation function encountered an error.
// *Action: Ensure that the function does not process or return DDL LCRs.
// Also ensure that the function does not return NULL.
26748, 00000, "The one-to-one transformation function %s encountered the following error: %s"
// *Cause: The specified transformation function encountered an error.
// *Action: Ensure that the function does not return an LCR that has a
// different type from the LCR which was passed to the function.
// Also ensure that the function does not return NULL.
// For DDL transformation functions, creating and returning a
// new DDL LCR is not allowed.
26749, 00000, "STREAMS propagation batch size"
// *Document: NO
// *Cause:
// *Action:
26750, 00000, "STREAMS internal transformation"
// *Document: NO
// *Cause:
// *Action:
26751, 00000, "STREAMS testing event"
// *Document: NO
// *Cause:
// *Action: Check that the type and value are correct.
26752, 00000, "Unsupported LCR received for \"%s\".\"%s\""
// *Cause: GoldenGate, XStream or Streams capture process received an LCR with unsupported
// operation from LogMiner.
// *Action: Stream:If this object is listed in DBA_STREAMS_UNSUPPORTED view,
// modify rules to prevent changes made to this object from
// getting captured.
// XStream: If this object is listed in DBA_XSTREAM_OUT_SUPPORT_MODE view,
// modify rules to prevent changes made to this object from
// getting captured.
// GoldenGate: If this object is listed in DBA_GOLDENGATE_SUPPORT_MODE view,
// modify rules to prevent changes made to this object from
// getting captured.
26753, 00000, "Mismatched columns found in '%s.%s'"
// *Cause: The columns in the LCR were not the same as the table in the
// database.
// *Action: Alter the database table.
26754, 00000, "cannot specify both one-to-one transformation function %s and one-to-many transformation function %s"
// *Cause: Both a one-to-one transformation function and a one-to-many
// transformation function were specified for a rule.
// *Action: Remove either the one-to-one transformation function, or the
// one-to-many transformation function.
26755, 00000, "STREAMS apply spill table partitioning event"
// *Document: NO
// *Cause:
// *Action:
26756, 00000, "STREAMS apply spill table partition ceiling event"
// *Document: NO
// *Cause:
// *Action:
26757, 00000, "Timed out waiting for remote operation on instance %s to finish"
// *Cause:
// *Action: Retry the operation at a later time.
26758, 00000, "%s skip LCR requested"
// *Document: NO
// *Cause: Internal error to handle skip LCR event.
// *Action:
26759, 00000, "Maximum number of skip LCR requests exceeded"
// *Document: NO
// *Cause:
// *Action:
26760, 00000, "Could not find message number %s for transaction with id %s"
// *Cause: Error
// *Action: Contact Oracle support"
26761, 00000, "Standby Redo Logs not available for real time mining"
// *Cause: Standby Redo Logs required for real time mining by downstream
// capture process were not available.
// *Action: Check the configuration of Standby Redo Logs and retry the
// operation at a later time. To start the capture process without
// real time mining property, reset DOWNSTREAM_REAL_TIME_MINE
// parameter of the capture process and retry the operation.
26762, 00000, "Cannot autogenerate name for parameter %s because of the following reason: %s"
// *Cause: An error was encountered while attempting to generate a name for
// a parameter which was passed a NULL value.
// *Action: If possible, fix the error, otherwise specify the
// parameter name explicitly.
26763, 00000, "invalid file type \"%s\""
// *Cause: An invalid file type was specified for the ASM file.
// *Action: Check documentation for valid ASM file types.
26764, 00000, "invalid parameter \"%s\" for local capture \"%s\""
// *Cause: An invalid parameter was specified for the local capture process.
// *Action: Check documentation for valid parameters.
26765, 00000, "invalid parameter \"%s\" for downstream capture \"%s\""
// *Cause: An invalid parameter was specified for the downstream capture
// process.
// *Action: Check documentation for valid parameters.
26766, 00000, "Unexpected redo pattern encountered by LogMiner"
// *Cause: LogMiner encountered an unexpected redo pattern. This is usually
// caused by tables with unsupported data types or newer table features.
// *Action: Remove the capture rule for the table and restart capture.
26767, 00000, "Not enough redo log information for LogMiner"
// *Cause: Direct-path SQL with NOLOGGING option or a SQL*Loader operation with
// UNRECOVERABLE clause was specified for the table.
// *Action: Remove the capture rule for the table and restart capture.
26768, 00000, "Maximum number of unsupported tables exceeded"
// *Cause: An attempt was made to add more than the allowed number of
// unsupported tables.
// *Action: Clear the current list of unsupported tables.
26769, 00000, "STREAMS force lob assembly event"
// *Document: NO
// *Cause:
// *Action:
26770, 00000, "Index-organized table not supported"
// *Cause:
// *Action:
26771, 00000, "User-defined column type not supported"
// *Cause:
// *Action:
26772, 00000, "Encrypted column not supported"
// *Cause:
// *Action:
26773, 00000, "Invalid data type for column \"%s\""
// *Cause:
// *Action:
26774, 00000, "Queue table not supported"
// *Cause:
// *Action:
26775, 00000, "Temporary table not supported"
// *Cause:
// *Action:
26776, 00000, "Subordinate object not supported"
// *Cause:
// *Action:
26777, 00000, "External table not supported"
// *Cause:
// *Action:
26778, 00000, "File column not supported"
// *Cause:
// *Action:
26779, 00000, "Materialized view not supported"
// *Cause:
// *Action:
26780, 00000, "Object table not supported"
// *Cause:
// *Action:
26781, 00000, "Nested table not supported"
// *Cause:
// *Action:
26782, 00000, "Function-based index not supported"
// *Cause:
// *Action:
26783, 00000, "Column data type not supported"
// *Cause:
// *Action:
26784, 00000, "STREAMS internal event"
// *Document: NO
// *Cause:
// *Action: Check that the type and value are correct.
26785, 00000, "Object has a NULL value"
// *Cause: A method was invoked on a NULL object.
// *Action: Initialize the object with a non-NULL value.
26786, 00000, "A row with key %s exists but has conflicting column(s) %s in table %s"
// *Cause: The row to update or delete exists in the table but had
// conflicting value for some columns.
// *Action: For Streams and XStream, please define a conflict resolution, or resolve the
// conflict and execute the error transaction using
// DBMS_APPLY_ADM.EXECUTE_ERROR.
// For logical standby, please verify the status of the database guard
// to ensure local modifications are not allowed, then re-instantiate
// the table and contact support if the problem persists.
// For GoldenGate, configure Conflict Resolution (CDR) or REPERROR handler
// for the table and restart replicat.
26787, 00000, "The row with key %s does not exist in table %s"
// *Cause: The row to update or delete does not exist in the table.
// *Action: For Streams and XStream, please define a conflict resolution, or resolve the
// conflict and execute the error transaction using
// DBMS_APPLY_ADM.EXECUTE_ERROR.
// For logical standby, please verify the status of the database guard
// to ensure local modifications are not allowed, then re-instantiate
// the table and contact support if the problem persists.
// For GoldenGate, configure Conflict Resolution (CDR) or REPERROR handler
// for the table and restart replicat.
26788, 00000, "The column %s is not encrypted in the local database."
// *Cause: The column in the destination database is NOT encrypted while
// it is encrypted in the source database.
// *Action: Set the corresponding column property in the destination database to
// 'encrypted' or change the apply parameter, PRESERVE_ENCRYPTED_COLS,
// to 'N' to supress the error.
26789, 00000, "Cannot split propagation %s because only one propagation originates from its source queue \"%s\".\"%s\""
// *Cause: Only one propagation originated from the propagation source queue.
// *Action: Please do not split this propagation.
26790, 00000, "Requesting a lock on %s \"%s\" timed out"
// *Cause: Could not get a lock on the object because another process was
// holding the lock.
// *Action: Please try later.
26791, 00000, "Cannot split or merge propagation \"%s\""
// *Cause: A process tried to split or merge this propagation, but failed and
// left STREAMS in an inconsistent state.
// *Action: Query DBA_RECOVERABLE_SCRIPT_BLOCKS view, and roll back the script
// which tried to split or merge this propagation.
26792, 00000, "Invalid source database name %s"
// *Cause: The value for the source database global name was not valid.
// *Action: Specify a valid database global name. If the source database
// is not the local database, check the listener is up and running.
26793, 00000, "Number of capture processes that enqueued message to queue \"%s\".\"%s\" not equal to one"
// *Cause: Split-merge API requires only one capture process enqueued message
// to the queue where the propagation originated
// *Action: Please drop one capture, or split or merge another propagation.
26794, 00000, "Hierarchically enabled tables not supported"
// *Cause: Hierarchically enabled tables are not supported.
// *Action: Disable hierarchy for the table.
26795, 00000, "Cannot modify an LCR received from an XStream outbound server"
// *Cause: An attempt was made to modify an LCR generated by an XStream outbound
// server.
// *Action: Clone the LCR generated by the XStream outbound server by
// using the provided OCILCR* functions, such as OCILCRNew,
// OCILCRHeaderSet, and OCILCRRowColumnInfoSet. Then modify the
// cloned LCR.
26796, 00000, "STREAMS excessive IO event"
// *Document: NO
// *Cause:
// *Action:
26798, 00000, "LOB logical change record (LCR) missing LOB column in table \"%s\".\"%s\""
// *Cause: The apply slave could not fill update LOB because of missing LOB column.
// *Action: Check that all LOB columns have been sent correctly.
26799, 00000, "unique constraint %s.%s violated for table %s.%s with column values %s"
// *Cause: The row to update or insert violated the unique constraint.
// *Action: For XStreams, define a conflict resolution, or resolve the
// conflict and execute the error transaction using
// DBMS_APPLY_ADM.EXECUTE_ERROR.
26800, 00000, "Apply not the only subscriber for \"%s\".\"%s\"."
// *Cause: The combined capture and apply optimization could not be used
// since Apply was not the lone subscriber to the queue.
// *Action: Apply has to be the only subscriber to the queue.
26801, 00000, "More than one subscriber for \"%s\".\"%s\"."
// *Cause: Multiple subscribers were found when the combined capture and apply
// optimization was configured to only work for one subscriber.
// *Action: Configure a single subscriber, apply or propagation for the queue,
// or enable the optimization for multiple subscribers.
26802, 00000, "Queue \"%s\".\"%s\" has messages."
// *Cause: The combined capture and apply optimization could not be used
// since the queue had messages.
// *Action: Make sure queue is empty before starting apply and capture.
26803, 00000, "Subscribers have changed for queue \"%s\".\"%s\"."
// *Cause: The combined capture and apply optimization could not be used
// since the subscribers had changed.
// *Action: Optimization can be used only if the queue has a single subscriber.
26804, 00000, "Apply \"%s\" is disabled."
// *Cause: The apply process was disabled or aborted.
// *Action: Start the apply process.
26805, 00000, "Queue \"%s\".\"%s\" has rule based subscribers."
// *Cause: The combined capture and apply optimization could not be used
// since the queue had rule based subscribers.
// *Action: Make sure queue has no rule based subscribers before starting
// apply and capture.
26806, 00000, "Remote database could not support combined capture and apply optimization."
// *Cause: The remote database has a version lower than Oracle 11.0 and hence
// does not understand combined capture and apply optimization.
// *Action: Upgrade the remote database to Oracle 11.0 or above in order to
// use the combined capture and apply optimization.
26807, 00000, "Database link is not NULL for Apply with the name \"%s\" ."
// *Cause: The combined capture and apply optimization could not be used
// since apply_database_link was not NULL.
// *Action: Drop and recreate the apply with NULL value for apply_database_link.
26808, 00000, "Apply process %s died unexpectedly."
// *Cause: Apply process died unexpectedly.
// *Action: Check your system for anomalies and restart apply.
// If this error persists, contact Oracle Support Services.
// See trace file for more details.
26809, 00000, "Capture aborted: checkpoint-free mode requires combined capture and apply mode."
// *Cause: The requirements for combined capture and apply mode were broken.
// *Action: Restore the combined capture and apply mode and then
// restart the capture. If combined capture and apply mode is no
// longer desired, drop the existing checkpoint-free capture and
// create another one that will take checkpoints.
26810, 00000, "Apply \"%s\" on database \"%s\" is in the mode of combined capture and apply."
// *Cause: The combined capture and apply optimization could not be used
// because Apply was already in the mode of combined capture and
// apply.
// *Action: Do not configure two captures for one apply.
26811, 00000, "Client has already attached to %s apply \"%s\"."
// *Cause: The client has already attached to the specified apply process.
// *Action: Detach apply process before reattach.
26812, 00000, "An active session currently attached to XStream server \"%s\"."
// *Cause: An attempt was made to attach to the specified XStream server while
// another session was attached to it.
// *Action: Retry when there is no session attaching to the specified XStream
// server.
26813, 00000, "The value for argument \"ARRAY_SIZE\" is too small"
// *Cause: The value for argument "ARRAY_SIZE" was less than the number of
// columns in the requested column list.
// *Action: Check the return value for "NUM_COLUMNS" parameter then allocate
// all input arrays to at least that size and invoke the same
// OCI function again.
26814, 00000, "The value for argument %s exceeds maximum %s"
// *Cause: The value for specified value exceeded the maximum allowed.
// *Action: Correct the value of specified argument.
26815, 00000, "Error from Apply Network Receiver for Apply \"%s\" and Capture \"%s\"."
// *Cause: The Apply Network Receiver aborted due to an unexpected error.
// *Action: Query DBA_APPLY_ERROR to determine the error and then restart
// the Capture and Apply.
/
26816, 00000, "%s apply process \"%s\" (OS id %s) is exiting due to ORA-%s."
// *Cause: An apply process encountered an unexpected error.
// *Action: Query DBA_APPLY to examine the status of Apply and
// restart Apply if needed.
/
26817, 00000, "%s capture process \"%s\" is unable to communicate with capture server %s during initialization."
// *Cause: Capture server might not be started properly
// *Action: Fix any errors during capture server creation and re-start capture process
/
26818, 00000, "%s capture process %s receives an error from capture server."
// *Cause: Capture server received an error.
// *Action: Check log for error details.
/
26819, 00000, "%s capture server for apply \"%s\" and capture \"%s\"encounters disabled or aborted propagation \"%s\"."
// *Cause: Propagation was disabled or aborted.
// *Action: Start propagation.
/
26820, 00000, "%s capture server for apply \"%s\" and propagation \"%s\" becomes active and needs join capture process \"%s\"."
// *Cause: Capture server was waiting for propagation or apply to start
// *Action: Capture process needs restart (done automatically).
/
26821, 00000, "No propagation process found between source queue \"%s\".\"%s\" and destination queue \"%s\".\"%s\"."
// *Cause: Propagation has not been configured.
// *Action: Configure a propagation between specified queues and restart capture.
/
26822, 00000, "Failure in creating capture servers (ksv error code %s)."
// *Cause: Failure in ksv slave creation.
// *Action: Identify the actual ksv error and act accordingly.
/
26823, 00000, "%s capture server %s is unable to communicate with capture process \"%s\"."
// *Cause: Capture process was not started properly or was aborted.
// *Action: If Oracle GoldenGate, XStream or Streams capture process was stopped, then restart the
// capture process. Otherwise, fix any errors during the capture
// process creation and restart the capture process.
/
26824, 00000, "user-defined XStream callback error"
// *Cause: A value other than OCI_CONTINUE or OCI_SUCCESS was returned for
// the user-defined XStream callback function. Any returned value
// other than OCI_CONTINUE or OCI_SUCCESS is invalid.
// *Action: Verify that either OCI_CONTINUE or OCI_SUCCESS is returned from
// the user-defined XStream callback function.
/
26825, 00000, "STREAMS process \"%s\" is not configured as an XStream outbound server."
// *Cause: An attempt was made to attach to a STREAMS apply process, which was
// not configured as an XStream outbound server.
// *Action: Check the apply name or re-create the apply process as an XStream
// outbound server.
/
26826, 00000, "%s apply coordinator and apply slave are unable to communicate."
// *Cause: GoldenGate, XStream or Streams Apply process may have died unexpectedly.
// *Action: Check your system for anomalies and restart apply.
// If this error persists, contact Oracle Support Services.
// See trace file for more details.
/
26827, 00000, "Insufficient privileges to attach to XStream outbound server \"%s\"."
// *Cause: Sufficient privileges were not granted to attach to the specified
// XStream outbound server.
// *Action: Query DBA_XSTREAM_OUTBOUND view to get the connect_user value for
// the specified outbound server. Then modify the application to
// connect to the outbound server's database using this value.
/
26828, 00000, "XStream outbound server \"%s\" requires combined capture and apply mode."
// *Cause: The specified XStream outbound server was not in combined capture
// and apply mode.
// *Action: Restore the combined capture and apply mode and then
// restart the capture.
/
26829, 00000, "Cannot set \"DISABLE_ON_ERROR\" parameter to 'N'."
// *Cause: An attempt was made to change the "DISABLE_ON_ERROR" parameter for
// an XStream outbound server to 'N'.
// *Action: Remove invalid statement.
/
26830, 00000, "Cannot define handler for an XStream outbound server."
// *Cause: An attempt was made to define a handler for an XStream outbound
// server.
// *Action: Remove invalid statement.
/
26831, 00000, "Cannot delete or execute error transaction from XStream outbound server \"%s\"."
// *Cause: An attempt was made to delete or execute an error transaction
// from the specified XStream outbound server.
// *Action: Remove invalid statement.
/
26832, 00000, "Unable to create XStream outbound server \"%s\" due to existing handler."
// *Cause: An attempt was made to create the specified XStream outbound server
// while there was a handler defined for the specified server.
// *Action: Use DBMS_APPLY_ADM.SET_DML_HANDLER procedure to remove all
// handlers defined on the specified server then retry statement.
/
26833, 00000, "%s failed to update acknowledgment SCN for propagation \"%s\" from capture \"%s\" to apply \"%s\"."
// *Cause: propagation might have been modified after GoldenGate, XStream or Streams was started.
// *Action: Ensure propagation is configured properly and restart GoldenGate, XStream or Streams.
/
26834, 00000, "Unable to alter parameter '%s' because %s capture process is not configured to run locally"
// *Cause: An attempt was made to alter the specified capture parameter when
// the GoldenGate, XStream or Streams capture process was not configured to run on the local
// database.
// *Action: Remove the invalid parameter or use DBMS_CAPTURE_ADM.ALTER_CAPTURE
// procedure to alter the parameter.
/
26835, 00000, "The source database for XStream outbound server \"%s\" is invalid"
// *Cause: An attempt was made to add an XStream outbound server with a
// source database that was different from the associated capture's
// source database.
// *Action: Correct the value for the 'source_database' parameter in the call.
/
26836, 00000, "The specified rules must be created from the same subsetting condition"
// *Cause: An attempt was made to remove an outbound server's subset rules
// when the specified INSERT, UPDATE, and DELETE rules were not
// created from the same subsetting condition.
// *Action: Correct the rules in the statement.
/
26837, 00000, "Server \"%s\" is not an XStream inbound server"
// *Cause: An attempt was made to execute a procedure not appropriate on
// an XStream inbound server.
// *Action: Replace with a procedure appropriate for an XStream inbound server
// and resubmit.
/
26838, 00000, "Setting apply parameter \"%s\" is not permitted for XStream Outbound Server"
// *Cause: An attempt was made to set an apply parameter that was not applicable
// for XStream Outbound Server.
// *Action: Configure XStream Outbound Server using valid parameters. Check the
// documentation for valid parameter values.
/
26839, 00000, "Apply tag for apply \"%s\" is not permitted for XStream Outbound Server"
// *Cause: An attempt was made to set an apply tag that was not applicable
// for XStream Outbound Server.
// *Action: Do not set the apply tag when using XStream Outbound Server.
/
26840, 00000, "Combined capture and apply optimization is disabled because %s is unable to identify an apply for the source database \"%s\"."
// *Cause: There were multiple Streams apply processes using the same queue
// which made combined capture and apply (CCA) optimization not
// possible.
// *Action: If Streams performance is an issue, check the
// "Combined Capture and Apply Optimization" chapter in the
// "Oracle Streams Concepts and Administration" book. Then reconfigure
// the Streams processes to meet this optimization's requirements.
/
26841, 00000, "No subscribers are found for queue \"%s\".\"%s\"."
// *Cause: No propagation or apply was configured for the specified queue.
// *Action: Configure propagation or apply for the specified queue.
/
26842, 00000, "Setting apply directive \"%s\" is not permitted for XStream Outbound Server"
// *Cause: An attempt was made to set an apply directive that was not applicable
// for XStream Outbound Server.
// *Action: Configure XStream Outbound Server using valid directives. Check the
// documentation for valid directives.
/
26843, 00000, "Local propagation \"%s\" found for capture queue \"%s\".\"%s\"."
// *Cause: The combined capture and apply optimization could not be used
// because a local propagation was attached to the capture queue.
// *Action: Remove the local propagation and restart capture.
/
26844, 00000, "Found \"%s\" active automatic split jobs for %s Capture \"%s\" in DBA_STREAMS_SPLIT_MERGE"
// *Cause: Only one active split job is allowed for each GoldenGate, XStream or Streams Capture, but
// multiple active automatic split jobs were found in
// DBA_STREAMS_SPLIT_MERGE.
// *Action: Check trace to see how the jobs were submitted and drop them.
/
26845, 00000, "Found \"%s\" active split rows with the same cloned %s Capture \"%s\" in DBA_STREAMS_SPLIT_MERGE"
// *Cause: In DBA_STREAMS_SPLIT_MERGE, for active split rows, the column
// CLONED_CAPTURE_NAME should be unique. However, multiple rows were
// found whose ACTION_TYPE column is 'SPLIT', ACTIVE column is 'ACTIVE'
// and have the same CLONED_CAPTURE_NAME.
// *Action: Check trace to see how the rows were inserted and call
// DBMS_STREAMS_ADM.RECOVER_OPERATION() for error recovery.
/
26846, 00000, "Found \"%s\" active automatic merge jobs for cloned %s Capture \"%s\" in DBA_STREAMS_SPLIT_MERGE"
// *Cause: Only one active merge job is allowed for each cloned GoldenGate, XStream or Streams Capture
// , but multiple active automatic merge jobs were found in
// DBA_STREAMS_SPLIT_MERGE.
// *Action: Check trace to see how the jobs were submitted and drop them.
/
26847, 00000, "Found invalid %s type: \"%s\""
// *Cause: Invalid GoldenGate, XStream or Streams type to split off was found. Type should
// only be 'PROPAGATION'(1) or 'APPLY'(2).
// *Action: Check trace to see how the invalid GoldenGate, XStream or Streams type was created and
// correct it.
/
26848, 00000, "Split a nonexistent Streams Capture process \"%s\" in job \"%s\""
// *Cause: The job attempted to split a non-existent original Streams Capture.
// *Action: Drop the split job, or wait until the Streams Capture comes to
// existence.
/
26849, 00000, "Split a nonsplittable %s Capture process \"%s\" in job \"%s\""
// *Cause: The job tried to split a GoldenGate, XStream or Streams Capture that was not splittable.
// That is, the Capture either had less than two subscribers,
// or it was not the only Capture of its queue.
// *Action: Drop the split job, or wait untill the GoldenGate, XStream or Streams Capture becomes
// splittable.
/
26850, 00000, "Changes to queue subscribers were detected by %s capture process."
// *Cause: The subscribers for capture queue might have changed.
// *Action: Capture process will restart automatically.
/
26851, 00000, "Unable to connect to apply \"%s\" because it has connected to another capture."
// *Cause: Another capture process is already connected to apply.
// *Action: Wait for the connected capture process to terminate or
// abort the connected capture process.
/
26852, 00000, "Invalid NULL value for column_value parameter."
// *Cause: NULL is not allowed to be passed as the column value.
// *Action: Replace NULL with a proper AnyData instance containing NULL,
// e.g., sys.AnyData.ConvertVarchar2(NULL), as the column
// value if the column value is NULL.
//
/
26853, 00000, "invalid cca maximum percentage %s"
// *Cause: Specified percentage value was not in range 0 - 100.
// *Action: Specify a percentage value in the range 0 - 100.
/
26854, 00000, "%s %s has no enqueue or dequeue privileges to the queue."
// *Cause: The GoldenGate, XStream or Streams user did not have enqueue or dequeue
// privilege to the queue.
// *Action: Grant GoldenGate, XStream or Streams user enqueue or dequeue privileges to the queue.
/
26855, 00000, "%s %s has insufficient database privilege to access the queue."
// *Cause: The GoldenGate, XStream or Streams user did not have sufficient database privilege to
// access the queue.
// *Action: Grant GoldenGate, XStream or Streams user database privileges to access the queue.
/
26856, 00000, "STREAMS %s has insufficient database privilege to access the queue."
// *Cause: The GoldenGate, XStream or Streams user did not have sufficient database privilege to
// access the queue.
// *Action: Grant GoldenGate, XStream or Streams user database privileges to access the queue.
/
26857, 00000, "LCR position cannot be null (XID=%s)."
// *Cause: The position of an LCR in the specified transaction was null.
// *Action: Use OCILCRHeaderSet to define the LCR position.
/
26858, 00000, "LCR position must be strictly increasing (XID='%s', LCR position='%s', previous position='%s')."
// *Cause: The position of an LCR in the specified transaction was less than or
// equal to the previous LCR in transaction.
// *Action: Use OCILCRHeaderSet to correct the LCR position.
/
26859, 00000, "Server \"%s\" is not an XStream outbound server"
// *Cause: An attempt was made to execute a procedure not appropriate on
// an XStream outbound server.
// *Action: Replace with a procedure appropriate for an XStream outbound server
// and resubmit.
/
26860, 00000, "Different transactions must have different transaction IDs (XID='%s', LCR position='%s', previous commit position='%s')."
// *Cause: The position of an LCR in the specified transaction was greater than the position
// of the previous commit LCR in transaction with same transaction ID.
// *Action: Use different transaction IDs for different transactions.
/
26861, 00000, "XStream testing"
// *Document: NO
// *Cause:
// *Action:
26862, 00000, "LCR position must be greater than the processed low position of the XStream inbound server (XID='%s', LCR position='%s')."
// *Cause: The position of an LCR in the specified transaction
// was less than or equal to the processed low postion of the
// XStream inbound server.
// *Action: Use OCILCRHeaderSet to correct the LCR position.
/
26863, 00000, "Job \"%s\" showing as an active job in DBA_STREAMS_SPLIT_MERGE does not exist in DBA_SCHEDULER_JOBS."
// *Cause: An active job showing in DBA_STREAMS_SPLIT_MERGE did not exist.
// It may have been dropped accidently or something was wrong with it.
// *Action: Check trace to identify the problem and call
// DBMS_STREAMS_ADM.RECOVER_OPERATION() for error recovery.
/
26864, 00000, "Error occurred in %s automatic job: \"%s\""
// *Cause: An error has happened inside GoldenGate, XStream or Streams automatic job.
// *Action: Check trace for more detail.
/
26865, 00000, "must send a COMMIT LCR to end transaction '%s' before sending another transaction"
// *Cause: An attempt was made by a client application to send LCRs for a
// new transaction before sending a COMMIT LCR for the specified
// transaction.
// *Action: Modify the client application to send a COMMIT LCR at the end
// of the specified transaction.
/
26866, 00000, "The Queue of %s Apply process \"%s\" is not changeable."
// *Cause: Not all of the conditions for the Queue of a GoldenGate, XStream or Streams Apply process
// to be changeable were met. Conditions are: -The Apply process is not
// running. -The Apply process has no error. -The Apply process has no
// spilling. -The Apply process is not used for XStream Outbound or
// Inbound Servers. -The Apply process is a local Apply process. -The
// corresponding GoldenGate, XStream or Streams Capture process should be stopped.
// *Action: Make sure all of the conditions are met.
/
26867, 00000, "%s must be called during OCIXStreamOutLCRReceive execution"
// *Cause: An attempt was made to execute the specified function while
// OCIXStreamOutLCRReceive call was not in progress.
// *Action: Check your program and make sure the specified call is invoked
// during OCIXStreamOutLCRReceive callback function.
/
26868, 00000, "%s must be called during OCIXStreamInLCRSend execution"
// *Cause: An attempt was made to execute the specified function while
// OCIXStreamInLCRSend call was not in progress.
// *Action: Check your program and make sure the specified call is invoked
// during OCIXStreamInLCRSend callback function.
/
26869, 00000, "must attach to an XStream inbound server before executing %s function"
// *Cause: An attempt was made to invoke the specified function
// before executing OCIXStreamInAttach call.
// *Action: Add OCIXStreamInAttach call before the specified function.
/
26870, 00000, "cannot call %s while OCIXStreamInLCRCallbackSend call is still executing."
// *Cause: An attempt was made to invoke the specified call while
// OCIXStreamInLCRCallbackSend call was executing.
// *Action: Check your program and remove the specified call when there is an
// OCIXStreamInLCRCallbackSend call in progress.
/
26871, 00000, "unexpected %s call (expecting %s)"
// *Cause: Could be one of the following reasons:
// 1) An attempt was made to invoke OCIXStreamInChunkSend when
// the most recent LCR or chunk sent did not have the
// OCI_XSTREAM_MORE_ROW_DATA flag set;
// 2) An attempt was made to invoke OCIXStreamInLCRSend when
// the most recent LCR or chunk sent had OCI_XSTREAM_MORE_ROW_DATA
// flag set.
26872, 00000, "must attach to an XStream outbound server before executing %s function"
// *Cause: An attempt was made to invoke the specified function
// before executing OCIXStreamOutAttach call.
// *Action: Add OCIXStreamOutAttach call before the specified function.
/
26873, 00000, "cannot call %s while OCIXStreamOutLCRCallbackReceive call is still executing."
// *Cause: An attempt was made to invoke the specified call while
// OCIXStreamOutLCRCallbackReceive call was executing.
// *Action: Check your program and remove the specified call when there is an
// OCIXStreamOutLCRCallbackReceive call in progress.
/
26874, 00000, "%s Capture process \"%s\" cannot be split."
// *Cause: An attempt was made to split a GoldenGate, XStream or Streams Capture process that could not be split.
// That is, the Capture process either had less than two subscribers,
// or it was not the only Capture process of its queue.
// *Action: Wait until the GoldenGate, XStream or Streams Capture process can be split.
/
26875, 00000, "Timeout while %s automatic split job \"%s\" waits for the subscriber \"%s\" of Capture process \"%s\" to acknowledge split"
// *Cause: To split a subscriber of a GoldenGate, XStream or Streams Capture process, an automatic
// split job needs to wait until the subscriber acknowledges the split.
// The wait timed out.
// *Action:
/
26876, 00000, "invalid processed low-watermark (current position=%s; new position=%s)"
// *Cause: An attempt was made to set the processed low-watermark to a value
// that was less than the current processed low-watermark.
// *Action: Correct the processed low-watermark in OCIXStreamOutProcessedLWMSet
// call.
/
26877, 00000, "must reattach after an OCIXStreamOut call was interrupted"
// *Cause: An attempt was made to execute another OCIXStreamOut API when
// an earlier call was interrupted because the XStream outbound
// server was disabled or the client requested cancellation of
// the operation.
// *Action: Execute OCIXStreamOutAttach call to reattach to the same XStream
// outbound server.
/
26878, 00000, "inconsistent input LCR (LCR is '%s' type, expecting '%s')"
// *Cause: An attempt was made to send an LCR that was not consistent with
// the specified LCR type.
// *Action: Correct your application to specify an LCR type that agrees with
// the LCR to be sent.
/
26879, 00000, "\"SET_ENQUEUE_DESTINATION\" directive is not permitted on rules used by XStream outbound server \"%s\""
// *Cause: One or more rules, used by the specified XStream outbound server,
// had SET_ENQUEUE_DESTINATION directive defined.
// *Action: Execute the following:
// 1) Execute query
// SELECT xr.rule_owner, xr.rule_name, xr.rule_set_owner,
// xr.rule_set_name
// FROM dba_apply_enqueue e, dba_xstream_rules xr
// WHERE e.rule_owner = xr.rule_owner AND e.rule_name = xr.rule_name
// AND xr.streams_name = <specified outbound server>;
// 2) For each rule returned, execute DBMS_APPLY_ADM.SET_ENQUEUE_DESTINATION
// procedure to set the destination queue to null, or execute
// DBMS_RULE_ADM.REMOVE_RULE to remove that rule from its associated
// rule set.
/
26880, 00000, "\"SET_EXECUTE\" directive is not permitted on rules used by XStream outbound server \"%s\""
// *Cause: One or more rules, used by the specified XStream outbound server,
// had SET_EXECUTE directive defined.
// *Action: Execute the following:
// 1) Execute query
// SELECT xr.rule_owner, xr.rule_name, xr.rule_set_owner,
// xr.rule_set_name
// FROM dba_apply_execute e, dba_xstream_rules xr
// WHERE e.rule_owner = xr.rule_owner AND e.rule_name = xr.rule_name
// AND xr.streams_name = <specified outbound server>;
// 2) For each rule returned, use DBMS_APPLY_ADM.SET_EXECUTE
// procedure to set the EXECUTE parameter to TRUE, or use
// DBMS_RULE_ADM.REMOVE_RULE to remove that rule from its associated
// rule set.
/
26881, 00000, "ORA-%s: %s raised in %s automatic %s job:\"%s\".\"%s\" for Capture process \"%s\" and cloned Capture process \"%s\"."
// *Cause: An error was raised in a GoldenGate, XStream or Streams automatic split/merge job for the given original and cloned Capture processes.
// *Action: Check the corresponding split/merge row in DBA_STREAMS_SPLIT_MERGE view, alert log and trace file for details.
/
26882, 00000, "Timeout while %s automatic split/merge job:\"%s\".\"%s\" tried to lock Capture process \"%s\"."
// *Cause: The GoldenGate, XStream or Streams Capture process could be locked by other automatic split/merge jobs.
// *Action: No action required. The GoldenGate, XStream or Streams automatic split/merge job will retry automatically.
/
26883, 00000, "Timeout due to %s Apply process \"%s\" while merge original Capture process \"%s\" and cloned Capture process \"%s\"."
// *Cause: When merging two GoldenGate, XStream or Streams Capture processes, the merge needs to wait untill the
// Apply process of the cloned Capture process goes
// ahead of the slowest subscriber of the original Capture
// process. This wait timed out.
// *Action: Make sure the GoldenGate, XStream or Streams Apply process still works properly.
/
26884, 00000, "Not allowed to specify OCI_LCR_ROW_COLVAL_OLD with OCILCR_NEW_ONLY_MODE."
// *Cause: An attempt was made to call OCILCRRowColumnInfoGet function with
// OCI_LCR_ROW_COLVAL_OLD and OCILCR_NEW_ONLY_MODE.
// *Action: Change OCI_LCR_ROW_COLVAL_OLD to OCI_LCR_ROW_COLVAL_NEW or
// remove OCILCR_NEW_ONLY_MODE argument.
/
26885, 00000, "OCIXStreamInCommit called before OCIXStreamInFlush"
// *Cause: An attempt was made to call OCIXStreamInCommit before calling OCIXStreamInFlush.
// *Action: Call OCIXStreamInFlush prior to calling OCIXStreamInCommit.
/
26886, 00000, "LCR commit position ('%s') must be greater than the applied high position of the XStream inbound server (position='%s')."
// *Cause: The position of the commit LCR was less than or equal to the applied
// high postion of the XStream inbound server.
// *Action: Set the commit position higher than the applied high position.
/
26887, 00000, "Insufficient privileges to attach to XStream inbound server \"%s\"."
// *Cause: Sufficient privileges were not granted to attach to the specified
// XStream inbound server.
// *Action: Query DBA_XSTREAM_INBOUND view to get the apply_user value for
// the specified XStream outbound server. Then, modify the application
// to connect to the inbound server's database using this value.
/
26888, 00000, "Redo compatibilty must be 10.2 or greater"
// *Cause: XStream Out requires redo comptibility to be 10.2 or greater.
// *Action: Drop the outbound server.
/
26889, 00000, "LOB assembly not supported for PDML parent transaction %s, child transaction %s."
// *Cause: LOB assembly is not supported for PDML transactions.
// *Action: Disable LOB assembly, or filter out the PDML transaction.
/
26890, 00000, "Invalid update LCR on Oracle Sequence \"%s\".\"%s\""
// *Cause: The new value column list of an update LCR on an Oracle Sequence
// did not have non-null columns \"CYCLE#\", \"INCREMENT$\", \"CACHE\"
// and \"HIGHWATER".
// *Action: Make sure the new value column list has all the required columns.
// This might be a user error if the LCR is from an XStream In client.
/
26891, 00000, "Target Oracle Sequence \"%s\".\"%s\" has inconsistent parameters with the source."
// *Cause: The source and target Oracle Sequences did not have the identical
// cache size, increment value, and cycle flag needed for replication
// purposes.
// *Action: Make sure the source and target Oracle Sequences have identical
// parameters. This might be a user error if the LCR is from an
// XStream In client.
/
26892, 00000, "XStream feature not supported"
// *Cause: The XStream feature was not supported.
// *Action: No action necessary.
/
26893, 00000, "Input LCR must be a commit LCR"
// *Cause: The input LCR was not a commit LCR.
// *Action: Make sure the input LCR is a commit LCR.
/
26894, 00000, "Invalid \"%s\" in Apply Progress redo"
// *Cause: The value of the field reported was possibly corrupted.
// *Action: Contact Oracle Support Services.
/
26895, 00000, "Setting parameter \"%s\" of Streams process \"%s\" is only permitted for Oracle GoldenGate or XStream."
// *Cause: An attempt was made to set a parameter that is only allowed
// for XStream.
// *Action: Oracle GoldenGate license is needed to use this parameter.
/
26896, 00000, "Attempted to connect multiple Oracle GoldenGate Capture processes, including \"%s\", with XStream outbound server \"%s\" through queue \"%s\".\"%s\""
// *Cause: An attempt was made to connect multiple Oracle GoldenGate Capture
// processes through a queue with the XStream outbound server.
// *Action: Each XStream outbound server can only connect with one co-located
// Capture process. Remove extra Capture processes.
/
26897, 00000, "Unable to start %s capture \"%s\" because its subscribers \"%s\" and \"%s\" have different purpose"
// *Cause: An attempt was made to start an Oracle Capture process but it failed
// to start because its subscribers had conflicting purpose.
// *Action: Remove one of the specified subscribers from the capture queue.
/
26898, 00000, "Unable to create \"%s\" because there is an Oracle Capture process using the same queue \"%s\".\"%s\""
// *Cause: An attempt was made to create an inbound server using the same
// queue that was used by an Oracle Capture process.
// *Action: Resubmit the statement using another queue name.
/
26899, 00000, "internal %s error"
// *Cause: An internal Streams, XStream or GoldenGate error has occurred.
// *Action: Please contact Oracle customer support.
/
26900, 00000, "Streams failed to update data dictionary table for propagation \"%s\" from capture \"%s\" to apply \"%s\"."
// *Cause: The data dictionary table was corrupted.
// *Action: Validate the data dictionary table to restart GoldenGate, XStream or Streams capture process.
/
26901, 00000, "%s propagation sender in the combined capture and apply mode is to be suspended while apply is disabled."
// *Cause: The corresponding subscriber was dropped or split.
// *Action: No action necessary.
/
26902, 00000, "%s propagation sender in the combined capture and apply mode is to be suspended while apply is enabled."
// *Cause: The corresponding subscriber was dropped or split.
// *Action: No action necessary.
/
26903, 00000, "Invalid edition name \"%s\""
// *Cause: The edition associated with the LCR did not exist in the
// destination database.
// *Action: Check if the edition needs to be created manually on the destination
// database or if the CREATE EDITION statement for this edition
// has been applied properly on the destination database.
/
26904, 00000, "Invalid bind variable \"%s\" in LCR field expression."
// *Cause: In the statement handler, the bind variables listed in
// the SQL expression did not match the allowed Logical Change Record field names.
// *Action: Verify that all the bind variables listed in the expression are
// legal Logical Change Record fields.
/
26905, 00000, "Invalid LCR method expression \"%s\" in statement handler."
// *Cause: The Logical Change Record method listed was not allowed in the statement handler.
// *Action: Verify that the Logical Change Record method listed in the expression is a legal
// DBMS_LCR method.
26906, 00000, "No change handler exists."
// *Cause: There was no change handler for the specified apply, operation,
// source table, change table, and capture values.
// *Action: Query DBA_APPLY_CHANGE_HANDLERS view to find the correct change
// handler.
26907, 00000, "Insufficient privileges to set converge tag"
// *Cause: Privileges were insufficient to set converge tag.
// *Action: The invoker needs EXECUTE_CATALOG_ROLE or execute privilege on
// DBMS_STREAMS_ADM to set converge tag. Grant appropriate privileges
// to the invoker.
/
26908, 00000, "XStream API must be executed using a dedicated server process."
// *Cause: An attempt was made to execute XStream API using a shared server
// process.
// *Action: Replace the connect string in the client application to use a
// dedicated server process.
/
26909, 00000, "cannot reexecute an eager error"
// *Cause: An attempt was made to reexecute an eager error transaction.
// An eager transaction is applied before the apply process sees
// the commit or rollback for the transaction.
// *Action: Fix the cause of the eager error and restart the apply process.
// When apply is restarted, capture will automatically resend
// the transaction, and the transaction will be applied by the
// apply process.
/
26910, 00000, "user error %s encountered in eager mode"
// *Cause: An error was encountered during eager apply. An eager
// transaction is applied before the apply process sees the commit
// or rollback for the transaction. If an error occurs during
// an eager transaction, the transaction will be rolled back.
// *Action: Query the DBA_APPLY_ERROR view to determine the error and
// take the appropriate action. The apply process will need to be
// restarted to apply the transaction that had the error. When
// apply is restarted, capture will automatically resend the
// transaction, and the transaction will be applied by the apply
// process.
/
26911, 00000, "invalid oldest position (current position=%s; new position=%s)"
// *Cause: An attempt was made to set the oldest position to a value
// that was less than the current value.
// *Action: Correct the oldest_position argument in
// OCIXStreamOutProcessedLWMSet2 call.
/
26912, 00000, "not allowed to invoke '%s' while in committed data-only mode"
// *Cause: An attempt was made to call the specified API while the attached
// XStream server was in committed data-only mode.
// *Action: Perform one of the following:
// 1) If the invalid call is OCIXStreamOutProcessedLWMSet2, then change it
// to OCIXStreamOutProcessedLWMSet or pass a null oldest_position to
// OCIXStreamOutProcessedLWMSet2 call.
// 2) If the invalid call is OCIXStreamInProcessedLWMGet2, then change it
// to OCIXStreamInProcessedLWMGet or pass a null oldest_position to
// OCIXStreamInProcessedLWMGet2 call.
/
26913, 00000, "must connect to instance %s where %s %s server \"%s\" is running"
// *Cause: The client application was not connected to the same Oracle RAC
// instance as the specified Oracle GoldenGate or XStream server.
// *Action: Connect to the specified instance using the network service name
// obtained from the following query:
// SELECT network_name FROM all_queues q, all_xstream_outbound ob
// WHERE q.owner = ob.queue_owner AND q.name = ob.queue_name
// AND server_name = '<server_name>';
/
26914, 00000, "Unable to communicate with %s capture process \"%s\" from outbound server \"%s\"."
// *Cause: Capture process might not haven been started properly or was aborted.
// *Action: If Oracle GoldenGate or XStream capture process was stopped,
// then restart the capture process. Otherwise, query the
// DBA_CAPTURE view to determine the reason and take the appropriate
// action.
// If the error is ORA-4031, either increase the initialization
// parameter STREAMS_POOL_SIZE or increase the capture parameter
// MAX_SGA_SIZE or increase both.
// Refer to the XStream documentation for additional information on
// these parameters.
/
26915, 00000, "Unable to return Logical Change Record (LCR) information due to missing data dictionary."
// *Cause: The current session was unable to return the requested information on
// the given LCR due to missing dictionary data on that LCR.
// *Action: Detach and reattach the XStream outbound server. Then retry the
// current call.
/
26916, 00000, "Must call OCIPOGGRedoLogOpen function before OCIPOGGRedoLogRead"
// *Cause: An attempt was made to call OCIPOGGRedoLogRead before calling
// OCIPOGGRedoLogOpen.
// *Action: Add OCIPOGGRedoLogOpen call before OCIPOGGRedoLogRead.
/
26917, 00000, "OCIPOGG API must be executed using a dedicated server process."
// *Cause: An attempt was made to execute OCIPOGG API using a shared server
// process.
// *Action: Replace the connect string in the client application to use a
// dedicated server process.
/
26918, 00000, "Must use '%s' procedure for outbound server \"%s\"."
// *Cause: An attempt was made to execute START_APPLY on an outbound server
// that uses uncommitted data mode.
// *Action: Use the specified procedure instead.
/
26919, 00000, "Capture \"%s\" is not associated with queue \"%s\".\"%s\". "
// *Cause: The capture specified in the ADD_OUTBOUND procedure was not
// associated with the specified queue.
// *Action: Resubmit the ADD_OUTBOUND procedure after removing either the
// capture_name or the queue_name argument.
/
26920, 00000, "%s outbound server \"%s\" has been stopped."
// *Cause: The specified outbound server was stopped.
// *Action: Execute START_OUTBOUND procedure to restart the outbound server or
// execute OCIXStreamOutAttach function to reattach to the outbound
// server.
/
26921, 00000, "Cannot alter the start SCN or time of %s Capture \"%s\"."
// *Cause: An attempt was made to alter the start SCN or time for a capture
// while other outbound servers were still attached to it.
// *Action: Execute the following:
// 1) Get the names of other outbound servers currently attached to the
// specified Capture using the query:
// SELECT server_name
// FROM dba_xstream_outbound
// WHERE (status = 'ATTACHED') AND
// (server_name <> '<altered_server>') AND
// (capture_name = '<specified_capture_name>');
// 2) Detach the client application from each server_name returned.
// 3) Retry the operation.
/
26922, 00000, "user %s does not have LOGMINING privilege"
// *Cause: An attempt was made to start the capture process or attach to
// an outbound server when the specified user did not have
// LOGMINING privilege.
// *Action: Grant LOGMINING privilege to the specified user and
// resubmit the failed operation.
/
26923, 00000, "cannot configure %s outbound server \"%s\" with %s capture \"%s\" due to different purpose"
// *Cause: An attempt was made to configure an outbound server with a
// capture used for different purpose.
// *Action: Execute the following:
// 1) Get the purpose of each capture and its associated queue:
// SELECT capture_name, queue_owner, queue_name, purpose
// FROM dba_capture;
// 2) Resubmit the statement using a queue or capture with the same purpose.
/
26924, 00000, "cannot configure %s using \"%s\".\"%s\" queue because it is used by \"%s\" for %s purpose"
// *Cause: An attempt was made to configure the specified process using a
// queue already used by another process for different purpose.
// *Action: Resubmit the statement using another queue of the same purpose.
/
26925, 00000, "cannot configure outbound server \"%s\" with capture \"%s\" because it is not using apply-state checkpoint"
// *Cause: An attempt was made to configure an outbound server with a
// capture not using apply-state checkpoint.
// *Action: Specify a different capture in the ADD_OUTBOUND procedure
// or re-create the capture and resubmit the statement.
/
26926, 00000, "Unable to attach because capture \"%s\" is missing dictionary redo logs"
// *Cause: The specified capture was unable to locate the dictionary redo log.
// *Action: Check the state of the specified capture from gv$streams_capture
// to determine the SCN or filename of the missing log file. Confirm
// that the filename exists and is accessible online and also in the
// DBA_REGISTERED_ARCHIVED_LOG view. In addition, for local capture,
// confirm that an entry exists for the file in the V$ARCHIVED_LOG view.
// If an entry is missing, it can be added using the ALTER DATABASE
// REGISTER .... LOGFILE command, specifying the keyword LOGICAL
// LOGFILE or PHYSICAL LOGFILE as appropriate.
/
26927, 00000, "Unable to communicate with %s capture process \"%s\" from outbound server \"%s\"."
// *Cause: A timeout occurred while waiting for capture to respond.
// *Action: Check the state of the specified capture from GV$XSTREAM_CAPTURE view.
// Determine the reason for capture's unresponsiveness.
// If streams_pool_size is not set or set with an inadequate value, consider
// setting or increasing the value of this parameter.
/
26928, 00000, "Unable to communicate with %s apply coordinator process \"%s\" from outbound server \"%s\"."
// *Cause: A timeout occurred while waiting for apply coordinator to respond.
// *Action: Check the state of the specified apply coordinator from
// GV$STREAMS_APPLY_COORDINATOR view.
// Determine the reason for apply coordinator's unresponsiveness.
// If streams_pool_size is not set or set with an inadequate value, consider
// setting or increasing the value of this parameter.
/
26929, 00000, "altering an outbound server with a remote capture is not allowed"
// *Cause: An attempt was made to alter an outbound server with a remote
// capture.
// *Action: None
/
26930, 00000, "User \"%s\" does not have privileges to perform this operation"
// *Cause: An attempt was made to create, alter, or drop a process that has
// a different user (such as capture user or apply user) than the
// invoking user.
// *Action: Use the DBMS_XSTREAM_AUTH.GRANT_ADMIN_PRIVILEGE or
// DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE procedures to grant the
// invoking user proper privileges.
/
26931, 00000, "This procedure can only be invoked from the root container."
// *Cause: An attempt was made to execute a procedure in a multitenant container database (PDB) or a non-container database.
// *Action: Execute the procedure from the root container.
/
26932, 00000, "Streams configuration is not allowed in a container database."
// *Cause: An attempt was made to configure a Streams environment in a container database.
// *Action: None
/
26933, 00000, "Cannot start Streams process \"%s\" while in a container database."
// *Cause: An attempt was made to start the specified Streams process while in
// a container database.
// *Action: None
/
26934, 00000, "Streams synchronous capture is not supported in a container database."
// *Cause: An attempt was made to perform a DML operation on a table being
// captured by a Streams synchronous capture in a container database.
// *Action: Remove all Streams synchronous captures then reexecute the DML
// operation.
/
26935, 0000, "Unsupported type %s.%s for parameter for procedure %s.%s.%s.\n"
//* Cause: Apply encountered a procedure call with a parameter with an
// unsupported type.
//* Action: Modify the rules to filter out the procedure call.
/
26936, 00000, "must execute OCIPOGGCaptureAttach before invoking %s function"
// *Cause: An attempt was made to invoke the specified function
// before executing OCIPOGGCaptureAttach call.
// *Action: Add OCIPOGGCaptureAttach call before the specified function.
/
26937, 00000, "client has already attached to %s capture \"%s\"."
// *Cause: The client was already attached to the specified capture.
// *Action: Detach from the specified capture before reattaching.
/
26938, 00000, "cannot pack LCR into LCR buffer (buffer size is %s, LCR size is %s)"
// *Cause: The logical change record (LCR) buffer was not large enough to store the current LCR.
// *Action: Increase the buffer size in the OCIPOGGCaptureAttach call.
/
26939, 00000, "%s capture \"%s\" is disabled."
// *Cause: The capture process was disabled or aborted.
// *Action: Start the capture process.
/
26940, 00000, "OCIPOGGCapture API must be executed using a dedicated server process."
// *Cause: An attempt was made to execute OCIPOGGCapture API using a shared
// server process.
// *Action: Replace the connect string in the client application to use a
// dedicated server process.
26941, 00000, "unable to perform LOB assembly for table %s.%s"
// *Cause: The apply process was unable to perform the LOB assembly for a DML
// for the specified table.
// *Action: Verify that the storage type for the columns are compatible at the
// source and destination.
26942, 00000, "LCR should not contain old value for column %s in table %s.%s"
// *Cause: The LCR contained old values for LOB, XMLType and object columns.
// *Action: Remove old values for any LOB, XMLType and object columns in
// the LCR.
/
26943, 00000, "cross PDB operation not allowed"
// *Cause: An attempt was made to perform an operation on a container database different
// from the container database where the call was made.
// *Action: Log into the root container or into the container where you want to perform
// the requested action.
26944, 00000, "User \"%s\" attempted to invoke a procedure without proper permissions."
// *Cause: An attempt was made to invoke a procedure without proper permissions.
// *Action: Use the DBMS_GOLDENGATE_AUTH.GRANT_ADMIN_PRIVILEGE to grant the
// invoking user proper privileges.
26945, 00000, "unsupported hint %s"
// *Cause: The specified hint was not supported.
// *Action: Remove the hint from the SQL statement.
/
26946, 00000, "OCIPOGGRedoLog API not supported in CDB."
// *Cause: An attempt was made to call an OCIPOGGRedoLog API in a multitenant
// container database (CDB).
// *Action: Do not call the OCIPOGGRedoLog API in a CDB.
//
/
26947, 00000, "Oracle GoldenGate replication is not enabled."
// *Cause: The 'enable_goldengate_replication' parameter was not set to 'true'.
// *Action: Set the 'enable_goldengate_replication' parameter to 'true'
// and retry the operation.
// Oracle GoldenGate license is needed to use this parameter.
/
26948, 00000, "Streams API must be executed using a dedicated server process."
// *Cause: The dblink configured for the propagation from the capture queue
// to the apply queue is using a shared server connection.
// *Action: Modify the dblink for this propagation to use a dedicated server
// connection.
/
26949, 00000, "Advanced Replication is not allowed in a container database."
// *Cause: An attempt was made to configure an advanced replication
// in a multitenant container database (CDB).
// *Action: Do not call the Advanced Replication API in a CDB.
/
26950, 00000, "Streams tracing event"
// *Document: No
// *Cause:
// *Action:
/
26951, 00000, "table \"%s\".\"%s\" has column data type not supported by conflict resolution"
// *Cause: A conflict was detected, but unsupported columns prevented resolving the conflict.
// *Action: Remove conflict resolution configuration for tables with LOB, LONG, XML, object, or extended types.
/
26952, 00000, "could not clone from the specified clone_capture_name %s while creating capture process %s"
// *Cause: The specified clone_capture_name could not be used as a clone
// candidate while creating the capture process.
// *Action: Re-create the capture without setting clone_capture_name.
/
26953, 00000, "source database character set is not a subset of the mining database character set"
// *Cause: An attempt was made to configure a downstream capture but the source database character
// set was not a subset of the mining database character set.
// *Action: Use AL32UTF8 character set or other compatible character set for the mining database.
/
26954, 00000, "invalid protocol (opcode %s) received during XStream execution"
// *Cause: An internal protocol error occurred while executing an XStream
// function.
// *Action: Contact Oracle Support Services.
/
26955, 00000, "cannot capture TIMESTAMP WITH LOCAL TIME ZONE data type"
// *Cause: The capture process was unable to capture TIMESTAMP WITH LOCAL TIME ZONE data type
// because the source database time zone was not available.
// *Action: Refer to My Oracle Support Note 1928808.1 to set the source database time zone for the
// specified capture process.
/
26956, 00000, "capture %s created successfully but the source database time zone is not available"
// *Cause: The capture process was created successfully; however, it will not be able to capture
// TIMESTAMP WITH LOCAL TIME ZONE data type unless the source database time zone is set.
// *Action: Refer to My Oracle Support Note 1928808.1 to set the source database time zone for the
// specified capture process.
/
26957, 00000, "LCR identifier length is invalid."
// *Cause: A logical change record (LCR) identifier with an incompatible length was used.
// *Action: Use an LCR identifier compatible with release 12.2 or higher specification.
/
26958, 00000, "LCR identifier version is invalid."
// *Cause: An invalid logical change record (LCR) identifier version number was used.
// *Action: Use an LCR identifier version compatible with release 12.2 or higher specification.
/
26959, 00000, "SCN value does not fit in SCN version 1."
// *Cause: The system change number (SCN) value was too big to fit in the original SCN specification.
// *Action: Use an SCN value compatible with the original SCN specification.
/
26960, 00000, "automatic CDR already configured for table \"%s\".\"%s\""
// *Cause: Automatic conflict detection and resolution was already configured.
// *Action: Remove the automatic conflict detection and resolution
// configuration and retry.
/
26961, 00000, "automatic CDR not configured for table \"%s\".\"%s\""
// *Cause: Automatic conflict detection and resolution was not configured.
// *Action: None.
/
26962, 00000, "automatic CDR delta resolution not configured for column \"%s\""
// *Cause: Automatic conflict detection and resolution delta resolution was
// not configured.
// *Action: None.
/
26963, 00000, "automatic CDR column group cannot be created"
// *Cause: Automatic conflict detection and resolution was configured with
// column granularity.
// *Action: Remove the column-level configuration and retry.
/
26964, 00000, "column \"%s\" already assigned to a column group"
// *Cause: The column was already part of a column group.
// *Action: Remove the column from the column group and retry.
/
26965, 00000, "column group name \"%s\" not available"
// *Cause: The column group name was already in use.
// *Action: Remove the existing column group and retry.
/
26966, 00000, "Event for Streams/XStream bugs"
// *Document: NO
// *Cause: This is an internal event.
// *Action: N/A
/
26967, 00000, "delete tombstone table \"%s\".\"%s\" cannot be dropped"
// *Cause: An attempt was made to drop a delete tombstone table.
// *Action: Remove the automatic conflict detection and resolution from the
// base table.
/
26968, 00000, "column group \"%s\" not found"
// *Cause: The column group did not exist.
// *Action: Check if the column group needs to be created.
/
26969, 00000, "column \"%s\" not part of column group \"%s\""
// *Cause: The column did not belong to the column group.
// *Action: Check the column list and retry.
/
26970, 00000, "table \"%s'\" does not contain a primary key constraint"
// *Cause: An attempt was made to configure automatic conflict detection and
// resolution with delete tombstones on a table without a primary key.
// *Action: Add a primary key and retry.
/
26971, 00000, "resolution column \"%s\" not present"
// *Cause: The resolution column was not set in the logical change record (LCR).
// *Action: Manually resolve the conflict.
/
26972, 00000, "An apply process attempted to modify the SYSAUX tablespace."
// *Cause: An ALTER TABLESPACE DDL to SYSAUX was attempted by Oracle GoldenGate, XStream or Streams process.
// *Action: Only SYS is allowed to modify SYSAUX.
/
26973, 00000, "automatic CDR not supported for table \"%s\".\"%s\" which has long columns"
// *Cause: Automatic conflict detection and resolution (CDR) support
// for long columns failed. CDR does not support long columns.
// *Action: None.
/
26974, 00000, "Apply process is stuck in synchronous error handling mode."
// *Cause: The apply process ran out of memory or queue space while suspended for synchronous error handling.
// *Action: Restart Oracle GoldenGate Replicat process.
/
26975, 00000, "Only one instance of an Oracle GoldenGate downstream live standby permitted."
// *Cause: An attempt was made to create an additional capture session for an
// Oracle GoldenGate downstream live standby. At most, one instance
// of this capture type is permitted on a database.
// *Action: None.
/
/
/ 27000-27299 Reserved for Oracle8 Unix OSDs
/ (skgfr, skgfq, ...)
/
/ 27000 - 27030 keep for SKGFQ (Also 27190-27229)
/
27000, 00000, "skgfqsbi: failed to initialize storage subsystem (SBT) layer"
// *Cause: sbtinit returned an error, additional information indicates
// error
// *Action: verify that vendor's storage subsystem product is operating
// correctly
27001, 00000, "unsupported device type"
// *Cause: the specified device type is supported on this platform
// *Action: check V$BACKUP_DEVICE for supported device types
27002, 00000, "function called with invalid device structure"
// *Cause: internal error, aditional information indicates which
// function encountered error
// *Action: check for trace file and contact Oracle Support
27003, 00000, "cannot open file on device allocated with NOIO option"
// *Cause: internal error, a file is being created/retrieved on a device
// allocated with NOIO option, additional information indicates
// which function encountered error
// *Action: check for trace file and contact Oracle Support
27004, 00000, "invalid blocksize specified"
// *Cause: internal error, blocksize specified is incorrect for the
// device on which file is being created, aditional
// information indicates blocksize specified, and the
// function that encountered the error
// *Action: check for trace file and contact Oracle Support
27005, 00000, "cannot open file for async I/O on device not supporting async"
// *Cause: internal error, a file is being opened for async I/O on a
// device that does not support async I/O, additional
// information indicates which function encountered error
// *Action: check for trace file and contact Oracle Support
27006, 00000, "sbtremove returned error"
// *Cause: additional information indicates error returned by sbtremove,
// and the function that encountered the error
// *Action: verify that vendor's storage subsystem product is operating
// correctly
27007, 00000, "failed to open file"
// *Cause: sbtopen returned error, additional information indicates error
// returned from sbtopen, and the function that encountered
// the error
// *Action: verify that vendor's storage subsystem product is operating
// correctly
27008, 00000, "function called with invalid file structure"
// *Cause: internal error, aditional information indicates which
// function encountered error
// *Action: check for trace file and contact Oracle Support
27009, 00000, "cannot write to file opened for read"
// *Cause: internal error
// *Action: check for trace file and contact Oracle Support
27010, 00000, "skgfwrt: write to file failed"
// *Cause: sbtwrite returned error, additional information indicates
// error returned from sbtwrite
// *Action: verify that vendor's storage subsystem product is operating
// correctly
27011, 00000, "skgfrd: cannot read from file opened for write"
// *Cause: internal error
// *Action: check for trace file and contact Oracle Support
27012, 00000, "skgfrd: read from file failed"
// *Cause: sbtread returned error, additional information indicates
// error returned from sbtread
// *Action: verify that vendor's storage subsystem product is operating
// correctly
27013, 00000, "skgfqdel: cannot delete an open file"
// *Cause: internal error
// *Action: check for trace file and contact Oracle Support
27014, 00000, "skgfqpini: translation error while expanding SS_UDMPDIR"
// *Cause: Failure of sltln in skgfqpini
// *Action: Check additional return error for more information.
27015, 00000, "skgfcls: failed to close the file"
// *Cause: sbtclose returned error, additional information indicates
// error returned from sbtclose
// *Action: verify that vendor's storage subsystem product is operating
// correctly
27016, 00000, "skgfcls: sbtinfo returned error"
// *Cause: additional information indicates error returned from sbtinfo
// *Action: verify that vendor's storage subsystem product is operating
// correctly
27017, 00000, "skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH)"
// *Cause: media handle string length exceeds SSTMXQMH
// *Action: verify that vendor's storage subsystem product is operating
// correctly, and that the platform limit (SSTMXQMH) is atleast
// 64 (the limit specified for sbtinfo). additional information
// indicates the media handle string length returned by sbtinfo, and
// the limit (SSTMXQMH)
27018, 00000, "BLKSIZE is not a multiple of the minimum physical block size"
// *Cause: User-specified BLKSIZE (blocking factor) is not a multiple of
// the minimum block size that is permitted on this platform.
// *Action: Two ADDITIONAL INFORMATION messages are displayed which show the
// blocking factor provided by the user and the minimum physical
// block size. Specify a BLKSIZE that is an integral multiple
// of the minimum block size.
27019, 00000, "tape filename length exceeds limit (SBTOPMXF)"
// *Cause: length of tape filename provided to sequential I/O OSD functions is
// too long
// *Action: additional information indicates in which function this error is
// encountered, the length of filename provided, and the limit on
// filename
27020, 00000, "named devices not supported"
// *Cause: the platform or the specified device type does not support
// named devices
// *Action: do not specify device name or use a device type that supports
// named devices. Use V$BACKUP_DEVICE view to see what device
// types and names (if any) are available.
27021, 00000, "sequential file handle must be specified"
// *Cause: The filename which will be passed to sbtopen was not specified.
// *Action: Specify a filename and continue. If this is a backup set
// being created via Recovery Manager, use the 'format' option to
// specify the backup piece handle name.
27022, 00000, "skgfqsbi: could not allocate memory for media manager"
// *Cause: Oracle could not allocate memory required by the media management
// software which is linked with Oracle to provide backup/restore
// services.
// *Action: Increase the amount of memory available to the Oracle process and
// retry the backup/restore.
27023, 00000, "skgfqsbi: media manager protocol error"
// *Cause: The media management software which is linked with Oracle to
// provide backup/restore services did not provide its function
// pointer structure to Oracle.
// *Action: This is an internal error in the media management
// product. Contact the media management vendor.
27024, 00000, "skgfqsbi: sbtinit2 returned error"
// *Cause: sbtinit2 returned an error. This happens during a backup or
// restore operation.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27025, 00000, "skgfqsbi: invalid media manager context area size"
// *Cause: The media management software requested a context area size
// which is greater than the maximum allowable size.
// *Action: This is an internal error in the media management
// product. Contact the media management vendor.
27026, 00000, "skgfrls: sbtend returned error"
// *Cause: sbtend returned an error. This happens during a backup or
// restore operation.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27027, 00000, "sbtremove2 returned error"
// *Cause: sbtremove2 returned an error. This happens when deleting a backup
// file.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27028, 00000, "skgfqcre: sbtbackup returned error"
// *Cause: sbtbackup returned an error. This happens when creating a backup
// file during a backup operation.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27029, 00000, "skgfrtrv: sbtrestore returned error"
// *Cause: sbtrestore returned an error. This happens when retrieving a
// backup file during a restore operation.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27030, 00000, "skgfwrt: sbtwrite2 returned error"
// *Cause: sbtwrite2 returned an error. This happens while writing a backup
// file during a backup operation.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
/
/
/ 27031 - 27099 keep for SKGFR (if more needed, allocate another range later)
/
27031, 00000, "mirror resilvering functions not supported"
// *Cause: internal error
// *Action: check for trace file and contact Oracle Support
27032, 00000, "failed to obtain file size limit"
// *Cause: getrlimit system call returned an error
// *Action: check errno
27033, 00000, "failed to obtain file size limit"
// *Cause: ulimit system call returned an error
// *Action: check errno
27034, 00000, "maximum length of ORACLE_SID exceeded"
// *Cause: too many characters in the ORACLE_SID string
// *Action: rename the ORACLE_SID to a string of up to the maximum number of
// characters specified for your system
27035, 00000, "logical block size is invalid"
// *Cause: logical block size for oracle files must be a multiple of the
// physical block size, and less than the maximum
// *Action: block size specified is returned as additional information,
// check init.ora parameters, additional information also indicates
// which function encountered the error
27036, 00000, "translation error, unable to expand file name"
// *Cause: additional information indicates sltln/slnrm error, and also
// indicates which function encountered the error
// *Action: check additional information
27037, 00000, "unable to obtain file status"
// *Cause: stat system call returned an error, additional information
// indicates which function encountered the error
// *Action: check errno
27038, 00000, "created file already exists"
// *Cause: trying to create a database file, but file by that name already
// exists
// *Action: verify that name is correct, specify reuse if necessary
27039, 00000, "create file failed, file size limit reached"
// *Cause: an attempt was made to create a file that exceeds the process's
// file size limit, additional information indicates which function
// encountered the error
// *Action: raise the file size limit
27040, 00000, "file create error, unable to create file"
// *Cause: create system call returned an error, unable to create file
// *Action: verify filename, and permissions
27041, 00000, "unable to open file"
// *Cause: open system call returned an error, additional information
// indicates which function encountered the error
// *Action: check errno
27042, 00000, "not enough space on raw partition to fullfill request"
// *Cause: internal error, file too large for raw partition, additional
// information indicates which function encountered the error
// *Action: check for trace file and contact Oracle Support
27043, 00000, "unable to seek to beginning of file"
// *Cause: seek system call failed, additional information indicates which
// function encountered the error
// *Action: check errno
27044, 00000, "unable to write the header block of file"
// *Cause: write system call failed, additional information indicates which
// function encountered the error
// *Action: check errno
27045, 00000, "unable to close the file"
// *Cause: close system call failed, additional information indicates which
// function encountered the error
// *Action: check errno
27046, 00000, "file size is not a multiple of logical block size"
// *Cause: file size as indicated by stat is not correct, additional
// information indicates which function encountered the error
// *Action: verify that the file has not been overwritten or truncated
27047, 00000, "unable to read the header block of file"
// *Cause: read system call failed, additional information indicates which
// function encountered the error
// *Action: check errno
27048, 00000, "skgfifi: file header information is invalid"
// *Cause: possibly trying to use a non-database file as a database file
// *Action: verify that file is a database file
27049, 00000, "unable to seek to and read the last block"
// *Cause: an attempt was made to seek to and read the last block in file,
// additional information indicates which function encountered error
// *Action: check errno
27050, 00000, "function called with invalid FIB/IOV structure"
// *Cause: internal error, aditional information indicates which
// function encountered error
// *Action: check for trace file and contact Oracle Support
27051, 00000, "I/O error (simulated, not real)"
// *Document: NO
// *Cause: this is just a simulated error (not a real one), additional
// information indicates which function encountered the error
// *Action: none
27052, 00000, "unable to flush file data"
// *Cause: fsync system call returned error, additional information
// indicates which function encountered the error
// *Action: check errno
27053, 00000, "blocksize in file header not a multiple of logical block size"
// *Cause: the logical block size is invalid, additional information indicates
// the logical block size and the blocksize in the file header
// *Action: use a different logical block size, or do not reuse file
27054, 00000, "NFS file system where the file is created or resides is not mounted with correct options"
// *Cause: The file was on an NFS partition and either reading the mount tab
// file failed or the partition wass not mounted with the correct
// mount option.
// *Action: Make sure mount tab file has read access for Oracle user and
// the NFS partition where the file resides is mounted correctly.
// For the list of mount options to use refer to your platform
// specific documentation.
/27055
27056, 00000, "could not delete file"
// *Cause: unlink system call returned error
// *Action: check errno
27057, 00000, "cannot perform async I/O to file"
// *Cause: internal error, query is being asked about async vector I/O
// when the file does not support async I/O
// *Action: check for trace file and contact Oracle Support
27058, 00000, "file I/O question parameter is invalid"
// *Cause: internal error, invalid query is being asked
// *Action: check for trace file and contact Oracle Support
27059, 00000, "could not reduce file size"
// *Cause: ftruncate system call returned error
// *Action: check errno
27060, 00000, "could not set close-on-exec bit on file"
// *Cause: fcntl system call returned error
// *Action: check errno
27061, 00000, "waiting for async I/Os failed"
// *Cause: aiowait function returned error
// *Action: check errno
27062, 00000, "could not find pending async I/Os"
// *Cause: There should have been some async I/Os in the system
// but a blocking aiowait indicates that there are
// no more I/Os. It could be either because of an Oracle
// bug or the vendor OS bug or due to a NFS server not
// responding
// *Action: check Oracle trace file, OS message files and
// contact Oracle Support
27063, 00000, "number of bytes read/written is incorrect"
// *Cause: the number of bytes read/written as returned by aiowait
// does not match the original number, additional information
// indicates both these numbers
// *Action: check errno
27064, 00000, "cannot perform async I/O to file"
// *Cause: internal error, asked to perform async I/O when IOV
// indicates that it cannot be performed on the file
// *Action: check for trace file and contact Oracle Support
27065, 00000, "cannot perform async vector I/O to file"
// *Cause: internal error, asked to perform async vector I/O when
// it cannot be performed on the file
// *Action: check for trace file and contact Oracle Support
27066, 00000, "number of buffers in vector I/O exceeds maximum"
// *Cause: internal error, number of buffers in vector I/O exceeds
// maximum allowed by the OSD, additional information indicates
// both these numbers
// *Action: check for trace file and contact Oracle Support
27067, 00000, "size of I/O buffer is invalid"
// *Cause: internal error, buffer size is either 0, or greater than
// SSTIOMAX or not a multiple of logical block size, additional
// information indicates where in function the error was
// encountered and the buffer size
// *Action: check for trace file and contact Oracle Support
27068, 00000, "I/O buffer is not aligned properly"
// *Cause: internal error, buffer is not aligned to SSIOALIGN boundary,
// additional information indicates where in function the error
// was encountered and the buffer pointer
// *Action: check for trace file and contact Oracle Support
27069, 00000, "attempt to do I/O beyond the range of the file"
// *Cause: internal error, the range of blocks being read or written is
// outside the range of the file, additional information indicates
// the starting block number, number of blocks in I/O, and the
// last valid block in the file
// *Action: check for trace file and contact Oracle Support
27070, 00000, "async read/write failed"
// *Cause: aioread/aiowrite system call returned error, additional
// information indicates starting block number of I/O
// *Action: check errno
27071, 00000, "unable to seek to desired position in file"
// *Cause: lseek system call returned error, additional information
// indicates block number in file to which seek was attempted
// *Action: check errno
27072, 00000, "File I/O error"
// *Cause: read/write/readv/writev system call returned error, additional
// information indicates starting block number of I/O
// *Action: check errno
27073, 00000, "Trying to close a file which has async I/Os pending to be dequeued"
// *Cause: internal error, the file is being closed but not all async I/Os
// to the file have been dequeued, additional information indicates
// number of I/Os pending on the file
// *Action: check for trace file and contact Oracle Support
27074, 00000, "unable to determine limit for open files"
// *Cause: The getrlimit() system call returned an error.
// *Action: Check errno.
27075, 00000, "SSTMOFRC constant too large"
// *Cause: internal error
// *Action: check for trace file and contact Oracle Support
27076, 00000, "unable to set limit for open files"
// *Cause: The setrlimit() system call returned an error.
// *Action: Check errno.
27077, 00000, "too many files open"
// *Cause: internal error, the number of files opened through skgfofi has
// reached the limit
// *Action: Check for trace file and contact Oracle Support.
27078, 00000, "unable to determine limit for open files"
// *Cause: The getrlimit() system call returned an error.
// *Action: Check errno.
27079, 00000, "unable to set async IO limit"
// *Cause: The setting of the limit for async I/O has failed.
// *Action: Check errno.
27080, 00000, "too many files open"
// *Cause: The number of files opened has reached the system limit.
// *Action: Check the error, and set system configuration values.
27081, 00000, "unable to close the file"
// *Cause: The close() system call failed.
// *Action: Check errno.
27083, 00000, "waiting for async I/Os failed"
// *Cause: The aio_waitn() library call returned an error.
// *Action: Check errno.
27084, 00000, "unable to get/set file status flags "
// *Cause: The fcntl() system call with F_GETFL/F_SETFL flag returned an error.
// *Action: Check errno.
27086, 00000, "unable to lock file - already in use"
// *Cause: the file is locked by another process, indicating that it is
// currently in use by a database instance.
// *Action: determine which database instance legitimately owns this file.
27087, 00000, "unable to get share lock - file not readable"
// *Cause: share lock request was made on a file not open for read access.
// *Action: file must be open read-only or read-write to get a share lock.
27088, 00000, "unable to get file status"
// *Cause: file not open or file descriptor is invalid.
27089, 00000, "unable to release advisory lock"
// *Cause: release of file lock failed
// *Action: see errno
27090, 00000, "Unable to reserve kernel resources for asynchronous disk I/O"
// *Cause: The system call to reserve kernel resources for asynchronous I/O
// has failed.
// *Action: Check errno
27091, 00000, "unable to queue I/O"
// *Cause: read/write/readv/writev system call returned error, additional
// information indicates starting block number of I/O
// *Action: check errno
27092, 00000, "size of file exceeds file size limit of the process"
// *Cause: an attempt was made to open a file that exceeds the process's
// file size limit (ulimit), additional information shows the current
// limit (logical blocks) and the size of the file (logical blocks)
// *Action: increase the processes file size limit (ulimit) and retry
27093, 00000, "could not delete directory"
// *Cause: rmdir system call returned error
// *Action: check errno
27094, 00000, "raw volume used can damage partition table"
// *Cause: A raw device with VTOC information was provided as a database file.
// *Action: Make sure the disk partition that is provided to Oracle
// does not start at sector 0
27095, 00000, "fail to get the disk sector size"
// *Cause: The system call to get the sector size failed. Additional information
// indicates which function encountered the error.
// *Action: Check error number.
27096, 00000, "fail to get file size"
// *Cause: The system call to get file size failed. Additional information
// indicates which function encountered the error.
// *Action: Check error number.
27097, 00000, "failed to set Access Control List ownership for ASM devices"
// *Cause: The system call to set ACL ownership for ASM devices failed.
// Additional information indicates which function encountered the error.
// *Action: Refer to Microsoft documentation for an explanation
// of the accompanying error code and text.
/
27098, 00000, "failed to rename file"
// *Cause: The system call to change the file name failed.
// Additional information indicates which function encountered the
// error.
// *Action: Check the Oracle trace file for additional information on file name
// and reason for failure.
/
27099, 00000, "failed to create file"
// *Cause: The system call to create this file type in this file system failed.
// Check if the creation of this file type is supported in this file
// system. Additional information indicates which function encountered
// the error.
//
// *Action: Refer to Oracle documentation for additional details.
//
/
/ 27100 - 27139 keep for SKGM
/
27100, 00000, "shared memory realm already exists"
// *Cause: Tried to start duplicate instances, or tried to restart an
// instance that had not been properly shutdown
// *Action: Use a different instance name, or cleanup the failed instance's
// SGA
27101, 00000, "shared memory realm does not exist"
// *Cause: Unable to locate shared memory realm
// *Action: Verify that the realm is accessible
27102, 00000, "out of memory"
// *Cause: Out of memory
// *Action: Consult the trace file for details
27103, 00000, "internal error"
// *Cause: internal error
// *Action: contact Oracle support
27104, 00000, "system-defined limits for shared memory was misconfigured"
// *Cause: System-defined shared memory limits were inadequate for Oracle.
// *Action: Consult the alert file for details.
27105, 00000, "unable to support any system page size for shared memory allocation"
// *Cause: Current configuration was not supported by any system page size.
// *Action: Consult the alert file for details.
27106, 00000, "system pages not available to allocate memory"
// *Cause: System page count for supported page sizes was misconfigured.
// *Action: Configure system page count as recommended in the alert file.
27107, 0000, "AUTO value for USE_LARGE_PAGES parameter is no longer supported"
// *Cause: The USE_LARGE_PAGES configuration parameter was set to AUTO.
// *Action: Consult the alert file for details.
27120, 00000, "unable to remove shared memory segment"
// *Cause: shmctl() call failed
// *Action: check permissions on segment, contact Oracle support
27121, 00000, "unable to determine size of shared memory segment"
// *Cause: shmctl() call failed
// *Action: check permissions on segment, contact Oracle support
27122, 00000, "unable to protect memory"
// *Cause: mprotect() call failed
// *Action: contact Oracle support
27123, 00000, "unable to attach to shared memory segment"
// *Cause: shmat() call failed
// *Action: check permissions on segment, contact Oracle support
27124, 00000, "unable to detach from shared memory segment"
// *Cause: shmdt() call failed
// *Action: contact Oracle support
27125, 00000, "unable to create shared memory segment"
// *Cause: shmget() call failed
// *Action: contact Oracle support
27126, 00000, "unable to lock shared memory segment in core"
// *Cause: insufficient privileges to lock shared memory segment in core
// *Action: make sure process is running with necessary privileges.
27127, 00000, "unable to unlock shared memory segment"
// *Cause: insufficient privileges to unlock shared memory segment
// *Action: make sure process is running with necessary privileges.
27128, 00000, "unable to determine pagesize"
// *Cause: sysconf() call failed
// *Action: contact Oracle support
27129, 00000, "VLM Map operation failed"
// *Document: NO
// *Cause: Internal error
// *Action: Contact Oracle Support Services.
27130, 00000, "VLM Unmap operation failed"
// *Document: NO
// *Cause: Internal error
// *Action: Contact Oracle Support Services.
27131, 00000, "VLM Add operation failed"
// *Document: NO
// *Cause: Internal error
// *Action: Contact Oracle Support Services.
27132, 0000, "VLM Remove operation failed"
// *Document: NO
// *Cause: Internal error
// *Action: Contact Oracle Support Services.
27133, 00000, "unable to determine stacksize"
// *Cause: getrlimit() call failed
// *Action: Contact Oracle Support Services.
27134, 00000, "unable to set stacksize"
// *Cause: setrlimit() call failed
// *Action: Contact Oracle Support Services.
27135, 00000, "Operating System hard stack limit is set too low"
// *Cause: Operating System hard stack limit was set too low.
// *Action: Check additional information for current and minimum limit.
// Increase the Operating System hard stack limit and retry.
27136, 00000, "MPMT and VLM are both enabled"
// *Cause: When the _mpmt_enabled parameter is set to TRUE, none of the
// following parameters should be set to TRUE:
// * use_indirect_buffers
// * _db_block_cache_protect
// * _db_block_cache_clone
//
// *Action: Either turn off Multi Process Multi Threads (MPMT) or
// turn off all the other parameters.
27137, 00000, "unable to allocate large pages to create a shared memory segment"
// *Cause: Parameter USE_LARGE_PAGES set to only, but large pages were not
// configured properly
// *Action: Check alert file for more information
27138, 00000, "unable to allocate large pages with current parameter setting"
// *Cause: With parameter USE_LARGE_PAGES set to only, none of the
// following parameters can be set:
// * memory_target/memory_max_target
// * _db_block_cache_protect
// *Action: Either turn off the USE_LARGE_PAGES parameter setting, or turn off
// all the other parameters. Large pages are compatible with
// sga_target, sga_max_size and shared_pool_size.
27139, 00000, "unable to reserve Oracle VM mapping in process address space"
// *Cause: The address space region was already mapped.
// *Action: Contact Oracle Support Services.
/
/ 27140-27189 RESERVED FOR SKGP
/
27140, 0000, "attach to post/wait facility failed"
// *Cause: The program attempted to initialize the post/wait facility,
// but the facility could not be attached.
// *Action: Check for additional errors and contact Oracle Support.
27141, 0000, "invalid process ID"
// *Cause: process operation attempted using invalid process ID
// *Action: contact Oracle Support
27142, 0000, "could not create new process"
// *Cause: OS system call
// *Action: check errno and if possible increase the number of processes
27143, 0000, "OS system call failure"
// *Cause: OS system call failed
// *Action: check errno and contact Oracle support
27144, 0000, "attempt to kill process failed"
// *Cause: OS system call error
// *Action: check errno and contact Oracle Support
27145, 0000, "insufficient resources for requested number of processes"
// *Cause: OS system call error
// *Action: check errno and contact Oracle Support
27146, 0000, "post/wait initialization failed"
// *Cause: OS system call failed
// *Action: check errno and contact Oracle Support
27147, 0000, "post/wait reset failed"
// *Cause: OS system call failed
// *Action: check errno and contact Oracle Support
27148, 0000, "spawn wait error"
// *Cause: OS system call failed
// *Action: check errno and contact Oracle Support
27149, 0000, "assignment out of range"
// *Cause: internal error, requested conversion too large for type
// *Action: contact Oracle Support
27150, 0000, "attempt to notify process of pending oradebug call failed"
// *Cause: OS system call
// *Action: check errno contact Oracle Support
27151, 0000, "buffer not large enough to hold process ID string"
// *Cause: internal error
// *Action: contact Oracle Support
27152, 0000, "attempt to post process failed"
// *Cause: OS system call failed
// *Action: check errno and contact Oracle Support
27153, 0000, "wait operation failed"
// *Cause: OS system called failed
// *Action: check errno contact Oracle Support
27154, 0000, "post/wait create failed"
// *Cause: internal error, multiple post/wait creates attempted simultaneously
// *Action: check errno and contact Oracle Support
27155, 0000, "could not execute file"
// *Cause: OS system call failed
// *Action: check errno and contact Oracle Support
27156, 0000, "request for process information failed"
// *Cause: internal error
// *Action: contact Oracle Support
27157, 0000, "OS post/wait facility removed"
// *Cause: the post/wait facility for which the calling process is awaiting
// action is removed from the system
// *Action: check errno and contact Oracle Support
27158, 0000, "process control failure"
// *Cause: Oracle was unable to set the specified process control.
// *Action: Consult the Oracle Administrator's Guide.
27159, 0000, "failure setting process scheduling priority"
// *Cause: Oracle was unable to set the scheduling priority desired.
// *Action: Consult the Oracle Administrator's Guide.
27160, 0000, "process requested to perform operation"
// *Cause: The current process was requested to perform an operation by
// another process.
// *Action: This is used internally; no action is required.
27161, 0000, "request for Oracle binary information failed"
// *Cause: The program was unable to get information about the Oracle binary.
// *Action: Check for additional errors and contact Oracle support.
27162, 0000, "thread creation failed"
// *Cause: The program was unable to create a thread.
// *Action: Check errno and contact Oracle support.
27163, 0000, "out of memory"
// *Cause: The program ran out of memory when allocating a temporary
// data structure.
// *Action: Increase the amount of memory on the system.
27164, 0000, "tried to join detached thread"
// *Cause: The program tried to join a detached thread.
// *Action: This is an internal error; contact Oracle support.
27165, 0000, "tried to join thread that does not exist"
// *Cause: The program tried to join a thread that does not exist.
// *Action: This is an internal error; contact Oracle support.
27166, 0000, "tried to join current thread"
// *Cause: A thread in the program tried to join itself.
// *Action: This is an internal error; contact Oracle support.
27167, 0000, "Attempt to determine if Oracle binary image is stored on remote server failed"
// *Cause: OS dependent operation failed
// *Document: NO
// *Action: This is an internal error; contact Oracle support.
27168, 0000, "Translation from hostname to network address failed"
// *Cause: Internal error
// *Action: Contact Oracle Support Services.
27169, 0000, "OS signal mask operation failed"
// *Cause: OS dependent operation failed
// *Document: NO
// *Action: Check errno and contact Oracle support.
27170, 0000, "Oracle RAC option of current Oracle binary differs from running instance"
// *Cause: The Oracle installation environment may have been modified while the
// instance was running.
// *Action: Restore the environment to its original state when the instance was
// started or shutdown (abort) and restart the instance.
/
/ 27190 - 27229 reserved skgfq
/
27190, 00000, "skgfrd: sbtread2 returned error"
// *Cause: sbtread returned an error. This happens while reading a backup
// file during a restore operation.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27191, 00000, "sbtinfo2 returned error"
// *Cause: sbtinfo2 returned an error. This happens while retrieving
// backup file information from the media manager's catalog.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27192, 00000, "skgfcls: sbtclose2 returned error - failed to close file"
// *Cause: sbtclose2 returned an error. This happens while closing a backup
// file during a backup or restore operation.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27193, 00000, "sbtinfo2 did not return volume label"
// *Cause: sbtinfo2 did not return the volume label information for the
// backup file that was just created.
// *Action: This is an internal error in the media management
// product. Contact the media management vendor.
27194, 00000, "skgfdvcmd: sbtcommand returned error"
// *Cause: sbtcommand returned an error. This happens when an rman SEND
// command is issued.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27195, 00000, "proxy copy not supported"
// *Cause: An attempt was made to do a proxy backup or restore, but the
// media management software installed with Oracle does not support
// proxy copy.
// *Action: Re-run the backup in non-proxy mode, or contact the
// media management vendor if the software is supposed to support
// proxy copy.
27196, 00000, "skgfpbk: sbtpcbackup returned error"
// *Cause: sbtpcbackup returned an error. This happens when a proxy backup
// is begun.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27197, 00000, "skgfprs: sbtpcrestore returned error"
// *Cause: sbtpcrestore returned an error. This happens when a proxy restore
// is begun.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27198, 00000, "skgfpvl: sbtpcvalidate returned error"
// *Cause: sbtpcvalidate returned an error. This happens during a proxy
// backup or restore.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27199, 00000, "skgfpst: sbtpcstatus returned error"
// *Cause: sbtpcstatus returned an error. This happens during a proxy
// backup or restore.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27200, 00000, "skgfpgo: sbtpcstart returned error"
// *Cause: sbtpcstart returned an error. This happens during a proxy
// backup or restore.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27201, 00000, "skgfpcm: sbtpccommit returned error"
// *Cause: sbtpccommit returned an error. This happens during a proxy
// backup or restore.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27202, 00000, "skgfpen: sbtpcend returned error"
// *Cause: sbtpcend returned an error. This happens during a proxy
// backup or restore.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27203, 00000, "skgfpqb: sbtpcquerybackup returned error"
// *Cause: sbtpcquerybackup returned an error. This happens during a proxy
// backup.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27204, 00000, "skgfpqr: sbtpcqueryrestore returned error"
// *Cause: sbtpcqueryrestore returned an error. This happens during a proxy
// restore.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27205, 00000, "skgfpcn: sbtpccancel returned error"
// *Cause: sbtpccancel returned an error. This happens during a proxy
// restore.
// *Action: This error is returned from the media management software which is
// linked with Oracle. There should be additional messages which
// explain the cause of the error. This error usually requires
// contacting the media management vendor.
27206, 00000, "requested file not found in media management catalog"
// *Cause: A backup file used in a recovery manager catalog maintenance
// command was not found in the media management catalog.
// *Action: Retry the command with a different file.
27207, 00000, "syntax error in device PARMS - parentheses mismatch or missing"
// *Cause: User-supplied PARMS value has incorrect syntax.
// *Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn
27208, 00000, "syntax error in device PARMS - environment variable value missing"
// *Cause: User-supplied PARMS value has incorrect syntax.
// *Action: Retry the command with correct syntax: ENV=(var1=val1,var2=val2,..)
27209, 00000, "syntax error in device PARMS - unknown keyword or missing ="
// *Cause: User-supplied PARMS value has incorrect syntax. The server
// expected to find ENV or BLKSIZE, but found an unknown keyword.
// *Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn
27210, 00000, "syntax error in device PARMS"
// *Cause: User-supplied PARMS value has incorrect syntax.
// *Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn
/
27211, 00000, "Failed to load Media Management Library"
// *Cause: User-supplied SBT_LIBRARY or libobk.so could not be loaded. Call
// to dlopen for media library returned error. See Additional
// information for error code.
// *Action: Retry the command with proper media library. Or re-install
// Media management module for Oracle.
27212, 00000, "some entrypoints in Media Management Library are missing"
// *Cause: media library does not have one of the following entrypoints :
// sbtinfo, sbtread, sbtwrite, sbtremove, sbtopen, sbtclose, sbtinit
// *Action: Retry the command with proper media library.
27213, 00000, "failed to unload Media Management Library"
// *Cause: dlclose for media library returned error. See Additional
// Additional information for error code.
// *Action: contact Oracle Support.
27214, 00000, "skgfrsfe: file search failed"
// *Cause: The FindNextFile function returned unxpected error.
// *Action: Check errors on the error stack for an explanation
// why the search for files could not be successfully executed.
27215, 00000, "skgfgsmcs: sbtinfo2 returned unknown file"
// *Cause: During an sbtinfo2() call, the media management software
// returned information about an unknown backup file.
// *Action: Contact the media management vendor.
27216, 00000, "skgfgsmcs: sbtinfo2 returned a malformed response"
// *Cause: The media management software returned a malformed
// response during an sbtinfo2() call.
// *Action: Contact the media management vendor.
27217, 00000, "failed to load Media Management Library from secure location"
// *Cause: SBT libraries were not installed in a secure location.
// *Action: Remove SBT_SECURE parameter or Request third party vendors
// to provide patch that installs SBT libraries in secured
// locations as mandated by Oracle.
27218, 00000, "failed to read ACFS mirror"
// *Cause: An attempt to communicate with the Oracle Automatic Storage
// Management Cluster File System (Oracle ACFS) kernel driver failed.
// *Action: Check errors on the error stack for an explanation of
// why communication with ACFS was not successful.
27219, 00000, "syntax error in device PARMS - quotes missing or mismatch"
// *Cause: The user-supplied PARMS value had incorrect syntax. Either quotes
// were missing or there was a mismatch in the ENV parameter.
// *Action: Retry the command with matching quotes inside ENV parameter.
27230, 00000, "OS system call failure"
// *Cause: OS system call failed
// *Action: check errno and contact Oracle support
/
/ 27231 - 27249 reserved for sskgof
/
27231, 00000, "unable to close file"
// *Cause: A file could not be closed.
// *Action: See accompanying errors.
27232, 00000, "unable to get file information"
// *Cause: Information about the file could not be obtained.
// *Action: See accompanying errors.
27233, 00000, "file is not an ELF file"
// *Cause: A file was not an ELF file.
// *Action: Check for file corruption and contact Oracle Support Services.
27234, 00000, "unable to read file"
// *Cause: A file could not be read.
// *Action: See accompanying errors.
27235, 00000, "unable to map file region into memory"
// *Cause: A file region could not be mapped into memory.
// *Action: See accompanying errors.
27236, 00000, "unable to unmap file from memory"
// *Cause: A file region could not be unmapped from memory.
// *Action: See accompanying errors.
27237, 00000, "ELF file is not a relocatable object file"
// *Cause: An ELF file was not the expected type.
// *Action: Supply the expected type of file.
27238, 00000, "ELF file is not an executable"
// *Cause: An ELF file was not the expected type.
// *Action: Supply the expected type of file.
27239, 00000, "ELF file is not a shared object file"
// *Cause: An ELF file was not the expected type.
// *Action: Supply the expected type of file.
27240, 00000, "ELF file does not have a required section"
// *Cause: An ELF file did not have a required section.
// *Action: Contact Oracle Support Services.
27241, 00000, "ELF-shared library has multiple sections of the same type"
// *Cause: An ELF-shared library had multiple sections of the same type.
// *Action: Contact Oracle Support Services.
27242, 00000, "ELF file has invalid hash table entry size"
// *Cause: An ELF file had an invalid hash table entry size.
// *Action: Contact Oracle Support Services.
27243, 00000, "ELF file has too many relocation sections"
// *Cause: An ELF file had too many relocation sections.
// *Action: Contact Oracle Support Services.
27244, 00000, "unable to determine base value for data relocation from ELF file"
// *Cause: An ELF file was missing important information.
// *Action: Contact Oracle Support Services.
27245, 00000, "unable to dlopen() binary image"
// *Cause: A file could not be accessed via dlopen().
// *Action: See accompanying errors and make file available.
27246, 00000, "unable to open file"
// *Cause: A file could not be opened.
// *Action: See accompanying errors and make file available.
/
/ 27250 - 27269 reserved for sm
/
27250, 00000, "OS system call failure"
// *Cause: OS system call failed
// *Action: check errno and contact Oracle support
/
/ 27270 - 27274 reserved for sz
/
27270, 00000, "szingroup: malloc failed"
// *Cause: The malloc library call failed to allocate space for a group list.
// *Action: This is possibly an operating system error.
// Contact Oracle Support Services.
/
27271, 00000, "szingroup: group lookup failure"
// *Cause: The 'getgrnam_r' library call failed to determine the members of a
// UNIX group.
// *Action: This is an internal error. Contact Oracle Support Services.
/
/ 27300 - 27350 reserved for slos Error Reporting
/
27300, 00000, "OS system dependent operation:%s failed with status: %s"
// *Cause: OS system call error
// *Action: contact Oracle Support
/
27301, 00000, "OS failure message: %s"
// *Cause: OS system call error
// *Action: contact Oracle Support
//
27302, 00000, "failure occurred at: %s"
// *Cause: OS system call error
// *Action: contact Oracle Support
//
27303, 00000, "additional information: %s"
// *Cause: OS system call error
// *Action: contact Oracle Support
/
/ 27351 - 27499 RESERVED FOR NEW DATABASE SCHEDULER
/
27351, 00000, "conflicting values of job attributes %s and %s"
// *Cause: The values of two attributes passed in to the CREATE_JOBS call
// or the JOB object constructor conflicted with each other. This is
// usually because both attributes cannot be non-NULL at the same
// time.
// *Action: Resolve the conflict by changing the value of one of the
// attributes and issue the call again.
27352, 00000, "unable to get lock on queue"
// *Document: NO
// *Cause: An internal scheduler synchronization error
// *Action: Contact Oracle Customer Support.
27353, 00000, "job attribute %s is missing"
// *Cause: An attribute needed to fully specify a job was not passed in
// to a call to CREATE_JOBS or the JOB object constructor.
// *Action: Issue the call again with the required attribute set.
27354, 00000, "attribute %s cannot be set for %s jobs"
// *Cause: The CREATE_JOBS call or the JOB object constructor was called
// with an argument that is illegal in the case of lightweight
// or in-memory jobs.
// *Action: Set the argument to the default value and issue the call again.
27355, 00000, "unable to lock row cache entry"
// *Document: NO
// *Cause: Failure in scheduler concurrency control
// *Action: Contact Oracle Customer Support.
27356, 00000, "invalid job argument"
// *Cause: An invalid job argument was passed into either the CREATE_JOBS
// call or the JOB object constructor.
// *Action: Correct the argument value and issue the call again.
27357, 00000, "duplicate reference to job object %s"
// *Cause: The scheduler CREATE_JOBS call had two or more references
// to the same job.
// *Action: Eliminate the duplicate references and issue the call again.
27358, 00000, "unknown allocation type"
// *Document: NO
// *Cause: Failure in scheduler memory allocation routines
// *Action: Contact Oracle Customer Support.
27359, 00000, "duplicate reference to attribute %s of job %s"
// *Cause: The scheduler SET_JOB_ATTRIBUTES call had two or more
// references to a specific atrribute of a job.
// *Action: Eliminate the duplicate references and issue the call again.
27360, 00000, "unknown operation type"
// *Document: NO
// *Cause: Failure in scheduler linked list routines
// *Action: Contact Oracle Customer Support.
27361, 00000, "scheduler API invoked with illegal or inconsistent arguments"
// *Cause: A DBMS_SCHEDULER API call was invoked with either illegal or
// inconsistent arguments.
// *Action: Refer to scheduler documentation for the call, make the necessary
// changes and issue the call again.
27362, 00000, "batch API call completed with errors"
// *Cause: Some of the commands submitted to a scheduler batch API call
// could not be successfully carried out because of errors. Other
// commands in the batch may have completed successfully.
// *Action: Check the view SCHEDULER_JOB_ERRORS to see which commands failed
// and why. Make the appropriate corrections and submit the failed
// commands again.
27363, 00000, "invalid program for %s job"
// *Cause: An attempt was made to create a lightweight or in-memory job using
// an invalid program. A program used in a lightweight or in-memory job
// has to be enabled, has to be in the same schema as the job, and the
// program action has to be either a PL/SQL block or a stored procedure.
// *Action: Use a valid program for the lightweight job.
27364, 00000, "remote database \"%s\" already registered as %s"
// *Cause: The user attempted to register a remote database that was
// already registered.
// *Action: To update the registration information, the REPLACE argument
// of the REGISTER_REMOTE_DATABASE procedure should be set to
// TRUE. If the registration information is already current, no
// further action is needed.
27365, 00000, "job has been notified to stop, but failed to do so immediately"
// *Cause: The job specified in the stop_job command
// cannot be stopped immediately(because it is rolling back or blocked
// on a network operation), but it has been notified to stop. This
// means it will be stopped as soon as possible after its current
// uninterruptable operation is done.
// *Action: No action is required for the job to be stopped, but calling
// stop_job with force (if you have the privilege)
// may cause the job to be stopped sooner.
27366, 00000, "job \"%s\".\"%s\" is not running"
// *Cause: An attempt was made to stop a job that was not running.
// *Action: Verify the status of the job. If the job is running but this
// message is still being returned, contact Oracle support.
27367, 00000, "program \"%s\".\"%s\" associated with this job is disabled"
// *Cause: An attempt was made to run a job whose program has been disabled.
// *Action: Reenable the program before running the job.
27368, 00000, "job execution abandoned"
// *Document: NO
// *Cause: A slave had picked up a job for execution that was either currently
// being run or had just finished running on another RAC instance, so
// the slave abandoned the job without executing it.
// *Action: This error is used as part of communication between various
// scheduler modules. It should not be seen by an end-user. If
// this message is seen, contact Oracle Customer Support.
27369, 00000, "job of type EXECUTABLE failed with exit code: %s"
// *Cause: A problem was encountered while running a job of type EXECUTABLE.
// The cause of the actual problem is identified by the exit code.
// *Action: Correct the cause of the exit code and reschedule the job.
27370, 00000, "job slave failed to launch a job of type EXECUTABLE"
// *Cause: The scheduler ran into an error when the job slave tried to start
// a job of type EXECUTABLE. The rest of the error stack will provide
// more detailed information on what the exact problem was.
// *Action: Correct the problem specified in the error stack and reschedule
// the job.
27371, 00000, "jobs of type EXECUTABLE are not supported on this platform"
// *Cause: The user tried to create a job or program of type EXECUTABLE on a
// platform where such jobs are not supported.
// *Action: Switch to a different platform or create a different type of job
// or program.
27372, 00000, "length of action and arguments exceeds platform limit %s"
// *Cause: The total length of the job or program action and the arguments
// exceeds the platform limit specified.
// *Action: Reduce the total length by specifying fewer and/or shorter
// arguments
27373, 00000, "unknown or illegal event source queue"
// *Cause: The source queue specified for the event based job or event
// based schedule was either not found or was of the wrong type.
// *Action: Check if the queue exists. If it does make sure it is a
// multiple consumer queue and it is a post 8.1 compatible queue.
// Single consumer queues and old-style queues cannot be used
// as event source queues.
27374, 00000, "insufficient privileges on event source queue"
// *Cause: The job owner had insufficient privileges on the event source
// queue that was specified for the job.
// *Action: The job owner has to have dequeue privileges on event source
// queue or he has to have manage queue or dequeue any queue
// system privileges. Make sure one of these privileges is
// granted.
27375, 00000, "valid agent name must be specified for secure queues"
// *Cause: The queue specified for the event based job or schedule was
// a secure queue and either no agent name was specified or
// an invalid agent name was specified.
// *Action: If no agent name was specified, retry the call with a valid
// agent name. If the agent name was valid, check if the agent
// is currently subscribed to the queue and, in the case of jobs,
// check is the agent has been authorized to act as the job
// owner.
27376, 00000, "event condition cannot be NULL"
// *Cause: A null event condition was passed in for an event based job
// or schedule. This is not allowed.
// *Action: Pass in a legal event condition.
27377, 00000, "windows cannot have event based schedules"
// *Cause: Event based schedules for windows are currently not supported.
// *Action: Use a time-based schedule instead.
27378, 00000, "cannot stop jobs of type EXECUTABLE on this platform"
// *Cause: An attempt was made to stop a job of type EXECUTABLE on a platform
// where the stop operation was not supported.
// *Action: If the attempt to stop the job was made with the FORCE option
// set to FALSE, try again but change the FORCE option to TRUE.
27379, 00000, "INSTANCE_ID attribute conflicts with job class settings"
// *Cause: The value of the INSTANCE_ID attribute of the job conflicted with the
// value of the SERVICE attribute of its job class.
// *Action: Change the value of the INSTANCE_ID attribute or place the job
// in a job class whose settings do not conflict with the
// INSTANCE_ID attribute. Then re-enable the job.
27380,0000, "not enough units to satisfy the constraint"
// *Cause: There were not enough resources to satisfy the constraint.
// *Action: Add more resource units.
27381,0000, "job cannot run, state is RESOURCE_UNAVAILABLE"
// *Cause: The job could not run because one of the resources was in a BLOCKED_ALL_JOBS state.
// *Action: Change the resource to either ENFORCE_CONSTRAINTS or IGNORE_CONSTRAINTS.
27382,0000, "job type %s has errors in the job action"
// *Cause: There were errors in the job action when the FAIL_ON_SCRIPT_ERROR job
// attribute was set to TRUE.
// *Action: Ensure that the job action has no errors or set FAIL_ON_SCRIPT_ERROR job
// attribute to FALSE. FAIL_ON_SCRIPT_ERROR is only valid for
// SQL_SCRIPT, BACKUP_SCRIPT, EXECUTABLE and EXTERNAL_SCRIPT job types.
27399, 00000, "job type EXECUTABLE requires the CREATE EXTERNAL JOB privilege"
// *Cause: The owner of a job of type EXECUTABLE does not have the
// CREATE EXTERNAL JOB system privilege.
// *Action: Grant the CREATE EXTERNAL JOB system privilege to the job owner or
// create another job in a schema which does have the CREATE EXTERNAL
// JOB system privilege.
/
27400, 00000, "In a PDB, the JOB_QUEUE_PROCESSES initialization parameter can only be set to 1000 or 0."
// *Cause: A value other than 1000 or 0 was specified for the JOB_QUEUE_PROCESSES initialization parameter.
// Inside a pluggable database (PDB), the JOB_QUEUE_PROCESSES initialization parameter can only
// accept the values of 1000 or 0 to indicate whether or not jobs should run in the PDB.
// *Action: Specify a proper value for this parameter.
/
/ 27401 - 27410 Reserved for scheduler events
/
27401, 00000, "Scheduler debug event"
// *Document: NO
// *Cause:
// *Action:
/
27402, 00000, "Scheduler tracing event"
// *Document: NO
// *Cause:
// *Action:
/
27403, 00000, "scheduler stop job event"
// *Document: NO
// *Cause:
// *Action:
/
27404, 00000, "Scheduler internal testing event"
// *Document: NO
// *Cause:
// *Action:
/
/ 27411 - 27420 Reserved for scheduler repeat interval errors
/
27411, 0000, "empty string is not a valid repeat interval."
// *Cause: An empty string '' was provided as a repeat interval for a window
// or a schedule.
// *Action: Specify a valid repeat interval, e.g.,
// 'FREQ=DAILY;BYHOUR=8;BYMINUTE=0;BYSECOND=0' for a job that executes
// daily at 8am.
/
27412, 00000, "repeat interval or calendar contains invalid identifier: %s"
// *Cause: The calendar string or calendar definition for the repeat interval
// of a job, schedule or window contained an unsupported keyword or
// reference to an undefined calendar.
// *Action: Correct the repeat interval such that it no longer contains the
// invalid keyword.
/
27413, 00000, "repeat interval is too long"
// *Cause: The repeat interval consisted of a calendar string larger than the
// maximum size allowed.
// *Action: Use a shorter calendar string for the repeat interval.
/
27414, 00000, "Invalid %s clause value"
// *Cause: The BY clause value was not recognized or was out-of-range for the
// frequency specified.
// *Action: Specify a valid BY clause value.
/
/
27415, 00000, "repeat interval or calendar must start with a frequency clause"
// *Cause: The specified calendar string for the repeat interval did not start
// with a frequency clause.
// *Action: Create a repeat interval that starts with a frequency clause,for example
// 'FREQ=YEARLY;BYMONTH=FEB'
/
27416, 00000, "BYDAY clause in repeat interval or calendar contains an invalid weekday"
// *Cause: The BYDAY clause of the repeat interval contained a value that
// did not represent a weekday.
// *Action: Use the correct three letter abbreviations for weekdays, for example
// MON for Monday and FRI for Friday.
/
27417, 00000, "BYWEEKNO clause requires YEARLY clause"
// *Cause: A repeat interval or calendar contained a BYWEEKNO clause
// with a frequency other than yearly.
// *Action: Remove the BYWEEKNO clause or change the frequency to YEARLY.
/
27418, 00000, "syntax error in repeat interval or calendar"
// *Cause: The repeat interval or calendar definition was not
// recognized as valid syntax.
// *Action: Specify a valid repeat interval.
/
27419, 00000, "unable to determine valid execution date from repeat interval"
// *Cause: The specified repeat interval contained conflicting clauses that
// made it impossible to ever find a matching date, e.g.,
// 'FREQ=YEARLY;BYMONTH=FEB;BYMONTHDAY=31'. Alternatively,
// the scheduler reached its maximum number of attempts to try to
// find a valid execution date. This occurs when theoretically
// there is a valid execution date far in the future, but the
// scheduler took too many attempts to determine this date.
// *Action: Remove the conflicting clauses, or simplify the repeat interval
// so that it is easier to determine the next execution date.
/
27420,00000, "Following message from %s interval interpreter"
// *Cause: The repeat interval or calendar definition was not
// recognized as valid syntax.
// *Action: Specify a valid repeat interval.
27421, 00000, "calendar expression restriction %s encountered"
// *Cause: The calendar expression was not valid because a limit test failed.
// For example, the maximum value of the interval that can be specified
// in the INTERVAL clause is limited to a value derived from the frequency clause.
// *Action: Specify a valid calendar definition.
/
27422, 00000, "usage of %s not supported in embedded calendar application \"%s\".\"%s\""
// *Cause: The main calendar definition used an embedded calendar in an INCLUDE,
// EXCLUDE, INTERSECT, or FREQ clause for which extra limitations
// apply.
// *Action: Remove the specific clause from the calendar definition.
/
27423,00000, "calendar clause %s specified more than once"
// *Cause: The calendar definition contained a clause that was specified
// twice or more times.
// *Action: Append the values in the second clause to the first clause
// and remove the second clause.
27424,00000, "calendar clauses %s and %s are incompatible"
// *Cause: The calendar definition contained clauses that were incompatible.
// *Action: Change or remove either clause.
/
27425,00000, "instance_id cannot be specified if database is not in Oracle RAC mode"
// *Cause: 'stop_job' was called with 'instance_id' outside Oracle RAC mode.
// *Action: Do not specify this parameter for 'stop_job' unless in Oracle RAC mode.
/
/
/ 27431 - 27500 Scheduler API errors continuation
/
27431, 00000, "chain \"%s\".\"%s\" has a user-managed rule set"
// *Cause: An attempt was made to modify a rule set that is not managed by the
// Scheduler.
// *Action: Modify the rule set directly using the dbms_rule_adm package or
// create another chain without specifying a rule set.
27432, 00000, "step \"%s\" does not exist for chain \"%s\".\"%s\""
// *Cause: The step specified does not exist for the given chain.
// *Action: Reissue the command using a step that exists for this chain.
27433, 00000, "cannot alter state of step \"%s\" for job \"%s\".\"%s\" to %s"
// *Cause: The step cannot be changed to the requested state. The state of a
// running step cannot be changed. A step which is running or has
// already run cannot be run again.
// *Action: Wait until the step has finished running.
27434, 00000, "cannot alter chain step job \"%s\".\"%s\".\"%s\""
// *Cause: A step job of a running chain cannot be altered, only stopped or
// dropped.
// *Action: Stop or drop the chain step job or alter the running chain step
// instead.
27435, 00000, "chain job terminated abnormally"
// *Cause: A chain job has ended abnormally. The error code for the running
// chain could not be retrieved.
// *Action: No action necessary. The job will run again when it is scheduled
// to.
27436, 00000, "Scheduler agent operation failed with message: %s"
// *Cause: The Scheduler agent encountered an unexpected error when trying to
// perform the specified action.
// *Action: Review the provided message and the Scheduler agent log for
// information on how to fix the issue or contact Oracle Support
// Services.
27451, 00000, "%s cannot be NULL"
// *Cause: An attempt was made to set a NOT NULL scheduler attribute to NULL.
// *Action: Reissue the command using a non-NULL value for the specified
// attribute.
27452, 00000, "\"%s\" is an invalid name for a database object."
// *Cause: An invalid name was used to identify a database object.
// *Action: Reissue the command using a valid name.
27453, 00000, "\"%s\" is an invalid job or program argument name."
// *Cause: An invalid job or program argument name was specified.
// *Action: Reissue the command using a valid name for this argument.
27454, 00000, "argument name and position cannot be NULL"
// *Cause: The name or position of a program or job argument was defined as
// NULL.
// *Action: Reissue the command providing either a valid argument name or
// valid argument position.
27455, 00000, "Only \"SYS\" is a valid schema for a %s."
// *Cause: A non-SYS schema was specified for an object that must be in the
// SYS schema.
// *Action: Reissue the command, leaving out the schema name or using the
// schema name of SYS.
27456, 00000, "not all arguments of program \"%s\".\"%s\" have been defined"
// *Cause: The number_of_arguments attribute of the named program did not
// match the actual number of arguments that have been defined.
// *Action: Define as many arguments as the number of arguments, or change
// the number of arguments.
27457, 00000, "argument %s of job \"%s\".\"%s\" has no value"
// *Cause: No value was provided for the job argument with the specified
// position.
// *Action: Provide a value for the job argument using any of the
// set_job_xxxx_value() routines. Or, when using a named program,
// specify a default value for the corresponding argument of the
// program.
27458, 00000, "A program of type PLSQL_BLOCK cannot have any arguments."
// *Cause: An attempt was made to create or enable a program of type
// PLSQL_BLOCK with arguments. This is not allowed.
// *Action: Change the number of arguments to zero, or change the type
// of the program.
27459, 00000, "A program of type EXECUTABLE must have character-only arguments."
// *Cause: A program of type EXECUTABLE was created or enabled with one or
// more arguments of non-character datatypes.
// *Action: Change the arguments to be of character-only datatypes.
27460, 00000, "cannot execute disabled job \"%s\".\"%s\""
// *Cause: An attempt was made to run a job that is disabled.
// *Action: Enable the job and then reschedule the job.
27461, 00000, "The value for attribute %s is too large."
// *Cause: The value that was provided for the specified attribute was too
// large.
// *Action: Reissue the command using a smaller or shorter value.
27463, 00000, "invalid program type %s"
// *Cause: An invalid program type was specified.
// *Action: Reissue the command using a valid program type.
27464, 00000, "invalid schedule type %s"
// *Cause: An invalid schedule type was specified.
// *Action: Reissue the command using a valid schedule type.
27465, 00000, "invalid value %s for attribute %s"
// *Cause: An invalid value was provided for the specified attribute.
// *Action: Reissue the command using a valid value for this attribute.
27466, 00000, "internal scheduler error: %s"
// *Document: NO
// *Cause: The scheduler ran into an internal error.
// *Action: Contact Oracle Customer Support.
27467, 00000, "invalid datatype for %s value"
// *Cause: The value provided for the named scheduler attribute was of an
// invalid datatype.
// *Action: Reissue the command using a value of the correct datatype.
27468, 00000, "\"%s\".\"%s\" is locked by another process"
// *Cause: An attempt was made to read or modify the state of the named
// scheduler object when another process was also updating the same
// object and held the lock.
// *Action: Retry the operation. Scheduler locks are held for a very
// short duration. If the error persists, contact Oracle Support.
27469, 00000, "%s is not a valid %s attribute"
// *Cause: A non-existant attribute was specified.
// *Action: Reissue the command using a valid attribute for that specific
// scheduler object.
27470, 00000, "failed to re-enable \"%s\".\"%s\" after making requested change"
// *Cause: A change was made to an enabled scheduler object that caused it
// to become disabled.
// *Action: Alter the object so that it becomes valid and then enable it.
27471, 00000, "window \"%s\".\"%s\" is already closed"
// *Cause: An attempt was made to close a window that was not open.
// *Action: No action required.
27472, 00000, "invalid metadata attribute %s"
// *Cause: An invalid metadata attribute was specified.
// *Action: Reissue the command using a valid metadata attribute.
27473, 00000, "argument %s does not exist"
// *Cause: An argument which was specified does not exist.
// *Action: Reissue the command using an argument name defined by the program
// or using a valid argument position.
27474, 00000, "cannot give both an argument name and an argument position"
// *Cause: An argument was specified using both a name and a position.
// *Action: Reissue the command using either the argument name or the argument
// position but not both.
27475, 00000, "unknown %s \"%s\".\"%s\""
// *Cause: The specified object did not exist, privileges were not granted,
// or the object was of the wrong type.
// *Action: Specify an object of the correct type on which you have privileges.
27476, 00000, "\"%s\".\"%s\" does not exist"
// *Cause: A database object was specified that does not exist.
// *Action: Reissue the command using an object that exists or create a new
// object and then reissue this command.
27477, 00000, "\"%s\".\"%s\" already exists"
// *Cause: An attempt was made to create an object with a name that has
// already been used by another object in the same schema.
// *Action: Reissue the command using a different name or schema.
27478, 00000, "job \"%s\".\"%s\" is running"
// *Cause: An attempt was made to drop a job that is currently running.
// *Action: Stop the job and then reissue the command, or reissue the command
// specifying the force option to stop the job first.
27479, 00000, "Cannot %s \"%s\".\"%s\" because other objects depend on it"
// *Cause: An attempt was made to drop or disable a scheduler object that has
// jobs associated with it without specifying the force option.
// *Action: Alter the associated jobs so they do not point to the scheduler
// object being dropped or disabled and then reissue the
// command. Alternatively reissue the command specifying the force
// option. If
// the force option is specified and a scheduler object is being
// dropped, all associated jobs will be disabled.
27480, 00000, "window \"%s\" is currently open"
// *Cause: An attempt was made to drop a window that is currently open, or
// to manually open a window while another window is already open.
// *Action: Close the window that is open and then reissue the command, or
// reissue the command while setting the force option to TRUE.
27481, 00000, "\"%s\".\"%s\" has an invalid schedule"
// *Cause: An attempt was made to enable a job or window that has an invalid
// schedule.
// *Action: Alter the schedule of the job or window so that it is valid and
// then reissue the enable command.
27482, 00000, "The scheduler credential \"%s\".\"%s\" is unusable."
// *Cause: An attempt was made to use a scheduler credential for which the
// key to decrypt its password was lost. Therefore, the password of the
// credential could not be retrieved.
// *Action: Reset the PASSWORD attribute of the credential by calling
// DBMS_CREDENTIAL.UPDATE_CREDENTIAL.
27483, 00000, "\"%s\".\"%s\" has an invalid END_DATE"
// *Cause: An attempt was made to enable a job or window that has an invalid
// end_date. Either the end_date is before the start_date or the
// end_date is in the past.
// *Action: Alter the job or window so that the end date becomes valid
// (possibly null) and then reissue the command.
27484, 00000, "Argument names are not supported for jobs without a program."
// *Cause: An attempt was made to set or reset a job argument by using the
// name of the argument. Identifying job arguments by their name is
// only supported in combination with jobs that are based on programs.
// Jobs that are not using a program cannot have named arguments.
// *Action: Use argument position instead of name and then issue the command
// again.
27485, 00000, "argument \"%s\" already exists at a different position"
// *Cause: An attempt was made to create or replace an argument with a name
// that is already used by an argument at a different position.
// *Action: Use a different name for the argument or drop or alter the
// argument which already exists with this name and then reissue the
// command.
27486, 00000, "insufficient privileges"
// *Cause: An attempt was made to perform a scheduler operation without the
// required privileges.
// *Action: Ask a sufficiently privileged user to perform the requested
// operation, or grant the required privileges to the proper user(s).
27487, 00000, "invalid object privilege for a %s"
// *Cause: The granted object privilege is not valid for the specified
// scheduler object.
// *Action: Check the scheduler documentation to verify which object privileges
// can be granted on which scheduler objects.
27488, 00000, "unable to set %s because %s was/were already set"
// *Cause: An attempt was made to set an object's attribute even though one
// or more conflicting attributes of the same object had already been
// set.
// *Action: Set the other conflicting attributes to NULL and then reissue
// the command.
27489, 00000, "unable to process job \"%s\".\"%s\" from job class \"%s\""
// *Cause: An error was encountered while processing the named job from
// the specified job class.
// *Action: Resolve the error for this job and then reissue the command.
// See the next error message on the stack to find out what the error
// for the job is.
27490,0000, "cannot open disabled window \"%s\".\"%s\""
// *Cause: The user tried to open a disabled window.
// *Action: Enable the window and then try to open it again.
27491,0000, "repeat_interval and start_date cannot both be NULL"
// *Cause: An attempt was made to set both repeat_interval and start_date
// to equal NULL for a Scheduler window or schedule.
// *Action: If either repeat_interval or start_date is set to equal NULL,
// the other should be set to a non-NULL value.
27492,0000, "unable to run job \"%s\".\"%s\": scheduler unavailable"
// *Cause: A job run with current session set to false can not be issued
// if the scheduler is not active. Check value of job_queue_processes
// parameter, issue dbms_ijob.set_enabled(true),
// database is in upgrade/migrade mode, database is in data guard
// mode, or scheduler attribute SCHEDULER_DISABLED is set to TRUE
// *Action: Run the job in the current session or activate the scheduler
27493,0000, "In-memory job \"%s.%s\" cannot be modified"
// *Cause: Once enabled, the full in-memory job could not be further modified.
// *Action: The only actions that can be taken now are to stop or drop the
// job.
27494,0000, "operation not permitted on lightweight and in-memory jobs"
// *Cause: An attempt was made to perform an action that was not
// permitted.
// *Action: Check Oracle Scheduler documentation to see which actions can be
// performed on the desired job.
27495,0000, "attribute %s cannot be set for in-memory jobs"
// *Cause: An attempt was made in a CREATE or SET_ATTRIBUTE call to set
// an attribute that could not be set for run-time in-memory jobs.
// *Action: If you need to set this attribute, use either regular or
// lightweight jobs.
27496,0000, "credential \"%s\".\"%s\" is disabled"
// *Cause: An attempt was made to run a job, file watcher or external
// procedure whose credential was disabled.
// *Action: Reenable the credential before running the job, file watcher or
// external procedure.
27497,0000, "operation is not permitted inside a pluggable database"
// *Cause: This operation was not permitted in a pluggable database.
// *Action: Log into the root database and retry the operation.
27498,0000, "resource constraint object type mismatch"
// *Cause: Not all of the resource constraints of a resource were of the same type.
// *Action: Delete existing constraints for the resource.
27499,0000, "in-memory job metadata is too large"
// *Cause: The in-memory job was too large. Due to the need to keep
// in-memory jobs efficient and performing well,we limit the size
// of in-memory job metadata to 8 kilobytes. This includes the
// space used for job argument values.
// *Action: Reduce the size of the job metadata and try again. If all the
// metadata is needed, then you should create some other type of
// job.
/
/ 27500-27599 RESERVED FOR IPC ERRORS
/
27500, 00000, "inter-instance IPC error"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the extra information and contact Oracle Support Services.
27501, 00000, "IPC error creating a port"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27502, 00000, "IPC error deleting OSD context"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27503, 00000, "IPC error attempting to cancel request"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27504, 00000, "IPC error creating OSD context"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27505, 00000, "IPC error destroying a port"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27506, 00000, "IPC error connecting to a port"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27507, 00000, "IPC error disconnecting from a port"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27508, 00000, "IPC error sending a message"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27509, 00000, "IPC error receiving a message"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27510, 00000, "IPC error waiting for a request to complete"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27512, 00000, "IPC error posting a process"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27513, 00000, "parameter %s contains invalid value %s"
// *Cause: The program could not identify the value as an IP address.
// *Action: Change the value to be a valid IP address.
27514, 00000, "IPC error copying memory to remote process"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27515, 00000, "inadequate memlock limit or driver settings"
// *Cause: Inter Process Communication(IPC) queue creation failed due to
// inadequate memlock limit or driver settings.
// *Action: Set a higher memlock limit and review the network driver
// settings to ensure that this limit is accepted.
27528, 00000, "Transport: %s required by %s is not available"
// *Cause: The IP addresses assigned to the instance did not support
// the specified transport.
// *Action: Check the IP addresses used in the alert log
// and contact Oracle Support Services.
27529, 00000, "IPC IP address %s is not available."
// *Cause: The IP address assigned to the instance was not associated with
// any network adapters.
// *Action: Ensure that the IP address is assigned to a network adapter.
27530, 00000, "IPC Ephemeral ports on IP address %s are exhausted."
// *Cause: The ephemeral ports on the IP address assigned to the instance
// were exhausted.
// *Action: Increase the ephemeral port range.
// 27531, 00000, "<<reuse me>>"
// *Cause:
// *Action:
27532, 00000, "IPC global name service error"
// *Cause: The global name space service used by KSXP reported an error
// *Action: Check additional error messages in the process trace file and
// contact Oracle Support Services.
// 27533, 00000, "<<reuse me>>"
// *Cause:
// *Action:
// 27534, 00000, "<<reuse me>>"
// *Cause:
// *Action:
// 27535, 00000, "<<reuse me>>"
// *Cause:
// *Action:
// 27536, 00000, "<<reuse me>>"
// *Cause:
// *Action:
// 27537, 00000, "<<reuse me>>"
// *Cause:
// *Action:
// 27538, 00000, "<<reuse me>>"
// *Cause:
// *Action:
// 27539, 00000, "<<reuse me>>"
// *Cause:
// *Action:
// 27540, 00000, "<<reuse me>>"
// *Cause:
// *Action:
// 27541, 00000, "<<reuse me>>"
// *Cause:
// *Action:
27542, 00000, "Failed to unprepare a buffer prepared for remote update"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27543, 00000, "Failed to cancel outstanding IPC request"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27544, 00000, "Failed to map memory region for export"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27545, 00000, "Fail to prepare buffer for remote update"
// *Cause: This is an operating system/cluster interconnect error.
// *Action: Check the value of errno and contact Oracle Support Services.
27546, 00000, "Oracle compiled against IPC interface version %s.%s found version %s.%s"
// *Cause: A misconfiguration or installation error occurred.
// *Action: Install the IPC library for this release of Oracle.
//
27547, 00000, "Unable to query IPC OSD attribute %s"
// *Cause: This is an operating system-dependent IPC error.
// *Action: Contact Oracle support Services.
27548, 00000, "Unable to unprepare IPC buffer"
// *Cause: This is an operating system-dependent IPC error.
// *Action: Contact Oracle support Services.
//
27550, 00000, "Target ID protocol check failed. tid vers=%s, type=%s, remote instance number=%s, local instance number=%s"
// *Cause: The local Oracle Real Application Cluster instance and remote
// instance are running with incompatible implementation of the
// inter-instance IPC protocol library. A misconfiguration or
// installation error occurred.
// *Action: Check additional error messages in the alert log and the process
// trace file.
27551, 00000, "Number of IPC ports exceeds OSD limit %s"
// *Document: NO
// *Cause: Attempted to create more IPC ports than is supported by OSD
// *Action: Contact Oracle Support Services.
27552, 00000, "exception accessing Global Shared Memory (GSM) in Oracle RAC cluster"
// *Cause: GSM is used to provide shared memory semantics on an Oracle RAC cluster.
// An error has occurred accessing shared memory hosted on a remote node.
// This is an internal programming error.
// *Action: Contact Oracle Support Services.
//
27553, 00000, "incompatible IPC settings in Oracle RAC cluster"
// *Cause: Inter-process Communication (IPC) settings were not compatible with other
// instances in the Oracle RAC cluster.
// *Action: Check additional error messages in the alert log and IPC0 trace file.
//
/
/ 27600-27699 RESERVED FOR EXADATA (SAGE) and HOST/CELL ERRORS
/
/
27601, 00000, "Cell storage initialization failed, cell library error code [%s]"
// *Cause: Cell storage client did not succeed in initializing.
// *Action: Check the value of errno and contact Oracle Support Services.
27602, 00000, "Failure to publish network status information, cell library error code [%s]"
// *Cause: Network status information publishing failed.
// *Action: Check the value of errno and contact Oracle Support Services.
27603, 00000, "Cell storage I/O error, I/O failed on disk %s at offset %s for data length %s"
// *Cause: Cell storage I/O read or write failed, possibly due to a configuration problem or a hardware failure.
// *Action: Check the value of errno and contact Oracle Support Services.
27604, 00000, "Cell storage ioctl error, ioctl failed on disk %s"
// *Cause: Ioctl operation on a cell storage disk failed.
// *Action: Check the value of errno and contact Oracle Support Services.
27605, 00000, "Smart I/O failed as a handle could not be obtained to the cell \"%s\" as the cell is not accessible."
// *Cause: The cell could have been unavailable.
// *Action: Ensure the cell is available. Check the network connectivity.
27606, 00000, "Smart I/O failed because the diskgroup was found to be unmounted. tablespace number: \"%s\", file number: \"%s\""
// *Cause: The diskgroup to which the specified file belongs was found
// to be unmounted.
// *Action: Ensure that the diskgroup to which the specified file belongs
// is mounted.
27607, 00000, "Smart I/O failed because there were no online disks. tablespace number: \"%s\", file number: \"%s\""
// *Cause: There were no online disks found for the specified file.
// *Action: Ensure the diskgroup to which the specified file belongs to is mounted.
// Ensure that the disks are online. Check the availability of
// cells and check the network.
27608, 00000, "Smart I/O failed because the disk \"%s\" on the cell \"%s\" was not open. error code: \"%s\", \"%s\""
// *Cause: The specified disk on the specified cell could not be opened.
// *Action: Ensure the cell is available. Check the network.
27609, 00000, "Smart I/O failed due to a network error to the cell \"%s\". error code \"%s\", \"%s\""
// *Cause: The specified cell could not be connected to.
// *Action: Ensure that the cell is available. Check the network.
27610, 00000, "Smart I/O failed due to shortage of memory on the cell \"%s\""
// *Cause: The specified cell had a shortage of memory to perform smart I/O.
// *Action: Reduce the parallel degree or number of Oracle sessions executing
// smart I/O.
27611, 00000, "Smart I/O failed due to a block corruption detected on the host. The block was received from cell \"%s\". disk: \"%s\", block: \"%s\", disk offset: \"%s\""
// *Cause: The data block indicated was corrupted on the host, but
// a corruption was not found on the cell.
// *Action: This may be due to a transient network error or a real block
// corruption. Check your network for any errors. Analyze the
// segment to which the file belongs. If there is indeed a
// corruption, try to restore the block using RMAN block recovery.
// If there is a trace file, report the errors in it to Oracle
// Support Services. If analyze did not report an error and network
// did not have any error, report the problem to Oracle Support
// Services as this appears to be a software error.
27612, 00000, "Smart I/O failed due to a block corruption detected on the cell \"%s\". disk: \"%s\", block: \"%s\", disk offset: \"%s\""
// *Cause: The data block indicated was found to be corrupted on the cell.
// *Action: This may be due to a software error or a real data corruption.
// Analyze the segment. If there is indeed a block corruption, try to
// restore the block using RMAN block level recovery. If there
// is a trace file, report the errors in it to Oracle Support
// Services. If analyze did not report an error, report
// the problem to Oracle Support Services as this appears to
// be a software error.
27613, 00000, "Smart I/O failed due to an I/O error on the cell \"%s\". disk: \"%s\", block: \"%s\", disk offset: \"%s\" I/O size: \"%s\""
// *Cause: An I/O request failed on the specified cell and disk.
// *Action: Check the specified disk on the cell.
27614, 00000, "Smart I/O failed due to an error \"%s, %s\" from the cell \"%s\". disk: \"%s\", block: \"%s\", disk offset: \"%s\" I/O size: \"%s\""
// *Cause: An I/O request failed, due to an internal error on the specified
// cell and disk.
// *Action: Report the problem to Oracle Support Services along with
// the process trace file and alert log.
27615, 00000, "Smart I/O file to ASM disk translation failed with error: %s."
// *Cause: An internal error caused a smart I/O operation to fail.
// *Action: Report the problem to Oracle Support Services along with
// the process trace file and alert log.
27616, 00000, "ASM Allocation Unit: %s"
// *Cause: This error message is usually accompanied by another message,
// indicating the real problem. This message exists to provide
// additional information to Oracle Support Services.
// *Action: Check the next error message.
27617, 00000, "Smart I/O failed because of an internal error. Cell \"%s\", disk \"%s\", cell library error code \"%s, %s\", error information \"%s\""
// *Cause: An internal error caused a smart I/O operation to fail.
// *Action: Report the problem to Oracle Support Services along with
// the process trace file and alert log.
27618, 00000, "Smart I/O failed because of an internal error. Cell \"%s\", cell library error code \"%s, %s\", error information \"%s\""
// *Cause: An internal error caused a smart I/O operation to fail.
// *Action: Report the problem to Oracle Support Services along with
// the process trace file and alert log.
27619, 00000, "Smart I/O failed because of an internal error when determining the time zone file version. Error code \"%s\""
// *Cause: An internal error caused a smart I/O operation to fail.
// *Action: Report the problem to Oracle Support Services along with
// the process trace file and alert log.
27621, 00000, "The value of %s is not valid for parameter %s"
// *Cause: Incorrect value is specified for an internal parameter.
// *Action: This parameter should only be set by Oracle Support Services.
// Check the additional diagnostic information in the trace file and
// contact Oracle Support Services for recommendations
// on setting this parameter.
27622, 00000, "Cell automation worker action interrupted"
// *Document: NO
// *Cause: Cell automation worker action was interrupted.
// *Action: This is used internally; no action is required.
27623, 00000, "Cell automation SQL action failed"
// *Cause: Cell automation manager or worker process failed to execute
// SQL action through OCI recursive call.
// *Action: Check the alert log and process trace file for additional
// information. Contact Oracle Support Services if the errors
// specified in the trace file cannot be corrected.
27624, 00000, "Smart I/O failed because the number of reconnects to the cell \"%s\" exceeded the maximum allowed \"%s\"."
// *Cause: The number of reconnects to a cell exceeded the maximum allowed.
// This problem indicates a possible network problem or a software problem
// on the cell.
// *Action: If the cellsrv is being restarted repeatedly, in a short interval,
// check the system load. The problem may be corrected by rebooting
// the cell. If the system is not overloaded, the repeated restarts
// are likely due to software problem. Report the problem to Oracle
// Support Services along with alert log and trace files. If the cellsrv
// is not restarting, the problem may be in the IB network. Check the
// network between the host and all the cells.
27625, 00000, "Exadata configuration failed."
// *Cause: One or both of the files, cellinit.ora and cellip.ora, were either invalid or missing.
// *Action: Check if the files, cellinit.ora and cellip.ora, are both present.
// They can be found in the $OSSCONF directory. If both are present,
// check if their contents are valid and correct.
// If the files are invalid or missing, produce files with
// valid information in the $OSSCONF directory. For information on
// how to set up these files, see the Exadata Users Guide.
27626, 00000, "Exadata error: %s (%s)"
// *Cause: The cause of this error is dependent on the context in which this error
// is reported.
// *Action: See the primary error reported with this error.
27627, 00000, "Software edition incompatible with Exadata storage."
// *Cause: Oracle Exadata can be used only with Oracle Database Enterprise Edition.
// *Action: Check if Oracle is linked with the Enterprise Edition options.
/
27628, 00000, "An invalid value was specified for the parameter %s."
// *Cause: An invalid value was specified for a parameter.
// *Action: Check the additional diagnostic information in the trace file and
// contact Oracle Support Services if further help is required.
27629, 00000, "External table smart I/O failed because the cell is not accessible."
// *Cause: The cell was unavailable.
// *Action: Ensure the cell is available.
27630, 00000, "External table smart scan debugging event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: None
27631, 00000, "External encryption or decryption is disabled."
// *Cause: Either decryption was disabled in the cellinit.ora initialization
// parameter file, or the cryptography mode requested by the database
// was incompatible with what was available on the cell.
// *Action: No action is necessary. The Exadata cell returns data in
// pass-through mode when encryption or decryption is required.
27632, 00000, "Cryptography engine verification debugging event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: None
27633, 00000, "RDBMS instance failed because no Exadata cells were discovered"
// *Document: NO
// *Cause: This Oracle binary is enabled on Exadata and SuperCluster only.
// However, the instance could not discover any Exadata cells.
// *Action: If this is not Exadata or SuperCluster, then no action is
// required. Otherwise, check the alert.log for additional
// error information.
/
/ 27700-27800 RESERVED FOR MGA
/
27777, 00000, "MGA Tracing On"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: None
27778, 00000, "MGA namespace is already marked for deletion."
// *Cause: Managed Global Area (MGA) namespace was already marked for deletion.
// No further attaches are allowed.
// *Action: None.
27779, 00000, "MGA segment creation failure"
// *Cause: The Managed Global Area (MGA) segment creation failed.
// *Action: Check the other error messages for additional information.
/
/ 27800-27900 RESERVED FOR EVENT NOTIFICATION (KSEVN)
/
27800, 00000, "invalid configuration (%s) for event creation (%s)."
// *Cause: Invalid configuration values were given while creating the event.
// *Action: None.
/
27801, 00000, "event notification handle not valid"
// *Cause: The event notification handle was not valid.
// *Action: None.
/
27888, 00000, "Event Notification Tracing On"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: None
/
/ 28000-28499 RESERVED FOR SECURITY RELATED ERRORS
/
/
28000, 00000, "The account is locked."
// *Cause: The wrong password was entered multiple consecutive times as
// specified by the profile parameter FAILED_LOGIN_ATTEMPTS, or the
// DBA locked the account, or the user is a common user locked in
// the root container.
// *Action: Wait for the PASSWORD_LOCK_TIME or contact the DBA.
/
28001, 00000, "the password has expired"
// *Cause: The user's account has expired and the password needs to be
// changed.
// *Action: Change the password or contact the database administrator.
//
28002, 00000, "the password will expire within %s days"
// *Cause: The password of the user's account has expired. Since the user's
// account is associated with a password profile with a limited
// password grace period and grace period is yet to elapse, the user
// will not be prompted to input a new password and ORA-28002 warning
// message will continue to be displayed upon each successful login
// to the user account, until the user changes their password.
// Once the grace period elapses, the password will expire and user
// login will start failing with ORA-28001 error, until the user
// changes their password.
// *Action: Change the password or contact the database administrator.
//
28003, 00000, "password verification for the specified password failed"
// *Cause: The new password did not meet the necessary complexity
// specifications and the password_verify_function failed
// *Action: Enter a different password. Contact the DBA to know the rules for
// choosing the new password
//
28004, 00000, "invalid argument for function specified in PASSWORD_VERIFY_FUNCTION %s"
// *Cause: The password verification function does not have the required
// number and type of input/output arguments and/or the return
// argument
// *Action: Check the manual to find out the format of the password
// verification function
//
28005, 00000, "invalid logon flags"
// *Cause: The flags are not properly set or
// conflicting flags are set in making calls
// *Action: Call the function with appropriate flags set.
//
28006, 00000, "conflicting values for parameters %s and %s"
// *Cause: The parameters PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX cannot
// both be set. One parameter should be unlimited while other is set
// *Action: Set one value to UNLIMITED explicitly
//
28007, 00000, "the password cannot be reused"
// *Cause: The password cannot be reused for the specified number of
// days or for the specified nunmber of password changes
// *Action: Try the password that you have not used for the specified
// number of days or the specified number of password changes
// Refer to the password parameters in the CREATE PROFILE statement
//
28008, 0000, "invalid old password"
// *Cause: old password supplied is wrong; Hence user cannot be
// authenticated using old password
// *Action: Supply the correct old password for authentication
//
28009, 00000, "connection as SYS should be as SYSDBA or SYSOPER"
// *Cause: connect SYS/<password> is no longer a valid syntax
// *Action: Try connect SYS/<password> as SYSDBA or
// connect SYS/<password> as SYSOPER
//
28010, 00000, "cannot expire external users, global users, or users with no authentication method"
// *Cause: If a user account is created as IDENTIFIED EXTERNALLY,
// IDENTIFIED GLOBALLY, NO AUTHENTICATION, this account
// cannot be expired.
// *Action Expire the password of a user that has "PASSWORD" as its
// AUTHENTICATION_TYPE in DBA_USERS views.
28011, 00000, "the password has expired; change your password now"
// *Cause: The password of the user's account has expired. Since the user's
// account is associated with a password profile with an UNLIMITED
// password grace period, the user will not be prompted to input
// a new password (as normally happens for accounts with a limited
// grace period). Instead, ORA-28011 warning message will continue
// to be displayed upon each successful login to the user account,
// until the user changes their password.
// *Action: Change the password or contact the database administrator.
//
28012, 00000, "connection as %s should use AS %s"
// *Cause: An attempt was made to connect as an administrative user
// without using AS SYSBACKUP, AS SYSDG, or AS SYSKM.
// *Action: Try connecting with AS SYSBACKUP, AS SYSDG, or AS SYSKM.
//
28013, 00000, "the password has expired"
// *Cause: The password of the proxy user expired.
//
// *Action: Connect directly as proxy user to change the password
// or contact the DBA.
//
28014, 00000, "cannot drop administrative users"
// *Cause: An attempt was made to drop administrative users.
// Administrative users can be dropped only by SYS during
// migration mode.
// *Action: Try dropping administrative users during migration mode.
//
28015, 00000, "account unlock attempted on read-only database but a conflicting account lockout on the primary exists"
// *Cause: An attempt to unlock an account on a read-only database
// was prevented, because the account was previously marked
// as locked on the primary database. All attempts to unlock
// the account on the read-only database will be prevented as
// long as the overriding "account locked" condition exists at
// the primary database.
// *Action: If this database is part of a Data Guard configuration,
// perform the account unlock action on the primary database.
// If this database is read-only, then set the database to
// read/write and perform the account unlock action.
//
28016, 00000, "Privilege %s cannot be granted to SYS."
// *Cause: An attempt was made to grant SYSBACKUP, SYSDG or SYSKM
// to the SYS user. These administrative privileges cannot
// be granted to SYS.
// *Action: Try granting the administrative privilege to other users.
//
28017, 00000, "The password file is in the legacy format."
// *Cause: An attempt was made to perform one of the following operations,
// but none of these operations are allowed while the password file
// is in LEGACY format.
// - Attempting to grant SYSBACKUP, SYSDG or SYSKM privileges.
// - Attempting to grant an administrative privilege to a user
// who has large password verifiers, for example, SHA-512
// hashed verifiers.
// - Attempting to grant a common administrative privilege to a
// common user in a multitenant container database (CDB).
// *Action: Create the password file in the new format ("12" or higher) or
// migrate the existing password file in LEGACY format to the new
// format ("12" or higher) using the INPUT_FILE option, then retry
// the operation.
//
28018, 00000, "This operation requires connection as SYS or SYSBACKUP."
// *Cause: An attempt was made to execute a command even though the
// user was not connected as SYS or SYSBACKUP.
// *Action: Connect as SYS or SYSBACKUP and retry this command.
//
28019, 00000, "audit cannot be configured on administrative privileges"
// *Cause: An attempt was made to configure audit on an administrative
// privilege using either the AUDIT, NOAUDIT, CREATE AUDIT POLICY,
// or ALTER AUDIT POLICY command.
// *Action: For traditional audit, use AUDIT_SYS_OPERATIONS to audit
// administrative privileges. If this is a unified audit, use
// action-based auditing to audit administrative users.
//
//
28020, 00000, "IDENTIFIED GLOBALLY already specified"
// *Cause: The IDENTIFIED GLOBALLY clause was specified twice.
// *Action: Use only one IDENTIFIED GLOBALLY clause.
28021, 00000, "cannot grant global roles"
// *Cause: The role granted was IDENTIFIED GLOBALLY. Global roles
// can only be granted via a central authority for the domain.
// *Action: Use ALTER ROLE to change the type of role (from IDENTIFIED
// GLOBALLY to other, such as IDENTIFIED BY password),
// or allocate it to a global user via the central authority.
28022, 00000, "cannot grant external roles to global user or role"
// *Cause: The role granted was IDENTIFIED EXTERNALLY. External
// roles cannot be granted to global users, to global roles or
// to any other roles.
// *Action: Use ALTER ROLE to change the type of the role being granted
// (from IDENTIFIED EXTERNALLY to other, such as NOT IDENTIFIED)
// or use ALTER USER to change the type of the user that is the
// grantee.
28023, 00000, "must revoke grants of this role to other user(s) first"
// *Cause: The role altered to IDENTIFIED GLOBALLY was granted to
// one or more other users and/or roles. Global roles cannot
// be granted to any user or role.
// *Action: Use REVOKE to revoke the role from other users or roles first.
28024, 00000, "must revoke grants of external roles to this role/user"
// *Cause: The user or role altered to IDENTIFIED GLOBALLY has
// external roles directly granted - these must be revoked, since
// external roles cannot be granted to global users or roles.
// *Action: Use REVOKE to revoke the external roles from the user or role
// to be ALTERed.
28025, 0000, "missing or null external name"
// *Cause: The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS
// clause was specified with a valid external name.
// *Action: Provide a valid external name.
28026, 0000, "user with same external name already exists"
// *Cause: The external name specified for the user being created or
// altered already exists for another user.
// *Action: External names must be unique among users. Specify another.
28027, 0000, "privileged database links may be used by global users"
// *Cause: Only users IDENTIFIED GLOBALLY may use a privileged database
// link.
// *Action: Either change the user to a global user or try to use a
// different database link.
28028, 0000, "could not authenticate remote server"
// *Cause: During the course of opening a privileged database link,
// the remote server was not securely identified using the
// network security service. Additional errors should follow.
// *Action: Consult the network security service documentation on how
// to properly configure the remote server.
28029, 0000, "could not authorize remote server for user %s"
// *Cause: During the course of opening a privileged database link,
// the remote server was found to lack the necessary authorizations
// to connect as the current global user.
// This may be because the server was not authorized by the network
// security service. Or it may be because the local server is
// restricting access by the remote server using the
// DBMS_SECURITY_DOMAINS_ADMIN package.
// *Action: Grant the remote server the proper authorization to connect as
// the given global user, and check that the local server is not
// restricting access.
28030, 0000, "Server encountered problems accessing LDAP directory service"
// *Cause: Unable to access LDAP directory service
// *Action: Please contact your system administrator
28031, 00000, "maximum of %s enabled roles exceeded"
// *Cause: The user attempted to enable too many roles.
// *Action: Enable fewer roles.
28032, 00000, "Your password has expired and the database is set to read-only"
// *Cause: Your password expired and needs to be changed before
// your login request can be processed.
// Because the database is currently open in read-only mode, the
// password change operation cannot be performed on this database.
// *Action: Log in to the primary database to change your password, then
// retry your login request at the standby database.
28033, 0000, "LDAP problem"
// *Document: NO
// *Cause:
// *Action:
28034, 00000, "cannot grant %s to an Oracle supplied user"
// *Cause: The KEEP DATE TIME, KEEP SYSGUID or KEEP SEQUENCE
// privilege could not be granted to an Oracle supplied user.
// *Action: Grant privilege directly to the application user.
28035, 0000, "Cannot Get Session Key for Authentication"
// *Cause: Client and server cannot negotiate shared secret during logon
// *Action: User should not see this error.
// Please contact your system administrator
28036, 0000, "HTTP digest authentication cannot be configured for this user"
// *Cause: An attempt was made to configure HTTP digest authentication for a
// global user, an external user, a no authentication type user,
// or a SYS user.
// *Action: Contact your system administrator.
28037, 0000, "Cannot Get Session Key for RACF Authentication"
// *Cause: Client and server cannot negotiate shared secret during logon
// *Action: User should not see this error.
// Please contact your system administrator
28038, 0000, "disallow O2LOGON"
// *Cause: turn off O2LOGON
// *Action:
28039, 0000, "cannot validate Kerberos service ticket"
// *Cause: The Kerberos service ticket provided was invalid or expired
// *Action: Provide a valid, unexpired service ticket.
28040, 0000, "No matching authentication protocol"
// *Cause: There was no acceptable authentication protocol for
// either client or server.
// *Action: The administrator should set the values of the
// SQLNET.ALLOWED_LOGON_VERSION_SERVER and
// SQLNET.ALLOWED_LOGON_VERSION_CLIENT parameters, on both the
// client and on the server, to values that match the minimum
// version software supported in the system.
// This error is also raised when the client is authenticating to
// a user account which was created without a verifier suitable for
// the client software version. In this situation, that account's
// password must be reset, in order for the required verifier to
// be generated and allow authentication to proceed successfully.
28041, 0000, "Authentication protocol internal error"
// *Cause: Authentication protocol failed with an internal error
// *Action:
28042, 0000, "Server authentication failed"
// *Cause: Server failed to authenticate itself to the client
// *Action: Confirm that the server is a valid database server.
28043, 000, "invalid bind credentials for DB-OID connection"
// *Cause: The Database password stored in the wallet did not match
// the one in OID .
// *Action: Use DBCA to reset the database password so that it
// is the same in database wallet and in OID.
28044, 000, "unsupported directory type"
// *Cause: The database tried to work with a directory which is not OID.
// *Action: Enterprise User Security works only with Oracle Internet Directory.
// Update the ldap.ora file to reflect an appropriate OID.
28045, 000, "SSL authentication between database and OID failed"
// *Cause: Server failed to authenticate itself to the Directory.
// *Action: Make sure the sqlnet.ora used is pointing to the wallet
// with the right certificate.
28046, 0000, "Password change for SYS disallowed"
// *Cause: REMOTE_LOGIN_PASSWORDFILE is set to SHARED, prohibiting SYS
// password changes.
// *Action: Change setting of REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE or NONE.
28047, 0000, "database is not a member of any enterprise domain in OID"
// *Cause: An enterprise user login was attempted on a database that is
// not a member of any enterprise domain in OID.
// *Action: An administrator should put the database into an enterprise
// domain in OID, and then the user should reconnect.
28048, 0000, "database is a member of multiple enterprise domains in OID"
// *Cause: An enterprise user login was attempted on a database that is
// a member of multiple enterprise domains in OID.
// *Action: An administrator should put the database into only one
// enterprise domain in OID, and then the user should reconnect.
28049, 00000, "the password has expired"
// *Cause: The enterprise user's password has expired and the password
// needs to be changed.
// *Action: change the password in the directory or contact the directory
// administrator.
28050, 00000, "specified user or role cannot be dropped"
// *Cause: The user or role specified in the DROP statement was a reserved
// Oracle object that could not be dropped.
// *Action: None.
28051, 00000, "the account is locked"
// *Cause: The enterprise user has consecutively entered the wrong password
// for maximum number of times specified in the realm's
// password policy profile.
// *Action: Contact the directory administrator.
28052, 00000, "the account is disabled"
// *Cause: The enterprise user's account in the directory has been disabled.
// *Action: Contact the directory administrator.
28053, 00000, "the account is inactive"
// *Cause: The enterprise user's account in the directory is currently not
// active.
// *Action: Contact the directory administrator.
28054, 00000, "the password has expired. %s Grace logins are left"
// *Cause: The enterprise user's password has expired. The user is
// able to login because he has gracelogins left.
// *Action: change the password in the directory or contact the directory
// administrator.
28055, 00000, "the password will expire within %s days"
// *Cause: The enterprise user's password is about to expire.
// *Action: Change the password in the directory or contact the directory
// administrator.
28056, 00000, "Writing audit records to Windows Event Log failed"
// *Cause: Unable to write an audit entry to the Windows event log
// used as the audit trail.
// *Action: Check the error number for a possible operating system error.
// If there is no error, contact Oracle Support Services.
28057, 00000, "name of the password file could not be constructed"
// *Cause: Possibly environment variable ORACLE_SID was not set.
// *Action: Set value for the ORACLE_SID environment variable.
28058, 00000, "login is allowed only through a proxy"
// *Cause: This account is marked "proxy only connect".
// *Action: Connect through a proxy user.
28059, 0000, "Cross-instance call failed"
// *Cause: An attempt to inform other Oracle RAC instances of a security
// event failed.
// *Action: Log into each instance to perform the administrative
// action.
/
/ 28060-28099 RESERVED FOR RADM (Real-time Application-controlled Data Masking)
/
28060, 00000, "A data redaction policy already exists on this column."
// *Cause: A data redaction policy was already in existence on this column.
// *Action: Specify a colunm which does not already have a redaction policy
// defined on it, or use DBMS_REDACT.ALTER_POLICY to alter the
// existing redaction policy for this column.
28061, 00000, "This object cannot have a data redaction policy defined on it."
// *Cause: An attempt was made to define a data redaction policy on an object
// other than a table or view. Note that a data redaction policy
// cannot be defined on an editioned view, or on specialized tables
// created internally by the server in conjunction with various
// features such as materialized view.
// *Action: Specify the name of a table or view.
28062, 00000, "The policy expression is too long."
// *Cause: The policy expression was longer than 4000 characters.
// *Action: Specify a policy expression of at most 4000 characters.
28063, 00000, "The policy expression is empty."
// *Cause: The EXPRESSION parameter to DBMS_REDACT.ADD_POLICY was empty.
// *Action: A nonempty policy expression must be specified in
// the EXPRESSION parameter to DBMS_REDACT.ADD_POLICY.
28064, 00000, "The redaction function is not valid."
// *Cause: The FUNCTION_TYPE parameter to DBMS_REDACT.ADD_POLICY was invalid.
// *Action: Specify the FUNCTION_TYPE parameter to DBMS_REDACT.ADD_POLICY
// as one of the following: DBMS_REDACT.NONE, DBMS_REDACT.FULL,
// DBMS_REDACT.RANDOM, DBMS_REDACT.PARTIAL, DBMS_REDACT.REGEXP,
// or DBMS_REDACT.NULLIFY. Note that only none redaction, full
// redaction, and NULL redaction may be applied to columns of type
// BLOB, and only none redaction, full redaction, NULL redaction,
// and regular expression-based redaction may be applied to columns
// of type CLOB or NCLOB.
/
/ 28065 is reserved for RADM internal error.
/
28066, 00000, "invalid column \"%s\""
// *Cause: An invalid column was specified in the COLUMN_NAME parameter.
// *Action: Check the columns in the object and specify the right column name.
28067, 00000, "missing or invalid column name"
// *Cause: A valid column name was not specified in the COLUMN_NAME parameter
// when a column name was required.
// Note that when using DBMS_REDACT.ALTER_POLICY, the default action
// is DBMS_REDACT.ADD_COLUMN
// *Action: Specify the name of a column.
28068, 00000, "The object \"%s\" does not have a data redaction policy."
// *Cause: The specified object did not have a data redaction policy defined
// on it.
// *Action: Specify the name of an object which has a data redaction policy,
// or use DBMS_REDACT.ADD_POLICY to add a data redaction policy.
28069, 00000, "A data redaction policy already exists on this object."
// *Cause: A data redaction policy was already in existence on this object.
// *Action: Specify a table or view which does not already have a redaction
// policy defined on it, or use DBMS_REDACT.ALTER_POLICY to alter the
// existing redaction policy for this object.
28070, 00000, "The column \"%s\" does not have a data redaction policy."
// *Cause: The specified column did not have a data redaction policy defined
// on it.
// *Action: Specify the name of a column which has a data redaction policy.
28071, 00000, "The action is not valid."
// *Cause: The ACTION parameter to DBMS_REDACT.ALTER_POLICY was invalid.
// *Action: Specify the ACTION parameter to DBMS_REDACT.ALTER_POLICY
// as one of the following values: DBMS_REDACT.MODIFY_EXPRESSION,
// DBMS_REDACT.MODIFY_COLUMN, DBMS_REDACT.ADD_COLUMN,
// or DBMS_REDACT.DROP_COLUMN.
28072, 00000, "The specified policy name is incorrect."
// *Cause: The POLICY_NAME parameter was incorrect.
// *Action: Specify the POLICY_NAME parameter with the name of the
// redaction policy currently defined on the object.
28073, 00000, "The column \"%s\" has an unsupported data type or attribute."
// *Cause: The column had a data type or attribute which is not supported
// by data redaction. The supported data types are CHAR, NCHAR,
// VARCHAR2, NVARCHAR2, NUMBER types, BINARY_FLOAT, BINARY_DOUBLE,
// DATE, TIMESTAMP, CLOB, NCLOB, and BLOB, except as listed below
// for certain function types:
// For DBMS_REDACT.PARTIAL and DBMS_REDACT.RANDOM,
// the CLOB, NCLOB, and BLOB datatypes are not supported.
// For DBMS_REDACT.REGEXP, the NUMBER, BINARY_FLOAT, BINARY_DOUBLE,
// DATE, TIMESTAMP, and BLOB datatypes are not supported.
// Virtual columns and base columns of virtual columns are
// not supported by data redaction.
// Columns with the INVISIBLE attribute are not supported by
// data redaction (this applies to both user-specified hidden
// columns and system-generated hidden columns).
// Vector encoded columns are not supported by data redaction.
// Columns with the IS JSON constraint are not supported.
// *Action: Specify the name of a column which has a supported data type
// and supported attributes. For columns with the IS JSON constraint,
// create a view on the columns and add the redaction policy to the
// view.
28074, 00000, "The \"%s\" field of the redaction parameters is not valid."
// *Cause: The redaction parameters specified had one or more fields that
// were invalid.
// *Action: Specify the redaction parameters according to Oracle documentation.
28075, 00000, "The data redaction policy expression has an error."
// *Cause: The data redaction policy expression had an error.
// *Action: Contact the data redaction policy administrator.
// To correct this error, when invoking the ADD_POLICY and
// ALTER_POLICY procedures of the data redaction DBMS_REDACT
// package, the policy administrator must specify a valid
// policy expression for the EXPRESSION parameter.
// Check the trace file for the name of the affected policy and
// the error, and correct the data redaction policy expression.
28076, 00000, "An attribute was not specified for SYS_SESSION_ROLES."
// *Cause: An attribute was not specified for the SYS_SESSION_ROLES
// namespace in the policy expression.
// *Action: Specify an attribute for SYS_SESSION_ROLES in the policy expression.
28077, 00000, "The attribute specified (%s) exceeds the maximum length."
// *Cause: The attribute specified in the policy expression for the
// SYS_SESSION_ROLES namespace exceeded the maximum length.
// *Action: Change the policy expression to use a valid attribute for
// SYS_SESSION_ROLES namespace.
28078, 00000, "A regular expression parameter is missing or invalid."
// *Cause: The FUNCTION_TYPE was DBMS_REDACT.REGEXP, but one or more
// of the regular expression parameters were missing or invalid,
// the REGEXP_PATTERN failed to compile properly, or the
// regular expression replacement operation failed.
// *Action: Specify the regular expression parameters according to
// Oracle documentation. At a minimum, the REGEXP_PATTERN and
// the REGEXP_REPLACE_STRING must be specified. Ensure that
// the REGEXP_PATTERN can compile properly as a regular expression,
// for example by testing it with REGEXP_REPLACE in a SQL query
// against a column containing some of the data to be redacted.
28079, 00000, "The policy was already enabled."
// *Cause: The redaction policy specified has already been enabled.
// *Action: Only disabled redaction policies can be enabled.
//
28080, 00000, "The policy was already disabled."
// *Cause: The redaction policy specified has already been disabled.
// *Action: Only enabled redaction policies can be disabled.
//
28081, 00000, "Insufficient privileges - the command references a redacted object."
// *Cause: The command referenced a redacted column in an
// object protected by a data redaction policy.
// *Action: If possible, modify the command to avoid referencing any
// redacted columns. Otherwise, drop the data redaction policies that
// protect the referenced tables and views, or ensure that the user issuing
// the command has the EXEMPT REDACTION POLICY system privilege, then
// retry the operation. The EXEMPT REDACTION POLICY system privilege
// is required for creating or refreshing a materialized view when the
// materialized view is based on an object protected by a data redaction
// policy. The EXEMPT REDACTION POLICY system privilege is required for
// performing a data pump schema-level export including any object
// protected by a data redaction policy. All data redaction policies are
// listed in the REDACTION_COLUMNS catalog view.
28082, 00000, "The parameter %s is invalid."
// *Cause: The specified parameter was either empty or too long.
// *Action: Specify a parameter of correct length. See the
// documentation for length requirements.
28083, 00000, "A redacted column was referenced in a virtual column expression."
// *Cause: This redacted column was referenced in a virtual column
// expression.
// *Action: Ensure the column expression definition for any virtual column
// does not refer to any redacted columns. To check for columns
// with redaction policies, use the REDACTION_COLUMNS catalog view
// which lists all data redaction policies.
28084, 00000, "internal event to enable data redaction statistics gathering"
// *Document: NO
// *Cause: N/A
// *Action: Set this event in your instance initialization file
// to enable gathering of statistics for data redaction.
// *Note: This is not a user error number or message.
// This message does not need to be translated or documented.
28085, 00000, "The input and output lengths of the redaction do not match."
// *Cause: As specified, the redaction parameters produced an output
// with a length different to that of the input.
// *Action: Use regular expression redaction instead of partial redaction.
28086, 00000, "The data redaction policy expression has an error.\n%s"
// *Cause: The data redaction policy expression had an error.
// *Action: Specify a valid policy expression.
// The data redaction policy expression must be written in SQL,
// and must be a valid predicate to use in the following SQL query.
// SELECT 1 FROM DUAL WHERE policy_expression;
28087, 00000, "The policy expression has an unsupported (use of) operator '%s'."
// *Cause: The policy expression used an unsupported operator,
// or used an operator in an unsupported way.
// *Action: Modify the policy expression to use only the supported operators
// in a supported way. Supported operators include "=", "!=", ">",
// "<", ">=", "<=", the length operators, the substring operators,
// and the context operators (SYS_CONTEXT and XS_SYS_CONTEXT).
// For a complete list of the supported operators, and the supported
// ways the allowed operators can be used, refer to the section on
// data redaction policy expressions in the Oracle documentation.
28088, 00000, "The policy expression has an unsupported PL/SQL function %s.%s.%s."
// *Cause: The policy expression had an unsupported PL/SQL function.
// *Action: Modify the policy expression to use a supported PL/SQL function.
// Supported PL/SQL functions include the Oracle Label Security
// dominates functions, and the Oracle Apex session state
// functions (V and NV).
// For a complete list of the supported PL/SQL functions,
// refer to data redaction in the Oracle documentation.
28089, 00000, "invalid SYS_CONTEXT namespace %s in policy expression"
// *Cause: The SYS_CONTEXT (or XS_SYS_CONTEXT) namespace used in the
// policy expression was not valid.
// *Action: Modify the policy expression to use a valid namespace.
// Supported namespaces include USERENV, SYS_SESSION_ROLES,
// XS$SESSION and the namespaces listed in the DBA_CONTEXT
// catalog view.
28090, 00000, "unsupported nesting of function %s.%s.%s within function %s.%s.%s in policy expression"
// *Cause: The policy expression had an unsupported PL/SQL function nesting.
// *Action: Modify the policy expression to use only supported PL/SQL
// function nesting. The Oracle Label Security functions
// NUMERIC_LABEL, CHAR_TO_LABEL, and SA_SESSION can only be
// used from within the Label Security dominates functions.
// For a complete list of supported PL/SQL function nesting,
// refer to the section on writing policy expressions
// in the Oracle documentation for data redaction.
28091, 00000, "unsupported use of PL/SQL function %s.%s.%s in policy expression"
// *Cause: The policy expression used a PL/SQL function in an unsupported way.
// *Action: Modify the policy expression to use the PL/SQL function properly.
// The parameters to the Oracle Label Security functions
// NUMERIC_LABEL, CHAR_TO_LABEL, and SA_SESSION must be constants.
// For a complete list of the supported ways PL/SQL functions
// can be used in a policy expression, refer to the section on
// writing policy expressions in the Oracle documentation for
// data redaction.
28092, 00000, "The parameter %s with value '%s' has an error."
// *Cause: The value of the parameter had an error.
//
// If DBMS_REDACT.CREATE_POLICY_EXPRESSION was invoked and
// the POLICY_EXPRESSION_NAME parameter had an error,
// the policy expression name either already existed,
// or was invalid.
//
// If DBMS_REDACT.DROP_POLICY_EXPRESSION was invoked and
// the POLICY_EXPRESSION_NAME parameter had an error,
// the policy expression either did not exist, was still
// in use (was applied to a column), or was invalid.
//
// If DBMS_REDACT.APPLY_POLICY_EXPR_TO_COL was invoked and
// the POLICY_EXPRESSION_NAME parameter had an error,
// a policy expression may already exist on this column.
// Only one policy expression may be associated with any
// given column.
// The name of any Oracle Data Redaction policy expression
// associated with a given column can be found
// in the REDACTION_EXPRESSIONS catalog view.
//
// If the DBMS_REDACT.ADD_POLICY was invoked and the OBJECT_SCHEMA
// parameter referenced the APEX or Spatial installation schema,
// the operation was prevented. Data redaction policies are not
// supported on objects within the APEX or Spatial installation
// schema.
//
// If the DBMS_REDACT.ADD_POLICY was invoked and the OBJECT_NAME
// references a metadata-linked view, the operation was prevented.
// Data redaction policies are not supported on metadata-linked
// views.
//
// *Action: Provide a valid value for the parameter.
//
// If DBMS_REDACT.CREATE_POLICY_EXPRESSION was invoked and
// the parameter was POLICY_EXPRESSION_NAME, provide a valid
// (new or existing) policy expression name.
// The names of all existing Oracle Data Redaction policy
// expressions can be found in the REDACTION_EXPRESSIONS
// catalog view.
//
// For the POLICY_EXPRESSION_NAME parameter of
// the DBMS_REDACT.DROP_POLICY_EXPRESSION procedure,
// provide a valid existing policy expression name
// which is not currently in use (applied to any column).
// The names of the columns to which a given policy expression
// is currently applied can be found in the REDACTION_EXPRESSIONS
// catalog view.
//
// For the POLICY_EXPRESSION_NAME parameter of
// the DBMS_REDACT.APPLY_POLICY_EXPR_TO_COL procedure,
// either provide NULL to remove the current policy expression
// association of the column, or provide a valid
// existing policy expression name. There is currently no API
// to alter an existing association. For now it must first be
// dropped followed by applying the new association.
// The names of all existing policy expressions can be
// found in the REDACTION_EXPRESSIONS catalog view.
//
// If DBMS_REDACT.ADD_POLICY was invoked, provide an
// OBJECT_SCHEMA which is not the APEX or Spatial installation
// schema. Data redaction policies are not supported on objects
// within the APEX or Spatial installation schema.
//
// If DBMS_REDACT.ADD_POLICY was invoked, provide an
// OBJECT_NAME which does not reference a metadata-linked view.
28093, 00000, "operation on column %s is not supported by data redaction"
// *Cause: The operation was not supported by data redaction.
// *Action: Perform only supported operations on any object which
// has a data redaction policy or which depends on an object
// with a data redaction policy.
// To check for columns with redaction policies, use the
// REDACTION_COLUMNS catalog view which lists all of the
// data redaction policies.
28094, 00000, "SQL construct not supported by data redaction"
// *Cause: The query had a SQL construct that was not supported by
// data redaction.
// *Action: Rewrite the query to avoid using an unsupported construct.
// Consult the Oracle documentation for details.
/
/ 28100-28149 RESERVED FOR FINE-GRAINED SECURITY
/
28100, 00000, "policy function schema %s is invalid"
// *Cause: The schema was dropped after the policy associated with the
// function had been added to the object.
// *Action: Drop the policy and re-create it with a policy function owned by
// a valid user. Or re-create the user and the policy function under
// the new user.
28101, 00000, "policy already exists"
// *Cause: A policy with the same name for the same object already exists.
// *Action: Check if the policy has already been added or use a different
// policy name.
28102, 00000, "policy does not exist"
// *Cause: Try to drop/enable/refresh a non-existent policy.
// *Action: Correct the policy name argument.
28103, 00000, "adding a policy to an object owned by SYS is not allowed"
// *Cause: Try to add a policy to a table or a view owned by SYS.
// *Action: You can not perform this operation.
28104, 00000, "input value for %s is not valid"
// *Cause: Input value for the argument is not valid
// *Action: specify a valid argument value.
28105, 00000, "cannot create security relevant column policy in an object view"
// *Cause: Security relevant column argument is not null in policy creation
// for an object view
// *Action:
28106, 00000, "input value for argument #%s is not valid"
// *Cause: Input values for the argument is missing or invalid.
// *Action: Correct the input values.
28107, 00000, "policy was disabled"
// *Cause: Try to flush a disabled policy.
// *Action: If the policy is supposed to be enforced, it must be enabled.
28108, 00000, "circular security policies detected"
// *Cause: Policies for the same object reference each other.
// *Action: Drop the policies
28109, 00000, "the number of related policies has exceeded the limit of 16"
// *Cause: Too many policies are involved in the same objects.
// *Action: Drop one or more policies. Or combine a few of them into one.
28110, 00000, "policy function or package %s.%s has error"
// *Cause: The policy function may have been dropped, or is no longer valid.
// *Action: Check the status of the function and correct the problem.
// Or re-create the policy with a valid function.
28111, 00000, "insufficient privilege to evaluate policy predicate"
// *Cause: Predicate has a subquery which contains objects that the owner of
// policy function does not have privilege to access.
// *Action: Grant appropriate privileges to the policy function owner.
28112, 00000, "failed to execute policy function"
// *Cause: The policy function has one or more error during execution.
// *Action: Check the trace file and correct the errors.
28113, 00000, "policy predicate has error"
// *Cause: Policy function generates invalid predicate.
// *Action: Review the trace file for detailed error information.
28115, 00000, "policy with check option violation"
// *Cause: Policy predicate was evaluated to FALSE with the updated values.
// *Action:
28116, 00000, "insufficient privileges to do direct path access"
// *Cause: Users with insufficient privileges attempting to do direct path
// access of tables with fine grain access control policies.
// *Action: Ask the database administrator to do the operation.
// Note that users can work with security administrator
// to temporarily drop/disable the policies at time of export,
// import, or load, but this has security implication, and
// thus access of the database must be controlled carefully.
28117, 00000, "integrity constraint violated - parent record not found"
// *Cause: try to update/insert a child record with new foreign key
// values, but the corresponding parent row is not visible
// because of fine-grained security in the parent.
// *Action: make sure that the updated foreign key values must also visible
// in the parent
28118, 00000, "policy group already exists"
// *Cause: try to create a policy group that already exists
// *Action:
28119, 00000, "policy group does not exist"
// *Cause: try to drop a policy group that does not exist
// *Action:
28120, 00000, "driving context already exists"
// *Cause: try to create a driving context that already exists
// *Action:
28121, 00000, "driving context does not exist"
// *Cause: try to drop a driving context that does not exist
// *Action:
28122, 00000, "can not update SYS_DEFAULT policy group"
// *Cause: An attempt was made to execute either DBMS_RLS.CREATE_POLICY_GROUP
// or DBMS_RLS.DELETE_POLICY_GROUP using SYS_DEFAULT as the policy
// group name.
// *Action: Do not attempt to CREATE or DELETE the SYS_DEFAULT policy
// group. This action is not permitted.
28123, 00000, "Driving context '%s,%s' contains invalid group '%s'"
// *Cause: A previous call to DBMS_SESSION.SET_CONTEXT specified an invalid
// policy group.
// *Action: Ensure that a valid policy group is passed to
// DBMS_SESSION.SET_CONTEXT when initializing a policy driving context.
28124, 00000, "Column %s in sec_relevant_cols cannot be of an object data type"
// *Cause: A column specified in sec_relevant_cols was of an object data type.
// *Action: Ensure that none of the columns specified in sec_relevant_cols
// is of an object data type or XMLType.
28125, 00000, "A protected base column was referenced in an unprotected virtual column expression."
// *Cause: A protected base column was referenced in an unprotected virtual
// column expression.
// *Action: Check the policy definition and make sure that the virtual column
// is also protected.
28126, 00000, "Attribute association failed for policy \"%s\"."
// *Cause: An attempt was made to associate a global application context
// attribute to either a context-sensitive or shared context-sensitive
// policy. Only local application context attribute association is
// supported.
// *Action: Specify a local application context attribute.
28130, 00000, "Fine Grained Access Control at table level"
// *Document: NO
// *Cause:
// *Action:
28131, 00000, "Fine Grained Access Control enforced"
// *Document: NO
// *Cause:
// *Action:
28132, 00000, "The MERGE INTO syntax does not support the security policy."
// *Cause: The MERGE INTO syntax did not support a security policy on the
// destination table, because the policy's statement_types did
// not include each of INSERT, UPDATE and DELETE.
// *Action: If you do not have the privilege to modify the security policy,
// then instead of MERGE INTO, use the INSERT, UPDATE and DELETE DML
// statements on the table that has a security policy defined on it.
// If you have the privilege to modify the security policy, then
// redefine it in such a way that statement_types includes all of
// the DML statement types (INSERT, UPDATE and DELETE).
//
28133, 00000, "full table access is restricted by fine-grained security"
// *Document: NO
// *Cause: The command requires full table access but the user is not SYS
// and does not have permission to by pass security policies.
// *Action: Grant appropriate privileges, or change the policy function so
// that it returns a NULL predicate under certain session
// environments.
/
28134, 00000, "object cannot have fine-grained access control policy"
// *Cause: Only tables, views, or synonyms of tables or views
// may have VPD policies
// *Action:
28135, 00000, "VPD check option silent error event"
// *Cause:
// *Action:
28136, 00000, "Ignore check option error"
// *Cause:
// *Action:
/
28137, 00000, "Invalid FGA audit Handler"
// *Cause: An invalid audit handler was specified.
// *Action: Specify a valid audit handler.
/
28138, 00000, "Error in Policy Predicate"
// *Cause: An invalid policy predicate was specified.
// *Action:Please specify a valide policy Predicate for the FGA policy
/
28139, 00000, "Maximum allowed Fine Grain Audit Policies Exceeded"
// *Cause: A maximum of 256 policies can be enabled on an object
// *Action: Drop or disable an existing policy before creating more
/
28140, 00000, "Invalid column specified "
// *Cause: Column name specified during policy creation is invalid
// *Action: Please specify a valid column name. Object columns are not
// supported
/
28141, 00000, "error in creating audit index file"
// *Cause: ORACLE was not able to create the file being used to hold
// audit file names.
// *Action: Examine the directory pointed to by the initialization
// parameter "audit_file_dest." Make sure that all of the
// following is true:
// 1. The directory exists.
// 2. The name indeed points to a directory and not a file.
// 3. The directory is accessible and writable to the ORACLE user.
/
28142, 00000, "error in accessing audit index file"
// *Cause: ORACLE was not able to access the file being used to hold
// audit file names.
// *Action: Make sure the file exists in the directory pointed to by the
// initialization parameter "audit_file_dest" and is readable
// by the ORACLE user.
/
28143, 00000, "Invalid argument passed to FGA ADD_POLICY procedure"
// *Cause: Invalid input argument was specified for FGA ADD_POLICY procedure.
// *Action: Specify correct type and number of arguments to FGA
// ADD_POLICY procedure.
/
28144, 00000, "Failed to execute fine-grained audit handler"
// *Cause: An error was encountered while executing fine-grained audit handler.
// *Action: Refer to the trace file for details.
/
28145, 00000, "XDS policy already exists for %s"
// *Cause: An XDS policy was enabled for an object that already has an
// associated XDS policy.
// *Action: Specify a different policy name or call enable_xds with
// the overwrite paramter set to TRUE.
/
28146, 00000, "invalid operation for policy \"%s\""
// *Cause: Attribute association (NAMESPACE, ATTRIBUTE) was specified for an
// invalid policy type. Attribute association can be specified only
// for context-sensitive and shared context-sensitive policy types.
// *Action: Do not perform any unsupported operation.
/
28147, 00000, "The specified attribute association (\"%s\", \"%s\") is already attached to policy \"%s\"."
// *Cause: An attempt was made to create the attribute association using
// names that were already used by existing attribute association
// of the policy.
// *Action: Adjust the names and retry the operation.
/
28148, 00000, "The specified attribute association (\"%s\", \"%s\") is not attached to policy \"%s\"."
// *Cause: An attempt was made to drop the attribute association that was not
// attached to the policy.
// *Action: Adjust the names and retry the operation.
/
28149, 00000, "input value for argument \"%s\" is missing"
// *Cause: Only one input value was specified for the (NAMESPACE, ATTRIBUTE) arguments.
// *Action: Specify an input value for both (NAMESPACE, ATTRIBUTE) arguments.
/
/ 28150-28199 RESERVED FOR N-TIER SECURITY
/
28150, 0000, "proxy not authorized to connect as client"
// *Cause: A proxy user attempted to connect as a client, but the proxy
// was not authorized to act on behalf of the client.
// *Action: Grant the proxy user permission to perform actions on behalf of the
// client by using the ALTER USER ... GRANT CONNECT command.
28151, 0000, "more than one user name specified for command"
// *Cause: More than one user name was specified for an ALTER USER command.
// *Action: Try the command again with only one user name.
/
28152, 0000, "proxy user '%s' may not specify initial role '%s' on behalf of client '%s'"
// *Cause: A proxy user attempted to specify an initial role for a client, but
// the client does not possess the role.
// *Action: Change the proxy user so that it does not specify the role or grant
// the role to the client.
/
28153, 0000, "Invalid client initial role specified: '%s'"
// *Cause: A role specified by a proxy user as an initial role to be
// activated upon connecting on behalf of a client is invalid.
// *Action: Connect again as the client specifying a valid role.
/
28154, 00000, "Proxy user may not act as client '%s'"
// *Cause: A proxy user may not assume the identity of a privileged user in
// order to limit the privileges that a proxy may possess.
// *Action: Execute the statement again specify a client other than a
// privileged user.
/
28155, 0000, "user '%s' specified as a proxy is actually a role"
// *Cause: A user specified in an AUDIT <operation> BY <proxy> ON BEHALF OF
// <client> is actually a role.
// *Action: Execute the statement again with a valid proxy user.
/
28156, 0000, "Proxy user '%s' not authorized to set role '%s' for client '%s'"
// *Cause: A proxy user has not been granted the right to use a role on
// behalf of a client.
// *Action: Execute the command ALTER USER <client> GRANT CONNECT THROUGH
// PROXY <proxy> to grant the needed role.
/
28157, 0000, "Proxy user '%s' forbidden to set role '%s' for client '%s'"
// *Cause: A proxy user was forbidden to use a role on behalf of a client
// through the command ALTER USER <client> GRANT CONNECT THROUGH
// <proxy> WITH ALL ROLES EXCEPT <role>
// *Action: Execute the command ALTER USER <client> GRANT CONNECT THROUGH
// PROXY <proxy> to grant the needed role.
28158, 00000, "missing ALL keyword"
// *Cause:
// *Action:
/
28159, 00000, "missing BEHALF keyword"
// *Cause:
// *Action:
/
28160, 00000, "missing EXCEPT keyword"
// *Cause:
// *Action:
/
28161, 00000, "missing ROLES keyword"
// *Cause:
// *Action:
/
28162, 00000, "missing THROUGH keyword"
// *Cause:
// *Action:
/
28163, 00000, "GRANT already specified"
// *Cause: The GRANT clause was specified twice.
// *Action: Use only one GRANT clause.
/
28164, 00000, "REVOKE already specified"
// *Cause: The REVOKE clause was specified twice.
// *Action: Use only one REVOKE clause.
/
28165, 0000, "proxy '%s' may not specify password-protected role '%s' for client '%s'"
// *Cause: A proxy user attempted to activate a role on behalf of a client
// which has a password associated with it. Since the proxy does not
// have a password, this activation cannot be allowed.
// *Action: Attempt to activate a different role or change the role
// administratively so that there is no password.
/
28166, 00000, "duplicate rolename in list"
// *Cause: The name of a role was specified more than once in a list.
// *Action: Repeat the command specifying the role once.
28168, 0000, "attempted to grant password-protected role"
// *Cause: An ALTER USER ... GRANT CONNECT command was attempted specifying a
// role that was password-protected.
// *Action: Specify a role which is not a password-protected role.
/
28169, 0000, "unsupported certificate type"
// *Cause: The type of certificate from which the server is to extract the
// credentials of the client is not supported.
// *Action: Specify a supported type.
/
28170, 0000, "unsupported certificate version"
// *Cause: The version of the certificate from which the server is to extract
// the credentials of the client is not supported.
// *Action: Specify a supported version.
/
28171, 0000, "unsupported Kerberos version"
// *Cause: the version the Kerberos ticket which the server is to use to
// validate the identity of the client is not supported.
// *Action: Specify a supported version.
/
28172, 00000, "distinguished name not provided by proxy"
// *Cause: A client user is to be identified using a distinguished
// name, but none was provided by the proxy user.
// *Action: Provide a distinguished name.
/
28173, 00000, "certificate not provided by proxy"
// *Cause: A client user is to be identified using a certificate but none
// was provided by the proxy user.
// *Action: Provide a certificate.
/
28174, 00000, "Kerberos ticket not provided by proxy"
// *Cause: A client user is to be authenticated using a Kerberos ticket but
// none was provided by the proxy user.
// *Action: Provide a Kerberos ticket.
/
28175, 00000, "incorrect certificate type"
// *Cause: the type of certificate provided by the proxy user to identify
// a client user does not match the type that is required.
// *Action: Provide a certificate of the correct type.
/
28176, 00000, "incorrect certificate version"
// *Cause: the version of certificate provided by the proxy user to
// identify a client user does not match the version that is
// required.
// *Action: Provide a certificate of the correct version.
/
28177, 00000, "incorrect Kerberos ticket version"
// *Cause: the version of Kerberos ticket provided by the proxy user to
// authenticate a client user does not match the version that is
// required.
// *Action: Provide a Kerberos ticket of the correct version.
/
28178, 00000, "password not provided by proxy"
// *Cause: A client user is to be authenticated using a database password but
// none was provided by the proxy user.
// *Action: Provide a password.
/
28179, 00000, "client user name not provided by proxy"
// *Cause: No user name was provided by the proxy user for the client user.
// *Action: Either specify a client database user name, a distinguished name or
// an X.509 certificate.
/
28180, 00000, "multiple authentication methods provided by proxy"
// *Cause: More than one authentication method was specified by the proxy
// user for the client user.
// *Action: Specify only one of the following: a client database user name,
// a distinguished name or an X.509 certificate.
/
28181, 00000, "proxy '%s' failed to enable one or more of the specified initial roles for client '%s'"
// *Cause: Attempt to enable specified initial roles after logon resulted in
// failure.
// *Action: Check that the initial roles are valid, granted to client, and
// not password protected.
/
28182, 00000, "cannot acquire Kerberos service ticket for client"
// *Cause: An attempt to use a Kerberos forwardable ticket granting ticket
// to obtain a Kerberos service ticket failed.
// *Action: Check that the Kerberos forwardable ticket granting ticket
// belongs to the client, is valid, and that the key distribution
// center is available.
/
28183, 00000, "proper authentication not provided by proxy"
// *Cause: A client user must be authenticated but
// no authentication credentials were provided by the proxy user.
// *Action: Provide some form of authentication credentials.
/
28184, 00000, "global user cannot have proxy permissions managed in the directory"
// *Cause: The client name specified was a global user.
// *Action: Use ALTER USER to change the type of user (from IDENTIFIED
// GLOBALLY to something else, such as IDENTIFIED BY password
// or IDENTIFIED EXTERNALLY).
/
28185, 00000, "cannot alter user with administrative privilege to proxy-only connect user"
// *Cause: An attempt was made to alter a user with administrative privilege to
// a proxy-only connect user.
// *Action: This user cannot be altered to proxy-only connect user.
/
28186, 00000, "cannot grant %s to a proxy-only connect user"
// *Cause: An attempt was made to grant administrative privilege like SYSDBA,
// SYSOPER, SYSASM, SYSBACKUP, SYSDG, SYSKM, or SYSRAC to a proxy-only
// connect user. Since proxy authentication using an administrative
// privilege is not supported, such grants are not allowed.
// *Action: none
/
28187, 00000, "cannot alter global user to proxy-only connect user"
// *Cause: An attempt was made to alter global user to proxy-only connect.
// *Action: none
/
28188, 00000, "cannot alter user SYS/SYSBACKUP/SYSDG/SYSKM/SYSRAC to be identified as globally"
// *Cause: An attempt was made to alter SYS/SYSBACKUP/SYSDG/SYSKM/SYSRAC to
// be identified as globally.
// *Action: none
28190, 00000, "SYSRAC administrative privilege cannot be granted to other users"
// *Cause: An attempt was made to grant SYSRAC administrative privilege to a
// user. This administrative privilege can only be used in operating
// system authentication and cannot be granted to other users.
// *Action: Use connection string '/ as SYSRAC' from an operating system
// account in the OSRAC group to connect to the database with the
// SYSRAC privilege.
28191, 00000, "cannot grant administrative privileges to a user with non-ASCII or non-EBCDIC characters in the user name"
// *Cause: An attempt to grant privileges to a user failed.
// Administrative privileges like SYSDBA, SYSOPER, SYSASM, SYSBACKUP,
// SYSDG, SYSKM, and SYSRAC cannot be granted to a user with non-ASCII
// or non-EBCDIC characters in the user name.
// *Action: Grant administrative privileges to users that have user names with
// only ASCII or EBCDIC characters.
/
/ 28200-28230 RESERVED FOR THE APPLICATION ROLE
/
//
28200, 00000, "IDENTIFIED USING already specified"
// *Cause: The IDENTIFIED USING clause was specified twice.
// *Action: Use only one IDENTIFIED USING clause.
/
28201, 00000, "invalid command to enable secure application role \'%s\'"
// *Cause: An attempt to enable the secure application role outside of the
// scope of the designated package failed.
// *Action: Enable the role using the designated package.
//
//
/
/ 28206-28220 RESERVED FOR THE PASSWORD COMPLEXITY
/
28206, 00000, "password length less than %d bytes"
// *Cause: The password entered by the user did not meet the minimum length criteria.
// *Action: Enter a password which meets the minimum length criteria.
/
28207, 00000, "password contains the user name"
// *Cause: The provided password contained the user name.
// *Action: Enter a password that does not contain the user name.
/
28208, 00000, "password contains the user name in reverse"
// *Cause: The provided password contained the reverse of the user name.
// *Action: Enter a password that does not contain the reverse of the user name.
/
28209, 00000, "password contains the server name"
// *Cause: The provided password contained the server name.
// *Action: Enter a password that does not contain the server name.
/
28210, 00000, "password too simple"
// *Cause: The password was simple enough to guess.
// *Action: Enter a complex paswword.
/
28211, 00000, "new password should differ from the old password by %s or more characters"
// *Cause: The new and old passwords should differ by at least the minimum number of characters as defined by the administrator.
// *Action: Enter a password that differs from the previous password by at least the minimum required number of changed characters, as defined by the administrator.
/
28212, 00000, "password must NOT contain a double-quotation"
// *Cause: The double-quotation mark character is reserved as a password delimiter.
// *Action: Enter a password without any double-quotation marks.
/
28213, 00000, "password must contain %d or more letters"
// *Cause: The password did not meet the minimum required number of alphabetic characters.
// *Action: Enter a password containing at least the minimum number of alphabetic characters.
/
28214, 00000, "password must contain %d or more uppercase characters"
// *Cause: The password did not meet the minimum required number of uppercase alphabetic characters.
// *Action: Enter a password containing at least the minimum number of uppercase alphabetic characters.
/
28215, 00000, "password must contain %d or more lowercase characters"
// *Cause: The password did not meet the minimum required number lowercase alphabetic characters.
// *Action: Enter a password containing at least the minimum number of lowercase alphabetic characters.
/
28216, 00000, "password must contain %d or more digits"
// *Cause: The password did not contain the minimum number of digits.
// *Action: Enter a password comtaining at least the minimum number of digits.
/
28217, 00000, "password must contain %d or more special characters"
// *Cause: The password did not contain the minimum number of special characters.
// *Action: Enter a password containing at least the minimum number of special characters.
/
28218, 00000, "password length more than 30 bytes"
// *Cause: The length of the password exceeds 30 bytes.
// *Action: Enter a password containing a maximum of 30 bytes.
//
//
/
/ 28221-28230 RESERVED FOR PASSWORD/ACCOUNT ENHANCEMENT
/
//
28221, 00000, "REPLACE not specified"
// *Cause: User is changing password but password verification function is
// turned on and the original password is not specified and the
// user does not have the alter user system privilege.
// *Action: Supply the original password.
/
28222, 00000, "may not modify reserved user"
// *Cause: An attempt was made to change or grant to a reserved user account.
// *Action: None.
//
//
/
28223, 00000, "first login requires password change"
// *Cause: This user was globally authenticated. Password policy settings
// in Oracle Internet Directory (OID) requires the password to be
// changed for the first connection. Further connections to the
// database will be denied if the password in OID is not changed.
// *Action: Connect to the OID to change the password.
/
28224, 00000, "user password or account management tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: None
/
/ 28230-28260 RESERVED FOR THE OBFUSCATION TOOLKIT
/
28231, 0000, "no data passed to obfuscation toolkit"
// *Cause: A NULL value was passed to a function or procedure.
// *Action: Make sure that the data passed is not empty.
/
28232, 0000, "invalid input length for obfuscation toolkit"
// *Cause: Length of data submitted for encryption or decryption is not a
// multiple of 8 bytes.
// *Action: Make sure that the length of the data to be encrypted or decrypted
// is a multiple of 8 bytes.
/
28233, 0000, "double encryption not supported"
// *Cause: The obfuscation toolkit does not support the encryption of
// already-encrypted data.
// *Action: Do not attempt to encrypt already-encrypted data.
/
28234, 00000, "key length too short"
// *Cause: The key specified is too short for the algorithm. DES
// requires a key of at least 8 bytes. Triple DES requires a
// key of least 16 bytes in two-key mode and 24 bytes in three-key
// mode.
// *Action: Specify a longer key.
/
28235, 00000, "algorithm not available"
// *Cause: The encryption algorithm desired is not available.
// *Action: Run the installer to install the needed algorithm in
// Oracle Advanced Security.
/
28236, 00000, "invalid Triple DES mode"
// *Cause: An unknown value was specified for the mode in which triple
// DES encryption is to run.
// *Action: Specify a valid value. See the package declaration for a
// list of valid values.
/
28237, 00000, "seed length too short"
// *Cause: The seed specified for the key generation routine must be at least
// 80 characters.
// *Action: Specify a longer seed.
/
28238, 00000, "no seed provided"
// *Cause: A NULL value was passed in as the seed to be used in generating
// a key.
// *Action: Provide a non-NULL value for the seed.
/
28239, 00000, "no key provided"
// *Cause: A NULL value was passed in as an encryption or decryption key.
// *Action: Provide a non-NULL value for the key.
/
/ 28261-28270 RESERVED FOR APPLICATION CONTEXT
/
28261, 0000, "CURRENT_USER can not be used in PLSQL Definer's Right procedure."
// *Cause: An attempt to retrieve CURRENT_USER using SYS_CONTEXT PLSQL
// interface.
// *Action: Use a SQL statement to query CURRENT_USER inside a DR procedure.
/
28262, 0000, "unused error"
// *Cause:
// *Action:
28263, 0000, "unused error"
// *Cause:
// *Action:
28264, 0000, "Client identifier is too long"
// *Cause: The length of the client identifier is longer than 64
// *Action: Set a client identifier whose length is less than 64.
//
/
/
28265, 0000, "Namespace beginning with 'SYS_' is not allowed."
// *Cause: Namespace beginning with 'SYS_' was not allowed.
// *Action: Use a namespace that does not begin with 'SYS_'.
//
/
28266, 0000, "Application Context tracing event"
// *Document: NO
// *Cause: N/A
// *Action: Debugging event for KZCTX layer.
/
28267, 0000, "Invalid NameSpace Value"
// *Cause: Context NameSpace conflicts with reserved key words or
// a secure Namespace is not allowed for this
// type of Application Context.
// *Action: Use a valid namespace.
//
/
28268, 0000, "Exceeded the maximum allowed size for Context information in a session"
// *Cause: The maximum size specified by the _session_context_size
// init.ora parameter was exceeded.
// *Action: Please change the value for _session_context_size in the
// init.ora file.
//
/
28269, 0000, "Event to enable overwrite of client_identifier when client_info is set"
// *Document: NO
// *Cause: N/A
// *Action: Set this event in your environment to propagate client_info session
// context attribute to client_identifier.
// *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
//
/
/ 28270-28290 RESERVED FOR PASSWORD AUTHENTICATED GLOBAL USER(KZAL)
/
28270, 0000, "Malformed user nickname for password authenticated global user."
// *Cause: An attempt to login as password-auuthenticated global user with
// a malformed user nickname.
// *Action: Make sure the nickname is valid and re-login.
/
28271, 0000, "No permission to read user entry in LDAP directory service."
// *Cause: ORACLE server does not have read permission on user nickname's
// X.500 user entry.
// *Action: Make sure ORACLE server is using right SSL credentials to connect
// to LDAP directory services.
// Make sure permissions for LDAP user entries are right.
/
28272, 0000, "Domain policy restricts password based GLOBAL user authentication."
// *Cause: Domain policy does not allow password-authenticated GLOBAL users.
// *Action: Make sure ORACLE server is using right SSL credentials to connect
// to LDAP directory services.
// Make sure orclDBAuthTypes attributes within Oracle enterprise
// domain object is either set to PWD or ALL.
/
28273, 0000, "No mapping for user nickname to LDAP distinguished name exists."
// *Cause: ORACLE server cannot map the given user nickname to LDAP
// distinguished name.
// *Action: Make sure user entries in LDAP are correctly provisioned with
// correct user nickname attribute values.
/
28274, 0000, "No ORACLE password attribute corresponding to user nickname exists."
// *Cause: LDAP user entry corresponding to user nickname does not have a
// ORACLE password attribute or the attribute is not initialized.
// *Action: Make sure user entries in LDAP are correctly provisioned with
// correct ORACLE password attribute values.
/
28275, 0000, "Multiple mappings for user nickname to LDAP distinguished name exist."
// *Cause: The given user nickname maps to more than one LDAP distinguished
// name.
// *Action: Make sure user nickname is unique within the enterprise.
/
28276, 0000, "Invalid ORACLE password attribute."
// *Cause: The ORACLE password attribute of a user entry has an invalid
// format.
// *Action: Make sure ORACLE password attribute value is RFC-2307 compliant.
/
28277, 0000, "LDAP search, while authenticating global user with passwords, failed."
// *Cause: The LDAP search for finding the appropriate user entry and ORACLE
// password failed.
// *Action: Make sure LDAP directory service is up and running.
/
28278, 0000, "No domain policy registered for password based GLOBAL users."
// *Cause: No policy about password authenticated GLOBAL users has been
// registered.
// *Action: Add attribute orclDBAuthTypes to the database server's Enterprise
// domain.
/
28279, 0000, "Error reading ldap_directory_access init parameter."
// *Cause: ldap_directory_access parameter is not specified corrrectly.
//
// *Action: Make sure spfile.ora has ldap_directory_access set correctly.
// Possible correct values are PASSWORD, SSL and NONE.
/
28280, 0000, "Multiple entries for ORACLE database password exist."
// *Cause: The ORACLE password attribute of a user entry has multiple entries
// of ORACLE database password.
// *Action: Make sure ORACLE password attribute has one entry for ORACLE Database
// password.
/
28281, 0000, "Global application context is not updated on one or more Oracle RAC instances"
// *Cause: While updating global application context across Oracle RAC instances,
// the background process errored out or the timeout expired due to
// some failure.
// *Action: Ensure every instance in Oracle RAC is operational and retry the operation.
/
/ 28290 - 28300 RESERVED FOR THE Kerberos Enterprise User Security
/
28290, 00000, "Multiple entries found for the same Kerberos Principal Name"
// *Cause: Multiple user entries has been configured with the same krbPrincipalName
// *Action: Modify enterprise user's entry to assign its Kerberos principal name
// Make sure the user entries in LDAP are provisioned correctly.
/
28291, 00000, "No Kerberos Principal Value found."
// *Cause: Oracle server fails to get value of krbPrincipalName attribute
// *Action: Make sure user entries are correctly provisioned with correct
// Kerberos principal value
/
28292, 00000, "No Domain Policy registered for Kerberos based authentication"
// *Cause: The enterprise domain entry is not configured for Kerberos based
// global authentication.
// *Action: Modify orclDBAuthType of the database server's enterprise
// domain entry and assign it "ALL" or "KRB5"
/
28293, 00000, "No matched Kerberos Principal found in any user entry"
// *Cause: Oracle server fails to find the principal in the user search base
// *Action: Make sure the user search base is correct.
// Use ESM to configure the enterprise user its Kerberos principal name
/
/
/ 28300 - 28329 RESERVED FOR THE ENTERPRISE USER SECURITY
/
28300, 00000, "No permission to read user entry in LDAP directory service."
// *Cause: ORACLE server does not have read permission on user entries.
// *Action: Make sure ORACLE server is using right credentials to connect
// to LDAP directory services.
// Make sure permissions for LDAP user entries are configured correctly.
/
28301, 00000, "Domain Policy hasn't been registered for SSL authentication."
// *Cause: An attempt was made to authenticate with SSL, but the database
// enterprise domain was not configured for SSL authentication.
// *Action: Modify orclDBAuthType of the server's enterprise domain entry
// and assign it "ALL" or "SSL".
/
28302, 00000, "User does not exist in the LDAP directory service."
// *Cause: An attempt was made to authenticate with SSL using the user's
// certificate, but there was no user entry in the LDAP server that
// matched the user's Distinguished Name.
// *Action: Add an user entry whose DN matches the user's PKI DN in
// the LDAP directory.
/
28303, 00000, "Distinguished name for user exceeds maximum supported length"
// *Cause: The user's distinguished name (DN) exceeded the maximum supported
// length.
// *Action: Shorten the user's distinguished name (DN) and retry.
/
28304, 00000, "Oracle encrypted block is corrupt (file # %s, block # %s)"
// *Cause: The indicated encrypted block was corrupt. This was an in-memory
// corruption. The exact cause is unknown. Possible causes could be:
// - the encryption wallet is incorrect or corrupted
// - the tablespace encryption key is incorrect or corrupted
// - decryption engine failure
// - actual logical error exists in decrypted block
// *Action: Review the encryption wallet and the keys stored in it to ensure
// they are valid and correct.
/
28305, 00000, "WALLET_LOCATION in sqlnet.ora file for container database is not supported."
// *Cause: WALLET_LOCATION was specified in sqlnet.ora file.
// *Action: Remove WALLET_LOCATION from sqlnet.ora file. Place the wallet in the
// pluggable database-specific default location.
/
28306, 00000, "The directory user has %s groups mapped to different database global users."
// *Cause: A directory user connected to the database while there were multiple
// directory user's groups mapped to different shared database global users.
// *Action: No action is required if by design the user's multiple groups need to be
// mapped to different database global users. Otherwise, create an exclusive
// database global user mapping for the directory user, or ensure that
// the directory user has only one mapped shared database global user.
/
28307, 00000, "The directory current time %s is unreasonable."
// *Cause: Either the directory service time was earlier than year 1900,
// or the format was incorrect.
// *Action: Ensure that the directory service clock is set properly.
/
28308, 00000, "The directory server type %s is not supported."
// *Cause: The database tried to work with a directory service which is not
/ supported.
// *Action: Update the ldap.ora file to reflect an appropriate directory
// server type.
/
28309, 00000, "Failed to get the service user's credential from the wallet."
// *Cause: The database tried to get the service user's credential from the wallet but
/ could not get it.
// *Action: Update the wallet with the service user's credential.
/
28310, 0000, "Role with same external name already exists."
// *Cause: The external name specified for the role being created or
// altered already exists for another role.
// *Action: External names must be unique among roles. Specify another.
/
28311, 00000, "Oracle encrypted data block not encrypted (file # %s, block # %s)"
// *Cause: The indicated data block was found unencrypted in a fully
// encrypted tablespace. The exact cause is unknown. Possible
// causes could be:
// - An encrypted data block is tampered and replaced with an
// unencrypted data block.
// - An Oracle internal issue.
// *Action: Collect block dump and redo dump for this block, and contact
// Oracle Support Services.
/
28312, 00000, "Proxy user is not supported with DSI."
// *Cause: Proxy user authentication is currently not supported with Directory
// Service Integration (DSI).
// *Action: Do not use proxy user authentication with DSI.
/
28313, 00000, "LDAP server connection is down."
// *Cause: The LDAP server is down or the connection to the LDAP server is closed.
// *Action: Retry the connect operation.
/
28314, 00000, "The current user database link is not supported with DSI."
// *Cause: An attempt was made to use the current user database link with
// Directory Services Integration (DSI).
// *Action: Do not use the current user database link with DSI.
/
28315, 00000, "encryption key mismatched for file # %s"
// *Cause: Oracle tablespace encryption could not verify the master
// key or the tablespace key for this data file. The exact cause is
// unknown. Possible cause could be:
// - The encryption wallet was incorrect.
// - The encryption wallet was incorrectly shared between databases.
// - The tablespace encryption key was incorrect or corrupted.
// *Action: Review the encryption wallet and the keys stored in it to ensure
// that they are valid, and contact Oracle Support Services.
/
/ 28330-28499 RESERVED FOR TRANSPARENT DATA ENCRYPTION
/
28330, 0000, "encryption is not allowed for this data type or the data type is invalid"
// *Cause: The data type was not supported for column encryption or
// the data type was invalid.
//
// *Action:
//
/
28331, 0000, "encrypted column size too long for its data type"
// *Cause: The column was both encrypted and one of the following:
// -for VARCHAR2 when extended character data types were disabled,
// the length specified was > 3932;
// -for VARCHAR2 when extended character data types were enabled,
// the length specified was > 32699;
// -for CHAR, the length specified was > 1932;
// -for NVARCHAR2 when extended character data types were disabled,
// the length specified was > 1966;
// -for NVARCHAR2 when extended character data types were enabled,
// the length specified was > 16349;
// -for NCHAR, the length specified was > 966;
// -for RAW when extended character data types were disabled,
// the length specified was > 3932;
// -for RAW when extended character data types were enabled,
// the length specified was > 32699;
// *Action: Reduce the column size.
//
/
28332, 0000, "cannot have more than one password for the encryption key"
// *Cause: More than one password was specified in the user command.
//
// *Action:
//
/
28333, 0000, "column is not encrypted"
// *Cause: An attempt was made to rekey or decrypt an unencrypted column.
//
// *Action:
//
/
28334, 0000, "column is already encrypted"
// *Cause: An attempt was made to encrypt an encrypted column.
//
// *Action:
//
/
28335, 0000, "referenced or referencing FK constraint column cannot be encrypted"
// *Cause: encrypted columns were involved in the referential constraint
//
// *Action:
//
/
28336, 0000, "cannot encrypt SYS owned objects"
// *Cause: An attempt was made to encrypt columns in a table owned by SYS.
//
// *Action:
//
/
28337, 0000, "the specified index may not be defined on an encrypted column"
// *Cause: Index column was either a functional, domain, or join index.
//
// *Action:
//
/
28338, 0000, "Column(s) cannot be both indexed and encrypted with salt"
// *Cause: An attempt was made to encrypt index column with salt or
// an attempt was made to create an index on encrypted column with salt.
//
// *Action: Alter the table and specify column encrypting without salt.
//
/
28339, 0000, "missing or invalid encryption algorithm"
// *Cause: Encryption algorithm was missing or invalid in the user command.
//
// *Action: Must specify a valid algorithm.
//
/
28340, 0000, "a different encryption algorithm has been chosen for the table"
// *Cause: Existing encrypted columns were associated with a different algorithm.
//
// *Action: No need to specify an algorithm, or specify the same one for the
// existing encrypted columns.
/
28341, 0000, "cannot encrypt constraint column(s) with salt"
// *Cause: An attempt was made to encrypt constraint columns with salt.
//
// *Action: Encrypt the constraint columns without salt.
//
/
28342, 0000, "integrity check fails on column key"
// *Cause: Encryption metadata may have been improperly altered.
//
// *Action:
//
/
28343, 0000, "fails to encrypt data"
// *Cause: data or encryption metadata may have been improperly altered or
// the security module may not have been properly setup
//
// *Action:
//
28344, 0000, "fails to decrypt data"
// *Cause: data or encryption metadata may have been improperly altered or
// the security module may not have been properly setup
//
// *Action:
//
/
28345, 00000, "cannot downgrade because there exists encrypted column"
// *Cause: An attempt was made to downgrade when there was an encrypted
// column in the system.
// *Action: Decrypt these columns before attempting to downgrade.
/
28346, 00000, "an encrypted column cannot serve as a partitioning column"
// *Cause: An attempt was made to encrypt a partitioning key column or
// create partitioning index with encrypted columns.
// *Action: The column must be decrypted.
/
28347, 00000, "encryption properties mismatch"
// *Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION |
// SUBPARTITION command, but encryption properties were mismatched.
// *Action: Make sure encrytion algorithms and columns keys are identical.
// The corresponding columns must be encrypted on both tables with
// the same salt and non-salt flavor.
/
28348, 0000, "index defined on the specified column cannot be encrypted"
// *Cause: An attempt was made to encrypt a column which is in a functional
// index, domain index, or join index.
//
// *Action: drop the index
//
/
28349, 0000, "cannot encrypt the specified column recorded in the materialized view log"
// *Cause: An attempt was made to encrypt a column which is already recorded
// in the materialized view log.
//
// *Action: drop the materialized view log
//
/
28350, 0000, "cannot encrypt the specified column recorded in CDC synchronized change table"
// *Cause: An attempt was made to encrypt a column which is already recorded
// in CDC synchronized change table.
// *Action: drop the synchronized change table
/
28351, 0000, "cannot encrypt the column of a cluster key"
// *Cause: An attempt was made to encrypt a column of the cluster key.
// A column of the cluster key in a clustered table cannot be
// encrypted.
// *Action: None
/
28352, 0000, "Event to force ZT error in kzekm"
// *Document: NO
// *Cause: N/A
// *Action: Set this event in your environment to simulate a ZT error.
// *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
//
/
28353, 0000, "failed to open wallet"
// *Cause: The database was unable to open the security module wallet due
// to an incorrect wallet path or password It is also possible
// that a wallet has not been created. Type mkwallet from command
// line for instructions.
// *Action: Execute the command again using the correct wallet password or
// verfying a wallet exists in the specified directory. If
// necessary, create a new wallet and initialize it.
/
28354, 0000, "Encryption wallet, auto login wallet, or HSM is already open"
// *Cause: Encryption wallet, auto login wallet, or HSM was already opened.
// *Action: None.
//
/
28355, 0000, "failed to initialize security module"
// *Cause:
//
// *Action:
//
/
28356, 0000, "invalid open wallet syntax"
// *Cause: The command to open the wallet contained improper spelling
// or syntax.
// *Action: If attempting to open the wallet, verify the spelling and
// syntax and execute the command again.
/
28357, 0000, "password required to open the wallet"
// *Cause: A password was not provided when executing the open wallet
// command, the isolate keystore command, or the unite keystore
// command.
// *Action: Retry the command with a valid password.
/
28358, 0000, "improper set key syntax"
// *Cause: The command to set the master key contained improper spelling
// or syntax.
// *Action: If attempting to set the master key for Transparent Database
// Encryption, verify the spelling and syntax and execute
// the command again.
/
28359, 0000, "invalid certificate identifier"
// *Cause: The certificate specified did not exist in the wallet.
// *Action: Query the V$WALLET fixed view to find the proper certificate
// identifier for certificate to be used.
/
28360, 0000, "security module internal error"
// *Cause:
//
// *Action:
//
/
28361, 0000, "master key not yet set"
// *Cause: The master key for the instance was not set.
// *Action: Execute the ALTER SYSTEM SET KEY command to set a master key
// for the database instance.
/
28362, 0000, "master key not found"
// *Cause: The required master key required could not be located. This may
// be casued by the use of an invalid or incorrect wallet.
// *Action: Check wallet location parameters to see if they specify the
// correct wallet. Also, verify that an SSO wallet is not being used
// when an encrypted wallet is intended.
28363, 0000, "buffer provided not large enough for output"
// *Cause: A provided output buffer is too small to contain the output.
// *Action: Check the size of the output buffer to make sure it is initialized
// to the proper size.
/
28364, 0000, "invalid wallet operation"
// *Cause: The command to operate the wallet contained improper spelling
// or syntax.
// *Action: Verify the spelling and syntax and execute the command again.
/
28365, 0000, "wallet is not open"
// *Cause: The security module wallet has not been opened.
// *Action: Open the wallet.
/
28366, 0000, "invalid database encryption operation"
// *Cause: The command for database encryption contained improper spelling
// or syntax.
// *Action: Verify the spelling and syntax and execute the command again.
/
28367, 0000, "wallet does not exist"
// *Cause: The Oracle wallet has not been created or the wallet location
// parameters in sqlnet.ora specifies an invalid wallet path.
// *Action: Verify that the WALLET_LOCATION or the ENCRYPTION_WALLET_LOCATION
// parameter is correct and that a valid wallet exists in the path
// specified.
/
28368, 0000, "cannot auto-create wallet"
// *Cause: The database failed to auto create an Oracle wallet. The Oracle
// process may not have proper file permissions or a wallet may
// already exist.
// *Action: Confirm that proper directory permissions are granted to the Oracle
// user and that neither an encrypted or obfuscated wallet exists in
// the specified wallet location and try again.
/
28369, 0000, "cannot add files to encryption-ready tablespace when offline"
// *Cause: You attempted to add files to an encryption-ready tablespace when
// all the files in the tablespace were offline.
// *Action: Bring the tablespace online and try again
//
/
28370, 0000, "ENCRYPT, DECRYPT or REKEY option not allowed"
// *Cause: An attempt was made to specify the ENCRYPT, DECRYPT or REKEY option
// on an unsupported tablespace.
// *Action: Remove this option and retry the statement.
//
/
28371, 0000, "ENCRYPTION clause or ENCRYPT option not allowed"
// *Cause: An attempt was made to specify the ENCRYPTION clause or
// ENCRYPT option for system and undo tablespaces.
// *Action: Remove one or both of these options and retry the statement.
//
/
28372, 0000, "missing ENCRYPT option for encrypted tablespace"
// *Cause: An attempt was made to specify the ENCRYPTION property for the
// CREATE TABLESPACE statement without specifying the ENCRYPT option
// to encrypt the tablespace.
// *Action: Add the ENCRYPT option and retry the statement.
//
/
28373, 0000, "missing or out of order ENCRYPTION clause"
// *Cause: An attempt was made to specify the ENCRYPT or DECRYPT option in the
// CREATE TABLESPACE statement or to specify the ENCRYPT or REKEY
// option in the ALTER TABLESPACE statement without first specifying
// the ENCRYPTION property for the tablespace.
// *Action: Add the ENCRYPTION clause or correct the syntax, and retry the
// statement.
//
/
28374, 0000, "typed master key not found in wallet"
// *Cause: You attempted to access encrypted tablespace or redo logs with
// a typed master key not existing in the wallet.
// *Action: Copy the correct Oracle Wallet from the instance where the tablespace
// was created.
//
/
28375, 0000, "cannot perform cross-endianism conversion on encrypted tablespace"
// *Cause: You attempted to perform cross-endianism conversion on encrypted
// tablespace.
// *Action: Cross-endianism conversion on encrypted tablespace is not supported.
//
/
28376, 0000, "cannot find PKCS11 library"
// *Cause: The HSM vendor's library cannot be found.
// *Action: Place the HSM vendor's library in the following directory structure:
// For Unix like system:
// /opt/oracle/extapi/[32,64]/hsm/{VENDOR}/{VERSION}/lib<apiname>.<ext>
// For Windows systems:
// %SYSTEM_DRIVE%\oracle\extapi\[32,64]\hsm\{VENDOR}\{VERSION}\lib<apin// ame>.<ext>
// [32, 64] - refers to 32bit or 64bit binary.
// {VENDOR} - The name of the vendor supplying the library.
// {VERSION} - Version of the library, perferably in num#.num#.num# for// mat.
/
28377, 0000, "No need to migrate from wallet to HSM"
// *Cause: There are either no encrypted columns or all column keys are already
// encrypted with the HSM master key.
// *Action: No action required.
/
28378, 0000, "Wallet not open after setting the Master Key"
// *Cause: The Master Key has been set or reset. However, wallet could not be
// reopened successfully.
// *Action: Reopen the wallet.
/
28379, 0000, "a different integrity algorithm has been chosen for the table"
// *Cause: Encrypted columns were associated with a different algorithm.
//
// *Action: You do not need to specify an algorithm, or specify the same
// one for the existing encrypted columns.
/
28380, 00000, "Event to force all newly created tablespaces to be encrypted for testing"
// *Document: NO
// *Cause: N/A
// *Action: Set this event in your environment to force all newly created
// tablespaces to be encrypted tablespaces. It is an easy way to
// convert an existing test to run with tablespace encryption. It is
// used for testing only and not for security. Often run with event
// 28381.
// *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
/
28381, 00000, "Event to bypass wallet setup for tablespace encryption"
// *Document: NO
// *Cause: N/A
// *Action: Set this event in your environment to bypass wallet setup for
// tablespace encryption. It uses a dummy encryption master key to
// simulate encryption or decryption by the wallet, and has no wallet
// dependency. It is an easy way to convert an existing test to run
// with tablespace encryption. It is used for testing only and not for
// security. Often run with event 28380.
// *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
/
28382, 00000, "Global wallet operation in RAC failed"
// *Cause: Wallet operation in RAC failed.
// *Action: Check V$WALLET_ENCRYPTION table to verify if the wallet operation
// succeeded on any instance. Retry the operation.
/
28383, 00000, "cannot do a PKI certificate-based Master Key migration"
// *Cause: A PKI certificate-based Master Key migration was not allowed.
// *Action: Execute a symmetric Master Key migration.
/
28384, 0000, "cannot perform Tablespace Encryption"
// *Cause: Tablespace Encryption was attempted when PKI certificate-based
// Master Key was in use.
// *Action: Perform a symmetric Master Key Rekey.
/
28385, 0000, "cannot perform a PKI certificate-based migration"
// *Cause: A PKI certificate-based migration to HSM was attempted.
// *Action: Perform a symmetric Master Key migration.
/
28386, 0000, "cannot perform a PKI certificate-based Master Key Rekey"
// *Cause: A PKI certificate-based Master Key Rekey was attempted when
// Tablespace Encryption or HSM was in use.
// *Action: Perform a symmetric Master Key Rekey or disable Tablespace
// Encryption for all tablespaces.
/
28387, 00000, "Could not acquire an enqueue for wallet operation in Oracle RAC"
// *Cause: Enqueue to block TDE operations in Oracle RAC database could
// not be obtained.
// *Action: Retry the wallet operation.
/
28388, 00000, "database is not open in read/write mode"
// *Cause: Database was not open in read/write mode and could not perform
// these wallet operations.
// *Action: Open the database in read/write mode and retry this command.
/
28389, 00000, "cannot close auto login wallet"
// *Cause: Auto login wallet could not be closed because it was opened with
// another wallet or HSM requiring a password.
// *Action: Close the wallet or HSM with a password.
/
28390, 00000, "auto login wallet not open but encryption wallet may be open"
// *Cause: Auto login wallet was not open. But, the encryption wallet may
// still be open and subsequent TDE operations might succeed.
// *Action: If auto login wallet is closed but TDE operations succeed,
// check the status of the encryption wallet and close that if
// required.
/
28391, 00000, "cannot close wallet or HSM, password mismatch"
// *Cause: Password provided did not match the password of the open
// wallet or HSM.
// *Action: Provide the correct password for wallet or HSM to
// close the wallet or HSM.
/
28392, 0000, "invalid close wallet syntax"
// *Cause: The command to close the wallet contained improper spelling
// or syntax.
// *Action: If attempting to close the wallet, verify the spelling and
// syntax and execute the command again.
/
28393, 0000, "password required to close the wallet"
// *Cause: A password was not provided when executing the close wallet
// command.
// *Action: Retry the command with a valid password.
/
28394, 0000, "decryption of data of length %s failed"
// *Cause: Decryption of data failed. Error may be due to plain text data in
// an external file being submitted for decryption, data encrypted
// with a different key or a utility being submitted for decryption,
// or TDE encrypted data in data files being corrupted.
// *Action: Verify that the correct external file is being specified or contact
// Oracle Support Services.
/
28395, 0000, "could not write the new master key to the wallet"
// *Cause: An attempt was made to write the new master key to the wallet. The
// wallet or the parent directory may not have the proper file
// permissions to write the master key in the wallet.
// *Action: Check the password-based wallet, auto login wallet, the parent
// directory permissions and disk space availability on the file
// system. Make sure that the Oracle processes have read/write
// permissions on the password-based and auto login wallets. Retry
// the command.
/
28396, 0000, "rekey of enc$ dictionary table failed"
// *Cause: One or more master keys required for the rekey operation could
// not be found in the wallet. Either incorrect master key identifiers
// were inserted into the enc$ dictionary table or the wallet
// containing the referenced master keys were improperly modified
// or deleted.
// *Action: Restore the most recent copy of the wallet and try again.
/
28397, 0000, "cannot bring file %s online since it has a passphrase-wrapped key"
// *Cause: The encrypted tablespace file was rewrapped using passphrase
// through the DBMS_TTS.PASSPHRASE_REWRAP_KEY procedure. Therefore it
// cannot be part of the database until it is converted by RMAN.
//
// *Action: Do not attempt to bring files with passphrase-wrapped keys online.
/
28398, 0000, "cannot rewrap encryption key for this file"
// *Cause: Cannot rewrap encryption key for this file because it was not
// from an encrypted tablespace, or it had already been rewrapped.
//
// *Action: Verify that the file is a copy of a file from an encrypted
// tablespace.
/
28399, 00000, "Event to disable automatic TDE wallet management in RAC"
// *Document: NO
// *Cause: N/A
// *Action: Set this event in your environment to disable the automatic
// management of wallet in RAC.
/
28400, 00000, "Event to enable TDE tracing"
// *Document: NO
// *Cause: N/A
// *Action: Set this event in your environment to obtain trace information
// for Transparent Data Encryption.
// *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
28402, 00000, "Event to disable restriction on 'grant any object privilege' system privilege"
// *Document: NO
// *Cause: N/A
// *Action: Set this event in your environment to allow user with 'grant any
// object privilege' system privilege to grant privilege on a view
// that the view owner is permitted to grant, even if the view owner
// does not have the privilege with 'with grant option' on the
// underlying objects. It would otherwise raise ORA-01720.
// *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
28403, 00000, "file %s cannot be modified because it is an online data file"
// *Cause: An attempt was made to modify an online data file when the file was
// not expected to be part of the database.
// *Action: Check the status of the file and its tablespace and make sure it
// is offline or is a copy of a data file
28404, 00000, "role cannot be altered"
// *Cause: An attempt was made to alter the role to become a global, external,
// password protected, or secure application role. The role could not
// be altered because it was already granted to one or more other
// roles or program units.
// *Action: Use REVOKE to revoke the role from other roles first.
28405, 00000, "cannot grant secure role to a role"
// *Cause: Role granted was a password protected or secure application role.
// This role can only be granted directly to a user.
// *Action: Grant the role directly to a user.
28406, 00000, "Event to keep connection made by database to OID open when enterprise user logs into database"
// *Document: NO
// *Cause: N/A
// *Action: Set this event in your environment to keep connection made by
// database to OID open when enterprise user logs into database.
// Default behaviour is to close the connection once enterprise user
// logs into database.
// *Note: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED.
28407, 0000, "Hardware Security Module failed with PKCS#11 error %s(%s)"
// *Cause: The Hardware Security Module (HSM) connection may have been lost
// or another internal HSM error was reached.
// *Action: Check the error. For more information on the error, check the trace
// files and try the following:
// 1) Retry the command. If the error repeats, go to step 2.
// 2) Verify that the HSM is configured correctly and connected.
// Retry the command. If the error repeats, go to step 3.
// 3) Ask your Security Officer to close and open the security
// module. Retry the command. If the error repeats, go to step 4.
// 4) Bounce the database if possible. Retry the command.
// If the error repeats, contact Oracle Support Services or your
// HSM vendor's support.
/
28408, 00000, "encryption using passphrase failed"
// *Cause: Encryption with the passphrase failed which was likely due to an invalid
// or missing passphrase or due to an internal error.
// *Action: Verify that the passphrase is provided and try the operation again. If
// the problem persists contact Oracle Support Services.
28409, 00000, "decryption using passphrase failed"
// *Cause: Decryption with the passphrase failed which was likely due to an invalid
// or missing passphrase or due to an internal error.
// *Action: Verify that the passphrase is provided and try the operation again. If
// the problem persists contact Oracle Support Services.
/
/
28410, 0000, "No need to migrate from HSM to wallet."
// *Cause: There were either no encrypted columns or all column keys were
// already encrypted with the wallet master key.
// *Action: No action required.
/
28411, 0000, "auto login wallet cannot be open during migration"
// *Cause: Auto login wallet could not be opened during migration.
// *Action: Close the auto login wallet and try the migration again.
/
28412, 0000, "cannot determine the database migration status"
// *Cause: The migration status of the database could not be determined.
// *Action: Verify if the migration status is correct in props$ and, if not,
// correct it. Shutdown and startup the database.
/
28414, 0000, "specified keys are in HSM"
// *Cause: Master key rekey or activation failed because the keys were in
// Hardware Security Module(HSM) but the configuration indicated that
// the keys were in wallet.
// *Action: Correct the sqlnet.ora configuration to HSM or migrate to wallet.
/
28415, 0000, "specified keys are in wallet"
// *Cause: Master key rekey or activation failed because the keys were in
// wallet but the configuration indicated that the keys were in
// Hardware Security Module(HSM).
// *Action: Correct the sqlnet.ora file configuration to wallet or migrate
// to HSM.
/
28416, 0000, "specify the correct keystore in the sqlnet.ora file"
// *Cause: The keystore specified in the sqlnet.ora file was incorrect.
// *Action: When migrating to HSM, the keystore specified in sqlnet.ora file
// should be HSM and similarly when migrating to wallet, the keystore
// specified in sqlnet.ora should be wallet. Check if the sqlnet.ora
// file configuration is correct and, if not, correct it.
/
28417, 0000, "password-based keystore is not open"
// *Cause: Password-based keystore was not opened.
// *Action: Close the auto login keystore, if required, and open a
// password-based keystore.
/
28418, 0000, "password-based HSM is not open"
// *Cause: Password-based HSM was not opened.
// *Action: Close the auto login keystore, if required, and open a
// password-based HSM.
/
28419, 00000, "migration from wallet to Hardware Security Module (HSM) failed"
// *Cause: The TDE_MASTER_KEY_ID entry did not exist in props$ table.
// A subsequent attempt to add TDE_MASTER_KEY_ID entry into
// props$ failed.
// *Action: Verify why the TDE_MASTER_KEY_ID entry was deleted from the props$
// table. Retry the command.
/
28420, 00000, "cannot open resetlogs from a restore point prior to wallet creation"
// *Cause: The open resetlogs, open read-only, or standby activation operation
// failed because the restore point is prior to the wallet creation, and
// the data file does not contain the database key information as stored
// in the control file.
// *Action: Restore to a restore point after the wallet creation, or rebuild the
// control file with existing data files.
/
28421, 00000, "cannot FINISH a tablespace encrypt, decrypt or rekey command which has not started"
// *Cause: The ALTER TABLESPACE FINISH [ENCRYPT | DECRYPT | REKEY] command
// did not find a failed attempt for tablespace encrypt, decrypt or
// rekey.
// *Action: Check if tablespace already has a desired key version and reissue
// the command without FINISH keyword if necessary.
/
28422, 00000, "operation disallowed: concurrent master key rekey"
// *Cause: Concurrent master key rekey was detected.
// *Action: Wait for the master key rekey operation to complete and retry
// the command.
//
/
28423, 00000, "current operation disallowed: %s tablespace is being encrypted, decrypted, or rekeyed"
// *Cause: The specified tablespace was being concurrently encrypted,
// decrypted, or rekeyed.
// *Action: Wait for the concurrent operation to complete and retry the command.
//
/
28424, 00000, "ENCRYPT, DECRYPT or REKEY option already specified"
// *Cause: In the CREATE or ALTER TABLESPACE statement, the ENCRYPT, DECRYPT
// or REKEY option was specified more than once.
// *Action: Remove all but one of the ENCRYPT, DECRYPT or REKEY options.
/
28425, 00000, "missing a valid FILE_NAME_CONVERT clause"
// *Cause: A valid FILE_NAME_CONVERT clause was not specified with the
// ALTER TABLESPACE [ENCRYPT | DECRYPT | REKEY] statement. The
// FILE_NAME_CONVERT clause is required unless Oracle Managed Files
// are being used.
// *Action: Specify a valid FILE_NAME_CONVERT clause and retry the command.
/
28426, 00000, "must FINISH a tablespace encrypt, decrypt or rekey command first"
// *Cause: The ALTER TABLESPACE [ENCRYPT | DECRYPT | REKEY] command found a
// previously failed attempt for tablespace encrypt, decrypt or rekey.
// *Action: Issue the ALTER TABLESPACE FINISH [ENCRYPT | DECRYPT | REKEY] command
// to complete the attempt for tablespace encrypt, decrypt or rekey.
/
28427, 00000, "cannot create, import or restore unencrypted tablespace: %s in Oracle Cloud"
// *Cause: The specified tablespaces were not encrypted. Oracle Cloud
// mandates that all tablespaces must be encrypted.
// *Action: Create, import or restore an encrypted tablespace, or encrypt the
// specified tablespace.
/
28428, 00000, "cannot encrypt or decrypt a data file in mount mode when the database is open elsewhere"
// *Cause: An attempt was made to encrypt or decrypt a data file in mount mode
// when the database was already opened by another Oracle RAC instance.
// *Action: Ensure that the database is not open anywhere and retry the command.
/
28429, 00000, "cannot encrypt or decrypt a data file on standby when it is open read-only"
// *Cause: An attempt was made to encrypt or decrypt a data file on a standby
// database when it was already opened in read-only mode.
// *Action: Restart the standby instance in mount mode and retry the command.
/
28430, 00000, "cannot encrypt or decrypt a data file for online tablespace %s"
// *Cause: An attempt was made to encrypt or decrypt a data file for an
// online tablespace.
// *Action: Bring the tablespace offline and retry the command.
/
28431, 00000, "cannot encrypt an already encrypted data file %s"
// *Cause: An attempt was made to encrypt a data file that was already encrypted
// in an encrypted tablespace.
// *Action: Check if the data file belongs to an encrypted tablespace.
/
28432, 00000, "cannot encrypt data file %s in seed pluggable database"
// *Cause: An attempt was made to encrypt a data file that was part of a seed
// pluggable database, which is not allowed.
// *Action: Check if the data file belongs to a seed pluggable database.
/
28433, 00000, "mismatched encryption property between data file %s and tablespace %s"
// *Cause: Either an unencrypted data file in an encrypted tablespace or an
// encrypted data file in an unencrypted tablespace was found.
// When bringing a tablespace online or opening the database,
// all data files in an encrypted tablespace must be encrypted, and
// all data files in an unencrypted tablespace must be unencrypted.
// *Action: Encrypt all of the data files in the tablespace before resuming the
// operation.
/
28434, 00000, "cannot decrypt an unencrypted data file %s"
// *Cause: An attempt was made to decrypt a data file that was unencrypted.
// *Action: Check if the data file belongs to an encrypted tablespace.
/
28435, 00000, "cannot decrypt data file %s which is not encrypted with the database key"
// *Cause: An attempt was made to decrypt a data file that was not encrypted
// with the database key. Only data files encrypted with the ALTER
// DATABASE DATAFILE ENCRYPT or ALTER TABLESPACE ENCRYPTION OFFLINE
// ENCRYPT statement are encrypted with the database key.
// *Action: Check if the data file belongs to an encrypted tablespace with a
// different key from the database key in the V$DATABASE_KEY_INFO
// view, or use the ALTER TABLESPACE ENCRYPTION ONLINE DECRYPT
// statement instead.
/
28436, 00000, "cannot encrypt data file %s in SYSTEM or SYSAUX tablespace"
// *Cause: An attempt was made to encrypt a data file that was a part of the
// SYSTEM or SYSAUX tablespace, which is not allowed in compatibility
// lower than 12.2.
// *Action: Check if the data file belongs to SYSTEM or SYSAUX tablespace, or
// change the database compatibility to 12.2 or later.
/
28437, 00000, "unexpected FILE_NAME_CONVERT clause with Oracle Managed Files"
// *Cause: A FILE_NAME_CONVERT clause was specified with the
// ALTER TABLESPACE [ENCRYPT | DECRYPT | REKEY] statement, which is not
// allowed when the database is using Oracle Managed Files.
// *Action: Remove the FILE_NAME_CONVERT clause and retry the command.
/
28438, 00000, "ALTER TABLESPACE %s ENCRYPTION %s%s operation not complete"
// *Cause: The ALTER TABLESPACE [ENCRYPT | DECRYPT | REKEY] command started
// but could not complete for all the data files of this tablespace.
// *Action: Check if all the data files are online and if the specified
// FILE_NAME_CONVERT clause covers all the data files of this
// tablespace, and retry the command with FINISH keyword, if
// V$ENCRYPTED_TABLESPACES shows that the tablespace is not in NORMAL
// status.
/
28439, 00000, "cannot close wallet when SYSTEM, SYSAUX, UNDO, or TEMP tablespaces are encrypted"
// *Cause: An attempt was made to close the wallet for a database
// with an encrypted SYSTEM, SYSAUX, UNDO, or TEMP tablespace.
// *Action: Decrypt the tablespace and retry the command.
/
28440, 00000, "cannot offline encrypt or decrypt data file %s - file is in use or recovery"
// *Cause: An attempt was made to offline encrypt or decrypt a data file
// that was online in an open instance, being encrypted or decrypted
// by another session, or was being recovered.
// *Action: Ensure that the tablespace is offline and no other encrypt or
// decrypt operation is performed on this data file, and end all
// recovery sessions.
28441, 00000, "RMAN clone instance cannot open wallet"
// *Cause: The RMAN clone instance failed to open the auto login wallet in an
// operation such as a pluggable database (PDB) or tablespace
// point-in-time recovery because the auto login wallet was
// incorrectly configured, or did not exist.
// *Action: Check and correct the auto-login wallet configuration or create
// an auto-login wallet from the password wallet, and retry the
// operation.
/
28442, 00000, "Rekey of the TDE master encryption key is not permitted when the database is in restricted mode."
// *Cause: An attempt was made to rekey the Transparent Data Encryption (TDE)
// master encryption key when the database was in restricted mode.
// *Action: Open the database in read-write mode and retry the command.
/
/
28443, 00000, "cannot access the TDE wallet"
// *Cause: An attempt was made to access the Transparent Data Encryption (TDE)
// master encryption key in the TDE wallet.
// *Action: Create a TDE wallet, provision a TDE master encryption key in the
// wallet and ensure that the wallet is open.
/
28444, 00000, "cannot enforce encryption of dictionary data"
// *Cause: Either encryption of the dictionary data was already enforced or an
// attempt was made to enforce encryption of the dictionary data with
// compatible parameter earlier than release 12.2.0.2.
// *Action: Ensure that the compatible parameter is later than release
// 12.2.0.2 because earlier versions cannot handle encrypted
// dictionary data.
/
28445, 00000, "Execution of the command failed."
// *Cause: Command execution failed due to an internal error.
// *Action: Check the trace file to learn the exact cause.
/
28446, 00000, "cannot execute dictionary data rekey/delete key"
// *Cause: Could not find an existing data encryption key.
// *Action: Ensure that a data encryption key exists before regenerating or
// deleting it.
/
28447, 00000, "insufficient privilege to execute ALTER DATABASE DICTIONARY statement"
// *Cause: An attempt was made to execute the ALTER DATABASE DICTIONARY
// statement without the necessary SYSKM privilege. For
// CONTAINER = ALL clause, the user must have the commonly granted
// SYSKM privilege or the user must have the local SYSKM privilege.
// *Action: Ensure that the user has the necessary privilege before executing the DDL.
/
28448, 00000, "The ALTER DATABASE DICTIONARY statement was used incorrectly."
// *Cause: ALTER DATABASE DICTIONARY statement was used incorrectly.
// *Action: Ensure that a valid ALTER DATABASE DICTIONARY statement is executed.
/
28449, 00000, "cannot use an invalidated database link"
// *Cause: An attempt was made to use an invalid database link.
// *Action: Reset the password of the invalidated database link.
/
28450, 00000, "encryption specified with CREATE DATABASE or CREATE PLUGGABLE DATABSE"
// *Cause: The encryption option was specified in a CREATE DATABASE
// or a CREATE PLUGGABLE DATABASE statement.
// *Action: Do not specify encryption in the CREATE DATABASE or CREATE
// PLUGGABLE DATABASE statement.
/
/ 28500-28749 RESERVED FOR THE HETEROGENEOUS SERVICES
/
28500, 00000, "connection from ORACLE to a non-Oracle system returned this message:"
// *Cause: The cause is explained in the forwarded message.
// *Action: See the non-Oracle system's documentation of the forwarded
// message.
//
28501, 00000, "communication error on heterogeneous database link"
// *Cause: An unexpected communication failure occurred
// on a heterogeneous database link to a non-Oracle system.
// The message above will be followed by a second message generated
// by the connected non-Oracle system.
// *Action: See the documentation for the non-Oracle system
// for an explanation of the second error message.
//
28502, 00000, "internal communication error on heterogeneous database link"
// *Cause: A communication error internal to ORACLE's heterogeneous
// services has occurred.
// *Action: Contact Oracle customer support.
//
28503, 00000, "bind value cannot be translated into SQL text for non-Oracle system"
// *Cause: A SQL statement used bind variables on a Heterogenous Services
// database link to a non-Oracle system, but the non-Oracle system
// does not support bind variables.
// *Action: Change your SQL statement so that it does not use bind variables.
//
28504, 00000, "ROWID not found in ROWID cache for heterogeneous database link"
// *Cause: The ROWID cache for Heterogeneous Services held no entry that
// corresponds to the specified ROWID. The ROWID entry may have been
// overwritten in the ROWID cache.
// *Action: Enlarge the Heterogeneous Services ROWID cache size by increasing
// the value of the Heterogenous Services initialization parameter
// HS_ROWID_CACHE_SIZE.
//
28505, 00000, "cannot get non-Oracle system capabilities from %s"
// *Cause: ORACLE was unable to retrieve capability information
// for the non-Oracle system connected through a heterogeneous
// database link. This capability information should be
// stored in data dictionary tables viewable with the
// HS_CLASS_CAPS or HS_INST_CAPS data dictionary views.
// *Action: Contact the DBA to check the server data dictionary table
// named in the error message. If table contents are
// incorrect, the DBA should restore all data dictionary content for
// this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is
// sufficient to delete all current data dictionary content for this
// class and/or instance and initiate a new connection
// to let the connected agent upload new data dictionary content
// to the server.
//
28506, 00000, "parse error in data dictionary translation for %s stored in %s"
// *Cause: A reference to an ORACLE data dictionary table or view name
// on a heterogeneous database link to a non-Oracle system
// could not be translated. The ORACLE data dictionary tables
// shown with view HS_CLASS_DD contain invalid SQL for the data
// dictionary translation.
// *Action: Contact customer support of the agent vendor.
//
28507, 00000, "error in data dictionary view %s"
// *Cause: The initialization parameter table for the Heterogeneous Services
// was not available, or its structure (number of columns or
// column types) was incorrect.
// *Action: Verify correct installation of the following Heterogeneous Services'
// initialization parameter views: HS_CLASS_INIT and HS_INST_INIT.
// If these views are not available, make sure you ran the
// script CATHS.SQL in the $ORACLE_HOME/rdbms/admin directory.
//
28508, 00000, "invalid value %s for Heterogeneous Services initialization parameter %s"
// *Cause: The specified Heterogeneous Services initialization parameter
// had an invalid value when attempting to connect to a non-Oracle
// system.
// *Action: Check the Heterogeneous Services and agent documentation to
// determine acceptable values
//
28509, 00000, "unable to establish a connection to non-Oracle system"
// *Cause: Initialization of a database link to a non-Oracle system
// failed to connect to the Heterogeneous Services agent
// process for this non-Oracle system.
// *Action: Check the Net8 service name definition in the following
// places:
// -- the USING clause of the CREATE DATABASE LINK statement
// -- the TNSNAMES.ORA file
// -- the Oracle Names Server
//
// The following are possible reasons for name mismatches:
// -- The USING clause in the CREATE DATABASE LINK statement has
// to match the service name defined in the TNSNAMES.ORA file
// or in the Oracle Names Server.
// -- The protocol-specific information in the service name
// definition must match the protocol-specific definition
// of the responding listener.
// -- The SID=<name> in the service name definition
// (in the TNSNAMES.ORA file or in Oracle Names Server) must
// match the value in the LISTENER.ORA file for the responding
// listener.
//
28510, 00000, "heterogeneous database link initialization failed"
// *Cause: Initialization of a heterogeneous database link to a
// non-Oracle system failed due to an error identified
// by the agent for this non-Oracle system.
// *Action: Make sure the non-Oracle system is up and running and that
// all of the environment and initialization values for the agent
// are set correctly.
//
28511, 00000, "lost RPC connection to heterogeneous remote agent using SID=%s"
// *Cause: A fatal error occurred in one of the following places:
// -- the connection between the ORACLE server and the agent
// -- the heterogeneous services remote agent itself
// -- the connection to the non-Oracle system
// This error occurred after communication had been established
// successfully.
// *Action: Check for network problems and remote host crashes. The problem is
// probably in the agent software. If so, contact a customer support
// representative of the agent vendor.
//
28512, 00000, "cannot get data dictionary translations from %s"
// *Cause: ORACLE was unable to retrieve data dictionary translation
// information for the non-Oracle system connected through a
// heterogeneous database link. This data dictionary translation
// information should be stored in data dictionary tables viewable
// with the HS_CLASS_DD or HS_INST_DD data dictionary views.
// *Action: Ask your DBA to check the server data dictionary table
// named in the error message. If table contents are
// incorrect, the DBA should restore all data dictionary content for
// this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is
// sufficient to delete all current data dictionary content for this
// class and/or instance and initiate a new connection
// to let the connected agent upload new data dictionary content
// to the server.
//
28513, 00000, "internal error in heterogeneous remote agent"
// *Cause: An internal error has occurred in the Oracle remote agent
// supporting a heterogeneous database link.
// *Action: Make a note of how the error was produced and contact the
// customer support representative of the agent vendor.
//
28514, 00000, "heterogeneous database link initialization could not convert system date"
// *Cause: The system date was not retrievable.
// *Action: Verify that the ORACLE server's host machine and operating system
// are operational. This error should not occur unless low level
// system functions are failing.
//
28515, 00000, "cannot get external object definitions from %s"
// *Cause: ORACLE was unable to retrieve definitions of distributed external
// procedures or remote libraries registered for the non-Oracle system
// instance, probably because the underlying data dictionary table
// does not exist or is malformed.
// *Action: Verify that the ORACLE server's Heterogeneous Services
// data dictionary was installed correctly. If the Heterogeneous
// Services data dictionary is not installed, execute the CATHS.SQL
// script in the $ORACLE_HOME/rdbms/admin directory.
//
28518, 00000, "data dictionary translation has illegal translation type"
// *Cause: A data dictionary translation definition, either in the ORACLE
// server data dictionary or in data dictionary content uploaded
// from a Heterogeneous Services agent, specified an illegal
// translation type code. Legal values are 'T' or 't' for
// 'translate', 'M' or 'm' for 'mimic'. Information on the exact
// data dictionary translation causing the error is written
// to a trace (*.TRC) file for the ORACLE instance and to
// the ORACLE instance's alert log. This error occurs
// when a Heterogeneous Services agent uploads data dictionary
// content to an ORACLE server on the first connection from the server
// to the agent.
// *Action: Contact the customer support of the agent vendor.
//
28519, 00000, "no heterogeneous data dictionary translations available"
// *Cause: The ORACLE server's data dictionary did not define data dictionary
// translations for the connected non-Oracle system, and automatic
// self-registration (data dictionary upload) was disabled.
// *Action: Ask a DBA to resolve this problem. The easiest solution is
// to enable automatic self-registration by setting the ORACLE
// server's HS_AUTO_REGISTER initialization parameter to TRUE.
// An alternative is to load the Heterogeneous Services
// data dictionary with information specific for the non-Oracle
// system by executing a SQL script supplied by the agent vendor.
// If the script is run and the error persists, contact the
// customer support representative of the agent vendor.
//
28520, 00000, "error initializing heterogeneous data dictionary translations"
// *Cause: ORACLE was unable to retrieve data dictionary translations for
// the non-Oracle system instance, probably because the underlying
// data dictionary table does not exist or is formed incorrectly.
// *Action: Verify that the ORACLE server's Heterogeneous Services
// data dictionary was installed correctly. If the Heterogeneous
// Services data dictionary is not installed, execute the CATHS.SQL
// script in the $ORACLE_HOME/rdbms/admin directory. If the connected
// agent, identified by FDS_CLASS_NAME, requires a custom installation
// script for the ORACLE server, verify that the script has been run.
// If both scripts were executed and the error persists, contact the
// customer support representative of the agent vendor.
//
28521, 00000, "no heterogeneous capability information available"
// *Cause: The ORACLE server's data dictionary did not contain
// capability definitions for the connected non-Oracle system,
// and automatic self-registration (data dictionary upload)
// was disabled.
// *Action: Ask a DBA to resolve this problem. The easiest resolution is
// to enable automatic self-registration by setting the ORACLE
// server's HS_AUTO_REGISTER initialization parameter to TRUE.
// An alternative is to load the Heterogeneous Services
// data dictionary with information specific for the non-Oracle
// system by executing a SQL script supplied by the agent vendor.
// If the script is run and the error persists, contact the
// customer support representative of the agent vendor.
//
28522, 00000, "error initializing heterogeneous capabilities"
// *Cause: ORACLE was unable to retrieve capability definitions for
// the non-Oracle system instance, probably because the underlying
// data dictionary table does not exist or is formed incorrectly.
// *Action: Verify that the ORACLE server's Heterogeneous Services
// data dictionary was installed correctly. If the Heterogeneous
// Services data dictionary is not installed, execute the CATHS.SQL
// script in the $ORACLE_HOME/rdbms/admin directory. If the connected
// agent, identified by FDS_CLASS_NAME, requires a custom installation
// script for the ORACLE server, verify that the script has been run.
// If both scripts were executed and the error persists, contact the
// customer support representative of the agent vendor.
//
28523, 00000, "ORACLE and heterogeneous agent are incompatible versions"
// *Cause: An operation on a database link attempted to connect to
// a non-Oracle system, but the ORACLE instance and the
// agent process for the non-Oracle system are incompatible.
// *Action: Ask your DBA to confirm configuration of both the ORACLE
// instance and the agent. Additional information on the
// version incompatibility is logged in trace (*.TRC) files,
// the ORACLE instance and the agent, and in the ORACLE
// instance's alert log. Check the documentation for your agent
// to find out which releases of the Oracle Server are supported.
//
28525, 00000, "unable to create Heterogeneous Services error message text"
// *Cause: Incorrect arguments were passed into the error message
// creation routine.
// *Action: Contact Oracle customer support.
//
28526, 00000, "invalid describe information returned to Heterogeneous Services"
// *Cause: The Heterogeneous Services received invalid describe
// information for a select list, bind list, or stored procedure
// from the Heterogeneous Services agent. This indicates a problem
// with the Heterogeneous Services' non-Oracle system agent.
// *Action: Contact customer support of the agent vendor.
//
28527, 00000, "Heterogeneous Services datatype mapping error"
// *Cause: Either an Oracle datatype could not be mapped to a non-Oracle
// datatype, or a non-Oracle datatype could not be mapped
// to an Oracle datatype. These mappings are defined as
// capability definitions in the ORACLE server's data dictionary.
// *Action: Verify that the ORACLE server's data dictionary has been
// initialized with correct capability definitions for the connected
// FDS_CLASS_NAME and FDS_INST_NAME. If table contents are incorrect,
// a DBA should restore all data dictionary content for this
// FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient
// to delete all current data dictionary content for this class and/or
// instance and initiate a new connection to let the connected agent
// upload new data dictionary content to the server. If the error
// persists contact the customer support representative of the agent
// vendor.
//
28528, 00000, "Heterogeneous Services datatype conversion error"
// *Cause: Either an Oracle datatype could not be converted to a non-Oracle
// datatype, or a non-Oracle datatype could not be converted
// to an Oracle datatype. The following are possible reasons for
// for the conversion failure:
// -- overflow problems (in the case of numbers)
// -- length limitations (in the case of character strings)
// -- invalid values passed into the conversion routines
// *Action: Contact customer support of the agent vendor. If the problem is
// due to size discrepancies between Oracle and the non-Oracle system,
// it may not be possible to convert the value.
//
28529, 00000, "invalid or missing parameter in Net8 service name definition"
// *Cause: There was an invalid or missing Heterogeneous Services parameter
// in the Net8 service name definition stored in either the
// TNSNAMES.ORA file or in the Oracle Names Server.
// *Action: Ask your DBA to make sure the information in the Net8 service
// definition is correct and complete. The correct information that
// should be included in the Net8 service definition can be found in
// the agent's documentation.
//
28530, 00000, "Heterogeneous Services initialization error in NLS language ID"
// *Cause: Heterogeneous Services was unable to initialize an NLS language ID.
// Both the ORACLE server and the Heterogeneous Services agent for the
// connected non-Oracle system must have language IDs.
// *Action: Contact Oracle customer support.
//
28533, 00000, "Heterogeneous Services coercion handling error"
// *Cause: The Heterogeneous Services encountered an error in coercion
// handling. The HS can, if the agent vendor so chooses, perform
// extra processing on SQL statements that contain implicit
// coercions or that contain coercion functions such as TO_CHAR,
// TO_NUMBER or TO_DATE. This functionality is controlled by
// coercion-related capabilities. HS logic reports this error
// when it encounters an error in one of these capability
// definitions.
// *Action: The capability table settings are controlled by the agent
// vendor and can be modified by the DBA. Contact your DBA and
// agent vendor and get the correct set of capabilities installed.
//
28534, 00000, "Heterogeneous Services preprocessing error"
// *Cause: One of the things that the Heterogeneous Services can do is
// to preprocess parts of SQL statements that contain implicit
// coercions or calls to explicit coercion functions like TO_CHAR
// TO_NUMBER or TO_DATE. For example, it could convert a call to
// TO_DATE to a bind variable, pre-evaluate the TO_DATE function
// call and pass the resulting value to the non-Oracle system as
// the bind value. This behavior is controlled by some coercion
// related capabilities. If the capabilities are set incorrectly,
// the HS could encounter errors when it attempts to do the
// preprocessing. If it does then this error will be signaled.
// *Action: The capability table settings are controlled by the agent
// vendor and can be modified by the DBA. Contact your DBA and
// agent vendor and get the correct set of capabilities installed.
//
28535, 00000, "invalid Heterogeneous Services context"
// *Cause: A Heterogeneous Services agent's driver module called
// an HS service routine with an invalid HS context value.
// This probably is a logic error in the driver.
// *Action: Contact Oracle customer support or your agent vendor.
//
28536, 00000, "error in processing Heterogeneous Services initialization parameters"
// *Cause: An error described by a subsequent error message
// prevented successful processing of Heterogeneous Services
// initialization parameters from the ORACLE server data dictionary.
// *Action: Check server data dictionary views HS_CLASS_INIT, HS_INST_INIT, and
// HS_ALL_INITS. Look for conditions which could produce
// the error identified in the error message immediately
// following this one.
//
28537, 00000, "no more result sets"
// *Cause: This error code was used internally within Oracle Database
// Gateway and Heterogeneous Services code and should not be
// reported to a client program.
// *Action: Contact Oracle customer support.
//
28538, 00000, "result set not found"
// *Cause: The client program tried fetching from a result set that is not
// open anymore. Many gateways will, on execution of a stored procedure,
// automatically close all result sets that were returned by any
// previously executed stored procedure.
// *Action: Check the documentation for the gateway that you are using and see
// if it will automatically close currently open result sets each time
// a stored procedure is executed. Then check if your client program is
// doing anything that violates this rule. If it is, fix your program. If
// it is not then contact Oracle customer support.
//
28539, 00000, "gateway does not support result sets"
// *Cause: The client program tried executing a stored procedure that returns
// one or more result sets through a gateway that does not have result
// set support.
// *Action: Check the documentation for the gateway that you are using and see
// if it supports result sets returned from stored procedures. If it
// does not, then the only way of accessing such stored procedures is
// to upgrade to a version of the gateway that does support result
// sets (if such a version exists). If the gateway does have result set
// support and you are still seeing this error then contact Oracle
// customer support.
//
28540, 00000, "internal result set error"
// *Cause: A protocol error internal to Heterogeneous Services or Oracle
// Database Gateway code has occurred.
// *Action: Contact Oracle customer support.
//
28541, 00000, "Error in HS init file on line %d.\n"
// *Cause: A syntax error occurred in the gateway initialization file.
// *Action: Check gateway init file to correct the syntax error.
// For further information, check the error message in the gateway
// trace file.
//
28542, 00000, "Error in reading HS init file \n"
// *Cause: Reading the gateway init file generated an error.
// *Action: Check the gateway initialization file name to see that the
// gateway initialization file acctually exists.
// Check the ifile parameter to see that it points to the correct
// location.
//
28543, 00000, "Error initializing apply connection to non-Oracle system"
// *Cause: Attempt to initialize connection to non-Oracle for heterogeneous
// replication failed.
// *Action: Check if the listener used to connect to the gateway is up and is
// correctly configured. Make sure that the database link used has
// been configured correctly and, if a tnsnames alias has been used
// in the database link definition, make sure that the configuration
// of the entry in tnsnames.ora has been done correctly.
//
28544, 0000, "connect to agent failed, probable Net8 administration error"
// *Cause: Net8 reported a failure to make a RSLV connection or
// a protocol mode error when the Oracle server attempted
// to establish communication with a Heterogeneous Services
// agent or an external procedure agent. This usually is due
// to an administration error in setting up Net8 service definitions
// in TNSNAMES.ORA or LISTENER.ORA: A basic network connection
// is opened, but it connects to a program which does not use
// the appropriate protocol. This often is a sign that the
// connection goes to the wrong program.
// *Action: Check Net8 administration in the following ways:
// -- When using TNSNAMES.ORA or an Oracle Names server, make sure
// that the connection from the ORACLE server uses the correct
// service name or SID.
// -- Check LISTENER.ORA on the agent's host machine to assure that
// the service name or SID refers to the correct agent
// executable in its (PROGRAM=...) clause.
// -- Confirm in TNSNAMES.ORA or the equivalent service definition
// that sevice 'extproc_connection_data' does NOT contain
// (HS=), or that the service definition used by a
// Heterogeneous Services database link DOES contain (HS=).
//
28545, 0000, "error diagnosed by Net8 when connecting to an agent"
// *Cause: An attempt to call an external procedure or to issue SQL
// to a non-Oracle system on a Heterogeneous Services database link
// failed at connection initialization. The error diagnosed
// by Net8 NCR software is reported separately.
// *Action: Refer to the Net8 NCRO error message. If this isn't clear,
// check connection administrative setup in tnsnames.ora
// and listener.ora for the service associated with the
// Heterogeneous Services database link being used, or with
// 'extproc_connection_data' for an external procedure call.
//
28546, 0000, "connection initialization failed, probable Net8 admin error"
// *Cause: A failure occurred during initialization of a network connection
// from the Oracle server to a second process: The connection
// was completed but a disconnect occurred while trying to
// perform protocol-specific initialization, usually due to
// use of different network protocols by opposite sides
// of the connection. This usually is caused by incorrect
// Net8 administrative setup for database links or external
// procedure calls. The most frequent specific causes are:
// -- Database link setup for an Oracle-to-Oracle connection
// instead connects to a Heterogeneous Services agent
// or an external procedure agent.
// -- Database link setup for a Heterogeneous Services connection
// instead connects directly to an Oracle server.
// -- The extproc_connection_data definition in tnsnames.ora
// connects to an Oracle instance instead of an external
// procedure agent.
// -- Connect data for a Heterogeneous Services database link,
// usually defined in tnsnames.ora, does not specify (HS=).
// -- Connect data for an Oracle-to-Oracle database link,
// usually defined in tnsnames.ora, specifies (HS=).
// *Action: Check Net8 administration in the following ways:
// -- When using TNSNAMES.ORA or an Oracle Names server, make sure
// that the connection from the ORACLE server uses the correct
// service name or SID.
// -- Check LISTENER.ORA on the connection end point's host machine
// to assure that this service name or SID connects to the
// correct program.
// -- Confirm in TNSNAMES.ORA or the equivalent service definition
// that service 'extproc_connection_data' does NOT contain
// (HS=), or that the service definition used by a
// Heterogeneous Services database link DOES contain (HS=).
//
28547, 0000, "connection to server failed, probable Oracle Net admin error"
// *Cause: A failure occurred during initialization of a network connection
// from a client process to the Oracle server. The connection
// was completed but a disconnect occurred while trying to
// perform protocol-specific initialization, usually due to
// use of different network protocols by opposite sides
// of the connection. This usually is caused by incorrect
// Oracle Net administrative setup for database links or external
// procedure calls. The most frequent specific causes are:
// -- The connection uses a connect string which refers
// to a Heterogeneous Services agent instead of
// an Oracle server.
// -- The connection uses a connect string which includes
// an (HS=) specification.
// -- Hitting Ctrl+C before connection initialization is
// complete.
// -- Using DRCP on Windows with SQLNET.AUTHENTICATION_SERVICES
// set to NTS.
// -- Connection timeout due to SQLNET.INBOUND_CONNECT_TIMEOUT
// parameter when all shared servers are busy in
// shared server configuration.
// -- The character set of the database is not recognized by
// the client process, which may be caused by an incorrect
// or unnecessary setting of the ORA_NLS10 client environment
// variable or by a new or user-defined character set
// installed in the Oracle server and used for the database.
// *Action: Check Oracle Net administration in the following ways:
// -- When using TNSNAMES.ORA or an Oracle Names server, make sure
// that the client connection to the Oracle server uses
// the correct service name or SID.
// -- Check LISTENER.ORA on the connection end point's host machine
// to assure that this service name or SID refers
// to the correct server.
// -- Confirm in TNSNAMES.ORA or the equivalent service definition
// that the connect string does not contain (HS=).
// -- Set SQLNET.AUTHENTICATION_SERVICES to NONE when using DRCP
// on Windows.
// -- Verify the NLS configuration of the Oracle client
// process. Ensure that the database character set is
// supported by the Oracle client software. If necessary,
// upgrade the Oracle client software or install the missing
// user-defined character set.
//
28550, 00000, "pass-through SQL: cursor not found"
// *Cause: A value passed to a pass-through SQL function or procedure call
// as a cursor does not identify a currently open cursor.
// *Action: Use a cursor number returned by the pass-through SQL
// OPEN_CURSOR call.
//
28551, 00000, "pass-through SQL: SQL parse error"
// *Cause: A non-Oracle system rejected text supplied as a
// pass-through SQL statement.
// *Action: Ensure that the SQL supplied to the pass-through SQL
// PARSE call is legal for the non-Oracle system.
//
28552, 00000, "pass-through SQL: call flow error"
// *Cause: A pass-through SQL function was called in an invalid order.
// *Action: Correct program flow by changing the order of API calls
// to match the flow described in the manual.
//
28553, 00000, "pass-through SQL: invalid bind-variable position"
// *Cause: A pass-through SQL function referring to the position
// of a bind variable in the currently-parsed SQL statement
// supplied an invalid bind-variable position. Valid
// values are 1 through n, where n is the number of
// bind-variable place-holders in the SQL text.
// *Action: Verify that the bind-variable position parameter is in
// the correct range to represent a place-holder in the
// SQL text. Confirm that the SQL text uses the correct
// syntax for a bind-variable place-holder, as required
// by the non-Oracle system.
//
28554, 00000, "pass-through SQL: out of cursors"
// *Cause: The maximum number of open cursors has been exceeded.
// *Action: Close open cursors by using the pass-through SQL
// CLOSE_CURSOR function.
//
28555, 00000, "pass-through SQL: required parameter missing or NULL"
// *Cause: An attempt was made to pass a NULL value to a non-NULL parameter.
// *Action: Use a non-NULL value for the parameter.
//
28556, 00000, "authorization insufficient to access table"
// *Cause: A query attempted to access a table in the non-Oracle system
// that is either privileged or has privileged columns.
// *Action: Contact the DBA for the non-Oracle system. The DBA can
// grant permission to access the privileged table or columns.
//
28557, 00000, "unknown %s for database link to non-Oracle system"
// *Cause: When attempting to connect to a non-Oracle system
// through a Heterogeneous Services database link,
// the agent supporting this non-Oracle system failed to return
// FDS_CLASS_NAME and/or FDS_INST_NAME. ORACLE requires these
// names to configure the heterogeneous database link.
// *Action: Contact the DBA to check setup of the connection and
// the Heterogeneous Services agent.
//
28558, 00000, "HS_FDS_CONNECT_STRING undefined for non-Oracle system"
// *Cause: A database link to a non-Oracle system had no
// HS_FDS_CONNECT_STRING initialization parameter in the ORACLE
// server's data dictionary for Heterogeneous Services. Without
// this parameter, the connection could not be completed.
// *Action: Contact your DBA to verify correct setup of an
// HS_FDS_CONNECT_STRING entry in the ORACLE Heterogeneous Services
// data dictionary.
//
28559, 00000, "FDS_CLASS_NAME is %s, FDS_INST_NAME is %s"
// *Cause: An associated error was reported in another message, and this
// message supplies supplementary information to assist
// diagnosis of that error. FDS_CLASS_NAME and FDS_INST_NAME are used
// to access information in tables and views of the ORACLE data
// dictionary that direct operation of Heterogeneous Services on
// a database link to a non-Oracle data store.
// *Action: Use the FDS_CLASS_NAME and FDS_INST_NAME values
// to check ORACLE data dictionary contents when necessary
// to diagnose the cause of the associated error.
//
28560, 0000, "error in configuration of agent process"
// *Cause: An ORACLE server invoked a function not supported
// by the connected agent (Heterogeneous Services
// or external procedures). The most probable cause is
// incorrect Net8 setup, resulting in use of the wrong
// agent executable.
// *Action: Check Net8 administration in the following ways:
// -- When using TNSNAMES.ORA or an Oracle Names server, make sure
// that the connection from the ORACLE server uses the correct
// SID.
// -- Check LISTENER.ORA on the agent's host machine to assure that
// this SID refers to the correct agent executable in its
// (PROGRAM=...) clause.
28561, 00000, "unable to set date format on non-Oracle system"
// *Cause: Initialization of a Heterogeneous Services connection
// to set the date format to be used on the connected
// non-Oracle system.
// *Action: If the Oracle data dictionary supplies a value for
// the HS_NLS_DATE_FORMAT parameter, confirm that this value
// is formatted correctly by the rules of the non-Oracle system.
// Also check for additional information in log and trace
// files generated by the Heterogeneous Services agent.
28562, 00000, "Heterogeneous Services data truncation error"
// *Cause: A select operation was attempted with an insufficient data buffer
// to satisfy the request.
// *Action: Contact your DBA to verify whether your gateway initialization
// parameter HS_KEEP_REMOTE_COLUMN_SIZE is set appropriately based
// on your requirement. If it is, make sure the sizes of bind
// parameters are sufficient.
// If the problem persists, contact Oracle Support Services.
/
/ 28575 - 28600 reserved for untrusted and distributed external procedures
/
28575, 00000, "unable to open RPC connection to external procedure agent"
// *Cause: Initialization of a network connection to the extproc agent did
// not succeed. This problem can be caused by network problems,
// incorrect listener configuration, or incorrect transfer code.
// *Action: Check listener configuration in LISTENER.ORA and TNSNAMES.ORA, or
// check Oracle Names Server.
//
28576, 00000, "lost RPC connection to external procedure agent"
// *Cause: A fatal error occurred in either an RPC network connection,
// the extproc agent, or the invoked 3GL after communication had
// been established successfully.
// *Action: First check the 3GL code you are invoking; the most likely
// cause of this error is abnormal termination of the
// invoked "C" routine. If this is not the case, check for
// network problems. Correct the problem if you find it. If all
// components appear to be normal but the problem persists, the
// problem could be an internal logic error in the RPC transfer
// code. Contact your customer support representative.
//
28577, 00000, "argument %s of external procedure %s has unsupported datatype %s"
// *Cause: While transferring external procedure arguments to the agent,
// an unsupported datatype was detected.
// *Action: Check your documentation for the supported datatypes of external
// procedure arguments.
//
28578, 00000, "protocol error during callback from an external procedure"
// *Cause: An internal protocol error occurred while trying to execute a
// callback to the Oracle server from the user's 3GL routine.
// *Action: Contact Oracle customer support.
//
28579, 00000, "network error during callback from external procedure agent"
// *Cause: An internal network error occurred while trying to execute a
// callback to the Oracle server from the user's 3GL routine.
// *Action: Contact Oracle customer support.
//
28580, 00000, "recursive external procedures are not supported"
// *Cause: A callback from within a user's 3GL routine resulted in the
// invocation of another external procedure.
// *Action: Make sure that the SQL code executed in a callback does not directly
// call another external procedure, or indirectly results in another
// external procedure, such as triggers calling external
// procedures, PL/SQL procedures calling external procedures, etc.
//
28581, 00000, "protocol error while executing recursive external procedure"
// *Cause: An internal protocol error occurred while trying to execute an
// external procedure resulting from a callback in another external
// procedure.
// *Action: Contact Oracle customer support.
//
28582, 00000, "a direct connection to this agent is not allowed"
// *Cause: A user or a tool tried to establish a direct connection to either
// an external procedure agent or a Heterogeneous Services agent,
// for example: "SVRMGR> CONNECT SCOTT/TIGER@NETWORK_ALIAS". This type
// of connection is not allowed.
// *Action: When executing the CONNECT statement, make sure your database link
// or network alias is not pointing to a Heterogeneous Option agent or
// an external procedure agent.
//
28583, 00000, "remote references are not permitted during agent callbacks"
// *Cause: A Heterogeous Services agent issued a callback to the Oracle server
// which attemted to to access a remote system. This is not supported.
// *Action: Make sure that SQL code issued by Heterogeneous Services agents
// does not reference a database link.
//
28584, 00000, "heterogeneous apply internal error"
// *Cause: The apply slave process encountered an error while trying to
// apply changes through a gateway to a non-Oracle system.
// *Action: Make sure that the apply database link is correctly configured and
// that the gateway listener and the non-Oracle system are correctly
// set up and are up and running. If everything is configured correctly
// and the problem still occurs, contact Oracle customer support.
//
// errors 28590 - 28599 are reserved for the HS agent control utility
//
28590, 00000, "agent control utility: illegal or badly formed command"
// *Cause: The user has issued an unrecognized or syntactically incorrect
// command.
// *Action: Refer to documentation and correct the syntax of the command.
//
28591, 00000, "agent control utility: unable to access parameter file"
// *Cause: The agent control utility was unable to access its parameter
// file. This could be because it could not find its admin
// directory or because permissions on directory were not correctly
// set.
// *Action: The agent control utility puts its parameter file in either
// the directory pointed to by the environment variable AGTCTL_ADMIN
// or in the directory pointed to by the environment variable
// TNS_ADMIN. Make sure that at least one of these environment
// variables is set and that it points to a directory that the
// agent has access to.
//
28592, 00000, "agent control utility: agent SID not set"
// *Cause: The agent needs to know the value of the AGENT_SID parameter
// before it can process any commands. If it does not have a
// value for AGENT_SID then all commands will fail.
// *Action: Issue the command SET AGENT_SID <value> and then retry the
// command that failed.
//
28593, 00000, "agent control utility: command terminated with error"
// *Cause: An error occurred during the processing of the command. There
// could be several causes. A SET or an UNSET command could have
// been issued after the agent was started. This is illegal. The
// user may have attempted to start two agents with the same SID
// value or the user could have attempted to shutdown an agent
// that is no longer running.
// *Action: If the user wishes to issue a SET or an UNSET command, he should
// make sure the agent is shutdown first by issuing the SHUTDOWN
// command.
//
28594, 00000, "agent control utility: invalid parameter name"
// *Cause: The user tried to set or unset an invalid agent parameter.
// *Action: Refer to documentation and correct the parameter name.
//
28595, 00000, "Extproc agent : Invalid DLL Path"
// *Cause: The path of DLL supplied for the extproc execution is invalid.
// *Action: Check if the DLL path is set properly using the EXTPROC_DLLS
// environment variable.
//
28596, 00000, "Extproc agent : Invalid or disabled credential %s"
// *Cause: The credentail of the PL/SQL library supplied for the extproc execution is invalid.
// *Action: Check if the credentail of the PL/SQL library is valid and enabled.
//
// errors 28600 - 28620 are reserved for bitmap indexes
//
28601, 00000, "invalid [no]MINIMIZE option"
// *Cause: user didn't type this
// alter table <table_name> MINIMIZE RECORDS_PER_BLOCK
// or
// alter table <table_name> NOMINIMIZE RECORDS_PER_BLOCK
// *Action: reenter correct sql command
//
28602, 00000, "statement not permitted on tables containing bitmap indexes"
// *Cause: table has bitmap indexes and user is minimizing or
// nominimizing records_per_block
// *Action: drop all bitmap indexes before changing records_per_block
//
//
28603, 00000, "statement not permitted on empty tables"
// *Cause: table is empty and statement does not work on empty tables
// *Action: try statement after loading your data
//
28604, 00000, "table too fragmented to build bitmap index (%s,%s,%s)"
// *Cause: The table has one or more blocks that exceed the maximum number
// of rows expected when creating a bitmap index. This is probably
// due to deleted rows. The values in the message are:
// (data block address, slot number found, maximum slot allowed)
// *Action: Defragment the table or block(s). Use the values in the message
// to determine the FIRST block affected. (There may be others).
28605, 00000, "bitmap indexes cannot be reversed"
// *Cause: user tried to create reverse bitmap index
// *Action: don't do this; it is not supported
//
28606, 00000, "block too fragmented to build bitmap index (%s,%s)"
// *Cause: The block(s) exceed the maximum number of rows expected when
// creating a bitmap index. This is probably
// due to maximum slot allowed set too low.
// The values in the message are:
// (slot number found, maximum slot allowed)
// *Action: alter system flush shared_pool; update tab$ set spare1 = 8192
// where obj# = (select obj# from obj$ where NAME=<table_name> AND
// owner# = <table_owner>; commit;
28611, 00000, "bitmap index is corrupted - see trace file for diagnostics"
// *Cause: Validate Index detected bitmap corruption in its argument index
// *Action: Drop this bitmap index and create a new one.
//
//
/ 28650 - 28699 - Reserved for IOTs
//
28650, 00000, "Primary index on an IOT cannot be rebuilt"
// *Cause: An attempt is made to issue alter index rebuild on IOT-TOP
// *Action: Use Alter table MOVE to reorganize the table(IOT)
28651, 00000, "Primary index on IOTs can not be marked unusable"
// *Cause: An attempt is made to mark IOT-TOP unusable thru ALTER INDEX
// *Action: Remove the option UNUSABLE
//
28652, 00000, "overflow segment attributes cannot be specified"
// *Cause: During ALTER MOVE ONLINE of a index-organized table, the user
// attempted to enter one or more of the following options:
// OVERFLOW, PCTTHRESHOLD,INCLUDING.
// *Action: Remove the illegal option(s).
28653, 00000, "tables must both be index-organized"
// *Cause: Attempt to exchange a non IOT table/partition with a partition/table
// respectively
// *Action: Ensure that non-partitioned and partitioned tables are both
// index-organized.
28654, 00000, "table and partition not overflow compatible"
// *Cause: If one of the tables (partitioned/non-partitioned) has overflow
// data segment and the other one doesn't.
// *Action: Ensure that non-partitioned and partitioned tables both
// have overflow data segment or neither one does.
28655, 00000, "Alter table add overflow syntax error"
// *Cause: Syntax error
// *Action: Check the syntax.
28656, 00000, "incomplete attribute specification"
// *Cause: The attribute specification is not done for all partitions"
// *Action: Specify the storage attributes either for ALL partitions or NONE
// NLS_DO_NOT_TRANSLATE [28657,28657]
28657, 00000, "Allow IOT w/o overflow though overflow is required"
// *Cause: N/A
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY BY IMPORT CODE.
28658, 00000, "This operation is supported only for Index-Organized tables"
// *Cause: Attempt to perform some IOT specific operation on a non-IOT
// *Action: don't do this. This is not supported
28659, 00000, "COMPRESS must be specified at object level first"
// *Cause: Attempt to specify COMPRESS at partition level
// without first specifying at the table level
// *Action: Specify COMPRESS at table level. Use ALTER TABLE xxx
// MODIFY DEFAULT ATTRIBUTES COMPRESS ...
28660, 00000, "Partitioned Index-Organized table may not be MOVEd as a whole"
// *Cause: Attempt to MOVE partitioned IOT as a whole
// *Action: don't do this. This is not supported
28661, 00000, "Object already has COMPRESS clause specified"
// *Cause: Attempt to specify compress for iot/index which already
// has a compression clause.
// *Action: This is a 'create time only' attribute
28662, 00000, "IOT index and overflow segments must share the same LOGGING attribute"
// *Cause: Attempt to specify LOGGING for one segment and NOLOGGING for the other segment.
// *Action: don't do that
28663, 00000, "Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW"
// *Cause: Attempt to specify LOGGING for a Alter Table Add Overflow.
// *Action: don't do that
28664, 00000, "a partitioned table may not be coalesced as a whole"
// *Cause: User attempted to coalesce a partitioned IOT using
// ALTER TABLE COALESCE statement, which is illegal
// *Action: Coalesce the table a partition at a time (using
// ALTER TABLE MODIFY PARTITION COALESCE)
28665, 00000, "table and partition must have same compression attribute"
// *Cause: User attempted to EXCHANGE a compression enabled
// partition with a compression disabled table or vice versa
// OR the # of columns compressed is different for table and partition
// *Action: Make sure the compression attributes match
// If they don't, fix it using ALTER TABLE MOVE [PARTITION] COMPRESS
28666, 00000, "option not allowed for an index on UROWID column(s)"
// *Cause: User attempted to build a REVERSE or COMPRESSED or GLOBAL
// partitioned index on UROWID column(s)
// *Action: Build the index without these options
28667, 00000, "USING INDEX option not allowed for the primary key of an IOT"
// *Cause: User attempted to define storage attributes for the primary key
// index of an Index-Organized table with USING INDEX clause. All
// the storage attribute defined for the (IOT)table applies to the
// primary key index and a separate USING INDEX clause is not
// required.
// *Action: Remove the USING INDEX clause and specify all attributes directly
// for the table
28668, 00000, "cannot reference mapping table of an index-organized table"
// *Cause: An attempt to directly access the mapping table of an
// index-organized table
// *Action: Issue the statement against the parent index-organized table
// containing the specified mapping table.
28669, 00000, "bitmap index can not be created on an IOT with no mapping table"
// *Cause: User attempted to create a bitmap index on an index-organized
// table without a mapping table.
// *Action: Enable bitmap indexes on the Index-organized table by creating a
// mapping table using 'ALTER TABLE .. MOVE MAPPING TABLE'.
28670, 00000, "mapping table cannot be dropped due to an existing bitmap index"
// *Cause: User attempted to drop the mapping table with NOMAPPING option
// when the IOT has one or more bitmap indexed.
// *Action: Drop the bitmap index(es) before dropping the mapping table.
28671, 00000, "UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole"
// *Cause: User attempted to UPDATE BLOCK REFERENCES on a partitioned index
// using ALTER INDEX UPDATE BLOCK REFERENCES statement, which is
// illegal.
// *Action: Issue a partition level operation with
// ALTER INDEX .. PARTITION .. UPDATE BLOCK REFERENCES
28672, 00000, "UPDATE BLOCK REFERENCES may not be used on a global index"
// *Cause: User attempted to UPDATE BLOCK REFERENCES on a global partitioned
// or non-partitioned index. This feature is not supported for
// non-partitioned or global partitioned index on a partitioned IOT
// and a global partitioned index on a non-partitioned IOT.
// *Action: Use online index [partition] rebuild to fix the block references
28673, 00000, "Merge operation not allowed on an index-organized table"
// *Cause: User attempted merge operation on an index-organized table. Merge
// is not supported on a IOT .
// *Action: Use updates and inserts on index-organized table .
28674, 00000, "cannot reference transient index-organized table"
// *Cause: An attempt was made to directly access a transient table created
// created on behalf of a index-organized table partition maintenance
// operation.
// *Action: Issue the statement against the associated permanent
// index-organized table.
/
/ 28700-28799 RESERVED FOR CODE-BASED ACCESS CONTROL
/
28700, 00000, "Only roles can be attached to or detached from program units."
// *Cause: An attempt was made to grant object privileges or system privileges
// to program units.
// *Action: Grant the privileges to a role first, and then grant the role to
// the program units.
/
28701, 00000, "Keyword PROCEDURE, FUNCTION, or PACKAGE is either missing or not correct."
// *Cause: The keyword PROCEDURE, FUNCTION, or PACKAGE was either missing
// before the program unit, or it was not consistent with the type of
// the program unit.
// *Action: Include the correct keyword PROCEDURE, FUNCTION or PACKAGE right
// before each program unit according to its type.
/
28702, 00000, "Program unit %s is not owned by the grantor."
// *Cause: An attempt was made to attach roles to or detach roles from one or
// more program units by someone other than the owner or SYS. Only a
// program unit owner or SYS can attach roles to or detach roles from
// a program unit.
// *Action: Specify only the program units owned by the grantor in the command.
/
28703, 00000, "Only regular database roles can be attached to or detached from program units."
// *Cause: An attempt was made to attach non-supported types of
// roles to or detach them from program units. Application roles,
// secure application roles, external roles, global roles, and
// light-weight roles cannot be attached to or detached from program
// units.
// *Action: Remove any application role, secure application role, external role,
// global role, and light-weight role from the command.
/
28704, 00000, "Role %s is not directly granted to the owner of the program units."
// *Cause: An attempt was made to attach roles that were not directly granted
// to the owner of the program units. The roles must be granted to the
// owner directly in order to attach them to the owner's program units.
// *Action: Grant the role to the owner of the program unit first.
/
28705, 00000, "The grantor does not have privileges to grant the role %s to the program units."
// *Cause: Privileges to grant a role to a program unit were insufficient.
// The grantor must have the GRANT ANY ROLE privilege or the ADMIN
// option or the DELEGATE option for the role to do the operation.
// *Action: Obtain the required privilege and retry.
/
28706, 00000, "duplicate program unit %s found in list"
// *Cause: A duplicate program unit was found in the GRANTEE clause.
// *Action: Specify each program unit only once.
/
28707, 00000, "Reserved word ALL was used with roles in the REVOKE command to detach roles from program units."
// *Cause: An attempt was made to use reserved word ALL jointly with roles
// in a REVOKE command to detach roles from program units.
// *Action: Do not specify roles in the privilege clause except for the
// reserved word ALL.
/
28708, 00000, "More than %s roles were attached to the program unit."
// *Cause: Too many roles were currently attached to the program unit.
// *Action: Detach some roles from the program unit.
/
28709, 00000, "Roles with DELEGATE option can only be granted to users."
// *Cause: One of the grantees was not a user when trying to grant roles with the DELEGATE option.
// *Action: Verify that the grantees are users and try the operation again.
/
28714, 00000, "OCI_BATCH_ERRORS or OCI_RETURN_ROW_COUNT_ARRAY mode can only be specified for INSERT, UPDATE, DELETE or MERGE statement."
// *Cause: OCI_BATCH_ERRORS or OCI_RETURN_ROW_COUNT_ARRAY mode was specified
// in a statement which is not INSERT, UPDATE, DELETE or MERGE.
// *Action: Specify OCI_BATCH_ERRORS or OCI_RETURN_ROW_COUNT_ARRAY only for
// INSERT, UPDATE, DELETE or MERGE statements.
28715, 00000, "OCI_STMT_SCROLLABLE_READONLY can only be specified for SELECT statements."
// *Cause: OCI_STMT_SCROLLABLE_READONLY mode was specified for a non-SELECT statement.
// *Action: Specify OCI_SCROLLABLE_READONLY only for SELECT statements.
28716, 0000, "Invalid buffer or buffer size for OCIServerRelease2() \n"
//* Cause: A zero length or null buffer was specified for the OCIServerRelease2().
//* Action: Specify a valid buffer and length.
/ $Header: security_src/mesg/nze1us.msg /main/22 2012/03/08 18:53:43 tnallath Exp $
/ $Header: security_src/mesg/nze1us.msg /main/22 2012/03/08 18:53:43 tnallath Exp $
/
/ Copyright (c) 1997, 1999, 2000, 2001 by Oracle Corporation
/ NAME
/ nzeus.msg - Network Zecurity Error messages - american (US) language
/ DESCRIPTION
/ Contains error messages for the Oracle Security Server
/ RETURNS
/ None.
/
/ NOTES
/ MODIFIED (MM/DD/YY)
/ tnallath 02/15/12 - nzupg12: enable fips
/ bhmathur 03/02/05 - Bug 2220658 Fix
/ rchahal 11/23/04 - changes suggested by errors_us
/ rchahal 10/11/04 - pkcs11 enhancement messages
/ skalyana 08/22/03 - Error message changes
/ skalyana 05/28/03 - Errors to be documented
/ rchahal 08/14/03 - crl error messages
/ skalyana 03/07/03 - Add messages for FIPS errors
/ skalyana 12/06/02 - Ad SSL Plus 4.2 error messages
/ supriya 10/30/01 - Fix for bug # 1691606
/ supriya 10/08/01 - Fix for bug # 1691606
/ vle 02/16/01 - fix err mesg for 29002,3
/ vle 02/09/01 - add nz mesg
/ ppovinec 02/08/01 - Net8 --> Oracle Net rename.
/ rturlapa 03/29/00 - Added Entrust error message.
/ rwessman 07/06/99 - Added SSL error messages
/ sdange 03/13/97 - ERROR NOT USER-VISIBLE
/ rwessman 03/06/97 - Corrected error numbers.
/
28750, 00000, "unknown error"
// *Cause: An Oracle Security Server error of an unspecified type occurred.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28751, 00000, "memory allocation failure"
// *Cause: The allocation of memory failed due to insufficient system memory.
// *Action: Terminate other processes to free up memory or add memory to the
// system.
/
28752, 00000, "data source initialization failure"
// *Cause: A data source failed to initialize. Frequently, this error is caused
// by insufficient system resources.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28753, 00000, "failure to terminate use of data source"
// *Cause: The system failed to terminate its use of a data source. This error may
// have been caused by memory or disk corruption, among other things.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28754, 00000, "object storage failure"
// *Cause: Error not user-visible.
// *Action:
// *Document: NO
/
28755, 00000, "object retrieval failure"
// *Cause: The system failed to retrieve information from a file or a
// database.
// *Action: Check if the data source exists, or check to ensure that the correct
// information exists.
/
28756, 00000, "callback failure to allocate memory"
// *Cause: A function supplied by the caller failed to allocate memory. This error could
// have been caused by system memory exhaustion.
// *Action: Terminate other processes to free up memory or add memory to the system.
/
28757, 00000, "system attempt to allocate 0 bytes of memory"
// *Cause: The system attempted to allocate 0 bytes of memory because there was no
// available memory left to allocate. This error could have been caused by insufficient system
// memory.
// *Action: Terminate other processes to free up memory or add memory to the system.
/
28758, 00000, "memory release failure"
// *Cause: The release of a memory fragment failed. This may be due to
// memory corruption either within the application or in the
// Oracle Security Server library.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28759, 00000, "failure to open file"
// *Cause: The system could not open the specified file.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28760, 00000, "list creation failure"
// *Cause: Error not user-visible.
// *Action:
// *Document: NO
/
28761, 00000, "element creation failure"
// *Cause: Error not user-visible.
// *Action:
// *Document: NO
/
28762, 00000, "failure to add element"
// *Cause: Error not user-visible.
// *Document: NO
// *Action:
/
28763, 00000, "Invalid parameter type found in configuration file."
// *Cause: A parameter in the sqlnet.ora file may have been specified incorrectly.
// *Action: Check the sqlnet.ora file for this parameter value.
/
28764, 00000, "failure to retrieve a configuration parameter"
// *Cause: The system failed to retrieve a configuration parameter from the sqlnet.ora file.
// This error may have occurred because a necessary configuration parameter was
// not specified in the sqlnet.ora file.
// *Action: Supply the needed configuration parameter in the sqlnet.ora file.
/
28765, 00000, "Data method list does not exist."
// *Cause: Error not user-visible.
// *Action:
// *Document: NO
/
28766, 00000, "failure to terminate use of data source"
// *Cause: The system failed to terminate its use of a data source. This error may
// have been caused by memory or disk corruption, or a system error.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28767, 00000, "invalid version number"
// *Cause: Version number of the wallet was incorrect. A corrupt wallet or
// an incompatible wallet was provided.
// *Action: Ensure that proper wallet is being used.
/
28768, 00000, "bad magic number"
// *Cause: An invalid magic number was specified in a data file. This could have been
// caused by a corrupted disk or by some other process overwriting the file.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28769, 00000, "Specified method does not exist."
// *Cause: The data access method that was specified in the configuration file is not
// supported.
// *Action: Specify a supported method. Consult the Oracle Security Server
// documentation to determine the supported types.
/
28770, 00000, "Data source is already initialized."
// *Cause: The caller attempted to initialize a data source which was already
// initialized.
// *Action: This is a programming error. An application should not attempt to
// initialize a data source more than once.
/
28771, 00000, "Data source is not yet initialized."
// *Cause: The caller attempted to use a data source which had not yet been
// initialized.
// *Action: This is a programming error. The application must always initialize
// the data source before it can be used.
/
28772, 00000, "invalid file ID"
// *Cause: Error not user-visible.
// *Action:
// *Document: NO
/
28773, 00000, "failure to write magic and version numbers"
// *Cause: Both the magic and version numbers failed to write. This usually
// occurs because of insufficient disk space.
// *Action: Delete unnecessary files to free up disk space or add disk space
// to the system.
/
28774, 00000, "file cannot write to disk"
// *Cause: The output of a file failed. This error usually occurs because of
// insufficient disk space.
// *Action: Delete unnecessary files to free up disk space or add disk space
// to the system.
/
28775, 00000, "file cannot close"
// *Cause: Failed to close a file which is used by a data access method.
// This error usually indicates memory corruption or a system error.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28776, 00000, "Output buffer supplied is too small."
// *Cause: The data returned by a function was too large for the
// supplied buffer.
// *Action: Call the routine again with a larger buffer.
/
28777,00000, "binding creation failure"
// *Cause: Failed to create a binding for use in the parsing of a parameter
// value. This error can be caused by the parameter value
// being in an incorrect format, such as a right parenthesis was not
// supplied where expected, or due to insufficient system memory.
// *Action: Make sure that the parameter is specified in the correct format.
// If the format is correct, free up system memory by terminating
// processes or adding more memory.
/
28778, 00000, "Configuration parameter is not specified in the proper format."
// *Cause: The configuration parameter was not specified in the proper format.
// *Action: Consult the Oracle Security Server documentation for a description
// of the proper format for this parameter.
/
28779, 00000, "no data access method specified in parameter"
// *Cause: No method for data access was specified in the parameter value.
// *Action: Specify a method for data access in the parameter. Consult the
// Oracle Security Server documentation for the supported data access
// methods for this data type.
/
28780, 00000, "invalid data access method specified by the parameter"
// *Cause: The data access method specified by the parameter value is not
// supported.
// *Action: Specify a supported data access method. Consult the Oracle Security Server
// documentation for the supported data access methods for this data
// data type.
/
28781, 00000, "No data for the access method is specified in the parameter."
// *Cause: No data was specified in the parameter for use with the specified
// access method.
// *Action: Consult the Oracle Security Server documentation for the data
// that must be specified for the access method.
/
28782, 00000, "data source is not allocated"
// *Cause: No memory was allocated for a data source.
// *Action: Ensure that the application calls in the data source initialization
// function.
/
28783, 00000, "invalid parameter"
// *Cause: There was no match for the parameter name that was used in the
// configuration file.
// *Action: Check your sqlnet.ora file for the correct parameter name.
/
28784, 00000, "file name translation failure"
// *Cause: The translation of a file name from Oracle format to native format has
// failed.
// *Action: Specify a correct file name. Consult your Oracle documentation for the
// correct file name format.
/
28785, 00000, "parameter does not exist"
// *Cause: A necessary configuration parameter was not found in the parameter file.
// *Action: Supply the required parameter.
/
28786, 00000, "decryption of encrypted private key failure"
// *Cause: An incorrect password was used to decrypt an encrypted private key.
// *Action: Enter the correct password.
/
28787, 00000, "private key encryption failure"
// *Cause: This may have been caused by an error in the mkwallet parameter of the
// sqlnet.ora file.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28788, 00000, "user provided invalid information, or an unknown error"
// *Cause: User may have responded to a prompt with unexpected input, or an
// unknown error occurred.
// *Action: Enter correct input, or enable tracing to check the trace file for
// errors.
/
28789, 00000, "name type not found"
// *Cause: Error not user-visible.
// *Action:
// *Document: NO
/
28790, 00000, "NLS string open failure"
// *Cause: The opening of a string for use by the NLS subsystem failed.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28791, 00000, "certificate verification failure"
// *Cause: Verification of the certificate, which the user supplied, failed.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28792, 00000, "PL/SQL operation failure"
// *Cause: A PL/SQL operation attempted by the Oracle Security Server failed.
// *Action: This is an internal error. Enable tracing and try the operation
// again. Contact Oracle customer support for assistance.
// *Document: NO
/
28793, 00000, "variable bind failure"
// *Cause: Error not user-visible.
// *Action:
// *Document: NO
/
28794, 00000, "data type attribute did not initialize"
// *Cause: The initialization of the attribute data type failed. This error may be
// due to insufficient system resources.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28795, 00000, "data type attribute did not terminate"
// *Cause: The termination of the use of the attribute data type subsystem
// failed.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28796, 00000, "access method is not supported"
// *Cause: The method specified to access data is not supported.
// *Action: Use a supported access method. Consult your Oracle documentation to determine
// which access methods are supported.
/
28797, 00000, "invalid key data type"
// *Cause: The type specified for a key is not supported.
// *Action: Correct the key type. Consult your Oracle documentation to determine which
// key types are supported.
/
28798, 00000, "Number of sub-keys application passes to bind does not match that in the key."
// *Cause: The number of keys passed by the application to bind does not match
// the number used to create the key.
// *Action: This is an internal programming exception. Contact Oracle customer
// support.
// *Document: NO
/
28799, 00000, "failure to allocate shared memory"
// *Cause: The allocation of shared memory for use in operations involving
// the shared server failed. This error was probably due to
// insufficient memory heap supplied by the Oracle server.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
// *Document: NO
/
28800, 00000, "data source failed to open"
// *Cause: A data source (a file or a database) failed to open.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28801, 00000, "invalid object type"
// *Cause: Error not user-visible.
// *Action:
// *Document: NO
/
28802, 00000, "invalid mode or data source in configuration file"
// *Cause: An invalid mode or data source has been specified in the
// configuration file (sqlnet.ora).
// *Action: Check the method parameter in the sqlnet.ora file.
// If the parameter value is correct, then enable tracing to
// determine the exact error.
/
28803, 00000, "I/O operation failure"
// *Cause: The system or application failed to access a data source
// (file or database).
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28804, 00000, "Data source cannot close."
// *Cause: The data source, which could be either a file or a database),
// failed to close.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28805, 00000, "Cannot retrieve information from the data source."
// *Cause: The system or application failed to retrieve information from
// the data source (file or database).
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28806, 00000, "Cannot write to the data source."
// *Cause: The system or application failed to write to the data source
// (file or database).
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28807, 00000, "Cannot update the data source."
// *Cause: The system or application failed to update the data source (file
// or database).
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28808, 00000, "Cannot retrieve method information from the configuration file."
// *Cause: The system or application failed to retrieve method
// information from the sqlnet.ora configuration file.
// *Action: Check the method configuration parameters in the sqlnet.ora file.
// If the method configuration parameters are correct, then enable
// tracing to determine the exact error.
/
28809, 00000, "Cannot delete information from the data source."
// *Cause: The system or application failed to delete information from the data
// source (file or database).
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28810, 00000, "Cannot create key descriptor."
// *Cause: The system failed to create a key descriptor.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28811, 00000, "invalid access descriptor"
// *Cause: Error not user-visible.
// *Action:
// *Document: NO
/
28812, 00000, "record operation failure"
// *Cause: Error not user-visible.
// *Action:
// *Document: NO
/
28813, 00000, "invalid record type"
// *Cause: Error not user-visible.
// *Action:
// *Document: NO
/
28814, 00000, "Cannot convert a number in Oracle format to native format."
// *Cause: Failed to convert a number from Oracle format to native format.
// *Action: This is an internal programming exception. Enable tracing to try
// and reproduce the problem. Contact Oracle customer support and
// supply the trace file.
/
28815, 00000, "Cannot convert a number in native format to Oracle format."
// *Cause: Failed to convert a number from native format to Oracle portable
// format failed.
// *Action: This is an internal programming exception. Enable tracing to try
// and reproduce the problem. Contact Oracle customer support and
// supply the trace file.
/
28816, 00000, "No password provided for a PL/SQL function."
// *Cause: A required password was not passed to a PL/SQL function.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28817, 00000, "PL/SQL function returned an error."
// *Cause: A PL/SQL function returned an error unexpectedly.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28818, 00000, "No package context provided."
// *Cause: The context that holds the state of the security package was not
// passed to a function or procedure that was expecting it.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
/
28819, 00000, "No distinguished name provided."
// *Cause: The user's distinguished name was not provided to a PL/SQL
// function or procedure.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28820, 00000, "Signature or decryption/encryption state is not provided."
// *Cause: The state of either a signature or decryption/encryption was not
// passed to a PL/SQL function or procedure.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28821, 00000, "No input buffer provided."
// *Cause: A PL/SQL function or procedure was not passed an expected buffer.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28822, 00000, "Required seed is not specified."
// *Cause: No seed was specified to the PL/SQL seed initialization function.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28823, 00000, "Number of random bytes to generate is not specified."
// *Cause: The number of random bytes to generate was not specified to the
// PL/SQL random number generator.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28824, 00000, "invalid encryption/decryption/signature state passed"
// *Cause: An invalid state was passed to a PL/SQL encryption, decryption, or
// signature procedure or function.
// *Action: Specify a correct state value.
// *Document: NO
/
28825, 00000, "No cryptographic engine function specified."
// *Cause: No function was specified for the cryptographic engine.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28826, 00000, "invalid cryptographic engine function passed"
// *Cause: An incorrect cryptographic engine function was passed to a PL/SQL
// function or procedure.
// *Action: Specify a correct engine function.
// *Document: NO
/
28827, 00000, "invalid cipher type passed"
// *Cause: An incorrect cipher type was passed to a PL/SQL function or
// procedure.
// *Action: Specify a correct cipher type.
// *Document: NO
/
28828, 00000, "invalid identity type passed"
// *Cause: An incorrect identity type was passed to a PL/SQL function or
// procedure.
// *Action: Specify a correct identity type.
// *Document: NO
/
28829, 00000, "no cipher type specified"
// *Cause: No cipher type was passed to a PL/SQL function or procedure.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28830, 00000, "no identity type specified"
// *Cause: No identity type was passed to a PL/SQL function or procedure.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28831, 00000, "no data unit format"
// *Cause: No data unit format was passed to a PL/SQL function or procedure.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28832, 00000, "invalid data unit format"
// *Cause: An incorrect data unit format was passed to a PL/SQL function or
// procedure.
// *Action: Specify a data unit format.
// *Document: NO
/
28833, 00000, "inadequate information provided"
// *Cause: Inadequate information, which usually is in the form of parameters,
// has been provided to a PL/SQL function.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28834, 00000, "Buffer is too small."
// *Cause: The buffer provided by PL/SQL to an Oracle Security Server toolkit
// function is too small for the data to be returned.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28835, 00000, "Identity descriptor is not present or is too small."
// *Cause: An identity descriptor, which is passed to a PL/SQL function or descriptor,
// was not provided or was not the correct size.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28836, 00000, "Wallet is not open."
// *Cause: The wallet to be used has not yet been opened.
// *Action: Call the function that opens the wallet.
/
28837, 00000, "no wallet descriptor"
// *Cause: No wallet descriptor was specified to a PL/SQL function or
// procedure.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28838, 00000, "no identity descriptor"
// *Cause: No identity descriptor was specified to a PL/SQL function or
// procedure.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28839, 00000, "no persona descriptor"
// *Cause: No persona descriptor was specified to a PL/SQL function or
// procedure.
// *Action: This is an internal error. Enable tracing to find more
// information. Contact Oracle customer support if needed.
// *Document: NO
/
28840, 00000, "Wallet is already open."
// *Cause: An attempt was made to open a wallet that was already open.
// *Action: This is a programming error. A wallet should only be opened once.
/
28841, 00000, "Operation is not supported."
// *Cause: An attempt was made to perform an operation that is not supported.
// *Action: This is a programming error. Please refer to Oracle documentation
// to determine which operations are supported.
/
28842, 00000, "Incorrect file permissions"
// *Cause: The subject file did not have the correct permissions for the operation.
// *Action: Ensure that the file permissions allow the current operation.
/
28843, 00000, "Operating system error while creating/opening file"
// *Cause: An operating system dependent error occurred while trying to create/
// open the file or while trying to set the appropriate permissions on
// the file.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28844, 00000, "No wallet present"
// *Cause: There was no wallet in the location specified.
// *Action: Check to ensure that the wallet is in the correct directory
// location.
/
28845, 00000, "No certificate"
// *Cause: Either there is no certificate or the system cannot find it.
// *Action: Check to ensure that the certificate is in the specified wallet.
/
28846, 00000, "No private key"
// *Cause: Either there is no private key or the system cannot find it.
// *Action: Check to ensure that the private key is in the specified wallet.
/
28847, 00000, "No clear private key file"
// *Cause: Failed to retrieve private key from SSO wallet
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28848, 00000, "No encrypted private key file"
// *Cause: Failed to retrieve private key from the wallet
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28849, 00000, "No Trustpoints"
// *Cause: The wallet does not have any trusted certificates
// *Action: Ensure that the wallet/keystore has trusted certificates.
/
28850, 00000, "No clear trustpoint file"
// *Cause:
// *Action:
// *Document: NO
/
28851, 00000, "No encrypted trustpoint file"
// *Cause:
// *Action:
// *Document: NO
/
28852, 00000, "Bad password"
// *Cause: The password created for an obfuscated wallet exceeds the maximum
// password length limit.
// *Document: NO
// *Action:
/
28853, 00000, "Initialization failure"
// *Cause: Either initialization or module loading has failed.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28854, 00000, "Memory allocation failure"
// *Cause: The allocation of memory failed due to insufficient system memory.
// *Action: Terminate other processes to free up memory or add memory to the
// system.
/
28855, 00000, "Unsupported SSL operation"
// *Cause: An unsupported operation was attempted, for example, an attempt was
// made to select a mode of operation that is not allowed.
// *Action: Refer to the SSL chapter in the product's documentation.
//
/
28856, 00000, "Buffer overflow error"
// *Cause: A buffer overflow error occurred during SSL handshake.
// *Action: This error is not normally visible to the user. Enable tracing
// and attempt the connection again. Then contact Oracle customer
// support with the trace output.
// *Document: NO
/
28857, 00000, "Unknown SSL error"
// *Cause: An unknown SSL error occurred.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28858, 00000, "SSL protocol error"
// *Cause: An error occurred while negotiating the SSL handshake between two processes.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28859, 00000, "SSL negotiation failure"
// *Cause: An error occurred during negotiation between two processes
// as part of the SSL protocol. This error will occur if the two sides to
// the connection do not support a common cipher suite.
// *Action: Configure each process so they support a common cipher suite.
// Then attempt the connection again. If error occurs again, enable
// tracing and retry the connection. Then contact Oracle customer
// support with the trace output.
/
28860, 00000, "Fatal SSL error"
// *Cause: An error occurred during the SSL connection to the peer. It is likely
// that this side sent data which the peer rejected.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
28861, 00000, "SSL connection would block"
// *Cause: This error is informational. It should never be communicated
// to the user.
// *Action: Enable tracing and retry the connection to determine the exact
// cause of the error. Contact Oracle customer support if needed.
/
28862, 00000, "SSL connection failed"
// *Cause: This error occurred because the peer closed the connection.
// *Action: Enable tracing on both sides and examine the trace output.
// Contact Oracle Customer support with the trace output.
/
28863, 00000, "SSL session not found"
// *Cause: This error is informational. It indicates that a specified
// session does not exist.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
28864, 00000, "SSL connection closed gracefully"
// *Cause: This error is informational. It indicates that the connection
// closed without error.
// *Action: This error is not normally visible to the user. Enable tracing
// and retry the connection. If the error persists, contact Oracle
// customer support.
/
28865, 00000, "SSL connection closed"
// *Cause: The SSL connection closed because of an error in the underlying
// transport or because the peer process quit unexpectedly.
// *Action: Enable tracing and retry the connection. The trace output
// should indicate how the failure occurred.
/
28866, 00000, "Invalid peer certificate encoding"
// *Cause: A field from a certificate in the peer's certificate chain could not be
// recognized.
// *Action: Refer to Oracle Wallet Manager documentation to find out how to obtain the
// peer's certificate. Then contact Oracle customer support with the peer's
// certificate chain.
/
28867, 00000, "Integer value is too big."
// *Cause: The certificate presented had an integer field whose value was
// too large.
// *Action: Refer to Oracle Wallet Manager documentation to find out how to obtain the
// peer's certificate. Then contact Oracle customer support with the peer's
// certificate chain.
/
28868, 00000, "Peer certificate chain check failed."
// *Cause: The check of the certificate list presented by the peer
// failed. Possible causes include:
// 1. the expiration of one of the certificates;
// 2. a certificate authority in a certificate was not recognized as
// a trust point;
// 3. the signature in a certificate could not be verified.
// *Action: Refer to Oracle Wallet Manager documentation to find out how to open
// your wallet and ensure that:
// 1. all of the certificates installed in your wallet are current
// 2. a certificate authority's certificate from your peer's certificate chain
// is added as a trusted certificate in your wallet
/
28869, 00000, "Peer's certificate is expired."
// *Cause: The certificate being used to authenticate a client or server
// has expired.
// *Action: Obtain a new certificate, which is unexpired, and attempt the
// connection again.
/
28870, 00000, "Name comparison failure"
// *Cause: A comparison of the names contained in two certificates failed.
// *Action: This error is not normally visible to the user. Enable tracing
// and retry the connection. If the error persists, contact Oracle
// customer support.
/
28871, 00000, "Peer certificate chain is incomplete."
// *Cause: The peer certificate chain presented was incomplete because it did not
// end with a self-signed root certificate.
// *Action: Refer to Oracle Wallet Manager documentation to find out how to open
// your wallet and ensure that:
// 1. the certificate authority's root certificate is self-signed.
// 2. a certificate authority's certificate from your peer's certificate chain
// is added as a trusted certificate in your wallet
/
28872, 00000, "Invalid peer certificate format"
// *Cause: The peer certificate does not conform to the X.509v3 standard.
// *Action: Refer to Oracle Wallet Manager documentation to find out how to get the
// peer certificate. Then contact Oracle customer support with the peer's
// certificate.
/
28873, 00000, "Invalid parameter"
// *Cause: A function was presented with a null parameter.
// *Action: This error is not normally visible to the user. Enable tracing
// and retry the connection. If the error persists, contact
// Oracle customer support.
// *Document: NO
/
28874, 00000, "SSL: I/O closed - override goodbye kiss"
// *Cause: This error is informational. It indicates that the connection closed
// without error.
// *Action: This error is not normally visible to the user. Enable tracing
// and retry the connection. If the error persists, contact
// Oracle customer support.
/
28875, 00000, "SSL: use server-gated cryptographic suites"
// *Cause: This is used as a internal status indicator and not really
// an error.
// *Action: This message is not normally visible to the user. Enable tracing
// and retry the connection. If the error persists, contact
// Oracle customer support.
/
28876, 00000, "Internet Explorer SGC Error"
// *Cause: An error occurred when processing a certificate sent from
// Microsoft Internet Explorer.
// *Action: This error is not normally visible to the user. Enable tracing
// and retry the connection. If the error persists, contact
// Oracle customer support.
/
// 28877, 00000, "UNUSED"
// *Cause:
//
// *Action:
//
/
// 28878, 00000, "UNUSED"
// *Cause:
//
// *Action:
//
/
28879, 00000, "no protocol side set"
// *Cause: An application attempted to provide credentials to an SSL
// connection but had not previously stated whether the process
// was a client or a server.
// *Action: This error is not normally visible to the user. Enable tracing
// and retry the connection. If the error persists, contact
// Oracle customer support.
/
// 28880, 00000, "UNUSED"
// *Cause:
// *Action:
// *Document: NO
/
// 28881, 00000, "UNUSED"
// *Cause:
// *Action:
// *Document: NO
/
28882, 00000, "UNUSED"
// *Cause:
// *Action:
// *Document: NO
/
28883, 00000, "UNUSED"
// *Cause:
// *Action:
// *Document: NO
/
28884, 00000, "invalid cipher suite"
// *Cause: An invalid cipher suite string has been specified in the
// product's configuration file.
// *Action: Refer to the product documentation for information about
// supported cipher suites.
/
28885, 00000, "No certificate with the required key usage found."
// *Cause: Certificate not created with the appropriate X509v3 key usage
// extension.
// *Action: Refer to Oracle Wallet Manager documentation to find out the
// supported key usages.
/
28890, 00000, "Entrust Login Failed"
// *Cause: An application failed to log in to an Entrust Profile.
// Possible causes include:
// 1. Entrust Admin/Authority was not online.
// 2. Invalid password for Entrust profile was specified.
// 3. Invalid path to Entrust profile was specified
// 4. Invalid Entrust initialization file was specified.
// 5. Entrust Server Login program was not executed (server-side only).
// *Action: Make sure that:
// 1. Entrust Authority is online;
// 2. Password for Entrust profile is specified correctly;
// 3. Path to Entrust profile is specified correctly;
// 4. A valid Entrust initialization file is provided;
// 5. Entrust Server Login program is run before the database startup.
// For more information, enable tracing and examine the trace output
// to get exact the Entrust failure codes.
/
29000, 00000, "Certificate not installed"
// *Cause: Trying to delete a certificate which has not been installed.
// *Action: Refer to the Oracle Wallet Manager documentation for information
// about delete option.
/
29001, 00000, "UNUSED"
// *Cause:
// *Action:
// *Document: NO
/
29002, 00000, "SSL transport detected invalid or obsolete server certificate."
// *Cause: The client detected a mismatch between the server's distinguished name
// specified on the server's certificate and the server's SID or service name.
// *Action: Refer to the SSL chapter in Oracle Advanced Security Administrator's Guide
// for information about enabling server distinguished name matching.
// Contact your administrator to perform the appropriate action.
/
29003, 00000, "SSL transport detected mismatched server certificate."
// *Cause: The client detected a mismatch between the server's distinguished name
// specified on the server's certificate and the server's SID or service name.
// *Action: Refer to the SSL chapter in Oracle Advanced Security Administrator's Guide
// for information about enabling server distinguished name matching.
// Contact your administrator to perform the appropriate action.
/
29004, 00000, "Callback Failure"
// *Cause: The alert callback returns this error; it is not fatal.
// *Document: NO
// *Action:
/
29005, 00000, "The certificate is invalid."
// *Cause: The peer certificate encoding is invalid when using SSL 2.0.
// *Action: Refer to Oracle Wallet Manager documentation to find out how to obtain the
// peer's certificate. Then contact Oracle customer support with the peer's
// certificate chain.
/
29006, 00000, "The certificate request message is invalid when using SSL 2.0."
// *Cause: There is an error processing the SSL 2.0 REQUEST-CERTIFICATE message.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29007, 00000, "Bad Clear Key Length when using SSL 2.0"
// *Cause: The clear key length of an SSL 2.0 Client Master key handshake message
// is invalid.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29008, 00000, "Bad DH Param key length"
// *Cause: The length of the Diffie-Hellman params exceeds export restrictions.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29009, 00000, "Bad encrypted key length when using SSL 2.0"
// *Cause: The encrypted key length of an SSL 2.0 Client Master key handshake
// message is invalid.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29010, 00000, "Export key length does not meet export restrictions."
// *Cause: The server sent a ServerKeyExchange message with an export key which
// does not meet export restrictions. For RSA, the export key must
// be exactly 512 bits.
// *Action: Obtain a certificate with the appropriate key length.
/
29011, 00000, "Finished message is incorrect."
// *Cause: The FINISHED message data verification failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29012, 00000, "Bad key argument length when using SSL 2.0"
// *Cause: The key argument length of an SSL 2.0 Client Master Key handshake message
// is invalid.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29013, 00000, "SSL MAC verification failure"
// *Cause: Verification of SSL Record MAC failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29014, 00000, "Maximum fragment length extension is incorrect."
// *Cause: The maximum fragment length extension specified is incorrect.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29015, 00000, "incorrect message length"
// *Cause: The message length is not correct.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29016, 00000, "inadequate PKCS1 message padding"
// *Cause: The message was not properly padded before encryption.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29017, 00000, "The premaster secret length is incorrect."
// *Cause: The premaster secret sent by the peer has an incorrect length.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29018, 00000, "The premaster secret contains an incorrect version number."
// *Cause: The premaster secret must contain the same version number as the ClientHello.
// The version sent by the client was incorrect.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29019, 00000, "The protocol version is incorrect."
// *Cause: There is a protocol version mismatch between the two peers.
// *Action: Specify the correct protocol version in the product's configuration
// file.
/
29020, 00000, "The handshake record length is too long."
// *Cause: The handshake record length exceeds the maximum that is allowed by the
// SSL specification.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29021, 00000, "Secret key length is incorrect when using SSL 2.0."
// *Cause: The length of the decrypted ENCRYPTED-KEY is incorrect.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29022, 00000, "Operation is being attempted on the wrong side of the client/server connection."
// *Cause: The SSL network layer has detected that the operation has been attempted on
// the wrong side of the client/server connection.
// *Action: Select the protocol side (of this protocol) to be the same as the one selected
// with a previous protocol.
/
29023, 00000, "The buffers are not empty."
// *Cause: Trying to free buffers that are not empty.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29024, 00000, "Certificate validation failure"
// *Cause: The certificate sent by the other side could not be validated. This may occur if
// the certificate has expired, has been revoked, or is invalid for another reason.
// *Action: Check the certificate to determine whether it is valid. Obtain a new certificate,
// alert the sender that the certificate has failed, or resend.
/
29025, 00000, "Error found in certificate check callback."
// *Cause: The application callback failed during additional certificate
// validation. Additional checks include CRL validation and extension checking.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29026, 00000, "Decryption failure"
// *Cause: SSL record decryption failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29027, 00000, "Error in entropy collection"
// *Cause: The internal entropy collection failed to generate enough seed data.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29028, 00000, "Server verification failure when using SSL 2.0"
// *Cause: Processing of an SSL 2.0 SERVER-VERIFY message failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29029, 00000, "SSL handshake already completed"
// *Cause: The system is trying to initiate a handshake when it has already been completed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29030, 00000, "SSL handshake is requested."
// *Cause: The peer sends this message if it wishes to renegotiate. The application
// can either proceed with the renegotiation or reject the request.
// *Action: This is not an error. To find out more details enable tracing
// and retry the connection. Contact Oracle customer support with the
// trace output.
/
29031, 00000, "SSL handshake is required."
// *Cause: Renegotiation cannot proceed before the SSL handshake is completed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29032, 00000, "The given identity is not complete."
// *Cause: The certificate list does not contain both private key and certificate.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29033, 00000, "Invalid PFX"
// *Cause: The PFX is invalid for this operation containing either no certificates
// and private key or multiple private keys. However, the API which returns
// this error is not used in our code.
// *Document: NO
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29034, 00000, "Correct cipher suite or client authentication is needed."
// *Cause: Before installing a private key, a cipher suite or client authentication suite
// using the same key exchange algorithm must be installed first. This has not
// been done.
// *Action: Install a cipher suite or client authentication suite that uses the same key
// exchange algorithm as the private key before re-installing the private key.
/
29035, 00000, "Pseudo Random Number Generator is needed"
// *Cause: PRNG not set yet. A PRNG must be installed first.
// *Document: NO
// *Action:
/
29036, 00000, "This feature is not supported"
// *Cause: Operation is not supported by the current connection parameters.
// *Action: Check the Oracle documentation to determine the appropriate
// connection parameters required for this operation.
/
29037, 00000, "No certificate is present"
// *Cause: The other client or server sent a certificate message that contained
// no certificates.
// *Action: Check the other side (client or server) to ensure they have
// appropriate credentials.
/
29038, 00000, "There are no matching certificates."
// *Cause: The other client or server sent a certificate message that contained
// a certificate which was not signed by a trusted certificate authority (CA).
// *Action: Check to ensure that the other client or server sends a certificate which is
// signed by a CA that is in your trusted list. Or, include the CA
// certificate for the other client or server's certificate as a trustpoint
// in your wallet.
/
29039, 00000, "There are no matching cipher suites."
// *Cause: Neither end of the handshake can agree on a cipher suite.
// *Action: Check to ensure that both sides of the handshake select cipher suites
// that are supported.
/
29040, 00000, "There are no supported cipher suites."
// *Cause: This end of the handshake cannot support any cipher suites. This
// connection and the peer have some matching cipher suites, however,
// these cipher suites cannot be negotiated because they cannot be supported
// by the connection.
// *Action: Check to ensure that both sides of the handshake select cipher suites
// that are supported by the connection. Refer to Oracle documentation for
// supported cipher suites.
/
29041, 00000, "The callback is NULL."
// *Cause: A NULL callback was passed.
// *Document: NO
// *Action:
/
29042, 00000, "Read buffer is not empty."
// *Cause: There is an attempt to free a read buffer that is not empty.
// *Document: NO
// *Action:
/
29043, 00000, "Read is required."
// *Cause: Renegotiation with the peer has not yet started. There is
// application data which must be processed before the
// handshake can proceed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29044, 00000, "Renegotiation has already been requested."
// *Cause: Renegotiation has already been requested.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29045, 00000, "Renegotiation request has been refused."
// *Cause: A renegotiated handshake has been refused by the peer.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29046, 00000, "Session is resumable."
// *Cause: Server is trying to resume a session with different session parameters.
// *Action: Server should resume the session with the correct session parameters.
/
29047, 00000, "Mismatch in Transport Layer Security extension"
// *Cause: Neither side can agree on a TLS extension.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29048, 00000, "Unexpected message received."
// *Cause: An unexpected message has been received.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29049, 00000, "Unknown record"
// *Cause: The record type is unknown.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29050, 00000, "Installed client authentication mode is not supported."
// *Cause: The enabled client authentication mode(s) cannot be used within
// the selected cipher suite.
// *Action: Enable a client authentication mode that can be used within the selected
// cipher suite.
/
29051, 00000, "The given public key type is not supported."
// *Cause: The public key in the first certificate is not supported.
// *Action: Check to ensure that the certificate complies with the X.509v3 standard.
/
29052, 00000, "Write buffer is not empty."
// *Cause: There is an attempt to free a write buffer that is not empty.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29084, 00000, "The parameter specified is illegal."
// *Cause: The parameter is not correct. For example, it could be bad input,
// or an invalid message.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29095, 00000, "Index is not correct."
// *Cause: The instance identified by the index parameter doesn't exist.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29096, 00000, "The given length is incorrect."
// *Cause: The specified length is too small or is invalid.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29100, 00000, "Cannot create local key ID."
// *Cause: Creation of local key identifier for the certificate or the private key
// failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29101, 00000, "Cannot add private key bag."
// *Cause: The private key could not be added to the PKCS#12 object. Possible reasons
// are: (i) A required parameter is NULL (ii) The PKCS#12 construct is not
// supported (iii) An ASN.1 encoding error occurred in the certificate.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29102, 00000, "Cannot add certificate bag."
// *Cause: Creation of certificate bag failed. The application could have
// run out of memory.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29103, 00000, "Cannot create PKCS #12 wallet."
// *Cause: Creation of PKCS#12 wallet failed possibly due to memory allocation
// failure.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
29104, 00000, "Cannot add certificate request."
// *Cause: Adding certificate request to the PKCS#12 wallet failed.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
29105, 00000, "Cannot export PKCS #12 wallet."
// *Cause: A required parameter is NULL or the PKCS#12 construct is not supported.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29106, 00000, "Cannot import PKCS #12 wallet."
// *Cause: A required parameter is NULL or the BER-encoding is malformed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29107, 00000, "Cannot create PKCS #12 wallet."
// *Cause: PKCS#12 wallet creation failed. The application may have
// run out of memory.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
29108, 00000, "Cannot initialize random object."
// *Cause: The random object could not be initialized or seeded. Either memory
// allocation has failed or the pseudo random number generator module
// has not been installed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29109, 00000, "Cannot create private key object."
// *Cause: The private key object could not be created. Memory allocation may have
// failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29110, 00000, "Invalid PKCS #12 bag type"
// *Cause: The PKCS #12 bag type is invalid. Either one of the required parameters
// is NULL or the requested OID is not in the list.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29111, 00000, "Invalid index"
// *Cause: The index passed for getting the bag type is less than 1.
// *Action: Check to ensure that the index is greater than 1.
/
29112, 00000, "Cannot access attributes from a PKCS #12 certificate bag."
// *Cause: The certificate cannot be accessed. One of the required parameters is
// probably NULL, or the index specified by the application does not contain
// a certbag, or the certificate could be malformed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29113, 00000, "Cannot access attributes from a PKCS #12 key bag."
// *Cause: Retrieval of the private key failed. One of the required parameters
// is probably NULL or the index specified by the application does not
// contain a key bag.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29114, 00000, "Cannot import private key."
// *Cause: The private key could not be imported. One of the required parameters
// could be NULL or the encoded private key could be malformed.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
29115, 00000, "Cannot export private key."
// *Cause: The private key could not be exported. Either the application ran out
// of memory or the key type is not valid.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
29116, 00000, "Cannot get PKCS #12 attributes."
// *Cause: Retrieval of an attribute failed. One of the required parameters could
// be NULL.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
29117, 00000, "Cannot add PKCS #12 attributes."
// *Cause: Could not add an attribute. The attribute parameter could be NULL.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
29118, 00000, "Cannot create PKCS #12 attributes."
// *Cause: Creation of the attributes failed, possibly due to a memory
// allocation error.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
29119, 00000, "Cannot import certificate."
// *Cause: The certificate cannot be imported. One of the required parameters could
// be NULL or the certificate has an invalid X.509 BER or DER encoding.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
29120, 00000, "Cannot export certificate."
// *Cause: The certificate cannot be exported. One of the required parameters could
// be NULL.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
29122, 00000, "could not add pkcs11 info to the pkcs12 wallet"
// *Cause: Failed while adding pkcs11 information into a pkcs12 wallet.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
29123, 00000, "could not get pkcs11 info from the pkcs12 wallet"
// *Cause: An error was encountered while retrieving pkcs11 information from
// the wallet.
// *Action: Enable tracing to determine the exact cause of this error.
// Contact Oracle customer support if needed.
/
29124, 00000, "pkcs11 library name already set"
// *Cause: pkcs11 library information was already set in the wallet.
// *Action: Use a different wallet that does not have this information.
// If issue persists, enable tracing to determine the exact cause of
// the error. Contact Oracle customer support if needed.
/
29125, 00000, "pkcs11 token label already set"
// *Cause: pkcs11 token label information was already set in the wallet.
// *Action: Use a different wallet that does not have this information.
// If issue persists, enable tracing to determine the exact cause of
// the error. Contact Oracle customer support if needed.
/
29126, 00000, "pkcs11 token passphrase already set"
// *Cause: The pkcs11 token passphrase can be set only once in the wallet.
// *Action: Use a different wallet that does not have this information.
// If issue persists, enable tracing to determine the exact cause of
// the error. Contact Oracle customer support if needed.
/
29127, 00000, "unknown pkcs11 information"
// *Cause: An unknown pkcs11 information type was encountered. The wallet may
// have been corrupted due to a system error or memory corruption.
// *Action: Enable tracing and retry the failed operation.
// Contact Oracle customer support with the trace output.
/
29128, 00000, "pkcs11 library name not set"
// *Cause: The wallet does not have pkcs11 library information.
// *Action: Ensure that the wallet was created with valid library location or
// update the wallet with this information.
/
29129, 00000, "pkcs11 token label not set"
// *Cause: The wallet does not have pkcs11 token label information.
// *Action: Ensure that the wallet was created with valid token label
// information or update the wallet with this information.
/
29130, 00000, "pkcs11 token passphrase not set"
// *Cause: The wallet does not have pkcs11 token passphrase.
// *Action: Ensure that the wallet was created with valid token passphrase
// information or update the wallet with this information.
/
29131, 00000, "pkcs11 certificate label already set in wallet"
// *Cause: The pkcs11 certificate label was already set in the wallet.
// *Action: Use an empty wallet (created with orapki).
/
29135, 00000, "Seed generation for Random Number Generator failed."
// *Cause: Generation of seed for random number generator failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29136, 00000, "The allocated buffer is too small."
// *Cause: The output buffer is too small.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29137, 00000, "The global context is incorrect."
// *Cause: The global context is incorrectly configured or invalid.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29140, 00000, "Cannot create certificate object."
// *Cause: Creation of the certificate object failed. The application could have
// run out of memory.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29141, 00000, "Cannot import in the der format."
// *Cause: Cannot import the certificate into the certificate object. The reason
// could be a malformed certificate.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29150, 00000, "DES self-test failure"
// *Cause: DES power up self-test has failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29151, 00000, "3DES self-test failure"
// *Cause: 3DES power up self-test has failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29152, 00000, "SHA-1 self-test failure"
// *Cause: The SHA-1 power up self-test has failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29153, 00000, "RSA self-test failure"
// *Cause: The RSA power up self-test has failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29154, 00000, "deterministic RNG self-test failure"
// *Cause: The deterministic Random Number Generator power up self-test has failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29155, 00000, "continuous key pair consistency check self-test failure"
// *Cause: The public-private key pair check test failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29156, 00000, "conditional RNG self-test failure"
// *Cause: Continuous Random Number Generator test, which is needed in FIPS mode,
// has failed.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29157, 00000, "Unable to build an absolute path to the library."
// *Cause: Not able to construct an absolute path to the
// location of the library.
// *Action: Enable tracing and attempt the connection again. Contact
// Oracle customer support with the trace output.
/
29158, 00000, "Unable to open library."
// *Cause: Opening of the library failed.
// *Action: Check to ensure that the library is present in the location
// specified, and that it has the appropriate file permissions.
/
29159, 00000, "Unable to read library."
// *Cause: Not able to read the library on which the DAC check has
// to be performed. Read call failed.
// *Action: Check if the library has the appropriate file permissions.
/
29160, 00000, "NZ library being used is different."
// *Cause: The NZ library being used at runtime is not the
// same one on which the digest was computed for the
// software integrity check.
// *Action: Check to ensure that the library being used is the same as the one on
// which the digest was pre-computed.
/
29161, 00000, "software integrity self-test failure"
// *Cause: The software integrity check test on the NZ shared library
// has failed.
// *Action: Check to ensure that the library being used is the same as the one on
// which the digest was pre-computed.
/
29162, 00000, "Non-FIPS cipher suites being used in FIPS mode."
// *Cause: The cipher suite being used does not contain FIPS-approved
// algorithms.
/
// *Action: Use cipher suites that contain FIPS-approved algorithms.
/
29163, 00000, "Third party PKI vendor is not supported in FIPS mode."
// *Cause: Third party PKI vendors like Entrust and MCS are not supported
// in FIPS mode.
// *Action: Use only Oracle PKI when running in FIPS mode.
/
29164, 00000, "External PKCS #12 wallet is not supported in FIPS mode."
// *Cause: PKCS #12 wallets created using third party software cannot be
// used in FIPS mode.
// *Action: Use only PKCS #12 wallets created by Oracle Wallet Manager when running in
// FIPS mode.
/
29166, 00000, "Bad key size in FIPS mode."
// *Cause: User attempted to use a key size that is not allowed in FIPS mode
// *Action: Ensure that the key size meets FIPS usage requirement. For example,
// RSA key modulus cannot be less than 1024 bits in FIPS mode.
/
29176, 00000, "CRL signature verification failed"
// *Cause: A CRL is verified before being used. CRL signature cannot be
// verified.
// *Action: Get a new CRL from CA
/
29177, 00000, "certificate serial number is not in CRL"
// *Cause: Cert is not revoked
// *Action:
/
29178, 00000, "certificate serial number is in CRL"
// *Cause: Cert has been revoked
// *Action: Reject the certificate
/
29179, 00000, "certificate validation check failed"
// *Cause: Could not complete checking certificate status with a CRL.
// *Action: Enable tracing to find more information on this error.
// Contact Oracle customer support if needed.
/
29180, 00000, "Unsupported validation protocol"
// *Cause: The certificate validation protocol is not supported
// *Action: Make sure a supported certificate validation protocol is specified
/
29181, 00000, "ldap_open failed"
// *Cause: Could not connect to the LDAP server
// *Action: Ensure that correct LDAP information was provided. Enable tracing
// to find more information. Contact Oracle customer support if needed.
/
29182, 00000, "ldap_bind failed"
// *Cause: Could not log in to the LDAP server
// *Action: Ensure that correct LDAP credentials were provided. Enable tracing
// to find more information. Contact Oracle customer support if needed.
/
29183, 00000, "ldap_search failed"
// *Cause: Failed to complete search operation in LDAP server
// *Action: Enable tracing to find more information on this error.
// Contact Oracle customer support if needed.
/
29184, 00000, "ldap_result failed"
// *Cause: Failed to retrieve results from LDAP operation
// *Action: Enable tracing to find more information on this error.
// Contact Oracle customer support if needed.
/
29185, 00000, "ldap_first_attribute failed"
// *Cause: Could not get the first attribute from LDAP entry.
// *Action: Enable tracing to find more information on this error.
// Contact Oracle customer support if needed.
/
29186, 00000, "ldap_get_values_len failed"
// *Cause: Failed to retrieve attribute values from LDAP entry
// *Action: Enable tracing to find more information on this error.
// Contact Oracle customer support if needed.
/
29187, 00000, "unsupported validation mechanism"
// *Cause: The validation mechanism specified in OID is not supported
// *Action: Make sure a supported validation mechanism is set in OID
/
29188, 00000, "ldap_count_entries failed"
// *Cause: Failed to get count of entries from a search result chain.
// *Action: Enable tracing to find more information on this error.
// Contact Oracle customer support if needed.
/
29189, 00000, "No entry found in OID"
// *Cause: CRL not found in OID
// *Action: Upload the CRL to OID
/
29190, 00000, "Multiple entries in OID"
// *Cause: For a given issuer name there should be only one CRL in OID
// *Action: Make sure there is only one CRL for a given issuer name in OID
/
29191, 00000, "OID connection information not set"
// *Cause: To connect to OID the connection information must be available
// *Action: Set the OID connection information.
/
29192, 00000, "Validation mechanism not set in OID"
// *Cause: The validation mechanism to be used is not set in OID
// *Action: Set validation mechanism to be used in OID at
// cn=ValidationMechanism, cn=Validation, cn=PKI, cn=Products,
// cn=OracleContext
/
29193, 00000, "no CRL found using CRLDP mechanism"
// *Cause: A CRL could not fetched using CRL Distribution point (CRLDP)
// *Action: Contact the CA
/
29194, 00000, "no CRL found in cache"
// *Cause: CRL not in cache
// *Action:
/
29195, 00000, "CRL is expired"
// *Cause: CRL nextUpdate time is in the past
// *Action: Get a new CRL from the CA
/
29222, 00000, "Distinguished name does not match."
// *Cause: Distinguished name (DN) on certificate doesn't match user.
// *Action: Create the global user in the database with the DN that matches with the
// one in the user certificate on the client side.
/
29223, 00000, "Cannot create certificate chain."
// *Cause: Unable to create a certificate chain with the existing trust points
// for the certificate that is to be installed.
// *Action: Install the trust point that signed the certificate.
/
29224, 00000, "Cannot locate matching certificate request."
// *Cause: No matching certificate request for the certificate was found.
// *Action: Install the correct certificate.
/
29225, 00000, "Certificate already installed."
// *Cause: Attempting to install a certificate into a persona which already has it.
// *Action: Do not install the certificate.
/
29226, 00000, "No matching private key found."
// *Cause: Could not locate a matching private key
// in the persona for the given certificate (public key).
// *Action:
/
29227, 00000, "Certificate is expired."
// *Cause: Certificate is no longer valid..
// *Action: Obtain another certificate or renew this certificate.
/
29228, 00000, "Cannot calculate the number of bytes for output."
// *Cause: The cryptographic engine is confused about the algorithm.
// *Action: Check the parameters being used with the cryptographic functions.
/
29229, 00000, "the magic number found in the header does not match expected"
// *Cause: The input TDU has either been corrupted or is not being
// used correctly.
// *Action: Check that the TDU is being used from the beginning. If
// possible, compare the size of the TDU upon generation to
// the size being used.
/
29230, 00000, "the header length is not sufficient for message header"
// *Cause: The input TDU has either been corrupted or it is not being
// used correctly.
// *Action: Check that the TDU is being used from the beginning. If
// possible, compare the size of the TDU upon generation to
// the size being used.
/
29231, 00000, "the cryptographic engine failed to initialize"
// *Cause: During initialization of the cryptographic engine, some
// failure occurred. Possible causes include running out of memory and
// trying to seed the random number generator.
// *Action: Make sure the executable has been linked with compatible
// library versions, and that you are not running out of swap
// space.
/
29232, 00000, "the cryptographic engine key initialization failed"
// *Cause: During initialization of a key for cryptography, some
// failure occurred. This includes running out of memory and
// passing illegal arguments.
// *Action: Make sure the executable has been linked with compatible
// library versions, and that the correct parameters are
// being used for the cryptographic functions.
/
29233, 00000, "the key object could not be encoded"
// *Cause: The key object may be corrupted or may be an unsupported type.
// *Action: Check the key object being passed to the encoding routine.
/
29234, 00000, "a key object was not extracted from encoding"
// *Cause: The encoding may be corrupted or may not be a key object
// at all.
// *Action: Check the encoding and parameters passed to decoding
// routine.
/
29235, 00000, "the key information could not be retrieved"
// *Cause: The key may be corrupted or may be an unsupported type.
// *Action: Check the parameters being used with the cryptographic
// functions.
/
29236, 00000, "the random number generator will not accept seed"
// *Cause: The cryptographic engine may have run out of memory.
// *Action: Make sure the executable has been linked with compatible
// library versions.
/
29237, 00000, "the cryptographic engine could not finish the algorithm"
// *Cause: The cryptographic engine does not have enough information
// to correctly finish applying the algorithm.
// *Action: Check the parameters being used with the cryptographic
// functions.
/
29238, 00000, "the cryptographic engine could not apply the algorithm"
// *Cause: The cryptographic engine does not have enough information
// to correctly apply the algorithm.
// *Action: Check the parameters being used with the cryptographic
// functions.
/
29239, 00000, "the cryptographic engine could not initialize the algorithm"
// *Cause: The cryptographic engine does not have enough information
// to correctly initialize the algorithm.
// *Action: Check the parameters being used with the cryptographic
// functions.
/
29240, 00000, "the cryptographic engine does not recognize the algorithm"
// *Cause: The application may be passing wrong parameters.
// *Action: Check the parameters being used with the cryptographic
// functions.
/
29241, 00000, "a buffer block needs more space but its length is fixed"
// *Cause: The application has preallocated an output buffer that is
// too short for the operation and has specified that the
// buffer should not grow as needed.
// *Action: Either preallocate a larger buffer or allow the toolkit to
// grow the output buffer as needed.
/
29242, 00000, "the asymmetric key is too short to be used with the data."
// *Cause: An asymmetric key must be at least 11 bytes longer than
// the data it is being used to encrypt.
// *Action: Use an asymmetric key with more bits or break the data
// into smaller pieces.
/
29243, 00000, "the toolkit does not recognize the type of key being used"
// *Cause: The application may be passing wrong parameters.
// *Action: Check the parameters being used with the toolkit functions.
/
29245, 00000, "the toolkit does not recognize the function being used"
// *Cause: The application is probably passing the wrong parameters.
// *Action: Check the parameters being used with the toolkit functions.
/
29246, 00000, "the toolkit could not parse the tdu"
// *Cause: The TDU could be corrupted.
// *Action: Check the parameters being used with the toolkit functions.
/
29247, 00000, "an unopen toolkit object was used before it was opened"
// *Cause: Some toolkit objects must be opened before they can be
// used.
// *Action: Check the parameters being used with the toolkit functions.
/
29248, 00000, "an unrecognized WRL was used to open a wallet"
// *Cause: WRL's have a specific set of types and must be formatted
// correctly.
// *Action: Check the parameters being used with the toolkit
// functions.
/
29249, 00000, "an unrecognized state was passed to a cryptographic function"
// *Cause: The application is probably passing the wrong parameters.
// *Action: Check the parameters being used with the toolkit functions.
/
/
/ 29250-29299 RESERVED FOR MORE PL/SQL AND UTILITY PACKAGE ERRORS
/
29250, 00000, "Invalid index specifed in call to dbms_sql.bind_array"
// *Cause: An invalid index was specified in a call to bind_array of
// dbms_sql. The index may have been null or of an improper
// value.
// *Action: Correct the index value by modifying your PL/SQL program and try
// the bind_array call again.
29251, 00000, "Index1 is greater than Index2 in call to dbms_sql.bind_array"
// *Cause: The value of index1 was greater than the value for index2 in
// the call to bind_array. This is illegal since the elements of
// the table that will be bound are those with indexes greater
// than or equal to index1 and less than or equal to index2.
// *Action: Correct the value of the two indexes and try the call to
// again bind_array.
29252, 00000, "collection does not contain elements at index locations in call to dbms_sql.bind_array"
// *Cause: The bound table does not contain elements at both index locations
// in call to bind_array of dbms_sql. This is illegal.
// Both index locations must contain elements.
// In other words tab.exists(index1) and tab.exists(index2) must
// both return true.
// *Action: Either modify the two indexes or the contents of the table
// and try the call again.
29253, 00000, "Invalid count argument passed to procedure dbms_sql.define_array"
// *Cause: The count argument specified in the call to procedure define_array
// of package dbms_sql had an invalid value. Invalid values are
// negative numbers and nulls. The argument must be a positive
// integer.
// *Action: Correct your PL/SQL program so that only valid arguments are passed
// to define_array and try again.
29254, 00000, "Invalid lower_bound argument passed to procedure dbms_sql.define_array"
// *Cause: The lower_bound argument specified in the call to procedure
// define_array had an invalid value. Legal values are all
// integers (both positive and negative) including zero. The null
// value is illegal.
// *Action: Correct your PL/SQL program so that only valid arguments are passed
// to define_array and try again.
29255, 00000, "Cursor contains both bind and define arrays which is not permissible"
// *Cause: Both define_array and bind_array have been called on this cursor.
// This is illegal. It is not possible for a cursor to both contain
// array binds and array defines. The semantics of this setting are
// nonsensical. Array defines are used to move data from select
// queries into PL/SQL tables and array binds to bind PL/SQL tables
// to non-select queries.
// *Action: Modify your PL/SQL program to only perform calls to one of the two
// functions depending on the kind of cursor at hand.
29256, 00000, "Cursor contains both regular and array defines which is illegal"
// *Cause: Both define_array and define_column have been called on this
// cursor. This is illegal. It is not possible for a cursor
// to both contain regular and array defines. The semantics of this
// setting are nonsensical. Array defines are used to move data
// from select queries into PL/SQL tables and regular defines to
// move data from select queries into PL/SQL variables.
// *Action: Modify your PL/SQL program to only perform calls to one of the two
// functions depending on the situation at hand.
29257, 00000, "host %s unknown"
// *Cause: The specified host was unknown.
// *Action: Check the spelling of the host name or the IP address. Make sure
// that the host name or the IP address is valid.
29258, 00000, "buffer too small"
// *Cause: The input or output buffer was too small for the operation.
// *Action: Increase the size of the buffer and retry the operation.
29259, 00000, "end-of-input reached"
// *Cause: The end of the input was reached.
// *Action: If the end of the input is reached prematurely, check if the input
// source terminates prematurely. Otherwise, close the connection
// to the input.
29260, 00000, "network error: %s"
// *Cause: A network error occurred.
// *Action: Fix the network error and retry the operation.
29261, 00000, "bad argument"
// *Cause: A bad argument was passed to the PL/SQL API.
// *Action: Check the arguments passed to the PL/SQL API and retry the call.
29262, 00000, "bad URL"
// *Cause: An improperly formed URL was passed to the PL/SQL API.
// *Action: Check the URL and retry the call.
29263, 00000, "HTTP protocol error"
// *Cause: A HTTP protocol error occured during the HTTP operation.
// *Action: Check the HTTP server that the HTTP operation was performed to
// make sure that it follows the HTTP protocol standard.
29264, 00000, "unknown or unsupported URL scheme"
// *Cause: The URL scheme was unknown or unsupported.
// *Action: Check the URL to make sure that the scheme is valid and supported.
29265, 00000, "HTTP header not found"
// *Cause: The requested HTTP header was not found.
// *Action: Check to make sure that the requested HTTP header is present.
29266, 00000, "end-of-body reached"
// *Cause: The end of the HTTP response body was reached.
// *Action: If the end of the HTTP response is reached prematurely, check if
// the HTTP response terminates prematurely. Otherwise, end the
// HTTP response.
29267, 00000, "illegal call"
// *Cause: The call to the PL/SQL API was illegal at the current stage of
// the operation.
// *Action: Retry the call at a different stage of the operation.
29268, 00000, "HTTP client error %s"
// *Cause: The HTTP response indicated that the HTTP client error occurred.
// *Action: Fix the HTTP client error and retry the HTTP request.
29269, 00000, "HTTP server error %s"
// *Cause: The HTTP response indicated that the HTTP server error occurred.
// *Action: Fix the HTTP server error and retry the HTTP request. Contact
// the admistrator of the HTTP server when necessary.
29270, 00000, "too many open HTTP requests"
// *Cause: Too many HTTP requests were opened.
// *Action: End some HTTP requests and retry the HTTP request.
29271, 00000, "not connected"
// *Cause: The network connection was not made while the network operation was
// attempted.
// *Action: Retry the network operation after the network connection is made
// successfully.
29272, 00000, "initialization failed"
// *Cause: The UTL_HTTP package failed to initialize.
// *Action: Free up some memory or other system resources and retry the
// operation.
29273, 00000, "HTTP request failed"
// *Cause: The UTL_HTTP package failed to execute the HTTP request.
// *Action: Use get_detailed_sqlerrm to check the detailed error message.
// Fix the error and retry the HTTP request.
29274, 00000, "fixed-width multibyte character set not allowed for a URL"
// *Cause: The character set used as an encoding of the URL is a fixed-width
// multibyte character set and is not allowed for a URL.
// *Action: Use the corresponding variable-width multibyte character set for
// the URL instead.
29275, 00000, "partial multibyte character"
// *Cause: The requested read operation could not complete because a partial
// multibyte character was found at the end of the input.
// *Action: Ensure that the complete multibyte character is sent from the
// remote server and retry the operation. Or read the partial
// multibyte character as RAW.
29276, 00000, "transfer timeout"
// *Cause: Timeout occurred while reading from or writing to a network
// connection.
// *Action: Check the remote server or the network to ensure that it responds
// within the timeout limit. Or increase the timeout value.
29277, 00000, "invalid SMTP operation"
// *Cause: The SMTP operation was invalid at the current stage of the SMTP
// transaction.
// *Action: Retry the SMTP operation at the appropriate stage of the SMTP
// transaction.
29278, 00000, "SMTP transient error: %s"
// *Cause: A SMTP transient error occurred.
// *Action: Correct the error and retry the SMTP operation.
29279, 00000, "SMTP permanent error: %s"
// *Cause: A SMTP permanent error occurred.
// *Action: Correct the error and retry the SMTP operation.
29280, 00000, "invalid directory path"
// *Cause: A corresponding directory object does not exist.
// *Action: Correct the directory object parameter, or create a corresponding
// directory object with the CREATE DIRECTORY command.
29281, 00000, "invalid mode"
// *Cause: An invalid value was specified for file open mode.
// *Action: Correct the mode to be one of the values: 'r','a', or 'w'.
29282, 00000, "invalid file ID"
// *Cause: A file ID handle was specified for which no corresponding
// open file exists.
// *Action: Verify that the file ID handle is a value returned from a
// call to UTL_FILE.FOPEN.
29283, 00000, "invalid file operation"
// *Cause: An attempt was made to read from a file or directory that does
// not exist, or file or directory access was denied by the
// operating system.
// *Action: Verify file and directory access privileges on the file system,
// and if reading, verify that the file exists.
29284, 00000, "file read error"
// *Cause: An attempt to read from a file failed.
// *Action: Verify that the file exists, and that it is accessible, and
// that it is open in read mode.
29285, 00000, "file write error"
// *Cause: Failed to write to, flush, or close a file.
// *Action: Verify that the file exists, that it is accessible, and that
// it is open in write or append mode.
29286, 00000, "internal error"
// *Cause: A fatal error occurred while allocating PL/SQL session memory.
// *Action: Verify that the PL/SQL session is connected and that
// adequate memory resources are available.
29287, 00000, "invalid maximum line size"
// *Cause: An invalid maximum line size value was specified.
// *Action: Correct the maximum line size to be in the range [1, 32767].
29288, 00000, "invalid file name"
// *Cause: An invalid file name or a file name of an invalid length was
// specified.
// *Action: Correct the file name.
29289, 00000, "directory access denied"
// *Cause: A directory object was specified for which no access is granted.
// *Action: Grant access to the directory object using the command
// GRANT READ ON DIRECTORY [object] TO [username];.
29290, 00000, "invalid offset specified for seek"
// *Cause: An attempt was made to seek past the end of the file, or
// both the absolute and relative offsets were NULL, or
// absolute offset was less than zero.
// *Action: If specifying an absolute offset, ensure it is in the range
// [0, <total number of bytes in the file>], or
// if specifying a relative offset, ensure it is no greater than the
// current byte position plus the number of bytes remaining in the
// file.
29291, 00000, "file remove operation failed"
// *Cause: A file deletion attempt was refused by the operating system.
// *Action: Verify that the file exists and delete privileges granted on
// the directory and the file.
29292, 00000, "file rename operation failed"
// *Cause: A file rename attempt was refused by the operating system
// either because the source or destination directory does not
// exist or is inaccessible, or the source file isn't accessible,
// or the destination file exists.
// *Action: Verify that the source file, source directory, and destination
// directory exist and are accessible, and that the destination
// file does not already exist.
29293, 00000, "A stream error occurred during compression or uncompression."
// *Cause: The stream state was discovered to be invalid during compression
// or uncompression, or an invalid compression quality was requested
// or a NULL or invalid compression parameter was detected.
// *Action: Verify that quality is within the range [0,9] and that valid
// input source data exists.
29294, 00000, "A data error occurred during compression or uncompression."
// *Cause: An error occurred while compressing or uncompressing input source.
// *Action: Verify that source data is a valid compressed or uncompressed
// data set.
29295, 00000, "invalid mime header tag"
// *Cause: An error occurred while scanning string for mime header tag
// *Action: Verify that source data is a valid mime header string, in the
// format: =?<charset>?<encoding>?<encoded string>?=
29296, 00000, "invalid encoded string"
// *Cause: An error occurred while decoding the input string
// *Action: Verify that source data is a valid encoded string.
29297, 00000, "The compressed representation is too big"
// *Cause: The compressed output is too big to return.
// *Action: Do not attempt to compress source data.
29298, 00000, "Character set mismatch"
// *Cause: The character set mode in which the file was opened did
// not match the character set of the read or write operation.
// *Action: Use the correct UTL_FILE read and write procedures which
// coorespond to the character set mode in which the file was
// opened.
29299, 00000, "Invalid handle for piecewise compress or uncompress"
// *Cause: The process program opened too many handles, and the specified
// handle was either uninitialized or outside a valid range.
// *Action: Close some handles and verify that the specified handle is opened
// or within a valid range.
/
/
/ 29300 - 29399 Reserved for errors from DBMS* pl/sql pakages.
/ These messages are generated from the dbms_sys_error package.
/ Messages can be given explicitly in this file or they can be passed as
/ a (single) string parameter to the
/ The dbms_sys_error.raise_system_error call.
/ If an error message is not found in this file, the string passed to the
/ call is used as the error message.
/
/ 29300 - 29354 RESERVED FOR THE DBMS_SQL PACKAGE
/
29300, 00000, "ORACLE error, tablespace point-in-time recovery"
// *Cause: Another ORACLE error occured in the DBMS_PITR package.
// *Action: See the text of the error message for a description of the error.
/
29301, 00000, "wrong DBMS_PITR package function/procedure order"
// *Cause: The DBMS_PITR package function/procedure was called in an incorrect
// order.
// *Action: Restart tablespace point-in-time recovery with a correct procedure.
/
29302, 00000, "database is not open clone"
// *Cause: The database was not opened as a clone database.
// *Action: Mount the database clone and open the database.
/
29303, 00000, "user does not login as SYS"
// *Cause: The user did not log in as SYS to perform tablespace point-in-time
// recovery in a clone database.
// *Action: Log in as SYS and restart tablespace point-in-time recovery.
/
29304, 00000, "tablespace '%s' does not exist"
// *Cause: The selected tablespace does not exist in the database.
// *Action: Check the list of tablespaces in V$TABLESPACE and select a valid
// tablespace.
/
29305, 00000, "cannot point-in-time recover tablespace '%s'"
// *Cause: An attempt was made to ALTER the tablespace to be read only.
// *Action: Check if the tablespace is SYSTEM or with online rollback segment.
/
29306, 00000, "datafile %s is not online"
// *Cause: The selected datafile was not online.
// *Action: Bring the the datafile online and rename it if necessary.
/
29307, 00000, "datafile %s error, %s"
// *Cause: The datafile is not ready for tablespace point-in-time recovery.
// *Action: Check the correct tablespace point-in-time recovery procedure.
/
29308, 00000, "view TS_PITR_CHECK failure"
// *Cause: Some objects which crossed the boundary of the recovery set were
// not allowed in the tabelspace point-in-time recovery.
// *Action: Query TS_PITR_CHECK and resolve the boundary crossing objects.
/
29309, 00000, "export dump file was generated by different version of DBMS_PITR package"
// *Cause: The version of DBMS_PITR is different from the version of the
// cloned database.
// *Action: Load the version of DBMS_PITR which matches the version of the
// cloned database.
/
29310, 00000, "database is not open, or opened as a clone"
// *Cause: Either the database was not open, or an attempt was made to open it
// as a cloned database.
// *Action: Open the production database instead.
/
29311, 00000, "export dump file was not generated by this database, %s does not match"
// *Cause: The export dump files were imported to an incorrect database.
// *Action: Open the correct production database and try the import again.
/
29313, 00000, "tablespace '%s' cannot be imported twice"
// *Cause: This is an internal error.
// *Action: Contact your database administrator.
/
29314, 00000, "tablespace '%s' is not OFFLINE FOR RECOVER nor READ ONLY"
// *Cause: Tablespace clean SCN is either 0 or invalid.
// *Action: ALTER the tablespace OFFLINE FOR RECOVER.
/
29315, 00000, "tablespace '%s' has been recreated"
// *Cause: An attempt was made to recover a tablespace to a point-in-time
// before it was recreated.
// *Action: Choose a different point in time for recovery.
/
29316, 00000, "datafile %s been imported twice"
// *Cause: This is an internal error.
// *Action: Contact your database administrator.
/
29317, 00000, "datafile %s does not exist"
// *Cause: The specified datafile could not be found in the production
// database.
// *Action: Copy the datafile from the clone database.
/
29318, 00000, "datafile %s is online"
// *Cause: The datafile is online.
// *Action: Take the datafile offline.
/
29319, 00000, "datafile %s is not correct"
// *Cause: An incorrect datafile was copied to the production database. The
// datafile information in the export dump file differs with the
// information in the datafile in the production database.
// *Action: Copy the datafile from the clone database to the production
// database.
/
29320, 00000, "datafile header error"
// *Cause: An error occured during reading datafile header.
// *Action: Copy the correct datafile from the clone database to the
// production database, then retry the operation.
/
29321, 00000, "too many datafiles added since the point-in-time"
// *Cause: Too many datafiles were added to the recovery set since the
// point-in-time recovery.
// *Action: Divide the recovery set into smaller subsets and retry.
/
29322, 00000, "SCN string size too long -- maximum size 58 bytes/characters"
// *Cause: Too many characters in specifying the SCN string
// *Action: Remove all unnecessary characters. Only 15 characters are required
// for both the hex and decimal representation of the 48 bit SCN.
/
29323, 00000, "ALTER DATABASE SET COMPATIBILITY command not supported by %s"
// *Cause: The ALTER DATABASE SET COMPATIBILITY command failed because one
// or more instances do not support dynamic compatible setting change.
// *Action: No action required.
29324, 00000, "SET COMPATIBILITY release string format is wrong"
// *Cause: It should be of the form x.x.x
// *Action: Use the correct format.
/
29325, 00000, "SET COMPATIBILITY release number lower than %s"
// *Cause: The SET COMPATIBILITY release compatibility release number was lower
// than the current compatible setting.
// *Action: Specify a higher release number.
/
29326, 00000, "SET COMPATIBILITY release number higher than %s"
// *Cause: The ALTER DATABASE SET COMPATIBILITY command failed because one
// or more instances had a lower release number.
// *Action: Specify a lower release number.
/
29327, 00000, "unsupported client compatibility mode used when talking to the server"
// *Cause: The client compatibility mode is higher than the
// version of the server.
// *Action: Using SET COMPATIBILITY command, specify the same
// release number as the server.
/
29328, 00000, "too many datafiles in this tablespace '%s'"
// *Cause: Too many datafiles in this bitmap tablespace. ORACLE does not
// support at this moment.
// *Action: Call Oracle Support.
/
29329, 00000, "Table not of type XMLType"
// *Cause: Table is not XMLType table
// *Action: Ensure table is a XMLType table
/
/
/ 29330 - 29334 Reserved for DBMS_SQLPLUS_SCRIPT and UTL_HTTP packages
/
29330, 00000, "Source script length too big"
// *Cause: Source script length exceeded the maximum size of 4 Gigabytes.
// *Action: Make sure source script length is not greater than 4 Gigabytes.
/
29331, 00000, "HTTP redirection %s"
// *Cause: The HTTP response indicated a redirection to another location.
// *Action: Retry the HTTP request at the redirected location.
/
/
/ 29335 - 29349 Reserved for Pluggable Tablespace errors.
/
29335, 00000, "tablespace '%s' is not read only"
// *Cause: The tablespace is not read only.
// *Action: Make the tablespace read only and retry the operation.
/
29336, 00000, "Internal error [%s] [%s] from DBMS_PLUGTS"
// *Cause: Internal error from package DBMS_PLUGTS.
// *Action: Call Oracle Support.
/
29337, 00000, "tablespace '%s' has a non-standard block size (%s)"
// *Cause: The tablespace has a non-standard block size and making
// such a tablespace read-write is not permitted.
// *Action: Use some other mechanism to import the data
/
29338, 00000, "datafile %s is in an undesired state (%s, %s)"
// *Cause: The referred datafile is not in a state ready for tablespace
// copy operation. For example, the datafile may be offline. The
// datafile needs to be ONLINE, and either READ ONLY or READ WRITE.
// *Action: Put the datafile into the desired state.
/
29339, 00000, "tablespace block size %s does not match configured block sizes"
// *Cause: The block size of the tablespace to be plugged in or
// created does not match the block sizes configured in the
// database.
// *Action:Configure the appropriate cache for the block size of this
// tablespace using one of the various (db_2k_cache_size,
// db_4k_cache_size, db_8k_cache_size, db_16k_cache_size,
// db_32K_cache_size) parameters.
/
29340, 00000, "export file appears to be corrupted: [%s] [%s] [%s]"
// *Cause: This is caused either by a corrupted export file or by an
// Oracle internal error.
// *Action: Make sure the export file used for transportable tablespace
// is not corrupted. If the error still occurs, call Oracle support.
/
29341, 00000, "The transportable set is not self-contained"
// *Cause: The set of objects in the set of tablespaces selected are
// not self-contained.
// *Action: Consider using different export options, or removing some
// of the pointers that caused the violation, or selecting a
// different set of tablespaces.
/
29342, 00000, "user %s does not exist in the database"
// *Cause: The referred user is one of the owners of data in the
// pluggable set. This user does not exist in the database.
// *Action: Consider either creating the user in the database or map
// the user to a different user via FROM_USER and TO_USER
// import options.
/
29343, 00000, "user %s (mapped from user %s) does not exist in the database"
// *Cause: The referred user is one of the owners of data in the
// pluggable set. This user does not exist in the database.
// *Action: Consider either creating the user or map the original user to
// a different user.
/
29344, 00000, "Owner validation failed - failed to match owner '%s'"
// *Cause: The system failed to match the referred owner. There are two
// cases that this may occur. (1) This user owns data in the
// transportable set, but this user is not specified in the TTS_OWNERS
// list of the import command line option, assuming that TTS_OWNERS
// is specified. (2) This user is specified in the TTS_OWNER list,
// but this user does not own any data in the transportable set.
// *Action: Retry import with a different OWNER list.
/
29345, 00000, "cannot plug a tablespace into a database using an incompatible character set"
// *Cause: Oracle does not support plugging a tablespace into a database
// using an incompatible character set.
// *Action: Use import/export or unload/load to move data instead.
/
29346, 00000, "invalid tablespace list"
// *Cause: the tablespace list supplied to dbms_tts.transport_set_check
// PL/SQL routine is in an incorrect format.
// *Action: Check the manual and use the correct format.
/
29347, 00000, "Tablespace name validation failed - failed to match tablespace '%s'"
// *Cause: The system failed to match the referred tablespace. There are
// 2 cases that this may happen. (1) This tablespace is in the
// transportable set, but it is not specified in the TABLESPACES
// list of the import command line option, assuming that TABLESPACES
// is specified. (2) This tablespace is in the TABLESPACES list, but
// it is not in the transportable set.
// *Action: Retry the operation with the correct TABLESPACES list.
/
29348, 00000, "You must specify the datafiles to be plugged in"
// *Cause: The datafiles to be plugged in are not specified.
// *Action: Specify the datafiles via the import DATAFILES command
// line option.
/
29349, 00000, "tablespace '%s' already exists"
// *Cause: Tried to plug-in a tablespace which already exists.
// *Action: Drop the offending tablespace if possible. Otherwise use a
// different method (e.g., import/export) to move data.
/
29350, 00000, "server version %s incompatible with package %s version %s"
/
29351, 00000, "can not transport system, sysaux, or temporary tablespace '%s'"
// *Cause: The referred tablespace is either the system tablespace, the
// sysaux tablespace, or a temporary tablespace.
// *Action: Do not include this tablespace in the transportable set.
29352, 00000, "event '%s' is not an internal event"
// *Cause: The DBMS_SYSTEM.WAIT_FOR_EVENT procedure was called with an event
// name that is not an internal event.
// *Action: Check the list of events from X$KSLED and verify the event name
// parameter passed to the WAIT_FOR_EVENT procedure.
29353, 00000, "The transportable list is too long."
// *Cause: The transportable list exceeds the buffer size of 32767.
// *Action: Reduce the list of tablespaces to transport.
/
29354, 00000, "cannot transport rekeying tablespace '%s'"
// *Cause: An attempt to transport a tablespace, or unplug a pluggable
// database containing a tablespace in the middle of a tablespace
// encrypt, decrypt, or rekey failed.
// *Action: Wait for the tablespace rekey to finish, or use the ALTER
// TABLESPACE ENCRYPTION FINISH [ ENCRYPT | DECRYPT | REKEY ] command
// to resume and finish the encrypt, decrypt, or rekey operation first.
/
/ 29355 - 29399 RESERVED FOR DBMS RESOURCE MANAGER PACKAGES
/
29355, 00000, "NULL or invalid %s argument specified"
// *Cause: The named argument was either invalid or specified as a NULL
// *Action: Specify non-null, valid arguments.
/
29356, 00000, "These parameters can be specified only for directives that refer to consumer groups."
// *Cause: A parameter was specified as an argument to procedure
// CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package
// DBMS_RESOURCE_MANAGER that is not allowed when the
// GROUP_OR_SUBPLAN is a plan.
// Only the following parameters are allowed when
// GROUP_OR_SUBPLAN is a plan:
// - MGMT_P1, MGMT_P2, MGMT_P3, MGMT_P4
// MGMT_P5, MGMT_P6, MGMT_P7, MGMT_P8
// - UTILIZATION_LIMIT
// *Action: Specify only these parameters when GROUP_OR_SUBPLAN is a plan.
/
29357, 00000, "object %s already exists"
// *Cause: The name specified as an argument to procedure CREATE_PLAN,
// CREATE_CDB_PLAN, CREATE_CONSUMER_GROUP,
// or CREATE_CATEGORY of package DBMS_RESOURCE_MANAGER
// was already in use.
// *Action: Specify an unused name.
/
29358, 00000, "resource plan %s does not exist"
// *Cause: An invalid plan name was specified as an argument to procedure
// UPDATE_PLAN or UPDATE_CDB_PLAN of package DBMS_RESOURCE_MANAGER.
// *Action: Specify an existing plan name.
/
29359, 00000, "invalid method name %s specified for resource plan %s"
// *Cause: An invalid method was specified as an argument to
// procedure CREATE_PLAN or UPDATE_PLAN of package
// DBMS_RESOURCE_MANAGER.
// *Action: Specify a valid method name.
/
29360, 00000, "resource plan %s contains multiple directives for subplan %s"
// *Cause: A resource plan and its subplans had more than one directive
// for a particular subplan.
// *Action: Modify the resource plan or its subplans so that there is at most
// one directive for this subplan.
/
29361, 00000, "value %s for %s is outside valid range of 0 to 100"
// *Cause: An invalid value was specified for a plan directive parameter.
// *Action: Specify a value between 0 and 100 inclusive.
/
29362, 00000, "plan directive %s, %s does not exist"
// *Cause: A nonexistent plan directive was specified for procedure
// UPDATE_PLAN_DIRECTIVE or UPDATE_CDB_PLAN_DIRECTIVE
// of package DBMS_RESOURCE_MANAGER.
// *Action: Specify an existing plan directive for update.
/
29363, 00000, "plan directive %s, %s is mandatory and cannot be modified or deleted"
// *Cause: An attempt was made to modify a mandatory plan directive.
// *Action: Do not attempt to modify mandatory plan directives because they
// are required by the Resource Manager and cannot be modified.
/
29364, 00000, "plan directive %s, %s already exists"
// *Cause: An attempt was made to create a plan directive that already exists.
// *Action: Retry the create operation using different values.
/
29365, 00000, "parameters %s and %s cannot both be set"
// *Cause: An attempt was made to set both parameters.
// *Action: Only set one of parameters or neither of them.
29366, 00000, "invalid CONSUMER_GROUP argument specified"
// *Cause: An invalid consumer group name was specified.
// *Action: Specify a non-NULL, valid consumer group name.
/
29367, 00000, "object %s does not exist"
// *Cause: A non-existent object name was specified as an argument to procedure
// CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.
// *Action: Specify a valid plan or consumer group name.
/
29368, 00000, "consumer group %s does not exist"
// *Cause: An non-existent consumer group was specified.
// *Action: Specify an existing consumer group.
/
29369, 00000, "invalid method name %s specified for consumer group %s"
// *Cause: An invalid method name was specified as an argument to
// procedure CREATE_CONSUMER_GROUP or UPDATE_CONSUMER_GROUP of package
// DBMS_RESOURCE_MANAGER.
// *Action: Specify a valid method name.
/
29370, 00000, "pending area is already active"
// *Cause: An attempt was made to activate a pending area that is
// already active.
// *Action: Wait until the pending area is no longer active; then, retry
// the operation.
/
29371, 00000, "pending area is not active"
// *Cause: An attempt was made to make changes without creating a pending
// area.
// *Action: Invoke procedure CREATE_PENDING_AREA before making any changes.
/
29372, 00000, "value for argument %s is too long; it must be less than or equal to %s characters"
// *Cause: An attempt was made to specify a string that exceeded
// the maximum length for that parameter.
// *Action: Use a value that fits within the specified limit.
/
29373, 00000, "resource manager is not on"
// *Cause: An attempt was made to execute an operation that cannot be
// executed with the resource manager being off
// *Action: Turn on the resource manager and try again.
/
29374, 00000, "resource plan %s in top-plan %s has no plan directives"
// *Cause: A plan was created in the pending area that is an orphan or
// stand-alone.
// *Action: Create plan directives if needed. Otherwise, delete the plan.
/
29375, 00000, "sum of values %s for level %s, plan %s exceeds %s"
// *Cause: The sum of plan directive parameter values for the specified
// plan level exceeded the limit specified.
// *Action: Alter the values for the level so that the sum is less
// than the limit specified.
/
29376, 00000, "number of consumer groups %s in plan %s exceeds %s"
// *Cause: The number of consumer groups in the specified plan was
// more than the limit specified.
// *Action: Change the plan so that the number of consumer groups
// is less than the limit specified.
/
29377, 00000, "consumer group %s is not part of top-plan %s"
// *Cause: OTHER_GROUPS was not included as part of the specified top-plan.
// Each top plan must include the built-in consumer group
// OTHER_GROUPS.
// *Action: Create a plan directive with the argument GROUP_OR_SUBPLAN
// being OTHER_GROUPS somewhere in the top-plan.
/
29378, 00000, "invalid consumer group mapping priorities"
// *Cause: The mapping priorities were not unique integers within the
// valid range.
// *Action: Set the mapping priorities to unique integers within the
// documented range.
/
29379, 00000, "resource plan %s is involved in a loop in top-plan %s"
// *Cause: A loop was discovered while validating a top-plan.
// *Action: Check the plans that have the specified plan as a GROUP_OR_SUBPLAN,
// and remove the plan directive that causes the loop.
/
29380, 00000, "resource plan %s is currently active and cannot be deleted"
// *Cause: An attempt was made to delete an active plan in the pending area.
// No changes can be made to active plans.
// *Action: Delete the plan when it is not in use.
/
29381, 00000, "plan/consumer_group %s referred to by another plan and cannot be deleted"
// *Cause: An attempt was made to delete a plan or consumer group that is
// referred to by another plan.
// *Action: Remove all plan directives that have the plan or consumer group as
// GROUP_OR_SUBPLAN; then delete the plan or consumer group.
/
29382, 00000, "validation of pending area failed"
// *Cause: Invalid changes were attempted in the pending area.
// *Action: See documentation and the error messages that follow this one.
/
29383, 00000, "all leaves of top-plan %s must be consumer groups"
// *Cause: An attempt was made to create or modify the specified top-plan
// but it has some plans as leaves.
// *Action: To identify which plans and/or plan directives need to be modified,
// look at all plans that have no plan directives. Then, alter the
// top-plan so that all its leaves are consumer groups.
/
29384, 00000, "number of consumer groups and subplans for plan %s exceeds %s"
// *Cause: An attempt was made to create or modify the specified plan, but
// the plan has more than 28 consumer groups or subplans.
// *Action: Make sure the specified plan points to no more than 28 distinct
// consumer groups or subplans.
/
29385, 00000, "cannot create plan directive from %s to %s"
// *Cause: An attempt was made to create a plan directive from a plan to
// itself.
// *Action: Make sure the arguments PLAN and GROUP_OR_SUBPLAN to procedure
// CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER are
// different.
/
29386, 00000, "plan or consumer group %s is mandatory and cannot be deleted or modified"
// *Cause: An attempt was made to delete or modify the specified mandatory
// plan or consumer group.
// *Action: Do not attempt to delete or modify mandatory plans and
// consumer groups.
/
29387, 00000, "no top-plans found in the pending area"
// *Cause: The VALIDATE_PENDING_AREA procedure found that either the
// intended top-plan(s) are involved in a loop or there are no
// top-plans.
// *Action: Check all edges going from a subplan to the intended top-plan.
// Make sure the top plan does not have any plan referring to it.
/
29388, 00000, "plan/consumer_group %s is part of more than one top-plan"
// *Cause: An attempt was made to delete a subtree that includes a plan or
// consumer group that is part of more than one top-plan as part
// of procedure DELETE_PLAN_CASCADE or package DBMS_RESOURCE_MANAGER.
// Such a plan or consumer group cannot be deleted.
// *Action: Check the ancestors of the plan or consumer group and make sure
// it is only part of the top-plan that includes the subtree being
// deleted.
/
29389, 00000, "too many errors during validation"
// *Cause: The number of errors detected during validation is too high.
// *Action: Perform the necessary actions to remove some errors, and retry
// validation.
/
29390, 00000, "some resource plans are not part of any top-plan"
// *Cause: An attempt was made to create or modify some plans in the
// pending area that are not part of any top-plan
// *Action: Remove these plans are try validation again.
/
29391, 00000, "%s and %s must be mandatory to create a mandatory plan directive"
// *Cause: An attempt was made to create a mandatory plan directive where
// either PLAN or GROUP_OR_SUBPLAN or both were not mandatory
// *Action: Recreate these objects as mandatory and then create the plan
// directive.
/
29392, 00000, "cpu parameters for level %s for plan %s must be zero"
// *Cause: The cpu parameters for the specified level had a non-zero value,
// which is not a valid value for the plan's current cpu policy.
// *Action: Change the cpu level parameters for the specified level to zero
// or change the plan cpu policy.
/
29393, 00000, "user %s does not exist or is not logged on"
// *Cause: An invalid user name was specified as argument to procedure
// SET_INITIAL_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER
// or SWITCH_CONSUMER_GROUP_FOR_USER of package DBMS_SYSTEM or
// the specified user was not logged on.
// *Action: Specify a valid user name.
/
29394, 00000, "session id %s and serial# %s do not exist"
// *Cause: Invalid session id and serial# were specified as arguments to
// procedure SWITCH_CONSUMER_GROUP_FOR_SESS of package
// DBMS_SYSTEM.
// *Action: Specify valid values from the view V$SESSION.
/
29395, 00000, "cannot set the initial consumer group to %s"
// *Cause: An attempt was made to set the initial consumer group of a user to
// OTHER_GROUPS or an INTERNAL_USE group.
// *Action: Certain groups are only for the resource manager's internal use.
// Specify another consumer group.
/
29396, 00000, "cannot switch group to %s"
// *Cause: An attempt was made to switch the consumer group of a user or
// a session to OTHER_GROUPS or an INTERNAL_USE group.
// *Action: Certain groups are only for the resource manager's internal use.
// Specify another consumer group.
/
29397, 00000, "cannot grant/revoke switch privilege for %s"
// *Cause: An attempt was made to grant or revoke the privilege to switch
// to OTHER_GROUPS or an INTERNAL_USE group.
// *Action: Certain groups are only for the resource manager's internal use.
// Specify another consumer group.
/
29398, 00000, "invalid privilege name specified"
// *Cause: An invalid privilege name was specified as an argument to
// procedure GRANT_SYSTEM_PRIVILEGE or REVOKE_SYSTEM_PRIVILEGE of
// package DBMS_RESOURCE_MANAGER_PRIVS.
// *Action: Specify a valid privilege name.
/
29399, 00000, "user %s does not have privilege to switch to consumer group %s"
// *Cause: An attempt was made to set the initial consumer group of the
// specified user but the user does not have the privilege to
// switch to that group.
// *Action: Grant the privilege to switch to the consumer group to the user
// and then set the initial group.
/
/ 29400 - 29469 Reserved for Oracle8 Data Cartridges
/
29400, 00000, "data cartridge error\n%s"
// *Cause: An error has occurred in a data cartridge external procedure.
// This message will be followed by a second message giving
// more details about the data cartridge error.
// *Action: See the data cartridge documentation
// for an explanation of the second error message.
29401, 00000, "data cartridge internal error [%s]"
// *Cause: The data cartridge encountered an unexpected condition.
// The argument is a string that identifies the internal
// error to Oracle development.
// This argument and the database version number are critical in
// identifying the root cause.
// *Action: Contact Oracle Support Services.
/
/
/ 29470 - 29489 RESERVED FOR THE DBMS_SQL PACKAGE
/
29470, 00000, "Effective userid or roles are not the same as when cursor was parsed"
// *Cause: The effective userid or roles on this call to DBMS_SQL are not the
// same as those at the time the cursor was parsed.
// *Action: Make sure the effective userid and roles are the same as when cursor
// was pared.
/
29471, 00000, "DBMS_SQL access denied"
// *Cause: DBMS_SQL access was denied due to security concerns.
// *Action: Check the alert log and trace file for more information.
/
29472, 00000, "DBMS_SQL.OPEN_CURSOR failed. security_level is outside the valid range of 0 to 2"
// *Cause: An invalid security_level value was specified.
// *Action: Specify a valid range of 0 to 2.
/
29473, 00000, "privilege checking level specified for '%s' must be between 0 and 2"
// *Cause: Invalid privilege checking level specified.
// *Action: Correct the privilege checking level specified.
/
29474, 00000, "DBMS_SQL.OPEN_CURSOR failed. security_level of 0 is not allowed"
// *Cause: Security level of 0 is specified with DBMS_SQL.OPEN_CURSOR.
// *Action: Specify a valid security level.
29475, 00000, "useLogonRoles=>TRUE not permitted with userid=>NULL"
// *Cause: An unsupported combination of argument values was present in a call
// to DBMS_SYS_SQL.PARSE_AS_USER.
// *Action: Specify a valid combination of argument values.
29476, 00000, "DBMS_SQL.CLOSE_CURSOR failed"
// *Cause: An attempt was made to close a DBMS_SQL cursor while it was
// executing under its own context.
// *Action: Rewrite the program so that it does not attempt to close a
// DBMS_SQL cursor while it is executing under its own context.
29477, 00000, "SQL statement size in bytes is too big"
// *Cause: The size of the SQL statement exceeded 4 gigabytes -1.
// *Action: Reduce the size of the SQL statement.
29478, 00000, "Implicit result cannot be returned through this statement."
// *Cause: An attempt was made to return an implicit result through a
// statement type other than a PL/SQL or DML statement.
// *Action: Implicit results can only be returned through a PL/SQL or DML
// statement.
29479, 00000, "Cannot return any more implicit results, limit 2,147,483,647 reached."
// *Cause: An attempt was made to return more than the maximum number of
// implicit results permitted.
// *Action: Ensure the number of implicit results does not exceed
// 2,147,483,647.
29480, 00000, "No more implicit results to retrieve."
// *Cause: An attempt was made to retrieve implicit results when none were
// available.
// *Action: This is an internal error.
29481, 00000, "Implicit results cannot be returned to client."
// *Cause: An attempt was made to return implicit results to an older version
// client that is not capable of receiving these implicit results.
// *Action: Upgrade the Oracle Database Client software.
/
29482, 00000, "Cannot specify both userid or username and xs_sessionid"
// *Cause: An unsupported combination of argument values was present in a call
// to DBMS_SYS_SQL.PARSE_AS_USER.
// *Action: Specify a valid combination of argument values.
/
29483, 00000, "Cannot specify both userid and username"
// *Cause: An unsupported combination of argument values was present in a call
// to DBMS_SYS_SQL.PARSE_AS_USER.
// *Action: Specify a valid combination of argument values.
/
29484, 00000, "Cannot specify both xs_sessionid and useLogonRoles=>TRUE"
// *Cause: An unsupported combination of argument values was present in a call
// to DBMS_SYS_SQL.PARSE_AS_USER.
// *Action: Specify a valid combination of argument values.
/
29485, 00000, "Complex type bind or define is not a linked type."
// *Cause: A complex type bound or defined in one container, where cursor
// execution occurs in another container, was not an object or
// metadata linked type.
// *Action: Verify that all complex types that are bound or defined in one
// container while execution occurs in another container are
// object or metadata linked types.
/
/ 29490 - 29499 RESERVED FOR THE DBMS_PARALLEL_EXECUTE PACKAGE
/
29490, 00000, "insufficient privilege"
// *Cause: The ADM_PARALLEL_EXECUTE role needed to execute the subprogram was not granted.
// *Action: Obtain ADM_PARALLEL_EXECUTE role and try again.
/
29491, 00000, "invalid table for chunking"
// *Cause: An attempt was made to chunk a table by ROWID, but the table was not a physical table or the table was an IOT.
// physical table or the table is an IOT.
// *Action: Use a table which has physical ROWID.
/
29492, 00000, "invalid state for create chunk"
// *Cause: An attempt was made to create chunks on a task which was not in the CREATED state.
// *Action: Make sure that the task is in the CREATED state.
/
29493, 00000, "invalid status"
// *Cause: An attempt was made to set an invalid value to the chunk status.
// *Action: Make sure that the status value is valid.
/
29494, 00000, "invalid state for run task"
// *Cause: An attempt was made to execute the task which was not in the CHUNKED state.
// *Action: Make sure that the task is in the CHUNKED state.
/
29495, 00000, "invalid state for resume task"
// *Cause: An attempt was made to resume execution but the task was not the FINISHED_WITH_ERROR or CRASHED state.
// *Action: Make sure that the task is in the FINISHED_WITH_ERROR or CRASHED
// state.
/
29496, 00000, "Parameter [%s] is null or its value length exceeds the maximum limit [%s]"
// *Cause: The input argument was null, or it exceeded the maximum length limit.
// *Action: Make sure that the argument is not null, and its length is within the limit.
/
29497, 00000, "duplicate task name"
// *Cause: A task with the same name was already in existence.
// *Action: Use another name.
/
29498, 00000, "task not found"
// *Cause: The task did not exist.
// *Action: Use an existing task.
/
29499, 00000, "chunk not found"
// *Cause: The specified chunk did not exist.
// *Action: Specify an existing chunk.
/
/ 29500 - 29699 Reserved for DDL and other integration for
/ embedding Aurora group's Java VM in the server
/
29500, 00000, "NAMED keyword is invalid in CREATE JAVA CLASS"
// *Cause: A NAMED keyword was specified in the CREATE JAVA CLASS
// statement. NAMED keywords are valid only in CREATE JAVA
// SOURCE or RESOURCE statements.
// *Action: Remove the NAMED keyword from the CREATE JAVA
// CLASS statement.
/
29501, 00000, "invalid or missing Java source, class, or resource name"
// *Cause: The required name for a Java source, class, or resource
// was invalid or missing.
// *Action: Specify a valid name.
/
29502, 00000, "NAMED keyword required in CREATE JAVA RESOURCE"
// *Cause: The name for a Java resource was not specified. The name
// must be specified with the NAMED keyword.
// *Action: Specify a valid name with the NAMED keyword.
/
29503, 00000, "SCHEMA keyword not valid with NAMED keyword"
// *Cause: SCHEMA and NAMED keywords were used together in the same
// CREATE JAVA command, but only one may be used in a
// CREATE JAVA command.
// *Action: Remove either the NAMED or the SCHEMA keyword.
/
29504, 00000, "invalid or missing schema name"
// *Cause: The required schema name was invalid or missing.
// *Action: Specify a valid schema name.
/
29505, 00000, "AS keyword is invalid in CREATE JAVA CLASS or RESOURCE"
// *Cause: The AS keyword was used in CREATE JAVA CLASS or RESOURCE.
// The AS keyword is valid only in CREATE JAVA SOURCE.
// *Action: Use the USING keyword in CREATE JAVA CLASS or RESOURCE.
/
29506, 00000, "invalid query derived from USING clause"
// *Cause: The USING clause did not form a valid query.
// *Action: Correct the USING clause.
/
29507, 00000, "query derived from USING clause found zero or many rows"
// *Cause: The USING clause defined a query that either did not return any
// values, or returned more than one value.
// *Action: Correct the USING clause.
/
29508, 00000, "query derived from USING clause did not select a value of type %s"
// *Cause: The USING clause did not form a query that selects a value of
// the type specified by the term following the USING keyword.
// *Action: Correct the USING clause.
/
29509, 00000, "incorrectly formed Java binary class definition"
// *Cause: An attempt was made to create a Java class using data expected
// to be in binary (Java .class) format. The data was found not
// to be in this format, or to be incorrectly formed.
// *Action: Correct the definition data.
/
29510, 00000, "name, %s.%s, already used by an existing object"
// *Cause: A CREATE JAVA command attempted to create a source, class,
// or resource object with a name that is already in use.
// *Action: Drop the existing object that is using the desired name,
// or use a different name for the new object.
/
29511, 00000, "could not resolve Java class"
// *Cause: A CREATE AND RESOLVE NOFORCE JAVA CLASS command specified
// definition data that could not be resolved, or resolution
// failed for some referenced class.
// *Action: Remove the NOFORCE option or remove impediments to resolution.
/
29512, 00000, "incorrectly formed name resolver specification"
// *Cause: A name resolver was not specified in the required
// form: (( <name pattern> , <schema name>) ...)
// *Action: Correct the specification.
/
29513, 00000, "referenced class name too long"
// *Cause: An attempt was made to import a .class file containing a
// class name of length greater than %d. The .class file
// could not be imported because the referenced class name
// was too long.
// *Action: Shorten the referenced class name in the .class file.
/
29514, 00000, "class name contains illegal character"
// *Cause: An attempt was made to import a .class file containing a
// character that cannot be converted to the server character
// set. The .class file could not be imported because of the
// illegal character.
// *Action: Correct the illegal character in the .class file.
/
29515, 00000, "exit called from Java code with status %s"
// *Cause: Java code included a call to
// java.lang.Runtime.exitInternal.
// *Action: Do not include this call unless non-local exit is desired.
/
29516, 00000, "Aurora assertion failure: %s"
// *Cause: An internal error occurred in the Aurora module.
// *Action: Contact Oracle Worldwide Support.
/
29517, 00000, "recursive resolution failed for a referenced class"
// *Cause: An attempt to resolve a referenced class failed.
// *Action: Review the errors for referenced classes and complete the
// necessary actions to correct them.
/
29518, 00000, "name %s resolved to an object in schema %s that is not a Java class"
// *Cause: A referenced name was resolved to an object that is not
// a Java class.
// *Action: Adjust name resolver or add missing Java class.
/
29519, 00000, "name %s resolved via a synonym in schema %s to a class with a different name"
// *Cause: A referenced name was resolved to a synonym, which translated to
// a class whose name does not match the referenced name.
// *Action: Adjust name resolver or add missing Java class.
/
29520, 00000, "name %s resolved to a class in schema %s that could not be accessed"
// *Cause: An attempt to access a referenced class failed.
// *Action: Adjust authorizations or name resolution.
/
29521, 00000, "referenced name %s could not be found"
// *Cause: Name resolution failed to find an object with the indicated name.
// *Action: Adjust name resolver or add missing Java class.
/
29522, 00000, "authorization error for referenced name %s.%s"
// *Cause: An attempt was made to resolve a class that is not authorized
// to use the indicated referenced class.
// *Action: Adjust authorizations or name resolution.
/
29523, 00000, "authorization error for unknown referenced name"
// *Cause: An attempt was made to resolve a class that is not authorized
// to use a referenced class. The name of the referenced class
// could not be determined.
// *Action: Adjust authorizations or name resolution.
/
29524, 00000, "wrong types of arguments in call to '%s'"
// *Cause: A method was called with argument(s) of incompatible type(s).
// *Action: Adjust caller.
/
29525, 00000, "referenced name is too long: '%s'"
// *Cause: An attempt was made to create a class that references a name
// longer than 4000 characters. The class could not be created
// because the name is too long.
// *Action: Adjust the definition.
/
29526, 00000, "created Java class %s\"%s\""
// *Cause: An informational message, not an error.
// *Action: None.
/
29527, 00000, "created Java source %s\"%s\""
// *Cause: An informational message, not an error.
// *Action: None.
/
29528, 00000, "invalid Java call in trigger %s"
// *Cause: The Java method specified in trigger does not exist or cannot be
// called as used.
// *Action: Adjust trigger definition.
/
29529, 00000, "invalid function or method call %s in trigger %s"
// *Cause: The function or method specified in Java trigger call expression
// could not be resolved.
// *Action: Adjust trigger definition.
/
29530, 00000, "could not create shortened name for %s"
// *Cause: Insert into shortened name translation table failed.
// *Action: Retry the insert.
/
29531, 00000, "no method %s in class %s"
// *Cause: An attempt was made to execute a non-existent method in a
// Java class.
// *Action: Adjust the call or create the specified method.
/
29532, 00000, "Java call terminated by uncaught Java exception: %s"
// *Cause: A Java exception or error was signaled and could not be
// resolved by the Java code.
// *Action: Modify Java code, if this behavior is not intended.
/
29533, 00000, "attempt to overwrite class or resource %s while defining or compiling %s.%s"
// *Cause: A class or resource defined by a SQLJ source conflicted with an existing object.
// *Action: Remove existing object, or modify SQLJ source.
/
29534, 00000, "referenced object %s.%s could not be resolved"
// *Cause: Name resolution determined that the indicated object is referenced
// but could not be resolved.
// *Action: Correct name resolver or address resolution problems in the
// referenced class, or correct compilation problems in its source.
/
29535, 00000, "source requires recompilation"
// *Cause: The reason the current class object was invalid is recorded
// with the source object from which it was compiled.
// *Action: Inspect errors in the source object and take the necessary
// corrective actions.
/
29536, 00000, "badly formed source: %s"
// *Cause: An attempt was made to create a Java source object with text
// that could not be parsed adequately to determine the class(es)
// defined by it.
// *Action: Correct errors in source.
/
29537, 00000, "class or resource cannot be created or dropped directly"
// *Cause: An attempt was made to create or drop a Java class or resource that
// is known to result from compilation of an existing Java source object.
// *Action: Act on the class or resource by acting on the source, or change
// the source so that it no longer defines the class or resource.
/
29538, 00000, "Java not installed"
// *Cause: An attempt was made to use a Java command when Java is not installed.
// *Action: Install Java, or do not use the command.
/
29539, 00000, "Java system classes already installed"
// *Cause: An attempt was made to use the CREATE JAVA SYSTEM command in a
// database where the Java system classes already are installed.
// *Action: Use CREATE OR REPLACE JAVA SYSTEM.
/
29540, 00000, "class %s does not exist"
// *Cause: Java method execution failed to find a class with the indicated name.
// *Action: Correct the name or add the missing Java class.
/
29541, 00000, "class %s.%s could not be resolved"
// *Cause: An attempt was made to execute a method in a Java class
// that had not been previously and cannot now be compiled
// or resolved successfully.
// *Action: Adjust the call or make the class resolvable.
/
29542, 00000, "class %s already defined by source %s"
// *Cause: An attempt was made to create a Java source object that
// would define a class that is already defined by a different
// Java source object.
// *Action: Either drop the old source or modify the new source.
/
29543, 00000, "Java command %s not yet implemented"
// *Cause: An attempt was made to use a Java command that is
// not yet implemented.
// *Action: Do not use the command.
/
29544, 00000, "invalid type"
// *Cause: The type argument in a call to a Java export or import command
// did not have a recognized value.
// *Action: Correct the value.
/
29545, 00000, "badly formed class: %s"
// *Cause: An attempt was made to create a Java class object with bytecodes
// that were rejected by the Java verifier.
// *Action: It is possible that an attempt was made to create the Java class
// from a damaged class file, in which case the CREATE should be
// reattempted with a correct class file. It is also possible that
// the message is the result of using "-" in the resolver so that
// the verifier could not check the correctness of some code. In
// that case, the class needs to be created with a resolver.
/
29546, 00000, "badly formed resource: %s"
// *Cause: An attempt was made to create a Java resource object with data
// that was rejected by the Java verifier.
// *Action: Correct the data.
/
29547, 00000, "Java system class not available: %s"
// *Cause: An attempt was made to use a command that requires a Java system
// class that was not yet present or was invalid.
// *Action: Load the system classes, or do not use the command.
/
29548, 00000, "Java system class reported: %s"
// *Cause: A command that uses a Java system class was aborted due to an
// error reported by the Java system class.
// *Action: Correct the error that was reported.
/
29549, 00000, "class %s.%s has changed, Java session state cleared"
// *Cause: A class in use by the current session was redefined or dropped,
// invalidating the current Java session state and requiring that
// it be cleared.
// *Action: No action required.
/
29550, 00000, "Java session state cleared"
// *Cause: The Java state in the current session became inconsistent and
// was cleared.
// *Action: No action required.
/
29551, 00000, "could not convert %s to Unicode"
// *Cause: A string in the database character set could not be converted
// to Unicode, as required for use by Java.
// *Action: Correct the string.
/
29552, 00000, "verification warning: %s"
// *Cause: An attempt was made to create a Java class object with bytecodes
// that caused the Java verifier to issue a warning.
// *Action: It is possible that the Java class was created from a damaged
// class file, in which case the CREATE should be reattempted
// with a correct class file. It is also possible that the message
// is the result of using "-" in the resolver so that the verifier
// could not check the correctness of some code. In that case, the
// class needs to be created with a resolver.
/
29553, 00000, "class in use: %s.%s"
// *Cause: An attempt was made to modify a Java class that is in use in the
// current call.
// *Action: Correct the code in use in this call.
/
29554, 00000, "unhandled Java out of memory condition"
// *Cause: The session encountered an out of memory condition in Java
// from which it could not recover. Java session state was cleared.
// *Action: No action required.
/
29555, 00000, "Java source, class or resource is not allowed here"
// *Cause: A Java source, class, or resource was specified in an
// inappropriate place in a statement.
// *Action: Make sure the name is correct or remove it.
/
29556, 00000, "object type has changed"
// *Cause: A database object name that named a Java source, class, or resource
// now names an object of a different type.
// *Action: No action required.
/
29557, 00000, "Java system class %s cannot be modified"
// *Cause: A command was attempted that would have modified a Java system class.
// *Action: No action required.
/
29558, 00000, "JAccelerator (NCOMP) not installed. Refer to Install Guide for instructions."
// *Cause: JAccelerator (NCOMP) is not installed.
// *Action: Please refer to the Post-installation Tasks section in the
// Database Install Guide for instructions on how to install
// JAccelerator (NCOMP).
/
29561, 00000, "Java VM JIT not supported on this platform."
// *Cause: Java VM JIT is not supported on this platform.
// *Action: No action required.
/
29655, 00000, "USING clause is incompatible with its supertype"
// *Cause: The USING clause of a type has to be the same as its supertype or
// compatible with it.
// *Action: Make sure the USING clause is compatible with its supertype.
/
29656, 00000, "Invalid option for USING"
// *Cause: The class has to implement the required interface for the value
// of the option for USING.
//
// *Action: Make sure the USING clause is supported.
/
29657, 00000, "class defined in EXTERNAL NAME clause is used in another subtype"
// *Cause: The supertype has an existing type that has the same value
// for the EXTERNAL NAME.
// *Action: Make sure the EXTERNAL NAME clause is unique among subtypes.
/
29658, 00000, "EXTERNAL NAME clause is not compatible with its supertype"
// *Cause: The EXTERNAL NAME clause of the type is not a subclass of the
// supertype EXTERNAL NAME.
// *Action: Make sure the EXTERNAL NAME clause of the type is a subclass of
// the EXTERNAL NAME of its supertype.
/
29659, 00000, "SQLJ Object Type validation failed to get default connection"
// *Cause: Unable to connect using the JDBC default connection.
//
// *Action: No action required.
/
29660, 00000, "Unable to find the class defined in the EXTERNAL NAME clause"
// *Cause: The class is not loaded in the database.
//
// *Action: Make sure the EXTERNAL NAME corresponds to a loaded class in the
// the database.
/
29661, 00000, "Unable to find the superclass of the defined in the EXTERNAL NAME"
// *Cause: The class is not loaded in the database.
//
// *Action: Make sure the superclass of the EXTERNAL NAME is loaded in the
// the database.
/
29662, 00000, "Unable to find a field that matches one or more of the attributes"
// *Cause: The EXTERNAL NAME option of one or more attributes do not match
// any fields in the defined class.
//
// *Action: Make sure the EXTERNAL NAME option of each attribute matches
// a field in the defined in the defined class.
/
29663, 00000, "Unable to find a method that matches one or more of the functions"
// *Cause: The EXTERNAL NAME option of one or more functions do not match
// any method in the defined class.
//
// *Action: Make sure the EXTERNAL NAME option of each function matches
// a method in the defined in the defined class.
/
29664, 00000, "Unable to generate the helper class for the defined type"
// *Cause: The helper class used for supporting SQLJ Object Type is not
// generated.
//
// *Action: No Action is required.
/
29665, 00000, "Java thread deadlock detected"
// *Cause: The Java VM has detected a thread deadlock.
//
// *Action: Modify the Java program to avoid the deadlock condition.
/
/ 29700-29799 reserved for Global Enqueue Service
/
29701, 00000, "unable to connect to Cluster Synchronization Service"
// *Cause: Connect to CSS failed or timed out.
// *Action: Verify the state of the CSS. If the CSS was not started,
// start it and then retry the database startup. If the CSS died
// or is not responding, check the Oracle and CSS trace files for
// errors and contact Oracle Support Services.
29702, 00000, "error occurred in Cluster Group Service operation"
// *Cause: An unexpected error occurred while performing a CGS operation.
// *Action: Verify that the LMON process is still active.
// Check the Oracle LMON trace files for errors.
// Also, check the related CSS trace file for errors.
29703, 00000, "error occurred in global enqueue service operation"
// *Cause: An unexpected error occurred while performing a global enqueue
// service operation.
// *Action: Check oracle trace files for errors.
29704, 00000, "cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release"
// *Cause: The ACTIVE_INSTANCE_COUNT parameter was specified when one of the
// instances in the cluster was running Oracle 8.1.5 or an earlier
// release.
// *Action: Restart the instance without specifying the ACTIVE_INSTANCE_COUNT
// parameter. Or, upgrade all instances to Oracle 8.1.6 or later
// release and then specify the parameter.
29705, 00000, "ACTIVE_INSTANCE_COUNT is %s which is incompatible with the value in other instances"
// *Cause: The value of the ACTIVE_INSTANCE_COUNT parameter must be the same
// in all Oracle cluster database instances.
// *Action: Check your initialization parameter files in all instances and
// ensure that the ACTIVE_INSTANCE_COUNT parameter has the same value.
// Then restart the instance.
29706, 00000, "incorrect value %s for parameter ACTIVE_INSTANCE_COUNT"
// *Cause: The ACTIVE_INSTANCE_COUNT parameter must be set to 1 in a two
// node cluster database configuration or unspecified if a secondary
// instance is not needed.
// *Action: Check your initialization parameter files and correct the value
// of the ACTIVE_INSTANCE_COUNT parameter. If you are configuring a
// two node primary/secondary cluster database, set this value to 1.
// Otherwise, do not specify any value for the parameter.
29707, 00000, "inconsistent value %s for initialization parameter %s with other instances"
// *Cause: The value of the initialization parameter in error must be
// identical on all Oracle cluster database instances and was not.
// *Action: Check your INIT.ORA files on all instances and ensure that the
// initialization parameters in error have the same value.
29708, 00000, "error occurred in Cluster Synchronization Services"
// *Cause: An unexpected error occurred while performing a CSS operation.
// *Action: Verify the state of the CSS. If the CSS died or
// is not responding, check the ORACLE and CSS trace
// files for errors and contact Oracle Support Services.
29709, 00000, "Communication failure with Cluster Synchronization Services"
// *Cause: Could not communicate with CSS to complete the operation.
// *Action: Verify the state of the CSS. If the CSS died or
// is not responding, check the ORACLE and CSS trace
// files for errors and contact Oracle Support Services.
29710, 00000, "Current operation aborted by Cluster Synchronization Services"
// *Cause: The operation could not be performed or CSS was shutting down.
// *Action: Check the log file of Cluster Synchronization Services daemon
// to verify the state of the service. Start the service if needed;
// otherwise, contact Oracle Support Services.
29711, 00000, "error occurred during registration of Oracle process with CSS"
// *Cause: An unexpected error occurred while performing a Cluster
// Synchronization Services (CSS) operation.
// *Action: Confirm that the database, and any ASM instances on which it
// depends, is operating normally. An outage in one of these can
// cause this error and it is an expected result. Otherwise, contact
// Oracle Support Services.
29712, 00000, "enable global enqueue service cancel event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue service cancel.
29713, 00000, "enable global enqueue service close event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue service close.
29714, 00000, "enable global enqueue service state object event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue service state object.
29715, 00000, "enable global enqueue internal error checking event"
// *Document: NO
// *Cause:
// *Action: check for internal errors in global enqueue service
29717, 00000, "enable global resource directory freeze/unfreeze event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for global resource directory freeze/unfreeze.
29718, 00000, "enable global enqueue service CGS interface event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue service CGS interface.
29719, 00000, "enable IMR split brain test event"
// *Document: No
// *Cause:
// *Action: Enable specific test scenerios for various split brain tests
29720, 00000, "enable global enqueue service SCN service event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue service SCN service.
29722, 00000, "enable global enqueue service process death event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue service process death.
29723, 00000, "Failed to attach to the global enqueue service (status=%s)"
// *Document: NO
// *Cause:
// *Action:
29724, 00000, "enable global enqueue heartbeat and CSS/GIPC event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for global enqueue heartbeat operations and CSS/GIPC
29725, 00000, "KA tracing"
// *Document: NO
// *Cause:
// *Action: Enable trace and field levels for KA diagnostics
29730, 00000, "use global enqueue converts to determine highest held mode"
// *Document: NO
// *Cause:
// *Action: Use global enqueue converts instead of inquiry messages to
// obtain highest held mode of a resource.
29733, 00000, "enable multiple recovery domains event trace"
// *Document: NO
// *Cause:
// *Action: Dump trace for ges/gcs multiple recovery domains
29735, 00000, "instance specified no longer exists"
// *Cause: A client of the global enqueue service specified an instance
// that no longer existed.
// *Action: Process aborts current operation due to termination of
// an instance
29736, 00000, "Instances running in the cluster are only read-mostly or read-only instances."
// *Cause: The instances that were running were only read-mostly or read-only instances
// which causes the whole cluster to shut down.
// *Action: Start the regular read/write instances and then restart
// read-mostly or read-only instances.
29737, 00000, "statement not allowed for read-mostly instances"
// *Document: NO
// *Cause:
// *Action:
29738, 00000, "This feature is not allowed on read-mostly instances."
// *Cause: The attempted feature was not allowed on read-mostly instances.
// *Action: The feature is not supported on read-mostly instances
// as this can be achieved on the other cluster instances which
// are not read-mostly.
29739, 00000, "Read-mostly and Read-only instances cannot be part of same cluster"
// *Cause: The Read-mostly and Read-only instances were part of the same cluster.
// *Action: Start the instance using an instance mode of the already existing
// Read-only Instance Mode nodes.
29740, 00000, "evicted by instance number %s, group incarnation %s"
// *Cause: This instance was evicted from the group by another instance of the
// cluster database group for one of several reasons, which may
// include a communications error in the cluster and failure to issue
// a heartbeat to the control file.
// *Action: Check the trace files of other active instances in the cluster
// group for indications of errors that caused a reconfiguration.
29741, 00000, "IMR active for some, but not all members of cluster"
// *Cause: The IMR feature is not active for this instance, but is active
// for another instance in the cluster database.
// *Action: Ensure that all instances have the same value for the _imr_active
// init.ora parameter
29742, 00000, "incompatible Instance Membership Recovery protocol among instances"
// *Cause: The selected Instance Membership Recovery protocol was not
// compatible with other running instances in the cluster database.
// *Action: Check the Instance Membership Recovery initialization parameters
// of all instances to ensure their consistency.
29743, 00000, "exiting from instance membership recovery protocol because this instance is not in good health"
// *Cause: This instance did not participate in the instance membership
// recovery protocol because it was not in good health. Some or all
// of its receivers were not making progress. Therefore, this instance
// terminated itself.
// *Action: Check the alert log, LMON and LMHB trace files for any errors and
// contact Oracle Support Services
29745, 00000, "Perform IMR test"
// *Document: NO
// *Cause:
// *Action: Simulate various scenarios for IMR testing.
29746, 0000, "Cluster Synchronization Service is being shut down."
// *Cause: The administrator has shut down the Cluster Synchronization
// Service daemon. This error message is intended to be informative
// to users on the status of the service.
// *Action: Check the log file of the Cluster Synchronization Service daemon
// to verify the state of the service.
29748, 00000, "Cluster Group Service Communication Trace Event"
// *Document: NO
// *Cause: Communication Layer and Group Sync Layer are tracing so much
// information together.
// *Action: Trace only the Communication Layer when this event is set in the
// init.ora parameter file.
29749, 00000, "Cluster Group Service Membership Trace Event"
// *Document: NO
// *Cause: Communication Layer and Group Sync Layer are tracing so much
// information together.
// *Action: Trace only the Group Sync Layer when this event is set in the
// init.ora parameter file.
29750, 00000, "enable CGS name service event trace"
// *Document: NO
// *Cause:
// *Action: Dump CGS name service tracing
29760, 00000, "instance_number parameter not specified"
// *Cause: The init.ora file did not contain a value for the instance_number
// which is required to identify this instance to other instances of
// the database running on the same cluster
// *Action: Assign a value to the instance_number parameter in the init.ora
// parameter file
29770, 00000, "global enqueue process %s (OSID %s) is hung for more than %s seconds"
// *Cause: The specified process mades no progress within the maximum
// allowed time.
// *Action: Check the alert file and relevent trace files and
// contact Oracle Support Services with the incident information.
29771, 00000, "process %s (OSID %s) blocks %s (OSID %s) for more than %s seconds"
// *Cause: The specified process blocked a global enqueue process for
// the maximum allowed time.
// *Action: Check the alert file and relevent trace files and contact
// Oracle Support Services with the incident information.
29775, 00000, "GCR Tracing"
// *Document: NO
// *Cause:
// *Action: Enable trace and field levels for GCR diagnostics.
/
/ 29780 -29789 Reserved for Gpnp Generic modules
/
29780, 00000, "unable to connect to GPnP daemon [%s]"
// *Cause: Attempt to connect to the GPnP deamon failed with the error
// reported.
// *Action: Take the corrective action to resolve the error reported. Refer
// to GPnP logs and documentation to figure out why the call
// failed.
29781, 00000, "invalid GPnP attribute [%s]"
// *Document: NO
// *Cause: The GPnP attribute specified was not recognized as a valid
// attribute.
// *Action: Correct the attribute type and retry the operation.
29782, 00000, "GPnP operation failed with error [%s]"
// *Document: NO
// *Cause: The GPnP operation failed with the specified error.
// *Action: Contact Oracle Support Services.
29783, 00000, "GPnP attribute SET failed with error [%s]"
// *Cause: An attempt to set the Grid Plug and Play (GPnP) attribute failed.
// See the brackets for the reason.
// *Action: Resolve the problem in the included message and retry the request.
29784, 00000, "Attribute update operation not permitted"
// *Cause: The update operation for attributes was not permitted because
// Cluster Synchronization Services (CSS) was not running on the
// host.
// *Action: Start Cluster Synchronization Services (CSS) and retry the
// operation.
29785, 00000, "GPnP attribute GET failed with error [%s]"
// *Cause: An attempt to get the Grid Plug and Play (GPnP) attribute failed.
// See the brackets for the reason.
// *Action: Resolve the problem in the included message and retry the request.
29786, 00000, "Oracle Restart attribute GET failed with error [%s]"
// *Cause: An attempt to get the Oracle Restart
// attribute failed. See the brackets for the reason.
// *Action: Resolve the problem in the included message and retry the request.
29787, 00000, "Oracle Restart attribute SET failed with error [%s]"
// *Cause: An attempt to set the Oracle Restart
// attribute failed. See the brackets for the reason.
// *Action: Resolve the problem in the included message and retry the request.
29788, 00000, "Network interface query failed with error [%s]"
// *Cause: Attempt to get the network information failed.
// See the brackets for the reason.
// *Action: Resolve the problem in the included message and retry the request.
29789, 00000, "internal test event"
// *Document: NO
// *Cause: This is an internal test event. Set only under guidance of
// development.
// *Action: Follow up with the Oracle Support Services using the traces
// generated by this event.
/
29790, 00000, "Cannot change user session parameters for a non-user session"
// *Cause: An attempt was made to change user session parameters for a
// non-user session.
// *Action: Execute the operation when connected with a user session
//
29791, 00000, "Transactions cannot be replayed"
// *Cause: The user attempted to replay a transaction.
// *Action: Reconnect and re-execute the transaction.
//
29797, 00000, "Enable AC performance optimization, only for internal testing"
// *Document: NO
// *Cause:
// *Action:
29798, 00000, "Dump diagnostics for HA only during internal testing."
// *Document: NO
// *Cause:
// *Action:
29799, 00000, "crash for soft assert macros in global enqueue service layer"
// *Document: NO
// *Cause:
// *Action:
/ 29800 - 29999 Reserved for Extensible Indexing project
/
/ sub-ranges 29800 - 29824 Operator DDL
/ 29825 - 29849 Indextype DDL
/ 29850 - 29874 Index DDL
/ 29875 - 29899 Index DML
/ 29900 - 29924 Query
/ 29925 - 29999 Optimizer & common errors
/
29800,00000, "invalid name for operator"
// *Cause: The name specified for the operator is incorrect.
// *Action: Specify a correct name for the operator.
29801,00000, "missing RETURN keyword"
// *Cause: The RETURN keyword has not been specified.
// *Action: Specify the RETURN keyword or check the SQL statement.
29802,00000, "missing CONTEXT keyword"
// *Cause: The CONTEXT keyword has not been specified.
// *Action: Specify the CONTEXT keyword or check the SQL statement.
29803,00000, "missing ANCILLARY keyword"
// *Cause: The ANCILLARY keyword has not been specified.
// *Action: Specify the ANCILLARY keyword or check the SQL statement.
29804,00000, "missing DATA keyword"
// *Cause: The DATA keyword has not been specified.
// *Action: Specify the DATA keyword or check the SQL statement.
29805, 00000, "missing COLUMN keyword"
// *Cause: Keyword COLUMN is expected .
// *Action: Either specify the COLUMN keyword or specify another option.
29806,00000, "specified binding does not exist"
// *Cause: The operator binding which has been specified does not exist.
// *Action: Ensure that the operator binding that has been specified does
// exist.
29807,00000, "specified operator does not exist"
// *Cause: The operator which has been specified does not exist.
// *Action: Ensure that the operator that has been specified does exist.
29808,00000, "specified primary operator binding does not exist"
// *Cause: The specified binding for the primary operator does not exist.
// *Action: Ensure that the specified binding for the primary operator exists.
29809,00000, "cannot drop an operator with dependent objects"
// *Cause: The operator which is being dropped has some dependent objects.
// *Action: Either drop the dependent objects first and then issue the DROP
// OPERATOR command or specify the FORCE option with DROP OPERATOR.
29810,00000, "inadequate operator privileges"
// *Cause: The user does not have the appropriate privileges to perform the
// specified operation on the operator.
// *Action: Grant the appropriate privileges to the user and then reissue the
// statement.
29811,00000, "missing STATISTICS keyword"
// *Cause: This is not a valid option with the ASSOCIATE command.
// *Action: Specify STATISTICS keyword after the ASSOCIATE command.
29812,00000, "incorrect object name specified"
// *Cause: The specified name is not a valid name.
// *Action: Specify the correct name of the object with for which an
// association needs to be defined.
29813,00000, "non-supported object type with associate statement"
// *Cause: The type of object specified is not supported with the associate
// statistics statement.
// *Action: Use a valid object type with the associate command.
29814,00000, "expecting USING or DEFAULT keyword"
// *Cause: Expecting the USING or DEFAULT keyword after the names of object(s).
// *Action: Provide the USING or DEFAULT keyword.
29815,00000, "object being associated is not present"
// *Cause: The object for which the association is being defined is not
// present.
// *Action: Ensure that all the objects for which the association is being
// defined are present.
29816,00000, "object being disassociated is not present"
// *Cause: Object which is being disassociated is not present.
// *Action: Ensure that the object which needs to be disassociated is
// present.
29817,00000, "non-supported option with disassociate statement"
// *Cause: The type of object specified is not supported with the disassociate
// statistics statement.
// *Action: Use a object type which is supported with the disassociate command.
29818,00000, "column name not properly specified"
// *Cause: Name of the column should contain the table and the column name.
// *Action: Specify a valid column name.
29819,00000, "cannot associate default values with columns"
// *Cause: User tried to associate DEFAULT values with columns which is not
// a valid option .
// *Action: Specify a valid option.
29820,00000, "the statistics type is not present"
// *Cause: The statistics type which is being associated with object(s) is
// not present.
// *Action: Ensure that the type which contains the statistics functions is
// present.
29821,00000, "specified primary operator does not exist"
// *Cause: The specified primary operator does not exist.
// *Action: Check the primary operator and the signature specified.
29822,00000,"selectivity cannot be specified for the type of object"
// *Cause: User tried to associate selectivity with index or indextypes which
// is not allowed .
// *Action: Specify a valid option.
29823,00000,"object being analyzed is not a table "
// *Cause: The object being analyzed is not a table and is not supported
// *Action: Specify only a supported option.
29824,00000, "operator is invalid"
// *Cause: The operator is invalid.
// *Action: Drop and recreate the operator.
29825, 00000, "invalid name for indextype"
// *Cause: Indextype name or Indextype schema name has invalid characters.
// *Action: Verify that the name has valid characters and it is not a reserved
// word.
29826, 00000, "keyword FOR is missing"
// *Cause: FOR keyword must be provided with Create Indextype statement.
// *Action: Use FOR keyword and provide relevant operator information.
29827, 00000, "keyword USING is missing"
// *Cause: USING keyword and corresponding implementation details must be provided.
// *Action: Provide USING keyword and relevant implementation details with Create
// Indextype statement.
29828, 00000, "invalid name for implementation type"
// *Cause: Implementation type or Implementation schema name is invalid.
// *Action: Verify that the name has valid characters and it is not a reserved
// word.
29829, 00000, "implementation type does not exist"
// *Cause: The implementation type specified with USING clause could not
// be found.
// *Action: Check to see if the type exists and the user has EXECUTE
// privilege on this type.
29830, 00000, "operator does not exist"
// *Cause: The operator could not be found.
// *Action: Verify that the operator exists and the user has EXECUTE
// privilege for this operator.
29831, 00000, "operator binding not found"
// *Cause: The specified binding for the operator is not available
// from the operator schema object.
// *Action: Verify that the operator with the specified binding exists.
29832, 00000, "cannot drop or replace an indextype with dependent indexes"
// *Cause: One or more indexes are dependent upon the indextype.
// *Action: Drop all the indexes which are dependent upon the indextype
// before dropping the indextype itself.
29833, 00000, "indextype does not exist"
// *Cause: There is no indextype by the specified name.
// *Action: Use public views for the indextypes to see if an
// indextype by the specified name has been created.
29834, 00000, "REF datatype not supported with operators"
// *Cause : The user specified a REF datatype which is not supported in CREATE
// OPERATOR.
// *Action: Reissue the CREATE OPERATOR statement without the REF datatype.
29835, 00000, "ODCIGETINTERFACES routine does not return required interface(s)"
// *Cause : The ODCIObjectList returned by the ODCIGetInterfaces routine
// does not contain the interface(s) required by the current usage.
// *Action : Ensure that the ODCIGetInterfaces routine returns the name(s)
// of the required interface(s).
29836, 00000, "failed to validate referenced operators"
// *Cause: One of the operators referenced cannot be compiled.
// *Action: Try to recompile the operators which are referenced by this
// indextype. Use USER_INDEXTYPE_OPERATORS view to find out the
// referenced operators.
29837, 00000, "insufficient privileges to execute implementation type"
// *Cause: User does not have privileges to execute the implementation type.
// *Action: The owner of the implementation type must grant appropriate
// privileges to the user.
29838, 00000, "insufficient privileges to execute the operator(s)"
// *Cause: User does not have privileges to execute one of the operators.
// *Action: The owner of the operators must grant appropriate privileges
// to the user .
29839, 00000, "failed to validate implementation type"
// *Cause: Implementation type cannot be compiled.
// *Action: Try to compile the implementation type.
29840, 00000, "indextype and implementation type are not in same schema"
// *Cause: Indextype and implementation type are in different schema.
// *Action: Put the indextype and implementation type in the same schema.
29841, 00000, "invalid option for ALTER INDEXTYPE"
// *Cause: The user specified an invalid option with the ALTER INDEXTYPE
// command
// *Action: Choose a valid option with the ALTER INDEXTYPE command
29842, 00000, "option not supported with the version %s of the indextype interface"
// *Cause : User specified an option which is not supported with the
// version of the indextype interface provided
// *Action: User should either not request for this option or should provide
// an implementation type that implements the correct version of the
// indextype interface.
29843, 00000, "indextype should support atleast one operator"
// *Cause : User attempted to drop all the operators from the indextype
// *Action : Do not drop all the operators from the indextype
29844, 00000, "duplicate operator name specified"
// *Cause : User attempted to add an operator name to an indextype which is already
// supported by the indextype
// *Action: Remove the duplicate operator and retry the command
29845, 00000, "indextype does not support local domain index on %s partitioned table"
// *Cause : User specified a create local domain index statement using an
// indextype that does not support local domain indexes on
// tables partitioned with the given method
// *Action: Use a different indextype or build a global domain index
29846, 00000, "cannot create a local domain index on a %s partitioned table"
// *Cause : User specified a create local domain index statement on a
// table partitioned using a method not supported by domain indexes
// *Action: Build a global domain index on the partitioned table
29847, 00000, "cannot create a local domain index on a partitioned index-organized table"
// *Cause : User specified a create local domain index statement on a
// partitioned index-organized table
// *Action: Build a global domain index on the partitioned index-organized
// table
29848, 00000, "error occurred in the execution of ODCIINDEXMERGEPARTITION routine"
// *Cause: Failed to successfully execute the ODCIIndexMergePartition routine.
// *Action: Check to see if the routine has been coded correctly.
29849, 00000, "error occurred in the execution of ODCIINDEXSPLITPARTITION routine"
// *Cause: Failed to successfully execute the ODCIIndexSplitPartition routine.
// *Action: Check to see if the routine has been coded correctly.
29850, 00000, "invalid option for creation of domain indexes"
// *Cause: The user specified an invalid option like ASC, DESC, SORT or a
// parallel clause, partitioning clause or physical attributes clause.
// *Action: Choose one of the valid clauses for creation of domain indexes.
29851, 00000, "cannot build a domain index on more than one column"
// *Cause: User attempted to build a domain index on more than one column.
// *Action: Build the domain index only on a single column.
29852, 00000, "keyword IS is missing"
// *Cause: IS keyword must be specified with Create Index statement for domain
// indexes.
// *Action: Use IS keyword and then specify the indextype name.
29853, 00000, "keyword UNIQUE may not be used in creating domain indexes"
// *Cause: An attempt was made to create a domain index with the
// UNIQUE attribute.
// *Action: Remove UNIQUE from the CREATE INDEX statement.
29854, 00000, "keyword BITMAP may not be used in creating domain indexes"
// *Cause: An attempt was made to create a domain index with the
// BITMAP attribute.
// *Action: Remove BITMAP from the CREATE INDEX statement.
29855, 00000, "error occurred in the execution of ODCIINDEXCREATE routine"
// *Cause: Failed to successfully execute the ODCIIndexCreate routine.
// *Action: Check to see if the routine has been coded correctly.
29856, 00000, "error occurred in the execution of ODCIINDEXDROP routine"
// *Cause: Failed to successfully execute the ODCIIndexDrop routine.
// *Action: Check to see if the routine has been coded correctly.
29857, 00000, "domain indexes and/or secondary objects exist in the tablespace"
// *Cause: An attempt was made to drop a tablespace which contains secondary
// objects and/or domain indexes.
// *Action: Drop the domain indexes in his tablespace. Also, find the domain
// indexes which created secondary objects in this tablespace and
// drop them. Then try dropping the tablespace.
29858, 00000, "error occurred in the execution of ODCIINDEXALTER routine"
// *Cause: Failed to successfully execute the ODCIIndexAlter routine.
// *Action: Check to see if the routine has been coded correctly.
29859, 00000, "error occurred in the execution of ODCIINDEXTRUNCATE routine"
// *Cause: Failed to successfully execute the ODCIIndexTruncate routine.
// *Action: Check to see if the routine has been coded correctly.
29860, 00000, "cannot truncate a table with domain indexes marked LOADING"
// *Cause: The table has domain indexes defined on it that are marked LOADING.
//* Action: Wait to see if the ongoing index DDL ends and the index state
// changes from LOADING state. Else ,drop the domain indexes marked as
// LOADING with the FORCE option.
29861, 00000, "domain index is marked LOADING/FAILED/UNUSABLE"
// *Cause: An attempt has been made to access a domain index that is
// being built or is marked failed by an unsuccessful DDL
// or is marked unusable by a DDL operation.
// *Action: Wait if the specified index is marked LOADING
// Drop the specified index if it is marked FAILED
// Drop or rebuild the specified index if it is marked UNUSABLE.
29862, 00000, "cannot specify FORCE option for dropping non-domain index"
// *Cause: A DROP INDEX FORCE was issued for a non-domain index.
// *Action: Reissue the command without the FORCE option.
29863, 00000, "warning in the execution of ODCIINDEXCREATE routine"
// *Cause: A warning was returned from the ODCIIndexCreate routine.
// *Action: Check to see if the routine has been coded correctly
// Check user specified log tables for greater detail.
29864, 00000, "analyzing domain indexes marked LOADING/FAILED not supported"
// *Cause: Tried to analyze a domain index which was marked as LOADING or
// FAILED.
// *Action: If the index was marked LOADING, wait till it is marked valid
// before retrying the analyze. If index was marked FAILED, drop it
// OR rebuild it and retry the analyze.
29865,00000, "indextype is invalid"
// *Cause: The indextype is invalid.
// *Action: Drop and recreate the indextype.
29866, 00000, "cannot create domain index on a column of index-organized table"
// *Cause: Tried to create a domain index on a column of an index-organized
// table.
// *Action: Do not attempt to create a domain index on columns of an
// index-organized table.
29867, 00000, "cannot create a domain index on a LONG column"
// *Cause: The user attempted to create a domain index on a column of LONG
// datatype.
// *Action: Do not create a domain index on a LONG column.
29868, 00000, "cannot issue DDL on a domain index marked as LOADING"
// *Cause: Tried to issue a DROP/ALTER/TRUNCATE on a domain index in a LOADING state.
// *Action: Wait till the index operation completes
// OR issue a DROP INDEX FORCE to drop the index.
29869, 00000, "cannot issue ALTER without REBUILD on a domain index marked FAILED"
// *Cause: Tried to issue a DROP/ALTER on a domain index in a FAILED state.
// *Action: Truncate the table to mark the index as valid
// OR do ALTER INDEX REBUILD to rebuild the index.
29870, 00000, "specified options are only valid for altering a domain index"
// *Cause: Specified the ONLINE or PARAMETERS clause with a non-domain index.
// *Action: Reissue the statement with the correct syntax for alter.
29871, 00000, "invalid alter option for a domain index"
// *Cause: The user specified an invalid option for altering a domain index.
// *Action: Reissue the alter statement with a valid option.
29872, 00000, "parameters clause cannot be combined with the specified options"
// *Cause: The user combined PARAMETERS clause with other alter index options.
// *Action: Reissue the statement with the correct syntax for alter.
29873, 00000, "warning in the execution of ODCIINDEXDROP routine"
// *Cause: A waring was returned from the ODCIIndexDrop routine.
// *Action: Check to see if the routine has been coded correctly
// Check the user defined warning log tables for greater details.
29874, 00000, "warning in the execution of ODCIINDEXALTER routine"
// *Cause: A waring was returned from the ODCIIndexAlter routine.
// *Action: Check to see if the routine has been coded correctly
// Check the user defined warning log tables for greater details.
29875, 00000, "failed in the execution of the ODCIINDEXINSERT routine"
// *Cause: Failed to successfully execute the ODCIIndexInsert routine.
// *Action: Check to see if the routine has been coded correctly.
29876, 00000, "failed in the execution of the ODCIINDEXDELETE routine"
// *Cause: Failed to successfully execute the ODCIIndexDelete routine.
// *Action: Check to see if the routine has been coded correctly.
29877, 00000, "failed in the execution of the ODCIINDEXUPDATE routine"
// *Cause: Failed to successfully execute the ODCIIndexUpdate routine.
// *Action: Check to see if the routine has been coded correctly.
29878, 00000, "warning in the execution of ODCIINDEXTRUNCATE routine"
// *Cause: A warning was returned from the ODCIIndexTruncate routine.
// *Action: Check to see if the routine has been coded correctly
// Check the user defined warning log tables for greater details.
29879, 00000, "cannot create multiple domain indexes on a column list using same indextype"
// *Cause: An attempt was made to define multiple domain indexes on the same
// column list using identical indextypes.
// *Action: Check to see if a different indextype can be used or if the index
// can be defined on another column list.
29880, 00000, "such column list already indexed using another domain index and indextype"
// *Cause: An attempt was made to create multiple domain indexes on a column
// list using indextypes which do not have disjoint operators.
// *Action: Check to see if the operator sets for the indextypes can be made
// disjoint.
29881, 00000, "failed to validate indextype"
// *Cause: Indextype cannot be compiled.
// *Action : Try to compile the indextype which is referenced by
// the domain index.
29882, 00000, "insufficient privileges to execute indextype"
// *Cause: User does not have privileges to execute the indextype.
// *Action: The owner of the indextype must grant appropriate
// privileges to the user.
29883, 00000, "cannot create a domain index on column expressions"
// *Cause : User specified an expression in the column list.
// *Action : Specify only simple columns in the column list for domain index.
29884, 00000, "domain index is defined on the column to be dropped"
// *Cause : An ALTER TABLE DROP COLUMN was issued on a column on which
// a domain index exists.
// *Action : Drop the domain index before attempting to drop the column.
29885, 00000, "domain index is defined on the column to be modified"
// *Cause : An ALTER TABLE MODIFY COLUMN was issued on a column on which
// a domain index exists.
// *Action: Drop the domain index before attempting to modify the column.
29886, 00000, "feature not supported for domain indexes"
// *Cause : Feature is not supported for domain indexes.
// *Action : No action required.
29887, 00000, "cannot support row movement if domain index defined on table"
// *Cause : An ALTER TABLE ENABLE ROW MOVEMENT was issued on a table which
// has a domain index defined on it.
// *Action : Drop the domain index if you want to enable row movement and
// then reissue the command.
29888, 00000, "cannot create domain index on a table with row movement enabled"
// *Cause : A create domain index statement was issued on a table that has
// row movement enabled.
// *Action : Disable the row movement in the table and then reissue the
// create domain index statement.
// NLS_DO_NOT_TRANSLATE[29889,29889]
29889, 00000, "allow a secondary object creation"
// *Document: NO
// *Cause: For internal use only
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED ONLY BY IMPORT CODE.
29890,00000, "specified primary operator does not have an index context"
// *Cause: The primary operator does not have an index and scan contexts.
// *Action: Create the primary operator with a context clause.
// NLS_DO_NOT_TRANSLATE[29891,29891]
29891, 00000, "enable debugging in ODCI user-defined routines"
// *Document: NO
// *Cause: For internal use only
// *Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE
// TRANSLATED OR DOCUMENTED. IT IS USED FOR SETTING A NEW EVENT FOR
// DEBUGGING SUPPORT IN ODCI USER-DEFINED ROUTINES
29892,00000, "indextypes with array DML do not support the given data type"
// *Cause: The user specified a REF or a LONG datatype which is not supported
// in CREATE/ALTER INDEXTYPE WITH ARRAY DML (DATA_TYPE, VARRAY_TYPE).
// *Action: Reissue the CREATE/ALTER INDEXTYPE statement without the REF or
// LONG datatype.
29893,00000, "indextypes without column data do not need the given data type"
// *Cause: WITH ARRAY DML (DATA_TYPE, VARRAY_TYPE) option and WITHOUT COLUMN
// DATA option conflicted in an alter indextype statement
// *Action: Reissue the ALTER INDEXTYPE statement without the conflict.
29894, 00000, "base or varray datatype does not exist"
// *Cause: One of the base and varray datatypes specified in WITH ARRAY DML
// (DATA_TYPE, VARRAY_TYPE) clause could not be found.
// *Action: Check to see if the datatype exists and the user has EXECUTE
// privilege on this datatype.
29895, 00000, "duplicate base datatype specified"
// *Cause : User attempted to add a base datatype to an indextype with ARRAY
// DML which is already supported by the indextype
// *Action: Remove the duplicate base datatype and retry the command
29896, 00000, "Length of PARAMETER string longer than %s characters"
// *Cause : An attempt was made to specify a parameter value that is
// longer than the allowed maximum.
// *Action: Reduce the parameter value length.
29897, 00000, "invalid domain index \"%s\" found on the same column"
// *Cause : An attempt was made to create a domain index on the same column
// where an invalid domain index exists.
// *Action: Drop the invalid index and reissue the CREATE INDEX statement.
29900, 00000, "operator binding does not exist"
// *Cause: There is no binding for the current usage of the operator.
// *Action: Change the operator arguments to match any of the existing
// bindings or add a new binding to the operator.
29901, 00000, "function underlying operator binding does not exist"
// *Cause: The function underlying the operator binding does not exist.
// *Action: Ensure that the function corresponding to the operator
// invocation exists.
29902, 00000, "error in executing ODCIIndexStart() routine"
// *Cause: The execution of ODCIIndexStart routine caused an error.
// *Action: Examine the error messages produced by the indextype code and
// take appropriate action.
29903, 00000, "error in executing ODCIIndexFetch() routine"
// *Cause: The execution of ODCIIndexFetch routine caused an error.
// *Action: Examine the error messages produced by the indextype code and
// take appropriate action.
29904, 00000, "error in executing ODCIIndexClose() routine"
// *Cause: The execution of ODCIIndexClose routine caused an error.
// *Action: Examine the error messages produced by the indextype code and
// take appropriate action.
29905, 00000, "method %s does not exist in type %s.%s"
// *Cause: A required method with the required signature does not exist
// in the specified type.
// *Action: Add the required method to the type.
29906, 00000, "indextype %s.%s does not exist"
// *Cause: The indextype does not exist.
// *Action: Create the indextype.
29907, 00000, "found duplicate labels in primary invocations"
// *Cause: There are multiple primary invocations of operators with
// the same number as the label.
// *Action: Use distinct labels in primary invocations.
29908, 00000, "missing primary invocation for ancillary operator"
// *Cause: The primary invocation corresponding to an ancillary operator
// is missing.
// *Action: Add the primary invocation with the same label as the
// ancillary operator.
29909, 00000, "label for the ancillary operator is not a literal number"
// *Cause: The label used for invoking the ancillary operator is not
// a literal number.
// *Action: Use a literal number as the label.
29910, 00000, "invalid callback operation"
// *Cause: Encountered an invalid callback operation.
// *Action: Ensure that all the callbacks executed from callouts are
// valid in the statement context.
29911, 00000, "null scan context returned by ODCIIndexStart() routine"
// *Cause: The ODCIIndexStart() routine returned a null scan context
// *Action: Ensure that the ODCIIndexStart() routine returns a non-null
// scan context.
29912, 00000, "event for turning off direct invocation of Contains/Score"
// *Document: NO
// *Cause: For internal use only
// *Action: Not a user error
29913, 00000, "error in executing %s callout"
// *Cause: The execution of the specified callout caused an error.
// *Action: Examine the error messages take appropriate action.
29914,00000,"ODCIGETINTERFACES routine does not return required stream version"
// *Cause: The ODCIObjectList returned by the ODCIGetInterfaces routine
// does not contain the required stream version for external tables.
// *Action: Ensure that the ODCIGetInterfaces routine returns the required
// stream version.
29915,00000,"cannot select FOR UPDATE from collection operand"
// *Cause: Collection operands cannot be updated
// *Action: Remove FOR UPDATE clause
29916, 00000, "event for turning on RAW pointer arg to table function"
// *Document: NO
// *Cause: For internal use only
// *Action: Not a user error
29917, 00000, "cannot lock a table which gets its rows from a collection operand"
// *Cause: Tables which gets its rows from a collection operand cannot be locked
// *Action: Don't lock the table
29918, 00000, "cannot create domain indexes on temporary tables"
// *Cause : An attempt was made to create a domain index on a temporary table
// *Action: Either create another type of index on the temporary
// table or change the table from temporary to a permanent table
29919, 00000, "failed in the execution of the ODCIINDEXUPDPARTMETADATA routine"
// *Cause: Failed to successfully execute the ODCIINDEXUPDPARTMETADATA routine.
// *Action: Check to see if the routine has been coded correctly.
29920, 00000, "failed in the partition maintenance operation of secondary table"
// *Cause: Failed to successfully execute the partition maintenance operation
// of a secondary table in system managed domain index.
// *Action: Check to see if the partition of a secondary table exists.
29921, 00000, "Ancillary operator not supported with set view query block"
// *Cause : Outer view query block contains ancillary operator and view query
// block contains union all.
// *Action: Define the union-all view query to contain the primary
// and ancillary query terms. i.e. have the operators within the view
// definition rather than in the query outside the view.
29922, 00000, "Invalid rowid returned by the user-defined query methods"
// *Cause: An invalid row identifier was returned by the user-defined query
// methods.
// *Action: Check the implementation of the indextype methods to make sure
// that the index creation and query methods are correct.
29925, 00000, "cannot execute %s"
// *Cause: The specified function does not exist or does not have an
// appropriate signature.
// *Action: Implement the function with the appropriate signature.
29926, 00000, "association already defined for the object"
// *Cause: The object for which the association is being defined, already
// has a statistics type associated with it.
// *Action: Disassociate the object and then associate the object.
29927, 00000, "error in executing the ODCIStatsCollect / ODCIStatsDelete routine"
// *Cause: The ODCIStatsCollect / ODCIStatsDelete function is causing an
// error.
// *Action: Check the ODCIStatsCollect / ODCIStatsDelete function.
29928, 00000, "duplicate default selectivity specified"
// *Cause: The keyword DEFAULT SELECTIVITY can only be specified once.
// *Action: Remove the duplicate keyword.
29929, 00000, "missing SCAN Keyword"
// *Cause: The scan context is not specified.
// *Action: Supply the SCAN keyword.
29930, 00000, "COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause"
// *Cause: The COMPUTE ANCILLARY DATA option was specified without the
// WITH INDEX CONTEXT clause.
// *Action: Specify the WITH INDEX CONTEXT option.
29931, 00000, "specified association does not exist"
// *Cause: One or more of the object(s) that have been specified to be
// disassociated, do not have an association defined for them.
// *Action: Verify the objects which have an association defined and issue
// the disassociate command again.
29932, 00000, "the type being dropped is a statistics type"
// *Cause: Some objects have defined their statistics methods in the type
// being dropped.
// *Action: First drop the relevant associations using the DISASSOCIATE
// command and then retry the DROP command, or use the FORCE option
// with DROP TYPE command.
29933, 00000, "object being disassociated has some user defined statistics stored"
// *Cause: There are some user defined statistics collected for the object
// being disassociated.
// *Action: First delete the user defined statistics and then reissue the
// DISASSOCIATE command or specify the FORCE option with DISASSOCIATE.
29934, 00000, "index specified for association is not a domain index"
// *Cause: The user issued an ASSOCIATE STATISTICS command with an index
// which is not a domain index.
// *Action: Issue an ASSOCIATE STATISTICS WITH INDEXES command on a domain
// index only
29935,00000, "missing FROM keyword"
// *Cause: The keyword FROM is missing.
// *Action: Specify the FROM keyword or check the SQL statement.
29936, 00000, "NULL association is allowed only with a column or an index"
// *Cause: User tried to use the ASSOCIATE command with a schema object
// other than a column or an index
// *Action: Specify the NULL clause only with a column or an index
29937, 00000, "domain index cannot be system-managed"
// *Cause: An ASSOCIATE STATISTICS command was issued with a domain index
// which is system-managed.
// *Action: Check to see if the domain index has been implemented with
// system-managed storage tables. To associate statitics with a
// system-managed domain index, issue ASSOCIATE STATISTICS command
// with the indextype of this domain index.
29938, 00000, "both indextype and statistics type should be system-managed"
// *Cause: Either an ASSOCIATE STATISTICS WITH SYSTEM MANAGED STORAGE TABLES
// command was issued with an indextype which is not system-managed,
// or an ASSOCIATE STATISTICS command was issued with an indextype
// which is system-managed.
// *Action: Check to see if both indextype and statistics type are implemented
// with system-managed storage tables.
29939, 00000, "could not implicitly transform user-managed domain index to system-managed domain index"
// *Cause: Implicit validation of a user-managed domain index with a
// system-managed indextype failed.
// *Action: Issue an ALTER INDEX COMPILE command on the domain index.
29940, 00000, "User-managed domain indexes are not allowed on interval-partitioned tables."
// *Cause: An attempt was made to create a local user-managed domain index on
// an interval-partitioned table.
// *Action: Convert the underlying index type to system-managed.
29941, 00000, "Cannot convert a table with user-managed local domain indexes to interval partitioning."
// *Cause: An attempt was made to convert a range-partitioned table with local
// user-managed domain indexes to interval partitioning.
// *Action: Either convert the underlying index type to system-managed or
// drop the local user-managed domain index before converting the
// table to interval partitioning.
29950, 00000, "warning in the execution of ODCIINDEXMERGEPARTITION routine"
// *Cause: A warning was returned from the ODCIIndexMergePartition routine.
// *Action: Check to see if the routine has been coded correctly
// Check user specified log tables for greater detail.
29951, 00000, "warning in the execution of ODCIINDEXSPLITPARTITION routine"
// *Cause: A warning was returned from the ODCIIndexSplitPartition routine.
// *Action: Check to see if the routine has been coded correctly
// Check user specified log tables for greater detail.
29952, 00000, "cannot issue DDL on a domain index partition marked as LOADING"
// *Cause: Tried to issue a DROP/ALTER/TRUNCATE on a domain index partition
// in a LOADING state.
// *Action: Wait till the index partition operation completes
// OR issue a DROP INDEX FORCE to drop the index
// OR issue a ALTER TABLE DROP PARTITION to drop the partition.
29953, 00000, "cannot issue DDL on a domain index partition marked as FAILED"
// *Cause: Tried to issue a DROP/ALTER on a domain index partition in a
// FAILED state.
// *Action: do ALTER INDEX REBUILD PARTITION to rebuild the index partition
// OR ALTER TABLE TRUNCATE PARTITION to mark the index partition
// as valid.
29954, 00000, "domain index partition is marked LOADING/FAILED/UNUSABLE"
// *Cause: An attempt has been made to access a domain index that is
// being built or is marked failed by an unsuccessful DDL
// or is marked unusable by a DDL operation.
// *Action: Wait if the specified index partition is marked LOADING
// Rebuild the specified index partition if it is marked FAILED
// or UNUSABLE.
29955, 00000, "error occurred in the execution of ODCIINDEXEXCHANGEPARTITION routine"
// *Cause: Failed to successfully execute the ODCIIndexExchangePartition routine.
// *Action: Check to see if the routine has been coded correctly.
29956, 00000, "warning in the execution of ODCIINDEXEXCHANGEPARTITION routine"
// *Cause: A warning was returned from the ODCIIndexExchangePartition routine.
// *Action: Check to see if the routine has been coded correctly
// Check user specified log tables for greater detail.
29957, 00000, "cannot create a function-based domain index on a %s table"
// *Cause: User specified an unsupported create function-based domain index
// statement.
// *Action: Issue the create function-based domain index statement only on
// supported types of tables.
29958, 00000, "fatal error occurred in the execution of ODCIINDEXCREATE routine"
// *Cause: Failed to successfully execute the ODCIIndexCreate routine.
// *Action: Check to see if the routine has been coded correctly.
29959, 00000, "error in the execution of the %s routine for one or more of the index partitions"
// *Cause: An error occurred during execution of the routine for one or more of
// the index partitions
// *Action: Check the *_IND_PARTITIONS view to see which partitions are marked
// FAILED.
// Rebuild or Truncate the FAILED index partitions
29960, 00000, "line %s, %s"
// *Cause: The ODCIIndex DDL routine has put a warning message into
// table SYS.ODCI_WARNINGS$
// *Action: Check the warning message
29961, 00000, "too many warnings occurred in the execution of ODCIIndex DDL routine"
// *Cause: The number of warnings during the ODCIIndex DDL routine is
// too high.
// *Action: Query table SYS.ODCI_WARNINGS$ to get more warning messages
29962, 00000, "fatal error occurred in the execution of ODCIINDEXALTER routine"
// *Cause: Failed to successfully execute the ODCIIndexAlter routine.
// *Action: Check to see if the routine has been coded correctly.
29963, 00000, "missing BINDING keyword"
// *Cause: Keyword BINDING is expected .
// *Action: Specify the BINDING keyword or check the SQL statement.
29964, 00000, "missing ADD or DROP keyword"
// *Cause: One of the keywords ADD or DROP is expected.
// *Action: Specify the ADD or DROP keyword or check the SQL statement.
29965, 00000, "The specified binding does not exist"
// *Cause: The binding specified in the DROP BINDING clause is not a valid
// binding for this operator.
// *Action: Specify an existing binding for this op in DROP BINDING clause.
29966, 00000, "The only binding of an operator cannot be dropped"
// *Cause: This operator only has one binding. It cannot be dropped using
// Alter Operator Drop Binding.
// *Action: If you wish to drop the entire operator, call Drop Operator.
29967, 00000, "Cannot drop an operator binding with dependent objects"
// *Cause: The operator binding that is being dropped has dependent objects.
// *Action: Either drop the dependent objects first and then issue the ALTER
// OPERATOR DROP BINDING command or specify the FORCE option with
// ALTER OPERATOR DROP BINDING.
29968, 00000, "No primary operator bindings found for ancillary binding #%s"
// *Cause: At least one ancillary binding of the specified operator could
// not be validated because all of its associated primary operator
// bindings have been dropped.
// *Action: Either drop the ancillary binding whose primary operators are
// missing, or drop the entire operator, if this is the only binding.
// This binding cannot be re-validated.
/
/29970 - 29999 Reserved for DB Change notification
29970, 00000, "Specified registration id does not exist"
// *Cause: An incorrect regid value was passed to dbms_chnf procedure.
// *Action: pass the correct regid value.
/
29971, 0000, "Specified table name not found or does not have any registrations"
// *Cause: The database could not locate the passed in table name
// *Action: CHeck the table name passed in.
/
29972, 0000, "user does not have privilege to change/ create registration"
// *Cause: User passed in an incorrect or someone else's regid/ handle.
// *Action: Check the passed in regid/ reg handle
/
29973, 0000, "Unsupported query or operation during change notification registration"
// *Cause: The user attempted to register an unsupported query type
// or an unsupported operation like a DML/DDL for change notification.
// *Action: Please check the statement being executed and refer to the
// documentation.
/
29974, 0000, "Internal event for PL/SQL debugging"
// *Cause: None
// *Action: none
/
29975, 0000, "Cannot register a query in the middle of an active transaction"
// *Cause: User tried to register a query within an uncommitted transction.
// *Action: Commit the transaction and retry.
/
29976, 0000, "Unsupported query for registration in guaranteed mode"
// *Cause: An operator or expression in the query was incompatible
// with query registration in the guaranteed granularity mode.
// *Action: Check all expressions, clauses and operators in the query and refer
// to the documentation for supported query types.
// The application can reattempt
// the query registration in best effort mode.
/
29977, 0000, "Unsupported column type for query registration in guaranteed mode"
// *Cause: An attempt was made to register a query with an unsupported
// column type or too many columns.
// *Action: Examine all column datatypes in the expression and refer
// to the documentation for supported query types.
// The application can reattempt
// the query registration in best effort mode.
/
29978, 0000, "Internal event for tracing Inband Notifications"
// *Cause: None
// *Action: none
/
29979, 0000, "unsupported row size for query result change notification"
// *Cause: An attempt was made to register query result change notification
// (QRCN) on a table with more than 255 columns.
// *Action: Use object change notification (OCN) instead.
/
29980, 0000, "Internal event for KTG crash recovery"
// *Document: NO
// *Cause: None
// *Action: none
/
29981, 0000, "Cannot register query: conflicting DDL in progress"
// *Cause: A query registration was attempted while there was a
// a concurrent DDL in progress.
// *Action: Retry the query registration.
/
29982, 0000, "Table type not supported for query registration in guaranteed mode"
// *Cause: The user attempted to register a query
// involving an unsupported table type.
// *Action: Examine all tables in the query registration and refer
// to the documentation for supported table types.
// The application can reattempt registration in best effort mode.
/
29983, 0000, "Unsupported query for Continuous Query Notification"
// *Cause: The query cannot be registered for Continuous Query Notification.
// *Action: The query has some constructs that make it incompatible
// with Continous Query Notification like
// synonyms or views. Please check the documentation for
// complete list.
/
29984, 0000, "Internal event to force CHNF registrations"
// *Cause: None
// *Action: none
/
29985, 0000, "Query Registration is only supported for automatic undo management"
// *Cause: User is using manual undo management
// *Action: Switch to using automatic undo management
/
29986, 0000, "Internal event for CQN to enable slow path ROWID generation"
// *Document: NO
// *Cause: None
// *Action: None
/
29987, 0000, "Internal event for validating context in KTG Hash Insert Item"
// *Document: NO
// *Cause: None
// *Action: None
/
29988, 0000, "Event to enable blocking on client cache registrations"
// *Document: NO
// *Cause: None
// *Action: None
/
29989, 0000, "not enough shared pool memory due to very many CQN registrations"
// *Document: NO
// *Cause: Max allowed shared pool usage for KTCN is 1 percent of shared pool size. The shared pool usage for KTCN depends directly on the number of CQN registrations.
// *Action: Increase shared_pool_size in Init.ora. Check relevant trace files to get more information about the current number of CQN registrations that caused this error message.
/
/ 30000 - 30010 Reserved 8.1 miscellaneous features
/
30000, 00000, "missing either trim specification or char expression in TRIM"
// *Cause: Since FROM is specified in TRIM function, either trim specification
// (TRAILING, HEADING, BOTH) or trim character or both must be
// specified.
// *Action: Add either trim specification (TRAILING, HEADING, BOTH) or
// trim character or both.
/
30001, 00000, "trim set should have only one character"
// *Cause: Trim set contains more or less than 1 character. This is not
// allowed in TRIM function.
//
// *Action: Change trim set to have only 1 character.
/
30002, 00000, "SYS_CONNECT_BY_PATH function is not allowed here"
// *Cause: SYS_CONNECT_BY_PATH function was called at places other than the
// SELECT list and ORDER BY clause.
//
// *Action: Remove calls to SYS_CONNECT_BY_PATH function at places other than
// the SELECT list and ORDER BY clause.
/
30003, 00000, "illegal parameter in SYS_CONNECT_BY_PATH function"
// *Cause:
// *Action: use a non-empty constant string as the second argument,
// then retry the operation.
/
30004, 00000, "when using SYS_CONNECT_BY_PATH function, cannot have separator as part of column value"
// *Cause: A column value contained the string that the SYS_CONNECT_BY_PATH
// function was to use to separate column values.
// *Action: Specify another separator for the SYS_CONNECT_BY_PATH function
// to use which does not occur in any column value, then retry.
/
30005, 00000, "missing or invalid WAIT interval"
// *Cause: A non-zero integer must be specified for wait interval (in seconds) after the WAIT keyword.
// *Action: Correct the syntax and retry.
/
30006, 00000, "resource busy; acquire with WAIT timeout expired"
// *Cause: The requested resource is busy.
// *Action: Retry the operation later.
/
30007, 00000, "CONNECT BY ROOT operator is not supported in the START WITH or in the CONNECT BY condition"
// *Cause: An attempt was made to use CONNECT BY ROOT operator in the START WITH or in the CONNECT BY condition.
// *Action: Remove CONNECT BY ROOT operator from the START WITH or from the CONNECT BY condition.
/
30008, 00000, "CONNECT BY clause must reference a PRIOR"
// *Cause: A CONNECT BY clause did not include a predicate referencing a
// PRIOR so there was no condition connecting a parent row to its
// child row.
// *Action: Add a reference to a PRIOR in the CONNECT BY clause.
/
30009, 0000, "Not enough memory for %s operation"
// *Cause: The memory size was not sufficient to process all the levels of the
// hierarchy specified by the query.
// *Action: In WORKAREA_SIZE_POLICY=AUTO mode, set PGA_AGGREGATE_TARGET to
// a reasonably larger value.
// Or, in WORKAREA_SIZE_POLICY=MANUAL mode, set SORT_AREA_SIZE to a
// reasonably larger value.
/
30010, 0000, "Not enough I/O buffers for the sort operation"
// *Cause: The sort was unable to allocate enough I/O buffers.
// *Action: Increase the amount of memory allowed for the sort or increase
// the maximum number of I/O buffers allowed in the system and
// retry the query.
/
/ Error numbers 30011-30050 reserved for Automatic Undo Management Errors
/
30011, 00000, "Error simulated: psite=%s, ptype=%s"
// *Cause: error generated for testing purposes.
// *Action: None.
30012, 00000, "undo tablespace '%s' does not exist or of wrong type"
// *Cause: the specified undo tablespace does not exist or of the
// wrong type.
// *Action: Correct the tablespace name and reissue the statement.
30013, 00000, "undo tablespace '%s' is currently in use"
// *Cause: the specified undo tablespace is currently used by another
// instance.
// *Action: Wait for the undo tablespace to become available or
// change to another name and reissue the statement.
30014, 00000, "operation only supported in Automatic Undo Management mode"
// *Cause: the operation is only supported in automatic undo mode.
// *Action: restart instance in Automatic Undo Management mode before
// retrying operation.
30015, 00000, "previously offlined undo tablespace '%s' is still pending"
// *Cause: the current operation is not allowed because an undo
// tablespace containing active transactions is pending
// from a previous SWITCH UNDO operation. The operation
// will be allowed again after all transactions in the
// previous undo tablespace are committed.
// *Action: Wait for all previous transactions to commit before
// reissuing the current statement.
30016, 00000, "undo tablespace '%s' is already in use by this instance"
// *Cause: the specified undo tablespace is currently used by this
// instance. The operation failed.
// *Action: If the specified undo tablespace name is wrong, reissue
// the statement with the correct name.
30017, 00000, "segment '%s' is not supported in %s Undo Management mode"
// *Cause: the type of the specified undo segment is incompatible with
// the current undo management mode of the instance.
// *Action: Check the undo segment name and the undo management mode
// and reissue statement if necessary.
30018, 00000, "Create Rollback Segment failed, USN %s is out of range"
// *Cause: the system runs out of undo segment number. Too many undo
// segments exist.
// *Action: drop some of the unused undo segments and retry operation.
30019, 00000, "Illegal rollback Segment operation in Automatic Undo mode"
// *Cause: This operation only allowed in Manual Undo mode.
// *Action: restart instance in Manual Undo_Management mode and retry
// operation.
30021, 00000, "Operation not allowed on undo tablespace"
// *Cause: This operation is not allowed on undo tablespaces
// *Action: Check the tablespace name and reissue command if necessary
30022, 00000, "Cannot create segments in undo tablespace"
// *Cause: Cannot create segments in undo tablespace
// *Action: Check the tablespace name and reissue command
30023, 00000, "Duplicate undo tablespace specification"
// *Cause: Cannot create more than one undo tablespace during database creation
// *Action: Modify the command to contain only one undo tablespace
30024, 00000, "Invalid specification for CREATE UNDO TABLESPACE"
// *Cause: You have specified an clause that should not used with CREATE UNDO TABLESPACE
// *Action: Drop the clause from the command and reissue it.
/
30025, 00000, "DROP segment '%s' (in undo tablespace) not allowed"
// *Cause: Explicit DROP operation is not allowed on undo tablespace segments
// *Action: Check the undo segment name and reissue statement if
// necessary.
30026, 00000, "Undo tablespace '%s' has unexpired undo with %s(sec) left, Undo_Retention=%s(sec)"
// *Cause: Tried to drop a tablespace that contains unexpired undo
// information
// *Action: lower setting of UNDO_RETENTION or wait a while before
// reissue command to drop undo tablespace
30027, 00000, "Undo quota violation - failed to get %s (bytes)"
// *Cause: the amount of undo assigned to the consumer group of this
// session has been exceeded.
// *Action: ask DBA to increase undo quota, or wait until other
// transactions to commit before proceeding.
30028, 00000, "Automatic Undo Management event for NTP testing"
// *Cause: test events for internal use only
// *Action: none.
30029, 00000, "no active undo tablespace assigned to instance"
// *Cause: the current instance does not have an active undo tablespace
// assigned to execute transactions.
// *Action: ask DBA to create an undo tablespace, online the undo
// tablespace and then retry operation.
30030, 00000, "suppress resumable related error message"
// *Cause: none
// *Action: This event is to be used if the errors 30031 and 30032
// wish to be suppressed.
/ level 1 will suppress resumable error messages
30031, 00000, "the suspended (resumable) statement has been aborted"
// *Cause: DBA or the user aborted the execution of the suspended statement
// in the resumable session
// *Action: none
30032, 00000, "the suspended (resumable) statement has timed out"
// *Cause: A correctible error was signaled in the resumable session and
// the error was not cleared within the timeout interval.
// *Action: Fix the correctible error within the timeout. Default is 2 hours.
// Or increase the (resumable) timeout.
30033, 00000, "Undo tablespace cannot be specified as default user tablespace"
// *Cause: It is incorrect to specify undo tablespace as default user
// tablespace
// *Action: Check the tablespace name and reissue the command
30034, 00000, "Undo tablespace cannot be specified as temporary tablespace"
// *Cause: Undo tablespace cannot be specified as default temporary
// tablespace for the user
// *Action: Check the tablespace name and reissue the command
30035, 00000, "Undo tablespace cannot be specified as default temporary tablespace"
// *Cause: Undo tablespace cannot be specified as default temporary
// tablespace for the database
// *Action: Check the tablespace name and reissue the command
30036, 00000, "unable to extend segment by %s in undo tablespace '%s'"
// *Cause: the specified undo tablespace has no more space available.
// *Action: Add more space to the undo tablespace before retrying
// the operation. An alternative is to wait until active
// transactions to commit.
30037, 00000, "Cannot perform parallel DML after a prior DML on the object"
// *Cause: Attempt to perform parallel DML after another DML on the same
// object in the same transaction.
// *Action: Use bitmap segments to perform multiple (parallel) DML
// operations on the same object. Or commit before issueing the DML
30038, 00000, "Cannot perform parallel insert on non-partitioned object"
// *Cause: Attempt to perform parallel insert on a non-partitioned object
// after a previous DML on the object in the same transaction.
// *Action: Commit before issueing the insert.
30039, 00000, "Cannot drop the undo tablespace "
// *Cause: Cannot drop an undo tablespace that is in use
// *Action: Switch to a different undo tablespace and then try to drop
30040, 00000, "Undo tablespace is offline"
// *Cause: Cannot operate on an offlined undo tablespace
// *Action: Online the undo tablespace and redo the operation
30041, 00000, "Cannot grant quota on the tablespace"
// *Cause: User tried to grant quota on an undo or temporary tablespace
// *Action: Check the tablespace name and reissue the command
30042, 00000, "Cannot offline the undo tablespace "
// *Cause: Cannot offline an undo tablespace that is in use
// *Action: Switch to a different undo tablespace and then try to offline
30043, 00000, "Invalid value '%s' specified for parameter 'Undo_Management'"
// *Cause: the specified undo management mode is invalid
// *Action: Correct the parameter value in the initialization file
// and retry the operation.
30044, 00000, "'Retention' can only specified for undo tablespace"
// *Cause: An attempt was made to specify retention for a non-undo tablespace.
// *Action: Modify the CREATE TABLESPACE statement.
30045, 00000, "No undo tablespace name specified"
// *Cause: If Create Database has the datafile clause, then
// undo tablespace name has to be specified, unless using OMF.
// *Action: Specify the undo tablespace name.
30046, 00000, "Undo tablespace %s not found in control file."
// *Cause: The specified undo tablespace is not present in the control file.
// *Action: Modify the CREATE CONTROLFILE statement that created the current
// control file to include undo tablespace(s) and reissue the
// statement.
30047, 00000, "Internal event for kti tracing"
// *Cause: internal use only
// *Action: none
30048, 00000, "Internal event for IMU auto-tuning"
// *Cause: internal use only
// *Action: none
30049, 00000, "Internal event for TA enq tracing"
// *Cause: internal use only
// *Action: none
/
30050, 00000, "Internal event for IMU private buffer leak checks"
// *Document: NO
// *Cause: internal use only
// *Action: none
/
/ 30051 - 30059 Reserved for row versions query feature
/
30051, 00000, "VERSIONS clause not allowed here"
// *Cause: A VERSIONS clause was specified when it was not allowed.
// *Action: Do not use the VERSIONS clause
30052, 00000, "invalid lower limit snapshot expression"
// *Cause: The lower limit snapshot expression was below the UNDO_RETENTION
// limit.
// *Action: Specify a valid lower limit snapshot expression.
30053, 00000, "invalid upper limit snapshot expression"
// *Cause: The upper limit snapshot expression is greater than the SQL
// statement read snapshot.
// *Action: Specify a valid upper limit snapshot expression.
30054, 00000, "invalid upper limit snapshot expression"
// *Cause: The upper limit snapshot expression is less than the lower limit
// snapshot expression.
// *Action: Specify a valid upper limit snapshot expression.
30055, 00000, "NULL snapshot expression not allowed here"
// *Cause: The snapshot expression is NULL.
// *Action: Specify a non-NULL snapshot expression.
/
/ 30060 - 30069 Reserved for Transaction layer internal tracing
/
30060, 00000, "Internal event for RECO tracing"
// *Cause: internal use only
// *Action: none
30061, 00000, "Internal Event for Savepoint Tracing"
// *Cause: internal use only
// *Action: none
30062, 00000, "Test support for ktulat latch recovery"
// *Cause: internal use only
// *Action: none.
30063, 00000, "Internal Event to Test NTP"
// *Cause: none
// *Action: none
30064, 00000, "Test support for two phase read only optimization"
// *Cause: internal use only
// *Action: none.
30065, 00000, "test support for row dependencies"
// *Cause: internal use only
// *Action: none.
30066, 00000, "test support - drop rollback segment wait"
// *Cause: internal use only
// *Action: none.
30067, 00000, "Internal Event to turn on nested debugging info"
// *Cause: none
// *Action: none.
30068, 00000, "Internal Event to turn on nested"
// *Cause: none
// *Action: none.
30069, 00000, "Auto Undo-Management Error simulation - test site = %s"
// *Cause: test events for internal use only.
// *Action: none.
/
/ 30070 - 30099 Reserved for datetime/interval feature
/
30071, 00000, "conversion between datetime/interval and string fail"
// *Cause: An error occurs during a conversion between datetime/interval
// and string data type due to one of the following reasons:
// - The buffer is too short to hold the result.
// - The format string is bad.
// *Action:
30072, 00000, "invalid time zone value"
// *Cause: The value specified for the time zone string, which appears in
// ALTER SESSION statement, environment variable ORA_SDTZ, or
// a datetime factor, is not valid.
// *Action:
30073, 00000, "invalid adjustment value"
// *Cause: The value is none of the followings: 'ADJUST', 'NO_ADJUST',
// 'ANSI_DATE', 'ADJUST_WITH_ANSI_DATE'. 'NO_ADJUST' is the default value.
// *Action: set it to one of the three values
//
30074, 00000, "GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed"
// *Cause: try to GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE.
// *Action: Do not GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE.
30075, 00000, "TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint"
// *Cause: User is trying to create a constraint on a time or timestamp with
// or without time zone column without explicitly specifying the time zone.
// *Action: Use time or timestamp with time zone literals only.
30076, 00000, "invalid extract field for extract source"
// *Cause: The extract source does not contain the specified extract field.
// *Action:
30077, 00000, "illegal casting between specified datetime types"
// *Cause: Cannot cast between the specified datetime types.
// *Action:
30078, 00000, "partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals"
// *Cause: An attempt was made to use a time/timestamp expression whose format
// does not explicitly have time zone on a TIME/TIMESTAMP or
// TIME/TIMESTAMP WITH TIME ZONE column.
// *Action: Explicitly use TIME/TIMESTAMP WITH TIME ZONE literal.
30079, 00000, "cannot alter database timezone when database has TIMESTAMP WITH LOCAL TIME ZONE columns"
// *Cause: An attempt was made to alter database timezone with
// TIMESTAMP WITH LOCAL TIME ZONE column in the database.
// *Action: Either do not alter database timezone or first drop all the
// TIMESTAMP WITH LOCAL TIME ZONE columns.
//
30081, 00000, "invalid data type for datetime/interval arithmetic"
// *Cause: The data types of the operands are not valid for datetime/interval
// arithmetic.
// *Action:
30082, 00000, "datetime/interval column to be modified must be empty to decrease fractional second or leading field precision"
// *Cause: datetime/interval column with existing data is being modified to
// decrease fractional second or leading field precisions.
// *Action: Such columns are only allowed to increase the precisions.
//
30083, 00000, "syntax error was found in interval value expression"
// *Cause: A syntax error was found during parsing an interval value
// value expression.
// *Action: Correct the syntax.
30084, 00000, "invalid data type for datetime primary with time zone modifier"
// *Cause: When a time zone modifier is specified, the data type of datetime
// primary must be one of the following: TIME, TIME WITH TIME ZONE,
// TIMESTAMP, TIMESTAMP WITH TIME ZONE.
// *Action:
30085, 00000, "syntax error was found in overlaps predicate"
// *Cause: A syntax error was found during parsing an overlaps predicate.
// *Action: Correct the syntax.
30086, 00000, "interval year-month result not allowed for datetime subtraction"
// *Cause: An attempt was made to specify interval year to month as the
// result of datetime subtraction.
// *Action: This is not allowed currently due to unclear specification
// in SQL Standards for this interval type. Change the interval
// type to interval day to second and resubmit statement.
30087, 00000, "Adding two datetime values is not allowed"
// *Cause: An attempt was made to add two datetime values.
// *Action: This addition is not allowed.
//
30088, 00000, "datetime/interval precision is out of range"
// *Cause: The specified datetime/interval precision was not between 0 and 9.
// *Action: Use a value between 0 and 9 for datetime/interval precision.
/
30089, 00000, "missing or invalid <datetime field>"
// *Cause: A <datetime field> (YEAR, MONTH, DAY, HOUR, MINUTE, SECOND) is
// expected but not found, or a <datetime field> specified the
// <end field> in an <interval qualifier> is more significant
// than its <start field>.
// *Action:
//
30090, 00000, "Internal general event for DST patching on TIMESTAMP WITH TIME ZONE data"
// *Document: NO
// *Cause: N/A
// *Action: N/A
// Level:
// 0x01 - trace loading of TT
// 0x02 - trace SQL statement generation
// 0x04 - trace RAC execution
// 0x08 - trace DBMS_DST procedures
// 0x10 - allow to start an upgrade window without opening DB
// in UPGRADE mode
// 0x20 - simulate a datapump job caller
// 0x40 - disable the optimization of using index to find if the
// data in a TSTZ column are affected
// *Comment: Not for general purpose use.
//
30091, 00000, "secondary translation table not loaded"
// *Cause: The secondary translation table for DST patching on TSTZ data
// was not loaded.
// *Action: Load the secondary translation table.
//
30092, 00000, "function not allowed at this stage of DST upgrade process"
// *Cause: Query included a function that is not allowed in the current
// state of DST upgrade process.
// *Action: This function is not allowed at the currect stage of DST upgrade.
//
30093, 00000, "function not allowed until the database is restarted"
// *Cause: Query included a function that is not allowed until the
// database is restarted.
// *Action: Shut down and restart the database.
//
30094, 00000, "failed to find the time zone data file for version %s in $ORACLE_HOME/oracore/zoneinfo"
// *Cause: There was no corresponding time zone data file in
// $ORACLE_HOME/oracore/zoneinfo for the input time zone version.
// *Action: None.
//
/ 30100-30134 Reserved for OCIExtract Cartridge Services
/
30100, 00000, "internal error [%d]"
// *Cause: An internal error has occurred.
// *Action: Contact Oracle Worldwide Support and report the error.
/
30101, 00000, "unknown parameter name '%.*s'"
// *Cause: You have misspelled the parameter name.
// *Action: Spell the parameter name correctly.
/
30102, 00000, "'%.*s' is not in the legal range for '%.*s'"
// *Cause: The value of the parameter is not within the legal range.
// *Action: Refer to the manual for the allowable values for this parameter.
/
30103, 00000, "'%.*s' contains an illegal integer radix for '%.*s'"
// *Cause: An illegal integer radix specification was found.
// *Action: Only 'd', 'h', 'D', and 'H' may be used as radix specifications.
/
30104, 00000, "'%.*s' is not a legal integer for '%.*s'"
// *Cause: The value is not a valid integer.
// *Action: Specify only valid integers for this parameter.
/
30105, 00000, "'%.*s' is not a legal boolean for '%.*s'"
// *Cause: The value is not a valid boolean.
// *Action: Refer to the manual for allowable boolean values.
/
30106, 00000, "reserved for future use"
// *Cause: None.
// *Action: None.
/
30107, 00000, "parameter name abbreviation '%.*s' is not unique"
// *Cause: The abbreviation given was not unique.
// *Action: Use a longer abbreviation to make the parameter name unique.
/
30108, 00000, "invalid positional parameter value '%.*s'"
// *Cause: An invalid positional parameter value has been entered.
// *Action: Remove the invalid positional parameter.
/
30109, 00000, "could not open parameter file '%.*s'"
// *Cause: The parameter file does not exist.
// *Action: Create an appropriate parameter file.
/
30110, 00000, "syntax error at '%.*s'"
// *Cause: A syntax error was detected.
// *Action: Change the input so that the correct syntax is used.
/
30111, 00000, "no closing quote for value '%.*s'"
// *Cause: A quoted string was begun but not finished.
// *Action: Put a closing quote in the proper location.
/
30112, 00000, "multiple values not allowed for parameter '%.*s'"
// *Cause: You attempted to specify multiple values for a parameter which can
// take only one value.
// *Action: Do not specify more than one value for this parameter.
/
30113, 00000, "error when processing file '%.*s'"
// *Cause: A problem occurred when processing this file.
// *Action: Examine the additional error messages and correct the problem.
/
30114, 00000, "error when processing from command line"
// *Cause: A problem occurred when processing the command line.
// *Action: Examine the additional error messages and correct the problem.
/
30115, 00000, "error when processing an environment variable"
// *Cause: A problem occurred when processing an environment variable.
// *Action: Examine the additional error messages and correct the problem.
/
30116, 00000, "syntax error at '%.*s' following '%.*s'"
// *Cause: A syntax error was detected.
// *Action: Change the input so that the correct syntax is used.
/
30117, 00000, "syntax error at '%.*s' at the start of input"
// *Cause: A syntax error was detected.
// *Action: Change the input so that the correct syntax is used.
/
30118, 00000, "syntax error at '%.*s' at the end of input"
// *Cause: A syntax error was detected.
// *Action: Change the input so that the correct syntax is used.
/
30119, 00000, "unable to obtain a valid value for '%.*s'"
// *Cause: No valid value was obtained for this parameter.
// *Action: Rerun the application and enter a valid value.
/
30120, 00000, "'%.*s' is not a legal oracle number for '%.*s'"
// *Cause: The value is not a valid oracle number.
// *Action: Refer to the manual for allowable oracle number values.
/
30121, 00000, "'%.*s' is not an allowable value for '%.*s'"
// *Cause: The value is not a legal value for this parameter.
// *Action: Refer to the manual for allowable values.
/
30122, 00000, "value '%.*s' for '%.*s' must be between '%d' and '%d'"
// *Cause: The value of the parameter is not within the legal range.
// *Action: Specify a value that is within the legal range.
/
/ Error numbers from 30123 to 30128 are reserved for possible LRM message
/ expansion.
/
30129, 00000, "invalid function argument received"
// *Cause: A function received an invalid argument
// *Action: Check function calls, make sure correct arguments are being passed.
/
30130, 00000, "invalid parameter key type received"
// *Cause: A function received an invalid parameter key type
// *Action: Check parameter key types in function calls
/
30131, 00000, "number of keys being set exceeds allocation"
// *Cause: Number of parameter keys being set exceeds allocation
// *Action: Reduce the number of keys being set or increase allocation
/
30132, 00000, "invalid key index supplied"
// *Cause: The key index specified was not within bounds
// *Action: Change key index to ensure it lies within bounds
/
30133, 00000, "reserved for future use"
// *Cause: None.
// *Action: None.
/
30134, 00000, "reserved for future use"
// *Cause: None.
// *Action: None.
/
/ Error numbers from 30135 to 30149 are reserved for OCIThread Cartridge
/ Service and OCI configuration.
/
30135, 00000, "OCI Thread operation fails"
// *Cause: An OCI Thread function call has failed.
//
// *Action: Check the function call to make sure that the correct parameters
// are being passed and take the apropriate action.
//
30136, 0000, "Drop-in compatibility is not supported for this application"
// *Cause: The current application is statically linked with defopt.o
// from an older release, which is incompatible with the current
// client shared library.
// *Action: 1) Relink the application against the new release of the client
// library; or
// 2) Relink the application against the older release of the client
// library without statically linking defopt.o.
/
/ OCIFile 30150-30174.
/ Error messages for OCIFile package.
/
30150, 00000, "Invalid argument passed to OCIFile function"
// *Cause: An invalid argument is passed to the OCIFile function. The most
// common cause is that a NULL pointer is passed where a non-NULL
// pointer is expected.
// *Action: Make sure that the values passed as arguments are valid. Esp
// check for NULL pointers.
/
30151, 00000, "File already exists"
// *Cause: Tried to open a file with OCI_FILE_EXCL flag and the file
// already exists.
//
// *Action: OCIFile is supposed throw this exception in this case.
/
30152, 00000, "File does not exist"
// *Cause: The OCIFile function requires the file to exist, but it does not.
//
// *Action: Make sure that the file exists.
/
/
30153, 00000, "An invalid File Object is passed to the OCIFile function"
// *Cause: An invalid File Object is passed to the OCIFile function.
//
// *Action: Make sure that the file object is a valid one. Create a new
// file object by calling OCIFileOpen if needed.
/
/
30154, 00000, "The memory address given as buffer for OCIFileRead/Write is invalid"
// *Cause: An invalid memory address is given as the buffer pointer for
// OCIFileRead/Write.
//
// *Action: Make sure that the required memory is allocated and pass a
// valid memory address as buffer pointer.
/
/
30155, 00000, "An I/O Error occured during an OCIFile function call"
// *Cause: An I/O error occurred at the system level.
//
// *Action: This is a system error and the action will depnd on the error.
/
/
30156, 00000, "Out of disk space"
// *Cause: The disks associated with the underlying file system are full.
//
// *Action: Create more disk space.
/
/
30157, 00000, "An invalid argument was given to operating system call"
// *Cause: The OS call was called with an invalid argument.
//
// *Action: Check the values passed. If unsuccessful to solve the problem
// contact ORACLE support.
/
/
30158, 00000, "The OCIFileWrite causes the file to exceed the maximum allowed size"
// *Cause: There is no space to write to the file. Its size is at the
// maximum limit.
//
// *Action: Up to the user.
/
/
30159, 00000, "OCIFileOpen: Cannot create the file or cannot open in the requested mode"
// *Cause: The create flag was specified in OCIFileOpen such that the file
// was to be created. But unable to do so. Or the file already exists
// and the permissions on it doesn't allow the file to be opened in
// in the requested open mode
//
// *Action: Check whether the user has permissions to create the specified
// file or if the file exists whether the permissions on it allow
// the requested open mode.
/
/
30160, 00000, "Unable to access the file"
// *Cause: The function was unable to access the existing the file.
//
// *Action: Check if the user has the required permissions on the file.
/
/
/
30161, 00000, "A system error occurred during the OCIFile function call"
// *Cause: A system error occured while executing the OCIFile function.
//
// *Action: Depend on the error.
/
/
30162, 00000, "The OCIFile context is not initialzed"
// *Cause: The function OCIFileInit need to be called before calling any
// other OCIFile function to initialize the OCIFile context.
//
// *Action: Call the function OCIFileInit need to be called before calling any
// other OCIFile function.
/
30163, 00000, "The thread safety initialization failed"
// *Cause: The call to SlgInit failed in OCIFileInit.
//
// *Action: Contact support
/
/
/ Error messages for the OCIFormat package: 30175-30199
/
30175, 00000, "invalid type given for an argument"
// *Cause: There is an argument with an invalid type in the argument list.
// *Action: Use the correct type wrapper for the argument.
/
30176, 00000, "invalid format code used in the format string"
// *Cause: There is an invalid format code in the format string.
// *Action: Replace the invalid format code with a valid one.
/
30177, 00000, "invalid flag used in a format specification"
// *Cause: There is an invalid flag in a format specification.
// *Action: Replace the invalid flag with a valid one.
/
30178, 00000, "duplicate flag used in a format specification"
// *Cause: There is a duplicate flag in a format specification.
// *Action: Remove the duplicate flag.
/
30179, 00000, "invalid argument index used in a format code"
// *Cause: Zero or negative argument index or index not following (."
// *Action: Replace the invalid argument index with a valid one.
/
30180, 00000, "argument index is too large"
// *Cause: An argument index exceeds actual number of arguments supplied.
// *Action: Fix format string or pass additional arguments.
/
30181, 00000, "integer in argument index is not immediately followed by )"
// *Cause: Missing closing parenthesis in argument index.
// *Action: Fix the format specification.
/
30182, 00000, "invalid precision specifier"
// *Cause: Period in format specification not followed by valid format.
// *Action: Replace the invalid precision specifier with a valid one.
/
30183, 00000, "invalid field width specifier"
// *Cause: Invalid field width supplied.
// *Action: Replace the invalid field width with a valid one.
/
30184, 00000, "argument type not compatible with a format code"
// *Cause: Bad argument type given for a format code.
// *Action: Make format and arguments be compatible.
/
30185, 00000, "output too large to fit in the buffer"
// *Cause: The buffer is not large enough to hold the entire output string.
// *Action: Fix the buffer size and length passed in.
/
30186, 00000, "'\\' must be followed by four hexdecimal characters or another '\\'"
// *Cause: In the argument of SQL function UNISTR, a '\' must be followed by
// four hexdecimal characters or another '\'
// *Action: Fix the string format
/
30187, 00000, "Permission denied for '%s' to access procedure GET_KEY."
// *Cause: The client was unauthorized to invoke the procedure DBMS_INTERNAL_CLKM.GET_KEY.
// *Action: DBMS_INTERNAL_CLKM.GET_KEY is an Oracle GoldenGate feature and can only
// be accessed by Oracle GoldenGate.
/
30188, 00000, "reserved for future use"
// *Cause: None.
// *Action: None.
/
30189, 00000, "reserved for future use"
// *Cause: None.
// *Action: None.
/
30190, 00000, "reserved for future use"
// *Cause: None.
// *Action: None.
/
30191, 00000, "missing argument list"
// *Cause: No argument list supplied.
// *Action: Modify the argument list to have at least OCIFormatEnd in it.
/
/ Error Numbers 30192 - 30199 are reserved for OGG/DB sharding
/
30192, 00000, "OGG Service URI: %s failed to %s process: %s name: %s - OGG message: %s"
// *Cause: Oracle GoldenGate (OGG) AdminService or DistributionService operation failed.
// *Action: Refer to the Oracle GoldenGate message for required action.
/
30193, 00000, "OGG sharding function called in non-OGG sharding deployment"
// *Cause: Internal error. An Oracle GoldenGate (OGG) specific sharding functionality
// was called in a non-Oracle GoldenGate sharding deployment.
// *Action: Contact Oracle Support Services.
/
30194, 00000, "Invalid combination of OGG Sharding deployment parameters specified"
// *Cause: The values specified for Oracle GoldenGate (OGG) sharding deployment
// parameters (number of shards, number of chunks, replication factor
// and distribution factor) were not compatible with each other.
// *Action: Ensure that the following invariants hold for each shardgroup:
// number of chunks >= number of shards
// number of shards >= replication factor
// distribution factor >= replication factor - 1
/
30195, 00000, "OGG command payload contains invalid operation code %s"
// *Cause: Internal error. The payload for Oracle GoldenGate (OGG) command sent from
// the Sharding Catalog to the shard database contained invalid operation code.
// *Action: Contact Oracle Support Services.
/
30196, 00000, "Sharding configuration parameter '%s' is not set in the shard database."
// *Cause: Internal error. A database initialization parameter required by the
// shard database was not set during deployment.
// *Action: Contact Oracle Support Services.
/
30197, 00000, "reserved for future use"
// *Cause: None.
// *Action: None.
/
30198, 00000, "reserved for future use"
// *Cause: None.
// *Action: None.
/
30199, 00000, "reserved for future use"
// *Cause: None.
// *Action: None.
/
/
/ Error Numbers 30200 - 30299 are reserved for NLS Cartridge Services
30200, 00000, "Wrong NLS item was passed into OCINlsGetInfo()"
// *Cause: The item is not supported NLS item
//
// *Action: Correct the item number passed to OCINlsGetInfo().
/
/
30201, 00000, "Unable to load NLS data object"
// *Cause: It may be caused by invalid NLS environment setting
//
// *Action: Check your NLS environment setting such as ORA_NLS33
/
/
30202, 00000, "NULL pointer to OCIMsgh was passed to OCIMsg function"
// *Cause: The NULL pointer was passed.
//
// *Action: Check your value of OCIMsgh pointer.
/
/
30203, 00000, "Cannot open mesage file"
// *Cause: The message may not exist in your system.
/
// *Action: Check your message for the given product and facility.
/
/
30204, 00000, "buffer is not large enougth"
// *Cause: The destination buffer is not large enough for storing
// converted data.
/
// *Action: Check the size of the destination buffer.
/
/
30205, 00000, "invalid Character set"
// *Cause: The specified character set is invalid.
/
// *Action: Check if the character set ID is valid.
/
/
/ 30300 - 30330 reserved for transaction recovery
/
30300, 00000, "unable to obtain SEG2"
// *Document: NO
// *Cause:
// *Action: Not a user error
/
30301, 00000, "cannot recover this transaction in parallel"
// *Document: NO
// *Cause:
// *Action: Not a user error
/
30302, 00000, "event to make PMON skip recovery"
// *Document: NO
// *Cause:
// *Action: Not a user error
/
30303, 00000, "Internal error"
// *Document: Internal event
// *Cause:
// *Action: Not a user error
/
30304, 00000, "Internal error"
// *Document: Internal event
// *Cause:
// *Action: Not a user error
/
30305, 00000, "Debug mode"
// *Document: Internal event
// *Cause:
// *Action: Not a user error
/
30306, 00000, "Internal error"
// *Document: Internal error
// *Cause:
// *Action: Not a user error
/
30307, 00000, "Internal error"
// *Document: Internal error
// *Cause:
// *Action: Not a user error
/
30308, 00000, "Internal error"
// *Document: Internal error
// *Cause:
// *Action: Not a user error
/
30309, 00000, "Interenal"
// *Document: NO
// *Cause:
// *Action: Not a user error
/
30310, 00000, "Interenal"
// *Document: NO
// *Cause: None
// *Action: Not a user error
/
30311, 00000, "Internal"
// *Document: NO
// *Cause: None
// *Action: Not a user error
/
30312, 00000, "Internal"
// *Document: NO
// *Cause: None
// *Action: Not a user error
/
30313, 00000, "Internal"
// *Document: NO
// *Cause: None
// *Action: Not a user error
/
30314, 00000, "Internal"
// *Document: NO
// *Cause: None
// *Action: Not a user error
/
30315, 00000, "Internal"
// *Document: NO
// *Cause: None
// *Action: Not a user error
/
30316, 00000, "Internal"
// *Document: NO
// *Cause: None
// *Action: Not a user error
/
/
30317, 00000, "Internal"
// *Document: NO
// *Cause: None
// *Action: Not a user error
/
/
30318, 00000, "Block Level Recovery attempted"
// *Document: NO
// *Cause: None
// *Action: Not a user error
/
30325, 00000, "SMON yielded shrink to perform other critical work"
// *Document: NO
// *Cause: None
// *Action: Not a user error
/
/ Error Numbers 30331 - 30429 are reserved for Summary Management Parse
/
30331, 00000, "summary does not exist"
// *Cause: A non-existant summary name was specified.
//
// *Action: Check the spelling of the summary name.
/
/
30332, 00000, "container table already in use by other summary"
// *Cause: Another summary is already using this table as a container table.
//
// *Action: Select another table or materialized view as the container table
// for this summary.
/
/
30333, 00000, "dimension does not exist"
// *Cause: The dimension named in a dimension DDL statment does not exist.
//
// *Action: Check the spelling of the dimension name.
/
/
30334, 00000, "illegal dimension level name"
// *Cause: A level name in a dimension ddl statement did not conform to
// SQL identifier rules.
//
// *Action: Use a level name that begins with a letter, consists of only
// letters, digits, and underscores and contains no more than 30
// characters.
/
/
30335, 00000, "JOIN KEY clause references a level not in this hierarchy"
// *Cause: The level name specified with the REFERENCES portion of a JOIN KEY
// clause in a dimension DDL statement does not reference a level
// in the hierarchy that contains the JOIN KEY clause.
//
// *Acction: Check the spelling of the level name.
/
/
30336, 00000, "no child for specified JOIN KEY"
// *Cause: The level specified in the REFERENCES portion of a JOIN KEY clause
// in a dimension DDL statement does not have a child level.
//
// *Action: Check the spelling of the level name referenced in the JOIN KEY
// clause. If the referenced level is the first level in the
// hierarchy, you need not and must not specify a JOIN KEY clause.
/
/
30337, 00000, "multiple JOIN KEY clauses specified for the same parent level"
// *Cause: Multiple JOIN KEY clauses were specified for a given parent
// level in a dimension hierarchy.
//
// *Action: Match up each JOIN KEY clause with the level it references in the
// hierarchy. Eliminate the redundant JOIN KEY clause.
/
/
30338, 00000, "illegal dimension hierachy name"
// *Cause: An illegal dimension hierarchy name was specified in a dimension DDL
// statement.
//
// *Action: Make sure the name begins with a letter, contains only letters,
// digits and underscore and contains no more than 30 characters.
// If you qualify the name with the owner name, make sure
// the owner name conforms with the requirements for an owner name
// on your system.
/
/
30339, 00000, "illegal dimension attribute name"
// *Cause: An illegal dimension attribute name was specified in a dimension DDL
// statement.
//
// *Action: Make sure the name begins with a letter, contains only letters,
// digits and underscore and contains no more than 30 characters.
// If you qualify the name with the owner name, make sure
// the owner name conforms with the requirements for an owner name
// on your system.
/
/
30340, 00000, "illegal dimension name"
// *Cause: An illegal dimension name was specified in a dimension DDL
// statement.
//
// *Action: Make sure the name begins with a letter, contains only letters,
// digits and underscore and contains no more than 30 characters.
// If you qualify the name with the owner name, make sure
// the owner name conforms with the requirements for an owner name
// on your system.
/
/
30341, 00000, "dropped level has references"
// *Cause: An attempt was made to drop a level using the default or RESTRICT
// option in a dimension while references to that level remain in the
// dimension. References can occur in hierarchies and attributes
// within the dimension.
//
// *Action: First remove any referenes to the level prior to dropping it, or
// specify the CASCADE option with the DROP LEVEL clause.
/
/
30342, 00000, "referenced level is not defined in this dimension"
// *Cause: A reference to a level not defined within the dimension was found.
//
// *Action: Check the spelling of the level name.
/
/
30343, 00000, "level name is not unique within this dimension"
// *Cause: Two or more levels were defined with the same name.
//
// *Action: Check the spelling of the level names.
/
/
30344, 00000, "number of child cols different from number of parent level cols"
// *Cause: The number of child columns specified in a JOIN KEY clause is not
// the same as the number of columns in the specified parent level.
//
// *Action: Check the child columns and the columns in the definition of the
// referenced parent level and correct the discrepency.
/
/
30345, 00000, "circular dimension hierarchy"
// *Cause: A circularity was found the dimension hierarchy.
//
// *Action: Check the hierarchy for a level name that occurs more than once.
/
/
30346, 00000, "hierarchy name must be unique within a dimension"
// *Cause: The same name was used for more than one hierarchy in a dimension.
//
// *Action: Check the spelling of the hierarchy name.
/
/
30347, 00000, "a table name is required to qualify the column specification"
// *Cause: A table name was omitted in a column specification where where
// the column must be qualified by the table name.
//
// *Action: Qualify the column with the table name.
/
/
30348, 00000, "ADD and DROP cannot both be specified"
// *Cause: One or more ADD clauses were found in the same ALTER DIMENSION
// statement with one or more DROP clauses.
//
// *Action: Separate your ADD operations into one ALTER DIMENSION statement
// and your DROP operations into another.
/
/
30349, 00000, "specified dimension hierarchy does not exist"
// *Cause: A hierarchy name was encountered that is not defined within
// the dimension.
//
// *Action: Check the spelling of the hierarchy name.
/
/
30350, 00000, "specified dimension attribute does not exist"
// *Cause: An attribute name was encountered that is not defined within the
// dimension.
//
// *Action: Check the attribute name spelling.
/
/
30351, 00000, "query rewrite does not currently support this expression"
// *Cause: A complex expression was specified that is is not currently
// supported by query rewrite.
//
// *Action: Reduce the complexity of the expression.
/
/
30352, 00000, "inconsistent numeric precision or string length"
// *Cause: The SELECT expression was of a different numeric precision or string
// length than the corresponding container column. Therefore, query
// rewrite cannot guarantee results that are identical to the
// results obtained with the un-rewritten query.
//
// *Action: Correct the precision or string length difference, specify the
// WITH REDUCED PRECISION option, or disable the REWRITE option
// on the materialized view.
/
/
30353, 00000, "expression not supported for query rewrite"
// *Cause: The SELECT clause referenced UID, USER, ROWNUM, SYSDATE,
// CURRENT_TIMESTAMP, MAXVALUE, a sequence number, a bind variable,
// correlation variable, a set result, a trigger return variable, a
// parallel table queue column, collection iterator, a non-deterministic
// date format token RR, etc.
// *Action: Remove the offending expression or disable the REWRITE option on
// the materialized view.
/
/
30354, 00000, "Query rewrite not allowed on SYS relations"
// *Cause: A SYS relation was referenced in the select clause for a
// materialized view with query rewrite enabled.
//
// *Action: Remove the reference to the SYS relation from the select clause or
// disable the REWRITE option on the materialized view.
/
/
30355, 00000, "materialized view container does not exist"
// *Cause: A DROP TABLE command was issued directly against the materialized
// view container table.
//
// *Action: Use the DROP MATERIALIZED VIEW command to clean up the residual
// meta data for the materialized view. Then use the CREATE
// MATERIALIZED VIEW statement to recreate the materialized view.
// Thereafter, use the DROP MATERIALIZED VIEW command rather than the
// DROP TABLE command to drop a materialized view.
/
/
30356, 00000, "the specified refresh method is not supported in this context"
// *Cause: The refresh method that was specified is not currently supported.
//
// *Action: Specify a different refresh method or change the context to
// enable support of the chosen refresh method.
/
/
30357, 00000, "this PL/SQL function cannot be supported for query rewrite"
// *Cause: The statement referenced a PL/SQL function that is not marked
// DETERMINISTIC.
// *Action: Perform one of the following actions:
// - Remove the use of the PL/SQL function.
// - Mark the PL/SQL function as DETERMINISTIC.
// - Disable the REWRITE option on the materialized view.
// The function should be marked DETERMINISTIC only if it always
// returns the same result value for any given set of input argument
// values, regardless of any database state or session state.
// Do not mark the function as DETERMINISTIC if it has any
// meaningful side-effects.
/
/
30358, 00000, "summary and materialized view are not in same schema"
// *Cause: An internal Oracle error occured.
//
// *Action: Report the problem through your normal support channels.
/
/
30359, 00000, "Query rewrite is not supported on SYS materialized views"
// *Cause: An attempt was made to enable the REWRITE option on a materialized
// view in the SYS schema.
//
// *Action: Create the materialized view in a different schema or disable the
// REWRITE option.
/
/
30360, 00000, "REF not supported with query rewrite"
// *Cause: The statement contained a REF operator. Repeatable behavior cannot
// be guaranteed with the REF operator. Therefore, query rewrite
// cannot support the REF operator.
//
// *Action: Remove the reference to the REF operator or disable the REWRITE
// option on the materialized view.
/
/
30361, 00000, "unrecognized string type"
// *Cause: An internal Oracle error occured.
//
// *Action: Report the problem through your normal support channels.
/
/
30362, 00000, "dimension column cannot be a sequence"
// *Cause: The dimension statement referenced a column that is a sequence.
//
// *Action: Remove the reference to the sequence.
/
/
30363, 00000, "columns in a dimension column list must be in the same relation"
// *Cause: The dimension statement contained a column list where the columns
// are not all from the same relation.
//
// *Action: Specify the list of columns using only columns from a single
// relation.
/
/
30364, 00000, "this level has the same set of columns as another"
// *Cause: The level definition contained the same set of columns as another
// level.
//
// *Action: Eliminate the redundant level definition.
/
/
30365, 00000, "left relation in the JOIN KEY clause cannot be same as right"
// *Cause: The relation of the child columns on the left side of the JOIN KEY
// clause was the same as that of the parent level on the right side.
//
// *Action: Remove the JOIN KEY clause. It is not required or allowed when
// the child and the parent are in the same relation.
/
/
30366, 00000, "child JOIN KEY columns not in same relation as child level"
// *Cause: The relation of the child columns on the left side of the JOIN KEY
// clause differed from that of that child level.
//
// *Action: Specify the correct child columns in the JOIN KEY clause.
/
/
30367, 00000, "a JOIN KEY clause is required"
// *Cause: A JOIN KEY clause was omitted in a dimension statement. A JOIN KEY
// clause is required when the child level and the parent level are
// not in the same relation.
//
// *Action: Specify a JOIN KEY clause to indicate how the relation of the
// child level joins to the relation of the parent level.
/
/
30368, 00000, "ATTRIBUTE cannot determine column in a different relation"
// *Cause: An ATTRIBUTE clause in a dimension statement specified a
// determined column on the right that is in a different relation
// than that of the level on the left.
//
// *Action: Specify attibutes only for those dimension levels that
// functionally determine other columns within the same relation.
/
/
30369, 00000, "maximum number of columns is 32"
// *Cause: A list of columns was specified using more than 32 columns.
//
// *Action: Specify the list using no more than 32 columns.
/
/
30370, 00000, "set operators are not supported in this context"
// *Cause: A set operator such as UNION, UNION ALL, INTERSECT, or MINUS was
// encountered in an unsupported context, such as in a materialized
// view definition.
//
// *Action: Re-specify the expression to avoid the use of set operators.
/
/
30371, 00000, "column cannot define a level in more than one dimension"
// *Cause: A column was used in the definition of a level after it had
// already been used to define a level in a different dimension.
//
// *Action: Reorganize dimension levels and hierarchies into a single
// dimension such that no column is used to define levels in
// different dimensions. There is no limit on the number of
// levels or hierarchies you can place in a dimension. A column can
// be used to define any number of levels provided all such levels
// are in the same dimension and provided no two levels contain
// identical sets of columns.
/
/
30372, 00000, "fine grain access policy conflicts with materialized view"
// *Cause: A fine grain access control procedure has applied a non-null policy
// to the query for the materialized view.
//
// *Action: In order for the materialized view to work correctly, any fine
// grain access control procedure in effect for the query must
// return a null policy when the materialized view is being
// created or refreshed. This may be done by ensuring that the
// usernames for the creator, owner, and invoker of refresh
// procedures for the materialized view all receive a null policy
// by the user-written fine grain access control procedures.
/
/
30373, 00000, "object data types are not supported in this context"
// *Cause: An object data type was encountered in an unsupported
// context.
//
// *Action: Re-specify the expression to avoid the use of objects.
/
/
30374, 00000, "materialized view is already fresh"
// *Cause: If the materialized view is fresh, ORACLE ignores the
// ALTER MATERIALIZED VIEW <mv> RELY FRESH command, and issues
// this error message.
//
// *Action: None
/
30375, 00000, "materialized view cannot be considered fresh"
// *Cause: If the materialized view is invalid or unusable, it cannot be considered
// fresh with the ALTER MATERIALIZED VIEW <mv> CONSIDER FRESH command.
//
// *Action: None
/
30376, 00000, "prevent sharing of a parsed query of an explain rewrite session"
// *Cause: Explain rewrite generates a shared cursor after parsing the user
// query. Raising this error will prevent the cursor from being
// shared.
//
// *Action: None
30377, 00000, "table %s.MV_CAPABILITIES_TABLE not found"
// *Cause: You have used the DBMS_MVIEW.EXPLAIN_MVIEW() API before you have
// defined the MV_CAPABILITIES_TABLE.
// *Action: Invoke the admin/utlxmv.sql script after connecting to the desired
// schema.
/
30378, 00000, "MV_CAPABILITIES_TABLE is not compatible with Oracle version"
// *Cause: One or more column definitions in the MV_CAPABILITIES_TABLE is
// either missing or incompatible with the current Oracle version.
// *Action: Connect to the appropriate schema,
// DROP TABLE MV_CAPABILITIES_TABLE and recreate it by invoking the
// admin/utlxmv.sql script prior to invoking the
// DBMS_MVIEW.EXPLAIN_MVIEW() API.
/
/
30379, 00000, "query txt not specified"
// *Cause: You have attempted use DBMS_MVIEW.EXPLAIN_REWRITE() API using
// an empty query text argument
// *Action: Input a valid SQL query
//
/
30380, 00000, "REWRITE_TABLE does not exist"
// *Cause: You have used the DBMS_MVIEW.EXPLAIN_REWRITE() API before you have
// created the REWRITE_TABLE.
// *Action: Create it using the admin/utlxrw.sql script after connecting to the
// desired schema
//
/
30381, 00000, "REWRITE_TABLE is not compatible with Oracle version"
// *Cause: One or more column definitions in the REWRITE_TABLE is
// either missing or incompatible with the current Oracle version.
// *Action: Connect to the appropriate schema,
// DROP TABLE REWRITE_TABLE and recreate it by invoking the
// admin/utlxrw.sql script prior to invoking the
// DBMS_MVIEW.EXPLAIN_REWRITE() API.
/
30382, 00000, "DROP MATERIALIZED VIEW %s.%s operation is not complete"
// *Cause: The drop materialized view operation got an unexpected error while
// dropping summary object.
// *Action: Issue the drop materialized view command again
/
30383, 00000, "specified dimension level does not exist in the attribute"
// *Cause: An attribute level was encountered that is not defined within the
// attribute.
//
// *Action: Check the attribute level name spelling.
/
30384, 00000, "specified column name does not exist in the attribute"
// *Cause: A column was encountered that is not defined within the attribute.
//
// *Action: Check the attribute column name spelling.
/
30385, 00000, "specified attribute relationship ('%s' determines '%s') exists"
// *Cause: The specified attribute relationship has already been declared
// in one of the attribute clauses
//
// *Action: Remove the duplicate attribute relationship
/
30386, 00000, "invalid SQL statement for DECLARE_REWRITE_EQUIVALENCE"
// *Cause: Either the source or destination statement is NULL
// *Action: Verify both source and destination statement are valid
/
30387, 00000, "invalid rewrite mode for REWRITE_EQUIVALENCE API"
// *Cause: The specified rewrite mode is not supported by REWRITE_EQUIVALENCE API
// *Action: Verify the rewrite mode is supported by REWRITE_EQUIVALENCE API
/
30388, 00000, "name of the rewrite equivalence is not specified"
// *Cause: The name of the rewrite equivalence is NULL
// *Action: Input a valid rewrite equivalence name
/
30389, 00000, "the source statement is not compatible with the destination statement"
// *Cause: The SELECT clause of the source statement is not compatible with
// the SELECT clause of the destination statement
// *Action: Verify both SELECT clauses are compatible with each other such as
// numbers of SELECT list items are the same and the datatype for
// each SELECT list item is compatible
/
30390, 00000, "the source statement is not equivalent to the destination statement"
// *Cause: the set of rows returned by the source SQL text is not the same as
// the set of rows returned by the destination SQL text
// *Action: Make sure both source and destination statement return the same number
// of rows
/
30391, 00000, "the specified rewrite equivalence does not exist"
// *Cause: the specified rewrite equivalence does not exist
// *Action: Verify the rewrite equivalence has been created
/
30392, 00000, "the checksum analysis for the rewrite equivalence failed"
// *Cause: the given checksum does not match with that generated from the
// source and destination statements.
// *Action: Verify the create safe rewrite equivalence statement to see if it
// has been modified.
/
30393, 00000, "a query block in the statement did not rewrite"
// *Cause: A query block with a REWRITE_OR_ERROR hint did not rewrite
// *Action: Verify the rewrite equivalence has been created
/
30394, 00000, "source statement identical to the destination statement"
// *Cause: The source statement was identical to the destination statement
// *Action: Make sure both source and destination statements are not identical
/
/
30397, 00000, "multiple JOIN KEY clauses specified for the same child level"
// *Cause: Multiple JOIN KEY clauses were specified for a given child
// level in a dimension hierarchy.
//
// *Action: Eliminate the redundant JOIN KEY clauses.
/
/
30398, 00000, "illegal JOIN KEY clause"
// *Cause: A JOIN KEY clause was specified that did not conform to certain
// requirements. A JOIN KEY clause connecting a child level with its
// non-immediate ancestor level is allowed only when that child level
// and its ancestor level satisfy the following conditions:
// 1. The immediate parent of the child level must be a skip level.
// 2. The child level cannot be a skip level.
// 3. The ancestor level must be a non-skip level.
// 4. The ancestor level must be the nearest non-skip level to
// the child level in the hierarchy.
//
// *Action: Modify the JOIN KEY clause so that it satisfies the conditions
// mentioned above.
/
/
30399, 00000, "a skip level must have at least one column that allows NULL values"
// *Cause: A SKIP clause cannot be specified with a level when all of the
// columns that make up the level have NOT NULL constraints.
//
// *Action: Drop the SKIP clause.
/
/
30400, 00000, "identical JOIN KEY clauses"
// *Cause: Two JOIN KEY clauses with identical child keys and parent levels
// were specified.
//
// *Action: Eliminate the redundant JOIN KEY clause.
/
/
30401, 00000, "JOIN KEY columns must be non-null"
// *Cause: The dimension statement failed because the column(s) in the JOIN
// KEY clause permitted NULL values. The JOIN KEY columns are related
// to the columns of the dimension's skip levels in one or both of the
// following ways:
// 1. A skip level is defined over one or more of the JOIN KEY
// columns.
// 2. The attribute clauses of a skip level determine one or more of
// the JOIN KEY columns.
//
// *Action: Modify the JOIN KEY columns so that they do not allow NULL
// values.
30402, 00000, "access advisor debug/testing trace"
// *Document: NO
// *Cause:
// *Action: access advisor debug/testing
/
/
30403, 00000, "Daylight Saving Time (DST) upgrade in progress"
// *Cause: Daylight Saving Time upgrade was in progress on a table
// in the materialized view.
// *Action: Wait until all tables in the materialized view have gone
// through DST upgrade.
/
/
30404, 00000, "general event for summary"
// *Document: NO
// *Cause: N/A
// *Action: This internal event is used to enable various actions
// associated with summary. The event level is interpreted
// as a bitmap of actions to enable.
//
// *Comment: Not for general purpose use.
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 enable acquiring Rewrite enqueue
/
/
30405, 00000, "hive_table_name missing"
// *Cause: The Hive table name was missing.
// *Action: Provide the name of the hive table in order to fetch its
// metadata.
/
/
30406, 00000, "invalid or missing cluster_id or hive URI"
// *Cause: The cluster ID or the hive URI (Uniform Resource Identifier)
// or both were missing.
// *Action: Provide the missing cluster ID or hive URI in order to fetch
// hive metadata.
/
30407, 00000, "external table not found"
// *Cause: The external table was not found.
// *Action: Create the specified external table before attempting the
// operation.
/
30408, 00000, "invalid platform for hive catalog views or DBMS_HADOOP package"
// *Cause: There was an attempt to create hive catalog views or a DBMS_HADOOP package
// on a platform other than Linux x86-64.
// *Action: None.
//
/
30409, 00000, "External table partitions are identical to hive table partitions."
// *Cause: There was an attempt to synchronize an external table with a hive table
// when external table partitions were identical to the hive table partitions.
// *Action: None.
/
30410, 00000, "External table metadata is incompatible with the source hive table."
// *Cause: There was an attempt to synchronize an external table with the source hive
// table with incompatible metadata.
// *Action: None.
/
30411, 00000, "Partition collision occurred because of a data type conversion error."
// *Cause: There was an attempt to create an Oracle external table partition from a
// Hive table partition with a partition key value identical to that of an
// existing partition. The Hive table partition key was of type decimal, but
// the Oracle table partition key was of type NUMBER(10, 0).
// *Action: None.
/
30413, 00000, "Oracle table to be merged with Hive table is already a hybrid partitioned table."
// *Cause: An attempt was made to merge external Hive table partitions with an already hybrid
// partitioned Oracle table.
// *Action: None.
/
30414, 00000, "Oracle table to be merged with Hive table must be a list partitioned table."
// *Cause: An attempt was made to merge external Hive table partitions with an unpartitioned
// or a non-list partitioned Oracle table.
// *Action: None.
/
30415, 00000, "Oracle table to be merged with Hive table cannot be an external table."
// *Cause: An attempt was made to merge external Hive table partitions with an Oracle
// external table.
// *Action: None.
/
30416, 00000, "Hive table to be merged with Oracle table has to be a non-empty partitioned table."
// *Cause: An attempt was made to merge an external non-partitioned or empty partitioned Hive table
// with an Oracle table.
// *Action: None.
30417, 00000, "The EXTERNAL MODIFY clause cannot be used to modify the location for an ORACLE_BIGDATA external table."
// *Cause: The EXTERNAL MODIFY clause was used to change the location for
// an ORACLE_BIGDATA external table.
// *Action: Create a new external table for the new location.
/
/ Error Numbers 30420 - 30479 are reserved for Summary Advisor and
/ Refresh Packages. These are raised by calling
/ dbms_sys_error.raise_system_error.
/
30420, 00000, "%s is not a valid identifier"
// *Cause: All identifiers used in the DBMS_OLAP package must have at most 30
// characters, and must start with a letter that is followed
// by any combination of letters, numerals, and the signs
// '$', '_', and '#'. Other characters cannot be used in identifiers.
// The rules for DBMS_OLAP identifiers are the same as for PL/SQL
// identifiers.
// *Action: Rename object to conform to the DBMS_OLAP naming rules and
// try again.
/
30430, 00000, "list does not contain any valid summaries"
// *Cause: List is empty or does not contain the names of existing summaries
//
// *Action: Verify that the list of names passed to refresh
// contains the name of at least one existing summary object
/
30431, 00000, "refresh method must be ANY or INCREMENTAL or FORCE_FULL, not %s"
// *Cause: An invalid refresh method was specified
//
// *Action: Verify that the refresh method is one of 'ANY' or 'INCREMENTAL' or 'FORCE_FULL'
/
30432, 00000, "summary '%s.%s' is in INVALID state"
// *Cause: The summary is in INVALID state and cannot be refreshed
//
// *Action:
/
30433, 00000, "'%s.%s' is not a summary"
// *Cause: There is no such summary, therefore it cannot be refreshed
//
// *Action: Verify the correct name of the summary
/
30434, 00000, "refresh method must be one of FC?AN, not '%s'"
// *Cause: An invalid refresh method was specified
//
// *Action: Verify that the refresh method is one of 'FC?AN'
/
30435, 00000, "job_queue_processes must be non-zero in order to refresh summaries"
// *Cause: The server must be started with parameter 'job_queue_processes' greater than zero
//
// *Action: Correct the value of job_queue_processes and restart the server instance
/
30436, 00000, "unable to open named pipe '%s'"
// *Cause: The refresh process was unable to open a named pipe to the job queue process
// usually because of insufficient system resources
//
// *Action: This is an internal error. Notify ORACLE technical support
/
30437, 00000, "all job queue processes have stopped running"
// *Cause: All of the job queue processes used by refresh have stopped for some reason.
// At least one job queue process must be running in order to refresh summaries.
//
// *Action: This is an internal error. Notify ORACLE technical support
/
30438, 00000, "unable to access named pipe '%s'"
// *Cause: The refresh process was unable to access a named pipe to the job queue process
// after it successfully opened the pipe. This usually indicates an internal or
// operating system error condition.
//
// *Action: This is an internal error. Notify ORACLE technical support
/
30439, 00000, "refresh of '%s.%s' failed because of %s"
// *Cause: The refresh job queue process encountered an error and is reporting it. The
// accompanying text of the message indicates cause of the error
// *Action: Varies, depending upon the reported cause.
/
30440, 00000, "can't fast refresh;refresh complete or set event 30441 for partial refresh "
// *Cause: Both DML and direct-load are performed against detail tables. Fast
// refresh can only process direct-load inserts.
// *Action:Refresh complete or set event 30441 to enable partial refresh with
// only direct-load inserts
/
30441, 00000, "enable partial refresh when both DML and direct load inserts occur"
// *Cause:
// *Action: level 1 - enable partial refresh with only direct-load inserts
/
30442, 00000, "can not find the definition for filter %s "
// *Cause: For the specified filterid parameter, there is no corresponding
// filter definition found in the advisor repository
// *Action: Use a valid filterid geneated by the create_filter function
/
30443, 00000, "definition for filter %s's item %s is invalid"
// *Cause: The specified filter is invalid. It contains at least one
// invalid filter item. If a filter item has a string list, it
// becomes illegal when the string list cannot be successfully parsed.
// If the filter item contains a range definition, and the lower
// bound of the range is greater than the higher bound, the item
// also becomes invalid.
// *Action: Remove the illegal filter with the purge_filter sub-program and
// redefine a correct filter
/
30444, 00000, "rewrite terminated by the sql analyzer"
// *Cause: The sql analyzer terminates the rewrite process
// *Action: This is an internal error. Notify ORACLE technical support
/
30445, 00000, "workload queries not found"
// *Cause: No workload queries in the advisor repository can satifiy the
// specified filter
// *Action: Redefine a new filter or load additional workload queries that can
// satisfy the specified filter
/
30446, 00000, "valid workload queries not found"
// *Cause: None of the specified queries can be successfully parsed. The error
// may come from many sources: SQL syntax error, the owner
// specified by the load_workload subprograms do not match the
// real user who generates the SQL statement
// *Action: Only load valid SQL statements into the advisor repository. Make
// sure the statements can be parsed with privilege of the owner
// as specified in the owner parameter of the load_workload()
// subprogram.
/
30447, 00000, "internal data for run number %s is inconsistent"
// *Cause: Users should not explicitly modify summary advisor's internal
// tables. Such modifications may cause inconsistency in the
// internal tables and result in this error.
//
// *Action: Users can call the DBMS_OLAP.PURGE_RESULTS subprogram to remove
// the inconsistent data from summary advisor's internal tables
/
30448, 00000, "internal data of the advisor repository is inconsistent"
// *Cause: Users should not explicitly modify summary advisor's internal
// tables. Such modifications may cause inconsistency in the
// internal tables and result in this error.
//
// *Action: This is an internal error. Notify ORACLE technical support
/
30449, 00000, "syntax error in parameter %s"
// *Cause: The syntax for the specified parameter is incorrect
//
// *Action: Check ORACLE documentation for the correct syntax
/
30450, 00000, "refresh_after_errors was TRUE; The following MVs could not be refreshed: %s"
// *Cause: One or more errors occurred during a refresh of multiple summaries.
// *Action: The number_of_failures parameter returns the count of how many failures
// occurred. The trace logs for each refresh operation describe the
// each individual failure in more detail
/
30451, 00000, "internal error"
// *Cause: An internal error was detected by the summary refresh subsystem, and
// aborted the refresh operation
// *Action: Notify ORACLE support.
/
30452, 00000, "cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X)"
// *Cause: Incremental refresh of summaries requires a COUNT(X) column in order to incrementally
// refresh AVG(X). It requires both SUM(X) and COUNT(X) columns in order to
// in refresh STDDEV(X) or VARIANCE(X)
// *Action: Make sure that the required columns are part of the summary definition if incremental
// refresh capability is desired.
/
30453, 00000, "summary contains AVG without corresponding COUNT"
// *Cause: Incremental refresh of summaries with AVG(X) requires a COUNT(X) column
// to be included in the summary definition
// *Action: Make sure that the required columns are part of the summary definition if incremental
// refresh capability is desired.
/
30454, 00000, "summary contains STDDEV without corresponding SUM & COUNT"
// *Cause: Incremental refresh of summaries with STDDEV(X) requires COUNT(X) and SUM(X) columns
// to be included in the summary definition
// *Action: Make sure that the required columns are part of the summary definition if incremental
// refresh capability is desired.
/
30455, 00000, "summary contains VARIANCE without corresponding SUM & COUNT"
// *Cause: Incremental refresh of summaries with VARIANCE(X) requires COUNT(X) and SUM(X) columns
// to be included in the summary definition
// *Action: Make sure that the required columns are part of the summary definition if incremental
// refresh capability is desired.
/
30456, 00000, "'%s.%s' cannot be refreshed because of insufficient privilege"
// *Cause: The user lacks one or more permissions that are required in order to refresh summaries.
// *Action: Make sure that the user is granted all required privileges.
/
30457, 00000, "'%s.%s' cannot be refreshed because of unmnanaged NOT NULL columns in container"
// *Cause: The container object for the summary contains one or more unmanaged columns do not
// allow nulls, and which do not specify a default valur for those columns.
// *Action: Make sure that default values are specified for all NOT NULL columns that are not
// part of the summary definition.
/
30458, 00000, "'%s.%s' cannot be refreshed because the refresh mask is %s"
// *Cause: An attempt was made to incrementally refresh a summary that is not incrementally
// refreshable.
// *Action: Do not attempt to incrementally refresh the summary; use full refresh instead.
/
30459, 00000, "'%s.%s' cannot be refreshed because the refresh method is NONE"
// *Cause: An attempt was made to refresh a summary whose refresh method is NONE
// *Action: Summaries whose refresh method is NONE (NEVER REFRESH) cannot be refreshed.
// Alter the summary to change the default refresh method from NONE to some other value.
/
30460, 00000, "'%s.%s' cannot be refreshed because it is marked UNUSABLE"
// *Cause: An attempt was made to refresh a summary which is UNUSABLE
// *Action: Determine why the summary is UNUSABLE, re-enable it, and retry the refresh.
/
30461, 00000, "'%s.%s' cannot be refreshed because it is marked DISABLED"
// *Cause: An attempt was made to refresh a summary which is DISABLED
// *Action: Determine why the summary is DISABLED, re-enable it, and retry the refresh.
/
30462, 00000, "unsupported operator: %s"
// *Cause: An attempt was made to refresh a summary containing an unsupported operator
// *Action: Verify that all columns of the summary contain expressions that are refreshable.
/
30463, 00000, "'%s' is not a detail table of any summary"
// *Cause: The list of tables passed to refresh_dependent contains at least one
// invalid table name. That table is not a detail table of any summary and
// is therefore an invalid input to refresh_dependent
//
// *Action: Verify the correct name of all tables in the list
/
30464, 00000, "no summaries exist"
// *Cause: A call was made to refresh_all_mviews, but no summaries exist.
// At least one summary must exist before calling refresh_all_mviews
//
// *Action: Create one or more summaries
/
30465, 00000, "supplied run_id is not valid: %s"
// *Cause: There are three possible causes: The specified run_id does not
// exist; the run_id was created by another user other than the
// current user; the run_id has already been used.
//
// *Action: Call DBMS_OLAP.CREATE_ID to create a new id
/
30466, 00000, "can not find the specified workload %s"
// *Cause: The specified workload_id is not valid
//
// *Action: Use a valid workload_id or DBMS_OLAP.WORKLOAD_ALL
/
30467, 00000, "internal data for filter number %s is inconsistent"
// *Cause: Users should not explicitly modify summary advisor's internal
// tables. Such modifications may cause inconsistency in the
// internal tables and result in this error.
//
// *Action: Users can call the DBMS_OLAP.PURGE_FILTER subprogram to remove
// the inconsistent data from summary advisor's internal tables
/
30475, 00000, "feature not enabled: %s"
// *Cause: The specified feature is not enabled.
// *Action: Do not attempt to use this feature.
/
30476, 00000, "PLAN_TABLE does not exist in the user's schema"
// *Cause: Estimate_Summary_Size uses Oracle SQL "EXPLAIN PLAN"
// command to estimate cardinality of the specified select-clause.
// This requires a table called the PLAN_TABLE in the user's
// schema. For more information refer to the SQL Reference Manual.
// *Action: Create the PLAN_TABLE as described for EXPLAIN PLAN. On most
// systems a script utlxplan.sql will create this table.
/
30477, 00000, "The input select_clause is incorrectly specified"
// *Cause: The input select-clause parameter to Estimate_Summary_Size
// is incorrectly specified and cannot be compiled.
// *Action: Check the syntax of the select-clause.
/
30478, 00000, "Specified dimension does not exist"
// *Cause: the specified dimension to be verified does not exist
// *Action: Check the spelling of the dimension name
/
30479, 00000, "Summary Advisor error\n%s"
// *Cause: An error has occurred in the Summary Advisor package
// This message will be followed by a second message giving
// more details about the nature of the error.
// *Action: See the Summary Advisor documentation
// for an explanation of the second error message.
//
/
/
/ Error Numbers 30480 - 30499 are reserved for OLAP operations
/
30480, 00000, "DISTINCT option not allowed with GROUP BY CUBE or ROLLUP"
// *Cause:
// *Action:
30481, 00000, "GROUPING function only supported with GROUP BY CUBE or ROLLUP"
// *Cause:
// *Action:
30482, 00000, "DISTINCT option not allowed for this function"
// *Cause:
// *Action:
30483, 00000, "window functions are not allowed here"
// *Cause: Window functions are allowed only in the SELECT list of a query.
// And, window function cannot be an argument to another window or group
// function.
// *Action:
30484, 00000, "missing window specification for this function"
// *Cause: All window functions should be followed by window specification,
// like <function>(<argument list>) OVER (<window specification>)
// *Action:
30485, 00000, "missing ORDER BY expression in the window specification"
// *Cause: Either the ORDER BY expression is mandatory for this function, or
// there is an aggregation group without any ORDER by expression.
// *Action:
30486, 00000, "invalid window aggregation group in the window specification"
// *Cause: If the window specification is specified
// using RANGE option and there are multiple ORDER BY expressions, then
// the aggregation group cannot contain any expression (It can only
// have CURRENT ROW, UNBOUNDED PRECEDING, or UNBOUNDED FOLLOWING).
// First end point (bound) cannot be UNBOUNDED FOLLOWING and second end
// point cannot be UNBOUNDED PRECEDING. If the first end point is
// CURRENT ROW, then second end point can only be CURRENT ROW or <expr>
// /UNBOUNDED FOLLOWING. If the first end point is <expr> FOLLOWING,
// then second end point can only be <expr>/UNBOUNDED FOLLOWING.
// *Action:
30487, 00000, "ORDER BY not allowed here"
// *Cause: DISTINCT functions and RATIO_TO_REPORT cannot have an ORDER BY
// *Action:
30488, 00000, "argument should be a function of expressions in PARTITION BY"
// *Cause: The argument of the window function should be a constant for
// a partition.
// *Action:
30489, 00000, "Cannot have more than one rollup/cube expression list"
// *Cause: GROUP BY clause has more than one rollup/cube expression list.
// *Action: Modify the query such that only one rollup/cube expressions
// appear per sub-query.
30490, 00000, "Ambiguous expression in GROUP BY ROLLUP or CUBE list"
// *Cause: An expression in the GROUP BY ROLLUP or CUBE list matches an
// expression in the ordinary GROUP BY expression list
// *Action: Remove the expression from either ordinary GROUP BY expression list
// or ROLLUP or CUBE expression list
30491, 00000, "missing ORDER BY clause"
// *Cause:
// *Action:
30492, 00000, "One of FIRST or LAST keywords is expected."
// *Cause:
// *Action:
30493, 00000, "The percentile value should be a number between 0 and 1."
// *Cause: A percentile value for PERCENTILE_CONT or PERCENTILE_DISC function
// is specified out of range.
// *Action: Specify a value from [0,1].
30494, 00000, "The argument [%s] of WIDTH_BUCKET function is NULL or invalid."
// *Cause:
// *Action:
30495, 00000, "The argument should be of numeric or date/datetime type."
// *Cause:
// *Action:
30496, 00000, "Argument should be a constant."
// *Cause:
// *Action:
30497, 00000, "Argument should be a constant or a function of expressions in GROUP BY."
// *Cause:
// *Action:
30498, 00000, "ALL option not allowed for this function"
// *Cause:
// *Action:
30499, 00000, "Event to dump stats used during grouping sets transformation"
// *Document: NO
// *Cause: N/A
// *Action: Dumps column stats used during grouping sets transformation
/
/
/
/ Error Numbers 30500 - 30549 are reserved for system triggers
/
30500, 00000, "database open triggers and server error triggers cannot have BEFORE type"
// *Cause: An attempt was made to create a trigger that fires before
// the database is open or before server errors, but these types of
// triggers are not supported.
// *Action: Do not attempt to create a trigger that fires before the database
// is open or before server errors.
/
30501, 00000, "instance shutdown triggers cannot have AFTER type"
// *Cause: An attempt was made to create a trigger that fires after
// an instance shutdown, but this type of trigger is not
// supported.
// *Action: Do not attempt to create a trigger that fires after an
// instance shutdown.
/
30502, 00000, "system triggers cannot have INSERT, UPDATE, or DELETE as triggering events"
// *Cause: An attempt was made to create a system trigger with INSERT,
// UPDATE, or DELETE triggering events, but this type of trigger
// is not supported because a system trigger does not have a base
// table.
// *Action: Do not attempt to create a system trigger with INSERT, UPDATE,
// or DELETE triggering events.
/
30503, 00000, "system triggers cannot have a REFERENCING clause"
// *Cause: An attempt was made to use a REFERENCING clause with a system
// trigger, but this type of trigger is not supported because
// a system triggers does not have a base table.
// *Action: Do not use a REFERENCING clause with a system trigger.
/
30504, 00000, "system triggers cannot have a FOR EACH ROW clause"
// *Cause: An attempt was made to use a FOR EACH ROW clause with a system
// trigger, but this type of trigger is not supported because
// a system triggers does not have a base table.
// *Action: Do not use a FOR EACH ROW clause with a system trigger.
/
30505, 00000, "system triggers should not reference a column in a WHEN clause"
// *Cause: An attempt was made to use a WHEN clause to reference a column
// with a system trigger, but this type of trigger is not supported
// because a system trigger does not have a base table.
// *Action: Change the WHEN clause to an appropriate clause.
/
30506, 00000, "system triggers cannot be based on tables or views"
// *Cause: An attempt was made to base a system trigger on a table or a
// view.
// *Action: Make sure the type of the trigger is compatible with the base
// object.
/
30507, 00000, "normal triggers cannot be based on a schema, a database, or a pluggable database"
// *Cause: An attempt was made to base a normal trigger on a schema,
// a database, or a pluggable database, but normal triggers can be
// based only on tables or views.
// *Action: Make sure the type of the trigger is compatible with the base
// object.
/
30508, 00000, "client logon triggers cannot have BEFORE type"
// *Cause: An attempt was made to create a trigger that fires before
// logon. This type of trigger is not supported.
// *Action: Do not attempt to create a trigger that fires before logon.
/
30509, 00000, "client logoff triggers cannot have AFTER type"
// *Cause: An attempt was made to create a trigger that fires after
// logoff. This type of trigger is not supported.
// *Action: Do not attempt to create a trigger that fires after logoff.
/
30510, 00000, "system triggers cannot be defined on the schema of SYS user"
// *Cause: An attempt was made to define a system trigger on the schema of
// SYS user. This type of trigger is not supported currently.
// *Action: Do not attempt to create a system trigger defined on the
// schema of SYS user.
/
30511, 00000, "invalid DDL operation in system triggers"
// *Cause: An attempt was made to perform an invalid DDL operation
// in a system trigger. Most DDL operations currently are not
// supported in system triggers. The only currently supported DDL
// operations are table operations, pluggable database operations,
// ALTER COMPILE operations, and ALTER SESSION operations.
// *Action: Remove invalid DDL operations in system triggers.
/
30512, 00000, "cannot modify %s.%s more than once in a transaction"
// *Cause: An attempt was made to modify an object more than once in a
// transaction. This error is usually caused by a DDL statement that
// fires a system trigger that tries to modify the same object.
// It can also happen when an attempt is made to perform more than
// one DDL operation on a queue table in the same transaction
// without issuing a commit between operations.
// *Action: Do not create system triggers that might modify an already
// modified object. Also, do not specify more than one DDL
// operation on a queue table in the same transaction.
/
30513, 00000, "cannot create system triggers of INSTEAD OF type"
// *Cause: Only BEFORE or AFTER triggers can be created on system events.
// *Action: Change the trigger type to BEFORE or AFTER.
/
30514, 00000, "system trigger cannot modify tablespace being made read only"
// *Cause: A beofre trigger tries to modify a tablespace which is being
// made READ ONLY as the part of DDL oepration
// *Action: Modify the trigger to avoid modifications to the objects
// in the same tablespace as the one which is being made read only,
// or use autonomous transactions to commit modifications
/
30515, 00000, "suspend triggers cannot have BEFORE type"
// *Cause: An attempt was made to create a trigger that fires before
// execution suspended. This type of trigger is not supported.
// *Action: Do not attempt to create a trigger that fires before execution
// suspended.
/
30516, 00000, "database role change triggers cannot have BEFORE type"
// *Cause: An attempt was made to create a trigger that fires before
// the role change completed. This type of trigger is not supported.
// *Action: Do not attempt to create a trigger that fires before the role
// change completes.
/
/ Error Numbers 30550 - 30559 are reserved for functional indexes
/
30550, 00000, "index depends on a package/function spec/body which is not valid"
// *Cause: the functional indexes depends on some invalid/non-existent
// package/function spec/body
// *Action: verify that all the package/functions which the index depends on
// exist and are valid
/
30551, 00000, "The index depends on a package/type body which does not exist"
// *Cause: the functional indexes depends on a package/type body which
// does not exist
// *Action: create the package/type body
/
30552, 00000, "The package/procedure/function cannot be changed"
// *Cause: The package/procedure/function is deterministic and some object
// depends on it
// *Action: Drop the other object which depends on the
// package/function/procedure you are trying to change
/
30553, 00000, "The function is not deterministic"
// *Cause: The function on which the index is defined is not deterministic
// *Action: If the function is deterministic, mark it DETERMINISTIC. If it
// is not deterministic (it depends on package state, database state,
// current time, or anything other than the function inputs) then
// do not create the index. The values returned by a deterministic
// function should not change even when the function is rewritten or
// recompiled.
/
30554, 00000, "function-based index %s.%s is disabled"
// *Cause: An attempt was made to access a function-based index that has
// been marked disabled because the function on which the index
// depends has been changed.
// *Action: Perform one of the following actions:
// -- drop the specified index using the DROP INDEX command
// -- rebuild the specified index using the ALTER INDEX REBUILD command
// -- enable the specified index using the ALTER INDEX ENABLE command
// -- make the specified index usable using the ALTER INDEX UNUSABLE
// command
/
30555, 00000, "global index partitioning key is an expression"
// *Cause: An attempt was made to use an expression as a partitioning key in
// an index.
// *Action: Do not attempt to use an expression as index partitioning key.
/
30556, 00000, "either functional or bitmap join index is defined on the column to be modified"
// *Cause : An ALTER TABLE MODIFY COLUMN was issued on a column on which
// either a functional index or bitmap join index exists.
// *Action: Drop the functional or bitmap join index before attempting to modify the column.
/
30557, 00000, "function based index could not be properly maintained"
// *Cause : The user updated a column on which a function based index is
// present which was not successfully updated
// *Action : Determine the error in updating the index and fix the problem
/
30558, 00000, "internal error [%s] in function based index"
// *Cause: This is an internal error.
// Action: Contact Worldwide support with the exact error text.
/
/
/ Error Numbers 30560 - 30574 are reserved for additional parser errors
/
30560, 00000, "SAMPLE clause not allowed"
// *Cause:
// *Action:
30561, 00000, "SAMPLE option not allowed in statement with multiple table references"
// *Cause:
// *Action:
30562, 00000, "SAMPLE percentage must be in the range [0.000001,100)"
// *Cause:
// *Action:
30563, 00000, "outer join operator (+) is not allowed here"
// *Cause: An attempt was made to reference (+) in either the select-list,
// CONNECT BY clause, START WITH clause, or ORDER BY clause.
// *Action: Do not use the operator in the select-list, CONNECT BY clause,
// START WITH clause, or ORDER BY clause.
30564, 00000, "Index maintainence clause not allowed for ADD partition to RANGE partitioned tables"
// *Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for
// ADD partition to a HASH partitioned table or ADD subpartition to a
// composite partitioned table.
// *Action:Remove clause and reissue operation
30565, 00000, "Only one INVALIDATE or UPDATE GLOBAL INDEXES clause may be specified"
// *Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES was specified more
// than once.
// *Action:Remove all but one of the INVALIDATE or UPDATE GLOBAL INDEXES
// clause and reissue the statement
30566, 00000, "Index maintainence clause not allowed for this command"
// *Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is not allowed
// for this command
// *Action:Remove clause and reissue operation
30567, 00000, "name already used by an existing log group"
// *Cause: The specified log group name has to be unique.
// *Action: Specify a unique name for the log group. The name
// cannot be the same as any other log group, constraint, or
// cluster hash expression.
30568, 00000, "cannot drop log group - nonexistent log group"
// *Cause: The <log_group_name> specified in alter table drop log group
// is incorrect or nonexistent.
// *Action: Reenter the statement using the correct log group name.
30569, 00000, "data type of given column is not supported in a log group"
// *Cause: An attempt was made to include a column in a log group with one of these
// unsupported data types: LONG, VARRAY, nested table, object,
// or LOB.
// *Action: Change the column data type or remove the log group. Then, retry
// the operation.
/
30570, 00000, "SEGMENT SPACE MANAGEMENT option already specified"
// *Cause: In CREATE TABLESPACE, the SEGMENT SPACE MANAGEMENT option was
// specified more than once.
// *Action: Remove all but one of the SEGMENT SPACE MANAGEMENT specifications.
/
30571, 00000, "invalid SEGMENT SPACE MANAGEMENT clause"
// *Cause: An invalid option appears for SEGMENT SPACE MANAGEMENT clause.
// *Action: Specify one of the valid options: AUTO, MANUAL.
/
30572, 00000, "AUTO segment space management not valid with DICTIONARY extent management"
// *Cause: in CREATE TABLESPACE, the AUTO SEGMENT SPACE MANAGEMENT was used
// with a DICTIONARY extent management clause.
// *Action: Either specify LOCAL extent management or remove the AUTO
// SEGMENT SPACE MANAGEMENT specification.
/
30573, 00000, "AUTO segment space management not valid for this type of tablespace"
// *Cause: in CREATE TABLESPACE, the AUTO SEGMENT SPACE MANAGEMENT was used
// while creating an UNDO or TEMPORARY tablespace.
// *Action: Remove the AUTO SEGMENT SPACE MANAGEMENT clause.
/
30574, 00000, "Cannot create rollback segment in tablespace with AUTO segment space management"
// *Cause: A rollback segment is being created in a tablespace that was created
// with AUTO segment space management.
// *Action: Create the rollback segment in a different tablespace.
/
/
/ Error Numbers 30575 - 30624 are reserved for ConText Cartridge
/
30575, 00000, "ConText Option not installed"
// *Cause: Oracle executable doesn't have ConText Option linked in
// *Action: get the correct version of Oracle
30576, 00000, "ConText Option dictionary loading error"
// *Cause: ConText dictionary tables may be corrupted
// *Action: not a user error
30577, 00000, "SAMPLE group size must be in the range [1,UB4MAXVAL]"
// *Cause:
// *Action:
30579, 00000, "enables order by PRIMARY KEY for base table scan during create index"
// *Document: NO
// *Cause:
// *Action: Set this event to enable order by PRIMARY KEY for base table
// scan during creation of Text index.
// *Comment: This event is primarily used for internal tests that require
// consistent docid ordering. Turning on this event can
// result in poor create index performance.
/
/
/
/
/
/ Error Numbers 30625 - 30644 are reserved for Inter Language Method Services
/ (ILMS)
/
30625, 00000, "method dispatch on NULL SELF argument is disallowed"
// *Cause: A member method of a type is being invoked with a NULL SELF
// argument.
// *Action: Change the method invocation to pass in a valid self argument.
30626, 00000, "function/procedure parameters of remote object types are not supported"
// *Cause:
// *Action:
30627, 00000, "Oracle event to pass temp lobs by ref from sql"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
30628, 00000, "Oracle event to turn off passing temp lobs by ref"
// *Cause:
// *Action: set this event only under the supervision of Oracle development
/
/
/ Error Numbers 30645 - 30664 are reserved for External tables
/
30645, 00000, "reject limit out of range"
// *Cause: Reject limit specifies the number of records rejected before
// terminating a table scan. The range is a either a number between
// 1..100000 or UNLIMITED if no limit is intended.
// *Action: Change the token representing the reject limit to either a number
// in the range of 0 and 100000 or the keyword UNLIMITED.
/
/
30646, 00000, "schema for external table type must be SYS"
// *Cause: A schema other then SYS was specified for the TYPE
// *Action: For this version of oracle server always use schema name SYS.
/
/
30647, 00000, "error retrieving access parameters for external table %s.%s"
// *Cause: an error occurred when fetching the access parameters for
// the specified external table.
// *Action: If the access parameter is a query which returns a CLOB,
// check EXTERNAL_TAB$ to make sure the query is correct.
/
30648,0000, "missing LOCATION keyword"
// *Cause:
// *Action:
/
30649,0000, "missing DIRECTORY keyword"
// *Cause: DEFAULT DIRECTORY clause missing or incorrect.
// *Action: Provide the DEFAULT DIRECTORY.
/
30650,0000, "missing PARAMETERS keyword"
// *Cause:
// *Action:
/
30651,0000, "missing CLOB keyword"
// *Cause:
// *Action:
/
30652,0000, "missing LIMIT keyword"
// *Cause:
// *Action:
/
30653,0000, "reject limit reached"
// *Cause: the reject limit has been reached.
// *Action: Either cleanse the data, or increase the reject limit.
/
30654,0000, "missing DEFAULT keyword"
// *Cause: DEFAULT DIRECTORY clause not specified or incorrect.
// *Action: Provide the DEFAULT DIRECTORY.
/
30655,0000, "cannot select FOR UPDATE from external organized table"
// *Cause: A select for update on an external table was attempted.
// *Action: Don't do it!
/
30656,0000, "column type not supported on external organized table"
// *Cause: Attempt to create an external organized table with a column
// of type LONG, LOB, BFILE, ADT, or VARRAY.
// *Action: These column types are not supported, change the DDL.
/
30657,0000, "operation not supported on external organized table"
// *Cause: User attempted on operation on an external table which is
// not supported.
// *Action: Don't do that!
/
30658,0000, "attempt was made to create a temporary table with EXTERNAL organization"
// *Cause: An attempt was made to create an External Organized Temporary table.
// This is not supported.
// *Action: Don't do that!
/
30659,0000, "too many locations specified for external table"
// *Cause: An attempt was made to create or query an external organized table with
// more than the maximum allowable (32767) locations specified.
// *Action: Don't do that, use fewer location clauses. Either consider
// concatenating the input files, or, creating two external tables
// with the input files split between them.
/
30660,0000, "event to enable external table ODM reads for all file sizes when testing"
// *Document: NO
// *Cause:
// *Action: Use ODM for all external table file sizes.
/
30661,0000, "NOT NULL constraint violated on fetch from external table (%s)"
// *Cause: A NULL entry was detected in the column with a NOT NULL constraint
// during a fetch from an external table.
// *Action: Remove the NOT NULL constraint on that column or update the external
// table entry.
30662, 00000, "Hadoop dump file trailers event"
// *Document: NO
// *Cause: Explicitly set.
// *Action: Set this event only in a Hadoop environment.
// *Comment: Turn on/off writing of Hadoop dump file trailers.
/
30663, 00000, "An EXTERNAL MODIFY clause can only be specified for an external table."
// *Cause: An EXTERNAL MODIFY clause was specified when querying an internal table.
// *Action: Remove the EXTERNAL MODIFY clause from the query.
/
30664, 00000, "column %s not found in projected column list for external table"
// *Cause: A requested column was not found in the projected column list.
// *Action: Remove the column from the query and retry.
/
/////////////////////////////////////////////////////////////////////////////
/ 30665 - 30675 are reserved for 12g SQL enhancements projects
/////////////////////////////////////////////////////////////////////////////
30665,0000, "invalid NOT NULL constraint specified on a DEFAULT ON NULL column"
// *Cause: A NOT NULL constraint was not specified correctly on a
// DEFAULT ON NULL column.
// *Action: If a NOT NULL constraint is specified on a DEFAULT ON NULL column,
// it must be enabled and nondeferrable.
30666,0000, "cannot modify NOT NULL constraint on a DEFAULT ON NULL column"
// *Cause: The NOT NULL constraint on a DEFAULT ON NULL column could not be
// modified.
// *Action: Do not modify the NOT NULL constraint on a DEFAULT ON NULL column.
30667,0000, "cannot drop NOT NULL constraint on a DEFAULT ON NULL column"
// *Cause: The NOT NULL constraint on a DEFAULT ON NULL column could not be
// dropped.
// *Action: Do not drop the NOT NULL constraint on a DEFAULT ON NULL column.
// The only way to drop the constraint is to remove the ON NULL
// property of the column default.
30668,0000, "LATERAL cannot follow CROSS APPLY or OUTER APPLY"
// *Cause: An attempt was made to follow the CROSS APPLY or OUTER APPLY
// keyword with the LATERAL keyword.
// *Action: Do not include the LATERAL keyword after CROSS APPLY or
// OUTER APPLY.
30669,0000, "table can have only one identity column"
// *Cause: An attempt was made to specify more than one identity column
// on a table.
// *Action: Specify only one identity column per table.
30670,0000, "invalid NOT NULL constraint specified on an identity column"
// *Cause: A NOT NULL constraint was not specified correctly on an
// identity column.
// *Action: If a NOT NULL constraint is specified on an identity column,
// it must be enabled and nondeferrable.
30671,0000, "cannot modify NOT NULL constraint on an identity column"
// *Cause: The NOT NULL constraint on an identity column could not be
// modified.
// *Action: Do not modify the NOT NULL constraint on an identity column.
30672,0000, "cannot drop NOT NULL constraint on an identity column"
// *Cause: The NOT NULL constraint on an identity column could not be
// dropped.
// *Action: Do not drop the NOT NULL constraint on an identity column.
// The only way to drop the constraint is to remove the identity
// property of the column with ALTER TABLE MODIFY <column>
// DROP IDENTITY.
30673,0000, "column to be modified is not an identity column"
// *Cause: An attempt was made to modify the identity properties of
// that is not an identity column.
// *Action: Modify the identity properties of an identity column.
/
30674,0000, "identity column cannot have a default value"
// *Cause: An attempt was made to add a default value to an identity
// column.
// *Action: Do not modify an identity column with a default value.
/
30675,0000, "identity column must be a numeric type"
// *Cause: An attempt was made to create or alter an identity column
// with a non-numeric data type.
// *Action: Do not assign a non-numeric data type to an identity column.
/
/ Error Numbers 30676 - 30725 are reserved for Multilanguage Debug
/ infrastructure (kga/kqa)
/
30676, 00000, "socket read or write failed"
// *Cause: A problem kept a socket from reading or writing the
// expected amount of data. More specific information is not
// available.
// *Action: Try re-establishing a connection. You may need to restart
// whatever program is at the other end of the socket that failed,
// or you may need to have some problem on your network fixed.
30677, 00000, "session is already connected to a debugger"
// *Cause: An attempt to connect a session to a debugger could not proceed
// because the session is already connected to some debugger.
// *Action: Either use the option to force a connection or first disconnect the
// session from its existing debugger.
30678, 00000, "too many open connections"
// *Cause: An attempt to open a connection failed because too many
// are already open by this session. The number of allowed
// connections varies as some may be in use through other
// components which share the same pool of allowed connections.
// *Action: Retry after closing some other connection. The number of
// connections supported is currently not adjustable.
30679, 00000, "JDWP-based debugging not supported in this configuration"
// *Cause: An attempt to open a debugging connection failed because this
// server configuration cannot support the required asynchronous
// socket traffic detection.
// *Action: This feature will not work under this server configuration.
// Either the feature is not supported on this platform at all,
// or is available only through use of a protocol=tcp dispatcher
// in shared-server configurations. Please consult the
// platform-specific documentation and "readme" material.
30680, 00000, "debugger connection handshake failed"
// *Cause: A problem occurred when trying to establish a debugger
// connection. This might indicate that the port specified as
// the location of the debugger is actually being used by some
// other type of application.
// *Action: Correct the host or port specifications if they are incorrect,
// and verify that the debugger is properly waiting for a connection.
30681, 00000, "improper value for argument EXTENSIONS_CMD_SET"
// *Cause: An improper parameter value was provided in a call to
// DBMS_DEBUG_JDWP.CONNECT_TCP.
// *Action: Correct the indicated parameter value and try again.
30682, 00000, "improper value for argument OPTION_FLAGS"
// *Cause: An improper parameter value was provided in a call to
// DBMS_DEBUG_JDWP.CONNECT_TCP.
// *Action: Correct the indicated parameter value and try again.
30683, 00000, "failure establishing connection to debugger"
// *Cause: An error was indicated when trying to establish a connection
// to a debugger. Usually a TNS error will display along with
// this message to further explain the problem, although this
// TNS error will likely be hidden if you choose to trap the error.
// *Action: Correct the indicated parameter value and try again.
30684, 00000, "request timed out"
// *Cause: The request was not processed within the given time.
// *Action: Try the request at a later time.
30685, 00000, "package version is not compatible with Oracle version"
// *Cause: The installed version of the package from which this error
// is raised is not compatible with this release of Oracle.
// *Action: Install a compatible version of the package's spec and body.
30686, 00000, "no dispatcher accepted TCP/IP connection request"
// *Cause: A connection had to be routed through a local socket
// rather than a dispatcher. When this occurs, shared servers
// are less beneficial because the session that owns the socket
// cannot relinquish the process until the socket is closed. The
// most likely cause is that no dispatcher is configured for
// protocol=tcp.
// *Action: To improve the scalability of your configuration,
// configure a dispatcher for protocol=tcp. To route these
// particular connections through a particular set of dispatchers,
// you can specify presentation=kgas. However, if you haven't done
// so, any protocol=tcp dispatcher will be used.
30687, 00000, "session terminated by debugger"
// *Cause: The execution of the session was stopped by the debugger. This can
// occur because of an explicit request sent by the debugger, or
// because the debugger disconnected without requesting the ORACLE
// server to let the session continue to run after the
// disconnection. It can also occur if the ORACLE server needs to
// disconnect the debugger at a time when the person controlling the
// debugger might not expect, such as upon a reset of the related
// package state or a change of the login user. To prevent continuing
// the execution using debugger-introduced modifications that might
// have been intended to be temporary, the ORACLE server needs to
// fully terminate the session.
// *Action: This is in response to a debugger request; it is not an error.
// No action is required.
30688, 00000, "maximum program calling depth exceeded"
// *Cause: Your program contains a set of calls that are
// too deep to be handled. Only transitions between the different
// execution engines (SQL, PL/SQL, and Java) count in reaching this
// limit; calls within the same engine don't count.
// *Action: Restructure your program so as to not call so deeply.
// Perhaps some recursion can be replaced with iteration.
30689, 00000, "improper value for ORA_DEBUG_JDWP"
// *Cause: An improper value was used for ORA_DEBUG_JDWP when trying to
// establish a connection to a debugger. The value either did not
// conform to the format of ORA_DEBUG_JDWP or was too long.
// *Action: Correct the value for ORA_DEBUG_JDWP and try again.
30690, 00000, "timeout occurred while registering a TCP/IP connection for data traffic detection"
// *Cause: A timeout occurred while registering a TCP/IP connection for
// data traffic detection.
// *Action: Retry the operation later.
30691, 00000, "failed to allocate system resources while registering a TCP/IP connection for data traffic detection"
// *Cause: System resources ran out while registering a TCP/IP
// connection for data traffic detection.
// *Action: Retry the operation later.
30695, 00000, "JDWP message format problem"
// *Cause: A message passed from one software subcomponent to another
// using the JDWP protocol appears invalidly formatted.
// *Action: This is an internal error. Contact ORACLE Support Services.
30696, 00000, "request aborted by the target session"
// *Cause: The request was aborted by the target session. Possible causes
// include an unresolved error while the request was processed or the
// target session had aborted.
// *Action: Correct the issue in the target session and try again.
30697, 00000, "remote tool request waiting to be processed"
// *Document: NO
// *Cause:
// *Action:
30725, 00000, "JDWP-based debugging is not yet available"
// *Cause: This feature is not yet available for use.
// *Action: Please wait for a future release.
/
/
/
/
/ Error Numbers 30726 - 30925 are reserved for OBJECT SQL
/
/
30726, 00000, "cannot specify referenced column list here"
// *Cause: An attempt was made to specify a referenced column list
// for a referential constraint involving a REF column.
// *Action: Remove the referenced column list specification.
30727, 00000, "duplicate referential constraint for a REF column"
// *Cause: Multiple referential constraints were specified for a single
// REF column.
// *Action: Remove the duplicate referential constraint and retry the
// operation.
30728, 00000, "maximum number of columns exceeded"
// *Cause: Adding referential constraint on a REF column requires the
// the creation of an additional column.
// *Action: Drop some columns and retry the operation.
30729, 00000, "maximum number of columns exceeded"
// *Cause: Adding scope or referential constraint on a REF column
// requires the creation of additional columns if the target
// table's object identifier is primary key based.
// *Action: Drop some columns and retry the operation.
30730, 00000, "referential constraint not allowed on nested table column"
// *Cause: An attempt was made to define a referential constraint on a nested
// table column.
// *Action: Do not specify referential constraints on nested table columns.
30731, 00000, "scope constraint not allowed on nested table column when the nested table is being created"
// *Cause: An attempt was made to define a scope constraint on a nested table
// column when the nested table is being created.
// *Action: Do not specify a scope constraint on a nested table column when
// creating it. Instead, specify it using the ALTER TABLE statement.
30732, 00000, "table contains no user-visible columns"
// *Cause: An attempt was made to query on a system table which has no
// user-visible columns.
// *Action: Do not query on a system table that has no user-visible
// columns.
30733, 00000, "cannot specify rowid constraint on scoped ref column"
// *Cause: An attempt was made to specify rowid constraint
// on a scoped REF column.
// *Action: Remove the rowid constraint and then retry the operation.
30734, 00000, "cannot specify scope constraint on ref column with rowid"
// *Cause: An attempt was made to specify scope constraint
// on a REF column with the rowid constraint.
// *Action: Remove the scope constraint and then retry the operation.
/
/ Error messages for Inheritance (30735 - 30765)
30735, 00000, "cannot create multiple subtables of the same type under a supertable"
// *Cause: An attempt was made to create under a supertable (superview),
// a subtable(subview) of the same type as another existing
// subtable (subview).
// *Action: Drop the existing subtable(subview) and retry the operation.
30736, 00000, "objects in a table or view hierarchy have to be in the same schema"
// *Cause: An attempt was made to create a subtable(subview) under a
// supertable(superview) located in another schema.
// *Action: Connect as schema owner of the superobject and
// retry the operation.
30737, 00000, "cannot create subtable of a type which is not a subtype of the type of the supertable"
// *Cause: An attempt was made to create a subtable(subview) of a type
// which is not a subtype of the type of the super object.
// *Action: Change the type of the subtable to be a subtype of the
// superobject's type and then retry the operation.
30738, 00000, "object \"%s\" does not exist in schema \"%s\""
// *Cause: The specified object does not exist.
// *Action: Ensure that the specified object exists and retry the operation.
30739, 00000, "cannot drop a table that has subtables"
// *Cause: The user tried to drop a table that has subtables defined
// under it.
// *Action: Drop all subtables before trying this operation.
30740, 00000, "cannot grant UNDER privilege on this object"
// *Cause: The user tried to grant UNDER privilege on an object that is
// not one of the following : non final object type, object table
// of non final type, object view of non final type.
// *Action: Ensure that the UNDER privilege is granted on a valid object.
30741, 00000, "WITH HIERARCHY OPTION can be specified only for SELECT or READ privileges"
// *Cause: An attempt was made to specify WITH HIERARCHY OPTION for a privilege
// other than SELECT or READ.
// *Action: Ensure that the WITH HIERARCHY OPTION is specified only with the
// SELECT or READ privilege.
30742, 00000, "cannot grant SELECT or READ privilege when WITH HIERARCHY OPTION is specified on the object"
// *Cause: An attempt was made to grant the SELECT or READ privilege when the WITH
// HIERARCHY OPTION was specified on an object that is not one of the following:
// - Object table of non-final type
// - Object view of non-final type
// *Action: Ensure that the SELECT or READ privilege is granted on a valid
// object when the WITH HIERARCHY OPTION is specified.
30743, 00000, "\"%s\" is not an object view"
// *Cause: The specified object is not an object view.
// *Action: Specify an object view and retry the operation.
30744, 00000, "\"%s\" is not an object table"
// *Cause: The specified object is not an object table.
// *Action: Specify an object table and retry the operation.
30745, 00000, "error occured while trying to add column \"%s\" in table \"%s\""
// *Cause: The user tried to add a subtype which tried to alter the tables
// dependent on the supertype.
// *Action: Ensure that the table will not exceed the columnlimit on adding
// this subtype.
30746, 00000, "error occured while trying to drop column \"%s\" in table \"%s\""
// *Cause: The user tried to drop a subtype with VALIDATE option which tried to
// check for stored instances of the type in the stated table
// *Action: Delete all instances of this subtype and then drop the type.
30747, 00000, "cannot create substitutable tables or columns of non final type %s.%s"
// *Cause: The user tried to create substitutable table or column of a
// non final type. This operation is not currently supported.
// *Action: Change the statement to create a non substitutable table/column.
30748, 00000, "column %s already enabled to store objects of type %s.%s"
// *Cause: The user is trying to enable a column to store instances of a
// type for which it is already enabled.
// *Action: None
30749, 00000, "column %s not enabled to store objects of type %s.%s"
// *Cause: The user is trying to disable a column from storing instances of a
// type for which it is already enabled.
// *Action: None
30750, 00000, "cannot enable column %s to store objects of type %s.%s"
// *Cause: The user is trying to enable a column to store instances of
// a subtype. The error is raised due to one of the following :
// *Action: Fix the cause of the error and retry the operation.
30751, 00000, "cannot disable column %s from storing objects of type %s.%s"
// *Cause: The user is trying to drop a type from being stored in a
// substitutable column or table. This error is raised due to one
// of the following reasons :
// - the column is enabled to store instances of some subtype of
// the type being dropped.
// - the column is enabled to store instances of only one type
// *Action: Fix the cause of the error and retry the operation.
30752, 00000, "column or table %s is not substitutable"
// *Cause: The user is performing an operation that is not allowed on
// non substitutable column or table.
// *Action: None.
30753, 00000, "column or table %s is substitutable"
// *Cause: The user is performing an operation that is not allowed on
// substitutable column or table.
// *Action: None.
30754, 00000, "column or table %s stores objects of only one type"
// *Cause: The user is trying to perform an operation that is not
// allowed on object column or table that is enabled to store
// instances of a single type.
// *Action: None
30755, 00000, "error during expansion of view hierarchy"
// *Cause: There was an error while trying to expand a view hierarchy.
// This could be due to invalid subviews (or subviews with errors)
// *Action: Ensure that all subviews are valid e.g. alter view ... compile
// and retry the operation.
30756, 00000, "cannot create column or table of type that contains a supertype attribute"
// *Cause: The user tried to create a column or table of an object type that
// contains a supertype attribute. This is not supported because
// it leads to infinite recursion in our current storage model.
// Note that creating a column of a type implies that we
// create columns corresponding to all subtype attributes as well.
// *Action: Change the type definition to contain a supertype REF attribute
// instead of the supertype object attribute.
30757, 00000, "cannot access type information"
// *Cause: Either a subtype was created and operations performed with this
// new type while the session was in progress, or
// the type information was unpinned from the object cache.
// *Action: Commit necessary changes, end the user session, reconnect
// again and re-try the object operations.
// If problem persists, contact your Oracle Support representative.
30758, 00000, "cannot specify local on a non-partitioned table"
// *Cause: The user specified local or global for a nested table storage
// parameter while the base table is non-partitioned.
// *Action: None
30759, 00000, "nested table cannot be partitioned for a composite partitioned base table"
// *Cause: The user specifed local or nested table parameters inside
// partition clause for a composite partitioned table.
// *Action: Issue the DDL without nested table partition clauses for composite
// partitioned table.
30760, 00000, "cannot drop system-generated hidden object column"
// *Cause: An attempt was made to drop a system-generated hidden
// object column
// *Action: None.
/
/ Error messages for REF operations
30765, 00000, "cannot modify scope for an unscoped REF column"
// *Cause: An attempt was made to modify the scope for an unscoped REF
// column.
// *Action: Use an ALTER TABLE ADD SCOPE FOR command instead.
30766, 00000, "cannot modify scope for a REF column with a REFERENCES constraint"
// *Cause: An attempt was made to modify the scope for a REF column with
// a REFERENCES constraint.
// *Action: Drop the REFERENCES constraint, and retry the operation.
30767, 00000, "OID type mismatch"
// *Cause: An attempt was made to modify the scope for a REF column to a
// table whose object identifier's type is different from that
// of the original scoped table.
// *Action:
30768, 00000, "Cannot evaluate pipelined function"
// *Cause: Pipelined functions can only be used in a TABLE expression in
// the from clause.
// *Action: Use a non-pipelined function instead.
30769, 00000, "event to allow creation of sub-tables"
// *Document: NO
// *Cause: N/A
// *Action: Allows the user to create sub-tables.
/
30770, 00000, "Cannot specify storage options for fixed size opaque type"
// *Cause: Storage clause was specified during table creation for a fixed
// size opaque type.
// *Action: Do not provide storage option clause.
30771, 00000, "Cannot add more than one referential constraint on REF column \"%s\""
// *Cause: Multiple referential constraints were specified for a single
// REF column.
// *Action: Remove the additional referential constraints and retry the
// operation.
30772, 00000, "opaque types do not have default constructors"
// *Cause: Constructor invocation did not succeed, since no user-defined
// constructors were defined for the opaque type, and since opaque
// types do not have default constructors.
// *Action: Add user-defined constructors to opaque type, or specify a
// member or static method for the opaque type.
30773, 00000, "opaque types do not have default constructors"
// *Cause: Constructor invocation did not succeed, since no user-defined
// constructors were defined for the opaque type, and since opaque
// types do not have default constructors.
// *Action: Add user-defined constructors to opaque type, or specify a
// member or static method for the opaque type.
30774, 00000, "Library \"%s\" was erroneously defined as a trusted library for opaque types"
// *Cause: User has defined some library as trusted library for opaque types.
// *Action: Trusted libraries for opaque types can only be defined in internal
// code.
//
/
/
/ Error Numbers 30926 - 30930 are reserved for SQL execution time errors
/
30926, 00000, "unable to get a stable set of rows in the source tables"
// *Cause: A stable set of rows could not be got because of large dml
// activity or a non-deterministic where clause.
// *Action: Remove any non-deterministic where clauses and reissue the dml.
/
30927, 00000, "Unable to complete execution due to failure in temporary table transformation"
// *Cause: In memory temporary tables we create are aged out of shared pool
// before we are able to grab them again.
// *Action: Reduce activities that use a lot of shared pool space or wait for a
// while, then retry.
/
30928, 00000, "Connect by filtering phase runs out of temp tablespace"
// *Cause: It is probably caused by the fact that there is a loop in the data.
// *Action: Please retry the query with the NO_FILTERING hint. If the same error
// still occurs, then increase temp tablespace.
/
30929, 00000, "ORDER SIBLINGS BY clause not allowed here"
// *Cause: ORDER SIBLINGS BY clause is specifed in a query which doesn't
// have CONNECT BY clause.
// *Action: Remove ORDER SIBLINGS BY clause or add CONNECT BY clause.
/
30930, 00000, "NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn"
// *Cause: CONNECT_BY_ISCYCLE was specifed in a query which does not
// have the NOCYCLE keyword.
// *Action: Remove CONNECT_BY_ISCYCLE or add NOCYCLE.
/
/ Error Numbers 30931 - 31200 are reserved for Project XDB (XML Support)
/
/
/ Errors 30931 - 30979 for XMLType & schema processing
/
30931, 00000, "Element '%s' cannot contain mixed text"
// *Cause: XML elements must be declared mixed to contain multiple text nodes
// *Action: Declare this element type as mixed in its schema
30932, 00000, "Reference node '%s' not contained in specified parent node '%s'"
// *Cause: When using a reference node, it must have the specified parent
// node
// *Action: Use a node in the specified parent as the reference
30933, 00000, "Element '%s' may not appear at this point within parent '%s'"
// *Cause: The ordering specified by the content model of the parent does
// not allow for this element to occur at this position.
// *Action: Reorder the child elements to conform with the content model
// of the parent element
30934, 00000, "'%s' (%s node) cannot be inserted in parent '%s' (%s node)"
// *Cause: The schema does not allow a child node of this type to be inserted
// into a parent node of this type. For example, only element
// nodes may only be inserted into a document
// *Action: Insert only child nodes that make sense for this node type
30935, 00000, "XML maxoccurs value (%s) exceeded"
// *Cause: An attempt was made to insert more than maxoccurs
// values into a schema-based XML document.
// *Action: Do not insert more than maxoccurs values into the document.
30936, 00000, "Maximum number (%s) of '%s' XML node elements exceeded"
// *Cause: An attempt was made to insert more than the allowed number
// of elements (specified by the maxoccurs facet) into an XML
// document.
// *Action: Do not attempt to add more than the maximum number of elements
// to XML documents.
30937, 00000, "No schema definition for '%s' (namespace '%s') in parent '%s'"
// *Cause: The schema definition for the parent node being processed does
// not allow for the specified child node in its content model.
// Note that any typecasting via xsi:type must occur before the
// schema definitions for the new type can be used.
// *Action: Only insert elements and attributes declared in the schema.
// Check to make sure that xsi:type (if used) is specified first.
30938, 00000, "No prefix defined for namespace '%s' (particle %s)"
// *Cause: An XML namespace mapping (xmlns:<prefix>=<namespace URL>) must
// be defined for each particle (element or attribute) stored in
// an schema-constrained XMLType document.
// *Action: Add an xmlns attribute definition (attribute name="xmlns:prefix"
// and value="namespace URL") to the current XMLType document.
// The safest place to add this attribute is in the root node of
// the document to ensure that the mapping will be in scope.
30939, 00000, "Order violation: Element '%s' may not follow element '%s'"
// *Cause: The XML schema specifies a content model that is sequential,
// where the order of nodes in the instance must follow the order
// specified by the schema, and this instance relies on the schema
// validity to avoid maintaining instance order information
// *Action: Insert elements only in the order specified in the schema
30940, 00000, "Cannot resolve prefix '%s' for QName node '%s'"
// *Cause: An attempt was made to store a QName value without having a
// valid namespace in scope for that prefix.
// *Action: Declare the namespace for the prefix used
30941, 00000, "Cannot specify empty URI for non-default namespace '%s'"
// *Cause: An attempt was made to insert a namespace declaration for
// a non-default namespace using an empty URI string.
// *Action: Specify a non-empty URI for namespace declarations other than
// the default namespace.
//////// Errors 30942 to 30950 reserved for XML Schema Evolution
30942, 00000, "XML Schema Evolution error for schema '%s' table %s column '%s'"
// *Cause: The given XMLType table/column which conforms to the given schema
// had errors during evolution. For more information, see the more
// specific error below this one
// *Action: Based on the schema, table and column information in this error
// and the more specific error below, take corrective action
30943, 00000, "XML Schema '%s' is dependent on XML schema '%s'"
// *Cause: Not all dependent schemas were specified and/or the schemas were
// not specified in dependency order, i.e., if schema S1 is dependent
// on schema S, S must appear before S1.
// *Action: Include the previously unspecified schema in the list of schemas
// and/or correct the order in which the schemas are specified. Then
// retry the operation.
30944, 00000, "Error during rollback for XML schema '%s' table %s column '%s'"
// *Cause: The given XMLType table/column which conforms to the given schema
// had errors during a rollback of XML schema evolution. For more
// information, see the more specific error below this one
// *Action: Based on the schema, table and column information in this error
// and the more specific error below, take corrective action
30945, 00000, "Could not create mapping table '%s'"
// *Cause: A mapping table could not be created during XML schema evolution.
// For more information, see the more specific error below this one
// *Action: Ensure that a table with the given name does not exist and retry
// the operation
30946, 00000, "XML Schema Evolution warning: temporary tables not cleaned up"
// *Cause: An error occurred after the schema was evolved while cleaning up
// temporary tables. The schema evolution was successful
// *Action: If the user needs to remove the temporary tables, use the mapping
// table to get the temporary table names and drop them.
30947, 00000, "Dependent table '%s' of XML schema '%s' is version-enabled"
// *Cause: An XMLType table that is dependent on an XML schema being evolved
// is version-enabled.
// *Action: Disable versioning on the XMLType table
30948, 00000, "Illegal in-place XML schema evolution operation: %s"
// *Cause: An attempt was made to make an XML schema change that is not
// permitted through in-place XML schema evolution.
// *Action: Ensure that the XML schema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
/////// End of XML Schema Evolution errors (30942 to 30950 reserved)
30951, 00000, "Element or attribute at Xpath %s exceeds maximum length"
// *Cause: An attempt was made to insert a node of length exceeding the
// maximum length (specified by the maxLength facet) into
// an XML document.
// *Action: Do not attempt to add a node exceeding the maximum length
// to XML documents.
30952, 00000, "illegal configuration of HTTP/HTTPS in xdbconfig.xml"
// *Cause: An attempt was made to update xdbconfig.xml when either
// 1) a value was specified for http2-port but not for
// http2-protocol (or vice versa), OR
// 2) http-port and http2-port were set to the same value.
// *Action: Specify values for both elements http2-port and http2-protocol,
// AND set different values for http-port and http2-port.
30953, 00000, "XML minoccurs value (%s) violated"
// *Cause: An attempt was made to delete more than the required minimum number
// of elements (specified by the minoccurs facet) from an XML
// document.
// *Action: Do not attempt to delete more than the required minimum
// number of elements that must be present from the XML document.
30954, 00000, "char %s is invalid in %s"
// *Cause: An invalid XML character was found.
// *Action: Use only characters allowed by the XML specification.
//
//////// Errors 30955 to 30989 reserved for XML Index
30955, 00000, "The XML Index does not exist or is not asynchronous"
// *Cause: An attempt was made to synchronize a nonexistent XML Index
// or a synchronous XML Index.
// *Action: Create the XML Index in asynchronous mode.
30956, 00000, "invalid option for XML Index"
// *Cause: Unexpected error.
// *Action: File a bug.
30957, 00000, "cannot downgrade because there are XML indexes"
// *Cause: An attempt was made to downgrade a database that has XML indexes.
// *Action: Drop all XML indexes before attempting the downgrade.
30958, 00000, "operation directly on the Pending Table is disallowed"
// *Cause: An illegal operation was attempted on secondary objects of an
// XML Index.
// *Action: Try appropriate operation on the XML Index.
30959, 00000, "The indexed column is not stored in CLOB."
// *Cause: An attempt was made to create an XML Index on an OR-XMLType column.
// *Action: Re-create the XML Index on a CLOB-XMLType column.
30960, 00000, "The entity is neither an XPATH nor a NAMESPACE."
// *Cause: The given string had invalid syntax.
// *Action: Check the syntax for XPATH and NAMESPACE.
30961, 00000, "internal SQL statement is too long"
// *Cause: unexpected internal error
// *Action: File a bug and provide the test case.
30962, 00000, "inconsistent ODCI input arguments"
// *Cause: unexpected internal error
// *Action: File a bug and provide the test case.
30963, 00000, "The indexed column is not of XMLType."
// *Cause: An attempt was made to create an XML Index on a non-XMLType column.
// *Action: Re-create the XML Index on an XMLType column.
30964, 00000, "The XML Index was not usable."
// *Cause: The domain index for XML was not created properly. The Path Table is missing.
// *Action: Drop and re-create the XML Index.
30965, 00000, "fragment does not fit into the VARCHAR2 VALUE column"
// *Cause: The fragment size exceeded the max size.
// *Action: Re-create the XML Index with values stored in CLOB.
30966, 00000, "error detected in the XML Index layer"
// *Cause: Unexpected error.
// *Action: File a bug.
30967, 00000, "operation directly on the Path Table is disallowed"
// *Cause: illegal operation on secondary objects of a domain index
// *Action: Try appropriate operation on the domain index.
30968, 00000, "invalid XPATH or NAMESPACE option for XML Index"
// *Cause: An attempt was made to use an unsupported option.
// *Action: Use the appropriate option.
30969, 00000, "invalid syntax for PARAMETERS"
// *Cause: An attempt was made to specify an invalid option.
// *Action: Check and use valid options.
30970, 00000, "option not supported for XML Index"
// *Cause: An attempt was made to specify an invalid option.
// *Action: Check and use valid options.
30971, 00000, "illegal operation on the Path Table"
// *Cause: An attempt was made to use an unsupported option.
// *Action: Use the appropriate command on the XML Index.
30972, 00000, "invalid ALTER INDEX option for XML Index"
// *Cause: An attempt was made to use an unsupported option.
// *Action: Use the appropriate option.
30973, 00000, "invalid Path Table option for XML Index"
// *Cause: An attempt was made to use an unsupported option.
// *Action: Use the appropriate option.
30974, 00000, "invalid Path Id Index option for XML Index"
// *Cause: An attempt was made to use an unsupported option.
// *Action: Use the appropriate option.
30975, 00000, "invalid Order Key Index option for XML Index"
// *Cause: An attempt was made to use an unsupported option.
// *Action: Use the appropriate option.
30976, 00000, "invalid Parent Order Key Index option for XML Index"
// *Cause: An attempt was made to use an unsupported option.
// *Action: Use the appropriate option.
30977, 00000, "invalid Value Index option for XML Index"
// *Cause: An attempt was made to use an unsupported option.
// *Action: Use the appropriate option.
30978, 00000, "The XML Index is not locally partitioned."
// *Cause: An attempt was made to create a global partitioned XML Index.
// *Action: Do not attempt to create global partitioned XML Index
// or to maintain a non-local partitioned XML Index.
30979, 00000, "Partitioned XML Index not yet supported."
// *Cause: An attempt was made to create a partitioned XML Index.
// *Action: Do not attempt to create partitioned XML Index.
30980, 00000, "Invalid Input."
// *Cause: The input to the function is not valid.
// *Action: Make sure the input is valid (both syntactically as well as semantically).
30981, 00000, "Internal event to configure Compact XML / Streaming XPath"
// *Cause: N/A
// *Action: Do not document.
30982, 00000, "Invalid option for a partition of an XML Index"
// *Cause: An invalid option was specified at the partition level.
// *Action: Remove the invalid option.
30983, 00000, "Maximum order key depth exceeded"
// *Cause: The document could not be indexed because its nesting depth was
// more than that allowed by XML Index.
// *Action: Remove the offending document.
30984, 00000, "The XMLType column has to be declared as virtual"
// *Cause: The XMLType column was not declared as virtual when creating
// a structured XMLIndex.
// *Action: The XMLType column has to be declared as virtual
// when creating a structured XMLIndex.
30985, 00000, "The virtual XMLType column for chaining is missing"
// *Cause: The virtual XMLType column for chaining was missing when creating
// a structured XML index.
// *Action: A virtual XMLType column for chaining has to be specified
// when creating a structured XML Index.
30986, 00000, "XML Index with more than one virtual column is disallowed"
// *Cause: An attempt was made to create an XML Index with more than one
// virtual column.
// *Action: Create only one virtual column.
30987, 00000, "XML Index on XML DB repository does not exist"
// *Cause: An attempt was made to operate on a non-existent XML Index
// on XML DB repository.
// *Action: First create the index using
// DBMS_XDB_ADMIN.CREATEREPOSITORYXMLINDEX. Try the operation again.
30988, 00000, "Metadata of XML Index corrupted"
// *Cause: An attempt to locate the XML Index failed.
// *Action: Contact Oracle Support Services.
30989, 00000, "XML Index on an Index Organized Table is not yet supported"
// *Cause: XML Index supported only on Heap Organized Table.
// *Action: Contact Oracle Support Services.
/////// End of XML Index (30955 to 30989 reserved)
30990, 00000, "insufficient privileges to change owner of resource %s"
// *Cause: An attempt was made to change the <Owner> field of an
// XML DB resource without sufficient privileges to do so.
// *Action: Switch to SYS before performing the ownership change, or have
// the intended recipient of the resource perform the transfer.
30991, 00000, "cannot use DOM to add special attribute to schema-based parent"
// *Cause: An attempt was made to add or remove an xsi:schemaLocation,
// xsi:noNamespaceSchemaLocation, xsi:type, or xsi:nil attribute
// to or from a schema-based XML node using DOM.
// *Action: Use the updateXML operator instead of DOM.
30992, 00000, "error occurred at Xpath %s"
// *Cause:
// *Action: See the following error and take appropriate action.
30993, 00000, "complex type %s is not referred by any global element"
// *Cause:
// *Action: Add a dummy global element to the schema that refers to
// the complex type.
30994, 00000, "Invalid argument for DOM stream"
// *Cause: Either a null or a nonleaf node was passed.
// *Action: Use a combination of DOM API and DOM streams to produce
// desired effect.
30995, 00000, "DOM streams operations cannot be performed on null/invalid node"
// *Cause: The node is NULL or inexistent
// *Action: Check the input parameters.
30996, 00000, "Streams operations over non-existent stream"
// *Cause: The stream passed is NULL or invalid.
// *Action: Check the input parameters.
30997, 00000, "XSL processing of XML failed with error LPX-%s"
// *Cause: An LPX routine (XML/XSL processing) returned an error
// while tranforming an XML doc.
// *Action: Look up the LPX error and follow its corrective action.
30998, 00000, "transformation error: %s"
// *Cause: Error occurred while transforming an XML doc with an XSL
// style sheet.
// *Action: Contact Oracle Support Services.
30999, 00000, "XML context creation failed while %s"
// *Cause: Error occurred while creating XML context.
// *Action: Contact Oracle Support Services.
31000, 00000, "Resource '%s' is not an XDB schema document"
// *Cause: The given schema URL does not refer to a registered XDB schema
// *Action: Make sure the specified schema has been registered in XDB
31001, 00000, "Invalid resource handle or path name \"%s\""
// *Cause: An invalid resource handle or path name was passed to
// the XDB hierarchical resolver.
// *Action: Pass a valid resouce handle or path name to the hierarchical
// resolver.
31002, 00000, "Path name %s is not a container"
// *Cause: XDB expected the given path name to represent a container.
// *Action: Pass a path name or resource handle that represents a container.
31003, 00000, "Parent %s already contains child entry %s"
// *Cause: An attempt was made to insert a duplicate child into
// the XDB hierarchical resolver.
// *Action: Insert a unique name into the container.
31004, 00000, "Length %s of the BLOB in XDB$H_INDEX is below the minimum %s"
// *Cause: In the XDB$H_INDEX table, the CHILDREN column, a BLOB, must
// have a certain minimum length without being chained.
// The calculated length of the LOB was less than the stated minimum.
// *Action: Set the value of the init.ora parameter db_block_size
// to at least 2K. For XDB to run at its fastest, set
// db_block_size to 8K.
31005, 00000, "Path name length %s exceeds maximum length %s"
// *Cause: The length of a path name passed to the XDB hierarchical
// resolver exceeded the maximum length.
// *Action: Choose a shorter path name.
31006, 00000, "Path name segment length %s exceeds maximum length %s"
// *Cause: The length of a path name segment passed to the XDB
// hierarchical resolver exceeded the maximum length of a path
// name segment.
// *Action: Choose a shorter path name segment.
31007, 00000, "Attempted to delete non-empty container %s/%s"
// *Cause: An attempt was made to delete a non-empty container in
// the XDB hierarchical resolver.
// *Action: Either perform a recursive deletion, or first delete
// the contents of the container.
31008, 00000, "LPX context creation failed while %s"
// *Cause: Error occurred while creating LPX context because of an unexpected
// NULL value.
// *Action: Contact Oracle Support Services.
31009, 00000, "Access denied for property %s"
// *Cause: An attempt was made to access a property you don't have access to
// *Action: Check the ACL to see what privileges you have for this property
31010, 00000, "XML element index %s exceeds maximum insertion index %s"
// *Cause: An attempt was made to insert an XML element at an
// invalid index location in the node.
// *Action: Choose a new index that falls within the allowed range.
31011, 00000, "XML parsing failed"
// *Cause: XML parser returned an error while trying to parse the document.
// *Action: Check if the document to be parsed is valid.
31012, 00000, "Given XPATH expression not supported"
// *Cause: XPATH expression passed to the function is currently unsupported.
// *Action: Check the xpath expression and change it to use a
// supported expression.
31013, 00000, "Invalid XPATH expression"
// *Cause: XPATH expression passed to the function is invalid.
// *Action: Check the xpath expression for possible syntax errors.
31014, 00000, "Attempted to delete the root container"
// *Cause: An attempt was made to delete the root container in the
// hierarchical index.
// *Action: Do not delete the root container.
31015, 00000, "Attempted to insert entry without name"
// *Cause: An attempt was made to insert an entry into the hierarchical
// resolver without a child name.
// *Action: Supply a child name and try inserting again.
31016, 00000, "Attempted to delete entry without name"
// *Cause: An attempt was made to delete an entry from the hierarchical
// resolver without a child name.
// *Action: Supply a child name and try deleting again.
31017, 00000, "Error generating unique OID for XML document"
// *Cause: An error occurred while generating a globally unique OID
// for storing an XML document.
// *Action:
31018, 00000, "Error deleting XML document"
// *Cause: The XMLType object pointed to by the given REF could not
// be deleted because either the REF was invalid or it
// pointed to a non-existent table.
// *Action: Either use FORCE deletion or supply a valid REF.
31019, 00000, "Recursive deletion snapshot too old for %s/%s"
// *Cause: Changes were made to the structure of a directory while it
// was being recursively deleted.
// *Action: Try deleting the directory again.
31020, 00000, "The operation is not allowed, Reason: %s"
// *Cause: The operation attempted is not allowed
// *Action: See reason and change to a valid operation.
31021, 00000, "Element definition not found"
// *Cause: The element definition was not found.
// *Action: Supply the definition for the element or use a defined element.
31022, 00000, "Element not found"
// *Cause: The element was not found.
// *Action: Make sure the specified element exists.
31023, 00000, "Index size error"
// *Cause: The index is greater than the allowed value.
// *Action: Make sure the index is less than allowed value.
31024, 00000, "Parser initialization failed with LPX-%s error\nwhile %s"
// *Cause: Error occurred while initializing a parser.
// *Action: Contact Oracle Support Services.
31025, 00000, "Invalid document element"
// *Cause: An attempt was made to replace the data at an invalid
// index number in the XML document
// *Action: Supply a correct occurrence number and try again.
31026, 00000, "unable to allocate additional memory while \n%s"
// *Cause: A dynamic memory allocation failure occurred.
// *Action: Report this problem to a database administrator.
31027, 00000, "Path name or handle %s does not point to a resource"
// *Cause: An attempt was made to retrieve a resource based on
// a path name or resource handle that points to an entity
// other than a resource.
// *Action: Do not attempt to retrieve a resource based on that path
// name or resource handle.
31028, 00000, "Resource metadata length %s exceeded maximum length %s"
// *Cause: An attempt was made to insert resource metadata that exceeded
// the maximum length of that type of metadata.
// *Action: Keep resource metadata within its allowed length.
31029, 00000, "Cannot bind to unsaved resource"
// *Cause: An attempt was made to bind to a resource that had not
// been saved to disk.
// *Action: Bind only to saved resources.
31030, 00000, "Unable to retrieve XML document"
// *Cause: The resource had an invalid (dangling) REF to an XML document.
// *Action: Rebind the resource using a valid XMLType REF.
31031, 00000, "cannot create context to parse an XPath\n%s"
// *Cause: Error occurred while parsing an XPath.
// *Action: Contact Oracle Support Services.
31032, 00000, "XML parsing failed with error LPX-%s\nwhile %s"
// *Cause: An LPX routine returned an error while transforming an
// XML doc.
// *Action: Look up the LPX error and follow its corrective action.
31033, 00000, "Requested number of XML children %s exceeds maximum %s"
// *Cause: An attempt was made to add more than the maximum number of
// allowable children in an XML element.
// *Action: Redefine the schema to allow breaking up of the children
// among siblings.
31034, 00000, "invalid node set encountered while executing %s"
// *Cause: The given node set was either NULL or has an invalid type associated
// with it.
// *Action: Contact Oracle Support Services.
31035, 00000, "Could not bind locked resource to path %s/%s"
// *Cause: An attempt was made to bind an existing resource to a new
// location in the hierarchy, but a lock could not be obtained
// on the resource.
// *Action: Commit or roll back the transaction that has the lock on the
// resource.
31036, 00000, "XSL processing context initialization failed"
// *Cause: A error occurred while creating a XSL context.
// *Action: Contact Oracle Support Services.
31037, 00000, "Invalid XML attribute name %s"
// *Cause: The attribute name in the XML document did not match anything in
// the associated schema.
// *Action: Supply only schema-defined or XML standard attributes.
31038, 00000, "Invalid %s value: \"%s\""
// *Cause: The text in the XML document did not represent a valid
// value given the datatype and other constraints in the schema.
// *Action: Ensure that the specified value in XML documents is valid
// with respect to the datatype and other constraints in the schema.
31039, 00000, "XML namespace length %s exceeds maximum %s"
// *Cause: The length of the disk-formatted XML namespace exceeded the
// maximum.
// *Action: Keep XML namespace declarations below the maximum length.
31040, 00000, "Property %s: XML type (%s) not compatible with internal memory type (%s)"
// *Cause: The XML datatype given is inconsistent with the database
// datatype, and a conversion cannot be made.
// *Action: This is an internal error, generally resulting from corruption
// of the compiled XML schema. Re-register schemas, or contact
// Oracle support.
//
31041, 00000, "Property %s: Memory type (%s) not compatible with database type (%s)"
// *Cause: The memory type associated with this property is mapped to
// an incompatible database type, and a conversion cannot be made.
// *Action: This is an internal error, generally resulting from corruption
// of the compiled XML schema. Re-register schemas, or contact
// Oracle support.
//
31042, 00000, "Too many properties in type '%s'"
// *Cause: The type can only have the same number of properties (elements
// and attributes) as a table can have columns.
// *Action: Modify the XML schema to move properties into subelements that
// are not inlined.
//
31043, 00000, "Element '%s' not globally defined in schema '%s'"
// *Cause: The specified element name has not been defined at the top level
// of the XML schema (i.e. globally). Elements must be defined
// globally to be the root of an XMLType object.
// *Action: Check the XML schema definition to make sure the specified
// element name has been defined at the top level.
31044, 00000, "Top-level prefix length %s exceeds maximum %s"
// *Cause: An attempt was made to save to disk a top-level XML namespace
// prefix whose length exceeded the maximum.
// *Action: Do not define XML namespace prefixes that exceed the maximum
// length.
31045, 00000, "Cannot store more than %s extras outside the root XML node"
// *Cause: An attempt was made to store more than the maximum number of
// XML extras (e.g. comments and processing instructions)
// either before or after the document's root node.
// *Action: Keep the number of extras outside the root node below
// the maximum.
31046, 00000, "Incorrect argument(s) specified in the operator"
// *Cause: One or more of the arguments specified in the operator in the
// query are incorrect
// *Action: Correct the arguments specified in the operator
//
31047, 00000, "Could not retrieve resource data at path %s"
// *Cause: An error occurred while retrieving the contents and/or metadata
// of a resource.
// *Action: Contact Oracle customer support.
31048, 00000, "Unsaved resources cannot be updated"
// *Cause: An attempt was made to update a resource that was never saved
// to disk.
// *Action: Perform a resource insertion instead.
31049, 00000, "Internal event to turn off direct path loading of XML"
// *Cause: N/A
// *Action: Do not document.
31050, 00000, "Access denied"
// *Cause: The requested access privileges have not been granted to the
// current user. User must be granted privileges prior to
// resource access.
// *Action: Check the set of requested access privileges to make sure that
// they are included in the set of access privilges granted to
// the user.
//
31051, 00000, "Requested access privileges not supported"
// *Cause: The requested access privileges are not supported for the
// specified resource.
// *Action: Ensure that the set of requested access privileges are valid
// access privileges for the specified resource.
//
31052, 00000, "Cannot delete ACL with other references"
// *Cause: The requested deletion of an ACL resource cannot proceed.
// The ACL is in use by other resources.
// *Action: Remove the resources that are making reference to the ACL
// in question and try again.
//
31053, 00000, "The value of the depth argument in the operator cannot be negative"
// *Cause: The value of the depth argument passed to the primary operator
// is not a positive integer
// *Action: Pass a positive value of the depth argument
//
31054, 00000, "The %s operator cannot have an ancillary operator "
// *Cause: An ancillary operator was used with an operator which does not
// does not support ancillary operators
// *Action: Remove the ancillary operator in the query
//
31055, 00000, "A null XMLType element cannot be inserted into RESOURCE_VIEW"
// *Cause: The element which is being inserted into the RESOURCE_VIEW is
// NULL
// *Action: Specify a non-null XMLType element to insert into RESOURCE_VIEW
//
31056, 00000, "The document being inserted does not conform to %s"
// *Cause: The XMLType element being inserted into the RESOURCE_VIEW does
// not conform to the specified Schema
// *Action: Insert an element which conforms to the specified Schema
//
31057, 00000, "Display Name of the element being inserted is null"
// *Cause: The Display Name of the element which is being inserted into the
// RESOURCE_VIEW is null
// *Action: Specify the Display Name and insert the element into RESOURCE_VIEW
//
31058, 00000, "cannot modify read-only XOBs"
// *Cause: Read-Only XOBs cannot be modified.
// *Action: Use only read operations on such a XOB.
//
31059, 00000, "Cannot insert root XML document node if it already exists"
// *Cause: An attempt was made to insert a root node into an XML
// document that already had a root node.
// *Action: Call the appropriate replace function to replace the node
// instead of inserting it anew.
31060, 00000, "Resource at path %s could not be deleted"
// *Cause: An error occurred while deleting the named resource. The
// specific error can be found one lower on the error stack.
// *Action: Look at the next error on the stack and take approprate action.
31061, 00000, "XDB error: %s"
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
31062, 00000, "Cannot delete an unsaved resource"
// *Cause: An attempt was made to delete a resource that had not
// been saved to disk.
// *Action: Delete only saved resources.
31063, 00000, "XPath compilation failed: %s.\n%s"
// *Cause: XPath compilation failed for specified reason.
// *Action: Contact Oracle Support Services.
31064, 00000, "Cannot instantiate abstract element or property [%s]"
// *Cause: An attempt was made instantiate an abstract element.
// *Action: Use only read operations on such elements.
31065, 00000, "Cannot modify read-only property [%s]"
// *Cause: An attempt was made to modify an immutable XML node.
// *Action: Use only read operations on such properties.
31066, 00000, "Insertion of %s into %s creates a cycle"
// *Cause: An attempt was made to insert a link into the XDB hierarchy
// that would create a cycle in the tree.
// *Action: Ensure that links to existing resources do not cause cycles.
31067, 00000, "XML nodes must be updated with valid nodes and of the same type"
// *Cause: An attempt was made to use updateXML to update an XML
// node with a node of another type.
// *Action: Ensure that the node specified by the XPath matches the type of
// new data provided.
31068, 00000, "updateXML expected data format [%s] instead of [%s]"
// *Cause: An attempt was made to use updateXML to update data
// with a node of the incorrect type. Text and attribute
// nodes must be updated with string data, whereas element
// nodes must be updated with XMLType data.
// *Action: Use CREATEXML or getStringVal to coerce the new data to the
// proper format.
31069, 00000, "Cannot apply typed changes to non-schema-based XMLType nodes"
// *Cause: An attempt was made to insert, delete, or update a
// non-schema-based XMLType node using an XML schema definition.
// *Action: Make changes to non-typed nodes only by referencing their tag
// names.
31070, 00000, "Invalid database user ID %s"
// *Cause: An attempt was made set an invalid user ID into an XDB
// resource metadata property.
// *Action: Verify the validity of the user ID and try again.
31071, 00000, "Invalid database username or GUID %s"
// *Cause: An attempt was made to set an invalid username or GUID
// into an XDB resource metadata property.
// *Action: Verify the validity of the username or GUID and try again.
31072, 00000, "Too many child nodes in XMLType fragment for updateXML"
// *Cause: An attempt was made to pass an XMLType fragment with multiple
// children as new data for the updateXML operator.
// *Action: Extract the desired child from the XMLType before passing
// it to updateXML as the desired new XML node.
31073, 00000, "Resource not retrieved using path name"
// *Cause: An attempt was made to access the path name of a resource
// that was either never saved to disk or was loaded using
// a method other than with its path name.
// *Action: Perform path name operations only on resources obtained using
// a path name.
31074, 00000, "XML comment length %s exceeds maximum %s"
// *Cause: The length of the disk-formatted XML comment exceeded the
// maximum.
// *Action: Keep outer XML comments declarations below the maximum length.
//////// 31075 - 31099 reserved for XML Schema Compiler
31075, 00000, "invalid %s declaration in XML Schema"
// *Cause: The XML schema contains an invalid declaration identified
// by the message.
// *Action: Fix the identified error and try again.
//
31076, 00000, "required attribute \"%s\" not specified"
// *Cause: The XML schema does not specify a required attribute.
// *Action: Specify a value for the required attribute.
//
31077, 00000, "invalid attribute \"%s\" specified"
// *Cause: The XML schema specifies an invalid attribute.
// *Action: Remove specification of the invalid attribute.
//
31078, 00000, "error in SQL mapping information"
// *Cause: There is an error in the SQL type and table specification
// within the XML Schema.
// *Action: Ensure that all specified SQL types and tables are
// valid and compatible with the corresponding XML types.
//
31079, 00000, "unable to resolve reference to %s \"%s\""
// *Cause: The identified type or attribute or element could not be resolved.
// *Action: Make sure that the name corresponds to a valid
// XML (simple/complex) type or attribute or element and try again.
//
31080, 00000, "type not specified for attribute or element \"%s\""
// *Cause: The identified attribute or element does not have a type.
// *Action: Make sure that every attribute and element has a valid
// type specification.
//
31081, 00000, "name not specified for global declaration"
// *Cause: The XML schema does not specify the name for the global
// declaration of attribute or element or simpleType or complexType.
// *Action: Specify names for all global declarations.
//
31082, 00000, "invalid attribute \"%s\" specified in declaration of \"%s\""
// *Cause: The XML schema specifies an invalid attribute.
// *Action: Remove specification of the invalid attribute.
//
31083, 00000, "error while creating SQL type \"%s\".\"%s\" "
// *Cause: An error occurred while trying to create the SQL type based
// on the specification of a complex type.
// *Action: Fix the identified error and try again.
//
31084, 00000, "error while creating table \"%s\".\"%s\" for element \"%s\""
// *Cause: An error occurred while trying to create the table based
// on the declaration for the identified element.
// *Action: Fix the identified error and try again.
//
31085, 00000, "schema \"%s\" already registered"
// *Cause: An attempt was made to register a schema with the same URL
// as a previously registered schema.
// *Action: Register the schema with a different URL.
31086, 00000, "insufficient privileges to register schema \"%s\""
// *Cause: An attempt was made to register a schema without
// sufficient privileges.
// *Action: Make sure that the user has sufficient privileges to register
// the schema.
31087, 00000, "insufficient privileges to delete schema \"%s\""
// *Cause: An attempt was made to delete a schema resource without
// sufficient privileges.
// *Action: Make sure that the user has sufficient privileges to delete the
// schema.
31088, 00000, "object \"%s\".\"%s\" depends on the schema"
// *Cause: An attempt was made to delete a schema which has dependent
// objects.
// *Action: Either drop the dependent objects prior to deleting the schema
// or use the CASCADE or FORCE options.
31089, 00000, "schema \"%s\" does not target namespace \"%s\""
// *Cause: The schema document contains references (via include and import
// definitions) to other schemas that do not belong to valid
// namespaces.
// *Action: Make sure that all schemas referenced via include definitions
// target the same namespace as the parent schema.
// Further make sure that the namespace specified in the import
// definition matches the actual target namespace of the
// specified schema.
31090, 00000, "invalid database schema name \"%s\""
// *Cause: The XML schema document contains an invalid database schema name
// For example, the value of attribute SQLSchema
// *Action: Make sure that all database user/schema names specified in the
// XML schema document refer to existing database users/schemas.
31091, 00000, "empty string specified as a SQL name"
// *Cause: The XML schema document contains a null SQL name. For
// example, the values of attributes SQLName, SQLType, defaultTable.
// *Action: Make sure that all names of SQL schema objects specified in the
// XML schema document are valid SQL names. Otherwise, remove
// such attributes from the schema and try again.
31092, 00000, "invalid SQL name \"%s\""
// *Cause: The XML schema document contains an invalid SQL name. For
// example, the values of attributes SQLName, SQLType, defaultTable.
// *Action: Make sure that all names of SQL schema objects specified in the
// XML schema document are valid SQL names. This implies that
// the database length and other restrictions on names be satisfied.
31093, 00000, "null or invalid value specified for parameter : %s"
// *Cause: The argument value passed for the given parameter is null or
// invalid.
// *Action: Make sure that all the input argument values are valid.
31094, 00000, "incompatible SQL type \"%s\" for attribute or element \"%s\""
// *Cause: The SQL type information provided in the XML schema is not
// compatible with the XML datatype for the specified attribute
// or element.
// *Action: Make sure that the specified SQL types are compatible with the
// declared XML datatypes.
31095, 00000, "cannot generate %s : \"%s.%s\" already exists"
// *Cause: The type/table name specified in the XML schema document
// cannot be generated because it is already being used.
// *Action: Use different names for types/tables or use the NOGEN mode
// so that schema compiler does not generate new types/tables.
31096, 00000, "validation failed for schema"
// *Cause: The XML Schema could not be validated.
// *Action: Make sure that the SQLType and other datatype mapping is
// valid.
31097, 00000, "Hierarchical Index not empty"
// *Cause: An attempt was made to rebuild the hierarchical index which is
// not empty.
// *Action: Delete all rows in the hierarchical index and then
// rebuild it.
31098, 00000, "Internal event to turn on XDB tracing"
// *Cause: N/A
// *Action: Do not document.
31099, 00000, "XDB Security Internal Error"
// *Cause: An XDB Security internal error has occurred.
// *Action: Contact Oracle Support.
//////// 31100 - 31110 reserved for WebDAV compliant resource locks
31100, 00000, "XDB Locking Internal Error"
// *Cause: An XDB Locking Internal error has occurred.
// *Action: Contact Oracle Support.
31101, 00000, "Token \"%s\" not given while locking resource \"%s\""
// *Cause: Locking attempted on resource when the pricipal already owns
// a lock given by the token above.
// *Action: Reattempt the lock with the token.
31102, 00000, "Already locked in exclusive mode. Cannot add lock."
// *Cause: The resource is already locked in exclusive mode. Cannot
// add another lock.
// *Action: Unlock the existing lock.
31103, 00000, "Resource locked in shared mode. Cannot add exclusive lock"
// *Cause: The resource is locked in shared mode. Cannot add a shared lock.
// *Action: Try locking in shared mode or unlocking the existing lock.
31104, 00000, "Cannot find lock with token \"%s\" on \"%s\""
// *Cause: The lock may have been unlocked or expired. If token was
// supplied, token may be wrong.
// *Action: Verify this lock exists. Supply correct token.
31105, 00000, "User does not own lock with supplied token \"%s\""
// *Cause: The lock corresponding to the supplied token is not owned
// by the user.
// *Action: Log on as correct user. Supply correct token.
31106, 00000, "Action failed as the parent container is locked"
// *Cause:
// *Action: Supply the lock token on parent container or unlock it
31107, 00000, "Action failed as resource \"%s\" is locked by name lock"
// *Cause: Lock requests cause the whole request URI to be locked
// *Action: Supply lock token or unlock the lock
31108, 00000, "Action failed as resource %s is locked"
// *Cause: Delete/Rename failed because of an existing lock
// *Action: Do lockdiscovery to find the lock and delete it.
31109, 00000, "Action failed as parent resource %s is locked"
// *Cause: Delete/Rename failed because of an lock on parent resource
// *Action: Do lockdiscovery to find the lock and delete it.
31110, 00000, "Action failed as resource %s is locked by name"
// *Cause: Delete/Rename failed because one of the children is locked.
// *Action: Do lockdiscovery to find the lock and delete it.
//
31111, 00000, "table %s cannot be hierarchically enabled"
// *Cause: Trigger <tabname>_xdb_pitrigger already exists
// *Action: Either the table is already hierarchically enabled or the
// user trigger <tabname>_xdb_pitrigger needs to be dropped.
//
// *Action: Delete all rows in the hierarchical index and then
// rebuild it.
//
31112, 00000, "fail to %s for %s port using xdb configuration"
// *Cause: port number for the defined presentation is not valid
// *Action: Either the port number is already in use or
// it is protected. Specify another port number.
//
31113, 00000, "XDB configuration may not be updated with non-schema compliant data"
// *Cause: An attempt was made to update the XDB configuration resource with
// non-schema or non-schema compliant data.
// *Action: Check the document to make sure it is schema based and schema
// compliant.
//
31114, 00000, "XDB configuration has been deleted or is corrupted"
// *Cause: The XDB configuration resource has been deleted or corrupted.
// *Action: Reinstall XDB, or reinsert a valid configuration document.
//
31115, 00000, "XDB configuration error: %s"
// *Cause: An error related to XDB configuration has occurred.
// *Action: Make sure the configuration resource contains valid data.
//
//
31116, 00000, "Tablespace not specified correctly"
// *Cause: XDB cannot be moved to the specified tablespace.
// *Action: Specify a valid tablespace.
//
//
31117, 00000, "Table \"%s\".\"%s\" is not resource metadata enabled"
// *Cause: This table does not have a RESID column for resource metadata
// *Action: Use disable/enable_hierarchy to enable resource metadata
//
//
31118, 00000, "System schema \"%s\" already registered"
// *Cause: An attempt was made to register schema with same URL as a system schema.
// *Action: Change the schema URL to avoid conflicts with system XML schemas.
//
31119, 00000, "XDB configuration cannot be udpated on all instances"
// *Cause: An attempt was made to update XDB configuration.
// *Action: Ensure that each instance is correctly configured with
// its listener.
//
31120, 00000, "usedPort cannot be invoked in a Pluggable Database"
// *Cause: An attempt was made to invoke 'usedPort' in a Pluggable Database.
// *Action: Connect to the root container and invoke 'usedPort'.
//
/ Range 31120 - 31150 for res view, link view & path index
/
31121, 00000, "The %s operator cannot be FALSE"
// *Cause: The value of the operator that was specified is FALSE.
// *Action: Specify an operator that evaluates to TRUE.
31122, 00000, "The %s operator has incorrect RHS value"
// *Cause: The value on the right hand side, that has been specified for the
// operator did not evaluate to TRUE.
// *Action: Specify a value on the right hand side that evaluates to TRUE .
//
/ Range 31125 - 31150 for events
/
31126, 00000, "Internal event for Structure XMLIndex debugging"
// *Document: NO
// *Cause: N/A
// *Action: N/A
31127, 00000, "RCList cannot contain noncommitted resource configuration"
// *Cause: A commit was not executed after adding a resource configuration
// to an RCList by calling DBMS_RESCONFIG.ADDRESCONFIG()
// *Action: Make sure a commit is executed after calling
// DBMS_RESCONFIG.ADDRESCONFIG()
31128, 00000, "The event handler calls cannot exceed the depth of %s"
// *Cause: Tried to fire an event with depth exceeding the maximum.
// *Action: Make sure the event that is being fired does not generate
// infinitely recursive calls, either to itself or to other
// functions or procedures.
31129, 00000, "Unable to retrieve repository's resource configuration"
// *Cause: Tried to access a resource configuration referenced by the XDB repository that
// has been deleted.
// *Action: Disassociate the resource configuration from the repository.
//
31130, 00000, "Specified resource configuration is not associated with given resource"
// *Cause: Tried to delete a nonexistant resource configuration
// from the configuration list of the target resource.
// *Action: Make sure that the resource and resource configuration names
// are specified correctly and the resource configuration belongs
// to the configuration list of the given resource.
31131, 00000, "<RCList> contains OID that is not a resource configuration OID"
// *Cause: The OID in <RCList> element was not a resource configuration OID.
// *Action: Update the <RCList> element and resubmit statement.
//
31132, 00000, "Cannot validate handler \"%s\".\"%s\""
// *Cause: Attempted to invoke an invalid event handler. This can be a result
// of one of the following reasons:
// 1) The handler did not exist.
// 2) The handler could not be compiled successfully.
// *Action: Verify that the named handler does exist, then recompile and fix
// all compilation errors that may subsequently arise.
//
31133, 00000, "Cannot execute handler \"%s\".\"%s\" with invoker rights"
// *Cause: Attempted to invoke an event handler with invoker rights when
// the SET-INVOKER attribute in the resource configuration that
// defines the handler was not set to TRUE.
// *Action: Either redefine the named handler with definer rights or change
// the SET-INVOKER attribute in the resource configuration that
// defines the named handler to TRUE.
//
31134, 00000, "Cannot delete a configuration that is referenced by other resources"
// *Cause: Attempted to delete a resource configuration that was referenced by other
// resources.
// *Action: Remove all references to the target resource configuration by
// executing DELETERESCONFIG or DELETEREPOSITORYRESCONFIG procedures
// in DBMS_RESCONFIG package or specify the DELETE_FORCE option in the
// DELETERESOURCE statement.
//
31135, 00000, "Resource has already been rendered"
// *Cause: One of the following has occurred:
// 1) Attempted to invoke setRender* method after the resource was
// rendered through a setRender* method or after data was written
// to the output stream.
// 2) Attempted to access the output stream of the resource after a setRender*
// method was executed on the resource.
// *Action: Remove the method causing the problem.
//
31136, 00000, "Resource configuration %s is already associated with the resource %s"
// *Cause: The resource configuration already exists in the resource configuration list
// of the resource or the repository
// *Action: Check if this resource configuration really needs to be added. If so,
// remove it from resource and repository lists before adding it.
//
31137, 00000, "Index out of range"
// *Cause: The position specified was not valid.
// *Action: Check (0 <= pos < size of the configuration list of the target resource)
//
31138, 00000, "Resource-configuration is being referenced by one or more resources"
// *Cause: Tried to add a resource configuration to the repository
// that was being referenced by existing resources.
// *Action: Remove the resource configuration from other resources
// before trying to add it to the repository again.
//
31139, 00000, "Invalid resource configuration list"
// *Cause: Attempted to create or update a resource that had duplicate resource
// configurations or conflicted with the repository configurations.
// *Action: Correct the resource configuration list and re-submit statement.
//
31140, 00000, "Illegal operation: %s"
// *Cause: Tried to invoke a method when it was not allowed.
// *Action: Do not execute the indicated method.
//
31141, 00000, "Must specify a valid path value"
// *Cause: The path specified for the <defaultChildConfig> or
// <defaultChildACL> element must refer to an existing resource.
// *Action: Correct problem and resubmit statement.
//
31142, 00000, "Must specify the schema for each listener"
// *Cause: The schema element was not specified.
// *Action: Correct problem and resubmit statement.
//
31143, 00000, "XDB_SET_INVOKER role is required"
// *Cause: XDB_SET_INVOKER role was required to set the SET-INVOKER
// attribute to TRUE.
// *Action: Correct problem and resubmit statement.
//
31144, 00000, "Implementation language for %s is not specified"
// *Cause: Implementation language for specified listener source was not
// specified.
// *Action: Correct problem and resubmit statement.
//
31145, 00000, "Duplicate listener, %s, found in resource configuration"
// *Cause: Duplicate listener source was found in resource configuration.
// *Action: Remove duplicates and resubmit statement.
//
31146, 00000, "Invalid listener source %s.%s"
// *Cause: The listener source specified in the resource configuration
// did not exist or was invalid.
// *Action: Correct the listener source in the <listener> element and
// resubmit statement.
//
31147, 00000, "%s is not an ACL resource"
// *Cause: The specified resource did not conform to acl.xsd schema.
// *Action: Specify a valid path for the <defaultChildACL> element and
// resubmit statement.
//
31148, 00000, "%s is not a valid resource configuration"
// *Cause: The resource specified in the <defaultChildConfig> element while
// creating a resource configuration or specified as the rcpath in a
// call using DBMS_RESCONFIG package did not conform
// to XDBResConfig.xsd schema.
// *Action: Specify a valid path and resubmit statement.
//
31149, 00000, "no such schema: %s"
// *Cause: Nonexistent schema defined in the resource configuration.
// *Action: Specify a valid schema in the resource configuration and resubmit
// statement.
//
31150, 00000, "uncaught error in handler %s"
// *Cause: The named handler raised an exception.
// *Action: Fix the identified error.
//
//////// 31151 - 31179 reserved for XML Schema Compiler
31151, 00000, "Cyclic definition encountered for %s: \"%s\""
// *Cause: The schema definition for this type has cycles.
// *Action: Remove cyclic definition and re-compile schema.
31152, 00000, "Internal event to enable lru XOBs"
// *Cause: N/A
// *Action: Do not document
31153, 00000, "Cannot create schema URL with reserved prefix \"http://xmlns.oracle.com/xdb/schemas/\""
// *Cause: This prefix is reserved for XDB extended schema URLs and cannot
// be used in a user specified URL.
// *Action: Modify the prefix to a different one.
31154, 00000, "invalid XML document"
// *Cause: The XML document is invalid with respect to its XML Schema.
// *Action: Fix the errors identified and try again.
31155, 00000, "attribute %s not in XDB namespace"
// *Cause: The specified attribute should be prefixed with XDB's namespace.
// *Action: Ensure that all XDB specified attributes are prefixed with
// XDB's namespace and try again.
31156, 00000, "Internal event to turn off validation during schema registration"
// *Cause: N/A
// *Action: Do not document
//
31157, 00000, "Invalid Content-Type charset"
// *Cause: HTTP Content-Type header had a charset that Oracle does not
// understand.
// *Action: Fix the Content-Type header in the HTTP request.
//
31158, 00000, "schema \"%s\" currently being referenced"
// *Cause: The specified schema URL is currently being referenced by
// the same session. This could happen because of PLSQL
// XMLType variables still in scope.
// *Action: Ensure all references to this schema in this session are
// released and try the operation again.
//
31159, 00000, "XML DB is in an invalid state"
// *Cause: XML DB's internal tables are in an invalid state, probably
// because the database was not upgraded or the upgrade was
// not successful
// *Action: Ensure that the database is upgraded successfully. If the problem
// persists, contact Oracle Support
//
31160, 00000, "max substitution group size %s exceeded by \"%s\" (%s) for head element \"%s\" (%s)"
// *Cause: The maximum limit on nested substitution groups has been exceeded
// by an element.
// *Action: Delete specified schema and re-register it after removing the
// offending substitution element.
//
31161, 00000, "element or attribute \"%s\" cannot be stored out of line"
// *Cause: An element or attribute of a simple type has SQLInline=false
// *Action: Remove the SQLInline=false qualification for the offending element
// or attribute
31162, 00000, "element or attribute \"%s\" has no SQLType specified"
// *Cause: Schema registration was invoked with GENTYPES=false without
// specifying a SQLType for some element or attribute
// *Action: Specify a SQLType for the offending element or attribute and
// register the schema again
31163, 00000, "element or attribute \"%s\" has invalid attribute value \"%s\" (should be \"%s\")"
// *Cause: An element or attribute for a complextype derived by restriction
// has an attribute whose value is different from that in the base
// type
// *Action: Remove the mismatched attribute values from the offending element
// or attribute
31164, 0, "cannot load object-relational XML attribute using direct path \n"
// *Cause: The table being loaded contains a xml column with object-relational
// storage. The xmltype column contains a type with subtypes. This
// type of attribute cannot be loaded with direct path.
// *Action: Perform the load with conventional path mode.
//
31165, 0, "cannot load object-relational XML attribute using direct path \n"
// *Cause: The table being loaded contains a xml column with object-relational
// storage. The xmltype column either contains an out-of-line
// partitioned table or the table itself is partitioned by one of
// the attributes of xmltype. This type of table cannot be loaded
// with direct path.
// *Action: Perform the load with conventional path mode.
//
31166, 0, "internal error code to handle ignorable attributes"
// *Cause: N/A
// *Action: Do not document
//
31167, 00000, "XML nodes over 64K in size cannot be inserted"
// *Cause: An attempt was made to insert an XML Text Node with a size
// greater than 64K. This is not supported.
// *Action: Create text nodes under 64K.
31168, 00000, "Node localname and namespace values should be less than 64K"
// *Cause: An attempt was made to specify an XML Node with localname
// or namespace value greater than or equal to 64K. This is not
// supported.
// *Action: Node localnames and namespace values should be under 64K.
31169, 00000, "Number of children (%s) defined in '%s' exceeds maximum (%s)"
// *Cause: An attempt was made to define more than the allowed number
// of children in a complexType of an XMLSchema document.
// *Action: Modify the XML Schema to move children of complexType into
// subelements that are not inlined.
31170, 00000, "Cyclic Schema Registration without using FORCE option"
// *Cause: An attempt was made to register cyclic schemas
// with FORCE = false.
// *Action: Use FORCE = true when registering cyclic schemas.
31171, 00000, "schema processing error LSX-%s\nwhile %s"
// *Cause: An LSX routine returned an error.
// *Action: Look up the LSX error and follow its corrective action.
31172, 00000, "cannot load ADT column or XMLType column using direct path"
// *Cause: The table being loaded contained an ADT column or XMLType column
// with object-relational or binary storage and supplemental logging
// was enabled for the table. Direct path load is not supported for
// such tables when supplemental logging is enabled.
// *Action: Perform the load with conventional path mode.
31173, 00000, "internal event used by XDB schema cache"
// *Document: NO
// *Cause: N/A.
// *Action: Do not document
31174, 00000, "internal event used by XDB repository"
// *Document: NO
// *Cause: N/A
// *Action: N/A
31176, 00000, "API not supported in this release"
// *Cause: This API was not supported.
// *Action: None
31178, 00000, "Miscellaneous event for XDB"
// *Document: NO
// *Cause: N/A
// *Action: N/A
31179, 00000, "internal XDB event for ftp test harness"
// *Cause: N/A
// *Action: Do not document
//////// 31180 - 31189 reserved for PL/SQL DOM API
31180, 00000, "DOM Type mismatch in invalid PL/SQL DOM handle"
// *Cause: The specified PL/SQL DOM handle is referencing a DOM Node whose
// DOM Type that does not match the one available in the session.
// This could happen because the pl/sql handle was reused, or the
// original document is no longer available.
// *Action: Ensure that the pl/sql handle for the target node is valid and
// try the operation again.
31181, 00000, "PL/SQL DOM handle accesses node that is no longer available"
// *Cause: The specified pl/sql handle is referencing a node in a
// DOM Document that is no longer available.
// *Action: Ensure that the pl/sql handle for the target node is valid and
// try the operation again.
31182, 00000, "Too many PL/SQL DOM handles specified"
// *Cause: An attempt was made to create a PL/SQL DOM handle that exceeded
// the maximum allowable number of PL/SQL DOM handles.
// *Action: Free PL/SQL DOM handles and try the operation again.
31183, 00000, "Node type %s cannot be converted to desired type"
// *Cause: The given node's type cannot be converted correctly for
// this operation. For example, a DOM Element cannot be converted
// to Document Fragment
// *Action: Pass a valid node type for the conversion.
31185, 00000, "DOM Nodes do not belong to the same DOM Document"
// *Cause: The specified PL/SQL DOM Node does not belong to the
// parent DOM Document of the referring DOM Node.
// *Action: Ensure that both the DOM Nodes are part of the same
// DOM Document.
//
31186, 00000, "Document contains too many nodes"
// *Cause: Unable to load the document because it has exceeded
// the maximum allocated number of DOM nodes.
// *Action: Reduces the size of the document.
//
31187, 00000, "Cannot Add Node '%s' (type='%s') to Simple Type Node '%s'"
// *Cause: Trying to add attribute/element nodes to a simple type against
// the schema definition. Simple types can have only special
// attribute like namespaces, xsi:nil etc.
// *Action: Use a valid node for the operation.
31188, 00000, "The specified printing option is invalid"
// *Cause: The printing option specified in the operation is invalid.
// *Action: Use a valid printing option for the operation.
31190, 00000, "Resource %s is not a version-controlled resource"
// *Cause: Either one of the following is the cause:
// - Checkout is requested for a resource that isn't under version
// control". Only version-controlled resource can be checked out.
// - Checkout is requested for a row of a non-versioned table.
// *Action: put the resource under version-control before checking out.
31191, 00000, "Resource %s is already checked out"
// *Cause: Either one of the following is the cause:
// - Checkout is requested for a resource that is already checked
// out to the workspace by the same of different user.
// *Action: checked in the resource from the workspace before checking out
31192, 00000, "Resource %s has not been checked out"
// *Cause: Either one of the following is the cause:
// - Checkin or uncheckout is requested for a resource that has not
// been checked out to the workspace by any user in a workspace
// *Action: checked in the resource from the workspace before checking out
31193, 00000, "This versioning feature isn't supported for resource %s"
// *Cause: Either one of the following is the cause:
// - Container cannot be put under version-controlled.
// *Action: Avoid using these features.
31194, 00000, "Resource %s is already deleted"
// *Cause: Access a version-controlled resource that is already deleted.
// *Action: Recreate the resource.
//
// *Action: Remove the cyclic definitions in the type and retry compilation.
31195, 00000, "XML node '%s' (type=%s) does not support this operation"
// *Cause: The given node's type is not supported for this operation. For
// example, trying to add children to an attribute node, or passing
// in a document node as a child, are unsupported operations.
// *Action: Use a valid node type for the operation.
31196, 00000, "XML nodes over %s in size cannot be printed"
// *Cause: An attempt was made to use an XML Text Node with a size
// greater than 64K, or an XML Comment Node with a size greater
// than 4K. These cannot be printed. For
// example, trying to add children to an attribute node, or passing
// in a document node as a child, are unsupported operations.
// *Action: Use getClobVal() or getStringVal() to print the Document.
31197, 00000, "Error in processing file %s"
// *Cause: An error occurred while operating on the specifed file.
// The possible causes are
// the file header is corrupt or
// check the next error on stack
// *Action: Ensure that the specified file is correct.
// Look at the next error on the stack and take appropriate action.
31198, 00000, "Mismatch in number of bytes transferred due to non-binary mode"
// *Cause: An error occurred while reading the specifed file.
// The most probable cause is that the transfer was initiated in
// ASCII mode.
// *Action: Ensure that the transfer mode is set to BINARY
31199, 00000, "Warning in processing file %s"
// *Cause: A warning was raised while operating on the specifed file.
// However, the current operation was completed successfully.
// *Action: This is primarily an informational message.
// Look at the next error on the stack to obtain further
// information.
31200, 00000, "Invalid ACL Argument"
// *Cause: A System Constraining ACL was passed as one of the
// arguments to this function.
// *Action: Please ensure that none of the aclid arguments are for
// the System Constraining ACL.
//
//
//////////////////////////// DBMS_LDAP & OiD messages
/ Error Numbers 31201 to 31399 are reserved for OiD (Oracle Internet Dir)
/ these will be used for the DBMS_LDAP package as well as other services.
31201, 00000, "DBMS_LDAP: generic error: %s"
// *Cause: There has been an error in the DBMS_LDAP package.
// *Action: Please report the error number and description to Oracle Support.
31202, 00000, "DBMS_LDAP: LDAP client/server error: %s"
// *Cause: There is a problem either on the LDAP server or on the client.
// *Action: Please report this error to the LDAP server administrator or
// your Database administrator.
31203, 00000, "DBMS_LDAP: PL/SQL - Init Failed."
// *Cause: There has been an error in the DBMS_LDAP Init operation.
// *Action: Please check the host name and port number, or report
// the error number and description to Oracle Support.
31204, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP Session."
// *Cause: There has been an error in the DBMS_LDAP bind operation.
// *Action: Please check the session handler that you use for binding,
// or report the error number and description to Oracle Support.
31205, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP Auth method."
// *Cause: There has been an error in the DBMS_LDAP bind operation.
// *Action: Please check the authentication credentials that you
// use for binding, or report the error number and
// description to Oracle Support.
31206, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP search scope."
// *Cause: There has been an error in the DBMS_LDAP search operation.
// *Action: Please check the search scope that you use for search,
// or report the error number and description to Oracle Support.
31207, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP search time value."
// *Cause: There has been an error in the DBMS_LDAP search operation.
// *Action: Please check the search time value that you use for search,
// or report the error number and description to Oracle Support.
31208, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP Message."
// *Cause: There has been an error in the DBMS_LDAP operation.
// *Action: Please check the LDAP message that you use for LDAP operation,
// or report the error number and description to Oracle Support.
31209, 00000, "DBMS_LDAP: PL/SQL - LDAP count_entry error."
// *Cause: There has been an error in the DBMS_LDAP count_entry operation.
// *Action: Please check the LDAP count_operation, or report the error
// number and description to Oracle Support.
31210, 00000, "DBMS_LDAP: PL/SQL - LDAP get_dn error."
// *Cause: There has been an error in the DBMS_LDAP get_dn operation.
// *Action: Please check the LDAP get_dn, or report the error
// number and description to Oracle Support.
31211, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP entry dn."
// *Cause: There has been an error in the DBMS_LDAP operation.
// *Action: Please check the entry dn that you use for LDAP operation,
// or report the error number and description to Oracle Support.
31212, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP mod_array."
// *Cause: There has been an error in the DBMS_LDAP operation.
// *Action: Please check the LDAP mod_array that you use for LDAP operation,
// or report the error number and description to Oracle Support.
31213, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP mod option."
// *Cause: There has been an error in the DBMS_LDAP populate_mod_array
// operation.
// *Action: Please check the LDAP mod option that you use for LDAP
// populate_mod_array operation, or report the error number
// and description to Oracle Support.
31214, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP mod type."
// *Cause: There has been an error in the DBMS_LDAP populate_mod_array
// operation.
// *Action: Please check the LDAP mod type that you use for LDAP
// populate_mod_array operation, or report the error number
// and description to Oracle Support.
31215, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP mod value."
// *Cause: There has been an error in the DBMS_LDAP populate_mod_array
// operation.
// *Action: Please check the LDAP mod value that you use for LDAP
// populate_mod_array operation, or report the error number
// and description to Oracle Support.
31216, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP rdn."
// *Cause: There has been an error in the DBMS_LDAP operation.
// *Action: Please check the LDAP rdn value that you use for LDAP
// operation, or report the error number and description to
// Oracle Support.
31217, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP newparent."
// *Cause: There has been an error in the DBMS_LDAP rename_s operation.
// *Action: Please check the LDAP newparent value that you use for LDAP
// rename_s operation, or report the error number and
// description to Oracle Support.
31218, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP deleteoldrdn."
// *Cause: There has been an error in the DBMS_LDAP rename_s operation.
// *Action: Please check the LDAP deleteoldrdn value that you use for LDAP
// rename_s operation, or report the error number and
// description to Oracle Support.
31219, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP notypes."
// *Cause: There has been an error in the DBMS_LDAP explode_dn or
// explode_rdn operation.
// *Action: Please check the LDAP notypes value that you use for LDAP
// explode_dn or explode_rdn operation, or report the error
// number and description to Oracle Support.
31220, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet location."
// *Cause: There has been an error in the DBMS_LDAP operation.
// *Action: Please check the LDAP sslwrl value that you use for LDAP
// operation, or report the error number and description to
// Oracle Support.
31221, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet passwd."
// *Cause: There has been an error in the DBMS_LDAP operation.
// *Action: Please check the LDAP sslpasswd value that you use for LDAP
// operation, or report the error number and description to
// Oracle Support.
31222, 00000, "DBMS_LDAP: PL/SQL - Invalid LDAP SSL authentication mode."
// *Cause: There has been an error in the DBMS_LDAP operation.
// *Action: Please check the LDAP sslauth value that you use for LDAP
// operation, or report the error number and description to
// Oracle Support.
31223, 00000, "DBMS_LDAP: cannot open more than %s LDAP server connections"
// *Cause: An attempt was made to open more than the maximum allowed
// LDAP server connections.
// *Action: Free unused connections.
31224, 00000, "DBMS_LDAP: invalid LDAP session"
// *Cause: An attempt was made by a PL/SQL module to use an LDAP session
// which is not valid and might have already been closed.
// *Action: Check the LDAP session handle in PL/SQL module involving
// DBMS_LDAP.
31225, 00000, "DBMS_LDAP: invalid BER_ELEMENT"
// *Cause: An attempt was made by a PL/SQL module to use a BER_ELEMENT
// which is not valid and might have already been freed.
// *Action: Check the BER_ELEMENT in PL/SQL module involving DBMS_LDAP.
31226, 00000, "DBMS_LDAP: MOD_ARRAY size limit exceeded"
// *Cause: An attempt was made by a PL/SQL module to add an
// element beyond the MOD_ARRAY size limit.
// *Action: Increase the MOD_ARRAY size limit in PL/SQL module involving
// DBMS_LDAP.
31227, 00000, "DBMS_LDAP: invalid LDAP MESSAGE handle"
// *Cause: An attempt was made by a PL/SQL module to use an LDAP MESSAGE
// handle which is not valid and might have already been freed.
// *Action: Check the LDAP MESSAGE handle in PL/SQL module involving
// DBMS_LDAP.
31228, 00000, "DBMS_LDAP: invalid MOD_ARRAY"
// *Cause: An attempt was made by a PL/SQL module to use a MOD_ARRAY
// which is not valid and might have already been freed.
// *Action: Check the MOD_ARRAY in PL/SQL module involving DBMS_LDAP.
31229, 00000, "DBMS_LDAP: invalid input parameter"
// *Cause: An invalid argument has been passed by a PL/SQL module to
// a DBMS_LDAP subprogram
// *Action: Check the input argument to the DBMS_LDAP subprogram in
// PL/SQL module involving DBMS_LDAP.
31230, 00000, "DBMS_LDAP: unable to dynamically allocate additional memory"
// *Cause: An error occured during dynamic memory allocation from
// session heap.
// *Action: Verify that adequate memory resources are available.
31231, 00000, "DBMS_LDAP: invalid PROPERTY_SET"
// *Cause: An attempt was made by a PL/SQL module to use a PROPERTY_SET
// which is not valid and might have already been freed.
// *Action: Check the PROPERTY_SET in PL/SQL module involving DBMS_LDAP.
31232, 00000, "DBMS_LDAP: invalid MOD_PROPERTY_SET"
// *Cause: An attempt was made by a PL/SQL module to use a MOD_PROPERTY_SET
// which is not valid and might have already been freed.
// *Action: Check the MOD_PROPERTY_SET in PL/SQL module involving DBMS_LDAP.
31398, 00000, "DBMS_LDAP: Shared servers are not supported."
// *Cause: The session executing functions from the DBMS_LDAP package
// is being handled by a shared server in the Database.
// *Action: Use dedicated database sessions to execute functions in the
// DBMS_LDAP package.
31399, 00000, "Cannot contact LDAP server %s at port %d"
// *Cause: The LDAP server specified could not be contacted. This can
// happen if the server is down or inaccessible.
// *Action: Contact the administrator of the LDAP server
//////////////////////////// End of DBMS_LDAP & OiD messages
/ Error Numbers 31401 - 31540 are reserved for CDC (Change Data Capture)
/ These are raised by calling dbms_sys_error.raise_system_error.
/
31401, 00000, "change source %s is not an existing change source"
// *Cause: The caller did not use the name of an existing change
// source. The name given does not match the name of any
// existing change source.
// *Action: Check the spelling of the change source name. Choose an
// existing change source.
//
31402, 00000, "unrecognized parameter %s"
// *Cause: Unrecognized parameter was detected.
// *Action: Check for too many parameters in the call.
//
31403, 00000, "change table %s already contains a column %s "
// *Cause: Issued ALTER_CHANGE_TABLE with an add operation but a column by
// this name already exists in the specified table.
// *Action: Check the names and call the procedure again.
//
31404, 00000, "all input parameters are null"
// *Cause: All input parameters are null. At least one property must be
// altered.
// *Action: Call the procedure again, making sure that all the required
// parameters have been specified. Ensure that at least one
// parameter is not null. Refer to user documentation for
// the correct way of calling this procedure.
//
31405, 00000, "cannot make changes while change set %s is advancing"
// *Cause: The change set is currently advancing. Change sources related
// to an advancing change set cannot be altered. Change tables
// related to the advancing change set cannot be created, altered
// or dropped. Some or all the parameters of the change set cannot
// be altered while the set is advancing.
// *Action: Wait until the change set has finished advancing, then reissue
// the command. If altering the change set, only the advance_enable
// parameter can be altered during an advance.
//
31406, 00000, "change source %s is referenced by a change set"
// *Cause: The operation cannot complete because this change source is
// referenced by one or more change sets.
// *Action: Drop the change sets first, then re-issue the command. May have
// to drop some change tables before the change sets are dropped.
//
31407, 00000, "end_date must be greater than the begin_date"
// *Cause: The end data of the change set is earlier than the begin date.
// The end date must always be later in time than the begin date,
// so that the duration between the begin and end dates is a
// positive amount of time.
// *Action: Change the begin date and/or the end date, so that the end date
// is later than the begin date.
//
31408, 00000, "invalid value specified for begin_scn or end_scn"
// *Cause: The begin_scn was not greater than zero. The end_scn was less than
// zero. The end_scn was less than the begin_scn.
// *Action: Check the values of both begin_scn and end_scn. Correct them to
// make sure that they form a legal SCN range. An end_scn value of
// zero indicates an infinite scn range.
//
31409, 00000, "one or more values for input parameters are incorrect"
// *Cause: One or more of the inputs to the procedure had invalid values.
// *Action: Identify the bad parameter(s) and supply correct values to the
// procedure.
//
31410, 00000, "change set %s is not an existing change set"
// *Cause: Could not find an existing change set by this name.
// *Action: Check the spelling of the change set name. Call the procedure
// again, passing the correct change set name.
//
31411, 00000, "change set %s is referenced by a change table"
// *Cause: The operation cannot be performed because the change set contains
// one or more change tables.
// *Action: You will need to drop the change table(s) first, then repeat the
// operation
//
31412, 00000, "change set %s is disabled and cannot be advanced"
// *Cause: The specified change set is disabled. The change set needs to be
// enabled for the operation to succeed.
// *Action: Determine why the change set is disabled and correct this
// condition. Alter the change set specifying 'y' for
// advance_enable then retry the operation.
//
31413, 00000, "change set %s is currently being advanced"
// *Cause: An advance operation is in progress for this change set and we
// only allow one at a time.
// *Action: Since the change set is currently being advanced, the best action
// is to wait for it to finish advancing. Only one caller
// at a time can advance the change set. Check for the cause of
// long running advance operations.
//
31414, 00000, "error(s) occurred during change table advance"
// *Cause: One or more errors occurred during the advance operation.
// *Action: Check the log file(s) for a more detailed report of the
// underlying errors.
//
31415, 00000, "change set %s does not exist"
// *Cause: Specified change set does not exist or the user does not have
// access to the publications in that change set. The name
// specified did not match the name of any existing change set.
// Certain privileges are required to access the publications
// within that change set.
// *Action: Check the name and call the procedure again, with the name of
// an existing change set. Contact the publisher or database
// administrator if user privileges are required to access the
// publications in the change set.
//
31416, 00000, "invalid SOURCE_COLMAP value"
// *Cause: A source_colmap value of 'y' was specified for an asynchronous
// change table.
// *Action: Specify a source_colmap parameter value of 'n' and call the
// procedure again.
//
31417, 00000, "column list contains control column %s"
// *Cause: Reserved column name was specified in a column list or column
// type parameter.
// *Action: Control columns are selected with separate parameters. If you
// did not want a control column, then change the name of the
// specified column so that it does not conflict with a reserved
// column name.
//
31418, 00000, "source schema %s does not exist"
// *Cause: Trying to create a synchronous change table and the source schema
// did not match any existing schema names in the database.
// *Action: Specify the name of an existing schema.
//
31419, 00000, "source table %s does not exist"
// *Cause: When creating a synchronous change table, the underlying source
// table must exist when the procedure is called. In this case,
// the source table did not exist.
// *Action: Specify the name of an existing table.
//
31420, 00000, "unable to submit the purge job"
// *Cause: When creating the first change table, a purge job is submitted to
// the job queue. Submission of this purge job failed.
// *Action: Make sure that job queue processes are enabled and are currently
// running. If this does not solve the problem, contact Oracle.
//
31421, 00000, "change table does not exist"
// *Cause: Specified change table does not exist.
// *Action: Recheck the name, and call the procedure again using an existing
// change table.
//
31422, 00000, "owner schema %s does not exist"
// *Cause: Value specifed for the owner parameter does not contain the name
// of an existing schema in the database.
// *Action: Recheck the name, and call the procedure again using an existing
// schema name.
//
31423, 00000, "change table %s does not contain column %s "
// *Cause: Issued ALTER_CHANGE_TABLE with a drop operation and the specified
// column does not exist in the change table.
// *Action: Recheck the names, and call the procedure again.
//
31424, 00000, "change table has active subscriptions"
// *Cause: The change table is subscribed to, so it cannot be dropped.
// *Action: Do not drop a change table while there are active subscribers.
// If this is an emergency, use the FORCE parameter. This will
// forcibly drop the change table out from under all subscribers.
//
31425, 00000, "subscription does not exist"
// *Cause: The subscription either did not exist or did not belong to
// this user.
// *Action: Call the function again with a valid subscription name.
//
31426, 00000, "cannot modify active subscriptions"
// *Cause: The subscription was already activated so that additional
// calls to SUBSCRIBE were prohibited.
// *Action: Subscribe to all the desired tables and columns before
// activating the subscription. Ensure that the correct
// subscription name is specifed.
//
31427, 00000, "publication %s already subscribed"
// *Cause: The subscription already contained this publication.
// *Action: Check the values of subscription_name and publication_id.
// Check any other subscribe calls to see if they subscribe
// to columns that are shared among more than one publication
// on the same source table. Do not attempt to subscribe to
// the same publication more than once in the same subscription.
// Use the publication_id variant of the SUBSCRIBE call if
// needed to specify precise publications.
//
31428, 00000, "no publication contains all the specified columns"
// *Cause: One or more of the specifed columns cannot be found in
// a single publication.
// *Action: Change the subscription request to select only columns that are
// in the same publication. Consult the USER_PUBLISHED_COLUMNS
// view to see current publications.
//
31429, 00000, "subscription has not been activated"
// *Cause: The called procedure required an activated subscription.
// *Action: Check the subscription name and correct if necessary. Call the
// ACTIVATE_SUBSCRIPTION procedure for this subscription and
// then reissue the original command.
//
31430, 00000, "subscriber view exists"
// *Cause: A view that is already in use was specified for the subscriber
// view.
// *Action: Call the SUBSCRIBE procedure using a different subscriber
// view name.
//
31431, 00000, "all source tables must belong to the synchronous change set"
// *Cause: Not all of the source tables belong to the synchronous change
// set.
// *Action: Check the spelling of the source tables. Make sure that all of
// the source tables belong to the synchronous change set.
//
31432, 00000, "invalid source table"
// *Cause: Either the schema_name.source_table did not exist or it did
// not belong to this subscription.
// *Action: Check the spelling of the schema_name and source_table. Verify
// that the specifed table exists in the specifed schema and is
// subscribed to by the subscription.
//
31433, 00000, "subscriber view does not exist"
// *Cause: The subscription did not contain this subscriber view.
// *Action: Recheck the name, and specify the name of an existing
// subscriber view.
//
31434, 00000, "purge is currently running"
// *Cause: Called the PURGE procedure while a purge job was currently
// running.
// *Action: Wait for purge to complete before reissueing this command.
//
31435, 00000, "an error occurred during the purge operation"
// *Cause: An error occurred during the purge operation
// *Action: Check the logfile for a more detailed report of the underlying
// errors.
//
31436, 00000, "duplicate change source %s"
// *Cause: A change source by the specifed name already exists.
// *Action: Recreate the change source with a unique name.
//
31437, 00000, "duplicate change set %s"
// *Cause: A change set by the specified name already exists.
// *Action: Recreate the change set with a unique name.
//
31438, 00000, "duplicate change table %s"
// *Cause: A change table by the specified name already exists.
// *Action: Recreate the change table with a unique name.
//
31439, 00000, "subscription is already active"
// *Cause: The subscription is already active.
// *Action: Check name and retry.
//
31440, 00000, "change set %s is empty and cannot be advanced"
// *Cause: User attempted to advance a change set which does not contain
// any change tables. Without change tables, a change set cannot
// be advanced.
// *Action: Create change tables in the change set, then retry the advance.
//
31441, 00000, "table is not a change table"
// *Cause: User attempted to execute the DROP_CHANGE_TABLE procedure on a
// table that is not a CHANGE table. This can also occur when
// a CHANGE table object has been orphaned. CHANGE tables can become
// orphaned after a CREATE_CHANGE_TABLE failure or an incomplete
// DROP_CHANGE_TABLE.
// *Action: Check spelling. If error was due to an incorrect name, then retry
// the procedure using the correct name. To drop a table that is
// not a CHANGE table, or an orphaned CHANGE table, use the
// DROP TABLE DDL command instead.
//
31442, 00000, "operation timed out while acquiring lock on %s"
// *Cause: CDC attempted to acquire a lock on the resource, but the operation
// timed out.
// *Action: Retry the operation later.
//
31443, 00000, "deadlock detected while acquiring lock on %s"
// *Cause: CDC attempted to acquire a lock on the resource, but encountered a
// deadlock.
// *Action: Contact Oracle corporation
//
31444, 00000, "parameter error while acquiring lock on %s"
// *Cause: CDC attempted to acquire a lock on the resource, but encountered a
// problem passing parameters to the lock manager.
// *Action: Contact Oracle corporation
//
31445, 00000, "invalid lock handle while acquiring lock on %s"
// *Cause: CDC attempted to acquire a lock on the resource, but encountered a
// invalid lock handle, which did not correspond to any existing
// handle.
// *Action: Contact Oracle corporation
//
31446, 00000, "this session does not own the lock handle for %s"
// *Cause: CDC attempted to acquire a lock on the resource, does not own the
// the lock associated with the lock. This is an internal
// error.
// *Action: Contact Oracle corporation
//
31447, 00000, "cannot create change tables in the SYS schema"
// *Cause: Attempted to create a change table in the SYS schema.
// This is not allowed.
// *Action: Use a different existing schema and retry the command.
//
31448, 00000, "invalid value for change_source"
// *Cause: The specified value was not a valid name for a Change Source.
// *Action: Specify a valid name and retry the command.
//
31449, 00000, "invalid value for change_set_name"
// *Cause: The specified value was not a valid name for a Change Set.
// *Action: Specify a valid name and retry the command.
//
31450, 00000, "invalid value for change_table_name"
// *Cause: The specified value was not a valid name for a Change Table.
// *Action: Specify a valid name and retry the command.
//
31451, 00000, "invalid value %s for capture_values, expecting: OLD, NEW, or BOTH"
// *Cause: The specified value was not a valid option for a capture_values.
// *Action: Specify a valid option and retry the command.
//
31452, 00000, "invalid value %s for parameter, expecting: Y or N"
// *Cause: The specified value was not Y or N.
// *Action: Specify Y or N for the parameter and retry the command.
//
31453, 00000, "invalid value %s for parameter, expecting: Y, N, or NULL"
// *Cause: The specified value was not Y, N or NULL.
// *Action: Specify Y, N or NULL for the parameter and retry the command.
//
31454, 00000, "invalid value %s for operation parameter, expecting: ADD or DROP"
// *Cause: The specified value was not ADD or DROP.
// *Action: Specify ADD or DROP and retry the command.
//
31455, 00000, "nothing to ALTER"
// *Cause: The specified column list is NULL and all optional control
// columns are 'N'.
// *Action: Specify one or more columns to ALTER.
//
31456, 00000, "error executing a procedure in the DBMS_CDC_UTILITY package"
// *Cause: An internal attempt to invoke a procedure within the
// DBMS_CDC_UTILITY package failed.
// *Action: Check the trace logs for more information. Ensure that the
// package has been installed successfully. Try issuing a DESCRIBE
// command from SQL on the package. If it fails, then try
// reinstalling the package. If it succeeds then try invoking one
// of the procedures from SQL.
//
31457, 00000, "maximum length of description field exceeded"
// *Cause: The maximum number of characters permitted in the description
// field was exceeded.
// *Action: The maximum length of the description field is 30 characters.
// Ensure the length does not exceed this value and retry the
// command.
//
31458, 00000, "an internal error occurred"
// *Cause: This is an internal error.
// *Action: Contact Oracle Worldwide Customer Support and report the error.
//
31459, 00000, "system triggers for DBMS_CDC_PUBLISH package are not installed"
// *Cause: One or more required system triggers are not installed. These
// triggers are required for the proper operation of Change Data
// Capture. Operations on Change tables cannot continue.
// *Action: Install or reenable the triggers, or reinstall the package.
//
31460, 00000, "logfile location %s is not an existing directory"
// *Cause: The directory specification for logfile location for the change
// source, does not correspond with an existing directory, or the
// directory was not accessible.
// *Action: 1. Create the directory if it does not exist. If the directory
// does exist, change the file system permissions so the directory
// can be accessed. OR 2. perform ALTER CHANGE SOURCE and change
// the logfile_location to be an existing directory that contains
// the logfiles
//
31461, 00000, "logfile location %s contains no files that match pattern %s"
// *Cause: The directory specification for logfile location for the change
// source, does not contain any files whose names pattern-match
// the logfile_suffix.
// *Action: 1. Make sure that the logfile location contains logfiles whose
// names match the logfile_suffix pattern for the change set.
// OR 2. perform ALTER CHANGE SOURCE and change the logfile_suffix
// such that it matches the names of existing logfiles in the
// directory
//
31462, 00000, "internal error while accessing metadata"
// *Cause: An unexpected internal error occurred while CDC was accessing
// its internal Metadata.
// *Action: Contact Oracle Corporation
//
31463, 00000, "logfile location %s is an empty directory"
// *Cause: The directory specification for logfile location for the change
// source, is an empty directory
// *Action: 1. Make sure it is the correct location of the logfiles. If it
// is, make sure the directory contains logfiles.
// OR 2. perform ALTER CHANGE SOURCE and change the logfile_location
// to be an existing directory that contains the logfiles
//
31464, 00000, "target table for the change table no longer exists"
// *Cause: User tried to drop a change table but its underlying storage table
// (that contains the change data) has been dropped.
// *Action: Contact Oracle Corporation
//
31465, 00000, "cannot obtain a lock on the subscription"
// *Cause: A timeout occurred while trying to place a lock on the
// subscription. Another session had already acquired the
// lock on the subscription.
// *Action: Ensure the subscription name is correct and correct it if
// necessary. If it is already correct, try the operation again
// after the session holding the lock has released it.
//
31466, 00000, "no publications found"
// *Cause: Did not find any publications that matched the input parameters
// or the user does not have the privileges to access the specified
// publication.
// *Action: Check the input parameters on the call to SUBSCRIBE. Validate
// that the proposed source table has been published by checking the
// USER_PUBLICATIONS view for that source table. Contact the
// publisher if user privileges are required to access the
// publication. Retry the command with correct security or
// publication information.
//
31467, 00000, "no column found in the source table"
// *Cause: The OBJECT_ID flag was set to 'Y' on the call to
// CREATE_CHANGE_TABLE and change table belongs to the synchronous
// change set. The corresponding object column was not detected in
// the source table.
// *Action: Create the change table with the OBJECT_ID flag set to 'N' or
// investigate why the object column is not in the source table and
// add it to the source table.
//
31468, 00000, "cannot process DDL change record"
// *Cause: The change set has stop_on_ddl enabled and was trying to process
// a DDL change record.
// *Action: Check the alert log to find out what the DDL record contained.
// Make any necessary changes to the change tables. Call
// ALTER_CHANGE_SET with recover_after_error and remove_ddl set to
// 'Y'.
//
31469, 00000, "cannot enable Change Data Capture for change set %s"
// *Cause: The change set has reached the specified limit that was set up
// by the CREATE_CHANGE_SET command.
// *Action: Check the alert log to find out whether capture, apply or both
// reached the limit. Once apply reaches its limit, the change
// set is permanently disabled. Create a new change set with
// new limits to continue capturing data.
//
31470, 00000, "asynchronous change tables must contain the RSID$ column"
// *Cause: If creating an asynchronous change table, the RSID was set to 'N'.
// If altering an asynchronous change table with an operation
// parameter of 'DROP' RSID was set to 'Y'.
// *Action: When creating asynchronous change tables, always specify 'Y'
// for the RSID parameter. When altering asynchronous change
// tables always specify 'N' for RSID.
//
31471, 00000, "invalid OBJECT_ID value"
// *Cause: An object_id value of 'y' was specified for an asynchronous
// change table.
// *Action: Specify an object_id parameter value of 'n' and call the
// procedure again.
//
31472, 00000, "Importing Change Data Capture version %s.%s is too new"
// *Cause: An attempt was made to Import a file that was exported by a
// newer version of Oracle than the target instance.
// *Action: If possible, re-export the file using a version of export
// that matches the import target. Objects can not be imported
// into previous versions of Oracle that did not support them.
//
31473, 00000, "date bound out of range"
// *Cause: The upper_bound or lower_bound specified in
// extend_window or purge_window API is beyond the range of records
// in the change set.
// *Action: Either select a bound that is within range or do not
// select an upper or lower bound at all.
//
31474, 00000, "Invalid change view window"
// *Cause: The specified upper_bound or lower_bound is forcing a condition
// where the change view window will have nothing in it.
// *Action: Select a different upper_bound or lower_bound and reissue the
// API call that produced the error. Alternatively, make the
// upper_bound or lower_bound parameter NULL and reissue the
// API call.
//
31475, 00000, "redo log catalog contains no metadata for the source table"
// *Cause: While advancing a change set, an CDC attempted to query the
// LogMiner dictionary system tables to obtain the columns from
// the source table. The query returned no rows. This may be
// because none of the redo logs contains a catalog, or it
// may be an internal error.
// *Action: First, verify that the source system contains the source table.
// execute dbms_logmnr_d.build procedure to populate the redos log
// with logminer dictionary information. If this has been done
// and the problem persists, then contact Oracle Corporation
//
31476, 00000, "a change table data column is missing from the source table"
// *Cause: While advancing a change set, an CDC determined that at least
// one of the data columns in a change table does not match the
// name of any of the columns in the source table. The source
// table column listis stored in dictionary table SYSTEM.LOGMNR_OBJ$
// *Action: Make sure that all of the data columns of the change table
// have the same names as the corresponding columns in the source
// table, and that all the columns exist in the source table.
//
31477, 00000, "could not detach LogMiner session during cleanup"
// *Cause: Failure during detach from a LogMiner session during advance of
// an asynchronous change set. This is an internal error. This
// exception is raised when a previous exception occurred during
// the internal protocol with LogMiner, after which Change Data
// Capture attempted to detach the LogMiner session as part of
// recovery. The detach session also failed
// *Action: Contact Oracle Corporation
//
31478, 00000, "could not detach LogMiner session after change set advance"
// *Cause: Failure during detach from a LogMiner session after successful
// advance of an asynchronous change set. This is an internal
// error. This exception is raised when an asynchronous change
// set has been successfully advanced but CDC was unable to detach
// from the LogMiner session
// *Action: Contact Oracle Corporation
//
31479, 00000, "could not create LogMiner session"
// *Cause: Failure during create of a new LogMiner session while advancing
// an asynchronous change set. This is an internal error.
// *Action: Contact Oracle Corporation
//
31480, 00000, "staging database and source database cannot be the same"
// *Cause: A CDC API call specified a source database name that matched
// the staging database on which the CDC API call is being executed.
// *Action: Make sure that the CDC API call is being executed from the
// staging database and that the source database is correctly
// specified. The source database and staging database need to be
// different databases.
//
31481, 00000, "change source %s is not a HotLog change source"
// *Cause: A change source was specified that was not a HotLog
// change source, but a HotLog change source was required.
// *Action: Correct the call to supply a HotLog change source.
//
31482, 00000, "invalid option for non-distributed Hotlog change source"
// *Cause: A CDC API call specified enabled_source = 'Y' on a
// non-Distributed HotLog change source.
// *Action: Specify a Distributed HotLog change source.
//
31483, 00000, "cannot have spaces in the parameter %s "
// *Cause: The specifed parameter contained at least 1 space character.
// *Action: Check the value of the specified parameter. Remove the spaces
// and reissue the CDC API call.
//
31484, 00000, "source database version must be at least 9.2.0.6 or greater"
// *Cause: The source database is not at version 9.2.0.6 or higher.
// *Action: Upgrade the source database to 9.2.0.6 or higher.
//
31485, 00000, "invalid database link"
// *Cause: The database link used to connect from a staging database to
// a source database was invalid. The database link may not exist,
// may not be accessible to the current user, or may have been
// redefined since the Distributed HotLog change source was
// originally created.
// *Action: Make sure that there is a database link to the
// source_database for the Distributed HotLog change source.
// Make sure this database link is accessible to the current
// user.
//
31486, 00000, "cannot support column %s in this configuration"
// *Cause: The specified column cannot be used in a Distributed HotLog
// configuration when the source database version is 9.2.0.6 or
// 10.1.0.0.
// *Action: Remove the specified column from the CREATE_CHANGE_TABLE or
// ALTER_CHANGE_TABLE CDC API call.
//
31487, 00000, "cannot support begin dates or end dates in this configuration"
// *Cause: The specified values cannot be used in a Distributed HotLog
// configuration.
// *Action: Remove the specified values from the CREATE_CHANGE_SET
// CDC API call.
//
31488, 00000, "cannot support change set %s in this configuration"
// *Cause: Change sources with the hot mine option enabled are limited to
// 1 change set. The system detected an existing change set so a
// second one can not be created.
// *Action: Associate the change set with a different change source.
//
31489, 00000, "invalid DDL_MARKERS value"
// *Cause: A DDL_MARKERS value of 'y' was specified for an synchronous
// change table.
// *Action: Specify a DDL_MARKERS parameter value of 'n' and call the
// procedure again.
//
31490, 00000, "could not attach to LogMiner session"
// *Cause: Failure during attach to a LogMiner session while advancing
// an asynchronous change set. This is an internal error.
// *Action: Contact Oracle Corporation
//
31491, 00000, "could not add logfile to LogMiner session"
// *Cause: Failure during add logfile to a LogMiner session while advancing
// an asynchronous change set. This is an internal error.
// *Action: Contact Oracle Corporation
//
31492, 00000, "could not set session parameters for LogMiner session"
// *Cause: Failure during set parameters for a LogMiner session while
// advancing an asynchronous change set. This is an internal error.
// *Action: Contact Oracle Corporation
//
31493, 00000, "could not prepare session for LogMiner session"
// *Cause: Failure during prepare session for a LogMiner session while
// advancing an asynchronous change set. This is an internal error.
// *Action: Contact Oracle Corporation
//
31494, 00000, "could not activate a LogMiner session"
// *Cause: Failure during activation of a LogMiner session while advancing
// an asynchronous change set. This is an internal error.
// *Action: Contact Oracle Corporation
//
31495, 00000, "error in synchronous change table on \"%s\".\"%s\""
// *Cause: There was an error originating from this synchronous change
// table. One possible cause is that schema redefinition has
// occurred on the source table and one or more columns in the
// change table are now a different type than corresponding
// source columns. Another possible cause is that there is a
// problem accessing the synchronous change table.
// *Action: Check further error messages in stack for more detail about
// the cause. If there has been schema redefinition, drop and
// recreate the synchronous change table.
//
31496, 00000, "must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables"
// *Cause: An attempt was made to use the SQL command DROP TABLE for change
// tables, but DROP TABLE is not supported for change tables.
// *Action: Use the DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE procedure instead
// of the DROP TABLE command.
//
31497, 00000, "invalid value specified for first_scn"
// *Cause: The first_scn was not greater than zero or was less than the
// previous value of first_scn.
// *Action: Check the value of first_scn. Correct it to make sure it is
// an integer greater than zero and greater than any previous
// value for this change source.
//
31498, 00000, "description and remove_description cannot both be specified"
// *Cause: The description and remove_description parameters were both
// specified.
// *Action: Check the values of description and remove_description.
// Correct call to only supply one of these values.
//
31499, 00000, "null value specified for required parameter %s"
// *Cause: A null value was specified for a parameter that requires
// an explicit value.
// *Action: Correct call to supply a value for this parameter.
//
31500, 00000, "change source %s is not a ManualLog change source"
// *Cause: A change source was specified that is not a ManualLog
// change source, but a ManualLog change source is required.
// *Action: Correct call to supply a ManualLog change source.
//
31501, 00000, "change source %s is not an AutoLog change source"
// *Cause: A change source was specified that was not an AutoLog
// change source, but an AutoLog change source was required.
// *Action: Correct call to supply an AutoLog change source.
//
31502, 00000, "invalid number supplied for supplemental_processes"
// *Cause: The caller supplied an invalid value for supplemental_processes.
// The value must be a positive integer.
// *Action: Correct call to supply a positive integer value for
// supplemental_processes.
//
31503, 00000, "invalid date supplied for begin_date or end_date"
// *Cause: The caller supplied an invalid value for begin_date or end_date.
// The value must be a valid date value.
// *Action: Correct call to supply a valid date value for
// begin_date and/or end_date.
//
31504, 00000, "cannot alter or drop predefined change source"
// *Cause: The caller attempted to alter or drop one of the predefined
// change sources HOTLOG_SOURCE or SYNC_SOURCE.
// *Action: Do not attempt to alter or drop a predefined change source
// or correct call to supply the name of a user-created change
// source.
//
31505, 00000, "cannot alter or drop predefined change set"
// *Cause: The caller attempted to alter or drop the predefined
// change set SYNC_SET.
// *Action: Do not attempt to alter or drop the predefined change set
// or correct call to supply the name of a user-created change
// set.
//
31506, 00000, "duplicate subscription name %s"
// *Cause: A subscription by the specifed name already exists.
// *Action: Recreate the subscription with a unique name.
//
31507, 00000, "%s parameter value longer than maximum length %s"
// *Cause: A value was specified for a parameter that was longer
// than the maximum permitted length.
// *Action: Correct the call to supply a shorter value for this parameter
// that fits within the maximum length.
//
31508, 00000, "invalid parameter value for synchronous change set"
// *Cause: A parameter value was specified that is not supported
// for synchronous change sets.
// *Action: Correct the call to supply only valid parameter values
// for a synchronous change set. Synchronous change sets
// only support the default values for the following parameters:
// begin_scn, end_scn, begin_date, end_date, stop_on_ddl,
// supplemental_processes.
//
31509, 00000, "publication does not exist"
// *Cause: The specified publication did not exist or the specified
// subscription subscribed to a publication that no longer exists.
// *Action: Recheck the publication or subscription specified. Either
// call the procedure again with an existing publication or
// create a new subscription that only subscribes to existing
// publications.
//
31510, 00000, "name uses reserved prefix CDC$"
// *Cause: A name was specified that starts CDC$. The name prefix CDC$
// is reserved for use by Oracle Corporation.
// *Action: Change the name so it does not start with characters CDC$
//
31511, 00000, "name exceeds maximum length of 30 characters"
// *Cause: A name was supplied that exceeds the maximum length of
// 30 characters.
// *Action: Change the name so it does not exceed 30 characters
//
31512, 00000, "name cannot contain double quotation marks"
// *Cause: A name containing a double quotation mark was supplied.
// Subscription names cannot contain the double quotation mark.
// *Action: Change the name so it has no double quotation marks
//
31513, 00000, "unsupported column type specified in change table"
// *Cause: A source column of an unsupported type was specified for
// inclusion in a change table. Columns types of LOB or LONG are
// not currently supported for change capture.
// *Action: Change the column list so that it does not include columns
// of LOB or LONG types.
//
31514, 00000, "change set %s disabled due to capture error"
// *Cause: This change set has encountered a capture error and was disabled.
// *Action: Contact the change set's publisher to request that the
// capture error be resolved. Subscriptions using this change
// set cannot be activated or have their subscription windows
// extended or purged until the capture error is resolved.
//
31515, 00000, "CDC change source %s already exists"
// *Cause: A Change Data Capture change source intended for import already
// existed.
// *Action: Either verify that the existing change source has the desired
// characteristics or drop the existing change source and
// perform the import again.
//
31516, 00000, "CDC change set %s already exists"
// *Cause: A Change Data Capture change set intended for import already
// existed.
// *Action: Either verify that the existing change set has the desired
// characteristics or drop the existing change set and
// perform the import again.
//
31517, 00000, "CDC change table %s.%s already exists"
// *Cause: A Change Data Capture change table intended for import already
// existed.
// *Action: Either verify that the existing change table has the desired
// characteristics or drop the existing change table and
// perform the import again.
//
31518, 00000, "change column %s already exists in CDC change table %s.%s"
// *Cause: A column in a Change Data Capture change table intended for
// import was already present in the change table.
// *Action: Either verify that the change table contains the desired
// columns or drop the change table and perform the import again.
//
31519, 00000, "CDC subscription %s already exists"
// *Cause: A Change Data Capture subscription intended for import already
// existed.
// *Action: Either verify that the existing subscription has the desired
// characteristics or drop the existing subscription and
// perform the import again.
//
31520, 00000, "CDC subscription %s already subscribes to publication ID %s"
// *Cause: A Change Data Capture subscription intended for import already
// subscribed to a publication.
// *Action: Either verify that the existing subscription has the desired
// characteristics or drop the existing subscription and
// perform the import again.
//
31521, 00000, "CDC subscription %s already subscribes to publication ID %s column %s"
// *Cause: A Change Data Capture subscription intended for import already
// subscribed to a published column.
// *Action: Either verify that the existing subscription has the desired
// characteristics or drop the existing subscription and
// perform the import again.
//
31522, 00000, "could not find Streams object %s for CDC change set %s"
// *Cause: An underlying Streams capture, apply, or queue was missing
// for an imported Change Data Capture change set.
// *Action: Drop the imported change set because it is invalid.
// Retry the import, ensuring that STREAMS_CONFIGURATION=y is
// specified.
//
31523, 00000, "could not find change source %s for CDC change set %s"
// *Cause: The change source was missing for an imported
// Change Data Capture change set.
// *Action: Drop the imported change set because it is invalid.
// Verify that the schema containing the missing change source
// was included in the original export. If needed, perform the
// export again, including the schema of the missing change source.
//
31524, 00000, "could not find change set %s for CDC change table %s.%s"
// *Cause: The change set was missing for an imported
// Change Data Capture change table.
// *Action: Drop the imported change table because it is invalid.
// Verify that the schema containing the missing change set
// was included in the original export. If needed, perform the
// export again, including the schema of the missing change set.
//
31525, 00000, "could not find column %s in CDC change table %s.%s"
// *Cause: A column was missing for an imported Change Data Capture
// change table.
// *Action: It is likely that this table existed before the import
// operation and import did not overwrite it. Determine whether
// the imported change table should supercede the original
// table. If so, drop the original table and retry the import.
// If not, the change table must have a different name in
// order to be imported.
//
31526, 00000, "could not find source table %s.%s for CDC change table %s.%s"
// *Cause: The source table was missing or was not set up correctly for
// an imported Change Data Capture change table. A synchronous
// change table requires the source table to exist and have the
// Change Data Capture trigger defined on it. An asynchronous
// change table requires table rules to be defined for the
// source table.
// *Action: Drop the imported change table because it is invalid.
// Verify that the schema containing the source table
// was included in the original export. If needed, perform the
// export again, including the schema of the source table.
// If change table is asynchronous, ensure that
// STREAMS_CONFIGURATION=y is specified for the import.
//
31527, 00000, "could not find source column %s for CDC change table %s.%s"
// *Cause: A source column was missing for an imported Change Data Capture
// change table.
// *Action: Drop the imported change table because it is invalid.
// Verify that the schema containing the source table
// was included in the original export. If needed, perform the
// export again, including the schema of the missing source table.
//
31528, 00000, "could not find change set %s for CDC subscription %s"
// *Cause: The change set was missing for an imported
// Change Data Capture subscription.
// *Action: Drop the imported subscription because it is invalid.
// Verify that the schema containing the missing change set
// was included in the original export. If needed, perform the
// export again, including the schema of the missing change set.
//
31529, 00000, "could not find publication for CDC subscriber view %s.%s"
// *Cause: A publication was missing for an imported
// Change Data Capture subscription.
// *Action: Drop the imported subscription because it is invalid.
// Verify that the schema containing the missing publication
// was included in the original export. If needed, perform the
// export again, including the schema of the missing publication.
//
31530, 00000, "could not find published column %s for CDC subscriber view %s.%s"
// *Cause: A published column was missing for an imported
// Change Data Capture subscription.
// *Action: Drop the imported subscription because it is invalid.
// Verify that the schema containing the missing published column
// was included in the original export. If needed, perform the
// export again, including the schema of the missing published
// column.
//
31531, 00000, "could not find column %s in CDC subscriber view %s.%s"
// *Cause: A column was missing in a subscriber view for an imported
// Change Data Capture subscription.
// *Action: It is likely that this view existed before the import
// operation and import did not overwrite it. Determine whether
// the imported subscriber view should supercede the original
// view. If so, drop the original view and retry the import.
// If not, the subscriber view must have a different name in
// order to be imported.
//
31532, 00000, "cannot enable change source %s"
// *Cause: The change source cannot be enabled when there is no change
// table created in any of the change sets associated with
// the change source.
// *Action: Add a change table to a change set before enabling the
// the change source.
//
31533, 00000, "only one change set (%s) is allowed in change source"
// *Cause: A Distributed HotLog change source can contain at most one
// change set.
// *Action: Create a new change source and create the change set in the
// new change source.
//
31534, 00000, "Change Data Capture %s publisher %s is missing DBA role"
// *Cause: The publisher does not have the DBA role, which is required by
// the Change Data Capture operation.
// *Action: Grant the DBA role the Change Data Capture publisher.
//
/
31535, 00000, "cannot support change source %s in this configuration"
// *Cause: Each database can only have one change source with hot mine
// option enabled. The system detected an existing hot mine
// change source in the database, therefore, a second hot mine
// change source cannot be created.
// *Action: Remove the existing change source and create this new change
// source again.
//
/
31536, 00000, "cannot support encrypted column %s in the source table"
// *Cause: One of the columns specified in the parameter COLUMN_TYPE_LIST
// was an encrypted column in the source table
// *Action: remove the encrypted column in the parameter COLUMN_TYPE_LIST
/
31537, 00000, "specified purge date is invalid"
// *Cause: The purge date specified was an invalid date or was outside
// of the range of data currently in the change set.
// *Action: Do not specify purge date or specify a date that is within
// the range of data in the change set.
/
31538, 00000, "change set %s disabled"
// *Cause: This change set was disabled.
// *Action: Contact the change set's publisher to request that the
// change set be enabled. Subscriptions using this change
// set cannot be activated or have their subscription windows
// extended or purged until the change set is enabled.
/
31539, 00000, "no privilege to create job"
// *Cause: This change table could not be created because the create job
// privilege is needed to submit the default purge job.
// *Action: Grant the create job privilege and try again
/
31540, 00000, "%s is not a valid identifier"
// *Cause: All Change Data Capture (CDC) identifiers must have at most 30
// characters, and must start with a letter that is followed
// by any combination of letters, numerals, and the signs
// '$', '_', and '#'. Other characters cannot be used in identifiers.
// The rules for CDC identifiers are the same as for PL/SQL identifiers.
// *Action: Rename object to conform to CDC naming rules and try again.
/
/ ADD NEW CHANGE DATA CAPTURE ERROR MESSAGES ABOVE THIS LINE and add
/ additional tests to tqccmesg.sql
/
/ Error Number 31541 - 31599 are reserved for Logminer
/
31541, 00000, "Supplemental logging is not enabled in CDB$ROOT."
// *Cause: An attempt was made to enable supplemental logging in a
// pluggable database when supplemental logging was not already
// enabled in CDB$ROOT.
// *Action: Enable supplemental logging in CDB$ROOT and then retry
// the command.
/
/ Error Numbers 31600 - 31699 are reserved for Data Pump
/ These are raised by calling dbms_sys_error.raise_system_error.
/
31600, 00000, "invalid input value %s for parameter %s in function %s"
// *Cause: A NULL or invalid value was supplied for the parameter.
// *Action: Correct the input value and try the call again.
31601, 00000, "Function %s cannot be called now that fetch has begun."
// *Cause: The function was called after the first call to FETCH_xxx.
// *Action: Correct the program.
31602, 00000, "parameter %s value \"%s\" in function %s inconsistent with %s"
// *Cause: The parameter value is inconsistent with another value
// specified by the program. It may be inconsistent with the
// object type associated with the OPEN context, or it may be
// of the wrong datatype (a boolean rather than a text string
// or vice versa).
// *Action: Correct the program
31603, 00000, "object \"%s\" of type %s not found in schema \"%s\""
// *Cause: The specified object was not found in the database.
// *Action: Correct the object specification and try the call again.
31604, 00000, "invalid %s parameter \"%s\" for object type %s in function %s"
// *Cause: The specified parameter value is not valid for this object type.
// *Action: Correct the parameter and try the call again.
31605, 00000, "the following was returned from %s in routine %s:\nLPX-%d: %s"
// *Cause: An LPX routine (XML/XSL processing) returned an internal
// error number to its PL/SQL wrapper routine in facility KUX which
// provides the implementation for package UTL_XML.
// *Action: Look up the LPX error number and follow its corrective action.
31606, 00000, "XML context %u does not match any previously allocated context"
// *Cause: A method in package UTL_XML was called with an invalid XML
// context handle. All handles must have previously been allocated by
// UTL_XML.XMLINIT.
// *Action: Always call XMLINIT before any other methods in pkg. UTL_XML.
31607, 00000, "function %s is inconsistent with transform."
// *Cause: Either (1) FETCH_XML was called when the "DDL" transform
// was specified, or (2) FETCH_DDL was called when the
// "DDL" transform was omitted.
// *Action: Correct the program.
31608, 00000, "specified object of type %s not found"
// *Cause: The specified object was not found in the database.
// *Action: Correct the object specification and try the call again.
31609, 00000, "error loading file \"%s\" from file system directory \"%s\""
// *Cause: The installation script initmeta.sql failed to load
// the named file from the file system directory into the database.
// *Action: Examine the directory and see if the file is present
// and can be read.
31610, 00000, "cannot call this function from a non-master process"
// *Cause: Called a Data Pump process model function from a process which is
// not a master process.
// *Action: Create a master process first. Then call the function from the
// master process. If this error occurs from a Data Pump client (e.g.
// expdp or impdp), try the operation again. If the error occurs
// again, contact Oracle Customer Support and report the error.
31611, 00000, "Data Pump multiple processing setting is locked and cannot be changed."
// *Document: NO
// *Cause: Internal use only.
// *Action: This error should never be reported except when doing problem
// analysis under the supervision of Oracle development.
// *Comment: Tried to disable or enable multiple processing after a master
// process was already created in this session. Exit the session and
// start a new session. Or, make the call before creating a master
// process.
31612, 00000, "Allocation of process descriptor failed."
// *Cause: During creation of a master process or a worker process, a failure
// occurred allocating a process descriptor for the process.
// *Action: Try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
31613, 00000, "Master process %s failed during startup."
// *Cause: The master process whose name is listed failed during startup.
// *Action: Refer to any following error messages for possible actions. Check
// the trace log for the failed process to see if there is any
// information about the failure. Correct the error, if possible, and
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
31614, 00000, "routine %s received this error from %s: \n%s"
// *Cause: The call to the specified routine failed and the specific error
// text is included in this error message (the last %s string).
// *Action: Correct inputs to the specified routine.
31615, 00000, "routine %s received this error: \n%s"
// *Cause: The specified routine failed and the specific error
// text is included in this error message (the last %s string).
// *Action: Correct inputs to the specified routine.
31616, 00000, "unable to write to dump file \"%s\""
// *Cause: Export was unable to write to the export file, probably because of
// a device error. This message is usually followed by a device
// message from the operating system.
// *Action: Take appropriate action to restore the device.
31617, 00000, "unable to open dump file \"%s\" for write"
// *Cause: Export was unable to open the export file for writing. This
// message is usually followed by device messages from the operating
// system.
// *Action: Take appropriate action to restore the device.
31618, 00000, "FILESIZE is outside valid range of %sKB to %sTB"
// *Cause: The value specified for the FILESIZE parameter was either too small
// to hold the header information for the export file, plus any data,
// or exceeded the allowed maximum size for a dump file.
// *Action: Retry the operation using a value for FILESIZE that falls within
// the valid range.
31619, 00000, "invalid dump file \"%s\""
// *Cause: Either the file was not generated by Export or it was corrupted.
// *Action: If the file was indeed generated by Export, report this as an
// Import bug and submit the export file to Oracle Customer Support.
31620, 00000, "file or device \"%s\" cannot be specified for %s operation"
// *Cause: There was an inappropriate use of file or device in the current
// operation.
// *Action: Correct operation or job setup.
31621, 00000, "error creating master process"
// *Cause: Setup to create a master process failed.
// *Action: Refer to any following error messages for possible actions. Correct
// the error, if possible, and try the operation again. If the error
// occurs again, contact Oracle Customer Support and report the error.
31622, 00000, "premature end of file at block %s"
// *Cause: The end of the dump file input was unexpectedly reached. This is
// caused either by a corrupted Data Pump export dump file or by an
// Oracle internal error. This message should be preceded by another
// message identifying the name of the dump file in question.
// *Action: Retry the Data Pump import operation. Contact Oracle Support
// Services if the problem persists.
31623, 00000, "a job is not attached to this session via the specified handle"
// *Cause: An attempt to reference a job using a handle which is invalid or
// no longer valid for the current session.
// *Action: Select a handle corresponding to a valid active job or start a
// new job.
31624, 00000, "A job cannot be modified after it has started."
// *Cause: The user attempted to change the definition of a Data Pump job
// through filters, transforms or parameters after it had started.
// These changes can only be made while defining a job.
// *Action: Stop the current job and rerun it with the correct definition.
31625, 00000, "Schema %s is needed to import this object, but is unaccessible"
// *Cause: An error occurred when attempting to import objects. The schema
// specified is needed to import this object, but access to this
// schema is not available.
// *Action: Refer to any following error messages for possible actions. Correct
// the error, if possible, and try the operation again. If the error
// occurs again, contact Oracle Customer Support and report the error.
31626, 00000, "job does not exist"
// *Cause: An invalid reference to a job which is no longer executing,
// is not executing on the instance where the operation was
// attempted, or that does not have a valid Master Table.
// Refer to any following error messages for clarification.
// *Action: Start a new job, or attach to an existing job that has a
// valid Master Table.
31627, 00000, "API call succeeded but more information is available"
// *Cause: The user specified job parameters that yielded informational
// messages.
// *Action: Call DBMS_DATAPUMP.GET_STATUS to retrieve additional information.
31628, 00000, "error getting worker process exception"
// *Cause: Attempt to get a worker process exception failed.
// *Action: Refer to any following error messages for possible actions. Correct
// the error, if possible, and try the operation again. If the error
// occurs again, contact Oracle Customer Support and report the error.
31629, 00000, "unable to allocate additional memory"
// *Cause: A dynamic memory allocation failure occurred.
// *Action: Report this problem to a database administrator.
31630, 00000, "a job name is required to attach a job for user %s"
// *Cause: No job name was supplied for an attach and the user has either
// no jobs executing or mutiple jobs executing.
// *Action: Provide a job name for attach to use in selecting an executing
// job, or to use for restarting a stopped job.
31631, 00000, "privileges are required"
// *Cause: The necessary privileges are not available for operations such
// as: restarting a job on behalf of another owner, using a device
// as a member of the dump file set, or ommiting a directory
// object associated with any of the various output files.
// Refer to any following error messages for additional information.
// *Action: Select a different job to restart, try a different operation, or
// contact a database administrator to acquire the needed privileges.
31632, 00000, "master table \"%s.%s\" not found, invalid, or inaccessible"
// *Cause: A Master Table is required but no such table exists, or the
// content is not consistent with that of a valid Master Table,
// or the table is not accessible. Refer to any following error
// messages for clarification.
// *Action: Make sure a valid Master Table exists, and eliminate any problems
// indicated by the following error messages.
31633, 00000, "unable to create master table \"%s.%s\""
// *Cause: Job creation failed because a Master Table and its indexes could
// not be created, most commonly due to the pre-existance of a table
// with the same name (job name) in the user schema. Refer to any
// following error messages for clarification.
// *Action: Select a different job name, DROP the existing table, or eliminate
// any problems indicated by the following error messages.
31634, 00000, "job already exists"
// *Cause: Job creation or restart failed because a job having the selected
// name is currently executing. This also generally indicates that
// a Master Table with that job name exists in the user schema. Refer
// to any following error messages for clarification.
// *Action: Select a different job name, or stop the currently executing job
// and re-try the operation (may require a DROP on the Master Table).
31635, 00000, "unable to establish job resource synchronization"
// *Cause: A lock used in synchronizing Data Pump resources during job
// creation and deletion could not be obtained during job creation.
// This indicates that a process for some other Data Pump job has not
// released the lock due to an internal error.
// *Action: Eliminate the processes for any failed Data Pump job and try to
// create the new job again. If the error continues to occur, contact
// Oracle Customer Support and report the error.
31636, 00000, "session is already attached to job %s for user %s"
// *Cause: The session executing the attach is already attached to
// the specified job.
// *Action: Select a different job or create a new session.
31637, 00000, "cannot create job %s for user %s"
// *Cause: Unable to create or restart a job. Refer to any following or
// prior error messages for clarification.
// *Action: Eliminate the problems indicated.
31638, 00000, "cannot attach to job %s for user %s"
// *Cause: Unable to attach a job to a session. Refer to any following or
// prior error messages for clarification.
// *Action: Eliminate the problems indicated.
31639, 00000, "unexpected data found"
// *Cause: The Master Table or Data Pump file contents appear invalid. The
// table or file may not have been produced by a Data Pump job, or
// they may have been corrupted.
// *Action: Select a different job name (Master Table) or replace the
// table or file with one produced by Data Pump.
31640, 00000, "unable to open dump file \"%s\" for read"
// *Cause: Import was unable to open the export file for reading. This
// message is usually followed by device messages from the operating
// system.
// *Action: Take appropriate action to restore the device.
31641, 00000, "unable to create dump file \"%s\""
// *Cause: Export was unable to create the specified file with write enabled.
// *Action: Check the file name and file system for the source of the error.
31642, 00000, "the following SQL statement fails: \n%s"
// *Cause: An internal error was generated from package DBMS_METADATA.
// *Action: Contact Oracle Customer Support and report the error.
31643, 00000, "unable to close dump file \"%s\""
// *Cause: Export or Import was unable to close the dump file. This message
// is usually followed by device messages from the operating system.
// *Action: Take appropriate action to restore the device.
31644, 00000, "unable to position to block number %s in dump file \"%s\""
// *Cause: Export or Import was unable to position its file pointer to a
// specific block within the dump file. This message is usually
// followed by device messages from the operating system.
// *Action: Take appropriate action based on the device messages.
31645, 00000, "unable to read from dump file \"%s\""
// *Cause: Import could not read from the dumpfile, probably because of a
// device error. This message is usually followed by a device message
// from the operating system.
// *Action: Take appropriate action to restore the device.
31646, 00000, "no dump files found"
// *Document: NO
// *Cause: Signal to Master process that no files have been added to the
// Import job.
// *Action:
31647, 00000, "Worker process received exit message from Master process"
// *Document: NO
// *Cause: File Manager component raises this exception to calling Worker
// when it receives an exit message during a file request. Worker
// can then initiate its orderly shutdown.
// *Action:
31648, 00000, "Timeout before master process %s finished initialization."
// *Cause: The master process whose name is listed started up but did not
// finish its initialization within the allowed time limit.
// *Action: Refer to any following error messages for possible actions. Check
// the trace log for the failed process to see if there is any
// information about the failure. Correct the error, if possible, and
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
31649, 00000, "Master process %s violated startup protocol."
// *Cause: The master process whose name is listed started up but then exited
// before notifying the creating process that it was finished with
// initialization.
// *Action: Refer to any following error messages for possible actions. Check
// the trace log for the failed process to see if there is any
// information about the failure. Correct the error, if possible, and
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
31650, 00000, "timeout waiting for master process response"
// *Cause: After creating the job infrastructure and sending the initial
// message to the master process, it failed to respond in the
// allotted time and most likely aborted during startup.
// *Action: Retry the open or attach request. Contact Oracle Customer Support
// if the problem persists.
31651, 00000, "communication error with master process - detaching job"
// *Cause: Unexpected failure trying to communicate with the master
// process.
// *Action: Attach again and retry operation. Contact Oracle Customer Support
// if the problem persists.
31652, 00000, "command response message was invalid type - detaching job"
// *Cause: Something horribly wrong with the command/response protocol.
// *Action: Reattach and retry operation. Contact Oracle Customer Support if
// the problem persists.
31653, 00000, "unable to determine job operation for privilege check"
// *Cause: Failure trying to determine the operation of the current job
// in order to test for appropriate privileges.
// *Action: Retry in case it's an intermittent failure. If it still fails,
// detach, reattach, and retry the call. Contact Oracle Customer
// Support if the problem persists.
31654, 00000, "unable to convert file or volume size as specified to a number"
// *Cause: File or volume size specification has an error the prevents it
// from being converted into a numeric value.
// *Action: Fix the call.
31655, 00000, "no data or metadata objects selected for job"
// *Cause: After the job parameters and filters were applied,
// the job specified by the user did not reference any objects.
// *Action: Verify that the mode of the job specified objects to be moved.
// For command line clients, verify that the INCLUDE, EXCLUDE and
// CONTENT parameters were correctly set. For DBMS_DATAPUMP API
// users, verify that the metadata filters, data filters, and
// parameters that were supplied on the job were correctly set.
31656, 00000, "cannot use TABLESPACE_EXPR filter with transportable mode"
// *Cause: A TABLESPACE_EXPR metadata filter was supplied for for a
// transportable mode import job. Transportable mode import does
// not support the subsetting of tablespaces from a dump file set.
// *Action: Remove the filter expression.
31657, 00000, "data filter name can not be defaulted"
// *Cause: A null data filter name was supplied.
// *Action: Fix the call to specify a data filter name.
31658, 00000, "specifying a schema name requires a table name"
// *Cause: The caller specified a schema name but neglected to specify
// a corresponding table name.
// *Action: Fix the call to include a table name.
31659, 00000, "status message was invalid type - detaching job"
// *Cause: Message from the master process on the status queue
// had an invalid message type, indicating a failure in the protocol.
// *Action: Reattach and retry the operation. Contact Oracle Customer Support
// if the problem persists.
31660, 00000, "metadata filter name can not be defaulted"
// *Cause: A null metadata filter name was supplied.
// *Action: Fix the call to specify a metadata filter name.
31661, 00000, "there are no metadata transform values of type VARCHAR2"
// *Cause: The specified metadata transform value was an invalid type.
// *Action: Fix the call to specify a valid metadata transform value.
31662, 00000, "metadata transform name can not be defaulted"
// *Cause: A null metadata transform name was supplied.
// *Action: Fix the call to specify a metadata transform name.
31663, 00000, "metadata remap name can not be defaulted"
// *Cause: A null metadata remap name was supplied.
// *Action: Fix the call to specify a metadata remap name.
31664, 00000, "unable to construct unique job name when defaulted"
// *Cause: The job name was defaulted, and the name creation algorithm
// was unable to find a unique job name for this schema where the
// table name (for the master table) didn't already exist.
// *Action: Specify a job name to use or delete some of the existing tables
// causing the name conflicts.
31665, 00000, "mode can only be defaulted for IMPORT and SQL_FILE operations"
// *Cause: The job mode can not be null except for IMPORT and SQL_FILE
// operations.
// *Action: Fix the call to specify the job mode.
31666, 00000, "Master process %s had an unhandled exception."
// *Cause: A Data Pump process model master process had an unhandled exception
// condition.
// *Action: Refer to any following error messages for possible actions. Check
// the trace log for the failed process to see if there is any
// information about the failure. Correct the error, if possible, and
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
31667, 00000, "parameter name can not be defaulted"
// *Cause: A null was supplied for the parameter name.
// *Action: Fix the call by providing a valid parameter name.
31668, 00000, "Timeout before worker process %s finished initialization."
// *Cause: The worker process whose name is listed started up but did not
// finish its initialization within the allowed time limit.
// *Action: Refer to any following error messages for possible actions. Check
// the trace log for the failed process to see if there is any
// information about the failure. Correct the error, if possible, and
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
31669, 00000, "Worker process %s violated startup protocol."
// *Cause: The worker process whose name is listed started up but then exited
// before notifying the creating process that it was finished with
// initialization.
// *Action: Refer to any following error messages for possible actions. Check
// the trace log for the failed process to see if there is any
// information about the failure. Correct the error, if possible, and
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
31670, 00000, "Username argument must be specified and non-null."
// *Cause: Called change user with a NULL username or a null string.
// *Action: Specify a valid username argument. If this error occurs from a
// Data Pump client (e.g. expdp or impdp), try the operation again.
// If the error occurs again, contact Oracle Customer Support and
// report the error.
31671, 00000, "Worker process %s had an unhandled exception."
// *Cause: A Data Pump process model worker process had an unhandled exception
// condition.
// *Action: Refer to any following error messages for possible actions. Check
// the trace log for the failed process to see if there is any
// information about the failure. Correct the error, if possible, and
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
31672, 00000, "Worker process %s died unexpectedly."
// *Cause: A Data Pump process model worker process died unexpectedly, so
// PMON is cleaning up the process.
// *Action: Check your system for problems. Check the trace file for the
// process, if one was created, for any additional information.
// Correct the error, if possible, and try the operation again. If
// the error occurs again, contact Oracle Customer Support and report
// the error.
31673, 00000, "worker process interrupt for normal exit by master process"
// *Cause: A worker process was requested to clean up and exit because the
// master process is doing a normal exit.
// *Action: If this error occurs from a Data Pump client (e.g. expdp or
// impdp). it means that the master process for the operation exited
// prematurely. Try the operation again. If the error occurs again,
// contact Oracle Customer Support and report the error.
31674, 00000, "worker process interrupt for unhandled exception in master process"
// *Cause: A worker process was requested to clean up and exit because an
// unhandled exception occurred in the master process.
// *Action: If this error occurs from a Data Pump client (e.g. expdp or
// impdp), it means that the master process for the operation had an
// unhandled exception. Check the log file for the operaton and the
// trace file for the master process for any additional information.
// Try the operation again. If the error occurs again, contact
// Oracle Customer Support and report the error.
31675, 00000, "worker process interrupt for unexpected death of master process"
// *Cause: A worker process was requested to clean up and exit (signaled
// by PMON, doing cleanup because the master process died
// unexpectedly).
// *Action: If this error occurs from a Data Pump client (e.g. expdp or
// impdp), it means that the master process for the operation died
// unexpectedly. Check the log file for the operaton and the trace
// file for the master process for any additional information. Try
// the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
31676, 00000, "illegal value for number of workers, %s"
// *Cause: Called create worker processes with an illegal number of workers
// specified.
// *Action: Make sure that the number of workers value is greater than 0 and
// less than the maximum value for the platform (normally 32767). If
// this error occurs from a Data Pump client (e.g. expdp or impdp)
// and you specified the parallel parameter, try the operation again
// with a smaller value for the parallel parameter. If the error
// occurs again, contact Oracle Customer Support and report the error.
31677, 00000, "Estimate in progress using %s method..."
// *Document: NO
31678, 00000, "Worker Aborting Job"
// *Document: NO
31679, 00000, "Table data object %s cannot be imported or exported using a network link."
// *Cause: The table object contained at least one type that requires direct
// path and at least one type that requires insert as select or
// external tables to import the data. There is no method available
// to export or import this data over a database link.
// *Action: Export this table and data to a file and then import the same
// table and data from that file.
31680, 00000, ". . exported %s %s rows"
// *Document: NO
31681, 00000, ". . imported %s %s rows"
// *Document: NO
31682, 00000, "Master table %s successfully loaded/unloaded"
// *Document: NO
31683, 00000, "Processing object type %s"
// *Document: NO
31684, 00000, "Object type %s already exists"
// *Document: NO
31685, 00000, "Object type %s failed due to insufficient privileges. Failing sql is:\n%s"
// *Document: NO
31686, 00000, "error creating worker processes"
// *Cause: Setup to create worker processes failed.
// *Action: Refer to any following error messages for possible actions. Correct
// the error, if possible, and try the operation again. If the error
// occurs again, contact Oracle Customer Support and report the error.
31687, 00000, "error creating worker process %s with worker id %s"
// *Cause: Attempt to create the listed worker process failed.
// *Action: Refer to any following error messages for possible actions. Check
// the trace log for the failed process to see if there is any
// information about the failure. Correct the error, if possible, and
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
31688, 00000, "Worker process %s failed during startup."
// *Cause: The worker process whose name is listed failed during startup.
// *Action: Refer to any following error messages for possible actions. Check
// the trace log for the failed process to see if there is any
// information about the failure. Correct the error, if possible, and
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
31689, 00000, "illegal value for base worker id, %s"
// *Cause: Called create worker processes with an illegal base worker id value
// specified.
// *Action: Make sure that the base worker id value is greater than 0 and less
// than the maximum value for the platform (normally 32767). If this
// error occurs from a Data Pump client (e.g. expdp or impdp), try the
// operation again. If the error occurs again, contact Oracle Customer
// Support and report the error.
31690, 00000, "Process name buffer size must be specified and must be greater than 0."
// *Cause: Called get worker exception and either specified NULL or 0 for the
// buffer size argument.
// *Action: Be sure to specify a buffer size that is big enough to hold the
// worker process name (e.g. 30 bytes). If this error occurs from a
// Data Pump client (e.g. expdp or impdp), try the operation again. If
// the error occurs again, contact Oracle Customer Support and report
// the error.
31691, 00000, "The worker received message number %s from the MCP, which is invalid."
// *Cause: Bad code.
// *Action: Fix mcp code and reissue export/import command.
31692, 00000, "The following SQL statement failed trying to insert a row into the Master table:\n%s"
// *Cause: Bad code.
// *Action: Fix code and reissue export/import command.
31693, 00000, "Table data object %s failed to load/unload and is being skipped due to error:\n%s"
// *Cause: Table failed to load or unload due to some error.
// *Action: Check load/unload error, correct problem and retry command.
31694, 00000, "master table %s failed to load/unload"
// *Cause: Master table failed to load or unload.
// *Action: Check load/unload error, correct problem and retry command.
31695, 00000, "Inconsistent master table on restart. The following SQL statement returned %s identical objects.\n%s"
// *Cause: Master table on restart has the same object inserted multiple
// times.
// *Action: Restart not possible, reissue original export/import.
31696, 00000, "unable to export/import %s using client specified %s method"
// *Cause: Table attributes prevent client specified method for exporting
// or importing data.
// *Action: Use default 'DATA_ACCESS' parameter value.
31697, 00000, "aborting operation at process order number %s"
// *Cause: User asked for it.
// *Action: Don't ask for it.
31698, 00000, "Error stack buffer size must be specified and must be greater than 0."
// *Cause: Called get worker exception and either specified NULL or 0 for the
// error stack size argument.
// *Action: Be sure to specify am error stack buffer size that is big enough to
// hold the error stack string (e.g. 4096 bytes). If this error occurs
// from a Data Pump client (e.g. expdp or impdp), try the operation
// again. If the error occurs again, contact Oracle Customer Support
// and report the error.
31699, 00000, "test error for use in testing"
// *Document: NO
// *Cause: Internal use only
// *Action: This error should never be reported to a customer.
// *Comment: Test error for use in testing.
/
/ Data Pump errors continue with message 39001
/
//////////////////////////// Future Security Features
/ Error Numbers 31700 to 31900 are reserved for Future Security Features
31700, 00000, "very long string supplied for %s parameter"
// *Cause: A very long string was supplied for the specified parameter in the
// intialization parameter file.
// *Action: Use a valid facility.level such as "local1.notice" as described
// in the manual pages of the Syslog.
/
31701, 00000, "Event to enable xmltype table export/import with schema"
// *Cause: Event to enable xmltype table export/import with schema
// *Action: Disable the event at level 0x100
/
31702, 00000, "This privilege has already been granted."
// *Cause: The GRANT statement contained a privilege that was already granted to the user.
// *Action: Remove the privilege from the statement and retry.
/
31703, 00000, "cannot grant %s privilege on behalf of other users"
// *Cause: Granting of the privilege was attempted by a user other than SYS or the owner.
// Action: Granting of the privilege can only be done by SYS or the owner.
31704, 00000, "cannot revoke %s privilege on behalf of other users"
// *Cause: Revoking of the privilege was attempted by a user other than SYS or the owner.
// Action: Revoking of the privilege can only be done by SYS or the owner.
31705, 00000, "failed to get library object"
// *Cause: An error occurred while trying to lock the library object.
// Action: Retry the operation later.
31706, 00000, "role %s not granted commonly or does not exist"
// *Cause: Either the role was not granted commonly to the user, or the role did not exist.
// *Action: Create the role or grant the role commonly to the user and retry
// the operation.
31707, 00000, "cannot grant %s privilege"
// *Cause: Granting of privilege INHERIT PRIVILEGES or TRANSLATE SQL was
// attempted to an invalid user.
// *Action: Grant the privilege to a valid user.
31708, 00000, "role %s not granted commonly or does not exist"
// *Cause: Either the role was not granted commonly to the user, or the
// role did not exist.
// *Action: Create the role or grant the role commonly to the user and
// retry the operation.
//////////////////////////// End of Future Security Features
//////////////////////////// Summary Management
/ Error Numbers 31901 to 31950 are reserved for Summary Management
//////////////////////////// End of Summary Management
31901, 00000, "the current operation was cancelled by the user"
// *Cause: The user requested to cancel current operation
// *Action: No action is necessary
/
31902, 00000, "access advisor debug/testing trace"
// *Document: NO
// *Cause:
// *Action: access advisor debug/testing
/
31903, 00000, "cannot unregister materialized view for Synchronous refresh"
// *Cause: One or more materialized views in the materialized views list
// were not registered for Synchronous refresh.
// *Action: Check catalog views for which materialized views are registered.
/
31904, 00000, "Synchronous refresh debug or testing trace"
// *Document: NO
// *Cause: N/A.
// *Action: Synchronous refresh debug or testing
/
31905, 00000, "Synchronous refresh cannot be used for materialized view \"%s\".\"%s\"\n%s"
// *Cause: The materialized view did not meet the requirements for Synchronous refresh.
// *Action: The query defining the materialized view must conform to a star or
// snowflake schema, the fact-table and materialized view must both
// be partitioned, and the partition-key of the materialized view
// must be functionally-dependent on the partition-key of the fact-table.
// Run CAN_SYNCREF_TABLE to obtain more diagnostics and troubleshoot
// the problem further.
/
31906, 00000, "Staging log of \"%s\".\"%s\" contains rows which do not belong to any of the table's partitions."
// *Cause: Synchronous refresh detected this error during PREPARE_REFRESH.
// Action: Check the data in the staging log for validity. If the data is
// valid, create additional partitions,, including a default
// partition if needed, with the ALTER TABLE command.
/
31907, 00000, "Synchronous refresh of \"%s\".\"%s\" results in rows which do not belong to any of the materialized view's partitions."
// *Cause: Synchronous refresh detected this error during PREPARE_REFRESH.
// Action: Check the data in the staging logs of the materialized view's
// base tables for validity. If the data is valid, create
// additional partitions, including a default partition if needed,
// with the ALTER MATERIALIZED VIEW command.
/
31908, 00000, "cannot modify the contents of a table with a staging log"
// *Cause: An attempt was made to alter the contents of a table with
// a staging log.
// *Action: Do not use the following ALTER TABLE statements on a table
// with a staging log:
// * ALTER TABLE EXCHANGE PARTITION
// * ALTER TABLE DROP PARTITION
// * ALTER TABLE TRUNCATE PARTITION
// You must use the REGISTER_PARTITION_OPERATION procedure in
// the DBMS_SYNC_REFRESH package to perform these operations.
/
31909, 00000, "base table \"%s\".\"%s\" must have primary key or foreign key when creating a staging log"
// *Cause: The base table did not have a primary or foreign key defined.
// *Action: Define primary key or foreign key on the base table.
/
31910, 00000, "staging log exists on table \"%s\".\"%s\""
// *Cause: Staging log was already generated on the base table.
// *Action: Do not attempt to create the staging log.
/
31911, 00000, "MV log on table \"%s\".\"%s\" is not completely consumed."
// *Cause: Materialized views (MV) referencing the base table were not refreshed.
// *Action: Refresh all the MVs referencing the base table before altering MV log to staging log.
/
31912, 00000, "Cannot alter MV log. MV log was not created on table \"%s\".\"%s\""
// *Cause: Materialized view (MV) log was not created on the base table.
// *Action: Do not alter the MV log.
/
31913, 00000, "Log is already an MV log on table \"%s\".\"%s\"."
// *Cause: An attempt was made to alter a staging log to a materialize view (MV) log when it was already an MV log.
// *Action: Do not alter the MV log.
/
31914, 00000, "Staging log was created on table \"%s\".\"%s\""
// *Cause: Staging log was not created on base table.
// *Action: Do not alter the staging log.
/
31915, 00000, "At least one MV referencing table \"%s\".\"%s\" is REFRESH ON COMMIT."
// *Cause: At least one materialize view (MV) referencing a table is defined as REFRESH ON COMMIT.
// *Action: Do not create or alter to the staging log.
/
31916, 00000, "Staging log on table \"%s\".\"%s\" cannot be dropped or altered."
// *Cause: The current group contained a materialize view (MV) referencing the table.
// *Action: Do not drop or alter the staging log.
/
31917, 00000, "illegal operation on a table which has been locked by synchronous refresh"
// *Cause: DML or DDL was used on a base table that had a staging log or was
// locked by synchronous refresh. The synchronous refresh operation
// locks tables related to the refresh group at PREPARE_REFRESH time
// and unlocks them after the EXECUTE_REFRESH is done to prevent
// wrong results.
// *Action: Do not perform DML or DDL on such tables. You cannot modify
// tables locked by PREPARE_REFRESH until you have done the
// corresponding EXECUTE_REFRESH.
/
31918, 00000, "The materialized view \"%s\".\"%s\" is registered for synchronous refresh and cannot be altered or dropped."
// *Cause: The materialized view was registered for synchronous refresh.
// *Action: Do not drop or alter the materialized view.
/
31919, 00000, "Value of DMLTYPE$$ column is not one of ('I','D','UO','UN') in staging log \"%s\".\"%s\"."
// *Cause: Value of DMLTYPE$$ column was not one of ('I','D','UO','UN').
// *Action: Update the staging log.
/
31920, 00000, "'UO' and 'UN' row counts or key values not matched in the staging log \"%s\".\"%s\"."
// *Cause: 'UO' and 'UN' row counts or key values were not matched in the staging log.
// *Action: Update the staging log.
/
31921, 00000, "Staging log rows to be updated, deleted or inserted were invalid.\n%s"
// *Cause: The staging log rows to be updated, deleted or inserted were invalid.
// *Action: Change the staging log key in the staging log table.
/
31922, 00000, "Foreign key must contain partition key in table \"%s\".\"%s\"."
// *Cause: The foreign key did not contain a partition key. If a table does not have a primary key, the foreign key must contain a partition key.
// *Action: Change the foreign key or partition key in the table.
/
31923, 00000, "must have primary key or partition key in table \"%s\".\"%s\""
// *Cause: The table did not have a primary key or a partition key.
// *Action: Add a primary key or partition key to the table.
/
31924, 00000, "must have either primary key or foreign key in table \"%s\".\"%s\""
// *Cause: The table did not have a primary key or a foreign key.
// *Action: Add a primary key or foreign key to the table.
/
31925, 00000, "Every row in staging log \"%s\".\"%s\" should contain non-NULL values for all the columns comprising staging log key."
// *Cause: The staging log contained NULL values in key columns.
// *Action: Fill in non-NULL values to the staging log key columns.
/
31926, 00000, "Type \"%s\" is not supported for synchronous refresh."
// *Cause: An attempt was made to create a staging log on a base table containing an unsupported data type.
// *Action: Do not attempt synchronous refresh on this base table. Refer to the documentation.
/
31927, 00000, "Staging log does not exist on table \"%s\".\"%s\"."
// *Cause: An attempt to prepare a staging log that did not exist.
// *Action: Create a staging log on the table first.
/
31928, 00000, "Synchronous refresh error\n%s"
// *Cause: An error occurred in the synchronous refresh package
// (DBMS_SYNC_REFRESH). This message will be followed by a second message
// giving more details about the nature of the error.
// *Action: See the synchronous refresh documentation
// for an explanation of the second error message.
/
31929, 00000, "Synchronous refresh debug or testing trace"
// *Document: NO
// *Cause: N/A.
// *Action: Synchronous refresh debug or testing
/
31930, 00000, "The table is locked by synchronous refresh and the requested operation cannot be performed."
// *Cause: An attempt was made to perform a PMOP (partition maintenance
// operation) or otherwise modify a table that was locked
// by synchronous refresh. The synchronous refresh operation
// locks tables related to the refresh group at PREPARE_REFRESH time
// and unlocks them after the EXECUTE_REFRESH is done to prevent
// wrong results.
// *Action: Do not perform PMOPs or modify the table between the execution of
// PREPARE_REFRESH and EXECUTE_REFRESH. You can do these operations
// before PREPARE_REFRESH or after EXECUTE_REFRESH.
/
31931, 00000, "general event for materialized view refresh"
// *Document: NO
// *Cause: N/A
// *Action: This internal event is used to enable various actions
// associated with MV refresh. The event level is interpreted
// as a bitmap of actions to enable.
//
// *Comment: Not for general purpose use.
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 enable complete refresh that does not use SCN for insert
/
31932, 00000, "cannot allocate memory of %s bytes for query expression"
// *Cause:
// *Action:
/
31933, 00000, "error occurred during refresh statistics processing at %s\n%s"
// *Cause: An error was detected by the refresh statistics subsystem at the
// position indicated by the first argument in the error message.
// The secondary error is indicated by the second argument in the
// error message. This error message is recorded in the trace file and
// alert log but is not thrown and the refresh operation is not
// aborted because of this error.
// *Action: Fix the problems indicated in the secondary error.
/
31934, 00000, "error occurred while shrinking the materialized view log at %s\n%s"
// *Cause: An error was detected while shrinking the materialized view (MV) log during
// refresh at the position indicated by the first argument in the error message.
// The secondary error is indicated by the second argument in the
// error message. This error message is recorded in the trace file and
// alert log but is not thrown and the refresh operation is not
// aborted because of this error.
// *Action: Fix the problems indicated in the secondary error, or disable
// MV log shrink during refresh by setting the parameter
// _mv_refresh_shrink_log to FALSE.
/
/////////////////////////////
/ Error Numbers 31951 to 31999 are reserved for Zonemaps
////////////////////////////
31951, 00000, "invalid SCALE value"
// *Cause: The value was not within the allowable range.
// *Action: Correct the value and try again.
/
31952, 00000, "invalid second argument"
// *Cause: The second argument was not an integer, bind variable, or the keyword PARTITION.
// *Action: Specify either the keyword PARTITION or an integer or a bind variable.
/
31953, 00000, "expected MIN or MAX aggregate not found"
// *Cause: Either a matching pair of MIN and MAX aggregates were missing or
// an aggregate other than MIN or MAX was found.
// *Action: Specify only matching pairs of MIN and MAX aggregates.
/
31954, 00000, "duplicate MIN or MAX aggregate found"
// *Cause: The same MIN or MAX aggregate was found more than once.
// *Action: Specify a MIN or MAX aggregate only once.
/
31955, 00000, "incorrect join found"
// *Cause: A join other than equality left outer join was found.
// *Action: Specify only simple equality left outer joins with the fact table
// on the left side.
/
31956, 00000, "construct or object '%s' not allowed for zonemap"
// *Cause: A construct or object not allowed in the zonemap definition was found.
// *Action: Remove the construct or object that is not allowed in the zonemap definition.
/
31957, 00000, "table %s not joined"
// *Cause: A table without a join to the fact table was found.
// *Action: Specify a left outer join between this table and the fact table.
/
31958, 00000, "fact table %s already has a zonemap %s on it"
// *Cause: The fact table already had a zonemap.
// *Action: Drop the existing zonemap and repeat the command.
/
31959, 00000, "internal error during the refresh of zonemap \"%s\".\"%s\""
// *Cause: An internal error was detected by the zonemap refresh subsystem and
// the refresh operation was aborted.
// *Action: Call Oracle Support Services.
/
31960, 00000, "must use DROP MATERIALIZED ZONEMAP to drop \"%s\".\"%s\""
// *Cause: An attempt was made to drop a zonemap using a command other than
// DROP MATERIALIZED ZONEMAP.
// *Action: Use the DROP MATERIALIZED ZONEMAP command.
/
31961, 00000, "must use ALTER MATERIALIZED ZONEMAP to alter \"%s\".\"%s\""
// *Cause: An attempt was made to alter a zonemap using a command other than
// ALTER MATERIALIZED ZONEMAP.
// *Action: Use the ALTER MATERIALIZED ZONEMAP command.
/
31962, 00000, "cannot fast refresh zonemap \"%s\".\"%s\""
// *Cause: The fast refresh operation was not possible because DML had occurred
// to one or more dimension tables of the zonemap.
// *Action: Specify the force ('?') or complete ('C') option.
/
31963, 00000, "invalid ALTER MATERIALIZED ZONEMAP option"
// *Document: NO
// *Cause:
// *Action:
/
31964, 00000, "matching GROUP BY expression required"
// *Cause: A matching GROUP BY expression was not found in the SELECT list.
// *Action: Specify an expression in the SELECT list that matches with the
// GROUP BY expression.
/
31965, 00000, "incorrect predicate found"
// *Cause: A predicate other than simple equality left outer join predicate
// was found.
// *Action: Specify only simple equality left outer join predicates with the
// fact table on the left side.
/
31966, 00000, "invalid option specified to alter \"%s\".\"%s\""
// *Cause: An invalid option was used to alter a zonemap table.
// *Action: Choose a valid option with the ALTER TABLE command.
/
31967, 00000, "built-in aggregate function must be named ZONE_ID$"
// *Cause: The name for built-in aggregate function was not ZONE_ID$.
// *Action: Specify zone_id$ or "ZONE_ID$" as the name for aggregate built-in
// function.
/
31968, 00000, "internal error during the staleness tracking of zonemap \"%s\".\"%s\""
// *Cause: An internal error was detected by the zonemap staleness tracking
// subsystem and the DML operation on the zonemap fact table was aborted.
// *Action: Call Oracle Support Services.
/
31969, 00000, "ZONEMAP not supported for table stored in tablespace of this storage type"
// *Cause: An attempt was made to define ZONEMAP on a table stored in
// non-Oracle Exadata storage.
// *Action: Create this table in a tablespace residing on Oracle Exadata
// storage and then define a ZONEMAP on it.
/
31970, 00000, "cannot comment on the materialized zonemap"
// *Cause: An attempt was made to issue a COMMENT ON TABLE statement
// on a materialized zonemap.
// *Action: Issue a COMMENT ON MATERIALIZED ZONEMAP statement instead.
/
31971, 00000, "maximum number of MIN/MAX columns is 240"
// *Document: NO
// *Cause:
// *Action:
/
31972, 00000, "cannot drop or alter the internal index on a materialized zone map"
// *Cause: An attempt was made to drop or alter the internal index used by a
// materialized zone map.
// *Action: Do not drop or alter the internal index on a materialized zone map.
// Operate on the materialized zone map instead.
/
31973, 00000, "invalid option specified to alter \"%s\".\"%s\"
// *Cause: An invalid option was used to alter a materialized view log table.
// *Action: Choose a valid option with the ALTER TABLE command.
/
/
//////////////////////////// KSP
/ Error numbers 31990 to 32030 are reserved for parameter operations
////////////////////////////
31990, 00000, "failed to process parameter \"%s\" from SPFILE"
// *Cause: An error was encountered while processing parameters from the SPFILE.
// *Action: Update the parameter value using the ALTER SYSTEM SET statement with scope set to SPFILE, and try opening the pluggable database again.
/
31991, 00000, "error occurred processing parameter '%s'"
// *Cause: The parameter could not be specified for a pluggable database.
// *Action: Remove the parameter and try again.
/
31992, 00000, "error while processing parameter '%s'"
// *Cause: An error was encountered while processing a comment for the parameter.
// *Action: Update or remove the comment and try again.
/
31993, 00000, "cannot overwrite parameter file '%s'"
// *Cause: The specified parameter file or server parameter file was already in existence.
// *Action: Delete the parameter file or server parameter file and try again.
/
31995, 00000, "error occurred processing parameter '%s'"
// *Cause: The combined length of all the parameter values was more than
// the allowed maximum.
// *Action: Reduce the parameter value length and retry the command.
/
32000, 00000, "write to SPFILE requested but SPFILE is not modifiable"
// *Cause: An ALTER SYSTEM command or an internal self-tuning mechanism
// requested a write to the SPFILE but the SPFILE was not modifiable.
// *Action: Perform an in-memory parameter update only.
/
32001, 00000, "write to SPFILE requested but no SPFILE is in use"
// *Cause: An ALTER SYSTEM command or an internal self-tuning mechanism
// requested a write to the SPFILE but no SPFILE was in use.
// *Action: Re-start the instance using an SPFILE, or execute ALTER SYSTEM
// SET SPFILE.
/
32002, 00000, "cannot create SPFILE already being used by the instance"
// *Cause: A create spfile command is trying to write to an SPFILE
// that was used to startup the instance.
// *Action: Specify a different SPFILE name
/
32003, 00000, "error occured processing parameter '%s'"
// *Cause: An error occured while parsing the parameter file.
// *Action: See additional errors to determine the root cause.
/
32004, 00000, "obsolete or deprecated parameter(s) specified for %s instance"
// *Cause: Obsolete or deprecated parameters for this instance type
// were specified in the SPFILE or the PFILE on the server side.
// *Action: See alert log for a list of parameters that are obsolete
// or deprecated. Remove them from the SPFILE or the server
// side PFILE.
/
32005, 00000, "error while parsing size specification [%s]"
// *Cause: The value specified for an alter operation on a size parameter
// is not valid
// *Action: Correct the value and retry the operation
/
32006, 00000, "%s initialization parameter has been deprecated"
// *Cause: A deprecated parmeter was specified at startup
// *Action: Consult Oracle documentation to find new parameters
// to use instead.
/
32007, 00000, "internal"
// *Cause: A parameter error occured.
// *Action: Call Oracle support.
/
32008, 00000, "error while processing parameter update at instance %s"
// *Cause: An error occured while processing a parameter on a remote
// instance.
// *Action: See accompanying error messages.
/
32009, 00000, "cannot reset the memory value for instance %s from instance %s"
// *Cause: Memory resets of local parameters are only allowed.
// *Action: Retry the query for the local instance if needed.
/
32010, 00000, "cannot find entry to delete in SPFILE"
// *Cause: The SPFILE did not contain the sid.parameter entry.
// *Action: Change the sid and/or the parameter.
/
32011, 00000, "cannot restore SPFILE to location already being used by the instance"
// *Cause: A restore operation trying to write to an SPFILE
// that was used to startup the instance.
// *Action: Specify a different SPFILE name
/
32012, 00000, "cannot reset the memory value of initialization parameter"
// *Cause: An attempt was made to reset the memory value of a parameter that has
// not been modified.
// *Action: None.
/
32013, 00000, "failure in verifying parameters from the restored SPFILE"
// *Cause: Failure during processing of parameters from restored SPFILE.
// It could be that restore image of the SPFILE is corrupted.
// *Action: Further diagnostic information should be in the error stack.
/
32014, 00000, "error processing parameter \"%s\" from the SPFILE restore image"
// *Cause: Failure during processing of parameters from restored SPFILE.
// It could be that restore image of the SPFILE is corrupted.
// *Action: Further diagnostic information should be in the error stack.
/
32015, 00000, "unable to restore SPFILE"
// *Cause: Failure during SPFILE restore. It could be that the restore
// destination is not valid.
// *Action: Further diagnostic information should be in the error stack.
/
32016, 00000, "parameter \"%s\" cannot be updated in SPFILE"
// *Cause: Database is mounted.
// *Action: Unmount the database to update the parameter in the SPFILE
/
32017, 00000, "failure in updating SPFILE"
// *Cause: A failure occured while updating the SPFILE.
// *Action: See associated errors.
/
32018, 00000, "parameter cannot be modified in memory on another instance"
// *Cause: Parameter adjustment can take a very long time
// *Action: Modify the parameter individually on each instance using
// the SID clause of the alter system command
/
32019, 00000, "The parameter SPFILE cannot be updated in the server parameter file."
// *Cause: An attempt was made to update the parameter SPFILE in the server
// parameter file.
// *Action: Convert the server parameter file into a parameter file and then
// add the parameters needed and recreate the server parameter file.
/
32020, 00000, "SID='*' clause needed to modify this parameter"
// *Cause: The parameter did not have the same value on all RAC instances.
// *Action: Retry the command by specifying SID='*'
//
/
32021, 00000, "parameter value longer than %s characters"
// *Cause: An attempt was made to alter a parameter value but the number of
// characters in the parameter value was longer than the
// allowed maximum. For a list parameter, one of the
// values in the list was longer than the allowed maximum.
// *Action: Reduce the parameter value length and retry the command.
// For the DISPATCHERS parameter, use listener aliases to
// reduce value length.
/
32022, 00000, "parameter %s value longer than %s characters"
// *Cause: The combined length of all the parameter values was more than
// the allowed maximum.
// *Action: Reduce the parameter value length and retry the command.
// For the DISPATCHERS parameter, use listener aliases to
// reduce value length.
/
32023, 00000, "failure to update the value for the parameter"
// *Document: NO
// *Cause: Internal error used by parameter processing
// *Action: None
/
32024, 00000, "invalid directory specified for audit_file_dest parameter"
// *Cause: Either the directory did not exist, it was not writable, or the
// path contained reference to the parent directory.
// *Action: Retry the command by specifying a valid directory or granting
// appropriate directory permissions.
/
32025, 00000, "%s.%s is not a table or view object."
// *Cause: An attempt was made to set the audit table to a non-table object
// or a non-view object.
// *Action: Specify a valid table or view object for the audit table option.
/
32026, 00000, "%s.%s has fewer columns compared to %s table."
// *Cause: An attempt was made to set the audit table to a table or view
// object that has fewer columns compared to the base audit table.
// *Action: Specify a valid table or view object for the audit table option.
/
32027, 00000, "There is no %s column with the matching type in %s.%s."
// *Cause: An attempt was made to set the audit table to a table or view
// object that does not have a column with the same name and type
// as the one in the audit table.
// *Action: Specify a valid table or view object for the audit table option.
/
32028, 00000, "Syslog facility or level not recognized"
// *Cause: Syslog facility or level did not conform to the standard
// facility or level provided in the syslog.h file
// *Action: Specify a facility or level such as "LOCAL1.NOTICE"
// which conforms to the syslog.h file
/
32029, 00000, "resetting with SCOPE=MEMORY or SCOPE=BOTH is currently not supported"
// *Cause: An attempt was made to reset an in-memory parameter value
// *Action: Specify SCOPE=SPFILE if applicable, or explicitly set the
// parameter to the desired value
/
32030, 00000, "an SPFILE is already associated with the instance"
// *Cause: An attempt was made to update the parameter SPFILE on an instance
// that was already associated with an spfile.
// *Action: Restart the instance with a parameter file.
/
/
/ Error Numbers 32031 - 32049 are reserved for WITH clause errors
/
32031, 00000, "illegal reference of a query name in WITH clause"
// *Cause: forward or recursive reference of a query name in WITH clause is not
// allowed.
// *Action: Correct query statement, then retry.
/
32032, 00000, "free temporary object number not available"
// *Cause: Too many queries using temp table transformation are currently
// being run to use up all temporay object numbers.
// *Action: Turn off temporary table transformation or wait, then retry
/
32033, 00000, "unsupported column aliasing"
// *Cause: column aliasing in WITH clause is not supported yet
// *Action: specify aliasing in defintion subquery and retry
/
32034, 00000, "unsupported use of WITH clause"
// *Cause: Inproper use of WITH clause because one of the following two reasons:
// 1. nesting of WITH clause within WITH clause not supported yet
// 2. For a set query, WITH clause can't be specified for a branch.
// 3. WITH clause cannot be specified within parenthesis.
// *Action: correct query and retry
/
32035, 00000, "unreferenced query name defined in WITH clause"
// *Cause: There is at least one WITH clause query name that is not
// referenced in any place.
// *Action: remove the unreferenced query name and retry
/
32036, 00000, "unsupported case for inlining of query name in WITH clause"
// *Cause: There is at least one query name which is inlined more than once
// because its definition query is too simple and references another
// query name. This is currently unsupported yet.
// *Action: remove such query name and retry
/
32037, 00000, "unsupported use of LEVEL in membership condition"
// *Cause: An attempt was made to use LEVEL in membership condition with
// subquery that is not supported.
// *Action: Rewrite query to avoid using LEVEL in membership condition
/
32038, 00000, "number of WITH clause column names does not match number of elements in select list"
// *Cause: A list of column aliases or names was specified for a WITH clause
// query name but the number of elements in the list did not match the
// number of elements in the select list of the definition query.
// *Action: Update the column alias list or the select list to ensure they
// have the same number of elements.
/
32039, 00000, "recursive WITH clause must have column alias list"
// *Cause: A WITH clause query referred to itself (recursive) but did
// not have a column alias list specified for it.
// *Action: Add a column alias list for the WITH clause query name.
/
32040, 00000, "recursive WITH clause must use a UNION ALL operation"
// *Cause: A WITH clause query referred to itself (recursive) but did
// not use a UNION ALL operation in its definition query.
// *Action: Rewrite the recursive WITH clause query to use a UNION ALL
// operation.
/
32041, 00000, "UNION ALL operation in recursive WITH clause must have only two branches"
// *Cause: A WITH clause query referred to itself (recursive) but used
// a UNION ALL operation with more than two branches, which is not
// currently supported.
// *Action: Rewrite the recursive WITH clause query to use only two branches in
// the UNION ALL operation.
/
32042, 00000, "recursive WITH clause must reference itself directly in one of the UNION ALL branches"
// *Cause: A WITH clause query referred to itself (recursive) indirectly,
// such as through a subquery or view.
// *Action: Rewrite the recursive WITH clause query to refer to itself directly
// in the FROM clause of one of the UNION ALL branches.
/
32043, 00000, "recursive WITH clause needs an initialization branch"
// *Cause: A WITH clause query referred to itself (recursive) but did not
// have a branch in a UNION ALL with no references to itself (the
// initialization branch or anchor member).
// *Action: Rewrite the recursive WITH query to have a branch in a UNION
// ALL operation with no references to itself.
/
32044, 00000, "cycle detected while executing recursive WITH query"
// *Cause: A recursive WITH clause query produced a cycle and was stopped
// in order to avoid an infinite loop.
// *Action: Rewrite the recursive WITH query to stop the recursion or use
// the CYCLE clause.
/
32045, 00000, "maximum level of recursion reached while executing recursive WITH query"
// *Cause: A recursive WITH query reached the maximum level of recursion
// specified and was stopped.
// *Action: Increase the maximum level of recursion or use the CYCLE clause.
/
32046, 00000, "sequence column name for SEARCH clause must not be part of the column alias list"
// *Cause: The SEARCH clause for a recursive WITH query specified a sequence
// column that was already listed in the column alias list for the
// WITH clause query name.
// *Action: Specify a different name for the sequence column for the SEARCH
// clause or remove the name from the column alias list.
/
32047, 00000, "cycle mark value and non-cycle mark value must be one byte character string values"
// *Cause: The cycle mark or the non-cycle mark values specified in the CYCLE
// clause of a recursive WITH query were not one byte character
// string values as required.
// *Action: Specify a one byte character string for the cycle mark and
// non-cycle mark values of the CYCLE clause for the recursive WITH
// query.
/
32048, 00000, "cycle mark column name for CYCLE clause must not be part of the column alias list"
// *Cause: The CYCLE clause for a recursive WITH query specified a cycle mark
// column that was already listed in the column alias list for the
// WITH clause query name.
// *Action: Specify a different name for the cycle mark column for the CYCLE
// clause or remove the name from the column alias list.
/
32049, 00000, "duplicate name found in column alias list for WITH clause"
// *Cause: The column alias list for a WITH clause element contained a name
// which appeared more than once in the list.
// *Action: Remove the duplicate name from the column alias list.
/
////////////////////////////// FILE MAPPING ERRORS
// Error numbers 32050 to 32099 are reserved for file mapping errors
//////////////////////////////
32050, 00000, "%s operation failed"
// *Cause: A mapping operation failed.
// *Action: Check FMON trace files for errors.
/
32051, 00000, "mapping service not available"
// *Cause: The mapping service was never started or previously failed
// to start properly.
// *Action: Set FILE_MAPPING to TRUE if it is not currently set. Otherwise,
// check FMON trace files for an ORA-32052 error.
/
32052, 00000, "failed to start mapping service"
// *Cause: The mapping service failed to start properly.
// *Action: Check FMON trace files for errors.
/
32053, 00000, "operation not supported"
// *Cause: Mapping libraries do not support operation.
// *Action: Check whether mapping libraries are available and
// whether operation is supported by the libraries.
/
32054, 00000, "lost communication with FMPUTL process"
// *Cause: Lost communication with mapping utility.
// *Action: Check FMON and FMPUTL trace files for errors.
/
32055, 00000, "invalid file type"
// *Cause: Invalid file type used when mapping files.
// *Action: Specify one of expected file types.
/
32056, 00000, "invalid number of extents"
// *Cause: Invalid number of extents used for map operation.
// *Action: Specify a non-negative number of extents.
/
32057, 00000, "invalid lock mode"
// *Cause: An invalid mode was used for a lock operation.
// *Action: Specify one of expected lock modes.
/
32058, 00000, "operation restricted to SYSDBA users"
// *Cause: Operation requires SYSDBA priviliges.
// *Action: Connect to the database as SYSDBA.
/
32059, 00000, "deadlock detected on mapping structures"
// *Cause: Mapping structures already locked by the same session.
// *Action: Unlock mapping structures before proceeding with current operation.
/
32060, 00000, "channel failure"
// *Cause: Channel failure between foreground and background process.
// *Action: Check foreground trace files for errors.
/
/
/ Error Numbers 32100 - 32299 are reserved for OCCI errors
/
32100, 00000, "operation invalid on transient object"
// *Cause: Trying to perform an operation on transient object which is
// is valid only on persistent objects
// *Action: Make sure object is persistent
/
32101, 00000, "cannot create OCI Environment"
// *Cause: An OCI Environment could not be created for OCCI
// *Action: Insure that the parameters to the creatEnvironment method are valid
/
32102, 00000, "invalid OCI handle"
// *Cause: An invalid OCI handle is passed to an OCI call.
// *Action: This is an internal OCCI Error. Please contact customer support.
/
32103, 00000, "error from OCI call"
// *Cause: An error code other than OCI_ERROR is returned from an OCI call.
// *Action: This is an internal OCCI Error. Please contact customer support.
/
32104, 00000, "cannot retrieve OCI error message"
// *Cause: Error message after an OCI call could not be retrieved.
// *Action: This is an internal OCCI Error. Please contact customer support.
/
32106, 00000, "array fetch not allowed without setBuffer on all columns"
// *Cause: The setBuffer method was not called for all column postions and
// the next method was called to fetch more than one row.
// *Action: Call the setBuffer method for all column positions if next is to
// to be called to fetch more than one row.
/
32107, 00000, "internal OCI memory allocation failure"
// *Cause: Memory could not be allocated from an OCI heap.
// *Action: Increase the process memory size.
/
32108, 00000, "max column or parameter size not specified"
// *Cause: The max column or parameter size is not specified.
// *Action: Specify the max size by setMaxColumnSize or setMaxParamSize.
/
32109, 00000, "invalid column or parameter position"
// *Cause: An invalid column or parameter position is specified.
// *Action: Specify a valid column or position number.
/
32110, 00000, "Connection not specified"
// *Cause: A null connection was passed.
// *Action: Pass a valid, non-null connection.
/
32113,00000, "Null object passed"
// *Cause: Null object was passed.
// *Action: Pass a non-null object.
/
32114, 00000, "Cannot perform operation on a null LOB"
// *Cause: The LOB instance on which the operation was attempted was null.
// *Action: Use a valid, non-null LOB instance to perform this operation.
/
32116, 00000, "Buffer size is less than amount specified"
// *Cause: The buffer size specified for the LOB read or write operation
// was less than the amount to be read or written.
// *Action: The buffer size must be equal to or greater than than the amount
// to be read from or written to the LOB.
/
32117, 00000, "Source LOB is null"
// *Cause: The source LOB instance on which the operation was attempted
// was null.
// *Action: Use a valid, non-null source LOB instance for this operation.
/
32118, 00000, "Cannot perform operation on a null FILE"
// *Cause: The FILE instance on which the operation was attempted was null.
// *Action: Use a valid, non-null FILE instance to perform this operation.
/
32120, 00000, "Buffer size is less than amount specified"
// *Cause: The buffer size specified for the FILE read or write operation
// was less than the amount to be read or written.
// *Action: The buffer size must be equal to or greater than than the amount
// to be read from or written to the FILE.
/
32121, 00000, "Source FILE is null"
// *Cause: The source FILE instance on which the operation was attempted
// was null.
// *Action: Use a valid, non-null source FILE instance for this operation.
/
32123, 00000, "Attribute number is out of range"
// *Cause: The attribute number passed is greater than the total number of
// attributes of the described object.
// *Action: Pass the attribute number within the allowable range.
/
32124, 00000, "Illegal attribute passed"
// *Cause: The attribute passed is not applicable for the described object.
// *Action: Pass a valid attribute.
/
32125, 00000, "Attribute type is not appropriate"
// *Cause: The return type of the get method does not match the type of the
// attribute being passed.
// *Action: Call the appropriate get method.
/
32126, 00000, "Cannot perform operations on a null REF"
// *Cause: The REF instance on which the operation was attempted was null.
// *Action: Use a valid, non-null REF instance to perform this operation.
/
32127, 00000, "REFs do not belong to any connection"
// *Cause: Neither of the REFs being compared had associated connection
// information.
// *Action: Atleast one of the REFs being compared must be associated with
// a valid connection.
/
32128, 00000, "setDataBuffer called after fetch has started"
// *Cause: Fetch from result set has already started and the setDataBuffer
// call was made.
// *Action: Call the setDataBuffer method before calling the next() method.
/
32129, 00000, "cannot get information about this column"
// *Cause: The setDataBuffer method was called to get information about this
// column. Therfore, the current method cannot be called.
// *Action: Use the information from the buffers specifed in the setDataBuffer
// call.
/
32130, 00000, "invalid offset/index refrenced in Bytes"
// *Cause: The offset/index is out of range of valid data locations in Bytes
// offsets.
// *Action: Insure that offsets or index is within the range of Bytes object.
/
32131, 00000, "bind data type cannot be changed"
// *Cause: The setXXX method is called again with a different data type than
// originally specified, or the setXXX method is called for a subsequent
// iteration without being called before the first iteration.
// *Action: Call the setXXX method with the same data type as done before the first
// iteration. If no setXXX method was called for this parameter postion
// the first iteration, then make sure that a setXXX method is called before
// the first addIteration method is called.
/
32132, 00000, "maximum iterations cannot be changed"
// *Cause: The setMaxIterations is called after a setXXX method has been called.
// *Action: Call the setMaxIterations method before calling any setXXX methods.
/
32133, 00000, "Cannot get stream from LOB/FILE"
// *Cause: An open stream exists on the the LOB/FILE on which
// the operation was attempted.
// *Action: Close the stream before getting another.
/
32134, 00000, "Cannot assign LOBs"
// *Cause: An open stream exists on the target LOB.
// *Action: Close the stream on the target LOB before assigning the LOBs.
/
32135, 00000, "Cannot assign FILEs"
// *Cause: An open stream exists on the target FILE.
// *Action: Close the stream on the target FILE before assigning the FILEs.
/
32136, 00000, "Cannot perform operation on an invalid stream"
// *Cause: The LOB/FILE from which the stream was obtained had been
// nullified or destroyed.
// *Action: Use a valid stream.
/
32139, 00000, "Cannot write to the stream"
// *Cause: A write was performed after the last buffer was written.
// *Action: Close this stream and get a new stream to perform the write.
/
32140, 00000, "cannot peform this operation on stream"
// *Cause: Either a read is attempted from a stream oi write mode, or
// a write is attempted on a stream in read mode.
// *Action: Check the status of the stream to find out the valid
// operations that can be performed.
/
32141, 00000, "get method does not match the type of the parameter"
// *Cause: The getXXX method called on the Statement object does
// not match the type of the bind parameter.
// *Action: Call the getXXX method that is the same as the type of the
// parameter.
/
32142, 00000, "maximum number of iterations exceeded"
// *Cause: The addIteration exceeds the maximum number of iterations
// set by the the setMaxIterations method.
// *Action: Increase the maximum number of allowed iterations.
/
32143, 00000, "Environment not specified"
// *Cause: A null environment was passed.
// *Action: Pass a valid, non-null environment.
/
32144, 00000, "Cannot perform operation on a null interval"
// *Cause: The interval involved in this operation is null.
// *Action: Use valid, non-null interval instance to perform this operation.
/
32145, 00000, "Environment not specified"
// *Cause: The interval on which the operation was attempted was null
// and no environment was specified.
// *Action: Specify non-null environment or perform the operation
// on a non null instance.
/
32146, 00000, "Cannot perform operation on a null date"
// *Cause: The date involved in this operation is null.
// *Action: Use valid, non-null date instance to perform this operation.
/
32147, 00000, "Environment not specified"
// *Cause: The date on which the operation was attempted was null
// and no environment was specified.
// *Action: Specify non-null environment or perform the operation
// on a non null instance.
/
32150, 00000, "Cannot perform operation on a null timestamp"
// *Cause: The timestamp involved in this operation is null.
// *Action: Use valid, non-null timestamp instance to perform this operation.
/
32151, 00000, "Environment not specified"
// *Cause: The timestamp on which the operation was attempted was null
// and no environment was specified.
// *Action: Specify non-null environment or perform the operation
// on a non null instance.
/
32152, 00000, "Cannot perform operation on a null number"
// *Cause: The number involved in this operation is null.
// *Action: Use valid, non-null number instance to perform this operation.
/
32153, 00000, "Environment not specified"
// *Cause: The number on which the operation was attempted was null
// and no environment was specified.
// *Action: Specify non-null environment or perform the operation
// on a non null instance.
/
32154, 00000, "Anydata context not specified"
// *Cause: A null anydata context was passed.
// *Action: Pass a valid, non-null anydata context.
/
32155, 00000, "Anydata not specified"
// *Cause: A null anydata was passed.
// *Action: Pass a valid, non-null anydata.
/
32156, 00000, "Cannot perform operation on stream"
// *Cause: This operation is not applicable to streams obtained from LOBs.
// *Action:
/
32157, 00000, "Infinity not supported"
// *Cause:
// *Action:
/
32158, 00000, "Invalid type passed"
// *Cause: An inapplicable type was passed to this call.
// *Action: Pass an applicable type.
/
32159, 00000, "Cannot set prefetch options for a null Type"
// *Cause: A null Type name was passed.
// *Action: Pass an non-null Type name.
/
32161, 00000, "Cannot perform piecewise fetch"
// *Cause: Zero amount was passed and buffer size was less than LOB size
// *Action: Specify a larger buffer or use Stream
/
32162, 00000, "Read/Write SQL method not registered"
// *Cause: readSQL/writeSQL method was NULL or was not registered
// *Action: Register readSQL/writeSQL by calling put method in Map
/
32163, 00000, "Method called on Invalid Environment type"
// *Cause: A non-XA call made on an XA Environment or
// XA call made on non-XA Environment
// *Action: Make sure Environment type is OK
/
32164, 00000, "Method called on Invalid Connection type"
// *Cause: A non-XA call made on an XA Connection or
// XA call made on non-XA Connection
// *Action: Make sure Connection type is OK
/
32165, 00000, "Cannot get XA environment"
// *Cause: Incorrect dbname string was passed or the
// XA connection has not been opened
// *Action: Pass the correct dbname string or check if
// the XA connection is open
/
32166, 00000, "Cannot get XA connection"
// *Cause: Incorrect dbname string was passed or the
// XA connection has not been opened
// *Action: Pass the correct dbname string or check if
// the XA connection is open
/
32167, 00000, "No payload set on the Message"
// *Cause: An attempt was made to enqueue a message without setting a
// payload on it.
// *Action: Set a payload on the message before calling the send method.
/
32168, 00000, "Cannot perform operation on a null AnyData"
// *Cause: The AnyData instance on which the operation was attempted
// was null.
// *Action: Use a valid, non-null AnyData instance to perform this operation.
/
32169, 00000, "Execution completed successfully but the number of rows affected is more than the maximum value of the unsigned integer."
// *Cause: The row count was larger than the maximum value of the
// unsigned integer. OCCI clients using 'executeUpdate()'
// cannot retrieve row counts larger than the maximum value
// of the unsigned integer.
// *Action: Use 'getUb8RowCount()' to get the correct row count.
// Use 'execute()' and 'getUb8RowCount()' for large updates.
/
/
/ Error Numbers 32300 - 32399 are reserved for Materialized view errors
/
32300, 00000, "cannot drop a secondary materialized view \"%s\".\"%s\""
// *Cause: An attempt was made to drop a materialized view of a
// nested table column's storage table.
// *Action: Drop the materialized view that contains the nested
// table column. This will implicitly drop all secondary
// materialized views.
/
32301, 00000, "object-relational materialized views must be primary key based"
// *Cause: An attempt was made to create an object-relational
// materialized view that is not primary key based.
// *Action: Create the materialized view with the PRIMARY KEY keyword.
/
32302, 00000, "object materialized views must be object ID based"
// *Cause: An attempt was made to create an object materialized view
// that is not object ID based.
// *Action: Create the materialized view using the OF clause but omit
// any ROWID or PRIMARY KEY clauses.
/
32303, 00000, "mviews with user-defined types cannot reference multiple master sites"
// *Cause: For materialized views with user-defined types,
// the definition query cannot reference tables from different
// master sites.
// *Action: Do not create materialized views with user-defined types
// referencing multiple master sites.
/
32304, 00000, "materialized views with user-defined types cannot use prebuilt table"
// *Cause: An attempt was made to create a materialized view with the
// ON PREBUILT TABLE option.
// *Action: Do not create the materialized view with the
// ON PREBUILT TABLE option.
/
32305, 00000, "RepAPI materialized views with user-defined types are not supported"
// *Cause: An attempt was made to create a RepAPI materialized view
// with user-defined types.
// *Action: Do not create a RepAPI materialized view with user-defined types.
/
32306, 00000, "updatable materialized views with user-defined types must use SELECT *"
// *Cause: An attempt was made to create an updatable materialized
// view with user-defined types where the definition query
// did not use SELECT * at the topmost level.
// *Action: Rewrite the definition query so that SELECT * is used
// at the topmost level.
/
32307, 00000, "must use FROM ONLY clause when referencing an object table"
// *Cause: An attempt was made to create a materialized view whose
// definition query references object tables without the
// FROM ONLY clause.
// *Action: Rewrite the definition query to use the FROM ONLY clause
// for all the object tables in the query.
/
32308, 00000, "object materialized views must use SELECT *"
// *Cause: An attempt was made to create an object materialized view
// where the definition query did not use SELECT *
// at the topmost level.
// *Action: Rewrite the definition query so that SELECT * is used
// at the topmost level.
/
32309, 00000, "object mview type \"%s\".\"%s\" does not match the master table type"
// *Cause: An attempt was made to create an object materialized view
// whose type does not match the type of the master object table.
// *Action: Redefine the type so that it matches the type of the
// master object table.
/
32310, 00000, "object materialized views must select from an object table"
// *Cause: An attempt was made to create an object materialized view whose
// definition query did not select from an object table.
// *Action: Rewrite the definition query to select from an object table.
/
32311, 00000, "materialized view definition query selects an unsupported user-defined type"
// *Cause: An attempt was made in the definition query to select an
// embedded user-defined type, function returning a
// user-defined type, or a function whose arguments are
// user-defined types.
// *Action: Rewrite the definition query to exclude these unsupported
// user-defined types.
/
32312, 00000, "cannot refresh a secondary materialized view \"%s\".\"%s\""
// *Cause: An attempt was made to refresh a materialized view of a
// nested table column's storage table.
// *Action: Refresh the materialized view that contains the nested
// table column. This will implicitly refresh all secondary
// materialized views.
/
32313, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after PMOPs"
// *Cause: A Partition Maintenance Operation (PMOP) has been performed on a
// detail table, and the specified materialized view does not support
// fast refersh after PMOPs.
// *Action: Use REFRESH COMPLETE. Note: you can determine why your
// materialized view does not support fast refresh after PMOPs using
// the DBMS_MVIEW.EXPLAIN_MVIEW() API.
/
32314, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after deletes/updates"
// *Cause: One or more deletes or updates has been performed on one or more
// of the detail tables referenced by the specified materialized
// view. This materialized view does not support fast refresh after
// deletes or updates.
// *Action: Use REFRESH COMPLETE. Note: you can determine why your
// materialized view does not support fast refresh after deletes or
// updates using the DBMS_MVIEW.EXPLAIN_MVIEW() API.
/
32315, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after mixed DML and Direct Load"
// *Cause: One or more of the materialized view logs on the detail tables
// referenced by the specified materialized view omits the sequence
// number option. Such a log cannot be used to refresh a
// materialized view after deletes or updates and direct path insert.
// *Action: Use REFRESH COMPLETE. Note: you can use the
// DBMS_MVIEW.EXPLAIN_MVIEW() API to determine which materialized view
// logs omit the sequence number option.
/
32316, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after mixed DML"
// *Cause: One or more of the materialized view logs on the detail tables
// referenced by the specified materialized view omits the sequence
// number option. Such a log cannot be used to refresh a
// materialized view after deletes or updates have been performed on
// multiple detail tables.
// *Action: Use REFRESH COMPLETE. Note: you can use the
// DBMS_MVIEW.EXPLAIN_MVIEW() API to determine which materialized view
// logs omit the sequence number option.
/
32317, 00000, "cannot run a job from a job"
// *Cause: An attempt was made to execute a job from within another job.
// *Action: Do not submit jobs that run other jobs.
/
32318, 00000, "cannot rename a materialized view"
// *Cause: Renaming a materialized view or its base table is not supported.
// *Action: Do not rename the base table of a materialized view.
/
32319, 00000, "Cannot use direct loader log to FAST REFRESH materialized view \"%s\".\"%s\""
// *Cause: The direct loader log might have been dropped
// *Action: Need to do complete refresh
/
32320, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after container table PMOPs"
// *Cause: A Partition Maintenance Operation (PMOP) has been performed on the
// materialized view, and no materialized view supports
// fast refersh after container table PMOPs.
// *Action: Use REFRESH COMPLETE. Note: you can determine why your
// materialized view does not support fast refresh after PMOPs using
// the DBMS_MVIEW.EXPLAIN_MVIEW() API.
/
32321, 00000, "REFRESH FAST of \"%s\".\"%s\" unsupported after detail table TRUNCATE"
// *Cause: A detail table has been truncated and no materialized view
// supports fast refersh after a detail table has been truncated
// *Action: Use REFRESH COMPLETE. Note: you can determine why your
// materialized view does not support fast refresh after TRUNCATE using
// the DBMS_MVIEW.EXPLAIN_MVIEW() API.
/
32322, 00000, "PCT refresh of \"%s\".\"%s\" not allowed the sequence of DMLs/PMOPs"
// *Cause: A table join dependent on another table on which PCT refresh is
// enabled has changed
// *Action: Use REFRESH FORCE which will pick the best possible refresh method on
// the materialized view
/
32330, 00000, "invalid operation on online redefinition interim table \"%s\".\"%s\""
// *Cause: An invalid operation was performed on an interim table which
// was being used for online redefinition of a table.
// *Action: Do not perform any unsupported operation on the interim table.
32331, 00000, "type \"%s\".\"%s\" is incompatible with the master site"
// *Cause: A type used by the materialized view was found to be
// incompatible with its coressponding type on the master site.
// This could be because the type does not exist on the master site
// or has been evolved to a different version from that on the
// materialzied view site.
// *Action: Make sure that the types used by the materialized view are the
// same on both the materialized view and master sites.
32332, 00000, "cannot refresh materialized view \"%s\".\"%s\" as type evolution has occured"
// *Cause: The types used by the materialized view or its master tables have
// been evolved.
// *Action: Ensure that the types used by the materialized view have been
// evolved to the same version at both the master and materialized
// sites. Then, before refreshing the materialized view, evolve the
// materialized view using ALTER MATERIALIZED VIEW.
/
32333, 00000, "disable table scn update for Materialized view"
// *Cause: an event is set for disabling table scn update to prevent
// deadlock situation. (bug 1376209)
// *Action: disable null refresh and/or base table scn update for Materialized view
/
32334, 00000, "cannot create prebuilt materialized view on a table already referenced by a MV"
// *Cause: the table on which the materialized view is created as prebuilt is already
// referenced by a materialized view
// *Action: create the materialized view on a different table
/
32335, 00000, "dimension must have at least one level"
// *Cause: An level-less dimension is not allowed.
// *Action: Do not drop the only level of a dimension.
/
32336, 00000, "cannot use USING NO INDEX to create materialized view \"%s\".\"%s\""
// *Cause: The USING NO INDEX option was specified to create an updatable
// primary key based materialized view, an index-organized
// materialized view or an object-id materialized view.
// *Action: Do not use the USING NO INDEX option to create an updatable
// primary key based materialized view, an index-organized
// materialized view or an object-id materialized view.
/
32337, 00000, "cannot alter materialized view or zonemap to refresh on commit with pending changes"
// *Cause: There were some pending changes in the detail tables.
// *Action: Perform on-demand refresh of the materialized view or zonemap to synchronize
// the data between the materialized view and the detail tables and then
// issue the ALTER MATERIALIZED VIEW or ALTER MATERIALIZED ZONEMAP statement.
/
32338, 00000, "on commit refresh grab all the detailed tables"
// *Cause: an event is set to let on-commit MV refresh to grab all the detailed
// tables, no matter whether they have modified or not.
// *Action:
/
32339, 00000, "cannot alter materialized view with the PMOP"
// *Cause: the materialized view is not allowed to have destructive PMOPS
// such as DROP, TRUNCATE and EXCHANGE (sub)partition. The UGA flag
// of i_am_a_refresh should be set first.
// *Action: execute set_i_am_a_refresh first before alter materialized view
// with the PMOP.
/
32340, 00000, "cannot tune the materialized view definition"
// *Cause: Due to constructs in the materialized view definition, it
// could not be tuned to be fast-refreshable or rewriteable.
// *Action: Execute DBMS_MVIEW.EXPLAIN_MVIEW to determine the cause.
/
32341, 00000, "The EXPLAIN_MVIEW facility failed to explain the materialized view \"%s\".\"%s\""
// *Cause: The dependent object(s) of the materialized view may have changed.
// The materialized view may no longer be valid.
// *Action: Execute ALTER MATERIALIZED VIEW COMPILE and to determine the status of
// the materialized view in catalog views.
/
32342, 00000, "The EXPLAIN_MVIEW facility failed to explain the materialized view statement"
// *Cause: An error exists in the materialized view definition. As a result,
// the materialized view statement could not be explained.
// *Action: Check the syntax of the statement. If it is a CREATE MATERIALIZED
// VIEW statement, then also check the PARAMETERs specified for the
// materialized view.
/
32343, 00000, "let MVIEW engine know that it is IMPORT from 9i or earlier"
// *Cause: N/A.
// *Action: Set this event only under the supervision of Oracle development.
// Not for general purpose use.
/
32344, 00000, "cannot create a secondary materialized view with synonym as base table"
// *Cause: It is not supported to create a secondary materialized view with
// synonym in the FROM clause.
// *Action: Removed the synonym(s) from the statement.
/
32345, 00000, "fail to refresh the materialized view %s.%s due to the changed synonym"
// *Cause: The definition of one or more synonyms in the from clause
// have changed. The structure of the materialized view has become
// invalid.
// *Action: Restore the synonym(s) or drop the materialized view and recreate
// it again.
/
32346, 00000, "ON COMMIT materialized view refresh caused changes to the master table/materialized view"
// *Cause: ON COMMIT refresh of a read-only materialized view changed the master table/materialized view.
// A trigger on the refreshed materialized view may be the cause.
// *Action: Do not create triggers on materialized view which update the master table/materialized view.
/
32347, 00000, "NULL capabilities during explain mview "
// *Cause: The supplied defining query did not generate any capabilities
// information.
// *Action: Replace the query since it is not suitable for creating a
// materialized view.
/
32348, 0000, "revalidate summary object based on user input"
// *Cause: An event was set to specify the number of attempts that the system
// needed to make in order to validate an invalidated summary object.
//
// *Action: Revalidate an invalidated summary object based on user input.
/
32349, 00000, "cannot reference prebuilt table in definition query for materialized view"
// *Cause: The prebuilt container table of the materialized view was
// referenced in the definition query.
// *Action: Change the definition query to reference a non-prebuilt table.
/
32350, 00000, "ON COMMIT refresh obtain shared lock for all the detailed tables"
// *Cause: An event was set to let ON COMMIT refresh to obtain a shared lock
// for all the detailed tables, whether they have been modified or
// not.
// *Action: No action necessary.
/
32351, 00000, "database link name cannot start with a number while creating materialized view"
// *Cause: This event was disabled by default. If enabled, the fix for bug
// 6074902 will be disabled and you will be unable to create database
// links starting with a number when creating a materialized view
// on remote tables.
// *Action: No action necessary.
/
32352, 00000, "cannot refresh materialized view %s.%s using out-of-place fast refresh"
// *Cause: Out-of-place fast refresh was either not enabled on this
// materialized view or not possible after changes to the base table
// made since the last refresh.
// *Action: Specify the FORCE or COMPLETE option for out-of-place refresh.
/
32353, 00000, "cannot refresh materialized view %s.%s using out-of-place PCT refresh"
// *Cause: Out-of-place Partition Change Tracking (PCT) refresh was either
// not enabled on this materialized view or not possible after
// changes to the base table made since the last refresh.
// *Action: Specify the FORCE or COMPLETE option for out-of-place refresh.
/
32354, 00000, "cannot refresh materialized view %s.%s using out-of-place complete refresh"
// *Cause: The materialized view did not qualify for out-of-place complete
// refresh.
// *Action: Set the 'out_of_place' parameter to 'false'.
/
32355, 00000, "out-of-place refresh cannot be used in atomic mode"
// *Cause: Both 'atomic_refresh' and 'out_of_place' parameters were set to
// 'true' in the refresh interface.
// *Action: Either set the 'atomic_refresh' parameter to 'false' or set
// the 'out_of_place' parameter to 'false'.
/
32356, 0000, "refresh_all_mviews() debug or testing"
// *Document: NO
// *Cause: None
// *Action: None
/
32357, 00000, "failed to refresh on-commit materialized view %s.%s"
// *Cause: There was an error in the refresh path of the on-commit
// materialized view.
// *Action: Examine the other messages on the error stack in the alert log and
// take corrective action.
/
32358, 00000, "cannot perform on-query computation for materialized view %s.%s"
// *Cause: The ENABLE ON QUERY COMPUTATION option was specified for the
// materialized view [owner].[mv_name] but on-query computation
// was not feasible for the change scenario.
// *Action: Alter the materialized view [owner].[mv_name] to disable on-query
// computation, or refresh the materialized view [owner].[mv_name]
// before issuing the query again.
/
32359, 00000, "cannot specify the FRESH_MV hint for this query"
// *Cause: The query included a construct that was not supported by the on-query
// computation, and so the FRESH_MV hint could not be specified. The on-query
// computation does not support the CONNECT BY clause, the MATERIALIZE hint, or
// spreadsheet queries.
// *Action: Remove the FRESH_MV hint from the query.
/
32360, 00000, "cannot ENABLE ON QUERY COMPUTATION for a refresh-on-commit materialized view"
// *Cause: The ENABLE ON QUERY COMPUTATION option was specified when the
// ON COMMIT REFRESH option was also specified.
// *Action: Remove the ENABLE ON QUERY COMPUTATION option or specify refresh
// options other than ON COMMIT REFRESH.
/
32361, 00000, "cannot ENABLE ON QUERY COMPUTATION for the materialized view"
// *Cause: On-query computation was not feasible for the materialized view
// being created or altered.
// *Action: Remove the ENABLE ON QUERY COMPUTATION option or make the
// materialized view capable of on-query computation.
/
32362, 00000, "cannot create system-partitioned materialized view"
// *Cause: An attempt to create a system-partitioned materialized view failed.
// *Action: Remove the PARTITION BY SYSTEM clause from the materialized
// view definition query.
/
32363,0000, "prebuilt table managed column cannot be a virtual column"
// *Cause: An attempt was made to create a materialized view on a
// prebuilt table that has a managed column which is a virtual column.
// *Action: Do not include the column in the materialized view definition.
/
32364, 00000, "cannot perform on-query computation for this query"
// *Cause: The FRESH_MV hint was specified for the query but
// on-query computation was not feasible due to conflicting
// system settings or processes.
// *Action: Remove the FRESH_MV hint from the query to run the query
// without on-query computation. To run the query with on-query
// computation, verify that the system settings are compatible with
// this feature.
/
32366, 00000, "mview definition query cannot include an inline external table clause"
// *Cause: An attempt was made to include an inline external table clause
// in the materialized view definition query.
// *Action: Remove the inline external table clause from the materialized
// view definition query. Alternatively, you can replace the
// inline external table clause with a reference to an external
// table having the same properties.
/
// Error Numbers 32400 - 32459 are reserved for Materialized view log errors
32400, 0000, "cannot use object id columns from materialized view log on \"%s\".\"%s\""
// *Cause: The materialized view log either does not have object id columns
// logged, or the timestamp associated with the object id columns is
// more recent than the last refresh time.
// *Action: A complete refresh is required before the next fast refresh.
// Add object id columns to the materialized view log, if required.
/
32401, 00000, "materialized view log on \"%s\".\"%s\" does not have new values"
// *Cause: Materialized view log on the indicated table does not have new
// values information.
// *Action: Add new values to materialized view log using the ALTER
// MATERIALIZED VIEW LOG command.
/
32403, 00000, "cannot use new values from mv log on \"%s\".\"%s\""
// *Cause: The materialized view log either does not have new values
// logged, or the timestamp associated with the new values columns is
// more recent than the last refresh time.
// *Action: Perform a complete refresh is required before the next fast
// refresh.
/
32404, 00000, "snapshot log uses Change Data Capture which is not enabled for this database"
// *Cause: A snapshot log that utilizes Change Data Capture is being imported
// to a database where Change Data Capture has not been enabled.
// *Action: First enable Change Data Capture on the database then retry the
// import.
/
32405, 00000, "cannot alter tablespace for existing materialized view log"
// *Cause: The tablespace specification for the existing materialized view log
// cannot be altered or changed.
// *Action: remove the tablespace clause from the statement.
/
32406, 00000, "cannot alter partitioning for existing materialized view log"
// *Cause: The partitioning specification for the existing materialized view log
// cannot be altered or changed.
// *Action: remove the partitioning clause from the statement.
/
32407, 00000, "cannot exclude new values when materialized view log includes new values"
// *Cause: The excluding new values specification for the existing
// materialized view log cannot be accepted when including new
// values is the current option.
// *Action: change excluding new values clause.
/
32408, 0000, "materialized view log on \"%s\".\"%s\" already has new values"
// *Cause: The materialized view log on the indicated table already has new values.
// *Action: No action required.
/
32409, 0000, "materialized view log on \"%s\".\"%s\" already excludes new values"
// *Cause: The materialized view log on the indicated table already excludes new values.
// *Action: No action required.
/
32410, 0000, "internal mv logging event"
// *Document: NO
// *Cause: N/A
// *Action: To be used only under supervision of Oracle development.
// *Comment: Not for general purpose use.
/
32411, 0000, "materialized view definition query exceeds the maximum length"
// *Cause: The materialized view definition query exceeds the 64K limit.
// *Action: Change the materialized view definition query so that it does not exceed
// the maximum length of 64K.
/
32412, 00000, "encrypted column \"%s\" not allowed in the materialized view log"
// *Cause: The materialized view log being created/altered is to capture an encrypted
// column of the base table.
// *Action: Do not capture the encrypted column.
/
32413, 00000, "allow concurrent refresh of materialized view and truncate"
// *Cause: This event is set to allow concurrent refresh of materialized view
// and truncate of base table; it prevents a deadlock situation.
// (bug 6710019)
// *Action: Set this event to allow concurrent refresh of materialized view
// and truncate of the base table.
/
32414, 00000, "materialized view logs are not compatible with each other for fast refresh"
// *Cause: An attempt was made to create a fast refreshable materialized view
// on tables which have commit SCN-based materialized view logs and
// tables which have timestamp-based materialized view logs.
// *Action: Use COMPLETE REFRESH or change underlying materailized view logs
// to make them compatible with each other for fast refresh.
/
32415, 0000, "fast refreshable remote materialized view on a detail table with commit SCN-based materialized view log is not supported"
// *Cause: The materialized view creation failed because fast refreshable
// remote materialized view on a detail table with commit SCN-based
// materialized view log was not supported.
// *Action: NONE.
/
32416, 0000, "one or more commit SCN-based materialized view logs are not in consistent state for fast refresh"
// *Cause: Dictionary table "SYS"."SNAP_XCMT$" is not in consistent state.
// *Action: No action required.
//
/
32417, 0000, "must use DROP MATERIALIZED VIEW LOG to drop \"%s\".\"%s\""
// *Cause: An attempt was made to drop materialized view log using a command
// other than DROP MATERIALIZED VIEW LOG.
// *Action: No action required.
//
/
32418, 0000, "COMMIT SCN keyword only appears in CREATE MATERIALIZED VIEW LOG statement"
// *Cause: An attempt was made to alter an existing materialized view log
// to have commit SCN.
// *Action: No action required.
//
/
32419, 0000, "on commit materialized view is not supported on detail tables with commit SCN-based materialized view logs"
// *Cause: An attempt was made to create an on commit materialized view on
// detail tables with commit SCN-based materialized view logs.
// *Action: No action required.
//
/
32420, 0000, "unsupported fast refreshable materialized view defined on detail tables which have commit SCN-based materialized view logs"
// *Cause: An attempt was made to create an unsupported fast refreshable materialized
// view on detail tables with commit SCN based materialized view logs.
// *Action: No action required.
//
/
32421, 0000, "commit SCN-based materialized view log is not supported on a table with LOB column(s)"
// *Cause: An attempt was made to create a commit SCN-based materialized
// view log on a table which has LOB column(s).
// *Action: No action required.
//
/
32422, 0000, "commit SCN-based materialized view log cannot be created on table \"%s\".\"%s\" when there exist direct load/PMOP log entries for the table"
// *Cause: An attempt was made to create a commit SCN-based materialized
// view log on a table which had direct load/PMOP log entries in
// sys.sumdelta$ and sys.sumpartlog$.
// *Action: Refresh the table's dependent materialized views before creating
// commit SCN-based materialized view log on the table.
//
/
32423, 0000, "commit SCN-based materialized view log cannot be dropped on table \"%s\".\"%s\" when there exist direct load/PMOP log entries for the table"
// *Cause: An attempt was made to drop a commit SCN-based materialized
// view log on a table which had direct load/PMOP log entries in
// sys.sumdelta$ and sys.sumpartlog$.
// *Action: Refresh the table's dependent materialized views before dropping
// commit SCN-based materialized view log on the table.
//
/
32424, 0000, "materialized view log on \"%s\".\"%s\" already has this purge option"
// *Cause: Materialized view log on the indicated table already has
// the purge option specified.
// *Action: Specify a different purge option or omit the purge option.
//
/
32425, 0000, "asynchronous and scheduled purge option is not allowed on commit SCN-based materialized view log"
// *Cause: An attempt was made to create or alter a commit SCN-based
// materialized log with asynchronous and scheduled purge option.
// *Action: Specify a different purge option or omit the purge option.
//
/
32426, 00000, "materialized view log on \"%s\".\"%s\" in DST upgrade"
// *Cause: The materialized view log was created or altered on a table
// that had a Daylight Saving Time upgrade in progress.
// *Action: Wait until DST upgrade finishes on the master table.
//
32427, 0000, "materialized view contains unsupported NLS transformation"
// *Cause: An attempt was made to create or alter materialized view
// under NLS settings which transformed the materialized view's
// defining query in ways not by supported by Oracle.
// *Action: Contact Oracle support or workaround problem by removing NLS
// settings or modifying the materialized view's defining query.
//
32428, 0000, "on-statement materialized join view error: %s"
// *Cause: An error related to on-statement materialized join view was
// received.
// *Action: Refer to the error message for more information.
//
/
32429, 0000, "commit SCN-based materialized view log cannot be created on AQ table"
// *Cause: An attempt was made to create a commit SCN-based materialized
// view log on an Oracle Database Advanced Queuing (AQ) table.
// *Action: Do not create a commit SCN-based materialized view log on AQ tables.
//
/
32430, 0000, "materialized view log cannot be created on read-only database"
// *Cause: An attempt was made to create a materialized view log on a read-only
// database.
// *Action: Do not create a materialized view log on a read-only database.
//
/
32431, 0000, "materialized view cannot be created on tables having inconsistent sharing"
// *Cause: An attempt was made to create a materialized view on tables having
// inconsistent sharing.
// *Action: Do not create a materialized view on tables having inconsistent
// sharing, or ensure that tables have consistent sharing.
//
/
// Error Numbers 32460 - 32479 are reserved for Private Temporary Tables
/
32460, 0000, "maximum number of private temporary tables per session exceeded"
// *Cause: An attempt was made to create a private temporary table that
// exceeded the maximum allowable private temporary tables per
// session.
// *Action: Drop some of the private temporary tables.
/
32461, 0000, "unable to complete creation of in-memory private temporary table"
// *Cause: An attempt was made to create an in-memory private temporary table that
// was no longer in the shared pool.
// *Action: Reduce the activities that use shared pool space, then retry
// creating the in-memory private temporary table.
/
32462, 0000, "cannot use an object modified in current transaction"
// *Cause: An object modified in the current transaction was found during the creation of
// in-memory private temporary table using CREATE TABLE AS SELECT (CTAS).
// *Action: Split the CTAS statement into CREATE TABLE followed by INSERT SELECT.
/
32463, 0000, "cannot create an object with a name matching private temporary table prefix"
// *Cause: An attempt was made to create an object with a name matching
// private temporary table prefix (either ORA$PTT_ or value in parameter,
// private_temp_table_prefix).
// *Action: Choose a different name.
/
32464, 0000, "private temporay table feature is disabled"
// *Cause: An attempt was made to create a private temporary table but the feature
// was disabled.
// *Action: Enable the feature by setting the parameter, private_temp_table_prefix,
// to a unqiue value starting with ORA$.
/
32465, 0000, "value specified for the parameter is incorrect"
// *Cause: An attempt was made to modify the PRIVATE_TEMP_TABLE_PREFIX parameter
// to a value that does not comply as specified in the documentation.
// *Action: The prefix value should be of the form ORA$<3uniqueCharacters>.
/
// Error Numbers 32480 - 32498 are reserved for WITH clause errors
/
32480, 00000, "SEARCH and CYCLE clauses can only be specified for recursive WITH clause elements"
// *Cause: A SEARCH or a CYCLE clause was specified for a WITH clause element
// that was not recursive.
// *Action: Remove the SEARCH or CYCLE clause, or add recursion to the WITH
// clause element.
/
32481, 00000, "cycle value for CYCLE clause must be different from the non-cycle value"
// *Cause: A CYCLE clause was specified for a recursive WITH query but the
// cycle value was the same as the non-cycle or DEFAULT value.
// *Action: Change either the cycle or the non-cycle values so that they no
// longer match.
/
32482, 00000, "sequence column for SEARCH clause must be different from the cycle mark column for CYCLE clause"
// *Cause: A SEARCH clause and a CYCLE clause was specified for a recursive
// WITH query, but the sequence column of the SEARCH clause matched
// the cycle mark column of the CYCLE clause.
// *Action: Change either the sequence column or the cycle mark column so that
// they no longer match.
/
32483, 00000, "duplicate name found in sort specification list for SEARCH clause of WITH clause"
// *Cause: A SEARCH clause was specified for a recursive query with a sort
// specification list which contained duplicate names.
// *Action: Remove the duplicate names from the sort specification list of
// the SEARCH clause.
/
32484, 00000, "duplicate name found in cycle column list for CYCLE clause of WITH clause"
// *Cause: A CYCLE clause was specified for a recursive query with a cycle
// column list which contained duplicate names.
// *Action: Remove the duplicate names from the cycle column list of
// the CYCLE clause.
/
32485, 00000, "element in cycle column list of CYCLE clause must appear in the column alias list of the WITH clause element"
// *Cause: An element in the cycle column list of a CYCLE clause that was
// specified for a recursive WITH query did not appear in the column
// alias list of the WITH clause element.
// *Action: Change the cycle column list to use only names which are listed
// in the column alias list of the WITH clause element.
/
32486, 00000, "unsupported operation in recursive branch of recursive WITH clause "
// *Cause: The recursive component of the UNION ALL in a recursive WITH clause
// element used an operation that was currently not supported. The
// following should not be used in the recursive branch of the
// UNION ALL operation: GROUP BY, DISTINCT, MODEL, grouping sets,
// CONNECT BY, window functions, HAVING, aggregate functions.
// *Action: Rewrite the query without the unsupported operation.
/
32487, 00000, "unsupported join in recursive WITH query"
// *Cause: The recursive component of a recursive WITH clause element
// contained one of the following:
// - A LEFT OUTER join where the right side was the recursive query name.
// - A RIGHT OUTER join where the left side was the recursive query name.
// - A FULL OUTER join involving the recursive query name.
// *Action: Rewrite the query without the unsupported join operation.
/
32488, 00000, "WITH clause element did not have a column alias list"
// *Cause: A WITH clause element used the SEARCH clause or CYCLE clause or both
// but did not have a column alias list specified for it.
// *Action: Add a column alias list for the WITH clause query name.
/
32489, 00000, "element in sort specification list of SEARCH clause did not appear in the column alias list of the WITH clause element"
// *Cause: An element in the sort specification list of a SEARCH clause that
// was specified for a recursive WITH query did not appear in the
// column alias list of the WITH clause element.
// *Action: Change the sort specification list to use only names which are
// listed in the column alias list of the WITH clause element.
/
32490, 00000, "recursive query name referenced more than once in recursive branch of recursive WITH clause element"
// *Cause: The recursive component of the UNION ALL in a recursive WITH clause
// element referenced the recursive query name more than once. Only
// one reference to the recursive query name is allowed in the
// recursive branch of a recursive WITH clause element.
// *Action: Rewrite the query using only one reference to the recursive query
// name in the recursive branch of the recursive WITH clause element.
/
32499, 00000, "operation not supported with old CONNECT BY clause"
// *Cause: The query used the old CONNECT BY clause on operations that are not supported.
// *Action: Disable the old CONNECT BY clause by disabling the _old_connect_by_enabled parameter.
/
//////////////////////////// DIAGNOSIBILITY
/ Error numbers 32500 to 32549 are reserved for diagnosibility
////////////////////////////
32500, 00000, "Dirname '%s' cannot exceed '%s' characters"
// *Cause: Path name too long
// *Action: Use shorter pathname than maximum specified for dirname.
/
32501, 00000, "Writing SGA to file failed"
// *Cause: Underlying OSDs encountered an error
// *Action: Check additional information. slercerrno contains errno.
/
32502, 00000, "Cannot execute command. Flash Freeze is not in effect"
// *Cause: This command can only be issued after a flash freeze
// *Action: Refer to instructions for flash freeze and Oracle diagnostics.
/
32503, 00000, "Mapping SGA from file failed"
// *Cause: Underlying OSDs encountered an error
// *Action: Check additional information. slercerrno contains errno.
/
32504, 00000, "expecting one of %s, %s, %s, or %s but found %s"
// *Cause: illegal value specified for create watchpoint mode
// *Action: specify one of the expected modes
/
32505, 00000, "too many watchpoints"
// *Cause: too many watchpoints created
// *Action: increase appropriate initialization parameters
/
32506, 00000, "expecting one of %s, %s, or %s but found %s"
// *Cause: invalid arguments provided
// *Action: provide one of the expected arguments
/
32507, 00000, "expecting %s but found %s"
// *Cause: invalid arguments to command
// *Action: provide one of the expected arguments
/
32508, 00000, "no such watchpoint id"
// *Cause: invalid watchpoint id
// *Action: use oradebug show to list valid watchpoint ids
/
32509, 00000, "watchpoint was already deleted"
// *Cause: trying to delete an already deleted watchpoint
// *Action: use oradebug show to list valid watchpoint ids
/
32510, 00000, "cannot create watchpoint on unreadable memory"
// *Cause: trying to create watchpoint on invalid address
// *Action: provide a different valid address
/
32511, 00000, "cannot create watchpoint in memory needed by watchpointing code"
// *Cause: overlap exists between requested memory range to watch
// and internal memory structures that watchpointing operations need
// *Action: provide a different address range
/
32512, 00000, "type '%s' is unknown"
// *Cause: trying to dump an invalid type name
// *Action: specify a known type
/
32514, 00000, "cannot dump multiple '%s' types: structure size is unknown"
// *Cause: trying to dump an invalid address
// *Action: provide a different valid address
/
32515, 00000, "cannot issue ORADEBUG command '%s' to process '%s'; prior command execution time exceeds %s ms"
// *Cause: The process targeted to execute the ORADEBUG command was
// busy executing another ORADEBUG command for a time greater
// than the timeout value specified.
// *Action: Increase the timeout value.
/
32516, 00000, "cannot wait for process '%s' to finish executing ORADEBUG command '%s'; wait time exceeds %s ms"
// *Cause: The execution of the ORADEBUG command took longer than the
// the timeout value specified.
// *Action: Increase the timeout value.
/
32517, 00000, "cannot issue ORADEBUG command '%s' to process '%s' (prior command execution time exceeds %s ms); total wait time exceeds %s ms"
// *Cause: The process targeted to execute the ORADEBUG command was
// busy executing another ORADEBUG command. But, because
// the total wait time for all targeted processes
// exceeded the maximum wait time, the ORADEBUG command was
// not issued to the target process.
// *Action: Increase the timeout value.
/
32518, 00000, "cannot wait for process '%s' to finish executing ORADEBUG command '%s' (waited %s ms); total wait time exceeds %s ms"
// *Cause: The total wait time for all targeted processes exceeded the
// maximum wait time, therefore the wait for the targeted process
// to finish executing the ORADEBUG command was aborted.
// *Action: Increase the timeout value.
/
32519, 00000, "insufficient privileges to execute ORADEBUG command: %s"
// *Cause: Sufficient privileges were not granted.
// *Action: Perform the operation using a database session that
// has the required privileges. See the Oracle ORADEBUG
// documentation for more details.
/
32520, 00000, "error authenticating credentials"
// *Cause: An error was encountered while authenticating credentials.
// *Action: Check the other error messages for additional information or
// contact Oracle Support Services.
/
32521, 00000, "error parsing ORADEBUG command: %s"
// *Cause: An invalid ORADEBUG command was specified.
// *Action: Specify the correct ORADEBUG command and arguments.
/
32522, 00000, "restricted heap violation while executing ORADEBUG command: [%s] [%s] [%s]"
// *Cause: An invalid memory heap was used in an ORADEBUG command.
// *Action: Try executing the ORADEBUG command in the current process or
// contact Oracle Support Services.
/
32523, 00000, "watchpoint cannot be created in dynamic processes"
// *Cause: An attempt was made to create a watchpoint in a process involving threads.
// *Action: Check the process mode or try creating watchpoints only in the static non-threaded processes.
/
//////////////////////////// LITERAL REPLACEMENT
/ Error numbers 32550 to 32574 are reserved for literal replacement
////////////////////////////
32550, 00000, "Replacement occured despite hint to the contrary"
// *Cause: This should never be signalled; it's internal.
// *Action: Report to Oracle support.
/
//////////////////////////// PARSER
/ Error numbers 32575 to 32599 are reserved for additional parsing errors
////////////////////////////
32575, 00000, "Explicit column default is not supported for modifying views"
// *Cause: Default keyword was used to modify views.
// *Action: Use implicit default - omitting column-value pair.
/
32576, 00000, "missing TYPE keyword"
// *Cause: keyword TYPE is missing.
// *Action: Use TYPE keyword.
/
32577, 00000, "username must be SYS or SYSTEM"
// *Cause: A user name of SYS or SYSTEM was not specified when providing
// a password in the CREATE DATABASE statement.
// *Action: Only passwords for the SYS and SYSTEM users can be provided
// in the CREATE DATABASE statement. Re-issue the statement with
// passwords for users SYS or SYSTEM.
/
32578, 00000, "password for SYS already specified"
// *Cause: A password for the SYS user was specified twice in the
// CREATE DATABASE statement.
// *Action: Re-issue the CREATE DATABASE statement with only one password
// for the SYS user.
/
32579, 00000, "password for SYSTEM already specified"
// *Cause: A password for the SYSTEM user was specified twice in the
// CREATE DATABASE statement.
// *Action: Re-issue the CREATE DATABASE statement with only one password
// for the SYSTEM user.
/
32580, 00000, "both SYS and SYSTEM passwords must be provided"
// *Cause: Passwords for both the SYS and SYSTEM users were not
// provided in the CREATE DATABASE statement. If one of the
// passwords was provided, then both should be provided.
// *Action: Re-issue the CREATE DATABASE statement with a password for
// both the SYS and SYSTEM users.
/
32581, 00000, "missing or invalid password"
// *Cause: An incorrect password was provided for the SYS or
// SYSTEM user in the CREATE DATABASE statement.
// *Action: Re-issue the CREATE DATABASE statement with a valid password.
/
32582, 00000, "table function with left correlation to a table cannot also be left outer-joined to the table"
// *Cause: A table function T2 contains a reference to a table T1. T2
// is also left outer-joined to T1. This is not allowed.
// *Action: Remove the reference to T1 from T2 or remove the left outer-join
// specification (+).
/
32583, 00000, "query passed to table function has wrong number of elements in select list"
// *Cause: The query used as an input to a table function which takes a
// a ref cursor as argument has wrong number of elements in the select
// list which does not correspond to the elements in ref cursor.
// The ref cursor mentioned here refers to the one referenced in
// order by parition clauses. This is not allowed.
// *Action: Make sure that the select list of the query matches the ref cursor
// columns as defined in the function.
/
32584, 00000, "missing LOG keyword"
// *Cause: keyword LOG is missing.
// *Action: Use LOG keyword.
/
32585, 00000, "duplicate specification of a supplemental log attribute"
// *Cause: In a create/alter DDL a supplemental log attribute is specified
// more than once.
// *Action: Rewrite the Create/Alter DDL such that it has a
// single occurence of any supplemental log attribute.
/
32586, 00000, "multiple specification of a supplemental logging attribute"
// *Cause: The primary key, unique index, foreign key or all
// column supplemental logging attribute can be specified at most
// once in a create/alter ddl.
// *Action: Rewrite the Create/Alter DDL with single occurence of
// the offending supplemental logging attribute.
/
32587, 00000, "Cannot drop nonexistent %s supplemental logging"
// *Cause: specified supplemental log attribute does not exist.
// *Action: None
//
/
32588, 00000, "supplemental logging attribute %s exists"
// *Cause: specified supplemental logging attribute exits.
// *Action: retry the alter/create ddl after removing this
// supplemental logging attribute.
//
/
32589, 00000, "unable to drop minimal supplemental logging"
// *Cause: Minimal supplemental logging could not be dropped as
// one of primary key, foreign key, unique or all column
// supplemental logging is enabled at the database level.
// *Action: Use V$DATABASE to determine the databasewide supplemental
// logging directives. Minimal supplemental logging could
// be dropped if and only if no other databasewide supplemental
// logging directives are enabled.
/
32590, 00000, "log group specification not allowed here"
// *Cause: Supplemental log specification is not allowed in the
// statement.
// *Action: Remove the supplemental log specification from the
// statement.
/
32591, 00000, "connect string too long"
// *Cause: The connect string specified for the database link was more than
// 2000 characters.
// *Action: Specify a connect string less than 2000 chracters.
/
32592, 00000, "all columns in log group can not be no log columns"
// *Cause: A supplemental log group must have at least one column of scalar
// type that is not marked as no log.
// *Action: Redefine the supplemental log group with at least one column of
// scalar type that is not marked as no log.
/
32593, 00000, "database supplemental logging attributes in flux "
// *Cause: there is another process actively modifying the database wide
// supplemental logging attributes.
// *Action: Retry the DDL or the LogMiner dictionary build that raised this
// error.
/
32594, 00000, "invalid object category for COMMENT command"
// *Cause: The object category specified is not a valid object for which to
// use the COMMENT command.
// *Action: Retry the COMMENT command by specifying an accepted object
// category. (ie, Table, Operator, Indextype, etc.)
/
32595, 00000, "DDL statement cannot be audited with BY SESSION specified"
// *Cause: An attempt was made to audit a DDL statement with BY SESSION
// clause specified. DDL statements can be audited BY ACCESS only.
// *Action: Specify BY ACCESS instead of BY SESSION to audit the DDL
// statement.
/
32596, 00000, "duplicate ALTER USER or CREATE USER option"
// *Cause: An ALTER USER option was duplicated.
// *Action: Remove the duplicate option.
/
32597, 00000, "database supplemental logging attributes inconsistent"
// *Cause: failed to propogate supplemental logging attributes to all
// RAC instances. Most likely caused by an instance leaving
// the RAC while this DDL was in progress.
// *Action: Retry the DDL or the LogMiner dictionary build that raised
// this error.
/
32598, 00000, "user names cannot be changed in ALTER DATABASE LINK command"
// *Cause: An attempt was made to change the fixed user name of the
// database link.
// *Action: None.
/
32599, 00000, "cannot create a view in SYS schema with V$ or GV$ name prefix"
// *Cause: An attempt was made to create a view in SYS schema with
// V$ or GV$ name prefix, which is reserved for fixed views.
// *Action: Provide a different name for the view or use a different schema.
/
//////////////////////////// LOB RETENTION and FLASHBACK
/ Error numbers 32600 to 32605 are reserved for lob retention
////////////////////////////
32600, 00000, "RETENTION and PCTVERSION cannot be used together"
// *Cause: cannot use both RETENTION and PCTVERSION together.
// *Action: Use either RETENTION or PCTVERSION.
/
32601, 00000, "value for retention cannot be provided"
// *Cause: cannot give a value for Retention Period.
// *Action: do not provide the value for parameter.
/
32602, 00000, "FREEPOOLS and FREELIST GROUPS cannot be used together"
// *Cause: cannot use both FREEPOOLS and FREELIST GROUPS together.
// *Action: Use either FREEPOOLS or FREELIST GROUPS.
/
32603, 00000, "invalid FREEPOOLS LOB storage option value"
// *Cause: The specified FREEPOOLS LOB storage option value must be an
// integer.
// *Action: Choose an appropriate integer value and retry the operation.
/
32604, 00000, "invalid REBUILD option"
// *Cause: Keyword FREEPOOLS expected after the REBUILD keyword.
// *Action: User must specify FREEPOOLS keyword.
/
32605, 00000, "invalid REBUILD option"
// *Cause: cannot rebuild freepools while creating table with lob column.
// *Action: User must not specify REBUILD... in this context.
/
//////////////////////////// MODEL
/ Error numbers 32606 to 32689 are reserved for MODEL
////////////////////////////
32606, 00000, "missing NAV keyword in MODEL clause"
// *Cause: The NAV keyword was not specified where it was expected.
// *Action: Specify the NAV keyword or check the SQL statement.
/
32607, 00000, "invalid ITERATE value in MODEL clause"
// *Cause: The specified ITERATE value must be a 4 byte positive integer.
// *Action: Choose an appropriate value and retry the operation.
/
32608, 00000, "missing INCREMENT or DECREMENT keyword in FOR loop"
// *Cause: INCREMENT or DECREMENT keyword was not specifiedi where it is expected.
// *Action: Specify the INCREMENT or DECREMENT keyword or check the SQL statement.
/
32609, 00000, "missing REFERENCE keyword in MODEL clause"
// *Cause: The REFERENCE keyword was not specified where it is expected.
// *Action: Specify the REFERENCE keyword or check the SQL statement.
/
32610, 00000, "missing SINGLE REFERENCE or DIMENSION keyword in MODEL clause"
// *Cause: SINGLE REFERENCE or DIMENSION keyword was not specified where it is
// expected.
// *Action: Specify the applicable keywords or check the SQL statement.
/
32611, 00000, "incorrect use of MODEL CV operator"
// *Cause: CV function was used outside a dimension expression, in UNTIL
// condition, or with non-dimensional arguments.
// *Action: Check the SQL statement and rewrite if necessary.
/
32612, 00000, "invalid use of FOR loop"
// *Cause: The MODEL FOR loop was used where it is not allowed.
// FOR loops are not allowed in complex dimensional predicates,
// on the right hand side of rules, or in the until condition.
// *Action: Check the SQL statement and rewrite if necessary.
/
32613, 00000, "not a MODEL cell"
// *Cause: The operator requires a MODEL cell as operand.
// *Action: Specify MODEL cell as operand, check SQL statement.
/
32614, 00000, "illegal MODEL SELECT expression"
// *Cause: An expression other than MODEL aliases, constants,
// or expressions of the two is specified in the
// MODEL SELECT clause.
// *Action: Reformulate the query, perhaps nesting inside another SELECT.
/
32615, 00000, "incorrect use of MODEL IS ANY predicate"
// *Cause: IS ANY predicate is used outside dimension expression or with
// non-dimensional or different dimensional arguments.
// *Action: Check the SQL statement and rewrite if necessary.
/
32616, 00000, "missing DIMENSION BY keyword in MODEL clause"
// *Cause: The DIMENSION keyword was not pecified where it is expected.
// *Action: Specify the DIMENSION keyword or check the SQL statement.
/
32617, 00000, "missing MEASURES keyword in MODEL clause"
// *Cause: The MEASURES keyword was not specified where it is expected.
// *Action: Specify the MEASURES keyword or check the SQL statement.
/
32618, 00000, "incorrect use of MODEL PREVIOUS function"
// *Cause: The MODEL PREVIOUS function was used outside of MODEL
// "ITERATE UNTIL" clause, or was nested.
// *Action: Check the SQL statement and rewrite if necessary.
/
32619, 00000, "incorrect use of MODEL ITERATION_NUMBER"
// *Cause: ITERATION_NUMBER was used outside of an iterated MODEL.
// *Action: Check the SQL statement and rewrite if necessary.
/
32620, 00000, "illegal subquery within MODEL rules"
// *Cause: A subquery was used illegally within the MODEL rule.
// *Action: Check the SQL statement and rewrite if necessary.
/
32621, 00000, "illegal aggregation in UNTIL iteration condition"
// *Cause: An aggregate function was used in UNTIL condition.
// *Action: Check the SQL statement and rewrite if necessary.
/
32622, 00000, "illegal multi-cell reference"
// *Cause: Multi-cell reference was specified on a measure expression
// without an aggregate function.
// *Action: Use an aggregate function on the measure expression or
// qualify the cell reference.
/
32623, 00000, "incorrect use of MODEL PRESENT* functions"
// *Cause: A PRESENT* function (IS PRESENT, PRESENTV, PRESENTNNV)
// was used in a measure expression.
// *Action: Check the SQL statement and rewrite if necessary.
/
32624, 00000, "illegal reordering of MODEL dimensions"
// *Cause: The expressions to qualify dimensions were specified
// in an incorrect order within a cell reference.
// *Action: Reorder dimension expressions in the cell reference.
/
32625, 00000, "illegal dimension in cell reference predicate"
// *Cause: A non-positional dimension was referenced in the predicate.
// *Action: Check the SQL statement and rewrite if necessary.
/
32626, 00000, "illegal bounds or increment in MODEL FOR loop"
// *Cause: FOR loop allows only numeric and datetime without timezone type
// for bounds. Only constants of interval and numeric types are
// allowed as increment/decrement expressions.
// *Action: Check the SQL statement and rewrite if necessary.
/
32627, 00000, "illegal pattern in MODEL FOR LIKE loop"
// *Cause: The FOR LIKE pattern had zero or more than one wild characters.
// *Action: Simplify the pattern to have a single wildcard character.
/
32628, 00000, "invalid nesting of MODEL cell reference"
// *Cause: MODEL cell reference was nested too deeply.
// *Action: Avoid deep nesting of cell references and rewrite if necessary.
/
32629, 00000, "measure used for referencing cannot be updated"
// *Cause: A measure used in nested referencing is updated by a MODEL
// rule in the automatic order MODEL.
// *Action: Modify the SQL statement or use sequential order MODEL.
/
32630, 00000, "multiple assignment in automatic order MODEL"
// *Cause: A MODEL cell was updated on the same measure in
// multiple MODEL rules. Multiple assignment is not allowed
// in automatic order MODELs as it causes in ambiguity
// and nondeterminism.
// *Action: Use sequential order MODEL or rewrite the rule to avoid this.
/
32631, 00000, "illegal use of objects in MODEL"
// *Cause: An object column was used as a MODEL column. Object types are
// not allowed as partition by, dimension by or measure expressions.
// *Action: Check the SQL statement and rewrite if necessary.
/
32632, 00000, "incorrect subquery in MODEL FOR cell index"
// *Cause: An illegal subquery was specified in MODEL FOR cell index.
// A subquery used in a MODEL FOR cell index can not have
// subqueries, correlation, binds and references to WITH tables.
// *Action: Check the SQL statement and rewrite if necessary.
/
32633, 00000, "MODEL subquery FOR cell index returns too many rows"
// *Cause: Subquery in MODEL FOR cell index returned more than
// the allowed maximum.
// *Action: Split the rule into multiple ones.
/
32634, 00000, "automatic order MODEL evaluation does not converge"
// *Cause: Evaluation using automatic rule ordering did not reach
// a convergence point.
// *Action: Modify the rules or use sequential order instead.
/
32635, 00000, "not a single cell reference predicate"
// *Cause: A predicate that is not a single cell reference predicate was specified
// where a single cell reference predicate was expected.
// A single cell reference predicate is either a constant expression
// or a predicate of the form <dimension_key = constant_expr>
// *Action: Make sure that the predicate is a proper single cell
// reference. In some cases, you might have to put explicit
// type conversion operators (or casts) on the constant expression.
/
32636, 00000, "Too many rules in MODEL"
// *Cause: The number of rules (possibly after rule unfolding) exceeded
// the maximum number of rules allowed.
// *Action: Reduce the number of rules.
/
32637, 00000, "Self cyclic rule in sequential order MODEL"
// *Cause: A self-cyclic rule was detected in the sequential order MODEL.
// Sequential order MODELs cannot have self cyclic rules
// to guarantee that the results do not depend on the order
// of evaluation of the cells that are updated or upserted.
// *Action: Use ordered rule evaluation for this rule.
/
32638, 00000, "Non unique addressing in MODEL dimensions"
// *Cause: The address space defined for the MODEL (partition by and dimension by
// expressions) do not uniquely identify each cell.
// *Action: Rewrite the MODEL clause. Using UNIQUE SINGLE REFERENCE
// option might help.
/
32639, 00000, "Aggregate functions on reference MODELs are not allowed"
// *Cause: An aggregate function was specified on the cells of a reference
// MODEL.
// *Action: Check the SQL statement and rewrite if necessary.
/
32640, 00000, "FOR LIKE loops are not allowed for multi-byte character types"
// *Cause: FOR LIKE loops was specified for a multi-byte character type.
// *Action: Check the SQL statement and rewrite if necessary.
/
32641, 00000, "invalid expression in MODEL rule ORDER BY clause"
// *Cause: An invalid expression was specified in the MODEL rule ORDER BY clause
// where only expressions of dimension and measure columns and
// reference MODEL cell references are allowed
// *Action: Modify the order by clause in the MODEL rule.
/
32642, 00000, "non-unique cell values from the ORDER BY clause"
// *Cause: The MODEL rule ORDER BY clause did not generate unique values for all
// cells that satisfy the predicates in the left side of the rule.
// *Action: Modify the rule ORDER BY clause in the MODEL rule.
/
32643, 00000, "invalid use of window function in MODEL rule"
// *Cause: The window functions can not be used in SQL Model rules
// that have FOR-loops on the left side or aggregates
// on the right side.
// *Action: Modify the MODEL rule.
/
32644, 00000, "this function is not allowed outside of MODEL clause"
// *Cause: A function allowed only within the MODEL clause is used
// outside of MODEL clause.
// *Action: Rewrite the SQL statement.
/
32689, 00000, "MODEL: event to turn on/off some optimizations"
// *Document: NO
// *Cause: N/A
// *Action: Turns on/off some optimizations in MODEL evaluation.
/
//////////////////////////// Hash Table Infrastructure (HTI)
/ Error numbers 32690 to 32699 are reserved for hash table infrastructure
////////////////////////////
/
32690, 00000, "Hash Table Infrastructure ran out of memory"
// *Cause: Not enough memory.
// *Action: Increase memory.
/
32691, 00000, "Internal event for Adaptive Group-By"
// *Document: NO
// *Cause: N/A
// *Action: Indicates the cache size multiple for in-memory and
// cache-friendly aggregation.
// *Comment: Not for general purpose use.
/
32692, 00000, "Internal event for Adaptive Group-By"
// *Document: NO
// *Cause: N/A
// *Action: Indicates number of batches to try HBF strategy.
// *Comment: Not for general purpose use.
/
32695, 00000, "HTI: Not enough memory"
// *Cause: Memory is not enough.
// *Action: Increase memory.
/
32696, 00000, "HTI: No free slot"
// *Cause: There is not enough memory.
// *Action: Increase memory.
/
32697, 00000, "HTI: max agg size"
// *Document: NO
// *Cause: N/A
// *Action: Sets max nda size
/
32698, 00000, "Overshoot in index scan prefetch"
// *Document: NO
// *Cause: N/A
// *Action:
/
32699, 00000, "HTI: event to dump statistics"
// *Document: NO
// *Cause: N/A
// *Action: Dumps hash infrastructure statistics
/
////////////////////////////// RAC DIAGNOSABILITY FRAMEWORK
// Error numbers 32700 to 32729 are reserved for RAC DIAG process
//////////////////////////////
32700, 00000, "error occurred in DIAG Group Service"
// *Cause: An unexpected error occurred while performing a DIAG Group Service
// operation.
// *Action: Verify that the DIAG process is still active. Also, check the
// Oracle DIAG trace files for errors.
/
32701, 00000, "Possible hangs up to hang ID=%s detected"
// *Cause: Hang Manager detected one or more hangs. These could be valid
// hangs that require action or the system could be overloaded causing
// very slow progress which can be interpreted as hangs. If hang
// resolution is enabled, Hang Manager may attempt to resolve
// the hang by terminating the ultimate blocker.
// *Action: Check the incident logs associated with this message for
// diagnostic information.
/
32702, 00000, "Rolling migration is going on"
// *Cause: DIAG detected rolling migration in IPC.
// *Action: No action needed. DIAG is shutting down for rolling migration.
// This error number is solely used for internal purposes.
/
32703, 00000, "deadlock detected: %s"
// *Cause: Oracle sessions waiting for resources were deadlocked.
// *Action: Reissue any commands that failed and contact Oracle Support
// Services with the incident information.
/
32704, 00000, "Oracle RAC deadlock detected: %s"
// *Cause: Oracle sessions or processes using Global Enqueue Service
// were deadlocked waiting for resources.
// *Action: Reissue any commands that failed and contact Oracle Support
// Services with the incident information.
/
32705, 00000, "Oracle RAC deadlock search terminated due to an exception"
// *Document: NO
// *Cause: Global Enqueue Service deadlock search encountered an internal
// error.
// *Action: This exception is caught and recovered automatically.
/ Error numbers 32706-32716 reserved for DBMS_HANG_MANAGER package
/
32706, 00000, "invalid parameter name or value for Oracle Hang Manager"
// *Cause: An invalid parameter name or value was passed to the
// DBMS_HANG_MANAGER package when setting an Oracle Hang Manager
// parameter.
// *Action: Choose a documented parameter name and value.
/
32707, 00000, "internal error of Oracle Hang Manager parameter management"
// *Cause: An internal error was encountered while processing the Oracle Hang
// Manager parameter management request.
// *Action: Check the alert log file for error details.
/
32708, 00000, "DBMS_HANG_MANAGER package not supported for this instance type"
// *Cause: Oracle Hang Manager parameter management was not supported for this
// instance type.
// *Action: No action required.
/
////////////////////////////// RAC DIAG-based parallel oradebug
// Error numbers 32730 to 32760 are reserved for DIAG-based parallel oradebug
//////////////////////////////
32730, 00000, "Command cannot be executed on remote instance"
// *Cause: DIAG is not registered with DIAG Group Service
// *Action: Issue the command without the cluster database syntax
/
32731, 00000, "Another Parallel Oradebug session is in progress"
// *Cause: Another session for Parallel Oradebug is in progress
// with the database
// *Action: Issue the command later when the current session finishes
/
32732, 00000, "Parallel Oradebug session is aborted"
// *Cause: Group reconfiguration is occurring among DIAGs
// *Action: Issue the command later when group reconfiguration completes
/
32733, 00000, "Error occurred when executing Parallel Oradebug"
// *Cause: Error is encountered during executing command at local node
// *Action: Check alert log and DIAG trace file for error detail
/
32734, 00000, "Error occurred when sending Oradebug command to remote DIAGs"
// *Cause: IPC communication problem encountered
// *Action: Check IPC communication between DIAGs and issue the command again
/ at a later time
32735, 00000, "DIAG process is not running in the instance"
// *Cause: DIAG process is not alive
// *Action: Check error in DIAG trace file and issue the command again
// when DIAG is restarted
/
32736, 00000, "Hang analysis aborted due to wrong message type"
// *Cause: DIAG received wrong message.
// *Action: Check DIAG trace files for errors.
/
32737, 00000, "Hang analysis aborted due to failed memory allocation"
// *Cause: DIAG couldn't allocate buffer for remote copy.
// *Action: Check DIAG trace files for errors.
/
32738, 00000, "Hang analysis aborted due to failed memory copy"
// *Cause: DIAG couldn't copy buffer to remote node.
// *Action: Check DIAG trace files for errors.
/
32739, 00000, "Hang analysis aborted due to failed heap re-grow"
// *Cause: DIAG couldn't re-grow the heap for wait-for-graphs.
// *Action: Check DIAG trace files for errors.
/
32740, 00000, "The requested operation cannot be proceeded"
// *Cause: Operation was aborted because instance termination was in progress.
// *Action: Retry later after restarting the instance.
/
32741, 00000, "Hang analysis already going on"
// *Cause: Hang analysis was already in process globally or for the instance.
// *Action: Wait for the current operation to complete and re-run the command.
/
32742, 00000, "Hang analysis initialize failed"
// *Cause: Hang analyzer was not able to allocate memory to initialize.
// *Action: Check the trace files.
/
32743, 00000, "command cannot be executed on remote instance"
// *Cause: The database was not mounted in SHARED mode.
// *Action: Mount the database in SHARED mode.
/
////////////////////////////// Temp LOB Ref Count
// Error numbers 32761 to 32765 are reserved for Temp LOB Ref Count tracing
//////////////////////////////
32761, 00000, "Turn off Temp LOB Ref Count Feature "
// *Cause: None
// *Action: Turn off the whole temp lob ref count feature
32762, 00000, "Turn on Temp LOB Ref Count Tracing "
// *Cause: None
// *Action: Check Trace file for debug info
32763, 00000, "Turn off N-Pass Temp LOB cleanup "
// *Cause: None
// *Action: Facilitate debugging and testing
////////////////////////////// SQL function on LOBs
// Error numbers 32766 to 32770 are reserved for SQL function on LOBs
//////////////////////////////
32766, 00000, "instr with negative offset: use varchar semantics on LOBs"
// *Cause: The current varchar behavior is different.
// e.g. instr('abcd', 'cd', -2, 1) returns 3, whereas
// instr(to_clob('abcd'), 'cd', -2, 1) returns 0, (i.e. no match),
// because the reverse search starts from offset -2, which points
// to 'c' and moving backward, i.e. 'd' is ignored.
// This is symmetric to instr('dcba','dc',2,1), which returns 0.
// *Action: ORACLE uses the same varchar semantics on LOBs (instr).
// Using the same example, instr(to_clob('abcd'), 'cd', -2, 1)
// will return 3 as in the varchar case.
/
/
32767, 00000, "No server connection for this operation"
// *Cause: The client side sql or plsql function operation requires
// a connection to the server, but currently no client/server
// connection existed.
//
// *Action: Establish a client/server connection.
/
/
////////////////////////////// BIGFILE TABLESPACE
// Error numbers 32771 to 32779 are reserved for Bigfile Tablespace
//////////////////////////////
32771, 00000, "cannot add file to bigfile tablespace"
// *Cause: An attempt was made to add the second file to a bigfile
// tablespace.
// *Action: Do not use this command with bigfile tablespace.
32772, 00000, "BIGFILE is invalid option for this type of tablespace"
// *Cause: An attempt was made to create a bigfile tablespace that is
// dictionary managed or locally managed with manual
// segment-space management.
// *Action: Either change the tablespace type to locally managed with
// automatic segment-space management, or create a SMALLFILE
// tablespace instead.
32773, 00000, "operation not supported for smallfile tablespace %s"
// *Cause: An attempt was made to perform an operation which is supported
// only for bigfile tablespaces, e.g. resize tablespace.
// *Action: Use the appropriate clause of the ALTER DATABASE DATAFILE
// command instead.
32774, 00000, "more than one file was specified for bigfile tablespace %s"
// *Cause: More than one datafile or tempfile was specified in CREATE
// TABLESPACE command for a bigfile tablespace.
// *Action: Change command to contain only one file or create a smallfile
// tablespace instead.
32775, 00000, "cannot change size attributes of read only tablespace %s"
// *Cause: An attempt was made to change size attributes of a tablespace
// that is read only.
// *Action: Change the tablespace to read/write and retry the operation.
32776, 00000, "Local temporary tablespaces are not allowed in a tablespace group."
// *Cause: An attempt was made to create or alter a tablespace group to contain
// a tablespace that is a local temporary tablespace.
// *Action: Use a tablespace that is not a local temporary tablespace or do not
// include this tablespace in a group.
32777, 00000, "DDL operations are disabled on local temporary tablespaces FOR RIM."
// *Cause: A DDL operation on a local temporary tablespace FOR RIM was
// attempted in a system without any read-only running instances.
// *Action: Add at least one read-only instance to the cluster.
32778, 00000, "DDL operations are disabled on local temporary tablespaces FOR LEAF."
// *Cause: A DDL operation on a local temporary tablespace FOR LEAF was
// attempted in a system without any read-only running instances.
// *Action: Add at least one read-only instance to the cluster.
/
// //////////////////////////
// 32780 - 32788 reserved for window function events
// //////////////////////////
/
32780, 00000, "Analytical Functions: event to turn on or off optimizations"
// *Document: NO
// *Cause: N/A
// *Action: Turns on or off some optimizations in OLAP analytical
// function evaluation
// Level:
// 0x01 - turn off reporting aggregate optimization
// 0x02 - turn off nosort rank pushdown/stopkey optimization
// 0x04 - turn off range parallelism for cumulative window fns
// 0x08 - turn off new sort in window functions
// 0x10 - turn off ordering key minimization
//
32781, 00000, "Trace event for window functions"
// *Cause: N/A
// *Action: Set this event only under the supervision of Oracle development.
// Trace level is a bitfield.
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0x0001 trace window functions after ordering semantics rewrite
// 0x0002 trace statistics collected for window functions
// 0x0004 trace ordering groups generated for window functions
// 0x0008 trace dynamic sampling statistics expressions
// 0x0010 trace messages for slave-2-QC communication
// 0x0020 trace window consolidation rows
/
32789, 00000, "Event to control/dump optimized-for-read feature"
// *Document: NO
// *Cause: N/A
// *Action: Controls optimzied-for-read feature
// Level:
// 0x01 - forces optimzied-for-read plan generation even for
// tables that are optimized for read (no inmem access
/ structure built on the table)
// 0x02 - <unused>
// 0x04 - <unused>
// 0x08 - <unused>
// 0x10 - dumps trace information
/
// //////////////////////////
// Schema compiler error
// //////////////////////////
/
32790, 00000, "Element '%s' cannot share the default table '%s' with element '%s'"
// *Cause: An element in the restriction shared a default table with the
// corresponding element in it's supertype.
// *Action: Change the default table's name for the element in restriction.
/
/////////////////////////////////////////////////////////////////////////////
/ 32791 - 32799 are reserved for 12g SQL enhancements projects
/////////////////////////////////////////////////////////////////////////////
32791,0000, "prebuilt table managed column cannot have a default on null"
// *Cause: An attempt was made to create a materialized view on a
// prebuilt table that has a managed column with a default on null
// expression.
// *Action: Either remove the default on null property, or do not include
// the column in the materialized view definition.
/
32792,0000, "prebuilt table managed column cannot be an identity column"
// *Cause: An attempt was made to create a materialized view on a
// prebuilt table that has a managed column that is an identity
// column.
// *Action: Either remove the identity property, or do not include
// the column in the materialized view definition.
/
32793,0000, "cannot alter a system-generated sequence"
// *Cause: An attempt was made to alter a system-generated sequence.
// *Action: A system-generated sequence, such as one created for an
// identity column, cannot be altered.
/
32794,0000, "cannot drop a system-generated sequence"
// *Cause: An attempt was made to drop a system-generated sequence.
// *Action: A system-generated sequence, such as one created for an
// identity column, cannot be dropped.
/
32795,0000, "cannot insert into a generated always identity column"
// *Cause: An attempt was made to insert a value into an identity column
// created with GENERATED ALWAYS keywords.
// *Action: A generated always identity column cannot be directly inserted.
// Instead, the associated sequence generator must provide the value.
/
32796,0000, "cannot update a generated always identity column"
// *Cause: An attempt was made to update an identity column created with
// GENERATED ALWAYS keywords.
// *Action: A generated always identity column cannot be directly updated.
/
32797,0000, "identity column sequence mismatch in ALTER TABLE EXCHANGE PARTITION"
// *Cause: The two tables specified in the EXCHANGE have identity columns
// with sequences that are neither both increasing nor decreasing.
// *Action: Ensure that the identity columns have sequences with INCREMENT BY
// having the same sign.
/
32798,0000, "cannot use ANSI RIGHT or FULL outer join with a left correlation"
// *Cause: An attempt was made to use a lateral view with a left correlation
// to the first operand of an ANSI RIGHT or FULL outer join.
// *Action: Rewrite the query without the left correlation.
/
32799,0000, "cannot rename a system-generated sequence"
// *Cause: An attempt was made to rename a system-generated sequence.
// *Action: A system-generated sequence, such as one created for an
// identity column, cannot be renamed.
/
/ ////////////////
/ 32800 - 32999 are reserved for Messaging Gateway (MGW)
/ Used by DBMS_MGWADM package and other related packages and types.
/ ////////////////
/
//////////// OLAP framework
/ Error numbers 33000 to 38000 are reserved for OLAP work.
/
/ End of File - Add errors from e38001.msg. Consult errorinf.txt
/ 65535 - (MAX ERROR NUMBER; NONE CAN BE LARGER)
/
/
/*********************************************************************
/
/ 32800 - 32999 reserved for Oracle Messaging Gateway (MGW)
/ These errors are used for DBMS_MGWADM package and related types.
/
/*********************************************************************
/
32800, 00000, "internal error %s"
// *Cause: An unexpected error occurred.
// *Action: Contact Oracle Support Services.
/
32801, 00000, "invalid value %s for %s"
// *Cause: An invalid value was specified for a parameter.
// *Action: Specify a valid value for the parameter.
/
32802, 00000, "value for %s must be %s"
// *Cause: An invalid value was specified for a parameter.
// *Action: Specify the value as indicated by the message.
/
32803, 00000, "value for %s cannot be altered"
// *Cause: An attempt was made to alter a value that cannot be altered.
// *Action: Retry the operation without altering the indicated value.
/
32804, 00000, "invalid value %s, %s should have form %s"
// *Cause: A value specified for a parameter has the incorrect form.
// *Action: Specify a string of the correct form.
/
32805, 00000, "identifier for %s too long, maximum length is %s characters"
// *Cause: An identifier string exceeded the maximum allowed length.
// *Action: Specify a string whose length is less than the maximum allowed
// length.
/
32806, 00000, "value for %s is too long, maximum length is %s"
// *Cause: A value exceeded it's maximum allowed length.
// *Action: Specify a value whose length is less than the maximum allowed
// length.
/
32807, 00000, "message system link %s already exists"
// *Cause: A message system link of the specified name already exists.
// *Action: Specify a different name.
/
32808, 00000, "message system link %s does not exist"
// *Cause: A message system link of the specified name does not exist.
// *Action: Specify a message system link name that already exists.
/
32809, 00000, "foreign queue %s is already registered"
// *Cause: The foreign queue has already been registered for this message
// system link (NAME@MSGLINK).
// *Action: Specify a different name that is not being used for this
// message system link.
/
32810, 00000, "foreign queue %s is not registered"
// *Cause: The foreign queue (NAME@MSGLINK) has not been registered for
// this message system link.
// *Action: Specify the name of a registered foreign queue.
/
32811, 00000, "subscriber %s already exists"
// *Cause: The specified subscriber identifier already exists.
// *Action: Specify a different identifier.
/
32812, 00000, "subscriber %s does not exist"
// *Cause: The specified subscriber identifier does not exist.
// *Action: Specify an existing subscriber identifier.
/
32813, 00000, "propagation schedule %s already exists"
// *Cause: The specified propagation schedule identifer already exists.
// *Action: Specify a different identifier.
/
32814, 00000, "propagation schedule %s does not exist"
// *Cause: The specified propagation schedule identifier does not exist.
// *Action: Specify a schedule identifier that already exists.
/
32815, 00000, "message system link %s is referenced by a foreign queue"
// *Cause: An attempt was made to remove a message system link currently
// referenced by one or more registered foreign queues.
// *Action: Unregister all foreign queues using this message system link
// and retry the operation.
/
32816, 00000, "foreign queue %s is referenced by a subscriber or schedule"
// *Cause: An attempt was made to unregister a foreign queue currently
// referenced by one or more subscribers or propagation schedules.
// *Action: Remove all subscribers and propagation schedules using this
// foreign queue and retry the operation.
/
32817, 00000, "message system link %s is not configured with a log queue for %s"
// *Cause: An attempt was made to add a propagation subscriber but the
// message system link was not configured with a log queue for the
// indicated propagation type.
// *Action: Alter the message system link to configure the link with a log
// queue for this propagation type.
/
32818, 00000, "AQ queue %s does not exist"
// *Cause: An operation was attempted where the specified AQ queue
// does not exist.
// *Action: Specify the name of an existing AQ queue.
/
32819, 00000, "AQ queue %s must be a normal queue"
// *Cause: An operation was attempted where the specified AQ queue exists
// but is not a normal queue.
// *Action: Specify the name of an AQ queue which was created as a normal
// queue (NORMAL_QUEUE).
/
32820, 00000, "subscriber queue and exception queue must use same message system link"
// *Cause: An operation was attempted for INBOUND propagation where the
// specified subscriber queue and exception queue reference
// different message system links.
// *Action: Specify an exception queue that is a registered foreign queue
// of the same message system link as the subscriber queue.
/
32821, 00000, "subscriber queue and exception queue must have same payload type"
// *Cause: An operation was attempted for OUTBOUND propagation where the
// AQ queues used for the subscriber queue and exception queue
// have different payload types.
// *Action: Specify an exception queue that has the same payload type as
// the subscriber queue.
/
32822, 00000, "subscriber %s is marked for removal"
// *Cause: An administration operation was attempted for a subscriber which
// is marked for removal. If attempting to remove a subscriber, the
// Messaging Gateway agent is not running or is running but unable
// to remove the subscriber at this time.
// *Action: Do not issue propagation administration commands for a subscriber
// for which removal is pending. Wait for the subscriber to be
// removed by the agent or issue REMOVE_SUBSCRIBER with the FORCE
// option to force the subscriber to be removed.
/
32823, 00000, "subscriber exists for queue %s and destination %s"
// *Cause: An attempt was made to create a propagation subscriber when one
// already exists for the specified queue and destination pair.
// *Action: Specify a different queue and destination pair, or remove the
// subscriber using that pair and retry the operation.
/
32824, 00000, "schedule exists for source %s and destination %s"
// *Cause: An attempt was made to create a propagation schedule when one
// already exists for the specified source and destination pair.
// *Action: Specify a different source and destination pair, or remove the
// schedule using that pair and retry the operation.
/
32825, 00000, "Messaging Gateway agent has not been started"
// *Cause: An attempt was made to shut down the Messaging Gateway agent when
// it is not started.
// *Action: No action required.
/
32826, 00000, "Messaging Gateway agent has already been started"
// *Cause: An attempt was made to start the Messaging Gateway agent when
// it is already started.
// *Action: No action required.
/
32827, 00000, "Messaging Gateway agent must be shut down"
// *Cause: An operation was attempted that requires the Messaging Gateway
// agent to be shut down.
// *Action: Issue SHUTDOWN, wait for MGW_GATEWAY view to show a NOT_STARTED
// status, and retry the operation. CLEANUP_GATEWAY may need to be
// issued to reset the gateway state if the agent fails to shut down
// after a reasonable time period.
/
32828, 00000, "Messaging Gateway agent must be running"
// *Cause: An operation was attempted that requires the Messaging Gateway
// agent to be started and responsive.
// *Action: Issue STARTUP, wait for MGW_GATEWAY view to show a RUNNING status,
// and retry the operation.
/
32829, 00000, "Messaging Gateway agent cannot be shut down while it is starting"
// *Cause: An attempt was made to shut down the Messaging Gateway agent when
// it is in the process of starting and initializing.
// *Action: Wait for MGW_GATEWAY view to show a RUNNING status and retry the
// operation. CLEANUP_GATEWAY may need to be issued to reset the
// gateway state if the agent fails to start after a reasonable
// time period.
/
32830, 00000, "result code %s returned by Messaging Gateway agent"
// *Cause: The Messaging Gateway agent terminated abnormally due to an
// unexpected error.
// *Action: Review the Messaging Gateway log file for further information
// regarding the problem. Resolve the problem and start the
// Messaging Gateway agent. Contact Oracle Support Services if
// the problem cannot be resolved.
/
32831, 00000, "timed out trying to acquire administration lock"
// *Cause: A timeout occurred when attempting an administration operation.
// Either an administration operation was attempted while the
// Messaging Gateway agent was starting and initializing, or
// two administration operations were attempted at the same time.
// *Action: Retry the operation. If the Messaging Gateway agent is starting,
// wait for MGW_GATEWAY view to show a RUNNING status and retry the
// operation.
/
32832, 00000, "failure %s trying to acquire administration lock"
// *Cause: An unexpected error occurred trying to acquire administration lock.
// *Action: Retry the operation. Contact Oracle Support Services if the error
// persists.
/
32833, 00000, "failure %s trying to release administration lock"
// *Cause: An unexpected error occurred trying to release administration lock.
// *Action: Contact Oracle Support Services if the error persists.
/
32834, 00000, "Messaging Gateway agent user has not been set"
// *Cause: A Messaging Gateway agent user has not been configured.
// *Action: Create a database user having role MGW_AGENT_ROLE and issue
// DB_CONNECT_INFO to configure an agent user.
/
32835, 00000, "database user %s does not exist"
// *Cause: The specified database user does not currently exist.
// *Action: Create the user and grant all necessary privileges and roles.
/
32836, 00000, "database user %s must be granted role %s"
// *Cause: The specified database user does not have a required role.
// *Action: Grant the user the indicated role.
/
32837, 00000, "invalid configuration state %s"
// *Cause: The specified configuration state is invalid.
// *Action: Remove and re-create the configured entities. Contact Oracle
// Support Services if the problem cannot be identified or resolved.
/
32838, 00000, "exceeded maximum number of properties"
// *Cause: An attempt was made to alter a property list where the number
// of properties in the resulting list exceeds the maximum allowed.
// *Action: Order the elements of the alter list differently so the number
// of elements in the resulting list is less than the maximum.
/
32839, 00000, "property %s is reserved, names with MGWPROP$_ prefix are not valid"
// *Cause: An attempt was made to specify a reserved name for a property name.
// *Action: Use a non-reserved name.
/
32840, 00000, "property name cannot be NULL"
// *Cause: An attempt was made to use NULL for a property name.
// *Action: Specify a non-NULL name.
/
32841, 00000, "invalid value for property %s"
// *Cause: An attempt was made to specify an invalid value for a property.
// *Action: Specify a valid property value.
/
32842, 00000, "value for property %s cannot be altered"
// *Cause: An attempt was made to alter a property that cannot be altered.
// *Action: Retry the operation without altering the indicated property.
/
32843, 00000, "value for %s is outside the valid range of %s to %s"
// *Cause: A value was specified that is not in the valid range.
// *Action: Specify a value within the indicated range.
/
32844, 00000, "exceeded maximum number of %s values"
// *Cause: An attempt was made to add a value of the specified type but
// the maximum number of such values has been reached.
// *Action: No action required.
/
32845, 00000, "Messaging Gateway agent is already running"
// *Cause: An attempt was made to start the Messaging Gateway agent
// when an agent instance is already running.
// *Action: Shut down the Messaging Gateway agent currently running,
// verify the agent process has been terminated, and start
// the Messaging Gateway agent.
/
32846, 00000, "Messaging Gateway agent cannot be started; status is %s"
// *Cause: An attempt to start the Messaging Gateway agent failed due to
// the indicated agent status. A BROKEN status indicates a problem
// that requires user intervention before the agent can be started.
// *Action: Review the MGW_GATEWAY view and the Messaging Gateway log file
// for further information. Resolve the problem and start the
// Messaging Gateway agent. Contact Oracle Support Services if
// the problem cannot be resolved.
/
32847, 00000, "operation is not supported on this platform"
// *Cause: An attempt was made to perform an operation that is not
// supported on this platform.
// *Action: Switch to a platform on which the operation is supported.
/
32848, 00000, "foreign queue DOMAIN required for JMS unified connections"
// *Cause: A DOMAIN was not specified when registering a foreign queue
// for a messaging system link that is configured to use the
// JMS unified messaging model.
// *Action: Specify a non-NULL value for the DOMAIN parameter.
/
32849, 00000, "%s cannot be set unless %s is set"
// *Cause: An attempt was made to specify a value for a parameter that
// cannot be set unless an associated parameter is also set.
// *Action: Specify a valid value for both parameters, or, do not specify
// a value for either parameter.
/
32850, 00000, "agent %s does not exist"
// *Cause: The specified Messaging Gateway agent name did not exist.
// *Action: Specify an existing agent name.
/
32851, 00000, "agent %s already exists"
// *Cause: The specified Messaging Gateway agent name already existed.
// *Action: Specify a different agent name.
/
32852, 00000, "agent %s is referenced by a message system link"
// *Cause: An attempt was made to remove a Messaging Gateway agent
// currently referenced by one or more message system links.
// *Action: Remove all message system links associated with this agent
// and retry the operation.
/
32853, 00000, "propagation job %s does not exist"
// *Cause: The specified propagation job identifier did not exist.
// *Action: Specify an existing identifier.
/
32854, 00000, "propagation job %s already exists"
// *Cause: The specified propagation job identifier already existed.
// *Action: Specify a different identifier.
/
32855, 00000, "propagation job %s is marked for removal"
// *Cause: An administration operation was attempted for a propagation job
// which is marked for removal. If attempting to remove a job, the
// Messaging Gateway agent is not running or is running but unable
// to remove the job at this time.
// *Action: Do not issue propagation administration commands for a job
// for which removal is pending. Wait for the job to be removed
// by the agent, or, issue REMOVE_JOB with the FORCE option to
// force the job to be removed.
/
32856, 00000, "operation not supported for propagation job"
// *Cause: An attempt was made to perform an operation that was not
// supported for a propagation job.
// *Action: Perform the operation using a propagation job procedure.
/
32857, 00000, "propagation job exists for source %s and destination %s"
// *Cause: An attempt was made to create a propagation job, subscriber,
// or schedule when a propagation job already existed for the
// specified source and destination pair.
// *Action: Specify a different source and destination pair, or remove the
// propagation job using that pair and retry the operation.
/
//
// Copyright (c) 2001, 2017, Oracle and/or its affiliates. All rights reserved.
//
// NAME
// olap33k.msg - OLAP messages in the 33,000 range
//
// DESCRIPTION
// Provides the OLAP error messages for inclusion in the RDBMS
//
// NOTES
// Concatenated with other files to build the RDBMS message file
// If you change this:
// cd rdbms/mesg
// gmake concat
// gmake oraus.msb
//
// MODIFIED (MM/DD/YY)
// cjohnson 09/05/17 - remove _APEIFV01_,_APEIFV02_
// cjohnson 04/12/17 - remove xsILPMLTPreOp01
// cjohnson 04/04/17 - remove NLSCHARSET01
// cjohnson 03/28/17 - remove MXINFILE01 MXARGS02
// jcarey 03/29/17 - bug 25254434 - block aw modification
// ghicks 03/19/17 - add _MXDSS22_, unnamed messages 34373
// cjohnson 03/09/17 - remove DBERR18
// ghicks 09/21/16 - add XSHIDE06, OBSCURE02 and edit SNSYN319
// jcarey 01/13/17 - update 36779 text
// cjohnson 01/02/17 - remove _MXCHGDCL24_
// ghicks 06/30/16 - remove IOSEC05, IOSEC06
// jcarey 08/26/15 - add 33279
// cjohnson 08/12/15 - reduce length of message 33422
// yuli 03/25/15 - remove unused 34374
// cchiappa 02/24/15 - Remove xspq
// cjohnson 01/21/15 - MXCGCHRL01
// jcarey 12/15/14 - add dberrplat
// cjohnson 02/25/14 - objeng messages,
// ghicks 04/21/14 - improve wording of XSDPART20 error, add 33277, 33433
// cjohnson 07/22/13 - mxdcl02
// panzho 07/10/13 - panzho_bug-16864696
// cjohnson 03/21/13 - improve CFINDVAL02 error
// mstasiew 05/10/12 - 13537982 unreserve 36425-36599 for SQL DDL for Cubes
// smierau 03/22/12 - Change text for 35563
// cvenezia 01/30/12 - Bug 12992498: add _EIFIMPRT01 (33393)
// wechen 01/18/12 - add _XSRWLD15_, _XSRWLD16_, _XSRWLD17_
// ghicks 01/17/12 - add PMTUPDAT07
// cjohnson 09/01/11 - remove vcfmt002
// jdhunter 06/02/11 - remove _XSOQMAP_BAD_MAP_ (36029)
// ckearney 05/12/11 - remove cbas
// rsamuels 03/22/11 - reserve range 36425-36599 for SQL DDL for Cubes
// akociube 02/23/11 - Add CBAS errors
// jdhunter 01/25/11 - add _XSOQMAP_BAD_MAP_ (36029)
// ckearney 01/24/11 - add 37423
// smierau 01/04/11 - Add 35585 for _XSRWLD14_
// ghicks 12/29/10 - add DIMSHOW01, DIMSHOW02
// byu 11/12/10 - add 37528 for _XSOBJORG_BAD_HIER_
// esoyleme 08/17/10 - cube dml
// jcarey 10/20/10 - update 36779 cause text
// jcarey 09/22/10 - correct syntax in msg 36779
// smesropi 08/02/10 - add 33409 for _EIFEXPRT16_
// yuli 09/09/10 - raise minimum compatible to 11.0
// cjohnson 05/05/10 - remove obsolete messages
// almurphy 04/01/10 - add 36145 for _XSSETPROP01_
// ckearney 03/31/10 - add error 37421
// ghicks 03/17/10 - add XSSPROPNA
// ckearney 02/05/10 - remove "bytes" from error 33674
// byu 01/15/10 - Add extra text to 35571 to make it more meaningful
// ruqtang 01/11/10 - remove XSAGDNGL46
// jdhunter 12/17/09 - Bug 8572767: OBJORG errors (37093-37099, 37166-37170)
// csperry 10/01/09 - Add 37575-37577 Invalid oplog component specified
// cchiappa 04/06/09 - Add sparsity advisor unexpected change message
// ckearney 03/26/09 - add EXPRESS AW errors 37580 to 37582
// ghicks 03/10/09 - _MXDSS18_, tinker with _MXDSS25_ wording
// ghicks 02/09/09 - _MXDSS25_
// wechen 02/04/09 - Add 37553, 37554
// ckearney 01/27/09 - _XSTFDSC06_
// ghicks 01/06/09 - _MXDSS28_
// cchiappa 12/17/08 - Add 37171: invalid number to SIGNAL
// cjohnson 12/04/08 - toomany errors
// smierau 11/24/08 - Add 35583
// cjohnson 11/27/08 - change deldent02
// cjohnson 11/19/08 - remove valset00
// cjohnson 10/22/08 - apaberr01
// cchiappa 10/22/08 - Add error logging to message
// wechen 10/18/08 - add 35582
// cjohnson 10/13/08 - ftcode00
// akociube 10/13/08 - more logging errors
// smierau 08/25/08 - Clean up modifications comments.
// wechen 08/20/08 - add 37552
// cchiappa 08/08/08 - Add DBMS_CUBE_LOG spec errors
// smierau 08/05/08 - Add logging reject messages.
// smierau 06/25/08 - added 34123 for rejected records log
// cjohnson 06/30/08 - remove mxdcl34 mxdcl35
// jcarey 06/18/08 - apibranch support
// cjohnson 07/08/08 - fix bad merge
// cvenezia 05/22/08 - add 37165
// wechen 05/14/08 - fix cause/action for 37541 through 37551
// jcarey 05/22/08 - restore 33275
// cchiappa 05/16/08 - Add logging errors
// ckearney 05/17/08 - add _OCI13_ & _OCI14_, 34805 & 34806 respectively
// wechen 05/14/08 - add 37541 through 37551
// jcarey 05/02/08 - add 33275
// jcarey 05/12/08 - add 33299
// ghicks 04/15/08 - cause and action for REGRESS00
// ruqtang 04/10/08 - add new hierck err mesg
// ckearney 11/30/07 - add 37163
// zqiu 04/12/07 - add 37420
// wechen 03/20/07 - add 37162
// mdombros 01/17/07 - add _XSTBLFUNC14_, change XSOTEXPAND00 to
// _XSTBLFUNC13_
// zqiu 01/12/07 - error for explain_mview on CREATE CUBE MV
// ghicks 12/27/06 - add _XSLPDSC07_
// ruqtang 12/15/06 - add _XSAGMODDIM02_
// cwelton 12/08/06 - add XSCCLOAD01 and XSCCLOAD02
// ruqtang 11/21/06 - add XSDPART25
// ruqtang 11/13/06 - add XSAGDNGL51
// hyechung 11/06/06 - add and modify XSMXCLEAs
// cjohnson 10/31/06 - makedcl10
// jcarey 10/30/06 - no aw detach when cursor open
// jcarey 10/24/06 - add _XSCHKMAKE01_
// ckearney 10/16/06 - add XSANALYZ04, 05 & 06, delete property stat msgs
// ruqtang 10/12/06 - add _XSCCOMP23, XSVPART09_
// hyechung 10/18/06 - add XSVALSETs
// hyechung 10/18/06 - add XSAGDNGL16
// hyechung 10/12/06 - add causes and actions
// sdonnell 10/11/06 - readonly
// ruqtang 09/18/06 - cc group mesg
// esoyleme 09/18/06 - xscoqa messages
// jcarey 09/18/06 - Dont rollback non-frozen AW to freeze point
// csperry 09/12/06 - Add no aggcount error
// ghicks 08/30/06 - add XSRESREV05
// cwelton 08/25/06 - add XSAGGR35, XSCCOMP17
// cchiappa 08/22/06 - Add more COT errors
// cjohnson 08/11/06 - remove obsolete messages
// cjohnson 08/15/06 - remove obsolete errors
// wechen 08/14/06 - recycle 37120, 37150, 37151, 37157
// jcarey 07/26/06 - add DBERRSYNC
// ruqtang 08/02/06 - XSRELGID24, 25
// wechen 07/31/06 - add 37161
// ruqtang 07/21/06 - add XSRELDEP00
// cchiappa 07/12/06 - Disallow DELETE of AW with COT
// ghicks 07/03/06 - new XSAWRESREVnn messages
// mdombros 06/12/06 - add 36825, tabfun arg expansion failed
// jcarey 06/15/06 - add xsILPMLTPreOp01
// ruqtang 06/16/06 - change err msg for GID Property
// pludwig 06/13/06 - txn117409: LOOP OPTIMIZED and LOOP AGGMAP()
// ruqtang 06/12/06 - more err msg for groupset option in gid
// ruqtang 05/31/06 - modify XSAGGR33
// ruqtang 06/06/06 - Add XSRELGID19, 20
// ckearney 06/05/06 - add ANALYZDIM00 & ANALYZCUBE00
// wechen 05/22/06 - add 37160
// jcarey 05/25/06 - comment
// wechen 05/26/06 - fix 37159
// mdombros 06/01/06 - join pushing failed msg
// ckearney 05/19/06 - update lmgen messages
// ruqtang 05/24/06 - add XSRELGID18
// cchiappa 06/02/06 - OLAP ORGANIZED tables error messages
// cchiappa 04/18/06 - OLAP ORGANIZED tables
// jcarey 04/14/06 - aw rollback
// wechen 05/12/06 - add 37159
// cjohnson 04/05/06 - timestamp
// cchiappa 04/07/06 - Reserve error number range for AW MVs
// pludwig 03/24/06 - txn117234: Add XSTBLFUNC10, 11, 10
// cjohnson 03/28/06 - fileset04
// cjohnson 03/24/06 - date_format
// cchiappa 03/20/06 - Eliminate DBERR00
// cjohnson 03/06/06 - datetime dim
// ckearney 02/09/06 - update sql import error messages
// cwelton 03/01/06 - cleanup CC error messages
// ghicks 02/08/06 - add _OCI12_, modify wording of a couple of others
// cchiappa 01/12/06 - Adjust Aggregate errors to reflect optional aggmap
// ghicks 12/21/05 - remove DTNAMES00, DTNAMES01 (MONTHNAMES, DAYNAMES)
// ghicks 12/12/05 - add PRMPINIT217, 218, 219
// ckearney 11/29/05 - add stat prop message
// ckearney 11/16/05 - add analyze errors
// cchiappa 12/01/05 - Add NXHANDLEALLO
// ghicks 11/15/05 - add _VCHEX01_
// jcarey 10/26/05 - add freezing
// cchiappa 11/07/05 - More verbose sparsity advisor messages
// ruqtang 10/11/05 - Add _XSHIERCK09_
// cchiappa 10/03/05 - Add fatal UPDATE error
// cjohnson 09/26/05 - stateq01
// ghicks 09/23/05 - add _PHYS03_, _PHYS04_
// ghicks 09/22/05 - add _SNSYN116_
// ruqtang 09/07/05 - add _XSHIERCK06-8_
// ghicks 08/24/05 - add _QFSVNS00_
// cjohnson 08/14/05 - qfget02 d ->ld
// ghicks 08/02/05 - add _NLSSORT01_
// ilyubash 06/17/05 - spell check a few errors
// cchiappa 07/20/05 - Add 33271: Simulated paging error
// zqiu 07/21/05 - add _XSPGERRPQUPD_
// jcarey 06/29/05 - fix pgfetch messages
// ruqtang 06/30/05 - add XSHIERCK05,06 and remove HIERCHECK_
// ghicks 06/29/05 - add _XSCHGDFN01_, add NTEXT to _HASHSCAN01_
// ruqtang 06/21/05 - add XSHIERCK03,04
// ghicks 06/18/05 - add _HASHSCANxx_
// zqiu 06/20/05 - better DBERR20
// ruqtang 06/16/05 - add XSAGMODHIER02
// zqiu 06/10/05 - add DBERR20
// ghicks 06/08/05 - remove _MXDCL07_, _MAKETD**_
// ghicks 04/19/05 - add _XSINPUTERR_
// dpeltier 04/21/05 - some new EIF messages
// ghicks 04/19/05 - _XSAGGCNTMOVE01_ .. 06_
// ghicks 03/25/05 - add XSLANGDM02
// cchiappa 03/30/05 - Remove 37081
// akociube 03/17/05 - add XSTBLFUNC09
// ghicks 03/18/05 - update list of valid types for _XSMCSESS04_
// cjohnson 03/16/05 - remove xscgrank05
// ghicks 03/17/05 - add XSLANGDM*; tinker with XSSPROP* punctuation.
// dpeltier 03/17/05 - really complicated iterators
// cchiappa 03/15/05 - Add XSAGDNGLPREC (33009)
// cjohnson 03/11/05 - remove unused errors
// cwelton 03/11/05 - add XSAGDNGL49, XSAGDNGL50
// cchiappa 03/10/05 - Add XSPQEXPRESS (37069)
// cjohnson 03/02/05 - xscgrank05
// ghicks 03/02/05 - add OPCREATE01, O2; remove PPENG04
// cchiappa 03/01/05 - Tweak sps adv errors based on errors_us feedback
// cjohnson 02/16/05 - delete mxcgaf04
// cchiappa 02/15/05 - Tweak sparsity advisor messages
// dpeltier 02/15/05 - partitioning / aggcount stuff
// ghicks 02/12/05 - add _LOCKCHECK01_
// cchiappa 02/10/05 - Add DELDENTANON
// cchiappa 02/08/05 - Move errors out of reserved ranges
// ruqtang 01/31/05 - add _XSCGMDLAGG09-13_
// dpeltier 01/24/05 - add messages for _mvtopart
// ghicks 01/20/05 - add XSFCAST28 (36951)
// cchiappa 01/10/05 - More sparsity advisor messages
// wechen 12/28/04 - add 37118 through 37120, 37150 through 37158
// ilyubash 12/09/04 - add DBERR07 (33274)
// cchiappa 11/29/04 - Sparsity advisor errors
// ckearney 11/01/04 - add 36849 & 36850, add %a to 36886
// ghicks 10/31/04 - spelling; remove MXSQL25, XSAGDNGL45
// dpeltier 10/13/04 - MXMSERR01 takes a qon node
// pludwig 10/04/04 - Fix assignments of scalar to temp scalar variables
// ruqtang 09/14/04 - correct more mesg for XSRELTBL/XSRELGID
// ruqtang 09/08/04 - XSRELGID17
// esoyleme 09/07/04 - message for transportable platform mismatch
// cchiappa 08/20/04 - Move bad error messages
// ghicks 07/28/04 - slight adjustment to MXRECAP09
// ghicks 07/19/04 - delete EIFEXPRT00
// cjohnson 07/13/04 - Add XSBASLIM00
// cchiappa 06/29/04 - Add XSAGGRFORM
// ghicks 06/30/04 - eliminate MODGONE00, add MDQUERY01
// dpeltier 06/25/04 - xsLmsMesg changes
// cwelton 06/24/04 - XSCCOMP11 thru XSCCOMP15
// zqiu 06/23/04 - more action for DBERRBSZ
// ckearney 06/23/04 - Add XSSRF04, XSSRF05 & XSSRF06
// cwelton 06/28/04 - Cleanup cc error messages
// ghicks 06/17/04 - add SNSYN205
// cchiappa 06/17/04 - Fix XSAGGR33 arguments
// cchiappa 06/09/04 - Tweak cause for XSAGGCNTPROP
// cchiappa 06/07/04 - Add XSAGGCNTPROP
// ghicks 06/03/04 - remove obsolete PRMPINIT initializers
// dpeltier 06/01/04 - XSCCOMP0[456] wording, add XSCCOMP10
// dpeltier 05/17/04 - aw_upgrade -> polymorphic convert
// cchiappa 05/14/04 - Add XSAGPROPFROM
// dpeltier 05/12/04 - AGGCOUNT
// ghicks 05/03/04 - XSSQLMDQ messages
// dpeltier 04/15/04 - AWUPG messages
// cchiappa 04/09/04 - Add XSSPROPDTYPE
// cchiappa 04/09/04 - Fix text for XSMXAGGR10
// cchiappa 04/09/04 - Add XSAGGRRUVCV
// cchiappa 03/29/04 - Spell correct DBERR18, text for 33269
// ruqtang 03/29/04 - RELTBL15
// dpeltier 03/16/04 - make EIFEXPRT01 more general
// dpeltier 03/03/04 - XSMXAGGR06
// cjohnson 03/02/04 - obsolete errors
// ilyubash 03/15/04 - Allow add SESSION in MULTI
// cjohnson 02/18/04 - obsolete errors
// cjohnson 02/23/04 - obsolete errors
// ghicks 02/05/04 - delete obsolete messages, add XSSPFC01
// dpeltier 01/30/04 - MAINTCHK messages
// ilyubash 12/29/03 - Add messages delayed since 10gR1
// jcarey 12/19/03 - add XSDBVALID 05, 06
// cwelton 08/18/03 - Add XSCCOMP00 - XSCCOMP09
// dpeltier 08/07/03 - add compressed composite messages
// ckearney 08/06/03 - add _XSSRF03_ message & update other SRF messages
// ghicks 08/05/03 - fix %p (-> %%p) in VCFMT005
// wechen 08/04/03 - add 37117 for xsldolap
// cjohnson 07/23/03 - MAXDIMS 256
// cchiappa 07/31/03 - Fix XSDPART24
// esoyleme 07/29/03 - add 37100
// pludwig 07/29/03 - txn107486: Concat custom members
// ghicks 07/22/03 - reintroduce QFHEAD01 in case of need
// ckearney 07/21/03 - add _XSTBLFUNC08_
// zqiu 07/22/03 - change err text of 36770
// rtang 07/24/03 - add XSAGDNGL48
// ghicks 07/17/03 - reword QFHEAD06; 86 QFHEAD01; QFHEAD causes/actions
// jcarey 07/16/03 - More cause and actions
// jcarey 07/15/03 - add finegrained access control error message
// zqiu 07/09/03 - add DBERRBSZ
// ilyubash 07/03/03 - Add Bad Expression error to Table Fucntions
// cchiappa 06/24/03 - Eliminate XSPQRO (37071)
// ghicks 06/23/03 - drop word 'dimension' from PERMIT06
// wechen 06/17/03 - add 37116 for xsldolap
// ilyubash 06/13/03 - Add Rollback support error messages
// pludwig 06/09/03 - txn107433: dup concat leaves in model DIMENSION stmt
// rtang 06/05/03 - add more errs for XSCGMDLAGG
// ghicks 05/29/03 - fix run-on sentence in 37002
// cchiappa 05/28/03 - Eliminate session sharing stuff
// wechen 05/27/03 - add 37115 for xsldolap
// pludwig 05/27/03 - txn106886: More UNIQUE Concats
// rtang 05/19/03 - XSMCSESS08
// dpeltier 05/19/03 - 9i2 compatibility & EIF
// ghicks 05/15/03 - 86 FCREATE06
// ghicks 05/09/03 - 86 QFGET04
// cwelton 05/08/03 - XSCCUBE01/02
// ghicks 05/07/03 - PERMIT06
// dpeltier 05/07/03 - add ESDREAD17, XSVPART07
// dpeltier 05/07/03 - partition list maintenance
// cjohnson 05/06/03 - TRGPRG02
// ghicks 04/29/03 - edit causes/actions for 4/21/03 messages
// cjohnson 04/29/03 - TRGSET01
// cchiappa 04/21/03 - Add XSPQRO
// ghicks 04/21/03 - CINSERT06/07, CMOVE03; reword XSMCSESS messages
// cjohnson 04/21/03 - TRIGGER
// rtang 04/21/03 - Add more XSRELGID err msg
// rtang 04/16/03 - XSMCSESS07
// dpeltier 04/08/03 - list partitioning changes
// cwelton 04/08/03 -
// pludwig 04/07/03 - txn105869: Unique CONCATs
// rtang 03/28/03 - More err msg for custmem
// cwelton 04/03/03 -
// cchiappa 03/26/03 - Add DBERRTABLE
// cjohnson 03/26/03 - TRANSLATEBYTES
// cchiappa 03/19/03 - DBERRLEN 8 byte arguments
// ghicks 03/19/03 - Add Hide/unhide model msg
// dpeltier 03/14/03 - change some partitioning messages
// cchiappa 03/13/03 - Add DBERRLEN
// cchiappa 03/06/03 - Reword DBDESC06
// esoyleme 02/06/03 - SQL spreadsheet error
// cjohnson 02/24/03 - chgdfn inverted
// cwelton 03/26/03 - XSAGPARTDEP - aggregate + recursive partitions
// cwelton 03/03/03 - XSAGHIERPART - aggregate + partitions
// dpeltier 02/14/03 - more partitioning stuff
// dpeltier 02/13/03 - bad compatibility settings for object define
// dpeltier 02/10/03 - some small partitioning stuff
// ilyubash 01/20/03 - New-gen-present errors
// ghicks 01/15/03 - remove (very) obsolete MAINTAIN COMPACT reference
// cjohnson 01/10/03 - sharemap
// zqiu 01/13/03 - remove _XSAWRENAME_*
// cchiappa 01/15/03 - Add message for text ag var reuse
// esoyleme 12/24/02 - fix message for 37080
// cjohnson 12/22/02 - TEMP dimension
// zqiu 01/03/03 - add 37060, 37061 for aw_rename
// wechen 12/19/02 - add 37111, 37112, 37113 & 37114 for xsldolap
// dpeltier 12/09/02 - multiwriter dimension maintenance
// ilyubash 12/02/02 - Multiwriter work
// dpeltier 11/19/02 - more partitioning
// ghicks 12/04/02 - substitution marker in MXCGVAR01
// cjohnson 11/26/02 - export partition template
// pludwig 11/19/02 - txn105041
// ghicks 11/16/02 - various small fixes
// rtang 11/15/02 - Fix MCSESS Error Msg
// rtang 11/12/02 - add XSMCSESS02
// ckearney 11/12/02 - Updated MXSQL24 & SQLOUT11
// ilyubash 11/11/02 - Add more Multiwriter errors
// cchiappa 11/04/02 - Optional aggmap in allocate (SNSYN163)
// dpeltier 11/04/02 - LIST partitioning
// dpeltier 11/02/02 - Add DELDENT05
// pludwig 11/01/02 - txn104999
// ghicks 10/28/02 - add QFSVNS01
// ilyubash 10/24/02 - More Multiwriter error msgs
// pludwig 10/23/02 - txn104769
// cchiappa 10/21/02 - Add BADSPROP, NOAGM
// cjohnson 10/19/02 - sort hierarchy
// ghicks 10/17/02 - add 'missing or' to MXIMPORT04
// dpeltier 10/16/02 - BASE -> CONCAT
// dpeltier 10/14/02 - more partitioning
// rtang 10/14/02 - messages for mnt session
// pludwig 10/12/02 - txn104553
// cchiappa 10/08/02 - Add _XSAGDIMBREAK_
// esoyleme 10/04/02 - more advisor messages
// dpeltier 09/30/02 - subpartitioning
// cchiappa 09/27/02 - Flow -> Drop
// cjohnson 09/27/02 - chgdims limit arg
// esoyleme 09/23/02 - aggregate advisor messages
// ilyubash 09/20/02 - Add more XSACQUIRE messages
// ghicks 09/19/02 - texts for AW LIST and AW(LISTALL)
// cchiappa 09/19/02 - Add 37003 - May not xeq in pq sess
// ckearney 09/12/02 - Change _XSSRF01 message
// dpeltier 09/11/02 - fix MXPSHPOP03
// ilyubash 09/05/02 - added multiwriter error msgs
// ilyubash 09/11/02 - Adding new DTB error messages
// ilyubash 09/04/02 - Add table function describe error messages
// dpeltier 09/04/02 - more partitioning
// dpeltier 08/28/02 - more partitioning
// cchiappa 09/04/02 - Add XSAGDIMFLOW
// rtang 08/22/02 - Add more error for GroupingID
// dpeltier 08/19/02 - Partitioned variables messages
// cchiappa 09/03/02 - Modify PHYS0{0,1}
// cchiappa 08/15/02 - Add autoupdate & autocommit error
// dpeltier 08/08/02 - More partitioning messages
// rtang 08/05/02 - Change RELTBL mesg
// cwelton 08/05/02 - Add XSTBLFUNC06
// ckearney 08/07/02 - Add _XSSRF02_ & _XSTBLFUNC07_
// cchiappa 08/02/02 - Add 37002, OLAP failed to initialize
// cchiappa 08/02/02 - Fix XSAGDNGL24, XSAGDNGL43
// cchiappa 08/01/02 - Add 36961, OLAP not available
// ckearney 08/01/02 - Add _XSSRF01_
// dpeltier 07/10/02 - XSDPART messages
// ghicks 07/30/02 - MAKEDCL35 - "date dimension" -> "time dimension"
// cchiappa 07/30/02 - Add XSUNUPDATED
// ghicks 07/25/02 - change MXPROPER04 to substitute min/max
// ilyubash 07/24/02 - Added MXDSS29
// pludwig 07/25/02 - txn103641
// rtang 07/23/02 - Add XSAGDNGL47
// pludwig 07/23/02 - pludwig_txn103382
// cwelton 07/24/02 - Add XSTBLFUNC05
// cjohnson 07/22/02 - XSSCLLEV09
// cwelton 07/17/02 - Add XSTBLFUNC04
// cchiappa 07/16/02 - Modify XSMXAGGRFROM
// pludwig 07/15/02 - pludwig_txn103382
// cchiappa 07/08/02 - Remove text from XSAGGR33 & XSAGGR34
// ghicks 07/02/02 - fix OFCENG02 ("specifiy")
// ckearney 06/27/02 - Added _SQLOUT20_ - ORA-35587.
// ckearney 07/10/02 - Added _XSSRF00_
// esoyleme 06/20/02 - Fix XSAGGR33
// cchiappa 06/20/02 - Add dataflow XSMXAGGR messages
// cchiappa 05/24/02 - Kill XSAGINFO01, add header
// jcarey 05/24/02 - LRG97582 - bad memory references past end-of-buffer
// dpeltier 05/23/02 - Fix NTEXT garbage in error messages
// edashevs ??/??/?? - edashevs_txn102340
// zqiu 05/14/02 - change OLAP_PAGE_POOL_SIZE to big int
// cwelton 05/04/02 - Implement LMINFO function
// cchiappa 05/02/02 - Alias dimension for parents in allocate
// ckearney 05/02/02 - sql SELECT work
// cchiappa 04/25/02 - Allow agg of unlike-dimensioned vars in one command
// cwelton 04/12/02 - obj(aggmaplist) function
// rtang 04/07/02 - Single dimension model only as dynamic model
// rtang ??/??/?? - rtang_txn105656
// ghicks ??/??/?? - ghicks_txn105486
// cchiappa ??/??/?? - cchiappa_txn105431
// cjohnson 03/27/02 - LEVELREL args for LAG/MOVING functions
// ghicks 03/13/02 - AIX porting bug 2194536 (again);
// ilyubash 02/01/02 - Gracefully handle out-of-temp-space problems.
// ghicks 01/26/02 - eversion and eifversion;
// ghicks 01/19/02 - allow obj(numvals) etc. to return > MINSB8MAXVAL;-
// cjohnson 01/18/02 - remove h files
// ghicks 01/18/02 - new Geneva functionality
// ghicks 01/11/02 - remove STRIP command;
// cchiappa 01/08/02 - Fix allocate bugs
// dpeltier 12/14/01 - More AW name: aliases, different semantics, etc.
// edashevs ??/??/?? - edashevs_txn101085
// pludwig 12/12/01 - Fix Bug 2139758 - 64bit problem in xskvbn.c
// dpeltier 12/11/01 - AW names / attachnames
// edashevs ??/??/?? - edashevs_txn100848
// jcarey 12/05/01 - causes and actions.
// dpeltier 12/05/01 - EIF export, FILEREAD, implicit conversion exceptions
// ahopeman 11/29/01 - Table functions use xsinterp to execute commands
// dpeltier 11/29/01 - Surrogate bug 2110865
// ghicks 11/29/01 - filequery
// ilyubash 11/29/01 - Segv in EIF code without running CDA
// cwelton 11/27/01 - Table Function error msg
// dpeltier 11/20/01 - Clean up LMS messaging; remove OS translation
// pludwig 11/20/01 - CONCAT base add and export exclude
// rtang 11/20/01 - New requirement of dynamic model at current stage
// cjohnson 11/19/01 - olint fixes
// jcarey ??/??/?? - jcarey_txn100717
// ilyubash 11/16/01 - Further support for directory aliases
// ghicks 11/16/01 - allow (slightly crippled) multi-file EIF export;
// rtang 11/14/01 - fill cause and action fields in error message.
// rtang 11/13/01 - number dimesnioned destination relation GID
// dpeltier 11/12/01 - NUMBER dims
// cjohnson 11/01/01 - remove .h files from xseng/globals.h
// dpeltier 10/31/01 - NTEXT: UNISTR(), output functions
// ghicks 10/31/01 - BUG2075951 - INFO(PARSE TYPE) for program/extcall
// dpeltier 10/29/01 - Surrogates: unit tests and bug fixes
// cjohnson 10/26/01 - GUARD/ONEXIT bugs
// ghicks 10/26/01 - porting grp changes for variable name conflicts etc.
// rtang 10/26/01 - hierheight & groupingid support multidim relations
// dpeltier 10/24/01 - Remove data gatherer messages from olap33k.msg
// cjohnson 10/21/01 - fix qa tests
// cjohnson 10/19/01 - remove obsolete code and fix txengcdd.tst
// ilyubash 10/19/01 - Fix AW DELETE and link it into enqueues
// cjohnson 10/16/01 - fix QA log files/ CGETPOS05 xsOOPS
// dpeltier 10/15/01 - Some NTEXT import / export fixes
// dpeltier 10/11/01 - Fix log files for message difs
// dpeltier 10/10/01 - Messages from rdbms/ora*.msb, not olap/aps*.msb
// abatakis ??/??/?? - Created from old files
//
/**************************************************************
/ Message file for Oracle OLAP
/**************************************************************
/
33000, 00000, "(AGOPEN00) %a %j %s\nAGGMAP %1p cannot be accessed because it was compiled by a more recent version of %2p."
// *Cause: The AGGMAP was already compiled by a more recent version of the
// product than was being used to execute this command.
// *Action: Recompile the AGGMAP in the current version.
/// Codes from xsagdang.c (100-359)
33002, 00000, "(XSAGDNGL00) %a %j %lf %lf\nIn AGGMAP %1p, the FLOOR argument of %2p must be less than the CEILING argument of %3p."
// *Cause: The user specified a floor argument greater than the
// ceiling argument.
// *Action: Adjust the floor and ceiling arguments so that the floor is
// less than the ceiling.
// OBSOLETE, please remove this
33003, 00000, "(XSAGDIMDROP) %j, to be transformed during data load, must be a base dimension and not otherwise referenced in the AGGMAP."
// *Cause: The user tried to specify a dimension in a dataflow-related clause
// in an aggmap which is already in another RELATION statement, DIMENSION
// statement, or possibly dimensioning the AGGMAP, or they specified a
// composite or conjoint dimension, or an object which is not a dimension
// *Action: Remove the conflicting reference or specify a valid object
33004, 00000, "(XSAGDNGL01) %q is not a relationship array."
// *Cause: A RELATION clause in the AGGMAP named a workspace object that
// is not a relation.
// *Action: Name a valid self-relation in the RELATION statement.
33005, 00000, "(XSAGDIMBREAK) Invalid breakout for dimension %n."
// *Cause: The user specified something that was not a valid dimension or
// relation on a BREAKOUTDIM line in an aggmap. This might be
// because the object was not a valid relation, was not over the
// specified dimension or was multidimensional
// *Action: Use a valid relation instead
33006, 00000, "(XSAGDNGL02) The relation %q is not related to itself."
// *Cause: A relation was named in a RELATION clause of the AGGMAP that is
// not a self-relation.
// *Action: Name a valid self-relation in the RELATION statement.
33007, 00000, "(XSAGPVAR) %a %j\n%1p may only be used as one of: an OPERATOR, ARGS, or FROMVAR variable."
33008, 00000, "(XSAGDNGL03) %a %j %j\nThe relation %2p is not a relation over a base dimension of AGGMAP %1p."
// *Cause: A relation was named in a RELATION clause of the AGGMAP that is
// not a relation for a base dimension of the AGGMAP.
// *Action: Name a valid self-relation in the RELATION statement, that is, one that
// has a dimension that dimensions the AGGMAP.
33009, 00000, "(XSAGDNGLPREC) %a %j\n In AGGMAP %1p, PRECOMPUTE may only be specified either for the entire AGGMAP or for individual RELATION statements."
// *Cause: PRECOMPUTE was specified both as a line in the AGGMAP and on at least one of the RELATION lines, or it was specified more than once as a line of the AGGMAP.
// *Action: Remove either the PRECOMPUTE line, or the PRECOMPUTE specification for all of the RELATION lines.
33010, 00000, "(XSAGDNGL04) %a %q %n\nRelation %1p is duplicated in the AGGMAP %2p."
// *Cause: Two RELATION statements in the AGGMAP reference the same
// relation object.
// *Action: Remove the duplicate RELATION statement.
33012, 00000, "(XSAGDNGL05) AGGMAP %n contains invalid syntax."
// *Cause: A line in the AGGMAP contains invalid syntax.
// *Action: Change the line to have valid syntax.
33014, 00000, "(XSAGDNGL06) %a %n %n %j\nIn AGGMAP %1p, variable operator %2p cannot be dimensioned by rollup dimension %3p."
// *Cause: Operator variables cannot have the rollup dimension as
// one of their base dimensions.
// *Action: Modify the definition of the operator variable so that the
// current rollup dimension is not one of its bases.
33016, 00000, "(XSAGDNGL07) %a %n %q\nIn AGGMAP %1p, %2p is not a valid operator or variable name."
// *Cause: An invalid argument was supplied to the OPERATOR clause in the
// relation statement.
// *Action: Fix the OPERATOR clause so that it specifies either a valid
// variable name or a valid operator.
33018, 00000, "(XSAGDNGL08) %a %n %n %s\nIn AGGMAP %1p, the data type of %2p must be TEXT, not %3p."
// *Cause: An operator variable was supplied whose data type is not TEXT.
// *Action: Change the operator clause to reference a TEXT variable.
33022, 00000, "(XSAGDNGL10) %a %j %j\nThe measure dimension %2p must be a TEXT or ID base dimension that does not dimension AGGMAP %1p, but is in the same analytic workspace."
// *Cause: A MEASUREDIM was supplied in the AGGMAP that was not acceptable.
// *Action: Modify the MEASUREDIM clause to specify a valid dimension.
33024, 00000, "(XSAGDNGL11) AGGMAP %j contains duplicate information."
// *Cause: The aggmap contains multiple instances of a clause that
// can only be specified once.
// *Action: Remove the extra clause.
33026, 00000, "(XSAGDNGL12) %a %j %q\nIn AGGMAP %1p, %2p is not a valid valueset."
// *Cause: A line in the AGGMAP contains an invalid element where a valid valueset is required.
// *Action: Change the line to have a valid valueset.
33028, 00000, "(XSAGDNGL13) %a %j %n\nIn AGGMAP %1p, %2p should be scalar, not a dimensioned valueset."
// *Cause: A line in the AGGMAP contains a dimensioned valueset where a scalared valueset is required.
// *Action: Change the line to have a scalar valueset.
33030, 00000, "(XSAGDNGL14) In AGGMAP %j, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements."
// *Cause: The AGGMAP either specified multiple PROTECT statements not
// on a RELATION line, or specified PROTECT statements both
// independently and on RELATION lines.
// *Action: Correct the AGGMAP to have valid syntax.
33032, 00000, "(XSAGDNGL15) %a %j %n\nIn AGGMAP %1p, VALUESET %2p must be in extra dimensions of the relation."
// *Cause: The RELATION phrase contains a VALUESET which is not over the extra dimension of the RELATION.
// *Action: Correct the RELATION phrase to contain a valueset over the extra dimension or not to contain any valueset.
33034, 00000, "(XSAGDNGL16) %a %j %j\nIn AGGMAP %1p, VALUESET %2p in PRECOMPUTE phrase must be in the self dimension of the relation."
// *Cause: The precompute phrase contains a valueset which is not over the self dimension of the relation.
// *Action: Correct the relation phrase to contain a valueset over the self dimension or not to contain any valueset.
33036, 00000, "(XSAGDNGL17) ARGS option %n must be a TEXT variable."
// *Cause: An ARGS value had a non-text data type.
// *Action: Use a text variable for ARGS.
33038, 00000, "(XSAGDNGL18) %a %j %j\nIn AGGMAP %1p, RELATION %2p contains hierarchy dimensions that are also dimensions of the AGGMAP."
// *Cause: Hierarchy dimensions(extra dimensions) of a RELATION in the AGGMAP are base dimensions of the AGGMAP.
// *Action: Correct the RELATION not to have hierarchy dimensions(extra dimensions) which are also base dimensions of the AGGMAP.
33040, 00000, "(XSAGDNGL19) %a %j %j %j\nIn AGGMAP %1p, VALUESETS %2p and %3p are both over the same hierarchy dimension."
// *Cause: Two or more different VALUESETs over the same hierarchy dimension are used in the AGGMAP.
// *Action: Use the same VALUESET for two RELATION phrases or use two different VALUESETs over two different hierachy dimensions.
33042, 00000, "(XSAGDNGL20) %a %j %j %j\nIn AGGMAP %1p, VALUESET %2p must qualify all relations dimensioned by %3p."
// *Cause: A VALUESET over a hierarchy dimension qualifies some RELATIONs but not all RELATIONs dimensioned by the same hierarchy dimension.
// *Action: Use the same VALUESET to qualify all the RELATIONs dimensioned by the same hierarchy dimension.
33044, 00000, "(XSAGDNGL21) %a %s %j\nAGGREGATE operator %1p requires a WEIGHTBY clause, but the ARGS clause in AGGMAP %2p did not specify one."
// *Cause: The user used an operator which needs weight values but not provided the weight values.
// *Action: Provide weight values using a WEIGHTBY cluase.
33045, 00000, "(XSAGDNGL51) %a %s %j %n\nThe AGGREGATE operator %1p does not require a weight, but ARGS clause in AGGMAP %2p specified %3p as a weight."
// *Cause: The ARGS variable specified a weight even though one is
// not needed.
// *Action: Modify the ARGS variable so that it does not specify a weight for
// that operation.
33046, 00000, "(XSAGDNGL22) In AGGMAP %j, you can specify only one SCREENBY clause."
// *Cause: The AGGMAP contained multiple SCREENBY clauses.
// *Action: Remove one of the SCREENBY clauses from the AGGMAP.
33048, 00000, "(XSAGDNGL23) %a %n %j %j\nIn AGGMAP %1p, the relation %2p and the relation %3p are both over the same base dimension."
// *Cause: The AGGMAP contains incompatible RELATION statements.
// *Action: Remove one of the RELATION statements from the AGGMAP.
33050, 00000, "(XSAGDNGL24) %a %j %j\nAGGMAP %1p cannot be used to aggregate %2p, because it is defined in a different analytic workspace."
// *Cause: The user attempted to aggregate a variable in another
// analytic workspace.
// *Action: Create an AGGMAP in the other analytic workspace to aggregate
// that variable.
33052, 00000, "(XSAGDNGL25) AGGMAP %j is a dimensioned AGGMAP; it can only be used to aggregate like-dimensioned variables."
// *Cause: The user attempted to aggregate a variable with different dimensions
// than the AGGMAP. This is only possible with undimensioned AGGMAPs.
// *Action: Create a new undimensioned AGGMAP.
33058, 00000, "(XSAGDNGL28) %a %j %t %d\nIn AGGMAP %1p, error code %2p is greater than the maximum error code of %3p."
// *Cause: The user specified an invalid ERRORMASK value.
// *Action: Remove the invalid value from the ERRORMASK list.
33060, 00000, "(XSAGDNGL29) In AGGMAP %j, the value for the ERRORLOG MAX option must be greater than 0."
// *Cause: The user specified an ERRORLOG MAX of 0 or a negative number.
// *Action: Adjust the AGGMAP so that it uses a positive number.
33062, 00000, "(XSAGDNGL30) %a %j %n\nIn ALLOCMAP %1p, WEIGHTBY option %2p must be a numerical VARIABLE or FORMULA."
// *Cause: The WEIGHTBY clause requires numerical VARIABLE or FORMULA but the user used invalid objects.
// *Action: Correct the WEIGHTBY cluase to use a valid numerical VARIABLE or FORMULA.
33064, 00000, "(XSAGDNGL31) %a %j %n\nIn AGGMAP %1p, the hierarchy dimension QDR %2p cannot refer to the related dimension of the relation."
// *Cause: The user specified an invalid hierarchy dimension qualified data reference.
// *Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference.
33066, 00000, "(XSAGDNGL32) %a %j %n\nIn AGGMAP %1p, the hierarchy dimension QDR %2p must be a hierarchy dimension of the relation."
// *Cause: The user specified an invalid qualified data reference for the hierarchy dimension.
// *Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference.
33068, 00000, "(XSAGDNGL33) %a %j %j\nIn AGGMAP %1p, the hierarchy dimension QDR over dimension %2p must specify a positive dimension offset."
// *Cause: The user specified an invalid qualified data reference for the hierarchy dimension.
// *Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference.
33070, 00000, "(XSAGDNGL34) %a %j %j\nIn AGGMAP %1p, all QDRs of dimension %2p must map to the same dimension position."
// *Cause: The user specified two conflicting hierarchy dimension qualified data references.
// *Action: Adjust the AGGMAP so that it uses a consistent qualified data reference.
33072, 00000, "(XSAGDNGL35) %a %j %j\nIn AGGMAP %1p, the hierarchy dimension QDR over dimension %2p must be specified for every relation dimensioned by that hierarchy dimension."
// *Cause: Multiple dimensions share the same hierarchy dimension, but it is
// only qualified within a subset of the AGGMAP relations.
// *Action: Adjust the AGGMAP so that it uses consistent qualified data references.
33074, 00000, "(XSAGDNGL36) %a %j %j %ld\nIn AGGMAP %1p, the offset %3p is not a valid offset into dimension %2p."
// *Cause: The hierarchy dimension offset is an invalid dimension position.
// *Action: Adjust the AGGMAP so that it uses valid qualified data references.
33076, 00000, "(XSAGDNGL37) %a %j %j %v\nIn AGGMAP %1p, the value '%3p' is not a valid value of dimension %2p."
// *Cause: The hierarchy dimension offset is an invalid dimension position.
// *Action: Adjust the AGGMAP so that it uses valid qualified data references.
33078, 00000, "(XSAGDNGL39) %a %j %q\nIn AGGMAP %1p, the hierarchy dimension QDR %2p must refer to a dimension."
// *Cause: The user specified an invalid qualified data reference for the hierarchy dimension.
// *Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference.
33080, 00000, "(XSAGDNGL40) %a %j %j\nIn AGGMAP %1p, you cannot reference dimension %2p with both a RELATION statement and a DIMENSION statement."
// *Cause: The user included both RELATION and DIMENSION statements in
// the AGGMAP referring to the same AGGMAP.
// *Action: Remove one of the conflicting clauses.
33082, 00000, "(XSAGDNGL41) %a %j %n\nIn AGGMAP %1p, the non-dimensioned valueset %2p must have a parent QDR in its VALUESET statement over the VALUESET's base dimension."
// *Cause: The VALUESET statement specified a scalar valueset
// but did not include a qualified data reference to specify the parent.
// *Action: Add a qualified data reference specifying the parent to the VALUESET statement.
33084, 00000, "(XSAGDNGL42) %a %j %j\nIn AGGMAP %1p, you cannot qualify the dimensioned valueset %2p."
// *Cause: The VALUESET line referred to a dimensioned valueset.
// *Action: Use a non-dimensioned valueset to limit the status of the
// dimensioned one.
/// XSAGINIT and XSAGCOMP messages (379-539) from xsagcomp.c
33086, 00000, "(XSAGINIT01) %a %j %j\nAGGMAP %1p cannot be dimensioned by a conjoint dimension."
// *Cause: The specified AGGMAP was dimensioned by
// a conjoint dimension.
// *Action: Use the CHGDFN command to change the conjoint to a composite dimension.
33088, 00000, "(XSAGINIT03) You do not have read permission for AGGMAP object %j."
// *Cause:
// *Action:
33090, 00000, "(XSAGINIT05) %a %j %j\nYou must have read permission for %1p to use AGGMAP %2p."
// *Cause:
// *Action:
33092, 00000, "(XSAGCOMP04) %v is not the name of a MODEL in any attached analytic workspace."
// *Cause: An invalid model name was attached to an AGGMAP.
// *Action: Remove the model from the AGGMAP or create a model with that name.
33094, 00000, "(XSAGGMAPLIST01) Your expression uses too much execution space. Eliminate recursion or reduce the levels of nesting."
// *Cause: formulas likely refer to each other recursively or with a great
// deal of depth.
// *Action: eliminate recursion and flatten formula trees.
33098, 00000, "(APABBR01) %a %V %j\nA value of '%1p' is not valid for the %2p option."
// *Cause: An inappropriate value was specified for the
// named option.
// *Action: Set a legal value for the option.
33100, 00000, "(APABBR02) %a %d %j\nValue '%1p' is not valid for the %2p option."
// *Cause: An inappropriate value was specified for the
// named option.
// *Action: Set a legal value for the option.
33106, 00000, "(APESCBAS01) '%i' is not a valid value for the ESCAPEBASE option. Valid values are 'd' and 'x'."
// *Cause:
// *Action:
33108, 00000, "(APFTMAX01) MAXFETCH must be between 1,000 and 2,147,483,647."
// *Cause:
// *Action:
33110, 00000, "(APXPKTSZ01) XAPIBUFFER must be between 1,000 and 64,512."
// *Cause:
// *Action:
33112, 00000, "(APFTBUFF01) FETCHBUFFER must be between 1,000 and 64,512."
// *Cause:
// *Action:
33114, 00000, "(APLIKESC01) %i is not a valid value for the LIKEESCAPE option because it is more than one character long."
// *Cause:
// *Action:
33116, 00000, "(APMSTYPE00) MODSIMULTYPE must be either AITKENS or GAUSS."
// *Cause:
// *Action:
33118, 00000, "(APMTOLER00) Value %d is out of range for MODTOLERANCE."
// *Cause:
// *Action:
33120, 00000, "(APMOVFLO00) Value %d is out of range for MODOVERFLOW."
// *Cause:
// *Action:
33122, 00000, "(APMGAMMA00) MODGAMMA must be a whole number greater than or equal to zero."
// *Cause:
// *Action:
33124, 00000, "(APMITERS00) MODMAXITERS must be a whole number greater than zero."
// *Cause:
// *Action:
33126, 00000, "(APMDAMPF00) MODDAMP must be greater than or equal to zero and less than one."
// *Cause:
// *Action:
33128, 00000, "(APMERROR00) MODERROR must be either STOP, CONTINUE, or DEBUG."
// *Cause:
// *Action:
33130, 00000, "(APMERROR01) The current connection type does not support interactive debugging."
// *Cause:
// *Action:
33132, 00000, "(APPGMGR00) %a %j %d\nThe %1p option value must be between 0 and %2p."
// *Cause:
// *Action:
33134, 00000, "(APSORTBUFSZ01) %a %d %d\nThe value of SORTBUFFERSIZE must represent a number between 0 and %1p. You supplied %2p."
// *Cause:
// *Action:
33136, 00000, "(APSPARSX01) The value of SPARSEINDEX cannot be a multi-line string."
// *Cause:
// *Action:
33138, 00000, "(APSPARSX02) The value '%v' is not valid for SPARSEINDEX."
// *Cause:
// *Action:
33140, 00000, "(AUTOCOMP1) %n is being compiled automatically."
// *Cause:
// *Action:
33141, 00000, "(XSAWFREEZE1) The analytic workspace %s is already frozen."
// *Cause: Attempting to freeze an AW when it is already frozen
// *Action: Thaw the AW before freezing it again.
33142, 00000, "(BADSYN00) The format of the %t command is incorrect."
// *Cause:
// *Action:
33143, 00000, "(XSAWFREEZE2) The analytic workspace %s must be attached RW or RX."
// *Cause: The AW must be updatable to change the freeze state
// *Action: Reattach AW before freezing or thawing it again.
33144, 00000, "(BADSYN01) The format of the %t command is incorrect."
// *Cause:
// *Action:
33145, 00000, "(XSAWFREEZE3) Cannot rollback analytic workspace %s; generations are in use."
// *Cause: One or more generations due to be destroyed as part of a rollback
// to freeze command are currently in use.
// *Action: Get sessions using those generations to detach the AW.
33146, 00000, "(BINENG00) The width argument for binary conversion can only be specified for INTEGER and BOOLEAN data."
// *Cause:
// *Action:
33147, 00000, "(XSAWFREEZE4) The analytic workspace %s is not frozen."
// *Cause: You are attempting to "rollback to freeze" an AW that is not
// frozen.
// *Action: Only execute this command on a frozen AW.
33148, 00000, "(BINENG01) The width argument for binary conversion must be 1, 2, or 4."
// *Cause:
// *Action:
33150, 00000, "(BOOLTOK01) %t is not a Boolean."
// *Cause:
// *Action:
33152, 00000, "(CDELETE03) %a %j %ld\nThe %1p dimension does not have a value at position %2p."
// *Cause:
// *Action:
33154, 00000, "(CFINDVAL01) The %j dimension does not have identifiers."
// *Cause:
// *Action:
33156, 00000, "(CFINDVAL02) %a %v %v\nPosition %2p\nin dimension %1p\nexceeds 2**63."
// *Cause:
// *Action:
33158, 00000, "(CGETPOS02) %a %j %ld\nThe %1p dimension does not have a value numbered %2p."
// *Cause:
// *Action:
33160, 00000, "(CGETSEQ02) %a %j %ld\nThe %1p dimension does not have a value at position %2p."
// *Cause:
// *Action:
33162, 00000, "(CGFIN00) principal-value"
// *Cause:
// *Action:
33164, 00000, "(CGFIN01) asset-value"
// *Cause:
// *Action:
33166, 00000, "(CGFIN02) The number of periods of the %t function cannot be dimensioned by time."
// *Cause:
// *Action:
33168, 00000, "(CGFIN03) The salvage value argument of the %t function must be dimensioned by the time dimension."
// *Cause:
// *Action:
33170, 00000, "(CGFIN04) The decline factor argument of the %t function cannot be dimensioned by the time dimension."
// *Cause:
// *Action:
33172, 00000, "(CGFIN05) The portion argument of the %t function cannot be dimensioned by time."
// *Cause:
// *Action:
33174, 00000, "(CGFIN06) The switch period argument of the DEPRDECLSW function cannot be dimensioned by time."
// *Cause:
// *Action:
33176, 00000, "(CGMCALC01) The member list expression in aggregation phrase %d is multidimensional."
// *Cause:
// *Action:
33178, 00000, "(CGMCALC02) %j appears as the dimension of more than one member list expression."
// *Cause:
// *Action:
33180, 00000, "(CGMCALC03) WEIGHTBY can only be specified for the AVERAGE aggregation method."
// *Cause:
// *Action:
33182, 00000, "(CGMCALC04) The base measure expression is not dimensioned by %j."
// *Cause:
// *Action:
33184, 00000, "(CGMCALC05) A valueset argument to MCALC must have one dimension and be a valueset of the same dimension."
// *Cause:
// *Action:
33186, 00000, "(CGMODSET01) The ACROSS option is not supported in model equations."
// *Cause:
// *Action:
33188, 00000, "(CGMODSET02) %a %j %v %j\nThe left-hand side of an equation involves the %1p dimension, whereas the '%2p' term on the right-hand side involves %3p."
// *Cause:
// *Action:
33190, 00000, "(CGMODSET03) An internal error caused the model assignment code generator to be called, but no MODEL is currently being compiled."
// *Cause:
// *Action:
33192, 00000, "(CGTCVT00) TCONVERT requires an argument dimensioned by time."
// *Cause:
// *Action:
33194, 00000, "(CGTCVT01) The argument to TCONVERT cannot be dimensioned by more than a single time dimension."
// *Cause:
// *Action:
33196, 00000, "(CGTCVT03) Invalid conversion method for TCONVERT."
// *Cause:
// *Action:
33198, 00000, "(CGTCVT04) The two conversion methods requested of TCONVERT are incompatible."
// *Cause:
// *Action:
33200, 00000, "(CGTCVT05) You cannot convert by both DAY and PERIOD. You must use one or the other."
// *Cause:
// *Action:
33202, 00000, "(CGTCVT06) The breakout dimension %j is not a time dimension."
// *Cause:
// *Action:
33204, 00000, "(CGTCVT07) %a %j %j\nIn converting data from time dimension %1p to %2p using TCONVERT, a conversion direction must be given."
// *Cause:
// *Action:
33206, 00000, "(CGTCVT08) %a %j %j\nIt is not possible to convert data dimensioned by %1p to be dimensioned by %2p."
// *Cause:
// *Action:
33208, 00000, "(CGTDF00) You can only find the start or end of a time period."
// *Cause:
// *Action:
33210, 00000, "(CGTDF01) The argument of the BEGINDATE or ENDDATE function must be dimensioned by exactly one time dimension."
// *Cause:
// *Action:
33213, 00000, "(CINSERT06) The target position for MAINTAIN ADD or MAINTAIN MOVE cannot fall in the range of session-only values."
// *Cause: The user specified a BEFORE or AFTER clause specifying a position in
// the range of SESSION dimension values.
// *Action: Do not use a position clause, or specify a position before the
// first SESSION value.
33214, 00000, "(CINSERT02) The %j dimension is too large."
// *Cause: The dimension has too many values.
// *Action: Deleted values can still take up space in the dimension and cause
// this error. Try removing the deleted values by exporting the
// dimension to EIF and reimporting it with the REPLACE DELETE option.
33215, 00000, "(CINSERT07) You cannot add session-only values to the %j dimension."
// *Cause: The user tried to add a SESSION dimension value while a spreadsheet
// spreadsheet cursor was open.
// *Action: Try adding the SESSION value while the cursor is not active.
33216, 00000, "(CINSERT03) %a %j %ld\nThe %1p dimension does not have a value numbered %2p."
// *Cause:
// *Action:
33217, 00000, "(CINSERT20) %a %j\nCustom member values cannot be added to concat dimension %1p, or to any of its bases, because it is not defined as UNIQUE."
// *Cause: Only UNIQUE concat dimensions can have custom member values.
// *Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry.
33218, 00000, "(CINSERT04) %a %K %j %d %d\n%1p is not a valid value for the %2p dimension. Values for this dimension can have at most %3p significant digits after rounding to %4p decimal places."
// *Cause: The user attempted to insert a value that
// had too many digits into a NUMBER dimension. For instance, the user might have tried to insert the
// value 99999 (5 digits) into a dimension with data type NUMBER(4).
// *Action: Use a smaller number for the dimension value, or define a
// new dimension with a larger precision and replace the old dimension
// with the new one.
33219, 00000, "(CINSERT05) %a %K %j %j %j\n%1p cannot be added to %2p because it is already a value of the dependent UNIQUE concat dimension %3p, from leaf dimension %4p."
// *Cause: A value cannot be added to a dimension if it conflicts with an
// existing value in a unique concat dimension containing this dimension.
// *Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE,
// or either of the duplicate values could be renamed to make them UNIQUE.
33220, 00000, "(CLOPEN01) %a %j %s\nThe time dimension %1p cannot be accessed because it consists of time periods not recognized in this release of %2p."
// *Cause:
// *Action:
33222, 00000, "(CLOPEN02) %a %j %s\nThe dimension %1p cannot be accessed because it was created by an incompatible version of %2p."
// *Cause:
// *Action:
33223, 00000, "(CMOVE03) You cannot move a session-only dimension value."
// *Cause: The user named a SESSION dimension value in the MAINTAIN MOVE
// command.
// *Action: Do not try to MAINTAIN MOVE session-only dimension values.
33224, 00000, "(CMOVE02) %a %j %ld\nThe %1p dimension does not have a value at position %2p."
// *Cause:
// *Action:
33226, 00000, "(COLDEL01) %a %d %d\nThe starting column must be between 1 and the maximum width of a text value (%1p). You cannot start removing at column %2p."
// *Cause:
// *Action:
33228, 00000, "(COLDEL02) %a %d %d\nThe columns to be removed must be between 1 and the maximum width of a text value (%1p). You cannot remove column %2p."
// *Cause:
// *Action:
33230, 00000, "(COLDEL03) The number of columns to be removed must be greater than zero. You cannot remove %d columns."
// *Cause:
// *Action:
33232, 00000, "(COLEXTR01) %a %d %d\nThe starting column must be between 1 and the maximum width of a text value (%1p). %2p is out of range."
// *Cause:
// *Action:
33234, 00000, "(COLEXTR02) %a %d %d\nThe columns to be extracted must be between 1 and the maximum width of a text value (%1p). You cannot extract column %2p."
// *Cause:
// *Action:
33236, 00000, "(COLEXTR03) The number of columns to be extracted must be greater than or equal to zero. You cannot extract %d columns."
// *Cause:
// *Action:
33238, 00000, "(COLINS01) %a %d %d\nThe starting column must be between 0 and the maximum width of a text value (%1p). You cannot start inserting at column %2p."
// *Cause:
// *Action:
33240, 00000, "(COLREP01) %a %d %d\nThe starting column must be between 1 and the maximum width of a text value (%1p). You cannot start replacing at column %2p."
// *Cause:
// *Action:
33242, 00000, "(COMPOSITE01) %j is a dimension composite and does not have position numbers that can be used in this context."
// *Cause:
// *Action:
33243, 00000, "(XSDPART51) %j is a PARTITION TEMPLATE and does not have position numbers that can be used in this context."
// *Cause:
// *Action:
33244, 00000, "(CRENAME01) %a %j %ld\nThe %1p dimension does not have a value at position %2p."
// *Cause:
// *Action:
33246, 00000, "(CRENAME02) The %j dimension does not have identifiers that can be renamed."
// *Cause:
// *Action:
33247, 00000, "(CRENAME03) %a %K %j %j\n%1p is already a value of the dependent UNIQUE concat dimension %2p, from leaf dimension %3p."
// *Cause: A value cannot be renamed in a dimension if the new value conflicts with an
// existing value in a unique concat dimension containing this dimension.
// *Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE,
// or either of the duplicate values could be changed to make them UNIQUE.
33248, 00000, "(CTDDEL04) %a %j %d\nDeletions from time dimension %1p must occur at either end. %2p values were not deleted."
// *Cause:
// *Action:
33250, 00000, "(CTDINSRT00) You attempted to add a value that was outside the allowable range of dates for time dimension %j."
// *Cause:
// *Action:
33252, 00000, "(CTXENG00) The CONTEXT name cannot be NA."
// *Cause:
// *Action:
33254, 00000, "(CTXENG01) CONTEXT '%v' already exists."
// *Cause:
// *Action:
33256, 00000, "(CTXENG02) CONTEXT '%v' does not exist."
// *Cause:
// *Action:
33258, 00000, "(CTXENG03) %a %n %v\n%1p has not been saved in CONTEXT '%2p'."
// *Cause:
// *Action:
33260, 00000, "(DIMSHOW01) Partition %v does not exist."
// *Cause: The DIMSHOW command specified a nonexistent partition.
// *Action: Specify the name of an existing partition, or remove the PARTITION
// qualification from the DIMSHOW command.
33261, 00000, "(DIMSHOW02) A partition name may be specified only for a partitioned variable."
// *Cause: A PARTITION qualification was provided for an object other than a
// partitioned variable.
// *Action: Remove the PARTITION qualification.
33262, 00000, "(DBERR01) Analytic workspace %s does not exist, or you do not have sufficient privileges to access it."
// *Cause: The analytic workspace requested does not seem to be in the current
// database
// *Action: Check that you are in the correct schema and have access to the
// requested AW.
33263, 00000, "Could not create analytic workspace %s"
// *Cause: A serious error was encountered while trying to set up the
// tables for the named analytic workspace. Possible causes for
// this error include:
// - A tablespace that cannot be written to.
// - Corrupt metadata about which analytic workspace exist.
// - Table names that the code cannot use.
// - There are remains of a partially removed analytic workspace.
// *Action: There should be another error on the error stack. Consult this
// error to determine what is causing the problem and remove that
// table.
33264, 00000, "(DBERR02) %a %s %s\nAnalytic workspace %1p cannot be accessed because it has been damaged or belongs to an incompatible version of %2p."
// *Cause:
// *Action:
33265, 00000, "(DBERRBSZ) %a %s %d %d\nAnalytic workspace %1p cannot be opened. Tablespace blocksize %2p does not match database cache size %3p."
// *Cause: The blocksize of the containing tablespace didn't match database cache size.
// *Action: Change either size to make them consistent, or set olap_page_pool_size to 0 to allow automatic OLAP pool management when compatibility is greater than 10.2.
33266, 00000, "(DBERR03) %a %s %s\nAnalytic workspace %1p cannot be accessed because it was last modified by an incompatible version of %2p."
// *Cause:
// *Action:
33267, 00000, "(DBERRRLS) %a %s\nAnalytic workspace %1p cannot be accessed because it has fine-grained access control applied to it"
// *Cause: An attempt was made to access the specified analytic workspace's
// LOB table. The OLAP option detected the table had fine-grained
// security applied to it. The OLAP option requires full access to
// this table to operate correctly.
// *Action: Remove the fine-grained access control.
33268, 00000, "(DBERRTHW) Analytic workspace %s cannot be attached with the THAW option because it was frozen with the NOTHAW option"
// *Cause: An attempt to attach the AW using the thaw option was made; the AW
// was frozen using the NOTHAW option.
// *Action: Either attempt the command again without the THAW option.
33269, 00000, "while operating on '%s'"
// *Cause: Error is raised to inform user what object was being worked on
// when an error occurred during the creation of an AW. It should
// always be signaled with 33263
// *Action: See error#33263
33270, 00000, "(DBERR05) Analytic workspace %s already exists."
// *Cause: The AW CREATE command was passed the name of an analytic
// workspace that already exists
// *Action: Specify a different name.
33271, 00000, "simulated paging error"
// *Cause: This is an internal error that should never be seen
// *Action: Contact Oracle technical support
33272, 00000, "(DBERR06) Analytic workspace %s cannot be opened."
// *Cause:
// *Action:
33273, 00000, "(XSCHKRLS01) Analytic workspace %s has open cursors and cannot be detached."
// *Cause: A session attempted to detach an analytic workspace while there
// are cursors open against it.
// *Action: Close the open cursor before attempting to close the analytic
// workspace.
33274, 00000, "(DBERR07) %a %s %s\nTimed out while trying to lock analytic workspace %1p for %2p."
// *Cause: A lock operation that was supposed to happen very quickly was taking too long. It can be due to another session being stopped while holding that lock, another session crashing while holding that lock, or an internal error.
// *Action: If another session is stopped, resume that session to let it release the lock. If another session has crashed, wait for a few minutes while PMON or SMON process is recovering that lock. Contact Oracle OLAP Support if none of the situations above apply.
33275, 00000, "Autonomous transaction query of an UPDATEd analytic workspace is not supported"
// *Cause: The user made attempt to reference an anayltic workspace that has uncommited updates within an autonomous query.
// *Action: Either COMMIT or ROLLBACK your uncommited changes, or don't use an autonomous transaction.
33276, 00000, "(DBERR08) Another user has analytic workspace %s attached."
// *Cause:
// *Action:
33277, 00000, "Could not upgrade analytic workspace %s.%s"
// *Cause: A serious error was encountered while trying to alter the
// tables for the named analytic workspace. Possible causes for
// this error include:
// - A tablespace that cannot be written to.
// - Corrupt metadata about which analytic workspace exist.
// - Table names that the code cannot use.
// - There are remains of a partially removed analytic workspace.
// *Action: There should be another error on the error stack. Consult this
// error to determine what is causing the problem and remove that
// table.
33278, 00000, "(DBERR09) Analytic workspace %s cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back."
// *Cause: There are still changes to this analytic workspace that were updated and not committed when the workspace was attached in MULTI mode.
// *Action: Either try attaching the workspace is RO or MULTI mode or commit or roll back the transaction before trying to attach the workspace in RW or EXCLUSIVE mode.
33279, 00000, "(DBERRDDP) %a %s\nAnalytic workspace %1p cannot be accessed because the AWLOB column has deduplication enabled."
// *Cause: An attempt was made to access the specific LOB table of the
// analytic workspace. The OLAP option detected that the LOB column has
// deduplication enabled. The OLAP option does not support LOB
// deduplication.
// *Action: Alter the table to disable LOB deduplication.
33280, 00000, "(DBERR10) Analytic workspace %s cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back."
// *Cause: There are still changes to this analytic workspace that were updated and not committed when the workspace was attached in RW or EXCLUSIVE mode.
// *Action: Either try attaching the workspace is RO, RW, or EXCLUSIVE mode or commit or roll back the transaction before trying to attach the workspace in MULTI mode.
33282, 00000, "(DBERR11) Cannot wait for analytic workspace %s to become available since doing so would cause a deadlock."
// *Cause: Trying to wait for the workspace to become available caused a deadlock.
// *Action: Release an analytic workspace that some other user might be waiting for before proceeding to attach this analytic workspace in this mode.
33284, 00000, "(DBERR12) %a %s %s\nAnalytic workspace %1p cannot be opened in MULTI mode before converting it by the latest version of %2p."
// *Cause: The AW is stored in 9i format.
// *Action: Convert the AW to a later format
33285, 00000, "DML operations are not permitted on analytic workspaces."
// *Cause: An attempt was made to directly modify the contents of a table
// containing an analytic workspace.
// *Action: Do not modify the table directly; let the OLAP option modify it.
33286, 00000, "(DBERR14) The specified access mode for analytic workspace %s is invalid."
// *Cause:
// *Action:
33288, 00000, "(DBERR15) Another user has incompatible access to analytic workspace %s, and the wait timeout has expired."
// *Cause: An attempt to access an analytic workspace conflicted with another
// user's access, and the timeout specified has elapsed.
// *Action: Wait until the conflicting user is done.
33290, 00000, "(DBERR17) Analytic workspace %s cannot be attached in the mode you requested because another user has it attached in an incompatible mode."
// *Cause: An attempt to access an analytic workspace conflicted with another
// user's access, and no timeout was specified
// *Action: Wait until the conflicting user is done.
33291, 00000, "(DBERRSYNC) Analytic workspace %s cannto be attached RW until a RESYNC command has brought it up to the current generation."
// *Cause: Another session has updated the analytic workspace since it was
// attached in the current session.
// *Action: Execute a RESYNC AW command to bring the analytic workspace up to
// the most recent version.
33293, 00000, "Please use the OLAP command AW TRUNCATE to truncate this table."
// *Cause: This table is part of an analytic workspace, and the OLAP option
// needs to control the truncation of the table.
// *Action: use the OLAP option to truncate the table.
33294, 00000, "(DBERR19) Analytic workspace %s cannot be created, deleted, or renamed while flashback mode is in effect."
// *Cause:
// *Action:
33295, 00000, "(DBERR20) An attached analytic workspace is blocking this command."
// *Cause: A table cannot be dropped because an analytic workspace based on this table is being attached.
// *Action: Look up the session in question in GV$AW_OLAP and kill it.
33296, 00000, "(DBERR21) Analytic workspace %s can only be attached RO while tablespace %s is READONLY."
// *Cause: The underlying tablespace of the analytic workspace is in READONLY status.
// *Action: Attach the analytic workspace in RO mode or alter the tablespace.
33297, 00000, "(DBERR22) %a %s %s\nAnalytic workspace %1p cannot be opened because it was last modified by an incompatible version of %2p."
// *Cause: The user attempted to attach an old OLAP Services analytic workspace that
// cannot be converted by this version of OLAP Services.
// *Action: Either create a new analytic workspace or try using a version of OLAP
// Services compatible with the one that created this analytic workspace.
33298, 00000, "(AWUPG01) Analytic workspace %s is already in the newest format allowed by the current compatibility setting"
// *Cause: User ran the DBMS_AW.CONVERT procedure on an analytic workspace
// that was created in or previously upgraded to the current
// compatibility mode.
// *Action: If upgrading the analytic workspace is necessary, upgrade
// the database instance and then re-run DBMS_AW.CONVERT. If the
// new features offered by upgrading the analytic workspace
// are not required, then no action is needed.
33299, 00000, "Please use DBMS_AW.AW_RENAME to rename this table."
// *Cause: This table is part of an analytic workspace, and the OLAP option
// needs to control the rename of the table.
// *Action: use the OLAP option to rename the table.
33300, 00000, "(DBERRPLAT) Analytic workspace %s encountered an error that may indicate that it was created on a different platform."
// *Cause: An attempt to transport an analytic workspace from a different
// platform failed.
// *Action: Transport the analytic workspace using a supported method, either
// by using export/import or by rebuilding it using an XML template.
33302, 00000, "(DBVALID01) SEVERE ERROR: Record %.0f multiply used."
// *Cause: The AW VALIDATE command has detected an error in the structure
// of the analytic workspace. This error will result in the
// corruption of one or more objects
// *Action: Export what you can of the analytic workspace.
33304, 00000, "(DBVALID02) Note: Record %.0f was allocated but not used. This can result in wasted space."
// *Cause: This is a benign message. The AW VALIDATE command found an
// analytic workspace has some inaccessible space.
// *Action: Either nothing, or export and recreate the analytic workspace
33305, 00000, "(DBVALID06) Note: Record %.0f was allocated but not used. This can result in wasted space. (PS %ld)"
// *Cause: This is a benign message. The AW VALIDATE command found an
// analytic workspace has some inaccessible space.
// *Action: Either nothing, or export and recreate the analytic workspace
33306, 00000, "(DBVALID03) The AW VALIDATE command cannot be used with read-only analytic workspace %s."
// *Cause: The AW VALIDATE command does not support read-only access.
// *Action: Attach the analytic workspace read/write and try again.
33308, 00000, "(DBVALID04) SEVERE ERROR: Record %.0f used but not allocated"
// *Cause: The AW VALIDATE command has detected a problem that will result
// in corruption of the analytic workspace. There is no corruption
// yet.
// *Action: Export and recreate the analytic workspace.
33309, 00000, "(DBVALID05) SEVERE ERROR: Record %.0f used but not allocated (PS %ld)"
// *Cause: The AW VALIDATE command has detected a problem that will result
// in corruption of the analytic workspace. There is no corruption
// yet.
// *Action: Export and recreate the analytic workspace.
33310, 00000, "(DECIMAL) %a %d %d %d %d\nThe number of decimal places must be between %2p and %3p, or %4p. It cannot be %1p."
// *Cause:
// *Action:
33312, 00000, "(DELDENT01) %n cannot be deleted while there are objects dimensioned by it, or formulas, programs, valuesets, or relations that use it."
// *Cause:
// *Action:
33313, 00000, "(DELDENT05) %n cannot be deleted because it is the target of an external partition of a partitioned variable."
// *Cause: User attempted to delete a variable, but some partitioned variable
// was defined to use that variable as the target of one of its
// external partitions.
// *Action: DELETE the partitioned variable or CHGDFN DROP PARTITION the
// the external partition from the partitioned variable, then
// delete the target variable.
33314, 00000, "(DELDENT02) %n cannot be deleted while it is executing."
// *Cause:
// *Action:
33315, 00000, "(XSDELDENTANON) %a %n %j\nYou cannot delete %1p while looping over unnamed composite %2p."
// *Cause: While looping over the named anonymous composite, an attempt was
// made to delete an object which is dimensioned by it.
// *Action: Delete the object outside of a loop over the dimension.
33316, 00000, "(DELDENT03) You cannot delete %n because you do not have PERMIT permission for it or it is readonly."
// *Cause:
// *Action:
33318, 00000, "(DELDENT04) The variable %n cannot be deleted while its NA trigger is executing."
// *Cause:
// *Action:
33320, 00000, "(DNAMELEN00) %a %s %d\nThe object name %1p has more than %2p characters."
// *Cause:
// *Action:
33324, 00000, "(DOSCMD01) The current directory is %s."
// *Cause:
// *Action:
33325, 00000, "(DOSCMD02) Current directory alias is not set."
// *Cause:
// *Action:
33332, 00000, "(DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again."
// *Cause: There is no currently active analytic workspace. The command
// that generated the error requires an active analytic workspace
// to operate on.
// *Action: Execute an AW ATTACH or AW CREATE command to establish an active
// workspace.
33334, 00000, "(DSSEXIST04) Analytic workspace %s is not attached."
// *Cause: The specified analytic workspace is currently not attached to
// the session, or the name is misspelled.
// *Action: Attach the analytic workspace with the AW ATTACH command, or
// correct the spelling of the name .
33336, 00000, "(DSSEXIST04A) Analytic workspace %t is not attached."
// *Cause: The specified analytic workspace is currently not attached to
// the session, or the name is misspelled.
// *Action: Attach the analytic workspace with the AW ATTACH command, or
// correct the spelling of the name .
33338, 00000, "(DSSEXIST05) You cannot specify the EXPTEMP analytic workspace."
// *Cause: The command requires a non-temporary analytic workspace to
// operate on.
// *Action: Specify an analytic workspace other than EXPTEMP.
33339, 00000, "You cannot detach analytic workspace %s. It is in use by an API branch."
// *Cause: The OLAP API is in a branch, and you are not allowed to detach
// the AW while the branch is active.
// *Action: End the branch before detaching the AW.
33340, 00000, "(DTINFRMT00) A format cannot be an empty string."
// *Cause:
// *Action:
33342, 00000, "(DTINFRMT01) %a %v %s\n'%1p' is not a valid format for a %2p value because it has a single angle bracket > that is not part of a field specification."
// *Cause:
// *Action:
33344, 00000, "(DTINFRMT02) %a %v %s\n'%1p' is not a valid format for a %2p value because an angle bracket < cannot be the last character."
// *Cause:
// *Action:
33346, 00000, "(DTINFRMT03) %a %v %s %i\n'%1p' is not a valid format for a %2p value because '%3p' is an unrecognized specification."
// *Cause:
// *Action:
33348, 00000, "(DTINFRMT04) %v is not a valid format because the B specifier cannot be used with a date."
// *Cause:
// *Action:
33350, 00000, "(DTINFRMT05) %a %v %i\n'%1p' is not a valid format because the '%2p' specification cannot be used with a date."
// *Cause:
// *Action:
33352, 00000, "(DTINFRMT06) %a %v %s\n'%1p' is not a valid format for a %2p value because the B specifier cannot be used with a period field."
// *Cause:
// *Action:
33354, 00000, "(DTINFRMT07) '%v' is not a valid format because the <NAME> specification can only be used once."
// *Cause:
// *Action:
33356, 00000, "(DTINFRMT08) '%v' is not a valid VNF format because it contains an ordinal specification."
// *Cause:
// *Action:
33358, 00000, "(DTINFRMT09) %a %v %i\n'%1p' is an ambiguous VNF format. The '%2p' specification must be followed by a space or separation character."
// *Cause:
// *Action:
33360, 00000, "(DTINFRMT10) '%v' is not a valid VNF format because at least two of the specifications are of the same type."
// *Cause:
// *Action:
33362, 00000, "(DTINFRMT11) '%v' is not a valid VNF format because it does not contain enough fields to match one of the defined VNF templates."
// *Cause:
// *Action:
33364, 00000, "(DTINFRMT12) '%v' is not a valid VNF format because it contains more information than is allowed."
// *Cause:
// *Action:
33366, 00000, "(DTINFRMT13) %a %v %s %i\n'%1p' is not a valid format for a %2p value because the '%3p' specification has no closing angle bracket >."
// *Cause:
// *Action:
33368, 00000, "(DTINFRMT14) %a %v %s\n'%1p' is not a valid format for a %2p value because it contains more than one line of text."
// *Cause:
// *Action:
33370, 00000, "(DTTOVC01) Unable to print dates longer than %d characters."
// *Cause:
// *Action:
33372, 00000, "(DUPCLCHK01) %j appears more than once in the dimension list."
// *Cause:
// *Action:
33374, 00000, "(DUPCLCHK02) %a %j %j\n%1p appears more than once in the dimension list. (It is also a base dimension of %2p.)"
// *Cause:
// *Action:
33376, 00000, "(DUPCLCHK03) %a %j %j %j\n%1p and %2p cannot both appear in a dimension list because they share at least one base dimension (%3p)."
// *Cause:
// *Action:
33381, 00000, "(EIFEXPRT20) You cannot EXCLUDE bases from %j, because it is not a concat dimension."
// *Cause:
// *Action:
33382, 00000, "(EIFEXPRT01) You cannot export two objects with the same name (%s)."
// *Cause:
// *Action:
33383, 00000, "(EIFEXPRT21) %a %j %j\nYou cannot EXCLUDE %1p because it is not a base of %2p."
// *Cause:
// *Action:
33384, 00000, "(EIFEXPRT02) You cannot rename a dimension (%q) when you export it."
// *Cause:
// *Action:
33385, 00000, "(EIFEXPRT22) You cannot EXCLUDE %q, because it is not a dimension."
// *Cause:
// *Action:
33386, 00000, "(EIFEXPRT03) The expression beginning with %t has no data type."
// *Cause:
// *Action:
33387, 00000, "(EIFEXPRT23) EXCLUDE or EXCLUDING can only be used following the name of a concat dimension."
// *Cause:
// *Action:
33388, 00000, "(EIFEXPRT04) The expression beginning with %t has too many dimensions."
// *Cause:
// *Action:
33389, 00000, "(EIFEXPRT24) %a %j %d %d\nConcat dimension %1p has %2p bases. You cannot EXCLUDE more than %3p of them."
// *Cause:
// *Action:
33390, 00000, "(EIFEXPRT05) There are no objects to export."
// *Cause:
// *Action:
33391, 00000, "(EIFEXPRT25) concat dimension %j has only 1 base, which cannot be EXCLUDED."
// *Cause:
// *Action:
33392, 00000, "(EIFEXPRT07) SCATTER name %q must be a text variable of one dimension shared with the expression."
// *Cause:
// *Action:
33393, 00000, "(EIFIMPRT01) Object %s exists in both the EIF file and the current analytic workspace."
// *Cause: An object with the given name was found in both the EIF file
// and the current analytic workspace.
// *Action: Rename the object in the analytic workspace that is causing the
// name conflict. If the object named in the error message belongs to a cube
// or a cube dimension, rename that cube or cube dimension.
33394, 00000, "(EIFEXPRT08) SCATTER type %q must be a text variable with the same dimension as the name."
// *Cause:
// *Action:
33396, 00000, "(EIFEXPRT09) The SCATTER expression must have at least two dimensions and be numeric if TYPE is given."
// *Cause:
// *Action:
33398, 00000, "(EIFEXPRT10) The SCATTER type value must be INTEGER, SHORTINTEGER, SHORT, or DECIMAL, not %v."
// *Cause:
// *Action:
33400, 00000, "(EIFEXPRT11) The scatter name value %v is not a valid EIF object name."
// *Cause:
// *Action:
33402, 00000, "(EIFEXPRT12) You cannot export an unnamed dimension composite by itself, but only with an object dimensioned by it."
// *Cause:
// *Action:
33404, 00000, "(EIFEXPRT13) The format for exporting an expression is:\n EXPORT expression AS name"
// *Cause:
// *Action:
33406, 00000, "(EIFEXPRT14) %q is not a legal name for an EIF file object."
// *Cause:
// *Action:
33408, 00000, "(EIFEXPRT15) You cannot use the SCATTER AS syntax because EIFVERSION is set to %d, and that version cannot import scattered objects."
// *Cause:
// *Action:
33409, 00000, "(EIFEXPRT16) Cannot use the FULLMAPID or RELATIVEMAPID syntax because NOAPI has been specified."
// *Cause: An attempt was made to specify FULLMAPID or RELATIVEMAPID syntax with the NOAPI option.
// *Action: Either specify the API option instead of NOAPI, or remove the FULLMAPID or
// RELATIVEMAPID option.
33413, 00000, "(EIFMAKEF01) You cannot export compressed composite %j because one of its bases has limited status or a PERMIT READ restriction."
// *Cause: Export of a compressed composite to an EIF file or lob failed
// because one or more of the bases had some values that were not
// in the current status. This can be caused either by a LIMIT
// command or a PERMIT READ restriction on the dimension.
// *Action: Either set the base dimensions' statuses to ALL and remove their
// PERMIT READ programs, or export using the NOAGGR keyword.
33414, 00000, "(EIFMAKEF02) %a %ld %d\n\" %1p bytes written in %2p seconds.\""
// *Document: NO
// *Cause: Used in formatting output for the LIST option of EXPORT
// *Action: None
33416, 00000, "(EIFPATHLIST) You tried to set EIFEXTENSIONPATH to one or more illegal path names."
// *Cause:
// *Action:
33420, 00000, "(EIFMAKEF03) The EXPORT command has terminated because of insufficient disk space. One or more files could not be created."
// *Cause:
// *Action:
33422, 00000, "(EIFMAKEF04) %a %s %d %s\nDue to insufficient disk space, the extension count of the EIF files(s) could not be recorded. To avoid any potential errors when the file is imported, DO NOT move, delete, or rename any of the EIF extension files. These are files of the form %1p.%3p, where %3p is the extension number. There are %2p such files."
// *Cause:
// *Action:
33424, 00000, "(EIFMAKEF05) %a %n %d\n%1p cannot be exported because EIFVERSION is set to %2p, and objects cannot have more than 6 dimensions in that version."
// *Cause:
// *Action:
33425, 00000, "(EIFMAKEF15) CAUTION: Exporting NTEXT objects using %s for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file."
// *Cause: The user exported an object with data type NTEXT, but the EIF file that
// will result from the EXPORT command is not written in Unicode. Because no
// non-Unicode file can represent all possible Unicode data, it is possible
// that some data will be lost when converting from the Unicode NTEXT object
// to the EIF file. The EIF file will be written in the character set
// indicated by the "nls_charset" argument of the EXPORT command, or, if
// no such argument is present, in the database character set.
// *Action: If the user is certain that the contents of the NTEXT object can
// be represented in the specified character set, then no action is necessary.
// Otherwise, the user can add "nls_charset 'UTF8'" to the EXPORT command
// string. This will result in the EIF file being written in UTF8 Unicode,
// which can represent all the data contained in NTEXT objects.
33426, 00000, "(EIFMAKEF06) %a %s %d\nThe expression named %1p cannot be exported because EIFVERSION is set to %2p, and objects cannot have more than 6 dimensions in that version."
// *Cause:
// *Action:
33427, 00000, "(EIFMAKEF16) CAUTION: NTEXT object %n will be exported with type TEXT."
// *Cause: User attempted to export an object whose data type is NTEXT, but
// but the EIFVERSION option indicates a version of Express / Oracle OLAP
// that does not support the NTEXT data type. The object will be exported as a
// TEXT object instead.
// *Action: No action needed.
33428, 00000, "(EIFMAKEF07) One or more SCATTER AS expressions cannot be exported because EIFVERSION is set to %d, and objects cannot have more than 6 dimensions in that version."
// *Cause:
// *Action:
33429, 00000, "(EIFMAKEF17) CAUTION: NTEXT expression will be exported with type TEXT."
// *Cause: User attempted to export an expression whose data type is NTEXT, but
// but the EIFVERSION option indicates a version of Express / Oracle OLAP
// that does not support the NTEXT data type. The expression will be exported
// as a TEXT object instead.
// *Action: No action needed.
33430, 00000, "(EIFMAKEF08) %a %j %d %s\n%1p cannot be exported because EIFVERSION is set to %2p, and that version does not use %3p objects."
// *Cause:
// *Action:
33432, 00000, "(EIFMAKEF09) %a %s %d %d\nYou cannot use the name %1p, because EIFVERSION is set to %2p. That version does not allow object names longer than %3p bytes."
// *Cause: The object name was too long for the analytic workspace format
// represented by the current setting of the EIFVERSION option.
// *Action: Change the value of the EIFVERSION option, or remove the object
// from the list of objects to be exported.
33433, 00000, "(EIFMAKEF09A) %a %s %d %d\nYou cannot use the name %1p, because EIFVERSION is set to %2p. That version does not allow object names longer than %3p characters."
// *Cause: The object name was too long for the analytic workspace format
// represented by the current setting of the EIFVERSION option.
// *Action: Change the value of the EIFVERSION option, or remove the object
// from the list of objects to be exported.
33434, 00000, "(EIFMAKEF10) %a %n %s\nYou cannot export the AGGMAP object %1p from this version of %2p to version 6.3. The internal format of an AGGMAP has changed too much."
// *Cause:
// *Action:
33436, 00000, "(EIFMAKEF11) %a %s %d\nYou cannot write an EIF file using the %1p character set, because EIFVERSION is set to %2p. That version does not support that character set."
// *Cause:
// *Action:
33438, 00000, "(EIFSPARS00) %a %d %j\n%1p values of %2p will be exported as NA, because they are not in the current status of its base dimensions."
// *Cause:
// *Action:
33440, 00000, "(EQUPDATE01) The expression for formula %j contains invalid syntax."
// *Cause:
// *Action:
33442, 00000, "(ESDREAD01) Discarding compiled code for %j because there is no NAME dimension."
// *Cause:
// *Action:
33443, 00000, "(ESDREAD14) %a %j %s\nDiscarding compiled code for %1p because analytic workspace %2p is not attached."
// *Cause: A program used an analytic workspace name in a qualified object
// name. The named analytic workspace is not attached at program run time.
// *Action: No action necessary. The program will be automatically
// recompiled. It is likely that the recompile will fail with an appropriate
// exception code, in which case the signaled condition should be
// corrected and the program re-run.
33444, 00000, "(ESDREAD02) %a %j %v\nDiscarding compiled code for %1p because %2p could not be found."
// *Cause:
// *Action:
33445, 00000, "(ESDREAD15) %a %j %j %j\nDiscarding compiled code for %1p because %2p and %3p, which were not partition-dependent when the code was compiled, are now partition-dependent."
// *Cause: Two variables are "partition-dependent" if they share any
// external partition target variables, or if one is the target of
// an external partition of the other. If object names referred to
// non-partition-dependent variables at compile time but refer to
// partition-dependent variables in the run-time context, the
// OLAP DML program, formula, or model will be automatically
// recompiled.
// *Action: None needed.
33446, 00000, "(ESDREAD03) %a %j %v %s\nDiscarding compiled code for %1p because %2p is now a %3p. It was another kind of object when the code was compiled."
// *Cause:
// *Action:
33447, 00000, "(ESDREAD16) %a %j %j %j\nDiscarding compiled code for %1p because %2p and %3p, which were partition-dependent when the code was compiled, are now not partition-dependent."
// *Cause: Two variables are "partition-dependent" if they share any
// external partition target variables, or if one is the target of
// an external partition of the other. If object names referred to
// partition-dependent variables at compile time but refer to
// non-partition-dependent variables in the run-time context, the
// OLAP DML program, formula, or model will be automatically
// recompiled.
// *Action: None needed.
33448, 00000, "(ESDREAD04) %a %j %v %s %s\nDiscarding compiled code for %1p because %2p now has %3p data, whereas it had %4p data when the code was compiled."
// *Cause: The datatype of the specified variable has changed.
// *Action: None needed.
33449, 00000, "(ESDREAD17) %a %j %v\nDiscarding compiled code for %1p because the partition method or partition dimension of %2p has changed since it was compiled."
// *Cause: The partitioning method (LIST, RANGE, or CONCAT) or the partition
// dimension of the partition template is sufficiently different
// from what it was when the code was compiled that the code must
// be recompiled.
// *Action: None needed.
33450, 00000, "(ESDREAD05) %a %j %v\nDiscarding compiled code for %1p because %2p now has more or fewer dimensions than it had when the code was compiled."
// *Cause: The dimensionality of the specified object has changed.
// *Action: None needed.
33452, 00000, "(ESDREAD06) %a %j %v %j %j\nDiscarding compiled code for %1p because %2p is now dimensioned by %3p. It was dimensioned by %4p when the code was compiled."
// *Cause: The dimensionality of the specified object has changed.
// *Action: None needed.
33454, 00000, "(ESDREAD07) %a %j %v %s %j %s %j\nDiscarding compiled code for %1p because %2p is now %3p %4p, whereas it was %5p %6p when the code was compiled."
// *Cause: The specified object has changed.
// *Action: None needed.
33456, 00000, "(ESDREAD08) %a %j %v %s %s\nDiscarding compiled code for %1p because %2p is a(n) %3p, which %4p did not expect to find in a compiled program."
// *Cause: The type of the specified object has changed.
// *Action: None needed.
33458, 00000, "(ESDREAD09) %a %j %v %s %s\nDiscarding compiled code for %1p because %2p is now type %3p, whereas it was type %4p when the code was compiled."
// *Cause: The type of the specified object has changed.
// *Action: None needed.
33460, 00000, "(ESDREAD10) %a %j %j %s\nDiscarding compiled code for %1p because object %2p is not in analytic workspace %3p."
// *Cause: The specified object is not in the same analytic workspace it
// was in when the compiled object was compiled.
// *Action: None needed.
33462, 00000, "(ESDREAD10A) %a %j %v %s\nDiscarding compiled code for %1p because object %2p is not in analytic workspace %3p."
// *Cause: The specified object was not in the same analytic workspace it
// was when the compiled object was compiled
// *Action: None needed.
33464, 00000, "(ESDREAD11) %a %j %j\nDiscarding compiled code for %1p because two external objects that were different at compile time are now the same object (%2p)."
// *Cause:
// *Action:
33466, 00000, "(ESDREAD12) %a %j %v %d\nDiscarding compiled code for %1p because model dimension %2p is not in the same analytic workspace as solution variable %3p."
// *Cause:
// *Action:
33468, 00000, "(ESDREAD13) %a %j %v %j\nDiscarding compiled code for %1p because %2p is no longer a surrogate of dimension %3p."
// *Cause: When the compiled code was saved, the specified object was a
// surrogate of a certain dimension. Now the specified object is a
// surrogate of a different dimension.
// *Action: No action needed; program automatically recompiles.
33472, 00000, "(EXPCHECK1) The %n formula cannot be edited or compiled while it is executing."
// *Cause:
// *Action:
33474, 00000, "(EXPCOMP01) The calculation expression in formula %n contains a format error."
// *Cause:
// *Action:
33475, 00000, "(EXPCOMP02) Invalid expression."
// *Cause:
// *Action:
33476, 00000, "(EXPORT00) Target file (%s) already exists. No data is being exported."
// *Cause:
// *Action:
33478, 00000, "(FCFINI02) Too many NA values exist in the input data; %s cannot fill them all."
// *Cause:
// *Action:
33480, 00000, "(FCFINI04) An error occurred while filling in the NA values in the input data."
// *Cause:
// *Action:
33482, 00000, "(FCFINI05) Calculation of starting values and handling of NA values in the input data require at least two cycles of input data."
// *Cause:
// *Action:
33484, 00000, "(FCFINI06) An error occurred while calculating starting values for the smooth, trend, and seasonal series."
// *Cause:
// *Action:
33486, 00000, "(FCFINI07) %s cannot calculate starting values from this input data."
// *Cause:
// *Action:
33488, 00000, "(FCFINI08) The forecast input has resulted in a divide-by-zero error in the calculation of the smoothed data series."
// *Cause:
// *Action:
33490, 00000, "(FCFINI09) The forecast input has resulted in a divide-by-zero error in the calculation of the seasonal index series."
// *Cause:
// *Action:
33492, 00000, "(FCINFO00) There is no saved forecast calculation for the INFO function to retrieve."
// *Cause:
// *Action:
33494, 00000, "(FCREATE01) %a %s %d\nFile %1p is already open on file unit number %2p."
// *Cause:
// *Action:
33508, 00000, "(FILEREAD01) Fileunit %d is invalid. FILEREAD and FILEVIEW can only access input files opened with the FILEOPEN function."
// *Cause:
// *Action:
33510, 00000, "(FILEREAD04) Unexpected EOF encountered in string while importing data."
// *Cause:
// *Action:
33512, 00000, "(FILESET01A) The value of the PAGESIZE option must be greater than the combined values of TMARGIN and BMARGIN."
// *Cause:
// *Action:
33514, 00000, "(FILESET02) The value of the TABEXPAND option must be between 0 and 100 inclusive. You specified %d."
// *Cause:
// *Action:
33516, 00000, "(FILESET04) You can set the %s attribute only if the fileunit is used exclusively for output."
// *Cause:
// *Action:
33520, 00000, "(FINENG01) %a %s %d\nThe number of periods specified in the %1p function must be greater then 0 and less than or equal to %2p."
// *Cause:
// *Action:
33522, 00000, "(FINENG02) The second argument of the %s function cannot be NA while the corresponding first argument is not NA."
// *Cause:
// *Action:
33524, 00000, "(FINENG03) Both the first and second arguments of the %s function must be nonnegative."
// *Cause:
// *Action:
33526, 00000, "(FINENG04) An asset value cannot be NA when the corresponding salvage value is not NA."
// *Cause:
// *Action:
33528, 00000, "(FINENG05) The asset value must be greater than the salvage value."
// *Cause:
// *Action:
33530, 00000, "(FINENG06) The first period depreciation strategy argument of the %s function cannot be NA."
// *Cause:
// *Action:
33532, 00000, "(FINENG07) The first period depreciation strategy argument of the %s function must evaluate to the word FULL or HALF."
// *Cause:
// *Action:
33534, 00000, "(FINENG08) The rate argument of payment or interest function cannot be NA while the corresponding principal argument is not NA."
// *Cause:
// *Action:
33536, 00000, "(FINENG09) Both the principal and rate arguments of the payment and interest functions must be nonnegative."
// *Cause:
// *Action:
33538, 00000, "(FINENG10) An internal error (%d) has occurred while evaluating an interest or payment function."
// *Cause:
// *Action:
33540, 00000, "(FINENG11) The decline-factor argument must be greater than 0."
// *Cause:
// *Action:
33542, 00000, "(FISOPEN01) A file identifier cannot exceed %d characters."
// *Cause:
// *Action:
33546, 00000, "(FNAMEQRY01) You must specify a file unit number for the %s option of FILEQUERY."
// *Cause:
// *Action:
// 33554 to 33559 reserved for FORCHECK, MAINTCHK, LOCKCHECK
33554, 00000, "(FORCHECK01) While looping over %j, you cannot change its status or contents."
// *Cause:
// *Action:
33555, 00000, "(FORCHECK03) While looping over alias dimension %j, you cannot change the contents of its base %j."
// *Cause:
// *Action:
33556, 00000, "(FORCHECK51) While looping over concat dimension %j, you cannot change the contents of its leaves."
// *Cause:
// *Action:
33557, 00000, "(MAINTCHK01) %a %s %j\nYou cannot %1p values of dimension %2p during a loop over it."
// *Cause: User tried to insert or delete a value of the specified dimension
// while some loop over that dimension was active. The loop could
// be an explicit FOR or ACROSS loop, or a natural expression
// evaluation or OLAP_TABLE loop. Also, it could be a loop over the
// dimension itself or over a derived dimension (like a composite
// or partition template) or dimension alias that includes it. The
// insert or delete could be explicitly caused by the MAINTAIN
// command. It is also possible that the user attempted to assign
// a value to a variable or partition dimensioned by a composite
// during a loop over that composite using a qualified data
// reference (QDR), and that the exception was generated by the
// engine's attempt to insert a new position in the composite to
// hold the new value.
// *Action: Move the dimension maintenance or QDR-based variable assignment
// outside the dimension loop.
33558, 00000, "(LOCKCHECK01) %a %j %k\nThe status or contents of the %1p dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to %2p."
// *Cause: A LIMIT or MAINTAIN was attempted on the named language dimension
// while the boolean option LOCK_LANGUAGE_DIMS was set to YES.
// *Action: SET LOCK_LANGUAGE_DIMS to NO and retry the MAINTAIN or LIMIT.
33560, 00000, "(FORECAST00) The time dimension (%n) has no values in status. The forecast cannot be calculated."
// *Cause:
// *Action:
33562, 00000, "(FORECAST01) The forecast LENGTH must be an non-NA value that is greater than or equal to zero."
// *Cause:
// *Action:
33564, 00000, "(FORECAST02) %a %d %d\nSum of forecast LENGTH and number of time dimension values in status equals %1p. The maximum is %2p."
// *Cause:
// *Action:
33566, 00000, "(FORECAST03) The values of ALPHA, BETA, and GAMMA must be greater than zero and less than or equal to one."
// *Cause:
// *Action:
33568, 00000, "(FORECAST04) The forecast PERIODICITY must be greater than or equal to 2."
// *Cause:
// *Action:
33570, 00000, "(FORECAST05) The forecast PERIODICITY must be less than or equal to the number of historical observations in the input data."
// *Cause:
// *Action:
33572, 00000, "(FORECAST07) In a forecast calculation, the time dimension (%v) must have consecutive values in status."
// *Cause:
// *Action:
33574, 00000, "(FORECAST09) %a %v %d\nThe forecast length extends beyond the end of the time dimension (%1p). Only %2p values will be calculated."
// *Cause:
// *Action:
33576, 00000, "(FORECAST10) The number of non-NA observations must be greater than 1 to calculate a TREND forecast."
// *Cause:
// *Action:
33578, 00000, "(FORECAST11) The number of positive observations must be greater than 1 to calculate an EXPONENTIAL forecast."
// *Cause:
// *Action:
33580, 00000, "(FORECAST12) %a %d %n %d\nThe number of historical periods (%1p) exceeds the number of values in the current status of %2p (%3p)."
// *Cause:
// *Action:
33582, 00000, "(FORECAST13) The number of historical periods must be a non-NA value greater than zero."
// *Cause:
// *Action:
33584, 00000, "(FORECAST100) Forecasting Analysis"
// *Cause:
// *Action:
33586, 00000, "(FORECAST101) Variable to Forecast:"
// *Cause:
// *Action:
33588, 00000, "(FORECAST102) Forecast Dimension:"
// *Cause:
// *Action:
33590, 00000, "(FORECAST103) Forecast Method:"
// *Cause:
// *Action:
33592, 00000, "(FORECAST104) Mean Absolute Percent Error:"
// *Cause:
// *Action:
33594, 00000, "(FORECAST105) Forecast Equation: "
// *Cause:
// *Action:
33596, 00000, "(FORECAST106) No forecast values can be shown since no FCNAME variable was specified to hold the results of the forecast."
// *Cause:
// *Action:
33598, 00000, "(FORECAST107) Actual Value"
// *Cause:
// *Action:
33600, 00000, "(FORECAST108) Fitted Value"
// *Cause:
// *Action:
33602, 00000, "(FORECAST109) Alpha: "
// *Cause:
// *Action:
33604, 00000, "(FORECAST110) Beta: "
// *Cause:
// *Action:
33606, 00000, "(FORECAST111) Gamma: "
// *Cause:
// *Action:
33608, 00000, "(FORECAST112) Periodicity: "
// *Cause:
// *Action:
33610, 00000, "(FORSTEP01) Program control transferred into a FOR loop from outside the loop. This transfer is not allowed."
// *Cause:
// *Action:
33612, 00000, "(FPUTENG01) The file unit operand of the FILEPUT command does not have a value."
// *Cause:
// *Action:
33614, 00000, "(FPUTENG02) File %s was opened for input only."
// *Cause:
// *Action:
33616, 00000, "(FPUTENG04) The FROM file unit operand of the FILEPUT command does not have a value."
// *Cause:
// *Action:
33618, 00000, "(FPUTENG05) There is not sufficient room on the page to write data. Check your PAGESIZE, TMARGIN, BMARGIN and header values."
// *Cause:
// *Action:
33620, 00000, "(FRACRPOS01) %a %s %s\n%1p is not a valid field option for a record in %2p format."
// *Cause:
// *Action:
33622, 00000, "(FRAPPEND01) You cannot specify a position when appending to an INTEGER dimension."
// *Cause:
// *Action:
33624, 00000, "(FRASSIGN01) %q is a WORKSHEET. You cannot use the Data Reader to assign values to it."
// *Cause:
// *Action:
33625, 00000, "(FRASSIGN02) You cannot use the APPEND keyword with concat dimension %j."
// *Cause: User used the APPEND keyword on a CONCAT target in a FILEREAD,
// SQL FETCH or SQL SELECT command.
// *Action: APPENDing a value to one of the CONCATs leaves automatically appends to the CONCAT.
33626, 00000, "(FRATPUSH01) %a %s %s\n%1p is not a valid field option for a record in %2p format."
// *Cause:
// *Action:
33628, 00000, "(FRATPUSH02) Dimension maintenance attributes can only be specified on the left side of the equal sign."
// *Cause:
// *Action:
33630, 00000, "(FRCBCHEK01) Invalid file unit %d. Files read by FILEREAD or FILEVIEW must be input files opened via the FILEOPEN function."
// *Cause:
// *Action:
33632, 00000, "(FRCBCHEK02) No current record is available for file unit %d."
// *Cause:
// *Action:
33634, 00000, "(FRCBSET01) %a %i %s\n%1p is not a valid value for the ORIGIN option of FILESET. Valid values are: %2p."
// *Cause:
// *Action:
33636, 00000, "(FRERROR01) %a %d %s\n%1p is not a valid value for %2p. Values for this attribute cannot be less than 1."
// *Cause:
// *Action:
33638, 00000, "(FRERROR02) %a %d %s %d\n%1p is not a valid value for SPACE because it results in a %2p value of %3p."
// *Cause:
// *Action:
33640, 00000, "(FRERROR03) %a %d %d %d\nThere is no field of width %1p at column %2p. The current record is only %3p bytes long."
// *Cause:
// *Action:
33642, 00000, "(FRERROR04) %a %d %s %s\n%1p is not a valid width for %2p %3p data."
// *Cause:
// *Action:
33644, 00000, "(FRERROR05) %a %s %s\nNA is not a valid width for %1p %2p data. There is no default width for this data type."
// *Cause:
// *Action:
33646, 00000, "(FRERROR06) %a %s %s\nThe string '%1p' is not a valid %2p value."
// *Cause:
// *Action:
33648, 00000, "(FRERROR07) The current packed field contains the invalid hexadecimal digit \"%c\"."
// *Cause:
// *Action:
33650, 00000, "(FRERROR08) The current packed field contains the invalid sign digit \"%c\"."
// *Cause:
// *Action:
33652, 00000, "(FRERROR09) %a %k %j\n%1p is not a valid %2p."
// *Cause:
// *Action:
33654, 00000, "(FRERROR10) %a %j %d\nThe %1p dimension does not have a value numbered %2p."
// *Cause:
// *Action:
33656, 00000, "(FRERROR11) The time dimension %j is empty. You cannot append integer positions to it unless it has at least one value."
// *Cause:
// *Action:
33658, 00000, "(FRFILPUT01) File %s is invalid. Source files for FILEPUT must be input files opened via the FILEOPEN function."
// *Cause:
// *Action:
33660, 00000, "(FRFILPUT02) %a %s %s\nYou cannot write from file %1p to file %2p, because the output file was not opened with the BINARY option."
// *Cause:
// *Action:
33662, 00000, "(FRFILPUT03) %a %s %s\nYou cannot write from file %1p to file %2p, because the output file was opened with the BINARY option."
// *Cause:
// *Action:
33664, 00000, "(FRSPARSE01) You cannot specify a dimension list for %j because it is not a conjoint dimension."
// *Cause:
// *Action:
33666, 00000, "(FRSTRDLM01) The %s expression cannot have more than one line."
// *Cause:
// *Action:
33668, 00000, "(FRSTRDLM02) %a %v %s\n%1p is not a valid value for the %2p expression."
// *Cause:
// *Action:
33670, 00000, "(FRSTRDLM03) The %s and DELIMITER expressions cannot have the same value."
// *Cause:
// *Action:
33672, 00000, "(FRSTRDLM04) A CSV DELIMITER cannot be set to a double quote or NULL."
// *Cause:
// *Action:
33674, 00000, "(FTCODE00) %a %d %d\nData block size %2p exceeds the maximum size of %1p."
// *Cause:
// *Action:
33678, 00000, "(GETSCAL00) The text expression specifying a DIMENSION data type cannot evaluate to NA."
// *Cause:
// *Action:
33680, 00000, "(GETTIMER00) first"
// *Cause:
// *Action:
33682, 00000, "(GETTIMER01) %a %t %v\nThe %2p parameter to %1p is dimensioned by more than one time dimension."
// *Cause:
// *Action:
33684, 00000, "(GETTIMER02) %a %t %v\nThe %2p parameter to %1p must be dimensioned by a time dimension, or an explicit time dimension must be given."
// *Cause:
// *Action:
33686, 00000, "(GETTIMER03) %a %t %j %v\nThe %3p parameter to %1p is not dimensioned by %2p."
// *Cause:
// *Action:
33688, 00000, "(GETTIMER04) The dimension composite %j cannot be used as a time dimension."
// *Cause:
// *Action:
33690, 00000, "(GETXVAL01) The formula %n cannot be recursively evaluated because the RECURSIVE option is set to NO."
// *Cause:
// *Action:
33692, 00000, "(GROWENG01) The growrate of an expression must be calculated over a strictly increasing time interval."
// *Cause:
// *Action:
33694, 00000, "(GROWENG02) The expression in the GROWRATE function must have non-NA values at the beginning and end of the given time interval."
// *Cause:
// *Action:
33696, 00000, "(GROWENG03) The beginning and ending values of the expression in GROWRATE must both be positive or both be negative."
// *Cause:
// *Action:
33698, 00000, "(GROWENG04) Cannot calculate the growrate for the values given"
// *Cause:
// *Action:
33700, 00000, "(GROWENG05) The beginning value of the expression in the GROWRATE function must be non zero."
// *Cause:
// *Action:
33704, 00000, "(ILPCHECK01) %n is not a program."
// *Cause:
// *Action:
33706, 00000, "(ILPCHECK12) The %n program cannot be compiled because it contains structural errors."
// *Cause:
// *Action:
33708, 00000, "(ILPCHECK13) The %n program cannot be compiled while it is executing."
// *Cause:
// *Action:
33712, 00000, "(ILPCHECK22) The %n program cannot be executed because it contains structural errors."
// *Cause:
// *Action:
33720, 00000, "(ILPCHECK43) The %n program cannot be hidden or unhidden while it is executing."
// *Cause:
// *Action:
33722, 00000, "(ILPCOMP05) All %t statements must precede the first non-declarative statement."
// *Cause:
// *Action:
33724, 00000, "(ILPCOMP07) The %n program could not be compiled because of an unrecoverable error."
// *Cause:
// *Action:
33726, 00000, "(ILPENG02) %j cannot be used more than once in simultaneous or nested FOR statements or ACROSS commands."
// *Cause:
// *Action:
33728, 00000, "(ILPINIT01) You cannot initialize %j because it is currently running."
// *Cause:
// *Action:
33730, 00000, "(ILPLNK01) %a %j %d %d\nDiscarding compiled code for %1p because it was compiled with code version %2p. The current code version is %3p."
// *Cause:
// *Action:
33732, 00000, "(ILPONLY) The %s function can only be used in a program."
// *Cause:
// *Action:
33734, 00000, "(ILPPUT01) %a %t %j\nLabel %1p conflicts with at least one other label in %2p. Labels must be unique for the first 8 characters."
// *Cause:
// *Action:
33736, 00000, "(ILPPUT02) The %j program contains unmatched DO or DOEND statements."
// *Cause:
// *Action:
33738, 00000, "(ILPPUT03) Program %j contains unmatched IF, WHILE, TEMPSTAT, FOR, or THEN/ELSE statement, or duplicate labels."
// *Cause:
// *Action:
33740, 00000, "(ILPPUT04) %a %t %j\nOn the line defining label %1p in the %2p program, text following the label has been ignored."
// *Cause:
// *Action:
33742, 00000, "(ILPPUT06) %a %j %d\nThe %1p program contains too many source lines. The limit is %2p lines. The program has been truncated."
// *Cause:
// *Action:
33744, 00000, "(ILPPUT07) IMPORTANT: Program %j contains text on the same line as a DO or DOEND statement, which will be ignored."
// *Cause:
// *Action:
33746, 00000, "(ILPPUT08) %v must be preceded by an IF clause."
// *Cause:
// *Action:
33748, 00000, "(ILPPUT09) %v must be preceded by a THEN clause."
// *Cause:
// *Action:
33750, 00000, "(ILPXEQ01) A referenced object can no longer be located. Execution will continue in interpreted mode."
// *Cause:
// *Action:
33756, 00000, "(ILTRK01) No data has been recorded by the TRACKPRG command."
// *Cause:
// *Action:
33758, 00000, "(IMPQUAF0) The EIF file %s does not have any objects in it."
// *Cause:
// *Action:
33760, 00000, "(IMPQUAF02) \nThere are %d objects in the EIF file:"
33762, 00000, "(XSCHGDIM01) Invalid LIMIT argument starting at %t."
// *Cause:
// *Action:
33766, 00000, "(INFOFC00) Invalid second argument to INFO(FORECAST %t)."
// *Cause:
// *Action:
33768, 00000, "(INFOMOD00) Invalid second argument to INFO(MODEL %t)."
// *Cause:
// *Action:
33770, 00000, "(INFOPARS01) Invalid second argument to INFO(PARSE %t)."
// *Cause:
// *Action:
33772, 00000, "(INFORG00) Invalid second argument to INFO(REGRESS %t)."
// *Cause:
// *Action:
33774, 00000, "(INTERP1) %t is not a command."
// *Cause:
// *Action:
33776, 00000, "(INTERP1A) %q is not a command."
// *Cause:
// *Action:
33780, 00000, "(INTERP3) The %t command can only be used in a program."
// *Cause:
// *Action:
33782, 00000, "(INTERP4) The %t command cannot be executed by ampersand substitution."
// *Cause:
// *Action:
33784, 00000, "(INTERP5) Ampersand substitution is not permitted in a %t statement."
// *Cause:
// *Action:
33788, 00000, "(INTTOK01) %t is not composed solely of digits."
// *Cause:
// *Action:
33790, 00000, "(IOERROR01) %a %s %s\nI/O error on file %1p: %2p."
// *Cause:
// *Action:
33792, 00000, "(IOERROR02) I/O error on file %s: Error text not available."
// *Cause:
// *Action:
33796, 00000, "(IOEXECUT00) The file identifier argument of %s does not have a value."
// *Cause:
// *Action:
33798, 00000, "(IOEXECUT01) File %s is the current OUTFILE or LOG unit, and cannot be closed with the FILECLOSE command."
// *Cause:
// *Action:
33800, 00000, "(IOEXECUT02A) The LENGTH argument to the FILEGET function (%d) is negative."
// *Cause:
// *Action:
33802, 00000, "(IOEXECUT02B) File %s was opened for writing."
// *Cause:
// *Action:
33804, 00000, "(IOEXECUT02C) File %s was opened for binary input. You must use FILEREAD or FILENEXT to read data from this file."
// *Cause:
// *Action:
33806, 00000, "(IOEXECUT03A) %a %s %s\nThe %1p option of FILEQUERY is not supported in this version of %2p."
// *Cause:
// *Action:
33808, 00000, "(IOEXECUT03B) You have requested a FILEQUERY option that is not supported in this version of %s."
// *Cause:
// *Action:
33810, 00000, "(IOEXECUT04A) %a %s %s\nThe %1p option of FILESET is not supported in this version of %2p."
// *Cause:
// *Action:
33812, 00000, "(IOEXECUT04B) The %s option of a file cannot be changed by the FILESET command."
// *Cause:
// *Action:
33814, 00000, "(IOEXECUT04C) The value to be set for the %s option cannot be NA."
// *Cause:
// *Action:
33816, 00000, "(IOEXECUT04D) You have requested a FILESET option that is not supported in this version of %s."
// *Cause:
// *Action:
33818, 00000, "(IOEXECUT05) %a %d %s\nFile unit %1p is invalid. %2p can access only input files opened via the FILEOPEN function."
// *Cause:
// *Action:
33820, 00000, "(IOEXECUT06) The file name argument to %s cannot be null or blank."
// *Cause:
// *Action:
33822, 00000, "(IRR01) %a %j %d %d\nTime dimension %1p has a range in status of %2p periods. The maximum range allowed by the IRR function is %3p periods."
// *Cause:
// *Action:
33824, 00000, "(ISDBUILD01) A local scalar named %t already exists."
// *Cause:
// *Action:
33826, 00000, "(LINEDEL01) The number of the first line to remove must be between 1 and the expression's total number of lines. %d is out of range."
// *Cause:
// *Action:
33828, 00000, "(LINEDEL02) You must remove at least one line. You cannot remove %d lines."
// *Cause:
// *Action:
33830, 00000, "(LINEINS01) The line number after which inserting begins (%d) is negative."
// *Cause:
// *Action:
33832, 00000, "(LINEREP01) The number of the first line to replace must be between 1 and the expression's total number of lines. %d is out of range."
// *Cause:
// *Action:
33834, 00000, "(LINEXTR01) The line number of the first line to extract must be greater than 0. You cannot start extracting at line %d."
// *Cause:
// *Action:
33836, 00000, "(LINEXTR02) You must extract at least one line. You cannot extract %d lines."
// *Cause:
// *Action:
33838, 00000, "(LLPINIT05) You attempted to loop over the time dimension %j beyond the allowable range of dates."
// *Cause:
// *Action:
33840, 00000, "(LOOPCODE01) %a %j %j %j\nMultiple relations exist between %1p and the dimensions of the expression to be aggregated. One is %2p, and another is %3p."
// *Cause:
// *Action:
33842, 00000, "(LOOPCODE02) %j cannot be used for aggregation. It is unrelated to the data's dimensions, or it is less aggregate than one of them."
// *Cause:
// *Action:
33844, 00000, "(LOOPCODE03) %a %j %j\nTime dimensions %1p and %2p are both dimensions of the data. Breaking out the aggregation by time is ambiguous."
// *Cause:
// *Action:
33846, 00000, "(LXNXTREC00) The input line was terminated by an end-of-file that occurred sooner than expected. The line might be incomplete."
// *Cause:
// *Action:
33848, 00000, "(LXNXTREC01) The input line was truncated to the maximum allowable size of %d characters."
// *Cause:
// *Action:
33852, 00000, "(LXPARSE01) You provided extra input starting at '%t'."
// *Cause:
// *Action:
33854, 00000, "(LXTOKEN01) The statement cannot be parsed because it is too long or too complex."
// *Cause:
// *Action:
33856, 00000, "(LXSUBST01) %t is not a valid ampersand-substitution expression."
// *Cause:
// *Action:
33858, 00000, "(LXSUBST02) The value of the ampersand-substitution expression is NA."
// *Cause:
// *Action:
33860, 00000, "(MAKEDCL01) You have no current analytic workspace. You must attach or create an analytic workspace before defining a new object."
// *Cause:
// *Action:
33862, 00000, "(MAKEDCL02) You must specify a data type when you define a %s."
// *Cause:
// *Action:
33864, 00000, "(MAKEDCL03) You cannot use the data type attribute when you define a %s."
// *Cause:
// *Action:
33866, 00000, "(MAKEDCL04) Your current analytic workspace does not contain an object named %j."
// *Cause:
// *Action:
33868, 00000, "(MAKEDCL05) You must specify two or more dimensions when you supply a dimension list for a WORKSHEET."
// *Cause:
// *Action:
33870, 00000, "(MAKEDCL06) %a %s %s\nYou cannot use the %1p attribute when you define a %2p."
// *Cause:
// *Action:
33872, 00000, "(MAKEDCL07) The %s DIMENSION must have a data type (ID, NTEXT, TEXT, NUMBER, DATETIME, TIMESTAMP, or INTEGER), a time period, or a list of bases for a conjoint dimension."
// *Cause:
// *Action:
33874, 00000, "(MAKEDCL08) %s is not the name of a valid option."
// *Cause:
// *Action:
33876, 00000, "(MAKEDCL09) %s must be an INTEGER dimension."
// *Cause:
// *Action:
33878, 00000, "(MAKEDCL10) Nested composites are not supported when compatability is 11 or greater."
// *Cause:
// *Action:
33880, 00000, "(MAKEDCL11) Dimensions specified for a WORKSHEET must be INTEGER dimensions."
// *Cause:
// *Action:
33882, 00000, "(MAKEDCL12) %a %s %s %s\nYou cannot use the %1p attribute when you define a %2p of type %3p."
// *Cause:
// *Action:
33883, 00000, "(MAKEDCL36) You cannot use the %t attribute when you define an EXTERNAL partition with an existing target."
// *Cause: User gave the TEMPORARY keyword in the definition of an external
// partition whose target variable was previously defined.
// *Action: Any storage characteristics of the external partition are
// determined by the target variable. These attributes should be
// set when the target is defined, not when the external partition
// is defined.
33884, 00000, "(MAKEDCL13) You can specify the TEMPORARY attribute only for a variable, dimension, relation, valueset, or worksheet."
// *Cause:
// *Action:
33886, 00000, "(MAKEDCL14) You cannot define an object dimensioned by NAME, because it is a special reserved dimension used to organize your analytic workspace dictionary."
// *Cause:
// *Action:
33888, 00000, "(MAKEDCL15) %a %s %s\nYou cannot use the %1p attribute when you define a fixed-width TEXT %2p."
// *Cause:
// *Action:
33890, 00000, "(MAKEDCL16) You cannot use the dimension list attribute when you define a %s."
// *Cause:
// *Action:
33892, 00000, "(MAKEDCL17) %a %s %s\nYou cannot use the %1p attribute when you define a scalar %2p."
// *Cause:
// *Action:
33893, 00000, "(MAKEDCL18) The TEMPORARY attribute cannot be specified for this type of dimension"
// *Cause:
// *Action:
33894, 00000, "(MAKEDCL20) The WIDTH attribute can only be used with non-scalar TEXT and INTEGER variables, or with TEXT dimensions."
// *Cause:
// *Action:
33895, 00000, "(MAKEDCL19) You can specify the SHAREMAP attribute only for a multiply dimensioned variable, relation, valueset, or worksheet."
// *Cause:
// *Action:
33896, 00000, "(MAKEDCL21) The WIDTH attribute for TEXT data must be a number between 1 and 4000."
// *Cause:
// *Action:
33898, 00000, "(MAKEDCL22) The WIDTH attribute for INTEGER data must be 1."
// *Cause:
// *Action:
33900, 00000, "(MAKEDCL23) The NOHASH attribute is only valid for conjoint dimensions."
// *Cause:
// *Action:
33902, 00000, "(MAKEDCL24) The %s attribute is only valid for conjoint dimensions and dimension composites."
// *Cause:
// *Action:
33904, 00000, "(MAKEDCL25) %a %j %s\n%1p is a dimension composite or is dimensioned by a dimension composite. You cannot use it as the type of a %2p."
// *Cause:
// *Action:
33908, 00000, "(MAKEDCL27) You cannot use the %s attribute when you define a DIMENSION ALIAS, CONCAT, or PARTITION TEMPLATE."
// *Cause:
// *Action:
33910, 00000, "(MAKEDCL28) You cannot specify a data type when you define a DIMENSION ALIAS, CONCAT, or PARTITION TEMPLATE."
// *Cause:
// *Action:
33911, 00000, "(MAKEDCL29) %a %s %s %s\nYou cannot define a %1p in analytic workspace %2p because it has not been upgraded to version %3p."
// *Cause: User attempted to define an object that requires a certain
// compatibility setting in an AW that has not been upgraded to that
// compatibility level.
// *Action: Make sure that the database is running in the appropriate
// compatibility mode, and upgrade the AW.
33912, 00000, "(MAKEDCL30) An AGGMAP cannot be dimensioned by a conjoint dimension."
// *Cause:
// *Action:
33914, 00000, "(MAKEDCL31) You cannot define a dimension alias of another dimension alias."
// *Cause:
// *Action:
33916, 00000, "(MAKEDCL32) The dimension alias target %j is not a simple dimension."
// *Cause:
// *Action:
33918, 00000, "(MAKEDCL33) %a %j %s\nYou cannot define a surrogate of dimension %1p because it is a %2p."
// *Cause: Not all kinds of dimensions can have surrogates. The user
// attempted to define a surrogate of a prohibited kind of dimension.
// *Action: Do not attempt to define a surrogate on this dimension.
33920, 00000, "(MAKEDCL34) The %s SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, DATETIME, TIMESTAMP, or INTEGER."
// *Cause: The user attempted to define a surrogate without specifying a valid
// data type.
// *Action: Specify the data type (ID, NTEXT, TEXT, NUMBER, or INTEGER) in the
// definition of the surrogate.
33922, 00000, "(MAKEDCL35) You cannot define a surrogate of dimension %j because it is a time dimension."
// *Cause: The user attempted to define a surrogate on a dimension that has type
// DAY, WEEK, MONTH, or YEAR.
// *Action: Do not attempt to define a surrogate on this dimension.
33934, 00000, "(MISCOPTI01) OFF"
// *Cause:
// *Action:
33936, 00000, "(MISCOPTI04) NA"
// *Cause:
// *Action:
33938, 00000, "(MISCOPTI05) Press <Enter> to continue."
// *Cause:
// *Action:
33940, 00000, "(MISCOPTI06) <DD><MTXT><YY>"
// *Cause:
// *Action:
33942, 00000, "(MODCALL01) Model %n cannot be run because another model is already active."
// *Cause:
// *Action:
33944, 00000, "(MODCALL02) Model %n needs a solution variable; one was not provided."
// *Cause:
// *Action:
33946, 00000, "(MODCALL03) Model %n does not take a solution variable, because it has no model dimensions."
// *Cause:
// *Action:
33948, 00000, "(MODCALL04) %a %n %n\nA solution variable must be provided for model %1p; however, %2p is not a variable."
// *Cause:
// *Action:
33950, 00000, "(MODCALL05) %a %n %n %s\nThe solution variable specified for the model %1p must be numeric. Variable %2p is type %3p."
// *Cause:
// *Action:
33952, 00000, "(MODCALL08) %a %n %n\nA solution variable must be specified for model %1p; however, %2p has no dimensions."
// *Cause:
// *Action:
33954, 00000, "(MODCALL09) %a %n %j %n\nSolution variable %1p is not dimensioned by %2p, which is a dimension of model %3p."
// *Cause:
// *Action:
33956, 00000, "(MODCALL10) %a %j %d\nThe execution of model %1p cannot be completed due to an internal error (TYPE = %2p)."
// *Cause:
// *Action:
33958, 00000, "(MODCALL11) The syntax for invoking a model is:\n model-name [solution-variable] [NOWARN]"
// *Cause:
// *Action:
33960, 00000, "(MODCALL14) Model %n contains simultaneous equations."
// *Cause:
// *Action:
33962, 00000, "(MODCALL15) %a %j %d %d\nModel %1p failed to converge after %2p iterations in block %3p."
// *Cause:
// *Action:
33964, 00000, "(MODCALL16) %a %j %d %d %d %j\nModel %1p diverged during iteration %2p in block %3p while executing statement %4p of model %5p."
// *Cause:
// *Action:
33966, 00000, "(MODCALL17) %a %n %n\nThe solution variable %1p is referenced as a variable in model %2p."
// *Cause:
// *Action:
33968, 00000, "(MODCALL18) %a %n %j %n\nSolution variable %1p is dimensioned by %2p, which is not a dimension of model %3p but is a dimension of a model execution block."
// *Cause:
// *Action:
33970, 00000, "(MODCALL19) %a %n %j %n\nSolution variable %1p is not dimensioned by %2p, but model %3p contains dimension-based equations that reference its values."
// *Cause:
// *Action:
33972, 00000, "(MODCHECK01) %n is not a model."
// *Cause:
// *Action:
33973, 00000, "(MODCHECK02) The %n model cannot be compiled while it is executing."
// *Cause:
// *Action:
33974, 00000, "(MODCHECK12) The %n model cannot be compiled because it contains structural errors."
// *Cause:
// *Action:
33975, 00000, "(MODCHECK13) The %n model cannot be hidden or unhidden while it is executing."
// *Cause:
// *Action:
33976, 00000, "(MODCHECK22) The %n model cannot be executed because it contains structural errors."
// *Cause:
// *Action:
33978, 00000, "(MODCOMP01) %j has already been named in a DIMENSION statement in this model."
// *Cause:
// *Action:
33980, 00000, "(MODCOMP02) DIMENSION statements are not allowed after an equation has appeared."
// *Cause:
// *Action:
33982, 00000, "(MODCOMP03) DIMENSION statements are not allowed after an INCLUDE statement has appeared."
// *Cause:
// *Action:
33983, 00000, "(MODCOMP15) The DIMENSION statement must list the dimensions of any included models."
// *Cause:
// *Action:
33984, 00000, "(MODCOMP04) INCLUDE statements are not allowed after an equation has appeared."
// *Cause:
// *Action:
33986, 00000, "(MODCOMP05) Only one INCLUDE statement is allowed in a model."
// *Cause:
// *Action:
33988, 00000, "(MODCOMP06) An INCLUDE statement must refer to another model; %n is not a model."
// *Cause:
// *Action:
33990, 00000, "(MODCOMP08) Models cannot be included recursively; %j has already been included."
// *Cause:
// *Action:
33992, 00000, "(MODCOMP09) The format of the DIMENSION command is:\n DIMENSION dimension1 [dimension2...]"
// *Cause:
// *Action:
33994, 00000, "(MODCOMP10) The format of the INCLUDE command is:\n INCLUDE model"
// *Cause:
// *Action:
33996, 00000, "(MODCOMP11) %j is not named in a DIMENSION statement in this model."
// *Cause:
// *Action:
33998, 00000, "(MODCOMP12) %a %j %j %j %j\nYou cannot use both %1p and %2p as model dimensions, because %3p is a surrogate of %4p."
// *Cause: The user attempted to include both a dimension and its surrogate in
// the DIMENSION statement of a model.
// *Action: Use either the dimension or the surrogate in the DIMENSION
// statement of the model, but not both.
34000, 00000, "(MODCOMP13) %a %j %j %j\nYou cannot use both %1p and %2p as model dimensions, because they are both surrogates of dimension %3p."
// *Cause: The user attempted to include two dimension surrogates of the same
// dimension in the DIMENSION statement of a model.
// *Action: Use either of the two surrogates in the DIMENSION statement of
// the model, but not both.
34001, 00000, "(MODCOMP14) Concat leaf dimension %j already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension."
// *Cause: Either two concat dimensions which share a common leaf dimension,
// or a concat and one of its leaves where both specified in the DIMENSION statement(s).
// *Action: Do not specify overlapping concat dimensions, or any leaves of specified concat dimensions.
34004, 00000, "(MODGRAPH01) %a %j %d\nThe model %1p cannot be compiled due to internal error %2p. Contact Oracle OLAP Technical support."
// *Cause:
// *Action:
34006, 00000, "(MODINFO00) There is no saved model information for the INFO function to retrieve."
// *Cause:
// *Action:
34008, 00000, "(MODINFO01) Model %j has not been compiled; the information requested is available only after compilation."
// *Cause:
// *Action:
34010, 00000, "(MODINFO02) Model %j has not been executed; the information requested is available only after execution."
// *Cause:
// *Action:
34012, 00000, "(MODPUT06) %a %j %d\nThe %1p model contains too many source lines. The limit is %2p lines. The model has been truncated."
// *Cause:
// *Action:
34014, 00000, "(MONITOR01) No data has been recorded by the MONITOR command."
// *Cause:
// *Action:
34016, 00000, "(MONITOR02) No program name has been supplied for the MONITOR command."
// *Cause:
// *Action:
34018, 00000, "(MSCGADD01) %j is an INTEGER dimension. Specify only the number of values to be added, not the specific values themselves."
// *Cause:
// *Action:
34019, 00000, "(MSCGADD03) %j is not a LIST PARTITION TEMPLATE."
// *Cause: User attempted to MAINTAINT ADD or DELETE a list value from a
// RANGE or CONCAT partition template.
// *Action: Partitioning in a RANGE or CONCAT partition template cannot
// be changed using the MAINTAIN command.
34020, 00000, "(MSCGADD02) %j is not a time dimension. You cannot add time periods to it."
// *Cause:
// *Action:
34021, 00000, "(MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE %j."
// *Cause: User attempted to MAINTAINT ADD or DELETE a list value from a
// LIST partition template, but didn't specify which partition
// to add to or delete from.
// *Action: Specify the partition:
// maintain (template) add to partition (partitionname) (values)
// or
// maintain (template) delete from partition (partitionname) (values)
34022, 00000, "(MSCGDEL02) You can only delete time periods from a time dimension."
// *Cause:
// *Action:
34024, 00000, "(MSCGMRG01) The RELATE keyword cannot be specified when the MERGE expression has no dimensions."
// *Cause:
// *Action:
34026, 00000, "(MSCGMRG02) %a %q %j\n%1p is not a relationship between %2p and the dimensions of the source expression."
// *Cause:
// *Action:
34028, 00000, "(MSCGMRG03) %j, the value of the RELATE relation, is not one of the dimensions of the source expression."
// *Cause:
// *Action:
34030, 00000, "(MSCGPOS00) %j is a time dimension. You can add values to it only FIRST or LAST."
// *Cause:
// *Action:
34031, 00000, "(MSCGPOS02) %j is a datetime dimension. Dimension values are automatically maintained in sorted order."
// *Cause:
// *Action:
34032, 00000, "(MSCGPOS01) %j is a dimension composite. You cannot specify a position when adding values to it."
// *Cause:
// *Action:
34034, 00000, "(MSEXECUT00B) %a %k %j\n%1p is already a value of %2p."
// *Cause:
// *Action:
34036, 00000, "(MSEXECUT00C) %a %v %j\n%1p is already a value of %2p."
// *Cause:
// *Action:
34038, 00000, "(MSEXECUT01) The expression for the position to add, merge, or delete is NA."
// *Cause:
// *Action:
34039, 00000, "(TRGPRG02) %n cannot be deleted while its trigger is executing."
// *Cause:
// *Action:
34040, 00000, "(TRGSET01) The TRIGGERASSIGN command can only be used in an ASSIGN TRIGGER."
// *Cause:
// *Action:
34041, 00000, "(TRGPRG01) A TRIGGER cannot be called recursively for the same object and event."
// *Cause:
// *Action:
34042, 00000, "(MSEXECUT03A) The expression for the position to be renamed is NA."
// *Cause:
// *Action:
34044, 00000, "(MSEXECUT03B) The expression for the new dimension value is NA."
// *Cause:
// *Action:
34046, 00000, "(MSEXECUT03C) %a %k %j\n%1p is already a value of %2p."
// *Cause:
// *Action:
34048, 00000, "(MSEXECUT04) Time dimension %j is empty. You must give it a value before you can add periods to its beginning or end."
// *Cause:
// *Action:
34050, 00000, "(MSEXECUT05) The expression for the argument to BEFORE or AFTER is NA."
// *Cause:
// *Action:
34052, 00000, "(MSEXECUT06) All dimension values must be single line values."
// *Cause:
// *Action:
34054, 00000, "(MSEXECUT07) %a %v %j\n%1p is already a value of %2p."
// *Cause:
// *Action:
34056, 00000, "(MSEXECUT08) The number of periods to add cannot be negative, zero, or NA."
// *Cause:
// *Action:
34058, 00000, "(MSEXECUT09) The number of periods to delete cannot be negative, zero, or NA."
// *Cause:
// *Action:
34059, 00000, "(MSEXECUT12) You cannot delete non session-only dimension values from unique concat dimension %j."
// *Cause: The user tried to apply MAINTAIN DELETE to a non-SESSION value.
// *Action: Only use MAINTAIN DELETE to remove SESSION values from a concat dimension.
34060, 00000, "(MSEXECUT10) You do not have permission to maintain %j."
// *Cause:
// *Action:
34061, 00000, "(MSEXECUT11) Session-only values cannot be added to non-unique concat dimension %j, or any of its base dimensions."
// *Cause: Only UNIQUE concat dimensions can have custom member values.
// *Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry.
34062, 00000, "(MXARGS01) = Args:"
// *Cause:
// *Action:
34066, 00000, "(MXARGS03) values of"
// *Cause:
// *Action:
34068, 00000, "(MXBREAK01) The BREAK statement can only be used within a FOR or WHILE loop or within a SWITCH statement."
// *Cause:
// *Action:
34070, 00000, "(MXBREAK02) The CONTINUE statement can only be used within a FOR or WHILE loop."
// *Cause:
// *Action:
34072, 00000, "(MXCALL01) %q is not a PROGRAM."
// *Cause:
// *Action:
34074, 00000, "(MXCGAF01) %a %s %s\nThe %1p function cannot be used with %2p data."
// *Cause:
// *Action:
34076, 00000, "(MXCGAF02) %n is neither a dimension nor the name of a relationship array."
// *Cause:
// *Action:
34078, 00000, "(MXCGAF03) %a %j %s\nThe dimension %1p appears more than once as an argument to %2p."
// *Cause:
// *Action:
34082, 00000, "(MXCGAF05) Specify the STATUS keyword only if at least one of the breakout dimensions is not a dimension of the expression argument."
// *Cause:
// *Action:
34084, 00000, "(MXCGAF06) You cannot specify %j as a breakout dimension because it is a dimension composite."
// *Cause:
// *Action:
34086, 00000, "(MXCGAF07) You can only specify a qualified data reference to a breakout relation object. %n is not a relation."
// *Cause:
// *Action:
34088, 00000, "(MXCGCE04) The THEN and ELSE expressions must evaluate to values of the same dimension."
// *Cause:
// *Action:
34090, 00000, "(MXCGCHRL01) %a %s %j\nThe expression argument to %1p is not dimensioned by %2p."
// *Cause:
// *Action:
34092, 00000, "(MXCGCON01) The use of a hexadecimal value (%t) is not supported."
// *Cause:
// *Action:
34094, 00000, "(MXCGCUM00) %a %n %j\nIn the CUMSUM function, the relation (%1p) must refer to the accumulation dimension (%2p)."
// *Cause:
// *Action:
34096, 00000, "(MXCGCUM01) The reset parameter '%n' is neither a RELATION nor a DIMENSION."
// *Cause:
// *Action:
34098, 00000, "(MXCGCUM02) The STATUS keyword has no effect unless the first argument has more than one dimension."
// *Cause:
// *Action:
34100, 00000, "(MXCGCVT01) Values of type %s are expected."
// *Cause:
// *Action:
34102, 00000, "(MXCGFIOF01) %a %t %s\nThe %1p option of FILEQUERY is not supported in this version of %2p."
// *Cause:
// *Action:
34104, 00000, "(MXCGGET01) %n is not a type of object that contains data values."
// *Cause:
// *Action:
34106, 00000, "(MXCGGET03) FILEREAD attributes can be specified only in the context of a FILEREAD or FILEVIEW command."
// *Cause:
// *Action:
34108, 00000, "(MXCGGET04) FILEREAD attributes cannot be specified for the NAME dimension."
// *Cause:
// *Action:
34110, 00000, "(MXCGGET05) FILEREAD attributes cannot be specified for a constant."
// *Cause:
// *Action:
34112, 00000, "(MXCGGT01) Values of type %s cannot be read with the MANY option."
// *Cause:
// *Action:
34114, 00000, "(MXCGGT02) The RAW attribute applies only to TEXT."
// *Cause:
// *Action:
34116, 00000, "(MXCGHCVT00) To convert TEXT to date use:\n CONVERT(expression DATE [dateorder])"
// *Cause:
// *Action:
34118, 00000, "(MXCGHCVT01) To convert date to TEXT or ID use:\n CONVERT(expression {ID|TEXT} [dateformat])"
// *Cause:
// *Action:
34120, 00000, "(MXCGHCVT02) To convert time dimension periods to TEXT or ID use:\n CONVERT(expression {ID|TEXT} [vnf-format])"
// *Cause:
// *Action:
34122, 00000, "(MXCGHCVT03) To convert NUMBER to TEXT or ID use:\n CONVERT(expression {ID|TEXT} [output-format])"
// *Cause:
// *Action:
34124, 00000, "(MXCGHCVT04) %a %s %s %s\nTo convert %1p to %2p use:\n CONVERT(expression %3p [format])"
// *Cause:
// *Action:
34126, 00000, "(MXCGKEY01) The first argument to the KEY function must be an expression yielding a dimension value."
// *Cause:
// *Action:
34128, 00000, "(MXCGKEY02) You cannot apply the KEY function to %j because it is not a conjoint dimension or composite."
// *Cause:
// *Action:
34130, 00000, "(MXCGKEY03) %a %j %j\n%1p is not a component of conjoint dimension %2p."
// *Cause:
// *Action:
34132, 00000, "(MXCGKEY04) %a %j %j\n%1p is not a component of composite %2p."
// *Cause:
// *Action:
34134, 00000, "(MXCGLA01) You are trying to perform an invalid operation. Dates cannot be exponentiated."
// *Cause:
// *Action:
34136, 00000, "(MXCGMOVE00) %a %t %j\nThe first argument to the %1p function is not dimensioned by %2p."
// *Cause:
// *Action:
34138, 00000, "(MXCGNPV03) The interest rate expression in the NPV function cannot be dimensioned by %j."
// *Cause:
// *Action:
34140, 00000, "(MXCGPFC01) %a %d %n\nArgument number %1p in the call to %2p is not a simple expression."
// *Cause:
// *Action:
34141, 00000, "(MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION %j."
// *Cause: User used the ASSIGN keyword on a DIMENSION target in a FILEREAD,
// SQL FETCH or SQL SELECT command.
// *Action: To create a new dimension value in a FILEREAD, SQL FETCH or
// SQL SELECT command, use the APPEND keyword.
34142, 00000, "(MXCGPUT01) You cannot assign values to a %s."
// *Cause:
// *Action:
34143, 00000, "(MXCGPUT02) You cannot assign values to SURROGATE %n because it is type INTEGER."
// *Cause: The user attempted to assign a value to a dimension surrogate whose
// data type is INTEGER. INTEGER surrogates, like INTEGER dimensions, cannot
// have values assigned to them. They can only be referenced by position.
// *Action: Do not attempt to assign values to an INTEGER surrogate. Values
// will automatically appear and disappear from the INTEGER surrogate as
// positions are added to or removed from the underlying dimension.
34144, 00000, "(MXCGPUT04) A model cannot assign values to a %s."
// *Cause:
// *Action:
34145, 00000, "(MXCGPUT03) You cannot use the APPEND keyword with SURROGATE %n."
// *Cause: User used the APPEND keyword on a SURROGATE target in a FILEREAD,
// SQL FETCH or SQL SELECT command.
// *Action: To assign a value to a SURROGATE in a FILEREAD, SQL FETCH or
// SQL SELECT command, use the ASSIGN keyword.
34146, 00000, "(MXCGQDR01) A qualified data reference (QDR) has this format:\n name(dimension1 dimvalue1 [dimension2 dimvalue2...])"
// *Cause:
// *Action:
34148, 00000, "(MXCGQDR02) %j cannot be used as a qualifier because it is a COMPOSITE or PARTITION TEMPLATE. You can use its component dimensions instead."
// *Cause:
// *Action:
34150, 00000, "(MXCGQDR05) A dimension can be named only once in a qualified data reference. %j has been named more than once."
// *Cause:
// *Action:
34152, 00000, "(MXCGQDR06) %a %q %j\nThe dimensions named in a qualified data reference must be dimensions of the qualified object. %1p is not dimensioned by %2p."
// *Cause:
// *Action:
34154, 00000, "(MXCGQDR10) %q has no dimensions, so it cannot have a qualified data reference."
// *Cause:
// *Action:
34156, 00000, "(MXCGRA00) You cannot compare time periods of different lengths or phases."
// *Cause:
// *Action:
34158, 00000, "(MXCGRA01) You cannot subtract time periods of different lengths or phases."
// *Cause:
// *Action:
34160, 00000, "(MXCGRA02) The format of the IN operator is\n <date> IN <time dimension value>."
// *Cause:
// *Action:
34162, 00000, "(MXCGRAVL01) The expression to be unraveled is not dimensioned by %j."
// *Cause:
// *Action:
34164, 00000, "(MXCGVAR01) A dimension used to define a local %s variable cannot be located. Execution cannot continue."
// *Cause: A local relation or valueset has become invalid, most probably
// because an object used by the currently executing program has
// been deleted.
// *Action: This is an internal error that should be referred to Oracle
// technical support.
34168, 00000, "(MXCGVFC01) Invalid context for the VALUE function."
// *Cause:
// *Action:
34170, 00000, "(MXCGVFC02) Data Reader attributes apply to the VALUE function only when it is used in a FILEREAD or FILEVIEW command."
// *Cause:
// *Action:
34172, 00000, "(MXCGWKDT01) The argument to the WKSDATA function must be the name of a WORKSHEET."
// *Cause:
// *Action:
34176, 00000, "(MXCHGDCL01) %n is not the kind of object whose index type can be changed."
// *Cause:
// *Action:
34177, 00000, "(MXCHGDCL19) %v cannot be deleted because one or more partitioned variables instantiate it."
// *Cause: User attempted to CHGDFN DELETE a partition template, but some
// partitioned variable had data in the partition specified for
// deletion.
// *Action: Drop the partitions that are causing the problem, then retry.
34178, 00000, "(MXCHGDCL02) %n cannot be changed to NOHASH. Only an object that was originally defined as NOHASH can be changed back to NOHASH."
// *Cause:
// *Action:
34179, 00000, "(MXCHGDCL20) %j is not a PARTITION TEMPLATE."
// *Cause: User specified an object that is not a partition template where
// a partition template is required.
// *Action: Supply the name of a partition template.
34181, 00000, "(MXCHGDCL21) %n is not a partitioned VARIABLE."
// *Cause: User specified an object that is not a partitioned variable in a
// place where a partitioned variable is required.
// *Action: Supply the name of a partitioned variable.
34182, 00000, "(MXCHGDCL04) %a %n %s\nWrong number of dimensions for %1p; segwidth not changed from: %2p"
// *Cause:
// *Action:
34183, 00000, "(MXCHGDCL22) Partition %v already exists."
// *Cause: User attempted to ADD a partition that already existed to a
// partitioned variable.
// *Action: None required - the partition already exists.
34184, 00000, "(MXCHGDCL05) %t is not a valid segment width."
// *Cause:
// *Action:
34185, 00000, "(MXCHGDCL23) Only dimension composites can have optional inversions. %n is not a dimension composite."
// *Cause:
// *Action:
34186, 00000, "(MXCHGDCL06) You cannot change %j to a dimension composite, because it is used as the type of a PROGRAM, RELATION or VALUESET."
// *Cause:
// *Action:
34187, 00000, "(MXCHGDCL06) REUSE cannot be specified for dimensions that already have deletions."
// *Cause:
// *Action:
34188, 00000, "(MXCHGDCL07) Only conjoint dimensions can be redefined as composites. %n is not a conjoint dimension."
// *Cause:
// *Action:
34190, 00000, "(MXCHGDCL08) You cannot convert the conjoint dimension %n to a composite because it has the NOHASH attribute."
// *Cause:
// *Action:
34192, 00000, "(MXCHGDCL09) %n is a dimension composite and its definition cannot be changed to NOHASH."
// *Cause:
// *Action:
34194, 00000, "(MXCHGDCL10) You cannot change %n to a composite while there are permissions applied to it."
// *Cause:
// *Action:
34196, 00000, "(MXCHGDCL11) Only dimension composites can be redefined as DIMENSIONs. %n is not a dimension composite."
// *Cause:
// *Action:
34198, 00000, "(MXCHGDCL12) You cannot change %n to a composite because its dimension list has one or more duplications."
// *Cause:
// *Action:
34200, 00000, "(MXCHGDCL13) You cannot change %j to a dimension composite because there are one or more formulas dimensioned by it."
// *Cause:
// *Action:
34202, 00000, "(MXCHGDCL14) %n is not a time dimension."
// *Cause:
// *Action:
34204, 00000, "(MXCHGDCL15) %n is not the kind of object to which SEGWIDTH can be applied."
// *Cause:
// *Action:
34206, 00000, "(MXCHGDCL16) You cannot change %j to a dimension composite because there are one or more relations dimensioned by it."
// *Cause:
// *Action:
34208, 00000, "(MXCHGDCL17) You cannot change %j to a dimension composite because it is used in one or more CONCATENATE or MERGE dimensions."
// *Cause:
// *Action:
34210, 00000, "(MXCHGDCL18) You cannot change %j to a dimension composite because one or more surrogates has been defined for it."
// *Cause: The user attempted to redefine a conjoint dimension as a composite, but
// the conjoint has one or more surrogates defined. A dimension that has
// surrogates cannot be redefined as a composite.
// *Action: Either delete all surrogates for the dimension, or do not attempt
// to redefine the dimension as a composite.
34212, 00000, "(MXCLASS01) An expression was specified where a DIMENSION or a VALUESET was expected."
// *Cause:
// *Action:
34214, 00000, "(MXCLASS02) %n is not a dimension."
// *Cause:
// *Action:
34216, 00000, "(MXCOMP001) %n cannot be compiled because it is not a PROGRAM, MODEL, AGGMAP, or FORMULA."
// *Cause:
// *Action:
34218, 00000, "(MXCTX01) %n cannot be in a CONTEXT because it is not a scalar variable."
// *Cause:
// *Action:
34220, 00000, "(MXCTX02) %n cannot be in a CONTEXT because it is not data."
// *Cause:
// *Action:
34222, 00000, "(MXCTX03) %n cannot be in a CONTEXT because it is a dimension composite."
// *Cause:
// *Action:
34224, 00000, "(MXDCL01) Analytic workspace %s is not attached."
// *Cause:
// *Action:
34226, 00000, "(MXDCL02) REUSE can only be specified for SIMPLE, COMPOSITE, and CONJOINT dimensions."
// *Cause:
// *Action:
34228, 00000, "(MXDCL03) Only dimensions can have time periods."
// *Cause:
// *Action:
34230, 00000, "(MXDCL04) You provided an invalid time period."
// *Cause:
// *Action:
34232, 00000, "(MXDCL05) A DAY dimension cannot be phased with a BEGINNING or ENDING phrase."
// *Cause:
// *Action:
34234, 00000, "(MXDCL06) Beginning date translates to an invalid end date."
// *Cause:
// *Action:
34236, 00000, "(MXDCL07) REUSE cannot be specified in AWs that have not been upgraded to version 12."
// *Cause:
// *Action:
34238, 00000, "(MXDCL08) A dimension cannot have a data type of DATE."
// *Cause:
// *Action:
34240, 00000, "(MXDCL09) You cannot specify EXPTEMP as an analytic workspace."
// *Cause:
// *Action:
34242, 00000, "(MXDCL10) You cannot specify an analytic workspace in this command."
// *Cause:
// *Action:
34243, 00000, "(MXDCL11) You can only use the %t keyword when defining a COMPOSITE."
// *Cause: User supplied the COMPRESSED keyword when defining an object
// that was not a COMPOSITE.
// *Action: If the intent is to create a compressed composite, make sure
// that the object type is COMPOSITE. Otherwise, remove the
// COMPRESSED keyword from the command string and rerun.
34246, 00000, "(MXDCL18) You cannot define an object with a recursive SPARSE dimension list."
// *Cause:
// *Action:
34248, 00000, "(MXDCL19) You cannot specify a dimension list for the %j dimension."
// *Cause:
// *Action:
34250, 00000, "(MXDCL20) The %j dimension is in the wrong analytic workspace to be used in this DEFINE command."
// *Cause:
// *Action:
34252, 00000, "(MXDCL21) You have specified the wrong number of dimensions for %j."
// *Cause:
// *Action:
34254, 00000, "(MXDCL22) %a %j %j\n%1p does not belong in the dimension list for composite %2p, or it is in the wrong position."
// *Cause:
// *Action:
34256, 00000, "(MXDCL23) %a %s %j\nYou must specify a dimension list for %1p %2p when using it in a definition."
// *Cause:
// *Action:
34258, 00000, "(MXDCL24) Dimension composite %v does not exist."
// *Cause:
// *Action:
34260, 00000, "(MXDCL25) %a %v %s\nYou cannot use %1p to dimension a %2p because it is, or involves, a dimension composite. Use the composite's bases instead."
// *Cause: The user attempted to use a COMPOSITE in the dimension list of
// an object that does not allow for such dimensions.
// *Action: Use the base dimensions of the COMPOSITE in the dimension list.
34262, 00000, "(MXDCL26) %a %t %t %s\nThe object name %1p!%2p can only be defined in analytic workspace %3p, not in the EXPRESS analytic workspace."
// *Cause:
// *Action:
34264, 00000, "(MXDCL27) %a %t %t %s %s\nThe object name %1p!%2p can only be defined in analytic workspace %3p, not in analytic workspace %4p."
// *Cause:
// *Action:
34268, 00000, "(MXDCL29) %s objects must be type DIMENSION."
// *Cause:
// *Action:
34270, 00000, "(MXDCL30) You cannot specify a data type when defining a dimension alias."
// *Cause:
// *Action:
34272, 00000, "(MXDCL31) You cannot specify a dimension list when defining a dimension %s."
// *Cause:
// *Action:
34274, 00000, "(MXDCL32) You cannot specify a width when defining a dimension alias."
// *Cause:
// *Action:
34276, 00000, "(MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension."
// *Cause: The user attempted to use NUMBER(Precision) or NUMBER(Precision, Scale)
// as the datatype in a definition for some object other than a DIMENSION or
// VARIABLE, such as a FORMULA or PROGRAM. This error can also be produced
// in cases where a NUMBER data type is not allowed at all.
// *Action: Use the NUMBER type without specifying a precision or scale. If
// a NUMBER data type is not allowed at all, this fix will only change the
// exception message to something more specific.
34279, 00000, "(MXDCL37) CONCAT can only be used when defining a DIMENSION."
// *Cause: The CONCAT keyword was used incorrectly.
// *Action: Retry the command without the CONCAT keyword.
34280, 00000, "(MXDCL38) PARTITION BY can only be used when defining a PARTITION TEMPLATE."
// *Cause:
// *Action:
34281, 00000, "(MXDCL39) A (precision code) argument can only be used with DATETIME or TIMESTAMP dimensions."
// *Cause:
// *Action:
34284, 00000, "(MXDCL52) A SPARSE dimension cannot be specified in this context."
// *Cause:
// *Action:
34286, 00000, "(MXDCL53) %a %j %s\n%1p cannot be used in this context because it is a %2p."
// *Cause: User specified a dimension composite, conjoint, or partition
// template in a place where that kind of dimension is not allowed.
// For instance, a relation cannot be dimensioned by a composite,
// and only a variable can dimensioned by a partition template.
// *Action: Usually, the offending dimension can be replaced with its
// bases. For instance, a relation cannot be dimensioned by a
// a composite of PRODUCT and GEOG, but it can be dimensioned
// by both PRODUCT and GEOG instead.
34298, 00000, "(MXDCLEQ01) %n was not defined as a formula, so you cannot use the EQ command to give it a value."
// *Cause:
// *Action:
34300, 00000, "(MXDCLEQ02) %n is not a time dimension, so you cannot define a VNF formatting string for it."
// *Cause:
// *Action:
34302, 00000, "(MXDCLEQ03) %n is not a DATETIME or TIMESTAMP dimension, formula, program, or variable, so you cannot define a DATE_FORMAT formatting string for it."
// *Cause:
// *Action:
34304, 00000, "(MXDCLILP01) There is no current program definition. Define a program or use the CONSIDER command before using the PROGRAM command."
// *Cause:
// *Action:
34306, 00000, "(MXDCLILP02) %n was not defined as a PROGRAM."
// *Cause:
// *Action:
34308, 00000, "(MXDCLILP03) Since you have no current program definition, your PROGRAM entries will be discarded. Type END to return to command level."
// *Cause:
// *Action:
34310, 00000, "(MXDCLILP04) The %n program cannot be redefined while it is executing."
// *Cause:
// *Action:
34312, 00000, "(MXDCLMOD01) There is no current model definition. Define a model or use the CONSIDER command before using the MODEL command."
// *Cause:
// *Action:
34314, 00000, "(MXDCLMOD02) %n was not defined as a model."
// *Cause:
// *Action:
34316, 00000, "(MXDCLMOD03) Since there is no current model definition, the MODEL statements will be discarded. Type END to return to the command line."
// *Cause:
// *Action:
34318, 00000, "(MXDCLAGR01) There is no current aggmap definition. Define an aggmap or use the CONSIDER command before using the AGGMAP command."
// *Cause:
// *Action:
34320, 00000, "(MXDELETE00) %a %q %s\nThe object %1p is not in the %2p analytic workspace."
// *Cause:
// *Action:
34324, 00000, "(MXFETCH01) The ACROSS and DOWN keywords cannot be set to NONE at the same time."
// *Cause:
// *Action:
34328, 00000, "(MXDEBUG01) %a %v %v\n= Entering %1p from %2p"
// *Cause:
// *Action:
34330, 00000, "(MXDEBUG02) = Entering %v"
// *Cause:
// *Action:
34332, 00000, "(MXDEBUG03) = Leaving %v"
// *Cause:
// *Action:
34334, 00000, "(MXDEBUG04) %a %v %k\n= Leaving %1p, Value = %2p"
// *Cause:
// *Action:
34336, 00000, "(MXGO00) The %t keyword can only be used for a model."
// *Cause:
// *Action:
34338, 00000, "(MXDIMEN01) An object cannot have more than %d dimensions."
// *Cause:
// *Action:
34340, 00000, "(MXDINSRT01) %a %v %s\nAn object named %1p already exists in analytic workspace %2p."
// *Cause:
// *Action:
34342, 00000, "(MXDSS01) IMPORTANT: Analytic workspace %s is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it."
// *Cause: This is an informational message that reminds you that you may
// not save changes to the specified analytic workspace.
// *Action: None, unless it was desired to save changes to the analytic
// workspace. In that case, detach and reattach the analytic
// workspace read-write.
34343, 00000, "(MXDSS02) %t is not a valid analytic workspace name. The name must be one of the following forms: SCHEMA.NAME, NAME, or ALIAS, where NAME is an analytic workspace name, SCHEMA is a schema name, and ALIAS is an analytic workspace alias."
// *Cause:
// *Action:
34344, 00000, "(MXDSS03) Analytic workspace %s is not attached."
// *Cause: The command attempted to operate on an analytic workspace
// that is not currently attached, or the name of the analytic
// workspace is misspelled.
// *Action: Attach the analytic workspace or correct the spelling.
34346, 00000, "(MXDSS04) The %s analytic workspace cannot be detached."
// *Cause: The specified analytic workspace is an internal workspace
// and may not be detached by the user.
// *Action: Specify a different analytic workspace to detach.
34348, 00000, "(MXDSS05) %s is used only for internal purposes and cannot be accessed as an analytic workspace."
// *Cause: The command attempted to operate on an internal analytic workspace
// used by the system.
// *Action: Specify a different analytic workspace.
34350, 00000, "(MXDSS06) %s is an open analytic workspace."
// *Cause: The specified analytic workspace is currently in use.
// *Action: The desired action requires an analytic workspace that is
// not currently in use.
34352, 00000, "(MXDSS07) %a %-8s %c %c %s\n%1p%2p R/%3p CHANGED %4p"
// *Cause:
// *Action:
34354, 00000, "(MXDSS08) %a %-8s %c %c %s\n%1p%2p R/%3p UNCHANGED %4p"
// *Cause:
// *Action:
34356, 00000, "(MXDSS09) %a %s %s\nAnalytic workspace %1p is attached in read-only mode, therefore you cannot change its %2p."
// *Cause:
// *Action:
34357, 00000, "(MXDSS10) %a %s %s\n%1p is not an alias of analytic workspace %2p."
// *Cause: User attempted to use AW UNALIAS on a non-existent alias.
// *Action: Make sure that the command specified the correct analytic
// workspace and alias. The alias must have been assigned (using AW ALIAS)
// during the current session and must not have been removed by
// a previous AW UNALIAS or AW DETACH command.
34358, 00000, "(MXDSS14) %d other users reading"
// *Cause: Used for AW LIST output formatting when %d > 1
// *Action: None
34359, 00000, "(MXDSS11) %s appears twice in the alias list."
// *Cause: User included the same name twice in the alias list of
// an AW ALIAS or AW UNALIAS command.
// *Action: Remove the duplicate name and try again.
34360, 00000, "(MXDSS15) %d other users writing"
// *Cause: Used for AW LIST output formatting when %d > 1
// *Action: None
34361, 00000, "(MXDSS12) %d other user reading"
// *Cause: Used for AW LIST output formatting when %d == 1
// *Action: None
34362, 00000, "(MXDSS16) Program %v does not exist."
// *Cause:
// *Action:
34363, 00000, "(MXDSS13) %d other user writing"
// *Cause: Used for AW LIST output formatting when %d == 1
// *Action: None
34364, 00000, "(MXDSS17) The read/write status of analytic workspace %s has not been changed. To change it, detach and re-attach the analytic workspace."
// *Cause:
// *Action:
34366, 00000, "(MXDSS19) Security override is not allowed on analytic workspace %s."
// *Cause:
// *Action:
34368, 00000, "(MXDSS20) Incorrect response. Security override failure."
// *Cause:
// *Action:
34370, 00000, "(MXDSS21) Permission to attach analytic workspace %s denied by a PERMIT program."
// *Cause:
// *Action:
34371, 00000, "(MXDSS22) Schema name \"%s\" contains characters that are not allowed in an analytic workspace name."
// *Cause: The specified or default schema name contained characters that can occur only in quoted identifiers, which are not supported in OLAP DML.
// *Action: Specify a schema name containing only characters that can appear in a nonquoted identifer.
34372, 00000, "(MXDSS26) An analytic workspace named %s is already attached."
// *Cause:
// *Action:
34373, 00000, "schema name contains unsupported characters"
// *Cause: The specified or default schema name, contained characters that can occur only in quoted identifiers, which are not supported in OLAP DML.
// *Action: Specify a schema name containing only characters that can appear in a nonquoted identifier.
34376, 00000, "(MXDSS28) %a %s %d\n%1p is not a valid analytic workspace name. Analytic workspace names must be %2p characters or less, can contain only letters, digits, underscores, and dollar signs, and cannot begin with a digit or dollar sign."
// *Cause: The specified analytic workspace or ALIAS name was too long or
// contained invalid characters.
// *Action: Verify that the analytic workspace name meets the specified
// criteria.
34378, 00000, "(MXDSS29) %s is a reserved word and cannot be used as an analytic workspace name."
// *Cause:
// *Action:
34380, 00000, "(MXEXPORT00) You can only export one worksheet to a spreadsheet file."
// *Cause:
// *Action:
34382, 00000, "(MXEXPORT01) Worksheets are the only objects you can export to spreadsheet files. %n is not a worksheet."
// *Cause:
// *Action:
34384, 00000, "(MXFILEIO01) The %t option of FILESET is not supported."
// *Cause:
// *Action:
34386, 00000, "(MXFILEIO02) No more than 9 arguments can be supplied to FILESET."
// *Cause:
// *Action:
34388, 00000, "(MXFILERD01) The format of the FILEREAD command is:\n FILEREAD unit [STOPAFTER n] [STRUCTURED | CSV | RULED] [fieldlist]"
// *Cause:
// *Action:
34390, 00000, "(MXFILERD02) The format of the FILEVIEW command is:\n FILEVIEW unit [STRUCTURED | RULED] [fieldlist]"
// *Cause:
// *Action:
34392, 00000, "(MXFORCAS00) You cannot calculate a forecast for an expression with no dimensions."
// *Cause:
// *Action:
34394, 00000, "(MXFORCAS01) You cannot calculate a forecast with an STSEASONAL expression with no dimensions."
// *Cause:
// *Action:
34396, 00000, "(MXFORCAS02) The expression to be forecast is not dimensioned by %j."
// *Cause:
// *Action:
34398, 00000, "(MXFORCAS03) The STSEASONAL expression must be dimensioned by only one dimension."
// *Cause:
// *Action:
34400, 00000, "(MXFORCAS04) time-series"
// *Cause:
// *Action:
34402, 00000, "(MXFORCAS05) When you specify the forecast LENGTH, you must also specify an FCNAME."
// *Cause:
// *Action:
34404, 00000, "(MXFORCAS06) When you specify METHOD WINTERS, you must also specify the PERIODICITY."
// *Cause:
// *Action:
34406, 00000, "(MXFORCAS07) When STSMOOTHED, STTREND, or STSEASONAL is specified, they must all be specified."
// *Cause:
// *Action:
34408, 00000, "(MXFORCAS08) You specified a forecast phrase that is valid only when METHOD WINTERS is specified."
// *Cause:
// *Action:
34410, 00000, "(MXFORCAS09) The arguments to FCNAME, FCSMOOTHED, FCTREND, and FCSEASONAL must be numeric. %q is not numeric."
// *Cause:
// *Action:
34412, 00000, "(MXFORCAS10) %a %q %j\nFCNAME, FCSMOOTHED, FCTREND, and FCSEASONAL variables must be dimensioned by time dimension %2p. %1p is not."
// *Cause:
// *Action:
34414, 00000, "(MXGETFLD01) %a %s %s\nYour FILEREAD or FILEVIEW statement specifies no width for a %1p %2p field. There is no default width for this data type."
// *Cause:
// *Action:
34416, 00000, "(MXGETFLD02) %a %s %s\n%1p data cannot be read as a %2p value."
// *Cause:
// *Action:
34418, 00000, "(MXGETFLD03) A STRUCTURED or CSV record cannot contain %s data."
// *Cause:
// *Action:
34420, 00000, "(MXGETFLD04) %a %s %s\nThe %1p option of FILEREAD or FILEVIEW cannot be specified for %2p data."
// *Cause:
// *Action:
34422, 00000, "(MXGETFLD05) The SCALE option of FILEREAD or FILEVIEW cannot be specified for BINARY data other than INTEGER."
// *Cause:
// *Action:
34424, 00000, "(MXGETFLD06) %a %s %s %s\nThe %1p option of FILEREAD or FILEVIEW cannot be specified for %2p %3p data."
// *Cause:
// *Action:
34426, 00000, "(MXGETFLD07) Values read into the relation %q must be INTEGER position numbers of its conjoint value dimension."
// *Cause:
// *Action:
34428, 00000, "(MXGETFLD08) Values read into conjoint dimension %q must be either INTEGER position numbers or a bracketed list of base dimension values."
// *Cause:
// *Action:
34430, 00000, "(MXGETFLD09) No data type was specified for one or more of the base dimensions of conjoint dimension %q."
// *Cause:
// *Action:
34432, 00000, "(MXGETFLD10) %q cannot be assigned time dimension data."
// *Cause:
// *Action:
34434, 00000, "(MXGETFLD11) You cannot read values of a dimension composite directly. You can specify a bracketed list of base dimension values."
// *Cause:
// *Action:
34436, 00000, "(MXGETFLD12) No data type was specified for one or more of the base dimensions of a dimension composite."
// *Cause:
// *Action:
34438, 00000, "(MXGETSVN01) A value of the %j dimension must be a single expression without surrounding angle brackets <>."
// *Cause:
// *Action:
34440, 00000, "(MXGETSVN02) %a %j %d\nA value of the %1p dimension must be a combination of %2p base dimension values surrounded by angle brackets <>."
// *Cause:
// *Action:
34442, 00000, "(MXGETSVN03) You cannot use a Qualified Object Name as a value of the NAME dimension."
// *Cause:
// *Action:
34444, 00000, "(MXGETSVN04) Dimension %j is not a concatenated dimension."
// *Cause:
// *Action:
34446, 00000, "(MXGETSVN05) %a %j %j\nDimension %1p is not a base of concatenated dimension %2p."
// *Cause:
// *Action:
34448, 00000, "(MXGOTO01) %t is not defined as a label."
// *Cause:
// *Action:
34450, 00000, "(MXIFERR) %a %t %s\nThe IF keyword must be followed by a BOOLEAN expression. The expression starting with %1p is %2p."
// *Cause:
// *Action:
34452, 00000, "(MXIMPORT01) %t is a reserved keyword that cannot be used in this context."
// *Cause:
// *Action:
34454, 00000, "(MXIMPORT02) When importing a spreadsheet, CSV file, or PRN file, the target must be a worksheet. %q is not a worksheet."
// *Cause:
// *Action:
34456, 00000, "(MXIMPORT03) The STOPAFTER specification cannot be NA."
// *Cause:
// *Action:
34458, 00000, "(MXIMPORT04) The RULER expression cannot be missing or NA."
// *Cause:
// *Action:
34460, 00000, "(MXIMPORT05) The expression identifying the file cannot be NA."
// *Cause:
// *Action:
34462, 00000, "(MXIMPORT06) The STOPAFTER specification cannot be less than one. The value was %d."
// *Cause:
// *Action:
34464, 00000, "(MXIMPORT07) TEXTSTART and TEXTEND are supported only for STRUCTURED PRN files. DELIMITER is supported for STRUCTURED PRN and CSV files."
// *Cause:
// *Action:
34466, 00000, "(MXIMPORT08) %a %q %s\nTarget %1p is not in analytic workspace %2p."
// *Cause:
// *Action:
34468, 00000, "(MXIMPORT09) %q is not a valid target name. You cannot use a Qualified Object Name to specify a target in an EIF import."
// *Cause:
// *Action:
34476, 00000, "(MXINFO01) The first argument to the %t function must be FORECAST, PARSE, REGRESS, SEASADJ, or MODEL."
// *Cause:
// *Action:
34478, 00000, "(MXLOG01) Disk file %s cannot be opened; it is in use."
// *Cause:
// *Action:
34480, 00000, "(MXMAINT01) %a %s %j\nYou cannot %1p values of conjoint dimension %2p."
// *Cause:
// *Action:
34481, 00000, "(MXMAINT07) %a %s %j\nYou cannot %1p values of PARTITION TEMPLATE %2p."
// *Cause: User attempted to use the MAINTAIN command with some keyword other
// than ADD or DELETE on a partition template.
// *Action: It is not possible to MAINTAIN a partition template, except to
// add or delete values of a partition list.
34482, 00000, "(MXMAINT02) %a %s %j\nYou cannot %1p values of time dimension %2p."
// *Cause:
// *Action:
34484, 00000, "(MXMAINT03) %a %s %j\nYou cannot %1p values of dimension composite %2p."
// *Cause:
// *Action:
34486, 00000, "(MXMAINT04) You cannot maintain dimension alias %j."
// *Cause:
// *Action:
34487, 00000, "(MXMAINT08) %a %s %j\nYou cannot %1p values of non-unique concat dimension %2p."
// *Cause: The specified MAINTAIN operation can only be applied to UNQUE concats.
// *Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry.
34488, 00000, "(MXMAINT05) %a %s %j\nYou cannot %1p values of concat dimension %2p."
// *Cause:
// *Action:
34489, 00000, "(MXMAINT06) You cannot maintain %j because it is a SURROGATE."
// *Cause: The user attempted to use the MAINTAIN command on a dimension
// surrogate. The MAINTAIN command can only be used with real dimensions,
// not surrogates.
// *Action: Use the MAINTAIN command to modify the underlying dimension
// of the surrogate instead.
34490, 00000, "(MXMOVE00) You cannot use Qualified Object Names in the MOVE command except as part of an expression."
// *Cause:
// *Action:
34492, 00000, "(MXMSERR00) Analytic workspace object %q does not exist."
// *Cause:
// *Action:
34494, 00000, "(MXMSERR01) %a %s %q\nAnalytic workspace %1p does not contain an object named %2p."
// *Cause:
// *Action:
34496, 00000, "(MXNAME01) The NAME dimension is available only when you have an active analytic workspace."
// *Cause:
// *Action:
34498, 00000, "(MXNAME02) You cannot use the NAME dimension in this context."
// *Cause:
// *Action:
34500, 00000, "(MXNAME03) %t is a reserved keyword that cannot be used in this context."
// *Cause:
// *Action:
34502, 00000, "(MXNAME03A) %v is a reserved keyword that cannot be used in this context."
// *Cause:
// *Action:
34504, 00000, "(MXNAME04) You have no current analytic workspace."
// *Cause:
// *Action:
34506, 00000, "(MXNAME05) %t is a local variable that cannot be used in this context."
// *Cause:
// *Action:
34508, 00000, "(MXNAME06) You cannot qualify references to the NAME dimension."
// *Cause:
// *Action:
34512, 00000, "(MXNEGERR) %a %s %t\nThe NOT operator can only be used with BOOLEAN expressions. The expression at %2p is %1p."
// *Cause:
// *Action:
34514, 00000, "(MXOPERR) %a %s %s %t\nYou cannot %1p %2p data in the expression that begins with '%3p'."
// *Cause: The user attempted an invalid operation.
// *Action:
34516, 00000, "(MXPROPER01) A property name cannot be NA."
// *Cause:
// *Action:
34518, 00000, "(MXPROPER02) A property named %i does not exist."
// *Cause:
// *Action:
34520, 00000, "(MXPROPER03) A property name cannot be a multi-line text."
// *Cause:
// *Action:
34522, 00000, "(MXPROPER04) %a %d %d %d\nA property name must be between %2p and %3p bytes long. You supplied a name of %1p bytes."
// *Cause:
// *Action:
34524, 00000, "(MXPROPER05) The object properties in this analytic workspace cannot be read, because they were created by an incompatible version of %s."
// *Cause:
// *Action:
34526, 00000, "(MXPSHPOP01) %a %s %n\nYou cannot %1p %2p because it is not a scalar variable."
// *Cause:
// *Action:
34528, 00000, "(MXPSHPOP02) %a %s %n\nYou cannot %1p %2p because it is not data."
// *Cause:
// *Action:
34530, 00000, "(MXPSHPOP03) %a %s %n %s\nYou cannot %1p %2p because it is a %3p."
// *Cause:
// *Action:
34534, 00000, "(MXPUTQDR01) A FILEREAD attribute list is not valid in this context."
// *Cause:
// *Action:
34536, 00000, "(MXRECAP00) COMMAND LOG\n -----------"
// *Cause:
// *Action:
34538, 00000, "(MXRECAP01) The format of the RECAP command is:\n RECAP [ALL|n] [string] [FILE pathname]"
// *Cause:
// *Action:
34540, 00000, "(MXRECAP02) RECAP does not support multi-line strings."
// *Cause:
// *Action:
34542, 00000, "(MXRECAP03) There are no entries in the command log."
// *Cause:
// *Action:
34544, 00000, "(MXRECAP04) No matching commands were found."
// *Cause:
// *Action:
34546, 00000, "(MXRECAP05) The format of the REDO command is:\n REDO [n] [oldtext newtext [option]]"
// *Cause:
// *Action:
34548, 00000, "(MXRECAP06) %a %d %v\nThere is no occurrence %1p of '%2p' in the command."
// *Cause:
// *Action:
34550, 00000, "(MXRECAP07) Command number %d is not available."
// *Cause:
// *Action:
34552, 00000, "(MXRECAP08) Multi-line strings cannot be used in editing the command."
// *Cause:
// *Action:
34554, 00000, "(MXRECAP09) The string '%v' does not occur in the command."
// *Cause:
// *Action:
34556, 00000, "(MXRECAP10) %a %v %v %d\nSubstituting %1p for %2p would cause the command to exceed the maximum command length (%3p)."
// *Cause:
// *Action:
34558, 00000, "(MXRECAP11) The format of the REEDIT command is:\n REEDIT [n] oldtext newtext [option]"
// *Cause:
// *Action:
34560, 00000, "(MXRECAP12) The %t command cannot be saved in the command log by REDO or REEDIT or executed by REDO."
// *Cause:
// *Action:
34562, 00000, "(MXRENAME02) %a %v %s\nAn object named %1p already exists in analytic workspace %2p."
// *Cause:
// *Action:
34564, 00000, "(MXRENAME03) The SPARSE keyword changes a named composite to unnamed. You cannot apply it to an unnamed composite."
// *Cause:
// *Action:
34566, 00000, "(MXRENAME04) Only integer dimensions can be named %s."
// *Cause:
// *Action:
34568, 00000, "(MXRENAME05) You cannot rename %n because you do not have PERMIT rights to do it or it is readonly."
// *Cause:
// *Action:
34570, 00000, "(MXRENAME06) %a %j %s\nThe dimension composite %1p is not in analytic workspace %2p."
// *Cause:
// *Action:
34572, 00000, "(MXRENAME07) You cannot change %n to an unnamed composite because it is not a composite."
// *Cause:
// *Action:
34574, 00000, "(MXRENAME08) You cannot change %n to an unnamed composite because it has permissions attached."
// *Cause:
// *Action:
34576, 00000, "(MXRENAME09) You cannot change %n to an unnamed composite because there are pushed statuses associated with it."
// *Cause:
// *Action:
34578, 00000, "(MXRENAME10) You cannot change %n to an unnamed composite because there are no objects dimensioned by it."
// *Cause:
// *Action:
34580, 00000, "(MXRENAME11) You cannot change %n to an unnamed composite because there are properties associated with it."
// *Cause:
// *Action:
34582, 00000, "(MXRENAME12) You cannot change %n to an unnamed composite, because there is already an unnamed composite with the same base dimensions."
// *Cause:
// *Action:
34584, 00000, "(MXRENAME13) %a %j %j\nYou cannot change %1p to an unnamed composite, because it appears in the dimension list of unnamed composite %2p."
// *Cause:
// *Action:
34586, 00000, "(MXRENAME14) %a %j %j\nYou cannot change %1p to an unnamed composite, because unnamed composite %2p appears in its dimension list."
// *Cause:
// *Action:
34588, 00000, "(MXRENAME15) %a %q %s\nThe object %1p is not in analytic workspace %2p."
// *Cause:
// *Action:
34592, 00000, "(MXRENAME17) %a %j %n\nYou cannot change %1p to an unnamed composite, because it would cause the dependent object %2p to exceed the limit for the number of named dimensions."
// *Cause:
// *Action:
34594, 00000, "(MXROLLUP01) %q is not a data variable."
// *Cause:
// *Action:
34596, 00000, "(MXROLLUP02) %a %s %n\nThe data type (%1p) of %2p is not INTEGER, DECIMAL, or SHORTDECIMAL."
// *Cause:
// *Action:
34598, 00000, "(MXROLLUP03) %j is not related to itself."
// *Cause:
// *Action:
34600, 00000, "(MXROLLUP04) %a %n %j\n%1p is not dimensioned by %2p."
// *Cause:
// *Action:
34602, 00000, "(MXROLLUP05) You must specify which dimension to roll up, since %n has more than one dimension."
// *Cause:
// *Action:
34604, 00000, "(MXROLLUP06) %q is not a relationship array."
// *Cause:
// *Action:
34606, 00000, "(MXROLLUP07) %a %n %j\n%1p does not yield values of %2p."
// *Cause:
// *Action:
34608, 00000, "(MXROLLUP08) %a %j %j\n%1p is not dimensioned by %2p."
// *Cause:
// *Action:
34610, 00000, "(MXROLLUP09) %a %j %j %n\nThe relationship array %1p shares the %2p dimension with %3p. It can only share the rollup dimension itself."
// *Cause:
// *Action:
34612, 00000, "(MXSHELL01) Your program or expression uses too much execution space. Eliminate recursion or reduce the levels of nesting."
// *Cause:
// *Action:
34614, 00000, "(MXSHOWCD00) No command was given. There is nothing to show."
// *Cause:
// *Action:
34616, 00000, "(MXSHOWCD01) No code is generated for the %t command."
// *Cause:
// *Action:
34618, 00000, "(MXSHOWCD02) The compiled code for %j cannot be displayed because the program has been hidden."
// *Cause:
// *Action:
34620, 00000, "(MXSHOWCD03) %a %s %j\nNo compiled code exists for %1p %2p."
// *Cause:
// *Action:
34622, 00000, "(MXSHOWCD04) %a %s %j\nNo text exists for %1p %2p."
// *Cause:
// *Action:
34624, 00000, "(MXSORT01) %a %d %j\nSort criterion %1p is not dimensioned by %2p."
// *Cause:
// *Action:
34626, 00000, "(MXSORT02) You must convert WORKSHEET values to a simple data type before using them as a sort criterion."
// *Cause:
// *Action:
34628, 00000, "(MXSQL99) The SQL \"%t\" command can only be used in a program, and it must be compiled before it can be executed."
// *Cause:
// *Action:
34630, 00000, "(MXSQL00) The format of the SQL DECLARE command is:\n SQL DECLARE cursor-name CURSOR FOR select-command"
// *Cause:
// *Action:
34632, 00000, "(MXSQL01) The format of the SQL OPEN command is:\n SQL OPEN cursor-name"
// *Cause:
// *Action:
34634, 00000, "(MXSQL02) The format of the SQL CLOSE command is:\n SQL CLOSE cursor-name"
// *Cause:
// *Action:
34636, 00000, "(MXSQL03) The format of the SQL FETCH command is:\n SQL FETCH cursor-name [LOOP [count]] INTO :host-var [:host-var ...] [THEN filereadactions]"
// *Cause:
// *Action:
34637, 00000, "(MXSQL11) The format of the SQL IMPORT command is:\n SQL IMPORT cursor-name INTO :host-var [:host-var ...]\n [THEN filereadactions]"
// *Cause:
// *Action:
34638, 00000, "(MXSQL04) The format of the SQL CLEANUP command is:\n SQL CLEANUP"
// *Cause:
// *Action:
34639, 00000, "(MXSQL05) The format of the SQL SELECT command is:\n SQL SELECT rest of select statement INTO :host-var [:host-var ...] [THEN filereadactions]"
// *Cause:
// *Action:
34642, 00000, "(MXSQL08) The format of the SQL PREPARE command is:\n SQL PREPARE statement-name FROM non-select-command"
// *Cause:
// *Action:
34644, 00000, "(MXSQL09) The format of the SQL EXECUTE command is:\n SQL EXECUTE statement-name"
// *Cause:
// *Action:
34646, 00000, "(MXSQL10) The format of the SQL PROCEDURE command is:\n SQL PROCEDURE procedure-name [ ( parameter {, parameter} ) ]"
// *Cause:
// *Action:
34647, 00000, "(MXSQL18) The text expression in a CURSOR FOR TEXT declaration cannot be NA."
// *Cause: The text for the SELECT expression in a CURSOR FOR TEXT
// declaration was evaluated at compile time as NA.
// *Action: Specify a text expression that is not NA at the time the
// program containing the SQL DECLARE is compiled.
34648, 00000, "(MXSQL19) The SQL command is incomplete."
// *Cause:
// *Action:
34650, 00000, "(MXSQL20) The SELECT command is not supported by %s. You must declare a cursor to retrieve SQL data."
// *Cause:
// *Action:
34652, 00000, "(MXSQL21) The SQL command contains a syntax error."
// *Cause:
// *Action:
34654, 00000, "(MXSQL23) Host variable expected; use :: to escape a colon."
// *Cause:
// *Action:
34656, 00000, "(MXSQL24) Additional WHERE clause conditions with CURRENT OF <cursor name> syntax"
// *Cause: A SQL UPDATE or DELETE statement tried to use the CURRENT of <cursor name> syntax with a WHERE clause containing multiple conditions.
// *Action: When using the CURRENT OF <cursor name> syntax make sure it is the only condition in the WHERE clause.
34658, 00000, "(MXSQL25) The words CURSOR FOR TEXT must be followed by a compile-time text expression specifying a SELECT command."
// *Cause: A SQL DECLARE <csr> CURSOR FOR TEXT command lacked a text expression,
// or the expression was otherwise invalid.
// *Action: Specify a single text expression that can be evaluated at compile
// time to yield a SELECT statement
34660, 00000, "(MXSQL26) SQL cursor %t has already been declared in this compilation."
// *Cause:
// *Action:
34662, 00000, "(MXSQL27) SQL statement %t has already been prepared in this compilation."
// *Cause:
// *Action:
34665, 00000, "(MXSQL30) Concat dimension %j cannot be used as a target host variable. You must specify one of its leaves, and then set the concat's status from that leaf."
// *Cause:
// *Action:
34666, 00000, "(MXSWITCH01) Only one DEFAULT label is allowed in a SWITCH."
// *Cause:
// *Action:
34668, 00000, "(MXSWITCH02) The format of a DEFAULT label statement is:\n DEFAULT:"
// *Cause:
// *Action:
34670, 00000, "(MXSWITCH03) Invalid syntax in case label expression"
// *Cause:
// *Action:
34672, 00000, "(MXSWITCH04) The format of a CASE label statement is:\n CASE case-expression:"
// *Cause:
// *Action:
34674, 00000, "(MXTRACE01) There is no trace in effect."
// *Cause:
// *Action:
34676, 00000, "(MXTRAP01) %t is not defined as a label."
// *Cause:
// *Action:
34680, 00000, "(MXUPDATE03) Analytic workspace %s is read-only. Therefore, the UPDATE command will not save changes."
// *Cause:
// *Action:
34682, 00000, "(MXUPDATE04) You have no attached analytic workspaces."
// *Cause:
// *Action:
34684, 00000, "(MXUPDATE05) All of your attached analytic workspaces are read-only. Therefore, the UPDATE command will not save changes."
// *Cause:
// *Action:
34686, 00000, "(MXVAR02) %t is not a valid data type for a declarative statement."
// *Cause:
// *Action:
34688, 00000, "(MXVAR03) %q cannot be used as a variable or argument type because it is the name of a dimension composite."
// *Cause:
// *Action:
34690, 00000, "(MXWATCH01) There are no watchpoints set."
// *Cause:
// *Action:
34692, 00000, "(MXXEQ01) A division by zero was attempted. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of division by zero."
// *Cause:
// *Action:
34694, 00000, "(MXXEQ02) Unsupported conversion of RELATION data was attempted."
// *Cause:
// *Action:
34696, 00000, "(MXXEQ03A) \"%v\" is not a number."
// *Cause:
// *Action:
34698, 00000, "(MXXEQ03B) \"%v\" is not a Boolean."
// *Cause:
// *Action:
34700, 00000, "(MXXEQ05) Function calls are too deeply nested to be evaluated."
// *Cause:
// *Action:
34702, 00000, "(MXXEQ13) \"%v\" is not a valid number format."
// *Cause:
// *Action:
34704, 00000, "(MXXEQ14) %a %v %v\n\"%1p\" does not match number format \"%2p\"."
// *Cause:
// *Action:
34706, 00000, "(MXXEQ35) %a %k %j\n%1p is not a valid %2p."
// *Cause:
// *Action:
34708, 00000, "(MXXEQ36) %k does not exist."
// *Cause:
// *Action:
34710, 00000, "(MXXEQ37) Positions in the product of breakout dimensions of an aggregation function cannot exceed 2**63."
// *Cause:
// *Action:
34712, 00000, "(NAFILENAME) The expression identifying the file cannot be NA or blank."
// *Cause:
// *Action:
34718, 00000, "(NLSCHARSET02) %v is not a valid, installed NLS character set."
// *Cause:
// *Action:
34719, 00000, "(NLSCHARSET03) Character data loss in NTEXT/TEXT conversion"
// *Cause: When character set conversion happens between TEXT and NTEXT
// either implicitly or explicitly, some characters are lost
// due to no mapping characters in the destination character set.
// *Action: Make sure all the characters can be mapped to destination
// character set or set NLS_NCHAR_CONV_EXCP to be FALSE.
// Note: This message is the OLAP equivalent of ORA-12713.
34720, 00000, "(NLSCHARSET04) An unknown character set conversion error occurred."
// *Cause:
// *Action:
34722, 00000, "(NLSCHARSET05) %a %s %s\nCAUTION: Character data loss in character set conversion from %1p to %2p"
// *Cause: Some operation required a string to be converted into a different
// character set, but the string contained characters that didn't
// exist in the new character set.
// *Action: Choose different character sets.
34726, 00000, "(NLSCHARSET06) %a %s %s\nCAUTION: String truncated during character set conversion from %1p to %2p"
// *Cause: Some operation required a string to be converted into a different
// character set. The string required more bytes in the new encoding,
// and exceeded some byte limit on its allowable length, causing
// some characters to be removed from the end of the string.
// *Action: If the byte limit is due to using the ID datatype, consider
// using the CHAR datatype instead. If the byte limit is due to
// the limit of 4000 bytes per line of CHAR data, break the long
// line up into multiple lines.
34730, 00000, "(NLSCHARSET08) CAUTION: During character set conversion, some of hidden program %j was truncated or could not be converted."
// *Cause:
// *Action:
34731, 00000, "(NLSSORT01) '%v' is not a valid NLS_SORT specification."
// *Cause: An unrecognized NLS_SORT value was specified in the SORT command
// or the SORT, SORTLINES or UNIQUELINES function.
// *Action: Specify a supported NLS_SORT value.
34732, 00000, "(NOCONSIDER) You have no current definition. Define an object or use the CONSIDER command before using the %s command."
// *Cause:
// *Action:
34738, 00000, "(NOUPDATE) A severe problem has been detected. Analytic workspace operations have been disabled."
// *Cause: A previous fatal error has marked the session so that it cannot
// perform any UPDATEs
// *Action: Start a new session
34740, 00000, "(NOUPDATEDB) Because of a previous error, changes made to the %s analytic workspace will not be saved."
// *Cause:
// *Action:
34744, 00000, "(NPV01) %a %j %d %d\nTime dimension %1p has a range in status of %2p periods. The maximum range allowed for the NPV function is %3p periods."
// *Cause:
// *Action:
34746, 00000, "(NPV02) The interest rate in the NPV function is %f. The value must be greater than -1."
// *Cause:
// *Action:
34748, 00000, "(NUMARGS1) %a %d %t %d\nYou supplied %1p argument(s) to the %2p function. You must supply at least %3p."
// *Cause:
// *Action:
34750, 00000, "(NUMARGS2) The %t function cannot have any arguments."
// *Cause:
// *Action:
34752, 00000, "(NUMARGS3) %a %d %t %d\nYou supplied %1p arguments to the %2p function. It can have no more than %3p arguments."
// *Cause:
// *Action:
34754, 00000, "(NUMARGS4) %a %d %d\nYou supplied %1p argument(s) to a function that requires at least %2p."
// *Cause:
// *Action:
34756, 00000, "(NUMARGS5) You supplied arguments to a function that does not take arguments."
// *Cause:
// *Action:
34758, 00000, "(NUMARGS6) %a %d %d\nYou supplied %1p arguments to a function that can have no more than %2p arguments."
// *Cause:
// *Action:
34760, 00000, "(NXHANDLE01) Decimal overflow in context that is unprotected by the DECIMALOVERFLOW option. Contact Oracle OLAP technical support."
// *Cause:
// *Action:
34761, 0000, "(NXHANDLEALLO) A decimal overflow occurred during an ALLOCATE operation. The results are not reliable."
// *Cause: While performing an ALLOCATE, a decimal overflow occurred
// *Action: Correct the data or use a higher precision datatype
34762, 00000, "(NXHANDLE02) A decimal overflow has occurred. Set DECIMALOVERFLOW to YES if you want NA to be returned as the result of a decimal overflow."
// *Cause:
// *Action:
34764, 00000, "(NXHANDLE03) A decimal overflow occurred during a ROLLUP operation. The results are not reliable."
// *Cause:
// *Action:
34766, 00000, "(NXHANDLE04) A decimal overflow occurred during an AGGREGATE operation. The results are not reliable."
// *Cause:
// *Action:
34768, 00000, "(NXHANDLE05) A decimal overflow occurred while parsing the AGGMAP."
// *Cause:
// *Action:
34770, 00000, "(OBJENG02) The object name argument to the OBJ function cannot be NA."
// *Cause:
// *Action:
34772, 00000, "(OBJENG03) %v contains more than one name."
// *Cause:
// *Action:
34774, 00000, "(OBJENG04) '%v' is not the name of a dimension or composite."
// *Cause:
// *Action:
34776, 00000, "(OBJENG05) Analytic workspace object %v does not exist."
// *Cause:
// *Action:
34778, 00000, "(OBJENG06) You cannot use the OBJ function on objects in analytic workspace %s."
// *Cause:
// *Action:
34780, 00000, "(OBJLIST01) Analytic workspace '%s' is not attached."
// *Cause:
// *Action:
34782, 00000, "(OBJSAVE2) Analytic workspace %s already has the maximum number of objects (65535)."
// *Cause:
// *Action:
34786, 00000, "(OCI02) The total length of all output variables cannot be more than %d bytes."
// *Cause:
// *Action:
34796, 00000, "(OCI08) SQL host variable %d cannot be bound."
// *Cause: The data type of the host variable is not supported.
// *Action: Specify only variables of supported types as host variable names.
34798, 00000, "(OCI09) OLAP OCI operation canceled."
// *Cause:
// *Action:
34800, 00000, "(OCI10) OLAP OCI operation returned '%s'."
// *Cause:
// *Action:
34802, 00000, "(OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled."
// *Cause: ROLLBACK past the UPDATE of one of the attached Analytic Workspaces was called. The current operation is aborted, and the Analytic Workspace detached.
// *Action: Change the called SQL procedure to avoid the ROLLBACK
34804, 00000, "(OCI12) %a %d %d\nThe value of SQL host variable %1p is too long. Use the WIDE keyword for columns that may exceed %2p bytes."
// *Cause: The host variable had a text value longer than the maximum SQL
// VARCHAR length
// *Action: Use the WIDE keyword in the host variable specification, e.g.
// :WIDE OLAP_object_name
34805, 00000, "(OCI13) Statement %v must have at least one host variable."
// *Cause: Statements prepared with DIRECT=YES must have at least one host variable.
// *Action: Add a host variable to the prepared statements declaration.
34806, 00000, "(OCI14) Statement %v can only be executed within an ACROSS command."
// *Cause: Statements prepared with DIRECT=YES must be executed in an ACROSS command.
// *Action: Execute the statement within an ACROSS command.
34828, 00000, "(OFCENG01) You cannot specify a text dimension value for an INTEGER dimension."
// *Cause:
// *Action:
34830, 00000, "(OFCENG02) %a %s %j\nThe %1p function cannot be applied to the dimension composite %2p."
// *Cause:
// *Action:
34832, 00000, "(OFCENG03) %v is not the name of a dimension or valueset."
// *Cause:
// *Action:
34833, 00000, "(OFCENG04) %a %s %j\nThe %1p function cannot be applied to the PARTITION TEMPLATE %2p."
// *Cause:
// *Action:
34834, 00000, "(OKUNDSS01) %a %s %j\nAnalytic workspace %1p must remain current because the %2p program is still executing in it."
// *Cause:
// *Action:
34836, 00000, "(OKUNDSS03) %a %s %j\nAnalytic workspace %1p cannot be detached because a currently executing command depends upon an object (%2p) it contains."
// *Cause:
// *Action:
34840, 00000, "(OPCREATE01) %a %s %s\nThe %1p option must be declared with datatype %2p."
// *Cause: An attempt was made to declare the option with the wrong datatype.
// *Action: Declare the option with the correct datatype.
34841, 00000, "(OPCREATE02) The %s option must be declared with the READONLY attribute."
// *Cause: An attempt was made to declare the option without the READONLY attribute.
// *Action: Declare the option READONLY.
34842, 00000, "(OPTWIDTH) %a %j %d %d %d\n%1p must be between %3p and %4p. It cannot be %2p. Its previous value was retained."
// *Cause:
// *Action:
34844, 00000, "(OPUTNA00) You cannot set an option to NA. The previous value of %j was retained."
// *Cause:
// *Action:
34846, 00000, "(OVERRIDE01) %08x"
34848, 00000, "(PARSE01) The text to be parsed is NA."
// *Cause:
// *Action:
34850, 00000, "(PARSE02) The expression is not properly constructed."
// *Cause:
// *Action:
34852, 00000, "(PHASTOVC00) Unsupported type"
// *Cause:
// *Action:
34854, 00000, "(PMTSETUP00) Permission expression for %n is invalid and will be treated as FALSE."
// *Cause:
// *Action:
34856, 00000, "(PMTSETUP01) Permission for %n does not have proper dimensionality of the BY expression."
// *Cause:
// *Action:
34858, 00000, "(PMTUPDAT01) Permission expression for %n is invalid and will not be stored."
// *Cause:
// *Action:
34859, 00000, "(PMTUPDAT07) %a %n %d\nPermission condition for %1p contains an expression longer than %2p bytes and cannot be stored."
// *Cause: One of the components of the PERMIT condition was too long.
// *Action: Rewrite the condition to shorten it.
34860, 00000, "(PMTUPDAT02) You do not have PERMIT rights for %n."
// *Cause:
// *Action:
34862, 00000, "(PMTUPDAT03) %n is not a dimension, so you cannot give it MAINTAIN permission."
// *Cause:
// *Action:
34864, 00000, "(PMTUPDAT04) %a %s %n\nA BY clause cannot be given with %1p permission for %2p."
// *Cause:
// *Action:
34866, 00000, "(PMTUPDAT05) You cannot apply permissions to dimension composite %n. Instead, you can apply permissions to its base dimensions."
// *Cause:
// *Action:
34868, 00000, "(PMTUPDAT06) You cannot apply permissions to dimension alias %n. Instead, you can apply permissions to the aliased dimension."
// *Cause:
// *Action:
34870, 00000, "(PERMIT01) You do not have permission to read this value of %n."
// *Cause:
// *Action:
34871, 00000, "(PERMIT06) %a %j %k\nSession-only value '%2p' of %1p has been deleted because a PERMIT change has revealed a duplicate value."
// *Cause: Execution of a PERMIT command revealed a permanent dimension or
// surrogate value having the same name as the SESSION value.
// *Action: If the SESSION value is still needed, add it with a different name.
34872, 00000, "(PERMIT02) You do not have permission to write this value of %n."
// *Cause:
// *Action:
34873, 00000, "(PERMIT07) You cannot write this value of %n since it is readonly."
// *Cause:
// *Action:
34874, 00000, "(PERMIT03) You do not have permission to run %n."
// *Cause:
// *Action:
34876, 00000, "(PERMIT04) You do not have permission to read AGGMAP %n."
// *Cause:
// *Action:
34877, 00000, "(PERMIT05) You cannot apply permissions to concat dimension %j. Instead, you may apply permissions to its leaf dimension(s)."
// *Cause:
// *Action:
34880, 00000, "(PPDTORDR00) DATEORDER must be YMD, YDM, MYD, MDY, DYM, or DMY."
// *Cause:
// *Action:
34882, 00000, "(PPENG00) The level name for %s cannot be NA."
// *Cause:
// *Action:
34884, 00000, "(PPENG01) %v does not match a PUSHLEVEL command."
// *Cause:
// *Action:
34886, 00000, "(PPENG02) The option %j is read-only. Since its value cannot be popped, it cannot be pushed."
// *Cause:
// *Action:
34888, 00000, "(PPENG03) The status list for %j is protected by the TEMPSTAT command."
// *Cause:
// *Action:
34892, 00000, "(PPESCCH01) The ESCAPECHAR option requires a single character."
// *Cause:
// *Action:
34894, 00000, "(PPESCCH02) The '%s' character is an invalid choice for the ESCAPECHAR option."
// *Cause:
// *Action:
34896, 00000, "(PPMONTHS00) At least 12 month names must be given. Only %d were provided."
// *Cause: There must be at least one name for each month. Not enough names
// were provided.
// *Action: Provide at least 12 names.
34897, 00000, "(PPMONTHS01) Blank lines are not allowed in the MONTHNAMES option."
// *Cause: There is at least one blank line in the string populating the
// MONTHNAMES option. We do not allow blank month names.
// *Action: Remove the blank line(s) from the string.
34900, 00000, "(PPWKDAYS00) At least 7 day names must be given. Only %d were provided."
// *Cause: There must be at least one name for each day. Not enough names were
// provided.
// *Action: Make sure there are at least 7 names in the string.
34901, 00000, "(PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option."
// *Cause: There is at least one blank line in the string populating the
// DAYNAMES option. We do not allow blank day names.
// *Action: Remove the blank line(s) from the string.
34902, 00000, "(PPWKDNY01) The value of WEEKDAYSNEWYEAR must be a number between 1 and 7."
// *Cause:
// *Action:
34904, 00000, "(VCFMT001) must be multi-line"
// *Cause:
// *Action:
34908, 00000, "(VCFMT003) missing arg"
// *Cause:
// *Action:
34910, 00000, "(VCFMT004) duplicate"
// *Cause:
// *Action:
34912, 00000, "(VCFMT005) error during %%p permutation"
// *Cause:
// *Action:
34914, 00000, "(VCFMT006) non-numeric"
// *Cause:
// *Action:
34916, 00000, "(PRMPINIT001) ->"
// *Cause:
// *Action:
34918, 00000, "(PRMPINIT002) Continue>"
// *Cause:
// *Action:
34920, 00000, "(PRMPINIT003) More>"
// *Cause:
// *Action:
34922, 00000, "(PRMPINIT004) PRG>"
// *Cause:
// *Action:
34924, 00000, "(PRMPINIT005) PRG>"
// *Cause:
// *Action:
34926, 00000, "(PRMPINIT006) =>"
// *Cause:
// *Action:
34928, 00000, "(PRMPINIT007) MDL>"
// *Cause:
// *Action:
34930, 00000, "(PRMPINIT008) MDL>"
// *Cause:
// *Action:
34934, 00000, "(PRMPINIT010) AGGMAP>"
// *Cause:
// *Action:
34936, 00000, "(PRMPINIT011) AGGMAP>"
// *Cause:
// *Action:
34946, 00000, "(PRMPINIT031) Press <Enter> to continue."
// *Cause:
// *Action:
34956, 00000, "(PRMPINIT200) exponentiate"
// *Cause:
// *Action:
34957, 00000, "(PRMPINIT217) compare"
// *Cause:
// *Action:
34958, 00000, "(PRMPINIT201) multiply"
// *Cause:
// *Action:
34959, 00000, "(PRMPINIT218) compare"
// *Cause:
// *Action:
34960, 00000, "(PRMPINIT202) divide"
// *Cause:
// *Action:
34961, 00000, "(PRMPINIT219) compare"
// *Cause:
// *Action:
34962, 00000, "(PRMPINIT203) add"
// *Cause:
// *Action:
34964, 00000, "(PRMPINIT204) subtract"
// *Cause:
// *Action:
34966, 00000, "(PRMPINIT205) compare"
// *Cause:
// *Action:
34968, 00000, "(PRMPINIT206) compare"
// *Cause:
// *Action:
34970, 00000, "(PRMPINIT207) compare"
// *Cause:
// *Action:
34972, 00000, "(PRMPINIT208) compare"
// *Cause:
// *Action:
34974, 00000, "(PRMPINIT209) compare"
// *Cause:
// *Action:
34976, 00000, "(PRMPINIT210) compare"
// *Cause:
// *Action:
34978, 00000, "(PRMPINIT211) compare"
// *Cause:
// *Action:
34980, 00000, "(PRMPINIT212) compare"
// *Cause:
// *Action:
34982, 00000, "(PRMPINIT213) AND"
// *Cause:
// *Action:
34984, 00000, "(PRMPINIT214) OR"
// *Cause:
// *Action:
34986, 00000, "(PRMPINIT215) NOT"
// *Cause:
// *Action:
34988, 00000, "(PRMPINIT216) negate"
// *Cause:
// *Action:
34990, 00000, "(PRNIMPRT01) %a %d %d\nCAUTION: %1p line(s) in a TEXT PRN file were too long. Each line was truncated to %2p bytes."
// *Cause:
// *Action:
34992, 00000, "(PRNIMPRT02) %a %d %d\nCAUTION: %1p field(s) in a STRUCTURED PRN or CSV file were too long. Each field was truncated to %2p bytes."
// *Cause:
// *Action:
34994, 00000, "(PRNIMPRT03) Unexpected EOF encountered in string while importing data."
// *Cause:
// *Action:
34996, 00000, "(PRNIMPRT04) Unexpected character '%lc' at end of string."
// *Cause:
// *Action:
35000, 00000, "(PRNRULER01) The RULER specification does not have any valid field descriptions."
// *Cause:
// *Action:
35002, 00000, "(PRNRULER02) Zero is not a valid repeat count."
// *Cause:
// *Action:
35004, 00000, "(PRNRULER03) The repeat count %d was not followed by a field type."
// *Cause:
// *Action:
35006, 00000, "(PRNRULER04) The character '%lc' is not a valid field type. The valid types are A, S and T."
// *Cause:
// *Action:
35008, 00000, "(PRNRULER05) A field description (type %c) did not include a field width."
// *Cause:
// *Action:
35010, 00000, "(PRNRULER06) %a %d %d\nThe width (%1p) for an A or T field was too large. The limit is %2p."
// *Cause:
// *Action:
35012, 00000, "(PRNRULER07) Zero is not a valid width for an S field."
// *Cause:
// *Action:
35014, 00000, "(PRNRULER08) %a %i %d\nA repeat count or field width (%1p) was too large. The limit is %2p."
// *Cause:
// *Action:
35016, 00000, "(QFCHECK00) The analytic workspace and EIF file definitions of %n have a mismatched type."
// *Cause: Importing from an EIF file or LOB into an existing Analytic
// Workspace object failed because the definition of the existing
// object was too different from the definition of the object in the
// EIF file or LOB.
// *Action: Import the object into an Analytic Workspace that does not
// already contain an object with the same name.
35017, 00000, "(QFCHECK06) The Analytic Workspace and EIF file definitions of %n have different partitioning methods."
// *Cause: Importing from an EIF file or LOB into an existing Analytic
// Workspace object failed because the definition of the existing
// object was too different from the definition of the object in the
// EIF file or LOB.
// *Action: Import the object into an Analytic Workspace that does not
// already contain an object with the same name.
35018, 00000, "(QFCHECK01) The analytic workspace and EIF file definitions of %n have a mismatched data type."
// *Cause: Importing from an EIF file or LOB into an existing Analytic
// Workspace object failed because the definition of the existing
// object was too different from the definition of the object in the
// EIF file or LOB.
// *Action: Import the object into an Analytic Workspace that does not
// already contain an object with the same name.
35019, 00000, "(QFCHECK07) The Analytic Workspace and EIF file definitions of %n have different partition dimensions."
// *Cause: Importing from an EIF file or LOB into an existing Analytic
// Workspace object failed because the definition of the existing
// object was too different from the definition of the object in the
// EIF file or LOB.
// *Action: Import the object into an Analytic Workspace that does not
// already contain an object with the same name.
35020, 00000, "(QFCHECK02) The analytic workspace and EIF file definitions of %n have mismatched dimensioning."
// *Cause: Importing from an EIF file or LOB into an existing Analytic
// Workspace object failed because the definition of the existing
// object was too different from the definition of the object in the
// EIF file or LOB.
// *Action: Import the object into an Analytic Workspace that does not
// already contain an object with the same name.
35021, 00000, "(QFCHECK08) The EIF file definition of %n has some partitions that are not present in the existing Analytic Workspace object."
// *Cause: Importing from an EIF file or LOB into an existing Analytic
// Workspace object failed because the definition of the existing
// object was too different from the definition of the object in the
// EIF file or LOB.
// *Action: Import the object into an Analytic Workspace that does not
// already contain an object with the same name.
35022, 00000, "(QFCHECK03) The analytic workspace and EIF file definitions of %n have a mismatched relation."
// *Cause: Importing from an EIF file or LOB into an existing Analytic
// Workspace object failed because the definition of the existing
// object was too different from the definition of the object in the
// EIF file or LOB.
// *Action: Import the object into an Analytic Workspace that does not
// already contain an object with the same name.
35023, 00000, "(QFCHECK09) The analytic workspace and EIF file definitions of %n have incompatible partition definitions."
// *Cause: Importing from an EIF file or LOB into an existing Analytic
// Workspace object failed because the definition of the existing
// object was too different from the definition of the object in the
// EIF file or LOB.
// *Action: Import the object into an Analytic Workspace that does not
// already contain an object with the same name.
35024, 00000, "(QFCHECK04) The analytic workspace and EIF file definitions of %n have mismatched time dimension attributes."
// *Cause: Importing from an EIF file or LOB into an existing Analytic
// Workspace object failed because the definition of the existing
// object was too different from the definition of the object in the
// EIF file or LOB.
// *Action: Import the object into an Analytic Workspace that does not
// already contain an object with the same name.
35026, 00000, "(QFCHECK05) The analytic workspace and EIF file definitions of %n have a mismatched ALIASOF dimension."
// *Cause: Importing from an EIF file or LOB into an existing Analytic
// Workspace object failed because the definition of the existing
// object was too different from the definition of the object in the
// EIF file or LOB.
// *Action: Import the object into an Analytic Workspace that does not
// already contain an object with the same name.
35028, 00000, "(QFASCII00) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35029, 00000, "(QFPART00) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35030, 00000, "(QFDATA00) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35031, 00000, "(QFSVNS00) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause: The EIF file contains a compressed composite with defective
// aggregation data.
// *Action: Recreate the EIF file using the NOAGGR keyword.
35032, 00000, "(QFDATA01) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35034, 00000, "(QFDATA02) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35036, 00000, "(QFGETBUF00) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35038, 00000, "(QFGETHDR00) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35040, 00000, "(QFOBJECT90) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35042, 00000, "(QFOBJECT92) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35044, 00000, "(QFOBJECT93) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35046, 00000, "(QFOBJECT94) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35048, 00000, "(QFOBJECT97) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35050, 00000, "(QFPUTILP97) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35052, 00000, "(QFPUTILP98) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35054, 00000, "(QFPUTILP99) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35056, 00000, "(QFSTRING00) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35058, 00000, "(QFVC00) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35060, 00000, "(QFVC01) The IMPORT command has terminated because of a defect in the EIF file."
// *Cause:
// *Action:
35062, 00000, "(QFGET01) %a %d %s\nDuplicate files found for extension number %1p of EIF file %2p."
// *Cause: IMPORT searched the directories specified in EIFEXTENSIONPATH and
// found two EIF extension files with the same name (differing at most
// by the case used in the final name component.
// *Action: Delete, rename or move any files that are not to be read by IMPORT.
35064, 00000, "(QFGET02) %a %ld %d\n\" %1p bytes read in %2p seconds.\""
// *Document: NO
// *Cause: Used in formatting output for the LIST option of IMPORT
// *Action: None.
35066, 00000, "(QFGET03) %a %d %s\nExtension number %1p is missing for EIF file %2p."
// *Cause: IMPORT searched the directories specified in EIFEXTENSIONPATH and
// could not find the appropriately numbered extension file.
// *Action: Move the missing file into one of the searched directories.
35070, 00000, "(QFHEAD00) File %s is not in EIF format, so you cannot import it with the EIF specification."
// *Cause:
// *Action:
35071, 00000, "(QFHEAD06) %a %s %s %s\nEIF file %1p cannot be imported because analytic workspace %2p has not been upgraded to version %3p."
// *Cause: User attempted to import from an EIF file that was created by a
// newer version of the product into an AW that was created by a
// older version of the product.
// *Action: Make sure that the compatibility mode parameter in the init.ora
// of the importing instance specifies a version that is at least
// as high as the parameter was in the exporting instance. Then,
// convert the AW to the latest storage format and reexecute the
// import command. Alternatively, change the EIFVERSION option of
// the exporting instance to a lower number, recreate the EIF file,
// and import the new file.
35072, 00000, "(QFHEAD01) EIF file %s cannot be imported."
// *Document: NO
// *Cause: Unknown. This is here in case of future need.
// *Action: Unknown.
35074, 00000, "(QFHEAD02) %a %s %s\nEIF file %1p cannot be read by this version of %2p."
// *Cause: The EIF file was created with an internal version number indicating
// it may contain objects that are not compatible with the current
// Oracle OLAP version, or the EIF file is in an obsolete format.
// *Action: If possible, set EIFVERSION in the exporting instance to a lower
// number, recreate the EIF file, and import the new file.
35076, 00000, "(QFHEAD04) %a %s %s\nCAUTION: The textual data in EIF file %1p is encoded in a character set that is not recognized by this version of %2p."
// *Cause: IMPORT could not recognize the character set specification in the
// EIF file.
// *Action: Check the imported text data. If it was not imported correctly,
// recreate the EIF file with a character set supported by the
// current Oracle version.
35078, 00000, "(QFHEAD05) An EIF extension file header for %s is not in the correct format."
// *Cause: An EIF extension file in multi-file IMPORT did not contain correct
// header information.
// *Action: Check to be sure that EIFEXTENSIONPATH is set correctly and that
// all the extension files for the current IMPORT were created by the
// same EXPORT command as the main EIF file.
35080, 00000, "(QFOBJECT01) %a %s %s\nYou cannot rename dimensions when you import them. The %1p dimension cannot be imported as %2p."
// *Cause:
// *Action:
35082, 00000, "(QFOBJECT02) You cannot import changes to the %n program now, because it is currently executing."
// *Cause:
// *Action:
35084, 00000, "(QFOBJECT06) CAUTION: %s is being imported. However, this is a reserved word, so you must rename the new object before you can use it."
// *Cause:
// *Action:
35086, 00000, "(QFOBJECT07) \" %d dimension values \""
// *Cause:
// *Action:
35087, 00000, "(QFOBJECT09) %a %v\nInvalid partition template:\n %1p "
// *Cause:
// *Action:
35088, 00000, "(QFOBJECT08) \" %d dimension value combinations \""
// *Cause:
// *Action:
35090, 00000, "(QFPARSE00) The object %s cannot be imported because it does not exist in the EIF file."
// *Cause:
// *Action:
35092, 00000, "(QFPARSE01) %a %s %s %s\nYou cannot import the object %1p into both %2p and %3p at the same time. To import an object into two different analytic workspaces, use two separate IMPORT commands with different INTO arguments."
// *Cause:
// *Action:
35094, 00000, "(QFPARSE02) %a %s %s %s %s %s\nThe object %1p cannot be imported into analytic workspace %2p because an object named %3p already exists in analytic workspace %4p. To force a new %5p to be created, use an INTO argument on the IMPORT command."
// *Cause:
// *Action:
35095, 00000, "(QFSVNS01) One or more imported values of fixed-width dimension %j have been truncated."
// *Cause: The data in the EIF file was exported from a dimension with wider values than the target dimension will accommodate.
// *Action: Change the definition of the target dimension, or check to be sure that multiple values from the target dimension have not become identical during the import process. This could cause data loss as data from later dimension values overstores data imported earlier.
35096, 00000, "(QUAFEOF) An unexpected end-of-file occurred in the EIF file. Check to make sure you have all the imported data that you expected."
// *Cause:
// *Action:
35098, 00000, "(RDPOW01) You cannot raise zero to a negative power."
// *Cause:
// *Action:
35100, 00000, "(RDPOW02) You cannot raise a negative number to a non-integer power."
// *Cause:
// *Action:
35102, 00000, "(READONLY00) The option %j is read-only. Its previous value was retained."
// *Cause:
// *Action:
35104, 00000, "(REALDTOK01) \"%t\" is not a number."
// *Cause:
// *Action:
35106, 00000, "(REGRESS00) The regression was not calculated because of a linear relationship between your independent variables."
// *Cause: The values of the specified independent variables are not
// independent. For example, one may be a multiple of the other.
// *Action: Chose independent variables whose values are truly
// independent of one another.
35108, 00000, "(REGRESS01) The number of non-NA observations with weights greater than zero (%d) is too small to calculate a regression."
// *Cause:
// *Action:
35110, 00000, "(REGRESS02) The number of independent variables cannot exceed %d."
// *Cause:
// *Action:
35112, 00000, "(REGRESS03) Regression Analysis"
// *Cause:
// *Action:
35114, 00000, "(REGRESS04) Dependent Variable: "
// *Cause:
// *Action:
35116, 00000, "(REGRESS05) WEIGHTBY Variable: "
// *Cause:
// *Action:
35118, 00000, "(REGRESS06) Regressor"
// *Cause:
// *Action:
35120, 00000, "(REGRESS07) Coefficient"
// *Cause:
// *Action:
35122, 00000, "(REGRESS08) Std. Error"
// *Cause:
// *Action:
35124, 00000, "(REGRESS09) T-ratio"
// *Cause:
// *Action:
35126, 00000, "(REGRESS10) Corrected R-square "
// *Cause:
// *Action:
35128, 00000, "(REGRESS11) F-Statistic (%1 %2)"
// *Cause:
// *Action:
35130, 00000, "(REGRESS12) Number of observations "
// *Cause:
// *Action:
35132, 00000, "(REGRESS13) Standard error of estimate "
// *Cause:
// *Action:
35134, 00000, "(RGACCUM01) A weighted regression cannot be calculated if any of the weights specified is less than zero."
// *Cause:
// *Action:
35136, 00000, "(RGINFO00) There is no saved regression information for the INFO function to retrieve."
// *Cause:
// *Action:
35138, 00000, "(RPACROSS01) You must specify dimension values if you use %t in an ACROSS phrase."
// *Cause:
// *Action:
35140, 00000, "(RPACROSS02) ACROSS must be followed by the name of a dimension or an expression with one dimension."
// *Cause:
// *Action:
35142, 00000, "(RPCOLUMN01) Multiple ACROSS phrases specifying the same dimension (%j) cannot be given for the same column."
// *Cause:
// *Action:
35144, 00000, "(RPFORMAT01) %a %s %d\nThe value of the %1p attribute in column %2p is NA."
// *Cause:
// *Action:
35146, 00000, "(RPFORMAT02) %a %s %d\nThe value of the %1p attribute in column %2p is negative."
// *Cause:
// *Action:
35148, 00000, "(RPFORMAT03) %a %s %d\nThe value of the %1p attribute in column %2p is zero."
// *Cause:
// *Action:
35150, 00000, "(RPFORMAT04) The INDENT value for column %d equals or exceeds the WIDTH."
// *Cause:
// *Action:
35152, 00000, "(RPFORMAT05) %a %d %d\nColumn %1p extends past the maximum length (%2p) of a report line."
// *Cause:
// *Action:
35154, 00000, "(RSEXECUT01) The %s function can only be used in a ROW or REPORT command."
// *Cause:
// *Action:
35156, 00000, "(RSEXECUT02) An argument to %s was NA."
// *Cause:
// *Action:
35158, 00000, "(RSEXECUT03) %a %d %s\nColumn index %1p in %2p is before the first or after the last report column."
// *Cause:
// *Action:
35160, 00000, "(RSEXECUT04) %a %d %s\nTotaling level index %1p in %2p is not between 1 and 256."
// *Cause:
// *Action:
35162, 00000, "(RSEXECUT05) %a %d %s\nThe column number (%1p) in %2p must be greater than zero."
// *Cause:
// *Action:
35164, 00000, "(RSEXECUT06) %a %d %s\nAn argument (%1p) to %2p must be zero or greater."
// *Cause:
// *Action:
35166, 00000, "(SIGENG01) %s"
// *Cause:
// *Action:
35168, 00000, "(SIGENG02) %a %v %s\n(%1p) Contact the administrator of your %2p application."
// *Cause:
// *Action:
35170, 00000, "(SIGENG03) The \"errorname\" argument to the SIGNAL command is NA."
// *Cause:
// *Action:
35171, 00000, "you may not signal error number %s with the SIGNAL command"
// *Cause: The user attempted to explicitly signal an invalid error number
// with the OLAP DML SIGNAL command
// *Action: Signal another error number
35172, 00000, "(SNCHILD01) There is duplicate information beginning at %t, or this information conflicts with a keyword."
// *Cause:
// *Action:
35174, 00000, "(SNSYN100) The word %t must be followed by a name."
// *Cause:
// *Action:
35176, 00000, "(SNSYN101) The format of the AGGMAPINFO function is:\n \n AGGMAPINFO(aggmap-name { RELATIONS | NUMRELS | AGGINDEX | STORE | SHARE | FCACHE | MAPTYPE | { RELATION | PRECOMPUTE | STATUS } expression})"
// *Cause:
// *Action:
35178, 00000, "(SNSYN102) The format of the INFILE command is:\n \n INFILE {EOF | filename} [NOW] [NLS_CHARSET name] [TABEXPAND expression]"
// *Cause:
// *Action:
35180, 00000, "(SNSYN103) The format of the OUTFILE command is:\n \n OUTFILE [APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET name]}"
// *Cause: The user specified incorrect syntax for the OUTFILE command.
// *Action:
35182, 00000, "(SNSYN104) The format of the WKSDATA function is:\n \n WKSDATA(worksheetname)"
// *Cause:
// *Action:
35184, 00000, "(SNSYN105) The dimension name (%t) must be followed by one of these keywords: TO, KEEP, ADD, REMOVE, COMPLEMENT, SORT, or INSERT."
// *Cause:
// *Action:
35186, 00000, "(SNSYN106) The word %t must be followed by an argument such as a dimension value."
// *Cause:
// *Action:
35188, 00000, "(SNSYN107) The word %t must be followed by an expression."
// *Cause:
// *Action:
35190, 00000, "(SNSYN108) The TOP or BOTTOM value (%t) must be followed by the keyword BASEDON or PERCENTOF and an expression."
// *Cause:
// *Action:
35192, 00000, "(SNSYN109) The dimension name must be followed by a sort order (A or D) and a sort criterion expression."
// *Cause:
// *Action:
35194, 00000, "(SNSYN110) The format of the INFO function is:\n \n INFO({FORECAST|PARSE|REGRESS|MODEL} choice [index1 [index2 ...]])"
// *Cause:
// *Action:
35196, 00000, "(SNSYN111) The format of the CHARLIST function is:\n \n CHARLIST(expression [dimension1 [dimension2 ...]])"
// *Cause:
// *Action:
35198, 00000, "(SNSYN112) The dimension name (%t) must be followed by one of these keywords: ADD, BULKRENAME, DELETE, MERGE, MOVE, or RENAME."
// *Cause:
// *Action:
35200, 00000, "(SNSYN113) An angle bracket (>) is missing after %t."
// *Cause:
// *Action:
35202, 00000, "(SNSYN114) A right parenthesis or an operator is expected after %t."
// *Cause:
// *Action:
35204, 00000, "(SNSYN115) A label is missing after %t."
// *Cause:
// *Action:
35206, 00000, "(SNSYN116) The word UNION must be followed by a parenthesized list of LIST clauses."
// *Cause:
// *Action:
35208, 00000, "(SNSYN117) An expression, SKIP, <, or ACROSS must follow '%t', or this expression conflicts with a keyword."
// *Cause:
// *Action:
35210, 00000, "(SNSYN118) A colon (:) is required after an ACROSS phrase."
// *Cause:
// *Action:
35212, 00000, "(SNSYN119) The format of the UNRAVEL function is:\n \n UNRAVEL(expression [dimension1 [dimension2 ...]])"
// *Cause:
// *Action:
35214, 00000, "(SNSYN120) The format of the COMPILE command is:\n \n COMPILE name [THREADS #]"
// *Cause:
// *Action:
35216, 00000, "(SNSYN121) The fileunit (%t) must be followed by an attribute (such as DATE) and a new value for the attribute."
// *Cause:
// *Action:
35218, 00000, "(SNSYN122) The format of LEAD and the LAG functions is:\n \n function(time-series nperiods time-dimension [STATUS|NOSTATUS])"
// *Cause:
// *Action:
35220, 00000, "(SNSYN123) The format of the EXISTS function is:\n \n EXISTS(text-expression)"
// *Cause:
// *Action:
35222, 00000, "(SNSYN135) The format of the EXTCHARS function is:\n \n EXTCHARS(text-expression [start [length]])"
// *Cause:
// *Action:
35224, 00000, "(SNSYN136) The format of the EXTLINES function is:\n \n EXTLINES(text-expression [start [length]])"
// *Cause:
// *Action:
35226, 00000, "(SNSYN137) The format of the FINDCHARS function is:\n \n FINDCHARS(search-text find-text [start [LINENUM]])"
// *Cause:
// *Action:
35228, 00000, "(SNSYN138) The format of the FINDLINES function is:\n \n FINDLINES(search-text find-text)"
// *Cause:
// *Action:
35230, 00000, "(SNSYN139) The format of the JOINCHARS function is:\n \n JOINCHARS(text-expression1 text-expression2 ...)"
// *Cause:
// *Action:
35232, 00000, "(SNSYN140) The format of the JOINLINES function is:\n \n JOINLINES(text-expression1 text-expression2 ...)"
// *Cause:
// *Action:
35234, 00000, "(SNSYN141) The format of the NUMCHARS function is:\n \n NUMCHARS(text-expression)"
// *Cause:
// *Action:
35236, 00000, "(SNSYN142) The format of the NUMLINES function is:\n \n NUMLINES(text-expression)"
// *Cause:
// *Action:
35238, 00000, "(SNSYN143) The format of the UPCASE function is:\n \n UPCASE(text-expression)"
// *Cause:
// *Action:
35240, 00000, "(SNSYN144) The format of the TEXTFILL function is:\n \n TEXTFILL(text-expression width)"
// *Cause:
// *Action:
35242, 00000, "(SNSYN145) The format of the INSCHARS function is:\n \n INSCHARS(text-expression characters [after-position])"
// *Cause:
// *Action:
35244, 00000, "(SNSYN146) The format of the INSLINES function is:\n \n INSLINES(text-expression newtext [after-expression])"
// *Cause:
// *Action:
35246, 00000, "(SNSYN147) The format of the REMCHARS function is:\n \n REMCHARS(text-expression start [length])"
// *Cause:
// *Action:
35248, 00000, "(SNSYN148) The format of the REMLINES function is:\n \n REMLINES(text-expression start [length])"
// *Cause:
// *Action:
35250, 00000, "(SNSYN149) The format of the REPLCHARS function is:\n \n REPLCHARS(text-expression characters [start-position])"
// *Cause:
// *Action:
35252, 00000, "(SNSYN150) The format of the REPLLINES function is:\n \n REPLLINES(text-expression newtext [start-line])"
// *Cause:
// *Action:
35254, 00000, "(SNSYN151) The format of the SORTLINES function is:\n \n SORTLINES(text-expression [A|D] [nls_sort [sort-exp]])"
// *Cause:
// *Action:
35256, 00000, "(SNSYN152) The format of the INLIST function is:\n \n INLIST(text-master text-sublist)"
// *Cause:
// *Action:
35258, 00000, "(SNSYN153) The format of the BLANKSTRIP function is:\n \n BLANKSTRIP(text-expression [LEADING|TRAILING|BOTH])"
// *Cause:
// *Action:
35260, 00000, "(SNSYN154) The format of the ARG function is:\n \n ARG(n)\nwhere \"n\" specifies the number of the argument to be returned."
// *Cause:
// *Action:
35262, 00000, "(SNSYN155) The format of the QUAL function is:\n \n QUAL(expression dimension1 dimvalue [dimension2 dimvalue ...])"
// *Cause:
// *Action:
35264, 00000, "(SNSYN156) The format of the ARGFR function is:\n \n ARGFR(start-arg-no)"
// *Cause:
// *Action:
35266, 00000, "(SNSYN157) The format of the CONVERT function is:\n \n CONVERT(expression datatype [options])"
// *Cause:
// *Action:
35268, 00000, "(SNSYN158) The format of the OBJ function is:\n \n OBJ(choice ['name']) or OBJ(choice [text-expression])"
// *Cause:
// *Action:
35270, 00000, "(SNSYN159) The format for this type of aggregation function is:\n \n function(expression [[STATUS] dimensions])"
// *Cause:
// *Action:
35272, 00000, "(SNSYN161) The ROWTOTALS attribute must immediately precede an ACROSS keyword."
// *Cause:
// *Action:
35274, 00000, "(SNSYN162) The first argument to GET must be a data type or the name of a dimension optionally preceded by the word NEW or VALID."
// *Cause:
// *Action:
35276, 00000, "(SNSYN163) The format of the ALLOCATE command is:\n \n ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [USING aggmap]"
// *Cause: The user used incorrect syntax for the ALLOCATE command.
// *Action: Correct the calling syntax.
35278, 00000, "(SNSYN164) A right parenthesis [)] is missing after \"%t\"."
// *Cause:
// *Action:
35280, 00000, "(SNSYN165) The format of the AGGREGATE command is:\n \n AGGREGATE varname1 [varname2 varname3 ...] [USING aggmap-name] [COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA] [FORCEORDER] [PARALLEL #] [{FROM|FROMVAR} fromname [, fromname2 ...]]"
// *Cause: The user used incorrect syntax for the AGGREGATE command.
// *Action: Correct the calling syntax.
35282, 00000, "(SNSYN166) The format of the AGGREGATE function is:\n \n AGGREGATE(varname [USING aggmap-name] [COUNTVAR intvar-name] [FORCECALC] [FORCEORDER] [{FROM|FROMVAR} fromname [, fromname2 ...]])"
// *Cause: The user used incorrect syntax for the AGGREGATE function.
// *Action: Correct the calling syntax.
35284, 00000, "(SNSYN167) The format of the IRR function is:\n \n IRR(cashflows time-dimension)"
// *Cause:
// *Action:
35286, 00000, "(SNSYN168) The format of the NPV function is:\n \n NPV(cashflows discount-rate time-dimension)"
// *Cause:
// *Action:
35288, 00000, "(SNSYN169) The format of a moving function is:\n \n function(expression, start, stop, stepsize, dimension)"
// *Cause:
// *Action:
35290, 00000, "(SNSYN170) The format of the CUMSUM function is:\n \n CUMSUM(expression [STATUS] dimension [resetdimension])"
// *Cause:
// *Action:
35292, 00000, "(SNSYN171) The format of the ISVALUE function is:\n \n ISVALUE(dimension expression)"
// *Cause:
// *Action:
35294, 00000, "(SNSYN173) The format of the STATLEN function is:\n \n STATLEN(dimension)"
// *Cause:
// *Action:
35296, 00000, "(SNSYN174) The format of the STATLIST function is:\n \n STATLIST(dimension [INTEGER] [width])"
// *Cause:
// *Action:
35298, 00000, "(SNSYN175) The format of the STATFIRST function is:\n \n STATFIRST(dimension)"
// *Cause:
// *Action:
35300, 00000, "(SNSYN176) The format of the STATLAST function is:\n \n STATLAST(dimension)"
// *Cause:
// *Action:
35302, 00000, "(SNSYN177) The format of the STATMIN function is:\n \n STATMIN(dimension)"
// *Cause:
// *Action:
35304, 00000, "(SNSYN178) The format of the STATMAX function is:\n \n STATMAX(dimension)"
// *Cause:
// *Action:
35306, 00000, "(SNSYN179) The format of the STATVAL function is:\n \n STATVAL(dimension nth-value-to-find [INTEGER])"
// *Cause:
// *Action:
35308, 00000, "(SNSYN180) The format of the STATRANK function is:\n \n STATRANK(dimension [dimension-value])"
// *Cause:
// *Action:
35310, 00000, "(SNSYN181) The format of the INSTAT function is:\n \n INSTAT(dimension dimension-value)"
// *Cause:
// *Action:
35312, 00000, "(SNSYN182) The format of the COLVAL function is:\n \n COLVAL(column-number)"
// *Cause:
// *Action:
35314, 00000, "(SNSYN183) The format of the RUNTOTAL function is:\n \n RUNTOTAL(subtotal-number)"
// *Cause:
// *Action:
35316, 00000, "(SNSYN184) The format of the SUBTOTAL function is:\n \n SUBTOTAL(subtotal-number)"
// *Cause:
// *Action:
35318, 00000, "(SNSYN185) The format of the INTPART function is:\n \n INTPART(expression)"
// *Cause:
// *Action:
35320, 00000, "(SNSYN186) The format of the SQRT function is:\n \n SQRT(expression)"
// *Cause:
// *Action:
35322, 00000, "(SNSYN187) The format of the LOG function is:\n \n LOG(expression)"
// *Cause:
// *Action:
35324, 00000, "(SNSYN188) The format of the LOG10 function is:\n \n LOG10(expression)"
// *Cause:
// *Action:
35326, 00000, "(SNSYN189) The format of the ABS function is:\n \n ABS(expression)"
// *Cause:
// *Action:
35328, 00000, "(SNSYN190) The format of the REM function is:\n \n REM(expression1 expression2)"
// *Cause:
// *Action:
35330, 00000, "(SNSYN191) The format of the MIN function is:\n \n MIN(expression1 expression2)"
// *Cause:
// *Action:
35332, 00000, "(SNSYN192) The format of the MAX function is:\n \n MAX(expression1 expression2)"
// *Cause:
// *Action:
35334, 00000, "(SNSYN194) The format of the VALUE function is:\n \n VALUE( )"
// *Cause:
// *Action:
35336, 00000, "(SNSYN195) The format of the FILEOPEN function is:\n \n FILEOPEN(filename-expression {READ | WRITE | APPEND} [BINARY] [NLS_CHARSET name])"
// *Cause:
// *Action:
35338, 00000, "(SNSYN196) The format of the FILEGET function is:\n \n FILEGET(fileunit [LENGTH n])"
// *Cause:
// *Action:
35340, 00000, "(SNSYN197) The format of the FILEQUERY function is:\n \n FILEQUERY({fileunit-number | filename-expression} attribute)"
// *Cause:
// *Action:
35342, 00000, "(SNSYN198) The format of the SYSVAR function is:\n \n SYSVAR(system-variable-name)"
// *Cause:
// *Action:
35344, 00000, "(SNSYN199) The format of the VALUES function is:\n \n VALUES(dimension [STATUS|NOSTATUS] [INTEGER])"
// *Cause:
// *Action:
35346, 00000, "(SNSYN201) The format of the LOWCASE function is:\n \n LOWCASE(text-expression)"
// *Cause:
// *Action:
35348, 00000, "(SNSYN202) Invalid format for the FORECAST command."
// *Cause:
// *Action:
35349,000000, "(SNSYN203) The format of the BASEVAL function is:\n \n BASEVAL(concat-dimension)"
// *Cause:
// *Action:
35350, 00000, "(SNSYN206) The format of the KEY function is:\n \n KEY(conjoint-dimension, base-dimension)"
// *Cause:
// *Action:
35351,000000, "(SNSYN204) The format of the BASEDIM function is:\n \n BASEDIM(concat-dimension [LEAF])"
// *Cause:
// *Action:
35352, 00000, "(SNSYN207) The format of the COMSET command is:\n \n COMSET TYPE SOCKET"
// *Cause:
// *Action:
35353, 00000, "(SNSYN205) The format of the MDQUERY function is:\n \n MDQUERY(object-type, schema-name, object-name [, refresh|norefresh])"
// *Cause:
// *Action:
35354, 00000, "(SNSYN208) The format of the COMSET function is:\n \n COMSET(TYPE)"
// *Cause:
// *Action:
35355, 00000, "(SNSYN209) Invalid format for the AW command."
// *Cause:
// *Action:
35356, 00000, "(SNSYN210) The format of the NUMTODSINTERVAL function is:\n \n NUMTODSINTERVAL(number, day|hour|minute|second)"
// *Cause:
// *Action:
35357, 00000, "(SNSYN211) The format of the NUMTOYMINTERVAL function is:\n \n NUMTOYMINTERVAL(number, year|month)"
// *Cause:
// *Action:
35358, 00000, "(SNSYN214) The format of the NAFILL function is:\n \n NAFILL( source-exp, fill-exp )"
// *Cause:
// *Action:
35360, 00000, "(SNSYN215) The format of the FILENEXT function is:\n \n FILENEXT(fileunit)"
// *Cause:
// *Action:
35362, 00000, "(SNSYN216) The format of the RECNO function is:\n \n RECNO(fileunit)"
// *Cause:
// *Action:
35364, 00000, "(SNSYN217) The format of the ROUND function is:\n \n ROUND(expression1 [, expression2])"
// *Cause:
// *Action:
35366, 00000, "(SNSYN218) The format for exporting an expression is \"expression AS name\" or \"SCATTER AS namevar [ TYPE typevar ]\"."
// *Cause:
// *Action:
35368, 00000, "(SNSYN219) The format of the ROW function is:\n \n ROW(list-of-column-descriptions)"
// *Cause:
// *Action:
35370, 00000, "(SNSYN220) The format of the AW function is:\n \n AW(subfunction [, analytic workspace-name-expression])"
// *Cause:
// *Action:
35372, 00000, "(SNSYN221) The format of the OBJLIST function is:\n \n OBJLIST[(analytic workspace-list-expression)]"
// *Cause:
// *Action:
35374, 00000, "(SNSYN222) The format of the UNIQUELINES function is:\n \n UNIQUELINES(text-expression [nls_sort [sort-exp]])"
// *Cause:
// *Action:
35376, 00000, "(SNSYN223) The format of the JOINCOLS function is:\n \n JOINCOLS(text-expression1 [, text-expression2 ... ])"
// *Cause:
// *Action:
35378, 00000, "(SNSYN224) The format of the EXTCOLS function is:\n \n EXTCOLS(text-expression [start [length]])"
// *Cause:
// *Action:
35380, 00000, "(SNSYN225) The format of the REMCOLS function is:\n \n REMCOLS(text-expression, start [, length])"
// *Cause:
// *Action:
35382, 00000, "(SNSYN226) The format of the REPLCOLS function is:\n \n REPLCOLS(text-expression, overlay-expression [, start-position])"
// *Cause:
// *Action:
35384, 00000, "(SNSYN227) The format of the INSCOLS function is:\n \n INSCOLS(text-expression, insert-expression [, after-position])"
// *Cause:
// *Action:
35386, 00000, "(SNSYN228) The format of MCALC is:\n \n MCALC(expression [ALWAYS] [SCREENBY expr] \n [method [OF] member-expr [WEIGHTBY expr]] ...)"
// *Cause:
// *Action:
35388, 00000, "(SNSYN229) The format of the DDOF function is:\n \n DDOF(expression)"
// *Cause:
// *Action:
35390, 00000, "(SNSYN230) The format of the MMOF function is:\n \n MMOF(expression)"
// *Cause:
// *Action:
35392, 00000, "(SNSYN231) The format of the YYOF function is:\n \n YYOF(expression)"
// *Cause:
// *Action:
35394, 00000, "(SNSYN232) The format of the DAYOF function is:\n \n DAYOF(expression)"
// *Cause:
// *Action:
35396, 00000, "(SNSYN233) The format of the SIN function is:\n \n SIN(expression)"
// *Cause:
// *Action:
35398, 00000, "(SNSYN234) The format of the COS function is:\n \n COS(expression)"
// *Cause:
// *Action:
35400, 00000, "(SNSYN235) The format of the MAKEDATE function is:\n \n MAKEDATE(year month day)"
// *Cause:
// *Action:
35402, 00000, "(SNSYN236) The format of the ANTILOG function is:\n \n ANTILOG(expression)"
// *Cause:
// *Action:
35404, 00000, "(SNSYN237) The format of the ANTILOG10 function is:\n \n ANTILOG10(expression)"
// *Cause:
// *Action:
35406, 00000, "(SNSYN238) The format of the ROLLUP command is:\n \n ROLLUP variable [OVER dimension] [USING relationship]"
// *Cause:
// *Action:
35408, 00000, "(SNSYN239) The format of the STARTOF function is:\n \n STARTOF(expression)"
// *Cause:
// *Action:
35410, 00000, "(SNSYN240) The format of the ENDOF function is:\n \n ENDOF(expression)"
// *Cause:
// *Action:
35412, 00000, "(SNSYN241) The format of the BEGINDATE function is :\n \n BEGINDATE(time-dimension-value)"
// *Cause:
// *Action:
35414, 00000, "(SNSYN242) The format of the ENDDATE function is :\n \n ENDDATE(time-dimension-value)"
// *Cause:
// *Action:
35416, 00000, "(SNSYN243) The format of the TCONVERT function is:\n \n TCONVERT(expression time-dimension method [method])"
// *Cause:
// *Action:
35418, 00000, "(SNSYN244) The format of the FILEERROR function is:\n \n FILEERROR(TYPE | POSITION | WIDTH | VALUE | DIMENSION | RESET)"
// *Cause:
// *Action:
35420, 00000, "(SNSYN245) The format of a payment or interest function is:\n \n FUNCTION(principal, rate, num-payments [time-dimension])"
// *Cause:
// *Action:
35422, 00000, "(SNSYN246) The format of the DEPRSL function is:\n \n DEPRSL(beg-val, end-val, num-pds, [FULL | HALF | exp, [time-dim]])"
// *Cause:
// *Action:
35424, 00000, "(SNSYN247) The format of DEPRDECL is:\n \n DEPRDECL(beg, end, n-pds, [decl-factor,\n [FULL | HALF | exp, [time dim]]])"
// *Cause:
// *Action:
35426, 00000, "(SNSYN248) The format of the DEPRSOYD function is:\n \n DEPRSOYD(beg-val, end-val, num-pds, [FULL | HALF | exp, [time-dim]])"
// *Cause:
// *Action:
35428, 00000, "(SNSYN249) The format of the GROWRATE function is:\n \n GROWRATE(expression [time dim])"
// *Cause:
// *Action:
35430, 00000, "(SNSYN250) The format of the NORMAL function is:\n \n NORMAL(mean, standard-deviation)"
// *Cause:
// *Action:
35432, 00000, "(SNSYN251) The format of DEPRDECLSW is:\n \n DEPRDECLSW(beg-val, end-val, num-pds, [decl-factor,\n FULL|HALF|exp, [sw-pd, [time dim]]]])"
// *Cause:
// *Action:
35434, 00000, "(SNSYN265) Invalid format for CHGDFN command."
// *Cause:
// *Action:
35436, 00000, "(SNSYN267) The format of the WEEKOF function is:\n \n WEEKOF(expression)"
// *Cause:
// *Action:
35438, 00000, "(SNSYN268) The format of the PERMIT command is: \n \n PERMIT READ|WRITE|MAINTAIN|PERMIT [WHEN bool-exp [BY bool-exp]]"
// *Cause:
// *Action:
35440, 00000, "(SNSYN269) The format of the PERMITRESET command is: \n \n PERMITRESET [name] [READ|WRITE]"
// *Cause:
// *Action:
35442, 00000, "(SNSYN270) The format of the PROPERTY command is:\n \n PROPERTY {prop-name [,] value} | {DELETE {ALL | prop-name}}"
// *Cause:
// *Action:
35444, 00000, "(SNSYN271) The format of the TRANSLATEBYTES function is:\n \n TRANSLATEBYTES(text 256-char-table)"
// *Cause:
// *Action:
35446, 00000, "(SNSYN274) The format of the LIMIT function is:\n \n LIMIT(limit arguments)"
// *Cause:
// *Action:
35448, 00000, "(SNSYN276) The keyword USING must be followed by a dimension list in angle brackets <>."
// *Cause:
// *Action:
35450, 00000, "(SNSYN277) The format of the CHANGECHARS function is:\n \n CHANGECHARS(text-expr oldtext newtext [num-to-change] [UPCASE])"
// *Cause:
// *Action:
35456, 00000, "(SNSYN281) The word %t must be followed by an unsigned number."
// *Cause:
// *Action:
35458, 00000, "(SNSYN282) The format of the ARCSIN function is:\n \n ARCSIN(expression)"
// *Cause:
// *Action:
35460, 00000, "(SNSYN283) The format of the ARCTAN function is:\n \n ARCTAN(expression)"
// *Cause:
// *Action:
35462, 00000, "(SNSYN284) The format of the COSH function is:\n \n COSH(expression)"
// *Cause:
// *Action:
35464, 00000, "(SNSYN285) The format of the SINH function is:\n \n SINH(expression)"
// *Cause:
// *Action:
35466, 00000, "(SNSYN286) The format of the TANH function is:\n \n TANH(expression)"
// *Cause:
// *Action:
35468, 00000, "(SNSYN287) The format of the TAN function is:\n \n TAN(expression)"
// *Cause:
// *Action:
35470, 00000, "(SNSYN288) The format of the ARCCOS function is:\n \n ARCCOS(expression)"
// *Cause:
// *Action:
35472, 00000, "(SNSYN301) The format of the MAXCHARS function is:\n \n MAXCHARS(text-expression)"
// *Cause:
// *Action:
35474, 00000, "(SNSYN305) The format of the STATALL function is:\n \n STATALL(dimension)"
// *Cause:
// *Action:
35476, 00000, "(SNSYN306) The format of the EXTBYTES function is:\n \n EXTBYTES(text-expression [start [length]])"
// *Cause:
// *Action:
35478, 00000, "(SNSYN307) The format of the FINDBYTES function is:\n \n FINDBYTES(search-text find-text [start [LINENUM]])"
// *Cause:
// *Action:
35480, 00000, "(SNSYN308) The format of the JOINBYTES function is:\n \n JOINBYTES(text-expression1 text-expression2 ...)"
// *Cause:
// *Action:
35482, 00000, "(SNSYN309) The format of the NUMBYTES function is:\n \n NUMBYTES(text-expression)"
// *Cause:
// *Action:
35484, 00000, "(SNSYN310) The format of the INSBYTES function is:\n \n INSBYTES(text-expression bytes [after-position])"
// *Cause:
// *Action:
35486, 00000, "(SNSYN311) The format of the REMBYTES function is:\n \n REMBYTES(text-expression start [length])"
// *Cause:
// *Action:
35488, 00000, "(SNSYN312) The format of the REPLBYTES function is:\n \n REPLBYTES(text-expression bytes [start-position])"
// *Cause:
// *Action:
35490, 00000, "(SNSYN313) The format of the CHANGEBYTES function is:\n \n CHANGEBYTES(text-expression oldtext newtext [number-to-change])"
// *Cause:
// *Action:
35492, 00000, "(SNSYN314) The format of the MAXBYTES function is:\n \n MAXBYTES(text-expression)"
// *Cause:
// *Action:
35494, 00000, "(SNSYN315) The word ACROSS must be followed by a dimension name."
// *Cause:
// *Action:
35496, 00000, "(SNSYN316) The format of the FILTERLINES function is:\n \n FILTERLINES(source-exp, filter-exp)"
// *Cause:
// *Action:
35498, 00000, "(SNSYN318) The format of the DBGOUTFILE command is:\n \n DBGOUTFILE [APPEND] {EOF | filename [NOCACHE]}"
// *Cause:
// *Action:
35500, 00000, "(SNSYN319) The format of the OBSCURE function is:\n \n OBSCURE ({HASH | HIDE | UNHIDE | ENCRYPT} [, TEXT],\n seed-text, input-text)"
// *Cause:
// *Action:
35502, 00000, "(SNSYN324) INSERT must be followed by FIRST, LAST, BEFORE dimension-value, or AFTER dimension-value."
// *Cause:
// *Action:
35504, 00000, "(SNSYN325) Invalid format for IMPORT command."
// *Cause:
// *Action:
35510, 00000, "(SNSYN330) The format of the CATEGORIZE function is:\n \n CATEGORIZE(expression {group literal list | group expression})"
// *Cause:
// *Action:
35512, 00000, "(SNSYN331) The format of the CORRELATION function is:\n \n CORRELATION(expression1, expression2, method, [BASEDON dimension1 [dimension2 ...]])"
// *Cause:
// *Action:
35514, 00000, "(SNSYN332) The format of the MODE function is:\n \n MODE(expression, BASEDON dimension)"
// *Cause:
// *Action:
35516, 00000, "(SNSYN333) The format of the PERCENTAGE function is:\n \n PERCENTAGE(expression [BASEDON dimension1 [dimension2 ...]])"
// *Cause:
// *Action:
35518, 00000, "(SNSYN334) The format of the RANK function is:\n \n RANK(expression, method, BASEDON dimension)"
// *Cause:
// *Action:
35520, 00000, "(SNSYN335) The format of the SMOOTH function is:\n \n SMOOTH(expression, method, parameters [BASEDON dimension1 [dimension2 ...]])"
// *Cause:
// *Action:
35522, 00000, "(SNSYN336) The format of the NLSITEMS function is:\n \n NLSITEMS({LANGUAGE | TERRITORY})"
// *Cause:
// *Action:
35524, 00000, "(SNSYN337) The format of the NLSAVAIL function is:\n \n NLSAVAIL({LANGUAGE | TERRITORY} itemname)"
// *Cause:
// *Action:
35526, 00000, "(SORTENG10A) The expression for TOP or BOTTOM has a value of NA."
// *Cause:
// *Action:
35528, 00000, "(SORTENG10B) In the TOP or BOTTOM phrase, you requested a negative number of dimension values (%d)."
// *Cause:
// *Action:
35529, 00000, "(SORTENG10D) You cannot sort more than 2**31 - 1 values."
// *Cause:
// *Action:
35530, 00000, "(SORTENG10C) You cannot specify a percentage greater than 100 or less than 0. You requested %f."
// *Cause:
// *Action:
35532, 00000, "(SPSFILE1) The file you specified is not in %s format."
// *Cause:
// *Action:
35534, 00000, "(SPSFILE2) %s files require worksheets with only two dimensions."
// *Cause:
// *Action:
35536, 00000, "(SPSFILE3) PRN files require worksheets with only two dimensions."
// *Cause:
// *Action:
35538, 00000, "(SPSIDIF01) %a %s %s\nA record (%1p) that was not in DIF format was read while importing file %2p."
// *Cause:
// *Action:
35540, 00000, "(SPSIWKS1) An unexpected end-of-file occurred in spreadsheet file %s. Check your data to make sure you imported all you expected."
// *Cause:
// *Action:
35542, 00000, "(SPSRREC01) An unexpected end-of-file occurred while importing file %s. Check your data to make sure you imported all you expected."
// *Cause:
// *Action:
35544, 00000, "(SQA03) %a %d %s\nThe SQL data in column %1p of your fetch statement cannot be converted to type %2p."
// *Cause:
// *Action:
35548, 00000, "(SQCGEXE01) SQL statement-name '%t' has not been prepared in the current program."
// *Cause:
// *Action:
35550, 00000, "(SQCGOPN01) SQL cursor '%t' has not been declared in the current program."
// *Cause:
// *Action:
35554, 00000, "(SQCSRNAM00) %a %v %d\nSQL cursor name '%1p' has an invalid length of %2p. A cursor name must have a length of 1 to 18 bytes, inclusive."
// *Cause:
// *Action:
35556, 00000, "(SQCSRNAM01) SQL cursor name '%v' has an invalid first character. Use a-z, @, # or $."
// *Cause:
// *Action:
35558, 00000, "(SQCSRNAM02) SQL cursor name '%v' contains an invalid character. Use a-z, 0-9, @, #, $ and _."
// *Cause:
// *Action:
35559, 00000, "(SQCSRNAM03) SQL cursor name cannot be INTO."
// *Cause:
// *Action:
35560, 00000, "(SQGETCD01) Conjoint dimension %j cannot be an input host variable. You can use the current values of its bases via the KEY function."
// *Cause:
// *Action:
35561, 00000, "(XSRWLD01) Object %n is not a valid target."
// *Cause: An invalid object was specified as a target.
// *Action: Choose a valid object as a target.
35562, 00000, "(SQLIMP01) %a %d %d\nThe SQL IMPORT command will produce %1p columns of output, but you have provided %2p host variables in your INTO clause."
// *Cause: The expression is the source query do not match the targets in the INTO clause.
// *Action: Make sure the the expressions in the source query match the targets in the INTO clause.
35563, 00000, "(XSRWLD17) Multiple values exist for an attribute of this dimension member."
// *Cause: Multiple source table rows containing different values for a dimension attribute were found.
// Only the first of the multiple rows has been loaded.
// *Action: Fix the mapping or remove the rows with conflicting attribute values.
35564, 00000, "(XSRWLD02) %a %s %s\nCannot convert from the %1p type to the %2p type."
// *Cause: Conversion from source to target is not allowed
// *Action: Choose a different target datatype
35565, 00000, "(XSRWLD03) For object %n only APPEND, MATCH or ASSIGN may be used."
// *Cause: An incorrect setting was applied to the target
// *Action: For DIMENSIONs use APPEND or MATCH, for SURROGATEs use ASSIGN.
35566, 00000, "(XSRWLD04) Object %n cannot be used with QDRs"
// *Cause: A QDR was placed on a target dimension
// *Action: Remove the QDR on the target dimension
35568, 00000, "(SQLIMP03) The datatype of variable %v should be INTEGER, LONGINTEGER or SHORTINTEGER."
// *Cause: The target variable was not INTEGER, LONGINTEGER or SHORTINTEGER.
// *Action: The target variable must be INTEGER, LONGINTEGER or SHORTINTEGER.
35569, 00000, "(XSRWLD05) %a %s %s %d\nAn error was encountered in converting data %1p to %2p in column %3p."
// *Cause: The data could not be converted to the target datatype.
// *Action: Ensure the source data is valid for the target datatype.
35570, 00000, "(XSRWLD06) A column value is not a valid member of its target dimension."
// *Cause: The source value for a dimension is not an existing member of the dimension.
// *Action: Ensure the column value is an existing member of its target dimension.
35571, 00000, "(XSRWLD07) The maximum number of load errors has occurred. No changes from this step were committed to the database."
// *Cause: The number of load errors exceeded the specified maximum.
// *Action: Fix the load errors, or increase the maximum number allowed and rerun the load.
35572, 00000, "(XSRWLD08) A column value is not a valid member of its related dimension."
// *Cause: The source data for a relation is not a member of the related dimension.
// *Action: Ensure the source data is a valid member of the related dimension.
35573, 00000, "(XSRWLD09) An incoming dimension value is null."
// *Cause: A source value for a dimension is null.
// *Action: Ensure the source data for the dimension is not null.
35574, 00000, "(SQLOUT02) SQL cursor '%v' is not known in the current logical unit of work."
// *Cause:
// *Action:
35575, 00000, "(SQLOUT04) %a %s %d %d\nThe %1p command will produce %2p columns of output, but you have provided %3p host variables in your INTO clause."
// *Cause:
// *Action:
35576, 00000, "(SQLOUT09) SQL cursor '%v' is not open."
// *Cause:
// *Action:
35577, 00000, "(SQLOUT10) SQL cursor '%v' has already been declared with a different SELECT statement."
// *Cause:
// *Action:
35578, 00000, "(SQLOUT11) SQL cursor '%v' cannot be used with CURRENT OF <cursor name> syntax"
// *Cause: The CURRENT OF <cursor> syntax in the WHERE clause tried to use a cursor that was not declared with the FOR UPDATE [ of <column name> ] SQL syntax.
// *Action: Add the FOR UPDATE [ OF <column name> ] SQL syntax to the cursor specified.
35579, 00000, "(SQLOUT12) SQL cursor '%v' has already been opened."
// *Cause:
// *Action:
35580, 00000, "(XSRWLD10) An incoming column contains a data type mismatch."
// *Cause: The data could not be converted to the target datatype.
// *Action: Ensure the source data is valid for the target datatype.
35581, 00000, "(XSRWLD11) You do not have permission to write this value of the target."
// *Cause: You do not have sufficient permissions to write to the specified target.
// *Action: Ask the owner of the schema or OLAP DBA to grant you sufficient permissions.
35582,00000, "(XSRWLD12) %a %v %v %v\nCannot change the level of dimension member \"%1p\" from \"%2p\" to \"%3p\" within a single load."
// *Cause: A dimension member is mapped to more than one level.
// *Action: Change the mapping so that each dimension member is mapped
// to only one level.
35583,00000, "(XSRWLD13) Cannot change the level of a dimension member within a single load."
// *Cause: A dimension member is mapped to more than one level.
// *Action: Change the mapping so that each dimension member is mapped
// to only one level.
35584, 00000, "(SQLOUT17) %a %s %d\nThe %1p procedure requires %2p parameters."
// *Cause:
// *Action:
35585,00000, "(XSRWLD14) This SQL query generated rejected records."
// *Cause: Rejected records were generated by this query.
// *Action: Locate the records that were rejected and resolve the rejection (for example, data, mapping, and so on).
35586, 00000, "(SQLOUT19) The parameter list passed to the procedure is syntactically incorrect."
// *Cause:
// *Action:
35587, 00000, "(SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of %d levels."
// *Cause: The nesting of table functions with the PREDMLCMD token populated
// with an OLAP DML expression that use the embedded SQL support to access
// another table function which contains a table functions with the
// PREDMLCMD token filled in with an OLAP DML expression that uses the
// embedded SQL support.
// *Action: Reduce the level of nesting between table functions and OLAP DML
// embedded SQL support.
35588,00000, "(XSRWLD15) %a %v %v %v\nCannot change the parent of existing dimension member \"%1p\" from \"%2p\" to \"%3p\" in LOAD RETAIN mode."
// *Cause: An attempt was made to change the parent of an existing dimension
// member in LOAD RETAIN mode.
// *Action: Fix the mapping or use LOAD [NO] SYNCH mode.
35589,00000, "(XSRWLD16) Cannot change the parent of an existing dimension member in LOAD RETAIN mode."
// *Cause: An attempt was made to change the parent of an existing dimension
// member in LOAD RETAIN mode.
// *Action: Fix the mapping or use LOAD [NO] SYNCH mode.
35590, 00000, "(SQPHRASE01) The host variable expression has invalid syntax."
// *Cause:
// *Action:
35592, 00000, "(SQRT00) The argument to SQRT is negative. Set ROOTOFNEGATIVE to YES if you want NA to be returned for the root of a negative number."
// *Cause:
// *Action:
35594, 00000, "(SSCGEXP01) The LIMIT criterion expression must be dimensioned by %j."
// *Cause:
// *Action:
35596, 00000, "(SSCGEXP02) %a %j %j\nThe LIMIT criterion expression must be dimensioned by %1p, which is a component of %2p."
// *Cause:
// *Action:
35600, 00000, "(SSCGLIMT01) The IFNONE label is not allowed when you specify NULL status."
// *Cause:
// *Action:
35602, 00000, "(SSCGLIMT02) You cannot limit dimension composite %j."
// *Cause:
// *Action:
35603, 00000, "(SSCGLIMT03) You cannot limit PARTITION TEMPLATE %j."
// *Cause:
// *Action:
35604, 00000, "(SSCGNULL01) The phrase \"IFNONE label\" can only be used when the LIMIT command executes in a program."
// *Cause:
// *Action:
35606, 00000, "(SSCGNULL02) %t is not defined as a label."
// *Cause:
// *Action:
35608, 00000, "(SSCGPOS01) You cannot limit a dimension to values of type %s. Use the CONVERT function if necessary."
// *Cause:
// *Action:
35610, 00000, "(SSCGREL01) %a %j %j\n%1p and %2p are not related."
// *Cause:
// *Action:
35612, 00000, "(SSCGREL02) Related dimension values are not allowed when you specify a scalar or multi-dimensional relationship array."
// *Cause:
// *Action:
35614, 00000, "(SSCGREL03) %a %j %j\n%1p is not a relationship involving %2p."
// *Cause:
// *Action:
35622, 00000, "(SSCGREL07) %a %q %j\n%1p is not a relation of %2p."
// *Cause:
// *Action:
35623, 00000, "(XSSCLLEV07) %a %q %j\n%1p is not a valueset of %2p."
// *Cause:
// *Action:
35624, 00000, "(SSCGREL08) %a %q %j\n%1p is not dimensioned by %2p."
// *Cause:
// *Action:
35625, 00000, "(XSSCLLEV08) %a %j %j\n%1p is not dimensioned by %2p."
// *Cause:
// *Action:
35626, 00000, "(SSCGREL09) %j is not related to itself."
// *Cause:
// *Action:
35627, 00000, "(XSSCLEV09) %q is not a relationship array."
// *Cause:
// *Action:
35628, 00000, "(SSCGREL10) %a %j %j\n%2p is not a dimension of relation %1p."
// *Cause:
// *Action:
35629, 00000, "(XSBASLIM00) %j does not have base dimensions."
// *Cause:
// *Action:
35630, 00000, "(SSCGREL11) %a %j %j\nWhile limiting dimension %2p, you cannot use it to qualify relation %1p."
// *Cause:
// *Action:
35632, 00000, "(SSCGREL12) %a %j %j\nWhile limiting an alias of %2p, you cannot use it to qualify relation %1p."
// *Cause:
// *Action:
35633, 00000, "(STATEQ01) Both arguments to STATEQUAL must be status lists of the same dimension."
// *Cause:
// *Action:
35634, 00000, "(SSCGVALS01) The format of a related dimension list is:\n related-dimension [valuelist] | relationship-array-name"
// *Cause:
// *Action:
35636, 00000, "(SSCGVALS02) %j is a dimension composite and its position numbers cannot be used in LIMIT NOCONVERT."
// *Cause:
// *Action:
35638, 00000, "(SSEXECUT02) NA is not a value of %j."
// *Cause:
// *Action:
35640, 00000, "(SSEXECUT03) You cannot MAINTAIN ADD %j while it is being LIMITed."
// *Cause:
// *Action:
35642, 00000, "(SSEXECUT07A) The expression for the beginning of the dimension range has a value of NA."
// *Cause:
// *Action:
35644, 00000, "(SSEXECUT07B) The expression for the end of the dimension range has a value of NA."
// *Cause:
// *Action:
35646, 00000, "(SSEXECUT08) The expression for BEFORE or AFTER has a value of NA."
// *Cause:
// *Action:
35648, 00000, "(SSEXECUT09) The expression for FIRST or LAST has a value of NA."
// *Cause:
// *Action:
35650, 00000, "(SSEXECUT15) The expression for BEFORE or AFTER is not in current status."
// *Cause:
// *Action:
35652, 00000, "(SSFRLST01) In the FIRST or LAST phrase, you requested a negative number of dimension values (%d)."
// *Cause:
// *Action:
35654, 00000, "(SSNULL) The status of the %j dimension cannot be set to null."
// *Cause:
// *Action:
35656, 00000, "(STATCHK00) %j has no values in status."
// *Cause:
// *Action:
35658, 00000, "(STATLIST01) The data width argument to the STATLIST function must be greater than zero."
// *Cause:
// *Action:
35660, 00000, "(STATVAL03) %a %j %ld\nThe %1p dimension does not have a status value numbered %2p."
// *Cause:
// *Action:
35662, 00000, "(STKTOINF01) %a %d %d\nThe width argument to the CONVERT(... INFILE) function was %1p. The limit is %2p."
// *Cause:
// *Action:
35664, 00000, "(STKTOINF02) %a %d %d\nConversion to INFILE would produce a value %2p bytes wide, exceeding the maximum input line length %1p."
// *Cause:
// *Action:
35666, 00000, "(STRBYT01) NTEXT arguments to the BYTE functions must be converted to TEXT. Use CONVERT(value TEXT NOTRANSLATE) to avoid translation."
// *Cause:
// *Action:
35668, 00000, "(STRCHG01) The oldtext and newtext arguments must be single-line text values."
// *Cause:
// *Action:
35670, 00000, "(STRCHG02) The oldtext argument must contain at least one character."
// *Cause:
// *Action:
35672, 00000, "(STRCHG03) The number-to-change argument must be greater than 0."
// *Cause:
// *Action:
35674, 00000, "(STRDEL01) The position of the first character to remove must be at least 1."
// *Cause:
// *Action:
35676, 00000, "(STRDEL02) You must remove at least one character. You cannot remove %d characters."
// *Cause:
// *Action:
35678, 00000, "(STREXTR01) The position of the first character to extract must be greater than zero. You cannot start extracting at position %d."
// *Cause:
// *Action:
35680, 00000, "(STREXTR02) You must extract at least one character. You cannot extract %d characters."
// *Cause:
// *Action:
35682, 00000, "(STRFIND01) The start argument must be at least 1."
// *Cause:
// *Action:
35684, 00000, "(STRINS01) Insertion must begin after a character position of zero or greater."
// *Cause:
// *Action:
35686, 00000, "(STRINS02) %a %d %d\nThe length of one line of a text value cannot exceed %1p characters. You attempted to create a line with %2p characters."
// *Cause:
// *Action:
35688, 00000, "(STRREP01) The position of the first character to replace must be at least 1."
// *Cause:
// *Action:
35690, 00000, "(SUBGONE00) You have requested a feature or used a command that is not supported in this release."
// *Cause:
// *Action:
35692, 00000, "(TDENDPT00) Dimension %j is empty."
// *Cause:
// *Action:
35694, 00000, "(TDINCNUM00) You attempted to work with a date outside of the allowable range."
// *Cause:
// *Action:
35696, 00000, "(TEXTFENG01) The data width argument to the TEXTFILL function must be greater than zero."
// *Cause:
// *Action:
35698, 00000, "(TFGROUP01) Dimension %j appears in more than one GROUP phrase, either directly or via a dimension composite or conjoint dimension."
// *Cause:
// *Action:
35700, 00000, "(TFGROUP02) An expression used in a GROUP phrase must have exactly one dimension."
// *Cause:
// *Action:
35702, 00000, "(TFPARSE01) Dimension %j appears in both the DOWN phrase and a GROUP phrase, either directly or via a conjoint dimension or composite."
// *Cause:
// *Action:
35704, 00000, "(TFPARSE02) Dimension %j appears in both the DOWN phrase and an ACROSS phrase, either directly or via a conjoint dimension or composite."
// *Cause:
// *Action:
35706, 00000, "(TFPARSE03) Dimension %j appears both inside and outside an ACROSS loop."
// *Cause:
// *Action:
35708, 00000, "(TFPARSE04) The expressions used in the DOWN phrase must all have the same single dimension."
// *Cause:
// *Action:
35710, 00000, "(TFPARSE05) The DOWN phrase must be a single expression or a list of expressions enclosed in angle brackets <>."
// *Cause:
// *Action:
35712, 00000, "(TFPARSE07) Dimension %j appears in both an ACROSS phrase and a GROUP phrase, either directly or via a conjoint dimension or composite."
// *Cause:
// *Action:
35716, 00000, "(TRIGGER00) NA trigger calls exceed the maximum allowable depth of %d."
// *Cause:
// *Action:
35718, 00000, "(TRIGGER01) The NA trigger expression for variable %n contains a format error."
// *Cause:
// *Action:
35720, 00000, "(TRIGGER02) The NA trigger for %n could not be executed recursively because the RECURSIVE option is set to NO."
// *Cause:
// *Action:
35726, 00000, "(TSFENG01) %a %d %d\nThe starting point (%1p) for a moving function must be less than or equal to the stopping point (%2p)."
// *Cause:
// *Action:
35728, 00000, "(TSFENG02) The step value (%d) for a moving function must be greater than zero."
// *Cause:
// *Action:
35730, 00000, "(TSFENG03) The starting point, stopping point, and step value for a moving function cannot be NA."
// *Cause:
// *Action:
35732, 00000, "(UNITCHEK01) %d is an invalid file unit number."
// *Cause:
// *Action:
35734, 00000, "(UNITCHEK02) File unit %d is not open."
// *Cause:
// *Action:
35736, 00000, "(VALNAME01) You cannot define NAME. NAME is a special reserved dimension used to organize your analytic workspace dictionary."
// *Cause:
// *Action:
35738, 00000, "(VCLEX01) \"%v\" is not a valid dimension value because it contains invalid characters or blanks, but it is not enclosed in single quotes."
// *Cause:
// *Action:
35740, 00000, "(VCLEX02) %t is too large to be an integer."
// *Cause:
// *Action:
35742, 00000, "(VCLEX06) %a %v %s\n%1p already exists in the %2p analytic workspace."
// *Cause:
// *Action:
35744, 00000, "(VCLEX07) \"%v\" is not a valid name because it contains invalid characters or blanks."
// *Cause:
// *Action:
35746, 00000, "(VCLEX08) %t is too large to be a short integer."
// *Cause:
// *Action:
35748, 00000, "(VCOVRFLW01) %a %d %d\nA text value cannot be more than %1p characters long. Your value is %2p characters long."
// *Cause:
// *Action:
35749, 00000, "(VCHEX01) '%c' is not a valid hexadecimal digit."
// *Cause: The text being converted contains an invalid hexadecimal digit.
// *Action: Replace the character with a digit in the range 0-9 or A-F.
35750, 00000, "(VCTOBOOL01) A multiline text value cannot be converted to a BOOLEAN."
// *Cause:
// *Action:
35752, 00000, "(VCTODT00) '%i' is not a valid date order. Valid orders are YMD, YDM, MYD, MDY, DMY, and DYM."
// *Cause:
// *Action:
35754, 00000, "(VCTODT01) %a %v %d\n'%1p' is not a valid date because %2p is out of range for a month."
// *Cause:
// *Action:
35756, 00000, "(VCTODT02) %a %v %d\n'%1p' is not a valid date because %2p is out of range for a year."
// *Cause:n'%1p'
// *Action:
35758, 00000, "(VCTODT03) %a %v %d\n'%1p' is not a valid date because %2p is out of range for a day of the month."
// *Cause:
// *Action:
35760, 00000, "(VCTODT04) '%v' is not a valid date because it is ambiguous."
// *Cause:
// *Action:
35762, 00000, "(VCTODT05) '%v' is not a valid packed numeric date."
// *Cause:
// *Action:
35764, 00000, "(VCTODT06) '%v' is not a valid date."
// *Cause:
// *Action:
35766, 00000, "(VCTODT07) %a %v %j\n'%1p' is not a valid date or name for the %2p dimension."
// *Cause:
// *Action:
35768, 00000, "(VCTODT08) %a %v %j %d\n'%1p' is not a valid name for %2p, because the period %3p is out of range."
// *Cause:
// *Action:
35770, 00000, "(VCTODT15) %a %v %i\n'%1p' is not a valid date. The numeric field '%2p' cannot be interpreted."
// *Cause:
// *Action:
35772, 00000, "(VCTODT16) %a %v %i\n'%1p' is not a valid date. '%2p' is the second year field encountered."
// *Cause:
// *Action:
35774, 00000, "(VCTODT17) %a %v %i\n'%1p' is not a valid date. A second alphabetic field, '%2p', is not allowed."
// *Cause:
// *Action:
35776, 00000, "(VCTODT18) '%v' is not a valid date. A date cannot end with a separation character."
// *Cause:
// *Action:
35778, 00000, "(VCTODT19) %a %v %i\n'%1p' is not a valid date. Input after '%2p' is extra."
// *Cause:
// *Action:
35780, 00000, "(VCTODT20) A date cannot be an empty string."
// *Cause:
// *Action:
35782, 00000, "(VCTODT21) '%v' is not a valid date because it is incomplete."
// *Cause:
// *Action:
35784, 00000, "(VCTODT22) '%v' is not a valid date. Packed numeric notation must be 6 or 8 digits long."
// *Cause:
// *Action:
35786, 00000, "(VCTODT23) %a %v %i\n'%1p' is not a valid date. '%2p' cannot be recognized as a month name."
// *Cause:
// *Action:
35788, 00000, "(VCTODT24) %a %v %i\n'%1p' is not a valid date. There are too many leading zeros beginning at '%2p'."
// *Cause:
// *Action:
35790, 00000, "(VCTODT25) %a %v %i\n'%1p' is not a valid date. A date cannot begin with '%2p'."
// *Cause:
// *Action:
35792, 00000, "(VCTODT27) %a %v %i\n'%1p' is not a valid date. '%2p' is not a valid character."
// *Cause:
// *Action:
35794, 00000, "(VCTORD01) A multiline text value cannot be converted to a number."
// *Cause:
// *Action:
35796, 00000, "(VERFAIL01) Your response does not meet the requirements for this item."
// *Cause:
// *Action:
35798, 00000, "(VERFAIL02) %s"
// *Cause:
// *Action:
35800, 00000, "(VSDOKAY01) %a %j %v %j %j\nDiscarding compiled code for %1p, because %2p now resolves to a value of %3p. Previously, it resolved to a value of %4p."
// *Cause:
// *Action:
35802, 00000, "(VSDOKAY02) %a %j %v %j\nDiscarding compiled code for %1p, because %2p is no longer a value of %3p."
// *Cause:
// *Action:
35804, 00000, "(WATCHXEQ01) %a %d %v %j\nWatch point %1p: %2p is true in %3p at statement:"
// *Cause:
// *Action:
35810, 00000, "(XSINPUTERR) The command has requested more input than was supplied in the command string."
// *Cause: The command required input that was not supplied in the string.
// *Action: Reexecute the command with the required input.
35812, 00000, "(XSACROSS01) The %t command cannot be executed by ACROSS."
// *Cause:
// *Action:
35818, 00000, "(XSCAT01) Group definition values cannot be NA."
// *Cause:
// *Action:
35820, 00000, "(XSCAT02) Each group definition value must be greater than its predecessor."
// *Cause:
// *Action:
35822, 00000, "(XSCGCAT01) The source expression must be numeric."
// *Cause:
// *Action:
35824, 00000, "(XSCGCAT02) The group expression must be numeric."
// *Cause:
// *Action:
35826, 00000, "(XSCGCAT03) The group expression must be one-dimensional."
// *Cause:
// *Action:
35828, 00000, "(XSCGCORR01) Data expressions must be numeric."
// *Cause:
// *Action:
35830, 00000, "(XSCGCORR02) BASEDON names must be dimensions."
// *Cause:
// *Action:
35832, 00000, "(XSCGCORR03) BASEDON names must be dimensions of both data expressions."
// *Cause:
// *Action:
35834, 00000, "(XSCGCORR04) You have named duplicate BASEDON dimensions."
// *Cause:
// *Action:
35836, 00000, "(XSCGCORR05) The two expressions must have at least one common dimension."
// *Cause:
// *Action:
35838, 00000, "(XSCGMODE01) The data expression must be numeric."
// *Cause:
// *Action:
35840, 00000, "(XSCGMODE02) BASEDON names must be dimensions."
// *Cause:
// *Action:
35842, 00000, "(XSCGMODE03) BASEDON names must be dimensions of the data expression."
// *Cause:
// *Action:
35844, 00000, "(XSCGMODE04) You have named duplicate BASEDON dimensions."
// *Cause:
// *Action:
35846, 00000, "(XSCGPCTAGE01) The data expression must be numeric."
// *Cause:
// *Action:
35848, 00000, "(XSCGPCTAGE02) BASEDON names must be dimensions."
// *Cause:
// *Action:
35850, 00000, "(XSCGPCTAGE03) BASEDON names must be dimensions of the data expression."
// *Cause:
// *Action:
35852, 00000, "(XSCGPCTAGE04) You have named duplicate BASEDON dimensions."
// *Cause:
// *Action:
35854, 00000, "(XSCGRANK01) The data expression must be numeric."
// *Cause:
// *Action:
35856, 00000, "(XSCGRANK02) BASEDON names must be dimensions."
// *Cause:
// *Action:
35858, 00000, "(XSCGRANK03) BASEDON names must be dimensions of the data expression."
// *Cause:
// *Action:
35860, 00000, "(XSCGRANK04) You have named duplicate BASEDON dimensions."
// *Cause:
// *Action:
35862, 00000, "(XSCGSMOOTH01) The data expression must be numeric."
// *Cause:
// *Action:
35864, 00000, "(XSCGSMOOTH02) You have not supplied enough smoothing parameters."
// *Cause:
// *Action:
35866, 00000, "(XSCGSMOOTH03) The smoothing parameters must be numeric."
// *Cause:
// *Action:
35868, 00000, "(XSCGSMOOTH04) BASEDON names must be dimensions."
// *Cause:
// *Action:
35870, 00000, "(XSCGSMOOTH05) BASEDON names must be dimensions of the data expression."
// *Cause:
// *Action:
35872, 00000, "(XSCGSMOOTH06) You have named duplicate BASEDON dimensions."
// *Cause:
// *Action:
35874, 00000, "(XSFCAST01) The %s forecasting option cannot be set."
// *Cause:
// *Action:
35876, 00000, "(XSFCAST02) You must use an INTO phrase to specify an output location for the forecast results."
// *Cause:
// *Action:
35878, 00000, "(XSFCAST03) The %s forecasting option cannot be queried."
// *Cause:
// *Action:
35880, 00000, "(XSFCAST04) You cannot specify a trial number when querying the %s forecasting option."
// *Cause:
// *Action:
35882, 00000, "(XSFCAST05) You must specify a trial number when querying the %s forecasting option."
// *Cause:
// *Action:
35884, 00000, "(XSFCAST06) The forecasting context handle cannot be NA."
// *Cause:
// *Action:
35886, 00000, "(XSFCAST07) %a %j %d %d\nThe time dimension %1p has %2p values in status. The limit is %3p."
// *Cause:
// *Action:
35888, 00000, "(XSFCAST08) The time dimension %j has no values in status."
// *Cause:
// *Action:
35890, 00000, "(XSFCAST09) %a %j %d %d\nThe time dimension %1p has only %2p values in status. You cannot specify %3p historical periods."
// *Cause:
// *Action:
35892, 00000, "(XSFCAST10) %a %s %s\nThe %1p target variable must also be dimensioned by %2p."
// *Cause:
// *Action:
35894, 00000, "(XSFCAST11) %a %s %s %f %f\n%1p must be less than or equal to %2p. The current values are %3p and %4p, respectively."
// *Cause:
// *Action:
35896, 00000, "(XSFCAST12) %a %s %f %f %f\nThe value of %1p must evenly divide the difference between MIN and MAX values. The current values are %2p, %3p, and %4p."
// *Cause:
// *Action:
35898, 00000, "(XSFCAST13) The trial number for querying %s cannot be NA."
// *Cause:
// *Action:
35900, 00000, "(XSFCAST14) %d is not the handle of an open forecasting context."
// *Cause:
// *Action:
35902, 00000, "(XSFCAST15) You cannot specify an NA value for %s."
// *Cause:
// *Action:
35904, 00000, "(XSFCAST16) %a %s %d %d %d\nValues of %1p must be between %2p and %3p. You specified %4p."
// *Cause:
// *Action:
35906, 00000, "(XSFCAST17) %a %s %f %f %f\nValues of %1p must be between %2p and %3p. You specified %4p."
// *Cause:
// *Action:
35908, 00000, "(XSFCAST18) %a %v %s\n'%1p' is not a recognized value of %2p."
// *Cause:
// *Action:
35910, 00000, "(XSFCAST19) The forecasting context %d has been invalidated because one or more of the extra dimensions of the time-series expression is no longer available."
// *Cause:
// *Action:
35912, 00000, "(XSFCAST20) %a %s %d\nA forecasting context identified by the text '%1p' already exists. Its handle is %2p."
// *Cause:
// *Action:
35914, 00000, "(XSFCAST21) Values of the TRADINGDAYS expression cannot be less than or equal to zero."
// *Cause:
// *Action:
35916, 00000, "(XSHIDE01) %n is not a program or model."
// *Cause:
// *Action:
35917, 00000, "(XSHIDE05) %a %n %s\nYou cannot HIDE model %1p because the analytic workspace in which it is defined has not been upgraded to version %2p."
// *Cause: User attempted to apply the HIDE command to a model in an AW
// that has not been upgraded to the necessary compatibility level.
// *Action: Make sure that the database is running in the appropriate
// compatibility mode, and upgrade the AW.
35918, 00000, "(XSHIDE02) You do not have access to %n."
// *Cause:
// *Action:
35919, 00000, "(XSHIDE06) %a %s %d\nThe encryption seed for %1p must be at least %2p characters long."
//* Cause: Seed text shorter than the minimum required length was specified.
//* Action: Supply seed text that is at least as long as the length specified.
35920, 00000, "(XSHIDE03) The encryption seed for HIDE and UNHIDE must be a non-empty, one-line TEXT value."
// *Cause:
// *Action:
35922, 00000, "(XSHIDE04) %n is already hidden."
// *Cause:
// *Action:
35924, 00000, "(XSMOOTH01) Smoothing parameters cannot be NA."
// *Cause:
// *Action:
35926, 00000, "(XSMOOTH02) Smoothing constants must be between 0 and 1."
// *Cause:
// *Action:
35928, 00000, "(XSMOOTH03) Cannot compute valuespace offset"
// *Cause:
// *Action:
35930, 00000, "(XSPCTAGE01) Cannot compute valuespace offset"
// *Cause:
// *Action:
35932, 00000, "(XSPGFTCH01) Analytic workspace %s is not attached."
// *Cause:
// *Action:
35934, 00000, "(XSPGFTCH02) No fetch analytic workspace specified"
// *Cause:
// *Action:
35936, 00000, "(XSPGFTCH03) %a %x %x\nPageSpace has %1p %2p pages."
// *Cause:
// *Action:
35950, 00000, "(OBSCURE01) The seed expression argument to OBSCURE cannot be NA."
// *Cause:
// *Action:
35951, 00000, "(OBSCURE02) The ENCRYPT option of OBSCURE is not supported at the current compatibility level."
// *Cause: An attempt was made to use the ENCRYPT option of the OBSCURE function, which is not supported for a compatibility level earlier than 12.2.0.2.
// *Action: Raise the compatibility level or choose a different OBSCURE option.
35952, 00000, "(XSSPFC01) %a %s %j %s %j %d\nThe %1p dimension %2p and the %3p dimension %4p must have the same number of values in status for SPFCEXEC method %5p."
// *Cause: This method requires the named dimensions to have the same number
// of values in status, but the user provided statuses of different
// lengths.
// *Action: Relimit the dimensions so that their status lengths are the same.
35958, 00000, "(XSPGREPORT01) %a %d %d %d %d %d\nOf %1p allocated pages %2p are currently in use, %3p are available for use, %4p are hard-locked, and %5p are soft-locked."
// *Cause:
// *Action:
35964, 00000, "(COPYDFN01) You must have a current analytic workspace to perform a COPYDFN."
// *Cause:
// *Action:
35966, 00000, "(COPYDFN02) The format of the COPYDFN command is:\n\n COPYDFN newname oldname."
// *Cause:
// *Action:
35968, 00000, "(COPYDFN03) Analytic workspace object %1 does not exist."
// *Cause:
// *Action:
35970, 00000, "(COPYDFN05) You cannot copy the definition of an OPTION."
// *Cause:
// *Action:
35972, 00000, "(COPYDFN06) %1 is an invalid name for an analytic workspace object."
// *Cause:
// *Action:
35974, 00000, "(DBDESC00) There are no objects in this analytic workspace."
// *Cause:
// *Action:
35976, 00000, "(DBDESC01) Last updated: %1 Time: %2"
// *Cause:
// *Action:
35978, 00000, "(DBDESC02) Print date: %1 Time: %2"
// *Cause:
// *Action:
35980, 00000, "(DBDESC03) %1 contains:"
// *Cause:
// *Action:
35982, 00000, "(DBDESC04) This report is in two parts:\n\n - Object Listing: An alphabetic list of analytic workspace objects \n beginning on the next page.\n\n - Object Descriptions: Detailed descriptions of all analytic workspace objects \n sorted by object type and alphabetically by name."
// *Cause:
// *Action:
35984, 00000, "(DBDESC05) Object List"
// *Cause:
// *Action:
35986, 00000, "(DBDESC06) Description of %1 objects"
// *Cause:
// *Action:
35988, 00000, "(DBDESC07) Description of PROGRAM %1"
// *Cause:
// *Action:
35990, 00000, "(DBDESC08) Description of MODEL %1"
// *Cause:
// *Action:
35992, 00000, "(DBDESC09) (Cont'd)"
// *Cause:
// *Action:
35994, 00000, "(DBDESC10) Page "
// *Cause:
// *Action:
35996, 00000, "(DBDESC11) Analytic Workspace: "
// *Cause:
// *Action:
35998, 00000, "(DBDESC12) Updated: "
// *Cause:
// *Action:
36000, 00000, "(DBDESC13) At: "
// *Cause:
// *Action:
36002, 00000, "(DBDESC14) NAME"
// *Cause:
// *Action:
36004, 00000, "(DBDESC15) TYPE"
// *Cause:
// *Action:
36006, 00000, "(DBDESC16) DESCRIPTION "
// *Cause:
// *Action:
36008, 00000, "(DBDESC17) Analytic Workspace Listing"
// *Cause:
// *Action:
36010, 00000, "(DBDESC18) Page "
// *Cause:
// *Action:
36016, 00000, "(XSHIERCK01) %a %n %v %d %v %v\nOne or more loops have been detected in hierarchy %1p over %2p. The loops include %3p items (%4p and %5p)."
// *Cause:
// *Action:
36017, 00000, "(XSHIERCK10) %a %j %v %v %v\nThe definition of hierarchy %1p over %2p in level %3p is not star consistent. The collision parents include %4p."
// *Cause: The definition of the hierarchy was not star consistent.
// *Action: Change the definition of the hierarchy.
36018, 00000, "(XSHIERCK02) The format of the HIERCHECK command is:\n\n HIERCHECK relation [STATUS|NOSTATUS|valueset] [MULTIPATH] [CONSISTENT] [{BALANCED|STAR_CONSISTENT} levelrelation] \nOr\n HIERCHECK aggmap [MULTIPATH] [CONSISTENT]"
// *Cause: The wrong object type was specified.
// *Action: Change the object to a RELATION or AGGMAP.
36019, 00000, "(XSHIERCK11) The format of the HIERSHAPE function is:\n\n HIERSHAPE(relation[(qdr)] {level|ragged|skiplevel|regular} USING levelrel [INHIERARCHY inhvs] LEVELORDER levelvs)"
// *Cause: The wrong object type or the wrong object definition was specified.
// *Action: Change the object type or use the correct object definition.
36020, 00000, "(XSHIERCK03) %a %j %v\nThe definition of hierarchy %1p over %2p is inconsistent. "
// *Cause: The definition of the hierarchy was inconsistent.
// *Action: Change the definition of the hierarchy.
36021, 00000, "(XSHIERCK12) The format of the HIERCHECK function is:\n\n HIERCHECK(relation [STATUS|NOSTATUS|valueset] [MULTIPATH] [CONSISTENT] [{BALANCED|STAR_CONSISTENT} levelrelation]) \nOr\n HIERCHECK(aggmap [MULTIPATH] [CONSISTENT])"
// *Cause: The wrong object type was specified.
// *Action: Change the object to a RELATION or AGGMAP.
36022, 00000, "(XSHIERCK04) %a %n\nValuesets specified in the HIERCHECK command must be scalar. %1p is dimensioned."
// *Cause: The HIERCHECK command specified a dimensioned valueset.
// *Action: Specify a scalar valueset in its place.
36024, 00000, "(XSHIERCK05) %a %n %n\nValueset %1p must contain values of one of the extra dimensions of relation %2p."
// *Cause: The HIERCHECK command specified a valueset over an invalid dimension.
// *Action: Specify a valueset containing values of one of the self-relation's
// extra dimensions (the dimensions in the relation's dimension list,
// minus the self-related dimension itself).
36025, 00000, "(XSHIERCK06) %a %n %j\nThe level dimension of the level relation %1p is the same as the relation dimension %2p."
// *Cause: The level dimension was the same as the relation dimension.
// *Action: Change the definition of the level relation.
36026, 00000, "(XSHIERCK07) %a %n %j\nLevel relation %1p is not dimensioned by relation dimension %2p."
// *Cause: The level relation was not dimensioned by the relation dimension.
// *Action: Change the definition of the level relation.
36027, 00000, "(XSHIERCK08) %a %j\nHierarchy %1p is not balanced."
// *Cause: The current hierarchy was not balanced.
// *Action: Change the hierarchy to balanced.
36028, 00000, "(XSHIERCK09) %a %j %v %v\nHierarchy %1p has multiple paths from %2p to %3p."
// *Cause: The current hierarchy had multiple paths.
// *Action: Remove multiple paths from the hierarchy.
36034, 00000, "(XSMHIERCK00) %a %n %j %d %v\nOne or more loops have been detected in relationship %1p over %2p. The last %3p of the items are %4p."
// *Cause: A relation was used that had loops in it. There were more items
// involved than could be reported.
// *Action: Correct the relation so that it does not contain loops.
36035, 00000, "(XSMHIERCKREL) %a %n %d %v\nOne or more loops have been detected in %1p. %2p items involved are %3p."
// *Cause: A relation was used that had loops in it.
// *Action: Correct the relation so that it does not contain loops.
36036, 00000, "(XSMHIERCK01) %a %n %j %d %v\nOne or more loops have been detected in relationship %1p over %2p. The %3p items involved are %4p."
// *Cause: A relation was used that had loops in it.
// *Action: Correct the relation so that it does not contain loops.
36038, 00000, "(INTL00) No application code specified"
// *Cause:
// *Action:
36040, 00000, "(INTL01) IMPORTANT: The length of the following phrase(s) exceeds %1. They will be truncated."
// *Cause:
// *Action:
36042, 00000, "(INTL02A) The %1 language analytic workspace for %2 could not be attached, and there is no English-language analytic workspace for this application."
// *Cause:
// *Action:
36044, 00000, "(INTL02B) Neither the %1 language analytic workspace nor the %2 language analytic workspace could be attached for %3, and there is no English-language analytic workspace for this application."
// *Cause:
// *Action:
36050, 00000, "(INTL06) Invalid option specified. Option must be either OSM, CA, or blank."
// *Cause:
// *Action:
36052, 00000, "(LISTBY00) LISTBY cannot be called as a function returning a value."
// *Cause:
// *Action:
36054, 00000, "(LISTBY01) You must have a current analytic workspace to use the LISTBY command."
// *Cause:
// *Action:
36056, 00000, "(LISTBY02) The syntax of the LISTBY command is:\n LISTBY dimension [dimension ...]\nDimension composites can also be named."
// *Cause:
// *Action:
36058, 00000, "(LISTBY03) %1 does not exist in any attached analytic workspace."
// *Cause:
// *Action:
36060, 00000, "(LISTBY04) %1 is not a dimension or composite."
// *Cause:
// *Action:
36062, 00000, "(LISTBY05) %1 is in a different analytic workspace from previously specified object(s) \"%2\"."
// *Cause:
// *Action:
36064, 00000, "(LISTBY06) The syntax for specifying an unnamed composite is:\n SPARSE<dimension-list>\nwhere 'dimension-list' is a list of simple or conjoint dimensions or named composites."
// *Cause:
// *Action:
36066, 00000, "(LISTBY07) %1 objects dimensioned by or related to %2 in analytic workspace %3"
// *Cause:
// *Action:
36068, 00000, "(LISTNAMES00) Analytic workspace %1 is not attached."
// *Cause:
// *Action:
36070, 00000, "(LISTNAMES01) There are no objects in the analytic workspace of the following types:\n%1"
// *Cause:
// *Action:
36072, 00000, "(LISTNAMES02) There are no objects in the analytic workspace."
// *Cause:
// *Action:
36074, 00000, "(LISTNAMES03) There are no objects in the analytic workspace that match '%1'."
// *Cause:
// *Action:
36076, 00000, "(LISTNAMES04) %1 is not a valid keyword for LISTNAMES.\nValid keywords are:\nALL, SORT or UNSORT, AW workspace-name\n%2"
// *Cause:
// *Action:
36078, 00000, "(MODEL00) Specify the name of a model for the report."
// *Cause:
// *Action:
36080, 00000, "(MODEL01) %1 does not exist."
// *Cause:
// *Action:
36082, 00000, "(MODEL02) %1 is not a model."
// *Cause:
// *Action:
36084, 00000, "(MODEL03) Model %1 has not been compiled."
// *Cause:
// *Action:
36086, 00000, "(MODEL04) Information is not available for model %1."
// *Cause:
// *Action:
36088, 00000, "(MODEL05) Model %1 is not the most-recently executed model."
// *Cause:
// *Action:
36090, 00000, "(MODEL06) Solution status: "
// *Cause:
// *Action:
36092, 00000, "(MODEL07) Model options in use: "
// *Cause:
// *Action:
36094, 00000, "(MODEL08) Solution status: "
// *Cause:
// *Action:
36096, 00000, "(MODEL09) Iterations: "
// *Cause:
// *Action:
36098, 00000, "(MODEL10) Divergent statement"
// *Cause:
// *Action:
36100, 00000, "(MODEL11) Model: %1"
// *Cause:
// *Action:
36102, 00000, "(MODEL12) Statement %1%2"
// *Cause:
// *Action:
36104, 00000, "(STATUS00) You must have a current analytic workspace to use the STATUS command."
// *Cause:
// *Action:
36106, 00000, "(STATUS01) There are no dimensions in your current analytic workspace."
// *Cause:
// *Action:
36108, 00000, "(STATUS02) There are no dimensions in analytic workspace %1."
// *Cause:
// *Action:
36110, 00000, "(STATUS03) %1 has no dimensions."
// *Cause:
// *Action:
36112, 00000, "(STATUS04) The current status of %1 is:"
// *Cause:
// *Action:
36114, 00000, "(STDHDR00) Page "
// *Cause:
// *Action:
36116, 00000, "(TRACKREPORT00) Program name"
// *Cause:
// *Action:
36118, 00000, "(TRACKREPORT01) Exclusive cost"
// *Cause:
// *Action:
36120, 00000, "(TRACKREPORT02) Inclusive cost"
// *Cause:
// *Action:
36122, 00000, "(TRACKREPORT03) Number of calls"
// *Cause:
// *Action:
36124, 00000, "(XLIST00) %1 exceptions found."
// *Cause:
// *Action:
36126, 00000, "(XLIST01) %1 already exists."
// *Cause:
// *Action:
36128, 00000, "(XLIST03) The exception criterion must be a single expression."
// *Cause:
// *Action:
36130, 00000, "(XLIST04) The exception criterion must be a BOOLEAN expression."
// *Cause:
// *Action:
36132, 00000, "(XLIST05) The exception criterion must be dimensioned."
// *Cause:
// *Action:
36134, 00000, "(XLIST06) %1 is not an exception list."
// *Cause:
// *Action:
36136, 00000, "(XLIST07) There is no current exception list. You can use the NAMEXL command to specify one."
// *Cause:
// *Action:
36138, 00000, "(XLIST08) %1 has been deleted."
// *Cause:
// *Action:
36140, 00000, "(XREF00) References To:"
// *Cause:
// *Action:
36142, 00000, "(XREF01) Referenced By:"
// *Cause:
// *Action:
36144, 00000, "(XREF02) NONE"
// *Cause:
// *Action:
36145, 00000, "(SETPROP01) The property \"%1\" cannot be set for measure \"%2\"."
// *Cause: A property name was given that is not one of the allowed properties
// to be set.
// *Action: Specify one of the legal property names.
36146, 00000, "(READSIZE01) The %s expression cannot be missing or NA."
// *Cause:
// *Action:
36148, 00000, "(READSIZE02) %a %s %d %d\nThe minimum value for %1p is %2p. You specified a value of %3p."
// *Cause:
// *Action:
36152, 00000, "(READSIZE04) %a %s %ld %ld\nThe maximum value for %1p is %2p. You specified a value of %3p."
// *Cause:
// *Action:
/// Codes for xsmxaggr.c (36154-36177)
36154, 00000, "(XSMXAGGR01) %n is not a data variable."
// *Cause: An object was specified on the Aggregate command line that
// was not a variable
// *Action: Specify a variable instead
36155, 00000, "(XSMXAGGRFROM) %a %n %n\n%1p must be a variable or formula of a similar data type to %2p to be used with FROM, or a TEXT variable or formula to be used with FROMVAR."
// *Cause: The user specified an illegal variable for use with FROM or
// FROMVAR on the AGGREGATE command line
// *Action: Specify a legal variable instead
36156, 00000, "(XSMXAGGR02) When using the BOOLEAN or FORMULA WEIGHT %n, WNAFILL is the only valid option."
// *Cause:
// *Action:
36157, 00000, "(XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword."
// *Cause: The user specified AUTOCOMMIT but not AUTOUPDATE on the AGGREGATE
// command line, which is illegal
// *Action: Either also specify AUTOUPDATE or don't specify AUTOCOMMIT
36158, 00000, "(XSMXAGGR03) %n must be an AGGMAP object."
// *Cause:
// *Action:
36160, 00000, "(XSMXAGGR04) %a %s %n\nYou cannot use %1p on scalar VARIABLE %2p."
// *Cause: The user tried to run the AGGREGATE or AGGCOUNT command or
// function on a scalar variable.
// *Action: Specify a dimensioned variable instead
36161, 00000, "(XSAGGRRUVCV) %a %n\nAggregation variable %1p cannot have itself as a COUNTVAR."
// *Cause: The user specified the same variable as both an aggregation
// variable and a COUNTVAR
// *Action: Specify a different COUNTVAR
36162, 00000, "(XSMXAGGR05) %a %s %n\nCOUNTVAR variable %2p must be of type INTEGER, not %1p."
// *Cause: The user specified a non-INTEGER variable as a COUNTVAR for
// aggregation
// *Action: Redefine the COUNTVAR to be an INTEGER
36164, 00000, "(XSMXAGGR07) %a %d %d\nWhen using the COUNTVAR clause, the number of variables to be aggregated (%1p) must match the number of COUNTVAR variables (%2p)."
// *Cause: The user specified a COUNTVAR clause to the AGGREGATE command, but
// the number of COUNTVAR variables specified did not match the
// number of variables to be aggregated
// *Action: Specify a separate COUNTVAR for each variable
36165, 00000, "(XSAGGCNTPROP) %a %n\nVariable %1p cannot have both an AGGCOUNT and the $COUNTVAR property."
// *Cause: An attempt was made to add the $COUNTVAR property to a
// variable which already had an AGGCOUNT, or vice versa.
// *Action: Delete the already existing $COUNTVAR property or AGGCOUNT first.
36166, 00000, "(XSMXAGGR08) %n is not a VARIABLE."
// *Cause: An attempt was made to perform an AGGREGATE or other action on an
// object which is not a variable.
// *Action: Specify a variable instead.
36167, 00000, "(XSAGGRFORM) %j is an illegal AGGMAP for aggregating a FORMULA."
// *Cause: The user attempted to aggregate a FORMULA using an AGGMAP
// that is not valid for aggregating FORMULAs. The AGGMAP must
// specify PRECOMPUTE(NA) for all relation lines and must not specify
// any caching.
// *Action: Correct the AGGMAP so it is legal for aggregating a FORMULA.
36168, 00000, "(XSMXAGGR10) %a %n %n\nCOUNTVAR variable %1p must have the same dimensionality as %2p"
// *Cause: The user specified a COUNTVAR variable which is missing at least
// one dimension of the aggregation variable
// *Action: Specify a COUNTVAR variable which has at least as many base
// dimensions as the aggregation variable
36170, 00000, "(XSMXAGGR12) %a %s %n\nThe data type of the WEIGHT %2p must be numeric or BOOLEAN, not %1p."
// *Cause: The user specified a WEIGHT variable or formula which wasn't
// numeric or boolean
// *Action: Specify a numerical or boolean weight instead
36172, 00000, "(XSMXAGGR18) WEIGHT option WNOAGG cannot be used with the WSTORE, WVARPRIORITY, or WAGGPRIORITY options on WEIGHT %n."
// *Cause:
// *Action:
36174, 00000, "(XSMXAGGR23) %n must be either a VARIABLE, a RELATION or a FORMULA."
// *Cause: The user specified something that was not a variable, a relation
// or a formula as a weight for AGGREGATE
// *Action: Specify a valid variable, relation or formula instead
36176, 00000, "(XSMXAGGR25) Relation %n must be a one-dimensional self-relation to be used as a weight for AGGREGATE."
// *Cause: The user specified an illegal relation as a weight. The relation
// might have been multidimensional, not a self-relation, or not a
// relation over one of the bases of the aggregation variable.
// *Action: Specify a valid self relation over one of the bases of the
// aggregation variable.
36178, 00000, "(XSAGGR01) To be used with AGGREGATE, AGGMAP %j must be declared with the AGGMAP command."
// *Cause: The user used the ALLOCMAP command to define the AGGMAP, so the
// AGGMAP can only be used with the ALLOCATE command, or the AGGMAP
// has no contents attached to it.
// *Action: Use the AGGMAP command to define the AGGMAP.
36179, 00000, "(XSNOAGM) %a %n\nNo AGGMAP was specified for VARIABLE %1p."
// *Cause: The user used the AGGREGATE command without specifying an
// AGGMAP on the command line, with a variable which had no $AGGMAP
// property.
// *Action: Specify an AGGMAP on the AGGREGATE command line, or add
// the $AGGMAP property to the variable in question.
36180, 00000, "(XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable %n."
// *Cause: When using AGGREGATE, only simple permissions and permissions on
// base dimensions are valid.
// *Action: Remove the permissions clause from the variable causing problems.
36181, 00000, "A VARIABLE cannot have both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties applied to it."
// *Cause: The user attempted to add both the $AGGREGATE_FROM and
// $AGGREGATE_FROMVAR properties to a single variable.
// *Action: Remove the existing property before applying the new one.
36182, 00000, "(XSAGGR09) %a %j %v\nCould not locate a value for variable %2p in measure dimension %1p."
// *Cause: A measure dimension was supplied in the AGGMAP, but a
// position for the variable was not found in it.
// *Action: Add a position for the variable in the measure dimension.
36184, 00000, "(XSAGGR10) You do not have sufficient permissions for the variable %n."
// *Cause: The user lacked the permissions necessary for the aggregation variable.
// *Action: Remove the restricting permissions from the variable or
// base dimension.
36185, 00000, "(XSAGGR11) %j does not have any AGGCOUNT information."
// *Cause: User attempted an operation (such as the AVERAGE aggregation
// operator or the AGGCOUNT function) that requires a variable
// to have AGGCOUNT information on a variable that does not.
// *Action: Define the variable using the WITH AGGCOUNT clause, or
// use the CHGDFN ADD AGGCOUNT command to enable AGGCOUNT
// for the variable.
36186, 00000, "(XSAGGR12) You must use a COUNTVAR when aggregating with AVERAGE."
// *Cause:
// *Action:
36188, 00000, "(XSAGGR16) AGGREGATE read a value less than 1 out of COUNTVAR variable %n. Either the values of the COUNTVAR variable are stored improperly, or there is problem in AGGREGATE. If no one has modified the values in this COUNTVAR, contact Oracle customer support."
// *Cause: Either someone improperly changed the COUNTVAR variable, or
// AGGREGATE has an error.
// *Action: Set the COUNTVAR variable to NA before starting
// AGGREGATE. If you previously set the COUNTVAR variable to NA, then contact Oracle OLAP technical support.
36190, 00000, "(XSAGGR26) %a %s %n %s\n%2p is of type %1p. The numerical calculation %3p requires INTEGER, DECIMAL or SHORTDECIMAL data."
// *Cause:
// *Action:
36192, 00000, "(XSAGGR27) %a %s %n %s\n%2p is of type %1p. The boolean calculation %3p requires BOOLEAN data."
// *Cause:
// *Action:
36194, 00000, "(XSAGGR28) %a %s %n %s\n%2p is of type %1p. The requested operation requires INTEGER, DECIMAL, SHORTDECIMAL or BOOLEAN data."
// *Cause:
// *Action:
36196, 00000, "(XSAGGR32) '%v' is an invalid argument specifier for AGGREGATE."
// *Cause:
// *Action:
36198, 00000, "(XSAGGR33) %a %j %j\nCannot aggregate over COMPRESSED COMPOSITE %1p using AGGMAP %2p because the operator variable with more than 1 line dimensions is not supported for bases of a COMPRESSED COMPOSITE."
// *Cause: The user specified an aggregation the operator variable with
// more than 1 line dimensions that is not supported by
// COMPRESSED COMPOSITES.
// *Action: Use a MODEL for the calculation, or use an uncompressed
// COMPOSITE.
36200, 00000, "(XSAGGR34) %a %s %j\nAGGREGATE operator %1p requires a WEIGHTBY clause, but ARGS variable %2p did not specify one."
// *Cause: The given operator requires a WEIGHT specification, but the
// ARGS variable did not supply one.
// *Action: Modify the ARGS variable to specify a weight for the operation.
36201, 00000, "(XSAGGR35) %a %j %j\nCannot aggregate %1p(partition %2p) because the subpartition is itself partitioned."
// *Cause: Attempted to aggregate an intermediate partition of a variable
// with nested partitioning.
// *Action: rerun the aggregate command seperately for each ultimate partition
// or just for the variable as a whole
/// XSAGOP errors from xsagdang.c, xsagaccu.c and xsaggr.c (35740-35799)
36202, 00000, "(XSAGOP01) '%v' is not a valid aggregation operator."
// *Cause: An invalid string was provided for an aggregation operator.
// *Action: Check the spelling of the operator to make sure you are
// specifying a valid one.
36204, 00000, "(XSAGOP04N) %a %j %s\nIn AGGMAP %1p, the NAOPERATOR %2p must be HFIRST, HLAST or HEVEN."
// *Cause: An invalid NAOPERATOR was specified.
// *Action: Specify HFIRST, HLAST or HEVEN.
36206, 00000, "(XSAGOP04R) %a %j %s\nIn AGGMAP %1p, REMOPERATOR %2p must be MIN, MAX, FIRST, LAST, HFIRST or HLAST."
// *Cause: An invalid REMOPERATOR was specified.
// *Action: Specify one of the legal operators.
36208, 00000, "(XSAGOP05N) %a %j %s %s\nIn AGGMAP %1p, you can only specify NAOPERATOR %3p with the PROPORTIONAL or EVEN operators, not %2p."
// *Cause: The user specified an NAOPERATOR when you were not using
// PROPORTIONAL or EVEN.
// *Action: Remove the NAOPERATOR clause from the RELATION line.
36210, 00000, "(XSAGOP05R) %a %j %s %s\nIn AGGMAP %1p, you can only specify the REMOPERATOR %3p with the PROPORTIONAL, EVEN, or HEVEN operators, not %2p."
// *Cause: The user specified a REMOPERATOR without using
// PROPORTIONAL, EVEN, or HEVEN.
// *Action: Remove the REMOPERATOR clause from the RELATION line.
36212, 00000, "(XSAGOP06) %a %j %s\nIn AGGMAP %1p, you can only specify the MIN, MAX, FLOOR, and CEILING arguments while using the PROPORTIONAL operator, not %2p."
// *Cause: The user specified MIN, MAX, FLOOR, or CEILING when using an
// operator other than PROPORTIONAL.
// *Action: Remove the incorrect argument from the RELATION line.
36214, 00000, "(XSRELOBC01) The value of INDEXCACHESIZE must be positive."
// *Cause:
// *Action:
36216, 00000, "(XSOPARM01) A DIMENSION must have a data type (ID, TEXT, or INTEGER), a time period, or a list of bases for a conjoint dimension."
// *Cause:
// *Action:
/// 36220 - 36229 reserved for xsGDILpDsc
36220, 00000, "(XSLPDSC01) All dimensions in LIST %d are also in the IGNORE clause."
// *Cause: One of the dimension lists in the dimension loop descriptor
// had no base dimensions except those in the IGNORE list. This
// leaves no dimensions for looping over.
// *Action: Fix the dimension loop descriptor.
36221, 00000, "(XSLPDSC02) %a %d %d\nLIST %1p and LIST %2p have different base dimensions."
// *Cause: The base dimensions of the dimension lists given in the loop
// descriptor do not match.
// *Action: Ensure that each dimension list has the same set of looping base
// dimensions. If necessary, use IGNORE within a lists to
// discard base dimensions that should not be looped.
36222, 00000, "(XSLPDSC03) duplicate IGNORE or DENSE information for dimension %j"
// *Cause: An IGNORE or DENSE list in a dimension loop descriptor
// included the dimension twice, included two different valuesets
// of the dimension, or includes the dimension and a valueset of the
// dimension.
// *Action: Only use the dimension or a valueset of the dimension
// once in an IGNORE or DENSE list.
36223, 00000, "(XSLPDSC04) object %q in IGNORE or DENSE list has illegal type"
// *Cause: An IGNORE or DENSE list in a dimension loop descriptor
// included and object that was not a dimension or a
// valueset, was a conjoint dimension, or was a dimensioned
// valueset.
// *Action: Only use simple dimensions and undimensioned valuesets in
// the IGNORE or DENSE list.
36224, 00000, "(XSLPDSC05) %j is not a loop dimension"
// *Cause: An IGNORE or DENSE list in a dimension loop descriptor
// referenced a dimension (or a valueset of a dimension)
// that was not a base dimension of the loop dimension list.
// *Action: Remove the dimension or valueset from the IGNORE or DENSE list.
36225, 00000, "(XSLPDSC06) A LOOP AGGMAP list must contain an aggmap object, followed by one or more variables and/or dimensions."
// *Cause: An invalid AGGMAP list was specified. Either to few objects were
// specified, or an incorrect type of object was used.
// *Action: Specify a valid AGGMAP list consisting of an aggmap object,
// followed by one or more variables and/or dimensions.
36226, 00000, "(XSLPDSC07) The syntax of the $LOOP property on formula %n is incorrect."
// *Cause: Unrecognized contents in the $LOOP property of a formula in the
// table function measure list.
// *Action: Restrict the contents of the $LOOP property to valid elements
// (other than OPTIMIZED and MEASURES) of the table function LOOP
// directive.
/// Codes 36230 - 36239 for the ANALYZE command
36230, 0000, "(XSANALYZ00) object %n cannot be used in the ANALYZE command"
// *Cause: An object that cannot be analyzed was used in the ANALYZE command.
// *Action: Analyze VARIABLES, RELATIONS, DIMENSIONS, or SURROGATES.
36231, 0000, "(XSANALYZ01) object %n cannot be used in the INHIERARCHY clause"
// *Cause: An invalid INHIERARCHY object was referenced.
// *Action: Use either a VALUESET or boolean VARIABLE.
36232, 0000, "(XSANALYZ02) a level list was specified when a language dimension was present"
// *Cause: A level list dimension was specified when a language dimension was present.
// *Action: Remove the USING clause.
36233, 0000, "(XSANALYZ03) the dimensionality of object %n does not match the ANALYZE command"
// *Cause: The dimensionality of the object did not match the ANALYZE command syntax used.
// *Action: Match the ANALYZE syntax to the dimensionality of the specified object.
36234, 0000, "(XSANALYZ04) all objects in the current status of the NAME dimension must have the same dimensionality when used with the ANALYZE command"
// *Cause: The dimensionality of at least one of the objects listed in the NAME dimension does not match the rest of the objects.
// *Action: Make sure all objects listed in the NAME dimension have the same dimensionality.
36236, 0000, "(XSANALYZ06) the AW format must be 11.0.0.0 or higher to use the ANALYZE command"
// *Cause: The AW version is less than 11.0.0.0
// *Action: Make sure the compatible mode is 11.0.0.0 or higher and upgrade the AW
36237, 0000, "(XSANALYZ07) %a %s %s\nanalytic workspace %1p.%2p must be attached RW or EXCLUSIVE mode"
// *Cause: The analytic workspace was already attached RO or MULTI mode.
// *Action: Detach the analytic workspace.
36238, 0000, "(XSANALYZ08) %a %s %s\nobject %1p.%2p does not exist"
// *Cause: The object name does not exist
// *Action: Check the spelling and case of the object name
/// Codes 36250 - 36256 for xsvalset.c
/// Codes 36500-36519 for xsaginfo.c
36258, 00000, "(XSAGINFO00) When the AGGMAPINFO function is called, %n must be an AGGMAP."
// *Cause: The AGGMAPINFO function was called with an object that is not
// an AGGMAP.
// *Action: Modify the call to AGGMAPINFO to specify an AGGMAP object.
36260, 00000, "(XSAGHIERPART00) %a %J %J %j\nAggregating from partition %1p to partition %2p over hierarchy %3p creates an increase in sparsity."
// *Cause: In the partition creation / aggmap creation a situation developed
// such that when aggregating over a particular dimension of the aggmap
// a partition boundary was crossed such that the sparsity of the target
// partition included dimensions that were not in the sparsity of the
// source partition. Since the process of aggregation always densifies
// rather than sparsifying this is an extremely suboptimal design and
// it is not supported by the aggregate system.
// *Action:
// Set up your partitioning such that for any partition boundary the
// source and target partitions of the aggregation will always move
// towards denser partitions. For any child (c) and any parent (p)
// where (c) and (p) are in different partitions it must be the case
// that the parent partition contains no dimension in the composite
// that the child partition does not contain in its composite.
36261, 00000, "(XSAGPARTDEP00) %a %J %J\nCan not Aggregate PARTITION TEMPLATE %1p because the path of aggregation would recursively enter partition %2p."
// *Cause: The partitioning scheme was such that while aggregating there
// exists a cell (m) such that both one of its descendants and
// one of its ancestors are both in the referenced partition, while
// (m) is in a different partition.
// *Action:
// Change the partitioning scheme.
36262, 00000, "(XSAGREMOD00) MODEL %q was not attached to the AGGMAP."
// *Cause:
// *Action:
36264, 00000, "(XSAGREMOD01) Removed MODEL: %v"
// *Cause:
// *Action:
36266, 00000, "(XSCGMDLAGG00) Invalid context for the AGGREGATION function"
// *Cause: The AGGREGATION function was used outside of the MODEL context.
// *Action: Use AGGREGATION only in a model.
36267, 00000, "(XSCGMDLAGG09) %n has no dimensions, so it cannot have a qualified data reference."
// *Cause: A dimension qualification was specified for a valueset with no dimensions.
// *Action: Remove the qualification.
36268, 00000, "(XSCGMDLAGG01) '%t' is not a valid dimension value."
// *Cause: The AGGREGATION parameter list included a value that does not exist in the
// MODEL dimension that contains the target of the AGGREGATION
// *Action: Specify only values from the appropriate MODEL dimension
36269, 00000, "(XSCGMDLAGG10) '%q' does not exist or is not a dimension."
// *Cause: A nonexistent or invalid object was specified as a QDR dimension.
// *Action: Specify existing dimensions only.
36270, 00000, "(XSCGMDLAGG03) The parameter list for the AGGREGATION function includes duplicate values."
// *Cause: One or more duplicate values appeared in the AGGREGATION parameter list.
// *Action: Remove the duplication.
36271, 00000, "(XSCGMDLAGG11) %a %j %n\n%1p is not in the dimension list of valueset %2p."
// *Cause: A QDR dimension was specified that does not appear in the valueset's
// dimension list.
// *Action: Specify only dimensions in the valueset's dimension list.
36272, 00000, "(XSCGMDLAGG04) '%q' is not a valid operator for the AGGREGATION function."
// *Cause: An invalid AGGREGATION operator was specified.
// *Action: Correct the invalid operator.
36273, 00000, "(XSCGMDLAGG12) Dimension %j appears more than once in the QDR."
// *Cause: A dimension was specified more than once in the QDR.
// *Action: Remove the duplication.
36274, 00000, "(XSCGMDLAGG05) The operator used in this equation needs a weight variable."
// *Cause: An invalid weight variable was specified.
// *Action: Correct the invalid weight variable.
36275, 00000, "(XSCGMDLAGG13) %a %t %j\n%1p is not a valid %2p."
// *Cause: A value was specified that does not exist in the QDR dimension.
// *Action: Specify an existing value.
36276, 00000, "(XSCGMDLAGG06) The current operator does not need a weight variable."
// *Cause: A weight variable was specified in a context that does not support it.
// *Action: Remove the weight variable.
36278, 00000, "(XSCGMDLAGG07) %q does not exist or is not valueset."
// *Cause: A nonexistent or invalid object was specified where a valueset is required.
// *Action: Specify an existing valueset only.
36280, 00000, "(XSCGMDLAGG08) Valueset %q does not contain values of any dimension of the current model."
// *Cause: AGGREGATION specified a valueset of a dimension not listed in a DIMENSION
// statement for the current model.
// *Action: Add the valueset's dimension to the model's DIMENSION list, or choose
// a different valueset.
36282, 00000, "(DNAMELEN01) %a %s %d\nObject name %1p is longer than %2p bytes."
// *Cause:
// *Action:
36286, 00000, "(EIFMAKEF12) The EXPORT command terminated, because there was not enough disk space in path %s to contain a complete extension file."
// *Cause:
// *Action:
36290, 00000, "(EIFMAKEF14) %a %n %d %s %s\nYou cannot export object %1p, because EIFVERSION is set to %2p. That version does not support %3p %4ps."
// *Cause: The user tried to export a NUMBER dimension to an EIF file with the
// EIFVERSION option set to a number less than 80000. Versions previous
// to that eversion do not support NUMBER dimensions.
// *Action: A NUMBER dimension cannot be used in a version of older than 9.2.0. If
// the EXPORT file is going to be read by version 9.2.0 or higher, set EIFVERSION to a number greater than or equal to 80000 and
// execute the EXPORT command again.
36300, 00000, "(XSCGTERM01) The command is too long or complex to compile. Eliminate or simplify expressions, or remove or shorten text constants."
// *Cause:
// *Action:
36302, 00000, "(MXCLASS03) You cannot reference an analytic workspace NAME dimension using a QON. You can only access the NAME dimension of the current analytic workspace."
// *Cause:
// *Action:
36304, 00000, "(MXDCLAGR02) %n was not defined as an AGGMAP."
// *Cause:
// *Action:
36306, 00000, "(MXDCLAGR03) Since there is no current aggmap definition, the AGGMAP statements will be discarded. Type END to return to the command line."
// *Cause:
// *Action:
36308, 00000, "(MXDCLAGR04) The object %n has been defined as an AGGMAP, and it cannot be redefined as an ALLOCMAP."
// *Cause:
// *Action:
36310, 00000, "(MXDCLAGR05) The object %n has been defined an ALLOCMAP, and it cannot be redefined as an AGGMAP."
// *Cause:
// *Action:
/// 36312 -> 36317 reserved for the PHYSICAL command and function
36312, 00000, "(PHYS00) %n must be a dimension, dimensioned variable or relation."
// *Cause: The user specified an invalid OLAP object while attempting
// to use the PHYSICAL function
// *Action: Specify a valid object
36313, 00000, "(PHYS03) The VALUE option of PHYSICAL cannot be applied to a variable."
// *Cause: the VALUE argument to PHYSICAL was supplied for a variable.
// *Action: remove VALUE or specify a relation or dimension.
36314, 00000, "(PHYS01) %n must be a dimension, relation or variable."
// *Cause: The user specified an invalid OLAP object while attempting
// to use the PHYSICAL command
// *Action: Specify a valid object
36315, 00000, "(PHYS04) You must specify the VALUE option for scalar relation %n."
// *Cause: The VALUE argument to PHYSICAL was omitted for a scalar relation
// *Action: specify VALUE or choose a dimensioned relation
36316, 00000, "(PHYS02) Relation %n must be a single-dimensional relation that relates one INTEGER dimension to another."
// *Cause: The user specified an invalid relation while attempting to use
// the PHYSICAL command
// *Action: Specify a valid relation
/// 36312 -> 36317 reserved for the PHYSICAL command and function
36320, 00000, "(PPENG05) No more than %d push levels are allowed."
// *Cause:
// *Action:
36322, 00000, "(PPENG06) %a %n %d\n%1p cannot be pushed more than %2p times."
// *Cause:
// *Action:
36324, 00000, "(PPNLSOPT00) %a %v %s\n'%1p' is not a legal value for the %2p option. The previous value was retained."
// *Cause:
// *Action:
36330, 00000, "(SNSYN124) The format of the PHYSICAL command is:\n \n PHYSICAL [dimension|relation]"
// *Cause:
// *Action:
36332, 00000, "(SNSYN125) The format of the PHYSICAL function is:\n \n PHYSICAL(dimension|variable|{relation [VALUE]})"
// *Cause:
// *Action:
36334, 00000, "(SNSYN126) The format of the TO_DATE function is:\n \n TO_DATE(value [format] [{option optionvalue}...])"
// *Cause:
// *Action:
36336, 00000, "(SNSYN127) The format of the TO_CHAR function is:\n \n TO_CHAR(value [format] [{option optionvalue}...])"
// *Cause:
// *Action:
36338, 00000, "(SNSYN128) The format of the TO_NUMBER function is:\n \n TO_NUMBER(value [format] [{option optionvalue}...])"
// *Cause:
// *Action:
36339, 00000, "(SNSYN129) The format of the TO_NCHAR function is:\n \n TO_NCHAR(value [format] [{option optionvalue}...])"
// *Cause:
// *Action:
36340, 00000, "(SNSYN130) The format of the PARTITIONCHECK function is:\n \n PARTITIONCHECK(aggmap, partition_template)"
// *Cause: Bad syntax
// *Action: Correct syntax
36341, 00000, "(SNSYN131) The format of the TO_TIMESTAMP function is:\n \n TO_TIMESTAMP(value [format] [{option optionvalue}...])"
// *Cause:
// *Action:
36342, 00000, "(SNSYN200) The format of the CLEAR command is:\n \n CLEAR [ ALL | STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]"
// *Cause: The syntax for the CLEAR command was invalid.
// *Action: Modify your syntax using the correct format.
36344, 00000, "(SNSYN272) The format of the AGGREGATION function is:\n \n AGGREGATION(dimension-value [dimension-value ...]) [OPERATOR operatorname [WEIGHT | WEIGHTBY weightvar]] "
// *Cause:
// *Action:
36346, 00000, "(SNSYN338) The format of the TRUNC function is:\n \n TRUNC(expression1 [, expression2])"
// *Cause:
// *Action:
36348, 00000, "(SNSYN339) The format of the CEIL function is:\n \n CEIL(number)"
// *Cause:
// *Action:
36350, 00000, "(SNSYN340) The format of the FLOOR function is:\n \n FLOOR(number)"
// *Cause:
// *Action:
36352, 00000, "(SNSYN341) The format of the ADD_MONTHS function is:\n \n ADD_MONTHS(date, number of months)"
// *Cause:
// *Action:
36354, 00000, "(SNSYN342) The format of the LAST_DAY function is:\n \n LAST_DAY(date)"
// *Cause:
// *Action:
36356, 00000, "(SNSYN343) The format of the MONTHS_BETWEEN function is:\n \n MONTHS_BETWEEN(date, date)"
// *Cause:
// *Action:
36358, 00000, "(SNSYN344) The format of the NEW_TIME function is:\n \n NEW_TIME(date, zone, new zone)"
// *Cause:
// *Action:
36360, 00000, "(SNSYN345) The format of the NEXT_DAY function is:\n \n NEXT_DAY(date, day name)"
// *Cause:
// *Action:
36362, 00000, "(XPROPEN01) %a %j %d %d\nDiscarding compiled code for %1p because it was compiled with code version %2p. The current code version is %3p."
// *Cause:
// *Action:
36376, 00000, "(XSAGZERO) AGGREGATE attempted to divide by zero. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of a division by zero."
// *Cause: A calculation in the current AGGREGATE command attempted to
// divide by zero as a result of an AVERAGE, WAVERAGE, HAVERAGE or HWAVERAGE
// operation.
// *Action: Either fix the data, or set DIVIDEBYZERO to YES to return NA instead of signaling an error.
36378, 00000, "(XSAGTHRWEIGHT) %a %n %n %j\nWhile running AGGREGATE with multiple threads, the weight variable %1p specified by your ARGS variable %2p must exist in the same analytic workspace as your AGGMAP %3p."
// *Cause: While running AGGREGATE in threaded mode, you attempted
// to specify a WEIGHT variable in another analytic workspace.
// *Action: Use a weight variable from the same analytic workspace as the aggmap and
// rollup variable.
36380, 00000, "(AGGRECURSE) AGGREGATE was called recursively, which is not allowed."
// *Cause: A model, NATRIGGER, or other object called the AGGREGATE function
// or command while another AGGREGATE function or command was already in
// progress.
// *Action: Modify your objects so that they do not need to have two
// AGGREGATE commands or functions executing at once.
36387, 00000, "(XSPARTCHECK00) Object %n must be an AGGMAP."
// *Cause:
// *Action:
36388, 00000, "(XSPARTCHECK01) Object %n must be a PARTITION TEMPLATE."
// *Cause:
// *Action:
36389, 00000, "(XSAGPARTDEP01) %a %v %v %J\nCan not aggregate from PARTITION %1p into PARTITION %2p due to increasing sparsity along DIMENSION %3p."
// *Cause: The user is attempting to use partitions as a means of sparsity
// control, however they have set up their partitions in a manner that
// simply makes no sense. It is a simple fact that during aggregation
// data becomes more dense, not less dense, and yet their partitions
// indicate the opposite.
// *Action: Modify the partition template add the specified dimension into
// the source composite, or removing it from the target composite.
36391, 00000, "(XSMXCLEA01) %a %n %n\nWhen CLEAR is used with the STATUS keyword or an AGGMAP, %1p must be dimensioned identically to %2p."
// *Cause: The user specified objects whose dimensionality didn't match
// *Action: Break up the CLEAR command into multiple commands where the
// dimensionality of the objects matches
36392, 00000, "(XSMXCLEA02) When using CLEAR with the PRECOMPUTES or NONPRECOMPUTES options, you must specify an AGGMAP."
// *Cause: The user didn't specify an AGGMAP with the CLEAR command.
// *Action: specify an aggmap by adding a USING phrase to the CLEAR
// command, or attach a '$AGGMAP' property to the variable.
36393, 00000, "(XSMXCLEA03) When using the AGGREGATES, CHANGES or CACHE options, you must specify the ALL keyword."
// *Cause: The user didn't use the ALL keyword when using CHANGES or CACHE.
// *Action: Specify the ALL keyword.
36394, 00000, "(XSMXCLEA04) %a %n\nWhen using CLEAR on the AGGMAP %1p, CACHE is the only valid directive."
// *Cause: The user attempted to CLEAR an AGGMAP using a directive other than
// CACHE.
// *Action: Amend the CLEAR line to only use the CACHE keyword with AGGMAPs.
36395, 00000, "(XSMXCLEA05) To CLEAR ALL AGGREGATES from %n, you must specify an AGGMAP."
// *Cause: The CLEAR command could not determine how the variable was
// aggregated because the variable is not dimensioned by a compressed
// composite.
// *Action: Specify an aggmap by adding a USING phrase to the CLEAR command,
// or attach a '$AGGMAP' property to the variable.
/// 36397 - 36405 reserved for system properties
36397, 00000, "(XSSPROPNA) The value of property %s cannot be NA."
// *Cause: The user tried to set a system-reserved property on an OLAP
// object to NA
// *Action: Set the property to a non-NA value
36398, 00000, "(XSSPROP01) Property name '%v' is invalid because only system-reserved property names can begin with '$'."
// *Cause: The user attempted to add a property which starts with $ but is
// not a reserved property name
// *Action: Remove the $ from the property name
36399, 00000, "(XSSPROPDTYPE) %a %s %s\nThe data type of property %1p must be %2p."
// *Cause: The user tried to set a system-reserved property on an OLAP
// object to a value with an illegal datatype
// *Action: Set the property with the proper datatype
36400, 00000, "(XSSPROP02) %q is not a valid variable name."
// *Cause: Not a valid variable name
// *Action: Change to a valid variable name
36401, 00000, "(XSSPROPOTYPE) %a %s %s\nProperty %1p may only be applied to objects of type %2p."
// *Cause: The user applied a reserved property name to an incorrect object
// type
// *Action: Apply the property to the correct object
36402, 00000, "(XSSPROP03) The property '$%s' requires a leading \"$\" because it is a system-reserved property name."
// *Cause: The user tried to specify a property name which is reserved, but
// did not use a leading $
// *Action: Either add a leading $ or choose another property name
36403, 0000, "(XSBADSPROP) %a %s %n %v\n%3p is an illegal value for system-reserved property %1p on %2p."
// *Cause: The user tried to specify an illegal value for a special property
// *Action: Specify a legal value.
36404, 00000, "(XSSPROP04) %a %s\nProperty %1p cannot be applied to an undimensioned (scalar) TEMPORARY variable."
// *Cause: The user applied a reserved property name to an incorrect object
// type
// *Action: Apply the property to the correct object
36405, 00000, "(XSSPROP05) Property ignored for object %n:"
// *Cause: A property was ignored during import.
// *Action: Refer to the message that follows this one and correct the error
// it describes.
/// 36398-36405 reserved for system properties
36406, 00000, "(VCACHE00) '%v' is an invalid value for the VARCACHE option. The only permissible values are 'SESSION', 'VARIABLE', and 'NONE'."
// *Cause: The user tried to assign an invalid value to the VARCACHE option
// *Action: Assign one of the valid values
36410, 00000, "(VCACHE03) '%v' is an invalid value for the $VARCACHE property. The only permissible values are 'DEFAULT', 'SESSION', 'VARIABLE', and 'NONE'."
// *Cause: The user tried to assign an invalid value to the $VARCACHE property
// on a variable
// *Action: Assign one of the valid values
/// Hole from 36411 to 36607
36608, 00000, "(XSAGHOVERFLOW) The depth of the hierarchies encountered while processing a composite dimension in AGGREGATE caused a counter overflow."
// *Cause: The depth of the hierarchies that are part of a composite
// exceeded 4 billion levels during the merge.
// *Action: Reduce the number of levels in the hierarchies, reduce the number of dimensions
// in the composite, or do not aggregate over all dimensions at once.
36610, 00000, "(XSLMS00) Unable to locate a message file for OLAP message: %k"
// *Cause: An internal OLAP DML program in the EXPRESS Analytic Workspace
// failed to retrieve a user message.
// *Action: Contact support.
36612, 00000, "(XSLMS01) invalid OLAP message number: %k"
// *Cause: An internal OLAP DML program in the EXPRESS Analytic Workspace
// attempted to retrieve a non-existent message.
// *Action: Contact support.
36616, 00000, "(XSAGMODHIER01) %a %j %j\nThere is a cycle formed by MODEL %1p and other embedded or containing models with the same dimension, %2p."
// *Cause: Inclusion of a dynamic model formed a cycle in the named dimension.
// *Action: Edit the models involving this dimension to remove the cycle.
36617, 00000, "(XSAGMODHIER02) %a %j\nThere is a self-cycle equation in MODEL %1p."
// *Cause: The model for relation modification included a self-cycle equation.
// *Action: Remove the self-cycle equation from the model.
36618, 00000, "(XSAGMODDIM00) %j is not a valid dynamic model for AGGMAP."
// *Cause: The model failed one of the following tests:
// 1) only one dimension (aside from LAG/LEAD dimensions);
// 2) assignment to dimension values only;
// 3) a single simple solution block;
// 4) no time-series functions with variable step values.
// *Action: Edit the model so that it conforms to the above requirements.
36620, 00000, "(XSAGMODDIM01) MODEL %j cannot find the matching embedded model."
// *Cause: AGGMAP ADD model could not find the matching embedded model.
// *Action: Add the matching embedded model to the AGGMAP.
36621, 00000, "(XSAGMODDIM02) %a %j %j\nYou cannot AGGREGATE the individual partition using static model %1p because a partition dimension or its deriver %2p appears in the equation of the step or simultaneous block."
// *Cause: An attempt was made to AGGREGATE the individual partition
// using the static model with the partition dimension in the
// equation of the step or simultaneous block.
// *Action: AGGREGATE the variable instead of the individual partition.
36622, 00000, "(XSAGMODLIST00) %a %j %n\n%2p cannot be added to the AGGMAP %1p because it is not a valid MODEL."
// *Cause: An object specified in AGGMAP ADD was not a model.
// *Action: Specify the name of a model.
36626, 00000, "(XSAGMODLIST02) %a %j %n\nMODEL %2p was skipped because there is already a MODEL by that name attached to AGGMAP %1p."
// *Cause: An attempt was made to add the same model to the AGGMAP twice.
// *Action: None required.
36628, 00000, "(XSAGMODLIST03) %a %j %n\nMODEL %2p could not be added to AGGMAP %1p."
// *Cause: The dimension of the model did not match a hierarchy of the aggmap.
// *Action: Add a RELATION statement to the AGGMAP for that dimension.
36630, 00000, "(XSDUNION00) An empty base dimension list was specified in the concat dimension definition."
// *Cause: An empty concat dimension list was specified.
// *Action: Specify a valid list of dimensions when defining a concat dimension.
36632, 00000, "(XSDUNION01) The concat dimension %n is not currently defined as UNIQUE."
// *Cause: Attempt was made to CHGDFN a concat, which is already non-unique, to NOT UNIQUE.
// *Action: Since the concat is already non-unique, this command is unnecessary.
36634, 00000, "(XSDUNION02) INTEGER dimension %j cannot be used as a concat dimension base."
// *Cause: The user cannot specify INTEGER base dimensions when defining a concat dimension.
// *Action: Change the datatype of the INTEGER base dimension, or omit it from the concat.
36635, 00000, "(XSDUNION03) The base dimension %j has an invalid datatype for use in a UNIQUE concat definition."
// *Cause: Base dimensions of a unique concat must have TEXT or ID datatypes.
// *Action: Specify a valid list of dimensions when defining a unique concat dimension.
36636, 00000, "(XSDUNION04) The unique concat dimension %n cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension."
// *Cause: A non-unique concat dimension cannot be used as a base of a dependent unique concat.
// *Action: CHGDFN any dependent unique concat dimensions to NOT UNIQUE and retry.
36637, 00000, "(XSDUNION05) %a %j\nThe concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension %1p."
// *Cause: A non-unique concat dimension cannot be used as a base of a dependent unique concat.
// *Action: CHGDFN any non-unique concat base dimensions to UNIQUE and retry.
36638, 00000, "(XSDUNION17) %a %j %j\nConcat dimension %1p cannot be changed to UNIQUE because it has a non-unique concat base dimension %2p."
// *Cause: A non-unique concat dimension cannot be used as a base of a dependent unique concat.
// *Action: CHGDFN any non-unique concat base dimensions to UNIQUE and retry.
36639, 00000, "(XSDUNION18) %a %j %j %v\nUNIQUE cannot be applied to this concat dimension because leaves %1p and %2p share the value %3p."
// *Cause: Unique concat base dimensions cannot contain duplicate values.
// *Action: Use MAINTAIN RENAME to change one of the duplicate values and retry.
36640, 00000, "(XSDUNION19) %a %j %j\nConcat dimension %1p cannot be changed to UNIQUE because base dimension %2p does not have a TEXT or ID datatype."
// *Cause: Base dimensions of a unique concat must have TEXT or ID datatypes.
// *Action:
36641, 00000, "(XSDUNION20) %a %j\nThe concat dimension must be defined as UNIQUE because base dimension %1p contains custom member values."
// *Cause: The UNIQUE keyword was not specified in the concat dimension definition,
// and is required if any of its base dimensions contain custom member values.
// *Action: Define the concat as UNIQUE, or remove all base custom member values.
36642, 00000, "(XSDUNION06) Concat dimension list contains duplicate leaf dimension %j."
// *Cause: Duplicate concat leaf dimension was found.
// *Action: Remove duplicate concat base dimensions and retry.
36643, 00000, "(XSDUNION21) %a %j\nConcat dimension %1p cannot be changed to NOT UNIQUE because it contains custom member values."
// *Cause: Only UNIQUE concat dimensions can have custom member values or
// base dimensions which contain custom member values.
// *Action: Remove all custom member values from the concat and all of its bases, and retry.
36644, 00000, "(XSDUNION07) Concat dimension %j contains a previously detected leaf dimension."
// *Cause: Concat dimension contains a previously detected leaf dimension.
// *Action:
36646, 00000, "(XSDUNION08) Only concat dimensions can be redefined as UNIQUE. %n is not a concat dimension."
// *Cause: UNIQUE keyword was used with an invalid object.
// *Action: Retry without the UNIQUE keyword.
36648, 00000, "(XSDUNION09) Concat dimension %n is already defined as UNIQUE."
// *Cause: Attempt to change a concat dimension to UNIQUE, but it is already UNIQUE.
// *Action:
36650, 00000, "(XSDUNION10) %a %j %j %j %v\nConcat dimension %1p cannot be changed to UNIQUE. Leaves %2p and %3p share the value %4p."
// *Cause: Unique concat base dimensions cannot contain duplicate values.
// *Action: Use MAINTAIN RENAME to change one of the duplicate values and retry.
36652, 00000, "(XSDUNION11) %a %n %s\n%1p is not a %2p type dimension."
// *Cause: The CHGDFN BASE ADD command is only valid for concat dimensions.
// *Action:
36654, 00000, "(XSDUNION12) %a %j %j %j\n%1p cannot be added to %2p because it conflicts with the dimensions of object %3p."
// *Cause:
// *Action:
36656, 00000, "(XSDUNION13) %a %j %j\n%1p is already a member of %2p and cannot be added."
// *Cause:
// *Action:
36658, 00000, "(XSDUNION14) %a %j %j\n%1p is not a direct base of %2p."
// *Cause:
// *Action:
36660, 00000, "(XSDUENG00) The first argument to the %s function must be an expression yielding a dimension value."
// *Cause:
// *Action:
36662, 00000, "(XSDUENG01) %a %s %j\nYou cannot apply the %1p function to %2p because it is not a concat dimension."
// *Cause:
// *Action:
// messages 36663 - 36687 reserved for partition templates
36663, 00000, "(XSDPART01) You must specify a dimension list when defining a PARTITION TEMPLATE."
// *Cause:
// *Action:
36664, 00000, "(XSDPART02) You must specify a partitioning method and one or more partition dimensions when defining a PARTITION TEMPLATE."
// *Cause: User tried to define a PARTITION TEMPLATE without a PARTITION BY
// clause.
// *Action: Add a PARTITION BY clause.
36665, 00000, "(XSDPART03) %q is not in the dimension list of the PARTITION TEMPLATE."
// *Cause: While defining a partition template, user attempted to specify
// a partition dimension that is not a dimension of the partition
// template itself.
// *Action: Choose a partition dimension from among the dimensions of the
// partition template.
36666, 00000, "(XSDPART04) %q is not a concat dimension."
// *Cause: User tried to define a partition template with
// PARTITION BY CONCAT(... dim ...) where dim is not a concat dimension.
// *Action: Only concat dimensions can serve as partition dimensions with
// CONCAT partitioning. Choose a different partition dimension.
36667, 00000, "(XSDPART05) %t is not a legal CONCAT partition."
// *Cause: User attempted to use RANGE or LIST syntax in defining a
// CONCAT partition template.
// *Action: Use CONCAT partition syntax.
36668, 00000, "(XSDPART06) %t is not a legal RANGE partition."
// *Cause: User attempted to use CONCAT or LIST syntax in defining a
// RANGE partition template.
// *Action: Use RANGE partition syntax.
36669, 00000, "(XSDPART07) %t is not a legal LIST partition."
// *Cause: User attempted to use RANGE or CONCAT syntax in defining a
// LIST partition template.
// *Action: Use LIST partition syntax.
36670, 00000, "(XSDPART08) %q is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions."
// *Cause: User attempted to define a partition template
// partitioned by an INTEGER or NTEXT dimension or a concat
// containing an NTEXT leaf.
// *Action: Either pick a different partition dimension, or redefine the
// dimension to use a different datatype.
36671, 00000, "(XSDPART09) Leaves of %q have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used."
// *Cause: User attempted to define a range partition template with a concat
// partition dimension, and the concat had two leaf dimensions with
// different datatypes.
// *Action: Pick a different partition dimension.
36672, 00000, "(XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension."
// *Cause: User attempted to define a RANGE or LIST partition template with
// more than one partition dimension.
// *Action: Remove all but one of the dimensions from the
// PARTITION BY RANGE(...) or PARTITION BY LIST(...) clause of
// the partition template definition.
36673, 00000, "(XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the <LEAF: VALUE> format."
// *Cause: When defining a RANGE partition template with a concat dimension
// for the partition dimension, the user attempted to define a
// range using the <LEAF: VALUE> format of a concat dimension value.
// *Action: Use just the leaf value. Instead of
// "VALUES LESS THAN <leaf: value>", just say,
// "VALUES LESS THAN value".
36674, 00000, "(XSDPART12) Invalid dimension value starting at %t."
// *Cause: When defining a RANGE or LIST partition template, the user
// specified an invalid value in a VALUES LESS THAN or VALUES
// clause. An "invalid value" can be one of two things: a value
// whose datatype does not match the partition dimension's
// datatype, or a non-constant value.
// *Action: Modify the offending VALUES LESS THAN or VALUES phrase.
36675, 00000, "(XSDPART13) A RANGE or LIST PARTITION TEMPLATE cannot have a conjoint for its partition dimension."
// *Cause:
// *Action:
36676, 00000, "(XSDPART14) Missing dimension list for %t."
// *Cause: User attempted to define a CONCAT partition template, and didn't
// supply a list of dimensions for one of the partition definitions.
// *Action: Give a dimension list for each partition.
36677, 00000, "(XSDPART15) %a %v %v\nDuplicate value in value lists of %1p and %2p"
// *Cause: In a LIST PARTITION TEMPLATE definition, a value appeared in more
// than one value list, or more than once within a single value list.
// *Action: List each value only once.
36678, 00000, "(XSDPART16) %j is missing from one or more partition dimension lists."
// *Cause: In the definition of a partition template, one of the partitions
// had a dimension list that did not contain all the dimensions
// of the partition template.
// *Action: Add the offending dimension to the partition's dimension list,
// or delete it from the partition template's dimension list.
// If using CONCAT partitioning and the missing dimension is a
// partition dimension, add to the partition dimension list any
// leaf of the partition dimension or any concat of leaves of
// the partition dimension.
36679, 00000, "(XSDPART17) %a %j %j %j\n%1p contains a leaf (%2p) that is not part of the partition dimension %3p."
// *Cause: In the definition of a CONCAT partition template, one of the
// partitions was dimensioned by a dimension that is "concat-related"
// to a partition dimension, meaning it shares some leaves with the
// partition dimension, but it contained some leaves that are not
// in the partition dimension.
// *Action: Either modify the dimensionality of the partition template to
// include a concat dimension that contains all the desired leaves,
// or pick a different dimension for the partition.
36680, 00000, "(XSDPART18) %j is not a dimension of the PARTITION TEMPLATE."
// *Cause: In the definition of a partition template, one of the partitions was
// dimensioned by a dimension that was not given in the dimension
// list of the partition template.
// *Action: Remove the offending dimension from the partition's dimension list,
// or add it to the partition template's dimension list.
36681, 00000, "(XSDPART19) %a %s %s\nPartitions %1p and %2p are out of order."
// *Cause: In the definition of a range partition template, a partition
// with a lower range boundary was listed after a partition with
// a higher range boundary.
// *Action: Alter the order of the partition definition list.
36682, 00000, "(XSDPART20) Partition name %t appears more than once."
// *Cause: A list of analytic workspace partitions was specified in which
// the partition name appeared more than once.
// *Action: Remove all but the first instance of the partition name from
// the list.
36683, 00000, "(XSDPART21) Partition %t dimensioned by more than one composite."
// *Cause: It is illegal to define a partition template in which one of the
// partitions is dimensioned by more than one composite.
// *Action: Make sure that the partition template being defined has at most
// one composite per partition.
36684, 00000, "(XSDPART22) %a %j %j\nYou cannot rename values of DIMENSION %1p because it is the partition dimension of RANGE PARTITION TEMPLATE %2p"
// *Cause: User attempted to rename a value of a dimension that serves as
// the partition dimension of some RANGE or LIST partition template.
// *Action: It is not possible to rename values in such a dimension without
// deleting all RANGE and LIST partition templates that are
// partitioned by it.
36685, 00000, "(XSDPART23) Only CONCAT partition templates can be subpartitioned."
// *Cause: User attempted to define a RANGE or LIST partition template with
// one or more partitions dimensioned by another partition template.
// *Action: Use only regular dimensions and composites to dimension each
// partition of the RANGE or LIST template.
36686, 00000, "(XSDPART24) %a %v %v\nValue %1p is not in partition %2p."
// *Cause: User attempted to reorganize a list partition template by
// removing a value from some partition's list, but the value
// was not in the list.
// *Action: Ensure that the given values match the given partition.
36687, 00000, "(XSDPART25) %a %j %j\nYou cannot use compressed composite %1p to dimension multiple partitions of the partition template, because its dimension list includes the PARTITION BY dimension %2p."
// *Cause: The specified PARTITION BY dimension also occurred in the dimension
// list of a compressed composite used to dimension multiple
// partitions.
// *Action: Ensure that no PARTITION BY dimension occurs among the bases of
// the compressed composite used to dimension multiple partitions.
36688, 00000, "(NTEXTCNV00) Error during conversion from TEXT to NTEXT."
// *Cause: An unknown character set conversion error occurred when converting
// a TEXT value to an NTEXT value.
// *Action: Unknown.
36691, 00000, "(NTEXTCNV02) Invalid escape sequence in argument to UNISTR function: %i."
// *Cause: The user called the UNISTR function on a string that had an
// invalid escape sequence. The only valid escape sequences in UNISTR are
// 1.) an escape-escape sequence, and 2.) an escape, followed by exactly
// four hexadecimal digits.
// *Action: Make sure that all escape sequences in UNISTR arguments are
// exactly four hexadecimal digits. To represent codepoints whose value
// is less than 0x1000, use preceding zeros. WRONG: 0x10; RIGHT: 0x0010.
36692, 00000, "(XSRELGID24) A level relation must be specified for the GROUPSET and ROLLUP options of GROUPINGID."
// *Cause: level relation was not specified.
// *Action: Specify a level relation.
36693, 00000, "(XSRELGID25) INHIERARCHY cannot be specified with the GROUPSET and ROLLUP options of GROUPINGID."
// *Cause: INHIERARCHY option was specified.
// *Action: Remove INHIERARCHY option.
36694, 00000, "(XSRELTBL01) The value cannot be added to dimension %j."
// *Cause: Unknown.
// *Action: Check the context and permission for dimension maintenance.
36695, 00000, "(XSRELGID26) %a %d %d\nThe length of GID dimension status is %1p. The length of LEVEL dimension status is %2p."
// *Cause: GID dimension status did not match LEVEL dimension status.
// *Action: Change either GID dimension status or LEVEL dimension status.
36696, 00000, "(XSRELTBL02) QDR dimension %j should not be the related dimension of the relation."
// *Cause: An ineligible dimension was specified in the Qualified Data Reference
// *Action: Do not attempt to qualify this dimension.
36698, 00000, "(XSRELTBL03) QDR dimension %j should be in the dimension list that dimensions the relation."
// *Cause: The named dimension was not in the relation's dimension list.
// *Action: Select only dimensions that are in the relation's dimension list.
36700, 00000, "(XSRELTBL04) Dimension %j cannot be qualified more than once."
// *Cause: The same dimension was specified more than once in the QDR.
// *Action: Specify each QDR dimension only once.
36702, 00000, "(XSRELTBL05) The format of the HIERHEIGHT function is: \n HIERHEIGHT(relation [,] level)\n level >= 1."
// *Cause: The HIERHEIGHT function was specified incorrectly.
// *Action: Make sure the format is correct.
36704, 00000, "(XSRELTBL06) %a %n %j\n%1p should be dimensioned by %2p."
// *Cause: The level relation is not dimensioned by the source relation dimension.
// *Action: Make sure the level relation has the correct definition.
36706, 00000, "(XSRELTBL07) %a %n %j\n%1p should be dimensioned by %2p and one level dimension."
// *Cause: The destination relation has the wrong definition.
// *Action: Make sure the destination relation has the correct dimensions.
36708, 00000, "(XSMXALLOC00) Variable %n must be dimensioned to be used by the ALLOCATE command."
// *Cause: The user supplied an undimensioned (scalar) variable to the ALLOCATE command.
// *Action: Use a dimensioned variable.
36710, 00000, "(XSMXALLOC01) %a %n %n\nTARGETLOG variable %2p must be dimensioned identically to TARGET variable %1p."
// *Cause: The user attempted to execute ALLOCATE with mismatched TARGET and
// TARGETLOG variables
// *Action: Use TARGET and TARGETLOG variables with matching dimensionality.
36712, 00000, "(XSMXALLOC02) Relation %n must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE."
// *Cause: The user specified an invalid source or basis relation on the
// ALLOCATE command line.
// *Action: Modify the relation to be a one-dimensional self-relation.
36714, 00000, "(XSMXALLOC03) %a %n %n\nTARGETLOG variable %2p must have the same data type as TARGET variable %1p."
// *Cause: The user specified a TARGETLOG variable that had a different
// data type from the TARGET variable.
// *Action: Use TARGETLOG and TARGET variables with an identical data type.
36718, 00000, "(XSALLOC00) You do not have the necessary permissions to use AGGMAP %j."
// *Cause: The user did not have sufficient permissions to run the ALLOCATE
// command
// *Action: Change to a user ID with the appropriate permissions, or use objects
// that you have permission to use.
36720, 00000, "(XSALLOC01) To be used with ALLOCATE, your AGGMAP %j must be defined with the ALLOCMAP command."
// *Cause: The user used the AGGMAP command to define the AGGMAP, so either the
// AGGMAP can only be used with the AGGREGATE command, or the AGGMAP
// has no contents attached to it.
// *Action: Use the ALLOCMAP command to define the AGGMAP.
36722, 00000, "(XSALLOC02) %a %j %n\nIn AGGMAP %1p, you specified an NA or ZERO sourceval but supplied formula %2p as your source for ALLOCATE."
// *Cause: The user requested that source values be modified during
// the allocation, but that is not possible when using a formula
// source.
// *Action: Either use a VARIABLE source or remove the SOURCEVAL
// specification for your ALLOCMAP.
36724, 00000, "(XSALLOC03) %j cannot include more dimensions than the source variable."
// *Cause:
// *Action:
36726, 00000, "(XSALERR00) The character '%c' is not a valid format specifier for the ALLOCATE error log."
// *Cause: The user specified an invalid formatter in the ALLOCERRLOGHEADER
// or ALLOCERRLOGFORMAT options.
// *Action: Correct the option to have a valid format.
36728, 00000, "(XSALERR01) %a %j %d\nWhile performing the ALLOCATE command with AGGMAP %1p, the error logging limit of %2p was exceeded."
// *Cause: The user specified an ERRORLOG MAX value in the ALLOCMAP, but
// more errors were encountered while performing the allocation.
// *Action: Either set ERRORLOG NOSTOP, reduce the allocation errors, or
// increase the ERRORLOG MAX setting
// Codes 36730-36760 are reserved for ALLOCATE error log output
// Please limit string length to conform to this:
// "-------------------------------------------------"
36730, 00000, "A deadlock occurred allocating data."
// *Cause:
// *Action:
36731, 00000, "An NA basis parent cell was encountered."
// *Cause:
// *Action:
36732, 00000, "A value was less than the FLOOR specification."
// *Cause:
// *Action:
36733, 00000, "A value exceeded the CEILING specification."
// *Cause:
// *Action:
36734, 00000, "A value was less than the MIN specification."
// *Cause:
// *Action:
36735, 00000, "A value exceeded the MAX specification"
// *Cause:.
// *Action:
36736, 00000, "Renormalizing data"
// *Cause:
// *Action:
36737, 00000, "The logging limit was exceeded."
// *Cause:
// *Action:
36738, 00000, "Falling back to NAOPERATOR after deadlock."
// *Cause:
// *Action:
36739, 00000, "Redistributing remainder with REMOPERATOR."
// *Cause:
// *Action:
36740, 00000, "A CHILDLOCK was detected in your valueset"
// *Cause:.
// *Action:
36741, 00000, "A source was OVER ALLOCATED to its children"
// *Cause:
// *Action:
// Codes 36730-36760 are reserved for ALLOCATE error log output
36761, 00000, "(XSLANGDM01) %a %s %J %s\nAnalytic workspace %1p already contains a dimension (%2p) with the %3p property."
// *Cause: An attempt was made to apply this property to more than one
// dimension in the AW.
// *Action: Remove the property from the named dimension and try the command
// again.
36762, 00000, "(XSLANGDM02) %a %s %J %s\nYou cannot modify the %1p property of %2p because analytic workspace %3p is attached in MULTI mode."
// *Cause: An attempt was made to add or delete a $DEFAULT_LANGUAGE property
// in an AW attached in multiwriter mode.
// *Action: Attach the AW in a different mode.
36763, 00000, "(XSAGGCNTMOVE01) Aggregation variable %n cannot have itself as an AGGCOUNT."
// *Cause: An attempt was made to turn a variable into its own AGGCOUNT.
// *Action: Select a different AGGCOUNT variable.
36764, 00000, "(XSAGGCNTMOVE02) %a %s %n\nAGGCOUNT variable %2p must be of type INTEGER, not %1p."
// *Cause: An attempt was made to create a non-INTEGER AGGCOUNT.
// *Action: Select an INTEGER AGGCOUNT variable.
36765, 00000, "(XSAGGCNTMOVE03) %a %s %s\nA %1p aggregation variable cannot have a %2p AGGCOUNT."
// *Cause: The specified AGGCOUNT variable did not have the same permanence as
// the aggregation variable.
// *Action: Select an AGGCOUNT variable with the same TEMPORARY or PERMANENT
// attribute as the aggregation variable.
36766, 00000, "(XSAGGCNTMOVE04) %n cannot be used as an AGGCOUNT because it has an AGGCOUNT."
// *Cause: The specified AGGCOUNT variable had its own AGGCOUNT
// *Action: Select a different variable, or remove the AGGCOUNT using CHGDFN.
36767, 00000, "(XSAGGCNTMOVE05) %n cannot be used as an AGGCOUNT while there are permissions applied to it."
// *Cause: The specified AGGCOUNT variable had its own permissions distinct
// from those on the aggregation variable.
// *Action: Select a different AGGCOUNT variable, or remove the permissions.
// In some cases this may require an UPDATE before the command can
// succeed.
36768, 00000, "(XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT must have the same base dimensions."
// *Cause: An AGGCOUNT variable was specified with different base dimensions
// than the aggregation variable.
// *Action: Select an AGGCOUNT variable with exactly the same base dimensions
// as the aggregation variable.
36777, 00000, "Unable to allocate %s bytes for the OLAP page pool."
// *Cause: Insufficient memory was available to allocate the needed memory
// for the online analytical processing (OLAP) page pool. One
// cause is the value of the OLAP_PAGE_POOL_SIZE initialization
// parameter.
// *Action: Check the value of the OLAP_PAGE_POOL_SIZE initialization
// parameter. It cannot be larger than 90% of the value of
// the PGA_AGGREGATE_LIMIT initialization parameter.
36778, 00000, "(XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace."
// *Cause: Ran out of temporary tablespace storage.
// *Action: Increase the amount of temporary tablespace storage.
36779, 00000, "Invalid parameter value."
// *Cause: The specified value for the OLAP_PAGE_POOL_SIZE initialization
// parameter was out of range. The OLAP_PAGE_POOL_SIZE
// initialization parameter must be between 2097152 and
// 2147483647, and smaller than 90% of the PGA_AGGREGATE_LIMIT
// initialization parameter. Additionally, you cannot use a
// fixed-size OLAP page pool with multiple tablespace block
// sizes. The OLAP_PAGE_POOL_SIZE initialization parameter remains
// unmodified.
// *Action: None.
36780, 00000, "(IOSEC01) Current Directory Alias is not set. Cannot complete %s."
// *Cause:
// *Action: Use CDA command to set current directory alias or include the directory alias in the file name.
36782, 00000, "(IOSEC02) Directory Alias used in %s does not exist, or you do not have sufficient privileges to access it."
// *Cause:
// *Action: Use CREATE DIRECTORY <name> AS 'path'. Then grant privileges to that directory alias.
36783, 00000, "Directory alias used in %s does not exist, or you do not have sufficient privileges to access it."
// *Cause: The directory alias did not exist, or you did not have sufficient privileges to access it.
// *Action: Use CREATE DIRECTORY <name> AS 'path'. Then grant privileges to that directory alias.
36784, 00000, "(IOSEC03) %s is an invalid directory or file name."
// *Cause:
// *Action:
36785, 00000, "Invalid directory or file name %s."
// *Cause:
// *Action:
36786, 00000, "(IOSEC04) File %s does not exist or cannot be accessed."
// *Cause:
// *Action:
36792, 00000, "(IOSEC07) Error accessing file %s."
// *Cause:
// *Action:
36793, 00000, "Error accessing file %s."
// *Cause:
// *Action:
//------------------------ TABLE FUNCTION ERRORS -----------------
/// Codes 36800 - 36900 reserved for table function code
36800, 00000, "(XSTBLFUNC00) The OLAP_TABLE function can only have a single LOOP statement within the LIMITMAP"
// *Cause: The OLAP table function given used more than one LOOP statement.
// *Action: It is currently impossible to specify more than one LOOP composite,
// either remove one of the statements (and loop densely over relevant
// dimensions), or create a new composite that encompasses both loops
// and have a single loop statement refer to that.
36802, 00000, "(XSTBLFUNC01) The OLAP_TABLE function must contain a DATAMAP that executes a FETCH command or a LIMITMAP."
// *Cause: There is no limitmap on the table function and either the datamap
// does not contain a fetch, or it errored before the fetch was called.
// *Action: Check the datamap for errors, make sure that it executes a fetch
// statement, if it is not intended to execute the fetch then make sure
// that the table function has a valid limitmap.
36804, 0000, "(XSTBLFUNC02) The OLAP_TABLE function encountered an error while parsing the LIMITMAP."
// *Cause: Invalid LIMITMAP syntax, or the name resolution failure of an
// ANALYTIC WORSKPACE OBJECT.
// *Action: Check the syntax of the limit map, check that the
// OLAP_TABLE function refers to a valid analytic workspace, check
// that all analytic workspace objects within the limitmap actually
// exist within the analytic workspace
36806, 0000, "(XSTBLFUNC03) The OLAP_TABLE function refers to an invalid ADT attribute: %s."
// *Cause: The limitmap refers to a matching of ADT attribute to AW object,
// but the ADT attribute is not an element of the specified ADT table.
// Most commonly this is a typo.
// *Action: Add the attribute to the ADT, correct the LIMITMAP, or remove
// the reference from the LIMITMAP.
36808, 0000, "(XSTBLFUNC04) %a %d %d\nThe OLAP_TABLE function LEVELREL clause cannot declare %1p ADT fields from %2p AW fields."
// *Cause: The limitmap has a levelrel clause which has a different number
// of values in the list to the right of the FROM than it has to the left.
// *Action: Change the limitmap so that there is a 1:1 mapping of adt and aw
// elements.
36810, 0000, "(XSTBLFUNC05) Analytic workspace object %v does not exist."
// *Cause: The limitmap refers to a non-existent aw object.
// *Action: Change the limitmap or define the object
36812, 0000, "(XSTBLFUNC06) Invalid Syntax at '?'."
// *Cause: The limitmap has a question mark character outside the context
// of a string.
// *Action: Fix the limitmap
36814, 0000, "(XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16)."
// *Cause: Datatype of column used in ROW2CELL clause of a LIMITMAP is not RAW(16).
// *Action: Change datatype to RAW(16).
36815, 0000, "(XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW single row function with the aw_attach parameter set to DURATION QUERY."
// *Cause: The OLAP_TABLE aw_attach parameter was set to DURATION QUERY.
// *Action: Change the OLAP_TABLE aw_attach parameter to DURATION SESSION.
36816, 0000, "(XSTBLFUNC09) The %j dimension is of datatype %s which does not support custom member upserts."
// *Cause: Custom members were attempted to be added via an upsert to a dimension that does not support them
// *Action: Disable the AW Hash optimization for this query
36817, 0000, "(XSTBLFUNC10) The LIMITMAP LOOP clause specifies an invalid type of object. %j must be a DIMENSION or COMPOSITE."
// *Cause: An invalid type of object was specified in the LOOP clause.
// *Action: Correct the LOOP clause.
36818, 0000, "(XSTBLFUNC11) A LIMITMAP DIMENSION clause specifies an invalid type of object. %j must be a DIMENSION."
// *Cause: An invalid type of object was specified in the DIMENSION clause.
// *Action: Correct the DIMENSION clause.
36819, 0000, "(XSTBLFUNC12) %j cannot be used in a LIMITMAP %s clause."
// *Cause: An invalid type of object was specified in a LIMITMAP clause.
// *Action: Correct the LIMITMAP clause.
36820, 0000, "(XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP."
// *Cause: Invalid LIMITMAP syntax.
// *Action: Correct the syntax of the limit map.
36821, 0000, "(XSJPUSH00) An error occurred while attempting to push a join of 2 AW tables."
// *Cause: Unknown.
// *Action: Re-execute the query with parameter _optimizer_aw_join_push_enabled = FALSE.
36825, 0000, "(XSTBLFUNC13) An error occurred expanding the cube_name argument in the OLAP table function"
// *Cause: Incorrect metadata or invalid cube name
// *Action: Correct the metadata.
36826, 0000, "(XSTBLFUNC14) OLAP C Looper is disabled by event 37395"
// *Cause: init.ora event 37395 includes level 8 which disables the OLAP C looper
// *Action: Remove event level 8 and use explicit FETCH function for OLAP_TABLE
36830, 0000, "(XSLMGEN00) %a %s %s\nObject %1p.%2p does not exist"
// *Cause: The object does not exist
// *Action: Check view token for errors
36831, 0000, "(XSLMGEN01) View token cannot be NA"
// *Cause: A NA was passed as the view token
// *Action: Pass in a valid view token
36832, 0000, "(XSLMGEN02) View token cannot be greater than 4000 bytes"
// *Cause: A view token was greater than 4000 bytes
// *Action: Pass in a view token less than 4000 bytes
36833, 0000, "(XSLMGEN03) View token cannot be blank"
// *Cause: A blank was passed as the view token
// *Action: Pass in a valid view token
36834, 0000, "(XSLMGEN04) Column tag is greater than 30 bytes"
// *Cause: A value greater than 30 bytes was passed as the column tag
// *Action: Pass in a column tag of 30 bytes or less
36835, 0000, "(XSLMGEN05) %a %s %s %s %s\nDimension %1p.%2p hierarchy %3p level %4p is missing a COLUMNNAME property value"
// *Cause: The COLUMNNAME property has no value
// *Action: Add a value to COLUMNNAME property
36836, 0000, "(XSLMGEN06) %a %s %s\nThe dimensionality of object %1p.%2p is different than the view token"
// *Cause: The dimensionality of the cube does not match the view token
// *Action: Check view token for unrelated hierarchies clauses
36837, 0000, "(XSLMGEN07) %a %s %s\nObject owner %1p is different than %2p"
// *Cause: The object owners are different
// *Action: Make the object owners match
36838, 0000, "(XSLMGEN08) %a %s %s %s\nDimension %1p.%2p attribute %3p is missing a COLUMNNAME property value"
// *Cause: The COLUMNNAME property has no value
// *Action: Add a value to COLUMNNAME property
36839, 0000, "(XSLMGEN09) %a %s %s %s\nCube %1p.%2p measure %3p is missing a COLUMNNAME property value"
// *Cause: The COLUMNNAME property has no value
// *Action: Add a value to COLUMNNAME property
36840, 0000, "(XSLMGEN10) %a %s %s\nCube %1p.%2p has no measures"
// *Cause: The cube has no measures
// *Action: Add a measure to the cube
36841, 0000, "(XSLMGEN11) %a %s %s\nDimension %1p.%2p was not found"
// *Cause: The view token referenced a dimension that does not exist
// *Action: Pass in a dimension that does exist
36842, 0000, "(XSLMGEN12) %a %s %s %s\nHierarchy %1p.%2p.%3p was not found"
// *Cause: The view token referenced a hierarchy that does not exist
// *Action: Pass in a hierarchy that does exist
36843, 0000, "(XSLMGEN13) %a %s %s %s\nDimension %1p.%2p hierarchy %3p is missing a PHYSICALNAME property value"
// *Cause: The property PHYSICALNAME has no value
// *Action: Populate the property PHYSICALNAME with a value
36844, 0000, "(XSLMGEN14) %a %s %s %s\nDimension %1p.%2p is missing a %3p property value"
// *Cause: The dimension is missing a required property
// *Action: Check dimension property values
36845, 0000, "(XSLMGEN15) Owner is greater than 30 bytes"
// *Cause: The owner passed is greater than 30 bytes
// *Action: Pass in an owner that is 30 bytes or less
36846, 0000, "(XSLMGEN16) AW name is greater than 30 bytes"
// *Cause: The AW name passed is greater than 30 bytes
// *Action: Pass in an AW name that is 30 bytes or less
36847, 0000, "(XSLMGEN17) AW name is blank"
// *Cause: The AW name passed is blank
// *Action: Pass in an AW name that has a value
36848, 0000, "(XSLMGEN18) %a %s %s\nObject name %1p is different than %2p"
// *Cause: The object names are different
// *Action: Make the object names match
36849, 0000, "(XSLMGEN19) AW owner does not match View token owner"
// *Cause: The AW owner does not match the View token owner
// *Action: Match AW ower to View token object owner
36850, 0000, "(XSLMGEN20) %a %s\nView token %1p is not correct"
// *Cause: The view token is not correct
// *Action: Check view token syntax for errors
36861, 0000, "(XSTFRC01) SQL Cache ID parameter is invalid or missing."
// *Cause: SQL Cache ID parameter is required to identify SQL cache to query
// *Action: Supply a valid SQL Cache ID. Normally, users should not call OLAP Random Access Cursor table function themselves and therefore should not encounter this error.
36862, 0000, "(XSTFRC02) %a %d %d\nColumn number for this SQL Cache must be between 1 and %1p. Specified column number %2p is invalid."
// *Cause: Column Map references a column number that is greater than the maximum column number in SQL Cache
// *Action: Reference a correct column number. Normally, users should not call OLAP Random Access Cursor table function themselves and therefore should not encounter this error.
36871, 0000, "(XSFTDSC01) Object %s cannot be used to define a column in a LIMITMAP."
// *Cause: The object cannot define a column in LIMITMAP most likely because it
// is of a wrong type such as, for example, a Worksheet.
// *Action: Remove the reference from the LIMITMAP.
36872, 0000, "(XSTFDSC02) Column type specifier cannot be used when the table function data type is specified."
// *Cause: Column type can only be used with implicitly-specified table functions
// *Action: Remove column type from reference from the LIMITMAP or remove the
// explicit table function data type specification.
36873, 0000, "(XSTFDSC03) Column type must be specified explicitly."
// *Cause: Missing column type specification.
// *Action: Please, make sure to specify a column type in COLUMN MAP. Normally, users should not call OLAP Random Access Cursor table function themselves and therefore should not encounter this error.
36874, 0000, "(XSTFDSC04) Expression %s cannot be used to define a column in a LIMITMAP."
// *Cause: The expression cannot define a column in LIMITMAP most likely
// because it is of a wrong type such as, for example, a Worksheet.
// *Action: Remove the reference from the LIMITMAP.
36875, 0000, "(XSTFDSC05) LIMITMAP is missing or is not a string literal."
// *Cause: Table functions that have an automatic ADT require LIMITMAP to be a string literal.
// *Action: Either specify ADT for the table function or specify LIMITMAP as a string literal.
36876, 0000, "(XSTFDSC06) The column datatype %s is not supported in OLAP table functions."
// *Cause: The object type layer does not support column datatype.
// *Action: Use a supported column datatype.
//------------------------- SINGLE ROW FUNCTION ERRORS ---------------------
36881, 0000, "(XSSRF00) The OLAP DML ROW2CELL function can only be used in a LIMITMAP."
// *Cause: Using the ROW2CELL function outside of the LIMITMAP.
// *Action: Remove use of the ROW2CELL function.
36882, 0000, "(XSSRF01) The second parameter of an AW single row function cannot be NULL."
// *Cause: The second parameter of the AW single row function was NULL
// *Action: Pass a valid OLAP DML expression as the second parameter of the AW single row function
36883, 0000, "(XSSRF02) The first parameter of an AW single row function cannot be NULL."
// *Cause: The first parameter of the AW single row function was NULL
// *Action: Make sure the column specified in the LIMITMAP ROW2CELL clause is the first parameter of the AW single row function.
36884, 0000, "(XSSRF03) The value of the first parameter of the AW single row function is incorrect."
// *Cause: The column specified in the LIMITMAP ROW2CELL clause was not the first parameter of the AW single row function.
// *Action: Make sure the column specified in the LIMITMAP ROW2CELL clause is the first parameter of the AW single row function.
36885, 0000, "(XSSRF04) Error rewriting OLAP DML expression. Column name too big"
// *Cause: The column name specified in the OLAP DML expression was larger than 30 bytes.
// *Action: Make sure the column name specified in the OLAP DML expression is less than or equal to 30 bytes.
36886, 0000, "(XSSRF05) %a %ld\nError rewritting OLAP DML expression. Rewritten expression is greater than %1p bytes"
// *Cause: The rewritten OLAP DML expression was larger than the output buffer.
// *Action: Create a smaller OLAP DML expression.
36887, 0000, "(XSSRF06) Error rewriting OLAP DML expression. Column name %s is not a valid ADT column."
// *Cause: The column name passes does not exist.
// *Action: Only reference columns that exist.
//----------------------------MORE XSAGDNGL-------------------
36902, 0000, "(XSAGDNGL43) %a %j %n\nIn AGGMAP %1p, the MODEL %2p is not a model over a base dimension of the AGGMAP."
// *Cause: Model may include equations others than dimension values, or
// blocks other than simple blocks.
// *Action: Make sure model only includes the simple blocks with dimension
// values.
36904, 0000, "(XSAGDNGL44) %a %j %n\nIn AGGMAP %1p, RELATION %2p occurs after a dynamic model. The dynamic model must be the last calculation within the AGGMAP."
// *Cause: Before the current relation, dynamic model exists.
// *Action: Make sure the dynamic model is the last statement.
36910, 0000, "(XSAGDNGL47) %a %j %j\nIn AGGMAP %1p, DYNAMIC MODEL %2p can only edit the top level of its matching relation hierarchy."
// *Cause: The model attempted to edit a child node in the relation hierarchy.
// *Action: Remove this attempt from the model definition.
36912, 0000, "(XSAGDNGL48) %a %j %n\nIn AGGMAP %1p, MODEL %2p cannot be simultaneous."
// *Cause: The aggmap contained a simultaneous model.
// *Action: Change the model definition so that it is no longer simultaneous.
36913, 0000, "(XSAGDNGL49) %a %j %j\nIn AGGMAP %1p, LOAD_STATUS object %2p must be an undimensioned VALUESET over the relation dimension."
// *Cause: The object refered to by the LOAD_STATUS clause of the aggmap
// wasn't an undimensioned valueset over the related dimension
// *Action: Change the aggmap definition so that it doesn't refer to an
// invalid object
36914, 0000, "(XSAGDNGL50) %a %j %j\nIn AGGMAP %1p, LOAD_STATUS valueset %2p contains both a child and its ancestor."
// *Cause: The LOAD_STATUS valueset is not allowed to contain both a dimension
// value and an ancestor of that value.
// *Action: Perform a limit remove ancestors on the valueset and confirm
// that the result matches the intended load.
// 36920 - 36929 reserved for _mvtopartartition messages
36920, 0, "(XSVPMVTOPART01) %n cannot become anonymous because it has properties."
// *Cause: The OLAP DML command would result in a named object
// becoming an anonymous object, but the object had one
// or more properties associated with it.
// *Action: Remove the properties using the PROPERTY command. In some cases
// an UPDATE may be required before the command can proceed.
36921, 0, "(XSVPMVTOPART02) %a %n %n\n%1p and %2p are not in the same analytic workspace."
// *Cause: The OLAP DML command requires certain objects to be in the
// same analytic workspace, and the command string specified
// objects from two different analytic workspaces.
// *Action: If more than one analytic workspace is attached to the
// session, make sure that the object names given in the
// command are unique across all attached analytic workspaces.
// Use qualified object names (QON's) if necessary.
36922, 0, "(XSVPMVTOPART03) %n is the target of an external partition of a partitioned variable."
// *Cause: An attempt was made to perform some prohibited operation on
// a variable which is itself a partition of some other variable.
// *Action: If desired, use the CHGDFN command to DROP the partition
// from the partitioned variable, and then run the command
// again.
36923, 0, "(XSVPMVTOPART04) %j is not a LIST or RANGE PARTITION TEMPLATE."
// *Cause: The user ran a command that only operates on a
// LIST or RANGE partition template (or a variable dimensioned
// by a LIST or RANGE partition template) on some other kind
// of analytic workspace object.
// *Action: Rerun the command on a LIST or RANGE partition template or
// a variable dimensioned by a LIST or RANGE partition template.
36924, 0, "(XSVPMVTOPART05) %j is not in a COMPOSITE."
// *Cause: The OLAP DML command expected that the variable would
// be dimensioned by a composite containing the specified dimension,
// the specified dimension within a composite.
// *Action: Rerun the command on some variable is dimensioned
// by a composite containing the specified dimension.
36925, 0, "(XSVPMVTOPART06) %a %v %j\nPartition %1p has some values that are not in %2p."
// *Cause:
// *Action:
36926, 0, "(XSVPMVTOPART07) More than one variable is dimensioned by %j."
// *Cause:
// *Action:
// ---- 36930 - 36939 are reserved for xsrdbms ----
36930, 0000, "Cannot start a recursive call to Oracle OLAP because a ROLLBACK past an UPDATE to an attached analytic workspace has been performed."
// *Cause: ROLLBACK past the UPDATE of one of the attached Analytic Workspaces was called. A recursive Oracle OLAP call cannot be made until the control returns to the initial OLAP call and the affected Analytic Workspaces detached.
// *Action: Change the called SQL procedure to avoid the ROLLBACK
// ---- 36940 - 36949 are reserved for XSDPENG ----
36940, 0000, "(XSDPENG00) You cannot apply the PARTITION function to %j because it is not a partition template."
// *Cause:
// *Action:
//----------------------------MORE XSFCAST--------------------
36950, 0000, "(XSFCAST22) %a %s %d %d\nThe list of %1p values cannot have more than %2p members. You supplied %3p."
// *Cause: There are more than the maximum number of OFFSET or PERIODICITY
// values.
// *Action: Remove some of the values.
36951, 0000, "(XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless PERIODICITY specifies more than one cycle."
// *Cause: ALLOCLAST was set to YES when PERIODICITY specified a single value
// rather than a list of nested cycles.
// *Action: Set ALLOCLAST to FALSE (the default), or specify more than one
// value for PERIODICITY (in the form of a parenthesized list).
36952, 0000, "(XSFCAST23) You cannot specify a cycle number when querying the %s forecasting option."
// *Cause: A cycle number was specified in a call to FCQUERY to retrieve
// forecast data not related to a cycle.
// *Action: Remove the cycle specification from the call to FCQUERY.
36954, 0000, "(XSFCAST24) %a %d %d\nThe cycle number must be between 1 and %1p. You specified %2p."
// *Cause: A cycle number less than 1 or greater than the maximum value was
// specified in a call to FCQUERY.
// *Action: Specify a number in the indicated range.
36956, 0000, "(XSFCAST25) There are only %d PERIODICITY values. You cannot specify more OFFSET values."
// *Cause: More OFFSET values were specified than PERIODICITY values.
// *Action: Supply only as many OFFSETs as there are PERIODICITY values.
36958, 0000, "(XSFCAST26) %a %d %d %d\nThe OFFSET value for cycle %1p cannot be greater than the cycle's PERIODICITY, which is %2p. You specified %3p."
// *Cause: The OFFSET for a cycle exceeded the PERIODICITY for that cycle.
// *Action: Supply an OFFSET less than or equal to the PERODICITY for the
// corresponding cycle.
36960, 0000, "(XSFCAST27) %a %s %d\nThe value of the %1p expression must be an odd number. You specified %2p."
// *Cause: An even number was given for an option that requires an odd number.
// *Action: Supply an odd number or let the option default.
36961, 0000, "Oracle OLAP is not available."
// *Cause: The user attempted to utilize functionality found only in
// Oracle OLAP, but OLAP has not been enabled in the executable.
// *Action: Install the Oracle OLAP option
//--------------------------------------------------------------
36962, 00000, "(XSRELTBL08) %a %t %j\n%1p is not a valid %2p."
// *Cause: The specified value does not exist in the dimension.
// *Action: Specify an existing value of the dimension.
36963, 00000, "(XSRELTBL16) INHIERARCHY object %q should be a valid valueset or boolean variable."
// *Cause: Invalid valueset or variable was specified.
// *Action: Specify a valid valueset or variable.
36964, 00000, "(XSRELTBL09) %j is not a valid level relation."
// *Cause: The specified level relation was not consistent with the
// parentage hierarchy.
// *Action: Fix one or both of the relations involved so that all parents
// are at a higher level than their children.
36965, 00000, "(XSRELTBL17) Invalid LEVELORDER valueset %q."
// *Cause: Invalid LEVELORDER valueset was specified.
// *Action: Specify a valid valueset.
36966, 00000, "(XSRELTBL10) %n must be a dimension."
// *Cause: The qualified object must be a dimensions.
// *Action: Remove the named object from the QDR.
36967, 00000, "(XSRELTBL18) Invalid INHIERARCHY valueset %q."
// *Cause: Invalid valueset was specified.
// *Action: Specify a valid valueset.
36968, 00000, "(XSRELTBL11) Invalid relation %q."
// *Cause: Non-object or an object other than a RELATION was specified
// as source or destination.
// *Action: Specify RELATION objects.
36969, 00000, "(XSRELTBL19) Merged family relation cannot take INHIERARCHY option."
// *Cause: INHIERARCHY option was specified.
// *Action: Remove INHIERARCHY option.
36970, 00000, "(XSRELTBL12) %n must be a self-relation."
// *Cause: The specified source relation was not a self-relation.
// *Action: Specify a self-relation as the source.
36971, 00000, "(XSRELTBL19) Merged family relation cannot take LEVELORDER option."
// *Cause: LEVELORDER option was specified.
// *Action: Remove LEVELORDER option.
36972, 00000, "(XSRELTBL13) %a %n %j\nRelation %1p must be dimensioned by %2p."
// *Cause: Destination relation is not dimensioned by source relation dimension.
// *Action: Give a correct destination relation.
36974, 00000, "(XSRELTBL14) %n is not a BOOLEAN variable dimensioned by all the dimensions of the hierarchy."
// *Cause: The named variable had either the wrong data type or the wrong
// dimensions.
// *Action: Specify a BOOLEAN variable dimensioned by all the dimensions
// of the hierarchy.
36975, 00000, "(XSRELTBL15) You must specify a USING clause naming a relation with same level dimension as LEVELORDER valueset %n."
// *Cause: USING was omitted from the HIERHEIGHT command, or specified a relation containing
// values of a different dimension than the LEVELORDER valueset.
// *Action: Provide a USING clause naming a relation containing values from the correct level dimension.
//--------------------------------------------------------------
36976, 00000, "(XSRELGID00) Invlid GROUPINGID destination relation or variable %q."
// *Cause: Non-Object or invalid relation or invlid variable.
// *Action: Specify the valid relation or variable.
36977, 00000, "(XSRELGID17) The GROUPINGID command does not support hierarchies with more than 126 levels."
// *Cause: The user specified a hierarchy with more than 126 levels.
// *Action: Decrease the number of levels in the hierarchy.
36978, 00000, "(XSRELGID01) %n must be a self-relation."
// *Cause: Source relation is not a self-relation.
// *Action: Specify a self-relation as the source relation.
36979, 00000, "(XSRELGID18) Property %v can only be set by the GROUPINGID command."
// *Cause: You tried to set the $GID_DEPTH property.
// *Action: Stop to set the $GID_DEPTH property.
36980, 00000, "(XSRELGID02) Variable %n must have a numeric data type."
// *Cause: The destination variable does not have a numeric data type.
// *Action: Make sure the variable is numeric.
36981, 00000, "(XSRELGID19) The format of the GROUPINGID function is:\n \n GROUPINGID(gidrel1 [gidrel2]...)"
// *Cause: Bad syntax
// *Action: Correct syntax
36982, 00000, "(XSRELGID03) %a %n %n\nThe destination variable/relation %1p must be dimensioned by all dimensions of the source relation %2p that have more than one value in status."
// *Cause: Destination variable/relation does not have enough dimensionality
// to hold the result from the multi-dimensional source relation.
// *Action: Either limit the status of hierarchy dimensions or redefine the
// destination variable/relation with the extended dimensionality
36983, 00000, "(XSRELGID20) The groupingid relation %n repeats."
// *Cause: The groupingid relation repeated.
// *Action: Remove the duplicated groupingid relation.
36984, 00000, "(XSRELGID04) A value cannot be inserted into dimension %j."
// *Cause:
// *Action:
36985, 00000, "(XSRELGID21) The source relation can be omitted only when using both surrogate GID and level order valueset."
// *Cause: Source relation was not specified.
// *Action: Specify the source relation or both surrogate gid and level
// order valueset.
36986, 00000, "(XSRELGID05) %a %n %j\nRelation %1p must be dimensioned by %2p."
// *Cause: The destination relation is not dimensioned by the dimension of the source relation.
// *Action: Redefine the destination relation or choose another relation
// with the correct dimensionality.
36988, 00000, "(XSRELGID06) The related dimension of relation %n must be of type NUMBER."
// *Cause: The related dimension of the destination relation has the wrong
// data type.
// *Action: Redefine the destination relation or choose another relation
// whose related dimension is of type NUMBER.
36989, 00000, "(XSRELGID23) GROUPSET and ROLLUP options in GROUPINGID require the destination relation."
// *Cause: Either variable or surrrogate dimension was specified as destination.
// *Action: Specify the destination relation.
36990, 0000, "(XSRELGID07) The level relation %n should be dimensioned by a level dimension."
// *Cause: The level relation is not dimensioned by a level dimension.
// *Action: Redefine the level relation or choose another relation with
// the correct dimensionality.
36991, 0000, "(XSRELGID08) The level relation and level order valueset provide inconsistent level mappings. "
// *Cause: There is a conflict between the hierarchy/level relation and
// the level order valueset.
// *Action: Choose objects that do not conflict.
36992, 0000, "(XSRELGID09) A level relation is needed to produce a surrogate dimension gid."
// *Cause: A level relation was not specified.
// *Action: Specify a level relation.
36993, 0000, "(XSRELGID10) OBJECT %j must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension %j."
// *Cause: not a surrogate dimension, or the surrogate dimension is not based on the level dimension.
// *Action: modify/change the surrogate dimension.
36994, 0000, "(XSRELGID11) The SURROGATE DIMENSION %j must be numeric."
// *Cause: The surrogate dimension is not numeric
// *Action: Change the surrogate dimension as numeric
36995, 0000, "(XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity."
// *Cause: more than 1 hierarchies in the current computing scope.
// *Action: use inhierarchy to limit
36996, 0000, "(XSRELGID13) Valueset %n should be defined over dimension %j."
// *Cause: Valueset doesn't match the dimension
// *Action: Change the valueset's dimension
36997, 0000, "(XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified. "
// *Cause: no level relation exists with level order valueset.
// *Action: provide the level relation.
36998, 0000, "(XSRELGID15) LEVEL ORDER VALUESET %n and LEVEL RELATION %n have the different level dimensions."
// *Cause: either level order valueset or level relation has wrong level dimension.
// *Action: choose the correct level dimension
36999, 0000, "(XSRELGID16) OBJECT %n is not a surrogate dimension, a source relation must be specified when creating any non-surrogate grouping id."
// *Cause: use variable/relation gid without providing the source relation
// *Action: use the surrogate or provide the source relation
37000, 0000, "(NOTALIAS00) %a %j %n\n%2p is not an ALIAS DIMENSION of %1p."
// *Cause: The user specified an object which is not alias dimension
// of the first dimension
// *Action: Specify an alias dimension of the first dimension
37001, 0000, "You have one or more attached but unupdated analytic workspaces."
// *Cause: The user has attempted to shut down OLAP, but they have active
// analytic workspaces whose changes have not been saved.
// *Action: Either issue the update command to update the AWs, or
// pass TRUE as the force parameter to dbms_aw.shutdown()
37002, 0000, "Oracle OLAP failed to initialize. Please contact Oracle OLAP technical support."
// *Cause: A severe error occurred while initializing OLAP.
// *Action: Contact support (and possibly OLAP development) for help in
// debugging the issue.
// ---- 37003 - 37008 for AW(LISTALL) ----
37003, 0000, "(AWLISTALL01) %d readers"
// *Cause: used in AW(LISTALL) output formatting when %d is 0
// *Action: none
37004, 0000, "(AWLISTALL02) %d reader"
// *Cause: used in AW(LISTALL) output formatting when %d is 1
// *Action: none
37005, 0000, "(AWLISTALL03) %d readers"
// *Cause: used in AW(LISTALL) output formatting when %d is > 1
// *Action: none
37006, 0000, "(AWLISTALL04) %d writers"
// *Cause: used in AW(LISTALL) output formatting when %d is 0
// *Action: none
37007, 0000, "(AWLISTALL05) %d writer"
// *Cause: used in AW(LISTALL) output formatting when %d is 1
// *Action: none
37008, 0000, "(AWLISTALL06) %d writers"
// *Cause: used in AW(LISTALL) output formatting when %d is > 1
// *Action: none
// ---- 37010 - 37059 are reserved for multiwriter ----
37010, 0000, "(XSACQUIRE_DIFFAW) When using the CONSISTENT WITH clause, all objects must come from the same analytic workspace."
// *Cause: The ACQUIRE command cannot keep objects from several workspaces consistent with each other
// *Action: Omit the CONSISTENT WITH clause or make sure all objects being acquired belong to the same analytic workspace.
37011, 0000, "(XSACQUIRE_LOCKED) Object %j is locked by another user."
// *Cause: Could not acquire (or acquire consistent) the object, since it is locked by another user
// *Action: Try to acquire this object later
37012, 0000, "(XSACQUIRE_TIMEOUT) Object %j is locked by another user and the WAIT timed out."
// *Cause: Could not acquire (or acquire consistent) the object for a while, since it is locked by another user
// *Action: Try to acquire this object later
37013, 0000, "(XSACQUIRE_DEADLOCK) Cannot wait to acquire object %j, since doing so would cause a deadlock."
// *Cause: Waiting to acquire the object would cause a deadlock
// *Action: Release some other object that another user is waiting for and try to acquire this object again.
37014, 0000, "(XSACQUIRE_ACQUIRED) Object %j is already acquired."
// *Cause: The object is already acquired
// *Action: Do not try to acquire this object again
37015, 0000, "(XSACQUIRE_YNRESYNC) Object %j is ambiguously listed to be acquired both with and without RESYNC."
// *Cause: The object is listed in with resync list and no resync list. Such usage is ambiguous as to the user's intent on preserving or not preserving private changes.
// *Action: Do not list the object both with and without RESYNC
37016, 0000, "(XSACQUIRE01) You must specify objects to acquire for the ACQUIRE command."
// *Cause: A list of objects to acquire with or without resync is missing
// *Action: Specify the list of objects to acquire
37018, 0000, "(XSACQUIRE03) Multiwriter operations are not supported for object %j."
// *Cause: Multiwriter presently does not work for this object type
// *Action: Attach the AW in RW or EXCLUSIVE modes to modify this object.
37020, 0000, "(XSMULTI01) Analytic workspace %s is not in MULTI mode."
// *Cause: The workspace for an object is not in multiwriter mode. Hence, no multiwriter operations are allowed on the objects in the workspace
// *Action: Attach the workspace in the multiwriter mode or do not use multiwriter commands with it.
37021, 0000, "(XSMULTI02) Object %j is not acquired."
// *Cause: The object must be acquired for this multiwriter operation
// *Action: Do not use this multiwriter operation on an object that is not acquired
37023, 0000, "(XSMLTUPD01) %a %j %j\nObject %1p cannot be updated without dimension %2p."
// *Cause: One cannot update an object if it is dimensioned by a maintained dimension without updating that dimension or if the object is a relation and the dimension is its target.
// *Action: Include the maintained dimension in the update list
37026, 0000, "(XSMLTRESYNC01) %a %j %j\nObject %1p cannot be resynced without dimension %2p."
// *Cause: One cannot resync an object if it is dimensioned by a maintained dimension without updating that dimension or if the object is a relation and the dimension is its target.
// *Action: Include the maintained dimension in the update list
37027, 0000, "(XSMLTRESYNC02) %a %j %j\nObject %1p cannot be resynced without modified object %2p because they share a modified composite dimension."
// *Cause: When one resyncs an object that is dimensioned by a composite dimension, the composite dimension is resynced automatically, dropping all new tuples. This cannot be done, however, if the automatic resync of the composite dimension might cause data in an object that shares the composite dimension to become NA.
// *Action: Resync both objects together. Alternatively, you can try to acquire the other object (that will ensure that the composite dimension is locked in the latest generation and will not be resynced when resyncing the first object), resync the first object, and release the other object.
37028, 0000, "(XSMLTRESYNC03) %a %j %j\nObject %1p cannot be resynced without modified object %2p because they share a modified dimension map."
// *Cause: When one resyncs an object that is dimensioned by a dimension map, the dimension map is resynced automatically, dropping all changes. This cannot be done, however, if the automatic resync of the dimension map might cause data in an object that shares the dimension map to become NA.
// *Action: Resync both objects together. Alternatively, you can try to acquire the other object (that will ensure that the dimensions map is locked in the latest generation and will not be resynced when resyncing the first object), resync the first object, and release the other object.
37030, 0000, "(XSMLTMAINT01) You cannot maintain %j because it is not ACQUIRED."
// *Cause: One cannot maintain a dimension in a multiwriter AW if it is not acquired.
// *Action: Acquire the dimension first.
37031, 0000, "(XSMLTMAINT02) You cannot DELETE values of dimension %j in MULTI mode."
// *Cause: DELETE is allowed in multiwriter mode only for SESSION dimension members
// *Action: Attach the AW in a R/W mode and perform the DELETE operation
37032, 0000, "(XSMLTMAINT03) You cannot MAINTAIN partition template %j in MULTI mode."
// *Cause: User attempted to add or remove values from a LIST partition
// template's lists while the AW containing the partition template
// was attached in multiwriter mode.
// *Action: Do the maintenance in read only or read-write mode.
37035, 0000, "(XSMLTDCL01) You can only DEFINE SESSION objects in analytic workspace %s because it is attached in MULTI mode."
// *Cause: Persistent object definition in multiwriter mode is not allowed.
// *Action: Do all persistent object definitions in read-write mode.
37036, 0000, "(XSMLTDCL02) You cannot DELETE objects in analytic workspace %s because it is attached in MULTI mode."
// *Cause: One cannot delete objects in an analytic workspace attached in MULTI mode.
// *Action: Do all object in read-only or read-write mode.
37037, 0000, "(XSMLTDCL03) You cannot RENAME objects in analytic workspace %s because it is attached in MULTI mode."
// *Cause: One cannot rename objects in an analytic workspace attached in MULTI mode.
// *Action: Do all persistent object maintenance in read-write mode.
37038, 0000, "(XSMLTDCL04) You cannot change definitions of objects in analytic workspace %s because it is attached in MULTI mode."
// *Cause: One cannot used CHGDFN command on objects in an analytic workspace attached in MULTI mode.
// *Action: Do all persistent object maintenance in read-write mode.
37039, 0000, "(XSMLTDCL05) You cannot maintain triggers in analytic workspace %s because it is attached in MULTI mode."
// *Cause: One cannot use TRIGGER command on objects in an analytic workspace attached in MULTI mode.
// *Action: Do all persistent object maintenance in read-write mode.
37040, 0000, "(XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition %j is locked by another user."
// *Cause: Some object required locking a composite, concat, dimension map, or internal partition, which is locked by another user
// *Action: Try to acquire this object later
37041, 0000, "(XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition %j is locked by another user and the WAIT timed out."
// *Cause: Some object required locking a composite, concat, dimension map, or internal partition, which could not be locked for a while, since it is locked by another user
// *Action: Try to acquire this object later
37042, 0000, "(XSACQUIRE_DEP_DEADLOCK) Cannot wait to acquire composite, concat, dimension map, or internal partition %j, since doing so would cause a deadlock."
// *Cause: Some object required locking a composite, concat, dimension map, or internal partition, which would cause a deadlock
// *Action: Release some other object that another user is waiting for and try to acquire this object again.
37043, 0000, "(XSACQUIRE_DEP_OLDGEN) Composite, concat, dimension map, or internal partition %j cannot be locked, since another user has committed a new one already."
// *Cause: Some object required locking a composite, concat, dimension map, or internal partition in the present generation, which is not possible, since a newer generation already exists.
// *Action: Try to acquire the main object with resync
37044, 0000, "(XSACQUIRE_OLDGEN) Cannot acquire object %j without resync."
// *Cause: Could not acquire the object without resync because another user has committed a newer version of it already.
// *Action: Try to acquire this object with resync parameter
37050, 0000, "(XSMLTDCL06) %a %n %s\nYou cannot use the RELATION command with %1p because analytic workspace %2p is attached in MULTI mode."
// *Cause: One cannot use the RELATION command on objects in an analytic workspace attached in MULTI mode.
// *Action: Change the default relation when the analytic workspace is attached in RW or Exclusive mode.
37051, 0000, "(XSAWRESREV01) You cannot RESYNC or REVERT analytic workspace %s because one or more objects have been defined in it during this session."
// *Cause:
// *Action:
37052, 0000, "(XSAWRESREV02) You cannot RESYNC or REVERT analytic workspace %s because one or more objects have been deleted from it during this session."
// *Cause:
// *Action:
37053, 0000, "(XSAWRESREV03) You cannot RESYNC or REVERT analytic workspace %s because one or more of its objects have had their definitions changed during this session."
// *Cause:
// *Action:
37054, 0000, "(XSAWRESREV04) You cannot RESYNC or REVERT analytic workspace %s because it contains one or more unnamed composites renamed during this session."
// *Cause:
// *Action:
37055, 0000, "(XSAWRESREV05) You cannot RESYNC analytic workspace %s because another session has changed the definitions of one or more objects it contains."
// *Cause:
// *Action:
37056, 0000, "(XSAWRESREV06) %a %j %s\nYou cannot RESYNC or REVERT analytic workspace %2p because one or more SESSION dimensions or composites are based on %1p."
// *Cause:
// *Action:
37060, 0000, "(XSMCSESS08) %v is not a valid custom member in dimension %j."
// *Cause: No custom member or invalid custom member
// *Action: Create the custom member or use the correct custom member
/// 37061 - 37071 available
37072, 0000, "(XSMCSESS00) Object %n has the wrong type."
// *Cause: The object is not of the object type specified in the APPLY clause
// *Action: Specify the correct object type
37073, 0000, "(XSMCSESS01) %a %n %j\nApplied relation %1p must be dimensioned by dimension %2p."
// *Cause: Applied relation has the different dimension from
// the dimension currently being maintained
// *Action: Maintain relation dimension
37074, 0000, "(XSMCSESS02) Variable %n has no default aggmap."
// *Cause: The applied variable has no default aggmap
// *Action: Use variable with the default aggmap or aggmap directly
37075, 0000, "(XSMCSESS03) You cannot rename a session-only dimension value."
// *Cause: The user tried to apply MAINTAIN RENAME to a SESSION value.
// *Action: Delete the old value and add a new one with the desired name.
37076, 0000, "(XSMCSESS04) %j is not the type of dimension that can have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and CONCAT with the UNIQUE attribute."
// *Cause: The user tried to add a SESSION value to a dimension type that does
// not support SESSION values.
// *Action: Use a dimension of one of the listed types.
37077, 0000, "(XSMCSESS05) Object %n is specified more than once."
// *Cause: The same object name was given more than once in the apply
// clause or in the step dimension list.
// *Action: Remove the repetitions.
37078, 0000, "(XSMCSESS06) The dimension being maintained (%n) cannot also be used as a step dimension."
// *Cause: The dimension being maintained was named as a step dimension.
// *Action: Remove this dimension from the list of step dimensions.
37079, 0000, "(XSMCSESS07) Aggmap %j cannot be used for AGGREGATE."
// *Cause: The current aggmap may be for ALLOCATE
// *Action: Choose the correct aggmap for AGGREGATE only.
// ---- 37080 - 37092 are reserved for aggregate advisor ----
37080, 00000, "Advice requested for hierarchy with too many levels"
// *Cause: A request was made for advice on a hierarchy with more levels
// than are supported.
// *Action: Only request advice for hierarchies with less than 32 levels.
37082, 00000, "Invalid percent"
// *Cause: A request was made for advice with an illegal percent value.
// *Action: Request between 0 and 100 percent precomputation.
37083, 00000, "Invalid object %s"
// *Cause: A request was made for advice with an illegal object name.
// *Action: Request using valid object names.
37084, 00000, "Output valueset %s must match %s's dimensionality"
// *Cause: A request was made for advice for a relation with different
// dimensionality from the output valueset.
// *Action: Request using objects that have the same dimensionality.
37086, 00000, "%s is not a valueset"
// *Cause: An operation was attempted that supports only valuesets as
// precompute expressions in an aggmap, yet a different kind of
// precompute expression was used.
// *Action: Replace this limit expression with an equivalent valueset and
// retry the operation. General precompute expressions are deprecated.
// ---- 37093 - 37099 are taken by the OBJORG() function
37093, 00000, "(XSOBJORG_BAD_CUBE) %a %s %s %s\ninvalid property \"%1p\" specified for cube \"%2p.%3p\""
// *Cause: Either the specified cube did not have an AW organization, or the specified property did not apply to cubes.
// *Action: Specify a property that applies to cubes and a cube with an AW organization.
37094, 00000, "(XSOBJORG_BAD_DIM) %a %s %s %s \ninvalid property \"%1p\" specified for dimension \"%2p.%3p\""
// *Cause: Either the specified dimension did not have an AW organization, or the specified property did not apply to dimensions.
// *Action: Specify a property that applies to dimensions and a dimension with an AW organization.
37095, 00000, "(XSOBJORG_BAD_MEAS) %a %s %s %s %s \ninvalid property \"%1p\" specified for measure \"%2p.%3p.%4p\""
// *Cause: Either the specified measure did not have an AW organization, or the specified property did not apply to measures.
// *Action: Specify a property that applies to measures and a measure with an AW organization.
37096, 00000, "(XSOBJORG_BAD_ATTR) %a %s %s %s %s \ninvalid property \"%1p\" specified for base attribute \"%2p.%3p.%4p\""
// *Cause: Either the specified base attribute did not have an AW organization, or the specified property did not apply to base attribute.
// *Action: Specify a property that applies to base attributes and a base attribute with an AW organization.
37097, 00000, "(XSOBJORG_BAD_DIM_LEVEL) %a %s %s %s %s \ninvalid property \"%1p\" specified for dimension level \"%2p.%3p.%4p\""
// *Cause: Either the specified dimension level did not have an AW organization, or the specified property did not apply to dimension levels.
// *Action: Specify a property that applies to dimension levels and a dimension level with an AW organization.
37098, 00000, "(XSOBJORG_BAD_MODEL) %a %s %s %s %s \ninvalid property \"%1p\" specified for dimension calculation model \"%2p.%3p.%4p\""
// *Cause: Either the specified dimension calculation model did not have an AW organization, or the specified property di not apply to dimension calculation models.
// *Action: Specify a property that applies to dimension calculation models and a dimension calculation model with an AW organization.
37099, 00000, "(XSOBJORG_BAD_DIMALITY) %a %s %s %s %s \ninvalid property \"%1p\" specified for dimensionality \"%2p.%3p.%4p\""
// *Cause: Either the specified dimensionality did not have an AW organization, or the specified property did not apply to dimensionalities.
// *Action: Specify a property that applies to dimensionalities and a dimensionality with an AW organization.
37100, 00000, "(XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces."
// *Cause: The user has attempted to shut down OLAP, but they have active
// analytic workspaces whose changes have not been saved.
// *Action: Issue the commit command.
// ---- 37101 - 37110 are reserved for partitioned variables ----
37101, 00000, "(XSVPART01) Partitioning information can only be given for variables dimensioned by a PARTITION TEMPLATE."
// *Cause: User attempted to define or reference an AW object with the
// "all internal" phrase or internal / external partition list, but
// the object was not a variable, was not dimensioned by a partition
// template, or was an already existing target of an external partition.
// *Action: Eliminate phrases specific to partitioned variables from the
// definition string, or dimension the variable by a partition
// template.
37102, 00000, "(XSVPART02) Invalid partition name %t."
// *Cause: The user gave an invalid partition name. When defining a partitioned
// variable, this message indicates that the partition name does not
// exist in the partition template. In any other context, it indicates
// that the partitioned variable or partition template does not have a
// partition with the given name.
// *Action: Supply a valid partition name.
37103, 00000, "(XSVPART03) The dimensionality or datatype of %q does not match the dimensionality or datatype of the partition."
// *Cause: User attempted to define a partitioned variable with an external
// partition, but the target of the external partition had incorrect
// dimensionality or datatype.
// *Action: Pick a different target variable. The target variable must be
// dimensioned by exactly the same dimensions, composites, and
// partition templates, in the same order, as are specified in
// the partition template, and must have the exact same datatype
// (including width, precision, and scale) as the partitioned
// variable itself.
37104, 00000, "(XSVPART04) A partitioned variable must be dimensioned by a single partition template only."
// *Cause: User attempted to define a partitioned variable with more than
// one partition templates, or a partition template and one or more
// other dimensions, in the dimension list.
// *Action: Use only a partition template in the dimension list of the
// variable. All dimensions of the variable must be included in
// the definition of the partition template.
37105, 00000, "(XSVPART05) Only variables dimensioned by a CONCAT PARTITION TEMPLATE can have %t partitions."
// *Cause: User attempted to create an external partition on a partitioned
// variable, but the variable was dimensioned by a RANGE or LIST
// partition template.
// *Action: Declare the partition INTERNAL instead of EXTERNAL, or use a
// CONCAT partition template in place of the RANGE or LIST partition
// template.
37106, 00000, "(XSVPART06) Invalid partition name %v."
// *Cause: The user gave an invalid partition name.
// *Action: Supply a valid partition name.
37107, 00000, "(XSVPART07) Attempt to write to non-existent partition of %j."
// *Cause: Some action attempted to write data to a partitioned variable,
// but the variable didn't have a partition for that data. This can
// result from a partition template that does not assign all possible
// dimension values to some subcube, or from a partitioned variable
// that does not have a partition for one of the partitions defined
// by the partition template.
// *Action: Make sure that the cell being written is assigned to some
// partition by the partition template, and that the variable has
// an actual partition associated with the partition of the template.
// Use the CHGDFN template DEFINE... command to define new partitions
// within the template, and the CHGDFN variable ADD... command to
// add new partitions to the variable. Alternatively, the
// PARTWRITEERR can be set to false, in which case data being
// written to a non-existent partition will be silently discarded.
37108, 00000, "(XSVPART08) %a %j %j\n%1p has an AGGCOUNT, but %2p does not."
// *Cause: An attempt was made to add a partition to a partitioned variable.
// Either the partition was defined WITH AGGCOUNT and the partitioned
// variable was not, or the partitioned variable was defined
// WITH AGGCOUNT and the partition was not.
// *Action: Use CHGDFN ADD AGGCOUNT or CHGDFN DROP AGGCOUNT to either
// add or remove an AGGCOUNT from either the partition or the
// partitioned variable.
37109, 00000, "(XSVPART09) %a %j %j\nPartition %1p and its parent variable %2p cannot both be specified."
// *Cause: Partition and its parent partition were operated upon together.
// *Action: Remove the partition from the object list.
// ---- 37111 - 37120 are reserved for xsldolap ----
37111, 00000, "Unable to load the OLAP API sharable library: (%s)"
// *Cause: This happens if:
// (1) the OLAP API sharable library is missing.
// (2) a sharable library upon which the OLAP API sharable library
// depends is missing.
// (3) the OLAP API sharable library is the wrong version.
// *Action: Ensure that Oracle is properly installed with the OLAP option.
// If the RDBMS has been patched, review the patch log for errors.
// If the problem persists, report it to Oracle Customer Support.
37113, 00000, "OLAP API initialization error: (%s)"
// *Cause: OLAP API initialization failed.
// *Action: Ensure that Oracle is properly installed with the OLAP option.
// If the RDBMS has been patched, review the patch log for errors.
// If the problem persists, report it to Oracle Customer Support.
37114, 00000, "OLAP API bootstrap error: (%s)"
// *Cause: OLAP API bootstrapping failed.
// *Action: Ensure that Oracle is properly installed with the OLAP option.
// If the RDBMS has been patched, review the patch log for errors.
// If the problem persists, report it to Oracle Customer Support.
37115, 00000, "New OLAP API history is not allowed"
// *Cause: If there are active OLAP API sessions, it is not allowed to
// start a new OLAP API history by setting _olapi_history_retention
// parameter to true.
// *Action: Wait until all active OLAP API sessions terminate before
// resetting _olapi_history_retention parameter to true.
37116, 00000, "OLAP API table function error: (%s)"
// *Cause: OLAP API table function failed.
// *Action: Ensure that Oracle is properly installed with the OLAP option.
// If the RDBMS has been patched, review the patch log for errors.
// If the problem persists, report it to Oracle Customer Support.
37117, 00000, "olapi history retention has been disabled"
// *Cause: Under certain circumstances, for example, when the database is
// read only, olapi history retention is not possible because
// it requires updating persistent tables from time to time.
// If olapi history retention has been disabled, setting
// _olapi_history_retention parameter to true has no effect.
// *Action: Ensure that Oracle is properly installed with the OLAP option.
// If the RDBMS has been patched, review the patch log for errors.
// If the problem persists, report it to Oracle Customer Support.
37118, 00000, "The OLAP API library was not preloaded."
// Cause: In shared-server mode, the OLAP API library should be loaded
// during process initialization to ensure that the C++ virtual table
// addresses are identical in all shared-server processes. The
// OLAP API session was executing in a process in which the library
// had not been loaded.
// Action: Set option _XSOLAPI_LOAD_AT_PROCESS_START to SHARED_SERVER or
// ALWAYS, restart the instance, and try again.
37119, 00000, "Incompatible OLAP API library load address"
// Cause: The OLAP API session was executing in a process in which the
// OLAP API sharable library was loaded which was at a different
// address than the process in which the OLAP API session originated.
// Action: Set option _XSOLAPI_LOAD_AT_PROCESS_START to ALWAYS, restart
// the instance, and try again.
37120, 00000, "expression string is null"
// Cause: expression parser received a null string for syntax analysis.
// Action: Prepare a non-null and well-formed MDX query string
// and try again.
37121, 00000, "AW Spreadsheet invalidated"
// *Cause: While this cursor was open, a command was issued that changed
// the underlying data to become inconsistent.
// *Action: Perform the query again, avoid performing dimension maintenance
// and cache clears during spreadsheet processing.
37122, 00000, "AW Session cache disabled"
// *Cause: A SQL Spreadsheet was attempted while the AW Session cache was
// disabled.
// *Action: Enable the session cache and perform the query again.
37123, 00000, "(XSCCOMP17) %a %j %v %v\nCan not AGGREGATE %1p(partition %2p) because it depends on unaggregated compressed partition %3p."
// *Cause: attempted to use a feature not supported by CC's in the current AW format
// *Action: Remove the unsupported feature from the aggmap, or upgrade the AW
37124, 00000, "(XSCCOMP16) %a %s %s %s\nCOMPRESSED COMPOSITES with %1p are not supported in analytic workspace %2p because it has not been upgraded to version %3p."
// *Cause: attempted to use a feature not supported by CC's in the current AW format
// *Action: Remove the unsupported feature from the aggmap, or upgrade the AW
37125, 00000, "(XSCCOMP00) Invalid use of a COMPRESSED COMPOSITE."
// *Document: NO
// *Cause: Generic error
// *Action:
37126, 00000, "(XSCCOMP01) The COMPRESSED COMPOSITE %j can only be used as a base of a single variable."
// *Cause: The user attempted to DEFINE a variable dimensioned by a
// COMPRESSED COMPOSITE, but that COMPRESSED COMPOSITE is already
// being used by another VARIABLE.
// *Action: Create a second COMPRESSED COMPOSITE for the second VARIABLE
// or add a measure dimension to the first variable.
37127, 00000, "(XSCCOMP02) The COMPRESSED COMPOSITE %j must be last in the dimension list."
// *Cause: The user attempted to DEFINE a variable dimensioned by a
// COMPRESSED COMPOSITE, but gave a slower varying dimension in
// the dimension list.
// *Action: Put the COMPRESSED COMPOSITE last in the dimension list
// when defining the VARIABLE.
37128, 00000, "(XSCCOMP20) %a %j %j\nThe partition template %1p has already used the COMPRESSED COMPOSITE %2p."
// *Cause: The COMPRESSED COMPOSITE specified for either a variable or
// partition template is already in use in another partition template.
// *Action: Define a different COMPRESSED COMPOSITE.
37129, 00000, "(XSCCOMP04) %a %j %j\nCannot aggregate over COMPRESSED COMPOSITE %1p using AGGMAP %2p. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE."
// *Cause: The AGGMAP was defined with a MODEL statement after a
// RELATION statement over a base of the COMPRESSED COMPOSITE.
// *Action: Change the AGGMAP so that the MODEL statements
// appear before the RELATION statements.
37130, 00000, "(XSCCOMP05) %a %j %j %j\nCannot aggregate over COMPRESSED COMPOSITE %1p using AGGMAP %2p because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base %3p."
// *Cause: A PRECOMPUTE clause was specified in the AGGMAP for a
// RELATION over a base of a COMPRESSED COMPOSITE, but AGGINDEX
// was ON
// *Action: Remove the PRECOMPUTE clause from the AGGMAP, or add AGGINDEX OFF
37131, 00000, "(XSCCOMP06) %a %j %j %s\nCannot aggregate over COMPRESSED COMPOSITE %1p using AGGMAP %2p because the OPERATOR %3p is not supported for bases of a COMPRESSED COMPOSITE."
// *Cause: The user specified an aggregation OPERATOR that is not
// supported by COMPRESSED COMPOSITES.
// *Action: Use a MODEL for the calculation, or use an uncompressed
// COMPOSITE.
37132, 00000, "(XSCCOMP07) Incremental aggregation over the dense DIMENSION %j is not supported when aggregating a VARIABLE dimensioned by a COMPRESSED COMPOSITE."
// *Cause: The status of the specified dimension did not include all
// detail cells.
// *Action: Add all detail cells to the status of the dimension and
// reissue the AGGREGATE command.
37133, 00000, "(XSCCOMP08) You cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR AGGREGATES command to reenable write access."
// *Cause: The user attempted to store a value into to a variable
// dimensioned by a compressed composite, and the variable
// had previously been precomputed using the AGGREGATE
// command. Once the AGGREGATE command is run on a
// variable dimensioned by a compressed composite, it
// becomes read-only until the computed values are removed
// with the CLEAR command.
// *Action: Run the CLEAR AGGREGATES command to remove the computed
// values from the variable and then rerun the failed
// operation. Note that CLEAR AGGREGATES will remove all
// the data computed during the last AGGREGATE command on
// this variable.
37134, 00000, "(XSCCOMP09) You cannot add new values to %j because it includes positions for precomputed aggregate values."
// *Cause: The user attempted to create a new position in a compressed
// composite, either directly (using MAINTAIN MERGE or
// MAINTAIN ADD) or by storing a value into the variable
// dimensioned by the compressed composite. This is not
// allowed when the variable has been precomputed using
// the AGGREGATE command. Once the AGGREGATE command is
// run on a variable dimensioned by a compressed composite,
// the compressed composite becomes read-only until
// the computed values are removed with the CLEAR command.
// *Action: Run the CLEAR AGGREGATES command to remove the computed
// values from the variable and then rerun the failed
// operation. Note that CLEAR AGGREGATES will remove all
// the data computed during the last AGGREGATE command on
// this variable.
37135, 00000, "(XSCCOMP19) %a %j\nThe COMPRESSED COMPOSITE %1p in the current defined partition template should be unique or global."
// *Cause: The COMPRESSED COMPOSITE was neither unique nor global.
// Unique means each subpartition should have different
// COMPRESSED COMPOSITEs;
// Global means all subpartitions should use the same COMPRESSED
// COMPOSITE if they use any COMPRESSED COMPOSITE.
// *Action: Redefine the partition template.
37136, 00000, "(XSCCOMP11) %a %j %j\nCannot ROLLUP dimension %1p which is a base of COMPRESSED COMPOSITE %2p, use AGGREGATE instead."
// *Cause: The user ran ROLLUP on a variable dimensioned by a
// COMPRESSED COMPOSITE.
// *Action: Instead of using ROLLUP, generate an aggmap and use AGGREGATE
37137, 00000, "(XSCCOMP12) %a %j\nYou cannot CHGDFN %1p because it is a COMPRESSED COMPOSITE."
// *Cause: The user tried to CHGDFN a compressed composite
// *Action: If the change is desired then delete the old composite and
// create a new one.
37138, 00000, "(XSCCOMP13) You cannot delete values from %j because it is an aggregated COMPRESSED COMPOSITE."
// *Cause: The user tried to MAINTAIN DELETE from an aggregated
// COMPRESSED COMPOSITE.
// *Action: In order to perform this sort of maintenance the composite
// must first be cleared. This can be done by running the
// CLEAR AGGREGATES command on the variable dimensioning the
// composite. Note that this will remove all data computed during
// the last AGGREGATE command.
37139, 00000, "(XSCCOMP14) %a %j %j\nCannot AGGREGATE %1p using AGGMAP %2p because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause."
// *Cause: The user tried to AGGREGATE a variable dimensioned by
// a COMPRESSED COMPOSITE with an AGGMAP that included a PROTECT
// clause.
// *Action: Modify the aggmap or create a new aggmap that does not
// include a PROTECT clause and reaggregate.
37140, 00000, "(XSCCOMP15) %a %j %j\nCannot AGGREGATE partitioned variable %1p using AGGMAP %2p because you cannot use the base of a COMPRESSED COMPOSITE as a partition dimension."
// *Cause: The user tried to run aggregate on a partitioned variable with
// a partition dimension that is a base of a COMPRESSED COMPOSITE.
// *Action: Repartition the data, drop the partition dimension from the
// aggmap, or don't use COMPRESSED COMPOSITES.
37141, 00000, "(XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure."
// *Cause: The schema and analytic workspace name for the MDQUERY cursor
// declaration were incorrectly specified.
// *Action: Specify the schema and awname as a host variable name preceded
// by a colon, or as a text literal string of the form 'SCHEMA.AWNAME'
// or '*.*' (quotes optional).
37142, 00000, "(XSSQLMDQ02) Invalid host variable data type for MDQUERY procedure: %s expected."
// *Cause: The user specified a host variable that was not of the correct type.
// *Action: Choose a different host variable.
37143, 00000, "(XSSQLMDQ03) %s is not a valid analytic workspace name."
// *Cause: The user specified an analytic workspace name not qualified by a schema name, or one or both components of the name exceed the maximum length
// *Action: Specify a schema-qualified analytic workspace name with components
// no longer than 30 characters long.
37144, 00000, "(MDQUERY01) %t is not a valid metadata object type for MDQUERY."
// *Cause: The user specified an unrecognized first argument to MDQUERY
// *Action: Specify a recognized object type (CUBE or DIMENSION)
37145, 00000, "(XSTTS_PLAT) Cannot transport analytic workspace across platforms."
// *Cause: The user attempted to transport a tablespace containing an
// analytic workspace from one platform to another.
// *Action: Use export/import to move an analytic workspace across platforms.
// ---- More error continue from 37140 -------
37146, 00000, "(XSCCOMP18) %a %j %j\nThe variable %1p is already dimensioned by the COMPRESSED COMPOSITE %2p."
// *Cause: An attempt was made to define the partition template dimensioned by
// the COMPRESSED COMPOSITE which had dimensioned the variable.
// *Action: Define the second COMPRESSED COMPOSITE.
37147, 00000, "(XSCCOMP21) %a %j %j\nThe variable %1p must be in the current operation group of the COMPRESSED COMPOSITE %2p."
// *Cause: The variable dimensioned by the COMPRESSED COMPOSITE was not in
// the object list of the current operation group. For AGGREGATE,
// all variables dimensioned by the same COMPRESSED COMPOSITE also
// must use the same aggmap
// *Action: Add the variable into the object list of the current operation
// group.
37148, 00000, "(XSCCOMP22) %a %j \n%1p is an aggregated COMPRESSED COMPOSITE."
// *Cause: Defined the variable or partition template with the aggregated
// COMPRESSED COMPOSITE.
// *Action: Clear the COMPRESSED COMPOSITE or use a new COMPRESSED COMPOSITE
37149, 00000, "(XSCCOMP23) %a %j\nIndividual partitions of the variable dimensiond by %1p cannot be aggregated separately."
// *Cause: An attempt was made to aggregate partitions of a variable
// dimensioned by a global COMPRESSED COMPOSITE partition template.
// *Action: Aggregate the partitioned variable dimensioned by the global
// COMPRESSED COMPOSITE.
// ---- 37150 - 37170 are reserved for xsldolap ----
37150, 00000, "line %s, column %s, %s"
// Cause: expression syntax error was found in expression query string.
// Action: Check the error message details and make the corrections.
37151, 00000, "expression parser initialization error"
// Cause: expression parser initialization failed
// Action: Please report this to Oracle Support Services.
37152, 00000, "MDX query error: (%s)"
// Cause: An exception occurred while MDX query was processed.
// Action: Check the error message details and try again.
37153, 00000, "unknown exception caught: (case %s)"
// Cause: An unknown exception was caught while MDX query was processed.
// Action: Please report it to Oracle Support Services.
37154, 00000, "OLAP API initialization error: (case %s)"
// Cause: OLAP API initialization failed.
// Action: Ensure that Oracle is properly installed with the OLAP option.
// If the RDBMS has been patched, review the patch log for errors.
// If the problem persists, report it to Oracle Support Services.
37155, 00000, "OLAP API bootstrap error: (case %s)"
// Cause: OLAP API bootstraping failed.
// Action: Ensure that Oracle is properly installed with the OLAP option.
// If the RDBMS has been patched, review the patch log for errors.
// If the problem persists, report it to Oracle Support Services.
37156, 00000, "(%s)"
// Cause: unknown
// Action: Check the error message details.
37157, 00000, "expression syntax error was found in expression string but error text was missing"
// Cause: This happened because the message file was missing.
// Action: Make sure that the message file xsous.msb is located in
// $ORACLE_HOME/olap/mesg and rerun your expression query.
37158, 00000, "Bad clob or varray IN-args: (case %s)"
// Cause: When in clob or varray mode, the PL/SQL mappings of OLAP API's
// IDL interface methods were executed blindly with null clob/varray
// or non-null clob/varray containing garbages.
// Action: Do not blindly execute them as doing so does not make sense
// unless you understand how OLAP API works internally.
37159, 00000, "C++ virtual table addresses become invalid due to session migration in shared server mode."
// Cause: Exec-shield is the primary reason that caused this error in
// shared server mode. When exec-shield is turned on, there is
// no way to ensure that the C++ virtual table addresses are
// identical in all shared-server processes.
// Action: Set option _XSOLAPI_FIX_VPTRS to TRUE, restart the instance,
// and try again.
37160, 00000, "OLAP object does not exist"
// *Cause: The specified OLAP object did not exist.
// *Action: Use an existing OLAP object instead.
37161, 00000, "invalid privilege specified for OLAP object"
// *Cause: An attempt was made to grant or revoke an invalid privilege on
// an OLAP object.
// *Action: Specify a valid privilege.
37162, 00000, "OLAP error"
// *Cause: An exception was raised by OLAP code.
// *Action: Check error messages and correct any reported problems.
37163, 00000, "cannot delete or truncate AW with dependent CUBES or CUBE DIMENSIONS"
// *Cause: User attempted to delete or truncate an AW which currently
// has a CUBE or CUBE DIMENSION defined over it
// *Action: Drop the corresponding CUBE or CUBE DIMENSION before deleting the AW
37164, 00000, "The current SQL statement does not support this OLAP object"
// *Cause: The OLAP object is not supported in the current SQL statement.
// *Action: Use a valid SQL command on the OLAP object.
37165, 00000, "cannot use EIF IMPORT into a non-empty Analytic Workspace (%s.%s)"
// *Cause: An attempt was made to use EIF IMPORT to populate a non-empty Analytic Workspace.
// *Action: Ensure that the target Analytic Workspace is empty before populating it with EIF IMPORT.
37166, 00000, "(XSOQ_BAD_OBJ) %a %s %s \nOLAP object \"%1p.%2p\" does not exist"
// *Cause: The specified OLAP object did not exist.
// *Action: Use an existing OLAP object instead.
37167, 00000, "(XSOQ_BAD_SUBOBJ) %a %s %s %s \nOLAP object \"%1p.%2p.%3p\" does not exist"
// *Cause: The specified OLAP object did not exist.
// *Action: Use an existing OLAP object instead.
37168, 00000, "(XSOBJORG_UNSUPP_OBJ) %a %s %s \nunsupported OLAP object \"%1p.%2p\" for OBJORG function"
// *Cause: The specified OLAP object was of a type that is not supported by the OBJORG function.
// *Action: Specify an OLAP object of a type that the OBJORG function supports.
37169, 00000, "(XSOBJORG_UNSUPP_SUBOBJ) %a %s %s %s \nunsupported OLAP object \"%1p.%2p.%3p\" for OBJORG function"
// *Cause: The specified OLAP object was of a type that is not supported by the OBJORG function.
// *Action: Specify an OLAP object of a type that the OBJORG function supports.
37170, 00000, "(XSOBJORG_NA) The top-level object name argument to the OBJORG function cannot be NA."
// *Cause: You passed NA as the second argument to the OBJORG function.
// *Action: Pass the name of the top-level object instead.
/// Errors 37171-37199 reserved for sparsity advisor
37171, 0, "dimension sources not specified"
// *Cause: The user passed an empty or null collection to
// DBMS_AW.ADVISE_SPARSITY
// *Action: Specify a valid set of dimension sources
37172, 0, "illegal dimension type"
// *Cause: The user specified an invalid member of the DIMTYPE field
// in the dimension sources argument
// *Action: Specify one of the valid enumerated values in DBMS_AW
37173, 0, "null dimension source data"
// *Cause: The user specified NULL for one of the members of the
// dimension sources argument
// *Action: Specify a value
37174, 0, "source SQL must be a SELECT statement"
// *Cause: The user specified an INSERT, UPDATE, DELETE or other type of
// SQL statement
// *Action: Specify a SQL SELECT statement instead
37175, 0, "column %s is not a column of source data"
// *Cause: A dimension column was specified which did not exist
// in the input data
// *Action: Specify one of the columns of the input data
37176, 0, "argument %s is not valid for the sparsity advisor"
// *Cause: An invalid argument was passed to the advisor
// *Action: Specify a TABLE, VIEW or SELECT statement instead
37177, 0, "column %s does not have any leaf values"
// *Cause: The specified dimension column or fact table did not contain any
// leaf values
// *Action: Populate the source data
37178, 0, "column %s has no values"
// *Cause: The specified dimension column did not contain any
// values
// *Action: Populate the source data
37179, 0, "expected at least one column for dimension %s, got %s"
// *Cause: Not enough columns were specified for the dimension
// *Action: Specify more source columns, or change the dimension to
// another type
37180, 0, "expected exactly one column for dimension %s, got %s"
// *Cause: Expected a single source column for the dimension. Either
// none or more than one was specified.
// *Action: Specify exactly one column, or change the dimension to
// another type
37181, 0, "expected exactly %s columns for dimension %s, got %s"
// *Cause: Expected a certain number of source columns for the dimension.
// Either none or the wrong number of columns was specified.
// *Action: Specify the right number of columns, or change the dimension to
// another type
37182, 0, "you may only specify one dimension to partition"
// *Cause: The user passed a DIMENSION_SOURCE_T to ADVISE_SPARSITY
// which specified partitioning on more than one dimension
// *Action: Remove all but one of the partitioning requests
37183, 0, "illegal value %s for PARTBY"
// *Cause: The user passed a value other than PARTBY_DEFAULT, PARTBY_NONE
// or PARTBY_FORCE to DBMS_AW.ADVISE_SPARSITY
// *Acton: Supply a legal value instead
37184, 0, "illegal value %s for ADVMODE"
// *Cause: The user passed a value other than ADVICE_DEFAULT, ADVICE_FAST
// or ADVICE_FULL to DBMS_AW.ADVISE_SPARSITY
// *Acton: Supply a legal value instead
37185, 0, "length of %s (%s) exceeds maximum (%s)"
// *Cause: The user passed an excessively long value
// *Action: Specify a legal value
37186, 0, "null child value for parent (%s) found in parent-child hierarchy"
// *Cause: While reading values for a parent-child hierarchy, a NULL child
// value was found for a non-NULL parent
// *Action: Correct the source table or SQL to return value parent and
// child pairs.
37187, 0, "null parent and child pair found in parent-child hierarchy"
// *Cause: While reading values for a parent-child hierarchy, a row was
// retrieved which had both null child and parent values.
// *Action: Correct the source table or SQL to return value parent and
// child pairs.
37188, 0, "unexpected null result while querying %s"
// *Cause: While querying the input fact table, the sparsity advisor
// unexpectedly got no results, possibly due to changes
// being made during operation.
// *Action: Retry the operation ensuring that the data is not changed
// while the sparsity advisor is running
/// Errors from 37200 - 37399 are reserved for events
/// Errors from 37400 - 37499 are reserved for CUBE ORGANIZED tables
/// and AW MVs
37400, 00000, "analytic workspace does not exist"
// *Cause: The user attempted to create an OLAP MV or Table on an
// AW that does not exist.
// *Action: Specify a valid AW in the ORGANIZATION CUBE clause
37401, 00000, "you may not perform this operation on a system analytic workspace"
// *Cause: The user attempted to create a CUBE MV or Table on a
// system-created AW.
// *Action: Specify a valid AW in the ORGANIZATION CUBE clause
37402, 00000, "analytic workspace object does not exist"
// *Cause: The user attempted to create a CUBE MV or Table mapping
// to an object that does not exist in the AW.
// *Action: Specify a valid AW object name in the ORGANIZATION CUBE
// clause.
37403, 00000, "invalid analytic workspace object type"
// *Cause: The user attempted to create a CUBE MV or Table mapping
// to an object that is not the correct type.
// *Action: Specify a valid AW object name in the ORGANIZATION CUBE
// clause.
37404, 00000, "Create table as select disallowed for CUBE ORGANIZED tables"
// *Cause: User attempted to create a CUBE ORGANIZED table by doing a
// create table as select.
// *Action: Do a create table followed by an insert as select
37405, 00000, "unknown ORGANIZATION CUBE keyword"
// *Cause: An unknown keyword was encountered while parsing the
// ORGANIZATION CUBE clause
// *Action: Correct the ORGANIZATION CUBE syntax
37406, 00000, "invalid option for a CUBE ORGANIZED table"
// *Cause: An attempt to specify one or more options for
// a CUBE ORGANIZED table such as:
// [NO]CACHE, NO LOGGING, CLUSTER, (NO)COMPRESS
// *Action: Remove the illegal option(s)
37407, 00000, "invalid column type for a CUBE ORGANIZED table"
// *Cause: A illegal column type is specified in a CUBE ORGANIZED table.
// *Action: Do not use column types such as LONG, LOB
37408, 00000, "Truncate table disallowed for CUBE ORGANIZED tables"
// *Cause: User attempted to perform a TRUNCATE operation on a
// CUBE ORGANIZED table
// *Action: Remove data with DELETE or drop the table and recreate it
37409, 00000, "cannot delete or truncate AW used by CUBE ORGANIZED table"
// *Cause: User attempted to delete or truncate an AW which currently
// has a CUBE ORGANIZED table or MV defined over it
// *Action: Drop the corresponding table or MV before deleting the AW
37410, 00000, "cannot delete or modify AW object referenced by CUBE ORGANIZED table"
// *Cause: User attempted to delete, chgdfn, or otherwise modify an object
// referenced by a CUBE ORGANIZED table or MV
// *Action: Drop the corresponding table or MV before manipulating the object
37411, 00000, "invalid object type"
// *Cause: User referenced an invalid object type
// *Action: Use an appropriate object
37412, 00000, "column not mapped by ORGANIZATION CUBE clause"
// *Cause: Not all columns in the table or MV definition were mapped in the
// ORGANIZATION CUBE clause
// *Action: Make sure that all columns are mapped
37413, 00000, "column referenced multiple times in ORGANIZATION CUBE clause"
// *Cause: The same column name was referenced multiple times inside of
// the ORGANIZATION CUBE clause
// *Action: Supply unique mappings for each column
37414, 00000, "dimension without mapping or hierarchy in ORGANIZATION CUBE clause"
// *Cause: A dimension was listed in the ORGANIZATION CUBE clause but no
// mapping information was supplied
// *Action: Provide either a column mapping or hierarchy for the dimension
37415, 00000, "AW schema must match TABLE or MATERIALIZED VIEW schema"
// *Cause: An ORGANIZATION CUBE table or MV on top of an existing AW must
// be created in the same schema as the AW
// *Action: Create the new object in the same schema as the AW
37416, 00000, "multiple GROUPING IDs found for ORGANIZATION CUBE"
// *Cause: Multiple GROUPING IDs for the ORGANIZATION CUBE TABLE or
// MATERIALIZED VIEW
// *Action: Remove the duplicates
37417, 00000, "variable does not have an AGGCOUNT"
// *Cause: A COUNT clause was specified in the ORGANIZATION CUBE
// description for a variable that does not have an
// AGGCOUNT
// *Action: chgdfn the variable to include an AGGCOUNT
37418, 0000, "detail query cannot be derived"
// *Cause: If an ORANIZATION CUBE MV is to automatically derive its loading
// clause, then its definition query cannot contain set operators
// (eg UNION ALL), a HAVING clause, START WITH or a SQL MODEL clause.
// The definition query contains these or other unsupported syntax.
// *Action: Use an explicit ORGANIZATION CUBE clause, or simplify the
// defining query.
37419, 0000, "ORGANIZATION CUBE clause not allowed in explain mview"
// *Cause: User tries to explain mview on a CREATE MATERIALIZED VIEW statement
// that contains a ORGANIZATION CUBE clause.
// *Action: Remove the ORGANIZATION CUBE clause from the CREATE MATERIALIZED
// MATERIALIZED VIEW statement.
37420, 0000, "unsupported feature with CUBE ORGANIZED materialized view"
// *Cause: User attempts operations such as creating a mv log on an CUBE ORGANIZED
// MATERIALIZED VIEW.
// *Action: Do not do that.
37421, 00000, "specified pseudocolumn is not supported by CUBE ORGANIZED tables"
// *Cause: An unsupported pseudocolumn was referenced with a CUBE ORGANIZED
// table.
// *Action: Remove the unsupported pseudocolumn.
37422, 00000, "illegal attempt to write to a calculated column"
// *Cause: An attempt was made to write to a calculated column which
// could not be written to.
// *Action: List only the non-calculated columns in your DML command.
37423, 00000, "operation not supported on CUBE ORGANIZED tables"
// *Cause: The attempted operation was not supported with CUBE ORGANIZED tables.
// *Action: Do not attempt this operation on CUBE ORGANIZED tables.
37424, 00000, "alter materialized view (MV) on a primary cube organized MV failed to find secondary cube MV table"
// *Cause: The operation failed due to the missing secondary cube materialized view (MV) table in alter MV.
// *Action: Recreate the primary CUBE MV and make sure the secondary cube MV table is correctly created.
/// Errors 37500-37520 for informational control flow signals
/// Errors 37521-37527 for _HASHSCAN program and KV repair
37521, 00000, "(HASHSCAN00) Dimension %s contains duplicate values. Please contact Oracle OLAP Technical Support."
// *Cause: The named dimension contains duplicate values.
// *Action: Contact Technical Support for instructions.
37522, 00000, "(HASHSCAN01) You must specify the name of an existing TEXT or NTEXT dimension."
// *Cause: the _HASHSCAN program was invoked with an invalid argument
// *Action: Provide a text expression yielding the name of an existing TEXT
// dimension
37523, 00000, "(HASHSCAN02) %1 unindexed values in dimension %2."
// *Document: NO
// *Cause: Informational message from _HASHSCAN program in EXPRESS
// *Action: None
37524, 00000, "(HASHSCAN03) Dimension %1 contains %2 unindexed values and %3 duplicate values\n(Asterisks indicate indexed positions)."
// *Document: NO
// *Cause: Informational message from _HASHSCAN program in EXPRESS
// *Action: None
37525, 00000, "(HASHSCAN04) Dimension value"
// *Document: NO
// *Cause: REPORT column heading from _HASHSCAN program in EXPRESS
// *Action: None
37526, 00000, "(HASHSCAN05) Logical position(s)"
// *Document: NO
// *Cause: REPORT column heading from _HASHSCAN program in EXPRESS
// *Action: None
37527, 00000, "(XSCHGDFN01) SESSION values of dimension %s are being automatically deleted."
// *Cause: When using CHGDFN to rebuild the hash index of a TEXT or NTEXT
// dimension, SESSION values were encountered.
// *Action: Recreate the SESSION values after the CHGDFN command completes.
// Information about the deleted values has been written to the
// trace file.
37528, 00000, "(XSOBJORG_BAD_HIER) %a %s %s %s %s\ninvalid property \"%1p\" specified for hierarchy \"%2p.%3p.%4p\""
// *Cause: Either the specified hierarchy did not have an AW organization, or the specified property did not apply to hierarchies.
// *Action: Specify a property that applies to hierarchy and a dimension with an AW organization.
37530, 00000, "(XSCCLOAD01) %a %j %j\nWhen aggregating between compressed partitions the base dimensions of %1p did not match the base dimensions of %2p."
// *Cause: When aggregating a partitioned variable the dimensionality of
// any compressed partitions should be identical.
// *Action: Delete the upper partition and redefine it with a composite that
// matches the lower partition. If it is dependent on multiple
// partitions with varying sparsity you must first unify the
// the sparsity of the source partitions.
37531, 00000, "(XSCCLOAD02) When aggregating between compressed partitions the source partitions were aggregated with a different AGGMAP, or the RELATIONS have changed since the source partitions were aggregated."
// *Cause: When aggregation crosses partition boundaries within a compressed
// variable the individual partitions must all be aggregated using
// a similar aggmap over the same unaltered relations.
// *Action: Modify the aggmap for the upper partition to more exactly match
// the aggmap of the source partitions, or if the aggmap is already
// similar, re-aggregate the source partitions to pick up any
// changes to the relations.
/// 37532 - 37540 available
// HIERCHECK and HIERSHAPE function errors
37541, 00000, "Hierarchy element DIMENSION_MEMBER can aggregate into element MEMBER_ANCESTOR through multiple paths."
// *Cause: When a low level hierarchy element can reach an aggregate element
// by more than one path through the hierarchy, it is said to have multiple
// paths. The danger is that the value of the low level hierarchy element
// will have its value counted multiple times (once per path) in the total of
// the aggregate element.
// *Action: Eliminate multiple paths from the hierarchy.
37542, 00000, "DIMENSION_MEMBER makes hierarchy HIERARCHY1 unbalanced."
// *Cause: A hierarchy is balanced if: 1) All members of a level are at the
// same depth from the root of the hierarchy and 2) All the members in
// different levels are at different depths from the root of the hierarchy.
// *Action: Fix the hierarchy so that it is balanced. This is often done by
// looking for nulls in the middle levels of a hierarchy.
37543, 00000, "Hierarchy member DIMENSION_MEMBER is inconsistent across HIERARCHY1 and HIERARCHY2."
// *Cause: Two hierarchies are inconsistent when members that appear in both
// hierarchies have different ultimate leaves.
// *Action: This problem is usually resolved by defining a new dimension member
// for the secondary hierarchy, or fixing the hierarchy table so that the
// definitions of the member match across hierarchies.
37544, 00000, "Dimension members DIMENSION_MEMBER and MEMBER_ANCESTOR make this dimension star inconsistent."
// *Cause: A dimension is "star consistent" when it can be represented in a
// star schema table. This requires that a hierarchy level map to a single
// underlying column. If a level is shared across one or more hierarchies,
// it must have the same set of members in each hierarchy (to share a
// column).
// *Action: Create a different level for the secondary hierarchy. This
// provides a separate level column for each hierarchy.
37545, 00000, "DIMENSION_MEMBER is part of a hierarchy loop."
// *Cause: A hierarchy has loops when the ancestor of a dimension member uses
// that member as its parent. Note that some loops are created across
// hierarchies. For example, in hierarchy 1, dimension member A is the parent
// of B, B is the parent of C and in hierarchy 2, C is that parent of A forms
// a hierarchy loop.
// *Action: Change the hierarchies so that the loop is eliminated or move the
// problem hierarchy to a different dimension.
37546, 00000, "(XSHIERSP00) Levelorder valueset is empty."
// *Cause: An empty levelorder valueset was specified for the HIERSHAPE function.
// *Action: specify a non-empty levelorder valueset.
37547, 00000, "(XSHIERSP01) DIMENSION_MEMBER has no level associated with it."
// *Cause: DIMENSION_MEMBER did not have an associated level. Level based
// hierarchies must have a level for every dimension member.
// *Action: Add level assignments for all dimension members in the hierarchy.
37548, 00000, "(XSHIERSP02) DIMENSION_MEMBER is not specified as a member of HIERARCHY1."
// *Cause: When a dimension member is part of a hierarchy, it appears in the
// INHIER valueset associated with the hierarchy. This dimension member is
// missing from this value set and thus should not be part of this hierarchy.
// *Action: Alter the hierarchy's membership to include the specified
// dimension member.
37549, 00000, "(XSHIERSP03) The level of DIMENSION_MEMBER is not lower than the level of MEMBER_ANCESTOR."
// *Cause: A dimension member has a parent that is lower or on the same level
// as this member according to the levelorder valueset.
// *Action: Fix the child and/or parent levels so that every dimension member
// has a parent whose level is higher than the level of this member.
37550, 00000, "(XSHIERSP04) The level of MEMBER_ANCESTOR is not one level above DIMENSION_MEMBER."
// *Cause: A dimension member has a parent that is not one level above the
// level of this member according to the levelorder valueset.
// *Action: Fix the child and/or parent levels so that every dimension member
// has a parent whose level is one level above the level of this member
// according to the levelorder.
37551, 00000, "(XSHIERSP05) Leaf value DIMENSION_MEMBER is not on the same level as the rest of leaf dimension values."
// *Cause: The detail or leaf values of this hierarchy must all have the same
// level. This member is on a different level than most of the leaf values.
// *Action: Fix DIMENSION_MEMBER's level so that all leaves are on the same
// level.
37552, 00000, "(XSHIERSP06) DIMENSION_MEMBER is associated with a level not found in the levelorder valueset."
// *Cause: DIMENSION_MEMBER must have an associated level that is found in
// the levelorder valueset so that we can figure out DIMENSION_MEMBER's
// level depth.
// *Action: Fix DIMENSION_MEMBER's associated level.
37553, 00000, "%a %v %v %n %j\nA cycle between %1p and %2p has been detected in relation %3p over %4p."
// *Cause: A relation was used that had loops in it.
// *Action: Correct the relation so that it does not contain loops.
37554, 00000, "%a %v %v %n\nA cycle between %1p and %2p has been detected in relation %3p."
// *Cause: A relation was used that had loops in it.
// *Action: Correct the relation so that it does not contain loops.
/// 37560 - 37579 reserved for OLAP logging errors
37560, 00000, "lob locator invalid for specified log target"
// *Cause: A lob locator was passed as a target to DBMS_CUBE_LOG.ENABLE, but
// the log_target was not DBMS_CUBE_LOG.TARGET_LOB
// *Action: Specify LOG_TARGET_LOB as the log_target, or specify a valid
// location instead
37561, 00000, "unknown logging type"
// *Cause: An invalid log_type was specified
// *Action: Specify a valid logging type from the DBMS_CUBE_LOG package
37562, 00000, "unknown logging target"
// *Cause: An invalid log_target was specified
// *Action: Specify a valid logging target from the DBMS_CUBE_LOG package
37563, 00000, "invalid log verbosity"
// *Cause: An invalid log_verbosity was specified
// *Action: Specify a valid logging verbosity from the DBMS_CUBE_LOG package
37564, 00000, "unknown log table version"
// *Cause: Could not determine the version of the specified logging table
// *Action: Specify a valid target table, or use DBMS_CUBE_LOG.TABLE_CREATE to
// create one
37565, 00000, "invalid parameter for specified log type"
// *Cause: The log_type specified does not support the specified parameter,
// for instance, DBMS_CUBE_LOG.MAX_ERRORS is not valid for
/ DBMS_CUBE_LOG.TYPE_OPERATIONS
// *Action: Specify a valid log_type / log_param combination
37566, 00000, "invalid log location"
// *Cause: The specified log location is in an invalid format. For file
// targets it must be of the form 'directory_alias/filename'
// *Action: Specify a valid log location
37567, 00000, "log location not specified"
// *Cause: The log location was not specified for a log target which
// requires one
// *Action: Specify a valid log location
37568, 00000, "invalid log parameter"
// *Cause: An invalid log_param was passed to dbms_cube_log.set_parameter
// or get_parameter
// *Action: Specify a valid parameter
37569, 00000, "invalid log parameter value"
// *Cause: An invalid value was passed to dbms_cube_log.set_parameter
// *Action: Specify a valid value
37570, 00000, "invalid log specification"
// *Cause: An invalid logging specification was supplied to
// DBMS_CUBE_LOG.SET_LOG_SPEC
// *Action: Correct the syntax being supplied
37571, 00000, "invalid SQL ID"
// *Cause: Either the SQL ID supplied was invalid or
// no associated logging information was captured.
// *Action: Specify a valid SQL ID.
37572, 00000, "invalid ID"
// *Cause: An invalid ID was supplied for the given
// SQL ID.
// *Action: Specify a valid ID for that SQL ID.
37573, 00000, "no limits logged"
// *Cause: There were no corresponding OLAP filters to the
// supplied information.
// *Action: Specify predicates on the original query
// or specify a new SQL ID or ID.
37574, 00000, "error logging to table \"%s.%s\""
// *Cause: An error occurerd attempting to write log records to the named
// table.
// *Action: Make sure the user has permissions to write to the table.
37575, 00000, "Invalid cube operations log component, \"%s\"."
// *Cause: Invalid cube operations log component value.
// *Action: Provide a valid cube operations log component or accept
// the default value by leaving the parameter unspecified.
37576, 00000, "Invalid cube operations log handle id."
// *Cause: An invalid cube operations log handle id was specified. No oplog
// handle found for oplogHandleId parameter.
// *Action: Provide a valid cube operations log handle id for oplogHandleId.
// Use DBMS_CUBE_LOG.START_OPLOG to get a valid handle id.
37577, 00000, "Invalid cube operations log message name."
// *Cause: Cube operations log message name value is NULL.
// *Action: Provide a valid non-null cube operations log message name.
37578, 00000, "Invalid cube operations log operation value."
// *Cause: Cube operation log operations value is NULL.
// *Action: Provide a valid non-null cube operations log operation value.
37580, 0000, "The EXPRESS AW does not exist."
// *Cause: The EXPRESS AW does not exist.
// Action: Ensure that Oracle is properly installed with the OLAP option.
// If the RDBMS has been patched, review the patch log for errors.
// If the problem persists, report it to Oracle Support Services.
37581, 0000, "The EXPRESS AW has not been properly installed."
// *Cause: The EXPRESS AW has not been properly installed.
// Action: Ensure that Oracle is properly installed with the OLAP option.
// If the RDBMS has been patched, review the patch log for errors.
// If the problem persists, report it to Oracle Support Services.
37582, 0000, "The EXPRESS AW version %s is different than the Oracle version %s."
// *Cause: The EXPRESS AW version does not match the current Oracle version.
// Action: Ensure that Oracle is properly installed with the OLAP option.
// If the RDBMS has been patched, review the patch log for errors.
// If the problem persists, report it to Oracle Support Services.
/// Errors from 37600 to 37799 are "bad" errors which can not be
/// caught by DML
37600, 00000, "(XSPGERRPERMDETACH) Ran out of tablespace storage while updating analytic workspace %s "
// *Cause: Ran out of lob segment space.
// *Action: Increase tablespace storage. AW may need to be detached.
37601, 00000, "(XSPGERRTEMP) Ran out of temporary storage while writing to analytic workspace with ID=%d. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace."
// *Cause: Ran out of temporary tablespace storage.
// *Action: Increase the amount of temporary tablespace storage.
37602, 00000, "(XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace %s. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace."
// *Cause: Ran out of temporary tablespace storage.
// *Action: Increase the amount of temporary tablespace storage.
37603, 00000, "(XSPGERRTEMPSYSTEM) Ran out of temporary storage while writing to a system temporary analytic workspace. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace."
// *Cause: Ran out of temporary tablespace storage.
// *Action: Increase the amount of temporary tablespace storage.
37604, 00000, "(XSPGERRPQUPD) Parallel updating analytic workspace %s failed"
// *Cause: Unexpected error occurred to parallel update servers.
// *Action: Check the error underneath and act accordingly. AW may need to be detached.
37605, 00000, "error during OLAP AW UPDATE"
// *Cause: An error occurred during the UPDATE process
// *Action: Refer to the next error in the error stack
/// THE FOLLOWING MESSAGES ARE OPERATING SYSTEM DEPENDENT AND
/// SHOULD MOSTLY BE REPLACED OR REMOVED FOR 9i2. PLEASE ADD NEW
/// MESSAGES ABOVE THE LINE.
37996,0, "(SNSYN950) The format of the SYSINFO function is:\n SYSINFO(option)"
// *Cause:
// *Action:
37999,0, "Serious OLAP error: %s. Please contact Oracle Technical Support."
// *Cause: Something unexpected occurred in the OLAP system
// *Action: Contact Oracle technical support
/// STOP!!!! DON'T ADD NEW MESSAGES HERE, ADD THEM WAY BACK ABOVE THE
/// DASHED LINE
//////////// Optimizer
/ Error numbers 38001 - 38100 are reserved for Optimizer.
///////////
38001, 00000, "RBO Disable constant predicate elimination optimization"
// *Cause:
// *Action:
38002, 00000, "CBO enable restriction on type of join (NL only) for a query block with pushed predicate"
// *Cause:
// *Action:
38003, 00000, "CBO Disable column stats for the dictionary objects in recursive SQL"
// *Cause:
// *Action:
38004, 00000, "CBO (9.0.1 ONLY) Enable column stats for the dictionary objects in recursive SQL"
// *Cause:
// *Action:
38005, 00000, "CBO disable fix for bug 2251373"
// *Cause:
// *Action:
38006, 00000, "DBMS_STATS override commit threshold for (sub)partition level stats"
// *Cause:
// *Action:38007, 00000, "CBO disable merging predicates >= && <="
// *Cause:
// *Action:
38008, 00000, "CBO disable costing overhead of inlist iteration"
// *Cause:
// *Action:
38009, 00000, "CBO disable fix for bug 2109825"
// *Cause:
// *Action:
38010, 00000, "CBO disable push predicate, driven by functional index into PV"
// *Cause:
// *Action:
38011, 00000, "CBO disable truncation of bind when dealing with fixed char descend index expression"
// *Cause:
// *Action:
38012, 00000, "CBO disable normalization of b-tree index selectivity"
// *Cause:
// *Action:
38013, 00000, "CBO disable delayed ANY=>EXISTS conversion for colocated subquery of CTAS"
// *Cause:
// *Action:
38014, 00000, "CBO disable grouping pruning if star_transformation is enabled"
// *Cause:
// *Action:
38015, 00000, "CBO enable unnesting of more than one subquery based on CVM"
// *Cause:
// *Action:
38016, 00000, "CBO disable full functional index scan"
// *Cause:
// *Action:
38017, 00000, "CBO disable push of join predicate for a table with RLS"
// *Cause:
// *Action:
38018, 00000, "CBO disable full statistics load for evaluation of average row length"
// *Cause:
// *Action:
38020, 00000, "CBO disable fix for bug 2324795"
// *Cause:
// *Action:
38021, 00000, "CBO disable view merge with multi-referenced non-deterministic function"
// *Cause:
// *Action:
38022, 00000, "CBO disable Distinct Sort Elimination at subquery unnest"
// *Cause:
// *Action:
38023, 00000, "CBO disable fix for bug 2853398"
// *Cause:
// *Action:
38025, 00000, "CBO enable generation of excessive semijoin subqueries"
// *Cause:
// *Action:
38026, 00000, "CBO enable bitmap plan based on domain index, with no domain index driver"
// *Cause:
// *Action:
38027, 00000, "CBO disable evaluation column gnd using inlist gnd"
// *Cause:
// *Action:
38028, 00000, "DBMS_STATS disable small object optimization"
// *Cause:
// *Action:
38029, 00000, "object statistics are locked"
// *Cause: An attept was made to modify optimizer statistics of the object.
// *Action: Unlock statistics with the DBMS_STATS.UNLOCK_TABLE_STATS procedure
// on base table(s). Retry the operation if it is okay to update statistics.
38030, 00000, "CBO enable strongly connected preds for intersect to join"
// *Cause:
// *Action:
38031, 00000, "CBO disable the fix for bug 2663857"
// *Cause:
// *Action:
38032, 00000, "CBO disable the fix for bug 3063008"
// *Cause:
// *Action:
38033, 00000, "CBO disable costing of push join predicate in OJ view"
// *Cause:
// *Action:
38034, 00000, "CBO disable the fix for bug 2871645"
// *Cause:
// *Action:
38036, 00000, "NSO disable the fix for bug 3070157"
// *Cause:
// *Action:
38037, 00000, "CBO disable the fix for bug 3405237"
// *Cause:
// *Action:
38038, 00000, "CBO disable the fix for bug 3168961"
// *Cause:
// *Action:
38039, 00000, "CBO enable view merge/ subquery ANY=>EXISTS conversion having view(subquery) predicates in front of outer query block (connecting) predicates"
// *Cause:
// *Action:
38040, 00000, "DBMS_STATS minimum sample size in number of rows (0 = internal default)"
// *Cause:
// *Action:
38041, 00000, "DBMS_STATS auto_sample_size overrides"
// *Cause:
// *Action:
38042, 00000, "CBO disable usage of tjp when generating pruning subquery"
// *Cause:
// *Action:
38044, 00000, "CBO disable expression folding at evaluation of a predicate selectivity"
// *Cause:
// *Action:
38047, 00000, "CBO disable join back elimination of 1-row tables"
// *Cause:
// *Action:
38048, 00000, "CBO enable the fix for bug 3400412"
// *Cause:
// *Action:
38049, 00000, "CBO disable the fix for bug 3406977"
// *Cause:
// *Action:
38050, 00000, "CBO disable the fix for bug 2943173"
// *Cause:
// *Action:
38051, 00000, "CBO disable the fix for bug 3349903"
// *Cause:
// *Action:
38052, 00000, "CBO disable the fix for bug 3317309"
// *Cause:
// *Action:
38053, 00000, "DBMS_STATS override automatic sample size adjustment"
// *Cause:
// *Action:
38054, 00000, "VOP enable the fix for bug 3537765"
// *Cause:
// *Action:
38055, 00000, "CBO disable the fix for bug 3193835"
// *Cause:
// *Action:
38056, 00000, "CBO disable peeking of form func(:b) bug 3668224"
// *Cause:
// *Action:
38057, 00000, "CBO disable special numeric string normalization for bug 3567928"
// *Cause:
// *Action:
38058, 00000, "CBO disable the fix for bug 3756797"
// *Cause:
// *Action:
38060, 00000, "CBO enable the fix for bug 3517431(enable NL with view on right side)"
// *Cause:
// *Action:
38061, 00000, "CBO disable unnest of a subquery with WITH subqueries"
// *Cause:
// *Action:
38063, 00000, "CBO disable the fix for bug 3903100"
// *Cause:
// *Action:
38064, 00000, "CBO disable the fix for bug 3488546"
// *Cause:
// *Action:
38065, 00000, "CBO disable the fix for bug 3746511"
// *Cause:
// *Action:
38066, 00000, "NSO regulate unnesting, semijoin elimination for IN and EXISTS subqueries with a view"
// *Cause:
// *Action:
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0 IN subquery with no correlation => unnest with transformation3 (nsojo3in()). EXISTS subquery or correlation => unnest with possible semijoin elimination (nsojo2())
// 1 IN subquery with no correlation => unnest with transformation3 (nsojo3in()). EXISTS subquery or correlation => unnest (nsojo2()), disable semijoin elimination
// 2 disable semijoin elimination for a view, unnest with nsojo1() or nsojo2()
// 4 unnest with possible semijoin elimination (nsojo1(), nsojo2())
// any other do not unnest with nsojo1() or nsojo2()
38067, 00000, "CBO enable peeking at replaced literal in equality(inequality) predicate"
// *Cause:
// *Action:
38068, 00000, "CBO enable override of guess impact on index choice"
// *Cause:
// *Action:
38069, 00000, "CBO disable duplicate predicate elimination"
// *Cause:
// *Action:
38073, 00000, "CBO disable the fix for bug 4308414"
// *Cause:
// *Action:
38074, 00000, "CBO disable the fix for bug 4275716"
// *Cause:
// *Action:
38075, 00000, "CBO enables fix for bug 4235962"
// *Cause:
// *Action:
38076, 00000, "CBO enables fix for bug 4258835"
// *Cause:
// *Action:
38077, 00000, "CBO enables fix for bug 4488689"
// *Cause:
// *Action:
38078, 00000, "CBO disables fix for bug 4708389"
// *Cause:
// *Action:
/
38079, 00000, "SQL Diagnostic"
// *Cause:
// *Action:
//
// LEVEL ACTION
//---------------------------------------------------------------------------
// 0 No validation performed. Service disabled
// 1 Structural validation checks
// 2 Internal consistency checks
// 4 Cross-object consistency checks
// 8 Semantic validation checks
// 16 Trace validation service
38080, 00000, "SQL Diagnostic kill event"
// *Cause: internal use only
// *Action: this event should never be set externally
// *Comment: commands a foreground to commit suicide on a given feature ID
/
38087, 00000, "dbms_stats enable fix of bug 5842686"
// *Cause:
// *Action:
/
38090, 00000, "CBO dump virtual columns in EXPLAIN PLAN"
// *Cause:
// *Action:
/
38091, 00000, "CBO forces native full outer join"
// *Cause:
// *Action:
38094, 00000, "dbms_stats enable fix of bug 6934892"
// *Cause:
// *Action:
/
38098, 00000, "CBO reject various transformation even if chosen"
// *Cause:
// *Action:
// LEVEL ACTION
//---------------------------------------------------------------------------
// 1 reject OR expansion
// 2 disable bitmap option
/
38099, 00000, "disable Oracle Exadata check for table clustering and zone maps"
// *Document: NO
// *Cause:
// *Action:
/
38100, 00000, "enable tracing of DML frequency tracking"
// *Cause:
// *Action:
/
/
///////////////////// MERGE and Multi-Table MERGE
/ Error numbers 38101 - 38130 are reserved for MERGE
/////////////////////
38101, 00000, "Invalid column in the INSERT VALUES Clause: %s"
// *Cause: INSERT VALUES clause refers to the destination table columns
// *Action:
38102, 00000, "Invalid column in the INSERT WHERE Clause: %s"
// *Cause: INSERT WHERE clause refers to the destination table columns
// *Action:
38103, 00000, "Invalid column in the UPDATE SET Clause: %s"
// *Cause: UPDATE SET clause refers to the source table columns in the LHS
// *Action:
38104, 00000, "Columns referenced in the ON Clause cannot be updated: %s"
// *Cause: LHS of UPDATE SET contains the columns referenced in the ON Clause
// *Action:
38105, 00000, "Delete not yet supported when Update row-migration is possible"
// *Cause: When Update Row-Migration is possible, Delete in MERGE is not yet
// supported
// *Action:
38106, 00000, "MERGE not supported on join view or view with INSTEAD OF trigger."
// *Cause: The MERGE operation contained a join view or view with INSTEAD of
// trigger which is not supported.
// *Action: When using MERGE to modify a view, you must only specify a single
// table in the view, and the view cannot have an INSTEAD OF trigger.
/
/
/
///////////////////// SQL Plan Management
/ Error numbers 38131 - 38170 are reserved for SPM
/////////////////////
38131, 00000, "specified SQL handle %s does not exist"
// *Cause: The specified SQL handle did not exist in the repository.
// *Action: Specify correct SQL handle.
/
38132, 00000, "specified SQL ID %s does not exist"
// *Cause: The SQL statement for SQL ID did not exist in the cursor cache.
// *Action: Specify correct SQL ID.
/
38133, 00000, "invalid parameter name %s specified"
// *Cause: An invalid parameter name was specified.
// *Action: Verify the name of the parameter.
/
38134, 00000, "invalid parameter value %s specified"
// *Cause: An invalid parameter value was specified.
// *Action: Verify the parameter value.
/
38135, 00000, "invalid fixed status value specified"
// *Cause: Specified fixed status value was neither YES or NO.
// *Action: Specify either 'YES' or 'NO'.
/
38136, 00000, "invalid attribute name %s specified"
// *Cause: An invalid attribute name was specified.
// *Action: Verify the name of the attribute.
/
38137, 00000, "invalid attribute value %s specified"
// *Cause: An invalid attribute value was specified.
// *Action: Verify the attribute value.
/
38138, 00000, "plan name is missing or NULL"
// *Cause: A valid plan name was not specified.
// *Action: Specify a valid plan name.
/
38139, 00000, "concurrent DDL Error in load plans operation"
// *Cause: A concurrent DDL operation was performed during a load
// plans operation.
// *Action: Try operation again.
/
38140, 00000, "no SQL plan baselines were found"
// *Cause: No SQL plan baselines were found during pack or unpack operation.
// *Action: Specify correct selection criterion.
/
38141, 00000, "SQL plan baseline %s does not exist"
// *Cause: A SQL plan baseline name was specified that did not exist.
// *Action: Verify the name of the SQL plan baseline.
/
38142, 00000, "SQL plan baseline named %s already exists"
// *Cause: A SQL plan baseline already exists with the name specified.
// *Action: Specify a different name or drop the existing SQL plan baseline.
/
38143, 00000, "invalid enabled status value specified"
// *Cause: Specified enabled status value was neither YES or NO.
// *Action: Specify either 'YES' or 'NO'.
/
38144, 00000, "specified plan name %s does not exist"
// *Cause: The specified plan name did not exist in the repository.
// *Action: Specify correct plan name.
/
38145, 00000, "neither SQL handle nor plan name specified"
// *Cause: The SQL handle or plan name was not specified.
// The SQL handle or plan name is required.
// *Action: Specify either SQL handle or plan name or both.
/
38146, 00000, "invalid verify value specified"
// *Cause: Specified verify value was neither YES or NO.
// *Action: Specify either 'YES' or 'NO'.
/
38147, 00000, "invalid commit value specified"
// *Cause: Specified commit value was neither YES or NO.
// *Action: Specify either 'YES' or 'NO'.
/
38148, 00000, "invalid time limit specified"
// *Cause: Specified time limit value was not a positive integer.
// *Action: Specify a positive integer value.
/
38149, 00000, "There is no recommended action for object %s in task %s."
// *Cause: The advisor did not generate a recommended action for the given object and task.
// *Action: Choose a different object and retry the operation.
/
38150, 00000, "not enough room for filter length %s; %s characters remaining"
// *Cause: An auto-capture filter was too large to fit in the remaining space.
// Each filter requires a number of characters equal to the size of its
// value plus one.
// *Action: Remove other filters to make room for the new filter.
/
38151, 00000, "module name is too long"
// *Cause: The provided module name was too long.
// *Action: Provide a valid module name.
/
38152, 00000, "action name is too long"
// *Cause: The provided action name was too long.
// *Action: Provide a valid action name.
/
38153, 00000, "Software edition is incompatible with SQL plan management."
// *Cause: SQL plan management could be used only with Oracle Database Enterprise Edition.
// *Action: Ensure that Oracle is linked with the Enterprise Edition options.
/
///////////////////// SQL Management Base
/ Error numbers 38171 - 38200 are reserved for SMB
/////////////////////
38171, 00000, "Insufficient privileges for SQL management object operation"
// *Cause: A DDL operation was attempted on a SQL management object by a
// session without the proper privileges.
// *Action: Grant the appropriate privilege.
/
38172, 00000, "No SQL management object satisfies specified filters"
// *Cause: An attempt was made to perform an operation by specifying filters
// that did not target any SQL management objects.
// *Action: Try different filters.
/
38173, 00000, "Invalid value %s specified for SQL management object attribute %s"
// *Cause: An invalid attribute value was specified.
// *Action: Specify a valid attribute value.
/
/
////////////////////////////
38201, 00000, "assert if pin during flush"
// *Cause: internal use only
// *Action : enables checking for bugs in upper layers when there
// is a pin on a buffer or there are users for
// buffer and we are trying to flush the object
// associated with the buffer
//
//////////////////////////// FLASHBACK DROP and RECYCLEBIN
/ Error numbers 38301 - 38400 are reserved for flashback drop
////////////////////////////
38301, 00000, "can not perform DDL/DML over objects in Recycle Bin"
// *Cause: Tried to perform DDL or DML operation on Recycle Bin object.
// *Action: DDL or DML operations are not permitted on Recycle Bin objects.
/
38302, 00000, "invalid PURGE option"
// *Cause: Invalid purge option specified.
// *Action: Specify a valid purge option.
/
38303, 00000, "invalid option for PURGE TABLESPACE"
// *Cause: Either a token other than USER was found following the tablespace
// name or some text was found following USER <user name>.
// *Action: Place nothing or only USER <user name> after the tablespace name
/
38304, 00000, "missing or invalid user name"
// *Cause: A valid user name was expected.
// *Action: Specify a valid user name.
/
38305, 00000, "object not in RECYCLE BIN"
// *Cause: Trying to Flashback Drop an object which is not in RecycleBin.
// *Action: Only the objects in RecycleBin can be Flashback Dropped.
/
38306, 00000, "this object is not recoverable standalone"
// *Cause: Trying to flashback drop an object other than of type TABLE.
// *Action: Only tables are recoverable.
/
38307, 00000, "object not in RECYCLE BIN"
// *Cause: Trying to Purge the object which is not in RecycleBin.
// *Action: Only the objects in RecycleBin can be PURGEDED.
/
38308, 00000, "invalid FLASHBACK DROP option"
// *Cause: Invalid Flashback Drop option specified.
// *Action: Specify a valid Flashback Drop option.
/
38309, 00000, "object not purgable"
// *Cause: An attempt was made to purge an object that is either not
// purgable or else dependent upon some other object.
// *Action: Cannot purge this object.
/
38310, 00000, "cannot purge tablespace for other users"
// *Cause: An attempt was made to purge the tablespace for a different user
// by a user who does not have system DBA priviledges.
// *Action: Cannot purge the tablespace for some other user.
/
38311, 00000, "cannot purge objects owned by other users"
// *Cause: An attempt was made to purge an object which is owned by
// some other user.
// *Action: Cannot purge this object.
/
38312, 00000, "original name is used by an existing object"
// *Cause: An attempt was made to recover an object preserving the original
// name, but that name is taken up by some other object.
// *Action: use the RENAME clause to recover the object with a different
// name.
/
////////////////////////////////////////////////////////////////////////////
// Error numbers from 38320 are reserved by ILM
////////////////////////////////////////////////////////////////////////////
38320, 00000, "policy does not exist"
// *Cause: An attempt was made to delete a nonexistent policy.
// *Action: Correct the policy name.
38321, 00000, "duplicate policy name specified"
// *Cause: A policy name was specified that already existed under this schema.
// *Action: Correct the policy name.
38322, 00000, "scope of policy not specified"
// *Cause: An attempt was made to add a policy without the scope.
// *Action: Specify a scope when creating a policy.
38323, 00000, "policy conflicts with policy %s"
// *Cause: An attempt was made to create a policy with the same action
// type and based on the same statistic as another policy on the
// object.
// *Action: Use a different action and/or statistic for the new policy,
// or delete the old policy.
38324, 00000, "policy conflicts with policy %s"
// *Cause: An attempt was made to create a policy with the same action, scope
// and compression level as another policy on the object.
// *Action: Use a different action, scope and/or level for the new policy, or
// delete the old policy.
38325, 00000, "policy conflicts with policy %s"
// *Cause: An attempt was made to create a compression policy that conflicts with
// another policy on the object.
// *Action: Change the policy so that policies with a higher compression level
// take effect after policies with a lower compression level, or delete
// the old policy.
38326, 00000, "schema level policies are not supported"
// *Cause: Attempt was made to create a schema level policy.
// *Action: Do not create a schema level policy.
38327, 00000, "invalid argument value"
// *Cause: The specified API argument values were of the wrong value range.
// *Action: Supply valid values for the API.
38328, 00000, "inconsistent internal state"
// *Cause: An inconsistency was detected in ILM related data in the dictionary.
// *Action: Contact Oracle Support Services.
38329, 00000, "internal ILM error"
// *Cause: An internal error occurred during execution of ILM related
// activity. Further information can be found in the alert log.
// *Action: Fix the problem and retry the operation.
38330, 00000, "insufficient privilege for ILM operation"
// *Cause: Sufficient privileges were not granted for the ILM operation.
// *Action: Retry operation with sufficient privileges granted. Consult
// documentation for privileges required to perform the ILM operation.
38331, 00000, "row-level write activity tracking not enabled on the table"
// *Cause: An attempt was made to create a modification time-based policy
// when row-level write tracking was not enabled on the object.
// *Action: Ensure that row-level write tracking is enabled on the table.
38332, 00000, "valid time periods were not present on the table"
// *Cause: An attempt was made to create a valid time-based policy
// when valid time periods were not present on the table.
// *Action: Add valid time periods to the table.
38333, 00000, "row-level access activity tracking not enabled on the table"
// *Cause: An attempt was made to create an access time-based policy
// when row-level access tracking was not enabled on the object.
// *Action: Ensure that row-level access tracking is enabled on the table.
38334, 00000, "segment-level access activity tracking not enabled on the table"
// *Cause: An attempt was made to create an access time-based policy
// when segment-level access tracking was not enabled on the object.
// *Action: Ensure that segment-level access tracking is enabled on the table.
38335, 00000, "sysdba privilege is required"
// *Cause: SYSDBA privilege is required for applying ILM policies on a tablespace.
// *Action: Grant user SYSDBA role before applying tablespace level ILM policies.
38336, 00000, "invalid policy"
// *Cause: A row level policy was used with a compression level other than OLTP.
// *Action: Use the OLTP compression level with row level compression policies.
38337, 00000, "invalid policy"
// *Cause: A custom policy is only allowed at the segment level.
// *Action: Change the scope of the policy to be of type segment.
38338, 00000, "incorrect ILM policy scope"
// *Cause: An attempt was made to create an Information Lifecycle Management
// (ILM) policy with incompatible scope.
// *Action: Ensure that the scope of the ILM policy is compatible.
38339, 00000, "invalid action specified"
// *Cause: An invalid action was specified in the policy definition.
// *Action: Specify a valid action in the policy definition.
38340, 00000, "invalid policy"
// *Cause: An attempt was made to create a custom policy at the
// tablespace level.
// *Action: Specify the policy directly on the desired objects.
38341, 00000, "policy conflicts with policy %s"
// *Cause: An attempt was made to create more than one storage tiering policy
// directly on an object.
// *Action: Delete the conflicting policy before creating a new policy.
38342, 00000, "heat map not enabled"
// *Cause: An attempt was made to create an Information Lifcecycle Management
// (ILM) policy when heat map was not enabled.
// *Action: Enable heat map before creating a new ILM policy.
38343, 00000, "ADO online mode not supported with supplemental logging enabled"
// *Cause: An attempt was made to perform an automatic data optimization (ADO)
// operation with supplemental logging enabled.
// *Action: Disable supplemental logging or switch to ADO offline mode and retry.
38344, 00000, "bulk load compression trace event"
// *Document: NO
// *Cause: Explicitly set.
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Turn on/off various bulk load compression trace features.
38345, 00000, "object not enabled for in-memory column store"
// *Cause: An attempt was made to create a policy on an object that was not
// enabled for in-memory column store.
// *Action: Enable the object for in-memory column store and specify the policy.
38346, 00000, "ILM operation not supported"
// *Cause: An attempt was made to use an Information Lifecycle Mangement (ILM)
// operation that is not supported for the current SQL statement.
// *Action: Use the operation with a supported SQL statement.
38347, 00000, "join group cannot be created"
// *Cause: Join group cannot be created on the specified tables.
// *Action: Check to see that the database is not in standby mode and has
// read-write privileges, the specified tables for creating join
// group are ready for processing and the dictionary tables
// im_domain$, im_joingroup$ are also present.
// Then, retry the operation.
38348, 00000, "join group cannot be dropped"
// *Cause: The specified join group cannot be dropped.
// *Action: Check to see that the database is not in standby mode and has
// read-write privileges, and the dictionary tables im_domain$,
// im_joingroup$ are present. Then, retry the operation.
38349, 00000, "join group cannot be altered"
// *Cause: The specified join group cannot be altered.
// *Action: Check to see that the database is not in standby mode and has
// read-write privileges, the specified tables used in altering join
// group are ready for processing and the dictionary tables
// im_domain$, im_joingroup$ are also present.
// Then, retry the operation.
38350, 00000, "join group not supported on given columns"
// *Cause: One of the columns used for the join group was not supported
// because the column property field was non-zero.
// *Action: Retry the operation on the join group without including
// the unsupported column.
38351, 00000, "join group not supported on abstract data type columns"
// *Cause: One of the columns used for the join group was of the abstract
// data type.
// *Action: Retry the operation on the join group without including
// columns of the abstract data type.
38352, 00000, "cannot alter column present in a join group"
// *Cause: The alter table operation caused one of the columns to
// become unsupported for a join group.
// *Action: Drop the column from the join group and retry the operation.
38353, 00000, "This table type is not supported by the ROW ARCHIVAL clause."
// *Cause: An attempt was made to create or alter table to enable ROW
// ARCHIVAL, but ROW ARCHIVAL is not supported for these table types.
// *Action: None.
38354, 00000, "syntax error; operation on join group cannot be done"
// *Cause: There was a syntax error found for either the create, alter, or
// drop in-memory join group.
// *Action: Use the correct syntax.
38391, 00000, "disabling ILM filtering"
38392, 00000, "kdc cluster trace event"
// *Document: NO
// *Cause: Explicitly set.
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Turn on/off internal diagnostic/debug prints for clustered tables.
//
38393, 00000, "ILM internal out-of-space error"
// *Cause: Information Lifecycle Management (ILM) internal operation
// encountered out-of-space error.
// *Action: None
//
38394, 00000, "test event for table ILM operations"
// *Cause: Internal testing event for table Information Lifecycle Management
// (ILM) operations.
// *Action: None
//
38395, 00000, "debug event for table ILM operations"
// *Cause: There was an internal debugging event for table Information
// Lifecycle Management (ILM) operations.
// *Action: None
//
38396, 00000, "table is already enabled for the ILM feature"
// *Cause: The table was already enabled for the specified Information Lifecycle
// Management (ILM) feature.
// *Action: No action required.
//
38397, 00000, "table is not enabled for the ILM feature"
// *Cause: An attempt was made to perform an Information Lifecycle Management
// (ILM) operation on a table on which the specified ILM feature is
// not enabled.
// *Action: No action required.
//
38398, 00000, "DDL not allowed on the system ILM column"
// *Cause: An attempt was made to drop, rename, or modify a system Information
// Lifecycle Management (ILM) column.
// *Action: No action required.
//
38399, 00000, "cannot update the system ILM column"
// *Cause: An attempt was made to update a system Information Lifecycle
// Management (ILM) column.
// *Action: No action required.
//
38400, 00000, "cannot combine ILM operation with other operations"
// *Cause: An attempt was made to combine Information Lifecycle Management (ILM)
// operation with other ALTER TABLE operations.
// *Action: Ensure that ILM is the sole operation specified in ALTER TABLE.
/////////////////// Expression Filter
// Error numbers 38401 to 38599 are reserved for Expression Filter
///////////////////
38401, 00000, "synonym %s not allowed"
// *Cause: An attempt was made to use a synonym for a data type of an
// attribute or a table alias.
// *Action: Use the object name instead of the synonym.
38402, 00000, "invalid name: empty string or spaces in the name"
// *Cause: There were spaces in the name.
// *Action: Remove spaces in the name or use quotes around the name.
38403, 00000, "attribute set name may not be longer than 22 characters"
// *Cause: The attribute set name was longer than 22 characters.
// *Action: Choose a name that has 22 or fewer characters.
38404, 00000, "schema extension not allowed for the attribute set name"
// *Cause: There was a schema extension for the attribute set name. Attribute
// sets are always created in the current schema and
// thus schema extended names are not allowed.
// *Action: Create the attribute set from the appropriate schema.
38405, 00000, "quotes not allowed in the attribute set name"
// *Cause: The attribute set name contained quotes.
// *Action: Remove quotes in the attribute set name.
38406, 00000, "attribute set %s already exists"
// *Cause: An attribute set with a matching name already exists in the
// current schema.
// *Action: Drop the existing attribute set or choose a different name.
38407, 00000, "The ADT associated with the attribute set already exists."
// *Cause: The Abstract type (ADT) with the same name as the attribute set
// already exists in the current schema.
// *Action: Create the attribute set for the existing ADT or drop the ADT.
38408, 00000, "The ADT \"%s\" does not exist in the current schema."
// *Cause: An attempt was made to create the attribute set from a
// nonexistent ADT.
// *Action: Make sure that the ADT with the same name as the attribute set
// exists in the current schema.
38409, 00000, "invalid name or option for the attribute set: %s"
// *Cause: An invalid name or option was used for the attribute set.
// *Action: Set serveroutput ON and repeat the operation for additional
// information.
38410, 00000, "schema extension not allowed for the table name"
// *Cause: An attempt was made to use a schema extended name for the table
// storing expressions.
// *Action: The table storing expressions and the corresponding attribute
// set should be created in the same schema.
38411, 00000, "invalid datatype for the column storing expressions"
// *Cause: An attempt was made to create an expression column from a
// column of invalid datatype.
// *Action: Create a VARCHAR2 or CHAR column to store expressions in a
// table.
38412, 00000, "Expression set column %s does not exist."
// *Cause: The column storing expressions does not exist.
// *Action: Pass a valid name for the column storing expressions.
38413, 00000, "elementary attribute name may not be longer than 32 characters"
// *Cause: An attempt was made to create an elementary attribute with a name
// longer than 32 characters.
// *Action: Use a shorter name for the elementary attribute.
38414, 00000, "invalid datatype for the attribute %s"
// *Cause: The datatype specified for the attribute was invalid.
// *Action: If the datatype is an ADT, make sure that the ADT exists and the
// current user has execute permissions to it.
38415, 00000, "invalid name or datatype for the attribute: %s"
// *Cause: An invalid name or datatype was used for the attribute.
// *Action: Set serveroutput ON and repeat the operation for additional
// information.
38416, 00000, "A stored attribute may not be longer then 300 characters."
// *Cause: An attempt was made to create a stored or indexed attribute
// longer than 300 characters.
// *Action: A predicate with such attribute may not be indexed. It will be
// evaluated as sparse predicate.
38417, 00000, "attribute set %s does not exist"
// *Cause: An attempt was made to use an attribute set that does not exist.
// *Action: Create the attribute set or choose an existing attribute set.
38418, 00000, "ADT associated with the attribute set %s does not exist"
// *Cause: The ADT with the same name as the attribute set was not found in
// the current schema.
// *Action: Drop the attribute set and recreate it.
38419, 00000, "invalid identifier in attribute : %s"
// *Cause: An identifier used in the stored/indexed attribute sub-expression
// was not defined or was invalid.
// *Action: Create all the required elementary attributes and user-defined
// functions and try again.
38420, 00000, "invalid stored attribute sub-expression: %s"
// *Cause: The sub-expression used for the stored expression was invalid.
// *Action: Set serveroutput ON and repeat the operation for additional
// information.
38421, 00000, "attribute %s already exists"
// *Cause: An attribute with a matching name (or form) already exists in the
// attribute set.
// *Action: Drop the existing attribute or choose a different name for the
// new attribute.
38422, 00000, "invalid datatype for the attribute: %s"
// *Cause: An attempt was made to create an attribute with invalid datatype.
// *Action: If the data type of the attribute is an ADT, make sure that the
// type exists.
38423, 00000, "Attribute set created from an ADT may not be extended."
// *Cause: An attempt was made to add an elementary attribute to an attribute
// set created from an ADT.
// *Action: Create a new attribute set and add all the required elementary
// attributes one at a time.
38424, 00000, "no attribute set currently assigned to the expression set"
// *Cause: An attempt was made to un-assign an attribute set from an expression
// set when there is no attribute set assigned to it.
// *Action: No action is required.
38425, 00000, "attribute set used for an index object may not be unassigned"
// *Cause: An attempt was made to un-assign an attribute set from an expression
// set when there is an Expression Filter index defined on the column.
// *Action: Drop the index before un-assigning the attribute set.
38426, 00000, "attribute set assigned to an expression set may not be dropped"
// *Cause: An attempt was made to drop an attribute set when it is still
// associated with an expression set.
// *Action: Un-assign the attribute set from the expression set before dropping
// it.
38427, 00000, "attribute %s does not exist"
// *Cause: An attempt was made to use an attribute set that does not exist.
// *Action: Create the attribute set.
38428, 00000, "too many attributes selected for indexing"
// *Cause: An attempt was made to create an expression filter index with more
// than 490 indexed attributes.
// *Action: Remove some of the indexed attributes. Make sure that the default
// indexed attributes associated with the attribute set combined with the
// indexed attributes specified in the Create Index Parameters clause
// are less than or equal to 490.
38429, 00000, "invalid datatype for a stored attribute: %s"
// *Cause: The (resulting) datatype for the attribute was not appropriate for
// storing.
// *Action: Choose a stored attribute that has a resulting datatype of
// NUMBER, VARCHAR2, CHAR or DATE.
38430, 00000, "Operation \"%s\" not supported in the current release."
// *Cause: An attempt was made to perform an unsupported operation.
// *Action: Do not use the operation.
38431, 00000, "could not evaluate subexpression \"%s\" for rowid \"%s\""
// *Cause: Either the expression was not a valid SQL-WHERE clause format or
// it had references to nonexistent schema objects.
// *Action: Correct the expression.
38432, 00000, "EVALUATE operator only allowed on an expression column"
// *Cause: An attempt was made to use the EVALUATE operator on a column not
// configured as a column storing expressions.
// *Action: Assign an attribute set to the column.
38433, 00000, "index \"%s\" could not be maintained due to \"%s\""
// *Cause: The error was caused by the recursive operation.
// *Action: Fix the error and retry.
38434, 00000, "could not evaluate expression \"%s\""
// *Cause: Either the expression was not in a valid SQL-WHERE clause format or
// it had references to nonexistent schema objects or there is a
// missing attribute value.
// *Action: Set serveroutput ON for more details.
38435, 00000, "missing elementary attribute value or invalid name-value pairs"
// *Cause: The second argument to the EVALUATE operator had either a missing
// attribute or an invalid value for an attribute.
// *Action: Try again after fixing the error.
38436, 00000, "attribute set used for an Expression set may not be modified."
// *Cause: An attempt was made to add an elementary attribute to an attribute
// set assigned to an expression set.
// *Action: Un-assign the attribute set and try again.
38437, 00000, "The ADT \"%s\" may not contain any user methods."
// *Cause: An attempt was made to create an attribute set from an ADT that
// has one or more user methods.
// *Action: Drop the ADT and recreate it with no user methods.
38438, 00000, "getVarchar not possible due to \"%s\" datatype in the attribute set"
// *Cause: An attempt was made to use the getVarchar API when the attribute
// set has one or more non-scalar types.
// *Action: Use AnyData conversion to encode the data item.
38439, 00000, "invalid operation \"%s\" "
// *Cause: An attempt was made to use an invalid operation.
// *Action: Use one of the following operations : ADD, DROP
38440, 00000, "attribute set %s does not exist"
// *Cause: An attempt was made to copy an attribute set that is not accessible
// from the current schema.
// *Action: Grant execute permissions on the corresponding ADT to the current
// user and try again.
38441, 00000, "System could not derive the list of STORED and INDEXED attributes."
// *Cause: The attribute set was created without default index parameters.
// *Action: Specify the default index parameters for the attribute set or
// include a valid PARAMETERS clause for the CREATE INDEX command.
38442, 00000, "The ADT \"%s\" is not in a valid state."
// *Cause: An attempt was made to use an ADT that is not in a valid state.
// *Action: Check the INCOMPLETE field in the user_types catalog view to make
// sure that the ADT is in a valid state. Drop the invalid ADT and
// recreate the corresponding attribute set.
38443, 00000, "An attribute set should be assigned to the expression set for statistics collection."
// *Cause: An attempt was made to collect statistics for an expression set
// with no attribute set assigned to it.
// *Action: Assign an attribute set to the expression set before collecting
// the statistics.
38444, 00000, "statistics do not exist for the expression set"
// *Cause: An attempt was made to clear the statistics that do not exist.
// *Action: No action was required.
38445, 00000, "TOP clause not allowed with no statistics"
// *Cause: An attempt was made to use the TOP parameters clause with no
// statistics available for the expression set.
// *Action: Collect statistics for the expression set and try again.
38446, 00000, "Error with embedded ADT \"%s\" in the attribute set."
// *Cause: The embedded ADT has errors.
// *Action: Set serveroutput ON for additional information.
38447, 00000, "Type required for the embedded ADT attribute \"%s\" is missing"
// *Cause: Object type required for the embedded ADT was missing.
// *Action: Set serveroutput ON for additional information.
38448, 00000, "Indexing predicates with \"%s\" operator is not supported."
// *Cause: An unsupported operator was used in the exf$indexoper array.
// *Action: Choose the operators from this list : =, <, >, <=, >=, !=,
// is null, is not null, nvl, and between.
38449, 00000, "table \"%s\" does not exist or is not accessible"
// *Cause: An attempt was made to create a table alias for a table that does
// not exist or is not accessible.
// *Action: Grant select privileges on the table to the current user.
38450, 00000, "error computing a stored attribute for the expression set."
// *Cause: Either values for one of the attributes was incorrect or a stored
// attribute was invalid due to broken dependencies.
// *Action: Correct the input.
38451, 00000, "index is in an inconsistent state"
// *Cause: One or more secondary objects used to maintain the index did not
// exist
// *Action: Drop the index and recreate it.
38452, 00000, "Expression Filter index name may not be longer than 25 characters"
// *Cause: An attempt was made to use a name longer than 25 characters for the
// Expression Filter index.
// *Action: Choose a name that has 25 or fewer characters
38453, 00000, "ExpFilter index should be created in the same schema as the base table."
// *Cause: An attempt was made to create the Expression Filter index in a
// schema other than that of the base table.
// *Action: Create the index in the same schema as the base table.
38454, 00000, "attribute set not defined for the column being indexed"
// *Cause: An attempt was made to create an Expression Filter index on a column
// with no attribute set association.
// *Action: Assign an attribute set to the expression set column begin indexed.
38455, 00000, "Expression Filter index should be created by the owner."
// *Cause: An attempt was made to create the Expression Filter index by a user
// who is not the owner of the index.
// *Action: Create the index using owner's privileges.
38456, 00000, "The attribute set \"%s\" is in an inconsistent state."
// *Cause: The attribute set was in an inconsistent state due to broken
// dependencies.
// *Action: Set serveroutput ON for more details. The attribute set may not be
// reused after this error.
38457, 00000, "The attribute \"%s\" is not a valid XMLType attribute."
// *Cause: An attempt was made to use a non-XMLType attribute to configure XPath
// filtering.
// *Action: Use an attribute of sys.XMLType datatype to configure XPath
// filtering.
38458, 00000, "invalid operation \"%s\" for XPATH_FILTER_PARAMETERS"
// *Cause: An attempt was made to use an invalid operation.
// *Action: Use one of the following operations : ADD, DROP.
38459, 00000, "XML Tag \"%s\" not found for the XMLType attribute \"%s\""
// *Cause: An Attempt was made to use a non-existent XML Tag.
// *Action: Correct the name of the XML Tag or the XMLType attribute.
38460, 00000, "filtering based on datatype \"%s\" not supported for XML Tags"
// *Cause: An attempt was made to configure XPath filtering with an XML Tag
// of unsupported datatype.
// *Action: Leave the XML Tag out of filter parameters. It will be processed
// as sparse predicate
38461, 00000, "XML Tag \"%s\" already exists for the XMLType attribute \"%s\""
// *Cause: An attempt was made to create a duplicate XML Tag.
// *Action: Choose a different XML Tag.
38462, 00000, "invalid attribute list"
// *Cause: The input was missing an attribute list or had null values for the
// attribute names.
// *Action: Correct the input.
38463, 00000, "invalid XML Tag list"
// *Cause: The input was missing a tag list or had null values for the
// tag names.
// *Action: Correct the input.
38464, 00000, "expression set is not empty."
// *Cause: An attempt was made to assign an attribute set to a non-empty
// expression set.
// *Action: Use FORCE = 'TRUE' to validate all the existing expressions.
38465, 00000, "failed to create the privilege checking trigger due to: %s"
// *Cause: Creation of the trigger failed due to the error listed in the
// message.
// *Action: Set serveroutput ON for more information.
38466, 00000, "user does not have privileges to CREATE/MODIFY expressions"
// *Cause: An attempt was made to INSERT or UPDATE a column storing expression
// without appropriate permissions.
// *Action: Appropriate privileges on the expression set should be granted by
// the owner of the expression set.
38467, 00000, "user cannot GRANT/REVOKE privileges to/from himself"
// *Cause: An attempt was made to GRANT or REVOKE privileges to or from the
// current user.
// *Action: The the to_user or from_user field should be different from the
// user performing the operation.
38468, 00000, "column \"%s\" is not identified as a column storing expressions."
// *Cause: An attempt was made to grant permission on a nonexistent expression
// set.
// *Action: Make sure that the table and the column exist and an attribute set
// is associated with the column.
38469, 00000, "invalid privilege for an expression set: %s"
// *Cause: An attempt was made to use an invalid privilege.
// *Action: See documentation for a valid privilege.
38470, 00000, "cannot revoke a privilege that was not granted."
// *Cause: An attempt was made to revoke a privilege that had not been granted.
// *Action: Check catalog views to see if the user has the privilege.
38471, 00000, "ROWIDs for table aliases cannot be null"
// *Cause: An attempt was made to pass a null value for the table alias
// attribute in the data item, which is not permitted.
// *Action: Pass a valid rowid value for the table alias.
38472, 00000, "VARCHAR representation of the data item is too long."
// *Cause: The VARCHAR representation of data item was too long.
// *Action: Use the EVALUATE operator with AnyData argument instead.
38473, 00000, "cannot drop a type used for Expression Filter attribute set"
// *Cause: An attempt was made to drop an ADT that was used to maintain an
// attribute set for the Expression Filter.
// *Action: Query USER_EXPFIL_ATTRIBUTE_SETS view to see the dependency.
38474, 00000, "attribute set may not have attributes of TABLE COLLECTION type."
// *Cause: An attempt was made to create an attribute with a TABLE COLLECTION
// type.
// *Action: Use VARRAYs instead of table collection, if possible.
38475, 00000, "The attribute set and the associated ADT are out of sync."
// *Cause: The ADT was directly modified by CREATE or ALTER operations.
// *Action: Drop the attribute set and recreate it from scratch.
38476, 00000, "abstract type used for an Attribute set may not be modified."
// *Cause: An attempt was made to alter a type (ADT) that is used to maintain
// an attribute set of an Expression set.
// *Action: Do not modify the ADT directly. Use DBMS_EXPFIL APIs instead.
38477, 00000, "attribute set cannot be derived from an evolved type or a subtype."
// *Cause: An attempt was made to create an attribute set from an evolved ADT
// or a subtype.
// *Action: The ADT used for the attribute set cannot be an evolved type or a
// subtype.
38478, 00000, "creation of system trigger EXPFIL_DROPOBJ_MAINT failed"
// *Cause: The creation of the system trigger EXPFIL_DROPOBJ_MAINT failed
// due to missing Expression Filter dictionary tables.
// *Action: Try a clean installation again. If this error is ignored, the
// Expression Filter dictionary could have some stale entries.
38479, 00000, "creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed"
// *Cause: The creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed
// due to missing Expression Filter dictionary tables.
// *Action: Try a clean installation again. If this error is ignored, the
// user will be able to evolve ADTs associated with the attribute
// set, thus causing spurious errors.
38480, 00000, "creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed."
// *Cause: The creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed
// due to errors in SYS.EXF$DBMS_EXPFIL_SYSPACK
// package.
// *Action: Try a clean installation again. If this error is ignored, a RENAME
// of the expression table may cause the EVALUATE queries to fail.
38481, 00000, "ADT \"%s\" is used for a dependent object."
// *Cause: An attempt was made to create an attribute set from an ADT which is
// used by one or more dependent objects.
// *Action: Use a new ADT instead.
38482, 00000, "no elementary attributes defined in the attribute set"
// *Cause: An attempt was made to use an empty attribute set.
// *Action: Create one or more elementary attributes for the attribute set.
38483, 00000, "invalid FUNCTION/PACKAGE/TYPE name: \"%s\""
// *Cause: An attempt was made to use an invalid name format.
// *Action: The function/package/type name should be specified in the
// following format [owner.]object_name
38484, 00000, "FUNCTION/PACKAGE/TYPE %s does not exist"
// *Cause: Attempt was made to use a object that does not exist.
// *Action: Query ALL_OBJECT view to ensure that the object exists.
38485, 00000, "invalid object type for the user-defined function"
// *Cause: An attempt was made to use an invalid object as a function.
// *Action: Valid object types are FUNCTION / PACKAGE / TYPE
38486, 00000, "FUNCTION/PACKAGE/TYPE already exists for the attribute set"
// *Cause: An attempt was made to add a duplicate function to the list.
// *Action: Use a different object name.
38487, 00000, "FUNCTION/PACKAGE/TYPE \"%s\" not allowed in the expression"
// *Cause: An attempt was made to use an un-approved function in the
// expression.
// *Action: Add the function to the corresponding attribute set
38488, 00000, "attribute set already assigned to the column storing expressions"
// *Cause: An attempt was made to reassign an attribute set to an expression
// column.
// *Action: Query USER_EXPFIL_EXPRESSION_SETS view to find the attribute set
// assigned the expression set
38489, 00000, "predicate table creation failed due to: ORA%s"
// *Cause: Predicate table creation failed due to the reported error.
// *Action: Set serveroutput ON for additional information
38490, 00000, "invalid name: quotes do not match"
// *Cause: The quotes in the name did not match.
// *Action: Correct the name to match the quotes.
38491, 00000, "could not evaluate subexpression for rowid \"%s\""
// *Cause: Either the expression was not in a valid SQL-WHERE clause format or
// it had references to nonexistent schema objects.
// *Action: Correct the expression.
38492, 00000, "invalid ALTER INDEX parameters clause \"%s\""
// *Cause: An invalid parameters clause was specified with the ALTER INDEX
// command.
// *Action: See documentation for a valid list of parameters.
38493, 00000, "feature not enabled : Expression Filter index"
// *Cause: An attempt was made to create an Expression Filter index in
// Standard Edition.
// *Action: Do not attempt to use this feature.
38494, 00000, "column in the table alias and an attribute have matching names"
// *Cause: One of the attributes in the set has the same name as the name
// of one of the columns in the table configured for table alias.
// *Action: If possible, use a different name for the attribute.
38495, 00000, "data type for the stored attribute %s is inconsistent."
// *Cause: The actual data type for the stored attribute configured for the
// Expression Filter index object did not match the data type
// recorded in the Expression Filter dictionary.
// *Action: Delete the attribute from the default index attributes and
// recreate it.
38496, 00000, "Expression Filter index is not in a valid state"
// *Cause: An attempt was made to REBUILD an Expression Filter index that
// was not valid.
// *Action: Use DEFAULT keyword in the parameters clause to rebuild the
// index from defaults or drop and recreate the index.
38497, 00000, "Expression Filter index does not exist"
// *Cause: Index with a matching name does not exist or the index was
// not created using ExpFilter indextype.
// *Action: Identify the correct index using the Expression Filter catalog
// views
38498, 00000, "invalid stored attribute for the index object : %s"
// *Cause: The expression filter index object has a stored or indexed attribute
// that had broken dependencies.
// *Action: Make sure that all the identifiers used in the attribute are
// valid.
38499, 00000, "expression set already configured for stored/indexed attributes"
// *Cause: The expression set already had a list of stored and indexed
// attributes. Additional attributes cannot be specified in the
// CREATE INDEX parameters clause.
// *Action: Remove TOP, STOREATTRS and INDEXATTRS clauses from the parameters
// clause or clear the expression set statistics using
// DBMS_EXPFIL.INDEX_PARAMETERS API.
38500, 00000, "%s"
// *Cause: There was a generic error
// *Action: See documentation for further information.
38501, 00000, "sub-query not allowed in the expression"
// *Cause: An attempt was made to use a sub-query in the expression.
// *Action: Do not use sub-queries in the expressions.
38502, 00000, "invalid XML tag: %s"
// *Cause: An attempt was made to use an invalid XML tag for the index.
// *Action: Correct the XML tag and retry.
38503, 00000, "index already defined using the parameters"
// *Cause: An attempt was made to modify the index parameters after
// the index creation.
// *Action: Drop the index and retry.
38504, 00000, "this operator not allowed with the configured attribute set"
// *Cause: An attempt was made to use the operator binding with an
// attribute set containing more than one (table alias) attribute.
// This is not permitted.
// *Action: Use a different operator binding.
38505, 00000, "invalid default value for the attribute"
// *Cause: An attempt was made to use an invalid default value or a default
// that is larger than 100 characters.
// *Action: Specify a correct default value.
38506, 00000, "invalid attribute type for text predicates"
// *Cause: An attempt was made to use an invalid type for an attribute
// configured for text predicates.
// *Action: Use either a VARCHAR or a CLOB attribute instead.
38507, 00000, "attributes of %s data type should be indexed"
// *Cause: An attempt was made to configure an attribute of spatial or text
// data type as stored predicate group.
// *Action: Configure them as indexed predicate groups instead.
/////////////////// Frequent Itemset Counting
// Error numbers 38600 - 38699 are reserved for Frequent Itemset Counting
///////////
38601, 00000, "FI Not enough memory for frequent itemset counting: %s"
// *Cause: The memory size did not satisfy the minimum memory requirement.
// *Action: In workarea_size_policy='manual' mode, set _fic_area_size to a
// reasonably larger value.
// Or, In workarea_size_policy='auto' mode, this error should never
// happen.
//
38602, 00000, "FI invalid input cursor"
// *Cause: The input cursor did not return exactly two columns for
// transactional input format or the input cursor didn't
// have consistent data types for horizontal input format
// *Action: For transactional input format, specify that the input cursor
// returns exactly two columns: one for transaction-id, one for
// item-id. For horizontal input format, make sure the input cursor's
// columns have the same data types.
//
38603, 00000, "FI including & excluding cursor can only return one column"
// *Cause: The including & excluding cursor did not return exactly one column.
// *Action: Specify that the cursor return only one column: item-id.
//
38604, 00000, "FI including & excluding cursor item-id type must match input cursor item-id type"
// *Cause: The including & excluding cursor item-id type did not match input
// cursor item-id type
// *Action: Specify that the item-id type of the cursors match each other.
//
38605, 00000, "FI not enough memory(%sK) for candidate generation(%sK)"
// *Cause: There was insufficient available memory for candidate generation.
// *Action: In workarea_size_policy='manual' mode, set _fic_area_size to a
// reasonably larger value.
// Or, in workarea_size_policy='auto' mode, set pga_aggregate_target to a
// reasonably larger value.
//
38606, 00000, "FI support threshold not between [0, 1]"
// *Cause: The user inputed a support threshold not in the range of [0, 1].
// *Action: The user should adjust the input value in the range of [0, 1].
//
38607, 00000, "FI minimum and maximum itemset length not between [1, %s]"
// *Cause: The inputed minimum or maximum itemset length exceed the internal
// maximum itemset length or less than 1.
// *Action: The user should adjust the input value not larger than the internal
// maximum itemset length and not less than 1.
//
38608, 00000, "FI itemset minimum-length(%s) should not be greater than maximum length(%s)"
// *Cause: The user inputed minimum length is more than maximum length.
// *Action: The user should adjust the input values to make the minimum length
// less than or equal to the maximum length.
//
38609, 00000, "FI Not enough memory for tree counting, requires at least %sKB"
// *Cause: The memory size did not satisfy the minimum memory requirement for
// tree counting.
// *Action: In workarea_size_policy='manual' mode, set _fic_area_size to a
// reasonably larger value.
// Or, In workarea_size_policy='auto' mode, this error should never
// happen.
//
38610, 00000, "FI \"%s\" name prefix is reserved for frequent itemset counting"
// *Cause: An error occurred because DBMS_FREQUENT_ITEMSET and prefix ORA_FI
// are reserved for the DBMS_FREQUENT_ITEMSET package's internal use.
// *Action: Do not re-define functions with names starting with
// DBMS_FREQUENT_ITEMSET package or ORA_FI.
38611, 00000, "FI input cursor's item type is not supported"
// *Cause: The input cursor's item type is not number or character type
// *Action: Redefine the input cursor so that item type is number
// or character type.
38612, 00000, "FI item length cannot exceed half of one database block."
// *Cause: The item's length was more than half of one database block.
// *Action: Redefine the data type of the item column so that its maximum
// length is less than half of one database block.
38613, 00000, "FI Cursor is returning less than 2 columns."
// *Cause: Cursor parameter is returning less than 2 columns.
// *Action: Modify the Cursor argument to return 2 columns.
38620, 00000, "DT expressions in input cursor do not have an alias name"
// *Cause: Expressions in input cursor do not have an alias name.
// *Action: Add an alias name for the expression.
38621, 00000, "Decision Tree maximum depth setting not between [2, 20]"
// *Cause: The user specified a max tree depth not in the range of [2, 20].
// *Action: The user should adjust the input value to be in the range of [2, 20].
//
38622, 00000, "Decision Tree not enough memory, requires at least %sKB"
// *Cause: The memory size did not satisfy the minimum memory requirement for
// decision tree building.
// *Action: In workarea_size_policy='manual' mode, set _dtree_area_size to a
// reasonably larger value.
// Or, In workarea_size_policy='auto' mode, please raise
// pga_aggregate_target to a reasonably larger value.
//
/////////////////// Flashback Database
// Error numbers 38700 to 38899 are reserved for Flashback Database
///////////////////
38700, 00000, "Limit of %s flashback database logs has been exceeded."
// *Cause: The maximum number of flashback database log files was exceeded.
// *Action: DB_FLASHBACK_RETENTION_TARGET may be set to high. Modify it to
// a smaller value.
38701, 00000, "Flashback database log %s seq %s thread %s: \"%s\""
// *Cause: This message reports the filename for details of another message.
// *Action: Other messages will accompany this message. See the associated
// messages for the appropriate action to take.
38702, 00000, "Cannot update flashback database log file header."
// *Cause: Could not write to the flashback database log file.
// *Action: Restore access to the file.
38703, 00000, "Type %s in header is not a flashback database log file."
// *Cause: A corrupt flashback database log file header was read.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38704, 00000, "Checksum error in flashback database log file header."
// *Cause: The flashback database log file header contained a
// checksum that does not match the value calculated from the file
// header as read from disk. This means the file header was
// corrupt.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38705, 00000, "Expected block size %s does not match %s in log header."
// *Cause: When the flashback log file header was read, the block size
// in the control file did not match the block size contained
// in the header.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38706, 00000, "Cannot turn on FLASHBACK DATABASE logging."
// *Cause: An ALTER DATABASE FLASHBACK ON command failed.
// Other messages in the alert log describe the problem.
// *Action: Fix the problem and retry.
38707, 00000, "Media recovery is not enabled."
// *Cause: An ALTER DATABASE FLASHBACK ON command failed because media
// recovery was not enabled.
// *Action: Turn on media recovery with an ALTER DATABASE ARCHIVELOG
// command and then retry the command.
38708, 00000, "not enough space for first flashback database log file"
// *Cause: An ALTER DATABASE FLASHBACK ON command failed because there
// was not enough space in the Recovery Area for the first
// flashback database log file.
// *Action: Make more space in the Recovery Area. For example, this
// can be done by increasing the value of
// DB_RECOVERY_FILE_DEST_SIZE.
38709, 00000, "Recovery Area is not enabled."
// *Cause: An ALTER DATABASE FLASHBACK ON command failed because the
// Recovery Area was not enabled.
// *Action: Set DB_RECOVERY_FILE_DEST to a location and retry.
38710, 00000, "Flashback log version %s is incompatible with ORACLE version %s."
// *Cause: The flashback database log file was rejected because it
// appeared to be written by an incompatible version of Oracle.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38711, 00000, "Corrupt flashback log block header: block %s"
// *Cause: A corrupt Flashback Database log file block header was read.
// More information was dumped to the trace file.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38712, 00000, "Corrupt flashback log record header: block %s, offset %s."
// *Cause: A corrupt flashback database log record header was read.
// Either the record type or length were incorrect.
// More information was dumped to the trace file.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38713, 00000, "Flashback Database logging is already turned on."
// *Cause: An ALTER DATABASE FLASHBACK ON command had no effect
// because flashback database logging was already on.
// *Action: No action required.
38714, 00000, "Instance recovery required."
// *Cause: An ALTER DATABASE FLASHBACK ON command failed because the
// database either crashed or was shutdown with the ABORT
// option.
// *Action: Open the database and then enter the SHUTDOWN command with the
// NORMAL or IMMEDIATE option.
38715, 00000, "Invalid log number specified in the DUMP FLASHBACK command."
// *Cause: An invalid log number was used when dumping a flashback database
// log file.
// *Action: Specify a valid flashback database log number.
38716, 00000, "Must supply an integer for the TYPE option."
// *Cause: An invalid value was specified for TYPE in the DUMP FLASHBACK
// command.
// *Action: Specify an integer value.
38717, 00000, "Invalid DUMP FLASHBACK option."
// *Cause: An invalid option was specified in the DUMP FLASHBACK
// command. Currently the only options allowed are: DBA,
// TYPE, and LOGICAL.
// *Action: Retry the command with the correct options.
38718, 00000, "Invalid thread number specified in the DUMP FLASHBACK command."
// *Cause: An invalid thread number was used in dumping the flashback database
// log files for a thread.
// *Action: Specify a valid thread number.
38719, 00000, "Invalid DUMP FLASHBACK object."
// *Cause: An invalid object was specified in a DUMP FLASHBACK
// command. Currently the only objects allowed are: LOGFILE
// or THREAD.
// *Action: Retry the command with the correct options.
38720, 00000, "Missing log file name or number."
// *Cause: A log file name or number was missing in a DUMP FLASHBACK LOGFILE
// command.
// *Action: Supply a valid log file name or number.
38721, 00000, "Invalid file number."
// *Cause: An invalid file number was specified in the DBA clause of a
// DUMP FLASHBACK command.
// *Action: Supply a valid file number.
38722, 00000, "ON or OFF expected."
// *Cause: The ALTER DATABASE FLASHBACK command was specified without
// the ON or OFF keyword.
// *Action: Retry the command with the ON or OFF keyword.
38723, 00000, "Invalid SCN expression."
// *Cause: The SCN keyword was specified in a FLASHBACK DATABASE command
// but the SCN expression was invalid.
// *Action: Retry the command using a valid SCN number.
38724, 00000, "Invalid option to the FLASHBACK DATABASE command."
// *Cause: An invalid option was specified to the FLASHBACK DATABASE command.
// Valid options are: SCN or TIMESTAMP.
// *Action: Correct the syntax and retry the command.
38725, 00000, "specified name \"%s\" does not match actual \"%s\""
// *Cause: The database name specified in a FLASHBACK DATABASE command
// did not match the name of the currently mounted database.
// *Action: Correct the database name spelling or DISMOUNT the mounted
// database and mount the correct database.
38726, 00000, "Flashback database logging is not on."
// *Cause: A FLASHBACK DATABASE command was tried but flashback database
// logging has not been enabled.
// *Action: Flashback database logging must be enabled via the ALTER
// DATABASE FLASHBACK ON command before a FLASHBACK DATABASE command
// can be tried. If the database must be taken back in time then
// a restore and incomplete recovery must be performed.
38727, 0000, "FLASHBACK DATABASE requires a current control file."
// *Cause: The control file being used is a backup control file.
// *Action: FLASHBACK DATABASE cannot be used with a backup control
// file. If the database must be taken back in time then a
// restore and an incomplete recovery must be performed.
38728, 00000, "Cannot FLASHBACK DATABASE to the future."
// *Cause: An SCN or time stamp provided in a FLASHBACK DATABASE command
// was in the future.
// *Action: Supply a proper SCN or time stamp and retry the command.
38729, 00000, "Not enough flashback database log data to do FLASHBACK."
// *Cause: There was not enough flashback database log data to do the
// FLASHBACK DATABASE.
// *Action: If the database must be taken back in time then a restore and
// incomplete recovery must be performed.
38730, 00000, "Invalid SCN/TIMESTAMP expression."
// *Cause: The expression supplied in a FLASHBACK DATABASE command
// was invalid.
// *Action: Retry the command using a valid number or time stamp expression.
38731, 00000, "Expected version %s does not match %s in log header."
// *Cause: The version of the flashback database log file header was
// corrupt.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38732, 00000, "Expected file size %s does not match %s."
// *Cause: The file size indicated in the control file did not match
// the file size contained in the flashback log file header.
// The flashback database log file was corrupt.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38733, 00000, "Physical size %s less than needed %s."
// *Cause: A flashback database log file shrank in size. This
// was likely to have been caused by operator or operating
// system error.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38734, 00000, "Flashback log is inconsistent; belongs to another database."
// *Cause: The database ID in the flashback database log file did
// not match the database ID in the control file.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38735, 00000, "Wrong log number %s in flashback log file header."
// *Cause: The log file number in the flashback database log file
// did not match the control file.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38736, 00000, "Wrong thread number %s in flashback log file header."
// *Cause: The thread number in the flashback database log file
// did not match the control file.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38737, 00000, "Expected sequence number %s doesn't match %s"
// *Cause: The flashback database log is corrupted or is an old version.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38738, 00000, "Flashback log file is not current copy."
// *Cause: A check of flashback database log file header at database
// open found that the flashback database log appeared to be
// an incorrectly restored backup. Flashback database log
// files cannot be backed up and restored.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38739, 00000, "Flashback log file is more recent than control file."
// *Cause: The control file change sequence number in the flashback
// database log file was greater than the number in the
// control file. This implies that the wrong control file
// was being used. Note that repeatedly causing this error
// can make it stop happening without correcting the real
// problem. Every attempt to open the database will advance the
// control file change sequence number until it is great enough.
// *Action: FLASHBACK DATABASE can only be used with the current
// control file. If it is not available, then a restore
// and an incomplete recovery must be performed instead.
38740, 00000, "Usable blocks value %s is not valid."
// *Cause: A flashback database log file header contained a usable
// blocks value greater than the file size. The flashback
// database log file file is corrupt.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38741, 00000, "Formatted blocks value %s is not valid."
// *Cause: The formatted blocks value in the flashback database
// log file was greater than the file size. The flashback
// database log file was corrupt.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38742, 00000, "Flashback log file has incorrect log reset status."
// *Cause: The flashback database log file header had log reset
// data that was different than the control file. The log
// was probably an incorrectly restored backup. Flashback
// database logs cannot be backed up.
// *Action: If you are doing a FLASHBACK DATABASE, then the flashback
// cannot be performed because of the corrupted log. A restore
// and an incomplete recovery must be performed instead.
38743, 00000, "Time/SCN is in the future of the database."
// *Cause: The Time/SCN provided in a FLASHBACK DATABASE command was in
// the future of the database.
// *Action: Retry the command with a correct Time/SCN or RECOVER the
// database.
38744, 00000, "file %s is not the same file seen at start of flashback"
// *Cause: A different copy of the file was accessed the last time FLASHBACK
// DATABASE looked at the file header. A backup of the file was
// restored or the meaning of the file name changed during
// FLASHBACK DATABASE.
// *Action:Ensure the correct file is available, then retry FLASHBACK
// DATABASE.
38745, 00000, "Simulate block corruption in krf_check_block()"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
38746, 00000, "error occurred while restoring data block (file# %s, block# %s)"
// *Cause: An error occurred during a FLASHBACK DATABASE command.
// See other errors on error stack.
// *Action: Investigate why the error occurred. It may be that the flashback
// database log data is corrupt. If so, a restore and an incomplete
// recovery must be performed instead.
38747, 00000, "corrupt before image (file# %s, block# %s)"
// *Cause: A corrupt data block before image was encountered during a
// FLASHBACK DATABASE command.
// *Action: The flashback log data is probably corrupt. If so, a restore
// and an incomplete recovery must be performed instead.
38748, 00000, "cannot flashback data file %s - file is in use or recovery"
// *Cause: An attempt to do FLASHBACK DATABASE found that the file was not
// available for recovery. Either it was online and the
// database was open in some instance, or another process was
// currently doing media recovery or flashback on the file.
// *Action: Do not do FLASHBACK DATABASE.
38749, 00000, "A media recovery has been started."
// *Cause: An attempt was made to start a FLASHBACK DATABASE in the
// same session as a media recovery.
// *Action: Complete or cancel the first media recovery session.
38750, 00000, "FLASHBACK DATABASE may not be performed using a dispatcher."
// *Cause: An attempt was made to use a dispatcher process for FLASHBACK
// DATABASE. Memory requirements disallow this recovery method.
// *Action: Connect to the instance via a dedicated server process to
// perform FLASHBACK DATABASE.
38751, 00000, "Flashback database log: \"%s\""
// *Cause: This message reports the filename for details of another message.
// *Action: Other messages will accompany this message. See the associated
// messages for the appropriate action to take.
38752, 00000, "file %s does not exist"
// *Cause: During an RMAN FLASHBACK DATABASE conversation, a file was listed
// which was not part of the database. The RMAN conversation
// was aborted.
// *Action: Retry the conversation with the appropriate file numbers.
38753, 00000, "Cannot flashback data file %s; no flashback log data."
// *Cause: An attempt to perform a FLASHBACK DATABASE failed because the file
// does not have enough flashback log data to cover the time to
// flash back. Either the file did not have flashback generation
// enabled for it, or had flashback generation turned off for it
// some time during the time span of the flashback.
// *Action: The file cannot be flashed back. The file must be taken offline
// or the tablespace dropped before continuing with the FLASHBACK
// DATABASE command.
38754, 00000, "FLASHBACK DATABASE not started; required redo log is not available"
// *Cause: A FLASHBACK DATABASE command did not start. A redo log needed for
// the recovery part of FLASHBACK DATABASE could not be found or
// accessed.
// *Action: See trace files for details of the problem.
38755, 00000, "Flashback is already turned on for this tablespace."
// *Cause: An attempt was made to turn on flashback database logging
// for a tablespace that already has flashback turned on.
// *Action: No action required.
38756, 00000, "Flashback is already turned off for this tablespace."
// *Cause: An attempt was made to turn off flashback database logging
// for a tablespace that already has flashback off.
// *Action: No action required.
38757, 00000, "Database must be mounted and not open to FLASHBACK."
// *Cause: An attempt to Flashback a database was made when the
// database was not mounted or was already open.
// *Action: Mount the database and retry the FLASHBACK command.
38758, 00000, "cannot flashback data file %s; restored since last recovery"
// *Cause: An attempt to do FLASHBACK DATABASE found that the file was
// restored since the last standby recovery. The file cannot be
// flashed back.
// *Action: The file must be taken offline before continuing with the
// FLASHBACK DATABASE command.
38759, 00000, "Database must be mounted by only one instance and not open."
// *Cause: An attempt to turn on or off Flashback Database logging was
// made when the database was open or mounted by more than one
// instance.
// *Action: Mount the database in only one instance and retry the command.
38760, 00000, "This database instance failed to turn on flashback database"
// *Cause: Database flashback is on but this instance failed to
// start generating flashback data. Look in alert log for more
// specific errors.
// *Action: Correct the error or turn off database flashback.
38761, 00000, "redo log sequence %s in thread %s, incarnation %s could not be accessed"
// *Cause: A redo log needed for the recovery portion of FLASHBACK could not
// be read or opened. The FLASHBACK operation failed.
// *Action: Restore the log and retry the FLASHBACK command.
38762, 00000, "redo logs needed for SCN %s to SCN %s"
// *Cause: The FLASHBACK DATABASE operation failed. The recovery portion of
// FLASHBACK DATABASE needed redo from the first SCN to the second,
// but one or more of the redo logs in the range could not be read or
// opened.
// *Action: Check the FLASHBACK DATABASE command trace file for a
// description of the inaccessible redo logs, restore access to
// them, and retry the FLASHBACK DATABASE command.
38763, 00000, "flashback not started; enabled threads have changed"
// *Cause: A FLASHBACK DATABASE command did not start. The set of enabled
// threads changed during the time to flash back.
// *Action: The flashback cannot be performed. Perform a restore and
// an incomplete recovery instead.
38764, 00000, "flashback not started; datafile %s enabled threads are different"
// *Cause: A FLASHBACK DATABASE command did not start. The datafile was
// restored from a backup taken when the enabled threads were different
// than at the time of the flashback.
// *Action: The flashback cannot be performed. Perform a restore and an
// incomplete recovery instead.
38765, 00000, "Flashed back database cannot be opened read-only."
// *Cause: A complete recovery was performed after a database flashback
// but the database was not opened for read-write access, or
// a FLASHBACK DATABASE command failed.
// *Action: If a complete recovery was performed after a database flashback,
// open the database for read-write access. If a FLASHBACK DATABASE
// command failed, fix what caused the command to fail and retry
// the command, or recover and open the database for read-write
// access.
38766, 00000, "cannot flashback data file %s; file resized smaller"
// *Cause: An attempt to do FLASHBACK DATABASE found that the file was
// shrunk during the time to flash back.
// *Action: The file cannot be flashed back. The file must be taken offline
// or the tablespace dropped before continuing with the FLASHBACK
// DATABASE command.
38767, 00000, "flashback retention target parameter mismatch"
// *Cause: The value of parameters DB_FLASHBACK_RETENTION_TARGET must be
// same in all instances. All databases must have same flashback
// retention target parameters.
// *Action: Check DB_FLASHBACK_RETENTION_TARGET values in all instances.
38768, 00000, "resizing datafile %s failed"
// *Cause: An operating system error occurred when Flashback Database tried
// to shrink (resize) a datafile. Flashback shrinks a file in order
// to undo the effects of a file expand, for example, an
// autoextension of the file.
// *Action: Recover the database to return it to its previous state, or fix
// the cause of the operating system error and retry the Flashback.
// If that is not possible, then the file can be taken offline and
// the Flashback command retried. The file will have to be restored
// from a backup and rolled forward.
38769, 00000, "FLASHBACK DATABASE failed after modifying data."
// *Cause: A FLASHBACK DATABASE command failed after modifying the
// the database. Look in the alert log for more information
// about the failure.
// *Action: Recover the database to return it to its previous state, or fix
// the cause of the error and retry the Flashback.
38770, 00000, "FLASHBACK DATABASE failed during recovery."
// *Cause: A FLASHBACK DATABASE command successfully restored the database
// but failed during the recovery step. Look in the alert log for
// more information about the failure.
// *Action: Fix the error and then recover the database to the same SCN or
// timestamp used in the FLASHBACK DATABASE command.
38771, 00000, "unnamed datafile(s) added to control file by flashback recovery"
// *Cause: The recovery step of FLASHBACK DATABASE encountered the creation
// of a datafile that could not be added to the control file.
// An entry has been added to the control file for the new
// datafile, but with the file name UNNAMEDnnnn, where nnnn
// is the file number. Related error messages provide the file
// names that were originally used to create the files.
// *Action: Rename the file in the control file, or use the ALTER
// ALTER DATABASE CREATE DATAFILE command to create a file
// suitable for recovery. If the file is not going to be
// recovered, then take it offline with the FOR DROP option.
// The recovery step of Flashback can be resumed by entering
// a RECOVERY command with the same SCN or timestamp as used
// in the FLASHBACK DATABASE command. For example,
// RECOVER AUTOMTAIC DATABASE UNTIL CHANGE <flashback-scn>.
38772, 0000, "cannot add datafile '%s' - file could not be created"
// *Cause: The recovery step of FLASHBACK DATABASE encountered the
// creation of a datafile and could not recreate the file.
// The error from the creation attempt is displayed in another message.
// The control file file entry for the file is 'UNNAMEDnnnnn'.
// *Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the
// file.
38773, 00000, "cannot add data file '%s' - file already part of database"
// *Cause: The recovery step of FLASHBACK database encountered the
// creation of a datafile and could not create the file
// because the file name is already in use in the database.
// The control file file entry for the file is 'UNNAMEDnnnnn'.
// *Action: Use the ALTER DATABASE CREATE DATAFILE statement to create
// the file with a different name.
38774, 00000, "cannot disable media recovery - flashback database is enabled"
// *Cause: An attempt was made to disable media recovery while flashback
// database was enabled.
// *Action: Use the ALTER DATABASE FLASHBACK OFF statement to disable
// flashback database, then disable media recovery.
38775, 00000, "cannot disable recovery area - flashback database is enabled"
// *Cause: An attempt was made to set DB_RECOVERY_FILE_DEST to null while
// flashback database was enabled. Flashback database requires
// DB_RECOVERY_FILE_DEST to be set.
// *Action: Use the ALTER DATABASE FLASHBACK OFF statement to disable
// flashback database, then disable the recovery area.
38776, 00000, "cannot begin flashback generation - recovery area is disabled"
// *Cause: During a database mount, the RVWR process discovered that the
// recovery area was disabled. DB_RECOVERY_FILE_DEST must have
// been set null or removed from the INIT.ORA file while the database
// was unmounted.
// *Action: Flashback database requires the recovery area to be enabled.
// Either enable the recovery area by setting the
// DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE initialization
// parameters, or turn off flashback database with the
// ALTER DATABASE FLASHBACK OFF command.
38777, 00000, "database must not be started in any other instance"
// *Cause: A command was attempted that required the database to be mounted
// in this instance and not started in any other instance. ALTER
// DATABASE OPEN RESETLOGS requires that the database be started in
// only one instance if flashback database logging is enabled.
// *Action: Ensure that the no other instances are started. Then retry the
// command.
38778, 00000, "Restore point '%s' already exists."
// *Cause: The restore point name of the CREATE RESTORE POINT command already
// exists. A restore point name must be unique.
// *Action: Either use a different name or delete the existing restore
// point with the same name.
38779, 00000, "cannot create restore point - too many restore points."
// *Cause: The maximum number of restore points already have been created.
// *Action: Delete some existing restore point and retry the operation.
38780, 00000, "Restore point '%s' does not exist."
// *Cause: The restore point name specified in the command did not exist.
// *Action: Look up restore points by query restore point tables.
38781, 00000, "cannot disable media recovery - have guaranteed restore points"
// *Cause: An attempt was made to disable media recovery while there is at
// least one guaranteed restore point.
// *Action: Drop all guaranteed restore points and then disable media recovery.
38782, 00000, "cannot flashback database to non-guaranteed restore point '%s'"
// *Cause: An attempt was made to flashback database to a non-guaranteed
// restore point while flashback database is off. You can only
// flashback a database to guaranteed restore point when flashback
// database is not on.
// *Action: Consider picking a guaranteed restore point to flashback the
// database to, if there is one.
38783, 00000, "Instance recovery required."
// *Cause: An attempt was made to create a restore point when the database
// is in mount mode but it was not shutdown cleanly before it was
// mounted. In order to create a restore point when the database
// is mounted, the database must be shutdown cleanly before it is
// mounted.
// *Action: Consider one of the following:
// 1. Create the restore point after opening the database.
// 2. Open the database, shut it down cleanly, mount the database,
// and retry creating the restore point.
38784, 00000, "Cannot create restore point '%s'."
// *Cause: An attempt to create a restore point failed. See other errors
// on the error stack and in the alert log for the specific reason.
// *Action: Fix the problem and retry.
38785, 00000, "Media recovery must be enabled for guaranteed restore point."
// *Cause: Media recovery is not enabled. Media recovery must be enabled
// in order to create a guaranteed restore point.
// *Action: Turn on media recovery with an ALTER DATABASE ARCHIVELOG
// statement and then retry the command.
38786, 00000, "Recovery area is not enabled."
// *Cause: An attempt was made to perform a command that requires Flash
// recovery area to be enabled.
// *Action: Set DB_RECOVERY_FILE_DEST to an appropriate location and retry.
38787, 00000, "Creating the first guaranteed restore point requires mount mode when flashback database is off."
// *Cause: While flashback database is not on, an attempt was made to
// create the first guaranteed restore point while the database
// is open.
// *Action: Mount the database and retry.
38788, 00000, "More standby database recovery is needed"
// *Cause: An attempt was made to create a restore point or a guaranteed
// while a physical standby database is not cleanly checkpointed.
// *Action: Perform more standby database recovery via managed standby
// database recovery. Cancel managed recovery and retry the command.
38789, 00000, "File name is too long."
// *Cause: The file name provided in the command was longer than the
// maximum allowed.
// *Action: Use a shorter file name.
38790, 00000, "BEFORE must be specified with RESETLOGS"
// *Cause: The FLASHBACK DATABASE command included the RESETLOGS parameter
// but not the BEFORE parameter.
// *Action: Retry the command with TO BEFORE RESETLOGS.
38791, 00000, "flashback did not start because file %s was not in a valid incarnation"
// *Cause: Flashback could not be started because a file was checkpointed
// or fuzzy at a point where the file can neither be restored nor recovered
// to our restore target. In order for a file to be brought to
// the restore target, the file has to be in one of the incarnations
// along the ancestral path from the current incarnation to the restore
// incarnation.
// *Action: Manually restore or recover the file to a point where it is in
// one of the incarnations along the ancestral path from the current
// incarnation to the restore incarnation.
38792, 00000, "encountered unknown flashback record from release %s"
// *Cause: A Flashback Database logfile contains a record written by
// a future Oracle release and is unknown by this release.
// *Action: The given release of Oracle must be installed in order
// to use these flashback database log files.
38793, 00000, "cannot FLASHBACK the database or pluggable database to a future SCN or time"
// *Cause: The Flashback Pluggable Database target SCN or timestamp is greater
// than the current database or pluggable database SCN/timestamp and
// the database or pluggable database incarnation is not the last
// opened incarnation.
// *Action: If the target SCN or timestamp is in the current incarnation
// or a child incarnation whose branch point is after the
// current database or pluggable database SCN then RECOVER DATABASE
// or RECOVER PLUGGABLE DATABASE to the target SCN or time. If the
// target SCN or timestamp is in a child incarnation whose branch
// point is prior to the current database or pluggable database SCN
// then FLASHBACK DATABASE to before the branch point. Next, use RMAN
// to reset the database or pluggable database to the child
// incarnation. Finally, RECOVER DATABASE OR PLUGGABLE DATABASE to
// the target SCN time.
38794, 00000, "Flashback target time not in current incarnation"
// *Cause: The Flashback Database target timestamp is not in the
// database's current incarnation or any of its ancestors.
// *Action: Use a different target timestamp or use RMAN to reset
// the database to the appropriate incarnation.
38795, 00000, "WARNING: FLASHBACK DATABASE succeeded but OPEN RESETLOGS would fail"
// *Cause: FLASHBACK DATABASE succeeded. However, if ALTER DATABASE
// OPEN RESETLOGS command was attempted now, it would fail with the
// specified error.
// *Action: Fix the error before trying ALTER DATABASE OPEN RESETLOGS.
38796, 00000, "Not enough flashback database log data to undo FLASHBACK."
// *Cause: There was not enough flashback log data to undo the flashback
// so a flashback was not started.
// *Action: It is still possible to get to the restore target by doing a flashback
// until the resetlogs branch point of the restore target
// is reached. This can be done by executing multiple "flashback
// to before resetlogs" commands, or by doing a flashback to the exact time
// or SCN of the desired resetlogs branch point. Note that this flashback
// cannot be undone should an error occur. The only option is to complete
// the flashback.
38797, 00000, "Full database recovery required after a database has been flashed back"
// *Cause: An attempt was made to recover some datafiles or tablespaces of a
// database after the database had been flashed back. In order to recover
// control file and all datafiles correctly, full database recovery is
// required after a database has been flashed back.
// *Action: Recover the whole database instead.
38798, 00000, "Cannot perform partial database recovery"
// *Cause: See other other messages on error stack for the cause.
// *Action: See other other messages on error stack for the action.
38799, 00000, "Cannot drop guaranteed restore point internally created for snapshot standby"
// *Cause: An attempt is made to drop the guaranteed restore point Oracle
// created internally for a snapshot standby.
// *Action: Use the "alter database convert to physical standby" command
// to convert the snapshot standby to a normal physical standby.
// This will automatically flashback the database and drop this
// guaranteed restore point.
38800, 00000, "Cannot start Redo Apply on the open physical standby database"
// *Cause: An attempt was made to start Redo Apply on an open physical
// standby database instance.
// *Action: Make sure the primary database is at compatibility 11.0.0 or
// higher. The redo logs to be recovered on an open physical standby
// database must be generated at compatibility 11.0.0 or higher. If
// you have any redo below 11.0.0 to be applied on the standby, you
// must apply them on a mounted standby before restarting recovery on
// an open standby when the log format advances to 11.0.0 or higher.
// If this is a RAC standby database, make sure the
// ACTIVE_INSTANCE_COUNT parameter is not set.
///////////////////////////// APPLICATION EDITION
// Error numbers 38801 to 38849 are reserved for Application Edition work.
/
//////////////////////////////
38801, 00000, "improper value for ORA_EDITION"
// *Cause: An improper value was used for ORA_EDITION when trying to
// specify an edition to use at login time. The value is not
// understandable as an identifier, or is too long.
// *Action: Correct the value for ORA_EDITION and try again.
38802, 00000, "edition does not exist"
// *Cause: This error occurred because a reference was made to an edition that
// does not exist or that the current user does not have privileges on.
// *Action: Check the edition name and verify that the current user has
// appropriate privileges on the edition.
38803, 00000, "edition is unusable"
// *Cause: This error occurred because a reference was made to an unusable
// edition.
// *Action: Use another edition.
38804, 00000, "not a legal edition name"
// *Cause: This error occurred because an attempt was made to create an
// edition called ORA$BASE, DATABASE_DEFAULT, or USER_DEFAULT. These
// are not legal edition names. Or a value provided as an edition
// name is not understandable as an identifier, or is too long.
// *Action: Choose a different name for the edition.
38805, 00000, "edition is in use"
// *Cause: An attempt was made to ALTER or DROP an edition that was being
// used in another session or was the database default edition.
// *Action: Retry when the edition is not in use and is not the database
// default edition.
38806, 00000, "edition is being altered or dropped"
// *Cause: An attempt was made to use an edition that was in the process of
// being altered or dropped.
// *Action: Use a different edition.
38807, 00000, "Implementation restriction: an edition can have only one child"
// *Cause: This error occurred because an attempt was made to create more
// than one child edition for a parent edition.
// *Action: Create the edition as a child of the leaf edition.
38808, 00000, "edition has a usable parent and a usable child"
// *Cause: An attempt was made to make an edition with a usable parent and a
// usable child edition unusable.
// *Action: An edition with a usable parent and a usable child edition cannot
// be made unusable. Retry after either parent or child has been made
// unusable.
38809, 00000, "edition must be unusable"
// *Cause: This error occurred because an attempt was made to drop a usable
// edition.
// *Action: Retry after the altering the edition to be unusable.
38810, 00000, "Implementation restriction: cannot drop edition that has a parent and a child"
// *Cause: This error occurred because an attempt was made to drop an edition
// that has a parent and a child edition.
// *Action: Retry after dropping the parent or child edition.
38811, 00000, "need CASCADE option to drop edition that has actual objects"
// *Cause: This error occurred because an attempt was made to drop an edition
// that has actual objects.
// *Action: Specify CASCADE option in drop command.
38812, 00000, "maximum number of editions reached"
// *Cause: The number of editions has reached the limit.
// *Action: Drop some editions before creating new ones.
38813, 00000, "editions not supported for schema %s"
// *Cause: The Oracle-supplied schema did not support editions.
// *Action: Do not attempt to enable editions for the specified
// Oracle-supplied schema.
38814, 00000, "ALTER SESSION SET EDITION must be first statement of transaction"
// *Cause: An attempt was made to execute an edition switch within an open transaction.
// *Action: Commit or rollback the transaction and reexecute the statement,
// or use DBMS_SESSION.SET_EDITION_DEFERRED if its deferred effect is
// appropriate.
38815, 00000, "ALTER SESSION SET EDITION must be a top-level SQL statement"
// *Cause: An edition switch failed because it was executed from a
// PL/SQL block or using recursive SQL.
// *Action: Execute the statement from a top-level OCI call,
// or use dbms_session.set_edition if its deferred effect is
// appropriate.
38816, 00000, "edition has a child that inherits objects from the edition"
// *Cause: This error occurred because an attempt was made to drop an edition
// that a child that inherits objects from the edition.
// *Action: Retry after the child edition has no inherited objects.
38817, 00000, "Insufficient privileges"
// *Cause: You did not have sufficient privileges to execute the
// subprogram package DBMS_EDITIONS_UTIL.
// *Action: Obtain the necessary privileges. Please see the package
// specification for details.
38818, 00000, "illegal reference to editioned object %s.%s"
// *Cause: An attempt was made to violate the rule "A noneditioned object
// may not depend on an editioned object."
// *Action: Either make this object editioned; or do not make the illegal
// reference.
38819, 00000, "user %s owns one or more objects whose type is editionable and that have noneditioned dependent objects"
// *Cause: An attempt was made to violate the rule "A noneditioned object
// may not depend on an editioned object."
// *Action: Either make sure that those objects owned by this user whose type
// is editionable have no noneditioned dependent objects; or use the
// FORCE option.
38820, 00000, "user has evolved object type"
// *Cause: User could not be edition enabled if it has evolved object type.
// *Action: Reset the evolved object type first.
38821, 00000, "unsupported DBMS_SQL Edition operation"
// *Cause: Could not bind or define ADT, VARRAY, nested table or REF data type
// when the specified Edition is different from the current edition.
// *Action: Use the current Edition.
38822, 00000, "referential integrity constraints not allowed on editioned views"
// *Cause: An attempt was made to create a referential integrity constraint
// to or from an editioned view or enable editions for a user that
// has views with referential integrity constraints.
// *Action: Do not attempt to create editioned views with referential
// integrity constraints.
38823, 00000, "Crossedition triggers are not allowed to exist when dropping the root edition"
// *Cause: An attempt was made to drop the root edition when enabled
// crossedition trigger exists.
// *Action: Drop or disable all the crossedition triggers before dropping the
// root edition.
38824, 00000, "A CREATE OR REPLACE command may not change the EDITIONABLE property of an existing object."
// *Cause: An attempt was made to replace an existing object with a different
// value for the EDITIONABLE property.
// *Action: Switch the EDITIONABLE property in the REPLACE statement, or alter
// the existing object to have an EDITIONABLE property matching the
// EDITIONABLE property in the REPLACE statement.
38825, 00000, "The EDITIONABLE property of an editioned object cannot be altered."
// *Cause: An attempt was made to alter the EDITIONABLE property of an object
// whose type has been enabled for editioning in the owner's schema.
// *Action: Drop the object and re-create it with the desired EDITIONABLE
// state.
38826, 00000, "The EDITIONABLE property of a TYPE or PACKAGE specification and its body must match."
// *Cause: An attempt was made to create a TYPE or PACKAGE specification or body
// whose EDITIONABLE property did not match its counterpart.
// *Action: Switch the EDITIONABLE property in the CREATE statement, or alter
// the existing object to have an EDITIONABLE property matching the
// EDITIONABLE property in the CREATE statement.
38827, 00000, "DBMS_SESSION.SET_EDITION_DEFERRED failed due to change of PDB."
// *Cause: An edition switch failed because an attempt was made to change
// pluggable database (PDB) before the edition switch took effect.
// *Action: Do not change PDB before the edition switch takes effect.
/
38828, 00000, "DBMS_SESSION.USE_DEFAULT_EDITION_ALWAYS mode is on."
// *Cause: A change of the session-level edition failed because the
// overriding USE_DEFAULT_EDITION_ALWAYS mode was on.
// *Action: Do not change the session-level edition, or first turn off
// USE_DEFAULT_EDITION_ALWAYS mode.
/
38829, 00000, "FLASHBACK DATABASE failed before modifying any data."
// *Cause: The FLASHBACK DATABASE command failed before modifying the
// the database. Look in the alert log for more information
// about the failure.
// *Action: Fix the cause of the error and retry the FLASHBACK DATABASE
// command.
38850, 00000, "an enabled thread missing from control file"
// *Cause: A CREATE CONTROLFILE statement was given that did not
// list all the enabled threads for the database.
// *Action: Reissue the CREATE CONTROLFILE statement, including all enabled
// threads.
38851, 00000, "cannot mark the current instance (redo thread) as disabled"
// *Cause: The standby switchover or failover operation failed because it
// needs to mark the current instance (redo thread) as disabled.
// *Action: Shut down this instance and start up using a different instance
// name or redo thread number and retry.
38852, 00000, "cannot mark the current instance (redo thread) as disabled"
// *Cause: The open resetlogs or standby activation operation failed because
// it must use a different instance (redo thread) than the current
// instance (redo thread) to open the database.
// *Action: Shut down this instance and start up using a different instance
// name or redo thread number and retry.
38853, 00000, "cannot mark instance %s (redo thread %s) as disabled"
// *Cause: The standby switchover or failover operation failed because it
// needs to mark an instance (redo thread) as disabled. That instance
// was up, which prevented it from being disabled.
// *Action: Shut down the specified instance and retry this command.
38854, 00000, "cannot mark instance %s (redo thread %s) as disabled"
// *Cause: The open resetlogs or standby activation operation failed because
// it needs to mark an instance (redo thread) as disabled. That
// instance was up, which prevented it from being disabled.
// *Action: Shut down the specified instance and retry this command.
38855, 00000, "cannot mark instance %s (redo thread %s) as enabled"
// *Cause: The standby switchover or failover operation failed because it
// needs to mark an instance (redo thread) as enabled. However, it
// had less than 2 online redo logs, which prevented it from being
// enabled.
// *Action: Add more logfiles to the specified instance and retry the command.
38856, 00000, "cannot mark instance %s (redo thread %s) as enabled"
// *Cause: The open resetlogs or standby activation operation failed because
// it needs to mark an instance (redo thread) as enabled. However, it
// had less than 2 online redo logs, which prevented it from being
// enabled.
// *Action: Add more logfiles to the specified instance and retry the command.
38857, 00000, "cannot mark redo thread %s as enabled"
// *Cause: The standby switchover or failover operation failed because it
// needs to mark a redo thread as enabled. However, the control file
// was recreated with a MAXINSTANCES value smaller than the thread
// number of the redo thread.
// *Action: Recreate the control file with a larger MAXINSTANCES value.
38858, 00000, "cannot mark redo thread %s as enabled"
// *Cause: The open resetlogs or standby activation operation failed because
// it needs to mark a redo thread as enabled. However, the control file
// was recreated with a MAXINSTANCES value smaller than the thread
// number of the redo thread.
// *Action: Recreate the control file with a larger MAXINSTANCES value.
38859, 00000, "instance %s (thread %s) is not ready to be disabled"
// *Cause: The command attempted to switch the instance (thread) into a new
// log before disabling it. The switch attempt failed because all
// eligible online logs were either being cleared or not completely
// archived yet.
// *Action: Wait a few minutes and retry.
38860, 00000, "cannot FLASHBACK DATABASE during instantiation of a logical standby"
// *Cause: The command was not permitted because the controlfile indicates
// the database was in the process of becoming a logical standby database
// but the controlfile conversion had not completed.
// *Action: If in the process of creating a logical standby database, perform the
// remaining instantiation procedures to completion. If this flashback
// operation followed a Data Guard failure, permit the errant Data Guard
// operation to successfully complete. Once the instantiation is
// complete, reissue the flashback operation.
38861, 00000, "flashback recovery stopped before reaching recovery target"
// *Cause: Flashback recovery on the standby ended early because the
// user attempted to flashback to an SCN or time for which there were no
// redo logs. Most likely, the user is trying to flashback to a future
// time in the database that the database has never recovered through.
// Check the alert log to find out which SCN the database recovered to.
// *Action: Flashback to an older SCN or acquire the necessary redo logs.
38862, 00000, "Flashback database logs are in use."
// *Cause: The command could not be performed because the flashback database
// logs were locked by another operation, such as FLASHBACK DATABASE
// or a query of V$FLASHBACK_DATABASE_LOG.
// *Action: Wait for the other operation to complete.
38863, 00000, "datafile %s has been restored from an optimized RMAN backup."
// *Cause: Flashback Database could not flash back the file because it
// was restored from an RMAN optimized backup with deallocated
// objects. Flashback cannot revert the file to a time before
// the last deallocation in the datafile backup.
// *Action: Restore the file from a backup prior to the Flashback target
// SCN or time and then retry the command.
38864, 00000, "cannot create a guaranteed restore point with user specified SCN or time."
// *Cause: An SCN or timestamp was specified when creating a guaranteed
// restore point. This is not supported. You can only create a
// guaranteed restore point as of the current time.
// *Action: Avoid this combination of options for creating a restore point.
38865, 00000, "cannot create restore point for a future SCN or time."
// *Cause: An attempt was made to create a restore point with an SCN or
// timestamp that is in the future.
// *Action: Revise the SCN or timestamp specified so that it is an SCN or
// timestamp in the past.
38866, 00000, "cannot create restore point for an SCN or time before current database incarnation."
// *Cause: An attempt was made to create a restore point with an SCN or
// timestamp that is before the beginning of the current database
// incarnation.
// *Action: Revise the SCN or timestamp specified so that it is within current
// database incarnation.
38867, 00000, "database not open: cannot create restore point with the specified timestamp"
// *Cause: An attempt was made to create a restore point with the specified
// timestamp while the database was not open. The database must be
// open in order to map the timestamp to an SCN.
// *Action: Open the database first or pick another way to create the restore
// point.
38868, 00000, "warning: the control file may have incorrect data file structure"
// *Cause: This control file was created or converted based on a control file
// from a time different from the time of the database.
// *Action: Open database and all pluggable databases read-only to synchronize
// the control file with the database dictionary. You can also force
// recovery to proceed by invoking recovery again.
38869, 00000, "datafile %s has been restored from an RMAN backup with undo block compression."
// *Cause: Flashback Database could not flash back the database because a
// file was restored from an RMAN backup with undo block compression,
// and the Flashback target was to a time when the missing undo may
// be needed to open the database.
// *Action: Restore an earlier backup of the file and retry the command
// or Flashback to a later time.
38870, 00000, "cannot backup a control file that may have incorrect data file structure."
// *Cause: This control file was created or converted based on a control file
// from a time different from the time of the database.
// *Action: Open database read-only to synchronize the control file with the
// database dictionary to fix the control file.
38871, 00000, "cannot enable flashback before open resetlogs after incomplete recovery."
// *Cause: To enable flashback on a primary database, the database must be
// clean without requiring open resetlogs.
// *Action: Open resetlogs first and then enable flashback database.
38872, 00000, "Cannot perform backup control file recovery if Flashback Database is enabled."
// *Cause: RECOVER DATABASE with the BACKUP CONTROLFILE option, or a
// database recovery that required the control file be made a backup
// failed because Flashback Database was enabled or there was a
// guaranteed restore point.
// *Action: Disable Flashback Database or remove the guaranteed restore point
// and retry the command.
38873, 00000, "missing incarnation information"
// *Cause: Flashback Database failed because incarnation information was not
// found in the control file. The Flashback target incarnation was not
// in the control file or had a missing parent incarnation.
// *Action: Register logs from the missing incarnations and retry the command.
38874, 00000, "cannot flashback data file %s - missing incarnation information"
// *Cause: Flashback Database failed because incarnation information for the
// start of the offline range for a file was not found in the control
// file. Flashback could not update the file's header with the missing
// incarnation's resetlogs information.
// *Action: Check the trace log for the offline range of the data file.
// If redo logs from the missing incarnation can be found, register
// the logs in the control file and retry the command.
38875, 00000, "FLASHBACK DATABASE not started; in test mode"
// *Cause: The FLASHBACK DATABASE command was not performed because it was
// started in test mode.
// *Action: No action required.
38876, 00000, "redo logs not required"
// *Cause: The FLASHBACK DATABASE command was performed in test mode
// and determined that no redo logs were required to perform the
// tested FLASHBACK DATABASE command.
// *Action: No action required.
38877, 00000, "required redo logs are available"
// *Cause: The FLASHBACK DATABASE command was performed in test mode
// and determined that no redo logs required to perform the
// tested FLASHBACK DATABASE command were missing.
// *Action: No action required.
38878, 00000, "required redo log is not available"
// *Cause: A redo log needed for the recovery part of FLASHBACK DATABASE could
// not be found or accessed.
// *Action: See trace files for details of the problem.
38879, 00000, "Cannot flashback data file %s; may not be able to undo all changes."
// *Cause: A data file was plugged in when there was a guaranteed restore
// point, but Flashback Database was not enabled. It is possible
// that some changes to the data file, after it was converted, were
// not logged to the Flashback Database logs.
// *Action: If the FLASHBACK DATABASE command was meant to rewind the database
// to a time before the file was plugged in, take the data file
// offline and retry the command. If the FLASHBACK DATABASE command
// was meant to rewind the database to a time after the file was
// plugged in, restore the original version of the plugged in file
// and retry the command.
38880, 00000, "Cannot advance compatibility from %s to %s due to guaranteed restore points"
// *Cause: Flashback database cannot undo the advance of database
// compatibility. Therefore, one cannot advance the compatibility
// of the database while there are guaranteed restore points in the
// database.
// *Action: Drop all guaranteed restore points first and retry, or delay
// the advance of database compatibility to a later time.
38881, 00000, "Cannot drop tablespace %s on primary database due to guaranteed restore points."
// *Cause: An attempt was made to drop a tablespace on a primary database while
// there are guaranteed restore points. You cannot do this because
// Flashback database cannot undo dropping of a tablespace.
// *Action: Drop all guaranteed restore points first and retry, or delay
// dropping the tablespace until all guaranteed restore points are
// removed.
38882, 00000, "Cannot drop tablespace %s on standby database due to guaranteed restore points."
// *Cause: An attempt was made to drop a tablespace on a standby database while
// there are guaranteed restore points. You cannot do this because
// Flashback database cannot undo dropping of a tablespace.
// *Action: Drop all guaranteed restore points and rerun recovery on standby database.
38883, 00000, "Cannot shrink data file %s on primary database due to guaranteed restore points."
// *Cause: An attempt was made to shrink a data file on a primary database while
// there are guaranteed restore points. You cannot do this because
// Flashback database cannot undo the shrinking of a data file.
// *Action: Drop all guaranteed restore points first and retry, or delay
// the data file resize until all guaranteed restore points are removed.
38884, 00000, "Cannot shrink data file %s on standby database due to guaranteed restore points."
// *Cause: An attempt was made to shrink a data file on a standby database while
// there are guaranteed restore points. You cannot do this because
// Flashback database cannot undo the shrinking of a data file.
// *Action: Drop all guaranteed restore points and rerun recovery on standby
// database.
38885, 00000, "WARNING: Flashback database has been disabled while fast-start failover is enabled."
// *Cause: Flashback database was disabled while fast-start failover was
// enabled.
// *Action: Enable flashback database if fast-start failover is enabled.
38886, 00000, "WARNING: Flashback database was disabled due to error when writing flashback database logs."
// *Cause: Recovery writer (RVWR) encountered an error when writing flashback database logs.
// *Action: See the error stack in the alert log.
38887, 00000, "WARNING: Recovery writer (RVWR) hang due to error when writing flashback database logs."
// *Cause: An error occurred while writing to the flashback database logs.
// *Action: Shutdown the instance or turn off flashback database.
38888, 00000, "invalid redo thread number"
// *Cause: The provided thread number was invalid.
// *Action: Specify a valid redo thread number.
/////////////////// DML Error Logging
// Error numbers 38900 to 38949 are reserved for DML Error Logging/DML hints
///////////////////
38900, 00000, "missing mandatory column \"%s\" of error log table \"%s\""
// *Cause: Mandatory column of error logging table is not present
// *Action : Add the named column to the error logging table.
// Consult ORACLE documentation for the correct data type.
//
38901, 00000, "column \"%s\" of table \"%s\" must be one of the first \"%s\" columns"
// *Cause: Mandatory information column of error logging table is present,
// but must be at the beginning of the row.
// *Action : Create the error logging table correctly.
// Consult ORACLE documentation for the correct format of an
// error logging table.
38902, 00000, "errors in array DML exceed %s"
// *Cause: The operation failed because the array DML had more errors
// than can be stored internally for BATCH ERRORs.
// *Action : Do not use BATCH ERROR mode when array DML has
// more error rows than the number specified in the error.
//
38903, 00000, "DML error logging is not supported for abstract column \"%s\""
// *Cause: A DML Error Logging operation was attempted on a table which has
// an ADT, REF, VARRAY, or nested table column type, and the
// error logging table referred to the specified column.
// *Action: Either do not use DML Error Logging on such a table or remove
// the offending column from the error logging table. The scalar
// columns can be logged, but not abstract column types.
//
38904, 00000, "DML error logging is not supported for LOB column \"%s\""
// *Cause: A DML Error Logging operation was attempted on a table which has
// a CLOB, NCLOB, or BLOB column type, and the error logging
// table referred to the specified column.
// *Action: Either do not use DML Error Logging on such table or remove
// the offending column from the error logging table. The scalar
// columns can be logged, but not LOB column types.
//
38905, 00000, "DML error logging is not supported for LONG column \"%s\""
// *Cause: A DML Error Logging operation was attempted on a table which has
// a LONG, or LONG RAW column type, and the error logging table
// referred to the specified column.
// *Action: Either do not use DML Error Logging on such a table or remove
// the offending column from the error logging table. The scalar
// columns can be logged, but not long column types.
//
38906, 00000, "insert into DML Error Logging table \"%s\" failed"
// *Cause: An error occurred when attempting to log a DML Error on behalf
// of the DML Error logging clause. This may be intended if
// a trigger is defined on the error table (which in turn errors
// out in certain cases).
// *Action: Determine root cause of error (in error stack).
//
38907, 00000, "DML error logging is not supported for FILE column \"%s\""
// *Cause: A DML Error Logging operation was attempted on a table which has
// a BFILE column and the Error Logging table referred to the
// specified column.
// *Action: Either don't use DML Error Logging on such table or remove
// the offending column from the error logging table. The scalar
// columns can be logged, but not BFILE column types.
//
38908, 00000, "internal error occurred during DML Error Logging"
// *Cause: An unexpected error occurred while executing recursive SQL
// to insert a row into the DML Error Logging table.
// *Action: Report this error to Oracle Support.
//
38909, 00000, "DML Error logging is not supported with BATCH ERROR mode"
// *Cause: A DML Error Logging operation was attempted on a table which has
// BATCH ERROR mode also specified.
// *Action: Refrain from using both DML Error Logging and BATCH ERROR
// mode on the same table.
//
38910, 00000, "BATCH ERROR mode is not supported for this operation"
// *Cause: BATCH ERROR mode specified for this operation.
// *Action: Refrain from using BATCH ERROR mode with this operation.
//
38911, 00000, "unique constraint (%s.%s) violated"
// *Cause: An INSERT statement with a CHANGE_DUPKEY_ERROR_INDEX
// hint tried to insert a duplicate key into a table.
// *Action: Either remove the unique restriction or do not insert the key.
//
38912, 00000, "An index must be specified in the index hint"
// *Cause: Index specification was missing in an IGNORE_ROW_ON_DUPKEY_INDEX
// or CHANGE_DUPKEY_ERROR_INDEX hint.
// *Action: In the hint, specify a unique index that exists on the table.
//
38913, 00000, "Index specified in the index hint is invalid"
// *Cause: The index specified in an IGNORE_ROW_ON_DUPKEY_INDEX or
// CHANGE_DUPKEY_ERROR_INDEX hint could not be found.
// *Action: Specify a unique index that exists on the table. The
// index cannot be a non-unique index or a bitmap index.
//
38914, 00000, "Either mutate the error or ignore row on unique violation"
// *Cause: IGNORE_ROW_ON_DUPKEY_INDEX and CHANGE_DUPKEY_ERROR_INDEX were
// both specified in the same statement.
// *Action: You cannot specify both hints in the same statement. Remove
// one of these two hints, or both, from the statement.
//
38915, 00000, "Multiple indexes in change or ignore duplicate key hint"
// *Cause: Multiple indexes were specified in an IGNORE_ROW_ON_DUPKEY_INDEX
// or CHANGE_DUPKEY_ERROR_INDEX hint.
// *Action: Only one index must be specified in the hint.
//
38916, 00000, "CHANGE_DUPKEY_ERROR_INDEX hint disallowed for this operation"
// *Cause: CHANGE_DUPKEY_ERROR_INDEX hint was specified for the operation.
// *Action: You cannot specify this hint for this operation. Remove the hint
// from the statement.
//
38917, 00000, "IGNORE_ROW_ON_DUPKEY_INDEX hint disallowed for this operation"
// *Cause: IGNORE_ROW_ON_DUPKEY_INDEX hint was specified for the operation.
// *Action: You cannot specify this hint for this operation. Remove the hint
// from the statement.
//
38918, 00000, "RETRY_ON_ROW_CHANGE hint disallowed for this operation"
// *Cause: RETRY_ON_ROW_CHANGE hint was specified for the operation.
// *Action: You cannot specify this hint for this operation. Remove the hint
// from the statement.
//
38919, 00000, "remote table not supported for DML error logging"
// *Cause: A remote table was specified in the DML error logging clause.
// *Action: You cannot specify a remote table to which errors will be logged.
// Specify a local table only.
//
/////////////////// Cross Platform Tablespace
// Error numbers 38950 to 38999 are reserved for Cross platform tablespace
///////////////////
38950, 00000, "Source platform %s not cross platform compliant"
// *Cause: Cross platform transport was not allowed for this platform.
// *Action: For a list of supported platforms, query fixed view
// SYS.V$TRANSPORTABLE_PLATFORM.
38951, 00000, "Target platform %s not cross platform compliant"
// *Cause: Cross platform transport was not allowed for this platform.
// *Action: For a list of supported platforms, query fixed view
// SYS.V$TRANSPORTABLE_PLATFORM.
// *Action:
38952, 00000, "Source database not 10.0.0.0 compatible"
// *Cause: Cross platform transport is not supported unless database
// compatibility is advanced to 10.0.0.0 or higher
// *Action: Use the compatible parameter to advance source database
// compatibility and redo the transport
38953, 00000, " Cross platform transport is not supported between source platform %s and target platform %s"
// *Cause:
// *Action: For a list of supported platforms, query fixed view
// SYS.V$TRANSPORTABLE_PLATFORM.
38954, 00000, "Cross platform transport is not supported between source platform identifier %s and target platform identifier %s"
// *Cause: The platform identifier in the transported file indicated that
// the datafile format was different than the target database
// datafile format.
// *Action: For a list of supported platforms, query fixed view
// SYS.V$TRANSPORTABLE_PLATFORM. If both platforms
// are present, Contact Oracle support
38955, 00000, "Source platform %s not cross platform compliant"
// *Cause: The platform identifier in the transported file indicated that
// this platform is not supported for a cross platform transport.
// *Action: For a list of supported platforms, query fixed view
// SYS.V$TRANSPORTABLE_PLATFORM.
38956, 00000, "Target platform %s not cross platform compliant"
// *Cause: Cross platform transport was not allowed for this platform.
// *Action: For a list of supported platforms, query fixed view
// SYS.V$TRANSPORTABLE_PLATFORM.
38958, 00000, "Source platform %s is in different byte order than target platform %s"
// *Cause: Probably a conversion was not done before the import phase
// of the transport.
// *Action: Use RMAN CONVERT functionality to convert endian ordering.
38959, 00000, "Failed to update block 0 to new version 10 format "
// *Cause: An attempt was made to update block 0 to version 10 format.
// *Action: check additional error messages and contact Oracle Support Services.
38960, 00000, "File %s from platform %s is not compatible with current platform %s"
// *Cause: The file was directly copied to this platform
// from a platform with a different endian ordering.
// *Action: Use RMAN CONVERT functionality to convert endian ordering.
38961, 00000, "data file: %s"
// *Cause: Reporting file name for details of another error.
// *Action: See associated error message.
//////////// Data Pump
/ Error numbers 39000 - 39499 are reserved for Data Pump
/ (continued from 31600 - 31699 range)
///////////
39000, 00000, "bad dump file specification"
// *Cause: The user specified a dump file that could not be used in the
// current job. Subsequent error messages describe the inadequacies
// of the dump file.
// *Action: Specify a dump file that is usable for the job.
39001, 00000, "invalid argument value"
// *Cause: The user specified API parameters were of the wrong type or
// value range. Subsequent messages supplied by
// DBMS_DATAPUMP.GET_STATUS will further describe the error.
// *Action: Correct the bad argument and retry the API.
39002, 00000, "invalid operation"
// *Cause: The current API cannot be executed because of inconsistencies
// between the API and the current definition of the job.
// Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS
// will further describe the error.
// *Action: Modify the API call to be consistent with the current job or
// redefine the job in a manner that will support the specified API.
39003, 00000, "unable to get count of total workers alive"
// *Cause: Attempt to get count of total worker processes alive failed.
// *Action: Check the additional error messages to see what caused the failure.
// Correct the error, if possible, and try the operation again. If
// this error occurs from a Data Pump client (e.g. expdp or impdp),
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
39004, 00000, "invalid state"
// *Cause: The state of the job precludes the execution of the API.
// *Action: Rerun the job to specify the API when the job is an appropriate
// state.
39005, 00000, "inconsistent arguments"
// *Cause: The current API cannot be executed because of inconsistencies
// between arguments of the API call.
// Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS
// will further describe the error.
// *Action: Modify the API call to be consistent with itself.
39006, 00000, "internal error"
// *Cause: An unexpected error occurred while processing a Data Pump job.
// Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS
// will further describe the error.
// *Action: Contact Oracle Customer Support.
39007, 00000, "Job %s has been reopened at %s"
// *Document: NO
// *Cause: Informational message to describe the reattachment to a job.
// *Action: None required.
39008, 00000, "Restarting %s: %s"
// *Document: NO
// *Cause: Informational message to describe the restarting of a job.
// *Action: None required.
39009, 00000, "Starting %s: %s"
// *Document: NO
// *Cause: Informational message to describe the starting of a job.
// *Action: None required.
39010, 00000, "******************************************************************************"
// *Document: NO
// *Cause: Informational message to introduce the file list for a job.
// *Action: None required.
39011, 00000, "Dump file set for %s.%s is:"
// *Document: NO
// *Cause: Informational message to introduce the file list for a job.
// *Action: None required.
39012, 00000, "Client detached before the job started."
// *Cause: The client detached or ended their session before the Data Pump
// job was started.
// *Action: Create new job and remain attached to the job until it is started.
39013, 00000, "Remapping the SYSTEM schema is not supported."
// *Cause: A remap_schema transform with the SYSTEM schema was specified.
// *Action: Retry the import command without remapping the SYSTEM schema.
39014, 00000, "One or more workers have prematurely exited."
// *Cause: One or more of the worker processes exited before the job was
// completed. With no workers, the master process will terminate
// the job.
// *Action: Rerun the job. If problem persists, contact Oracle Customer
// Support.
39015, 00000, "job is not running"
// *Cause: An API was executed that required the job to be running, but the
// job was not active.
// *Action: Retry the API. If problem persists, contact Oracle Customer
// Support.
39016, 00000, "Operation not supported when job is in %s state."
// *Cause: The state of the job precludes the execution of the API.
// *Action: Rerun the job to specify the API when the job is an appropriate
// state.
39017, 00000, "Worker request not supported when job is in %s state."
// *Cause: The state of the job precludes the execution of a worker request.
// This is an internal error.
// *Action: Contact Oracle Customer Support.
39018, 00000, "master process received invalid message number %s"
// *Cause: Internal Error
// *Action: Contact Oracle Customer Support.
39019, 00000, "invalid operation type %s"
// *Cause: User specified an invalid operation name on an DBMS_DATAPUMP.OPEN
// API or an invalid operation name was specified in the master table
// for a restart API.
// *Action: Correct the operation name and recreate the job.
39020, 00000, "invalid mode type %s"
// *Cause: User specified an invalid mode on an DBMS_DATAPUMP.OPEN API or an
// invalid mode was specified in the master table for a
// restart API.
// *Action: Correct the mode and recreate the job.
39021, 00000, "Database compatibility version %s is not supported."
// *Cause: User selected COMPATIBLE as the version on an DBMS_DATAPUMP.OPEN
// API, but the current database compatibility version is not
// supported by the Data Pump API. Database versions before 9.2 are
// not supported by the Data Pump.
// *Action: Specify a supported version and recreate the job.
39022, 00000, "Database version %s is not supported."
// *Cause: User selected LATEST as the version on an DBMS_DATAPUMP.OPEN API,
// but the current database version is not supported by the
// Data Pump API. Database versions before 9.2 are not supported by
// the Data Pump.
// *Action: Specify a supported version and recreate the job.
39023, 00000, "Version %s is not supported."
// *Cause: User specified an explicit version on an DBMS_DATAPUMP.OPEN API,
// but the current database version is not supported by the
// Data Pump API. Database versions before 9.2 are not supported by
// the Data Pump.
// *Action: Specify a supported version and recreate the job.
39024, 00000, "wrong schema specified for job"
// *Cause: Internal error caused by the master process
// finding inconsistencies between the schemas specified for the job.
// *Action: Contact Oracle Customer Support.
39025, 00000, "jobs of type %s are not restartable"
// *Cause: Attempt to restart a job which was not restartable.
// *Action: Recreate the job via the open API.
39026, 00000, "master table is inconsistent on validation %s"
// *Cause: Job cannot be restarted because it failed a validation check.
// Validation checks are of the form -xx.y where -xx is the
// value of the PROCESS_ORDER column in the master table where the
// error was detected and y is the actual validity check for the row.
// *Action: Recreate the job. If master table has not been modified, but
// problem persists, contact Oracle Customer Support.
39027, 00000, "wrong version of master table"
// *Cause: Job cannot be restarted because the version of the database
// upon which the job started is different than the current version
// of the database and the format of the master table has changed
// between the versions.
// *Action: Recreate the job.
39028, 00000, "cannot restart job from %s state"
// *Cause: The job was not in a suitable state for restart. Jobs must begin
// executing before they can be restarted.
// *Action: Recreate the job.
39029, 00000, "worker %s with process name \"%s\" prematurely terminated"
// *Cause: The specified worker process terminated unexpectedly. Subsequent
// messages describe the reason for the termination.
// *Action: In many cases, the Data Pump will attempt to automatically restart
// the worker. If problem persists, contact Oracle Customer Support.
39030, 00000, "invalid file type %s"
// *Cause: An invalid filetype was specified for an DBMS_DATAPUMP.ADD_FILE
// API call.
// *Action: Correct the filetype parameter and reissue the API request.
39031, 00000, "invalid filter name %s"
// *Cause: An invalid filter name was specified on a DBMS_DATAPUMP.DATA_FILTER
// API call.
// *Action: Correct the filter name parameter and reissue the API request.
39032, 00000, "Parameter %s is not supported in %s jobs."
// *Cause: The specified parameter was not supported for the specified class
// of jobs.
// *Action: Re-create the job with the appropriate mode or operation type.
39033, 00000, "Data cannot be filtered under the direct path access method."
// *Cause: The user specified that the data access method for the job was
// direct which precludes the use of certain data filters.
// *Action: Use the SUBQUERY or the SAMPLE data filter with the automatic
// data access method.
39034, 00000, "Table %s does not exist."
// *Cause: The user referenced a table in an API that did not exist.
// *Action: Correct table name and retry API.
39035, 00000, "Data filter %s has already been specified."
// *Cause: The user has already specified a data filter that matches on the
// filter name, schema name, and table.
// *Action: Specify a different data filter.
39036, 00000, "invalid metadata filter name %s"
// *Cause: An invalid metadata filter name was specified on a
// DBMS_DATAPUMP.METADATA_FILTER API call.
// *Action: Correct the metadata filter name parameter and reissue the API
// request.
39037, 00000, "Object type path not supported for %s metadata filter."
// *Cause: An object type path was specified for the filter, but the filter
// does not support the object type path parameter.
// *Action: Remove the object type path parameter.
39038, 00000, "Object path \"%s\" is not supported for %s jobs."
// *Cause: The specified object type path is invalid for the job mode.
// *Action: Correct the object type path.
39039, 00000, "Schema expression \"%s\" contains no valid schemas."
// *Cause: The specified SCHEMA_EXPR filter resulted in no schemas being
// selected.
// *Action: Correct the the SCHEMA_EXPR filter specification.
39040, 00000, "Schema expression \"%s\" must identify exactly one schema."
// *Cause: For TABLE mode jobs, the SCHEMA_EXPR filter must identify exactly
// one schema.
// *Action: Correct the the SCHEMA_EXPR filter specification.
39041, 00000, "Filter \"%s\" either identifies all object types or no object types."
// *Cause: A Metadata filter specifying path names either
// returned all objects or no objects in the job.
// *Action: Correct the the metadata filter specification.
39042, 00000, "invalid transform name %s"
// *Cause: An invalid transform name was specified on a
// DBMS_DATAPUMP.METADATA_TRANSFORM API call.
// *Action: Correct the transform name parameter and reissue the API request.
39043, 00000, "Object type %s is not supported for %s."
// *Cause: The specified object type is invalid for the specified transform
// or remap.
// *Action: Correct the object type.
39044, 00000, "Metadata transform %s has already been specified."
// *Cause: The user has already specified the metadata transform for
// the same class of object types.
// *Action: Specify a different object_type for the transform.
39045, 00000, "invalid metadata remap name %s"
// *Cause: An invalid metadata remap name was specified on a
// DBMS_DATAPUMP.METADATA_REMAP API call.
// *Action: Correct the metadata remap name parameter and reissue the API
// request.
39046, 00000, "Metadata remap %s has already been specified."
// *Cause: The user has already specified a metadata remap that matches on the
// remap name and original value.
// *Action: Specify a different original value.
39047, 00000, "Jobs of type %s cannot use multiple execution streams."
// *Cause: The user specified a value of parallelism that is precluded
// by the operation type or mode of the job.
// *Action: Specify only a parallelism of 1 for this type of job.
39048, 00000, "Unable to start all workers; only %s worker(s) available."
// *Cause: The full degree of parallelism could not be honored due
// process limits, resource limits, or other internal errors.
// *Action: Increase process/resource limits for the job.
39049, 00000, "invalid parameter name %s"
// *Cause: An invalid parameter name was specified on a
// DBMS_DATAPUMP.SET_PARAMETER API call.
// *Action: Correct the parameter name and reissue the API request.
39050, 00000, "parameter %s is incompatible with parameter %s"
// *Cause: Two parameters were set that were incompatible with each other.
// Only the first parameter setting will be used.
// *Action: Decide which parameter is to be used and stick to it.
39051, 00000, "parameter %s specified multiple times"
// *Cause: The user has already specified a parameter that matches on the
// name and the specific parameter doesn't support duplicate
// definitions.
// *Action: Specify non-repeatable parameters only once.
39052, 00000, "cannot specify SKIP_CURRENT on initial start of a job."
// *Cause: The user has already specified SKIP_CURRENT for a job that has
// never executed.
// *Action: Only specify SKIP_CURRENT when restarting a job.
39053, 00000, "parameter or attribute %s must be defined for a %s job"
// *Cause: The job being defined cannot be started because it is missing the
// specified definition.
// *Action: Specify the omitted parameter or attribute before starting the job.
39054, 00000, "missing or invalid definition of the SQL output file."
// *Cause: The job being defined cannot be started because it is missing the
// file to receive the SQL output of the job or the definition
// is unusable.
// *Action: Specify a valid directory name and file name for the SQL file.
39055, 00000, "The %s feature is not supported in version %s."
// *Cause: The user attempted to use a feature that was not enabled in the
// database version specified for the current job. Typically, this
// error occurs if the compatibility level of the database is below
// the current version of the database or if the user explicitly
// specifies a version for a Data Pump job.
// *Action: Specify the current database version as a version parameter for the
// the job.
39056, 00000, "invalid log file specification."
// *Cause: The log file for the job was incorrectly specified.
// *Action: Specify a valid directory name and file name for the log file.
39057, 00000, "invalid worker request %s for %s jobs."
// *Cause: The worker process sent a message that wasn't supported for the
// current job.
// *Action: Internal error -- contact Oracle Customer Support and report
// the error.
39058, 00000, "current object skipped: %s of type %s"
// *Cause: The user specified SKIP_CURRENT when restarting a job. This
// message is a confirmation that the object will not be imported.
// *Action: User must manually define the object in the target database.
39059, 00000, "dump file set is incomplete"
// *Cause: An IMPORT or SQL_FILE operation was being performed but not
// all of the files from the EXPORT dump file set were included.
// *Action: Check the export log file and make sure all of the files that
// were exported are included in the current job.
39060, 00000, "table(s) dropped because of conflict with master table"
// *Cause: A table specified by a job was not included because its definition
// would collide with the master table definition for the current job.
// *Action: After the job completes. Import the conflicting tables using a
// unique job name to avoid conflicts with normal user tables.
39061, 00000, "import mode %s conflicts with export mode %s"
// *Cause: The mode used for import cannot be used with a dump file set of
// specified mode. Transportable jobs are not compatible with other
// modes.
// *Action: Perform the import using a mode compatible with the export.
39062, 00000, "error creating master process %s"
// *Cause: An attempt to create the listed master process failed.
// *Action: Refer to any following error messages for possible actions. Check
// the trace log for the failed process to see if there is any
// information about the failure. Correct the error, if possible, and
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
39063, 00000, "unable to write to the bad file"
// *Document: NO
// *Cause: Errors were detecting while writing to the bad file. Subsequent
// messages will detail the problems.
// *Action: Fix the problems outlined in the secondary messages.
39064, 00000, "unable to write to the log file"
// *Cause: Errors were detecting while writing to the log file. Subsequent
// messages will detail the problems.
// *Action: Fix the problems outlined in the secondary messages.
39065, 00000, "unexpected master process exception in %s"
// *Cause: An unhandled exception was detected internally within the master
// control process for the Data Pump job. This is an internal error.
// messages will detail the problems.
// *Action: If problem persists, contact Oracle Customer Support.
39066, 00000, "Unable to close the bad file."
// *Document: NO
// *Cause: Errors were detecting while closing the bad file. Subsequent
// messages will detail the problems.
// *Action: Fix the problems outlined in the secondary messages.
39067, 00000, "Unable to close the log file."
// *Cause: Errors were detecting while closing the log file. Subsequent
// messages will detail the problems.
// *Action: Fix the problems outlined in the secondary messages.
39068, 00000, "invalid master table data in row with PROCESS_ORDER=%s"
// *Cause: A corruption was detected in the master table in the specified
// row(s). Either the row wasn't found, it was missing columns or
// had illegal values in its columns.
// *Action: Rerun the job with an uncorrupted master table.
39069, 00000, "Unable to open the bad file."
// *Document: NO
// *Cause: Errors were detecting while opening the bad file. Subsequent
// messages will detail the problems.
// *Action: Fix the problems outlined in the secondary messages.
39070, 00000, "Unable to open the log file."
// *Cause: Errors were detecting while opening the log file. Subsequent
// messages will detail the problems.
// *Action: Fix the problems outlined in the secondary messages.
39071, 00000, "Value for %s is badly formed."
// *Cause: The value of the user specified filter did not contain a legitimate
// SQL clause. Subsequent messages will detail the problems.
// *Action: Fix the problems outlined in the secondary messages.
39072, 00000, "Job %s successfully completed at %s"
// *Document: NO
// *Cause: Informational message to delineate the end of the job.
// *Action: None
39073, 00000, "Job %s completed with %s error(s) at %s"
// *Document: NO
// *Cause: Informational message to delineate the end of the job
// *Action: None
39074, 00000, "Job %s stopped by user request at %s"
// *Document: NO
// *Cause: Informational message to delineate the termination of the job
// *Action: None
39075, 00000, "Job %s stopped due to fatal error at %s"
// *Document: NO
// *Cause: Informational message to delineate the termination of the job
// *Action: None
39076, 00000, "cannot delete job %s for user %s"
// *Cause: Unable to delete a job. Refer to the any following or prior error
// messages for clarification.
// *Action: Eliminate the problems indicated.
39077, 00000, "unable to subscribe agent %s to queue \"%s\""
// *Cause: The Data Pump's communication layer was unable to attach one of its
// processes to the control or status queue. Subsequent messages will
// detail the problem.
// *Action: Fix the problem if possible, or contact Oracle Customer Support.
39078, 00000, "unable to dequeue message for agent %s from queue \"%s\""
// *Cause: The Data Pump's communication layer was unable to retrieve a
// message from the control or status queue. Subsequent messages will
// detail the problem.
// *Action: Fix the problem if possible, or contact Oracle Customer Support.
39079, 00000, "unable to enqueue message %s"
// *Cause: The Data Pump's communication layer was unable to send the
// specified message on the control or status queue. Subsequent
// messages will detail the problem.
// *Action: Fix the problem if possible, or contact Oracle Customer Support.
39080, 00000, "failed to create queues \"%s\" and \"%s\" for Data Pump job"
// *Cause: The Data Pump's communication layer was unable to create the
// status and control queues required for interprocess communication.
// Subsequent messages will detail the problem.
// *Action: Fix the problem if possible, or contact Oracle Support.
39081, 00000, "failed to unsubscribe agent %s from queue \"%s\""
// *Cause: The Data Pump's communication layer was unable to unsubscribe a
// process from the control or status queue. Subsequent messages will
// detail the problem.
// *Action: Fix the problem if possible, or contact Oracle Customer Support.
39082, 00000, "Object type %s created with compilation warnings"
// *Cause: The object in the SQL statement following this error was created
// with compilation errors. If this error occurred for a view, it
// is possible that the base table of the view was missing.
// *Action: This is a warning. The object may have to be recompiled before
// being used.
39083, 00000, "Object type %s failed to create with error:\n%s\nFailing sql is:\n%s"
// *Cause: Examine original error code to determine actual cause
// *Action: Original error code will contain more information
39084, 00000, "cannot detach job %s for user %s"
// *Cause: Unable to detach a job from the session. Refer to any following
// error messages for clarification.
// *Action: Eliminate the problems indicated.
39085, 00000, "cannot update job %s for user %s"
// *Cause: Unable to update the fixed table information for a job. Refer to
// any following or prior error messages for clarification.
// *Action: Eliminate the problems indicated.
39086, 00000, "cannot retrieve job information"
// *Cause: Unable to retrieve fixed table information for a job. Refer to the
// secondary error messages that follow this one for clarification.
// *Action: Eliminate the problems indicated by the secondary errors.
39087, 00000, "directory name %s is invalid"
// *Cause: A corresponding directory object does not exist.
// *Action: Correct the directory object parameter, or create a corresponding
// directory object with the CREATE DIRECTORY command.
39088, 00000, "file name cannot contain a path specification"
// *Cause: The name of a dump file, log file, or sql file contains a
// path specification.
// *Action: Use the name of a directory object to indicate where the file
// should be stored.
39089, 00000, "ku trace event"
// *Document: NO
// *Cause: Explicitly set.
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Turn on/off various ku trace and debug features (documentation
// in kupp.c and kupp.h).
39090, 00000, "Cannot add devices to file oriented job."
// *Cause: Attempt to add a device to a job that already contains more than
// one disk file.
// *Action: Only specify one file for jobs that contain sequential devices.
39091, 00000, "unable to determine logical standby and streams status"
// *Cause: An error occurred when determining if the Data Pump job needed to
// support logical standby or streams.
// *Action: The subsequent message describes the error that was detected.
// Correct the specified problem and restart the job.
39092, 00000, "unable to set SCN metadata for object \"%s.%s\" of type %s"
// *Cause: An error occurred when applying a SCN to the specified object to
// support logical standby or streams.
// *Action: The subsequent message describes the error that was detected.
// Correct the specified problem and restart the job.
39093, 00000, "FLASHBACK automatically enabled to preserve database integrity."
// *Cause: A Data Pump job was required to enable flashback support to
// specific SCNs in order to preserve the consistency of a logical
// standby or streams instantiation.
// *Action: None
39094, 00000, "Parallel execution not supported in this database edition."
// *Cause: Parallel execution of Data Pump jobs is not supported for this
// database edition.
// *Action: Specify a parallelism of 1 for jobs not running on Enterprise
// Edition databases.
39095, 00000, "Dump file space has been exhausted: Unable to allocate %s bytes"
// *Cause: The Export job ran out of dump file space before the job was
// completed.
// *Action: Reattach to the job and add additional dump files to the job
// restarting the job.
39096, 00000, "invalid input value %s for parameter %s"
// *Cause: A NULL or invalid value was supplied for the parameter.
// *Action: Correct the input value and try the call again.
39097, 00000, "Data Pump job encountered unexpected error %s"
// *Cause: An unexpected, potentially non-fatal error occurred while
// processing a Data Pump job.
// *Action: Contact Oracle Customer Support.
39098, 00000, "Worker process received data objects while loading metadata. Invalid process order range is %s..%s"
// *Cause: This is an internal error. Messages will detail the problem.
// *Action: If problem persists, contact Oracle Customer Support.
39099, 00000, "cannot create index for \"%s\" on master table %s"
// *Cause: One or more indexes couldn't be created on the master table.
// subsequent error messages describe the failure.
// *Action: Correct the condition that is preventing the indexes from being
// created.
39100, 00000, "Total estimation using %s method: %s"
// *Document: NO
39101, 00000, ". estimated %s"
// *Document: NO
39102, 00000, "Timeout before master process %s finished initialization. Master error:"
// *Cause: The master process whose name is listed started up but did not
// finish its initialization within the allowed time limit.
// *Action: Refer to any following error messages for possible actions. Also,
// check the trace log for the failed process, if one was created,
// to see if there is any additional information about the failure.
// Correct the error, if possible, and try the operation again. If
// the error occurs again, contact Oracle Customer Support and report
// the error.
39103, 00000, "Timeout before worker process %s finished initialization. Worker error:"
// *Cause: The worker process whose name is listed started up but did not
// finish its initialization within the allowed time limit.
// *Action: Refer to any following error messages for possible actions. Also,
// check the trace log for the failed process, if one was created,
// to see if there is any additional information about the failure.
// Correct the error, if possible, and try the operation again. If
// the error occurs again, contact Oracle Customer Support and report
// the error.
39104, 00000, "cannot call this function from a SQL parallel query slave process"
// *Cause: Called a Data Pump process model function from a process which is
// a SQL parallel query slave process
// *Action: A SQL parallel query slave process cannot create a Data Pump master
// process. This is not supported. If this error occurs from a Data
// Pump client (for example, expdp or impdp), contact Oracle
// Customer Support and report the error.
39105, 00000, "Master process %s failed during startup. Master error:"
// *Cause: The master process whose name is listed failed during startup.
// *Action: Refer to any following error messages for possible actions. Also,
// check the trace log for the failed process, if one was created,
// to see if there is any additional information about the failure.
// Correct the error, if possible, and try the operation again. If
// the error occurs again, contact Oracle Customer Support and report
// the error.
39106, 00000, "Worker process %s failed during startup. Worker error:"
// *Cause: The worker process whose name is listed failed during startup.
// *Action: Refer to any following error messages for possible actions. Also,
// check the trace log for the failed process, if one was created,
// to see if there is any additional information about the failure.
// Correct the error, if possible, and try the operation again. If
// the error occurs again, contact Oracle Customer Support and report
// the error.
39107, 00000, "Master process %s violated startup protocol. Master error:"
// *Cause: The master process whose name is listed started up but then exited
// before notifying the creating process that it was finished with
// initialization.
// *Action: Refer to any following error messages for possible actions. Also,
// check the trace log for the failed process, if one was created,
// to see if there is any additional information about the failure.
// Correct the error, if possible, and try the operation again. If
// the error occurs again, contact Oracle Customer Support and report
// the error.
39108,00000, "Worker process %s violated startup protocol. Worker error:"
// *Cause: The worker process whose name is listed started up but then exited
// before notifying the creating process that it was finished with
// initialization.
// *Action: Refer to any following error messages for possible actions. Also,
// check the trace log for the failed process, if one was created,
// to see if there is any additional information about the failure.
// Correct the error, if possible, and try the operation again. If
// the error occurs again, contact Oracle Customer Support and report
// the error.
39109,00000, "Unprivileged users may not operate upon other users' schemas"
// *Cause: An unprivileged user attempted to reference another user's schema
// during a Data Pump operation. Because of this, no schemas were
// were selected for the job.
// *Action: Retry the operation under a username owning the schema.
39110,00000, "error deleting worker processes"
// *Cause: An attempt to delete the worker processes failed.
// *Action: Refer to any following error messages for possible actions. Correct
// the error, if possible, and try the operation again. If the error
// occurs again, contact Oracle Customer Support and report the error.
39111,00000, "Dependent object type %s skipped, base object type %s already exists"
// *Cause: During a Data Pump import job, a dependent object is being skipped
// because its base object already existed.
// *Action: If the object from the dump file is wanted, drop the base and
// dependent objects and try to import again using desired filters.
39112,00000, "Dependent object type %s skipped, base object type %s creation failed"
// *Cause: During a Data Pump import job, a dependent object is being skipped
// because its base object creation failed.
// *Action: If the object from the dump file is wanted, drop the base and
// dependent objects and try to import again using desired filters
39113,00000, "Unable to determine database version"
// *Cause: The Data Pump was unable to determine the compatibility level and
// version of the current database using SYS.DBMS_UTILITY.DB_VERSION.
// *Action: Make sure access to the DBMS_UTILITY package is granted to you.
// If this is a network job, be sure that access to the DBMS_UTILITY
// package is granted to you on the remote instance.
39114,00000, "Dump files are not supported for network jobs."
// *Cause: An attempt was made to add a dumpfile to an Import job that is
// using a network link to the source database.
// *Action: Do not specify a dumpfile for jobs that do not require dumpfiles.
39115,00000, "%s is not supported over a network link"
// *Cause: An attempt was made to use an option that is not supported over
// network links such as the PARTITION_LIST filter.
// *Action: Do not attempt to use Data Pump features on network jobs if they
// are not compatible with jobs over the network.
39116,00000, "invalid trigger operation on mutating table %s.%s"
// *Cause: A Data Pump load operation failed because a trigger attempted to
// fire on the table while it was mutating.
// *Action: Disable trigger(s) on the specified table. Also see ORA-004091.
39117,00000, "Type needed to create table is not included in this operation. Failing sql is:\n%s"
// *Cause: A create table was attempted and a dependent type does not exist
// in the dumpfile or on the target database. Either the export or
// the import Data Pump job was a table mode job and types are not
// included in table mode jobs.
// *Action: Determine which type(s) are missing and create them on the target
// system and run the Data Pump import job again.
39118, 00000, ". . imported %s %s out of %s rows"
// *Document: NO
39119,00000, "worker process interrupt for delete worker processes call by master process"
// *Cause: The master process that created this worker process called
// delete worker processes to abort the current operation.
// *Action: No action is necessary. This is an informational error message.
39120, 00000, "Table %s can't be truncated, data will be skipped. Failing error is:\n%s"
// *Cause: Table data was about to be loaded into a table that already existed
// and the table_exists_action parameter is truncate, but the table
// could not be truncated.
// *Action: Determine actual cause by looking at base error.
39121, 00000, "Table %s can't be replaced, data will be skipped. Failing error is:\n%s"
// *Cause: Table data was about to be loaded into a table that already existed
// and the table_exists_action parameter is replace, but the table
// could not be dropped.
// *Action: Determine actual cause by looking at base error.
39122, 00000, "Unprivileged users may not perform %s remappings."
// *Cause: A user attempted to remap objects during an import but lacked the
// IMPORT_FULL_DATABASE privilege.
// *Action: Retry the job from a schema that owns the IMPORT_FULL_DATABASE
// privilege.
39123, 00000, "Data Pump transportable tablespace job aborted\n%s"
// *Cause: A DBMS_PLUGTS procedure failed and the Data Pump operation could
// not continue so it was aborted. The DBMS_PLUGTS failure listed
// describes the original error.
// *Action: Look at the DBMS_PLUGTS error to determine actual cause.
39124, 00000, "dump file name \"%s\" contains an invalid substitution variable"
// *Cause: The substitution variable '%' must be followed by '%','u', or 'U'.
// *Action: Correct the substitution variable in the dump file name and
// re-enter the command.
39125, 00000, "Worker unexpected fatal error in %s while calling %s [%s]"
// *Cause: An unhandled exception was detected internally within the worker
// process for the Data Pump job while calling the specified external
// routine. This is an internal error. Additional information may be
// supplied.
// *Action: If problem persists, contact Oracle Customer Support.
39126, 00000, "Worker unexpected fatal error in %s [%s] \n%s"
// *Cause: An unhandled exception was detected internally within the worker
// process for the Data Pump job. This is an internal error.
// Additional information may be supplied.
// *Action: If problem persists, contact Oracle Customer Support.
39127, 00000, "unexpected error from call to %s \n%s"
// *Cause: The exception was raised by the function invocation,
// a procedural action extension of export.
// *Action: Record the accompanying messages and report this as a Data Pump
// internal error to customer support.
39128, 00000, "unexpected DbmsJava error %d from statement %s"
// *Cause: The error was returned from a call to a DbmsJava procedure.
// *Action: Record the accompanying messages and report this as a Data Pump
// internal error to customer support.
39129, 00000, "Object type %s not imported. Name conflicts with the master table"
// *Cause: The table being imported from the remote instance has the same
// name as the master table running this Data Pump job.
// *Action: Rerun the Data Pump job with a nonconflicting name.
39130, 00000, "Object type %s not imported. Base object name conflicts with the master table"
// *Cause: The object being imported from the remote instance is dependent on
// an object that has the same name as the master table running this
// Data Pump job.
// *Action: Rerun the Data Pump job with a nonconflicting name.
39131, 00000, "ACCESS_METHOD of DIRECT_PATH not recommended for %s. Errors could occur"
// *Document: NO
// *Cause: An undocumented parameter used during load caused the specified
// table to load DIRECT PATH when the DATA PUMP job would have
// selected EXTERNAL TABLE.
// *Action: If the table did not load correctly, reissue DATA PUMP command
// without the undocumented parameter.
39132, 00000, "object type \"%s\".\"%s\" already exists with different hashcode"
// *Cause: An object type could not be created because there was already
// a type with the same name but a different hashcode on the target
// system. Tables in the transportable tablespace set that use
// this object type cannot be read.
// *Action: Drop the object type from the target system and retry the
// operation.
39133, 00000, "object type \"%s\".\"%s\" already exists with different typeid"
// *Cause: An object type in a transportable tablespace set already exists
// on the target system, but with a different typeid. The typeid
// could not be changed because the type is used by an existing table.
// Tables in the transportable tablespace set that use this object
// type cannot be read.
// *Action: Drop the object type from the target system and retry the
// operation.
39134, 00000, "Cannot include \"%s\" tablespace as a Transportable Tablespace"
// *Cause: The user attempt to specify the SYSAUX or SYSTEM tablespace as
// a member of the transportable tablespace list in the current job.
// These tablespaces may not be transported between databases.
// *Action: Specify different tablespaces to be transported.
39135, 00000, "File \"%s\" is already a member of this dump set"
// *Cause: An attempt was made to add a new file to an export job but a
// file with the same name already exists in the dump set for the
// job.
// *Action: Reenter the new file information using a different file name.
39136, 00000, "cannot specify an SCN on a transportable job"
// *Cause: A target SCN was specified for a table in a transportable job
// by the streams or logical standy components which was not the
// defaulted SCN for the table.
// *Action: This is an internal error. Please report it to Oracle support.
39137, 00000, "cannot specify a TABLE_EXISTS_ACTION of %s for a job with no metadata"
// *Cause: A job was defined with the TABLE_EXISTS_ACTION parameter set to
// REPLACE or SKIP, but without metadata. Without metadata, data
// could not be loaded for the requested table actions.
// *Action: Change the setting of the TABLE_EXISTS_ACTION parameter to APPEND
// or TRUNCATE or supply Metadata with the data.
39138, 00000, "Insufficient privileges to load data not in your schema"
// *Cause: An unprivileged user attempted to load data into a different
// schema.
// *Action: Use a privileged account if you must load data not in your schema
39139, 00000, "Data Pump does not support XMLType objects in version %s. %s will be skipped."
// *Cause: Object had an XMLType column using either an object relational or
// binary storage format, which is unsupported by Data Pump in
// the target version.
// *Action: Use the original export and import utilities to move this object.
39140, 00000, "dump file \"%s\" belongs to job %s"
// *Cause: When a dump file set consists of multiple files, all files
// in the set must be specified for an import operation, and all
// files must have been produced by the same export job.
// One of the files provided does not belong to the original dump
// file set. For instance, it was created by a different export job
// than the other files.
// *Action: Remove the dump file indicated in the message and retry the
// import operation providing only the complete set of
// dump files created by a specific export job.
39141, 00000, "dump file \"%s\" is a duplicate of dump file \"%s\""
// *Cause: When a dump file set consists of multiple files, all files
// in the set must be specified for an import operation.
// One of the files provided to import was found to be a duplicate
// of another dump file in the set. This can occur if the files in
// the dump set were copied or renamed using operating system
// utilities and the same dump file was inadvertently copied more
// than once with different destination names.
// *Action: Remove the dump file indicated in the message and retry the
// import operation providing only the complete set of
// dump files created by a specific export job.
39142, 00000, "incompatible version number %s in dump file \"%s\""
// *Cause: A dump file was specified for an import operation whose version
// number is incompatible with the dump file version of the
// Data Pump product currently running on the system. Usually this
// message indicates that the dump file was produced by a newer
// version of the Data Pump export utility.
// *Action: Import this dump file using the Data Pump import utility with
// the same version as the export which created the file.
39143, 00000, "dump file \"%s\" may be an original export dump file"
// *Cause: A dump file was specified for an import operation which appears
// to have been created using the original export utility. These
// dump files cannot be processed by the Data Pump import utility.
// *Action: Try using the original import utility to process this dump file.
39144, 00000, "file name parameter must be specified and non-null"
// *Cause: No file name was provided in an DBMS_DATAPUMP.ADD_FILE API call.
// *Action: Correct the file name parameter and reissue the API request.
39145, 00000, "directory object parameter must be specified and non-null"
// *Cause: No directory object was provided in either an DBMS_DATAPUMP.ADD_FILE
// API call or to the directory parameter used by the Data Pump
// command line clients.
// *Action: Correct the directory object parameter and retry the operation.
//
39146, 00000, "schema \"%s\" does not exist"
// *Cause: The specified schema was referenced as the source of a
// REMAP_SCHEMA parameter, but did not exist in the dump file (for
// file-based import) or in the source database (for network import).
// *Action: Specify the correct name of the schema to be remapped.
39147, 00000, "cannot migrate Data Pump queue table ownership to this instance"
// *Cause: There are active Data Pump jobs running on another instance in a
// RAC. All concurrent, active Data Pump jobs must be run on the same
// instance.
// *Action: Start this job on the same instance where other active Data Pump
// jobs are running, or wait until they finish.
39148, 00000, "unable to import data into pre-existing queue table %s. Table_exists_action of %s being ignored for this table"
// *Cause: A Data Pump import detected that a queue table that was to be
// imported already exists. Importing data into pre-existing queue
// tables is not supported.
// *Action: If the data from the dump file is desired, then drop the queue
// table and perform the import again, or use the import parameter
// table_exists_action=replace.
39149, 00000, "cannot link privileged user to non-privileged user"
// *Cause: A Data Pump job initiated be a user with
// EXPORT_FULL_DATABASE/IMPORT_FULL_DATABASE roles specified a
// network link that did not correspond to a user with
// equivalent roles on the remote database.
// *Action: Specify a network link that maps users to identically privileged
// users in the remote database.
39150, 00000, "bad flashback time"
// *Cause: A flashback time was specified for the Data Pump job which
// either could not be parsed or else could not be translated
// into a system change number (SCN). This typically occurs when
// specifying a time far in the past.
// *Action: Specify an explicit SCN for the desired flashback rather than a
// time.
39151, 00000, "Table %s exists. All dependent metadata and data will be skipped due to table_exists_action of skip"
// *Document: NO
39152, 00000, "Table %s exists. Data will be appended to existing table but all dependent metadata will be skipped due to table_exists_action of append"
// *Document: NO
39153, 00000, "Table %s exists and has been truncated. Data will be loaded but all dependent metadata will be skipped due to table_exists_action of truncate"
// *Document: NO
39154, 00000, "Objects from foreign schemas have been removed from import"
// *Cause: An non-privileged user attempted to import objects into a schema
// other than their own.
// *Action: Either perform the import from a privileged schema or else remap
// all schemas that were exported into the username running the
// import.
39155, 00000, "error expanding dump file name \"%s\""
// *Cause: Export was unable to expand the directory object and dump file
// name into a full file name. Subsequent messages will detail the
// problems.
// *Action: Fix the problems outlined in the secondary messages.
39156, 00000, "error parsing dump file name \"%s\""
// *Cause: Export was unable to parse the dump file name. Subsequent messages
// will detail the problems.
// *Action: Fix the problems outlined in the secondary messages.
39157, 00000, "error appending extension to file \"%s\""
// *Cause: Export or Import was unable to append the default extension to
// create the file name. The given file name could be too long or
// contain illegal characters. Subsequent messages will detail the
// problems.
// *Action: Fix the problems outlined in the secondary messages.
39158, 00000, " Completed %s %s objects in %s seconds"
// *Document: NO//
39159, 00000, "cannot call this function from a non-Data Pump process"
// *Cause: Called a Data Pump process model function from a process which is
// not a Data Pump process.
// *Action: Refer to any other error messages for additional information.
// If this error occurs from a Data Pump client (e.g. expdp or impdp),
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
39160, 00000, "error on whats my name call"
// *Cause: Attempt to get the Data Pump process name failed.
// *Action: Refer to any following error messages for additional information.
// If this error occurs from a Data Pump client (e.g. expdp or impdp),
// try the operation again. If the error occurs again, contact Oracle
// Customer Support and report the error.
39161, 00000, "Full database jobs require privileges"
// *Cause: Either an attempt to perform a full database export without the
// EXP_FULL_DATABASE role or an attempt to perform a full database
// import over a network link without the IMP_FULL_DATABASE role.
// *Action: Retry the operation in a schema that has the required roles.
39162, 00000, "Transportable tablespace job require privileges"
// *Cause: User attempted to perform a transportable tablespace job without
// being having the proper EXP_FULL_DATABASE or
// IMP_FULL_DATABASE role.
// *Action: Retry the operation in a schema that has the required roles.
39163, 00000, "A sample size of %s is invalid."
// *Cause: An attempt was made to do data sampling on a table with a value
// outside of the range of 0 - 100.
// *Action: Retry the filtering using a sampling number greater than 0 and less
// than 100.
39164, 00000, "Partition %s was not found."
// *Cause: If exporting or importing over the network, the user specified a
// partition name that was not found in the source database. For
// importing from files, the user specified a partition name not found
// in the dump file set.
// *Action: Retry the operation using the correct partition name.
39165, 00000, "Schema %s was not found."
// *Cause: If exporting or importing over the network, either the user
// specified a schema name that was not found in the source database
// or else the user lacked the proper EXP_FULL_DATABASE or
// IMP_FULL_DATABASE role that would allow them to access another
// schema. For importing from files, the user specified a schema
// name not found in the dump file set.
// *Action: Retry the operation using the correct schema name.
39166, 00000, "Object %s was not found or could not be exported or imported."
// *Cause: If exporting to files or importing over the network, one of the
// following occurred:
// - The object specified did not exist in the source database.
// - The user lacked the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE
// role that would allow access to the object.
// - The VIEWS_AS_TABLES object contained a type that is not supported
// with the VIEWS_AS_TABLES parameter.
// If importing from files, the user specified an object name that was
// not found in the dump file set.
// *Action: Retry the operation using the correct object name, correct set of
// privileges, or a view that has only supported types.
39167, 00000, "System partition %s of table %s does not exist in target database. Data from this partition will be loaded in %s, the first system partition."
// *Document: NO
39168, 00000, "Object path %s was not found."
// *Cause: If exporting or importing over the network, the user specified an
// object type path name that was not found in the source database.
// For importing from files, the user specified an object type path
// name not found in the dump file set.
// *Action: Retry the operation using the correct object type path name.
39169, 00000, "Local version of %s cannot work with remote version of %s."
// *Cause: A Data Pump job specified a network link, but the version on the
// remote database cannot interoperate with the version on the
// local database.
// *Action: Do not specify network links between instance running different
// versions of the database.
39170, 00000, "Schema expression %s does not correspond to any schemas."
// *Cause: A schema expression or schema list was supplied for a Data Pump
// job that did not identify any schemas in the source database.
// *Action: Correct the schema specifications and retry the job.
39171, 00000, "Job is experiencing a resumable wait.\n%s"
// *Cause: The Data Pump job is stalled with one or more of its sessions
// having a resumable wait. Resumable waits are typically caused by
// a non-expandable tablespace running out of space. The follow-on
// message describes the nature of the wait.
// *Action: Correct the condition causing the wait. This will typically
// involve adding datafiles to the tablespace that is full.
39172, 00000, "Cannot remap transportable tablespace names with compatibility of %s."
// *Cause: The user attempted to remap a tablespace name in a transportable
// tablespace job when the compatibility level was set below 10.1.
// *Action: Reset the compatibility level of the database to a more recent
// version.
39173, 00000, "Encrypted data has been stored unencrypted in dump file set."
// *Cause: No encryption password was specified for an export job that
// involved data that was encrypted in the database.
// *Action: No specific user action is required. This is only a warning that
// secure data may be readable from within the dump file set.
39174, 00000, "Encryption password must be supplied."
// *Cause: No encryption password was supplied to import a dump file set that
// was created using an encryption password.
// *Action: Specify the encryption password for the dump file set.
39175, 00000, "Encryption password is not needed."
// *Cause: An encryption password was supplied to import a dump file set
// that was not created using an encryption password.
// *Action: No user action is required. This is merely a warning message.
39176, 00000, "Encryption password is incorrect."
// *Cause: The wrong encryption password was supplied to import a
// dump file set.
// *Action: Resubmit the job using the correct encryption password for the dump
// file set.
39177, 00000, "invalid compression value %s"
// *Cause: An invalid value was specified for compression.
// *Action: Correct the value and recreate the job.
39178, 00000, "cannot perform estimate on metadata only jobs"
// *Cause: An estimate was requested for a job by specifying the ESTIMATE
// or ESTIMATE_ONLY parameter. However, the job was also defined
// to have no data. These specifications conflict with each other.
// *Action: Remove one of the conflicting specifications for the job.
39179, 00000, "unable to load table \"%s\".\"%s\" because of OID transform"
// *Cause: The OID transform for the job was set to false and the identified
// table contained either VARRAYs with non-final types or unscoped
// REF columns. Both of these column types have embedded OIDs so they
// cannot be imported correctly when OIDs are not preserved.
// *Action: You must manually move the data with the specified tables when OIDs
// are not preserved.
39180, 00000, "unable to encrypt ENCRYPTION_PASSWORD"
// *Cause: The specified encryption password was unable to be
// encrypted for placement within the master table or decrypted when
// it was to be restored from the master table. Subsequent messages
// will describe the actual error that caused the encryption to fail.
// *Action: Fix the problems referenced by the subsequent messages. The most
// common reason for the encryption to fail is the lack of a security
// wallet.
39181, 0000, "Only partial table data may be exported due to fine grain access control on %s"
// *Cause: An unprivileged user has tried to export a table that has fine
// grain access control. The table owner is subjected to access
// control and may not be able to export all rows in the table.
// Only the rows that can be seen by that user will be exported. In
// order to preserve integrity of the table, the user importing the
// table should have enough privilege to recreate the table with the
// security policies at import time.
// *Action: It is strongly recommended that the database administrator handle
// exporting of this table.
39182, 00000, "internal error %s occurred during compression phase %s\n"
// *Cause: An unexpected error occurred while compressing data buffers.
// *Action: Contact Oracle Customer Support.
39183, 00000, "internal error %s ocurred during decompression phase %s\n"
// *Cause: An unexpected error occurred while decompressing data buffers.
// *Action: Contact Oracle Customer Support.
39184, 00000, "Transportable Data Pump jobs cannot exclude PLUGTS objects"
// *Cause: A Transportable Data Pump job requires all PLUGTS% objects, but the
// user-supplied exclude filters were excluding these objects.
// *Action: Reenter command without excluding PLUGTS% objects.
39185, 00000, "The transportable tablespace failure list is"
// *Cause: Some of the tablespaces specified for this job could not be
// exported.
// *Action: See specific errors for each tablespace, correct the problem, and
// try again.
39186, 00000, "No tablespaces in the specified list exist."
// *Cause: The tablespaces specified on the EXPORT command did not exist.
// *Action: Check the list of tablespaces and reenter command with correct set
// of tablespaces.
39187, 00000, "The transportable set is not self-contained, violation list is"
// *Cause: The tablespaces specified for this job did not satisfy the closure
// checking. The list of violations specified each closure violation.
// *Action: See specific errors for violation and correct the problem or change
// the tablespaces on the command line and try again.
39188, 00000, "unable to encrypt dump file set"
// *Cause: Data Pump could not create an encrypted dump file set.
// This message will be accompanied by other messages that give
// more details about why the encrypted dump file set could not
// be created. The most common reason for this message is that you
// are trying to create a dump file set that can be transparently
// decrypted, and the database external security device is not open.
// *Action: If the external security device is not open, then open it.
// If the external security device is not configured, then the
// only type of encrypted dump file set that you can create is a
// password-based dump file set.
39189, 00000, "unable to decrypt dump file set"
// *Cause: The dump file set could not be decrypted. The reason could be
// either that an invalid password was entered, or that, when using
// transparent decryption, the database external security device
// was not open.
// *Action: If password-based import was enabled for this dump file set,
// then supply the correct password. If transparent import was
// enabled for this dump file set, then ensure that the database
// external security device is open.
39190, 00000, "internal error occurred during encryption phase %s\n"
// *Cause: An unexpected error occurred while encrypting data buffers.
// *Action: See the secondary error for more information and contact Oracle
// Customer Support.
39191, 00000, "internal error ocurred during decryption phase %s\n"
// *Cause: An unexpected error occurred while decrypting data buffers.
// *Action: See the secondary error for more information and contact Oracle
// Customer Support.
39192, 00000, "table mode jobs with transportable=always and partition filters only allow objects from one table"
// *Cause: Multiple tables are not supported when specifying partitions
// while using transportable table mode.
// *Action: Retry the job specifying only one table.
39193, 00000, "Table mode jobs do not allow the schema to be wild carded."
// *Cause: The table filter included a schema expression with the % wild card.
// *Action: Retry the job specifying actual schemas.
39194, 00000, "Table mode jobs require the tables to be comma separated."
// *Cause: The string describing tables in a table mode job was not comma
// separated.
// *Action: Retry the job specifying the tables separated by commas.
39195, 00000, "At least one schema in the TABLE_FILTER does not exist."
// *Cause: The TABLE_FITER specified contains a schema that does not exist.
// *Action: Retry the job specifying only schemas that exist.
39196, 00000, "dump file set is consistent"
// *Document: NO
// *Cause: N/A
// *Action: None
39197, 00000, "dump file set is inconsistent"
// *Document: NO
// *Cause: N/A
// *Action: Contact Oracle Support Services.
39198, 00000, "dump file set is complete"
// *Document: NO
// *Cause: N/A
// *Action: None
39199, 00000, "dump file set consistency error: %s\n"
// *Document: NO
// *Cause: N/A
// *Action: Contact Oracle Support Services.
39200, 00000, "Link name \"%s\" is invalid."
// *Cause: The name of the network link supplied for a Data Pump job was not
// usable. Secondary messages identify the problem.
// *Action: Rerun the job using a valid network link.
39201, 00000, "Dump files are not supported for estimate only jobs."
// *Cause: An attempt was made to add a dumpfile to an Export job that only
// requested file estimates.
// *Action: Do not specify a dumpfile for jobs that do not require dumpfiles.
39202, 00000, "Data cannot be filtered or selected in %s jobs."
// *Cause: A data filter was supplied for the specified type of job, but is
// not supported in the specified job type. From the command line,
// data filters can be specified by the CONTENT, TABLES (partition
// specifications), SAMPLE and QUERY parameters.
// *Action: Do not restrict data handling on jobs that cannot support data
// filtering.
39203, 00000, "Partition selection is not supported over a network link."
// *Cause: Specific partitions were selected for a job operating over a
// network link.
// *Action: Remove the partition specifications and rerun the job.
39204, 00000, "No subsetting of tablespaces is allowed for transportable import."
// *Cause: A tablespace filter was applied to a transportable import job that
// was not performed over a network link. In this case, the
// tablespace may not be changed from its specification at export
// time.
// *Action: Rerun the job without specifying a tablespace filter.
//
39205, 00000, "Transforms are not supported in transportable jobs."
// *Cause: A metadata transformation such as STORAGE or SEGMENT_ATTRIBUTES
// has been specified for a transportable Data Pump job.
// *Action: Rerun the job without specifying a transform.
39206, 00000, "A parallel degree of %s is invalid."
// *Cause: A bad numeric was supplied for specifying the parallelism to be
// used within a Data Pump job. The degree of parallelism must be
// an integer great than 0.
// *Action: The the degree specifying and retry the parallelism setting.
39207, 00000, "Value %s is invalid for parameter %s."
// *Cause: A parameter for a Data Pump job was set with a NULL or invalid
// value.
// *Action: Refer to the documentation to identify the legal values
// for each parameter. Retry the operation with a valid value.
39208, 00000, "Parameter %s is invalid for %s jobs."
// *Cause: The a parameter has been specified that is not supported for the
// specified type of Data Pump.
// *Action: Remove the parameter specification and retry the operation.
39209, 00000, "Parameter %s requires privileges."
// *Cause: Use of the specified privileges requires the user to have
// the IMP_FULL_DATABASE role for import jobs or the EXP_FULL_DATABASE
// role for export jobs.
// *Action: Remove the parameter specification and retry the operation.
39210, 00000, "A PCTSPACE adjustment of %s is invalid."
// *Cause: User specified a storage space transformation that was out of
// range. Values for PCTSPACE must be greater than zero.
// *Action: Retry the operation with a valid PCTSPACE value.
39211, 00000, "unable to retrieve dumpfile information as specified"
// *Cause: User specified an invalid or inaccessible file with the specified
// filename and directory object.
// *Action: Retry the operation with a valid directory object and filename.
39212, 00000, "installation error: XSL stylesheets not loaded correctly"
// *Cause: The XSL stylesheets used by the Data Pump Metadata API
// were not loaded correctly into the Oracle dictionary table
// "sys.metastylesheet." Either the stylesheets were not loaded
// at all, or they were not converted to the database character
// set.
// *Action: Connect AS SYSDBA and execute dbms_metadata_util.load_stylesheets
// to reload the stylesheets.
39213, 00000, "Metadata processing is not available"
// *Cause: The Data Pump could not use the Metadata API. Typically,
// this is caused by the XSL stylesheets not being set up properly.
// *Action: Connect AS SYSDBA and execute dbms_metadata_util.load_stylesheets
// to reload the stylesheets.
39214, 00000, "Data Pump does not support external tables with encrypted columns. %s will not be exported"
// *Cause: The object is an external table with encrypted columns and this is
// unsupported with Data Pump.
// *Action: External table must be manually recreated on the target system.
39215, 00000, "invalid call to routine, %s"
// *Document: NO
// *Cause: N/A
// *Action: N/A
39216, 00000, "object type \"%s\".\"%s\" hashcode or version number mismatch"
// *Cause: An object type in a transportable tablespace set could not be used
// because there was a type with the same name but a different
// hashcode (and type definition) or the same hashcode but different
// version numbers for the type on the target system. Tables in
// the transportable tablespace set that use this object type cannot
// be created.
// *Action: Drop the object type and dependent objects from the target system
// if possible and retry the operation.
39217, 00000, "object type \"%s\".\"%s\" typeid mismatch"
// *Cause: An object type in a transportable tablespace set already exists
// on the target system, but with a different typeid. The typeid
// could not be changed because the type or a dependent type is used
// by an existing table. Tables in the transportable tablespace set
// that use this object be created.
// *Action: Drop the object type and dependent objects from the target system
// if possible and retry the operation.
39218, 00000, "type check on object type \"%s\".\"%s\" failed"
// *Cause: The type check on a type failed. Therefore, the table create
// for the table which uses the type also fails.
// *Action: Refer to any following error messages for additional information.
// Correct the error, if possible, and try the action again.
39219, 00000, "directory object name is too long"
// *Cause: The directory object name provided to the Data Pump Job was
// invalid because its length was greater than 30 characters.
// *Action: Retry the operation with a valid directory object name.
39220, 00000, "file name is too long"
// *Cause: The file name provided to the Data Pump Job was invalid because
// its length was greater than 4000 characters.
// *Action: Retry the operation with a valid file name.
39221, 00000, "Specifying data filters is invalid when dumpfiles do not contain table data."
// *Cause: A data filter was supplied for an import job, but the dumpfile does
// not contain any table data. The export command created a dumpfile
// with metadata only. No table data was included. From the command
// line, data filters can be specified by the CONTENT, SAMPLE and
// QUERY parameters.
// *Action: Do not restrict data handling on jobs that cannot support data
// filtering.
39222, 00000, "Unable to create global temporary master table %s"
// *Cause: Data Pump tried to create a global temporary master table but could
// not. The errors that follow describe why the table could not be
// created.
// *Action: Examine and fix the problems described in the additional errors.
39223, 00000, "Internal Data Pump error. Master table information for version %s not found."
// *Cause: An unexpected error occurred while processing the job. The data in
// an internal table could not be found.
// *Action: Contact Oracle Support Services.
39224, 00000, "%s row(s) were rejected with the following error:\n%s"
// *Cause: These rows were not loaded due to constraint or
// index violations.
// *Action: Retry the operation when row data is fixed.
39225, 00000, " column %s: %s"
// *Document: NO
// *Cause: This row was not loaded due to constraint or index violations.
// To help identify the rejected row, columns that make up the
// primary key of the loading table are listed.
// *Action: Retry the operation when row data is fixed.
39226, 00000, " Rejected row #%s:"
// *Document: NO
// *Cause: This row was rejected due to constraint or index violations.
// *Action: Retry the operation when row data is fixed.
39227, 00000, "Rejected rows with the primary keys are:"
// *Document: NO
// *Cause: The following rows were rejected due to constraint or index
// violations. Primary key information for these rejected rows
// are listed below.
// *Action: Retry the operation when row data is fixed.
39228, 00000, "Unable to construct a unique departitioned object name for %s %s.%s:%s when defaulted."
// *Cause: All (sub)partitions in the job were to be created as individual
// objects and the renaming was defaulted. The job will attempt to
// create unique object names, but the name creation algorithm was
// unable to find a unique object name for the specified
// (sub)partition.
// *Action: Specify a rename_table transform to use or delete some of the
// existing objects causing the name conflicts.
39229, 00000, ". . verified %s %s rows"
// *Document: NO
39230, 00000, "Service name %s is not available"
// *Document: YES
// *Cause: The specified resource service name for the Data Pump job
// was not available.
// *Action: Pick a service name that the user is authorized to use.
39231, 00000, "invalid data remap name: %s"
// *Document: YES
// *Cause: The specified type of data remapping was not supported.
// *Action: Only COLUMN_FUNCTION data remaps are supported. Retry the
// operation using a supported data remap name.
39232, 00000, "invalid remap function: %s"
// *Document: YES
// *Cause: The specified package function for performing data remapping
// was not found.
// *Action: Either create the specified package function or else grant
// the user access to the function.
39233, 00000, "invalid remap column name: %s"
// *Document: YES
// *Cause: The column name specified for the data remapping either does not
// exist in the specified table, is not a scalar column, or is
// not supported.
// *Action: Specify a scalar column name within the table to be remapped.
39234, 00000, "Data cannot be remapped under the direct path access method."
// *Document: YES
// *Cause: Data remapping was requested on a job that requires the direct
// path access method. Data remapping can only be performed using
// the external table access method.
// *Action: Retry the job without specifying any access method.
39235, 00000, "data remap %s has already been specified"
// *Document: YES
// *Cause: A data remap has already been specified for the indicated column.
// Only one data remap may be defined for a column.
// *Action: Remove one of the data remap specifications for the job.
39236, 00000, "wrong number of data objects in job: Expected %s/Found %s"
// *Document: NO
// *Cause: A job option required that a limited number of table storage
// segments exist in a job. That number was exceeded.
// *Action: Specify partition and table filters to reduce the number of data
// objects in the job.
39237, 00000, "Failed to load XML document %s. Compare process aborted."
// *Cause: An error occurred while performing XML difference parse.
// *Action: Resubmit XML compare request with valid document.
39238, 00000, "XML node attribute differences are not supported."
// *Cause: MDAPI XML difference parsing did not support node attributes.
// *Action: Resubmit XML compare request with valid document.
39239, 00000, "No differences found."
// *Cause: XML documents compared were identical.
// *Action: No action required.
39240, 00000, "Error while processing difference document."
// *Cause: Error occurred in the MDAPI difference writer.
// *Action: Refer to any following error messages for additional information.
// Correct the error, if possible, and try the action again.
39241, 00000, "Datafiles required for transportable tablespace %s:"
// *Document: NO
// *Cause: Informational message to introduce the tablespace and datafile
// list for a transportable DataPump job.
// *Action: None required.
39242, 00000, "Unable to export/import %s due to table attributes."
// *Cause: See the Data Pump documentation for an explanation of what table
// attributes prevent an export or import from succeeding.
// *Action: Resolve conflicting table attributes.
39243, 00000, "Import job requires 'TRANSPORT_DATAFILES' parameter."
// *Cause: The export job used 'TRANSPORTABLE=ALWAYS' and the import job
// requires TRANSPORT_DATAFILES to be specified.
// *Action: Specify the transport datafiles associated with this job.
39244, 00000, "Event to disable dropping null bit image header during relational select"
// *Document: NO
// *Cause: N/A
// *Action: Do not strip off null bit image header on relational select
// during a Data Pump external table export.
39245, 00000, "import job requires export dump file \"%s\""
// *Cause: A Data Pump IMPORT or SQL_FILE operation was being performed
// but not all of the files from the Data Pump export dump file
// set were included.
// *Action: Check the export log file and make sure all of the files that
// were exported are included in the current job. The import log
// file also lists the export names of the missing files.
39246, 00000, "cannot locate master table within provided dump files"
// *Cause: A Data Pump IMPORT or SQL_FILE operation was being performed
// but not all of the files from the Data Pump export dump file
// set were included. In particular, the dump file containing the
// export job's master table was not provided.
// *Action: Check the export log file and make sure all of the files that
// were exported are included in the current job.
39247, 00000, "dump file size inconsistency found: [%s], [%s], [%s], [%s]"
// *Document: NO
// *Cause: N/A
// *Action: Contact Oracle Support Services.
39248, 00000, "invalid file identifier found: [%s], [%s]"
// *Document: NO
// *Cause: N/A
// *Action: Contact Oracle Support Services.
39249, 00000, "object size inconsistency found: [%s], [%s], [%s], [%s], [%s]"
// *Document: NO
// *Cause: N/A
// *Action: Contact Oracle Support Services.
39250, 00000, "Using version to downgrade a transportable job is not supported"
// *Document: NO
// *Cause: An attempt was made to specify a version that was older than
// the database-compatible version. This is not supported for
// transportable jobs.
// *Action: Either remove the version parameter for transportable jobs or
// do not use transportable tablespaces if a dumpfile for an older
// version is required.
39251, 00000, "Importing a SecureFile LOB with metadata into a scalar, column %s, is not allowed."
// *Cause: An import of a SecureFile LOB with metadata into a scalar column
// was attempted.
// *Action: Change the scalar column to a SecureFile LOB.
39252, 00000, "Importing a SecureFile LOB with metadata or archived SecureFile LOB into a BasicFile LOB is not allowed"
// *Cause: An attempt was made to import a SecureFile LOB that contained
// metadata or was archived at the time of export into a BasicFile LOB.
// *Action: Perform the import into a different table, perform
// DBMS_LOB.ARCHIVE_GET on any archived SecureFile LOBs, and then use
// INSERT AS SELECT to migrate the SecureFile LOB data to the
// BasicFile LOB.
39253, 00000, "Specified tables do not exist."
// *Cause: The tables specified for this export job did not exist.
// *Action: Check the specified table list and make sure the tables listed
// exist.
39254, 00000, "Direct path load not possible into preexisting table with column that has a default value and is not being loaded or is default on null; table %s, column %s"
// *Cause: The direct path access method could not be used to load into a
// preexisting table that has a column with a default value and
// that column is not being loaded into, or the column is default
// on null.
// *Action: Remove the ACCESS_METHOD parameter from the import command line.
39255, 00000, "Failed to fetch PLUGTS_BLKs."
// *Cause: The Data Pump expected a PLUGTS_BLK object to be exported but
// none were.
// *Action: Contact Oracle Support Services.
39256, 00000, "Transportable tablespace Data Pump jobs from read-only databases not supported."
// *Cause: The remote database was read-only and Data Pump export jobs using
// transportable tablespace over a network link require the remote
// database to be read/write.
// *Action: Use Data Pump without transportable tablespace or make the remote
// database read/write.
39257, 00000, "internal error: %s"
// *Document: NO
// *Cause: N/A
// *Action: Contact Oracle Support Services.
39258, 00000, "Cannot rename cluster."
// *Cause: DBMS_METADATA_DIFF was comparing two clusters with different
// names. There is no SQL ALTER statement to rename a cluster.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39259, 00000, "Cannot add column to cluster."
// *Cause: DBMS_METADATA_DIFF was comparing two clusters with different
// column lists. There is no SQL ALTER statement to add a column
// to a cluster.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39260, 00000, "Cannot delete column from cluster."
// *Cause: DBMS_METADATA_DIFF was comparing two clusters with different
// column lists. There is no SQL ALTER statement to delete a column
// from a cluster.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39261, 00000, "Cannot modify column in cluster."
// *Cause: DBMS_METADATA_DIFF was comparing two clusters with different
// column lists. There is no SQL ALTER statement to modify a column
// in a cluster.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39262, 00000, "Cannot alter size for hash cluster."
// *Cause: DBMS_METADATA_DIFF was comparing two hash clusters with
// different sizes. There is no SQL ALTER statement to modify
// the size of a hash cluster.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39263, 00000, "Cannot alter PARALLEL INSTANCES."
// *Cause: DBMS_METADATA_DIFF was comparing two objects, both with
// PARALLEL but with different INSTANCES values.
// There is no SQL ALTER statement to modify PARALLEL INSTANCES.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39264, 00000, "Cannot alter type of table: %s"
// *Cause: DBMS_METADATA_DIFF was comparing tables of different types:
// relational table, object table or XMLType table.
// There is no SQL ALTER statement to change a table's type.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39265, 00000, "Cannot alter object_type of object table: %s"
// *Cause: DBMS_METADATA_DIFF was comparing object tables based on
// different object types. There is no SQL ALTER statement
// to change an object table's object type.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39266, 00000, "Cannot alter unpartitioned table to partitioned."
// *Cause: DBMS_METADATA_DIFF was comparing two tables, one unpartitioned,
// the other partitioned. There is no SQL ALTER statement
// to partition an unpartitioned table.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39267, 00000, "Cannot remove default from table column."
// *Cause: DBMS_METADATA_DIFF was comparing two table columns,
// one with a default value, one without. There is no SQL ALTER
// syntax to remove a column default.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39268, 00000, "Cannot alter a real column to make it virtual or vice versa."
// *Cause: DBMS_METADATA_DIFF was comparing two table columns,
// one virtual, one real. There is no SQL ALTER statement
// to make a virtual column real or vice versa.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39269, 00000, "Cannot alter a column of type LONG to anything other than LOB."
// *Cause: DBMS_METADATA_DIFF was comparing two table columns,
// the first of type LONG, the second of a data type other than
// LOB. There is no SQL ALTER statement to modify a long data type
// to anything other than a CLOB or NCLOB.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39270, 00000, "Cannot alter a LOB column to another data type."
// *Cause: DBMS_METADATA_DIFF was comparing two table columns,
// the first of type CLOB, NCLOB or BLOB, the second of
// some other data type. There is no SQL ALTER statement to
// change the data type of a LOB column.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39271, 00000, "Cannot alter substitutability of column: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two table columns.
// This error may occur because the first column is substitutable
// and the second column is not, or because the first column is
// OF TYPE and the second column is substitutable.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39272, 00000, "Cannot alter organization of nested table column: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two nested table columns.
// One was a heap table, the other an index-organized table.
// There is no SQL ALTER statement to change the organization
// of a nested table.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39273, 00000, "Cannot alter storage type of XMLType column: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two XMLType columns
// with different storage types (CLOB, BINARY, OBJECT RELATIONAL).
// There is no SQL ALTER statement to change the storage type
// of an XMLType column.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39274, 00000, "Cannot alter physical organization of table."
// *Cause: DBMS_METADATA_DIFF was comparing two tables with different
// physical organizations (heap, index organized, external, or
// cluster). There is no SQL ALTER statement to change the
// physical organization of a table.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39275, 00000, "Cannot alter INITIAL storage option."
// *Cause: DBMS_METADATA_DIFF was comparing two tables with different
// FREELIST GROUPS storage options.
// There is no SQL ALTER statement to change a table's
// INITIAL storage option.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39276, 00000, "Cannot alter MINEXTENTS storage option."
// *Cause: DBMS_METADATA_DIFF was comparing two tables with different
// MINEXTENTS storage options.
// There is no SQL ALTER statement to change a table's
// MINEXTENTS storage option.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39277, 00000, "Cannot alter FREELIST GROUPS storage option."
// *Cause: DBMS_METADATA_DIFF was comparing two tables with different
// FREELIST GROUPS storage options.
// There is no SQL ALTER statement to change a table's
// FREELIST GROUPS storage option.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39278, 00000, "Cannot alter table with segments to segment creation deferred."
// *Cause: DBMS_METADATA_DIFF was comparing two tables, the first with
// allocated segments, the second with deferred segments.
// There is no SQL ALTER statement to change a table
// which already has segments to segment creation deferred.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39279, 00000, "Cannot alter tablespace of overflow segment."
// *Cause: DBMS_METADATA_DIFF was comparing two index organized tables
// whose overflow segments have different tablespaces.
// There is no SQL ALTER statement to change an overflow segment's
// tablespace.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39280, 00000, "Cannot drop overflow segment."
// *Cause: DBMS_METADATA_DIFF was comparing two index organized tables,
// the first with an overflow segment, the second without.
// There is no SQL ALTER statement to drop an overflow segment.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39281, 00000, "Cannot alter COMPRESS in index-organized materialized view."
// *Cause: DBMS_METADATA_DIFF was comparing two index organized
// materialized views with different key compression values.
// There is no SQL ALTER statement to modify the key compression
// of an index organized materialized view.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39282, 00000, "Cannot alter default tablespace of partitions in partitioned table."
// *Cause: DBMS_METADATA_DIFF was comparing two partitioned tables
// with different default tablespaces.
// There is no SQL ALTER statement to change the default
// tablespace of a partitioned table.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39283, 00000, "Cannot drop, split or merge hash partition: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two tables or indexes
// partitioned or subpartitioned by hash, and a
// (sub)partition in the first object was not present
// in the second object.
// Partition maintenance operations such as drop, split
// or merge can only be performed on list or range
// (sub)partitioned objects.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39284, 00000, "Cannot alter the list values of a list subpartition: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two tables subpartitioned
// by list, one of which has a subpartition with the same name
// but a different values list as a subpartition in the other.
// There is no SQL ALTER statement to change the list values
// of a list subpartition.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39285, 00000, "Cannot alter index key compression."
// *Cause: DBMS_METADATA_DIFF was comparing two indexes with different
// values of key compression.
// There is no SQL ALTER statement to change index key compression.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39286, 00000, "Cannot convert between types of index."
// *Cause: DBMS_METADATA_DIFF was comparing two indexes of different
// types, for example, a table index, a domain index,
// a cluster index, a bitmap index or a bitmap join index
// There is no SQL ALTER statement to change the type of
// an index.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39287, 00000, "Cannot alter index column list."
// *Cause: DBMS_METADATA_DIFF was comparing two indexes with different
// column lists.
// There is no SQL ALTER statement to change the columns
// of an index.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39288, 00000, "Cannot alter index base table."
// *Cause: DBMS_METADATA_DIFF was comparing two table indexes
// defined on different tables.
// There is no SQL ALTER statement to change the base table
// of an index.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39289, 00000, "Cannot add or drop local index partition or subpartition: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two locally partitioned indexes
// with different partitions or subpartitions.
// There is no SQL ALTER statement to add or drop
// a partition or subpartition of a locally partitioned index.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39290, 00000, "Cannot drop a partition of a globally partitioned index."
// *Cause: DBMS_METADATA_DIFF was comparing two globally partitioned indexes
// and a partition in the first index does not exist in the second
// index. There is no SQL ALTER statement to drop a partition of a
// globally partitioned index.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39291, 00000, "Cannot alter index storage option: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two indexes with different
// values for the specified storage option.
// There is no SQL ALTER statement to change this storage option.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39292, 00000, "Cannot alter join table of bitmap join index."
// *Cause: DBMS_METADATA_DIFF was comparing two bitmap join indexes
// with different join tables.
// There is no SQL ALTER statement to alter the join tables
// of a bitmap join index.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39293, 00000, "Cannot alter join condition of bitmap join index."
// *Cause: DBMS_METADATA_DIFF was comparing two bitmap join indexes
// with different join conditions.
// There is no SQL ALTER statement to alter the join condition
// of a bitmap join index.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39294, 00000, "Cannot alter indextype of domain index."
// *Cause: DBMS_METADATA_DIFF was comparing two bitmap domain indexes
// with different indextypes.
// There is no SQL ALTER statement to alter the indextype
// of a domain index.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39295, 00000, "Cannot alter index base cluster."
// *Cause: DBMS_METADATA_DIFF was comparing two cluster indexes
// defined on different clusters.
// There is no SQL ALTER statement to change the base cluster
// of a cluster index.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39296, 00000, "Cannot alter index partitioning type or partitioning columns."
// *Cause: DBMS_METADATA_DIFF was comparing two indexes with incompatible
// partitioning:
// (1) one is partitioned and one is not
// (2) both are partitioned but in different ways
// (locally vs. globally, hash vs. range)
// (3) both are partitioned but on different columns.
// There is no SQL ALTER statement to change the way an index
// is partitioned.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39297, 00000, "Cannot alter materialized view attribute: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two materialized views
// with incompatible attributes.
// There is no SQL ALTER statement to change this attribute
// of a materialized view.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39298, 00000, "Cannot alter materialized view partitioning type or partitioning columns."
// *Cause: DBMS_METADATA_DIFF was comparing two materialized views
// with incompatible partitioning:
// (1) one is partitioned and one is not
// (2) both are partitioned but in different ways
// (locally vs. globally, hash vs. range)
// (3) both are partitioned but on different columns.
// There is no SQL ALTER statement to change the way a materialized
// view is partitioned.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39299, 00000, "Cannot alter materialized view physical organization."
// *Cause: DBMS_METADATA_DIFF was comparing two materialized views
// with different physical organizations: heap, index
// organized, etc.
// There is no SQL ALTER statement to change the index organization
// of a materialized view.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39300, 00000, "Cannot alter materialized view log partitioning type or partitioning columns."
// *Cause: DBMS_METADATA_DIFF was comparing two materialized view logs
// with incompatible partitioning:
// (1) one is partitioned and one is not
// (2) both are partitioned but in different ways
// (locally vs. globally, hash vs. range)
// (3) both are partitioned but on different columns.
// There is no SQL ALTER statement to change the way a materialized
// view log is partitioned.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39301, 00000, "Cannot alter values recorded in materialized view log: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two materialized view logs
// that are recording different values, and the set of values
// in the first materialized view log cannot be changed to that
// in the second materialized view log.
// The error message identifies the specific problem.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39302, 00000, "Cannot alter tablespace of materialized view log."
// *Cause: DBMS_METADATA_DIFF was comparing two materialized view logs
// which have different tablespaces.
// There is no SQL ALTER statement to change the tablespace of
// a materialized view log.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39303, 00000, "Cannot alter attribute of queue: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two advanced queues
// with attribute differences that cannot be reconciled.
// The error message identifies the specific problem.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39304, 00000, "Cannot alter attribute of queue table: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two AQ queue tabless
// with attribute differences that cannot be reconciled.
// The error message identifies the specific problem.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39305, 00000, "Cannot alter attribute of sequence: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two sequences
// with attribute differences that cannot be reconciled.
// The error message identifies the specific problem.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39306, 00000, "Cannot alter attribute of trigger: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two triggers
// with differences that cannot be reconciled.
// The error message identifies the specific problem.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39307, 00000, "Cannot alter attribute of type: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two types
// with differences that cannot be reconciled.
// The error message identifies the specific problem.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39308, 00000, "Cannot alter attribute of view: %s"
// *Cause: DBMS_METADATA_DIFF was comparing two views
// with differences that cannot be reconciled.
// The error message identifies the specific problem.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39309, 00000, "Cannot alter tablespace between bigfile and smallfile."
// *Cause: DBMS_METADATA_DIFF was comparing two tablespaces,
// one bigfile, one smallfile.
// There is no SQL ALTER statement to change a tablespace
// from smallfile to bigfile or vice versa.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39310, 00000, "Cannot alter tablespace type."
// *Cause: DBMS_METADATA_DIFF was comparing two tablespaces of different
// types: permanent, temporary or undo.
// There is no SQL ALTER statement to change the type of
// a tablespace.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39311, 00000, "Cannot alter tablespace blocksize."
// *Cause: DBMS_METADATA_DIFF was comparing two tablespaces with
// different blocksizes.
// There is no SQL ALTER statement to change the blocksize
// of a tablespace.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39312, 00000, "Cannot alter tablespace encryption."
// *Cause: DBMS_METADATA_DIFF was comparing two tablespaces, one
// encrypted, one not.
// There is no SQL ALTER statement to change the encryption property
// of a tablespace.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39313, 00000, "Cannot alter tablespace flashback mode."
// *Cause: DBMS_METADATA_DIFF was comparing two tablespaces, one
// in flashback mode, one not.
// There is no SQL ALTER statement to alter the flashback mode
// of a tablespace.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39314, 00000, "Cannot alter tablespace extent_management."
// *Cause: DBMS_METADATA_DIFF was comparing two tablespaces with
// different extent management properties.
// There is no SQL ALTER statement to alter the extent management
// properties of a tablespace.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39315, 00000, "Cannot drop the first data file from a permanent or undo tablespace."
// *Cause: DBMS_METADATA_DIFF was comparing two permanent or undo
// tablespaces. The first data file in the first tablespace
// is missing from the second tablespace.
// There is no SQL ALTER statement to drop the first data file from
// a permanent or undo tablespace.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39316, 00000, "Cannot resize a data file in a smallfile tablespace."
// *Cause: DBMS_METADATA_DIFF was comparing two smallfile tablespaces.
// A data file in the first tablespace is of a different size
// from the corresponding data file in the second tablespace.
// There is no SQL ALTER statement to resize a data file in
// a smallfile tablespace.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39317, 00000, "Cannot change the segment space management of a tablespace."
// *Cause: DBMS_METADATA_DIFF was comparing two tablespaces
// with different segment space management.
// There is no SQL ALTER statement to change the segment space
// management of a tablespace.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39318, 00000, "Cannot alter user name."
// *Cause: DBMS_METADATA_DIFF was comparing two users with different names.
// There is no SQL ALTER statement to change the name of a user.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39319, 00000, "Cannot undo password expiration."
// *Cause: DBMS_METADATA_DIFF was comparing two users and the first user
// had an expired password.
// There is no SQL ALTER statement to undo the expiration
// of a user password.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39320, 00000, "Column names do not match between export and import databases."
// *Cause: The column names of the table being imported did not match the
// column names of the preexisting table.
// *Action: Ensure the column names match between export and import
// database.
39321, 00000, "Cannot alter functional index or virtual expression column: %s"
// *Cause: Altered column was referenced in a virtual column or functional
// index expression.
// There is no SQL ALTER statement to change a column which is
// referenced in one of these types of expressions.
// *Action: The difference cannot be eliminated with a SQL ALTER statement.
//
39322, 00000, "Cannot use transportable tablespace with TIMESTAMP WITH TIME ZONE columns and different time zone version."
// *Cause: The source database was at a different time zone version than the
// target database and there were tables in the dumpfile with
// TIMESTAMP WITH TIME ZONE columns.
// *Action: Convert the target database to the same timezone version as the
// source database or use Data Pump without transportable tablespace.
39323, 00000, "cannot load data from external table dump file \"%s\""
// *Cause: A dump file was specified for an import operation that had been
// created with external tables using the ORACLE_DATAPUMP
// access driver. This type of dump file cannot be processed using
// the Data Pump import utility.
// *Action: Access the data in this dump file with external tables using the
// ORACLE_DATAPUMP access driver.
39324, 00000, "cannot load data from Data Pump dump file \"%s\""
// *Cause: A dump file was specified for a load operation that had been
// created using the Data Pump. This type of dump file cannot be
// processed by external tables using the ORACLE_DATAPUMP access
// driver.
// *Action: Access the data in this dump file using the Data Pump.
39325, 00000, "TABLE_EXISTS_ACTION cannot be applied to %s."
// *Cause: An object was already in existence that uses a name in common with
// this table. The name collision could be the table name, a
// constraint, a LOB storage table, or something else in the table
// definition.
// *Action: Drop the existing object before running Data Pump.
39326, 00000, "cannot load data into table, %s, due to an unusable index"
// *Cause: An unusable index existed on the table. This index
// prevented data from being loaded into the table associated with
// this index.
// *Action: Either drop the unusable index or make it valid before attempting
// the import operation.
39327, 00000, "Oracle Database Vault data is being stored unencrypted in dump file set."
// *Cause: No encryption was specified for an export job that involved data
// from an Oracle Database Vault realm.
// *Action: No specific user action is required. This is only a warning that
// secure data may be readable from within the dump file set.
39328, 00000, "encryption password is too long"
// *Cause: The encryption password provided to the Data Pump job was invalid
// because its length was greater than the maximum allowed. When
// using the password to encrypt the dump file set, the maximum length
// is 1000 bytes. When using the password to re-encrypt encrypted
// columns only, the maximum length is 30 bytes.
// *Action: Retry the operation with a valid encryption password.
39329, 00000, "Tablespace %s needs to be locally managed."
// *Cause: An attempt was made to run an Oracle Data Pump job with the
// TRANSPORTABLE=ALWAYS parameter. Tablespaces that contain data for
// EARLY_OPTIONS in an Oracle Data Pump job run with FULL=Y and
// TRANSPORTABLE=ALWAYS parameter need to be locally managed.
// *Action: Run the Oracle Data Pump job without the TRANSPORTABLE parameter
// set to ALWAYS.
// 39330- 39336 reserved for 11.2.0.3/11.2.0.4 messages
39330, 00000, "internal cryptographic error: [%s]"
// *Document: NO
// *Cause: N/A
// *Action: Contact Oracle Support Services.
39331, 0000, "Wallet is not open on remote node."
// *Cause: The security module wallet was not open on the remote node.
// *Action: Open the wallet on the remote node.
39332, 00000, "metadata file span inconsistency found: [%s]"
// *Document: NO
// *Cause: N/A
// *Action: Contact Oracle Support Services.
39337, 00000, "Data Pump Auto Retry Count event"
// *Document: NO
// *Cause: Explicitly set.
// *Action: Set this event only under the supervision of Oracle support.
// *Comment: Useful when running Data Pump Export on an Oracle Direct NFS
// (dNFS) Storage Appliance. Certain Data Pump I/O operations may
// fail when a dNFS storage server reboot occurs. This event controls
// how many times the failed I/O operation will be retried. The level
// is an integer value in the range 0 to 255. If not set, then the
// default value is 10.
39338 ,0000, "Oracle Big Data access driver event flag"
// *Document: NO
// *Cause:
// *Action: The level is a bitmask that can be used as follows:
// 0x01 - Forces data mode to be automatic if data mode not specified
// 0x02 - Forces data mode to be field if data mode not specified
39339, 00000, "Table %s was skipped due to transportable import and TSTZ issues resulting from time zone version mismatch."
// *Cause: The source database is at a different time zone version than the
// target database and this table contains TIMESTAMP WITH TIME ZONE
// data.
// *Action: Convert the target database to the same time zone version as the
// source database or use Oracle Data Pump with conventional data
// movement to export then import this table.
39340, 00000, "unsupported object, %s will be skipped."
// *Cause: Oracle Data Pump encountered an object type that it currently does not support.
// *Action: Manually move the object to the target database.
39341, 00000, "Cannot convert an existing column into an identity column."
// *Cause: An attempt was made to convert an existing column into an identity column.
// There is no SQL ALTER statement that will convert an existing column into
// an identity column.
// *Action: The difference cannot be eliminated with a SQL ALTER statement.
39342, 00000, "Internal error - failed to import internal objects tagged with %s due to %s."
// *Cause: Oracle Data Pump encountered an internal tagged object that failed
// to import properly. All other objects with the same tag will be
// skipped.
// *Action: Contact Oracle Support Services.
39343, 00000, "Object type %s failed to create returning error:\n%s\n"
// *Cause: The object type could not be created. Examine the original error code to determine the actual cause.
// *Action: The original error code will contain more information.
39344, 00000, "import done in %s character set and %s NCHAR character set"
// *Document: NO
39345, 00000, "Warning: possible data loss in character set conversions"
// *Cause: Oracle Data Pump displayed this message at the start of the
// import operation because it determined that the character set
// or the NCHAR character set used by the export database was
// different from that of the target database and also that the
// target database character set was not a superset of the export
// database character set.
// *Action: No specific user action is required.
39346, 00000, "data loss in character set conversion for object %s"
// *Cause: Oracle Data Pump import converted a metadata object from
// the export database character set into the target database
// character set prior to processing the object. Some characters
// could not be converted to the target database character set and
// so the default replacement character was used.
// *Action: No specific user action is required. This type of data loss can
// occur if the target database character set is not a superset of
// the export database character set.
39347, 00000, "Character data loss was detected during conversion, the row was rejected."
// *Cause: The row contained characters that did not exist in the destination
// character set.
// *Action: No specific user action is required. The destination character
// set must be a superset of the source character set to avoid data
// loss.
39348, 00000, "export done in %s character set and %s NCHAR character set"
// *Document: NO
39349, 00000, " Estimated %s %s objects in %s seconds"
// *Document: NO//
39350, 00000, "Startup took %s seconds"
// *Document: NO//
39351, 00000, "Analyzed %s %s objects in %s seconds"
// *Document: NO//
39352, 00000, "Wrong number of TRANSPORT_DATAFILES specified: expected %s, received %s"
// *Cause: The number of TRANSPORT_DATAFILES specified on the impdp command
// was not correct.
// *Action: Specify the correct TRANSPORT_DATAFILES for this transportable
// job.
39353, 00000, "Data was not imported for %s. Cannot locate the time zone version %s file."
// *Cause: This table contains TIMESTAMP WITH TIME ZONE data and Oracle Data
// Pump needed to load the source version of the time zone file.
// This version cannot be located.
// *Action: Install the latest time zone version files.
39354, 00000, ". . exported %s %s rows in %s seconds using %s"
// *Document: NO
39355, 00000, ". . imported %s %s rows in %s seconds using %s"
// *Document: NO
39356, 00000, ". . imported %s %s out of %s rows in %s seconds using %s"
// *Document: NO
39357, 00000, "\nWarning: Oracle Data Pump operations are not typically needed when connected to the root or seed of a container database.\n"
// *Cause: The Oracle Data Pump client was attached to the root or seed
// container database.
// *Action: Continue if this is the desired connection string or attach to a
// pluggable database within the container database.
// *Document: YES
39358, 00000, "Export dump file version %s not compatible with target version %s"
// *Cause: The Oracle Data Pump export job version was newer than the target
// compatibility version.
// *Action: Upgrade the target database to a compatibility level of at least
// the export job version, or rerun the export job with a job
// version that is lower than or equal to the compatibility version
// of the target database.
39359, 00000, "Source time zone version is %s and target time zone version is %s."
// *Cause: The time zone version of the source database is not the same as
// the time zone version of the target database.
// *Action: Tables containing TIMESTAMP WITH TIME ZONE data cannot be
// imported with transportable tablespace technology when time zone
// versions are different between the export and target databases.
// All affected tables will be reported during the import job and
// will not be created. If any are reported, convert the target
// database to the same time zone version as the source or use
// Oracle Data Pump with conventional data movement to export then
// import the affected tables.
39360, 00000, "Table %s was skipped due to transportable import and TSLTZ issues resulting from time zone mismatch."
// *Cause: The time zone of the source database is different than the time
// zone of the target database and this table contains TIMESTAMP
// WITH LOCAL TIME ZONE data.
// *Action: Convert the target database to the same time zone as the source
// database or use Oracle Data Pump with conventional data movement
// to export then import this table.
39361, 00000, "Source time zone is %s and target time zone is %s."
// *Cause: The time zone of the source database is different than the time
// zone of the target database.
// *Action: Tables containing TIMESTAMP WITH LOCAL TIME ZONE data cannot be
// imported with transportable tablespace technology when time zones
// are different between the export and target databases. All
// affected tables will be reported during the import job and will
// not be created. If any are reported, convert the target database
// to the same time zone as the source or use Oracle Data Pump with
// conventional data movement to export then import the affected
// tables.
39362, 00000, "internal Oracle Data Pump import error"
// *Document: NO
// *Cause: N/A
// *Action: Contact Oracle Support Services.
39363, 0000, "Type evolution could not be preserved for %s"
// *Cause: Trying to apply each version of the type during import resulted
// in compilation warnings. The type was successfully recreated
// to the latest version only.
// *Action: Export dump files as well as transportable tablespaces that
// contain earlier versions of this type cannot be imported on
// top of this type definition.
39364, 00000, "encryption password is too long"
// *Cause: The encryption password provided to the Oracle Data Pump job was
// invalid because its length was greater than the maximum allowed.
// When using the password to encrypt the dump file set, the maximum
// length is 128 bytes. When using the password to re-encrypt
// encrypted columns only, the maximum length is 30 bytes.
// *Action: Retry the operation with a valid encryption password.
39365, 00000, "OBSOLETE"
// *Document: NO
// *Cause: N/A
// *Action: Contact Oracle Support Services.
39366, 00000, "disable table lock on %s.%s failed with:\n%s\n"
// *Cause: Examine the original error code to determine the actual cause.
// *Action: The original error code contains more information.
39367, 00000, "Statistics are being skipped. Cannot locate the time zone version %s file."
// *Cause: Importing statistics requires that the Oracle Data Pump load the
// source version of the time zone file. This version cannot be
// located.
// *Action: Install the latest time zone version files.
39368, 00000, "cannot alter partition varray column properties"
// *Cause: DBMS_METADATA_DIFF was comparing two partitioned tables.
// There is no SQL ALTER statement to change varray column properties.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39369, 00000, "some rows may not be exported for %s due to block corruption"
// *Cause: The corrupted data blocks were ignored when Oracle Data Pump was
// exporting the table.
// *Action: No action is required.
39370, 00000, "remap value %s is too long"
// *Cause: The remap value provided to the Oracle Data Pump job was
// invalid because its length was greater than the maximum allowed.
// *Action: Retry the operation with a valid remap value.
39371, 00000, "cannot specify partition in remap_table without departitioning"
// *Cause: The 'remap_table' value specified a partition but the tables were
// not being departitioned.
// *Action: Either remove the partition name in the 'remap_table' parameter or
// add the 'partition_options=departition' parameter.
39372, 00000, "\nWarning: Oracle Data Pump is exporting from a database that supports long identifiers to a version that does not support long identifiers.\n"
// *Cause: The Oracle Data Pump job was exporting from a database version
// that has support for long identifiers and may have objects with
// long identifiers but the target version does not support long
// identifiers.
// *Action: Continue if this is the desired action but be aware that some
// objects may not be exported and some that are exported will not
// be able to be imported to the target databse.
// *Document: YES
39373, 00000, "cannot export %s to version %s due to long identifiers"
// *Cause: This object had long identifiers and could not be exported to the
// target version specified in the Oracle Data Pump command.
// *Action: If this is the desired action, then continue, but be aware that
// this object will not be included in the dump file. If this is not
// the desired action then change the version parameter to a value
// greater than or equal to 12.2.0.0.0.
// *Document: YES
39374, 00000, "Statistics failed to export. Failing error is \n%s"
// *Cause: The statistics failed to export.
// *Action: Examine the original error code to determine the actual cause.
39375, 00000, "Statistics failed to import. Failing error is \n%s"
// *Cause: The statistics failed to import.
// *Action: Examine the original error code to determine the actual cause.
39376, 00000, "invalid data encountered (%s)"
// *Cause: Optional data validation detected invalid data while accessing
// external table data.
// *Action: See trace files for details of the problem.
39377, 00000, "altering table read-only %s.%s failed with:\n%s\n"
// *Cause: Altering the table to read-only failed.
// *Action: Examine the original error code to determine the actual cause.
39378, 00000, "Data Pump %s import job conflicts with underscore parameter %s"
// *Cause: The mode used for import cannot be used with the underscore
// parameter.
// *Action: Unset the underscore parameter and retry the import.
39379, 00000, "Logging for table %s may not be restored."
// *Cause: The table was created with NO LOGGING specified and the restore to
// the original value failed.
// *Action: Verify the logging attributes on the table.
39380, 00000, "Cannot alter tablespace with lost write protection."
// *Cause: DBMS_METADATA_DIFF was comparing two tablespaces.
// There is no SQL ALTER statement to change tablespace lost write protection.
// *Action: The difference cannot be eliminated with a SQL ALTER statement.
39381, 00000, "Cannot add datafile to bigfile tablespace."
// *Cause: DBMS_METADATA_DIFF was comparing two tablespaces.
// Datafile can not be added to a bigfile tablespace.
// *Action: The difference cannot be eliminated with an SQL ALTER statement.
39382, 00000, "There are %s cursors left open in the %s package."
// *Cause: This is an internal error. The identified package left some
// cursors opened.
// *Action: Contact Oracle Support Services.
39383, 00000, "There is more data loss than reported for object type %s."
// *Cause: The maximum number of replacement characters for each read
// operation prevented all objects within this object type that
// lost data from being found. There should be one or more messages
// preceding this one that indicate data loss for specific objects
// within the named object type. However, this message indicates that
// there may be more objects within the named object type that lost
/ data but were not listed in the preceding messages.
// *Action: No specific user action is required.
39384, 00000, "Warning: User %s has been locked and the password expired."
// *Cause: Oracle Data Pump displayed this message while importing users
// because it determined that a user was created with a password
// version that is no longer supported. See the documentation for
// PASSWORD_VERSIONS in the system view DBA_USERS for more
// information.
// *Action: Connect AS SYSDBA and unlock the account and set a password
// for the user. This can be done by issuing an
// "ALTER USER <username> ACCOUNT UNLOCK;" command followed by
// an "ALTER USER <username> IDENTIFIED BY <password>;" command.
// See the documentation for the SQLNET.ORA parameter
// SQLNET.ALLOWED_LOGON_VERSION_SERVER which explains how to
// control which password versions will be created when the
// password for the user is reset.
39385, 00000, "Data was not imported for %s."
// *Cause: The Data Pump export job had an unreported problem while
// exporting the data for this table, partition, or subpartition.
// *Action: Retry the export command including the data for this
// table, partition, or subpartition.
39386, 00000, "cannot load data into sharded table from sharded catalog for table %s"
// *Cause: Data pump import operation was trying to load table data into a
// sharded table from the sharded catalog database. Table data for
// sharded tables must be loaded into the sharded databases.
// *Action: Use the data pump to load the table data into the sharded
// database.
39387, 00000, "cannot load metadata into a sharded database"
// *Cause: Data pump import operation was trying to load metadata into a
// sharded database.
// *Action: Metadata is propagated to the sharded database from the sharded
// catalog.
39388, 00000, "cannot use transportable tablespace to export from a sharded database"
// *Cause: An attempt was made to export from a sharded database using
// transportable tablespace.
// *Action: Perform this operation without transportable tablespace.
39389, 00000, "no form of transportable export is allowed from a sharded catalog"
// *Cause: An attempt was made to export from a sharded catalog using a form
// of transportable Data Pump.
// *Action: Perform this operation without transportable data movement.
39390, 00000, "cannot use Oracle Data Pump with a network link in a sharded environment"
// *Cause: An attempt was made to perform an Oracle Data Pump operation over
// a network link with either the source or target database being
// sharded.
// *Action: Perform this operation without a network_link parameter.
39391, 00000, "maximum number of Data Pump jobs (%s) exceeded"
// *Cause: The value of the MAX_DATAPUMP_JOBS_PER_PDB initialization
// parameter exceeded the allowed value.
// *Action: Retry the operation or increase the maximum allowed value of
// the MAX_DATAPUMP_JOBS_PER_PDB initialization parameter.
39392, 00000, "Data Pump filter object %s invalid length"
// *Cause: The Data Pump filter contained an object name that was larger
// than 128 characters.
// *Action: Fix the object name in the filter and retry the Data Pump command.
39393, 00000, "direct path operation in shard catalog not allowed on sharded table %s"
// *Cause: Direct path operations could not be performed on a sharded table
// from inside of the catalog database for a sharded table. The data
// for sharded tables lives in other shard databases.
// *Action: Use direct path operations directly on the shard databases.
39394, 00000, "Cannot alter vector encoded attributes on a table column."
// *Cause: An attempt was made to change a column that was vector encoded with a
// SQL ALTER statement.
// *Action: The difference cannot be eliminated with a SQL ALTER statement.
39395, 00000, "Warning: object %s requires password reset after import"
// *Cause: During Data Pump Export or Import, fixed user or shared database
// link objects were exported and the enforcement of dictionary
// credentials was set to ENABLED.
// *Action: After running Data Pump Import, execute the ALTER DATABASE LINK
// statement for each link mentioned in the error message and reset
// the password for the link. Failure to reset the password for the
// link results in an ORA-28449 error when attempting to use the
// link.
//
39396, 00000, "Warning: exporting encrypted data using transportable option without password"
// *Cause: The encryption password was not specified for an export job that
// used the transportable option and included one or more encrypted
// tablespaces.
// *Action: No specific user action is required. However, note that the wallet
// on the source and target databases must be identical in order to
// import the dump file. Continue if this is the desired operation or
// add an encryption password to the DataPump export command.
/////////////////
/ Error numbers 39000 - 39499 (above) are reserved for Data Pump
/////////////////
/============================================================================
/ 39500-39599 Reserved for CRS Integration Errors
/ CRS is the High Availability Framework. HAS VOB
/============================================================================
39500, 00000, "failed to notify CRS of a Startup/Shutdown event for database \"%s\", instance \"%s\" (ignored)"
// *Cause: The instance was unable to obtain the context or information
// required to notify the CRS framework.
// *Action: None Required. The error is ignored.
/
39501, 00000, "failed to notify CRS of a Startup/Shutdown event [%s] (ignored)"
// *Cause: The instance was unable to communicate with the CRS framework.
// *Action: None Required. The error is ignored.
/
39502, 00000, "failed to notify CRS of a Startup/Shutdown event [%s] (ignored)"
// *Cause: The instance was unable to create an environment context.
// *Action: None Required. The error is ignored.
/
39503, 00000, "failed to notify CRS of a Startup/Shutdown event [%s] (ignored)"
// *Cause: The instance was unable to populate the environment context.
// *Action: None Required. The error is ignored.
/
39504, 00000, "failed to notify CRS of a Startup/Shutdown event [%s] (ignored)"
// *Cause: The instance was unable to find the location of the alert file.
// *Action: None Required. The error is ignored.
/
39505, 00000, "Transparent HA tracing event"
// *Document: NO
// *Cause:
// *Action:
/
39510, 00000, "CRS error performing %s on %s \'%s\' on \'%s\'\n%s"
// *Cause: Unable to perform action on associated CRS resource.
// *Action: See following error messages for additional information.
// Fix error and retry.
/
39511, 00000, "Start of CRS resource for instance '%1!s' failed with error:[%2!s]\n%3!s"
// *Cause: The Cluster Ready Services (CRS) detected an error during an attempt
// to start the indicated resource. The instance start operation was
// terminated. The accompanying messages provide detailed failure
// information.
// *Action: Examine the accompanying messages, correct the indicated problems,
// and then retry the operation.
/
39512, 00000, "Stop of CRS resource for instance '%1!s' failed with error:[%2!s]\n%3!s"
// *Cause: The Cluster Ready Services (CRS) detected an error during an attempt
// to stop the indicated resource. The instance stop operation was
// terminated. The accompanying messages provide detailed failure
// information.
// *Action: Examine the accompanying messages, correct the indicated problems,
// and then retry the operation.
/
/============================================================================
39600, 00000, "Queue keys needs to be a suffix of cluster key."
// *Cause: Attempt to specify queue key columns that don't form a suffix of
// the cluster key.
// *Action: Only specify queue key columns as a suffix of cluster key.
39601, 00000, "Hash key is required."
// *Cause: Missing hash key in the cluster key specification.
// *Action: Specify one or more hash key columns.
/============================================================================
/ 39700 - 39725 Reserved for Upgrade/Downgrade/Reload/Patch/CPU errors
/============================================================================
39700, 00000, "database must be opened with UPGRADE option"
// *Cause: A normal database open was attempted, but the database has not
// been upgraded to the current server version.
// *Action: Use the UPGRADE option when opening the database to run
// catupgrd.sql (for database upgrade), or to run catalog.sql
// and catproc.sql (after initial database creation).
39701, 00000, "database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE"
// *Cause: The database was mounted for SHARED cluster access.
// *Action: Set the CLUSTER_DATABASE initialization parameter to FALSE and
// restart the server with the UPGRADE or DOWNGRADE option.
39702, 00000, "database not open for UPGRADE or DOWNGRADE"
// *Cause: An upgrade, downgrade, reload, or patch script was invoked when
// the database was not open for UPGRADE or DOWNGRADE.
// *Action: Use STARTUP UPGRADE to open the database for upgrade or to apply
// a patch set. Use STARTUP DOWNGRADE for running a downgrade script
// or the reload script.
39703, 00000, "server version and script version do not match"
// *Cause: An upgrade, downgrade, reload, or patch script was invoked, but
// the database instance version was not the version for which the
// script was intended.
// *Action: Check that the correct ORACLE_HOME and ORACLE_SID environment
// variables are set. Also check that the SQL script is being invoked
// from the correct ORACLE_HOME.
39704, 00000, "permission to modify component registry entry denied"
// *Cause: An attempt was made to modify an entry in the component
// registry, but the session user was not authorized; only the
// CONTROL or SCHEMA user for the component are authorized to modify the
// component registry entry.
// *Action: Connect as either the CONTROL or SCHEMA user for the component.
39705, 00000, "component '%s' not found in registry"
// *Cause: No entry in the component registry was found for the specfied
// component.
// *Action: Check the spelling of the component ID and use the DBA_REGISTRY view
// to list the existing components.
39706, 00000, "schema '%s' not found"
// *Cause: The schema name specified was not found in the database.
// *Action: Create the schema before loading the component.
39707, 00000, "compatibile parameter %s too high for downgrade to %s"
// *Cause: A downgrade was attempted, but the compatible initialization
// parameter value was greater than the downgrade release version.
// *Action: Once the compatible value has been raised, downgrade to earlier
// releases is not supported.
39708, 00000, "component '%s' not a %s component"
// *Cause: The component was not a component for the specified namespace.
// *Action: Either enter a valid component identifier for the namespace or
// set the session namespace to the correct component namespace.
39709, 00000, "incomplete component downgrade; %s downgrade aborted"
// *Cause: One or more components did not have a status of DOWNGRADED.
// *Action: Correct the component problem and re-run the downgrade script.
39710, 00000, "The database mode conflicts with the connection type."
// *Cause: An attempt was made to connect to a database when the
// database was open for upgrade or downgrade, but a conflicting
// type of connection was specified.
// Only the SYSDBA and SYSOPER types of administrative connection
// are allowed while the database is open in upgrade or downgrade
// mode.
// *Action: If you are not an administrative user, try to connect again
// after the database upgrade or downgrade is complete.
// If you are an administrative user, specify either the
// AS SYSDBA or the AS SYSOPER administrative connection type.
39711, 00000, "critical patch number less than last installed CPU number"
// *Cause: A Critical Patch Update (CPU) script was invoked that had a
// number that was less than the last CPU installed in the
// database.
// *Action: Check the DBA_REGISTRY_HISTORY view to identify the last
// CPU for the database, and install the most recent CPU.
39712, 00000, "XE edition server cannot open database"
// *Cause: An attempt was made to open a Standard Edition or Enterprise
// Edition database with the Express Edition of the server.
// *Action: Use the Express Edition server only with Express Edition
// databases.
39713, 00000, "Type attribute or method already altered"
// *Document: NO
// *Cause: When the database was open in UPGRADE mode, an attempt was
// made to alter a type to add, modify, or drop attributes
// and/or methods that had already been added, modified, or
// dropped.
// *Action: The error is automatically suppressed in UPGRADE mode.
39714, 00000, "upgrade script utlmmig.sql failed"
// *Cause: A normal database open was attempted, but the upgrade script
// utlmmig.sql failed to complete.
// *Action: Use the UPGRADE option when opening the database and then run
// utlmmig.sql.
39715, 00000, "Downgrade script UTLMMIGDOWN.SQL failed."
// *Cause: A normal database open was attempted, but the downgrade script
// UTLMMIGDOWN.SQL failed to complete.
// *Action: Use the DOWNGRADE option when opening the database and then run
// UTLMMIGDOWN.SQL.
/============================================================================
/ 39726 - 39750 Reserved for Table Compression
/============================================================================
39726, 00000, "unsupported add/drop column operation on compressed tables"
// *Cause: An unsupported add/drop column operation for compressed table
// was attemped.
// *Action: When adding a column, do not specify a default value.
// DROP column is only supported in the form of SET UNUSED column
// (meta-data drop column).
39727, 00000, "COMPATIBLE must be set to 10.0.0.0.0 or higher"
// *Cause: An add/drop column operation for compressed table has been
// performed on the database. This requires COMPATIBLE to be set
// to 10.0.0.0.0 or higher during upgrade from 9.2 to a 10i or higher
// release.
// *Action: Set COMPATIBLE to 10.0.0.0.0 and retry the upgrade.
/============================================================================
/ 39751 - 39760 Reserved for Partitioned Outer Join
/============================================================================
39751, 0000, "partitioned table on both sides of PARTITIONED OUTER JOIN is not supported"
// *Cause: An attempt was made to partition both sides of PARTITIONED OUTER
// JOIN.
// *Action: Specify partitioned table on one side of PARTITIONED OUTER JOIN only.
39752, 0000, "redundant column in partitioning and join columns is not allowed"
// *Cause: An attempt was made to specify redundant columns in partitioning
// and join columns for NATURAL or named column PARTITIONED OUTER JOIN.
// *Action: Do not specify redundant column in partitioning and join columns.
39753, 0000, "unsupported use of subquery in PARTITIONED OUTER JOIN condition"
// *Cause: An attempt was made to use subquery in PARTITIONED OUTER
// JOIN condition.
// *Action: Remove subquery from the join condition.
39754, 0000, "FULL PARTITIONED OUTER JOIN is not supported"
// *Cause: An attempt was made to use FULL PARTITIONED OUTER JOIN.
// *Action: Specify FULL PARTITIONED OUTER JOIN through UNION of LEFT and RIGHT
// PARITTION OUTER JOIN.
39755, 0000, "cannot use PARTITIONED OUTER JOIN with a left correlation"
// *Cause: An attempt was made to use a PARTITIONED OUTER JOIN where
// the right side is a lateral view with a left correlation
// to the left side and is partitioned.
// *Action: Rewrite the query without the left correlation.
/============================================================================
/ 39761 - 39860 Reserved for Direct Path API
/============================================================================
39761, 0000, "stream reset required before loading this stream again"
// *Cause: An attempt was made to load a stream that was previously loaded
// but has not been reset yet.
// *Action: Reset the specified stream and convert column array data to it
// before attempting to load it again.
39762, 0000, "streams must be loaded in conversion order"
// *Cause: An attempt was made to load a stream out of conversion order.
// *Action: Load streams in the same order they were converted.
39763, 0000, "stream must be completely loaded before it is reset"
// *Cause: An attempt was made to reset a stream that contains converted
// column array data and hasn't been completely loaded yet.
// *Action: Before resetting a stream, load it until a status of OCI_SUCCESS,
// OCI_NO_DATA, or OCI_NEED_DATA is returned.
39764, 0000, "specified stream is not in the specified direct path context"
// *Cause: A direct path operation was attempted using a stream that was
// not created in the specfied direct path context.
// *Action: Only use streams created in the specified direct path context.
39765, 0000, "stream must be reset before used in a column array conversion"
// *Cause: The stream was completely loaded, but has not been reset yet.
// *Action: Reset loaded streams after load returns OCI_SUCCESS, OCI_NO_DATA,
// or OCI_NEED_DATA. The stream can then be used in a column array
// to stream conversion.
39766, 0000, "invaid stream specified for column array conversion"
// *Cause: A stream must be loaded and reset before used again in a
// column-array-to-stream conversion. This error is issued if
// another stream has subsequently been converted before the
// specified stream has been loaded, or if the latest load of this
// stream returned OCI_ERROR.
// *Action: Don't convert into a previous stream before it is loaded. Also,
// when load stream returns OCI_ERROR, the stream must be loaded
// again to insure any remaining information in the stream is loaded.
// The stream must be loaded even if the last or only row was in
// error. There may be error information in the stream that needs
// to be sent to the server.
39767, 0000, "finish is not allowed when unloaded stream data exists"
// *Cause: A direct path finish was attempted when at least one stream
// buffer has not been completely loaded.
// *Action: All streams must be loaded after a column array to stream
// conversion until load stream returns a status of OCI_SUCCESS
// or OCI_NO_DATA. The load can then be finished.
39768, 0000, "only one direct path context top level column array is allowed"
// *Cause: Attempt to create multiple top level column arrays in a direct
// path context, when only one is allowed.
// *Action: Create another direct path context if additional top level column
// arrays are required.
39769, 0000, "finish is not allowed with an incompletely loaded last row"
// *Cause: Part of a row has been loaded, but it is not complete.
// *Action: Finish loading the current row when load stream returns
// OCI_ERROR or OCI_NEED_DATA.
39770, 0000, "current conversion row should be ignored"
// *Document: NO
// *Cause: Direct Path API client indicated we should ignore this row and
// move on to the next row. Any stream data written for the current
// row will be ignored.
// *Action: None, this is an internal message. The end user or Direct Path
// API client code should never see it.
39771, 0000, "stream must be loaded before its handle is freed"
// *Cause: An attempt was made to free a stream handle after conversion but
// before the stream was loaded.
// *Action: Load the stream until OCI_SUCCESS, OCI_NEED_DATA or OCI_NO_DATA
// is returned before attempting to free the stream handle. If
// OCI_NEED_DATA is returned, another stream must be loaded to
// complete last row.
39772, 0000, "column array reset disallowed after OCI_CONTINUE or OCI_NEED_DATA"
// *Cause: An attempt was made to reset a column array when a row conversion
// is still in progress.
// *Action: Complete the current row before reseting the column array. To
// ignore the current row when conversion returned OCI_NEED_DATA,
// set the current column flag to OCI_DIRPATH_COL_ERROR. This should
// be followed by a conversion, which will undo and ignore the row.
// The column array(s) can then be reset.
39773, 0000, "parse of metadata stream failed"
// *Cause: An unexpected error occured while attempting to parse the metadata // stream for a table being loaded.
// *Action: Call Oracle support.
39774, 00000, "parse of metadata stream failed with the following error:\n %s"
// *Cause: An unexpected error occured while parsing the metadata stream.
// *Action: See the secondary error for more information.
39775, 0000, "direct path API commit not allowed due to previous fatal error"
// *Cause: An attempt was made to commit a Direct Path context after a fatal
// error.
// *Action: Correct the error and retry.
39776, 0000, "fatal Direct Path API error loading table %s"
// *Cause: A fatal error was detected loading the specified or previous table.
// *Action: Correct the error and retry.
39777, 0000, "data saves are not allowed when loading lob columns"
// *Cause: An attempt was made to save data when loading lob columns or
// columns stored as lobs (such as varrays and xml types).
// *Action: Do not attempt to do a data save or partial save when loading lob
// columns. A finish save is allowed.
39778, 0000, "the parallel load option is not allowed when loading lob columns"
// *Cause: An attempt was made to load lob columns using the attribute
// OCI_ATTR_DIRPATH_PARALLEL. This error will also be issued when
// loading any columns that are stored as lobs (such as varrays and
// xml types).
// *Action: Do not use the parallel attribute when loading lob columns.
39779, 0000, "type \"%s\".\"%s\" not found or conversion to latest version is not possible"
// *Cause: Unable to import table data using the specified type. The type was
// nonexistent in the database or the input type could not be
// converted to the existing type. The reasons why a conversion
// was not possible are:
// 1. The version of the type in the database was greater than
// the version of the type at export time because 1 or more
// attributes have been added or dropped from the type.
// 2. If the type existed in the database prior to the import
// operation, then its internal identifier may not match the
// internal identifier of the type from the export database.
// The identifiers must match for an import to succeed.
// *Action: Ensure the types in the database match those at export time.
39780, 0000, "Direct path context operations are not allowed after the context is aborted or finished"
// *Cause: The specified direct path context was aborted or finished.
// *Action: Do not pass a direct path context that has ended to any direct
// path functions.
39781, 0000, "Direct path stream loads are not allowed after another context loading the same table has ended"
// *Cause: Attempt to load a stream in one context after another loading the
// same table has ended.
// *Action: Close all contexts before trying to create another that loads the
// same table as a previous context in the same session.
39782, 0000, "Direct path prepare is not allowed after another context loading the same table has ended"
// *Cause: Direct path prepare called after a context loading the same table
// has ended.
// *Action: Close all contexts before trying to create another that loads the
// same table as a previous context in the same session.
39783, 0000, "Invalid direct path transaction active"
// *Cause: Direct path operations were not performed in the transaction
// started by the first OCIDirPathPrepare call.
// *Action: Ensure the correct transaction is active prior to calling Direct
// Path API operations.
39784, 0000, "This direct path operation is not allowed while another is in progress"
// *Cause: Another direct path operation was active.
// *Action: Complete any direct path operations in progress before attempting
// this operation.
39785, 0000, "SQL expressions returning ADT objects are not allowed in direct path"
// *Cause: The passed SQL expression returned a user-defined ADT which was
// not supported.
// *Action: Remove the SQL expression.
39786, 0000, "Number of columns does not match between export and import databases"
// *Cause: External tables could not import into a table with mismatched
// columns.
// *Action: Ensure the number of columns matches between export and import
// database.
39787, 0000, "Column %s subtype \"%s\".\"%s\" is not instantiable."
// *Cause: Subtype specified was not instantiable.
// *Action: Ensure all subtypes specified are instantiable.
39788, 0000, "Subtype \"%s\".\"%s\" is specified multiple times for column %s."
// *Cause: Subtype specified was not unique.
// *Action: Ensure all subtypes specified are unique.
39789, 0000, "\"%s\".\"%s\" is not a valid type for column %s."
// *Cause: Subtype specified was not a valid type for the column being loaded.
// *Action: Ensure all subtypes specified are valid types for the column
// being loaded.
39790, 000, "Attribute \"%s\" specified multiple times for column %s."
// *Cause: Attribute specified multiple times.
// *Action: Ensure all attributes specified are unique.
39791, 000, "Attribute \"%s\" for column %s is not in subtype \"%s\".\"%s\"."
// *Cause: Attribute was not included in the subtype indicated.
// *Action: Ensure the attribute is included in the subtype indicated by the
// specified subtype index.
39792, 000, "Attribute \"%s\" is not valid for subtypes(s) loaded into column %s."
// *Cause: Attribute specified was not included in any subtypes specified for
// the column or the declared subtype of the column.
// *Action: Ensure the attribute is included in at least one of the subtypes
// loaded into the column.
39793, 000, "Attribute \"%s\" is not unique within the hierarchy being loaded."
// *Cause: The attribute was defined in multiple lines of descent in the
// hierarchy being loaded.
// *Action: When describing the attribute, a subtype index must be specified
// to uniquely identify the attibute being loaded.
39794, 000, "No attributes loaded for subtype \"%s\".\"%s\"."
// *Cause: None of the attributes loaded were included in the type shown.
// *Action: At least one attribute must be loaded for each subtype specified.
39795, 000, "Subtype index is not first attribute for object table or column, %s."
// *Cause: The subtype index was not the first attribute when describing
// the atributes of an object column or object table with multiple
// subtypes.
// *Action: Describe the subtype index as the first attribute for this object
// column or object table.
/
39796, 000, "column array entry for %s is not valid for the current subtype"
// *Cause: This column was not part of the current subtype being loaded for
// this object column or table. Therefore, its entry must be null
// in the column array.
// *Action: Set the column array entry to null.
/
39797, 000, "The subtype index value is not valid."
// *Cause: The subtype index value in the column array was not valid for the
// object column or object table.
// *Action: Set a valid subtype index value in the column array for this table
// or column.
/
39798, 000, "The column array row offset %d is out of range (max: %d)."
// *Cause: The specified row offset was too large for the column array.
// *Action: Ensure the row offset is in range.
/
39799, 000, "The column index %d is out of range (max: %d)."
// *Cause: The specified column index was too large for the column array.
// *Action: Ensure the column index is in range.
/
39800,000, "Database version %d does not support the load of multiple subtypes."
// *Cause: Direct Path API support for loading multiple subtypes of an object
// table or column was only present in the Oracle 11 release and
// higher.
// *Action: Upgrade database to Oracle 11 or higher.
/
39801, 0000, "Subtype \"%s\".\"%s\" is not a valid subtype for column %s."
// *Cause: Subtype specified was not the declared type nor was it derived
// from the declared type.
// *Action: Ensure all subtypes specified are either the declared type or
// derived from the declared type.
/
39802, 0000, "ADT object column %s specified a SQL expression which is not allowed in direct path mode."
// *Cause: The ADT column reported in the error specified a SQL
// expression which returned the ADT. This is not supported.
// *Action: Remove the SQL expression.
/
39803, 0000, "Data saves are not allowed on tables with partitioning referential constraints."
// *Cause: Data saves (and the sqlldr ROWS parameter) are not allowed when
// loading both the parent and child tables of a partitioning
// referential constraint.
// *Action: Do not attempt data saves when loading both the parent and child
// tables of a partitioning referential constraint.
/
39804, 0000, "The load was aborted due to an error loading parent %s while also loading child %s."
// *Cause: An error occurred while loading the child and parent table of a
// partitioning referential constraint. The load was aborted
// to ensure the partitioning referential constraint was not
// violated.
// *Action: Fix the error that caused the load to abort and retry.
/
39805, 0000, "Parallel loads are not allowed when loading child and parent."
// *Cause: A parallel load was requested when loading the child and parent
// of a partitioning referential constraint. This is not allowed.
// *Action: Remove the parallel option.
/
39806, 0000, "The attempt to lock %s parent table %s %s %s failed."
// *Cause: While loading the child table of a partitioning referential
// constraint, the parent table must be locked in SHARE mode.
// *Action: Determine why the parent table could not be locked and retry.
/
39807, 0000, "Partial data save on child %s was ignored."
// *Cause: An attempt was made to partially save data when loading both
// the child and parent of a partitioning referential constraint
// or when loading a table with a domain index.
// *Action: Fix the error that caused the partial load and retry.
/
39808, 0000, "The SINGLEROW option must be specified for parent table %s."
// *Cause: The SINGLEROW option was not specified when loading both the
// parent and child table of a partitioning referential constraint.
// *Action: Ensure the SINGLEROW option is specified for the parent when
// loading the parent and child of a partitioning referential
// constraint.
/
39809, 0000, "Data saves are not allowed on tables with domain indexes."
// *Cause: Data saves (and the sqlldr ROWS parameter) could not be allowed
// when loading a table with domain indexes.
// *Action: Do not attempt data saves when loading a table with domain
// indexes.
/
39810, 0000, "Data saves are not allowed when NO_INDEX_ERRORS is specified."
// *Cause: Data saves (and the sqlldr ROWS parameter) could not be allowed
// when loading with the NO_INDEX_ERRORS option.
// *Action: Do not attempt data saves when loading a table with the
// NO_INDEX_ERRORS option.
/
39811, 0000, "index %s.%s had the following error:"
// *Cause: An error occurred on the index; error follows.
// *Action: Fix the error and retry.
/
39812, 0000, "index %s.%s partition %s had the following error:"
// *Cause: An error occurred on the index; error follows.
// *Action: Fix the error and retry.
/
39813, 0000, "index %s.%s had %s partition errors:"
// *Cause: A logical index error occurred on a partitioned index which
// affected one or more index partitions, which are listed below
// this message.
// *Action: Fix the error(s) and retry.
/
39814, 0000, "The SKIP_INDEX_MAINTENANCE option is not allowed with NO_INDEX_ERRORS."
// *Cause: The SKIP_INDEX_MAINTENANCE option was used with the
// NO_INDEX_ERRORS option.
// *Action: Do not use SKIP_INDEX_MAINTENANCE with NO_INDEX_ERRORS.
/
39815, 0000, "Direct Path Unload of an external table is not allowed."
// *Cause: An attempt was made to use Direct Path API Unload to
// unload an external table.
// *Action: Do not use Direct Path Unload to unload an external table.
/
39816, 0000, "Direct Path Unload of tables with encrypted column(%s.%s) is not allowed."
// *Cause: An attempt was made to use Direct Path API Unload to unload
// a table with encrypted columns.
// *Action: Do not use Direct Path Unload to unload a table with encrypted
// columns.
/
39817, 0000, "index %s.%s was ignored due to:"
// *Cause: Index was unusable at the start of the load and it was requested
// that unusable indexes be skipped.
// *Action: No action required.
/
39818, 000, "index %s.%s partition %s was ignored due to:"
// *Cause: Index was unusable at the start of the load and it was requested
// that unusable indexes be skipped.
// *Action: No action required.
/
39819, 0000, "The OCI_ATTR_DIRPATH_NO_INDEX_ERRORS attribute cannot be set to TRUE in direct path parallel loads."
// *Cause: An attempt was made to set the OCI_ATTR_DIRPATH_NO_INDEX_ERRORS
// attribute to TRUE in a direct path parallel load.
// *Action: Do not set the OCI_ATTR_DIRPATH_NO_INDEX_ERRORS to TRUE for direct
// path parallel loads.
/
39820, 0000, "Zero length LONG piece detected for column %s row %s."
// *Cause: A zero length piece was detected for a LONG column.
// *Action: Do not use a length of zero when loading LONG columns.
/
39821, 00000, "domain index on columnar data made unusable\n"
// *Cause: An attempt was made to load a columnar table with a domain index
// using SQL*Loader direct part load
// *Action:
39822, 0000, "A new direct path operation is not allowed in the current transaction."
// *Cause: All previous direct path contexts ended and the current
// transaction was ready for a commit or abort of those changes.
// *Action: Commit or abort the current transaction, and start a new
// transaction for the next direct path context.
/
39823, 0000, "The attribute OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS is only allowed for load operations."
// *Cause: The attribute OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS was set for a
// nonload operation.
// *Action: Use OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS for load operations only.
/
39824, 0000, "The OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS attribute was set when no transaction was active."
// *Cause: There was no active transaction to use.
// *Action: Start a transaction or do not set the attribute
// OCI_ATTR_DIRPATH_USE_ACTIVE_TRANS to TRUE.
39825, 0000, "Direct path load of view or synonym (%s.%s) with multiple dependencies not permitted."
// *Cause: An attempt was made to load a view or synonym which has more than a single
// dependency.
// *Action: A view or synonym being loaded by the direct path API must resolve to a single object.
39826, 0000, "Direct path load of view or synonym (%s.%s) could not be resolved."
// *Cause: A synonym or view could not be translated.
// *Action: Verify that the view or synonym is valid.
39827, 0000, "Direct path load of PL/SQL function not permitted."
// *Cause: An attempt was made to load a PL/SQL function with the direct path API.
// *Action: Remove PL/SQL function the direct path load.
/
39828, 0000, "Constraint %s was disabled because of index %s.%s error."
// *Cause: The index used for the constraint was set as unusable.
// *Action: Fix the error that caused the index to be set unusable.
/
39829, 0000, "function-based index on columnar data made unusable\n"
// *Cause: An attempt was made to load a columnar table with a function-based
// index using SQL*Loader direct path load.
// *Action: Rebuild the function-based index after the load completes.
39830, 0000, "XML parsing failed \n%s"
// *Cause: XML parser returned an error while trying to parse the document.
// *Action: Fix the error that caused the document to be invalid.
39831, 0000, "Direct path load failed, (%s.%s) is not a table."
// *Cause: Object being loaded did not resolve to a table.
// *Action: Verify that the view or table name is correct.
39832, 0000, "Direct path unload was not allowed due to columns with default values."
// *Cause: Direct path unload was attempted on a table with columns that have
// default values.
// *Action: Do not attempt a direct path unload of a table with columns
// that have default values.
39833, 0000, "Direct path parallel load was not allowed on a temporary table."
// *Cause: A direct path parallel load was attempted on a temporary table.
// *Action: Do not attempt a direct path parallel load on a temporary table.
/
39834, 0000, "Direct path load or unload was not allowed on a remote table."
// *Cause: An attempt was made to specify a remote table in a direct path
// API load or unload.
// *Action: Do not specify a remote table in a direct path API load or unload.
/
39835, 0000, "Direct path load partition memory exceeded. PGA use is %skb, PGA limit is: %skb"
// *Cause: A direct path load ran out of process memory when loading multiple
// partitions.
// *Action: Use the PARTITION_MEMORY parameter to limit memory used when
// loading many partitions. Once this limit is reached, loading
// of some partition rows will be delayed until memory use falls
// below the limit. Use a value (kb) lower than the current program
// global area (PGA) limit included in this message and try the
// load again.
39836, 0000, "Invalid direct path API server context detected"
// *Cause: The data cartridge encountered an unexpected condition.
// *Action: Contact Oracle Support Services.
//
39837, 0000, "Direct path loading does not support the DEFAULT value clause for column %s."
// *Cause: Direct path loading could not support loading the default value
// for the data type of the indicated column.
// *Action: Use conventional path loading. Otherwise, use DEFAULTS=IGNORE,
// DEFAULTS=IGNORE_UNSUPPORTED_EVALUATE_ONCE or
// DEFAULTS=IGNORE_UNSUPPORTED_EVALUATE_EVERY_ROW.
//
39838, 0000, "Direct path load of a specific partition with interval subpartitioning is not allowed."
// *Cause: An attempt was made to load a specific partition of a table that
// was interval subpartitioned. This is not supported by the Direct
// Path API.
// *Action: Load the entire table when the table is interval subpartitioned.
//
39839, 0000, "Direct path default expression cache size (%s) is too large."
// *Cause: An attempt was made to allocate a default expression cache that
// was too large.
// *Action: Use a smaller value for the default expression cache and retry.
/
39840, 0000, "A data load operation has detected data stream format error %s."
// *Cause: A dump file data stream format error was detected during a
// load operation.
// *Action: The stream format error may have been caused by a corrupted
// dump file. If possible, re-create the dump file and try again.
// If the problem persists, contact Oracle Support Services.
/
39841, 0000, "A data load operation detected a data stream format error (see next error), attempting to continue."
// *Cause: A dump file data stream format error was detected during a
// load operation. An attempt was made to continue the load from
// a point beyond the corruption.
// *Action: The stream format error may have been caused by a corrupted
// dump file. If possible, re-create the dump file and try again.
// If the problem persists, contact Oracle Support Services.
/
39842, 0000, "Data load operation was discontinued due to the previous data stream format error."
// *Cause: A dump file data stream format error was detected during a
// a load operation. The operation was aborted.
// *Action: The stream format error may have been caused by a corrupted
// dump file. If possible, re-create the dump file and try again.
// If the problem persists, contact Oracle Support Services.
/
39843, 0000, "Invalid direct path API server context detected"
// *Cause: The data cartridge encountered an unexpected condition.
// *Action: Contact Oracle Support Services.
/
39844, 000, "Bad stream format detected: [%s] [%s] [%s] [%s] [%s] [%s] [%s] [%s]"
// *Cause: A dump file data stream format or initialization error was
// detected during a load or import operation.
// *Action: The stream format error may have been caused by a corrupted
// dump file. If possible, re-create the dump file and try again.
// If the problem persists, contact Oracle Support Services.
//
39845, 0000, "A data load operation detected a data stream format error, attempting to continue."
// *Cause: A dump file data stream format error was detected during a
// load operation. An attempt was made to continue the load from
// a point beyond the corruption.
// *Action: The stream format error may have been caused by a corrupted
// dump file. If possible, re-create the dump file and try again.
// If the problem persists, contact Oracle Support Services.
/
//
/============================================================================
/ 39861 - 39899 Reserved for point-in-time recovery and flashback of PDB
/============================================================================
39861, 00000, "auxiliary data file copy file for Pluggable Database %s: \"%s\""
// *Cause: This message reports the filename for details of another message.
// *Action: Other messages will accompany this message. See the associated
// messages for the appropriate action to take.
39862, 00000, "RESETLOGS option only valid after a Pluggable Database incomplete recovery"
// *Cause: The ALTER PLUGGABLE DATABASE OPEN RESETLOGS command was issued,
// but the Pluggable Database was not flashed back or point-in-time
// recovered.
// *Action: Retry the ALTER PLUGGABLE DATABASE OPEN command without specifying
// RESETLOGS.
39863, 00000, "An earlier Pluggable Database incomplete recovery failed."
// *Cause: An earlier Pluggable Database flashback or point-in-time recovery
// failed.
// *Action: Retry the Pluggable Database flashback or incomplete recovery.
39864, 00000, "Data file %s on standby database must be restored and renamed, and standby database recovery must be restarted."
// *Cause: A missing data file was added on a standby database in response to
// a Pluggable Database (PDB) OPEN RESETLOGS command on the primary
// database. This data file must be restored and renamed on the standby
// database before standby database recovery can be restarted.
// *Action: Restore the missing data file and rename it on the standby
// database, then restart standby database recovery.
39865, 00000, "cannot FLASHBACK beyond Pluggable Database resetlogs operation"
// *Cause: An attempt was made to perform a FLASHBACK DATABASE beyond a
// Pluggable Database resetlogs system change number (SCN).
// *Action: Choose a FLASHBACK SCN that is more recent than the Pluggable
// Database resetlogs SCN.
39866, 00000, "Data files for Pluggable Database %s must be offline to flashback across special 12.1 PDB resetlogs."
// *Cause: An attempt was made to perform a FLASHBACK DATABASE beyond a Pluggable
// Database (PDB) resetlogs performed at 12.1 compatibility. Futhermore,
// the PDB resetlogs was performed after a flashback or point-in-time
// recovery (PITR) of the PDB to its parent database incarnation. This
// is not supported unless all data files in the PDB are offline.
// *Action: Take the data files for the Pluggable Database (PDB) offline
// before performing the FLASHBACK DATABASE command. To bring the PDB
// to the same past point in time as the container database (CDB),
// those data files can be restored from backups and recovered to that
// same past point in time. This can be done in one of two ways:
// * Flashback the CDB and open the CDB with resetlogs.
// Restore the PDB later, and perform a complete PDB recovery.
// * Flashback the CDB first. Restore and recover the PDB to the
// same system change number (SCN). Open CDB with resetlogs.
39867, 1, "Clean PDB restore point '%s' is on an orphan incarnation of the pluggable database."
// *Cause: The specified clean PDB restore point was on an orphan incarnation
// of the pluggable database. One cannot flashback a pluggable database
// to an orphan incarnation.
// *Action: Check the restore point.
39870, 00000, "container database is not open in read/write mode"
// *Cause: A command was attempted that requires the container database (CDB)
// to be open in read/write mode.
// *Action: Open the container database in read/write mode and try the
// command again.
39871, 00000, "An earlier Pluggable Database resetlogs operation failed after making changes."
// *Cause: An earlier ALTER PLUGGABLE DATABASE OPEN RESETLOGS command failed
// after it made some changes.
// *Action: Perform another Pluggable Database point-in-time recovery before
// attempting to open the Pluggable Database with RESETLOGS.
39872, 00000, "Data file %d is in the middle of Pluggable Database resetlogs operation."
// *Cause: The data file was in the middle of a Pluggable Database
// resetlogs operation.
// *Action: Find the right file version or perform more media recovery.
// For additional information, see other errors.
39873, 00000, "Restore all data files to a checkpoint SCN lower than %s."
// *Cause: This error provides additional information for error 39874.
// *Action: Restore the data files as suggested and restart the recovery
// process.
39874, 00000, "Pluggable Database %s recovery halted"
// *Cause: The Pluggable Database was recovered into an orphan branch.
// *Action: Restore all data files to a checkpoint system change number (SCN)
// lower than the branch point and restart the recovery process.
// Check the alert log for additional information.
39875, 00000, "Data file %s is in the middle of Pluggable Database resetlogs operation."
// *Cause: The data file is in the middle of a Pluggable Database (PDB)
// resetlogs operation.
// *Action: If possible, recover the data file further so that it is not in
// the middle of a PDB resetlogs operation. Another alternative is
// to perform PDB point-in-time recovery.
39876, 00000, "cannot perform CDB OPEN RESETLOGS because data file %s is in the middle of a PDB resetlogs operation"
// *Cause: The data file mentioned was in the middle of a Pluggable Database
// (PDB) resetlogs operation.
// *Action: Recover the container database (CDB) to a different system change
// number (SCN) at which the data files are not in the middle of a
// PDB resetlogs operation. Alternatively, you can offline the
// problematic data file and let CDB OPEN RESETLOGS succeed.
// You may need to perform PDB point-in-time recovery later in
// order to open the PDB of the offlined data file.
39877, 00000, "keyword ONLINE or OFFLINE expected"
// *Cause: The ONLINE or OFFLINE keyword was not specified after the ALL
// keyword.
// *Action: Use the correct syntax.
39878, 00000, "Only one Pluggable Database name can be specified."
// *Cause: Multiple Pluggable Database names were specified for the ALTER
// PLUGGABLE DATABASE OPEN RESETLOGS command.
// *Action: Specify only one Pluggable Database name.
39879, 00000, "Pluggable Database %s is in the middle of a Pluggable Database RESETLOGS operation"
// *Cause: There was already an on-going Pluggable Database OPEN RESETLOGS operation
// for this Pluggable Database.
// *Action: If needed, retry after the Pluggable Database OPEN RESETLOGS operation
// completes.
39880, 00000, "One or more pluggable databases were in the middle of a point-in-time recovery at this incomplete database recovery SCN."
// *Cause: In the past, one or more pluggable databases had an active pluggable
// database RESETLOGS operation as of this incomplete recovery SCN.
// *Action:
// Additional messages are logged in the alert log indicating all of
// the pluggable databases affected by this container database OPEN
// RESETLOGS operation.
//
// Recover the container database to a different system change
// number (SCN) at which none of the pluggable databases had
// an active RESETLOGS operation.
//
// To continue the container database OPEN RESETLOGS operation at the
// same SCN, offline all of the data files of the affected pluggable
// databases first and reissue the command. However, a
// new point-in-time recovery of the affected pluggable databases
// would be required before these databases can be opened again.
39881, 00000, "Pluggable database %s must be closed while recovering the physical standby across PDB RESETLOGS"
// *Cause: The pluggable database (PDB) is open while the physical standby
// is recovering across a PDB RESETLOGS operation for the PDB.
// *Action: Close the PDB and restart physical standby recovery.
39882, 00000, "cannot create clean pluggable database restore point for the specified pluggable database (con_id:%s)"
// *Cause: There were still outstanding transactions in the closed pluggable
// database.
// *Action: Retry the command after opening the pluggable database and
// closing all outstanding transactions. Alternatively, create a
// normal pluggable database restore point.
39883, 00000, "Restore point %s for pluggable database %s is not a clean pluggable database restore point."
// *Cause: For a pluggable database using shared undo, there was an attempt to
// flashback pluggable database in SQL without a clean pluggable
// database restore point. The specified restore point was not a
// clean pluggable database restore point.
// *Action: Do one of the following:
// - Issue flashback pluggable database in RMAN.
// - Issue the SQL flashback pluggable database command to flashback
// to a clean pluggable database restore point.
// - Turn on local undo mode for the pluggable database. The SQL
// flashback pluggable database command can always be used to
// flashback a pluggable database using local undo.
39884, 00000, "Flashback of PDB (con_id:%s) cannot restore data file %s which is currently used by PDB (con_id:%s)."
// *Cause: The data file required to flashback the specified pluggable
// database to the specified point in time could not be restored.
// The file number of the pluggable database data file was used by a
// different pluggable database.
// *Action: Flashback the pluggable database to a different point-in-time.
// Alternatively, drop the conflicting data file from the database
// first before you flashback the pluggable database. If neither
// option can be used, you can also flashback the entire consolidated
// database or restore and recover a copy of the consolidated
// database to the specified point-in-time. You can then extract
// the recovered data.
39885, 00000, "flashback/PITR of a pluggable database before its creation is not allowed"
// *Cause: The flashback/PITR System Change Number (SCN) or timestamp specified was
// less than the pluggable database creation SCN or timestamp.
// Flashback/PITR SCN or timestamp cannot be less than the pluggable
// database creation SCN or timestamp.
// *Action: Check the flashback/PITR SCN or timestamp and retry the command.
39886, 00000, "With shared undo, one can only use an SQL command to flashback a pluggable database (PDB) to a clean PDB restore point."
// *Cause: The command issued did not specify a clean pluggable database
// restore point. For a pluggable database using shared undo,
// one can only use the SQL Flashback pluggable database command
// to flashback to a clean pluggable database restore point.
// *Action: Do one of the following:
// - Issue flashback pluggable database in RMAN.
// - Issue the SQL flashback pluggable database command to flashback
// to a clean pluggable database restore point.
// - Turn on local undo mode for the pluggable database. The SQL
// flashback pluggable database command can always be used to
// flashback a pluggable database using local undo.
39887, 00000, "Cannot create restore points for SEED PDB"
// *Cause: There was an attempt to create a restore point for SEED PDB.
// *Action: Create restore points in ROOT or for a different pluggable
// database.
39888, 00000, "Guaranteed restore points exist for pluggable database %s."
// *Cause: There was an attempt to drop or unplug a pluggable database when
// there were still guaranteed restore points for this pluggable
// database.
// *Action: Drop all the guaranteed restore points for the pluggable database
// before dropping the pluggable database.
39889, 00000, "Specified System Change Number (SCN) or timestamp is in the middle of a previous PDB RESETLOGS operation."
// *Cause: The specified System Change Number (SCN) or timestamp is in the middle of a
// previous PDB RESETLOGS operation. More specifically, each PDB
// RESETLOGS operation may create a PDB incarnation as shown in
// v$pdb_incarnation. Any SCN between INCARNATION_SCN and
// END_RESETLOGS_SCN or any timestamp between INCARNATION_TIME and
// END_RESETLOGS_TIME as shown in v$pdb_incarnation is considered in
// the middle of the PDB RESETLOGS operation.
// *Action: Flashback the PDB to an SCN or timestamp that is not in the middle
// of a previous PDB RESETLOGS operation.
39890, 00000, "Flashback or PITR of a pluggable database to a System Change Number (SCN) or timestamp before latest undo mode switch is not allowed."
// *Cause: An attempt was made to flashback/PITR a pluggable database (PDB) to
// a System Change Number (SCN) or timestamp that precedes the
// latest switch between shared and local undo.
// *Action: Flashback/PITR a pluggable database (PDB) to an SCN or timestamp that
// comes after the latest switch between shared and local undo.
39891, 00000, "Clean PDB restore point cannot be created when CDB is in local undo mode."
// *Cause: There was an attempt to create a clean restore point when the
// CDB was in local undo mode. This is not supported. Clean PDB restore
// points are designed for CDB in shared undo mode. They are not useful
// for CDB in local undo mode.
// *Action: Do not use "clean" option when creating the restore point.
39892, 00000, "Flashing back a pluggable database to a timestamp that falls on an orphaned database incarnation is not allowed."
// *Cause: An attempt was made to flashback a pluggable database (PDB) to a
// timestamp that falls on an orphaned database incarnation.
// *Action: Flashback a pluggable database (PDB) to an earlier timestamp that
// falls somewhere along the current database incarnation's direct
// ancestor path.
39893, 00000, "PDB restore point could not be created"
// *Cause: There was an attempt to create a restore point for a pdb that was
// still in the process of being created or was never opened before.
// *Action: Retry the operation after pdb creation is complete and opened once.
39894, 00000, "PDB restore point could not be created"
// *Cause: There was an attempt to create a restore point for a pdb when an
// application install or upgrade was going on.
// *Action: Retry the operation after application install or upgrade is complete.
39895, 00000, "unable to flashback or PITR a pluggable database"
// *Cause: The flashback or point-in-time recovery (PITR) system change number
// (SCN) or timestamp specified was less than the SCN or timestamp at
// which the pluggable database was first opened in read/write mode.
// *Action: Check the flashback or PITR SCN or timestamp and retry the command.
39896, 00000, "INSTANCES clause and RESETLOGS keyword cannot be used together in ALTER PLUGGABLE DATABASE command"
// *Cause: The INSTANCES clause was specified in the ALTER PLUGGABLE DATABASE
// OPEN RESETLOGS command.
// *Action: Specify either the INSTANCES clause or the RESETLOGS keyword in the
// command, but not both.
39897, 00000, "A required flashback log has been reused during flashback of a pluggable database."
// *Cause: At least one required flashback log has been reused during
// flashback of a pluggable database.
// *Action: You can no longer flashback this pluggable database to the same
// point-in-time as specified because a required flashback log file
// has been reused. You may still be able to flashback this
// pluggable database to a more recent point-in-time. You can also
// recover the pluggable database to undo the effect of the failed
// flashback pluggable database operation.
/============================================================================
/ 39901 - 39949 Reserved for Transportable Tablespace prvtplts
/============================================================================
39901, 0000, "Partitioned table %s.%s is partially contained in the transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: Check table partitions by querying SYS.DBA_TAB_PARTITIONS.
39902, 0000, "Subpartitioned table %s.%s is partially contained in the transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: Check table subpartitions by querying SYS.DBA_TAB_SUBPARTITIONS.
39903, 0000, "IOT Partition %s.%s is partially contained in the transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: Check table partitions by querying SYS.DBA_IND_PARTITIONS.
39904, 0000, "Partitioned object %s.%s is partially contained in the transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: Check partitions and overflow segments by querying
// SYS.DBA_IND_PARTITIONS and SYS.DBA_TAB_PARTITIONS.
39905, 0000, "Table %s.%s in tablespace %s points to LOB segment %s.%s in tablespace %s."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39906, 0000, "Constraint %s between table %s.%s in tablespace %s and table %s.%s in tablespace %s."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39907, 0000, "Index %s.%s in tablespace %s points to table %s.%s in tablespace %s."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39908, 0000, "Index %s.%s in tablespace %s enforces primary constraints %s of table %s.%s in tablespace %s."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39909, 0000, "Index %s.%s in tablespace %s points to table/cluster %s.%s in tablespace %s."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39910, 0000, "Partitioned Global index %s.%s in tablespace %s points to partition %s of table %s.%s in tablespace %s outside of transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39911, 0000, "Index %s.%s in tablespace %s points to partition %s of table %s.%s in tablespace %s outside of transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39912, 0000, "Partitioned index %s.%s in tablespace %s points to table %s.%s in tablespace %s outside of transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39913, 0000, "%s %s.%s in tablespace %s not allowed in transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39914, 0000, "Index %s.%s in tablespace %s points to subpartition %s of table %s.%s in tablespace %s outside of transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39915, 0000, "Partition %s of table %s.%s in tablespace %s points to LOB segment %s.%s in tablespace %s."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39916, 0000, "Subpartition %s of table %s.%s in tablespace %s points to LOB segment %s.%s in tablespace %s."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39917, 0000, "SYS owned object %s in tablespace %s not allowed in pluggable set"
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39918, 0000, "PLSQL Functional Index %s.%s in tablespace %s not allowed in transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39919, 0000, "Object %s.%s in tablespace %s not contained within transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: Check SYS.DBA_OBJECTS.
39920, 0000, "Rollback segment %s in tablespace %s not allowed in transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39921, 0000, "Default Partition (Table) Tablespace %s for %s not contained in transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39922, 0000, "Default Partition (Index) Tablespace %s for %s not contained in transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39923, 0000, "Default Composite Partition (Table) Tablespace %s for %s not contained in transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39924, 0000, "Default Composite Partition (Index) Tablespace %s for %s not contained in transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39925, 0000, "LOB segment %s.%s in tablespace %s points to table %s.%s in tablespace %s."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39926, 0000, "Join index between table %s.%s in tablespace %s and table %s.%s in tablespace %s."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39927, 0000, "Scoped REF constraint between table %s.%s in tablespace %s and table %s.%s in tablespace %s."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39928, 0000, "%s %s.%s in tablespace %s contains evolved type data that have not been upgraded."
// *Cause: Transportable tablespace operation could not be performed because
// some tables depending on evolved types were not upgraded.
// *Action: Transportable tablespace operation can only be performed when all
// tables depending on evolved types have been upgraded. Perform
// ALTER TABLE <tab_name> UPGRADE for the table name listed in the
// message above
39929, 0000, "Table %s.%s in tablespace %s has encrypted columns which are not supported."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39930, 0000, "Violation %s."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: Contact Oracle Support Services.
39931, 0000, "XML Schema %s Owner: %s not fully contained in the transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: Identify the associated elements and resolve self containment.
39932, 0000, "Extensible Index %s.%s not fully contained in the transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: Identify the associated table and list of secondary objects and resolve self containment.
39933, 0000, "Parent table %s.%s and its nested table columns are not fully contained in the transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: Identify the nested tables using view DBA_NESTED_TABLES and resolve self containment.
39934, 0000, "Materialized view log %s.%s in tablespace %s and master table %s.%s in tablespace %s are not fully contained in the transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39935, 0000, "Updatable materialized view log %s.%s in tablespace %s and materialized view %s.%s in tablespace %s are not fully contained in the transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39936, 0000, "Token manager for the CSX tablespace %s not fully contained in the transportable set."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: Include the specified tablespace into the transportable set.
39937, 0000, "Unsupported operation, default token tables used for binary XML data."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: Copy default token tables into a new token table set using DBMS_CSX_ADMIN package.
39938, 0000, "Operation not supported, tablespace %s contains binary XML data."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: None required.
39939, 0000, "More than one set of token tables are used in tablespace %s."
// *Cause: Informational message to describe a failure during transportable
// containment checking.
// *Action: Remap tables in the specified tablespace to use same token tables.
39940, 0000, "Child reference partitioned table %s.%s in tablespace %s or parent table %s.%s in tablespace %s is included but not both."
// *Cause: Informational message to describe a failure during transportable
// containment checking. Both parent and child reference partition
// tables must be included.
// *Action: Check reference partitioned tables.
39941, 0000, "Partitioned table %s.%s in tablespace %s has a partition that has an incomplete online move."
// *Cause: This is an informational message to describe a failure during
// transportable containment checking. Online moves need to be
// complete before transporting a tablespace.
// *Action: Use the DBMS_PART.CLEANUP_ONLINE_OP procedure to force the online move to complete.
39942, 0000, "Subpartitioned table %s.%s in tablespace %s has a subpartition that has an incomplete online move."
// *Cause: This is an informational message to describe a failure during
// transportable containment checking. Online moves need to be
// complete before transporting a tablespace.
// *Action: Use the DBMS_PART.CLEANUP_ONLINE_OP procedure to force the online move to complete.
39943, 0000, "Global index %s.%s in tablespace %s has orphaned entries."
// *Cause: This is an informational message to describe a failure during
// transportable containment checking. Orphaned entries need to be
// cleaned up before transporting a tablespace.
// *Action: Use DBMS_PART.CLEANUP_GIDX() to cleanup orphaned index entries.
39944, 0000, "Global partitioned index %s.%s in tablespace %s has orphaned entries."
// *Cause: This is an informational message to describe a failure during
// transportable containment checking. Orphaned entries need to be
// cleaned up before transporting a tablespace.
// *Action: Use DBMS_PART.CLEANUP_GIDX() to cleanup orphaned index entries.
39945, 0000, "Token conflicting with existing tokens."
// *Cause: The binary XML tokens contained in the imported tablespace
// conflicted with the existing tokens.
// *Action: Use the dump file export or import instead of transportable tablespace.
39946, 0000, "Nondefault token table encountered."
// *Cause: During transportable tablespace import, a nondefault token table
// was encountered.
// *Action: Use the dump file export or import instead of transportable tablespace.
/
39947, 00000, "Table %s.%s in tablespace %s has token tables in tablespace %s."
// *Cause : The token tables for the table were in a tablespace which was not
// being exported.
// *Action: Include the specified tablespace into the transportable set.
/
/ 39950 - 39999 - reserved PL/SQL related errors
39950, 00000, "invalid parameter for PLSQL warnings flag"
// *Cause: The user either entered invalid value for the PLSQL_WARNINGS
// flag or the value of the flag conflicts with other values.
// *Action: Enter correct values for the switch.
39951, 00000, "incomplete values specified for PL/SQL warning settings"
// *Cause: The user either did not enter the value for the settings or
// entered incomplete values.
// *Action: Enter correct syntax for the switch.
39952, 00000, "only numbers can be specified as range values"
// *Cause: The range values did not have numerical values only.
// *Action: Enter only numerical values.
39953, 00000, "the range value specified is beyond allowed range"
// *Cause: The range values were either too low or too high.
// *Action: Specify only the allowed range values.
39954, 00000, "DEFERRED is required for this system parameter"
// *Cause: The ALTER SYSTEM command for PLSQL_WARNINGS did not include the
// keyword, DEFERRED.
// *Action: Change the command to use the keyword, DEFERRED.
39955, 00000, "invalid PL/SQL warning message number"
// *Cause: The PL/SQL message number specified was not in a valid range.
// *Action: Specify PL/SQL warning message numbers within the valid range.
39956, 00000, "duplicate setting for PL/SQL compiler parameter %s"
// *Cause: A PL/SQL compiler parameter was set more than once.
// *Action: Remove the duplicate PL/SQL compiler setting.
39957, 0, "invalid warning category"
// MANUAL:
// INDEX: "WARNING"
// RELEASE: 10.0.0
// CAUSE: The category of the message was incorrect.
// ACTION: Specify a vaild category
39958, 0, "invalid warning category qualifier"
// MANUAL:
// INDEX: "WARNING"
// RELEASE: 10.0.0
// CAUSE: The category qualifier was incorrect.
// ACTION: Specify a vaild category qualifier.
39959, 0, "invalid warning number (%s)"
// MANUAL:
// INDEX: "WARNING"
// RELEASE: 10.0.0
// CAUSE: The warning number was incorrect.
// ACTION: Specify a vaild warning number.
39960, 0, "scope can only be SYSTEM or SESSION"
// MANUAL:
// INDEX: "WARNING"
// RELEASE: 10.0.0
// CAUSE: The scope specified was not set.
// ACTION: Specify a vaild scope, either SESSION or SYSTEM.
39961, 0, "message specified was not found"
// MANUAL:
// INDEX: "WARNING"
// RELEASE: 10.0.0
// CAUSE: The message number specified was not set.
// ACTION: specify the message number whise settings have been set
// in the given scope.
39962, 0, "invalid parameter for PLSQL_CCFLAGS"
// CAUSE: The value for the PLSQL_CCFLAGS parameter was not valid.
// ACTION: Specify a vaild value for the PLSQL_CCFLAGS parameter.
39963, 00000, "Trigger Runtime Debug event"
// *Document: NO
// *Cause:
// *Action:
// *Comment: This is a runtime trigger debugging event
39964, 0, "Specified value for _PLSQL_MAX_STACK_SIZE (%s) is larger than available memory (%s)"
// CAUSE: The value specified for the _PLSQL_MAX_STACK_SIZE parameter was larger
// than the amount of stack size available to the process.
// ACTION: Specify a smaller value for the _PLSQL_MAX_STACK_SIZE parameter.
39965, 0, "Collection of records with PL/SQL type attributes are not allowed in this context."
// CAUSE: The collection of records with attributes of PL/SQL types
// were not allowed as an argument to the TABLE operator.
// ACTION: Use the collection of records whose attributes are of the types
// that SQL can understand.
39966, 0, "This form is allowed only in WITH clause context"
// CAUSE: Only an entry point number was specified for SYS_PLSQL_CPU,
// SYS_PLSQL_COUNT or SYS_PLSQL_IO costing operator. This is allowed only
// when these operators are applied to functions appearing in the WITH clause.
// ACTION: Specify the required function, package, or type name. An optional
// schema name can also be specified.
39967, 0, "Cannot use this PL/SQL procedure while data files are being moved or rekeyed."
// CAUSE: Some data files were being moved or rekeyed either on the primary or
// standby database.
// ACTION: Check the status of data files and try this command again.
39968, 0, "Invalid value for parameter PLSCOPE_SETTINGS. Value must be from among 'IDENTIFIERS:[ALL|NONE|PLSQL|SQL|PUBLIC], STATEMENTS:[ALL|NONE]'."
// CAUSE: The value for the PLSCOPE_SETTINGS parameter was not valid.
// ACTION: Specify a vaild value for the PLSCOPE_SETTINGS parameter.
39969, 0, "Bind variable should be of a supported PL/SQL type"
// MANUAL:
// INDEX:
// RELEASE: 12.2
// CAUSE: A variable of a wrong type was used in the DBMS_SQL.BIND_VARIABLE_PKG call.
// In the DBMS_SQL.BIND_VARIABLE_PKG call, the type of the variable should be
// declared in a package specification and should be either a record or
// one of the supported collection types.
// ACTION: Use a bind variable whose type is one of the supported types
// for this operation and whose type is declared in a package specification.
39970, 0, "Bind calls are not allowed after cursor execution"
// MANUAL:
// INDEX:
// RELEASE: 12.2
// CAUSE: A bind call was used after the cursor was executed. Binds can only be
// done after the cursor was parsed but before execution.
// ACTION: Move the bind call before cursor execution.
39971, 0, "cannot use this PL/SQL procedure for this pluggable database when PATH_PREFIX information is not accessible"
// CAUSE: Some pluggable databases have specified PATH_PREFIX for security
// purposes, but the PL/SQL procedure was unable to check the
// PATH_PREFIX because the root was not open or for some other security
// reasons.
// ACTION: Open the root or connect to the root directly and try this command
// again.
///// EOF - Add errors till 40000 ABOVE this line. REGISTER at errorinf.txt
///// EOF - Add errors till 40000 ABOVE this line. REGISTER at errorinf.txt
///// 40001 - 41000 reserved for Data Mining at $(DMHOME)mesg/e40001.msg
///// MAX ERROR NUMBER 65535
//
// Copyright (c) 2001, 2018, Oracle and/or its affiliates. All rights reserved.
//
// NAME
// e40001.msg - Data Mining Error Messages
//
// DESCRIPTION
// Provides the Data Mining error messages for integration with the RDBMS
//
// NOTES
// Concatenated with other .msg files to build the RDBMS message file.
// If you change this file, do the following:
// cd $SRCHOME/rdbms/mesg
// gmake concat
// gmake oraus.msb
//
// MODIFIED (MM/DD/YY)
// sriksure 04/02/18 - Bug 27698424: Backport SODA bugs from main
// vjitta 03/02/18 - Bug 27365834: Adding new error for bulk inserts
// morgiyan 10/20/17 - Bug 27033953: Add 40687
// morgiyan 08/30/17 - Bug 26633401: Add 40685
// sriksure 08/08/17 - Bug 26591120: Add 40682
// yinlu 07/06/17 - bug 25462183: update cause of error 40469
// prthiaga 06/26/17 - Bug 26138602: Add 40679
// prthiaga 06/01/17 - Bug 26183549: Add 40675, 40676
// samys 05/11/17 - Bug 25886677: Add 40669,40670
// morgiyan 04/30/17 - Bugs 25537626,25537633,25655779,25798355,25972801
// prthiaga 03/01/17 - Add 40666
// bhammers 03/07/17 - bug 25684242: add 40666
// bhammers 02/08/17 - add 40667
// sriksure 02/21/17 - Bug 25552526: Add 40665
// bhammers 02/08/17 - add 40664
// prthiaga 02/15/17 - Bug 25559353: Add 40663
// ineall 02/10/17 - Bug 25353642: Change [dbslrn-1] to generic error
// bmilenov 02/07/17 - bug-25503310: edit error message 40212
// sriksure 01/11/17 - Add SODA errors
// ffeli 12/12/16 - Add 40171 to 40176 for algorithm registration
// jyarmus 10/21/16 - for exponential smoothing
// yacheche 09/12/16 - add CUR messages
// prthiaga 08/18/16 - Bug 24469409: Add 40655
// bhammers 03/11/15 - add 40651 and reformat to fit 80 chars per line
// prthiaga 03/10/16 - Bug 22905133: Add 40651 & 40652
// prthiaga 02/03/16 - Bug 22675745: Add 40620 to 40650
// sumkumar 02/17/16 - Bug 22747292: Add error message 40365
// qinwan 12/22/15 - R model empty input data error
// ffeli 12/14/15 - Bug 22280773: add R model error message
// yinlu 12/08/15 - bug 22319840: modify error 40599
// jyarmus 12/02/15 - modify 40031 for 12.2 bug 22019147
// jyarmus 11/23/15 - modify 40022 for 12.2 bug 22019147
// yinlu 11/20/15 - bug 22224064: add 40599
// qinwan 11/13/15 - Add R model error messages
// amozes 10/30/15 - #(22119239): prevent silent library load failure
// bmilenov 10/27/15 - Add EM filtered attributes message
// acolunga 09/17/15 - bug 21838734: change 40582 and 40583
// prthiaga 09/02/15 - Add 40597, 40598
// prthiaga 08/27/15 - Add mesg 40596
// alsakha 08/07/15 - Bug 20655745
// skabraha 07/27/15 - add 40595
// tinchen 06/23/15 - Bug 21079411: add mesg 40507
// alsakha 06/18/15 - Bug 20963331, mesg 40237
// zliu 05/27/15 - add mesg 40576
// amozes 05/26/15 - #(21121420): prevent partition mismatch
// nihao 05/26/15 - add 40034
// nihao 05/04/15 - No valid covariance matrix messages
// acolunga 04/23/15 - Adding 40589 and 40590
// bmilenov 04/20/15 - bug-20877814: No model and zero norm messages
// dbai 03/09/15 - validate including/excluding rule settings
// tinchen 02/24/15 - Bug 20282871: Adding 40506
// dbai 02/14/15 - bug 20542280: add 40236
// anamiris 02/02/15 - Bug 6194865: Adding 40505
// bmilenov 01/16/15 - bug-6614289: Upper bound for KM clusters
// yinlu 01/09/15 - data guide related error message
// amozes 12/24/14 - #(20263259): add 40139
// anamiris 12/03/14 - Bug 19802640 : Adding 40504
// dbai 12/01/14 - add 40235: validate AR aggregates setting
// sumkumar 10/22/14 - Bugs 19545730/19545735 : Add 40363 for disallowing
// sysdba/sysoper admin privilege grants to SYS user
// prthiaga 08/18/14 - Add 40558
// prthiaga 08/18/14 - add 40559
// skabraha 07/31/14 - add 40557
// prthiaga 05/06/14 - Add 40554
// jim 03/31/13 - reserve 40551-40600 for JSON, add 40551, 40552
// for json/bson conversion
// bhammers 03/03/13 - add 40500 as JSON event
// zliu 12/23/13 - fix bug 17993901
// bhammers 12/12/13 - add more err messages for JSON
// hxzhang 11/26/13 - fix bug 17854856
// zliu 11/05/13 - fix bug 17745102
// zliu 10/30/13 - add error msg for json_textcontains()
// ineall 07/18/13 - claim range 40501 - 40550 for recovery
// mmcracke 06/20/13 - proj 47099 partitioned model
// bhammers 04/04/13 - claim range 40441 - 40500 for JSON err mesg
// jyarmus 09/06/12 - bug 14571812
// pstengar 04/24/12 - #(13977291):add 40422 OC does not handle TEXT
// yincwang 02/28/12 - #(13784455):add 40123
// amozes 09/13/11 - desupport ABN
// jyarmus 12/13/10 - Fix typo per reviewer comment in message 40030
// pstengar 12/10/10 - add msgs for unstructured text support project
// jyarmus 11/30/10 - add too many forced-in features message
// jyarmus 11/29/10 - modify message 40030 to include forced in features
// amozes 10/15/10 - Add 40342 and 40343
// bmilenov 10/12/10 - SVD error edits based on errors_us feedback
// amozes 10/12/10 - #(10193686): minor wording change to 40307
// pstengar 04/29/10 - modify 40390, 40391 and 40392
// mmcracke 03/10/10 - Add message for invalid reverse transformation
// amozes 12/09/09 - #(8564529): modify cause/action for 40103
// amozes 12/09/09 - (#6439334): clarify the term label
// pstengar 10/27/09 - PMML
// mmcracke 07/24/09 - bug# (8715612) add NMF exception for maxattr
// exceeded
// jyarmus 11/03/08 - enable intercept-only models
// jyarmus 09/30/08 - add weight column error message
// mmcampos 09/22/08 - #(5990796): same data in all rows error for k-means
// using cosine distance
// jyarmus 08/04/08 - temporarily make intercept only model throw an error
// amozes 05/06/08 - #(6868134): disable force drop for other schemas
// jyarmus 03/24/08 - incorporate comments of errors_us in action clause
// of error 40030
// jyarmus 03/20/08 - add error when final glm model build fails after row
// sampling for feature selection
// ramkrish 05/02/07 - add transactional data errors
// ramkrish 03/17/08 - support class weights for SVM along with priors
// bmilenov 10/17/07 - Add SVD messages
// jyarmus 02/28/08 - fix bug 6764805 GLM inappropriately drops the
// diagnostics table
// ramkrish 04/24/07 - 40341 - prevent model table access by user
// pstengar 10/25/07 - add score_criterion_type error msg
// amozes 04/12/07 - add error for large DT nested
// bmilenov 03/09/07 - Add glm error when cholesky decomposition fails with
// ridge on
// dmukhin 10/25/06 - bug 5462460: alter reverse expression
// mmcracke 10/23/06 - Fix string place holders for 40209
// jyarmus 10/25/06 - changes based on comments from errors_us
// jyarmus 10/23/06 - changes for review comments
// jyarmus 10/12/06 - add glm messages
// bmilenov 10/10/06 - Add data load and GLM error messages
// ramkrish 09/15/06 - remove 40294 - predb will return NULL instead
// amozes 09/07/06 - #(5447028): make 40271 more generic for AI
// bmilenov 08/22/06 - Edit GLM error messages
// jyarmus 08/17/06 - add error message when user disables ridge and XT X
// is singular and an error message when there are too
// many attributes to construct a fisher matrix in
// memory
// ramkrish 08/03/06 - add 40294
// ramkrish 07/25/06 - modify cause for 40292
// amozes 07/28/06 - add error 40263 for NMF builds
// dmukhin 07/20/06 - prj 18875: stack interface
// amozes 07/05/06 - #(5375230): fix error message 40306
// amozes 06/01/06 - generalize 40306
// dmukhin 05/30/06 - prj 18875: stack interface
// dmukhin 05/15/06 - prj 18876: scoring cost matrix
// ramkrish 05/23/06 - add GLM errors
// dmukhin 04/28/06 - ADP: errors
// xbarr 03/13/06 - Add 40350 - downgrade error mesg
// mmcracke 01/18/06 - Add Duplicate Model Table mesg
// gtang 08/22/05 - Add 40323
// gtang 11/02/04 - Add 40321 and 40322 used for clustering model
// jyarmus 10/07/04 - restore error message 40217 used by dmsvmb.c
// jyarmus 08/11/04 - add error message - one class model cannot take
// priors
// ramkrish 07/29/04 - 3754809: add 40290 and 40291
// amozes 07/29/04 - 40306 - no wide data for tree
// mjaganna 07/26/04 - Add Decision tree error messages
// dmukhin 07/12/04 - 40288 - DMF; mining model load debugging
// and tracing
// ramkrish 06/29/04 - 40289 - duplicate attributes
// ramkrish 06/29/04 - 40287 for KM cosine model
// xbarr 06/25/04 - xbarr_dm_rdbms_migration
// bmilenov 05/27/04 - create specific exception for repeated
// target or attribute
// dmukhin 05/12/04 - DMF: no remote support
// amozes 04/30/04 - upgrade/downgrade by SYS
// dmukhin 04/15/04 - DMF: error messages
// mmcracke 03/15/04 - Add new SVM delete_class error messages
// pstengar 10/02/03 - Modified action description for error 40105
// cbhagwat 07/10/03 - Gina review comments
// cbhagwat 07/08/03 - put 40214 back
// mmcracke 06/25/03 - NMF parameter error
// ramkrish 06/13/03 - chg 40107
// gtang 05/22/03 - modify text for 40222 and 40223
// jyarmus 05/16/03 - add exception when classification model
// is presented with only a single unique
// target value
// cbhagwat 05/09/03 - Add factoring error
// cbhagwat 05/08/03 - code review changes
// pstengar 04/03/03 - Added message for model locking
// mmcracke 04/03/03 - Add messaging to NMF
// cbhagwat 04/01/03 - cost matrix error
// gtang 03/28/03 - Add export/import errors
// cbhagwat 03/21/03 - message for DBMS_DM computes
// cbhagwat 03/14/03 - dbms_dm edits
// bbloom 03/04/03 - Add error messages for ABN
// cbhagwat 02/24/03 - 40103 message change
// jyarmus 02/13/03 - add an error message for requesting rules
// for a non-Single Feature ABN Model
// pkuntala 02/14/03 - removed NMF exception, instead reuse 40206
// ramkrish 02/10/03 - modify message for 40210
// bmilenov 01/13/03 - Add exceptions for mismatched prior and cost
// matrix tables
// cbhagwat 01/14/03 - change error message for dbms_dm
// ramkrish 01/10/03 - refine/generalize 40215 for model-op
// incompatibility
// cbhagwat 12/26/02 - feature not supported
// pstengar 12/11/02 - Added model not of CLASSIFICATION type
// cbhagwat 12/11/02 - duplicate setting
// cbhagwat 12/03/02 - Adding data type errors for dbms_dm
// ramkrish 11/13/02 - cleanup for RDBMS integration
// ramkrish 11/13/02 - add BLAST messages
// jyarmus 11/12/02 - add SVM messages
// pkuntala 11/11/02 - add NMF messages
// cbhagwat 11/01/02 - add PL/SQL API and some generic messages
// ramkrish 09/12/02 - creation
/
/ 40001 - 40020 RESERVED FOR BLAST
/
40001, 00000, "value for %s must be greater than zero"
// *Cause: The input parameter in question has a value of zero or less.
// *Action: Provide a value greater than zero for the relevant parameter.
/
40002, 00000, "wordsize must be %s or greater"
// *Cause: The input wordsize is less than the prescribed limit for the
// BLAST Match or Align algorithm.
// *Action: Provide a wordsize greater than or equal to the prescribed value.
/
40003, 00000, "wordsize must be in the range %s - %s for BLAST-P"
// *Cause: The input wordsize has a value out of the prescribed range.
// *Action: Provide a wordsize value within the prescribed range for BLAST-P.
/
40004, 00000, "penalty must be negative for BLAST-N"
// *Cause: The input value provided for penalty is zero or greater.
// *Action: Provide a negative penalty value.
/
/
/ 40021 - 40040 RESERVED FOR GLM
/
40021, 00000, "no column named %s in training table %s"
// *Cause: The training table does not contain the specified column
// *Action: Provide a case-id/target column that exists in the training table
/
40022, 00000, "null case ID column - cannot provide row diagnostics"
// *Cause: The row diagnostics were enabled, but without a
// corresponding case or row identifier column in the build data.
// *Action: Provide a non-null case identifier column in the build data.
/
40023, 00000, "sufficient memory could not be allocated given the number of attributes"
// *Cause: Unable to allocate sufficient memory to create a model
// capable of producing confidence bounds on predictions because
// there were too many attributes or there were high cardinality
// categorical attributes, or both, in the build data.
// *Action: Reduce the number of attributes, especially high cardinality
// categoricals, or enable ridge regression.
/
40024, 00000, "solution to least squares problem could not be found"
// *Cause: Unable to find solution because the predictor covariance matrix
// was singular.
// *Action: Enable ridge regression or remove exact multicollinearities from
// the build data.
/
40025, 00000, "reference class name not found in build data"
// *Cause: The provided reference class name was not found in the
// build data.
// *Action: Provide an existing target value as the reference class name.
/
40026, 00000, "reference class name not found in the weights table"
// *Cause: The provided reference class name did not correspond to any
// of the entries in the weights table.
// *Action: Provide consistent specification for reference class name
// and weights table.
/
40027, 00000, "Target attribute has more than two distinct values"
// *Cause: Generalized Linear Models only support binary classification.
// *Action: Consolidate target values into two distinct categories.
/
40028, 00000, "solution to least squares problem could not be found"
// *Cause: Unable to find solution because the predictor build data
// were not properly scaled.
// *Action: Standardize the predictor build data by enabling auto prep.
/
40029, 00000, "Specified diagnostics table name already exists"
// *Cause: A diagnostics table name matching an existing table was specified.
// *Action: Choose a table name that does not match any existing user table.
/
40030, 00000, "solution to least squares problem could not be found"
// *Cause: Unable to find solution because the predictor covariance matrix
// was singular for the forced-in features.
// *Action: If there are forced-in features, remove them.
// If GLMS_FTR_ACCEPTANCE was set to GLMS_FTR_ACCEPTANCE_STRICT,
// reset it to GLMS_FTR_ACCEPTANCE_RELAXED and rebuild the model.
/
40031, 00000, "too many forced-in features (maximum allowable 1000)"
// *Cause: Too many forced-in features were specified or the features
// were high cardinality attributes, or both.
// *Action: Reduce the number of forced-in attributes.
/
40032, 00000, "solution to least squares problem could not be found"
// *Cause: Unable to find solution because the predictor covariance matrix
// was singular for the selected features.
// *Action: If GLMS_FTR_ACCEPTANCE was set to GLMS_FTR_ACCEPTANCE_STRICT,
// reset it to GLMS_FTR_ACCEPTANCE_RELAXED and rebuild the model.
/
40033, 00000, "invalid covariance matrix"
// *Cause: This was caused by one or more of the following:
// - Data rows were too few in number.
// - Mining attributes were too many.
// - Ridge regression was on.
// *Action: Modify the data or disable ridge regression to get a valid
// covariance matrix and full diagnostic statistics.
/
/ 40101 - 40180 Generic Errors Across All Data Mining Algorithms
/
40034, 00000, "FORCE_IN incompatible with the setting GLMS_FTR_SELECTION disabled"
// *Cause: The setting GLMS_FTR_SELECTION which was disabled was incompatible
// with the specified FORCE_IN transformation.
// *Action: Either enable the setting GLMS_FTR_SELECTION, or respecify the
// FORCED_IN transformation to be compatible with the
// disabled GLMS_FTR_SELECTION setting.
/
/
/ 40051 - 40060 RESERVED FOR Exponential smoothing
/
40051, 00000, "too few rows to estimate the specified model"
// *Cause: The time series had fewer rows than the number of parameters in
// the model.
// *Action: Choose a simpler model type with fewer parameters.
/
40052, 00000, "series contains large numbers; possible numerical instability"
// *Cause: The time series contained numbers greater than 1 million.
// *Action: Scale the data.
/
40053, 00000, "inappropriate data for multiplicative model"
// *Cause: The time series was not strictly positive.
// *Action: Choose a model type that does not contain a multiplicative trend
// or seasonality.
/
40054, 00000, "time series is constant"
// *Cause: The time series was constant.
// *Action: Choose a model type that does not contain a multiplicative trend
// or seasonality.
/
40055, 00000, "too few rows to estimate trend"
// *Cause: The time series had too few rows to obtain an initial trend
// estimate.
// *Action: Choose a simple exponential model type.
/
40056, 00000, "must provide a valid EXSM_INTERVAL setting"
// *Cause: A valid value was not specified for the EXSM_INTERVAL setting. If
// the case ID column type is datetime, a valid EXSM_INTERVAL setting
// must be provided.
// *Action: Specify a valid EXSM_INTERVAL setting.
/
40057, 00000, "must provide a valid case ID column"
// *Cause: The case ID column was required to provide time labels, but a
// valid case ID column was not provided.
// *Action: Specify a valid case ID column name as input.
/
40058, 00000, "seasonal effect not estimable for irregular time series"
// *Cause: There was no consecutive one year period containing all existing
// seasons.
// *Action: Choose a model type with no seasonal effect.
/
40101, 00000, "Data Mining System Error %s-%s-%s"
// *Cause: An internal system error occured during a data mining operation.
// *Action: Contact Oracle Support Services.
/
40102, 00000, "invalid input %s for data mining operation %s"
// *Cause: The input parameter is either null or invalid for the given
// operation.
// *Action: Provide a valid value. Check range for NUMBER parameters.
/
40103, 00000, "invalid case-id column: %s"
// *Cause: The case-id column was invalid.
// If a case-id column is specified, it must be present in the
// input data source. The case-id column cannot be the same
// as the target column, and the column's data type is restricted
// to NUMBER, CHAR, and VARCHAR2 when building a GLM model with
// a diagnostics table.
// *Action: Change the schema of your input data to supply a case-id column
// of appropriate data type.
/
40104, 00000, "invalid training data for model build"
// *Cause: The training data provided in the reported table is unsuitable for
// build, either because it is empty, has unsuitable data, or the
// schema of the table does not match the input specifications.
// *Action: Inspect the training data and correct the contents/schema as
// appropriate.
/
40105, 00000, "input data incompatible with model signature"
// *Cause: The data provided for this post-build operation is in format
// different from that used for model build.
// *Action: Provide data whose attribute data types match the build data.
// Input data attributes must have the same data types as
// those described in the model signature for the model.
/
40106, 00000, "positive target value not specified for computing Lift"
// *Cause: Positive target value has not been specified for Lift.
// *Action: Provide a positive target value for the Lift operation.
/
/
40107, 00000, "operation requires %s option to be installed"
// *Cause: The specified option has not been installed with the RDBMS.
// *Action: Install the reported option and retry the operation.
/
40108, 00000, "input data contains too few distinct target (%s) values"
// *Cause: At least two distinct target values are required for Build.
// *Action: Provide counter-example target values in the input data.
/
40109, 00000, "inconsistent logical data record"
// *Cause: Repeated instances of a record identifier or repeated
// attribute(s) in a nested column.
// *Action: Remove or re-label repeated instances to resolve inconsistencies.
/
40110, 00000, "Duplicate model tables found for table type %s"
// *Cause: Operation would result in duplicate model table types which is
// not supported.
// *Action: Remove the duplicate entry.
/
40111, 00000, "no mining attributes found in build data"
// *Cause: Could not build a model when only special or empty columns were
// present. Special columns include target, row weight,
// and case ID columns.
// *Action: Provide mining attribute data.
/
40112, 00000, "insufficient number of valid data rows"
// *Cause: Fewer than two valid data rows were found in the
// build data.
// *Action: Provide at least two valid build data rows. If the model is
// either a classification or regression model, then valid rows must
// have non-NULL targets. If a weight column was provided, then valid
// rows must have positive row weights. In addition, if DELETE_ROW
// missing value treatment was used, consider disabling it.
/
40113, 00000, "insufficient number of distinct target values"
// *Cause: Less than two distinct target values were found in the build data.
// *Action: Provide the classification build data with valid rows containing
// at least two distinct target values. Valid rows must
// have non-NULL targets. If a weight column was provided, then valid
// rows must have positive row weights. In addition, if DELETE_ROW
// missing value treatment was used, consider disabling it.
/
40114, 00000, "weights table target values mismatched with build data"
// *Cause: The entries in the weights table did not correspond
// to the target values in the build data.
// *Action: Verify the entries in the weights table.
/
40115, 00000, "weights table schema is incorrect"
// *Cause: The weights table did not have the required schema.
// *Action: Provide a weights table with schema: (target_value, weight),
// where the type of the first column corresponds to the type of
// the target column (CHAR, VARCHAR2 or NUMBER) and the type of
// the second column is NUMBER.
/
40116, 00000, "NULL values found in weights table"
// *Cause: The weights table had NULL entries.
// *Action: Replace or eliminate all NULL entries in the weights table.
/
40117, 00000, "repeated target values found in weights table"
// *Cause: The weights table had repeated target values.
// *Action: Remove the repeated target values from the weights table.
/
40118, 00000, "insufficient number of target values in weights table"
// *Cause: The weights table had less that 2 target values.
// *Action: Provide at least two target values in the weights table.
/
40119, 00000, "nested columns incompatible with missing value treatment"
// *Cause: delete_row missing value treatment is not supported
// for nested columns.
// *Action: Use 2D (non-nested) data representation or manually
// delete the rows with NULL values and disable the delete_row
// missing value treatment.
40120, 00000, "invalid weight value in the weights table"
// *Cause: Negative or zero weight values were found in the weights table.
// *Action: Ensure that weight values in the weights table are positive.
/
40121, 00000, "force option not allowed for drop model in different schema"
// *Cause: The force option was specified, but the model is in
// a different schema.
// *Action: If the force option is necessary, run the drop model from
// the owning schema. If the force option is not necessary,
// set the force parameter to FALSE.
/
40122, 00000, "invalid data type for row weights column %s."
// *Cause: Row weights column was not assigned one of the allowed data types.
// *Action: Choose a row weight column of type NUMBER or FLOAT.
/
40123, 00000, "invalid row weights column %s"
// *Cause: Row weights column was the same as the target column.
// *Action: Choose a new row weights column.
/
40124, 00000, "partition key column %s missing from input"
// *Cause: A partitioned model was referenced in the query, but
// the partition key column was not found in the input.
// *Action: Provide an input dataset containing the partition key column.
/
40125, 00000, "partition %s does not exist"
// *Cause: The partition entered did not exist.
// *Action: Check the spelling of the partition and try again.
/
40126, 00000, "model %s is not partitioned"
// *Cause: The model specified was not a partitioned model.
// *Action: Specify a model that is partitioned.
/
40127, 00000, "invalid number of partition keys specified"
// *Cause: The number of partition keys specified did not match
// the model.
// *Action: Specify key values for each partition.
/
40128, 00000, "partition %s exists for partition keys specified"
// *Cause: A partition already existed for the partition keys specified.
// *Action: Specify unique key values for each partition.
/
40129, 00000, "partition name %s exists for this model"
// *Cause: The partition name specified was not unique for this model.
// *Action: Specify a unique partition name.
/
40130, 00000, "invalid partition name %s"
// *Cause: The partition name specified was not valid.
// *Action: Check the spelling of the partition name and try again.
/
40131, 00000, "invalid data type for partition column %s"
// *Cause: The partition column did not have a supported data type.
// *Action: Choose a partition column of type NUMBER, CHAR, or VARCHAR2.
/
40132, 00000, "partition not specified"
// *Cause: A model partition was not specified.
// This function requires the specification of a model partition.
// *Action: Specify a model partition.
/
40133, 00000, "invalid partition columns"
// *Cause: The partition columns in the operation did not match those in the
// existing model.
// *Action: Specify the correct partitioning keys.
/
40134, 00000, "OAA debug event"
// *Cause:
// *Document: NO
// Level 1 - force 40138 during multi-DDL operation.
// Level 2 - force 40138 during multi-DDL operation.
// Level 4 - force 40138 during multi-DDL operation.
// *Action: Set this event only under the supervision of Oracle development.
/
40135, 00000, "cannot drop the only partition of a partitioned model"
// *Cause: The specified partitioned model contained a single partition.
// An empty model is not supported.
// *Action: Drop the model, or add additional partition(s) then drop the
// desired partition.
/
40136, 00000, "maximum number of partition columns exceeded"
// *Cause: The maximum number of 16 partition columns was exceeded.
// *Action: Reduce the number of partition columns.
/
40137, 00000, "maximum number of partitions exceeded"
// *Cause: The maximum number of partitions per model was exceeded.
// *Action: Reduce the number of partitions.
/
40138, 00000, "atomicity check"
// *Cause:
// *Document: NO
// *Action: Return this error only under the supervision of Oracle development.
/
40139, 00000, "no partitions found in training data"
// *Cause: There were no partitions found in the training data.
// *Action: Specify partitioning keys that have one or more distinct
// values in the training data.
/
40140, 00000, "model could not be built"
// *Cause: The training data did not allow the building of a meaningful model.
// *Action: Modify the training data to ensure that there are valid data
// rows, columns, or targets. If there is solver choice,
// ensure that the selected solver is appropriate for the
// training data.
/
40141, 00000, "only zero norm rows were provided in the training data"
// *Cause: All training data rows had zero norm.
// *Action: Modify the training data or enable automatic data preparation.
/
40142, 00000, "partition mismatch for feature comparison"
// *Cause: The partition key column values did not match for one or
// more scored rows.
// *Action: Modify the query to ensure that each scored row contains
// matching partition key column values.
/
40150, 00000, "Model %s function is not specified."
// *Cause: The required R function was not specified.
// *Action: Specify the required R function in the model setting table and
// build the R model.
/
40151, 00000, "invalid output type from R SCORE, WEIGHT, or DETAILS function"
// *Cause: The R SCORE, WEIGHT, or DETAILS function did not return the result
// in a data.frame containing either R numeric values for SCORE and
// WEIGHT function or R numeric or string values for DETAILS
// function.
// *Action: Modify the R function to return the result in a data.frame
// that contains values of valid types.
/
40152, 00000, "Output data.frame mismatches the input for R SCORE or WEIGHT function."
// *Cause: The R SCORE or WEIGHT function returned a different number of rows
// than that of the input data.frame.
// *Action: Modify the R function to output the result for each row of
// the input data.frame.
/
40153, 00000, "invalid value on attribute %s for R model"
// *Cause: The specified attribute was not a scalar numeric value or
// a single string.
// *Action: Set the specified attribute of the R model with a valid value.
/
40154, 00000, "invalid type or value for R parameter specification"
// *Cause: The R parameter was not a scalar numeric value or a single
// string.
// *Action: Modify the parameter specification to use either a scalar
// numeric value or a single string.
/
40155, 00000, "R script %s is not found."
// *Cause: The specified script was not found in the R script repository.
// *Action: Verify that the script exists in the R script repository or
// create it using the rqScriptCreate PL/SQL function.
/
40156, 00000, "invalid or mismatched output specification for R model view"
// *Cause: The R DETAILS function output format specfication did not use
// numeric or string value, or did not match the actual output
// from the R DETAILS function.
// *Action: Use scalar numeric and string to specify the R DETAILS function
// output format and match the actual output of the R function.
/
40157, 00000, "R_HOME is not set on %s."
// *Cause: The R_HOME was not set to the location where R was installed.
// *Action: Use sys.rqConfigSet to set the R_HOME to the correct value.
/
40158, 00000, "invalid values on R memory control settings"
// *Cause: The R memory control settings did not use positive values.
// *Action: Use sys.rqConfigSet to set R memory control with valid values.
/
40159, 00000, "Parameter setting %s is not specified for R model."
// *Cause: The expected setting was not on the model setting table.
// *Action: Set the expected setting on the model setting table.
/
40160, 00000, "Mining function %s requires attribute %s on the R model."
// *Cause: The generated R model did not have the required attribute.
// *Action: Set the required attribute for the R model in the R BUILD function.
/
40161, 00000, "Either attribute %s or %s, but not both, is required."
// *Cause: Conflict attributes were specified for the R model object.
// *Action: Set the required attribute only for the return R model object.
/
40162, 00000, "mismatched results from %s output data.frame"
// *Cause: The R regression model prediction did not return an R data.frame
// with a single column of numerics for predicted value, or two
// additional columns containing the standard error of model fit and
// the degree of freedom were missing from the output when SQL
// function prediction_bounds was invoked.
// *Action: Modify the specified R function to return the results in the
// right format.
/
40163, 00000, "some prediction results missing from %s output"
// *Cause: The R classification, clustering, or feature extraction model
// SCORE function did not return the prediction for each class,
// cluster, or feature respectively in the output R data.frame.
// *Action: Modify the R model SCORE function to return all predicted values
// in the output data.frame.
/
40164, 00000, "contribution weights of some attributes missing from %s output"
// *Cause: The R model WEIGHT function did not return the contribution weight
// for each attribute of the data.
// *Action: Modify the R model WEIGHT function to return the contribution
// weights for all attributes.
/
40165, 00000, "mismatched target class name from R model prediction %s"
// *Cause: The R classification model prediction did not have correct target
// class names assigned as the column names for the return data.frame.
// *Action: Modify the R classification model SCORE function to set the correct
// target class names on the return data.frame.
/
40166, 00000, "invalid R name for input data.frame columns"
// *Cause: The input data.frame column names contained special characters that
// are not supported by R.
// *Action: Modify the input data.frame column names and remove the
// unsupported characters from the column names.
/
40167, 00000, "no valid data in input table"
// *Cause: The specified input table contained no valid data to build R model.
// *Action: Insert valid data into the input table to build R model.
/
40170, 00000, "Error out in R: %s "
// *Cause: The R function execution failed.
// *Action: Verify the specified R model function script.
/
40171, 00000, "The algorithm cannot be dropped because there are models built on it."
// *Cause: An attempt was made to drop models built on this algorithm.
// *Action: Drop the model first.
/
40172, 00000, "The algorithm registration does not follow the predefined JSON schema."
// *Cause: An attempt was made to register an algorithm that did not follow the predefined
// JavaScript Object Notation (JSON) schema.
// *Action: Check the predefined JSON schema and revise the algorithm format.
/
40173, 00000, "The same algorithm name, mining function, and algorithm type combination already exits."
// *Cause: An attempt was made to register an algorithm with the same name, mining function and type combination.
// *Action: Use a different algorithm name for the same mining function and algorithm type.
/
40174, 00000, "The algorithm that is used is not registered yet."
// *Cause: The specified algorithm did not exist.
// *Action: Register the algorithm first.
/
40175, 00000, "Registered algorithm name and R script definition cannot be used simultaneously."
// *Cause: An attempt was made to use both registered algorithm name and R scripts definition.
// *Action: Keep either registered algorithm name or R script definition, but not both.
/
40176, 00000, "The current user does not have privilege to register or drop an algorithm."
// *Cause: The privileges to register or drop an algorithm were not granted.
// *Action: Obtain the proper privileges before attempting to register or drop an algorithm.
/
/ 40181 - 40200 RESERVED FOR DBMS_DATA_MINING_TRANSFORM
/
40181, 00000, "invalid transformation definition for column %s"
// *Cause: Transformation definition has duplicate or NULL columns.
// *Action: Provide a valid transformation definition specification.
/
40182, 00000, "invalid column reference"
// *Cause: Transformation expression has no column references or more than
// one reference or the reference is qualified.
// *Action: Provide a valid expression.
/
40183, 00000, "invalid stack definition for attribute %s"
// *Cause: Stack definition expression or reverse expression has syntax
// errors or it does not match the transformation definition.
// *Action: Provide a valid expression.
/
40184, 00000, "transformation definition does not match the data"
// *Cause: Transformation definition specifies nested transformation for
// non-nested data or it removes all of the columns.
// *Action: Provide a valid data.
/
/ 40201 - 40250 RESERVED FOR DBMS_DATA_MINING
/
40201, 00000, "invalid input parameter %s"
// *Cause: The input parameter was either null or invalid.
// *Action: Provide a valid value for the input parameter.
/
40202, 00000, "column %s does not exist in the input table %s"
// *Cause: The column was missing from the table.
// *Action: Correct the table schema and/or provide the correct column name.
/
40203, 00000, "model %s does not exist"
// *Cause: The model did not exist.
// *Action: Supply a valid model name.
/
40204, 00000, "model %s already exists"
// *Cause: A model by the same name exists.
// *Action: Provide a different, unique name for the model.
/
40205, 00000, "invalid setting name %s"
// *Cause: The input setting name was invalid.
// *Action: Consult the documentation for the settings table and provide
// a valid setting name.
/
40206, 00000, "invalid setting value for setting name %s"
// *Cause: The input value for the given setting name was invalid.
// *Action: Consult the documentation for the settings table and provide
// a valid setting value.
/
40207, 00000, "duplicate or multiple function settings"
// *Cause: The input settings table contained settings for multiple
// mining functions.
// *Action: Provide setting(s) for a single function in the settings table.
/
40208, 00000, "duplicate or multiple algorithm settings for function %s"
// *Cause: The input settings table had duplicate or multiple algorithm
// settings for a mining function.
// *Action: Provide only one appropriate algorithm setting for the
// mining function.
/
40209, 00000, "setting %s is invalid for %s function"
// *Cause: The specified setting was not supported for the
// mining function supplied.
// *Action: Provide appropriate combination of function and algorithm settings.
/
40210, 00000, "invalid score criterion type when cost matrix is specified"
// *Cause: The score criterion type may not be 'PROBABILITY' when a cost matrix
// is specified.
// *Action: Set score criterion type to 'COST' or don't specify a cost matrix.
/
40211, 00000, "algorithm name %s is invalid"
// *Cause: Algorithm name for the model was invalid or the operation was
// not valid for the algorithm.
// *Action: Check the algorithm name for the model and verify that the
// operation is valid.
/
40212, 00000, "invalid target data type in input data for %s function"
// *Cause: Target data type was invalid.
// *Action: Classification and attribute importance functions accept CHAR,
// VARCHAR2, and NUMBER data type targets. VARCHAR2 data type targets
// longer than 4000 bytes are not supported.
// Regression and time series functions accept NUMBER, BINARY_DOUBLE,
// and BINARY_FLOAT data type targets only.
/
40213, 00000, "contradictory values for settings: %s, %s"
// *Cause: The settings values were not compatible.
// *Action: Check the documentation and change the setting value(s).
/
40214, 00000, "duplicate setting: %s"
// *Cause: Duplicate setting in the settings table.
// *Action: Remove the duplicate setting from the settings table.
/
40215, 00000, "model %s is incompatible with current operation"
// *Cause: The current operation was not supported for the mining function
// the model corresponds to.
// *Action: Provide the model name suitable for current operation.
/
40216, 00000, "feature not supported"
// *Cause: The feature was not supported in the API.
// *Action: Modify the code to avoid usage of the feature.
/
40217, 00000, "priors table mismatched with training data"
// *Cause: The entries in the priors table do not correspond
// to the targets in the training data.
// *Action: Verify the entries in the priors table.
/
40218, 00000, "Both priors table and weights table are specified"
// *Cause: Both a priors table and a weights table are specified for
// SVM model build.
// *Action: Priors table is the old (pre 11g) mechanism for specifying
// class weights, and class weights table is the new (and correct)
// way to specify class weights. Remove the priors table entry
// from the settings table (after transferring class weight settings,
// if appropriate). Going forward, priors table will be valid
// only for NB models. Use class weights for SVM.
/
40219, 00000, "apply result table %s is incompatible with current operation"
// *Cause: The current operation was not allowed for the apply
// result table supplied.
// *Action: Ensure that the operation being performed is valid for the mining
// function used to build the model (using for which the apply
// result table was created).
/
40220, 00000, "maximum number of attributes exceeded"
// *Cause: The data had too many attributes.
// *Action: Reduce the dimensionality of the data.
/
40221, 00000, "maximum target cardinality exceeded"
// *Cause: The target cardinality of the training data was too high.
// *Action: Reduce the target cardinality.
/
40222, 00000, "data mining model export failed, job name=%s, error=%s"
// *Cause: The model export job failed.
// *Action: Check export job settings as required by DataPump.
/
40223, 00000, "data mining model import failed, job name=%s, error=%s"
// *Cause: The model import job failed.
// *Action: Check import job settings as required by DataPump.
/
40224, 00000, "must specify a valid ID column name when setting %s is provided"
// *Cause: The training data is transactional. A valid ID column
// must be specified.
// *Action: Specify a valid ID column name as input.
/
40225, 00000, "model is currently in use by another process"
// *Cause: The model is currently in use by another process.
// *Action: Retry if necessary.
/
40226, 00000, "model upgrade/downgrade must be performed by SYS"
// *Cause: Upgrade/Downgrade routines are being invoked by a
// user with insufficient privilieges.
// *Action: Run the routines as SYS during migration.
/
40227, 00000, "invalid transformation attribute"
// *Cause: Transformation list provided to CREATE_MODEL has duplicate or NULL
// attributes. Case ID or target attribute has attribute_subname that
// is not NULL. Attribute provided to ALTER_REVERSE_EXPRESSION does
// not exist in the model.
// *Action: Remove NULLs and duplicates and fix case ID and target attributes
// or provide a valid attribute for a given model.
/
40228, 00000, "scoring cost matrix already exists"
// *Cause: The model already has a scoring cost matrix.
// *Action: To add a new scoring cost matrix the existing one should be
// removed first.
/
40229, 00000, "scoring cost matrix not found"
// *Cause: The model does not have a scoring cost matrix.
// *Action: To remove a scoring cost matrix the model should have one.
/
40230, 00000, "invalid transformation expression"
// *Cause: Expression has syntax or semantic errors.
// *Action: Provide a valid expression.
/
40231, 00000, "transactional input incompatible with specified algorithm"
// *Cause: Training data in transactional format is not accepted for
// model creation using the specified mining algorithm.
// *Action: Pivot the data into 2D tabular format, or provide the
// transactional input through a nested table column.
/
40232, 00000, "transactional input - incompatible datatype for column %s"
// *Cause: The data type of the column in the input training data is
// not supported.
// *Action: Cast or change the type of the column to one of CHAR, VARCHAR,
// NUMBER or FLOAT
/
40233, 00000, "transactional input - case id should be provided with id %s"
// *Cause: The training data is transactional by virtue of presence of a
// and item id - but does not have a case id specification.
// *Action: Specify a valid case id column name as input
/
40234, 00000, "reverse expression incompatible with model cost matrix"
// *Cause: A cost matrix existed for this model with actual and predicted
// values which were inconsistent with the values resulting from
// the specified reverse transformation.
// *Action: Either remove the cost matrix table and re-add it with the
// new actual and predicted values, or respecify the reverse
// transformation to be consistent with the existing cost matrix.
/
40235, 00000, "invalid setting value for setting ASSO_AGGREGATES: %s"
// *Cause: The setting ASSO_AGGREGATES was not valid.
// *Action: Specify valid aggregates column names.
/
40236, 00000, "maximum number of aggregates exceeded"
// *Cause: The setting ASSO_AGGREGATES specified too many aggregates.
// *Action: Reduce the number of aggregates.
/
40237, 00000, "duplicate case IDs in training table"
// *Cause: The same value occurred more than once in the case ID
// column of the training table.
// *Action: Eliminate the duplicate case IDs in the training table.
/
40238, 00000, "invalid linear algebra shared library %s"
// *Cause: The shared library containing platform-optimized linear
// algebra routines was not loaded.
// *Action: Verify that the shared library is correctly installed.
/
/
/ 40251 - 40260 RESERVED FOR SVM
/
40251, 00000, "no support vectors were found"
// *Cause: The input data is non-predictive in nature, or one of the input
// settings is incorrect/incompatible with respect to the input data.
// *Action: Provide additional data or change model setting value.
/
40252, 00000, "no target values were found"
// *Cause: No target values were identified during load.
// *Action: Validate that the target is correctly specified.
/
40253, 00000, "no target counter examples were found"
// *Cause: One or more of the target classes have only positive examples.
// *Action: Provide counter examples or remove that target class.
/
40254, 00000, "priors or weights cannot be specified for one-class models"
// *Cause: Priors or weights were specified.
// *Action: Do not specify priors or weights for one-class models.
/
40255, 00000, "specified priors or weights table has an incorrect schema"
// *Cause: The priors or class weights table whose name is specified in
// in the settings does not have the prescribed schema. A priors
// table should have the schema (target_value, prior_probability)
// and a class weights table should have the schema
// (target_value, class_weight)
// *Action: Modify the schema of the input priors or class weights table
// to match the ones provided above (also in the documentation).
/
/
/ 40261 - 40270 RESERVED FOR NMF
/
40261, 00000, "input data for model build contains negative values"
// *Cause: The input data contains negative values, which is not acceptable
// for a Non-negative Matrix Factorization model.
// *Action: Provide clean data for build without any negative values.
/
40262, 00000, "NMF: number of features not between [1, %s]"
// *Cause: The number of requested features must be greater than
// 1, and less than the smaller of the number of attributes
// and the number of cases in the dataset.
// *Action: Specify the desired number of features within the acceptable
// range.
40263, 00000, "no meaningful matrix factorization found"
// *Cause: Input data was not significantly different from 0.
// *Action: Check your data for problems or add a positive constant
// to all the numeric attributes.
/
40264, 00000, "number of mining attributes (%s) exceeds maximum (%s)"
// *Cause: Input data was found to contain a number of mining attributes
// exeeding the maximum allowed.
// *Action: Check the input data for categorical fields with high cardinality.
/
/ 40271 - 40280 RESERVED FOR ABN
/
40271, 00000, "no statistically significant features were found"
// *Cause: Input data inadequate in volume and/or quality to derive
// statistically significant predictors for building a
// data mining model.
// *Action: Provide a well-prepared training data set.
/
40272, 00000, "apply rules prohibited for this model mode"
// *Cause: Adaptive Bayes Network rules are only generated for SingleFeature
// ABN models
// *Action: Rebuild model in SingleFeature mode and then apply with rules.
/
40273, 00000, "invalid model type %s for Adaptive Bayes Network algorithm"
// *Cause: The valid values for the abns_model_type settings are:
// abns_multi_feature, abns_single_feature, abns_naive_bayes.
// *Action: Use a valid value for the abns_model_type setting.
/
40274, 00000, "the Adaptive Bayes Network algorithm is desupported"
// *Cause: An attempt was made to score an Adaptive Bayes Network model.
// *Action: Drop the existing model and build a new model
// using a supported classification algorithm.
/
/
/ 40281 - 40300 RESERVED FOR DMF
/
40281, 00000, "invalid model name"
// *Cause: A model name is invalid or does not exist.
// *Action: Check spelling. A valid model name must begin with a letter and may
// contain only alphanumeric characters and the special characters $,
// _, and #. The name must be less than or equal to 30 characters and
// cannot be a reserved word.
/
40282, 00000, "invalid cost matrix"
// *Cause: Cost matrix specification is invalid.
// *Action: Provide valid cost matrix specification. Check syntax for data
// mining functions.
/
40283, 00000, "missing cost matrix"
// *Cause: Cost matrix specification is missing.
// *Action: Provide valid cost matrix specification. Check syntax for data
// mining functions.
/
40284, 00000, "model does not exist"
// *Cause: The model entered does not exist.
// *Action: Check spelling.
/
40285, 00000, "label not in the model"
// *Cause: The user-specified label was not present in the model.
// *Action: Provide a valid label. The set of valid labels can be
// retrieved from a classification model by invoking PREDICTION_SET,
// from a clustering model by invoking CLUSTER_SET,
// and from a feature extraction model by invoking FEATURE_SET.
/
40286, 00000, "remote operations not permitted on mining models"
// *Cause: An attempt was made to perform queries or DML operations on
// remote tables using local mining models.
// *Action: Remove the reference to remote tables in the statement.
/
40287, 00000, "invalid data for model - cosine distance out of bounds"
// *Cause: The norm computed using attribute values from the incoming row
// for the cosine model is outside the range 0-1.
// *Action: Remove or correct the data in the offending row.
/
40288, 00000, "event to debug and trace mining model load"
// *Document: NO
// *Cause: N/A
// *Action: Level 1 - force 4031 during shared model load
// Level 2 - trace model load info
/
40289, 00000, "duplicate attributes provided for data mining function"
// *Cause: A duplicate, non-nested attribute was provided as input to
// the data mining function. A duplicate attribute is one which
// is present in the model signature, occurs more than once
// in the USING clause after tablename expansion, and is not
// a collection element in a nested table column.
// *Action: Eliminate the duplicate attribute(s).
/
40290, 00000, "model incompatible with data mining function"
// *Cause: The supplied model cannot be operated upon by the data mining
// function because the model is built for a mining function and/
// or based on an algorithm that is incompatible with function.
// *Action: Provide the name of the model suitable for the function.
/
40291, 00000, "model cost not available"
// *Cause: The supplied model was assumed to have been built with
// a cost matrix specification, when in reality, it was not.
// *Action: Provide a model name that corresponds to a model that was
// built with an appropriate cost matrix specification.
/
40292, 00000, "confidence level must be greater than 0 and less than 1"
// *Cause: The specified value for confidence level is out of range.
// *Action: Specify a value for confidence level in the range 0 < level < 1
/
40293, 00000, "input class is invalid for the specified predictive model"
// *Cause: The specified model is either not a classification model, or
// does not have the input class label as one of its target values.
// *Action: Provide the correct target value (class label) or provide the
// appropriate classification model with the target attribute that
// has the specified class label as one of its values.
/
/
/ 40301 - 40320 RESERVED FOR DECISION TREE CLASSIFICATION AND REGRESSION
/
40301, 00000, "invalid cost matrix specification"
// *Cause: A valid cost matrix is not specified.
// *Action: Consult documentation for valid cost matrix specification.
/
40302, 00000, "invalid classname %s in cost matrix specification"
// *Cause: Actual or predicted classname specified is not present in training
// data
// *Action: Provide valid classname(s) in cost matrix specification
/
40303, 00000, "invalid prior probability specification"
// *Cause: Valid prior probabilities not specified.
// Valid probabilities should be between 0 and 1.
// *Action: Consult documentation for valid prior probability specification.
/
40304, 00000, "invalid classname %s in prior probability specification"
// *Cause: Actual or predicted classname specified is not present in training
// data.
// *Action: Provide valid classname(s) in prior probability specification.
/
40305, 00000, "invalid impurity metric specified"
// *Cause: Impurity metric specified is not valid. Examples of valid metrics
// are TREE_IMPURITY_GINI, TREE_IMPURITY_ENTROPY.
// *Action: Consult documentation for valid impurity metrics and specification.
/
40306, 00000, "dm_nested types not supported by this algorithm"
// *Cause: The training input to the CREATE_MODEL routine
// contained one or more columns of DM_NESTED type
// (DM_NESTED_NUMERICALS or DM_NESTED_CATEGORICALS).
// These columns are currently not supported by Orthogonal
// Partitioning Clustering (O-Cluster).
// *Action: Remove columns of these data types from the input data source.
40307, 00000, "nested attribute combined name and value too long"
// *Cause: The data that was presented to the decision tree
// algorithm was too long. The length is computed from
// the sum of the length of the nested attribute name
// and the length of the attribute value.
// *Action: Reduce the length of the attribute name or reduce the
// length of the categorical value (perhaps by recoding).
/
40308, 00000, "RFOR_MTRY is greater than attribute count or negative or 0"
// *Cause: The setting for RFOR_MTRY was either 0 or >= number of
// attributes. The default behavior in this scenario is to use all of
// the attributes for the model build.
// *Action: Consider a different value for RFOR_MTRY.
/
40309, 00000, "The Random Forest sample size exceeds available memory."
// *Cause: The sample did not fit into available memory.
// *Action: No action needed. The sample size was adjusted automatically to
// fit into memory.
/
/
/
/ 40321 - 40340 RESERVED FOR CLUSTERING MODELS
/
40321, 00000, "invalid bin number, is zero or negative value"
// *Cause: Input bin number has zero or negative values.
// *Action: Provide positive bin numbers starting from 1.
/
40322, 00000, "bin number too large"
// *Cause: Bin number is too large.
// *Action: Reprocess build data by choosing smaller bin numbers.
//
40323, 00000, "Attribute %s has too many distinct values (%s)"
// *Cause: Exceeded maximum number of distinct values allowed in an attribute.
// *Action: Bin numerical data with fewer than 1024 bins or recode categorical
// data with fewer than 1024 unique values.
//
/
40324, 00000, "All rows contain the same data"
// *Cause: All rows contained the same data and could not be clustered
// using k-Means with cosine distance metric.
// *Action: Use Euclidean distance metric.
//
40325, 00000, "maximum number of clusters exceeded"
// *Cause: The maximum number of clusters was exceeded.
// *Action: Reduce the number of clusters.
/
40326, 00000, "no mining attributes after filtering"
// *Cause: All mining attributes were filtered out.
// *Action: Disable attribute filtering.
/
/
/ 40341 - 40360 RESERVED FOR MODEL MAINTENANCE UPGRADE/DOWNGRADE MESSAGES
/
40341, 00000, "access violation on model storage object"
// *Cause: An attempt was made to directly access/modify a schema object
// that stores model metadata and content.
// *Action: Perform all mining operations (create,drop,alter, and select
// using data mining functions) against named model objects.
// Contact your DBA or Oracle Support if you suspect that an
// orphaned schema object.
/
40342, 00000, "model was not correctly upgraded"
// *Cause: An attempt was made to use a model, but the model was not
// correctly upgraded to the current release. This is most
// likely caused by importing a model from an old release
// without upgrading it, but could also be caused by a
// failed database upgrade.
// *Action: Invoke the SYS.DMP_SYS.UPGRADE_MODELS() procedure.
/
40343, 00000, "invalid version specified in UPGRADE_MODELS"
// *Cause: An invalid version was specified when invoking the
// UPGRADE_MODELS procedure. Valid values for the version
// are 10.2.0, 11.0.0, 12.0.0, and NULL.
// *Action: Specify a valid version for UPGRADE_MODELS.
/
40350, 00000, "One or more models exist that cannot be downgraded"
// *Cause: There are data mining models in the database
// that were created in a release beyond the selected
// release for downgrade.
// *Action: Prior to downgrade, drop data mining models that cannot
// be downgraded to the selected release.
/
/
/ 40361 - 40380 RESERVED FOR SECURITY (PRIVILEGE/AUDIT) MESSAGES
/
40361, 00000, "only SELECT and ALTER are valid for mining models"
// *Cause: An attempt was made to grant or revoke an invalid privilege
// on a mining model.
// *Action: Do not attempt to grant or revoke any privilege besides SELECT
// or ALTER on mining models.
/
40362, 00000, "invalid object %s.%s specified in the statement"
// *Cause: An attempt was made to grant a privilege on an invalid object.
// *Action: Ensure that the dependents of the object are valid before
// attempting to grant the privilege on the object.
/
/
40363, 00000, "GRANT failed: user SYS always has SYSOPER and SYSDBA"
// *Cause: An attempt was made to grant SYSOPER or SYSDBA privileges to SYS
// user. These administrative privileges cannot be granted to SYS,
// since SYS always has SYSOPER and SYSDBA privileges.
// *Action: Try granting administrative privilege to users other than SYS.
/
40364, 00000, "Use of BECOME USER functionality is restricted."
// *Cause: This is an internal error message.
// *Action: Contact Oracle Support Services.
/
40365, 00000, "The SYS user cannot be locked while the password file is in its current format."
// *Cause: An attempt was made to lock the SYS user account by executing the
// DDL statement ALTER USER SYS ACCOUNT LOCK while the password file
// was created in LEGACY or 12 format.
// *Action: The password file must be created in the 12.2 format to provide
// support for maintaining the ACCOUNT_STATUS of all administrative
// users including SYS.
/
40366, 00000, "Administrative privilege cannot be granted to this user."
// *Cause: An attempt was made to grant administrative privilege to a user
// who has been created with NONE as its authentication type.
// Such grants are not allowed.
// *Action: Do not grant administrative privilege to user with
// NONE as its AUTHENTICATION_TYPE in DBA_USERS view.
/
40367, 00000, "An Administrative user cannot be altered to have no authentication type."
// *Cause: An attempt was made to alter an administrative user to have no
// authentication type.
// *Action: Revoke administrative privilege from the user
// before attempting to alter the user.
/
/ 40381 - 40500 RESERVED FOR PMML IMPORT
/
40381, 00000, "Invalid field specification for: %s"
// *Cause: The derived field was incorrectly defined.
// *Action: Ensure that the field is correctly defined in the PMML document.
/
40382, 00000, "More than one linear regression equation in the model"
// *Cause: More than one linear regression equation was in the model.
// *Action: Ensure that there is only one linear regression equation in the
// model.
/
40383, 00000, "No model found in PMML document"
// *Cause: There was no model found in the PMML document.
// *Action: Ensure that the PMML document contains a model section.
/
40384, 00000, "Only one model allowed in PMML document"
// *Cause: More than one model existed in the PMML document.
// *Action: PMML model import only supports one model per PMML document.
// Ensure that only one model exists in the PMML document.
/
40385, 00000, "Target has more than two categories"
// *Cause: The target contained more than two categories.
// *Action: PMML model import supports only binary logistic regression.
// Ensure that the target contains no more than two categories.
/
40386, 00000, "NormContinuous must include at least two LinearNorm elements"
// *Cause: NormContinuous included less than two LinearNorm elements.
// *Action: NormContinuous must include at least two LinearNorm elements.
// Ensure that at least two LinearNorm elements are included.
/
40387, 00000, "Invalid interval for Discretize field: %s"
// *Cause: The intervals were incorrect.
// *Action: Ensure that that both margins are not missing.
/
40388, 00000, "Unsupported feature in PMML document: %s"
// *Cause: The feature was not supported by Predictive Model Markup Language
// (PMML) model import.
// *Action: Ensure that you use the supported features.
/
40389, 00000, "Unsupported PMML transformation: %s"
// *Cause: The transformation was not supported.
// *Action: Ensure that you use the supported transformations.
/
40390, 00000, "PMML DerivedField must have a unique name specified: %s"
// *Cause: "The Predictive Model Markup Language (PMML) DerivedField did not
// reference another defined field and did not have a unique name."
// *Action: "Specify a unique name for each DerivedField."
/
40391, 00000, "PMML DerivedField depends on a undefined field: %s"
// *Cause: A DerivedField referenced an undefined field.
// *Action: Ensure that the DerivedField references other defined fields.
/
40392, 00000, "PMML regression equation references an undefined field: %s"
// *Cause: The Predictive Model Markup Language (PMML) Regression equation did
// not reference defined fields. PMML Regression equation may only
// reference defined fields.
// *Action: Ensure that all fields are defined.
/
/
/
/ 40401 - 40420 RESERVED FOR SVD
/
40401, 00000, "categorical attributes are not supported by this algorithm"
// *Cause: The build data provided to the CREATE_MODEL routine contained
// one or more categorical attributes of types CHAR, VARCHAR2, or
// DM_NESTED_CATEGORICAL. These attributes are currently not supported
// for the SVD algorithm.
// *Action: Remove the categorical attributes from the build data.
/
40402, 00000, "cannot output U matrix without a valid case identifier column"
// *Cause: A U matrix was requested, but there was no case identifier
// column in the build data.
// *Action: Provide a non-null case identifier column in the build data.
/
40403, 00000, "model does not have any valid features"
// *Cause: All singular values in the SVD model were equal to zero.
// This can occur if the build data contains only zeros or
// all build columns have constant values and automatic data
// preparation is turned on.
// *Action: Inspect and modify the build data.
/
40404, 00000, "approximate computation cannot be disabled for the build data"
// *Cause: The build data had a very high number of attributes. An SVD model
// can be built only by enabling approximate computation.
// *Action: Enable approximate computation.
/
40405, 00000, "Full SVD solvers cannot be used for the build data."
// *Cause: The build data had a very high number of attributes. A Singular
// Value Decomposition (SVD) model cannot be built using full
// SVD solvers.
// *Action: Select a truncated SVD solver.
/
/
/ 40421 - 40440 RESERVED FOR UNSTRUCTURED TEXT
/
40421, 00000, "missing text policy name"
// *Cause: Text policy name was missing.
// *Action: Provide a valid text policy name created using
// CTX_DDL.CREATE_POLICY().
/
40422, 00000, "TEXT attribute types not supported by this algorithm"
// *Cause: The training input to the CREATE_MODEL routine
// contained one or more attributes of TEXT type.
// These attributes are currently not supported by Orthogonal
// Partitioning Clustering (O-Cluster).
// *Action: Remove attributes of these types from the input data source.
/
40423, 00000, "Extraction of tokens from text failed"
// *Cause: Extraction of tokens from an attribute of TEXT type failed.
// *Action: Check text policy, policy owner, other settings for TEXT type,
// and computer resources.
/
/ 40441 - 40500 RESERVED FOR JSON
/
40441, 00000, "JSON syntax error"
// *Cause: The provided JavaScript Object Notation (JSON) data had invalid
// syntax and could not be parsed.
// *Action: Provide JSON data with the correct syntax.
/
40442, 00000, "JSON path expression syntax error ('%s')%s"
// *Cause: The provided JavaScript Object Notation (JSON) path expression
// had an invalid syntax and could not be parsed.
// *Action: Provide JSON path expression with the correct syntax.
/
40443, 00000, "unsupported JSON path expression"
// *Cause: The provided JavaScript Object Notation (JSON) path expression
// contained unsupported features.
// *Action: Remove unsupported features from JSON path expression.
/
40444, 00000, "JSON processing error"
// *Cause: The requested JavaScript Object Notation (JSON) operation failed.
// *Action: Ensure that the JSON operation is invoked correctly.
/
40445, 00000, "unsupported JSON operation"
// *Cause: The requested JavaScript Object Notation (JSON) operation is not
// supported.
// *Action: None.
/
40446, 00000, "expecting keyword STREAM"
// *Cause: The JavaScript Object Notation (JSON) operator expected the
// keyword STREAM.
// *Action: Add the keyword STREAM to the JSON operator.
/
40447, 00000, "expecting PASSING clause"
// *Cause: The JavaScript Object Notation (JSON) operator expected a PASSING
// clause.
// *Action: Add a PASSING caluse to the JSON operator.
/
40448, 00000, "expecting RETURNING clause"
// *Cause: The JavaScript Object Notation (JSON) operator expected a
// RETURNING clause.
// *Action: Add a RETURNING clause to the JSON operator.
/
40449, 00000, "invalid data type for return value"
// *Cause: The provided data type for the return value was invalid or
// unsupported.
// *Action: Provide a supported return value.
/
40450, 00000, "invalid ON ERROR clause"
// *Cause: The provided ON ERROR clause was invalid.
// *Action: Provide a valid ON ERROR clause.
/
40451, 00000, "invalid default value provided"
// *Cause: The provided default value was not allowed here.
// *Action: Provide a valid default value.
/
40452, 00000, "default value not matching type defined in RETURNING clause"
// *Cause: The provided default value did not match the type defined in
// the RETURNING clause.
// *Action: Ensure that the default value and RETURNING clause are of the
// same type.
/
40453, 00000, "JSON operator syntax error"
// *Cause: The provided JavaScript Object Notation (JSON) operator had invalid
// syntax.
// *Action: Provide JSON operator with correct syntax.
/
40454, 00000, "path expression not a literal"
// *Cause: The provided path expression was not a literal (a constant).
// *Action: Provide a constant path expression.
/
40455, 00000, "default value not a literal"
// *Cause: The provided default value was not a literal (a constant).
// *Action: Provide a constant default value.
/
40456, 00000, "JSON_VALUE evaluated to non-scalar value"
// *Cause: The provided JavaScript Object Notation (JSON) path expression
// selected a non-scalar value.
// *Action: Correct the JSON path expression or use JSON_QUERY.
/
40457, 00000, "JSON path expression contained an invalid array index ('%s')%s"
// *Cause: The provided JavaScript Object Notation (JSON) path expression
// contained an invalid array index.
// *Action: Provide a valid array index. The first element in the array has the
// index 0.
/
40458, 00000, "JSON_EXISTS used outside predicate"
// *Cause: The operator JSON_EXISTS was used outside of a predicate.
// *Action: Use JSON_EXISTS inside a predicate, for instance by embedding it
// inside a CASE expression.
/
40459, 00000, "output value too large (actual: %s, maximum: %s)"
// *Cause: The provided JavaScript Object Notation (JSON) operator generated a
// result which exceeds the maximum length specified in the RETURN
// clause.
// *Action: Increase the maximum size of the data type in the RETURNING clause
// or use a CLOB/BLOB in the RETURNING clause.
/
40460, 00000, "default value too large"
// *Cause: The provided default value exceed the maximum length specified
// in the RETURN clause.
// *Action: Increase the maximum size of the data type in the RETURNING clause
// or reduce the length of the default value.
/
40461, 00000, "Unsupported character set"
// *Cause: The provided JavaScript Object Notation (JSON) operator does not
// supported the current database character set.
// *Action: Chose a different database character set, for instance AL32UTF8,
// AL16UTF16, or a single byte character set.
/
40462, 00000, "JSON_VALUE evaluated to no value"
// *Cause: The provided JavaScript Object Notation (JSON) path expression
// did not select a value.
// *Action: Correct the JSON path expression.
/
40463, 00000, "JSON path expression contained an invalid variable name"
// *Cause: The provided JavaScript Object Notation (JSON) path expression
// contained a variable name that was not used in the PASSING clause.
// *Action: Ensure that the variable names in the path expression and
// PASSING clause match.
/
40464, 00000, "JSON PASSING clause contained duplicate variable names"
// *Cause: The provided JavaScript Object Notation (JSON) PASSING clause
// contained non-unique variable names.
// *Action: Rename the variables in the PASSING clause.
/
40465, 00000, "JSON PASSING clause contained too many unnamed parameters"
// *Cause: The provided JavaScript Object Notation (JSON) PASSING clause
// contained too many unnamed parameters.
// *Action: Assign names to the parameters provided in the PASSING clause.
/
40466, 00000, "Invalid parameter in IS [NOT] JSON predicate"
// *Cause: The IS [NOT] JSON predicate containes an invalid parameter.
// *Action: Remove or correct the parameter.
/
40467, 00000, "JSON_TEXTCONTAINS() cannot be evaluated without a JSON-enabled context index"
// *Cause: There was no JavaScript Object Notation (JSON)-enabled context
// index available.
// *Action: Create a JSON-enabled context index.
/
40468, 00000, "first input parameter to JSON_TEXTCONTAINS() must be a column"
// *Cause: The first input parameter to JSON_TEXTCONTAINS() was not a column.
// *Action: Pass a column to the first input parameter to JSON_TEXTCONTAINS().
/
40469, 00000, "JSON path expression in JSON_TEXTCONTAINS() is invalid"
// *Cause: A predicate or array position was used in JavaScript Object
// Notation (JSON) path expression, or the length of a JSON field name in
// the path expression exceeded the JSON search index token length limit.
// *Action: Neither use a predicate or array position in a JSON path expression
// nor a step with length longer than the JSON search index token
// length limit.
/
40470, 00000, "JSON_VALUE evaluated to multiple values"
// *Cause: The provided JavaScript Object Notation (JSON) path expression
// selected more than one value.
// *Action: Correct the JSON path expression or use JSON_QUERY.
/
40471, 00000, "selected value not JSON array or object"
// *Cause: The selected value was not a JavaScript Object Notation (JSON)
// value.
// (object or array)
// *Action: Use CAST AS ARRAY to return this value.
/
40472, 00000, "invalid escape in JSON data"
// *Cause: The provided JavaScript Object Notation (JSON) data had an invalid
// escape sequence.
// *Action: Provide JSON data with corrected escape sequence.
/
40473, 00000, "duplicate key names in JSON object"
// *Cause: The provided JavaScript Object Notation (JSON) data had duplicate
// key names in one object.
// *Action: Provide JSON data with unique key names in each JSON object.
/
40474, 00000, "invalid UTF-8 byte sequence in JSON data"
// *Cause: The provided JavaScript Object Notation (JSON) data had an invalid
// UTF-8 byte sequence.
// *Action: Provide JSON data with corrected UTF-8 byte sequence or escape
// the characters.
/
40475, 00000, "JSON data nested too many levels"
// *Cause: The provided JavaScript Object Notation (JSON) data had too many
// levels of nesting.
// *Action: Provide JSON data with fewer levels of nesting.
/
40476, 00000, "JSON key too long"
// *Cause: The provided JavaScript Object Notation (JSON) data had a key which
// exceeds the maximum length.
// *Action: Provide JSON data with shorter key names.
/
40477, 00000, "internal JSON error"
// *Cause: There was an internal error in the JavaScript Object Notation
// (JSON) processing layer.
// *Action: None.
/
40478, 00000, "output value too large (maximum: %s)"
// *Cause: The provided JavaScript Object Notation (JSON) operator generated a
// result which exceeds the maximum length specified in the RETURN
// clause.
// *Action: Increase the maximum size of the data type in the RETURNING clause
// or use a CLOB or BLOB in the RETURNING clause.
/
40479, 00000, "internal JSON serializer error"
// *Cause: There was an internal error in the JavaScript Object
// Notation (JSON) serializer).
// *Action: None.
/
40480, 00000, "result cannot be returned without array wrapper"
// *Cause: The JavaScript Object Notation (JSON) path expressions selected
// a value that can only be returned inside an array.
// *Action: Add WITH ARRAY WRAPPER to the JSON function.
/
40481, 00000, "ASCII or PRETTY not supported for non-textual return data type"
// *Cause: An attempt was made to pretty print or escape non-ASCII
// characters for a non-textual output of a JavaScript Object Notation
// (JSON) operation.
// *Action: Change return data type to VARCHAR2 or CLOB or remove the PRETTY
// or ASCII serialization option.
/
40482, 00000, "JSON_TEXTCONTAINS() used outside predicate of WHERE clause"
// *Cause: JSON_TEXTCONTAINS() was used outside of the predicate of a WHERE
// clause.
// *Action: Use JSON_TEXTCONTAINS() inside a preciate of a WHERE clause.
/
40483, 00000, "incorrect search string to JSON_TEXTCONTAINS()"
// *Cause: An incorrect search string to JSON_TEXTCONTAINS() was used.
// *Action: The search string to JSON_TEXTCONTAINS() needs to be a non-zero
// length compile time constant.
40484, 00000, "invalid data type for JSON_TABLE column"
// *Cause: A column in the provided JSON_TABLE had an unsupported data type.
// *Action: Provide a supported data type.
/
40485, 00000, "keyword PRETTY not valid for this column"
// *Cause: A JSON_TABLE column with JSON_VALUE semantics could not be pretty
// printed.
// *Action: Change column semantics to JSON_QUERY or remove the keyword PRETTY.
/
40486, 00000, "array wrapper not valid for this column"
// *Cause: A JSON_TABLE column with JSON_VALUE semantics could not have an
// array wrapper.
// *Action: Change column semantics to JSON_QUERY or remove the array wrapper.
/
40487, 00000, "invalid usage of keyword EXISTS"
// *Cause: A JSON_TABLE column with JSON_EXISTS semantics had invalid
// parameters.
// *Action: Remove the invalid keywords.
/
40488, 00000, "invalid ON ERROR clause for column semantics"
// *Cause: An ON ERROR clause was provided that was not valid for the selected
// column semantics.
// *Action: Change or remove the ON ERROR clause or change the column
// semantics.
/
40489, 00000, "keyword ASCII not valid for this column"
// *Cause: A JSON_TABLE column with JSON_VALUE semantics could not be pretty
// printed.
// *Action: Change column semantics to JSON_QUERY or remove keyword ASCII.
/
40490, 00000, "COLUMNS clause required"
// *Cause: The provided JSON_TABLE row source requires a COLUMNS clause.
// *Action: Provide a COLUMNS clause.
/
40491, 00000, "invalid input data type for JSON_TABLE"
// *Cause: The provided input to JSON_TABLE has an unsupported data type.
// *Action: Provide a (N)VARCHAR2, (N)CLOB, RAW, BLOB or BFILE input.
/
40492, 00000, "invalid column definition in JSON_TABLE"
// *Cause: A column definition inside JSON_TABLE was invalid.
// *Action: Correct the column definition.
/
40493, 00000, "invalid option or parameter in JSON_TABLE"
// *Cause: The provided JSON_TABLE definition contained one or more
// invalid options or parameters.
// *Action: Correct the JSON_TABLE definition.
/
40494, 00000, "error during execution of JSON_TABLE"
// *Cause: The provided JSON_TABLE definition could not be evaluated.
// *Action: Correct the JSON_TABLE definition.
/
40495, 00000, "internal error in JSON_TABLE"
// *Cause: The provided JSON_TABLE definition could not be evaluated.
// *Action: Contact Oracle Support Services.
/
40496, 00000, "too many keys for JSON_OBJECTAGG"
// *Cause: The number of rows in a JSON_OBJECTAGG aggregation group
// exceeded the maximum number of keys for a JSON Object.
// *Action: Reduce the number of rows in each group, or remove
// the WITH UNIQUE KEYS check.
/
40497, 00000, "only one ordinality column permitted"
// *Cause: The provided JSON_TABLE definition contained more than one
// ordinality column.
// *Action: Remove the ordinality column or columns from the JSON_TABLE
// definition.
/
40498, 00000, "binary format requested for non-binary data type"
// *Cause: The provided JSON format was binary but the input data type
// was not binary.
// *Action: Either change the format clause or use an input of binary
// data type.
/
40499, 00000, "no format defined for binary data type"
// *Cause: The provided JavaScript Object Notation (JSON) input was of
// binary type but a format was not defined.
// *Action: Define a format for binary input.
/
40500, 00000, "General event for JSON operations"
// *Document: NO
// *Cause: General event for JSON operations
// *Action: N/A, this is an Oracle internal event code.
/
/ 40501 - 40550 Reserved for Recovery
/
40501, 00000, "cannot open an encrypted log file"
// *Cause: An attempt was made to open a log file that has been encrypted
// for storage and management by the Oracle Availability Machine.
// Only the processes involved in shipping such a log to or
// from the Oracle Availability Machine can open the log.
// *Action: Allow the Oracle Availability Machine to manage the log file.
/
/ It appears, 40502 and 40503 are being used by spcmgmt for testing purposes
/
40504, 00000, "file %s created before last CREATE CONTROLFILE, could not proceed with recovery"
// *Cause: An attempt at media recovery found that the data file already
// existed before the last CREATE CONTROLFILE statement was executed.
// The information needed for doing the media recovery was lost with
// the control file that existed when the data file was added to the
// database.
// *Action: Restore a more recent backup of the data file and retry the
// recovery.
/
40505, 00000, "tablespace #%s has been dropped"
// *Cause: An attempt was made on the physical standby database to access the
// tablespace that was being dropped by Redo Apply. Note that the
// target tablespace was dropped on the primary database and the
// physical standby database was applying the redo that was generated
// at the primary database for the target tablespace drop.
// *Action: None.
/
40506, 00000, "event to help in testing of Auto BMR to fix file header corruption"
// *Document: NO
// *Cause: Simulate an error in a file header in order to test automatic block
// media recovery support for file header fix.
// *Action: Level is bitmap of file numbers.
/
40507, 00000, "The file header of data file %s is corrupt. Automatic block repair is trying to fix the file header."
// *Cause: A corrupt data file header was encountered during a checkpoint.
// *Action: Run the query after the data file header is fixed by the automatic
// block repair.
/
40508, 00000, "Abstract data type created on primary database. Need to wait for it to be replicated at standby database."
// *Document: NO
// *Cause: Simulate an error to cause cursor recompilation at standby database.
// *Action: No user action needed. This error is used internally during
// remote abstract data type creation
/
40509, 00000, "cursor compilation failed because %s"
// *Cause: Cursor compilation failed. Check the alert log for
// more details.
// *Action: Run the query again after fixing the condition that failed
// cursor compilation.
/
40510, 00000, "This type of file cannot be renamed."
// *Cause: An attempt was made to rename a file for which renaming is not
// supported.
// *Action: Do not attempt to rename files of this type.
/
/
/ 40551 - 40700 Reserved for JSON
/
40551, 00000, "internal BSON/JSON conversion error [%s]"
// *Cause: BSON/JSON conversion failed with internal error.
// *Action: Contact Oracle Support Services.
/
40552, 00000, "invalid data type"
// *Cause: The BSON/JSON converter was invoked with an invalid data type.
// *Action: Ensure that both the input and output is of data type BLOB.
/
40553, 00000, "path expression with predicates not supported in this operation"
// *Cause: A path expression with predicates was specified in a JavaScript
// Object Notation (JSON) operation that does not support predicates.
// *Action: Only JSON_EXISTS supports predicates.
/
40554, 00000, "invalid input data type in PASSING clause"
// *Cause: The specified PASSING clause had an unsupported data type.
// *Action: Use a supported data type in the PASSING clause.
/
40555, 00000, "incorrect PASSING clause"
// *Cause: The specified PASSING clause was invalid.
// *Action: Specify a valid passing clause.
/
40556, 00000, "unsupported chaining of JSON_TABLE"
// *Cause: The specified JSON_TABLES were chained.
// *Action: Use the NESTED PATH syntax for JSON_TABLE.
/
40557, 00000, "cannot update a JSON value"
// *Cause: An attempt was made to update a JavaScript Object Notation (JSON)
// value.
// *Action: Update the entire JSON object instead.
/
40558, 00000, "package functions are unsupported below compatible 12.0.0.0.0"
// *Cause: DBMS_SODA_ADMIN was used when the database was operating
// at a compatible setting lower than 12.0.0.0.0.
// *Action: Upgrade the database compatible setting to 12.0.0.0.0 or higher
// to enable the desired new features.
/
40559, 00000, "one or more JSON objects exist that cannot be downgraded."
// *Cause: There were JavaScript Object Notation (JSON) objects in the
// database that were created in a release beyond the selected
// release for downgrade.
// *Action: Prior to downgrade, drop the JSON objects that cannot
// be downgraded to the selected release.
40560, 00000, "JSON_TABLE nested path expressions not disjunct"
// *Cause: The JSON_TABLE expression contained two or more nested path
// expressions that (partially or fully) selected the same fields.
// *Action: Correct or combine the nested path expressions so that they
// become disjunct.
40561, 00000, "invalid path in JSON_TABLE nested path clause"
// *Cause: The JSON_TABLE expression contained a nested path clause with an
// invalid path expression.
// *Action: Correct or remove the nested path expression.
40562, 00000, "Conversion from GeoJSON to SDO_GEOMETRY failed."
// *Cause: The selected value could not be converted to a SDO_GEOMETRY object.
// *Action: Ensure that the path expression selects one valid GeoJSON value.
40563, 00000, "default value not allowed for object types."
// *Cause: The error handler specified a default value and the returned data
// type was an object type. These cannot be combined.
// *Action: Change either the return type or choose 'NULL ON ERROR' or
// 'ERROR ON ERROR' as error handler.
40564, 00000, "Invalid JSON specification."
// *Cause: The provided specification was invalid.
// *Action: Correct the specification parameter.
40565, 00000, "JSON path expression did not select a value."
// *Cause: The JavaScript Object Notation (JSON) path expression did not
// select a value.
// *Action: Correct the JSON path expression.
40566, 00000, "JSON path expression selected a value of different data type."
// *Cause: The JavaScript Object Notation (JSON) path expression selected a
// data type value different
// than the requested data type.
// *Action: Use another 'get-method' to retrieve the value selected by the JSON
// path expression.
40567, 00000, "JSON patch operation failed."
// *Cause: The JavaScript Object Notation (JSON) patch operation failed.
// *Action: Correct the specification parameter.
40568, 00000, "Cannot modify read-only target."
// *Cause: An attempt to modify a JavaScript Object Notation (JSON) structure
// failed because the structure cannot be modified.
// *Action: None.
40569, 00000, "Unimplemented JSON feature."
// *Cause: An attempt was made to execute an unimplemented JavaScript Object
// Notation (JSON) feature.
// *Action: None.
40570, 00000, "JSON conversion failed."
// *Cause: A conversion between a JavaScript Object Notation (JSON) value and
// another type failed.
// *Action: Check the type definition or the selected JSON value.
40571, 00000, "JSON key name not found."
// *Cause: A key with the specified name was not found in the JavaScript
// Object Notation (JSON) data.
// *Action: Correct the key name.
40572, 00000, "Invalid JSON array position."
// *Cause: An attempt was made to access an item inside a JavaScript Object
// Notation (JSON) array with a position that is either out of bounds
// or invalid.
// *Action: Correct the position value.
40573, 00000, "Invalid use of PL/SQL JSON object type."
// *Cause: An attempt was made to use a PL/SQL JavaScript Object Notation
// (JSON) object type in an invalid context.
// *Action: Use PL/SQL JSON object types only inside PL/SQL.
40574, 00000, "JSON operation on redacted column %s not allowed."
// *Cause: An attempt was made to use a JavaScript Object Notation (JSON)
// operation on a column which has a redaction policy.
// *Action: Drop the redaction policy. Re-create redaction policy on a new view
// over the column if needed.
/
40576, 00000, "Invalid use of bind variable in SQL/JSON path."
// *Cause: An attempt was made to bind a non-runtime constant to
// a bind variable in SQL/JSON path.
// *Action: Bind either compile time constant or runtime SQL bind variable
// value to a bind variable for SQL/JSON path.
/
40577, 00000, "invalid key name"
// *Cause: The provided key name was not valid.
// *Action: Provide a valid key name.
/
40578, 00000, "invalid or non-existent array position"
// *Cause: The provided array position was not valid or non-existant.
// *Action: Provide a valid array position or use the 'append' function to add
// new items to the array.
/
/ 40581-40619 JSON data guide related
/
40581, 00000, "package functions are unsupported below compatible %s"
// *Cause: The package was used with a database that was operating at
// a compatible setting lower than expected.
// *Action: Upgrade the database to a compatible setting that is the
// expected release or higher to enable the desired new features.
/
40582, 00000, "cannot find a data guide-enabled context index"
// *Cause: A data guide-enabled context index for the specified column
// in the specified table was not found.
// *Action: Ensure that the table and column exist, the column is a JavaScript
// Object Notation (JSON) column, and a data guide-enabled context
// index exists on the JSON column before invoking the procedure or
// function.
/
40583, 00000, "view name or table name or JSON column name cannot be null"
// *Cause: The view name or table name or JSON column name was null.
// *Action: Pass in a valid view name or table name or JavaScript Object
// Notation (JSON) column name to the function or procedure.
/
40584, 00000, "JSON column %s does not exist"
// *Cause: The given table did not have a JavaScript Object Notation (JSON)
// column with the given name.
// *Action: Ensure that the table name and JSON column name are specified
// correctly.
/
40585, 00000, "invalid frequency"
// *Cause: The specified frequency was invalid.
// *Action: The range of frequency has to be 0 to 100.
/
40586, 00000, "error occurred in the execution of %s"
// *Cause: A internal error occurred.
// *Action: This is an internal error. Contact Oracle Support Services.
/
40587, 00000, "invalid JSON type"
// *Cause: The specified JavaScript Object Notation (JSON) type was invalid.
// *Action: Ensure that the JSON type is specified correctly.
/
40588, 00000, "invalid estimate percentage"
// *Cause: The specified estimate percentage was invalid.
// *Action: The range of estimate percentage has to be 0.000001 to 100.
/
40589, 00000, "path %s does not exist"
// *Cause: The specified path was not found.
// *Action: Ensure that the specified path exists.
/
40590, 00000, "invalid format"
// *Cause: The specified format was invalid.
// *Action: Ensure that the format is specified correctly.
/
40591, 00000, "empty data guide on json column"
// *Cause: No data has been inserted to the json column.
// *Action: Insert data or commit.
/
40592, 00000, "name conflicts were found during execution of DBMS_JSON.ADDVC: %s"
// *Cause: An attempt was made to create virtual columns using an annotated
// Javascript Object Notation (JSON) data guide with the name of a
// column that already exists.
// *Action: Change the preferred name of the virtual column in the annotated
// Javascript Object Notation (JSON) data guide.
/
40593, 00000, "name conflicts were found during execution of DBMS_JSON.CREATEVIEW: %s"
// *Cause: An attempt was made to create a view using an annotated Javascript
// Object Notation (JSON) data guide with the name of a column
// that already exists.
// *Action: Change the preferred name of the column in the annotated Javascript
// Object Notation (JSON) data guide.
/
40594, 00000, "invalid data guide"
// *Cause: The specified data guide was invalid.
// *Action: Ensure that the specified data guide follows data guide rules.
/
40595, 00000, "Name input to JSON generation function cannot be null."
// *Cause: The name input given to the Javascript Object Notation (JSON)
// generation function was null.
// *Action: Ensure that the input has a valid value.
/
40596, 00000, "error occurred in JSON processing %s"
// *Cause: An error occurred when evaluating the JavaScript Object
// Notation (JSON) operator.
// *Action: None.
/
40597, 00000, "JSON path expression syntax error ('%s')%s\nat position %s"
// *Cause: The specified JavaScript Object Notation (JSON) path expression
// had invalid syntax and could not be parsed.
// *Action: Specify JSON path expression with the correct syntax.
/
40598, 00000, "JSON path expression contained an invalid array index ('%s')%s\nat position %s"
// *Cause: The specified JavaScript Object Notation (JSON) path expression
// contained an invalid array index.
// *Action: Specify a valid array index. The first element in the array has
// the index 0.
/
40599, 00000, "IS JSON check constraint cannot be dropped."
// *Cause: IS JSON check constraint could not be dropped when there was a JSON
// search index created on the column.
// *Action: Drop the JSON search index first before dropping the
// IS JSON check constraint.
/
40600, 00000, "JSON_EQUAL used outside predicate"
// *Cause: The operator JSON_EQUAL was used outside of a predicate.
// *Action: Use JSON_EQUAL inside a predicate, for instance by embedding it
// inside a CASE expression.
/
/ 40601-40700 JSON related , there 19 error messages available here
/
40620, 00000, "total length of key names in JSON object too long"
// *Cause: The length of all the key names combined exceeded the maximum
// length permitted for a JavaScript Object Notation (JSON) object.
// *Action: Use fewer keys or shorter key names.
/
40621, 00000, "Collection create mode %s is not supported."
// *Cause: An invalid collection create mode was specified.
// *Action: Use a valid collection create mode.
/
40622, 00000, "Creating a collection backed by view or package in ''NEW'' mode is not allowed."
// *Cause: Creating a collection backed by view or package in NEW mode
// was not allowed.
// *Action: Do not specify a view or package when creating the collection in
// NEW create mode, or specify a create mode that supports view or
// package-based collections.
/
40623, 00000, "The table intended to back the collection does not exist."
// *Cause: The table intended to back the collection did not exist.
// *Action: Ensure that the table intended to back the collection exists.
/
40624, 00000, "Columns of the mapped table backing the collection do not match collection metadata."
// *Cause: The columns of mapped table backing the collection did not match
// the collection metadata.
// *Action: Ensure that the columns of the table backing the collection match
// their description in collection metadata.
/
40625, 00000, "The view intended to back the collection does not exist."
// *Cause: The view intended to back the collection did not exist.
// *Action: Ensure that the view intended to back the collection exists.
/
40626, 00000, "The table or view underlying the collection cannot be dropped."
// *Cause: The table or the view underlying the collection could not be
// dropped.
// There could be uncommitted writes to the collection.
// *Action: Ensure that all writes to the collection are committed.
/
40627, 00000, "Columns of the mapped view backing the collection do not match collection metadata."
// *Cause: The columns of mapped view backing the collection did not match
// the collection metadata.
// *Action: Ensure that the columns of the view backing the collection match
// their description in collection metadata.
/
40628, 00000, "Projection specification is not valid JSON"
// *Cause: Projection specification was not expressed in valid JSON.
// *Action: Ensure that projection specification is expressed in valid JSON.
/
40629, 00000, "Patch specification is not valid JSON"
// *Cause: Patch specification was not expressed in valid JSON.
// *Action: Ensure that patch specification is expressed in valid JSON.
/
40630, 00000, "Versioning method '%s' is not valid."
// *Cause: The specified versioning method was not valid.
// *Action: Specify a valid versioning method.
/
40631, 00000, "The last-modified column index can only be set when the last-modified column name is set."
// *Cause: The last-modified column index was specified without setting the
// last-modified column name.
// *Action: Specify the last-modified column name if the last-modified column
// index is required.
/
40632, 00000, "Key column length value cannot be less than 0."
// *Cause: The specified key column length value was less than 0.
// *Action: If the key column length value is specified, then ensure that
// it is greater than 0.
/
40633, 00000, "When using GUID or UUID to assign character type key values, the key column length must be 32 bytes or greater."
// Cause: The specified key column length for a GUID or UUID character type
// key value was less than 32 bytes.
// Action: Ensure that the specified key column length for a GUID or UUID
// character type key value is 32 bytes or greater.'
/
40634, 00000, "Key assignment method '%s' is not valid."
// *Cause: The specified key assignment method was not valid.
// *Action: Specify a valid key assignment method.
/
40635, 00000, "If the key assignment method is 'SEQUENCE', a key column sequence name must be specified."
// *Cause: The key assignment method 'SEQUENCE' was specified, but the key
// column sequence name was not set.
// *Action: If the key assignment method is 'SEQUENCE', ensure that the key
// column sequence name is set.
/
40636, 00000, "Content column type '%s' is not valid."
// *Cause: The specified content column type was not valid.
// *Action: Specify a valid content column type.
/
40637, 00000, "Content column maximum length value cannot be less than 0."
// *Cause: The specified content column maximum length value was less than 0.
// *Action: Specify a content column maximum length value greater than 0.
/
40638, 00000, "Content column validation mode '%s' is not valid."
// *Cause: The specified content column validation mode was not valid.
// *Action: Specify a valid content column validation mode.
/
40639, 00000, "Content column compress setting '%s' is not valid."
// *Cause: The specified content column compress setting was not valid.
// *Action: Specify a valid content column compress setting.
/
40640, 00000, "Content column LOB cache setting '%s' is not valid (must be 'true' or 'false')."
// *Cause: The specified content column LOB cache setting was not valid.
// *Action:'Specify a valid content column LOB cache setting.
/
40641, 00000, "Content column LOB encrypt setting '%s' is not valid."
// *Cause: The specified content column LOB encrypt setting was not valid.
// *Action: Specify a valid content column LOB encrypt setting.
/
40642, 00000, "The collection cannot have a media type column unless the content column type is BLOB."
// *Cause: The content column type was set to a type other than Binary Large
// Object (BLOB),
// and the media type column was requested.
// *Action: If the media type column is requested, set the content column
// type to BLOB.
/
40643, 00000, "INITIAL storage clause parameter value cannot be less than 0."
// *Cause: The specified INITIAL storage clause parameter value was not valid.
// *Action: Specify a valid INITIAL storage clause parameter value.
/
40644, 00000, "PCTINCREASE storage clause parameter value cannot be less than 0."
// *Cause: The specified PCTINCREASE storage clause parameter value was not
// valid.
// *Action: Specify a valid PCTINCREASE storage clause parameter value.
/
40645, 00000, "If the key column sequence name was specified, the key column assignment method must be set to 'SEQUENCE'."
// *Cause: The key column sequence name was specified, but the key column
// assignment method was not 'SEQUENCE'.
// *Action: If the key column sequence name is specified, ensure that the key
// column assignment method is 'SEQUENCE'.
//
/
40646, 00000, "SecureFile LOB settings cannot be used when the content column type is '%s'."
// *Cause: SecureFile LOB settings were specified, but the content column was
// not of LOB type.
// Action: If SecureFile LOB settings are specified, ensure that the content
// column is of LOB type.
/
40647, 00000, "A non-zero content column maximum length cannot be set for LOB content types."
// *Cause: A non-zero content column maximum length was specified, but the
// content column was of a LOB type.
// *Action: If non-zero content column maximum length is specified, ensure that
// the content column is not of a LOB type.
/
40648, 00000, "Versioning method other than 'NONE' can only be specified if version column name is specified."
// *Cause: Versioning method other than 'NONE' was specified, but the version
// column name was not specified.
// *Action: If a versioning method other than 'NONE' is specified, ensure that
// the version column name is set.
/
40649, 00000, "Key column maximum length cannot be greater than 255 bytes."
// *Cause: A key column maximum length value greater than 255 bytes was
// specified.
// *Action: Ensure that the key column maximum length value is not greater
// than 255 bytes.
/
40650, 00000, "The specified key column type cannot be used with a maximum length."
// *Cause: A key column type that does not support maximum length was specified.
// *Action: Ensure that if a key column maximum length is set, the key column type
// supports a maximum length setting.
/
/ 40651 - 40700 JSON related
/
40651, 00000, "Key column type '%s' is not valid."
// *Cause: The specified key column type was not valid.
// *Action: Specify a valid key column type.
/
40652, 00000, "Read-only setting is not valid (must be 'true' or 'false')."
// *Cause: The specified read-only setting was not valid.
// *Action: Specify a valid read-only setting.
/
40653, 00000, "Spatial data type MDSYS.SDO_GEOMETRY not found."
// *Cause: The spatial data type MDSYS.SDO_GEOMETRY could not be found.
// *Action: Create data type MDSYS.SDO_GEOMETRY by installing Oracle Spatial
// and Graph or Oracle Locator.
/
40654, 00000, "Input to JSON generation function has unsupported data type."
// *Cause: An input parameter to the JavaScript Object Notation (JSON)
// generation function had a data type that is not supported.
// *Action: Use the correct input or a conversion function to convert the
// input to a supported data type.
/
40655, 00000, "no PASSING clause specified"
// *Cause: The PASSING clause was not specified for the bind
// variables in the query.
// *Action: Add a PASSING clause to specify the values for bind
// variables.
/
40656, 00000, "Variable in JSON path expression has no value in PASSING clause."
// *Cause: The JavaScript Object Notation (JSON) path expression contained a
// variable name that had no corresponding value in the external
// PASSING clause.
// *Action: Add a variable to the external PASSING clause and ensure that the
// names match.
/
40657, 00000, "Variable in PASSING clause has no name."
// *Cause: The expression provided in the PASSING clause had no name.
// *Action: Name the expression in the PASSING clause.
/
40658, 00000, "Collection name cannot be null for this operation."
// *Cause: An attempt was made to perform the operation without a name.
// *Action: Specify the collection name for the operation.
/
40659, 00000, "Data type does not match the specification in the collection metadata."
// *Cause: An attempt was made to use an invalid data type.
// *Action: Use the data type that is specified in the collection descriptor.
/
40660, 00000, "Content value cannot be null for instantiating a document."
// *Cause: An attempt was made to instantiate a document with a null content.
// *Action: Specify non-null content for instantiating the document.
/
40661, 00000, "Key value cannot be null for this operation."
// *Cause: An attempt was made to perform an operation with a null key.
// *Action: Specify non-null key for the operation.
/
40662, 00000, "Document cannot be null for this operation."
// *Cause: An attempt was made to perform an operation with a null document.
// *Action: Instantiate a document using the constructor before this operation.
/
40663, 00000, "cannot modify a read-only collection"
// *Cause: An attempt was made to modify a read-only collection.
// *Action: None.
/
40664, 00000, "cannot add additional IS JSON check constraint"
// *Cause: An attempt was made to add an IS JSON check constraint to a column that already had an IS JSON check constraint.
// *Action: None.
/
40665, 00000, " A client-assigned key cannot be used for this operation."
// *Cause: An attempt was made to use a client-assigned key for this collection.
// *Action: Remove the client-assigned key from the document.
/
40666, 00000, "Internal error '%s' received from JSON processor"
// *Cause: An internal error was received during a JSON operation.
// *Action: This is an internal error. Contact Oracle Support Services.
40667, 00000, "Patch operation cannot destroy JSON_ELEMENT_T type."
// *Cause: An operation in the patch specification attempted to remove the top-most container (object or array) from the JSON_ELEMENT_T type.
// *Action: Modify the patch specification by either removing the operation that deletes the top-most container or by adding an operation that adds a new top-most container.
/
40668, 00000, "collection metadata too long"
// *Cause: The collection metadata which was passed was too long.
// *Action: Reduce the size of the collection metadata.
/
40669, 00000, "Collection create failed: collection with same name but different metadata exists."
// *Cause: Creation of the collection failed because there was an existing collection with same
// name but different metadata.
// *Action: None.
/
40670, 00000, "Unable to complete collection create due to an interfering collection DDL operation."
// *Cause: Existing collection with the same name was encountered, but
// dropped from another process before its metadata could be checked.
// *Action: Retry creating the collection.
/
40671, 00000, "Collection not found."
// *Cause: Collection was not found.
// *Action: None.
/
40672, 00000, "Specified key column max length of %s bytes exceeds maximum allowed 255 bytes."
// *Cause: Key column max length specified in the supplied metadata
// exceeded maximum allowed length of 255 bytes.
// *Action: Ensure key column max length specified in the supplied metadata
// does not exceed 255 bytes.
/
40673, 00000, "%s argument cannot be NULL."
// *Cause: Supplied argument was NULL.
// *Action: Provide a valid argument.
/
40674, 00000, "Length of %s metadata value cannot exceed %s bytes."
// *Cause: Length of the supplied metadata value exceeded allowed limit.
// *Action: Provide a valid metadata value.
/
40675, 00000, "Metadata descriptor must be specified using valid JSON."
// *Cause: JSON supplied for the metadata descriptor was not valid.
// *Action: Supply valid JSON for the metadata descriptor.
/
40676, 00000, "invalid Query-By-Example (QBE) filter specification\n%s"
// *Cause: The Query-By-Example (QBE) filter specification was invalid.
// *Action: Correct the filter specification.
/
40677, 00000, "internal SODA error"
// *Cause: There was an internal error in the Simple Oracle Document Access
// (SODA) processing layer.
// *Action: None.
/
40678, 00000, "The total number of keys specified using the attributes key, keys, and filter is %s; exceeds the maximum allowed limit of %s."
// *Cause: The number of keys exceeded allowed limit.
// *Action: Reduce the number of keys to below the maximum allowed limit
/
40679, 00000, "Lob length of %s bytes exceed maximum supported length of %s bytes"
// *Cause: The large object (LOB) content that was fetched exceeded the maximum supported length
// *Action: None.
/
40680, 00000, "invalid identifier used for path expression in JSON_TABLE"
// *Cause: A double-quoted identifier used a path expression that was invalid.
// *Action: Use single quotes to specify the path expression.
/
40681, 00000, "OCI_SODA_AS_STORED cannot be used if the content column type is CLOB or VARCHAR2"
// *Cause: An attempt was made to use OCI_SODA_AS_STORED on a collection whose
// content column type is not BLOB.
// *Action: Use OCI_DEFAULT or OCI_SODA_AS_AL32UTF8.
/
40682, 00000, "invalid combination of flags used"
// *Cause: An attempt was made to use an invalid combination of flags.
// *Action: Use only one of the flags. (OCI_DEFAULT, OCI_AS_STORED or OCI_SODA_AS_AL32UTF8)
/
40683, 00000, "Value '%s' is not valid for field '%s' (must be 'true' or 'false')."
// *Cause: The specified setting was not valid.
// *Action: Specify a valid setting ('true' or 'false').
/
40684, 00000, "maximum number of key names exceeded"
// *Cause: An attempt was made to return a list of keys names for a JSON object that had more than 32767 keys.
// *Action: Reduce the number of keys in the JSON object to 32767 or less.
/
40685, 00000, "UTF-32 encoding is not supported for JSON documents."
// *Cause: UTF-32 encoded content was specified for a document of type "applicaton/json".
// *Action: Use UTF-8 or UTF-16 encoding with JavaScript Object Notation (JSON) documents.
/
40686, 00000, "For a JSON-only collection, media type of the input document must be 'application/json'."
// *Cause: An attempt was made to write a document with media type other than 'application/json'
// to a JSON-only collection.
// *Action: Provide a document with media type 'application/json'.
/
40687, 00000, "CREATE_MODE parameter of CREATE_COLLECTION function is invalid."
// *Cause: Invalid value was supplied as CREATE_MODE parameter of CREATE_COLLECTION function.
// *Action: Supply MAP or DDL constant for the CREATE_MODE parameter of CREATE_COLLECTION function.
/
40689, 00000, "Skip value cannot be set to null."
// *Cause: An attempt was made to set a null value for skip.
// *Action: Specify a non-null value for skip in the operation.
/
40690, 00000, "Limit value cannot be set to null."
// *Cause: An attempt was made to set a null value for limit.
// *Action: Specify a non-null value for limit in the operation.
/
40691, 00000, "The cursor for the operation has already been closed."
// *Cause: An attempt was made to use a cursor that has already been closed.
// *Action: Do not use the cursor that has already been closed or retry the
// operation after removing the close.
/
40692, 00000, "Version value cannot be set to null."
// *Cause: An attempt was made to set a null value for version.
// *Action: Specify a non-null value for version in the operation.
/
40693, 00000, "Filter value cannot be set to null."
// *Cause: An attempt was made to set a null value for filter.
// *Action: Specify a non-null value for filter in the operation.
/
40694, 00000, "Query-by-example (QBE) is not supported on heterogeneous collections."
// *Cause: An attempt was made use QBE on a heterogeneous collection.
// *Action: Do not use QBE on heterogeneous collection.
/
40695, 00000, "The collection does not have version column."
// *Cause: An attempt was made to use version in the operation on a collection with no version column.
// *Action: Do not use version on a collection with no version column.
/
40696, 00000, "invalid type for index property %s: expected %s"
// *Cause: An invalid index property type was specified.
// *Action: Supply a valid type for the index property.
/
40697, 00000, "invalid value specified for index property 'dataguide'"
// *Cause: An invalid value for the index property 'dataguide' was specified.
// *Action: Supply a valid value for the 'dataguide' index property. Valid values are 'on' or 'off'.
/
40698, 00000, "invalid value specified for index property 'search_on'"
// *Cause: An invalid value for the index property 'search_on' was specified.
// *Action: Specify a valid value for the 'search_on' index property. Valid values are 'none', 'text', or 'text_value'.
/
40699, 00000, "invalid value specified for index property 'order'"
// *Cause: An invalid value for the index property 'order' was specified.
// *Action: Specify a valid value for the 'order' index property. Valid values are 'asc', 'desc', '-1', or '1'.
/
40700, 00000, "missing %s index property"
// *Cause: A mandatory index property was missing.
// *Action: Specify the mandatory index property.
/
// JSON/SODA errors continue from 40711
//
/////////////////////////////////////////////////////////////////////////////
/ 40701 - 40710 RESERVED FOR CUR
//
40701, 00000, "null case ID column - cannot provide row importance"
// *Cause: The row importance was enabled, but without a
// corresponding case or row identifier column in the build data.
// *Action: Provide a non-null case identifier column in the build data.
/
/////////////////////////////////////////////////////////////////////////////
/ 40711 - 40800 are reserved for JSON/SODA
/////////////////////////////////////////////////////////////////////////////
40711, 00000, "incompatible index field properties %s and %s"
// *Cause: Incompatible index field properties were specified.
// *Action: Specify compatible index field properties.
/
40712, 00000, "Index property %s cannot be specified without specifying the 'fields'."
// *Cause: An index property was specified without specifying the 'fields' property.
// *Action: Specify the properties of index fields.
/
40713, 00000, "Index property 'lax' cannot be specified with 'scalarRequired'."
// *Cause: Index properties 'lax' and 'scalarRequired' were both specified.
// *Action: Specify either 'lax' or 'scalarRequired' but not both.
/
40714, 00000, "data type %s not recognized or acceptable for an index column"
// *Cause: An invalid data type property was used.
// *Action: Specify a valid data type (for example, STRING, VARCHAR, VARCHAR2, NUMBER, DATE, or TIMESTAMP).
/
40715, 00000, "Index property 'maxLength' cannot be specified with non-string data types."
// *Cause: Index property 'maxLength' was specified with a non-string data type.
// *Action: Remove the 'maxLength' index property if a non-string data type must be used.
/
40716, 00000, "Text indexing is not supported on heterogeneous collections."
// *Cause: An attempt was made to create a text index on a heterogeneous collection.
// *Action: Do not create a text index on a heterogeneous collection.
/
40717, 00000, "Functional indexing is not supported on heterogeneous collections."
// *Cause: An attempt was made to create a functional index on a heterogeneous collection.
// *Action: Do not create a functional index on a heterogeneous collection.
/
40718, 00000, "Geospatial indexing is not supported on heterogeneous collections."
// *Cause: An attempt was made to create a geospatial index on a heterogeneous collection.
// *Action: Do not create a geospatial index on a heterogeneous collection.
/
40719, 00000, "invalid index property %s"
// *Cause: An invalid index property was specified.
// *Action: Specify a valid index property.
/
40720, 00000, "Text indexing is not supported on collections with key column of NVARCHAR2 data type."
// *Cause: An attempt was made to create a text index on a collection with a key column of NVARCHAR2 data type.
// *Action: Do not create an index on a collection that has a key column of NVARCHAR2 data type.
/
40721, 00000, "Text indexing is not supported on collections with content column of NVARCHAR2 or NCLOB data type."
// *Cause: An attempt was made to create a text index on a collection with a content column of NVARCHAR2 or NCLOB data type.
// *Action: Do not create an index on a collection that has a content column of NVARCHAR2 or NCLOB data type.
/
40722, 00000, "Text indexing is not supported on collections with encrypted content column."
// *Cause: An attempt was made to create a text index on a collection with an encrypted content column.
// *Action: Do not create an index on a collection with an encrypted content column.
/
40723, 00000, "index specification cannot be null"
// *Cause: An attempt was made to specify a null index specification.
// *Action: Specify a non-null index specification.
/
40724, 00000, "array steps in the fields path is not supported"
// *Cause: An attempt was made to use array steps in fields path.
// *Action: Do not use array steps in the fields path.
/
40725, 00000, "path for the field in the index specification cannot be null"
// *Cause: An attempt was made to specify a null value for the field's path in the index specification.
// *Action: Specify a non-null value for the field's path in the index specification.
/
40726, 00000, "path for the field in the index specification is invalid"
// *Cause: An attempt was made to specify an invalid path in the index specification.
// *Action: Specify a valid path for the field in the index specification.
/
40727, 00000, "number of paths with string data type exceeds the maximum permissible limit of 16"
// *Cause: Number of paths with string data type exceeds the maximum permissible limit of 16.
// *Action: Reduce the number of paths with string data type.
/
40728, 00000, "missing dot separator in path %s at position %s."
// *Cause: A dot separator was missing in the path expression.
// *Action: Specify the missing dot step separator in the path expression.
/
40729, 00000, "unclosed quote at end of path %s"
// *Cause: A quote that was not closed was detected at the end of the path.
// *Action: Specify the missing back quote at the end of the path expression.
/
40730, 00000, "an invalid character detected in the escape string in the path %s at position %s"
// *Cause: An attempt was made to use a path containing invalid charcters in the escape string.
// *Action: Specify a valid escape string in the path expression.
/
40731, 00000, "invalid quoted step in the path %s at position %s"
// *Cause: An attempt was made to use an invalid quoted step in the path.
// *Action: Specify a valid quoted step in the path expression.
/
40732, 00000, "incomplete escape sequence in the path %s"
// *Cause: An attempt was made to use an incomplete escape sequence in the path.
// *Action: Specify an escape sequence that is complete in the path expression.
/
40733, 00000, "An index with the specified name already exists in the schema."
// *Cause: An attempt was made to create an index with the same name as another index in the schema.
// *Action: Specify an index name that does not match the name of any indexes already existing in the schema.
/
40734, 00000, "key for the document to replace must be specified using the key attribute"
// *Cause: An attempt was made to replace a document without setting the key attribute.
// *Action: Set the key attribute for the replace operation.
/
40736, 00000, "Query-By-Example (QBE) filter is not valid JSON\n%s"
// *Cause: QBE filter was not expressed in valid JSON.
// *Action: Ensure that the QBE filter is expressed in valid JSON.
/
40737, 00000, "partitionColumn.path is missing"
// *Cause: partitionColumn.name was specified, but partitionColumn.path was missing.
// *Action: Specify partitionColumn.path.
/
40738, 00000, "partitionColumn.name is missing"
// *Cause: partitionColumn.path, partitionColumn.maxLength, or partitionColumn.sqlType
// is specified, but partitionColumn.name is missing.
// *Action: Specify partitionColumn.name value.
/
40739, 00000, "Partition column type %s is not valid."
// *Cause: The specified partition column type was not valid.
// *Action: Specify a valid partition column type.
/
40740, 00000, "Cannot use '%' with content columns of type '%'."
// *Cause: An invalid combination of content column settings was specified.
// *Action: Specify a valid combination of content column settings.
/
40741, 00000, "Cannot use '%' with a heterogeneous collection."
// *Cause: An invalid combination of heterogeneous collection settings was specified.
// *Action: Specify a valid combination of heterogeneous collection settings.
/
40742, 00000, "Invalid value of '%'."
// *Cause: An invalid metadata component value was specified.
// *Action: Specify a valid metadata component value.
/
40743, 00000, "Partition column length value cannot be less than 0."
// *Cause: The specified partition column length value was less than 0.
// *Action: If the partition column length value is specified, then ensure that
// it is greater than 0.
/
40744, 00000, "Specified partition column max length of %s bytes exceeds maximum allowed %s bytes."
// *Cause: Partition column max length specified in the supplied metadata
// exceeded the maximum allowed length.
// *Action: Ensure that the partition column max length specified in the supplied metadata
// does not exceed the maximum allowed length.
/
40745, 00000, "The specified partition column type cannot be used with a maximum length."
// *Cause: A partition column type that does not support maximum length was specified.
// *Action: Ensure that, if a partition column maximum length is set, the partition column type
// supports a maximum length setting.
/
40746, 00000, "keyColumn.path must be set with '%s' key assignment method."
// *Cause: keyColumn.path was not set with the specified EXTRACT or INSERT key assignment method.
// *Action: Ensure that keyColumn.path is set when the key assignment method is EXTRACT or INSERT.
/
40747, 00000, "The value %s is not a valid key of type %s."
// *Cause: The key value was not of a valid type.
// *Action: Ensure that the input for key is of a valid type.
/
40748, 00000, "SKIP and LIMIT attributes cannot be used for count operation."
// *Cause: An attempt was made to use SKIP and LIMIT attributes in a count operation.
// *Action: Do not use SKIP or LIMIT attributes in a count operation.
/
40749, 00000, "Index property %s cannot be specified without specifying the fields or spatial properties."
// *Cause: An index property was specified without specifying the fields or spatial properties.
// *Action: Specify either the properties of the index fields or spatial.
/
40750, 00000, "Document flags are not the same in all the input documents."
// *Cause: The document flags were not the same in all the input documents supplied to
// the insert operation.
// *Action: Ensure that the document flags are the same in all the input documents supplied
// to the insert operation.
/
40751, 00000, "Input document array length must be greater than 0."
// *Cause: The supplied input document array length was less than or equal to 0.
// *Action: Supply the input document array length that is greater than 0.
/
/////////////////////////////////////////////////////////////////////////////
/ next free error range starts from 40800
//////////// Errors starting from 41001
/
/////////////////////////////////////////////////////////////////////////////
// 41001-41099 Reserved for Transparent Session Migration
/////////////////////////////////////////////////////////////////////////////
41001, 00000, "session id list not specified"
// *Cause: An attempt to migrate was made, which failed because
// the session id list specified was null.
// *Action: Check the session id list, and try again with a valid value.
41002, 00000, "destination instance not specified"
// *Cause: An attempt to migrate was made, which failed because
// the destination instance specified was null.
// *Action: Check the destination instance , and try again with a valid value.
41003, 00000, "client id not specified"
// *Cause: An attempt to migrate was made, which failed because
// the client id specified was null.
// *Action: Check the client id, and try again with a valid value.
41004, 00000, "percentage not specified"
// *Cause: An attempt to migrate was made, which failed because
// the percentage specified was null.
// *Action: Check the percentage, and try again with a valid value.
41005, 00000, "session id list not specified"
// *Cause: An attempt to cancel migration was made, which failed because
// the session id list specified was null.
// *Action: Check the session id list, and try again with a valid value.
41006, 00000, "session id not specified"
// *Cause: An attempt to get migration status was made, which failed because
// the session id specified was null.
// *Action: Check the session id, and try again with a valid value.
41007, 00000, "sid field is null"
// *Cause: A session id instance passed into a dbms_tsm procedure or
// function had a null sid field.
// *Action: Check the session id, and try again with a valid value.
41008, 00000, "serial# field is null"
// *Cause: A session id instance passed into a dbms_tsm procedure or
// function had a null serial# field.
// *Action: Check the session id, and try again with a valid value.
41009, 00000, "Session with session number %s, serial number %s does not exist"
// *Cause: An attempt to migrate was made, which failed because of
// invalid session number and/or serial number.
// *Action: Check the session number and serial number and try again.
41010, 00000, "No more memory to hold connection state information"
// *Cause: An attempt to reference more connections than configured
// *Action: Check the connection information and try again.
41011, 00000, "Operation failed for session id %s, serial number %s"
// *Cause: An migration related operation failed because of contention
// between sessions.
// *Action: Check the additional error codes for more information, and
// retry operation later.
41012, 00000, "Migration not allowed for session number %s, serial number %s"
// *Cause: An attempt to migrate was made, which failed because
// the session specified cannot be migrated.
// *Action: Check the session number and serial number and try again.
41013, 00000, "instance name not specified"
// *Cause: An attempt to migrate was made, which failed because
// the instance name specified was null.
// *Action: Check the instance name, and try again with a valid value.
41014, 00000, "Session number %s, serial number %s currently being migrated"
// *Cause: An attempt to migrate was made, which failed because
// the session specified is currently being migrated.
// *Action: Check the session number and serial number and try again.
41015, 00000, "destination connect string not specified"
// *Cause: A migration attempt was made, which failed because
// the connect string specified was null.
// *Action: Check the connect string and try again.
41016, 00000, "Session recreation failed"
// *Cause: Session recreation failed at the destination instance.
// *Action: Check session state and try migration again
41017, 00000, "Session prepare failed for session number %s, serial number %s"
// *Cause: A migration attempt was made, which failed because
// session prepare failed.
// *Action: Retry migration again after checking all arguments.
41019, 00000, "Session begin at the destination instance failed"
// *Cause: Session begin failed at the destination instance because
// the shadow connection could not be established.
// *Action: Check the connect string and try beginning the session again.
41020, 00000, "invalid value \"%s\" specified for parameter \"%s\""
// *Cause: An invalid value was specified for the the given parameter.
// *Action: Correct the value being specified for the parameter.
41021, 00000, "OCI error during transparent session migration"
// *Cause: An OCI operation failed during transparent session migration.
// *Action: Check the OCI error signalled, and take corrective action.
41022, 00000, "instance name not specified"
// *Cause: An attempt to recover after instance death was made,
// which failed because the instance name specified was null.
// *Action: Check the instance name, and try again with a valid value.
41023, 00000, "death time not specified"
// *Cause: An attempt to recover after instance death was made,
// which failed because the death time specified was null.
// *Action: Check the death time, and try again with a valid value.
41024, 00000, "Cursor needs to be parsed again"
// *Cause: An SQL operation failed because the cursor state was lost.
// *Action: Reissue all operations starting from parse.
41025, 00000, "sid field %s is invalid"
// *Cause: A session id instance passed into a dbms_tsm procedure or
// function had an invalid sid field.
// *Action: Check the session id, and try again with a valid value.
41026, 00000, "serial# field %s is invalid"
// *Cause: A session id instance passed into a dbms_tsm procedure or
// function had an invalid serial# field.
// *Action: Check the serial#, and try again with a valid value.
41027, 00000, "Error status %s during OCI operation at %s"
// *Cause: An OCI operation failed during transparent session migration.
// *Action: Check the OCI error signalled, and take corrective action.
41028, 00000, "Session id not specified"
// *Cause: An attempt to migrate was made, which failed during migration
// because the session id specified by the client was null.
// *Action: Check the session id, and try again with a valid value.
41029, 00000, "Destination session id not specified for sid %s serial# %s"
// *Cause: An attempt to migrate was made, which failed during migration
// because the destination session id specified by the client
// was null.
// *Action: Check the session id, and try again with a valid value.
41030, 00000, "Session id not specified"
// *Cause: An attempt to migrate was made, which failed during migration
// because the session id specified by the client was null.
// *Action: Check the session id, and try again with a valid value.
41031, 00000, "Destination session key not specified for sid %s serial# %s"
// *Cause: An attempt to migrate was made, which failed during migration
// because the destination session key specified by the client
// was null.
// *Action: Check the session id, and try again with a valid value.
/
/ 41095 is reserved for tuning
/ 41096 is reserved for tuning component state handling
/ levels 0x0000000f reserved for cursors
/ 41097 is reserved for tuning migratability checks
/ 41098 is reserved for tracing
/ 41099 is reserved for debug mode
////////////////////////////////////////////////////////////////////////////
/// Reserved 41100 - 41199
/// DIRECTOR messages
////////////////////////////////////////////////////////////////////////////
41100, 0000, "Oracle Cluster Registry operation failed with event %s."
// *Cause: The Portable Clusterware/Oracle Cluster Registry stack
// returned an error.
// *Action: Check if the Portable Clusterware stack is properly brought up.
41101, 0000, "The database: %s has already been designated as Cluster Director."
// *Cause: An attempt was made to designate multiple databases as the
// Cluster Director.
// *Action: Undesignate the existing Cluster Director before
// Designating a new one.
41102, 0000, "No database has currently been designated as Cluster Director."
// *Cause: An attempt was made to query/undesignate a Cluster Director when
// no database has been designated as Cluster Director.
41103, 0000, "Only the designated Cluster Director: %s can undesignate itself."
// *Cause: An attempt was made to undesignate the current Cluster Director
// by a database that is not the Cluster Director.
// *Action: Login to the currently designated Cluster Director to perform
// the undesignation.
41104, 0000, "The database: %s is the Cluster Director."
// *Cause: An attempt was made to control the Cluster Director on a database
// that is not the Cluster Director.
// *Action: Log in to the currently designated Cluster Director to perform
// the control operation.
41105, 0000, "The Cluster Director is not stopped."
// *Cause: An attempt was made to control the Cluster Director before the
// Cluster Director was stopped.
// *Action: Use dbms_cluster_director.stop to stop the Cluster Director and
// retry the control operation.
41106, 0000, "invalid argument %s: value is null"
// *Cause: An attempt to read the scan hostname or port failed
// *Action: Verify pcw is running and scan is configured.
// Run grdcscan read_config to verify or
// grdcscan set_config host:port to set scan name and port.
41107, 0000, "invalid argument: service %s cannot be found"
// *Cause: The program attempted to access a nonexistent or deleted service.
// *Action: Check to make sure the service has been properly created.
41108, 0000, "Posting system alert with reason_id %s failed with code [%s] [%s]"
// *Cause: Internal Error: An attempt to post a system alert failed.
// *Action: If this condition repeats, please contact Oracle Support.
41109, 0000, "Updating system alert with reason_id %s failed; previous alert not found"
// *Cause: System Error: An attempt to update a system alert failed.
// The alert was improperly cleared from WRI$_ALERT_OUTSTANDING.
// *Action: Do not delete from WRI$_ALERT_OUTSTANDING.
// If this condition repeats, please contact Oracle Support.
41110, 0000, "The Director has blocked this instance. Cannot start [%s]"
// *Cause: An attempt to start services on an instance that will be shutdown
// *Action: Start the services on another available instance
//
////////////////////////////////////////////////////////////////////////////
/// 41200 - 41299 Reserved for Session State Capture and Restore (SSCR)
////////////////////////////////////////////////////////////////////////////
41201, 0000, "Session state not capturable due to reason (%s, %s)"
// *Cause: Session state capture was initiated when session state
// could not be captured.
// *Action: Check session state status and make sure session state can be
// captured.
41202, 0000, "Session state capture or restore failed"
// *Cause: Capture or restore operation failed.
// *Action: Check session state status and failure reason for details.
41203, 0000, "Invalid session state operation"
// *Cause: Invalid session state operation was issued.
// *Action: Check if session status was valid for the current operation.
41204, 0000, "Session capture in progress"
// *Cause: Session state capture was initiated and could not perform
// the requested operation.
// *Action: Wait for the current capture to complete or abort it.
41205, 0000, "Invalid parameter for session state capture or restore"
// *Cause: Invalid parameter was passed to session state capture or
// restore interface.
// *Action: Correct the invalid parameter(s).
41206, 0000, "Session capture or restore internal error KPCSFR-%s"
// *Cause: Internal operation error was encountered.
// *Action: Turn on related trace for details and report it as a bug.
41207, 0000, "Cannot restore session state due to reason (%s, %s)"
// *Cause: Session state restore was initiated when session was not
// ready for state restore.
// *Action: Restore session state immediately after logging into
// a session or perform necessary operations to make the
// session ready for restore; for example, commit current
// transaction, or close BFiles.
41208, 00000, "OCI error during session state capture and restore"
// *Cause: An OCI operation failed during an internal operation of
// session state capture and restore.
// *Action: Check the OCI error signaled and take corrective action.
41209, 00000, "OCI operation failed at %s due to ORA-%s"
// *Cause: An OCI operation failed during an internal operation of
// session state capture and restore.
// *Action: Check the OCI error signaled and take corrective action.
41210, 00000, "Failed to resolve session state directory object"
// *Cause: Session state directory object passed to capture or
// restore was incorrect.
// *Action: Verify session state directory object and retry.
41211, 00000, "Failed to insert capture or restore record"
// *Cause: An error occurred while capture or restore record was
// being stored into the database.
// *Action: Check the error signaled and take corrective action.
41251, 0000, "Failed to restore session state from a file (error code %d)"
// *Cause: Session state file may be corrupted.
// *Action: Ensure that the file is a session state file.
//
41252, 0000, "Failed to switch to new session in SSCR"
// *Cause: This is the generic internal error number for the SSCR
// exceptions. This indicates that the SSCR has encountered
// an exceptional condition.
// *Action: Report as a bug.
//
41253, 0000, "Failed to access session state file"
// *Cause: An error was encountered while reading from or writing to
// session state capture file.
// *Action: Check the error stack for the actual error number and
// turn on tracing if necessary.
//
41254, 0000, "Invalid session state file: %s"
// *Cause: An invalid session state file was used in session state
// restore operation.
// *Action: Check if the session state file is a valid file created
// by session capture.
//
41255, 0000, "Package not supported: %s"
// *Cause: The specified package is not supported.
// *Action: Do not call the package functions and procedures.
//
// 41299 is reserved for SSCR automated test event
////////////////////////////////////////////////////////////////////////////
/// 41300 - 41399 Reserved for session state media drivers
////////////////////////////////////////////////////////////////////////////
41300, 0000, "File driver is not initialized"
// *Cause: An attempt was made to operate on the uninitialized file driver.
// *Action: Initialize the file driver using the OCIServerAttach function.
//
41301, 0000, "failed to write data to file"
// *Cause: You may not have sufficient privileges or quotas for this action.
// *Action: Ensure that you have sufficient privileges
// and quotas for this action.
//
41302, 0000, "failed to read data from file"
// *Cause: The file may not exist or you do not have privileges
// for this action.
// *Action: Ensure that the file exists and that you have
// sufficient privileges for this action.
//
41303, 0000, "Received partial data from file"
// *Cause: This is the generic internal error number for file driver
// exceptions. This indicated that file driver encountered an
// exception condition.
// *Action: Report as a bug.
//
41304, 0000, "Failed to connect to file driver"
// *Cause: The connect string may be incorrect.
// *Action: Ensure that the connect string is correct.
//
41305, 0000, "Failed to open file"
// *Cause: You may not have sufficient privileges for this action.
// *Action: Ensure that the file exists and that you have sufficient
// privileges for this action.
//
////////////////////////////////////////////////////////////////////////////
/// 41400 - 41499 Reserved for OCI
////////////////////////////////////////////////////////////////////////////
41400, 0000, "Bind character set (%s) does not match database character set (%s)"
// *Cause: In this recursive OCI call, the bind character set was
// different from the current database character set.
// This is usually caused by database character set change.
// *Action: Be sure to obtain bind data in database character set and
// do rebind in the current environment.
//
41401, 0000, "Define character set (%s) does not match database character set (%s)"
// *Cause: In this recursive OCI call, the define character set was
// different from the current database character set.
// This is usually caused by database character set change.
// *Action: Be sure to do redefine in the current environment.
//
41402, 0000, "SCNs not valid after failover; failover cannot continue"
// *Cause: The Oracle server process failed and replay was initiated.
// However, the system change numbers (SCN) recorded during the
// original execution are not valid on the new database after
// failover. This may happen if the new database was opened with
// RESETLOGS, or if the new database was set up to allow significant
// lag in replication. Failover cannot continue.
// *Action: Resubmit the request.
//
41403, 0000, "failed over to older server; failover cannot continue (%s, %s, %s)"
// *Cause: Failover replay was enabled for a service in which some standby
// databases were older than the original server and could not replay
// work from the original server.
// *Action: Disable replay on the service, or upgrade your databases to
// compatible versions.
//
41404, 0000, "invalid replay context"
// *Cause: Application continuity protocol was violated.
// *Action: Contact Oracle Support Services.
//
41405, 0000, "Failed over to older server; failover cannot continue (%s, %s)."
// *Cause: Failover replay was enabled for a service in which some standby
// databases were older than the original server and could not replay
// work from the original server.
// *Action: Disable replay on the service, or upgrade your databases to
// compatible versions.
//
41406, 0000, "driver disabled replay"
// *Document: NO
// *Cause: The application driver side of Application Continuity disabled
// replay mode. This is a normal code used in internal protocols,
// and should not be seen by customers or raised as an error.
// *Action: If displayed as an error, this represents an Application
// Continuity protocol violation, and customer should report
// it to Oracle Support Services.
//
41407, 0000, "SQL command not supported for replay; replay disabled"
// *Cause: Application replay encountered a command that was not supported
// for replay, and so replay was disabled.
// *Action: Use a service without replay for this operation.
//
41408, 0000, "embedded COMMIT in last call; failover cannot continue"
// *Cause: The Oracle server process failed after committing a transaction
// but COMMIT was embedded in a stored procedure and it cannot
// be guaranteed that the stored procedure finished. Failover
// cannot continue.
// *Action: User may resubmit request.
//
41409, 0000, "cannot replay committed transaction; failover cannot continue"
// *Cause: The Oracle server process failed after committing a transaction
// in the current request. The transaction cannot be replayed, so
// the current request cannot be replayed and session state cannot
// be restored. Failover cannot continue.
// *Action: User may resubmit request.
//
41410, 0000, "call committed a transaction and started a new transaction; failover cannot continue"
// *Cause: The Oracle server process failed after committing a transaction
// in the current request. One call that committed a transaction,
// and thus cannot be replayed, also started a new transaction.
// Since that call cannot be replayed, the new transaction cannot
// be restored. Failover cannot continue.
// *Action: Resubmit, and consider restructuring application to not start
// a transaction in the same call after committing a transaction.
//
41411, 0000, "too many round trips in request; replay disabled"
// *Cause: The Oracle server process failed after executing a request with
// more than 65535 round trips, so replay of the request is
// not possible.
// *Action: Resubmit, and consider partitioning application calls into
// more requests with fewer round trips.
//
41412, 0000, "results changed during replay; failover cannot continue"
// *Cause: The Oracle server process failed and replay was initiated.
// However, results of the replay differed from the original
// execution. Failover cannot continue.
// *Action: User may resubmit request.
//
41413, 0000, "too much data in call capture; replay disabled"
// *Cause: The Oracle server process failed after executing a request with
// a complicated call whose capture had too much data, therefore,
// replaying of the request was not possible.
// *Action: Resubmit and partition the application calls into more requests
// with fewer round trips.
//
41414, 0000, "could not allocate memory for call capture; replay disabled"
// *Cause: The Oracle server process failed after executing a request with
// a memory allocation failure during capture, therefore,
// replaying of the request was not possible.
// *Action: Resubmit and partition the application calls into more requests
// with fewer round trips.
//
41415, 0000, "duplicate or conflicting KEEP or NOKEEP specifications"
// *Cause: Duplicate KEEP or NOKEEP was specified, or both KEEP and NOKEEP
// were specified.
// *Action: Remove the duplicate or conflicting specification.
//
41416, 00000, "Internal DBMS_FILE_TRANSFER event number"
// *Document: NO
// *Cause: N/A
// *Action: Set this event only under the supervision of Oracle Support
// Services or Development. It enables tracing in DBMS_FILE_TRANSFER
// package, see kpbf.c for trace levels.
//
41417, 0000, "invalid use of DBMS_APP_CONT_PRVT: [%s] [%s] [mode=%s] [%s] [%s] [%s] [%s] [%s]"
// *Cause: Application continuity protocol was violated.
// *Action: Contact Oracle Support Services.
//
41418, 0000, "Replay context is corrupt. Reason: [%s], [%s], [%s], [%s]"
// *Cause: The replay context was not valid.
// *Action: Check your network configuration and hardware.
//
41419, 0000, "session released to server pool"
// *Document: NO
// *Cause: The DRCP-based application released the session to the server
// pool, thereby disabling replay mode.
// This is a normal code used in internal protocols,
// and should not be seen by customers or raised as an error.
// *Action: If displayed as an error, this represents an Application
// Continuity protocol violation, and customer should report
// it to Oracle Support Services.
//
41420, 0000, "block size cannot be zero"
// *Cause: The block size sent by remote server was zero.
// *Action: Specify a valid block size as documented in the Oracle Database
// Administration Guide when creating data files. If displayed as
// an error, this represents a DBMS_FILE_TRANSFER protocol violation
// which should be reported to Oracle Support Services.
//
41421, 0000, "database request ended"
// *Cause: The application ended its database request or released the
// connection to the connection pool, thereby disabling replay mode.
// *Action: Resubmit the request.
//
41422, 0000, "unsupported use of an incoming database link connection from a background, JOBQ slave or PQ slave"
// *Cause: A background, JOBQ slave or PQ slave attempted to use an
// incoming database link connection and such usage is not
// supported.
// *Action: Contact Oracle Support Services.
// NLS_DO_NOT_TRANSLATE [41423,41423]
41423, 0000, " PDB closure error"
// *Document: NO
// *Cause: Internal
// *Action: Internal
//
41424, 0000, "initial session state mismatch during replay"
// *Cause: The initial session state at replay did not match the state
// at the beginning of the request.
// *Action: Review this request to see if the request committed, and if
// not whether it is safe to resubmit.
//
41425, 0000, "replay disabled for a global transaction that uses Two-Phase Commit (2PC) managed by external Transaction Processing Monitor (TPM)"
// *Cause: The request was unable to replay because it was part of a
// Two-Phase Commit (2PC) transaction managed by the
// Transaction Processing Monitor (TPM).
// *Action: Two-Phase Commit (2PC) through the external Transaction
// Processing Monitor (TPM) is not supported for Application
// Continuity. Check whether the application can use local or
// one-phase transactions.
41426, 0000, "could not determine session state information"
// *Cause: Unable to obtain session state classification information.
// *Action: Check alert log for more details.
//
41427, 0000, "client session environment missmatch at replay"
// *Cause: The client session environment could not be restored
// to the original values.
// *Action: Check the setting of failover_restore on your service.
//
41428, 0000, "initial session state could not be verified during replay"
// *Cause: The client session environment could not be verified
// for a failover of the first statement in a series.
// *Action: Upgrade to a driver with full support for automatic
// Application Continuity.
//
41429, 0000, "non-replayable side effect on failed connection"
// *Cause: The application executed an operation with side effects,
// which disabled Application Continuity for this request.
// *Action: Review this request to see if the request committed, and if
// not whether it is safe to resubmit wth this side effect.
//
41430, 0000, "connection test not found or is predefined"
// *Cause: An attempt was made to enable or disable a connection test that
// did not exist or to delete a predefined connection test.
// *Action: Query the view DBA_CONNECTION_TESTS to see which connection
// tests exist and add the connection test, if needed. Predefined
// connection tests can be disabled but not deleted.
//
41431, 0000, "Application Continuity does not support ISOLATION_LEVEL=SERIALIZABLE; failover cannot continue."
// *Cause: Application Continuity did not support ISOLATION_LEVEL=SERIALIZABLE.
// *Action: Consider using SELECT FOR UPDATE instead of serializable
// transactions.
41432, 0000, "An open transaction is detected when attempting to start a request or at the end of a request."
// *Cause: It is illegal to have an open transaction when starting a new
// request or at the end of a request.
// *Action: Commit or rollback the open transaction in the previous request
// or in the callback for session setup or failover.
// It is illegal to have an open transaction at the end
// of a labeling or failover callback
41433, 0000, "Diagnostic event for enabling session state tracking (ksusgn)"
// *Document: NO
// *Cause:
// *Action: Internal use only.
//
////////////////////////////////////////////////////////////////////////////
/// Reserved 41500 - 41520
/// Parameter Migration Messages
////////////////////////////////////////////////////////////////////////////
41500, 0000, "possibly obsolete parameter %s"
// *Document: NO
// *Cause: An attempt was made to migrate a session to another
// instance that did not contain the same parameter
// *Action: Avoid migration into this instance or reconnect without
// setting the session parameter.
41501, 0000, "parameter %s has had a type modification"
// *Document: NO
// *Cause: An attempt was made to migrate a session to another
// instance that had modified the parmeter to a different
// type.
// *Action: Avoid migration into this instance or reconnect without
// setting the session parameter.
/////////////////////////////////////////////////////////////////////////////
// Reserving 41600 - 41999 for Rule Manager / Expression Filter
/////////////////////////////////////////////////////////////////////////////
41601, 0000, "invalid property for the rule class"
// *Document: YES
// *Cause: An invalid property was specified for the rule class.
// *Action: Correct the rule class properties and try again.
41602, 0000, "insufficient privileges"
// *Document: YES
// *Cause: The user does not have required privileges on the object.
// *Action: Obtain the required privileges and try again.
41603, 0000, "invalid privilege type"
// *Document: YES
// *Cause: An attempt was made to grant an invalid privilege on a rule class.
// *Action: Correct the privilege name and try again.
41604, 0000, "cannot revoke a privilege that was not granted"
// *Document: YES
// *Cause: An attempt was made to revoke a privilege that was never granted.
// *Action: None
41605, 0000, "schema extended name not allowed: %s"
// *Document: YES
// *Cause: An attempt was made to specify a schema extended name for an
// event structure, a rule class, or an action call-back procedure.
// *Action: Specify the object name with out a schema extension.
41606, 0000, "rule class name already used by an existing object"
// *Document: YES
// *Cause: An attempt was made to create a rule class with a name that is
// already used by an existing object.
// *Action: Specify a different name for the rule class and try again.
41607, 0000, "rule class creation failed with %s"
// *Document: YES
// *Cause: rule class creation failed with a recursive error.
// *Action: Correct the rule class specification and try again.
41608, 0000, "rule class does not exist"
// *Document: YES
// *Cause: An attempt was made to access a rule class that does not exist
// or is not accessible.
// *Action: Correct the rule class name and try again.
41609, 0000, "invalid name for the rule class"
// *Document: YES
// *Cause: An invalid name was specified for the rule class.
// *Action: Correct the rule class name and try again.
41610, 0000, "callback procedure name already used for an existing object"
// *Document: YES
// *Cause: An attempt was made to create a callback procedure with a name
// that is already used for an existing object.
// *Action: Choose another name for the callback procedure.
41611, 0000, "rule identifier \"%s\" not unique in the rule class"
// *Document: YES
// *Cause: An attempt was made to use a duplicate rule identifier.
// *Action: Choose a unique identifier for the rule and try again.
41612, 0000, "scalar values expected for action preferences"
// *Document: YES
// *Cause: Incorrect values were specified for the action preferences.
// *Action: Correct the action preferences values and try again.
41613, 0000, "invalid action preference for rule class: %s"
// *Document: YES
// *Cause: An attempt was made to use an invalid action preference.
// *Action: Correct the input and try again.
41614, 0000, "missing action preference value"
// *Document: YES
// *Cause: Values for one or more action preferences were not specified.
// *Action: Specify values for all relevant action preferences.
41615, 0000, "too many values in action preference list"
// *Document: YES
// *Cause: Too many entries were specified in the action preference
// values list. The action preference values list should not have
// more entries than the action preference names list.
// *Action: Correct the input and try again.
41616, 0000, "rule class's action callback procedure may have errors"
// *Document: YES
// *Cause: The operation failed because the action callback procedure
// associated with the rule class has compilation errors.
// *Action: Recompile the action callback procedure and try the operation
// again.
41617, 0000, "action preference name \"%s\" collides with an event attribute name"
// *Document: YES
// *Cause: An attempt was made to create an action preference with the same
// name as an attribute in the event structure.
// *Action: Choose a different name for action preference and try again.
41618, 0000, "specified rule does not exist"
// *Document: YES
// *Cause: Invalid rule identifier was used to operate on a rule definition.
// *Action: Use a valid rule identifier.
41619, 0000, "rule manager feature currently not supported"
// *Document: YES
// *Cause: An attempt was made to use a rule manager feature that is currently
// not supported.
// *Action: No action necessary. This is an informational message only.
41620, 0000, "invalid ordering property for the rule class"
// *Document: YES
// *Cause: An attempt was made to specify an invalid ordering property for
// the rule class.
// *Action: Make sure that the attributes listed in the ordering property
// are all part of the rule class/event structure definition with
// appropriate extended names.
41621, 0000, "error in ordering property :%s"
// *Document: YES
// *Cause: An attempt was made to specify an invalid ordering property for
// the rule class.
// *Action: Make sure that the attributes listed in the ordering property
// are all part of the rule class/event structure definition with
// appropriate extended names.
41622, 0000, "invalid primitive event object in rule class properties : %s"
// *Document: YES
// *Cause: In the rule class properties, the name used for one or the
// primitive event objects was not found in the corresponding
// composite event structure.
// *Action: Correct the name of the primitive event object in the rule class
// properties and try again.
41623, 0000, "conflicting values for autocommit and duration properties"
// *Document: YES
// *Cause: An attempt was made to create a rule class with autocommit enabled
// when the duration of events is set to TRANSACTION.
// *Action: Turn autocommit off or choose a different duration policy.
41624, 0000, "invalid duration policy for primitive object in a composite event"
// *Document: YES
// *Cause: An attempt was made to specify a SESSION or TRANSACTION duration
// policy for the primitive objects.
// *Action: Correct the rule class properties and try again.
41625, 0000, "event structure %s does not exist"
// *Document: YES
// *Cause: The object type that represents the event structure was not
// created in the user's schema.
// *Action: Create the object type with the event structure's name and try
// again.
41626, 0000, "invalid XML element \"%s\" in rule class properties"
// *Document: YES
// *Cause: An invalid XML element was used in the properties specification
// for the rule class.
// *Action: Use the correct (case-sensitive) tags in the properties.
41627, 0000, "event structure object type in inconsistent state"
// *Document: YES
// *Cause: The object type specified for the event structure was in an
// inconsistent state.
// *Action: Fix the object type and try again.
41628, 0000, "invalid usage of \"%s\" attribute in \"%s\" element"
// *Document: YES
// *Cause: An invalid or unsupported XML attribute was used in the
// rule class properties.
// *Action: Use the correct (case-sensitive) tags in the properties.
41629, 0000, "event structure for simple events cannot be reused for composite events"
// *Document: YES
// *Cause: An attempt was made to reuse an object type (event structure) for
// composite events when it is already configured for simple events.
// *Action: Drop the attribute set associated with the object and try again.
41630, 0000, "invalid value for \"%s\" attribute in the rule class properties"
// *Document: YES
// *Cause: An invalid value was specified for an attribute in the rule class
// properties.
// *Action: Correct the value and try again.
41631, 0000, "invalid text node or child element for \"%s\" element in properties"
// *Document: YES
// *Cause: An attempt was made to specify a child element or a text node
// in invalid position in the rule class properties specification.
// *Action: Correct the rule class properties and try again.
41632, 0000, "invalid value for the \"%s\" attribute"
// *Document: YES
// *Cause: An attempt was made to assign an invalid value for an attribute
// in the rule class properties.
// *Action: See the documentation.
41633, 0000, "specified rule class configuration not supported: \"%s\""
// *Document: YES
// *Cause: An attempt was made to use an unsupported configuration for the
// rule class.
// *Action: Remove the specified tag in the properties and try again.
41634, 0000, "invalid duration specification in rule properties: \"%s\""
// *Document: YES
// *Cause: Invalid value was specified for the duration attribute in the
// rule class properties.
// *Action: Correct the value and try again.
41635, 0000, "invalid unit of time used in duration specification"
// *Document: YES
// *Cause: An attempt was made to use an invalid unit of time for the
// rule class's duration specification. Valid units are :
// minutes, hours, and days.
// *Action: Correct the duration specification and try again.
41636, 0000, "invalid duration specification at the primitive event level"
// *Document: YES
// *Cause: An attempt was made to specify a duration policy for the
// primitive events when the composite event was configured with
// TRANSACTION or SESSION duration policy.
// *Action: Correct the rule class properties and try again.
41637, 0000, "missing primitive event name"
// *Document: YES
// *Cause: The name attribute of the object element in the rule class
// properties was not specified. This is a required value.
// *Action: Specify the name of the primitive event and try again.
41638, 0000, "invalid attribute for \"%s\" element in rule condition"
// *Document: YES
// *Cause: An attempt was made to specify an invalid attribute for an XML
// element in the rule condition.
// *Action: Correct the rule condition and try again.
41639, 0000, "invalid child node in \"%s\" element"
// *Document: YES
// *Cause: An attempt was made to specify an invalid child element or text
// node for an XML element in the rule condition.
// *Action: Correct the rule condition and try again.
41640, 0000, "invalid element \"%s\" in the rule condition"
// *Document: YES
// *Cause: An attempt was made to use an invalid element or a valid element
// in invalid position in the rule condition.
// *Action: Correct the rule condition and try again.
41641, 0000, "invalid or empty rule condition"
// *Document: YES
// *Cause: An attempt was made to specify an invalid or empty rule
// condition.
// *Action: Correct the input and try again.
41642, 0000, "Missing \"%s\" element in the rule condition"
// *Document: YES
// *Cause: The rule condition was specified without a required element.
// *Action: Correct the rule condition and try again.
41643, 0000, "invalid attribute for the \"%s\" element in the rule condition"
// *Document: YES
// *Cause: An attempt was made to specify an invalid attribute for an
// element in the rule condition.
// *Action: Correct the rule condition and try again.
41644, 0000, "invalid use of \"%s\" attribute in rule condition"
// *Document: YES
// *Cause: An attempt was made to specify an invalid attribute for an
// element in the rule condition.
// *Action: Correct the rule condition and try again.
41645, 0000, "duplicate tag \"%s\" in rule condition"
// *Document: YES
// *Cause: An attempt was made to specify the same XML tag in more than one
// positions within a single rule condition.
// *Action: Remove the duplicate reference to the tag and try again.
41646, 0000, "missing \"%s\" attribute for \"%s\" element in the rule condition"
// *Document: YES
// *Cause: One of the required attributes was not specified in the rule
// condition.
// *Action: Correct the rule condition and try again.
41647, 0000, "negation not allowed in rule conditions with \"any\" semantics"
// *Document: YES
// *Cause: An attempt was made to specify a \"not\" element within an
// \"any\" element in the rule condition.
// *Action: Correct the rule condition and try again.
41648, 0000, "invalid sequence of child elements in \"%s\" element"
// *Document: YES
// *Cause: An attempt was made to specify an invalid sequence of elements
// within a parent element.
// *Action: Correct the rule condition and try again.
41649, 0000, "invalid rule condition for a rule class involving composite events"
// *Document: YES
// *Cause: An attempt was made to add an invalid rule condition to a rule
// set defined for composite events.
// *Action: Correct the input and try again.
41650, 0000, "invalid composite event structure"
// *Document: YES
// *Cause: A composite event structure may only have attributes that are
// either table aliases or of an object type that is defined in the
// owner's schema.
// *Action: Ensure that the event structure has no scalar attributes and all
// the embedded types in it are defined in the owner's schema.
41651, 0000, "Event structure object type has one or more dependent objects"
// *Document: YES
// *Cause: An attempt was made to configure an object type that has one or
// more dependents as a event structure. The object type cannot be
// modified due to the dependent objects.
// *Action: Create a new object type for the event structure and try again.
41652, 0000, "invalid value for the equal attribute in the rule condition"
// *Document: YES
// *Cause: An invalid value is assigned to the equal attribute in the rule
// condition.
// *Action: Correct the input and try again.
41653, 0000, "inconsistent value for the \"count\" attribute of the \"any\" element"
// *Document: YES
// *Cause: The value specified for the \"count\" attribute of the \"any\"
// element is greater than or equal to the the number of primitive
// events appearing in the rule condition.
// *Action: Specify a smaller value for the \"any\" element's \"count\"
// attribute.
41654, 0000, "insufficient number of primitive events for the use of \"sequence\""
// *Document: YES
// *Cause: An attempt was made to use \"sequence\" attribute when there is
// an insufficient number of primitive events in the rule
// conditions.
// *Action: Remove the sequence specification.
41655, 0000, "rule condition construct not supported: %s"
// *Document: YES
// *Cause: An attempt was made to use a rule condition construct that is not
// supported in the current release.
// *Action: Modify the rule condition.
41656, 0000, "insufficient number of child elements in \"%s\" element."
// *Document: YES
// *Cause: An attempt was made to use fewer than two elements within an
// \"and\" or \"notany\" element.
// *Action: Specify at least two elements within the parent element.
41657, 0000, "rule class internal objects cannot be dropped"
// *Document: YES
// *Cause: An attempt was made to drop an internal object that is required
// for a rule class.
// *Action: Drop the rule class associated with this object.
41658, 0000, "invalid value for the \"count\" attribute in the \"any\" element"
// *Document: YES
// *Cause: An invalid value is assigned to the count attribute in the rule
// condition. The values should be a positive integer that is
// smaller than the number of object elements within the \"any\"
// element.
// *Action: Correct the input and try again.
41659, 0000, "invalid primitive event \"%s\" for the rule class"
// *Document: YES
// *Cause: An attempt was made to use an invalid primitive event in a rule
// condition.
// *Action: Correct the input and try again.
41660, 0000, "ordering property for the rule class is too long"
// *Document: YES
// *Cause: An attempt was made to configure the rule class with an ordering
// property that is longer than 240 characters.
// *Action: Correct the input and try again.
41661, 0000, "the system generated rule class package has errors"
// *Document: YES
// *Cause: An attempt was made to use a rule class configuration that was not
// supported.
// *Action: File a bug.
41662, 0000, "number of primitive events in the composite event exceeds maximum limit"
// *Document: YES
// *Cause: An attempt was made to create a composite event structure with
// more than 32 primitive events.
// *Action: Use a composite event that consists of fewer primitive events.
41663, 0000, "invalid use of \"equal\" or \"sequence\" attribute with a single event"
// *Document: YES
// *Cause: An attempt was made to use \"equal\" or \"sequence\" attribute
// when the \"count\".
// attribute in a rule condition with \"any\" semantics is set to 1.
// *Action: Remove the \"equal\" and \"sequence\" specifications.
41664, 0000, "invalid consumption policy for the primitive event"
// *Document: YES
// *Cause: An attempt was made to use EXCLUSIVE consumption policy for a
// primitive event when the composite event is configured for RULE
// consumption policy.
// *Action: Correct the rule class properties and try again.
41665, 0000, "conflicting values for duration, consumption, and autocommit policies"
// *Document: YES
// *Cause: An attempt was made to use an EXCLUSIVE consumption policy with
// no autocommit and a duration other than TRANSACTION or SESSION.
// *Action: Modify the rule class properties and try again. Autocommit should
// be set to YES when the consumption policy is EXCLUSIVE.
41666, 0000, "XML schema validation failed when validating against %s"
// *Document: YES
// *Cause: The user input has undefined element or attribute according to
// the provided XML schema definition.
// *Action: Correct the user inputs and try again.
41667, 0000, "rule class results view name already used for an existing object"
// *Document: YES
// *Cause: An attempt was made to use a duplicate name for the rule class
// results view.
// *Action: Use a different name for the rule class results view.
41668, 0000, "invalid operation for the rule class"
// *Document: YES
// *Cause: An attempt was made to use an invalid operation for the rule class.
// *Action: No action necessary. This is an informational message only.
41669, 0000, "invalid list of primitive event identifiers"
// *Document: YES
// *Cause: An attempt was made to pass an empty list of primitive event
// identifiers to the CONSUME_PRIM_EVENTS API.
// *Action: Correct the input and try again.
41670, 0000, "duplicate or invalid event name in equal specification"
// *Document: YES
// *Cause: An attempt was made to specify a duplicate or invalid
// primitive event for the rule class's equal property.
// *Action: Correct the input and try again.
41671, 0000, "duplicate table names in the event structure with table aliases"
// *Document: YES
// *Cause: The table used for an event structure has the same name as
// another table or a primitive event type in the event structure.
// *Action: Use an event structure with distinct table names for table
// aliases.
41672, 0000, "invalid rowid passed in for \"%s\" table"
// *Document: YES
// *Cause: An attempt was made to pass a NULL or invalid rowid for a table
// in the event structure.
// *Action: Correct the input and try again.
41673, 0000, "sequence attribute not allowed in rule conditions using table aliases"
// *Document: YES
// *Cause: An attempt was made to use sequence attribute in a rule condition
// that is defined using table aliases. Sequence usage is not
// permitted for the lack of timestamp attribute.
// *Action: Correct the input and try again.
41674, 0000, "dmlevents policy allowed only for event structures with table aliases"
// *Document: YES
// *Cause: An attempt was made to use the dmlevents policy for an event
// structure with no table alias constructs.
// *Action: Correct the rule class properties and try again.
41675, 0000, "schema for data tables does not match that of the rule class"
// *Document: YES
// *Cause: An attempt was made to use the dmlevents policy for a rule class
// that refers to table residing in different schema. To use the
// dmlevents policy, the table associated with table aliases in the
// event structure and the rule class should exist in the same schema.
// *Action: Remove dmlevents specification from rule class properties.
41676, 0000, "invalid use of dmlevents policy for primitive event"
// *Document: YES
// *Cause: An attempt was made to use the dmlevents policy for a primitive
// event defined with more than one table alias attribute.
// *Action: Remove the dmlevents specification from the rule class properties.
41677, 0000, "DML event trigger creation failed with %s"
// *Document: YES
// *Cause: Triggers could not be created on the data table to track DML
// events.
// *Action: Remove the dmlevents specification from the rule class properties.
41678, 0000, "conflicting values for the autocommit and dmlevents policies"
// *Document: YES
// *Cause: An attempt was made to use dmlevents policy in combination with
// autocommit set to YES. This combination is not allowed.
// *Action: Set autocommit to NO and try again.
41679, 0000, "dmlevents specification only allowed with table alias attributes"
// *Document: YES
// *Cause: An attempt was made to use the dmlevents policy for an event
// structure not containing any table alias attributes.
// *Action: Remove the dmlevents specification from the rule class properties.
41680, 0000, "Rules Manager background process %s does not exist"
// *Document: YES
// *Cause: An attempt was made to use a Scheduler process that does not
// exist.
// *Action: Execute EXFSYS.RLM$CREATE_SCHEDULER_JOBS procedure as a privileged
// user.
41681, 0000, "clean up of expired events failed"
// *Document: YES
// *Cause: The background process that cleans up the expired events failed
// for a rule class.
// *Action: Invoke EXFSYS.DBMS_RLMGR_UTL.CLEANUP_EVENTS API for the exact
// nature of the problem.
41682, 0000, "invalid rule class package"
// *Document: YES
// *Cause: An attempt was made to use a rule class package with invalid
// signature or permissions.
// *Action: Drop the rule class and recreate it.
41683, 0000, "unable to lock a rule in the rule class"
// *Document: YES
// *Cause: A rule matching the current event is locked by another session.
// *Action: Reissue the command after committing the other sessions.
41684, 0000, "invalid value for the RLM$ENABLED column"
// *Document: YES
// *Cause: An attempt was made to insert or update a value other than 'Y'
// or 'N' into the RLM$ENABLED column of a rule class table.
// *Action: Retry the DML statement with a value of 'Y' or 'N' for the
// RLM$ENABLED column.
41685, 0000, "invalid window specification for the collection element"
// *Document: YES
// *Cause: An invalid attribute value was specified for the \"windowlen\" or
// the \"windowsize\" attribute. The value specified for the \"windowlen\"
// attribute should be a number indicating the number of days or a fraction of
// a day. The value specified for the \"windowsize\" attribute should be
// an integer which indicates number of items in the collection. The maximum
// value allowed for the window specification is 64000.
// *Action: Correct the input and try again.
41686, 0000, "use of \"collection\" invalid for the primitive event"
// *Document: YES
// *Cause: An attempt was made to define a rule condition with \"collection\"
// element when the corresponding event was not configured for collections
// of events.
// *Action: Correct the rule condition and try again.
41687, 0000, "attribute \"%s\" not allowed in the \"groupby\" specification"
// *Document: YES
// *Cause: The attributes listed in the \"groupby\" specification in a rule
// condition were not a subset of the attributes specified in the rule
// class properties.
// *Action: Correct the \"groupby\" specification for the rule condition and try again.
41688, 0000, "invalid value for the \"groupby\" attribute"
// *Document: YES
// *Cause: An invalid value was specified for the \"groupby\" attribute.
// *Action: Correct the input and try again.
41689, 0000, "invalid collection specification in the rule condition"
// *Document: YES
// *Cause: An attempt was made to insert a rule condition with invalid collection
// element specification.
// *Action: Correct the input and try again.
41690, 0000, "maximum number of grouping expressions for a rule class exceeded"
// *Document: YES
// *Cause: An attempt was made to specify more than 32 expressions for the
// \"groupby\" clause in rule class properties.
// *Action: Use fewer than 32 expressions for the \"groupby\" clause.
41691, 0000, "invalid aggregate specification: %s"
// *Document: YES
// *Cause: The aggregate operation specified in the rule condition was invalid.
// *Action: Correct the input and try again.
41692, 0000, "unsupported aggregate operator in the having/compute clause: %s"
// *Document: YES
// *Cause: An attempt was made to use an unsupported aggregate operator in
// the having or the compute clause in the rule condition.
// *Action: Correct the input and try again.
41693, 0000, "invalid attribute or data type for an aggregate operator: %s"
// *Document: YES
// *Cause: An attempt was made to apply an aggregate operator on an invalid
// attribute or an attribute with invalid or unsupported data type
// in the aggregate operator. Only NUMBER and DATE attributes are
// allowed in the aggregate operators.
// *Action: Correct the input and try again.
41694, 0000, "invalid equal specification around: %s"
// *Document: YES
// *Cause: An attempt was made to specify an invalid equal clause for a rule
// condition or the rule class properties.
// *Action: Correct the input and try again.
41695, 0000, "equal specification should have a minimum of two elements"
// *Document: YES
// *Cause: An attempt was made to specify fewer than two elements in the
// equal clause for a rule condition or the rule class properties.
// *Action: Correct the input and try again.
41696, 0000, "invalid operator in the having clause: %s"
// *Document: YES
// *Cause: An attempt was made to use an invalid relational operator in the
// having clause of the rule condition.
// *Action: Correct the input and try again.
41697, 0000, "attribute prefix missing in aggregate specification: %s"
// *Document: YES
// *Cause: An attempt was made to specify an aggregate predicate across
// multiple primitive event types with no attribute prefix.
// *Action: Correct the input and try again.
41698, 0000, "invalid use of \"%s\" attribute in aggregate predicate"
// *Document: YES
// *Cause: An attempt was made to use an attribute where a literal is expected
// in the aggregate predicate in the rule condition.
// *Action: Correct the input and try again.
41699, 0000, "maximum number of aggregate operations per rule condition exceeded"
// *Document: YES
// *Cause: An attempt was made to specify more than 5 aggregate operations
// in a rule condition.
// *Action: Correct the input an try again.
41700, 0000, "a conditions table already exists for the event structure"
// *Cause: A table storing the primitive rule conditions was already
// assigned to the event structure.
// *Action: No action necessary. This is an informational message only.
41701, 0000, "conditions table with a rule class association cannot be truncated or dropped"
// *Cause: An attempt was made to truncate or drop a conditions table when
// one or more rule classes are associated to it through the event
// structure.
// *Action: Drop the rule class before truncating or dropping the conditions
// table.
41702, 0000, "invalid conditions table"
// *Cause: An attempt was made to use an invalid conditions table.
// *Action: Correct the input and try again.
41703, 0000, "invalid child node in \"object\" element with \"ref\" attribute"
// *Cause: An attempt was made to use both a condition and a \"ref\" attribute
// in the \"object\" element.
// *Action: Remove the \"ref\" attribute.
41704, 0000, "invalid condition reference: \"%s\""
// *Cause: An attempt was made to use a reference to a nonexistent
// conditions table or a condition.
// *Action: Ensure that the conditions table exists for the primitive event
// and the value specified for the \"ref\" attribute of the
// \"object\" element is valid.
41705, 0000, "conditions table cannot be dropped with DROP TABLE command"
// *Document: YES
// *Cause: An attempt was made to drop a conditions table with a DROP
// TABLE command.
// *Action: Use DBMS_RLMGR.DROP_CONDITIONS_TABLE instead.
41706, 0000, "a condition referenced in rule conditions may not be deleted"
// *Cause: An attempt was made to delete a condition when one or more rule
// conditions refer to it.
// *Action: Delete the rules before deleting the conditions.
41707, 0000, "unsupported construct with collection events: \"%s\""
// *Cause: An attempt was made to define a collection rule condition
// with unsupported constructs.
// *Action: Correct the input and try again.
41708, 0000, "the identifier for the shared condition may not be modified"
// *Cause: An attempt was made to update the identifier of a row
// stored in the conditions table.
// *Action: Insert a row with the new identifier instead.
41710, 0000, "invalid use of aggregate operator for a noncollection event"
// *Document: YES
// *Cause: An attempt was made to specify an aggregate operator on an
// event that is not identified as collection.
// *Action: Correct the input and try again.
41711, 0000, "invalid attribute in the rule condition's having clause"
// *Document: YES
// *Cause: An invalid attribute is used in the specification for the
// having clause of the rule condition.
// *Action: Correct the input and try again.
41712, 0000, "missing groupby specification for the collection \"%s\""
// *Document: YES
// *Cause: An attempt was made to use a collection element with no groupby
// specification in the rule condition.
// *Action: Correct the input and try again.
41713, 0000, "invalid use of \"windowlen\" and \"windowsize\" attributes"
// *Document: YES
// *Cause: An attempt was made to use the windowlen and windowsize attributes
// within the same collection element.
// *Action: Correct the input and try again.
41714, 0000, "invalid use of window specification with SESSION/TRANSACTION duration"
// *Document: YES
// *Cause: An attempt was made to use the windowlen or windowsize attributes
// when the events are configured for SESSION or TRANSACTION duration.
// *Action: Remove the window specification and try again.
41721, 0000, "invalid use of DMLEVENTS and CNFEVENTS in rule class properties"
// *Document: YES
// *Cause: An attempt was made to specify both the DMLEVENTS and CNFEVENTS
// for the same rule class.
// *Action: Remove either the DMLEVENTS or the CNFEVENTS specification.
41722, 0000, "insufficient privileges for database change notification"
// *Document: YES
// *Cause: An attempt was made to use CNFEVENTS property with insufficient
// privileges.
// *Action: Grant CHANGE NOTIFICATION privilege and EXECUTE privilege on
// DBMS_CHANGE_NOTIFICATION to the user and try again.
/////////////////////////////////////////////////////////////////////////////
// Reserving 42000 - 42249 for Online Redefinition error codes.
/////////////////////////////////////////////////////////////////////////////
42000, 0000, "invalid online redefinition column mapping for table \"%s\".\"%s\""
// *Document: YES
// *Cause: An attempt was made to change the logical structure of a
// materialized view log, queue table, or a partition
// by specifying a non-NULL column mapping during online
// redefinition.
// *Action: Pass a NULL column mapping parameter.
42002, 0000, "partition \"%s\" of table \"%s\".\"%s\" not being redefined"
// *Document: YES
// *Cause: An attempt was made to redefine a partition which is not
// involved in this redefinition.
// *Action: Pass a valid partition name.
42003, 0000, "partition must be specified for this redefinition"
// *Document: YES
// *Cause: A partition was involved in this redefinition but was
// not specified.
// *Action: Specify the partition involved in this redefinition.
42004, 0000, "redefinition not instantiated"
// *Document: YES
// *Cause: An attempt was made to complete an instantiation-deferred
// redefinition without invoking
// dbms_redefinition.sync_interim_table.
// *Action: Invoke dbms_redefinition.sync_interm_table to instantiate this
// redefinition.
42005, 0000, "invalid type of redefinition method"
// *Document: YES
// *Cause: An unknown redefinition method was used.
// *Action: Use one of the supported redefinition methods:
// o dbms_redefinition.cons_use_pk
// o dbms_redefinition.cons_use_rowid
42006, 0000, "dependent object registration not supported during a partition redefinition"
// *Document: YES
// *Cause: An attempt was made to register dependent objects when redefining
// a partition.
// *Action: Do not invoke dbms_redefinition.register_dependent_object during
// a partition redefinition.
42007, 0000, "dependent object unregistration not supported during a partition redefinition"
// *Document: YES
// *Cause: An attempt was made to unregister dependent objects when
// redefining a partition.
// *Action: Do not invoke dbms_redefinition.unregister_dependent_object
// during a partition redefinition.
42008, 0000, "error occurred while instantiating the redefinition"
// *Document: YES
// *Cause: An error occurred while instantiating the online redefinition
// which requires aborting the redefinition.
// *Action: Correct the error, abort, and restart the online redefinition.
42009, 0000, "error occurred while synchronizing the redefinition"
// *Document: YES
// *Cause: An error occurred while synchronizing the online redefinition.
// *Action: Correct the error and continue the online redefinition.
42010, 0000, "error occurred while synchronizing the redefinition"
// *Document: YES
// *Cause: An error occurred while synchronizing the online redefinition
// which requires aborting the redefinition.
// *Action: Correct the error, abort, and restart the online redefinition.
42011, 0000, "error occurred while completing the redefinition"
// *Document: YES
// *Cause: An error occurred while completing the online redefinition.
// *Action: Correct the error and continue the online redefinition.
42012, 0000, "error occurred while completing the redefinition"
// *Document: YES
// *Cause: An error occurred while completing the online redefinition
// which requires aborting the redefinition.
// *Action: Correct the error, abort, and restart the online redefinition.
42013, 0000, "interim table of an AQ IOT table should be an IOT table"
// *Document: YES
// *Cause: An attempt was made to create a table that is not
// an index-organized table (IOT) as the interim table
// of an AQ IOT table (history, time management, or dequeue).
// *Action: Ensure that the interim table is created as an IOT table.
42014, 0000, "online redefinition unable to lock AQ objects"
// *Document: YES
// *Cause: An online redefinition of an AQ table was unable to lock
// all related AQ objects.
// *Action: Abort and retry the redefinition.
42015, 0000, "online redefinition unable to log changes made to AQ tables"
// *Document: YES
// *Cause: An online redefinition of an AQ table was unable to
// log changes made to AQ tables during the redefinition.
// *Action: Abort and retry the redefinition.
42016, 0000, "shape of interim table does not match specified column mapping"
// *Cause: The number of columns, or the type or the length semantics of a
// column, in the interim table did not match the specified
// column mapping.
// *Action: Ensure that the interim table matches the column mapping by
// either modifying the column mapping string or altering the
// interim table's column definition(s).
42017, 0000, "interim table of an AQ table should not be an AQ table"
// *Document: YES
// *Cause: An attempt was made to create an AQ table as an interim
// table of an online redefined AQ table.
// *Action: Ensure that the interim table is not created as an AQ table.
42018, 0000, "partition cannot be redefined online because of index organization incompatibility"
// *Document: YES
// *Cause: interim table is incompatible with partition being redefined
// because one or more of the following apply:
// - one is index-organized and the other is not
// - one has IOT overflow segment and the other does not
// - one has IOT mapping table and the other does not
// *Action: Ensure that the interim table is compatible with the partition
// being redefined.
42019, 0000, "partition cannot be redefined online because of incompatible partitioning of interim table"
// *Document: YES
// *Cause: both original and interim tables are partitioned, or original
// table is composite-partitioned but interim table is
// non-partitioned.
// *Action: Ensure that the interim table has compatible partitioning with
// the original table. For example, if the original table is
// partitioned, the interim table should be non-partitioned. If the
// original table is composite-partitioned, the interim table
// should be partitioned.
42020, 0000, "partition cannot be redefined online because of unsupported type of interim table"
// *Document: YES
// *Cause: An unsupported type of interim table was provided during the
// partition redefinition. Currently the following types of interim
// tables are not supported:
// - a nested table or has nested-table columns
// - an external table
// - part of cluster
// - contains LOB shared segments
// *Action: Do not use unsupported types of interim tables.
42021, 0000, "partition cannot be redefined online because of incompatible row dependencies"
// *Document: YES
// *Cause: original/interim table was created with row dependency and
// interim/original table was not.
// *Action: Ensure that both tables are created with same row dependency
// properties.
42022, 0000, "partition cannot be redefined online because of presence of nested columns"
// *Document: YES
// *Cause: An attempt was made to online redefine a partition with nested
// table columns.
// *Action: Do not attempt to online redefine a partition with nested
// table columns.
42023,0000, "compatibility of AQ table must be release 8.1.x or later"
// *Cause: An attempt was made to perform online redefinition on an
// AQ table that was created with compatibility prior to release 8.1.x.
// *Action: Ensure that the AQ table is created with the COMPATIBLE parameter
// set to release 8.1.x or later before attempting online redefinition.
42024,0000, "interim table of an AQ table can not be a partitioned table"
// *Cause: An attempt was made to use a partitioned table as an interim table.
// *Action: Ensure that the interim table is not a partitioned table.
42025,0000, "redefinition of CONS_USE_ROWID method cannot be used to redefine an AQ IOT table"
// *Cause: An attempt was made to use method of DBMS_REDEFINITION.CONS_USE_ROWID
// to redefine an AQ IOT table.
// *Action: Ensure that method of DBMS_REDEFINITION.CONS_USE_PK is used to
// redefine an AQ IOT table.
42026,0000,"duplicated rows detected while instantiating the redefinition"
// *Cause: Duplicated rows are detected during instantiation of the redefinition.
// *Action: Abort the redefinition, turn off the optimistic ascending SCN
// optimization, and restart the redefinition.
42027,0000,"cannot redefine an object online that is not a table"
// *Cause: An attempt was made to redefine an object online that is not a table.
// *Action: Ensure that the object being redefined online is a table.
42028,0000,"materialized view log \"%s\".\"%s\" does not exist"
// *Cause: An attempt was made to register a nonexistent
// materialized view log as a dependent object.
// *Action: Invoke DBMS_REDEFINITION.REGISTER_DEPENDENT_OBJECT on a
// valid materialized view log.
42029, 00000, "cannot online redefine table \"%s\".\"%s\" at this time"
// *Cause: An attempt was made to redefine a table which is incompatible
// with another ongoing redefinition.
// *Action: Do not perform the redefinition operation on this table or wait
// until the incompatible ongoing redefinition has completed.
//
42030, 00000, "cannot online redefine table \"%s\".\"%s\" with commit SCN-based MV log"
// *Cause: An attempt was made to redefine a table which had a commit
// SCN-based materialzed view log defined on it.
// *Action: Do not attempt to online redefine a table that has a commit
// SCN-based materialzed view log defined on it.
//
42031, 00000, "interim table cannot have a commit SCN-based MV log defined on it"
// *Cause: An attempt was made to use an interim table which had a commit
// SCN-based materialzed view log defined on it.
// *Action: Ensure that the interim table does not have a commit
// SCN-based materialzed view log defined on it.
//
42032, 00000, "cannot online redefine table \"%s\".\"%s\" with Flashback Data Archive enabled"
// *Cause: An attempt was made to redefine a table which had Flashback Data
// Archive enabled.
// *Action: Do not attempt to online redefine a table that has Flashback Data
// Archive enabled.
//
42033, 00000, "interim table \"%s\".\"%s\" cannot have Flashback Data Archive enabled"
// *Cause: An attempt was made to redefine a table with an interim table
// which had Flashback Data Archive enabled.
// *Action: Do not attempt to online redefine a table with an interim table
// which has Flashback Data Archive enabled.
//
42034, 00000, "cannot online redefine table \"%s\".\"%s\" which is a CDC table"
// *Cause: An attempt was made to redefine a table which is a CDC table.
// *Action: Do not attempt to online redefine a table that is a CDC table.
//
42035, 00000, "cannot online redefine IOT table \"%s\".\"%s\" with CONS_USE_ROWID"
// *Cause: An attempt was made to redefine an IOT table with CONS_USE_ROWID.
// *Action: Do not attempt to online redefine an IOT table with CONS_USE_ROWID.
//
42036, 00000, "cannot online redefine temporary table \"%s\".\"%s\""
// *Cause: An attempt was made to redefine a temporary table.
// *Action: Do not attempt to online redefine a temporary table.
//
42037, 00000, "cannot online redefine table \"%s\".\"%s\" with IOT overflow segment"
// *Cause: An attempt was made to redefine a table with IOT overflow segment.
// *Action: Do not attempt to online redefine a table with IOT overflow segment.
//
42038, 00000, "cannot online redefine table \"%s\".\"%s\" with a CDC log defined on it"
// *Cause: An attempt was made to redefine a table with a CDC log defined
// on it.
// *Action: Do not attempt to online redefine a table with a CDC log defined on
// it.
//
42039, 00000, "cannot online redefine table \"%s\".\"%s\" with FGA enabled"
// *Cause: An attempt was made to redefine a table with Fine Grained Auditing
// (FGA) or Row Level Security (RLS) enabled.
// *Action: Do not attempt to online redefine a table with Fine Grained Auditing
// (FGA) or Row Level Security (RLS) enabled.
//
42040, 00000, "cannot online redefine table \"%s\".\"%s\" with column of binary XML type"
// *Cause: An attempt was made to redefine a table with a column of binary XML
// type.
// *Action: Do not attempt to online redefine a table with a column of binary
// XML type.
//
42041, 00000, "cannot online redefine table \"%s\".\"%s\" with nested table columns"
// *Cause: An attempt was made to redefine a table with nested table columns.
// *Action: Do not attempt to online redefine a table with nested table columns.
//
42042, 00000, "time out in acquiring DML lock during online redefinition"
// *Cause: During FINISH_REDEF_TABLE procedure, the elapsed time waiting to
// acquire a table or partition DML lock on the original table exceeds
// the timeout the user specified.
// *Action: Rerun FINISH_REDEF_TABLE procedure to continue the process.
//
42043, 00000, "CONS_VPD_AUTO is only applicable to null column mapping"
// *Cause: An attempt was made to specify CONS_VPD_AUTO for non-null
// column mapping other than null column mapping. CONS_VPD_AUTO
// can only be specified for null column mapping.
// *Action: Set the COPY_VPD_OPT value to CONS_VPD_MANUAL.
//
42044, 00000, "cannot redefine table with non-null VPD policy predicate against the table owner or redefinition invoker"
// *Cause: Virtual Private Database (VPD) policies with non-null predicate
// against the table owner or redefinition invoker existed on the
// original table.
// *Action: Drop the VPD policies with non-null predicate against the table
// owner or redefinition invoker. Restart online redefinition.
//
42045, 00000, "COPY_VPD_OPT cannot be set to CONS_VPD_NONE with VPD policies on table \"%s\".\"%s\"."
// *Cause: An attempt was made to set the COPY_VPD_OPT value to CONS_VPD_NONE.
// COPY_VPD_OPT cannot be set to CONS_VPD_NONE with Virtual Private
// Database (VPD) policies on the original table.
// *Action: Set COPY_VPD_OPT to CONS_VPD_AUTO or CONS_VPD_MANUAL.
//
42046, 00000, "COPY_VPD_OPT cannot be set to %s with VPD policies on interim table \"%s\".\"%s\"."
// *Cause: An attempt was made to set the COPY_VPD_OPT value to either
// CONS_VPD_NONE or CONS_VPD_AUTO. Cannot set the COPY_VPD_OPT value
// to CONS_VPD_NONE or CONS_VPD_AUTO with Virtual Private Database
// (VPD) policies on the interim table.
// *Action: Set the COPY_VPD_OPT value to CONS_VPD_MANUAL.
//
42047, 00000, "The specified value for COPY_VPD_OPT is invalid."
// *Cause: An unknown COPY_VPD_OPT value was used.
// *Action: Use one of the supported COPY_VPD_OPT values:
// o DBMS_REDEFINITION.CONS_VPD_NONE
// o DBMS_REDEFINITION.CONS_VPD_AUTO
// o DBMS_REDEFINITION.CONS_VPD_MANUAL
//
42048, 00000, "Automatic copying of VPD policies with application context is not supported in online redefinition."
// *Cause: An attempt was made to set the COPY_VPD_OPT value to CONS_VPD_AUTO
// for Virtual Private Database (VPD) policies with application
// context. Automatic copying of VPD policies with application context
// is not supported in online redefinition.
// *Action: Drop VPD policies with application context or set the COPY_VPD_OPT
// value to CONS_VPD_MANUAL.
//
42049, 00000, "cannot online redefine multiple tables and multiple partitions"
// *Cause: An online redefinition procedure was passed multiple original tables
// and multiple partitions to redefine.
// *Action: Do not attempt to online redefine multiple tables at the same time
// as multiple partitions.
42050, 00000, "COPY_VPD_OPT cannot be set to CONS_VPD_MANUAL when redefining a partition."
// *Cause: An attempt was made to set the COPY_VPD_OPT value to
// CONS_VPD_MANUAL. COPY_VPD_OPT cannot be set to CONS_VPD_MANUAL
// when redefining a partition.
// *Action: Set COPY_VPD_OPT to CONS_VPD_NONE or CONS_VPD_AUTO.
//
42051, 00000, "duplicate partition names in partition name list"
// *Cause: An online redefinition procedure was passed a partition name
// list containing duplicates.
// *Action: Ensure that all names in the partition name list are unique.
//
42052, 00000, "interim table cannot have materialized view or zonemap defined on it"
// *Cause: An attempt was made to redefine a table with an interim table on
// which a materialized view or zonemap was defined.
// *Action: Remove all materialized views and zonemaps defined on the interim
// table and retry online redefinition, or do not attempt online
// redefinition.
//
42053, 00000, "cannot online redefine table \"%s\".\"%s\" with OLS/XDS enabled"
// *Cause: An attempt was made to redefine a table with Oracle Label Security
// (OLS) or Extensible Data Security (XDS) enabled.
// *Action: Do not attempt to online redefine a table with Oracle Label Security
// (OLS) or Extensible Data Security (XDS) enabled.
//
42054, 00000, "cannot online redefine table \"%s\".\"%s\" with UXI XML index"
// *Cause: An attempt was made to redefine a table with XML indexes having
// an Unstructured XMLIndex (UXI) component.
// *Action: Do not attempt to online redefine a table with XML indexes having
// an Unstructured XMLIndex (UXI) component.
//
42055, 00000, "general event for online redefinition"
// *Document: NO
// *Cause: N/A
// *Action: This internal event is used to enable various actions
// associated with online redefinition. The event level
// is interpreted as a bitmap of actions to enable.
//
// *Comment: Not for general purpose use.
42056, 00000, "interim table cannot be a system-partitioned table"
// *Cause: An attempt was made to redefine a table with an interim table
// that was a system-partitioned table.
// *Action: Use an interim table whose partition type is supported.
//
42057, 00000, "cannot use lock free finish redef for current redefinition"
// *Cause: An attempt was made to enable lock free finish redef for
// current redefinition, but lock free was not feasible.
// *Action: Refer to the documentation for restrictions.
//
42058, 00000, "unsupported UPDATE statement"
// *Cause: The UPDATE statement passed to DBMS_REDEFINITION.EXECUTE_UPDATE
// was not supported.
// *Action: Refer to the documentation for restrictions and supported types.
//
42059, 00000, "cannot update a table with a DML trigger on UPDATE"
// *Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE
// method attempted to update a table with a trigger on UPDATE,
// which is not supported.
// *Action: Drop the DML trigger.
//
42060, 00000, "cannot update a table with a nested table column"
// *Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE
// method attempted to update a table with a nested table column,
// which is not supported.
// *Action: Refer to the documentation for restrictions.
//
42061, 00000, "cannot update a typed table or a table with an ADT column"
// *Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE
// method attempted to update a typed table or a table with an ADT
// column, which is not supported.
// *Action: Refer to the documentation for restrictions.
//
42062, 00000, "cannot update a table with a partition extended name"
// *Cause: An attempt was made to pass an UPDATE statement with a partition
// extended name to the DBMS_REDEFINITION.EXECUTE_UPDATE method, which
// is not supported.
// *Action: Refer to the documentation for restrictions.
//
42063, 00000, "DBMS_REDEFINITION.EXECUTE_UPDATE diagnostics event"
// *Document: NO
// *Cause:
// *Action: Internal use only.
//
42064, 00000, "invalid UPDATE statement %s"
// *Cause: An attempt was made to pass an invalid UPDATE statement
// to the DBMS_REDEFINITION.EXECUTE_UPDATE method.
// *Action: Pass a valid UPDATE statement to the
// DBMS_REDEFINITION.EXECUTE_UPDATE method.
//
42065, 00000, "REDEF_TABLE() does not support redefining AQ table"
// *Cause: An attempt was made to redefine an Advanced Queueing (AQ) table
// with the REDEF_TABLE() procedure.
// *Action: Do not attempt to redefine an AQ table using REDEF_TABLE().
//
42066, 00000, "illegal redefinition for a clustered table"
// *Cause: An attempt was made to redefine a clustered table to modify
// the tablespace or compression type with the REDEF_TABLE()
// procedure.
// *Action: Do not attempt to specify a new tablespace or compression type.
//
42067, 00000, "invalid column mapping with invisible columns on original or interim table"
// *Cause: There was an invalid column mapping with invisible columns on the original
// or interim table.
// *Action: Invisible columns in the column mapping string must be
// invisible on both the original and interim table.
//
42068, 00000, "rollback unsupported with COPY_VPD_OPT option"
// *Cause: ENABLE_ROLLBACK and COPY_VPD_OPT were both set to TRUE.
// *Action: Either unset ENABLE_ROLLBACK or COPY_VPD_OPT.
//
42069, 00000, "rollback unsupported"
// *Cause: Tables in the redefinition are either an object, advanced queue or
// index-organized table.
// *Action: Currently ROLLBACK is unsupported on such tables.
//
42070, 00000, "wrong usage of DBMS_REDEFINITION.ROLLBACK"
// *Cause: ENABLE_ROLLBACK was not set to TRUE during START_REDEF_TABLE.
// *Action: Restart START_REDEF_TABLE with ENABLE_ROLLBACK set to TRUE and then
// use ROLLBACK.
//
42071, 00000, "rollback unsupported with NO-DML lock option"
// *Cause: ENABLE_ROLLBACK was set to TRUE along with DML_LOCK_TIMEOUT
// set to -1.
// *Action: Either unset ENABLE_ROLLBACK or DML_LOCK_TIMEOUT.
//
42072, 00000, "REDEF_TABLE() does not support a table with LONG column."
// *Cause: An attempt was made to redefine a table that has a LONG column
// with the REDEF_TABLE() procedure.
// *Action: Do not attempt to redefine a table with LONG column using
// REDEF_TABLE().
//
42073, 00000, "cannot online redefine external table or fixed table"
// *Cause: An attempt was made to redefine an external table or a fixed table.
// *Action: Do not attempt to online redefine an external table or a fixed
// table.
//
42074, 00000, "Cannot update a table with VPD policy"
// *Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE
// method attempted to update a table with Virtual Private Database
// (VPD) policy.
// *Action: Refer to the documentation for restrictions.
//
42075, 00000, "wrong usage of parameter, DISABLE_ROLLBACK in FINISH_REDEF_TABLE"
// *Cause: ENABLE_ROLLBACK was not set to TRUE during START_REDEF_TABLE.
// *Action: Rerun FINISH_REDEF_TABLE with DISABLE_ROLLBACK set to FALSE.
//
42076, 00000, "DBMS_REDEFINITION does not support a table on single table hash clusters."
// *Cause: An attempt was made to use DBMS_REDEFINITION on a table on single
// table hash clusters.
// *Action: Do not attempt to use DBMS_REDEFINITION to operate on a table that
// is on single table hash clusters.
//
42077, 00000, "unsupported column type found in VPD protected object"
// *Cause: An attempt was made with Oracle Virtual Private Database (VPD)
// policy to enforce column security on a column with unsupported
// operator type.
// *Action: Refer to the documentation for restrictions.
//
42078, 00000, "DBMS_REDEFINITION does not support a clustered table without cluster index or with virtual cluster index"
// *Cause: An attempt was made to use the DBMS_REDEFINITION package on a clustered table
// without a cluster index or with a virtual cluster index.
// *Action: Create a regular cluster index and rerun the DBMS_REDEFINITION procedure.
//
42079, 00000, "wrong usage of DBMS_REDEFINITION.FINISH_REDEF_TABLE"
// *Cause: Rollback was initiated as part of the previous call to
// FINISH_REDEF_TABLE.
// *Action: Use ROLLBACK or ABORT_ROLLBACK to end redefinition.
//
42080, 00000, "wrong usage of DBMS_REDEFINITION.ABORT_ROLLBACK"
// *Cause: ABORT_ROLLBACK was called without starting the rollback operation.
// *Action: Use ABORT_REDEF_TABLE instead of ABORT_ROLLBACK.
//
42081, 00000, "wrong usage of DBMS_REDEFINITION.ABORT_REDEF_TABLE"
// *Cause: ABORT_REDEF_TABLE was called when ROLLBACK was active.
// *Action: Use ABORT_ROLLBACK instead of ABORT_REDEF_TABLE.
//
42082, 00000, "cannot update a table with a hidden column"
// *Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE
// method attempted to update a table with a hidden column, which is
// not supported.
// *Action: Refer to the documentation for restrictions.
//
42083, 00000, "cannot online redefine table \"%s\".\"%s\" with staging log"
// *Cause: An attempt was made to redefine a table that had a staging log.
// *Action: Do not attempt to online redefine a table that has a staging log.
//
42084, 00000, "cannot online redefine table that has inconsistent sharing with interim table"
// *Cause: An attempt was made to redefine a table that had inconsistent
// sharing with an interim table.
// *Action: Do not attempt to online redefine a table that has inconsistent
// sharing with an interim table, ensure that there is consistent
// sharing.
//
42086, 00000, "cannot enable ROLLBACK on a table with row movement enabled"
// *Cause: An attempt was made to enable ROLLBACK on a table with row movement
// enabled in the redefinition.
// *Action: Currently, ROLLBACK is unsupported on such tables.
//
42087, 00000, "cannot enable ROLLBACK on a nested table"
// *Cause: An attempt was made to enable ROLLBACK on a nested table.
// *Action: Currently, ROLLBACK is unsupported on such tables.
//
42088, 00000, "cannot enable ROLLBACK on a clustered table"
// *Cause: An attempt was made to enable ROLLBACK on a clustered table.
// *Action: Currently, ROLLBACK is unsupported on such tables.
//
42089, 00000, "ROLLBACK unsupported with specified column mapping string"
// *Cause: The specified column mapping string included an identity column.
// *Action: ROLLBACK is unsupported with column mapping string.
//
42090, 00000, "cannot use EXECUTE_UPDATE when the statement contains ROWID"
// *Cause: An attempt was made to use EXECUTE_UPDATE when the update statement
// contained ROWID.
// *Action: Execute the update statement directly.
//
42091, 00000, "shape of interim table does not match original table"
// *Cause: An attempt was made to online redef a table when either the original
// table or the interim table did not have ROW ARCHIVAL.
// *Action: Remove ROW ARCHIVAL from the tables or add it to both tables.
/////////////////////////////////////////////////////////////////////////////
// Reserving 42280 - 42299 for RENAME SCHEMA
/////////////////////////////////////////////////////////////////////////////
42287, 00000, "cannot rename user on whose type a table depends"
// *Cause: An attempt was made to rename a user whose schema contained
// a type on which some table depends. The operation may not
// proceed as it would render the table invalid causing loss of data.
// *Action: Drop table(s) dependent on types belonging to the schema of the
// user being renamed.
42288,0000,"may not create a schema synonym for the specified schema"
//* Cause: An attempt was made to create a schema synonym for one of
// the reserved schemas (such as SYS or SYSTEM.)
//* Action: Schema synonyms for this schema may not be created.
42289,0000,"may not rename specified user"
//* Cause: An attempt was made to rename one of the following:
// - reserved user (such as SYS or SYSTEM)
// - an administrative user
// - a common user
// - a locked user account
//* Action: This user may not be renamed.
42290,0000,"specified schema does not exist"
//* Cause: An attempt was made to create a schema synonym for a schema
// which did not exist.
// *Action: Correct the input and try again.
42291, 00000, "schema synonym '%s' does not exist"
// *Cause: The named schema synonym did not exist.
// *Action: Verify you are using the correct schema synonym name.
42292, 00000, "RENAME TO already specified"
// *Cause: The RENAME TO clause was specified twice.
// *Action: Use only one RENAME TO clause.
42293, 00000, "user name conflicts with another user, role or schema synonym name"
// *Cause: There was already a user, role or schema synonym with that name.
// *Action: Specify a different user name.
42294, 00000, "role name conflicts with another user, role or schema synonym name"
// *Cause: There was already a user, role or schema synonym with that name.
// *Action: Specify a different role name.
42295, 00000, "schema synonym name conflicts with another user, role or schema synonym name"
// *Cause: There was already a user, role or schema synonym with that name.
// *Action: Specify a different schema synonym name or use CREATE OR REPLACE
// SCHEMA SYNONYM.
42296, 00000, "user, role or schema synonym '%s' does not exist"
// *Cause: There was no user, role, or schema synonym by that name.
// *Action: Respecify the name.
42297, 00000, "cannot drop a schema synonym for a schema of a user who is currently connected"
// *Cause: An attempt was made to drop a schema synonym for a schema of
// a user who was logged on.
// *Action: Make sure user is logged off, then repeat command.
42298, 00000, "cannot rename a user that is currently connected"
// *Cause: An attempt was made to rename a user that was logged on.
// *Action: Make sure user is logged off, then repeat command.
//
/////////////////////////////////////////////////////////////////////////////
// Reserving 42300 - 42398 for Editioning Views.
/////////////////////////////////////////////////////////////////////////////
42300,0000,"an Editioning view is already defined on this table"
//* Cause: An attempt was made to create an Editioning view on a table on
// which another Editioning view is already defined in the same
// Edition. This violates a restriction that at most one
// Editioning view may be associated with any base table in a given
// Edition.
//* Action: Create the new view as a regular view or, if the view being
// created is really intended to be an Editioning view associated
// with this table, drop the existing Editioning view before creating
// the new one.
42301,0000,"definition of an Editioning view may not refer to a synonym"
//* Cause: An attempt was made to create an Editioning view referring to a
// synonym, which is not supported.
//* Action: Do not create an Editioning view if you want the view to refer to a
// synonym.
42302,0000,"definition of an Editioning view may not refer to remote tables"
//* Cause: An attempt was made to create an Editioning view referring to
// remote tables, which is not supported.
//* Action: Do not create an Editioning view if you want the view to refer to a
// remote table.
42303,0000,"duplicate column reference in a definition of an Editioning view"
//* Cause: An attempt was made create an Editioning view referencing the same
// column of a base table more than once, which is not supported.
//* Action: Do not create an Editioning view if you have multiple columns
// referring to the same column of the base table.
42304,0000,"base table and the Editioning view must belong to the same schema"
//* Cause: An attempt was made to create an Editioning view in a schema
// different from that of the base table.
//* Action: Create an Editioning view in the same schema as the base table.
42305,0000,"only an Editioning view may replace an Editioning view"
//* Cause: An attempt was made to replace an Editioning view with a view
// which is not an Editioning view or vice versa.
//* Action: Ensure that either both or neither of the views involved are
// Editioning views.
42306,0000,"a CrossEdition trigger may not be created on an Editioning view"
//* Cause: An attempt was made to create a CrossEdition trigger on an
// Editioning view, which is not supported.
//* Action: Instead of creating a CrossEdition trigger on an Editioning view,
// create it on the Editioning view's underlying table.
42307,0000,"columns of an Editioning view may only refer to base table columns"
//* Cause: An attempt was made to define an Editioning view containing a
// column referring to an entity other than a base table column
// (for example, a PL/SQL function without a parameter), which is not
// supported.
//* Action: Ensure that every column of an Editioning view refers to a column
// of a base table.
42308,0000,"view %s.%s is already in read-only mode"
//* Cause: An attempt was made to set a read-only table in read-only mode.
//* Action: This DDL can only be executed on a read/write view.
42309,0000,"view %s.%s is already in read/write mode"
// *Cause: An attempt was made to set a read/write view in read/write mode.
// *Action: This DDL can only be executed on a read-only view.
42310,0000,"Implementation restriction: this operation is only permitted on Editioning views"
//* Cause: The view being altered was not an Editioning view. In this
// release, an ALTER VIEW READ ONLY, or ALTER VIEW READ WRITE
// operation is only permitted on Editioning views.
//* Action: Ensure that the view is an Editioning view.
42311,0000,"This operation is not permitted on Editioning views with compilation errors"
//* Cause: ALTER VIEW READ ONLY and ALTER VIEW READ WRITE are not permitted on
// Editioning views which have compilation errors.
//* Action: Resolve the compilation errors.
/
/ do NOT translate or document message 42312 - it is for internal use only
// NLS_DO_NOT_TRANSLATE [42312,42312]
42312, 00000, "Editioning View hints."
// *Document: NO
// *Cause: Internal use only.
// *Action: None.
42313,0000,"This operation is not supported on Editioning views marked invalid"
//* Cause: ALTER VIEW READ ONLY and ALTER VIEW READ WRITE are not permitted on
// Editioning views which are marked invalid.
//* Action: Recompile the Editioning view to ensure that it is valid.
42314, 00000, "editioning view cannot be owned by a non-editioned user"
// *Cause: An attempt was made to create an editioning view in a
// schema where views were not editionable.
// *Action: Enable editions for the user for views and then create the
// editioning view.
//
42399,0000,"cannot perform a DML operation on a read-only view"
//* Cause: An attempt was made to insert, delete, or update row(s) of a
// view created with read-only option. DML operations on such views
// are explicitly prohibited.
//* Action: Perform the desired DML operation on the view's underlying base
// table or issue ALTER VIEW ... READ WRITE command to make the
// view updatable.
/////////////////////////////////////////////////////////////////////////////
// 42800 - 42899 RESERVED FOR ROW LEVEL SECURITY (CONTINUED FROM 28100-28149)
/////////////////////////////////////////////////////////////////////////////
//
42800, 00000, "The specified attribute association (\"%s\", \"%s\") is already attached to existing shared context-sensitive policies with the specified policy function %s.%s."
// *Cause: An attempt was made to add an attribute association which was
// already attached to shared context-sensitive policies with
// the specified policy function. All shared context-sensitive policies
// with a common policy function need to have the same set of attribute
// associations. Attribute associations of an existing shared
// context-sensitive policy which is using the specified policy
// function will be automatically added to the new policy.
// *Action: Retry the operation without specifying the attribute association.
//
42801, 00000, "Value is not set for context attribute (\"%s\", \"%s\") which is associated with the Row Level Security (RLS) policy \"%s\"."
// *Cause: The value was not set for every attribute association of the shared
// context-sensitive policy. The value must be set for every attribute
// association of the shared context-sensitive policy.
// *Action: Set the value for the context attribute and retry the operation.
//
42802, 00000, "Could not read attribute associations from an existing shared context-sensitive policy which is using the specified policy function."
// *Cause: An existing shared context-sensitive policy using the specified
// policy function was dropped from another session.
// *Action: Re-issue the command.
42803, 00000, "Cannot use bind variable in VERSIONS clause when the object has a Row-Level Security (RLS) policy defined on it."
// *Cause: The object being accessed had a Row-Level Security (RLS) policy
// defined on it and the VERSIONS clause contained a bind variable.
// *Action: Rewrite the query without the use of bind variable in the VERSIONS
// clause.
42804, 00000, "The query could disclose rows protected by select VPD policy."
// *Cause: The object being accessed had a select Virtual Private Database (VPD)
// policy defined on it and the DML which is executed could disclose
// rows protected by the select VPD policy.
// *Action: Define VPD policy with the specific statement type.
42805, 00000, "The number of VPD policies on an object exceed the maximum number that is allowed."
// *Cause: A maximum of 255 Virtual Private Database (VPD) policies that can be enforced on an object was exceeded.
// *Action: Drop an existing policy before creating a new policy.
/////////////////////////////////////////////////////////////////////////////
// 42900 - 42999 RESERVED FOR LABEL SECURITY (CONTINUED FROM 12400-12499)
/////////////////////////////////////////////////////////////////////////////
//
42900, 00000, "OLS policy creation not allowed in application root."
// *Cause: Oracle Label Security (OLS) policy creation was attempted in
// application root.
// *Action: Switch to an application pluggable database to create an OLS policy.
//
42901, 00000, "Cannot apply OLS policy on common or application objects."
// *Cause: An attempt was made to enforce Oracle Label Security (OLS) policy
// on common or application objects.
// *Action: Apply OLS policy on local objects only.
//
42902, 00000, "cannot use virtual column as OLS policy column"
// *Cause: An attempt was made to use the virtual column as an Oracle Label
// Security (OLS) policy column.
// *Action: Use another column or update the user table.
//
42903, 00000, "Cannot assign OLS authorizations to common or application users."
// *Cause: An attempt was made to assign Oracle Label Security (OLS)
// authorizations to common or application users.
// *Action: Assign OLS authorizations to local users only.
//
42904, 00000, "full table access is restricted by Oracle Label Security"
// *Cause: The user did not have permission to bypass reads for Oracle Label
// Security policies.
// *Action: Grant appropriate privileges, or change the policy configurations.
//
42905, 00000, "Oracle Label Security is not supported for an external table."
// *Cause: An attempt was made to enforce Oracle Label Security (OLS) policy
// to external tables.
// *Action: OLS is not supported for external tables.
//
42906, 00000, "Cannot assign a non-existing OLS data label as row label."
// *Cause: An attempt was made to assign a non-existing Oracle Label Security
// (OLS) data label as a row label in an OLS-OID configuration.
// *Action: Ensure that the row label is a valid data label.
//
/////////////////////////////////////////////////////////////////////////////
// Reserving 43000 - 43499 for NZ error codes.
/////////////////////////////////////////////////////////////////////////////
/
/ Copyright (c) 2003 by Oracle Corporation
/ NAME
/ nze2us.msg - Network Zecurity Error messages - american (US) language
/ DESCRIPTION
/ Contains error messages for the Oracle Security Server
/ RETURNS
/ None.
/
/ NOTES
/ MODIFIED (MM/DD/YY)
/ rchahal 11/23/04 - changes suggested by errors_us
/ rchahal 10/11/04 - add pkcs11 messages
/ rchahal 08/20/03 - rchahal_nz_errors2
/ rchahal 08/14/03 - New nz error range (43000 - 43499)
/
43000, 00000, "pkcs11 library not found"
// *Cause: The PKCS11 library could not be found.
// *Action: Make sure that the pkcs11 library is at the location specified in
// the wallet.
/
43001, 00000, "pkcs11 token not found"
// *Cause: The PKCS11 token could not be found.
// *Action: Make sure that a token with correct label is present in slot.
/
43002, 00000, "pkcs11 passphrase is wrong"
// *Cause: The PKCS11 passphrase is wrong.
// *Action: Make sure that the token passphrase specified is correct.
/
43003, 00000, "pkcs11: C_GetFunctionList() returned error"
// *Cause:
// *Action:
/
43004, 00000, "pkcs11: C_Initialize returned error"
// *Cause:
// *Action:
/
43005, 00000, "pkcs11: No tokens present"
// *Cause: a token is not present in the slot
// *Action: Place a pkcs11 token in the slot
/
43006, 00000, "pkcs11: C_GetSlotList returned error"
// *Cause:
// *Action:
/
43008, 00000, "pkcs11: C_GetTokenInfo returned error"
// *Cause:
// *Action:
/
43009, 00000, "Symbol not found in pkcs11 library"
// *Cause:
// *Action:
/
43011, 00000, "pkcs11: Token login failed"
// *Cause: To login to the pkcs11 token a correct passphrase is needed
// *Action: Check the token passphrase.
/
43013, 00000, "pkcs11: Failed to change certC provider"
// *Cause:
// *Action: Check trace message.
/
43014, 00000, "pkcs11: finding private key on token error"
// *Cause: error occurred while finding private key on token
// *Action: Make sure the private key corresponding to the certificate in
// wallet is on the token. Check trace message
/
43015, 00000, "pkcs11: key pair gen error"
// *Cause: error occurred while generating key pair using HSM
// *Action: Check trace message
/
43016, 00000, "pkcs11: wallet already contains pkcs11 information"
// *Cause:
// *Action:
/
43017, 00000, "pkcs11: No certificate found on the smart card/HSM"
// *Cause: No certificate was found on the smart card/HSM.
// *Action: Follow smart card/HSM vendor documentation to populate the smart card/HSM with certificate.
/
43018, 00000, "pkcs11: No user certificate found on the smart card/HSM"
// *Cause: No user certificate was found on the smart card/HSM.
// *Action: Follow smart card/HSM vendor documentation to populate the smart card/HSM with certificate and private key.
/
43019, 00000, "pkcs11: No certificate found on smart card/HSM label with given cert label"
// *Cause: There were no certificate labels on the smart card/HSM that matched the certificate label specified in the wallet.
// *Action: Follow smart card/HSM vendor documentation to set certificate label in smart card/HSM.
/
43020, 00000, "pkcs11: Multiple certificates found on smart card/HSM with given cert label"
// *Cause: Certificates with identical labels were found in the smart card/HSM.
// *Action: Follow smart card/HSM vendor documentation to assign unique certificate labels to certificates.
/
43021, 00000, "pkcs11: Certificate with given cert label is not a user cert"
// *Cause: The certificate with the specified certificate label did not have a matching private key in the smart card/HSM.
// *Action: Follow smart card/HSM vendor instructions to create credentials (certificate/private key) in smart card/HSM.
/
43059, 00000, "RSA error. See trace output."
// *Cause:
// *Action: Provide the trace output to Oracle Support for further diagnostics.
/
43084, 00000, "Certificate is using forbidden or unsupported signature algorithm."
// *Cause: Certificate may be using MD2 or MD5 signature algorithm.
// *Action: Review wallet content and remove or replace certificates using obsolete algorithms.
/
43126, 00000, "SSL/TLS : received invalid ClientHello message."
// *Cause:
// *Action: Provide a network trace to Oracle Support for further diagnostics.
/
43127, 00000, "SSL/TLS : received invalid ServerHello message."
// *Cause:
// *Action: Provide a network trace to Oracle Support for further diagnostics.
/
/
/ Reserving 43750 - 43800 for additional transaction layer error codes.
/
43750, 0000, "invalid or illegal combination of COMMIT WRITE options"
// *Document: YES
// *Cause: invalid or illegal combination of options provided to COMMIT
// WRITE SQL statement.
// *Action: Provide a valid combination of options for COMMIT WRITE
// statement
43751, 0000, "invalid value for parameter %s"
// *Document: YES
// *Cause: invalid or illegal value provided for parameter.
// *Action: Provide a valid value for the parameter
/
/ Reserving 43801 - 43900 for additional data layer (KD) errors/events.
/ Reserving 43851 - 43900 for 11g lob errors/events.
/
43801, 0000, "parallel long-to-lob debugging event"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
43802, 0000, "disable probe before index leaf block delete"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43803, 0000, "change notification tracing for iot/indexes"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43804, 0000, "iot-rollback testing"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43805, 0000, "auto-parallel tables/indexes"
// *Document: NO
// *Cause: This is an internal testing event; if the event has a
// non-zero level, tables/indexes created (noparallel,
// parallel 1, or without any parallelism specification)
// by the session will have a DOP = 2, unless the session
// forces parallel DDL (in which case the forced settings
// will be honored).
// The level of this event indicates the object type to be
// parallelized such as heap tables, indexes on heap tables,
// IOTs and indexes on IOTs.
// This event can be used to automatically enable parallelism
// testing for all tables/indexes without modifying test
// sources.
// *Action: N/A
43806, 0000, "iot nonkey reserve length fixup"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43807, 0000, "indexes on ORA_ROWSCN not allowed"
// *Document: YES
// *Cause: An attempt was made to create an index that refers to the
// ORA_ROWSCN pseudo-column, either directly or in an
// expression.
// *Action: Do not use ORA_ROWSCN to define an index on a table.
43808, 0000, "Turn on local CELL debugging"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43809, 0000, "Force non-coalesced extent scans"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43810, 0000, "check-and-skip corrupt blocks in index scans"
// *Document: NO
// *Cause: This is an event meant for use in special data-recovery
// scenarios, and must be enabled only under the supervision
// of Oracle support or development.
// *Action: N/A
43811, 0000, "limit readahead for block sampling table/index scans"
// *Document: NO
// *Cause: This is an event meant for use in scenarios where the default
// "db_file_multiblock_read_count" computed for the RDBMS is
// too large, and smaller values provide better IO/elapsed-time
// performance for sampling scans at low sampling rates.
// The event should be used only after consultation with
// Oracle support or development.
// *Action: N/A
43812, 0000, "avoid online index (re)build cleanup on specific errors"
// *Document: NO
// *Cause: This is an event meant for use in scenarios where the
// cleanup of a failed online index (re)build operation should
// be skipped, depending on the error that occurred. The
// error code is the value of this event. The event should
// be used only after consultation with Oracle support or
// development, and for internal debugging purposes.
// *Action: N/A
43813, 0000, "set soft limit for index leaf block ITL entries"
// *Document: NO
// *Cause: This is an event meant for use in scenarios where the growth
// of an index leaf block ITL is disproportionate to the number
// of concurrent sessions. The event level sets a soft limit on
// the ITL size. The event should be used only after consultation
// with Oracle Support Services or Development.
// *Action: N/A
43814, 0000, "DROP INDEX is invalid for hash cluster index"
// *Document: YES
// *Cause: An attempt was made to drop an index defined on a hash
// cluster. Hash cluster indexes cannot be dropped.
// *Action: Do not attempt to drop an index defined on a hash cluster.
43815, 0000, "Turn on local CELL INDEX debugging"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43816, 0000, "Turn on local CELL debugging"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or development.
// *Action: N/A
43820, 0000, "#block rejections in space reclamation before segment extension"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
43821, 0000, "b+tree level to enable rejection limit"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
43822, 0000, "enable/disable/trace rejection heuristic"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
43850, 0000, "Advanced Compression Option parameter is required to be enabled"
// *Document: YES
// *Cause: An Advanced Compression Option (ACO) feature was specified
// without enabling the ACO parameter.
// *Action: Set or Update the ACO parameter (enable_option_advanced_compression)
// to TRUE.
43852, 0000, "SECUREFILE and BASICFILE cannot be used together"
// *Document: YES
// *Cause: SECUREFILE and BASICFILE were both specified.
// *Action: Modify the SQL statement to specifiy only one of SECUREFILE or
// BASICFILE.
43853, 0000, "SECUREFILE lobs cannot be used in non-ASSM tablespace \"%s\""
// *Document: YES
// *Cause: SECUREFILE lobs require ASSM
// *Action: Specify an ASSM tablespace for SECUREFILE lobs.
//43854, 0000, "Deprecated"
// *Document: No
// *Cause: Don't use this for external errors. Was used in 11.1.0.6.0.
// *Action:
43855, 0000, "SYNC and ASYNC cannot be used together"
// *Document: NO
// *Cause: SYNC and ASYNC were both specified.
// *Action: Modify the SQL statement to specify either SYNC or ASYNC.
43856, 0000, "Unsupported LOB type for SECUREFILE LOB operation"
// *Document: YES
// *Cause: A LOB that is not a SECUREFILE was used in a SQL statement or
// in a call where a SECUREFILE LOB was expected.
// *Action: Convert the LOB to a SECUREFILE LOB or do not use this keyword
// or call.
43857, 0000, "Parameter Error"
// *Document: YES
// *Cause: Attempt to modify a LOB with an invalid parameter.
// *Action: Fix paramters and retry the operation.
43858, 0000, "Use CACHE LOGGING SYNC as default for SECUREFILE LOBs"
// *Document: NO
// *Cause: Used NOCACHE LOGGING as the default storage clause for
// SECUREFILE LOBs.
// *Action: This event is provided only for internal testing and qa purposes.
43859, 0000, "CONTENTTYPE string too long"
// *Document: YES
// *Cause: Length of CONTENTTYPE string exceeded the defined maximum.
// *Action: Modify length of CONTENTTYPE string and retry operation.
43860, 0000, "Lob fragments metadata has reached predefined limit"
// *Document: NO
// *Cause: Lob fragment update operation can no longer be performed
// since the preset limit of metadata size has been reached
// *Action: Perform lob reorganization and mark reset.
43861, 0000, "Provided lob mark offset had been erased"
// *Document: NO
// *Cause: Client is accessing through an erased lob mark offset
// *Action: Perform mark reset. Check application for consistency
43862, 0000, "CONTENTTYPE buffer length incorrect"
// *Document: YES
// *Cause: Length of CONTENTTYPE buffer less than defined constant.
// *Action: Modify length of CONTENTTYPE buffer and retry operation.
43863, 0000, "securefile inode preallocation percentage"
// *Document: NO
// *Cause: Set the value of the securefile inode space preallocation
// percentage.
// *Action: This event should be used only under the supervision of
// Oracle Support Services or development.
43864, 0000, "securefile inode preallocation mode"
// *Document: NO
// *Cause: Set the value of the securefile inode space preallocation
// mode.
// *Action: This event should be used only under the supervision of
// Oracle Support Services or development.
43865, 0000, "SECUREFILE LOBs WGC layer fast callbacks disabling event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
43866, 0000, "SECUREFILE LOBs RCI layer fastpath inline read disabling event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
43868, 0000, "SECUREFILE LOBs WGC layer flushing testing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
43869, 0000, "SECUREFILE LOBs WGC layer crash testing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
43870, 0000, "SECUREFILE lobs WGC layer tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
43871, 0000, "SECUREFILE LOBs WGC layer in-memory read disabling event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
43872, 0000, "SECUREFILE LOBs WGC layer shared I/O buffer disabling event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
43873, 0000, "SECUREFILE LOBs WGC layer shared I/O buffer forcing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
43874, 0000, "SECUREFILE LOBs WGC layer SGA buffer forcing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
43875, 0000, "SECUREFILE lobs transformation layer tracing event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43876, 0000, "SECUREFILE lob transformation feature \"%s\" not yet supported"
// *Document: NO
// *Cause: This is an internal event to be used only in the development
// and testing phase, to allow incremental implementation.
// *Action: Wait till the feature is supported.
43877, 0000, "SECUREFILE LOB memory pressure simulation event"
// *Document: NO
// *Cause: This is an internal event to be used only in the development
// and testing phase, to simulate memory pressure conditions.
// *Action: N/A
43878, 0000, "LOB feature unsupported below compatible setting 11.2.0"
// *Document: YES
// *Cause: An 11.2 LOB feature was specified when the database was operating
// at a compatible setting lower than "11.2.0".
// *Action: Upgrade the database compatible setting to "11.2.0" or higher
// to enable the desired new features.
43879, 0000, "SECUREFILE lobs deduplication facility testing event"
// *Document: NO
// *Cause: This is an internal testing event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43880, 0000, "SECUREFILE lobs rci flushing event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43881, 0000, "SECUREFILE lobs delta update debugging event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43882, 0000, "SECUREFILE LOBs delta update testing event"
// *Document: NO
// *Cause: This is an internal testing event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43883, 0000, "SECUREFILE LOBs delta update invalid operation"
// *Document: YES
// *Cause: Invalid delta update operation was issued on LOB.
// This includes operation beyond LOB length; move operation
// with destination offset inside move interval.
// *Action: Check operation parameters for validity.
43884, 0000, "SECUREFILE LOB mapping service debugging event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
43896, 0000, "SECUREFILE internal event for CTX testing"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
43897, 0000, "SECUREFILE internal event for SQL"
// *Document: NO
// *Cause: This is an internal testing event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43898, 0000, "SECUREFILE lobs tracing event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43899, 0000, "SECUREFILE lobs inode tracing event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: N/A
43900, 0000, "SECUREFILE lob feature \"%s\" not yet supported"
// *Document: NO
// *Cause: This is an internal event to be used only in the development
// and testing phase, to allow incremental implementation.
// *Action: Wait till the feature is supported.
/
/ Reserving 43901 - 44000 for SQL execution errors/events.
/
43901, 0000, "sampling repeatibility event"
// *Document: NO
// *Cause: This event is used to prevent intermittent difs caused by
// sampling inrepeatibility.
// *Action: N/A
43902, 0000, "qksDestroyServices debugging event"
// *Document: NO
// *Cause: This event is used to dump debugging information when
// qksDestroyServices is executed.
// *Action: N/A
43903, 0000, "always result-cache node"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
43904, 0000, "temp table event"
// *Document: NO
// *Cause: This is an internal event.
// *Action: N/A
43905, 0000, "result cache tracing event"
// *Document: NO
// *Cause: This is an internal event.
// *Action: N/A
43906, 0000, "result cache service (qesrc) validation event"
// *Document: NO
// *Cause: This is an internal event.
// *Action: N/A
43907, 0000, "This argument must be a literal or bind variable."
// *Document: YES
// *Cause: An attempt was made to provide an argument that was not a literal
// or bind variable.
// *Action: Provide an argument that is either a literal or bind variable.
43908, 0000, "invalid output data type"
// *Document: YES
// *Cause: An invalid output data type was provided.
// The valid output data types for VALIDATE_CONVERSION operator and
// the operators supporting DEFAULT ON CONVERSION ERROR syntax are:
// NUMBER, BINARY_FLOAT, BINARY_DOUBLE, DATE, TIMESTAMP,
// TIMESTAMP WITH TIME ZONE, INTERVAL DAY TO SECOND,
// INTERVAL YEAR TO MONTH.
// *Action: Provide a valid output data type.
43909, 0000, "invalid input data type"
// *Document: YES
// *Cause: An invalid input data type was provided for Validate_Conversion
// operator.
// For the NUMBER, BINARY_FLOAT and BINARY_DOUBLE output data types,
// the input data types can be:
// - NUMBER
// - BINARY_FLOAT
// - BINARY_DOUBLE
// - CHAR
// - VARCHAR2
// - NCHAR
// - NVARCHAR2
// For the DATE, TIMESTAMP, TIMESTAMP WITH TIME ZONE, INTERVAL DAY
// TO SECOND, and INTERVAL YEAR TO MONTH output data types,
// the input data types can be:
// - CHAR
// - VARCHAR2
// - NCHAR
// - NVARCHAR2
// *Action: Provide a valid input data type.
43910, 0000, "precision is not supported by Validate_Conversion operator"
// *Document: YES
// *Cause: Precision was provided for the following data types:
// NUMBER, TIMESTAMP, TIMESTAMP WITH TIME ZONE,
// INTERVAL YEAR TO MONTH, INTERVAL DAY TO SECOND.
// *Action: Do not specify precision for following data types:
// NUMBER, TIMESTAMP, TIMESTAMP WITH TIME ZONE,
// INTERVAL YEAR TO MONTH, INTERVAL DAY TO SECOND.
43911, 0000, "cannot specify collation for non-character columns"
// *Document: YES
// *Cause: COLLATE was specified for a non-character column.
// *Action: Remove the COLLATE keyword.
43912, 0000, "invalid collation specified for a CLOB or NCLOB value"
// *Document: YES
// *Cause: A character LOB column or expression was declared as having a
// collation other than USING_NLS_COMP or the determined collation
// for a collation-sensitive operator or function operating on
// character LOB values was not USING_NLS_COMP. Character LOB
// values support only the USING_NLS_COMP collation.
// *Action: Correct the collation declarations to make sure the
// USING_NLS_COMP collation is applied to the character LOB values.
43913, 0000, "unable to derive collation for the result: conflicting collations"
// *Document: YES
// *Cause: Arguments to the operator or function (operation) that have
// the lowest coercibility level and are relevant for derivation
// of the collation for the result of this operation had
// conflicting collations.
// *Action: Check the collation derivation rules in the Oracle Database
// documentation and apply the COLLATE operator as appropriate
// to remove the existing conflict.
43914, 0000, "unable to determine collation: arguments have undefined collation"
// *Document: YES
// *Cause: Arguments to the operator, function, or condition (operation)
// that are relevant for determining the collation to be used
// by this operation had undefined collations.
// *Action: Check the collation determination rules in the Oracle Database
// documentation and apply the COLLATE operator as appropriate to
// assign a collation explicitly.
43915, 0000, "unable to determine collation: arguments have conflicting collations"
// *Document: YES
// *Cause: Arguments to the operator, function, or condition (operation)
// that have the lowest coercibility level and are relevant for
// determining the collation to be used by this operation had
// different collations.
// *Action: Check the collation determination rules in the Oracle Database
// documentation and apply the COLLATE operator as appropriate to
// remove the existing conflict.
43916, 0000, "unable to determine collation for the column"
// *Document: YES
// *Cause: An attempt was made to create a virtual character column
// in a table, a character column in a table based on a query
// (CREATE TABLE AS SELECT), or a character column in the key
// of a functional index. The expression on which the column
// definition was based did not have a derived collation
// to be used for the column, because of a collation conflict
// in one of its operators. In case of a virtual column, no
// collation was provided for the column through the data type
// declaration, either.
// *Action: Check the collation derivation rules in the Oracle Database
// documentation and apply the COLLATE operator in the defining
// expression as appropriate to resolve collation conflicts.
// If defining a virtual column, alternatively, specify a data type
// for the column to let the column inherit the collation from
// the table default, or specify the collation explicitly
// with the data type.
43917, 0000, "invalid collation for a primary key column of the index-organized table"
// *Document: YES
// *Cause: An attempt was made to specify an invalid collation for the
// primary key column of an index-organized table.
// *Action: Use one of the supported collations for the primary key
// column of the index-organized table: BINARY, USING_NLS_COMP,
// USING_NLS_SORT, USING_NLS_SORT_CS, USING_NLS_SORT_VAR1, or
// USING_NLS_SORT_VAR1_CS.
43918, 0000, "This argument must be a literal"
// *Document: YES
// *Cause: An attempt was made to provide an argument that was not a
// literal.
// *Action: Provide a literal argument.
43919, 0000, "Nested aggregates are not supported for pivot operation."
// *Document: YES
// *Cause: Nested aggregates were specified in the pivot operator.
// This operation is not supported.
// *Action: Remove the nested aggregates from the pivot operation.
43920, 0000, "DEFAULT ON NULL is not supported for object type or REF columns"
// *Document: YES
// *Cause: DEFAULT ON NULL was specified on a object type or REF column.
// These types are not supported.
// *Action: Remove the ON NULL keyword for this column.
43921, 0000, "invalid collation for cluster column"
// *Document: YES
// *Cause: An attempt was made to create an index cluster in which one of
// the key columns had an unsupported declared collation or an
// attempt was made to create a hash cluster in which a key column
// with SORT clause had an unsupported declared collation.
// Only the collations BINARY, USING_NLS_COMP, USING_NLS_SORT,
// USING_NLS_SORT_CS, USING_NLS_SORT_VAR1, and
// USING_NLS_SORT_VAR1_CS are supported for character columns in
// index clusters and for sorted character columns of hash clusters.
// *Action: Use one of the supported collations for the offending column.
43922, 0000, "Collation of the column cannot be modified."
// *Document: YES
// *Cause: An attempt was made to modify the declared collation of a
// column that either:
// o belonged to a foreign key
// o belonged to a primary or unique key and that key was
// referenced by some foreign key
// o corresponded to a cluster key column
// o was referenced by a defining expression of a virtual column
// o was referenced by a defining expression of a functional
// index
// o corresponded to an attribute of a user-defined type
// or an object table
// o belonged to the container table of a materialized view
// o was referenced by a join condition of a bitmap join index
// The declared collation of such columns cannot be modified.
// *Action: Use one of the following as appropriate:
// o Drop the offending constraint, virtual column, or index,
// modify the collation of the column, and re-create the
// dropped element.
// o If possible, modify the type attribute instead of the
// column.
// o If possible, modify the derived collation of the
// corresponding materialized view column (for example, with
// the COLLATE operator) and re-create the materialized view
// to re-create its container table with the new column
// collation.
// o Save the tables of a cluster, re-create the cluster using
// the new collation, and restore the saved tables into the
// cluster.
43923, 0000, "The column cannot be modified to the specified collation."
// *Document: YES
// *Cause: An attempt was made to modify the declared collation of a
// column that belonged to a primary or unique key, or
// a standard index key, or a partitioning key, and the new
// collation was from a different group than the old collation,
// where the groups are defined as follows:
// Group 1: BINARY, USING_NLS_COMP, USING_NLS_SORT,
// USING_NLS_SORT_CS, USING_NLS_SORT_VAR1,
// and USING_NLS_SORT_VAR1_CS
// Group 2: BINARY_CI, USING_NLS_SORT_CI,
// and USING_NLS_SORT_VAR1_CI
// Group 3: BINARY_AI, USING_NLS_SORT_AI,
// and USING_NLS_SORT_VAR1_AI
// *Action: When modifying the column collation, specify a new collation
// that is in the same group as the current column collation.
// If there is no current collation, because you changed
// the column data type at the same time and the old data
// type is not a character data type, then select a collation
// from Group 1 as the new collation.
43924, 0000, "unable to modify collation of an Oracle-maintained database object"
// *Document: YES
// *Cause: An attempt was made to modify the collation of an
// Oracle-maintained database object. Modifications of
// Oracle-maintained database objects are generally not permitted.
// *Action: Do not modify Oracle-maintained database objects unless
// explicitly instructed to do so by Oracle Support Services.
43925, 0000, "A character column in the index definition has an unsupported collation."
// *Document: YES
// *Cause: An attempt was made to create a bitmap join index or
// a domain index with a key or join condition that contained
// a character column with a declared collation other than BINARY,
// USING_NLS_COMP, USING_NLS_SORT, USING_NLS_SORT_CS,
// USING_NLS_SORT_VAR1, or USING_NLS_SORT_VAR1_CS. Only these
// listed collations are supported by this type of the index.
// *Action: Use one of the supported collations for the key column or
// join condition.
43926, 0000, "Cannot use the specified collation with some of the dependent objects."
// *Document: YES
// *Cause: An attempt was made to change the collation of a character
// column to a collation that is not supported in a key of a
// bitmap join index, a domain index key
// to which the column belongs.
// Only the collations BINARY, USING_NLS_COMP, USING_NLS_SORT,
// USING_NLS_SORT_CS, USING_NLS_SORT_VAR1, and
// USING_NLS_SORT_VAR1_CS are supported in these keys.
// *Action: Use one of the supported collations for the key column.
43927, 0000, "Cannot specify default collation for object tables."
// *Cause: An attempt was made to explicitly state the default collation
// setting for an object table. However, default collations do not
// apply to object tables because all columns of an object table
// inherit collations from the attributes of the base type
// of the table.
// *Action: The operation is not allowed.
43928, 0000, "Conversion error handling is not allowed here."
// *Cause: An attempt was made to use the default value, in case of a
// conversion failure, by specifying the DEFAULT <argument> ON
// CONVERSION ERROR statement to a conversion operator.
// This feature is not allowed for current operation.
// *Action: Remove DEFAULT <argument> ON CONVERSION ERROR
// from the conversion operator and try again.
43929, 0000, "Collation cannot be specified if parameter MAX_STRING_SIZE=STANDARD is set."
// *Document: YES
// *Cause: The COLLATE or DEFAULT COLLATION clause was specified in a DDL
// statement or the DEFAULT_COLLATION parameter was specified in an
// ALTER SESSION statement, but the value of the initialization
// parameter MAX_STRING_SIZE was STANDARD. The data-bound collation
// feature is disabled if the value of this parameter is STANDARD.
// *Action: Set MAX_STRING_SIZE to EXTENDED by following the procedure
// documented in the Oracle Database Reference.
43930, 0000, "A query issued from a pre-12.2 database references a column with an unsupported collation."
// *Document: YES
// *Cause: A table or view column with a declared collation other than
// USING_NLS_COMP was referenced in a distributed query that
// originated in an Oracle Database with the release number
// lower than 12.2. Such references are not allowed.
// *Action: In the remote database that reported this error, create a view
// corresponding to the subquery that was executed in that
// database and make sure that all columns of this view have
// the collation USING_NLS_COMP. Use the COLLATE operator
// if necessary. In the original query, replace the subquery
// with a reference to the view.
43931, 0000, "DEFAULT COLLATION may not be combined with other operations"
// *Document: YES
// *Cause: An ALTER TABLE statement attempted to combine DEFAULT COLLATION
// with some other operation, which is not allowed.
// *Action: Ensure that DEFAULT COLLATION is the only operation specified
// in an ALTER TABLE statement.
43932, 0000, "DROP IDENTITY cannot be combined with other operations"
// *Document: YES
// *Cause: An ALTER TABLE statement attempted to combine DROP IDENTITY
// with some other operation, which is not allowed.
// *Action: Ensure that DROP IDENTITY is the only operation specified
// in an ALTER TABLE statement.
43933, 0000, "Collation must be specified."
// *Document: YES
// *Cause: Collation was not specified in a context where it was required.
// *Action: Specify the required collation.
/
/ Reserving 44001 - 44020 for DBMS_ASSERT errors
/
44001, 0000, "invalid schema"
// *Document: Yes
// *Cause: The schema for the given schema name did not exist.
// *Action: Provide a valid schema name.
44002, 0000, "invalid object name"
// *Document: Yes
// *Cause: The input parameter string was not a qualified
// SQL identifier of an existing SQL object.
// *Action: Make sure the string matches an existing SQL object that
// is accessible by the current schema.
44003, 0000, "invalid SQL name"
// *Document: Yes
// *Cause: The input parameter string was not a valid simple SQL name.
// *Action: Check with the DBMS_ASSERT spec to verify that the parameter
// string is a valid simple SQL name.
44004, 0000, "invalid qualified SQL name"
// *Document: Yes
// *Cause: The input parameter string was not a valid qualified SQL name.
// *Action: Check with the DBMS_ASSERT spec to verify that the parameter
// string is a valid qualified SQL name.
/
/ Reserving 44021 - 44100 for DBMS_SESSION errors
/
44021, 00000, "DBMS_SESSION.SET_CURRENT_SCHEMA_DEFERRED failed due to change of PDB."
// *Cause: Set schema failed because an attempt was made to change the
// pluggable database (PDB) before the set schema took effect.
// *Action: Do not change the PDB before the set schema takes effect.
/
/
/ Reserving 44101 - 44200 for UTL package errors
/
44101, 0000, "invalid priority"
// *Document: Yes
// *Cause: The priority level given by the user was invalid.
// *Action: See UTL_MAIL for valid priority values and change the
// priority parameter accordingly.
44102, 0000, "unknown or unsupported algorithm"
// *Document: Yes
// *Cause: An unknown or unsupported authentication or compression
// algorithm was encountered.
// *Action: Check the authentication or compression algorithm. Use one that
// is supported by Oracle.
/
/ Reserving 44201 - 44300 for Shared Cursor (KKS) errors
/
44201, 0000, "cursor needs to be reparsed"
// *Document: No
// *Cause: An error has occured during cursor compilation.
// This error is trapped by the shared cursor layer(KKS).
// The heaps of the invalid cursor will be purged, the error will
// be cleared and the cursor will be reparsed.
// *Action: N/A
44202, 0000, "dump kkdcCheckAcrMap information"
// *Document: No
// *Cause:
// *Action: Causes kkdcCheckAcrMap to write debug information to the trace
// file.
44203, 0000, "timeout waiting for lock on cursor"
// *Document: Yes
// *Cause: A timeout occured while waiting for a cursor to be compiled.
// This is usually caused by the SQL parse requiring access to
// system resources which are locked by concurrently executing
// sessions.
// *Action: Investigate possible causes of resource contention. If
// neccessary, contact support for additional information
// on how to diagnose this problem.
44204, 0000, "library cache object %s.%s found in an in-flux state"
// *Document: Yes
// *Cause: The pseudo-cursor depends on a table which was found to
// be obsolete due to metadata invalidation of the library
// cache object.
// *Action: Contact Oracle Support Services for additional information.
44205, 0000, "cursor needs to be reparsed due to Private Temp Table(PTT)"
// *Document: No
// *Cause: PTT found in the cursor. To make cursor specific to a given session,
// a unique comment is added and reparsed.
// This error is trapped by the shared cursor layer(KKS).
// This error will be cleared and the cursor will be reparsed.
// *Action: N/A
/
/ Reserving 44301 - 44320 for DBMS_SERVICES errors
/
44301, 0000, "NULL service name is not permitted"
// *Document: Yes
// *Cause: The service name argument was found to be NULL.
// *Action: Provide a non-NULL service name.
44302, 0000, "NULL network name is not permitted"
// *Document: Yes
// *Cause: The network name argument was found to be NULL.
// *Action: Provide a non-NULL network name.
44303, 0000, "service name exists"
// *Document: Yes
// *Cause: This service name was already in existence.
// *Action: Provide a new unique service name.
44304, 0000, "service %s does not exist"
// *Document: Yes
// *Cause: The specified service was not in existence.
// *Action: Provide a valid service name.
44305, 0000, "service %s is running"
// *Document: Yes
// *Cause: The specified service was running.
// *Action: This message is informational only.
44306, 0000, "service name exceeds maximum length of %s"
// *Document: Yes
// *Cause: The service name was too long.
// *Action: Use a shorter service name.
44307, 0000, "network name too long"
// *Document: Yes
// *Cause: The network name, excluding the domain, was too long.
// *Action: Use a shorter network name.
44308, 0000, "services not initialized"
// *Document: No
// *Cause: The services layer was not yet initialized.
// *Action: N/A
44309, 0000, "unknown failure"
// *Document: No
// *Cause: There was an unknown failure.
// *Action: Contact Oracle Support Services.
44310, 0000, "maximum number of services exceeded"
// *Document: Yes
// *Cause: The maximum number of services has been reached.
// *Action: N/A
44311, 0000, "service %s not running"
// *Document: Yes
// *Cause: The specified service was not running.
// *Action: This message is informational only.
44312, 0000, "database closed"
// *Document: Yes
// *Cause: The database was closed.
// *Action: Open the database and retry the operation.
44313, 0000, "instance name invalid"
// *Document: Yes
// *Cause: The instance name argument was not valid.
// *Action: Provide a valid instance name.
44314, 0000, "network name already exists"
// *Document: Yes
// *Cause: The network name was already in existence.
// *Action: Use an alternate network name.
44315, 0000, "all service attributes null"
// *Document: Yes
// *Cause: All attributes specified were null.
// *Action: At least one attribute must be non-null.
44316, 0000, "invalid argument"
// *Document: Yes
// *Cause: Invalid argument supplied.
// *Action: Supply a valid argument.
44317, 0000, "database open read-only"
// *Document: Yes
// *Cause: The database is open read-only.
// *Action: Close the database and reopen it read/write before
// trying again.
44318, 0000, "exceeded maximum SERVICE_NAMES length"
// *Document: Yes
// *Cause: The total length of all running service network names
// exceeded the maximum allowable length.
// *Action: Stop another service to start this one.
44319, 0000, "Cannot delete AQ service"
// *Document: Yes
// *Cause: Specified AQ service belonged to a queue.
// *Action: Delete the queue.
44320, 0000, "cannot modify global service"
// *Document: Yes
// *Cause: Could not modify the global service because of insufficient
// privileges or you were trying to modify the global service
// attribute.
// *Action: Use global service management to modify a global service.
/
/ Reserving 44321 - 44400 for DBMS_HPROF and PLSTIMER errors
/
44321, 0000, "cannot read command line from trace file %s"
// *Document: Yes
// *Cause: Trace file could not be read.
// *Action: Make sure trace file exists and contains valid raw trace data.
44322, 0000, "invalid file name '%s'"
// *Document: Yes
// *Cause: A NULL or zero length file name was specified.
// *Action: Correct the file name to be a nonzero length string.
44323, 0000, "negative <count> '%s' to %s option"
// *Document: Yes
// *Cause: The given count was a nonpositive number.
// *Action: Provide a positive count number.
44324, 0000, "no <count> argument to %s option"
// *Document: Yes
// *Cause: Count number was missing for the option.
// *Action: Provide a count number to the option.
44325, 0000, "no entry points found in trace file %s"
// *Document: Yes
// *Cause: The given trace symbol was not found.
// *Action: N/A
44326, 0000, "no <symbol> argument to %s option"
// *Document: Yes
// *Cause: <symbol> argument to -[un]trace option was missing.
// *Action: Provide <symbol> argument to -[un]trace option.
44327, 0000, "no <filename> argument to %s option"
// *Document: Yes
// *Cause: <filename> argument to the option was missing.
// *Action: Provide <filename> argument to the option.
44328, 0000, "unsupported version number: %s"
// *Document: Yes
// *Cause: Version of the trace file was not supported.
// *Action: Provide supported version of trace file.
44329, 00000, "length of full path name too long"
// *Cause: The full path name provided was too long.
// *Action: Use a shorter directory path, file name or both.
/
/ Reserving 44401 - 44409 for Classic Export/Import events
/
44401, 0000, "turn off DBA privilege"
// *Document: No
// *Cause: special processing event.
// *Action: N/A.
44402, 0000, "restore DBA privilege"
// *Document: No
// *Cause: special processing event.
// *Action: N/A.
44403, 0000, "invalid value specified for flag parameter"
// *Document: Yes
// *Cause: Mutually exclusive values were specified for the flag parameter.
// *Action: Internal error. Contact Oracle Support Services.
44404, 0000, "upicui2 client function requires Oracle server of 10.2 or higher"
// *Document: Yes
// *Cause: A 10.2 or higher client is being used with an older Oracle server.
// *Action: Use an Oracle server with the same version as the client.
44405, 0000, "parse enabled for segment attributes of IOT mapping table"
// *Document: NO
// *Cause: An internal event was triggered during the import as part of
// the fix for bug 4375555. This event allows specification
// of segments attributes of IOT mapping tables.
// *Action: N/A
44406, 0000, "preserve HAKAN factor for ALTER TABLE ADD CONSTRAINT"
// *Document: NO
// *Cause: An internal event was triggered during the TTS import as part
// of the fix for bug 7251049. This event use to preserve HAKAN
// factor for ALTER TABLE ADD CONSTRAINT.
// *Action: N/A
/
/ Using event 44410 to evaluate xmlagg() LOB based.
/
44410, 0000, "XMLAGG function exceeds system limits"
// *Document: No
// *Cause: The XMLAGG aggregate function with GROUP BY clause
// exceeded the 30k sort buffer limitation.
// *Action: N/A
/
/ Reserving 44411 - 44420 for Fusion Security ACL Enhancement
/
44411, 0000, "Invalid ACL: START_DATE cannot be larger than END_DATE for all ACE"
// *Document: Yes
// *Cause: The END_DATE was smaller than the START_DATE
// in one of the ACE's in this ACL.
// *Action: Set all END_DATE to be larger than or equal to the START_DATE
// in each of the ACE's in this ACL.
44412, 0000, "Invalid ACL: Cyclic ACL inheritance is not allowed"
// *Document: Yes
// *Cause: A cycle was formed by ACL inheritance.
// *Action: Check the ACL inheritance and break the cycle by removing some
// ACL inheritance.GG function exceeds system limits.
44413, 0000, "Invalid ACL: Security class of parent ACL must be an ancestor of security class of child ACL"
// *Document: Yes
// *Cause: Security class of parent ACL was not an ancestor of security
// class of child ACL
// *Action: Change the security class of parent ACL to be an ancestor of
// security class of child ACL.
44414, 0000, "Invalid ACL: Parent ACL '%s' does not exist"
// *Document: Yes
// *Cause: The path to the parent ACL was not a valid resource.
// *Action: Change the parent ACL of this resource or create the parent
// ACL at the specified location.
44415, 0000, "Invalid ACL: Undefined privileges"
// *Document: Yes
// *Cause: An undefined privilege was found in an ACE in the ACL.
// *Action: Make sure the privilege is defined in the security class as
// specified in the ACL.
44416, 0000, "Invalid ACL: Unresolved principal '%s'"
// *Document: Yes
// *Cause: An unresolved principal is found in an ACE in the ACL.
// *Action: Make sure the principal is a valid user or role in the system.
44417, 0000, "Invalid ACL: Invalid ACLID"
// *Document: Yes
// *Cause: The specified ACLID did not point to a valid ACL document.
// *Action: Make sure the ACLID points to a valid ACL document.
44418, 0000, "Invalid ACL: %s"
// *Document: Yes
// *Cause: The specified ACL did not meet the validation requirements of the constraining ACL.
// *Action: Ensure ACL meets the validation requirements of the constraining ACL.
/
/ Reserving 44421 - 44499 for Compact Binary XML errors
/
44421, 0000, "cannot DISALLOW NONSCHEMA without a SCHEMA clause"
// *Document: Yes
// *Cause: If no SCHEMA clause (explicit schema or ANYSCHEMA) was
// specified, nonschema data cannot be disallowed.
// *Action: Remove DISALLOW NONSCHEMA or add some SCHEMA clause.
44422, 0000, "nonschema XML disallowed for this column"
// *Document: Yes
// *Cause: An attempt was made to insert nonschema based XML documents
// in a binary XML column that disallows nonschema data.
// *Action: Insert only schema-based documents or alter the column
// to ALLOW NONSCHEMA data.
44423, 0000, "XML Schema registered for BINARY cannot be used for CLOB/OBJ-REL"
// *Document: Yes
// *Cause: An attempt was made to use a XML Schema registered for
// binary usage as part of a CLOB or OBJ-REL clause.
// *Action: Specify a schema registered for CLOB or OBJ-REL use. Else
// specify BINARY XML storage for column.
44424, 0000, "BINARY XML storage requires XML Schema registered for BINARY usage"
// *Document: Yes
// *Cause: An attempt was made to specify BINARY XML storage using
// an XML schema not registered for BINARY.
// *Action: Specify a schema registered for BINARY usage. Else
// specify CLOB or OBJ-REL storage for column.
44425, 0000, "XML DB needs to be installed for creating an XMLType table or column"
// *Document: Yes
// *Cause: An attempt was made to create an XMLType table or column with
// out XML DB installed.
// *Action: Install XML DB.
/
/ Reserved 44501 - 44510 for XML DB Repository locks
/
44501, 00000, "QMEL: Too much concurrency."
// *Document: YES
// *Cause: Too much concurrency
// *Action: Transient error, try again.
44502, 00000, "QMEL: Lock not found."
// *Document: YES
// *Cause: Lock not found
// *Action: Check arguments
44503, 00000, "QMEL: Lock Denied."
// *Document: YES
// *Cause: Lock denied
// *Action: N/A
44504, 00000, "Resource Locked by Implicit Lock"
// *Document: YES
// *Cause: The resource is locked by an implicit lock
// *Action: Implicit locks are normally caused by NFS locks. Refer to
// XDB Protocol guide for removing/obtaining information about
// implicit locks.
44505, 00000, "QMEL: Invalid arguments."
// *Document: YES
// *Cause: Arguments to QMEL are not correct.
// *Action: N/A
/
/ Reserved 44510 - 44599 for XDB NFS
/
44510, 00000, "NFS: Internal server error"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44511, 00000, "NFS: Operation not supported"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44512, 00000, "NFS: Bad XDR"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44513, 00000, "NFS: Clientid is stale"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44514, 00000, "NFS: Invalid parameter"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44515, 00000, "NFS: Bad name argument"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44516, 00000, "NFS: No entry found"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44517, 00000, "NFS: Not a directory"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44518, 00000, "NFS: Is a dir "
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44519, 00000, "NFS: resource exists"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44520, 00000, "NFS: No file handle"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44521, 00000, "NFS: Resource constraint"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44522, 00000, "NFS: Bad stateid"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44523, 00000, "NFS: Old stateid"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44524, 00000, "NFS: Access not allowed"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44525, 00000, "NFS: File not opened in correct mode"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44526, 00000, "NFS: Lock not supported"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44527, 00000, "NFS: No grace period"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44528, 00000, "NFS: Stale stateid"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44529, 00000, "NFS: Bad type"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44530, 00000, "NFS: Bad handle"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44531, 00000, "NFS: Attribute not supported"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44532, 00000, "NFS: Files not same"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44533, 00000, "NFS: Buffer too small"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44534, 00000, "NFS: Operation illegal"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44535, 00000, "NFS: No restore filehandle found"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44536, 00000, "NFS: Name too long"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44537, 00000, "NFS: Read only file system"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44538, 00000, "NFS: Handle stale"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44539, 00000, "NFS: Bad owner"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44540, 00000, "NFS: Client Id in use"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44541, 00000, "NFS: File locked"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44542, 00000, "NFS: current filehandle is a symbolic link"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
44550, 00000, "NFS: Client disconnected"
// *Document: NO
// *Cause: This is an internal debugging event.
// *Action: N/A
/
/ Reserved 44600 - 44699 for LogMiner and Logical Standby
/
44600, 00000, "checkpoint write in progress (%s out of %s steps complete)"
// *Document: NO
// *Cause: LogMiner builder process is writing transaction data to
// checkpoint table.
// *Action: N/A
/
44601, 00000, "checkpoint read in progress (%s out of %s steps complete)"
// *Document: NO
// *Cause: LogMiner builder process is reading checkpointed transaction
// data.
// *Action: N/A
/
44602, 00000, "pageout in progress (%s out of %s steps complete)"
// *Document: NO
// *Cause: LogMiner builder process is writing transaction data to
// disk to free up memory.
// *Action: N/A
/
44603, 00000, "pagein of transaction %s.%s.%s in progress (%s out of %s steps complete)"
// *Document: NO
// *Cause: Process associated with a LogMiner session is reading paged out
// transaction data from disk.
// *Action: N/A
/
44604, 00000, "Barrier synchronization on DDL with XID %s.%s.%s (waiting on %s transactions)"
// *Document: NO
// *Cause: LogMiner builder process is waiting for outstanding transactions
// to be applied before commiting changes to the dictionary.
// *Action: N/A
44605, 00000, "Unused event"
// *Document: NO
// *Cause: This is an internal event.
// *Action:
44606, 00000, "Supplemental logging test event"
// *Document: NO
// *Cause: This is an internal event.
// *Action:
44607, 0000, "Archive logging must be enabled."
// *Document: Yes
// *Cause: Archive logging was not enabled.
// *Action: Enable archive logging on the database.
44608, 0000, "Supplemental logging settings cannot be modified in Oracle Database Express Edition."
// *Document: Yes
// *Cause: An attempt was made to modify supplemental logging settings using Oracle Database Express Edition.
// *Action: Upgrade to Oracle Database Standard Edition (SE) or Oracle
// Database Enterprise Edition (EE) to enable supplemental
// logging and logical replication.
/
/ Reserved 44700 - 44729 for Fusion Security XML Translations
/
44700, 0000, "Language '%s' is not a valid language for a translation"
// *Document: Yes
// *Cause: Invalid language.
// *Action: The language must conform to IETF RFC 3066.
44701, 0000, "Language not found for translation"
// *Document: Yes
// *Cause: The document had multiple translations and one of them
// did not have the xml:lang attribute.
// *Action: All translations must have the xml:lang attribute when
// multiple translations are present.
44702, 0000, "Multiple translations found for language '%s'"
// *Document: Yes
// *Cause: The document had multiple translations for a language.
// *Action: The document must contain only one translation per
// language for every translated element.
44703, 0000, "Multiple source language translations found"
// *Document: Yes
// *Cause: The document had multiple source language translations.
// *Action: The document must contain only one source language
// translation for every translated element.
44704, 0000, "XPath '%s' does not uniquely identify a translated element"
// *Document: Yes
// *Cause: The given XPath pointed to multiple translated elements.
// *Action: The given XPath must uniquely identify a translated element.
44705, 0000, "Must have xdb:maxOccurs='1' for translated elements"
// *Document: Yes
// *Cause: The value of xdb:maxOccurs was not '1' for a translated element.
// *Action: The value of xdb:maxOccurs must be '1' for a translated element.
44706, 0000, "Must have xsd:maxOccurs='unbounded' for translated elements"
// *Document: Yes
// *Cause: The value of xsd:maxOccurs was not 'unbounded' for a
// translated element.
// *Action: The value of xsd:maxOccurs must be 'unbounded' for a
// translated element.
44707, 0000, "No source language translation found"
// *Document: Yes
// *Cause: The document had no source language translation for a
// translated element.
// *Action: The document must contain exactly one source language
// translation for every translated element.
44708, 0000, "Translations not supported for object relational storage"
// *Document: Yes
// *Cause: The storage type of the schema was object relational.
// *Action: Register the schema with storage type as clob or binary xml.
44709, 0000, "Invalid schema definition for translated element"
// *Document: Yes
// *Cause: The schema definition for a translated element was
// invalid.
// *Action: A translated element must be a complex type with simple
// content which is a restriction or extension of
// xs:string.
44710, 0000, "Malformed XLIFF document: %s"
// *Document: Yes
// *Cause: The XLIFF document was malformed.
// *Action: Fix the error and try again.
44711, 0000, "XPath refers to an untranslatable element"
// *Document: Yes
// *Cause: XPath pointed to an untranslatable element.
// *Action: XPath for this operation must refer to a translatable element.
44712, 0000, "Invalid XPath in XLIFF document used for merging"
// *Document: Yes
// *Cause: XPath within trans-unit/id attribute was invalid.
// *Action: XPath within trans-unit/id attribute must point to a
// set of translations, not to a particular translation.
44713, 0000, "XPath does not select all translations"
// *Document: Yes
// *Cause: XPath did not select all translations for a particular
// element.
// *Action: XPath must point to a set of translations, not to a
// particular translation.
44714, 0000, "Fusion Security resources cannot be updated or deleted"
// *Document: No
// *Cause: An attempt was made to update or delete a resource that
// belongs to Fusion Security.
// *Action: None.
44715, 0000, "Event for XDB initialization"
// *Document: No
// *Cause: Internal event that was enabled during XDB initialization
// *Action: None.
44716, 0000, "Fusion security resources cannot be added or deleted here"
// *Document: No
// *Cause: An attempt was made to add or delete a resource that
// belongs to fusion security where it is disallowed.
// *Action: None.
44717, 0000, "First 7 positions (0-6) in the XDB repository is reserved for fusion security"
// *Document: Yes
// *Cause: An attempt was made to add or add a resource to the XDB
// repository at a position reserved for fusion security.
// *Action: Give a position other than 0 to 6.
44718, 0000, "Port conflict in XDB Configuration file"
// *Document: Yes
// *Cause: A port number specified in the XDB Configuration file conflicts
// with a port number used in the XDB Configuration file of the
// same non-consolidated database or the same Pluggable Database
// or a different Pluggable Database of the same consolidated database
// or the root container of the same consolidated database.
// *Action: Specify a different port number.
/
/
/ Reserved 44730 - 44750 for XML Index
/
44730, 00000, "XML Index %s is not usable at the moment"
// *Cause: The async XML Index could not be used since ORACLE is not open
// for query.
// *Action: Try the same query again when ORACLE is open for query, or use
// NO_XMLINDEX_REWRITE hint.
44731, 00000, "Path %s cannot be removed from the repository XML Index"
// *Cause: The repository XML Index indexed one of the parent folders of
// the resource identified by given path.
// *Action: Try removing the parent folder from the repository XML Index.
44732, 00000, "Path %s cannot be removed from the repository XML Index"
// *Cause: The repository XML Index did not index the resource identified
// by given path.
// *Action: Try removing a resource that is indexed by the repository XML
// Index.
44733, 00000, "The repository XML Index cannot be dropped directly"
// *Cause: DROP INDEX could not be used on the repository XML Index.
// *Action: Try using DBMS_XDB_ADMIN.DROPREPOSITORYXMLINDEX.
44734, 00000, "Predicate Index on nodes with similar children not allowed"
// *Cause: There was at least one node in the document with multiple similar
// children which was used in Predicate Indexing.
// *Action: Try removing Predicate Index on nodes with multiple similar
// children.
44735, 00000, "Too many predicates"
// *Cause: Number of predicates were more than limit.
// *Action: Try reducing number of predicates.
44736, 00000, "Group name already existed"
// *Cause: The group name specified already exists.
// *Action: Try a different group name.
44737, 00000, "Parameter %s did not exist."
// *Cause: The parameter name specified did not exist.
// *Action: Check the parameter name.
44738, 00000, "Group %s did not exist."
// *Cause: The group name specified did not exist.
// *Action: Check the group name.
44739, 00000, "Cannot drop the last group."
// *Cause: An attempt was made to drop the last group in the index.
// *Action: Use the DROP INDEX statement instead.
44740, 00000, "Parameter %s is already registered."
// *Cause: The parameter name specified was already registered.
// *Action: Either drop the existing parameter or use a different parameter
// name.
44741, 00000, "Cannot drop a group whose tables are shared by other group(s)."
// *Cause: An attempt was made to drop a group whose tables are shared by other group(s).
// *Action: First drop group(s) with shared table(s) from this group.
44742, 00000, "Cannot alter columns of a table that is shared by other group(s)."
// *Cause: An attempt was made to add columns to, modify columns of, or drop columns
// from a table shared by other group(s).
// *Action: First drop group(s) with shared table(s) from this group and then proceed with this operation.
44743,00000, "Cannot alter columns of a dependent shared table."
// *Cause: An attempt was made to add columns to, modify columns of, or drop columns
// from a dependent shared table. One can only add columns to, modify columns of,
// or drop columns from the original shared table.
// *Action: Use the group name of the original shared table while executing this operation.
44744, 00000, "Cannot have more than one drop, add or modify operations in an ALTER INDEX statement."
// *Cause: An attempt was made to have more than one add, modify, or drop
// column or group operations in the ALTER INDEX statement.
// *Action: Use multiple ALTER INDEX statements instead.
44745, 00000, "Cannot add or drop columns to or from multiple tables."
// *Cause: An attempt was made to add or drop columns to or from multiple
// tables in a single ALTER INDEX statement.
// *Action: Use multiple ALTER INDEX statements instead.
44746, 00000, "Missing XMLTABLE in GROUP clause."
// *Cause: An attempt was made to create or add a group without XMLTABLE.
// *Action: Add required XMLTABLE clause to the GROUP clause.
44747, 00000, "An XMLIndex with a structured component cannot be specified with ASYNC."
// *Cause: An attempt was made to specify ASYNC parameter for an XMLIndex with a
// structured component.
// *Action: Use valid parameters for XMLIndex with a structured component.
44748, 00000, "Invalid name for GROUP."
// *Cause: An attempt was made to create a GROUP with invalid name.
// *Action: Use a valid name for the GROUP.
44749, 00000, "Missing PATH for the COLUMN."
// *Cause: An attempt was made to create a COLUMN without PATH.
// *Action: Specify PATH for the COLUMN definition.
44750, 00000, "Cannot create secondary index on unstructured component of XMLIndex."
// *Cause: An attempt was made to create a secondary index on the
// unstructured component of an XMLIndex when the XMLIndex does not
// have an unstructured component.
// *Action: Alter XMLIndex to add an unstructured component.
/
/ Reserved 44751 - 44770 for In Place Schema Evolution
/
44751, 00000, "XML schema enumeration index is out of range"
// *Cause: The enumeration item corresponding to the enumeration index
// could not be found in the XML schema.
// *Action: If the XML schema has been evolved, try restarting the client
// that performed the evolution.
44752, 00000, "New element '%s' in complex type '%s' has the same qualified name as another element"
// *Cause: The new element that was added to a complex type by in-place XML
// schema evolution had the same qualified name as another element
// in the same complex type or in one of its ancestor complex types.
// *Action: Try adding an element with a different qualified name.
44753, 00000, "Change to minOccurs attribute of element '%s' is illegal"
// *Cause: The value of attribute minOccurs on an element could not be
// increased by in-place XML schema evolution.
// *Action: Do not increase the value of attribute minOccurs.
44754, 00000, "Change to maxOccurs attribute of element '%s' is illegal"
// *Cause: The value of attribute maxOccurs on an element could not be
// decreased by in-place XML schema evolution.
// *Action: Do not decrease the value of attribute maxOccurs.
44755, 00000, "Change to complexType property of element '%s' is illegal"
// *Cause: The complexType property on an element could not be
// changed by in-place XML schema evolution.
// *Action: Do not change the complexType property.
44756, 00000, "Change to SQLType attribute of element '%s' is illegal"
// *Cause: The SQLType property on an element in a binary XML schema could
// not be changed by in-place XML schema evolution.
// *Action: Do not change the SQLType property.
/
/ Reserved 44771 - 44799 for DBMS_SERVICE errors
/
44771, 0000, "Invalid name for a container database."
// *Document: Yes
// *Cause: The service operation failed.
// *Action: Check the name of the container database.
44772, 0000, "Cluster Ready Services (CRS) operation failed"
// *Document: Yes
// *Cause: The CRS operation failed.
// *Action: Check the trace file and the CRS daemon log file for details.
44773, 0000, "Cannot perform requested service operation."
// *Document: Yes
// *Cause: The consolidated database was not open. The operation was not
// performed.
// *Action: Open the consolidated database.
44774, 0000, "Pluggable database attribute cannot be changed."
// *Document: Yes
// *Cause: The attempted operation was invalid for a consolidated
// database.
// *Action: PDB attribute of a service cannot be changed.
44775, 0000, "Pluggable database service cannot be created."
// *Document: Yes
// *Cause: The attempted pluggable database operation failed.
// *Action: Check the trace file for details.
44776, 0000, "Pluggable database service cannot be deleted."
// *Document: Yes
// *Cause: The attempted pluggable database operation failed.
// *Action: Check the trace file for details.
44777, 0000, "Pluggable database service cannot be started."
// *Document: Yes
// *Cause: The attempted pluggable database operation failed.
// *Action: Check the trace file for details.
44778, 0000, "Invalid value for service attribute retention_time."
// *Document: Yes
// *Cause: The attempted operation failed.
// *Action: The value for the service attribute 'retention_time' must be greater
// than the value of the service attribute 'replay_initiation_timeout'.
44779, 0000, "Invalid value for service attribute replay_initiation_timeout."
// *Document: Yes
// *Cause: The attempted operation failed.
// *Action: The value for the service attribute 'replay_initiation_timeout'
// must be greater than the value of the service attribute 'failover_delay'.
44780, 0000, "Invalid value for service attribute commit_outcome."
// *Document: Yes
// *Cause: The attempted operation failed.
// *Action: The value for the service attribute 'commit_outcome' cannot be disabled
// if the service attribute 'failover_type' has the value 'transaction'.
44781, 0000, "Invalid value for service attribute aq_ha_notifications."
// *Document: Yes
// *Cause: The attempted operation failed.
// *Action: The value for the service attribute 'aq_ha_notifications' cannot be disabled
// if the service attribute 'failover_type' has the value 'transaction'.
44782, 0000, "Cluster Ready Services (CRS) service operation failed - reason: %s."
// *Document: Yes
// *Cause: The attempted CRS service operation failed.
// *Action: Check the trace file for details.
44783, 0000, "The maximum number of runtime load balancing services exceeded."
// *Document: Yes
// *Cause: The number of runtime load balancing services reached the maximum allowed.
// *Action: N/A
44784, 0000, "Service cannot be deleted."
// *Document: Yes
// *Cause: The attempted service operation failed.
// *Action: Internal services and the database service cannot be deleted.
44785, 0000, "Service attribute commit_outcome cannot be specified for the database or Pluggable Database service."
// *Document: Yes
// *Cause: The attempted service operation failed.
// *Action: None
44786, 0000, "Service operation cannot be completed."
// *Document: Yes
// *Cause: The service was not imported successfully while plugging in the pluggable database or the service is defined in a different pluggable database.
// *Action: Connect to the correct pluggable database and re-execute the service operation.
44787, 0000, "Service cannot be switched into."
// *Document: Yes
// *Cause: The service did not exist in the new pluggable database or the service was not started in the pluggable database.
// *Action: Use a valid service name for the pluggable database or start the service in the pluggable database first.
44789, 0000, "Service cannot be switched into."
// *Document: Yes
// *Cause: One of the verification checks failed.
// *Action: Check the previous error message.
44790, 0000, "exceeded maximum GUID length"
// *Document: Yes
// *Cause: The total length of a globally unique identifier (GUID) exceeded 16 characters.
// *Action: Specify a GUID with the correct length.
44791, 0000, "Drain timeout or stop option cannot be specified for a different database instance."
// *Document: Yes
// *Cause: Drain timeout and stop option could not be used for remote operations.
// *Action: Connect to the correct database instance to use drain timeout or stop option.
44792, 0000, "cannot initialize Oracle Call Interface (OCI) environment"
// *Document: Yes
// *Cause: There was not enough memory available.
// *Action: Configure the Oracle database with more memory.
44793, 0000, "cannot stop internal services"
// *Document: Yes
// *Cause: The user tried to stop an internal service.
// *Action: None
/
/ Reserved 44800 - 44849 for DBMS_WLM errors
/
44800, 0000, "Number of classifiers cannot be NULL"
// *Document: Yes
// *Cause: The num_classifiers argument was found to be NULL.
// *Action: Provide a non-NULL num_classifiers.
44801, 0000, "NULL classifier list not permitted"
// *Document: Yes
// *Cause: The wlm_classifiers argument was found to be NULL.
// *Action: Provide a non-NULL wlm_classifiers.
44802, 0000, "No new plan (classifier list) has been submitted"
// *Document: Yes
// *Cause: No new plan was created before submission.
// *Action: Create a new plan, followed by adding classifier & PC lists.
44803, 0000, "Plan is in transition (about to be activated)"
// *Document: Yes
// *Cause: New plan was attempted to be created before activating the
// current plan.
// *Action: Completely submit the current plan and activate it.
44804, 0000, "Plan is not created yet"
// *Document: Yes
// *Cause: A new plan was not created before submitting the Classifier
// and Performance Class lists.
// *Action: Call dbms_wlm.create_plan first to create the plan.
44805, 0000, "No classifier is present"
// *Document: Yes
// *Cause: The classifier list contained no classifiers.
// *Action: Check the syntax of the classifier list.
44806, 0000, "Extra classifiers are present in list"
// *Document: Yes
// *Cause: More classifiers were present in the list than specified.
// *Action: Only include the number of classifiers less than or equal
// to num_classifiers mentioned in dbms_wlm.create_plan.
44807, 0000, "Peformance Class name is too large"
// *Document: Yes
// *Cause: The Performance Class name was larger than 32 bytes.
// *Action: Rename the Performance Class to fit within 32 bytes.
44808, 0000, "Work Request Class name is too large"
// *Document: Yes
// *Cause: The Work Request Class name was larger than 32 bytes.
// *Action: Rename the Work Request Class to fit within 32 bytes.
44809, 0000, "No expression is present for classifier"
// *Document: Yes
// *Cause: This classifiers contained no expression. It should
// contain one more more expressions.
// *Action: Check syntax in the classifier list.
44810, 0000, "No parameter is present for expression"
// *Document: Yes
// *Cause: This expression contained no paramaters or attribute values.
// It should contain one or more attribute values. Attributes can
// be SERVICE_NAME, MODULE, ACTION, PROGRAM or USER.
// *Action: Check syntax in the classifier list.
44811, 0000, "Service name is too large"
// *Document: Yes
// *Cause: The service name mentioned in the parameter list was too large.
// *Action: Check the service name.
44812, 0000, "Module name is too large"
// *Document: Yes
// *Cause: The module name mentioned in the parameter list was too large.
// *Action: Check the module name.
44813, 0000, "Action name is too large"
// *Document: Yes
// *Cause: The action name mentioned in the parameter list was too large.
// *Action: Check the action name.
44814, 0000, "Program name is too large"
// *Document: Yes
// *Cause: The program name mentioned in the parameter list was too large.
// *Action: Check the program name.
44815, 0000, "User name is too large"
// *Document: Yes
// *Cause: The user name mentioned in the parameter list was too large.
// *Action: Check the user name.
44816, 0000, "Number of Performance Classes is less than specified"
// *Document: Yes
// *Cause: The number of Performance Classes submitted were less than
// what was specified.
// *Action: Submit the full list of Performance Classes.
44817, 0000, "Classifier list is too large"
// *Document: Yes
// *Cause: The length of the classifier list was greater than 4000 bytes.
// *Action: Break the list into two lists before submission.
44818, 0000, "General failure"
// *Document: Yes
// *Cause: There was an unknown failure.
// *Action: Contact Oracle Support Services.
44819, 0000, "Execution of this WLM function is denied"
// *Document: Yes
// *Cause: Either a WLM plan was being loaded from another instance,
// or the strict order of the PL/SQL calls
// for loading WLM plan was not followed.
// *Action: Check if another session is also concurrently trying to load
// a WLM plan. If that is not true, check the order in which you
// are making these PL/SQL calls to load your WLM plan.
44820, 0000, "Number of Work Request Classes is less than specified"
// *Document: Yes
// *Cause: The number of Work Request Classes submitted were less than
// what was specified.
// *Action: Submit the full list of Work Request Classes.
44821, 0000, "Number of classifiers is too large"
// *Document: Yes
// *Cause: A very large number ( > 1024) of classifiers were requested.
// *Action: Submit a smaller ( < 1024) number of classifiers.
44822, 0000, "QoS Resource Manager plan does not exist in database \"%s\""
// *Document: Yes
// *Cause: QoS Resource Manager plan did not exist in this database.
// *Action: Rerun CATPROC.SQL to create the plan.
44823, 0000, "The QoS Resource Manager plan is not in use"
// *Document: Yes
// *Cause: The QoS Resource Manager plan was not in use.
// *Action: Correct the setting of the current Resource Manager plan
// and try again.
44824, 0000, "Resource Manager is disabled"
// *Document: Yes
// *Cause: Resource Manager was turned off.
// *Action: Reenable the Resource Manager and retry the operation.
44825, 0000, "Classifier plan does not match across instances"
// *Document: Yes
// *Cause: Classifier plan was not the same across instances.
// *Action: Resubmit the classifier plan and try again.
44826, 0000, "Number of Performance Classes is more than what was specified."
// *Document: Yes
// *Cause: The number of Performance Classes submitted were more than
// what was specified.
// *Action: Submit only the specified number of Performance Classes.
44827, 0000, "Number of Performance Classes is too large"
// *Document: Yes
// *Cause: A large number ( >= 50) of Performance Classes were requested.
// *Action: Submit a smaller ( < 50) number of Performance Classes.
/
/ 44850 - 44900 reserved for GSM related error codes.
/
44850, 0000, "attempt to set a bad status %s [%s]"
// *Document: Yes
// *Cause: There was an internal Global Service Manager (GSM) error.
// *Action: Contact Oracle Support Services.
44851, 0000, "\"%s\" is not a valid name for a database"
// *Document: Yes
// *Cause: The specified database name was not valid.
// *Action: Provide a valid database name.
44852, 0000, "maximum number of regions exceeded"
// *Document: Yes
// *Cause: The maximum number of regions was exceeded.
// *Action: Check the catalog to see if you can remove unused regions.
44853, 0000, "maximum number of valid nodes for VNCR exceeded"
// *Document: Yes
// *Cause: The maximum number of nodes for valid node checking for
// registration (VNCR) was exceeded.
// *Action: Check the catalog to see if you can remove unused nodes.
44854, 0000, "catalog has already been created"
// *Document: Yes
// *Cause: This database already contained the cloud catalog.
// *Action: Make sure that the specified database name is correct and, if
// yes, delete and re-create the catalog.
44855, 0000, "cloud name is not valid"
// *Document: Yes
// *Cause: The specified cloud name contained invalid characters or was too
// long.
// *Action: Provide a valid (or shorter) cloud name.
44856, 0000, "catalog service name is not valid"
// *Document: Yes
// *Cause: There was an internal Global Service Manager (GSM) error.
// *Action: Contact Oracle Support Services.
44857, 0000, "cloud \"%s\" does not exist"
// *Document: Yes
// *Cause: The specified cloud name did not match the one found in the
// catalog.
// *Action: Provide a valid cloud name.
44858, 0000, "cannot remove catalog"
// *Document: Yes
// *Cause: The catalog contained one or more database or Global Service
// Manager (GSM) objects.
// *Action: Remove the database and GSM objects from the catalog.
44859, 0000, "GSM \"%s\" is already defined in the catalog"
// *Document: Yes
// *Cause: The specified Global Service Manager (GSM) was already in
// existence in the catalog.
// *Action: Check the specified object name.
44860, 0000, "Region \"%s\" was not found in the catalog."
// *Document: Yes
// *Cause: The specified region was not found in the catalog.
// *Action: Check the specified object name.
44861, 0000, "invalid use of REMOVE VNCR command"
// *Document: Yes
// *Cause: A valid node and group name were specified in the same command.
// *Action: Provide either a valid node or group name.
44862, 0000, "region name and buddy region name cannot be the same"
// *Document: Yes
// *Cause: A region was specified as buddy for itself.
// *Action: Provide a valid buddy region name.
44863, 0000, "region \"%s\" is the last region and cannot be removed"
// *Document: Yes
// *Cause: The last region could not be removed from the cloud catalog.
// *Action: No action is required.
44864, 0000, "cannot remove region because it is still being used by a GSM"
// *Document: Yes
// *Cause: The region contained databases or Global Service Manager (GSM).
// *Action: Remove the database and GSM objects from the region first.
44865, 0000, "cannot remove GDS pool because it is still being used by a database or service"
// *Document: Yes
// *Cause: The Global Data Services (GDS) pool contained databases or
// services.
// *Action: Remove the databases and services from the GDS pool.
44866, 0000, "pool \"%s\" can only contain databases that belong to a Data Guard broker configuration"
// *Document: Yes
// *Cause: An attempt was made to add a database that does not belong to a
// Data Guard broker configuration to a Data Guard broker pool.
// *Action: None.
44867, 0000, "GDS pool already contains database \"%s\""
// *Document: Yes
// *Cause: The database or service was already in the Global Data
// Services (GDS) pool.
// *Action: None.
44868, 0000, "pool \"%s\" is a pool that contains a Data Guard broker configuration; Databases that do not belong to a broker configuration cannot be added to this pool."
// *Document: Yes
// *Cause: An attempt was made to add a database to a pool that contains
// a Data Guard broker configuration.
// *Action: None.
44869, 0000, "cannot build net service name with \"%s\ because it is too long"
// *Document: Yes
// *Cause: The automatically created network service name was too long.
// *Action: Use a shorter network domain name.
44870, 0000, "The \"role\" property is only supported for pools that contain a Data Guard broker configuration."
// *Document: Yes
// *Cause: ROLE was specified for a pool that did not contain a Data Guard
// broker configuration.
// *Action: None.
44871, 0000, "This operation cannot be performed on PREFERRED_ALL service \"%s\"."
// *Document: Yes
// *Cause: The service was created with the PREFERRED_ALL option.
// *Action: Do not perform this operation on a PREFERRED_ALL service.
44872, 0000, "The same name \"%s\" cannot be used for both source and target databases."
// *Document: Yes
// *Cause: The source and target parameters of MOVE SERVICE were the same.
// *Action: Check the parameters and try again.
44873, 0000, "database \"%s\" already offers the service"
// *Document: Yes
// *Cause: An attempt was made to add a service to a database that already
// offered the service.
// *Action: No action is required.
44874, 0000, "service \"%s\" not offerered by database \"%s\""
// *Document: Yes
// *Cause: An attempt was made to start or stop a service on a database
// that does not offer the service.
// *Action: None.
44875, 0000, "database-related service parameters exceed the maximum allowed parameter length (1024 bytes)"
// *Document: Yes
// *Cause: The specified database-related service parameters were not
// valid.
// *Action: Check the parameters and try again.
44876, 0000, "service %s is running"
// *Document: Yes
// *Cause: The specified service was running.
// *Action: This message is informational only.
44877, 0000, "service \"%s\" is not enabled on database \"%s\""
// *Document: Yes
// *Cause: The service could not be started on the database because it was
// disabled.
// *Action: Enable the service.
44878, 0000, "The database current lag is too high for the service \"%s\"."
// *Document: Yes
// *Cause: The service could not be started on the standby database because
// the database current lag exceeds the service lag.
// *Action: The standby current lag needs to be reduced.
44879, 0000, "A region name has not been provided."
// *Document: Yes
// *Cause: An attempt was made to add a new Global Service Manager (GSM)
// without providing a region. When there is more than one existing
// region, a region name must be provided.
// *Action: Check the syntax and rerun the command.
44880, 0000, "catalog has not yet been created"
// *Document: Yes
// *Cause: An attempt was made to modify the catalog, but it does not yet
// exist.
// *Action: Create the catalog before trying to modify it.
44881, 0000, "GDS pool is not empty"
// *Document: Yes
// *Cause: An attempt was made to add broker configuration to a Global
// Data Services (GDS) pool that already contained a database.
// This is not allowed.
// *Action: Either remove all databases from the Global Data Services (GDS)
// pool or create a new GDS pool.
44882, 0000, "The name \"%s\" is not valid for a GDS pool."
// *Document: Yes
// *Cause: The name of the specified Global Data Services (GDS) pool was
// not valid.
// *Action: Check the name and try again.
44883, 0000, "The name \"%s\" is not valid for a region."
// *Document: Yes
// *Cause: The name of the specified region was not valid.
// *Action: Check the name and try again.
44884, 0000, "The name \"%s\" is not valid for a service."
// *Document: Yes
// *Cause: The name of the specified service was not valid.
// *Action: Check the name and try again.
44885, 0000, "invalid VNCR name %s"
// *Document: Yes
// *Cause: The name specified for the valid node checking for registration
// (VNCR) was not valid.
// *Action: Check the name and try again.
44886, 0000, "The name \"%s\" is not valid for a VNCR group."
// *Document: Yes
// *Cause: The name specified for the valid node checking for registration
// (VNCR) group was not valid.
// *Action: Check the name and try again.
44887, 0000, "The name \"%s\" is not valid for a GSM."
// *Document: Yes
// *Cause: The name of the specified Global Service Manager (GSM) was not
// valid.
44888, 0000, "The name \"%s\" is not valid for a GSM user."
// *Document: Yes
// *Cause: The name of the specified Global Service Manager (GSM) was not
// valid.
// *Action: Check the name and try again.
44889, 0000, "Region \"%s\" is already defined in the catalog."
// *Document: Yes
// *Cause: The specified region was already in existence in the catalog.
// *Action: Check the specified region name.
44890, 0000, "GDS pool \"%s\" is already defined in the catalog."
// *Document: Yes
// *Cause: The specified Global Data Services (GDS) pool was already in
// existence in the catalog.
// *Action: Check the specified pool name.
44891, 0000, "GSM \"%s\" was not found in the catalog"
// *Document: Yes
// *Cause: The specified region was not found in the catalog.
// *Action: Check the specified region name.
44892, 0000, "GDS pool \"%s\" was not found in the catalog."
// *Document: Yes
// *Cause: The specified Global Data Services (GDS) pool was not found
// in the catalog.
// *Action: Check the specified pool name.
44893, 0000, "Database \"%s\" was not found in pool \"%s\"."
// *Document: Yes
// *Cause: The specified database was not found in the pool.
// *Action: Check the specified database name.
44894, 0000, "Service \"%s\" was not found in the catalog."
// *Document: Yes
// *Cause: The specified service was not found in the catalog.
// *Action: Check the specified service name.
44895, 0000, "cannot remove region because it is still being used by a database"
// *Document: Yes
// *Cause: The region contained databases.
// *Action: Remove the database objects from the region.
44896, 0000, "GDS pool already contains service \"%s\""
// *Document: Yes
// *Cause: The service was already in the Global Data Services (GDS) pool.
// *Action: None.
44897, 0000, "The \"lag\" property is only supported for pools that contain a Data Guard broker configuration."
// *Document: Yes
// *Cause: LAG was specified for a pool that did not contain a Data Guard
// broker configuration.
// *Action: None.
44898, 0000, "The \"failover_primary\" property is only supported for pools that contain a Data Guard broker configuration."
// *Document: Yes
// *Cause: FAILOVER_PRIMARY was specified for a pool that did not contain a
// Data Guard broker configuration.
// *Action: None.
44899, 0000, "VNCR name \"%s\" is already defined in the catalog."
// *Document: Yes
// *Cause: The specified valid node checking for registration (VNCR) name
// was already in existence in the catalog.
// *Action: Check the specified VNCR name.
44900, 0000, "Identifier \"%s\" is too long."
// *Document: Yes
// *Cause: The specified identifier exceeded the maximum allowed length.
// *Action: Use a shorter identifier name
/
/ 44901 - 44950 reserved for XML DB LINKS related error codes.
/
//
44901, 0000, "Unable to resolve symbolic link \"%s\""
// *Document: YES
// *Cause: The system is unable to resolve the specified symbolic link.
// *Action: Check the definition of the symbolic link to ensure that this
// refers to a valid resource.
44902, 0000, "Too many steps in resolving symbolic link \"%s\""
// *Document: YES
// *Cause: This error is raised when the system is unable to fully resolve
// a path with symbolic links within a reasonable number of steps.
// It could be due to cycles in definitions of symbolic links or
// very long chains of symbolic links to symbolic links.
// *Action: Remove any cycles in symbolic link definitions. If there are no
// cycles, reduce the length of chains of symbolic links to symbolic
// links.
44903, 0000, "Cannot create hard link to specified resource"
// *Document: YES
// *Cause: The system cannot create a hard link to the specified resource.
// *Action: Check the configuration parameter(s) to verify the restrictions
// on creating hard links to folder or non-folder resources.
44904, 0000, "target path in document link exceeds maximum length"
// *Document: YES
// *Cause: Target path length exceeds the maximum which can be stored
// to disk.
// *Action: Reduce target path to smaller length
44905, 0000, "extended link type not supported"
// *Document: YES
// *Cause: XLink type attribute is extended.
// *Action: Remove extended link, or replace with simple link.
44906, 0000, "unable to resolve target in document link"
// *Document: YES
// *Cause: target path does not resolve to valid resource.
// *Action: check validity of target path.
44907, 0000, "can not delete with incoming hard document links"
// *Document: YES
// *Cause: there is a hard document link with this resource as the target.
// *Action: query DOCUMENT_LINKS view to see which resource has a hard
// link to this resource. Change the document link in the
// source resource accordingly.
44908, 0000, "found a loop in XInclude elements while expanding %s"
// *Document: YES
// *Cause: There is a loop in XInclude elements within the document.
// *Action: Remove the loop in XInclude elements.
44909, 0000, "href attribute is required within XInclude element"
// *Document: YES
// *Cause: The href attribute is missing within XInclude element.
// *Action: Add the href attribute.
44910, 0000, "xpointer not supported within XInclude element"
// *Document: YES
// *Cause: The xpointer attribute is specified within XInclude element.
// *Action: Remove the xpointer attribute.
44911, 0000, "exceeded maximum depth of nested xinclude expansion"
// *Document: YES
// *Cause: The depth of nested xinclude expansion has exceeded system limit.
// *Action: Reduce the depth of nested xinclude expansion.
44912, 0000, "invalid or unsupported xpath expression %s"
// *Document: YES
// *Cause: The specified xpath is either invalid or unsupported in this context.
// *Action: Change the xpath expression.
44913, 0000, "error while processing XInclude %s"
// *Document: YES
// *Cause: There was an error while processing the specified XInclude.
// *Action: Ensure that the XInclude attributes are correct.
44914, 0000, "schema XPointer exceeds maximum length"
// *Document: YES
// *Cause: The XPointer was too long with the schema URL and element name.
// *Action: Use a shorter name.
//
44915, 0000, "cannot rename virtual folders"
// *Document: YES
// *Cause: Renaming virtual folders was not supported.
// *Action: Create a new virtual folder instead.
//
44916, 0000, "cannot recursively delete virtual folders"
// *Document: YES
// *Cause: Recursive deletion of virtual folders was not supported.
// *Action: Delete components of the virtual folder first.
//
44917, 0000, "Resources cannot point to resources."
// *Document: YES
// *Cause: A REF was being set to point to the resource table."
// *Action: This is not supported.
//
44918, 0000, "The source of a copy cannot be an ancestor of the destination."
// *Document: YES
// *Cause: The destination of a copy was an ancestor of the source.
// *Action: Correct the source and destination of the copy.
//
44919, 0000, "cannot overwrite existing resource"
// *Document: YES
// *Cause: Overwriting an existing resource was prohibited.
// *Action: Specify a new destination or indicate that overwrite is permitted.
//
44920, 0000, "The source and destination of a copy or move cannot be the same."
// *Document: YES
// *Cause: A copy or move was attempted with the same source and destination.
// *Action: Use the correct source and destination.
//
44921, 0000, "The XPath returns none or more than one node."
//
// *Document: YES
// *Cause: The XPath did not map to a single node.
// *Action: Specify a path that maps to a single node.
//
44922, 0000, "The XPath expression must evaluate to a scalar type."
// *Document: YES
// *Cause: The XPath did not map to a scalar type.
// *Action: Specify a path that maps to a scalar type.
//
44951, 0000, "ASSM BasicFile Bulk reclaim event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: NA
44952, 0000, "ASSM BasicFile Enqueue Hash reclaim event"
// *Document: NO
// *Cause: This is an internal event, and must be enabled
// only under the supervision of Oracle support or development.
// *Action: NA
/
/ 45000 - 45099 reserved for SecureFile Archive
/
45001, 0000, "SecureFile archive implicit not allowed"
// *Document: YES
// *Cause: A SecureFile was archived and implicit retrieval was not allowed.
// *Action: Retrieve the SecureFile with a Get operation.
45002, 00000, "Content ID not found in the DBFS HS"
// *Cause: The content ID was invalid or was already deleted.
// *Action: No action required.
//
45003, 00000, "DBFS HS: Invalid checksum, potential data corruption"
// *Cause: Potential data corruption.
// *Action: No action required.
//
45004, 00000, "DBFS HS SBT Error"
// *Cause: Error related to SBT Tape library.
// *Action: Refer to error log for more details.
//
45005, 00000, "DBFS HS invalid store"
// *Cause: Error related to DBFS HS Store.
// *Action: Check that the store name and store parameters are valid values.
//
45053, 0000, "Internal Debugging Event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
45097, 0000, "SECUREFILE LOBs DBFS HS streaming test event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
45098, 0000, "SECUREFILE LOBs DBFS HS debug event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
45099, 0000, "SECUREFILE LOBs DBFS HS test event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
/
/ BEGIN error messages reserved for the Recovery Appliance (45100 - 45299)
/
45100, 0000, "Database incarnation went from %s to %s. Recovery Appliance repair is required."
// *Document: YES
// *Cause: A 'startup resetlogs' command was executed on the Recovery Appliance.
// This caused old metadata to be used to refer to the storage locations.
// Before the Recovery Appliance can be started, a repair
// operation must be run to synchronize its metadata with its
// storage.
// *Action: Execute DBMS_RA.STARTUP_RECOVERY_APPLIANCE. If any incidents
// are logged during the subsequent repair, they will need to be
// corrected.
// Once they have been corrected, repeat the execution of
// DBMS_RA.STARTUP_RECOVERY_APPLIANCE.
45101, 0000, "Bad chunk number. Expected %s, but received %s."
// *Document: NO
// *Cause: During a purge, a reservation was made without specifying a chunk
// count.
// *Action: N/A this is an internal error.
45102, 0000, "unable to allocate %s bytes of storage"
// *Document: YES
// *Cause: The Recovery Appliance was unable to allocate additional
// disk space in the storage location of the database for the current
// allocation. This condition may be due to one of the following
// reasons: * Guaranteed copy has been specified for a database
// and there are too many backups waiting to be copied to tape.
// * The metadata of the Recovery Appliance is being repaired.
// * Nothing can be purged within the storage location of the database.
// *Action: Add additional storage to the storage location of the database.
45103, 0000, "storage location not found"
// *Document: NO
// *Cause: A storage location was not found for storing disk files
// associated with the current database.
// *Action: N/A this is an internal error.
45104, 0000, "backup piece not found"
// *Document: NO
// *Cause: An attempt was made to delete a backup piece, but the backup
// piece did not exist.
// *Action: N/A this is an internal error.
45105, 0000, "Cannot reserve space except when purging."
// *Document: NO
// *Cause: An attempt was made to reserve space in a storage location
// while not performing a purge task. Reservations are only
// supported for purge tasks.
// *Action: N/A this is an internal error.
45106, 0000, "illegal virtual backup ID: %s"
// *Document: NO
// *Cause: The specified virtual backup ID does not correspond to a valid
// virtual backup.
// *Action: N/A this is an internal error.
45107, 0000, "Incremental backup does not fit into block pool at this time."
// *Document: NO
// *Cause: The backup being processed was an incremental backup and
// could not
// be placed into the block pool until other backups are included.
// This backup should be retried later.
// *Action: N/A this is an internal error.
45108, 0000, "Backup cannot be included in block pool."
// *Document: NO
// *Cause: The backup being processed could not be included into the block
// pool because the SCN values did not match nor will they ever.
// This can happen if the backup was previously included or if
// the backup is older than other content already in the block pool.
// *Action: N/A this is an internal error.
45109, 0000, "metadata for database %s; file %s is corrupt"
// *Document: YES
// *Cause: Internal self checks found corruption in the metadata
// used to manage the Recovery Appliance block pool.
// *Action: Contact Oracle Support Services and provide
// trace and alert files.
45110, 0000, "pending interrupt detected"
// *Document: NO
// *Cause: A task was running that prevented a higher priority task
// from running.
// *Action: None. This is not a user visible exception.
45111, 0000, "Task %s is being terminated after %s restarts."
// *Document: YES
// *Cause: A Recovery Appliance task generated too many errors.
// Following an error, a task is normally restarted. If it
// fails to restart after 10 tries, the Recovery Appliance
// marks the task as broken and no longer tries to restart it.
// *Action: Correct the error that terminated the task and request the task
// to be rerun.
45112, 0000, "retry current task"
// *Document: NO
// *Cause: The task encountered a problem that prevented it from
// completing. Re-executing the task after a pause should
// enable a clean run. Not getting a write lock is one example
// of why a task must be retried.
// *Action: None. This is not a user visible exception.
45113, 0000, "Recovery Appliance internal error %s"
// *Document: YES
// *Cause: An internal error was encountered.
// *Action: Contact Oracle Support Services
// and provide trace and alert files.
45114, 0000, "file \"%s\" not referenced by metadata for storage location %s"
// *Document: YES
// *Cause: A consistency check performed by the check files task of the
// Recovery Appliance identified that the file was not
// being referenced by the metadata of the Recovery Appliance.
// Without these references, the Recovery Appliance cannot manage the
// file.
// *Action: If the file was inadvertently put in the storage location,
// it should be moved elsewhere. If the file has been separated
// from its metadata, contact Oracle Support Services and provide
// trace and alert files.
45115, 0000, "database with DB_KEY %s is too big to move."
// *Document: YES
// *Cause: An attempt was made to move the specified database to a new
// storage
// location, but the database could not be shrunk to within its
// storage reservation and still preserve its retention window.
// *Action: Increase the storage reservation for the database or shrink
// its retention window.
45116, 0000, "anomaly detected while reading metadata for backup piece with BP_KEY %s"
// *Document: YES
// *Cause: A transient anomaly was found in the backup data.
// *Action: If the anomaly persists, find a copy of the backup piece, if
// available, and reinsert it into the storage location. If no
// copy is available, generate a new level 0 backup for all data
// files in the backup piece.
45117, 0000, "There is not enough space for this task."
// *Document: NO
// *Cause: The task did not have enough file space to proceed.
// Some tasks may reserve space to free additional space.
// *Action: None. This is not a user visible exception.
45118, 0000, "servlet timeout error"
// *Document: YES
// *Cause: A restore task was waiting on a servlet process to pass
// data to a client. The time allotted for responding was
// exceeded and the restore task was aborted.
// *Action: This can be a common occurrence if the client cancels the
// restore request. Reissue the request.
45119, 0000, "received a nonexistent operation for privilege change"
// *Cause: An illegal option was specified.
// *Action: BACKUP, RECONCILE, READ, WRITE, and NULL are only
// supported values.
45120, 0000, "operation failed due to insufficient space"
// *Cause: The storage location was too small to support the new database.
// *Action: increase the size of your storage location or reduce
// DISK_RESERVED_SPACE in the protection policy
45121, 0000, "received an incorrect value for a privilege change"
// *Cause: An internal error was detected while granting or revoking
// privileges.
// *Action: Contact Oracle Support Services
// and provide trace and alert files.
45122, 0000, "invalid size or number specified"
// *Cause: An invalid size or number was specified.
// *Action: Use a non-NULL or number greater than 0.
45123, 0000, "The name %s (%s) already exists."
// *Cause: The object name was not unique.
// *Action: Specify a unique name for this object.
45124, 0000, "Object %s (%s) is referenced and cannot be deleted."
// *Cause: The object was in use by a storage location or database.
// *Action: Delete all objects that reference this item.
45125, 0000, "Object %s (%s) did not exist."
// *Cause: The object name did not exist.
// *Action: Specify an existing object.
45126, 0000, "failed to delete database %s"
// *Cause: The database could not be deleted. An unexpected error has
// occurred.
// *Action: Examine the associated messages to determine the cause of
// the exception.
45127, 0000, "Required parameter %s must be specified."
// *Cause: The parameter was not supplied to API routine.
// *Action: Rerun the command specifying the missing parameter.
45128, 0000, "backup piece %s in database %s is not referenced by the catalog"
// *Cause: A consistency check performed by the check files task of the
// Recovery Appliance identified that the specified backup piece
// was unreferenced by the RMAN catalog. Without this reference,
// the Recovery Appliance cannot reclaim space used by this piece.
// *Action: Contact Oracle Support Services.
45129, 0000, "expected %s bytes used by database %s in storage location %s, but found %s bytes used"
// *Cause: A consistency check performed by the check files task of the
// Recovery Appliance identified that the storage usage of the
// database in a storage location did not match the sum of
// the size of storage pieces assigned to the Recovery Appliance.
// *Action: Contact Oracle Support Services.
45130, 0000, "Storage parameter overlaps with storage in %s."
// *Cause: A parameter for a storage location was specified that overlapped
// storage previously assigned to another storage location.
// *Action: Reissue the command specifying a different location for the
// storage.
45131, 0000, "illegal or unknown restore compression option specified"
// *Cause: The specified compression option was not supported on either
// the Recovery Appliance database or the database providing the
// backup.
// *Action: Query V$RMAN_COMPRESSION_ALGORITHM view to ensure the algorithm
// name matches one of the algorithm names in that table and that
// the option has IS_VALID = 'YES' and that the INITIAL_RELEASE
// column is less than both the Recovery Appliance and the database
// providing the backup. Reissue the command specifying a valid
// compression algorithm name.
45132, 0000, "corrupt block detected in backup piece"
// *Cause: A corrupt block was detected in a backup piece when populating
// the Recovery Appliance block pool.
// *Action: Perform block media recovery on the corrupt blocks of the
// database and do a cumulative level 1 backup.
45133, 0000, "expected %s byte allocation by database %s, but found %s bytes allocated"
// *Cause: A consistency check performed by the check files task of the
// Recovery Appliance found that the storage allocations of the
// database did not match the sum of the size of
// allocations for that database in all storage locations.
// *Action: Contact Oracle Support Services.
45134, 0000, "Communications SGA is exhausted."
// *Document: NO
// *Cause: System Global Area (SGA) for communication buffers has run out.
// *Action: This is informational only. This condition is expected and
// managed by the Recovery Appliance.
45135, 0000, "request terminated by the Recovery Appliance"
// *Document: YES
// *Cause: A request was holding resources needed by the Recovery Appliance
// and was terminated to free those resources. This can be the
// result of a
// lack of disk space or some other resource.
// *Action: Check available disk space, as well as for errors on the
// Recovery Appliance database.
45136, 0000, "invalid value for parameter %s"
// *Cause: The value supplied for the specified parameter was invalid.
// *Action: Check the Recovery Appliance
// documentation and rerun the command with a correct value.
45137, 0000, "unknown platform"
// *Cause: The Recovery Appliance has not received any backups from
// System Backup to Tape (SBT) or through polling. This is
// necessary for the Recovery Appliance to learn about the
// protected platform of the database and for the current
// operation to succeed.
// *Action: Backup a small archived log or other backup using SBT or by
// sending it to the polling location. Then retry this operation.
45138, 0000, "Backup not found."
// *Cause: The specified backup could not be found in the catalog.
// *Action: Please check and specify the correct backup piece key or
// backup set key.
45139, 0000, "A useful backup could not be found to correct this corruption."
// *Cause: A virtual backup piece key was provided, but there was no known
// backup on tape or disk to correct this backup.
// *Action: If the broken backup is the oldest virtual backup for the data
// file, sometimes an even older backup will have the data needed
// to correct the catalog. Find and specify that older backup
// directly.
45140, 0000, "cannot insert backup into catalog"
// *Cause: The specified backup was either not an incremental or not
// in the proper SCN range to correct problems in the catalog.
// *Action: Make sure you have provided the correct key value and find a
// proper incremental backup piece.
45141, 0000, "File \"%s\" was missing from storage location %s."
// *Document: YES
// *Cause: During recovery of the Recovery Appliance, the specified file
// was referenced by the metadata of the Recovery Appliance, but was
// not found in its storage location.
// *Action: The file should be recovered from a replicated Recovery Appliance
// if it exists. If the file has been separated
// from its metadata, then contact Oracle Support Services
// and provide trace and alert files.
45142, 0000, "The Recovery Appliance prerequisite is already set up."
// *Cause: The DBMS_RA_INSTALL procedure was executed to set up
// prerequisite objects for creation of a catalog schema for the
// Recovery Appliance. This error is reported because there can be
// only one user schema that manages the Recovery Appliance for the
// database.
// *Action: To re-create the Recovery Appliance schema in another user schema,
// uninstall the earlier Recovery Appliance schema setup.
45143, 0000, "The Recovery Appliance prerequisite setup administors user name is mismatched."
// *Cause: The DBMS_RA_INSTALL procedure was executed to uninstall the
// Recovery Appliance prerequisite object for the wrong user name.
// *Action: Correct the user name parameter for DBMS_RA_INSTALL and
// reexecute the procedure.
45144, 0000, "Undefined initial replication type for protection policy."
// *Cause: The initial_replication_type was undefined for the protection
// policy.
// *Action: Update the protection policy initial_replication_type with one of
// LAST FULL, ALL, or NONE.
45145, 0000, "Recovery Appliance user %s does not exist."
// *Cause: The Recovery Appliance user did not exist.
// *Action: Specify an existing Recovery Appliance user.
45146, 0000, "Storage location %s needs %s additional bytes of storage."
// *Cause: The metadata of the Recovery Appliance was being repaired following
// a database open with the 'resetlogs' command and the storage
// allocated in the specified storage location was insufficient.
// This may be caused by either an 'update_storage_location' call
// being lost due to the 'resetlogs' command or the storage
// location becoming very low on free storage when the resetlogs
// command was executed.
// *Action: Update the storage location with the specified values and try
// the repair again by executing
// DBMS_RA.STARTUP_RECOVERY_APPLIANCE.
45147, 0000, "Database %s and database %s are both moving."
// *Cause: The metadata of the Recovery Appliance was being repaired following
// a database open with 'resetlogs' and two databases
// were found to be moving between storage locations.
// The Recovery Appliance will only function correctly when one
// database is being moved. This may be caused by an
// 'update_protection_policy' or 'update_db' call being lost due
// to the 'resetlogs' command.
// *Action: Determine the storage locations used by each database and repeat
// any database movements that may have been lost.
45148, 0000, "must fix %s errors before restarting the Recovery Appliance"
// *Cause: During a repair of the metadata of the Recovery Appliance, errors
// were found that precluded the restart of the
// Recovery Appliance.
// *Action: Fix the identified errors and execute
// DBMS_RA.STARTUP_RECOVERY_APPLIANCE to retry the repair.
45149, 0000, "unknown task type: %s"
// *Cause: The Recovery Appliance tried to execute a task
// with an unknown task type.
// *Action: Contact Oracle Support Services.
45150, 0000, "File %s references unknown DBID %s."
// *Cause: During a repair of the metadata of the Recovery Appliance, the
// specified file was found that referenced the specified database
// which was unknown to the Recovery Appliance. This may be caused
// by an 'add_db' call being lost due to a 'resetlogs' command.
// *Action: Repeat the lost 'add_db' call.
45151, 0000, "bad locking protocol for lock %s"
// *Cause: An internal error caused locking to be used incorrectly.
// *Action: Contact Oracle Support Services.
45152, 0000, "bad backup piece format for %s"
// *Cause: During a repair of the metadata of the Recovery Appliance, the
// specified file was found whose type could not be determined.
// *Action: Remove the corrupted file and reexecute
// DBMS_RA.STARTUP_RECOVERY_APPLIANCE.
45153, 0000, "unknown data file %s for DBID %s"
// *Cause: During repair of the metadata of the
// Recovery Appliance, data for the specified database was
// found whose data file could not be found.
// *Action: Using RMAN on the specified database, use the 'resync' command
// to refresh the metadata on the Recovery Appliance and retry the
// restart of the Recovery Appliance.
45154, 0000, "bad Recovery Appliance format found in file %s"
// *Cause: During a repair of the metadata of the Recovery Appliance, a file was
// found in a storage location that was neither a chunk file nor
// a backup piece.
// *Action: Remove the offending file from the storage location of the
// Recovery Appliance and retry the restart of the Recovery Appliance.
45155, 0000, "The Recovery Appliance has not been installed."
// *Cause: The Recovery Appliance was never installed on this database.
// The requested procedure is only supported on the
// Recovery Appliance.
// *Action: Do not attempt the procedure except on the Recovery Appliance.
45156, 0000, "SBT job %s not found"
// *Cause: The specified SBT job was not found.
// *Action: Check if the SBT job has been deleted by user. If so,
// then drop the scheduler job.
45157, 0000, "Parameter value %s (%s) is invalid."
// *Cause: The specified value for the parameter was invalid.
// *Action: Specify a valid value.
45158, 0000, "SBT library %s is not ready."
// *Cause: The specified SBT library was found to not be ready.
// *Action: Check if the library has been paused by user. If so,
// then resume the SBT library.
45159, 0000, "RECOVERY_WINDOW_GOAL is lost for database %s."
// *Cause: A low space condition forced the deletion of backups needed
// to support the recovery window goal for the named database.
// *Action: This is a warning and no action is needed. However, you may
// use DBMS_RA.UPDATE_PROTECTION_POLICY to increase the
// DISK_RESERVED_SPACE value of the database to ensure additional
// backups are saved.
// Select SPACE_USAGE from RA_DATABASE to see how much space is
// currently in use. You should also check for KEEP backups
// consuming space on disk and decide if they should be moved to
// tape or other disk storage. See DBMS_RA.MOVE_BACKUP_PIECE for
// more details.
45160, 0000, "Incremental forever strategy is lost for database %s."
// *Cause: A low space condition has forced the deletion of backup data
// needed to generate the last remaining virtual LEVEL 0 of one or
// more data files. The next client backup will be a full LEVEL 0
// backup, even if LEVEL 1 was specified.
// *Action: This is a warning and no action is needed. However, you may
// use DBMS_RA.UPDATE_DB to increase the RESERVED_SPACE value
// of the database to ensure additional backups are saved.
// Select SPACE_USAGE from RA_DATABASE to see how much space is
// currently in use. You should also check for KEEP backups
// consuming space on disk and decide if they should be moved to
// tape or other disk storage. See DBMS_RA.MOVE_BACKUP_PIECE for
// more details.
45161, 0000, "The backup piece size cannot exceed database DISK_RESERVED_SPACE."
// *Cause: An individual backup piece exceeded the database
// protection policy DISK_RESERVE_SPACE value. A safe
// DISK_RESERVED_SPACE value would exceed the size of the database.
// *Action: Use DBMS_RA.UPDATE_DB to increase the DISK_RESERVED_SPACE
// value of the database.
45162, 0000, "System global area memory is configured incorrectly."
// *Cause: Check initialization parameters LARGE_POOL_SIZE and
// SHARED_POOL_SIZE. The Recovery Appliance will use all of
// LARGE_POOL_SIZE or 20% of SHARED_POOL_SIZE to restore virtual
// or tape backups. The actual space needed is
// NETWORK_CHUNKSIZE * 2 * (number of concurrent restore channels)
// where NETWORK_CHUNKSIZE is set using DBMS_RA.CONFIG.
// Use DBMS_RA.CONFIG to lower NETWORK_CHUNKSIZE or preferably,
// increase either LARGE_POOL_SIZE or SHARED_POOL_SIZE.
// *Action: Check initialization parameters LARGE_POOL_SIZE and
// SHARED_POOL_SIZE and set it correctly.
45163, 0000, "operation is only supported for user %s"
// *Cause: An attempt was made to start the Recovery Appliance
// by a user other than the Recovery Appliance administrator.
// *Action: Only start the Recovery Appliance as the user specified at
// installation time.
45164, 0000, "The Recovery Appliance is not running."
// *Cause: An attempt was made to use the Recovery Appliance, but the
// Recovery Appliance has been deactivated by the administrator.
// *Action: Have the Recovery Appliance administrator execute
// DBMS_RA.STARTUP_RECOVERY_APPLIANCE and retry the operation.
45165, 0000, "Recovery Appliance backup piece with BP_KEY %s is corrupt"
// *Document: YES
// *Cause: Corruption was found in the backup data.
// *Action: Ensure that you have a functioning backup of the affected data
// file. Then delete the corrupt backup piece to clear the
// condition.
45166, 0000, "unable to access file %s"
// *Cause: An attempt was made to access the specified file which resulted
// in an error. An explanation of the error appears in the
// following messages.
// *Action: Verify the correctness of the file. If it is corrupt, either
// delete it or replace it.
45167, 0000, "unable to validate backup piece with BP_KEY %s"
// *Cause: An attempt was made to validate the specified backup piece which
// resulted in an error. An explanation of the error appears in the
// following messages.
// *Action: Verify the correctness of the backup piece. If it is corrupt,
// either delete it or replace it.
45168, 0000, "unexpected scheduler exit while executing task ID %s of type %s"
// *Cause: A task failed with an unexpected error code in the
// Recovery Appliance.
// *Action: Contact Oracle Support Services.
45169, 0000, "unexpected timer process exit"
// *Cause: The timer process failed with an unexpected error code in the
// Recovery Appliance.
// *Action: Contact Oracle Support Services.
45170, 0000, "Storage location %s is too full."
// *Cause: Purging the specified storage location would result in the loss
// of the recovery window goal for one of its databases.
// *Action: Add more storage to the storage location or remove some databases
// from the storage location or reduce the recovery window goal
// for some of the databases in the storage location.
45171, 0000, "The chunk optimization task has not run recently for one or more databases."
// *Cause: The background chunk optimization task had not been performed
// recently for at least one database. This may happen if the
// Recovery Appliance is too overloaded with foreground
// activities to have time to do background tasks.
// *Action: Remove some load from the Recovery Appliance by reducing
// the frequency of backups by protected databases or by offloading
// some of the databases from the Recovery Appliance.
45172, 0000, "The validation task has not run recently for one or more databases."
// *Cause: The background validation task had not been performed recently
// for at least one database. This may happen if the
// Recovery Appliance is too overloaded with foreground
// activities to have time to do background tasks.
// *Action: Remove some load from the Recovery Appliance by reducing
// the frequency of backups by protected databases or by offloading
// some of the databases from the Recovery Appliance.
45173, 0000, "The checkfiles task has not run recently for one or more storage locations."
// *Cause: The background checkfiles task had not been performed recently
// for one or more storage locations. This may happen
// if the Recovery Appliance is too overloaded with
// foreground activities to have time to do background tasks.
// *Action: Remove some load from the Recovery Appliance by reducing
// the frequency of backups by protected databases or by offloading
// some of the databases from the Recovery Appliance.
45174, 0000, "unable to use replication server %s"
// *Cause: While using the Recovery Appliance, either a backup
// failed to be transmitted to the target replicated Recovery Appliance
// or a restore request failed to complete on the
// replicated Recovery Appliance.
// *Action: Check the following error messages to diagnose the actual error.
45175, 0000, "unable to use SBT library %s"
// *Cause: While using the Recovery Appliance, a request failed
// to complete while using the specified System Backup to Tape
// library.
// *Action: Check the following error messages to diagnose the actual error.
45176, 0000, "Replication server %s is not in the paused state."
// *Cause: An attempt was made to update information for a replication
// server that was not in a paused state.
// *Action: Pause the replication server on this Recovery Appliance.
45177, 0000, "unable to find file %s previously found while polling"
// *Cause: A backup piece file previously found in a polling location was
// later not accessible to the Recovery Appliance.
// *Action: If the file was unavailable due to network errors, the file will
// be found again once the network is available. If
// the backup piece was deleted, create a new backup.
45178, 0000, "The allocation unit size cannot be changed."
// *Cause: An attempt was made to move one or more databases into a
// storage location with a different allocation unit size.
// This value comes from the ASM disk group allocation unit size
// specified when creating the disk groups referenced by the
// storage location.
// *Action: Use a storage location with the same minimum allocation
// size as the source. If necessary create new disk groups
// with a matching size before creating a new storage location.
45179, 0000, "The reconcile task has not run recently for database %s."
// *Cause: The background reconcile task had not been performed
// recently for the specified database. This may happen
// if the Recovery Appliance is too overloaded with
// foreground activities to have time to do background tasks.
// *Action: Remove some load from the Recovery Appliance by reducing
// the frequency of backups by protected databases or by offloading
// some of the databases from the Recovery Appliance.
45180, 0000, "The crosscheck task has not run recently for database one or more databases."
// *Cause: The background reconcile task had not been performed
// recently for at least one database. This may happen
// if the Recovery Appliance is too overloaded with
// foreground activities to have time to do background tasks.
// *Action: Remove some load from the Recovery Appliance by reducing
// the frequency of backups by protected databases or by offloading
// some of the databases from the Recovery Appliance.
45181, 0000, "polling found duplicate file name %s"
// *Cause: The given file name has already been included in a storage
// location. There are three possible reasons for this warning.
// * Two databases are contributing to the same polling location
// but their format does not include the DBID.
// * A backup command did not specify a unique format name.
// * Recovery has restored an archived log into that location.
// This is possible when the polling location is the primary
// archive log destination.
// *Action: If the cause is name formatting, then fix the formatting and
// rename the specified files. Polling will then find them again
// and include them. If this was recovery, and the files are true
// duplicates, delete the files. Note that the DELETE_INPUT option
// will not help with these duplicate files because they were
// not copied.
45182, 0000, "database access cannot be granted or revoked using catalog owner or sys "
// *Cause: The catalog owner or sys was specified as the user in the
// DBMS_RA.GRANT_DB_ACCESS and DBMS_RA.REVOKE_DB_ACCESS
// procedures.
// This is not allowed.
// *Action: A different user should be created and granted the necessary
// access.
45183, 0000, "request is blocked by session %s on instance %s"
// *Cause: An API request was made to the Recovery Appliance
// while another API was in progress. Only one API may be
// performed at a time.
// *Action: Wait for the other API to complete or kill the identified session
// before repeating the failed API request.
45184, 0000, "ORA-%s occurred during wallet operation; WRL %s"
// *Cause: An operation on the wallet failed due to the indicated error.
// *Action: Refer to the indicated Oracle message for more information.
45185, 0000, "alias %s not found in %s wallet"
// *Cause: The specified WALLET alias did not appear in the wallet.
// *Action: Check the WALLET alias or create an alias in the wallet for
// the specified attribute and retry the command.
45186, 0000, "current task failed"
// *Document: NO
// *Cause: The task encountered a problem that prevented it from
// completing. Mark the task as failed and continue with next
// task. Giving up copy sbt task after few retry is one example
// of why a task must be marked as failed.
// *Action: None. This is not a user visible exception.
45187, 0000, "storage location %s is unusable; container repair key is %s"
// *Document: YES
// *Cause: During a repair of the Recovery Appliance, fatal
// errors were detected while rebuilding the specified storage
// location.
// *Action: Inspect the alert log for the instance upon which the repair
// command was issued for the errors detected. If you detect that
// the errors are caused by missing disk groups, add those disk
// groups and execute the STARTUP_RECOVERY_APPLIANCE API. If you
// decide that the missing data cannot be restored, execute the
// REPAIR_STORAGE_LOCATION API with the REPLACE option prior to
// executing the STARTUP_RECOVERY_APPLIANCE API.
45188, 0000, "storage location %s requires repair; container repair key is %s"
// *Document: YES
// *Cause: During a repair of the Recovery Appliance, consistency
// errors were detected while rebuilding the specified storage
// location.
// *Action: Inspect the alert log for the instance upon which the repair
// command was issued for the errors detected. If you detect that
// the errors are caused by missing disks or disk groups, add those
// disks or disk groups and execute the STARTUP_RECOVERY_APPLIANCE
// API. If you decide that the missing data cannot be restored,
// execute the REPAIR_STORAGE_LOCATION API with the REPLACE option
// prior to executing the STARTUP_RECOVERY_APPLIANCE API.
45189, 0000, "repair failed because storage location was renamed from %s to %s"
// *Document: YES
// *Cause: During a repair of the Recovery Appliance, a storage
// location was found whose name was different from the name
// originally used to define the storage location.
// *Action: Delete the bad storage location and re-create it with the proper
// name.
45190, 0000, "anomaly detected while reading metadata for database with DB_KEY %s"
// *Document: YES
// *Cause: A transient anomaly was found in the backup data.
// *Action: If the anomaly persists, generate a new level 0 backup for all
// data files in the database.
45191, 0000, "no suitable SBT library was found for the Recovery Appliance backups"
// *Document: YES
// *Cause: Recovery Appliance could not find a suitable
// System Backup to Tape (SBT) library for performing the
// Recovery Appliance metadata backups.
// *Action: Create an SBT library that can be used for the Recovery Appliance
// backup.
45192, 0000, "reservation already exists for the Recovery Appliance backup"
// *Document: YES
// *Cause: An attempt was made to create a new reservation to perform a
// Recovery Appliance metadata backup when an
// unexpired reservation exists.
// *Action: Remove the existing reservation and then create a new
// reservation.
45193, 0000, "multiple SBT libraries are present"
// *Document: YES
// *Cause: More than one System Backup to Tape (SBT) library was found
// that can be used to back up the Recovery Appliance
// metadata.
// *Action: Specify a name while reserving the SBT library.
45194, 0000, "Recovery Appliance metadata backup to SBT library failed"
// *Document: YES
// *Cause: An error occurred while backing up the Recovery Appliance
// metadata to the System Backup to Tape (SBT)
// library. The error could be caused by the SBT library
// configuration or an internal Recovery Appliance error.
// *Action: Check the SBT library configuration or RA_INCIDENT_LOG view.
45195, 0000, "reservation wait time exceeded"
// *Document: YES
// *Cause: A timeout occurred while waiting for the system backup to
// tape (SBT) library reservation.
// *Action: Increase the wait time for the reservation by modifying the
// '_drive_wait_minutes' configuration parameter and retry
// the operation.
45196, 0000, "failed to unreserve existing reservation"
// *Document: YES
// *Cause: The existing System Backup to Tape (SBT) library reservation
// could not be unreserved.
// *Action: Check the 'ERROR_LOG' table and trace files for information
// about the cause of this error.
45197, 0000, "SBT library %s could not be found for reservation"
// *Document: YES
// *Cause: The Recovery Appliance could not find a
// System Backup to Tape (SBT) library for the given name.
// *Action: Check the SBT library name and retry the operation.
45198, 0000, "machine is not a physical Recovery Appliance"
// *Document: YES
// *Cause: Recovery Appliance services were attempted
// to start on a machine that was not a physical
// Recovery Appliance.
// *Action: The Recovery Appliance services cannot be
// started on this system.
45199, 0000, "Error %s encountered when executing %s."
// *Cause: An error was encountered when executing PL/SQL code.
// This message should be accompanied by other error message(s)
// indicating the cause of the error.
// *Action: Check the accompanying errors.
/
/ 45200 - 45225 reserved for C Servlet Recovery Appliance Error Codes
/
45200, 0000, "HTTP status code: %s"
// *Cause: The indicated HTTP status code was received while
// processing a servlet request,
// *Action: None.
45201, 0000, "additional Information: %s"
// *Cause: The indicated additional error was received while
// processing a servlet request.
// *Action: None.
45202, 0000, "operation failed, retry possible"
// *Cause: A backup, restore operation failed while processing
// a servlet request.
// The operation may be retried.
// *Action: This message is used by the SBT client to decide whether
// to retry the operation.
45203, 0000, "failed to %s backup piece file \"%s\""
// *Cause: An OS operation on the specified backup piece returned an error.
// *Action: Check additional messages.
45210, 0000, "resource busy, retry possible"
// *Cause: A backup or restore operation failed while processing a
// servlet request.
// The operation may be retried.
// *Action: This message is used by the SBT client to decide whether
// to retry the operation.
45211, 0000, "error encountered while sending data; error code %s"
// *Cause: An error was encountered while sending data to the client.
// *Action: Check additional messages.
45212, 0000, "error encountered while receiving data; error code %s"
// *Cause: An error was encountered while receiving data from client.
// *Action: Check additional messages.
45213, 0000, "user or role '%s' does not exist"
// *Cause: There was no user or role with the name specified.
// *Action: Provide a valid user name or role.
45214, 0000, "cannot convert '%s' to number"
// *Cause: An arithmetic, numeric, string, conversion, or constraint error
// occurred. For example, a NULL value was assigned to a variable
// that was declared as NOT NULL or an integer larger than 99 was
// assigned to a variable declared as NUMBER(2).
// *Action: Change the data, how it is manipulated, or how it is declared
// so that values do not violate defined constraints.
45215, 0000, "cannot delete a replication server that is in use"
// *Cause: An attempt was made to delete a replication server that was
// actively restoring a backup.
// *Action: Cancel the restore or wait for the restore to complete before
// deleting the replication server.
45216, 0000, "backup metadata of %s (%s) for database %s was not found"
// *Cause: The reported backup metadata was not found.
// *Action: This is an informational message. Ensure that you retain the
// backups until the SBT tasks are executed.
45217, 0000, "SBT task %s is not found"
// *Cause: The specified SBT task was not found.
// *Action: Provide a valid SBT task identifier and retry the command.
/
/ 45264 - 45274 reserved for Recovery Appliance backup restore script
/
45264, 0000, "error encountered during Recovery Appliance test recovery %s"
// *Document: YES
// *Cause: As part of Recovery Appliance protection, test recovery
// was performed by the Recovery Appliance metadata protection
// script. The test recovery uses the image copies, without
// additional disk space requirement to restore data files, to test
// the database.
// *Action: Additional information regarding this failure is recorded in the
// RA_INCIDENT_LOG and is also displayed in the Oracle Enterprise
// Manager console.
45265, 0000, "error encountered during Recovery Appliance backup health check %s"
// *Document: YES
// *Cause: As part of Recovery Appliance protection, backup health
// check was performed by the Recovery Appliance metadata
// protection script. The backup health check uses the database
// 'validate' and 'preview' command to test the backups.
// *Action: Additional information regarding this failure is recorded in the
// RA_INCIDENT_LOG and is also displayed in the Oracle Enterprise
// Manager console.
45266, 0000, "error encountered during Recovery Appliance database health check %s"
// *Document: YES
// *Cause: As part of Recovery Appliance protection, database health
// check was performed by the Recovery Appliance metadata
// protection script. The database health check uses the 'backup
// validate' command to perform the database health check.
// *Action: Additional information regarding this failure is recorded in the
// RA_INCIDENT_LOG and is also displayed in the Oracle Enterprise
// Manager console.
/
/ 45275 - 45299 reserved for container files
/
45275, 00000, "container: '%s'"
// *Cause: This message reports the name of the Recovery Appliance
// container involved in other messages.
// *Action: See associated error messages for a description of the problem.
45276, 00000, "could not create container"
// *Cause: A container creation failed. There will be
// other messages printed in the error stack that show more
// details about the problem.
// *Action: Investigate the entire error stack. If the problem is
// correctable, do so and retry creating this container.
45277, 00000, "New AU size %s differs from existing AU size %s in group %s."
// *Cause: An attempt was made to create a new container that has
// a different AU size than the other containers that already exist
// in this container group.
// *Action: Specify a container with the same AU size as the other containers
// in the container group.
45278, 00000, "Container group %s is not empty."
// *Cause: An attempt was made to drop the specified container group
// but it is not empty.
// *Action: Either remove the remaining objects from the group or use the
// FORCE option. Note that the FORCE option will irretrievably
// delete all files in the container group.
45279, 00000, "Container group %s does not exist."
// *Cause: The specified container group does not exist.
// *Action: Specify a container group that exists.
45280, 00000, "Container group %s already exists."
// *Cause: The specified container group already exists.
// *Action: Specify a container group that does not exist.
45281, 00000, "Size of %s bytes exceeds maximum container size of %s bytes."
// *Cause: You tried to create a container greater than the maximum size.
// *Action: Specify a smaller size.
45282, 00000, "error identifying container"
// *Cause: An error occurred while identifying a container.
// *Action: There will be other messages on the error stack that show
// details of the problem.
45283, 00000, "error writing to container"
// *Cause: An I/O error occurred while writing to a container.
// *Action: There will be other messages on the error stack that show
// details of the problem.
45284, 00000, "error reading from container"
// *Cause: An I/O error occurred while reading from a container.
// *Action: There will be other messages on the error stack that show
// details of the problem.
45285, 00000, "Cannot create more than %s container groups."
// *Cause: An attempt to add a new container group would cause the
// number of container groups to exceed the system maximum.
// *Action: Increase the container group limit.
45286, 00000, "Cannot create more than %s containers."
// *Cause: An attempt to add a new container would cause the
// number of containers to exceed the system maximum.
// *Action: Increase the container limit.
45287, 00000, "File name %s is not valid for creation."
// *Cause: An attempt was made to create a contained file name in
// an invalid format.
// *Action: Correct the name and retry the operation.
45289, 00000, "Cannot reserve %s bytes in container group %s."
// *Cause: The specified container group was out of space.
// *Action: Add another container to the container group.
45290, 00000, "Cannot shrink file %s because file is busy."
// *Cause: The specified file cannot be reduced in size because some
// other process was holding the file open.
// *Action: Wait until the other process releases the file before attempting
// to reduce its size.
45291, 00000, "Container %s is not globally identified."
// *Cause: An attempt to create or identify a file failed because a
// required container is not globally identified in this instance.
// The logs from the GEN0 process will usually indicate the
// reason why the file could not be identified.
// *Action: Examine the logs from the GEN0 process and correct the problem
// that is making some containers inaccessible.
45292, 00000, "error during container group rebuild"
// *Cause: An unrecoverable error occurred during container group rebuild.
// *Action: Review other messages on the error stack for additional details.
45299, 00000, "Recovery Appliance container fault injection event."
/
/ END error messages reserved for Recovery Appliance (45100 - 45299)
/
/
/ 45300 - 45399 reserved for ?????
/
45300, 0000, "internal primary-side LogMiner tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
//
/
/ 45400 - 45499 reserved for DBMS_ROLLING PL/SQL package
/
45400, 00000, "operation not permitted on current database"
// *Document: YES
// *Cause: An operation was not permitted to start because the
// database role is not supported.
// *Action: Attempt the operation on the primary database. If the
// primary database has recently switched to a logical
// standby database, and an error has occurred, reexecute the
// DBMS_ROLLING.SWITCHOVER procedure on the former primary
// database until successful completion of the operation.
45401, 00000, "upgrade plan is already active"
// *Document: YES
// *Cause: An upgrade plan was already active.
// *Action: The existing plan must first be destroyed by calling
// DBMS_ROLLING.DESTROY_PLAN.
45402, 00000, "LOG_ARCHIVE_CONFIG must contain the DG_CONFIG attribute"
// *Document: YES
// *Cause: The DG_CONFIG attribute was missing from the LOG_ARCHIVE_CONFIG
// parameter.
// *Action: Configure this parameter with the DG_CONFIG attribute before
// performing DBMS_ROLLING operations.
45403, 00000, "database %s must be specified in DG_CONFIG"
// *Document: YES
// *Cause: The specified database was not found in the DG_CONFIG
// attribute of the LOG_ARCHIVE_CONFIG parameter.
// *Action: Add the specified database to the DG_CONFIG attribute of the
// LOG_ARCHIVE_CONFIG parameter.
45404, 00000, "target version is incompatible"
// *Document: YES
// *Cause: The configured target software version was incompatible with a
// DBMS_ROLLING administered upgrade.
// *Action: Use alternative upgrade methods.
45405, 00000, "A rolling upgrade operation is already in progress."
// *Document: YES
// *Cause: A DBMS_ROLLING operation was already in progress. Only one
// operation is permitted at a time.
// *Action: Wait for the operation to complete, or query the PID
// column of DBA_ROLLING_STATUS view to identify the active
// process.
45406, 00000, "operation completed with warnings"
// *Document: YES
// *Cause: An operation succeeded but warnings were generated.
// *Action: Consult the DBA_ROLLING_EVENTS view for the list of warnings.
45407, 00000, "operation encountered a query error"
// *Document: YES
// *Cause: An internal database query failed.
// *Action: Consult the DBA_ROLLING_EVENTS and DBA_ROLLING_PLAN views to
// identify the error code and instruction that caused the
// failure.
45408, 00000, "parameter name is unknown"
// *Document: YES
// *Cause: The specified parameter could not be modified because the
// parameter name was not recognized.
// *Action: Verify that the parameter is among the available parameters
// listed in DBA_ROLLING_PARAMETERS view.
45409, 00000, "parameter value is invalid or out of bounds"
// *Document: YES
// *Cause: The specified parameter could not be modified because its
// value was invalid or out of bounds.
// *Action: Consult the DBA_ROLLING_PARAMETERS view to obtain the valid
// range of values for the associated parameter.
45410, 00000, "parameter may not be modified"
// *Document: YES
// *Cause: The specified parameter could not be modified.
// *Action: Internal parameters may not be modified through the
// DBMS_ROLLING.SET_PARAMETER procedure. If the parameter is a
// user parameter, the parameter is no longer meaningful at the
// current phase of the upgrade.
45411, 00000, "operation requires additional arguments"
// *Document: YES
// *Cause: An operation has failed because one or more arguments were
// not supplied.
// *Action: Retry the operation with all required arguments.
//
45412, 00000, "parameter scope argument is unknown"
// *Document: YES
// *Cause: An operation has failed because the database unique name
// provided in the scope argument was not known.
// *Action: Verify that the database unique name exists in the
// DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter.
45413, 00000, "parameter has no default value"
// *Document: YES
// *Cause: The specified parameter could not be reverted back to its
// default value because the default value did not exist.
// *Action: The parameter must be set to an explicit value.
45414, 00000, "could not connect to a remote database"
// *Document: YES
// *Cause: Connections to one or more databases failed.
// *Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views to
// identify the involved databases and the specific error codes.
45415, 00000, "instruction execution failure"
// *Document: YES
// *Cause: A rolling upgrade operation has halted due to the failure of
// one or more required upgrade instructions.
// *Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views to
// identify the active instructions and their associated error
// codes.
45416, 00000, "operation cannot start until plan rebuild"
// *Document: YES
// *Cause: An operation was not permitted to start due to recent
// parameter modifications which required a rebuild of the
// upgrade plan.
// *Action: Call the DBMS_ROLLING.BUILD procedure to rebuild the upgrade
// plan.
45417, 00000, "operation not permitted since current phase was not %s"
// *Document: YES
// *Cause: An operation was not permitted to start because the
// upgrade was in a different phase.
// *Action: Call the DBMS_ROLLING procedure associated with the
// current phase.
45418, 00000, "database is not running the higher version RDBMS"
// *Document: YES
// *Cause: A rolling upgrade instruction has failed because a
// database was not running the correct target RDBMS version.
// *Action: Consult the DBA_ROLLING_PLAN view to identify the offending
// databases and restart them on the higher version binaries.
45419, 00000, "DB_UNIQUE_NAME parameter must be specified"
// *Document: YES
// *Cause: The DB_UNIQUE_NAME parameter was not configured.
// *Action: Configure the DB_UNIQUE_NAME parameter.
//
45420, 00000, "return TNS service was not found"
// *Document: YES
// *Cause: An instruction failed because a Transparent Network Substrate
// (TNS) service name for return communication was not found on a
// remote database.
// *Action: Consult the DBA_ROLLING_PLAN view to identify the offending
// database or databases.
45421, 00000, "database type is not supported by rolling upgrade"
// *Document: YES
// *Cause: One or more databases specified in the DG_CONFIG attribute
// was incompatible with a DBMS_ROLLING administered upgrade.
// *Action: Disable the databases from the upgrade configuration by
// setting their associated INVOLVEMENT parameters to a value
// of NONE, and rebuild the upgrade plan.
45422, 00000, "operation requires existing plan"
// *Document: YES
// *Cause: An operation was not permitted to start because it
// required an active plan.
// *Action: Configure an upgrade plan by calling the
// DBMS_ROLLING.INIT_PLAN procedure.
45423, 00000, "target database has mismatched DB_UNIQUE_NAME"
// *Document: YES
// *Cause: A specified DB_UNIQUE_NAME attribute in a
// LOG_ARCHIVE_DEST_n parameter did not match the
// DB_UNIQUE_NAME at the target database.
// *Action: Ensure the DB_UNIQUE_NAME attribute and associated
// Transparent Network Substrate (TNS) service name or
// associated connect string has been configured properly.
45424, 00000, "initialization parameter file has unexpected value"
// *Document: YES
// *Cause: An instruction failed due to an initialization parameter
// file at a remote database that was found to be invalid.
// *Action: Consult the DBA_ROLLING_PLAN view to identify the offending
// database.
45425, 00000, "operation halted due to required user interaction"
// *Document: YES
// *Cause: A rolling upgrade operation stopped because interaction is
// required.
// *Action: Consult the DBA_ROLLING_EVENTS view to identify the actions
// required.
45426, 00000, "managed recovery process was not running"
// *Document: YES
// *Cause: An operation failed due to the inactive managed recovery
// process at a remote database.
// *Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
// to identify the offending database. Restart the managed
// recovery process or resolve any errors that would prevent
// the managed recovery process from remaining active.
45427, 00000, "logical standby Redo Apply process was not running"
// *Document: YES
// *Cause: An operation failed due to the inactive logical standby
// Redo Apply process at a remote database.
// *Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
// to identify the offending database. Restart the logical
// standby Redo Apply process or resolve any errors that
// would prevent the logical standby Redo Apply process from
// remaining active.
45428, 00000, "database was not in expected database role"
// *Document: YES
// *Cause: An instruction failed due to a database operating in a database
// role which was not expected.
// *Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views to
// identify the offending database. If the role change is due to
// a failover, the FAILOVER parameter must be set and the upgrade
// plan must be rebuilt before resuming the rolling upgrade.
//
45429, 00000, "database was set to an invalid Data Guard protection mode"
// *Document: YES
// *Cause: An instruction failed due to a database operating at a
// data protection mode that was not expected.
// *Action: Consult the DBA_ROLLING_PLAN view to identify the offending
// database. Set the data protection mode accordingly based on
// the requirement as described in the instruction.
//
45430, 00000, "flashback database was not enabled"
// *Document: YES
// *Cause: An instruction failed due to a database that was found to
// not have Flashback Database enabled.
// *Action: Consult the DBA_ROLLING_PLAN view to identify the offending
// database. Configure the database with adequate storage to
// support guaranteed restore points and enable Flashback
// Database.
//
45431, 00000, "database was mounted or open in an invalid mode"
// *Document: YES
// *Cause: An instruction failed due to a database that was mounted or
// open in an invalid mode.
// *Action: Consult the DBA_ROLLING_PLAN view to identify the offending
// database and the expected mode. Restart the database in the
// expected mode.
//
45432, 00000, "future primary database is not a physical standby database"
// *Document: YES
// *Cause: An operation was not permitted because the future primary
// database is not a physical standby database.
// *Action: Specify a physical standby database as the future primary
// database.
//
45433, 00000, "failover was detected on an unsupported database"
// *Document: YES
// *Cause: An operation was not permitted because a failover was
// detected on a database which does not permit continuation
// of the rolling upgrade.
// *Action: Consult the DBA_ROLLING_EVENTS view to identify the
// unsupported database and abort the rolling upgrade.
//
45434, 00000, "multiple failovers of the same type detected"
// *Document: YES
// *Cause: An operation was not permitted because multiple failovers
// were detected on standby databases which protect a common
// target.
// *Action: Consult the DBA_ROLLING_EVENTS view to identify the
// offending databases. Remove the unwanted databases from
// the configuration and rebuild the upgrade plan.
//
45435, 00000, "managed recovery process was running"
// *Document: YES
// *Cause: An operation failed due to an active managed recovery
// process at a remote database.
// *Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
// to identify the offending database and stop the managed
// recovery process.
45436, 00000, "logical standby Redo Apply process was running"
// *Document: YES
// *Cause: An operation failed due to an active Redo Apply process at
// a remote database.
// *Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
// to identify the offending database and stop the Redo Apply
// process.
45437, 00000, "database upgrade progress is inconsistent"
// *Document: YES
// *Cause: An operation failed due to the discovery of the catalog
// upgrade progress on a database that was different from the
// progress value saved in the plan state.
// *Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
// to identify the offending database and remove the database
// from the configuration.
45438, 00000, "database is not in mounted mode"
// *Document: YES
// *Cause: An operation failed due to the discovery of a database
// which was not in mounted mode.
// *Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
// to identify the offending database. If the database was
// opened, restart the database in mounted mode.
45439, 00000, "database is not in open read/write mode"
// *Document: YES
// *Cause: An operation failed due to the discovery of a database
// which was not in open read/write mode.
// *Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
// to identify the offending database. Open the database in
// read/write mode.
45440, 00000, "server parameter file has not been configured"
// *Document: YES
// *Cause: An operation failed due to the discovery of a database
// which was not configured with a server parameter file that
// could be modified.
// *Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
// to identify the offending database. Ensure the database has
// been configured with a server parameter file, and that the
// parameter file can be modified.
45441, 00000, "no databases eligible for rollback"
// *Document: YES
// *Cause: A rollback operation could not start because the databases have
// not created the guaranteed restore point needed for rollback.
// *Action: A rollback is not necessary. The rolling operation can be
// cancelled by calling DBMS_ROLLING.DESTROY_PLAN.
45442, 00000, "rollback is not permitted after a role change"
// *Document: YES
// *Cause: A rollback operation was not permitted due to a prior role
// change event such as a switchover or failover.
// *Action: Reconfigure the Data Guard configuration manually.
45443, 00000, "cannot quiesce replicated PL/SQL procedures"
// *Document: YES
// *Cause: An operation failed because there were other processes executing
// long running replicated PL/SQL procedures.
// *Action: Increase the value of DICTIONARY_PLS_WAIT_TIMEOUT and retry the
// failed operation.
45480, 00000, "operation status is unknown"
// *Document: NO
// *Cause: An instruction failed to produce a status.
// *Action: N/A. This is an internal error.
//
45481, 00000, "message is malformed"
// *Document: NO
// *Cause: A received message was malformed.
// *Action: N/A. This is an internal error.
//
45482, 00000, "no callback exists"
// *Document: NO
// *Cause: A callback did not exist for the specified opcode.
// *Action: N/A. This is an internal error.
//
45483, 00000, "agent process is not ready"
// *Document: NO
// *Cause: An agent process received a message when it was not ready.
// *Action: N/A. This is an internal error.
//
45484, 00000, "agent process has been disabled"
// *Document: NO
// *Cause: An agent process disabled itself due to an internal error.
// *Action: N/A. This is an internal error.
//
45485, 00000, "directive %u is invalid - reason: %s"
// *Document: NO
// *Cause: A directive was specified which violates internal assumptions.
// *Action: N/A. This is an internal error.
//
45486, 00000, "database update progress is inconsistent"
// *Document: YES
// *Cause: An operation failed due to the discovery of the update progress
// on a database that was different from the progress value saved
// in the plan state.
// *Action: Consult the DBA_ROLLING_PLAN and DBA_ROLLING_EVENTS views
// to identify the offending database and remove the database
// from the configuration.
//
45489, 00000, "required condition was not satisfied"
// *Document: NO
// *Cause: An instruction which tested for a specific requirement
// determined that the requirement was not met.
// *Action: Consult the DBA_ROLLING_PLAN view to identify the failure
// context such as the affected database and the requirement.
// The trace and alert files of the affected database may also
// contain additional information.
//
45490, 00000, "rolling upgrade trace event"
// *Document: NO
// *Cause: N/A.
// *Action: N/A. This is an internal event.
//
45491, 00000, "rolling upgrade debug event"
// *Document: NO
// *Cause: N/A.
// *Action: N/A. This is an internal event.
//
45499, 00000, "internal error - %s"
// *Document: NO
// *Cause: An internal error was encountered.
// *Action: N/A. This is an internal error.
//
/
/ 45500 - 45599 reserved for GSM related error codes.
/
45500, 0000, "Cannot remove a database from a pool that contains a broker configuration."
// *Document: Yes
// *Cause: An attempt was made to remove a database from a pool that
// contained a broker configuration.
// *Action: If the broker configuration has changed, use the SYNC command
// in gsmctl to synchronize the pool
//
45501, 0000, "The maximum number of global service managers for this region has been exceeded."
// *Document: Yes
// *Cause: A new Global Service Manager (GSM) was added to a region that
// already contained the maximum number of GSMs.
// *Action: The maximum has been reached. Do not attempt to add anymore GSMs.
//
45502, 0000, "Insufficient privileges to perform this operation."
// *Document: Yes
// *Cause: A Global Service Manager (GSM) command was executed by
// a non-privileged user.
// *Action: Either connect as a privileged user, or ask your GSM administrator
// to add you as a pool or GSM administrator.
//
45503, 0000, "This database is already in cloud %s."
// *Document: Yes
// *Cause: An attempt was made to add a database to a cloud when it was
// already in another cloud.
// *Action: A database can only be in one cloud. Remove it from the
// other cloud first.
45504, 0000, "Cannot relocate a preferred_all service."
// *Document: Yes
// *Cause: The command 'relocate service' is not supported for preferred_all
// services.
// *Action: Do no attempt to relocate a preferred_all service.
//
45505, 0000, "The maximum number of services has been reached."
// *Document: Yes
// *Cause: The hard limit for the number of global services has been reached.
// *Action: No more global services can be added without first removing a
// service.
45506, 0000, "The maximum number of GDS pools has been reached."
// *Document: Yes
// *Cause: The hard limit for the number of Global Data Services (GDS)
// pools has been reached.
// *Action: No more Global Data Services (GDS) pools can be added without
// first removing a pool.
//
45507, 0000, "Region %s does not have a buddy region."
// *Document: Yes
// *Cause: The specified region did not have a buddy.
// *Action: This message is informational only. Consider using
// 'modify region' to add a buddy for this region.
//
45508, 0000, "Database %s does not have an assigned region."
// *Document: Yes
// *Cause: The specified database did not have an assigned region.
// *Action: Use 'modify database' to assign a region to this database.
//
45509, 0000, "Database %s has an invalid status \"%s\"."
// *Document: Yes
// *Cause: The specified database had an invalid status.
// *Action: Check that the account \"gsmuser\" has been enabled by
// the remote DBA, that you used the correct password for
// \"gsmuser\" when running \"add database\", and that there
// is an existing valid node check for registration (VNCR)
// entry for this database host.
//
45510, 0000, "There is an outstanding GSM request for change number %s created at %s. GSM has failed to apply this request %s times."
// *Document: Yes
// *Cause: A change request originating from a gdsctl command was not
// applied after several minutes.
// *Action: Verify that the Global Service Manager (GSM) server is able
// to connect to all databases in the framework to apply the change.
//
45511, 0000, "Service %s does not have a preferred database."
// *Document: Yes
// *Cause: The specified service did not have a preferred database.
// This can happen if the database was removed from the pool.
// *Action: Use 'modify service' to provide a preferred database for this
// service.
//
45512, 0000, "Service %s is a local only service which has an available database in region %s, but does not have a preferred database in the same region."
// *Document: Yes
// *Cause: The specified service did not have a preferred database in a
// region in which it had an available database.
// *Action: Use 'modify service' to provide a preferred database in this
// region for this service, or remove the available database
// in this region.
//
45513, 0000, "Database %s has no global services defined for it."
// *Document: Yes
// *Cause: A database was added to the global data services framework,
// but no global services have been defined for it, or they
// have all been removed.
// *Action: This is an informational message. Consider defining a service
// for this database, or removing the database from the framework.
//
45514, 0000, "Region %s does not contain any databases."
// *Document: Yes
// *Cause: A region was added to the global data services framework,
// but no databases were added to this region, or they have
// all been removed.
// *Action: This is an informational message. Consider adding a database
// to this region or removing the region.
//
45515, 0000, "Region %s does not contain any GSMs."
// *Document: Yes
// *Cause: A region was added to the global data services framework, but
// no global services manager servers were defined for this region,
// or they have all been removed.
// *Action: This is a warning message. You are advised to define a GSM
// in this region for high availability.
//
45516, 0000, "GDS pool %s does not contain any databases."
// *Document: Yes
// *Cause: The specified Global Data Services (GDS) pool did not contain
// any databases.
// *Action: This is an informational message. Consider adding databases to
// this pool or removing the pool from the global data services
// framework.
//
45517, 0000, "GDS pool %s does not contain any global services."
// *Document: Yes
// *Cause: The specified Global Data Services (GDS) pool did not contain
// any global services.
// *Action: This is an informational message. Consider adding services to
// this pool or removing the pool from the global data services
// framework.
//
45518, 0000, "Service %s will not be started on logical/snapshot standby."
// *Document: Yes
// *Cause: The specified service will not be started on a logical/snapshot
// standby.
// *Action: This is a warning message. Consider re-defining lag parameter
// to "any", if the service needs to be started on
// a logical/snapshot standby.
//
45519, 0000, "Database pool %s is empty; this operation cannot be performed on an empty pool."
// *Document: Yes
// *Cause: The database pool does not contain any databases.
// Therefore this operation will have no effect.
// *Action: This is a warning message. Do not perform this operation on
// an empty database pool.
//
45520, 0000, "A service with locality ANYWHERE cannot set region failover."
// *Document: Yes
// *Cause: Service attributes ANYWHERE and REGION_FAILOVER are incompatible.
// *Action: Do not attempt to set REGION_FAILOVER on a service with locality
// ANYWHERE.
//
45521, 0000, "A service with a primary role cannot set FAILOVER_PRIMARY."
// *Document: Yes
// *Cause: A service with a primary role cannot set FAILOVER_PRIMARY.
// *Action: Do not attempt to set FAILOVER_PRIMARY on a service that has
// a primary role.
//
45522, 0000, "LOCAL_ONLY service %s cannot be relocated to a database in another region."
// *Document: Yes
// *Cause: The specified service is LOCAL_ONLY and cannot be relocated
// to a database in a different region.
// *Action: Do not relocate a LOCAL_ONLY service to a database in another
// region.
//
45523, 0000, "Warning: service %s is already stopped."
// *Document: Yes
// *Cause: The service was stopped already.
// *Action: None; this is only a warning message.
//
45524, 0000, "must explicitly specify Global Data Services pool name because there could be multiple candidates"
// *Document: Yes
// *Cause: An attempt to have a default Global Data Services pool
// when multiple pools already coexist in the domain failed.
// *Action: Do not omit '-gdspool gdspool_name_list' when multiple pools exist
//
45525, 0000, "A value of TRANSACTION was provided for the service parameter '-failovertype', but bad or nonexistent value was specified for service parameter '-retention'."
// *Document: Yes
// *Cause: The command specified a value of TRANSACTION for the service
// parameter '-failovertype', and either did not provide a value for
// the parameter '-retention', or provided a value that was less
// than or equal to the value provided for the parameter
// '-replay_init_time'.
// *Action: If a service is created with a value of TRANSACTION for the
// parameter '-failovertype', then a value must be provided for
// the parameter '-retention', and that value must be greater
// than the value provided for the parameter '-replay_init_time'.
//
45526, 0000, "A value of TRANSACTION was provided for the service parameter '-failovertype', but a bad or nonexistent value was specified for service parameter '-replay_init_time'."
// *Document: Yes
// *Cause: The command specified a value of TRANSACTION for the service
// parameter '-failovertype', and either did not provide a value for
// the parameter '-replay_init_time', or provided a value that was
// less than or equal to the value provided for the parameter
// '-failoverdelay'.
// *Action: If a service is created with a value of TRANSACTION for the
// parameter '-failovertype', then a value must be provided for
// the parameter '-replay_init_time', and that value must be greater
// than the value provided for the parameter '-failoverdelay'.
//
45527, 0000, "Database compatibility level was too low for use with Global Data Services (GDS)."
// *Document: Yes
// *Cause: The major database compatibility level is below 12. The Global
// Data Services (GDS) feature requires that the database
// compatibility level of all participating databases be at 12 or
// above.
// *Action: In order to use this database for Global Data Services (GDS), an
// upgrade must be completed so that its major compatibility level
// is at 12 or above.
//
45528, 0000, "Service %s has not been globally started."
// *Document: Yes
// *Cause: An attempt was made to start the service in a specific database
// without first starting it globally.
// *Action: Start the service globally by using 'start service' command
// without specifying the '-database' parameter.
//
45529, 0000, "Database has not been configured to use an SPFILE."
// *Document: Yes
// *Cause: The database was not configured to use an SPFILE. This
// is required before it can be used within a Global Data
// Services (GDS) framework.
// *Action: Reconfigure the database to use an SPFILE and attempt the
// action again.
//
45530, 0000, "A local service with the same name already exists."
// *Document: Yes
// *Cause: An attempt was made to create a global service with the same
// name as an existing local service.
// *Action: Use a different service name or delete the existing local
// service.
//
45531, 0000, "This database is already in another Global Data Services (GDS) framework."
// *Document: Yes
// *Cause: An attempt was made to create a Global Data Services (GDS)
// catalog on a database that was already in another GDS framework.
// *Action: Remove this database from the other framework before
// using it as a Global Data Services (GDS) catalog.
//
45532, 0000, "This database is already a catalog for another Global Data Services (GDS) framework."
// *Document: Yes
// *Cause: An attempt was made add a database to a Global Data Services
// (GDS) framework, but it was already a catalog database for
// another framework.
// *Action: Do not attempt to to add a Global Data Services (GDS) catalog
// to another GDS framework.
//
45533, 0000, "Service %s is already being modified from another GDSCTL session."
// *Document: Yes
// *Cause: The specified service was already in the process of being
// modified.
// *Action: Wait until any other service modifications have completed. If
// this problem persists, contact Oracle Support Services.
//
45534, 0000, "There is a running GSM (Global Service Manager) connected to the catalog."
// *Document: Yes
// *Cause: This command could not be executed while there were running
// GSM (Global Service Manager) servers connected to the catalog.
// *Action: Shut down all GSM servers before running this command.
//
//
45535, 0000, "Catalog version cannot be determined."
// *Document: Yes
// *Cause: The version of the GDS (Global Data Services) catalog could not
// be determined.
// *Action: Contact Oracle Support Services.
//
45536, 0000, "This version of GDSCTL is not compatible with the GDS (Global Data Services) catalog."
// *Document: Yes
// *Cause: The version of GDSCTL being used was not compatible with the
// current GDS catalog.
// *Action: Refer to the documentation for compatible versions and upgrade
// or downgrade GDSCTL or the GDS catalog.
//
//
45537, 0000, "This version of GSM (Global Service Manager) is not compatible with the GDS (Global Data Services) catalog."
// *Document: Yes
// *Cause: The version of GSM being used was not compatible with the
// current GDS catalog.
// *Action: Refer to the documentation for compatible versions and upgrade
// or downgrade GSM or the GDS catalog.
//
45538, 0000, "The database version is not compatible with the GDS (Global Data Services) catalog."
// *Document: Yes
// *Cause: The version of the database being added was not compatible with
// the GDS catalog.
// *Action: Refer to the documentation for compatible versions and upgrade
// or downgrade the database or the GDS catalog.
//
45539, 0000, "Database %s has already been added to another pool."
// *Document: Yes
// *Cause: An attempt was made to add a database to a pool, but this
// database has already been added to another pool.
// *Action: Do not attempt to add a database to two different pools.
//
45540, 0000, "Call to SRVCTL failed with status %s, errors: %s."
// *Document: Yes
// *Cause: An attempt to call the SRVCTL command line failed with the
// specified errors.
// *Action: Refer to the Oracle Real Application Clusters (Oracle RAC)
// documentation and resolve the problems reported by SRVCTL.
//
45541, 0000, "Parameters \"-serverpool\" and \"-cardinality\" are invalid for administrator-managed Oracle RAC databases."
// *Document: Yes
// *Cause: The service command stipulated -serverpool or -cardinality
// but this database was an administrator-managed Oracle RAC
// database, which does not recognize these parameters.
// *Action: Do not use -serverpool or -cardinality on administrator-managed
// Oracle RAC databases.
//
45542, 0000, "Parameters \"-serverpool\", \"-cardinality\", and \"-instances\" are invalid for non-Oracle RAC databases."
// *Document: Yes
// *Cause: The service command stipulated -serverpool, -cardinality,
// or -instances but this database was a non-Oracle RAC database,
// which does not recognize these parameters.
// *Action: Do not use -serverpool, -cardinality, or -instances on
// non-Oracle RAC databases.
//
45543, 0000, "Parameter \"-instances\" is invalid for policy-managed Oracle RAC databases."
// *Document: Yes
// *Cause: The service command stipulated -instances, but this database
// was a policy-managed Oracle RAC database, which does not
// recognize this parameter.
// *Action: Do not use -instances on policy-managed Oracle RAC databases.
//
45544, 0000, "An invalid weight string was provided for manual override of runtime load balancing."
// *Document: Yes
// *Cause: The string provided by GDSCTL to override runtime load balancing
// with manual region weights was badly formed.
// *Action: Retry the command. If the problem persists, contact Oracle
// Support Services.
//
45545, 0000, "cannot delete all remaining instances"
// *Document: Yes
// *Cause: This command would delete all remaining instances from the
// service, leaving the service in an invalid state.
// *Action: Do not provide an instance list that would delete all instances.
//
45546, 0000, "cannot create process to run SRVCTL with system error %s"
// *Document: Yes
// *Cause: There was a problem creating a new process to run SRVCTL from
// the command line.
// *Action: Check the Oracle alert log on the Oracle database server
// machine and rectify the problem on the server.
//
45547, 0000, "A call to SRVCTL failed with error %s because of bad parameters."
// *Document: Yes
// *Cause: The command-line execution of SRVCTL failed because of bad
// parameters.
// *Action: Check the database server traces and contact Oracle Support
// Services.
//
45548, 0000, "The catalog database can be downgraded, downgrading a catalog database after making changes is not advised."
// *Document: Yes
// *Cause: This is a warning message only. This command required catalog
// changes and the 'compatible' database parameter indicated that
// the database could be downgraded. Downgrading a catlog database
// after making catalog changes is not advised and may cause
// data loss in the catalog.
// *Action: Make your database upgrade permanent by updating the
// 'compatible' database parameter before using GDSCTL commands
// that will alter the catalog.
//
45549, 0000, "Catalog changes are not possible without a running GSM at the current version."
// *Document: Yes
// *Cause: This command required catalog changes, which are not allowed
// unless there is at least one Global Service Manager (GSM) server
// running at the current version.
// *Action: Start a GSM server that is running the current version of the
// software. If there are none, upgrade at least one exitsing
// GSM or add a new one at the current version.
//
45550, 0000, "service does not exist"
// *Document: Yes
// *Cause: An attempt was made to start a service that did not exist
// on the target database.
// *Action: None. This error was caught by the Global Service Manager (GSM),
// and the service was created automatically.
//
45551, 0000, "Instance %s was not in the instance list for this database."
// *Document: Yes
// *Cause: An attempt was made to delete an instance from this database
// but the instance was not in the existing instance list.
// *Action: None. This is a warning only. No action was taken for the named
// instance.
//
45552, 0000, "None of the provided instances were in the instance list for this database."
// *Document: Yes
// *Cause: The provided instance list did not contain any valid instances,
// or the existing instance list for the catalog was empty.
// *Action: Check the list of instances and run the command again
// if necesary.
45553, 0000, "Service %s does not have any instances defined for database\\(s\\) %s."
// *Document: Yes
// *Cause: An attempt was made to start a service on an
// administrator-managed Oracle RAC database, but there were no
// instances defined for the service on that database.
// *Action: Define instances for the service on all of the listed databases
// before attempting to start the service.
//
45554, 0000, "There are no services that can start on database %s."
// *Document: Yes
// *Cause: An attempt was made to start all services for a given database
// but there were no services that could start.
// *Action: None. This is a warning message indicating that no action
// was taken for this command.
//
45555, 0000, "The target database is not in the preferred or available list for this service."
// *Document: Yes
// *Cause: The new database name provided was not in the list of preferred
// or available databases for the service.
// *Action: Either add the new database to the service or relocate the
// service to another database.
//
45556, 0000, "A database name or service name was not provided."
// *Document: Yes
// *Cause: A disable service request did not provide either a database
// name or a service name.
// *Action: Provide either a service name or a database name on the
// request.
//
45557, 0000, "The database pool %s does not contain a broker configuration."
// *Document: Yes
// *Cause: An attempt was made to remove a broker configuration from a
// database pool that does not contain one.
// *Action: Rerun the command using a different database pool.
//
45558, 0000, "There are no database pools in this catalog."
// *Document: Yes
// *Cause: The catalog did not have any database pools defined.
// *Action: Create at least one database pool before running any other
// commands.
//
45559, 0000, "Global service manager (GSM) %s did not provide a version."
// *Document: Yes
// *Cause: The GSM did not provide a version when attempting to connect
// to the catalog.
// *Action: This version of GSM is too old to connect to the catalog.
// Upgrade the GSM installation.
//
45560, 0000, "Database %s must contain at least one preferred instance."
// *Document: Yes
// *Cause: The MODIFY command did not add any preferred instances or
// removed all existing preferred instances from this database.
// *Action: Provide at least one preferred instance, or do not attempt to
// remove all existing preferred instances.
//
45561, 0000, "region name is required"
// *Document: Yes
// *Cause: A region name was not provided and was required because there
// were multiple regions in the catalog.
// *Action: Provide the region name on the command line.
//
45562, 0000, "The Global Data Services catalog must be created in a root container."
// *Document: Yes
// *Cause: The CREATE CATALOG command could not be executed on a container other than
// the root container.
// *Action: Use the root container to create the Global Data Services catalog.
//
45563, 0000, "The pool database cannot be a pluggable database."
// *Document: Yes
// *Cause: The ADD DATABASE command could not add a pluggable database.
// *Action: Provide the consolidated database name instead.
//
45564, 0000, "pool \"%s\" contains a sharded root configuration; only preferred_all services are allowed"
// *Document: Yes
// *Cause: An attempt was made to add non-uniform service to a pool that contains
// a sharded root.
// *Action: None.
//
45565, 0000, "pool \"%s\" contains a sharded root configuration; databases cannot be added to this pool"
// *Document: Yes
// *Cause: An attempt was made to add a database to a pool that contains
// a sharded root.
// *Action: None.
//
45566, 0000, "pool \"%s\" contains a sharded root configuration"
// *Document: Yes
// *Cause: An attempt was made to work with a generic pool that was not
// a sharded root.
// *Action: None.
//
45567, 0000, "pool \"%s\" is not a shard"
// *Document: Yes
// *Cause: An attempt was made to work with a generic pool that was not
// a shard.
// *Action: None.
//
45568, 0000, "database link to catalog is invalid"
// *Document: Yes
// *Cause: An attempt to use a database link from a pool database
// to a catalog failed.
// *Action: Check the network connectivity and master global service
// manager (GSM) endpoint.
//
45569, 0000, "condition not ready for GSM to acquire catalog lock."
// *Document: No
// *Cause: This is added to avoid infinite loop to acquire lock.
// *Action: GSM will catch this error and sleep on its side.
//
45570, 0000, "The %s is not empty and cannot be removed."
// *Document: Yes
// *Cause: The shardspace or shardgroup was not empty and contained
// at least one shardgroup or shard.
// *Action: Delete all shards or shardgroups before calling the procedure
// again.
//
45572, 0000, "Remote shard conversion job %s failed with error: %s"
// *Document: Yes
// *Cause: The remote scheduler job to convert a shard from seed has failed.
// *Action: Read the error and resolve the problem described, then restart
// the job using the \"deploy\" command in GDSCTL.
//
45573, 0000, "shard open mode is %s, it should be READ WRITE"
// *Document: Yes
// *Cause: The shard was opened in the incorrect mode for Oracle Data Guard
// broker setup.
// *Action: If the open mode was \"MOUNTED\", then check that the shard
// has been correctly converted from a shard seed. If the shard
// was already a converted primary shard, then open it in the
// correct mode and rerun \"deploy\" from GDSCTL.
//
45574, 0000, "shard has role %s, it should be PRIMARY"
// *Document: Yes
// *Cause: The shard did not have the correct role for Oracle Data Guard
// broker setup.
// *Action: Ensure the shard is placed in a shardgroup that
// will automatically assign the correct role to it.
//
45575, 0000, "Deployment has terminated due to previous errors."
// *Document: Yes
// *Cause: Due to previous errors deployment could not continue.
// *Action: Resolve the issues described in all of the displayed errors and
// rerun \"deploy\" from GDSCTL.
//
45576, 0000, "Shard %s requires conversion from seed, but the remote scheduler is not configured."
// *Document: Yes
// *Cause: The remote scheduler agent is required to convert the shard
// from a seed, but it has not been configured.
// *Action: Configure the remote scheduler and rerun "\deploy\" from GDSCTL.
//
45577, 0000, "cannot convert standby shards to primary shard %s because the DBID is unknown"
// *Document: Yes
// *Cause: A primary shard was added to the catalog but the DBID was not
// discovered, and none of the standby shards could be converted.
// *Action: Remove the primary shard from the catalog and re-add it so
// that the database identifier (DBID) can be discovered.
//
45578, 0000, "No credential for scheduler jobs."
// *Document: Yes
// *Cause: Credential could not be created or retrieved.
// *Action: Specify -osaccount and -ospassword in \"add shard\", or
// use \"add credential\" command to add credential.
//
45579, 0000, "There are converted physical standby shards for intended primary seed shard %s."
// *Document: Yes
// *Cause: The primary shard was still an unconverted seed, but it had
// converted standby shards. Standby shards cannot be
// converted before their primary shard.
// *Action: Either remove the converted standby shards or remove
// the primary shard, convert it manually, and re-add it.
//
45580, 0000, "invalid value specified for input parameter %s"
// *Document: Yes
// *Cause: The specified parameter was set to an invalid value.
// *Action: Verify the parameter value and retry operation.
//
45581, 0000, "cannot mix sharded and non-sharded pools in the same catalog"
// *Document: Yes
// *Cause: At attempt was made to create a sharded and a non-sharded
// database pool in the same catalog.
// *Action: Create a separate catalog for each database pool type.
//
45582, 0000, "The chunk %s was not found or has been moved to another shard."
// *Document: Yes
// *Cause: The client application specified a chunk name associated
// with the current user call that was not found on the current
// shard.
// *Action: Invalidate the connection pool routing table for this shard.
//
45583, 0000, "chunk %s does not contain the specified key"
// *Document: Yes
// *Cause: The chunk, specified by the client application, was split
// or never contained the specified key.
// *Action: Invalidate the pool routing table for the given chunk.
// The client should ask the listener to route to the specified key.
//
45584, 0000, "The shard object to be removed does not exist."
// *Document: Yes
// *Cause: The shardspace or shardgroup that you intended to remove
// did not exist in catalog.
// *Action: Do not attempt to remove the shard object again.
//
45585, 0000, "Chunk move failure: target shard is unavailable: \"%s\""
// *Document: Yes
// *Cause: The chunk move failed. The source shard could not connect to
// the target.
// *Action: Check the availability of the target shard and network
// configuration.
//
45586, 0000, "Chunk move failure: target shard is in invalid state: \"%s\""
// *Document: Yes
// *Cause: The chunk move failed. The target shard was improperly
// configured.
// *Action: Call the GDSCTL VALIDATE SHARD command for more details.
//
45587, 0000, "Chunk move failure: target standby is unavailable; connection string: \"%s\""
// *Document: Yes
// *Cause: The chunk move failed. The source shard could not connect to
// the target standby shard.
// *Action: Check the availability of the target standby shard and broker
// configuration.
//
45588, 0000, "Chunk move failure: unable to read tablespace information \"%s\""
// *Document: Yes
// *Cause: Shard metadata inconsistency was detected.
// *Action: Call the GDSCTL VALIDATE SHARD command for more details.
//
45589, 0000, "Chunk move failure: DB_FILE_CREATE_DEST value is not valid"
// *Document: Yes
// *Cause: Shard configuration inconsistency was detected.
// *Action: Set the DB_FILE_CREATE_DEST initialization parameter to a
// valid existing folder.
//
45590, 0000, "Chunk move failure: backup cannot be created for tablespace \"%s\""
// *Document: Yes
// *Cause: Shard configuration inconsistency was detected.
// *Action: Set the DB_FILE_CREATE_DEST initialization parameter to a
// valid existing folder.
//
45591, 0000, "Chunk move failure: data file copy error. Destination: \"%s\""
// *Document: Yes
// *Cause: There was a database management system (DBMS) file transfer
// error.
// *Action: Check the alert log for details.
//
45592, 0000, "Chunk move failure: RPC error on: \"%s\""
// *Document: Yes
// *Cause: There was a database management system (DBMS) file transfer
// error.
// *Action: Check the alert log for details.
//
45593, 0000, "Chunk move failure: file delete error on source shard"
// *Document: Yes
// *Cause: The backup file could not be deleted from the file system.
// *Action: Check the operating system log for details.
//
45594, 0000, "Chunk move failure: cannot put chunk into read-only state"
// *Document: Yes
// *Cause: There was an internal error which prevented a chunk state
// change.
// *Action: Check the alert log for details.
//
45595, 0000, "Chunk move failure: export metadata error"
// *Document: Yes
// *Cause: There was an internal error which prevented the metadata export.
// *Action: Check the alert log for details.
//
45596, 0000, "cannot remove region because it contains a shardgroup"
// *Document: Yes
// *Cause: The region was not empty because it contained at least one shardgroup.
// *Action: Remove all shardgroups from the region and retry the operation.
45597, 0000, "Chunk move failure: Data Pump error: \n %s"
// *Document: No
// *Cause: The Data Pump import operation failed.
// *Action: Check the alert log for details.
//
45598, 0000, "Shard %s is in converted state %s, it should be either \"PRIMARY\" or \"PHYSICAL STANDBY\"."
// *Document: Yes
// *Cause: The shard was in an invalid or unsupported state for use with
// sharding.
// *Action: Rebuild the shard using Oracle Database Configuration Assistant (DBCA)
// or reapply an RMAN backup to bring the shard to a supported state.
//
45599, 0000, "Shard %s is in converted state %s, but does not have a valid DBID."
// *Document: Yes
// *Cause: The discovered database identifier (DBID) for the shard was
// invalid, but the shard was already converted from a shard seed.
// *Action: Check the DBID for the shard and report this issue to Oracle
// Support Services.
//
/
/
/ 45600-45899 Reserved for Transparent Sensitive Data Management (TSDP)
/ Start error messages for TSDP
/
45600, 0000, "Transparent Sensitive Data Protection (TSDP) internal error"
// *Cause: There was an unexpected error during TSDP operation.
// *Action: Retry the command. If the problem persists, contact
// Oracle Support Services.
45601, 0000, "Invalid data has been found and discarded. Valid data has been imported."
// *Cause: The names of invalid or nonexistent database objects were found
// in the XML input.
// *Action: Check the trace files for the names of the invalid objects found
// in the XML input.
45602, 0000, "Schema %s does not exist."
// *Cause: The schema specified did not exist.
// *Action: Specify a valid schema.
45603, 0000, "Schema %s does not contain table %s."
// *Cause: The table specified did not exist in the schema.
// *Action: Specify a valid table.
45604, 0000, "Column %s.%s does not exist in schema %s."
// *Cause: The column specified did not exist.
// *Action: Specify a valid column.
45605, 0000, "invalid sensitive type %s"
// *Cause: A sensitive type that was associated with one or more
// sensitve columns did not exist.
// *Action: Ensure the valid sensitive type is mentioned. If it is a new
// sensitive type, include the definition in the XML input.
45606, 0000, "There was no sensitive column matching the given criteria."
// *Cause: There was no sensitive column matching the schema, table
// and column input.
// *Action: Ensure the valid column is mentioned.
45607, 0000, "Column %s.%s in schema %s has already been identified as sensitive."
// *Cause: The column was already identified as sensitive.
// *Action: Remove the column from the list of sensitive columns to be imported.
45608, 0000, "There are no sensitive columns for source %s."
// *Cause: No sensitive columns were found for the given source.
// *Action: Specify the valid source.
45609, 0000, "Sensitive type %s already exists."
// *Cause: The sensitive type already existed in the database.
// *Action: Specify a different name for the sensitive type.
45610, 0000, "Sensitive type %s does not exist."
// *Cause: The sensitive type did not exist in the database.
// *Action: Specify the valid sensitive type.
45611, 0000, "cannot drop sensitive type %s"
// *Cause: The sensitive type that is associated with one or more columns
// could not be dropped.
// *Action: Ensure the sensitive type is not associated with any column before
// dropping it.
45612, 0000, "A Transparent Sensitive Data Protection (TSDP) policy with name %s already exists."
// *Cause: A TSDP policy with the same name was found.
// *Action: Specify a different name for the policy.
45613, 0000, "invalid Oracle security feature"
// *Cause: The Oracle security feature specified was not supported by
// Transparent Sensitive Data Protection.
// *Action: Specify a valid security feature.
45614, 0000, "invalid Transparent Sensitive Data Protection (TSDP) policy %s"
// *Cause: The TSDP policy specified did not exist.
// *Action: Specify a valid policy.
45615, 0000, "One or more sensitive column types already exist."
// *Cause: Importing the list of sensitive columns succeeded. However,
// one or more sensitive column types already existed in the
// database and were not imported again. The corresponding
// column is associated with the existing type.
// *Action: Check the trace files for details regarding which sensitive
// column types were not imported.
45616, 0000, "Column %s.%s in schema %s is not identified as sensitive."
// *Cause: An attempt was made to alter a column that was not identified as
// sensitive.
// *Action: Specify a valid column.
45617, 0000, "Policy %s is not associated with sensitive column type %s."
// *Cause: The given policy was not associated with the sensitive column
// type.
// *Action: Specify the valid combination of policy and sensitive column type.
45618, 0000, "policy enforcement failure on one or more columns"
// *Cause: Policy enforcement on one or more columns encountered errors.
// *Action: Check the alert log or trace files for more details.
45619, 0000, "Policy %s is not enabled on column %s."
// *Cause: The given policy was not enabled on the column.
// *Action: Specify a valid policy.
45620, 0000, "Policy %s is already associated with sensitive column type %s."
// *Cause: The given policy was associated with the sensitive column type.
// *Action: Specify the valid policy and sensitive column type.
45621, 0000, "Disabling of a policy on one or more columns failed."
// *Cause: Errors were encountered while disabling one or more policies.
// *Action: Check the alert log for more details.
45622, 0000, "warnings generated during policy enforcement"
// *Cause: The cause of this error could be one or more of the following:
// - The policy that was associated with the sensitive column type
// of a column was not enabled on the column because no subpolicy
// matched the column properties.
// - There was no policy associated with the sensitive column type
// of a sensitive column.
// - A conflicting redaction policy was enabled on the table.
// *Action: Check the alert log for more details.
45623, 0000, "There is no policy associated with the sensitive column type."
// *Cause: There was no policy associated with the sensitive column type
// of a column.
// *Action: Check the alert log for more details.
45624, 0000, "reenabling protection failed before import"
// *Cause: Importing the list of sensitive columns failed because there was a
// problem in disabling protection on the columns. A subsequent
// attempt to reenable protection on the columns also failed.
// *Action: Check the alert log for more details.
45625, 0000, "reenabling protection failed after import"
// *Cause: Importing the list of sensitive columns succeeded. A subsequent
// attempt to reenable protection on the columns failed.
// *Action: Check the alert log for more details.
45626, 0000, "Dropping of one or more columns from the list failed."
// *Cause: Disabling protection on the column failed.
// *Action: Check the trace files for more details.
45627, 0000, "There are no sensitive columns of sensitive column type %s."
// *Cause: There was no column for the given sensitive column type.
// *Action: Specify a valid sensitive column type.
45628, 0000, "no policy associated with sensitive column type %s"
// *Cause: There was no policy associated with the sensitive column type.
// *Action: Specify a valid sensitive column type.
45629, 0000, "policy %s is enabled on one or more columns"
// *Cause: A Transparent Sensitive Data Protection policy that was enabled on
// a column could not be altered or dropped.
// *Action: Disable the policy before altering or dropping the policy.
45630, 0000, "Policy %s is associated with one or more sensitive types."
// *Cause: A Transparent Sensitive Data Protection policy that was associated
// with a sensitive column type could not be dropped.
// *Action: Disassociate the policy from the sensitive column type before
// dropping the policy.
45631, 0000, "Policy %s does not have the given condition."
// *Cause: The given condition was not found for the policy.
// *Action: Specify the valid condition for the policy.
45632, 0000, "default policy %s cannot be altered"
// *Cause: The default policy for Transparent Sensitive Data Protection could
// not be altered.
// *Action: Specify the valid policy to be altered.
45633, 0000, "default policy %s cannot be dropped"
// *Cause: The default policy for Transparent Sensitive Data Protection could
// not be dropped.
// *Action: Specify the valid policy to be dropped.
45634, 0000, "The security feature does not contain parameter %s."
// *Cause: An invalid parameter was found for the given security feature.
// *Action: Verify the parameters input to the policy.
45635, 0000, "invalid parameter found: %s"
// *Cause: An invalid parameter was found for the given security feature.
// *Action: Verify the parameters input to the policy.
45636, 0000, "Input parameter for \'%s\' is not valid."
// *Cause: Invalid input was given for the parameter.
// *Action: Enter valid input.
45637, 0000, "invalid condition given for policy condition "
// *Cause: The given condition was invalid.
// *Action: Enter a valid value for the condition.
45638, 0000, "Policy %s is enabled on one or more columns of sensitive type %s."
// *Cause: A Transparent Sensitive Data Protection policy that was enabled on
// one or more columns of a particular sensitive type could not be
// disassociated from the sensitive type.
// *Action: Ensure the policy is not enabled on a column of the given
// sensitive type.
45639, 0000, "discovery result cannot be imported"
// *Cause: One or more columns from the XML input were already identified
// as sensitive by a different source.
// *Action: Check the trace file for a list of sensitive columns that were
// already identified as sensitive.
45640, 0000, "Columns from SYS schema cannot be marked as sensitive."
// *Cause: A column in a SYS-owned table was being marked as sensitive.
// *Action: Ensure the column being marked as sensitive does not belong to
// SYS schema.
45641, 0000, "cannot specify SEC_RELEVANT_COLS parameter"
// *Cause: The SEC_RELEVANT_COLS parameter was specified while configuring a
// Transparent Sensitive Data Protection (TSDP) policy.
// SEC_RELEVANT_COLS_OPT parameter can be specified to indicate that
// TSDP should input the sensitive column as input to
// SEC_RELEVANT_COLS parameter at the time of enabling protection.
// *Action: Use the SEC_RELEVANT_COLS_OPT parameter to configure the security
// relevant column.
45642, 0000, "transparent sensitive data protection (TSDP) operation not supported"
// *Cause: An attempt was made to perform the TSDP operation from inside
// the application install or patch begin-end block.
// *Action: Perform the TSDP operation outside the application install or
// patch begin-end block.
45643, 0000, "specified column cannot be marked as sensitive."
// *Cause: An attempt was made to mark one of the virtual or hidden columns
// as sensitive.
// *Action: Retry the operation by removing the virtual or hidden column.
/
/ END error messages for TSDP (45600 - 45899)
/
/
/ 45900 - 45999 reserved for Recovery Manager (KRB*)
/
45900, 0000, "data file number %s already included as %s"
// *Cause: RMAN attempted to use the specified data file number, but this
// data file number was already in use by a different container
// database.
// *Action: Resolve the conflict and retry the command.
45902, 00000, "cannot rename data file '%s' - file was instantly restored."
// *Cause: During ALTER DATABASE RENAME or RMAN command SWITCH,
// the rename was specified for an instantly restored file.
// *Action: Rename the file that was not instantly restored or
// wait until the repopulation work is complete and the retry the
// command.
45903, 00000, "catalog instantly restored data file copy %s is not supported"
// *Cause: This data file copy was instantly restored.
// Cataloging such file is not supported.
// *Action: Do not request to catalog instantly restored data file copy.
45904, 0000, "instant restore of data file copy %s is not supported"
// *Cause: An attempt was made to restore a data file copy in instant
// restore mode. This is not supported.
// *Action: Do not restore a data file copy in instant restore mode.
/
45905, 00000, "deleting or restoring instantly restored data file %s is not supported"
// *Cause: This data file was instantly restored with the full option.
// A background process was repopulating the data file.
// An attempt to take the data file out of the process failed.
// Deleting or restoring such files is not supported.
// *Action: Retry the command later.
45906, 00000, "moving instantly restored data file %s is not supported"
// *Cause: This data file was instantly restored.
// Moving such file is not supported.
// *Action: Do not request to move instantly restored data file.
45907, 00000, "instant restore of data file %s failed"
// *Cause: During an instant restore, it was not possible to initialize
// the destination data file. There might be other messages on
// the error stack or alert log or trace file that indicate
// the specific reason for the failure.
// One common reason for this message is that the instant restore
// feature is disabled in this database.
// *Action: Check the other messages. If the situation cannot be resolved,
// then request a regular (not instant) restore.
45908, 00000, "cannot create a control file record for data file number %s"
// *Cause: This data file was instantly restored. An attempt was made to
// create a record in the control file for the data file.
// Unless the database is mounted, this command cannot be completed.
// *Action: Mount the database and retry the command.
45909, 00000, "restore, recover or block media recovery may be in progress"
// *Cause: A backup or copy was attempted while restore, recover or block
// media recovery was in progress. This error should be preceded by
// another error indicating file access enqueue problem for a file
// specified in a backup, copy or restore operation.
// *Action: Let restore, recover or block media recovery finish before
// starting a backup or copy operation.
45910, 00000, "cannot look up the rewrapped key for tablespace %s"
// *Cause: During transport, an encrypted tablespace could not find
// its rewrapped key as part of an RMAN cross-platform command.
// *Action: Connect to the respective pluggable database and check
// if the master table is created.
45911, 00000, "cannot restore as encrypted/decrypted on database with compatibility below 12.2"
// *Cause: Restore with encryption and decryption is only supported on 12.2
// compatible databases and above.
// *Action: Upgrade database or restore without encryption/decryption.
45912, 00000, "cannot restore as encrypted or decrypted from backup piece having compatibility of Oracle Database earlier than release 11g release 2 (11.2)"
// *Cause: An attempt was made to restore with encryption and decryption for
// backups with compatibility less or equal to Oracle Database 11g
// release 2 (11.2).
// *Action: Create a backup of Oracle Database 11g release 2 (11.2) database
// or, restore without encryption or decryption.
45913, 00000, "cannot backup file %s because it belongs to dropped PDB"
// *Cause: The indicated file was not included in the backup because
// it belongs to a dropped pluggable database (PDB).
// *Action: Do not request to backup dropped PDB files.
45914, 00000, "cannot backup a mounted control file of type backup"
// *Cause: An attempt was made to backup a control file when the mounted
// control file at that time was a backup control file. This is not
// allowed.
// *Action: Mount a current control file and retry the operation.
45915, 00000, "physical block size %0!s does not match logical block size %1!s"
// *Cause: The physical block size and logical block size of the backup piece
// did not match.
// *Action: Ensure that the physical block size size and logical block size
// match before copying the backup piece.
45916, 00000, "must use backup control file that has dropped PDB with GUID %s"
// *Cause: Some restored files belonged to the dropped pluggable database (PDB)
// with respect to the current control file.
// *Action: Restore and mount a backup control file that has the dropped PDB.
45917, 00000, "nonexistent backup piece or data file \"%s\" in the current container"
// *Cause: An attempt was made to access a backup piece or data file. This
// attempt failed because the specified file is not known to the
// current container.
// *Action: Specify the name of an existing file that can be accessed by the
// current container. Check the relevant V$ table for a list of
// possible files.
/////////////////////////////////////////////////////////////////////////////
// END error messages for Recovery Manager (45900 - 45999)
/////////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////////////////////
// 46000 - 46249 Reserved for fusion security error messages
/////////////////////////////////////////////////////////////////////////////
//
/////////////////////////////////////////////////////////////////////////////
// 46000 - 46049 Reserved for XS Data Security
/////////////////////////////////////////////////////////////////////////////
46000, 00000, "invalid option to apply XS Data Security"
// *Cause: The input value was not a valid option to apply XS Data Security.
// *Action: Use a valid option to apply XS Data Security.
46001, 00000, "argument %s is not valid for XS Data Security policies"
// *Cause: An illegal argument value was used with DBMS_RLS to apply XS Data Security.
// *Action: Use the XS_DATA_SECURITY API to apply XS Data Security.
46003, 00000, "Column \"%s\" is not valid in data security policy for \"%s\""
// *Cause: An invalid column was specified in the data security policy.
// *Action: Correct the column name in the policy.
//
46004, 00000, "XS Data Security policy is not applied on %s.%s"
// *Cause: A table without an XS Data Security policy applied was specified.
// *Action: Specify a table with one XS Data Security policy applied.
//
46005, 00000, "multiple XS Data Security policies applied on %s.%s"
// *Cause: A table with more than one XS Data Security policy applied was specified.
// *Action: Specify a table with one XS Data Security policy applied.
//
46006, 00000, "cannot mix VPD column and XS column constraint policies"
// *Cause: The object was protected by both VPD (Virtual Private Database)
// column security and XS column constraint policies.
// *Action: Disable or drop either the VPD or XS column policies.
//
46007, 00000, "no XS Data Security policy associated with %s.%s"
// *Cause: A table not associated with an XS Data Security policy was specified.
// *Action: Specify a table associated with an XS Data Security policy.
//
46008, 00000, "multiple XS Data Security policies associated with %s.%s"
// *Cause: A table associated with more than one XS Data Security policy was specified.
// *Action: Specify a table associated with one XS Data Security policy.
//
46019, 00000, "User-built Static ACL Materialized View does not exist"
// *Cause:A non-existing user-built Static ACL Materialized View was specified
// *Action: Create a user-built Static ACL Materialized View with the
// specified name or use system-built Static ACL views
//
46020, 00000, "User-built Static ACL Materialized View has invalid schema"
// *Cause:A user-built Static ACL Materialized View was specified
// but with an incorrect schema
// *Action: Create a user-built Static ACL Materialized View with
// at least the required columns with correct names and types
//
46021, 00000, "Invalid refresh mode specified for Static ACL Materialized View"
// *Cause:The refresh mode specified for the Materialized View supporting
// static ACLs is invalid.
// *Action: Specify either "ON DEMAND" or "ON COMMIT" for parameter
// refresh_mode
//
46022, 00000, "Invalid name specified for user-built Static ACL Materialized View"
// *Cause:The name specified for the Static ACL Materialized View (ACLMV) is
// reserved for system-built ACLMVs.
// *Action: Rename the user-built Static ACL Materialized View
//
46023, 00000, "Application Session affinity is not the same as when the cursor was parsed."
// *Cause: The security context was changed and was different from the time the
// cursor was parsed.
// *Action: Make sure the security context is the same as when the cursor was
// parsed.
//
46024, 00000, "The policy schema differs from the object schema for Static ACL Materialized View based XDS policy."
// *Cause: The specified object schema was different from the policy schema.
// *Action: Make sure the object and the policy have the same schema.
//
46025, 00000, "no static rule specified in applied policy"
// *Cause: The policy applied on the table did not contain any static rules.
// *Action: Ensure the applied policy has at least one static rule.
//
46026, 00000, "creation of static ACL materialized view (MV) failed"
// *Cause: Creation of the static access control
// list (ACL) materialized view (MV) failed.
// *Action: Check the trace file for detailed error information.
//
46049, 00000, "XS Security - Data Security tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
/
/////////////////////////////////////////////////////////////////////////////
// 46050 - 46100 Reserved for XS Security Sessions (XSS)
/////////////////////////////////////////////////////////////////////////////
46050, 00000, "Oracle Real Application Security internal error."
// *Cause: There was an Oracle Database Real Application Security internal error.
// *Action: None.
46051, 00000, "invalid application user specified"
// *Cause: An invalid application user was specified.
// *Action: Check the user name and execute the function or procedure again.
46052, 00000, "invalid session ID specified"
// *Cause: An invalid XS Security session ID was specified.
// *Action: Check the session ID and execute the function or procedure again.
46053, 00000, "invalid cookie specified"
// *Cause: An invalid XS Security session cookie was specified.
// *Action: Check the session cookie and execute the function or procedure
// again.
46054, 00000, "invalid namespace specified"
// *Cause: An invalid XS session application namespace or system-defined
// namespace was specified. Certain operations are not allowed on
// the system-defined namespace.
// *Action: Check the namespace and execute the function or procedure again.
46055, 00000, "invalid role specified"
// *Cause: An invalid application role was specified.
// *Action: Check the role and execute the function or procedure again.
46056, 00000, "invalid namespace or attribute specified"
// *Cause: An invalid XS Security application namespace or attribute
// was specified.
// *Action: Check the namespace and attribute, and execute the function or
// procedure again.
46057, 00000, "namespace already exists"
// *Cause: The specified XS Security application namespace was already
// in existence.
// *Action: Execute the function or procedure with a different namespace.
46058, 00000, "attribute %s is invalid"
// *Cause: An invalid XS Security application namespace attribute was
// specified.
// *Action: Check the attribute and execute the function or procedure.
46059, 00000, "Invalid ACL identifier specified"
// *Cause: The specified ACL identifier is invalid.
// *Action: Check the ACL identifier, and execute the function or procedure
// again with a valid ACL ID.
46060, 00000, "user name not specified"
// *Cause: An application user was not specified.
// *Action: Execute the function or procedure with a user name.
46061, 00000, "session ID not specified"
// *Cause: XS Security session ID was not specified.
// *Action: Execute the function or procedure with a session ID.
46062, 00000, "Namespace not specified"
// *Cause: XS Security application namespace was not specified.
// *Action: Execute the function or procedure with a namespace.
46063, 00000, "not attached to XS Security session"
// *Cause: There was no attachment to an XS Security session.
// *Action: Attach to an XS Security session and execute the function or procedure.
46064, 00000, "attribute name not specified"
// *Cause: XS Security application namespace attribute name was not
// specified.
// *Action: Execute the function or procedure with an attribute name.
46065, 00000, "attribute value not specified"
// *Cause: XS Security application namespace attribute value was not
// specified.
// *Action: Execute the function or procedure with an attribute value.
46066, 00000, "inactivity timeout not specified"
// *Cause: XS Security session inactivity timeout was not specified.
// *Action: Execute the function or procedure with an inactivity timeout value.
46067, 00000, "cookie not specified"
// *Cause: XS Security session cookie was not specified.
// *Action: Execute the function or procedure with a cookie value.
46068, 00000, "role not specified"
// *Cause: XS Security role was not specified.
// *Action: Execute the function or procedure with a Role value.
46069, 00000, "operation disallowed in an application session"
// *Cause: Operations were blocked when an application session was attached.
// *Action: Try the operation later after the application session is detached.
46070, 00000, "insufficient privileges"
// *Cause: An attempt was made to execute an XS Security session
// function or procedure without the appropriate privilege.
// *Action: Ask the administrator to perform the operation or to grant the
// appropriate privilege.
46071, 00000, "Error occured in event handler %s"
// *Cause: An error or exception was returned by the error handling function
// invoked as part of the current operation.
// *Action: Check the trace files to identify the source of the error in the
// event handling function. Attempt the operation again after the
// error has been resolved. Also, abort attach session since the
// changes made to the session by the event handler might not have
// been recorded because of the error.
46072, 00000, "Column width too small"
// *Cause: The size of the column or variable used to store the output of this
// function or procedure is too small.
// *Action: Increase the size of the column or variable and try again.
46073, 00000, "cookie already in use by another session"
// *Cause: The specified XS Security session cookie was used by
// another XS Security session.
// *Action: Execute the function or procedure with a different cookie.
46074, 00000, "session ID mismatch"
// *Cause: The specified session ID does not match the attached session ID.
// *Action: Execute the function or procedure without a session ID or with a
// matching attached session.
46075, 00000, "already attached to an application user session"
// *Cause: The current database session is already attached to an application
// user session.
// *Action: Detach from the current application user session before attaching
// to the new application user session.
46076, 00000, "The specified name length not within valid range."
// *Cause: The length of the name was shorter or longer than allowed limits.
// *Action: Try again with a new name with a length less than the maximum or
// or more than the minimum allowed.
46077, 00000, "Length of value too large"
// *Cause: The specified attribute value is too large.
// *Action: Execute the function or procedure again with a smaller attribute
// value.
//
46078, 00000, "Invalid event type specified"
// *Cause: The event type specified is invalid.
// *Action: Reattempt the operation with an invalid event type.
46079, 00000, "invalid external principal specified"
// *Cause: An XS Security principal already existed with same name.
// *Action: Specify another external principal and try again.
46080, 00000, "User status is currently inactive"
// *Cause: User was marked inactive.
// *Action: Change status in enterprise directory to active and try again.
46081, 00000, "User's password has expired"
// *Cause: User password was expired.
// *Action: Change the user's password and update status to active.
46082, 00000, "User's account was locked"
// *Cause: The user's account is locked.
// *Action: Update user's status to Active in Enterprise Directory and try
// again.
46083, 00000, "Cannot update the GUID of the principal"
// *Cause: The GUID of the principal existed or the external source was not set.
// *Action: NONE.
46084, 00000, "cannot update or delete system-seeded XS objects."
// *Cause: An attempt was made to update or delete system-seeded XS objects.
// *Action: Do not attempt to update or delete system-seeded XS objects.
46085, 00000, "Cannot add a proxy user when there was no proxy roles."
// *Cause: An attempt was made to add a proxy user to a target user when proxy roles did not exist.
// *Action: Verify the proxy roles and try again.
46086, 00000, "Cannot detach from a direct-login XS session"
// *Cause: An attempt was made to detach from an XS session created by a
// direct password login.
// *Action: To detach and destroy the XS session, logout of the DB session.
//
46087, 00000, "Switching users not allowed for a proxy session"
// *Cause: An attempt was made to switch users within a proxy session.
// *Action: Switch back to original user and try again.
//
46088, 00000, "operation disallowed in application session"
// *Cause: The specified operation was not allowed in an application session.
// *Action: None.
46089, 00000, "Unsupported verifier type"
// *Cause: This verifier was not currently supported.
// *Action: Execute again with a different verifier type.
//
46090, 00000, "Requested event handler not registered for the event"
// *Cause: An attempt was made to update or delete nonregistered event handler.
// *Action: Please verify event handler name.
//
46091, 00000, "Requested event handler already registered for the event"
// *Cause: An attempt was made to re-register an event handler.
// *Action: Please verify event handler name.
//
46092, 00000, "Requested event handler does not exist"
// *Cause: An attempt was made to register a nonexistent event handler.
// *Action: Please verify event handler name or create the event handler.
//
46093, 00000, "Cannot destroy a direct-login XS session"
// *Cause: An attempt was made to destroy an XS session created by a
// direct password login.
// *Action: To destroy the XS session, logout of the DB session.
//
46094, 00000, "XS user not effective"
// *Cause: An attempt was made to create an XS session by a user that is
// not effective.
// *Action: To create the XS session, contact the administrator to check
// the effective dates on the user.
//
46095, 00000, "Invalid error code supplied"
// *Cause: An error code with an illegal value was supplied.
// *Action: Use an error code from the range of valid values.
//
46096, 00000, "An attribute in a namespace cannot have both default value and first read event set."
// *Cause: Both default value and first read were specfied in namespace template.
// *Action: Specify either default value or first read for the attribute in
// the namespace, but not both.
//
46097, 00000, "The %s did not exist in the %s."
// *Cause: An attempt was made to delete an XS artifact which was not
// in existence within the scope.
// *Action: Check if the XS artifact was created or referenced within the
// scope.
//
46098, 00000, "The %s already exists in the %s."
// *Cause: An attempt was made to create or refer to an XS artifact which was
// already in existence within the scope.
// *Action: Check if the XS artifact name is unique within the scope.
//
46099, 00000, "Feature unsupported or not implemented"
// *Cause: This feature was not supported or implemented.
// *Action: None.
//
46100, 00000, "XS session operations are disallowed during the execution of a definer's rights program unit."
// *Cause: An attempt was made to do an XS session operation that could modify
// the current security context inside a definer's rights program unit.
// *Action: Change the program unit to invoker's rights.
/
/////////////////////////////////////////////////////////////////////////////
// 46101 - 46149 Reserved for XS Security Security Class and ACL
/////////////////////////////////////////////////////////////////////////////
46101, 00000, "Circular definition for aggregate privilege %s in security class %s"
// *Cause: Definition of an aggregate privilege contained itself.
// *Action: Fix the aggregate privilege definition.
46102, 00000, "Privilege %s aggregated in security class %s is not found"
// *Cause: Definition of an aggregate privilege contained a privilege that is
// not defined in this or parent security classes.
// *Action: Fix the aggregate privilege definition.
46103, 00000, "Circular definition for security class %s"
// *Cause: Security class definition inherited from itself through circular definition.
// *Action: Fix the security class definition.
46104, 00000, "Security class %s cannot inherit from base security classes"
// *Cause: Definition of a security class specified an internal base security
// class as a parent security class.
// *Action: Remove the internal base security class from the "inherits-from" list.
46105, 00000, "unable to load security class %s"
// *Cause: The specified security class did not exist.
// *Action: Create the security class.
46106, 00000, "Missing parent security class for security class %s"
// *Cause: The specified security class did not have any parent security class.
// *Action: Add a parent security class using "inherits-from" tag.
46107, 00000, "Privilege %s not found in the associated security classes"
// *Cause: The specified privilege did not exist in the security classes that
// were associated with the ACLs.
// *Action: Use a security class that contains the specified privilege.
46108, 00000, "Invalid security class targetNamespace or name."
// *Cause: The security class targetNamespace attribute was either null or was
// longer than 4000 characters. Or, the security class name attribute
// was either null or was longer than 1024 characters.
// *Action: Provide valid targetNamespace and name attributes.
46109, 00000, "Duplicate definition for privilege %s in security class %s."
// *Cause: The privilege name in the security class was previously defined
// in another security class.
// *Action: Provide a unique name for the privilege.
46110, 00000, "XS Security - ACL tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
46111, 00000, "Security Class %s specified in the ACL %s does not exist."
// *Cause: An invalid security class was specified in the ACL.
// *Action: Specify a valid security class.
46112, 00000, "Duplicate security class name %s under targetnamespace %s"
// *Cause: The security class name under the targetnamespce was also used
// for another security class.
// *Action: Provide a unique name for the security class.
46113, 00000, "Invalid identity value for the XS operator parameter at position '%s'"
// *Document: NO
// *Cause: An XS Security operator was used with an invalid
// identity value for one of its parameters.
// *Action: Specify a valid value.
46114, 00000, "ACL name %s not found."
// *Cause: An invalid ACL name was used as one of the operator parameters.
// *Action: Specify a valid ACL name.
46115, 00000, "error raised during evaluation of a data realm"
// *Cause: During SQL execution, evaluation of a data realm failed
// with an error.
// *Action: Find the cause of the error from the error stack.
46116, 00000, "The ACL %s is referenced by a namespace template."
// *Cause: An attempt was made to delete an access control list (ACL)
// which was referenced by a namespace template.
// *Action: Delete the namespace template first if the ACL needs to be deleted.
46117, 00000, "The ACL %s is set on a user or dynamic role."
// *Cause: An attempt was made to delete an access control list (ACL)
// that was set on a user or dynamic role.
// *Action: Set the ACL on the user or dynamic role to NULL, or delete the
// user or dynamic role if the ACL needs to be deleted.
46118, 00000, "ACL %s schema must be SYS."
// *Cause: An attempt was made to use an access control list (ACL) whose
// schema was not SYS.
// *Action: Check and use an ACL whose schema is SYS.
46119, 00000, "ACL must not be NULL."
// *Cause: An attempt was made to specify a NULL value for an access control
// list (ACL).
// *Action: Remove the NULL parameter, or specify an existing ACL.
46148, 00000, "XS Security - Application Session tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
46149, 00000, "XS Security - Security Classes tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
46150, 00000, "XS Security - XS Principals tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
46151, 00000, "XS Security - MidTier Caches tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
46152, 00000, "XS Security - invalid %s specified"
// *Document: NO
// *Cause: An XS Security procedure was used with an invalid
// value for one of the parameters.
// *Action: Specify a valid value.
46153, 00000, "XS Security - Purge existing application sessions when database is restarted"
// *Document: NO
// *Cause: This is an internal event and must be enabled only under the
// supervision of Oracle Support Services or development.
// *Action: N/A
/
/////////////////////////////////////////////////////////////////////////////
// 46200 - 46249 Reserved for XS Security Sessions (XSS) - continued
/////////////////////////////////////////////////////////////////////////////
46200, 00000, "Attribute cannot be deleted. The attribute is seeded from the template."
// *Cause: An attempt was made to delete an attribute that was seeded
// from the template from which this namespace was created.
// *Action: Attempt to delete only custom attributes.
46201, 00000, "Attribute %s already exists in namespace %s."
// *Cause: An attempt was made to create an attribute that
// already exists within the given namespace.
// *Action: Make sure the attribute name is unique within the namespace.
46202, 00000, "handler specified in the namespace template does not exist"
// *Cause: An attempt was made to create a namespace template with an invalid handler function.
// *Action: Specify a valid handler function in the template.
46203, 00000, "handler is not specified in the namespace template"
// *Cause: An attempt was made to create a template or a custom attribute
// with events specified. However, a handler function was not specified
// in the template.
// *Action: Specify a valid handler function in the template.
46204, 00000, "Multiple UID or GUID specified for the resource."
// *Cause: An attempt was made to create a resource with multiple UIDs or GUIDs specified in the document.
// *Action: Provide, at most, one UID or GUID for the resource in the document.
46205, 00000, "User with empty GUID cannot create session."
// *Cause: An attempt was made by an user with an empty GUID to create a session.
// *Action: Update the GUID for the user.
46206, 00000, "Negative inactivity timeout value not allowed."
// *Cause: An attempt was made to set the inactivity timeout time to a negative value.
// *Action: Specify a non-negative inactivity timeout value.
46207, 00000, "During global callback execution, %s is not allowed."
// *Cause: An attempt was made to execute a disallowed session operation during
// global callback execution.
// *Action: Remove the invalid session operation from callback function.
46208, 00000, "Circular callback call caused by %s"
// *Cause: Circular callback call caused an infinite chain of callback
// function executions.
// *Action: Check the event handling functions to identify the source
// of the circular callback call. Attempt the operation again
// after the error has been resolved.
46209, 00000, "User switch is disallowed for administrative operation."
// *Cause: An attempt was made to switch user with administrative operation.
// *Action: Attach the application session to a database session first.
46210, 00000, "Source user is not anonymous in user assignment operation."
// *Cause: An attempt was made to assign user to a named user.
// *Action: Change source user to the anonymous user first.
46211, 00000, "XS entity name length not within valid range."
// *Cause: An attempt was made to create an XS entity with a name length
// less than the minimum or more than the maximum allowed.
// *Action: Ensure the name length is in the valid range (between 1 and 128).
46212, 00000, "XS entity with this name already exists."
// *Cause: An attempt was made to create an XS entity with a name that
// already belongs to another entity.
// *Action: Use a different name and try again.
46213, 00000, "An unexpected constraint violation occurred during creation of an XS entity."
// *Cause: An attempt was made to create an XS entity resulting in an
// unexpected constraint violation.
// *Action: Check with the DBA or security administrator for resolution.
46214, 00000, "Deletion of the XS entity is not allowed while dependencies exist."
// *Cause: An attempt was made to delete an XS entity with dependent
// entities in the system.
// *Action: Remove the dependencies and try again.
46215, 00000, "XS entity by the name %s did not exist."
// *Cause: A reference was made to an XS entity that did not exist.
// *Action: Review the entity reference and try again.
46216, 00000, "XS entities are not related."
// *Cause: An attempt was made to remove a relation that did not exist.
// *Action: Review the entity reference and try again.
46217, 00000, "Operation is not allowed."
// *Cause: An unexpected operation was performed.
// *Action: Check with the DBA or security administrator for resolution.
46218, 00000, "Unauthorized proxy user"
// *Cause: The current user was not an authorized proxy user of the client user during a switching user operation.
// *Action: Add the current user as a proxy user of the client user.
//
46219, 00000, "Role version numbers mismatch in server and mid-tier."
// *Cause: There was another mid-tier attached to the server session with a different set of roles.
// *Action: Reattach the session supplying the current set of roles.
46220, 00000, "database is in readable standby mode; changes will not be saved"
// *Cause: An attempt was made to change an application session in readable
// standby mode.
// *Action: None.
46221, 00000, "cannot modify an application user that is currently connected"
// *Cause: An attempt was made to modify an application user that is currently
// logged on.
// *Action: Make sure the application user is logged off, then repeat the command.
46222, 00000, "Real Application principal name %s conflicts with another user or role name."
// *Cause: There was already a user or role with that name.
// *Action: Specify a different user or role name.
46230, 00000, "XS administrative operation failed."
// *Cause: An unexpected error occurred during the requested XS
// administrative operation.
// *Action: None.
46231, 00000, "Granted role is not a regular role."
// *Cause: A nonregular role was granted to a principal.
// *Action: Grant a regular role to a principal.
46232, 00000, "Circular grant for role"
// *Cause: The role was granted from itself through circular operation.
// *Action: Fix the role grant operation.
46233, 00000, "Circular definition for ACL %s"
// *Cause: The ACL was inherited from itself through circular definition.
// *Action: Fix the ACL definition.
46235, 00000, "Policy parameter %s did not exist."
// *Cause: The policy parameter did not exist.
// *Action: Review the parameter definition and try again.
46236, 00000, "Invalid policy parameter type"
// *Cause: Invalid parameter type was specified.
// *Action: Use the correct parameter type.
46237, 00000, "Mid-tier cache synchronization failed"
// *Cause: An unexpected error occurred during mid-tier cache synchronization.
// *Action: None.
46238, 00000, "Database user or role '%s' does not exist"
// *Cause: An invalid database user or role was specified as the principal
// name.
// *Action: Make sure the database principal is a valid database user or role.
//
46239, 00000, "Key manager not initialized."
// *Cause: A request to sign the message could not be processed because the
// key manager was not initialized.
// *Action: Reinitialize the key manager and resubmit the request.
//
46240, 00000, "Application proxy user is already configured with a schema."
// *Cause: An attempt was made to add a schema to an application proxy user that
// already was configured with a schema.
// *Action: Remove the schema configuration of the application proxy user and try
// again.
46241, 00000, "Application proxy user is not configured with the schema."
// *Cause: An attempt was made to remove a schema from an application proxy user
// that was not configured.
// *Action: None.
//
46242, 00000, "Granting a role to XSGUEST is not allowed."
// *Cause: An attempt was made to grant a role to the XSGUEST seeded user.
// *Action: None.
46243, 00000, "The dispatcher's session does not exist."
// *Cause: The dispatcher's session timed out due to inactivity.
// *Action: Increase the inactivity timeout for the dispatcher's session.
46244, 00000, "The request is not signed by the dispatcher."
// *Cause: A request was made without the dispatcher's signature. The server
// is configured to accept requests signed by the dispatcher only.
// *Action: Ask the administrator to configure the mid-tier allowing the dispatcher
// signature. Or, ask the administrator to configure the server to not be
// in dispather-only mode.
46245, 00000, "Invalid session or namespace request"
// *Cause: The request message was corrupt.
// *Action: Check with the DBA or security administrator for resolution.
46246, 00000, "session operation failed"
// *Cause: An attempt was made to either update an XS Data Security session
// which did not exist, or to create an XS Data Security session which
// already existed, or to attach a direct-login XS Data Security
// session.
// *Action: None.
46247, 00000, "detach completed; session changes are not saved"
// *Cause: The XS Data Security session is detached successfully, but session
// changes are not saved due to updating an XS Data Security session
// which did not exist.
// *Action: None.
46248, 00000, "This type of database link is not supported."
// *Cause: An attempt was made to use an unsupported database link type in an XS
// Data Security session.
// *Action: Use a supported database link type.
/
/////////////////////////////////////////////////////////////////////////////
// 46250 - 46350 Reserved for Database Auditing
/////////////////////////////////////////////////////////////////////////////
46250, 00000, "Invalid value for argument '%s'"
// *Cause: Input value was not valid for the procedure.
// *Action: Use a valid option.
46251, 00000, "Value for argument '%s' out of range"
// *Cause: Input value was out of range.
// *Action: Use a value within allowed range.
46252, 00000, "Cannot complete the operation, overlapping job already exists"
// *Cause: Cleanup job already existed which spanned the given audit trail type.
// *Action: Drop the existing job.
46253, 00000, "Cannot complete the operation, overlapping property already exists"
// *Cause: The property already exists which spans the given audit trail type.
// *Action: Clear the existing property.
46254, 00000, "'%s' already exists"
// *Cause: The value being set already existed.
// *Action: Delete the existing entry.
46255, 00000, "Incorrect job name specified"
// *Cause: The job did not exist or was not created by DBMS_AUDIT_MGMT package.
// *Action: Create the job using DBMS_AUDIT_MGMT package.
46256, 00000, "Internal error: Audit Table not partitioned"
// *Cause: Invalid operation on a non partitioned table.
// *Action: Contact Oracle Support Services.
46257, 00000, "Property '%s' cannot be cleared"
// *Cause: The property could not be cleared.
// *Action: None. The property can only be set or reset.
46258, 00000, "Cleanup not initialized for the audit trail"
// *Cause: DBMS_AUDIT_MGMT.INIT_CLEANUP was not called for the erroring audit trail.
// *Action: Invoke the procedure, DBMS_AUDIT_MGMT.INIT_CLEANUP.
46260, 00000, "Error during audit trail cleanup"
// *Cause: The audit trail cleanup operation could not be completed.
// *Action: Check the UNIX error number for a possible operating system error.
// If there is no error, contact Oracle Support Services.
46261, 00000, "Error during audit trail cleanup, internal error"
// *Cause: The audit trail cleanup could not be completed because of an internal error.
// *Action: Contact Oracle Support Services.
46262, 00000, "Audit table(s) cannot be moved to '%s' tablespace"
// *Cause: The tablespace was either unavailable or did not have enough space
// to accomodate the audit table being moved.
// *Action: Make sure that the tablespace is online and has enough space
// for the audit tables being moved.
46263, 00000, "The audit trail is already initialized for cleanup"
// *Cause: DBMS_AUDIT_MGMT.INIT_CLEANUP was already invoked for the audit trail
// type.
// *Action: None.
46264, 00000, "Error during DBMS_AUDIT_MGMT operation"
// *Cause: Could not complete the DBMS_AUDIT_MGMT operation.
// *Action: Check the PL/SQL error stack and trace files for a possible error.
// Fix the cause and retry the operation. If the error is internal or
// if there is no error, contact Oracle Support Services.
46265, 00000, "Subset of audit trail is already initialized"
// *Cause: Audit Trail was initialized which spans the given audit trail type.
// *Action: Use DBMS_AUDIT_MGMT.DEINIT_CLEANUP to deinitialize conflicting audit trail types.
46266, 00000, "Missing value for argument '%s' in Oracle RAC enabled database"
// *Cause: The DBMS_AUDIT_MGMT API was executed in an Oracle RAC enabled
// database and AUDIT_TRAIL_TYPE was one of AUDIT_TRAIL_OS or
// AUDIT_TRAIL_XML. But, Oracle RAC instance number for which
// DBMS_AUDIT_MGMT API was run, was not supplied.
// *Action: Input a valid Oracle RAC instance number for which the
// configuration must be done.
46267, 00000, "Insufficient space in '%s' tablespace, cannot complete operation"
// *Cause: Could not complete the operation because the DBMS_AUDIT_MGMT API
// involved movement of one or more audit tables and there was not
// enough space in the destination tablespace.
// *Action: Turn on tracing using DBMS_AUDIT_MGMT.SET_DEBUG_LEVEL to find
// the amount of space required. Then, allocate that space in the
// destination tablespace, even if destination tablespace datafile has
// AUTOEXTEND option turned on. And then, retry the operation.
46268, 00000, "Conflicting operation on audit table(s)"
// *Cause: Audit tables were being operated by more than one DBMS_AUDIT_MGMT
// API from different sessions. The simultaneous execution of the
// following API with one another and with itself can cause the
// conflict: INIT_CLEANUP, DEINIT_CLEANUP, SET_AUDIT_TRAIL_LOCATION
// and MOVE_DBAUDIT_TABLES.
// *Action: Wait until the execution of one of the API's completes and try
// executing the API again.
46269, 00000, "Conflicting operation on audit files"
// *Cause: Audit files were being operated by more than one DBMS_AUDIT_MGMT
// API from different sessions. The simultaneous execution of the
// CLEAN_AUDIT_TRAIL API with itself can cause the conflict.
// *Action: Wait until the execution of one of the API's complete and try
// executing the API again.
46270, 00000, "event to turn off Audit Commit Delay enforcement"
// *Document: NO
// *Cause: This is an internal event and must be enabled.
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
46271, 00000, "Error during DBMS_AUDIT_MGMT operation; database I/O suspended"
// *Cause: An I/O attempt occurred during DBMS_AUDIT_MGMT operation and the
// database I/O was suspended.
// *Action: Retry the operation after resuming database I/O suspension. If
// database I/O is not suspended, contact Oracle Support Services.
46272, 00000, "Subset of audit trail is already deinitialized"
// *Cause: Audit trail was deinitialized which spans the given audit trail type.
// *Action: Use DBMS_AUDIT_MGMT.INIT_CLEANUP to initialize conflicting audit
// trail types.
46273, 00000, "DBMS_AUDIT_MGMT operation failed in one of the PDB"
// *Cause: The executed DBMS_AUDIT_MGMT operation failed in one of the PDB.
// *Action: Check the trace files for the PDB information where the operation
// failed. Fix the cause and retry the operation. If the error is
// internal or if there is no error, contact Oracle Support Services.
46274, 00000, "Error during DBMS_AUDIT_MGMT operation; tablespace '%s' not available"
// *Cause: The tablespace associated with Unified Audit Trail is either invalid
// or is offline.
// *Action: Check if the tablespace is valid and make sure the tablespace is
// online and writable.
46275, 00000, "Conflicting operations on '%s' table"
// *Cause: Audit trail table was being operated by more than one API from
// different sessions. The simultaneous execution of
// DBMS_AUDIT_MGMT.INIT_CLEANUP or
// DBMS_AUDIT_MGMT.SET_AUDIT_TRAIL_LOCATION with
// SA_SYSDBA.CREATE_POLICY or SA_SYSDBA.DROP_POLICY can cause the
// conflict.
// *Action: Wait for the completion of the conflicting SA_SYSDBA procedure and
// try executing the DBMS_AUDIT_MGMT API again.
46276, 00000, "DBMS_AUDIT_MGMT operation on unified audit trail failed"
// *Cause: Audit records were not generated in the unified audit trail.
// *Action: Generate audit records in the unified audit trail
// and retry the operation.
46277, 00000, "Conflicting operation on unified audit trail"
// *Cause: Unified audit trail is being operated by more than one
// DBMS_AUDIT_MGMT API from different sessions. The simultaneous
// execution of the following API with one another and with itself
// can cause the conflict: FLUSH_UNIFIED_AUDIT_TRAIL,
// LOAD_UNIFIED_AUDIT_FILES, CLEAN_AUDIT_TRAIL, and
// SET_AUDIT_TRAIL_LOCATION.
// *Action: Wait until the execution of one of the API's complete and try
// executing the API again.
46278, 00000, "Conflicting operation using DBMS_AUDIT_MGMT routines"
// *Cause: One of the following API's was concurrently executed with itself or
// with another API in separate sessions causing a conflict:
// - SET_LAST_ARCHIVE_TIMESTAMP
// - CLEAR_LAST_ARCHIVE_TIMESTAMP
// - CLEAN_AUDIT_TRAIL
// - SET_AUDIT_TRAIL_PROPERTY
// - CLEAR_AUDIT_TRAIL_PROPERTY.
// *Action: Wait until the execution of one of the API's completes and try
// executing the API again.
46279, 00000, "Input value for argument '%s' exceeds the maximum length."
// *Cause: The identifier name generated after concatenating with
// 'AMGT$DP$' exceeded 30 or 128 bytes.
// *Action: Specify a value which does not exceed the maximum length after
// concatenation.
//
// 46340 - 46500 Use for Auditing
//
46340, 00000, "Command cannot have both BY <user-list> and IN SESSION <session-information> clauses together"
// *Cause: BY <user-list> clause was supplied with IN SESSION
// <session-information> clause in the command.
// *Action: Use either BY <user-list> or IN SESSION <session-information>
// clause.
46341, 00000, "ALL STATEMENTS option cannot be supplied with BY SESSION clause"
// *Cause: An attempt was made to use ALL STATEMENTS audit option with
// BY SESSION clause. ALL STATEMENTS audit option can be configured
// with BY ACCESS only.
// *Action: Specify BY ACCESS instead of BY SESSION.
46342, 00000, "NOAUDIT command cannot be executed with IN SESSION clause"
// *Cause: An attempt was made to use IN SESSION <session-information> clause
// in NOAUDIT command.
// *Action: None.
46343, 00000, "Cannot drop AUDSYS user"
// *Cause: An attempt was made to drop the AUDSYS user that hosts
// the audit trail.
// *Action: None
46349, 00000, "event to turn off OS flush for XML audit file write"
// *Document: No
// *Cause: This is an internal event and must be enabled only
// under the supervision of Oracle Support Services
// or development.
// *Action: N/A
46350, 00000, "Audit policy %s already applied with the BY clause."
// *Cause: An attempt was made to apply audit policy with the EXCEPT clause
// which was already applied with the BY clause.
// *Action: Remove audit policy using the NOAUDIT command.
46351, 00000, "Audit policy %s already applied with the EXCEPT clause."
// *Cause: An attempt was made to apply audit policy with the BY clause which
// was already applied with the EXCEPT clause.
// *Action: Remove audit policy using the NOAUDIT command.
46352, 00000, "NOAUDIT command with the EXCEPT clause is not allowed."
// *Cause: An attempt was made to remove audit policy using NOAUDIT command
// with the EXCEPT clause.
// *Action: Remove audit policy selectively using NOAUDIT command with
// the BY clause.
46353, 00000, "missing or invalid audit policy name."
// *Cause: A valid audit policy name was expected.
// *Action: Specify a valid audit policy name.
46354, 00000, "missing or invalid audit context or attribute name."
// *Cause: A valid context or attribute name was expected.
// *Action: Specify a valid context attribute name.
46355, 00000, "missing or invalid privilege audit option."
// *Cause: Creating or altering the audit policy was attempted with
// an invalid system privilege audit option.
// *Action: Use a valid system privilege audit option.
46356, 00000, "missing or invalid action audit option."
// *Cause: Creating or altering the audit policy was attempted with
// an invalid action audit option.
// *Action: Use a valid action audit option.
46357, 00000, "Audit policy %s not found."
// *Cause: The specified audit policy object did not exist in the database.
// *Action: Use the correct audit policy name and try again.
46358, 00000, "Audit policy %s already exists."
// *Cause: The specified audit policy object already existed in the database.
// *Action: Use a different name and try again.
46359, 00000, "Invalid auditing option for %s."
// *Cause: Creating or altering the audit policy was attempted with
// an invalid audit option for the object.
// *Action: Use a valid audit option for the object.
46360, 00000, "Same auditing option cannot be both added and dropped in audit policy."
// *Cause: Altering the audit policy was attempted for adding and dropping the
// same auditing option in the audit policy.
// *Action: Choose either to add or drop the audit option.
46361, 00000, "Audit policy cannot be dropped as it is currently enabled."
// *Cause: An attempt was made to drop the audit policy which is currently enabled.
// *Action: Disable the audit policy before dropping.
46362, 00000, "Could not translate variable ORACLE_BASE."
// *Cause: An attempt to obtain the value for ORACLE_BASE failed.
// *Action: Make sure the variable is set.
46363, 00000, "Audit directory '%s' not found."
// *Cause: Could not find the specified audit directory.
// *Action: Make sure the audit directory is created.
46364, 00000, "Audit directory '%s' could not be created."
// *Cause: Could not create the specified audit directory.
// *Action: Make sure the Oracle process has permissions to create the audit
// directory.
46365, 00000, "Audit file '%s' could not be created."
// *Cause: Could not create the specified audit file.
// *Action: Make sure the Oracle process has permissions to create the audit
// files in the audit directory.
46366, 00000, "File '%s' is not a recognized Oracle audit file."
// *Cause: The file found in Oracle audit directory was not a valid Oracle
// audit file.
// *Action: Remove the file from the audit directory and try the action again.
46367, 00000, "Database is not opened for write; cannot complete operation."
// *Cause: An operation requiring the database to be open in read/write mode
// was attempted.
// *Action: Open the database in read/write mode.
46368, 00000, "Audit policy does not have a simple rule condition."
// *Cause: Creating or altering the audit policy was attempted with a complex
// audit condition.
// *Action: Use a simple rule expression for audit policy condition.
46369, 00000, "An error occurred while evaluating audit policy condition."
// *Cause: Check the error stack for detailed error information.
// *Action: Fix the errors in the error stack and retry the operation.
46370, 00000, "cannot connect as AUDSYS user"
// *Cause: An attempt was made to connect to the database as AUDSYS user.
// *Action: Do not connect to the database as AUDSYS user.
46372, 00000, "audit file '%s' not found"
// *Cause: An operation was attempted on the audit file which was not available
// in the audit directory.
// *Action: Make sure the file exists in the $ORACLE_BASE/audit/$ORACLE_SID
// directory.
46373, 00000, "Audit policy '%s' must have at least one audit option."
// *Cause: An attempt was made to create, alter or enable the empty
// audit policy.
// *Action: Use at least one audit option in the audit policy.
46374, 00000, "error during AUDIT or NOAUDIT of audit policy in an Oracle RAC enabled database"
// *Cause: The operation could not be completed on one or more Oracle RAC instances.
// *Action: Check the trace file for more information.
// Ensure every instance in Oracle RAC is operational and
// retry the operation.
46375, 00000, "ASM Audit - Event to enable ASM Audit"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
46376, 00000, "FGA policy owner '%s' is not available"
// *Cause: An attempt to import Fine-Grained Audit (FGA) policy failed because
// the specified FGA policy owner has not been imported.
// *Action: Perform the import of the specified user schema and retry the operation.
46377, 00000, "Auditing cannot be configured on the specified system privilege."
// *Cause: An attempt was made to configure auditing on the system privilege which
// is not supported by the audit facility.
// *Action: None.
46378, 00000, "Cannot use bind variable in VERSIONS clause when the object has FGA policy defined on it."
// *Cause: The object being accessed had a fine-grained audit (FGA) policy
// defined on it and the VERSIONS clause contained a bind variable.
// *Action: Rewrite the query without the use of a bind variable in the VERSIONS
// clause.
46379, 00000, "generation of audit session ID failed with error '%d'"
// *Cause: An error was encountered while generating the audit session ID.
// *Action: Retry the operation and, if the error persists, contact
// Oracle Support Services.
46380, 00000, "invalid usage of EXCEPT clause"
// *Cause: Use of the EXCEPT clause and the USERS WITH GRANTED ROLES clause
// in the same AUDIT and NOAUDIT statements was not a valid combination
// *Action: Do not use the EXCEPT clause here.
46381, 00000, "audit configuration using global roles is not supported"
// *Cause: A global role was found in the enablement list.
// *Action: Remove the global role from the enablement list and retry the
// operation.
46382, 00000, "must disable unified audit policy on this role first"
// *Cause: The role being altered to IDENTIFIED GLOBALLY has unified audit
// policy enabled on users to whom it is directly granted. Audit
// configuration using global role is not supported.
// *Action: Use NOAUDIT POLICY command to disable the unified audit policy
// on users to whom this role is directly granted.
46383, 00000, "incorrect order of unified audit options"
// *Cause: The order in which audit options were mentioned was incorrect.
// *Action: Make sure privilege audit options are followed by action audit
// options which in turn should be followed by role audit options.
46384, 00000, "incorrect order of unified audit policy clause"
// *Cause: The order in which ADD, DROP or CONDITION clauses were mentioned
// was incorrect.
// *Action: Make sure the ADD clause is followed by the DROP clause which
// in turn should be followed by the CONDITION clause.
46385, 00000, "DML and DDL operations are not allowed on table \"%s\".\"%s\"."
// *Cause: A DML or DDL operation was attempted on a unified auditing
// internal table.
// *Action: No action required. Only Oracle is allowed to perform such
// operations on a unified auditing internal table.
46386, 00000, "error during TRANSFER_UNIFIED_AUDIT_RECORDS operation"
// *Cause: Either the database was not open in the read/write mode, or the
// transfer of the unified audit records was already in progress.
// *Action: Open the database in read/write mode and rerun the
// TRANSFER_UNIFIED_AUDIT_RECORDS operation after the
// ongoing transfer process finishes.
46387, 00000, "Cannot perform this operation on unified audit internal table"
// *Cause: An attempt was made to perform an operation that is not allowed
// on a non-partitioned unified audit internal table.
// *Action: No action required. This operation can only be performed on
// partitioned unified audit internal table.
46388, 00000, "unified audit files space usage in container is too high"
// *Cause: Space usage by unified audit files in the current container has
// exceeded the value of MAX_AUDIT_STORAGE for the container.
// *Action: Create some space by deleting the old audit records using
// DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL or open the container
// in the read/write mode and execute
// DBMS_AUDIT_MGMT.LOAD_UNIFIED_AUDIT_FILES.
/
/////////////////////////////////////////////////////////////////////////////
// 46500 - 46599 Reserved for Auditing in Consolidated Databases
/////////////////////////////////////////////////////////////////////////////
//
46500, 00000, "User is not a common user."
// *Cause: An attempt was made to apply the common audit configuration to a
// local user. Common audit configuration can be
// applied only to common users.
// *Action: Specify a common user.
/
46501, 00000, "Object is not a common object."
// *Cause: Object audit option for the common audit policy was specified on
// a local object. A common audit policy can have object audit
// options on common objects only.
// *Action: Specify a common object.
/
46503, 00000, "not connected to a pluggable database"
// *Cause: An attempt was made to create a local audit policy or
// configuration while not connected to a pluggable database.
// Local audit policy or configuration can be created only when
// connected to a pluggable database.
// *Action: Connect or switch session to a pluggable database to create
// local audit policy or configuration.
/
46504, 00000, "AUDIT command cannot specify ON <object> and CONTAINER clauses together."
// *Cause: An attempt was made to specify the CONTAINER clause with the AUDIT
// command while configuring object auditing. The CONTAINER clause is
// not supported for object auditing using the SQL AUDIT command.
// *Action: Do not specify the CONTAINER clause while configuring object
// auditing using SQL AUDIT command.
/
46505, 00000, "Role is not a common role."
// *Cause: An attempt was made to apply the common audit configuration to a
// local role. Common audit configuration can be applied to
// common roles only.
// *Action: Specify a common role.
/
46506, 00000, "FGA handler schema is not common user."
// *Cause: An attempt was made to create fine-grained Audit (FGA) policy on
// common object and associated handler schema is not common user.
// *Action: Specify FGA handler schema as common userappropriately.
/
46507, 00000, "FGA object name is not a common object."
// *Cause: An attempt was made to create common fine-grained Audit (FGA)
// policy on a local object. A common FGA policy can only be
// configured on common object.
// *Action: Specify a common object.
/
46508, 00000, "not connected to root container"
// *Cause: An attempt was made to create a Fine-Grained Auditing (FGA) policy
// on an object-linked common object from within a pluggable
// database (PDB).
// *Action: Connect to the root and create FGA policies on object-linked
// common objects.
/
/////////////////////////////////////////////////////////////////////////////
// 46600 - 46899 Reserved for Key Management Errors
/////////////////////////////////////////////////////////////////////////////
//
46600, 00000, "invalid ADMINISTER KEY MANAGEMENT command"
// *Cause:
// *Action:
/
46601, 00000, "missing KEYSTORE, ENCRYPTION, KEY, or TAG keyword"
// *Cause:
// *Action:
/
46602, 00000, "missing OPEN or CLOSE keyword"
// *Cause:
// *Action:
/
46603, 00000, "invalid ADMINISTER KEY MANAGEMENT CREATE command"
// *Cause:
// *Action:
/
46604, 00000, "invalid or missing keystore file name"
// *Cause: The required keystore file name was invalid or missing.
// *Action: Specify a valid keystore file name.
/
46605, 00000, "master key identifier is invalid or missing"
// *Cause:
// *Action:
/
46606, 00000, "tag is invalid or missing"
// *Cause:
// *Action:
/
46607, 00000, "client secret is invalid or missing"
// *Cause:
// *Action:
/
46608, 00000, "client identifier is invalid or missing"
// *Cause:
// *Action:
/
46609, 00000, "export or import secret is invalid or missing"
// *Cause:
// *Action:
/
46610, 00000, "expecting SELECT query that returns the master key identifiers"
// *Cause:
// *Action:
/
46612, 00000, "import file name is invalid or missing"
// *Cause:
// *Action:
/
46614, 00000, "export file name is invalid or missing"
// *Cause:
// *Action:
/
46615, 00000, "missing WITH or CONTAINER keyword"
// *Cause:
// *Action:
/
46616, 00000, "master key is invalid or missing"
// *Cause:
// *Action:
/
46617, 00000, "master key identifier is invalid or missing"
// *Cause:
// *Action:
/
46620, 00000, "backup for the keystore cannot be taken"
// *Cause: Either the specified backup location was not an ASM path name when
// the configured keystore location was an ASM path or the specified
// backup location was an ASM path name when the configured keystore
// location was not an ASM path.
// *Action: Either specify an ASM path name for the backup location if the
// keystore location is an ASM path or specify a non-ASM path name for
// the backup location if the keystore location is not an ASM path.
/
46621, 00000, "no backup identifier specified"
// *Cause: Backup identifier was not specified.
// *Action: Provide a valid backup identifier.
/
46622, 00000, "location of the backed up keystore is incorrect"
// *Cause: Keystore location where the backup was to be created was incorrect.
// *Action: Provide a valid location to backup the keystore.
/
46623, 00000, "cannot create the keystore file name"
// *Cause: Keystore name could not be formed possibly due to the incorrectly
// specified keystore location.
// *Action: Verify the location to where the keystore can be backed up.
/
46624, 00000, "cannot find the source keystore"
// *Cause: The source keystore for which the backup was requested was not
// found.
// *Action: Verify that the source keystore exists and try again.
/
46625, 00000, "backup keystore already exists"
// *Cause: A backup of the keystore of the same name already existed in the
// given location.
// *Action: Change the location of the backup keystore or the backup identifier
// of the backup keystore and try again.
/
46626, 00000, "cannot create a backup of the keystore"
// *Cause: The backup of the keystore could not be created.
// *Action: Check the trace file for more information and try again.
/
46627, 00000, "keystore password mismatch"
// *Cause: The keystore password specified did not match that of the keystore
// that was open.
// *Action: Specify the correct keystore password.
/
46628, 00000, "cannot alter the software keystore password"
// *Cause: An attempt was made to alter the software keystore password.
// *Action: Check the viability of the keystore and replace the keystore
// from the backup if required and try to alter the keystore
// password.
/
46629, 00000, "keystore was not open after the alter keystore operation"
// *Cause: The keystore password was changed. However, the keystore was
// closed during this operation.
// *Action: Reopen the keystore with the new password.
/
46630, 00000, "keystore cannot be created at the specified location"
// *Cause: Keystore could not be created at the specified location because
// a keystore of the same type already exited.
// *Action: Specify a different location to create the keystore. If no keystore
// exists and the operation is failing, check the trace file and
// try again.
/
46631, 00000, "keystore needs to be backed up"
// *Cause: The keystore was not backed up. For this operation to proceed, the
// keystore must be backed up.
// *Action: Backup the keystore and try again.
/
46632, 00000, "password-based keystore does not exist"
// *Cause: Password-based keystore was missing for this operation. Auto login
// keystore can be created from a password-based keystore only.
// *Action: Specify a location where the password-based keystore exists.
/
46633, 00000, "creation of a password-based keystore failed"
// *Cause: Password-based keystore could not be created at the specified
// location due to either incorrect file permissions for Oracle on
// the specified location or due to the nonexistence of the specified
// location.
// *Action: Check the trace file for more information, create permissions on
// the specified location, or specify a different location and try
// again.
/
46634, 00000, "creation of a local auto login keystore failed"
// *Cause: The local auto login keystore could not be created at the specified
// location due to the incorrect password specified for the
// password-based keystore or due to incorrect file permissions for
// Oracle on the specified location or due to the nonexistence of the
// specified location.
// *Action: Check the trace file for more information, specify the correct
// password for the password-based keystore, create permissions on
// the specified location, or specify a different location and try
// again.
/
46635, 00000, "creation of an auto login keystore failed"
// *Cause: The auto login keystore could not be created at the specified
// location due to the incorrect password specified for the
// password-based keystore or due to incorrect file permissions for
// Oracle on the specified location or due to the nonexistence of the
// specified location.
// *Action: Check the trace file for more information, specify the correct
// password for the password-based keystore, create permissions on
// the specified location, or specify a different location and try
// again.
/
46636, 00000, "cannot add second keystore to the target keystore"
// *Cause: The second keystore could not be added to the target keystore.
// *Action: Check trace files for more information. Delete the target keystore
// and try merging the two keystores again.
/
46637, 00000, "cannot add first keystore to the target keystore"
// *Cause: The first keystore could not be added to the target keystore.
// *Action: Check trace files for more information. Delete the target keystore
// and try merging the two keystores again.
/
46638, 00000, "merging of the two keystores failed"
// *Cause: The two keystores could not be merged.
// *Action: Check trace files for more information. If the target keystore is
// corrupted, replace it from the backup and try merging the two
// keystores again.
/
46639, 00000, "backup of keystore failed during migration"
// *Cause: Keystore location was not configured correctly in the sqlnet.ora
// file.
// *Action: Keystore location is missing or not correct in the sqlnet.ora
// file. Specify the correct keystore location for migration
// and backup.
/
46640, 00000, "incorrect file name for exporting keys "
// *Cause: The file name of the file to which keys from the keystore will
// be written was incorrect or invalid.
// *Action: Verify the file name. Ensure that both the full path and the
// file name are provided.
/
46641, 00000, "incorrect file name for importing keys "
// *Cause: The file name of the file from which the keys will be read
// and saved in the keystore was incorrect or invalid.
// *Action: Verify the file name. Ensure that both the full path and the
// file name are provided.
/
46642, 00000, "key export destination file already exists"
// *Cause: The file name specified as the export destination for keys exported
// from the keystore was already in existence.
// *Action: Specify a different file name that does not exist.
/
46643, 00000, "file from which keys are to be imported does not exist"
// *Cause: The specified file from which the keys are to be imported into the
// keystore did not exist.
// *Action: Specify the name of a file that contains keys exported from the
// keystore.
/
46644, 00000, "creation or open of file to store the exported keys failed"
// *Cause: Creation or opening of the file specified as the key export
// destination, where the keys exported from the keystore were to be
// written, failed.
// *Action: Verify that the file name is valid and that the Oracle process has
// sufficient privilege to create, open and write to the file.
/
46645, 00000, "open of file from which keys are to be imported failed"
// *Cause: The file specified as the key import source, from which the keys
// were to be imported into the keystore, could not be opened.
// *Action: Verify that the file name is valid and that the Oracle process has
// sufficient privilege to read the file.
/
46646, 00000, "file from which keys are to be imported is invalid or lacks needed file permission"
// *Cause: The file specified as the key import source, from which the keys were
// to be imported, was not a valid file or does not have the needed file
// access permission.
// *Action: Specify a valid file, containing keys which were previously
// exported from the keystore. Also, ensure that the file has
// read and write access permission.
/
46647, 00000, "specified protection differs from that specified in the file"
// *Cause: The file specified as the key import source, from which the keys are
// to be imported, had different protection from what was specified in
// the SQL command.
// *Action: Provide a valid protection option, ensuring that it is the same
// protection option that was in the file from which the keys are to
// be imported.
/
46648, 00000, "cannot commit the keys to the keystore"
// *Cause: The operation of writing the keys to the keystore failed.
// *Action: Verify that the keystore is not corrupt. Copy the keystore from
// the backup if it is corrupt. Retry the command.
/
46649, 00000, "master key with the specified identifier does not exist"
// *Cause: Master key with the specified identifier does not exist in the
// keystore.
// *Action: Specify a valid master key identifier for the SQL command and retry
// the command.
/
46650, 00000, "cannot retrieve information for a master key identifier"
// *Cause: The master key or the master key information associated with a
// specified master key identifier did not exist.
// *Action: Check the contents of the trace file to identify the faulty master
// key identifier. Either fix or drop the faulty master key, then
// retry the command.
/
46651, 00000, "cannot create a master key"
// *Cause: Master key creation failed.
// *Action: Check the trace file for errors and retry the command.
/
46652, 00000, "cannot create tag for the master key"
// *Cause: Creation of the tag for the specified master key failed.
// *Action: Check the contents of the trace file for errors and retry the
// command.
/
46653, 00000, "cannot retrieve master key information"
// *Cause: Retrieval of the master key information for the specified master key
// identifier failed.
// *Action: Check the contents of the trace file for errors and retry the
// command.
/
46654, 00000, "cannot add the imported keys to the keystore"
// *Cause: The operation of writing the imported keys to the keystore failed.
// *Action: Check the contents of the trace file for more information on the
// cause of the failure and retry the command.
/
46655, 00000, "no valid keys in the file from which keys are to be imported"
// *Cause: The specified keystore, from which keys are to be imported, did not
// contain any valid keys.
// *Action: None.
/
46656, 00000, "operation not valid for container database"
// *Cause: The specified operation was not supported for the container
// database.
// *Action: None.
/
46657, 00000, "the source keystores are the same"
// *Cause: The specified source keystores to be merged were the same. There is
// no need to merge these keystores.
// *Action: Check the locations and types of the specified keystores. Specify
// the correct path and types for the source keystores, if necessary.
/
46658, 00000, "keystore not open in the container"
// *Cause: The keystore was not open in the container.
// *Action: Open the keystore in the container.
/
46659, 00000, "master keys for the given PDB not found"
// *Cause: The master keys for the specified pluggable database (PDB) could not
// be retrieved.
// *Action: Check if the master keys were generated for the specified PDB and
// retry the command.
/
46660, 00000, "the source and target keystores are the same"
// *Cause: The specified source and target keystores to be merged were the same.
// There is no need to merge these keystores.
// *Action: Check the locations and types of the specified keystores. Specify
// the correct path and types for the source and target keystores, if
// necessary.
/
46661, 00000, "keystore not open in root container"
// *Cause: The root container keystore was not open.
// *Action: Open the root container keystore.
/
46662, 00000, "master keys not created for all PDBs"
// *Cause: Creation of the master key failed for one or more pluggable
// databases (PDBs).
// *Action: Check the trace files for errors. Create the keys in PDBs where
// the operation failed or retry the command.
/
46663, 00000, "master keys not created for all PDBs for REKEY"
// *Cause: Creation of the master key failed for one or more pluggable
// databases (PDBs) and as such REKEY failed for these PDBs.
// *Action: Check the trace files for errors. REKEY the keys in PDBs where
// the master keys could not be created or retry the command.
/
46664, 00000, "master keys not created for any PDBs during REKEY"
// *Cause: Creation of the master key failed for all pluggable databases (PDBs).
// *Action: Check the contents of the trace file for more information on the
// cause of the failure and retry the command.
/
46665, 00000, "master keys not activated for all PDBs during REKEY"
// *Cause: Activation of the master key failed for one or more pluggable
// databases (PDBs) and as such REKEY failed for these PDBs.
// *Action: Check the trace files for errors. Activate the keys in PDBs where
// the master keys were created but not activated or retry the
// command.
/
46666, 00000, "master keys not created or activated for all PDBs during REKEY"
// *Cause: Creation of the master key failed for one or more pluggable
// databases (PDBs). Further, activation of one or more created master
// keys also failed for some PDBs and as such REKEY failed on these
// PDBs.
// *Action: Check the trace files for errors. REKEY the PDBs where the master
// keys could not be created. Activate the keys in PDBs where the
// master keys were created but not activated or retry the command.
/
46667, 00000, "client not found in the keystore"
// *Cause: An entry with the given client name was not found in the keystore.
// *Action: Add the secret for the given client to the keystore, if required.
/
46668, 00000, "client already exists in the keystore"
// *Cause: An entry with the given client name was already in existence in
// the keystore.
// *Action: Delete or update the entry with the client name.
/
46669, 00000, "the target keystore does not exist"
// *Cause: The location specified for the target keystore did not contain a
// valid keystore, or target keystore did not have valid file
// permissions.
// *Action: Specify a different location for the target keystore where it
// exists. Also, check the file permissions of the target keystore.
/
46670, 00000, "client secret keystore operation failed"
// *Cause: The client secret keystore add, update or delete operation failed.
// *Action: Open the keystore and retry the client secret keystore operation.
/
46671, 00000, "master key not set in root container"
// *Cause: Master key was not set in the root container.
// *Action: Set the Master key in the root container.
/
46672, 00000, "backup keystore file name could not be stored"
// *Cause: The file name of the keystore backup could not be recorded in props$.
// *Action: Open the keystore and retry the backup operation.
/
46673, 00000, "write to the export file failed"
// *Cause: Oracle was unable to write an entry to the export file.
// *Action: Check the trace file for more information and retry the operation.
// If there is no trace information and trying the operation again
// fails, contact Oracle Support Services.
/
46674, 00000, "read from the export file failed"
// *Cause: Oracle was unable to read an entry from the export file.
// *Action: Check the trace file for more information and retry the operation.
// If there is no trace information and trying the operation again
// fails, contact Oracle Support Services.
/
46675, 00000, "write of keys for export failed"
// *Cause: Oracle was unable to write an entry for export.
// *Action: Check the trace file for more information and retry the operation.
// If there is no trace information and trying the operation again
// fails, contact Oracle Support Services.
/
46676, 00000, "read of keys for import failed"
// *Cause: Oracle was unable to read an entry for import.
// *Action: Check the trace file for more information and retry the operation.
// If there is no trace information and trying the operation again
// fails, contact Oracle Support Services.
/
46677, 00000, "specified backup identifier exceeds maximum length"
// *Cause: The backup identifier within the ASM file name of the keystore
// exceeded the maximum length of 12 characters.
// *Action: Specify a backup identifier that does not exceed the limit.
/
46678,0000, "cannot encrypt an identity column created with GENERATED BY DEFAULT or GENERATED ALWAYS"
// *Cause: An attempt was made to encrypt an identity column created with
// GENERATED BY DEFAULT or GENERATED ALWAYS keywords.
// *Action: An identity column created with the GENERATED BY DEFAULT or
// GENERATED ALWAYS keywords cannot be encrypted.
/
46679, 00000, "missing or invalid master key encryption algorithm"
// *Cause: An encryption algorithm for the master key was missing or invalid
// in the user command.
// *Action: Specify a valid algorithm: 'AES256', 'ARIA256', 'SEED128',
// or 'GOST256'.
/
46680, 00000, "master keys of the container database must be exported"
// *Cause: The master keys of the container database were not exported.
// *Action: Export the master keys of the container database before unplugging
// the container database.
/
46681, 00000, "reverse migration failed for PDB"
// *Cause: Reverse migration failed for one or more pluggable databases (PDB).
// *Action: Check the trace files for errors. Retry the command.
/
46683, 00000, "addition of master key string not supported with CONTAINER=ALL"
// *Cause: An attempt was made to add a master key with the same master key
// identifier to more than one container database. A user specified
// master key string with a master key identifier can be added to
// a single container only.
// *Action: Retry the operation without CONTAINER=ALL clause.
/
46684, 00000, "master key identifier exists in the keystore"
// *Cause: An attempt was made to add a master key with a master key
// identifier that was already present in the keystore.
// *Action: Specify a different value for the master key identifier in the
// master key string.
/
46685, 00000, "invalid master key identifier or master key value"
// *Cause: The master key identifier or master key value was invalid.
// To be valid, the values supplied for both the master key
// identifier and the master key value must be hex-encoded and must
// have the following properties:
// - For a master key value to be valid, its length must be a valid
// key length for the specified encryption algorithm.
// - For a master key identifier to be valid, it must have a length
// of 16 bytes.
// - For a master key identifier to be valid, it must have a
// non-zero value.
// *Action: Specify a correct value for the master key identifier or master key
// in the master key string.
/
46686, 00000, "missing or invalid master key string"
// *Cause: The master key string was missing or invalid.
// *Action: Specify the correct master key string.
/
46687, 00000, "operation not supported for HSM"
// *Cause: The specified operation is not supported with Hardware Security
// Module (HSM).
// *Action: Check the trace file for more details.
/
46688, 00000, "cannot move a master key"
// *Cause: The master key could not be moved out of the keystore.
// *Action: Check whether the specified master key identifiers are valid, and
// if they are found in the V$ENCRYPTION_KEYS view. Container keys can
// be moved from the CDB$ROOT only when the container is unplugged
// and dropped from the CDB. Check the trace file for additional
// errors if needed. Retry the command.
/
46689, 00000, "specified master key identifier does not exist in the keystore"
// *Cause: An attempt was made to move a master key that did not exist in the
// keystore.
// *Action: Check if the master key identifier exists in the keystore by
// querying the V$ENCRYPTION_KEYS view.
/
46690, 00000, "could not create wallet"
// *Cause: The new wallet used to store the keys to be moved could not be created.
// The cause could be the lack of permission to write to the
// directory for the Oracle user or the directory did not exist.
// *Action: Check the permissions for the Oracle user on the directory or
// check if the directory exists.
//
/
46691, 00000, "The value of the KEYSTORE_CONFIGURATION attribute is invalid."
// *Cause: An attempt was made to set or use an invalid value for
// the KEYSTORE_CONFIGURATION attribute of the TDE_CONFIGURATION
// instance initialization parameter.
// *Action: Use a valid value for the KEYSTORE_CONFIGURATION attribute
// of the TDE_CONFIGURATION instance initialization parameter.
// When using WALLET_ROOT, set the TDE_CONFIGURATION instance
// initialization parameter correctly in both the root and in
// the pluggable database.
// A value must be provided for the TDE_CONFIGURATION instance
// initialization parameter if a value is provided for the
// WALLET_ROOT instance initialization parameter, in order to
// fully specify the keystore configuration of the CDB$ROOT and
// of the pluggable database (either both parameters must be
// present, or both must be absent).
// For an ADMINISTER KEY MANAGEMENT ISOLATE KEYSTORE operation,
// the KEYSTORE_CONFIGURATION attribute of the CDB$ROOT must
// have the value FILE.
// For an ADMINISTER KEY MANAGEMENT ISOLATE KEYSTORE operation,
// if a value for the KEYSTORE_CONFIGURATION attribute is set in
// the pluggable database, it must have the value FILE.
// If the TDE_CONFIGURATION instance initialization parameter
// is not set in the pluggable database, the isolation operation
// automatically sets its KEYSTORE_CONFIGURATION attribute to FILE.
/
46692, 00000, "cannot close wallet"
// *Cause: An attempt was made to close the wallet when it was in use.
// *Action: Close the wallet in any pluggable database
// that is configured with an isolated wallet.
// Alternatively, use the FORCE KEYSTORE CLOSE clause
// of the ADMINISTER KEY MANAGEMENT command.
/
46693, 00000, "The WALLET_ROOT location is missing or invalid."
// *Cause: An attempt was made to perform a keystore operation when the
// instance initialization parameter WALLET_ROOT was missing
// or invalid.
// *Action: Start the database after setting the WALLET_ROOT instance
// initialization parameter to the directory where all of the
// wallets are stored.
/
46694, 00000, "The keys are already in the root keystore."
// *Cause: An attempt was made to unite an isolated keystore with
// the root keystore, but the keys of the isolated keystore
// were already present in the root keystore.
// *Action: No action is required. Check the value of the TDE_CONFIGURATION
// instance initialization parameter of your system and ensure that
// you are issuing the ADMINISTER KEY MANAGEMENT UNITE KEYSTORE
// command in the correct pluggable database.
/
46695, 00000, "The value of the TDE_CONFIGURATION instance initialization parameter is invalid."
// *Cause: An attempt was made to set or use an invalid value for
// the TDE_CONFIGURATION instance initialization parameter.
// *Action: Use a valid value for the TDE_CONFIGURATION instance
// initialization parameter. The KEYSTORE_CONFIGURATION attribute
// must be present and must have a valid value. During recovery,
// the CONTAINER attribute can also be specified and its value must
// be a valid container name. The CONTAINER attribute can only be
// be specified when the TDE_CONFIGURATION instance initialization
// parameter is modified in the CDB$ROOT, not when it is modified
// in a pluggable database.
/
46696, 00000, "A master key is required by another pluggable database."
// *Cause: An attempt was made to isolate a master key when it was still
// required by another pluggable database. Another pluggable
// database might still require the master key if the pluggable
// databases were clones of each other.
// *Action: Before attempting to isolate the keys of a pluggable database,
// perform an ADMINISTER KEY MANAGEMENT SET KEY command on each
// pluggable database that requires the master key, in order to
// remove any dependency on the master key being isolated.
// Alternately, include the FORCE clause and issue the ADMINISTER
// KEY MANAGEMENT FORCE ISOLATE KEYSTORE command, which causes the
// master keys of the pluggable database to be copied to the
// isolated keystore rather than moved to it, so that the keys
// remain available to any pluggable database that requires them.
/
46697, 00000, "Keystore password required."
// *Cause: The keystore password clause was not provided for this SQL
// command.
// *Action: Retry the command with a keystore password clause.
/
46698, 00000, "CDB$ROOT is not open."
// *Cause: CDB$ROOT was not open.
// *Action: Open the CDB$ROOT and retry the command.
/
46699, 00000, "cannot create a keystore"
// *Cause: A keystore could not be created.
// A combination of the following conditions prevented the operation:
// 1. The pluggable database was not open in read/write mode.
// Note that the pluggable database needs to be open in read/write
// mode for the KEYSTORE_MODE configuration of the pluggable
// database to be automatically changed to ISOLATED during
// the ADMINISTER KEY MANAGEMENT CREATE KEYSTORE command.
// 2. The KEYSTORE_MODE configuration of the pluggable
// database was UNITED (rather than ISOLATED).
// *Action: Open the pluggable database in read/write mode
// or configure the pluggable database as ISOLATED,
// and retry the ADMINISTER KEY MANAGEMENT
// CREATE KEYSTORE command.
/
46700, 00000, "failed to copy or move wallet"
// *Cause: An attempt was made to either copy or move the isolated wallet of
// the pluggable database (PDB) that was plugged.
// *Action: Ensure that the source wallet location and the file specified in
// XML exist on disk and are accessible from this database.
// Also, ensure that WALLET_ROOT is set and the directory specified
// in WALLET_ROOT exists on the disk.
/
46701, 00000, "failed to delete source wallet"
// *Cause: An attempt was made to delete the source wallet file during
// the pluggable database (PDB) plug with MOVE clause.
// *Action: Ensure that the source wallet file and the directory allow
// deletion of the wallet.
/
/////////////////////////////////////////////////////////////////////////////
// 46900 - 46950 Reserved for Proxy user errors
/////////////////////////////////////////////////////////////////////////////
//
46900, 00000, "unsupported proxy authentication"
// *Cause: A proxy authentication was attempted using an administrative
// privilege.
// *Action: Authenticate without any administrative privilege if proxy
// authentication is desired.
/
/////////////////////////////////////////////////////////////////////////////
// 46951 - 46980 Reserved for Oracle Password file related errors
/////////////////////////////////////////////////////////////////////////////
//
46951, 00000, "unsupported format for password file '%s'"
// *Cause: An attempt was made to use the Oracle password file which is not
// in legacy or in release 12.1 or higher format. The password file
// is either not present or may have become corrupt.
// *Action: Re-create the password file and grant the administrative privileges
// to users appropriately.
/
46952, 00000, "standby database format mismatch for password file '%s'"
// *Cause: An attempt was made to apply password file changes made on the
// primary database to the password file of the standby database,
// but there was a password file format mismatch which prevented
// the operation.
// *Action: Re-create the password file on the standby database using the
// same password file format as that of the primary database.
// Ensure that the password file format used on the standby database
// matches that of the primary database.
/
46953, 00000, "The password file is not in the 12.2 format."
// *Cause: An attempt was made to perform one of the following operations,
// but none of these operations are allowed while the password file
// is in LEGACY or in release 12.1 format.
// - Attempting to grant an administrative privilege to an external
// user (a user created as IDENTIFIED EXTERNALLY).
// - Attempting to change the authentication type of an
// administrative-privileged user from PASSWORD to EXTERNAL.
// - When a common user has an administrative privilege granted in a
// pluggable database (PDB) but no longer exists in the CDB$ROOT
// container, attempting to create this common user again in the
// root as IDENTIFIED EXTERNALLY.
// *Action: Create the password file in 12.2 format or migrate the existing
// password file to 12.2 format, then retry the operation.
/
/////////////////////////////////////////////////////////////////////////////
// 46981 - 46999 Reserved for Exadirect Secure
/////////////////////////////////////////////////////////////////////////////
//
//
46981, 00000, "Access to service %s from %s was denied."
// *Cause: Access to this service from this location was not allowed.
// *Action: Contact Oracle Support Services.
/
46982, 00000, "Internal error: driver access control operation is not supported"
// *Document: NO
// *Cause:
// *Action:
/
46983, 00000, "Internal error: invalid driver access control operation"
// *Document: NO
// *Cause:
// *Action:
/
46984, 00000, "Internal error: driver access control operation failed"
// *Document: NO
// *Cause:
// *Action:
/
46985, 00000, "Service FireWall - ACL tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services
// or development.
// *Action: N/A
/
46986, 0000, "Internal error: no security attribute for client connection"
// *Document: NO
// *Cause:
// *Action:
/
46987, 0000, "Access control propagation failed (error=%08x)."
// *Cause: The executed DBMS_SFW_ACL_ADMIN operation failed.
// *Action: Retry the operation.
/
46988, 0000, "Access control propagation timed out."
// *Cause: The executed DBMS_SFW_ACL_ADMIN operation timed out.
// *Action: Retry the operation.
/
// Copyright (c) 2004, 2017, Oracle and/or its affiliates. All rights reserved.
//
// DESCRIPTION
// e47000.msg - Provides the error messages for Database Vault product
//
// NOTES
// Concatenated with other .msg files to build the RDBMS message file.
// If you change this file, do the following:
// cd $SRCHOME/rdbms/mesg
// make concat
// make oraus.msb
//
// MODIFIED (MM/DD/YY)
// sjavagal 09/05/17 - Bug 26325568: add 47800, 47801, 47802 and 47803
// jibyun 04/17/17 - Bug 25906289: use numeric placeholders for correct
// translation
// qinwu 02/22/17 - proj 70151: add 47967, 47968, 47969, and 47970
// dalpern 10/15/16 - bug 22665467: add DV checks on DEBUG [CONNECT]
// sjavagal 10/03/16 - Bug23265486: Added 47247,47328,47034,47431 and 47350.
// sanbhara 05/22/16 - Bug 23177463 - adding 47430
// youyang 02/12/16 - add index function list
// jibyun 11/01/15 - introduce DIAGNOSTIC authorization
// kaizhuan 09/16/15 - Bug 21609808: Add 47910
// sanbhara 09/10/15 - Bug 21299474 - adding 47327.
// kaizhuan 06/18/15 - Bug 21099196: Add 47326
// yapli 05/26/15 - Bug 18354393: Add ORA-47945
// sanbhara 05/19/15 - Bug 21107486 - adding 47429.
// kaizhuan 05/15/15 - Bug 20619821: update 47503 and 47504
// kaizhuan 04/17/15 - Bug 20884867: update 47285
// kaizhuan 02/20/15 - Project 46814
// namoham 01/29/15 - Bug 20308342: Make maintenance auth error msgs more
// descriptive
// youyang 01/26/15 - add 47942
// youyang 08/12/14 - add 47941
// jibyun 10/27/14 - Bug 17937386: add ORA-47993
// kaizhuan 10/01/14 - Project 46812: add error messages 47106,
// 47107, 47108 and 47109.
// namoham 08/26/14 - Project 36761: maintenance authorization
// jibyun 08/06/14 - Project 46812: support for Database Vault policy
// namoham 03/25/14 - Bug 17850033: add 47940
// jheng 02/07/13 - Bug 16292773: add ORA-47939
// sanbhara 09/07/12 - Bug 14594374 - adding error 47504.
// yanchuan 07/25/12 - Bug 14374099: introduce error code 47959, 47960
// youyang 07/30/12 - bug14389719:add message for dv is not enabled on cdb
// root
// jdavison 05/31/12 - Fix messages with incorrect action format
// youyang 03/13/12 - add ddl authorization
// kaizhuan 02/13/12 - Bug 12670283: add error 47500 for DV sanity check
// kaizhuan 03/08/12 - Bug 8843200: add error 47349
// jibyun 03/09/12 - Bug 13728213: add 47412 and 47413
// youyang 12/23/11 - add 47971 and 47972 for proxy authorization
// jheng 01/30/12 - Bug 13629868: rename profile to capture
// yanchuan 01/25/12 - Bug 13560188: Introduce error code 47246
// jheng 01/25/12 - Bug 13615338: add error 47958
// yanchuan 10/17/11 - Bug 12776828: Message changes for ORA-47502
// jheng 10/14/11 - Bug 12668661: add error 47937
// jibyun 08/10/11 - Bug 7118790: Add error mesg 47411
// sanbhara 06/02/11 - Project 24121 - add new error msgs 47501, 47502
// jheng 5/26/11 - add new error codes for privilege profile
// jheng 09/28/09 - add new error code for DV Job and Datapump Auth
// jheng 08/05/10 - add ORA-47907 for bug 9941304
// jibyun 11/19/09 - Bug 829498: Add error messages for object deletion
// failures
// jsamuel 03/28/09 - add new error message for dvremov bug 8335937
// pknaggs 02/02/09 - 7832176 don't parse as DVSYS if !KZVDV_DVSYS_EXISTS
// youyang 11/07/08 - Add message for realm violation of granting and
// revoking roles
// jibyun 10/17/08 - Bug 7478215: Add new DV events, 47388 and 47389
// tchorma 05/02/06 -
// sgaetjen 04/14/06 - DV product name
// ayalaman 04/06/06 -
// sgaetjen 04/03/06 - add password profile messages and cause/actions
// for all
// sgaetjen 03/02/06 - add parameter check
// tchorma 02/12/06 - PL/SQL authorization errors
// tchorma 03/31/06 - 5131720: Dissallow invalid object types for realm
// protection
// sgaetjen 03/02/06 - add parameter check
// tchorma 02/12/06 - PL/SQL authorization errors
// ayalaman 01/25/06 - add error message for session state
// sgaetjen 01/17/06 - add custom rule set error code and message
// sgaetjen 01/10/06 - add command rule validation message
// sgaetjen 12/30/05 - add trace event
// sgaetjen 12/22/05 - add internal error
// sgaetjen 12/20/05 - Initial ADE checkin
// sgaetjen 12/20/05 - Created
47000, 00000, "Factor Type %s already defined"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47001, 00000, "Factor Type %s not found"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47002, 00000, "error creating Factor Type %s, %s"
// *Cause: An unexpected error occurred creating the factor type
// *Action: Please review the definition and retry the operation
47003, 00000, "error deleting Factor Type %s, %s"
// *Cause: An unexpected error occurred deleting the factor type
// *Action: Please review the definition and retry the operation
47004, 00000, "error updating Factor Type %s, %s"
// *Cause: An unexpected error occurred updating the factor type
// *Action: Please review the definition and retry the operation
47005, 00000, "error renaming Factor Type %s, %s"
// *Cause: An unexpected error occurred renaming the factor type
// *Action: Please review the definition and retry the operation
47020, 00000, "Factor %s already defined"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47021, 00000, "Factor %s not found"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47022, 00000, "error creating Factor %s, %s"
// *Cause: An unexpected error occurred creating the factor
// *Action: Please review the definition for accuracy and retry the operation
47023, 00000, "error deleting Factor %s, %s"
// *Cause: An unexpected error occurred deleting the factor
// *Action: Please review the definition for accuracy and retry the operation
47024, 00000, "error updating Factor %s, %s"
// *Cause: An unexpected error occurred updating the factor
// *Action: Please review the definition for accuracy and retry the operation
47025, 00000, "Factor Link already exists for %s and %s"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47026, 00000, "error creating Factor Link for %s and %s, %s"
// *Cause: An unexpected error occurred creating the factor link
// *Action: Please review the definition for accuracy and retry the operation
47027, 00000, "Factor Link does not exist for %s and %s"
// *Cause: The factor link referenced does not exist
// *Action: Please review the definition for accuracy and retry the operation
47028, 00000, "error deleting Factor Link for %s and %s, %s"
// *Cause: An unexpected error occurred deleting the factor link
// *Action: Please review the definition for accuracy and retry the operation
47029, 00000, "Factor type %s is used by one or more factors."
// *Cause: The specified factor type was used by existing factor(s).
// *Action: Remove the dependent factors and retry the operation.
47030, 00000, "Factor %s is referred by one or more factor links."
// *Cause: The specified factor was referred by existing factor link(s).
// *Action: Remove the dependent factor links and retry the operation.
47031, 00000, "Factor %s is used by one or more policy factors."
// *Cause: The specified factor was used by existing policy factor(s).
// *Action: Remove the dependent policy factors and retry the operation.
47032, 00000, "Factor %s is referred by one or more identities."
// *Cause: The specified factor was referred by existing identities.
// *Action: Remove the dependent identities and retry the operation.
47033, 00000, "Factor link for %s and %s is referred by one or more identity maps."
// *Cause: The specified factor link was referred by existing identity maps.
// *Action: Remove the dependent identity maps and retry the operation.
47034, 00000, "cannot rename default factor %s"
// *Cause: An attempt was made to rename a default factor. Default factors cannot be renamed.
// *Action: No action required.
47040, 00000, "Identity %s for Factor %s already defined"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47041, 00000, "Identity %s for Factor %s not found"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47042, 00000, "error creating Identity %s for Factor %s, %s"
// *Cause: An unexpected error occurred creating the identity
// *Action: Please review the definition for accuracy and retry the operation
47043, 00000, "error deleting Identity %s for Factor %s, %s"
// *Cause: An unexpected error occurred deleting the identity
// *Action: Please review the definition for accuracy and retry the operation
47044, 00000, "error updating Identity %s for Factor %s, %s"
// *Cause: An unexpected error occurred updating the identity
// *Action: Please review the definition for accuracy and retry the operation
47045, 00000, "Identity %s for Factor %s is used by one or more identity maps."
// *Cause: The specified identity was used by exiting identity map(s).
// *Action: Remove the dependent identity maps and retry the operation.
47046, 00000, "Identity %s for Factor %s is referred by one or more policy labels."
// *Cause: The specified identity was used by exiting policy label(s).
// *Action: Remove the dependent policy labels and retry the operation.
47060, 00000, "Identity map for Identity %s.%s, Factor Link %s, %s already defined for operation %s on %s"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47061, 00000, "Identity map for Identity %s.%s, Factor Link %s, %s not found for operation %s on %s"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47062, 00000, "error creating Identity map for Identity %s.%s, Factor Link %s, %s already defined for operation %s on %s"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47063, 00000, "error deleting Identity map for Identity %s.%s, Factor Link %s, %s already defined for operation %s on %s"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47080, 00000, "code %s already defined in group %s"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47081, 00000, "code %s not found in group %s"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47100, 00000, "Command rule %s already defined for %s.%s."
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47101, 00000, "Command rule %s not found for %s.%s."
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47102, 00000, "error creating command rule %s for %s.%s, %s"
// *Cause: An unexpected error occurred creating the command rule
// *Action: Please review the definition for accuracy and retry the operation
47103, 00000, "error deleting command rule %s for %s.%s, %s"
// *Cause: An unexpected error occurred deleting the command rule
// *Action: Please review the definition for accuracy and retry the operation
47104, 00000, "error updating command rule %s for %s.%s, %s"
// *Cause: An unexpected error occurred updating the command rule
// *Action: Please review the definition for accuracy and retry the operation
47105, 00000, "invalid object owner %s for command %s"
// *Cause: The object owner is invalid for this command
// *Action: Choose an object owner other than SYS or a wildcard for this
// command
47106, 00000, "Command rule %s already defined for clause %s with clause parameter %s."
// *Cause: The object with this name exists already.
// *Action: Choose a unique object name and retry the operation.
47107, 00000, "Command rule %s not found for clause %s with clause parameter %s."
// *Cause: The object being requested did not exist.
// *Action: Choose an object name that exists and retry the operation.
47108, 00000, "Command rule %s does not support clause level protection."
// *Cause: Oracle Database Vault did not support clause level protection for this command rule.
// *Action: Choose a valid command rule that supports clause level protection.
47109, 00000, "Command rule %s for clause %s with parameter %s does not support event level protection."
// *Cause: Oracle Database Vault did not support event level protection for this command rule.
// *Action: Choose a valid command rule that supports clause level protection.
47120, 00000, "Document %s already defined"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47121, 00000, "Document %s not found"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47140, 00000, "Factor expression %s already defined"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47141, 00000, "Factor expression %s not found"
// *Cause: The object being requested does not exists
// *Action: Choose an object name that exists and retry the operation
47160, 00000, "Factor link %s already defined"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47161, 00000, "Factor link %s not found"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47180, 00000, "Integration Policy for OLS Policy %s is already defined"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47181, 00000, "Integration Policy for OLS Policy %s not found"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47182, 00000, "Label algorithm %s not found"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47183, 00000, "error creating Integration Policy for OLS Policy %s, %s"
// *Cause: An unexpected error occurred creating the integration policy
// *Action: Please review the definition for accuracy and retry the operation
47184, 00000, "error updating Integration Policy for OLS Policy %s, %s"
// *Cause: An unexpected error occurred updating the integration policy
// *Action: Please review the definition for accuracy and retry the operation
47185, 00000, "error deleting Integration Policy for OLS Policy %s, %s"
// *Cause: An unexpected error occurred deleting the integration policy
// *Action: Please review the definition for accuracy and retry the operation
47200, 00000, "Integration Policy Factor already defined for Factor %s and Policy %s"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47201, 00000, "Integration Policy Factor not found for Factor %s and Policy %s"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47202, 00000, "error creating Integration Policy Factor for factor %s and policy %s, %s"
// *Cause: An unexpected error occurred creating the integration policy factor
// *Action: Please review the definition for accuracy and retry the operation
47203, 00000, "error deleting Integration Policy Factor for factor %s and policy %s, %s"
// *Cause: An unexpected error occurred deleting the integration policy factor
// *Action: Please review the definition for accuracy and retry the operation
47220, 00000, "Label %s for Identity %s.%s under OLS Policy %s already defined"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47221, 00000, "Label %s for Identity %s.%s under OLS Policy %s not found"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47222, 00000, "error creating Label %s for Identity %s.%s under OLS Policy %s, %s"
// *Cause: An unexpected error occurred creating the identity label
// *Action: Please review the definition for accuracy and retry the operation
47223, 00000, "error deleting Label %s for Identity %s.%s under OLS Policy %s, %s"
// *Cause: An unexpected error occurred deleting the identity label
// *Action: Please review the definition for accuracy and retry the operation
47240, 00000, "Realm %s already defined"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47241, 00000, "Realm %s not found"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47242, 00000, "error creating Realm %s, %s"
// *Cause: An unexpected error occurred creating the realm
// *Action: Please review the definition for accuracy and retry the operation
47243, 00000, "error deleting Realm %s, %s"
// *Cause: An unexpected error occurred deleting the realm
// *Action: Please review the definition for accuracy and retry the operation
47244, 00000, "error updating Realm %s, %s"
// *Cause: An unexpected error occurred updating the realm
// *Action: Please review the definition for accuracy and retry the operation
47245, 00000, "error renaming Realm %s, %s"
// *Cause: An unexpected error occurred renaming the realm
// *Action: Please review the definition for accuracy and retry the operation
47246, 00000, "cannot change default realm %s to mandatory realm"
// *Cause: An attempt was made to change the realm type of this default realm
// to mandatory realm.
// *Action: No action required.
47247, 00000, "cannot rename default realm %s"
// *Cause: An attempt was made to rename a default realm. Default realms cannot be renamed.
// *Action: No action required.
47260, 00000, "Realm authorization to %s for realm %s already defined."
// *Cause: The object with this name exists already.
// *Action: Choose a unique object name and retry the operation.
47261, 00000, "Realm authorization to %s with %s scope for realm %s not found."
// *Cause: The object being requested does not exist.
// *Action: Choose an object name that exists and retry the operation.
47262, 00000, "error creating realm authorization to %s for realm %s, %s"
// *Cause: An unexpected error occurred creating the realm authorization.
// *Action: Review the definition for accuracy and retry the operation.
47263, 00000, "error deleting realm authorization to %s for realm %s, %s"
// *Cause: An unexpected error occurred deleting the realm authorization.
// *Action: Review the definition for accuracy and retry the operation.
47264, 00000, "error updating realm authorization to %s for realm %s, %s"
// *Cause: An unexpected error occurred updating the realm authorization.
// *Action: Review the definition for accuracy and retry the operation.
47265, 00000, "The %s scope realm authorization is not allowed in realm %s."
// *Cause: The realm authorization scope was greater than the realm scope.
// *Action: Modify the realm authorization scope or add the
// realm authorization to a realm with proper scope.
47280, 00000, "Realm Object %s,%s.%s already defined in Realm %s"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47281, 00000, "Realm Object %s,%s.%s not found in Realm %s"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47282, 00000, "error adding Realm Object %s,%s.%s to Realm %s, %s"
// *Cause: An unexpected error occurred creating the realm object
// *Action: Please review the definition for accuracy and retry the operation
47283, 00000, "error deleting Realm Object %s,%s.%s from Realm %s, %s"
// *Cause: An unexpected error occurred deleting the realm object
// *Action: Please review the definition for accuracy and retry the operation
47284, 00000, "error adding Realm Object %s.%s. %s is not a valid object type"
// *Cause: The specified object type is not valid.
// *Action: Enter a valid object type for the specified object name, or enter
// "%" and all objects with the specified name and the specified
// owner will be added to the realm.
47285, 00000, "Object is not a common object."
// *Cause: The object was neither a metadata link nor an object link object.
// *Action: Enter a metadata link object or an object link object or enter
// "%" and all objects with the specified
// owner will be added to the realm.
47290, 00000, "error creating VPD policy for Realm %s, %s"
// *Cause: An unexpected error occurred creating the VPD policy
// *Action: Please review the definition for accuracy and retry the operation
47300, 00000, "Role already %s defined"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47301, 00000, "Role %s not found"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47302, 00000, "error creating Role %s, %s"
// *Cause: An unexpected error occurred creating the role
// *Action: Please review the definition for accuracy and retry the operation
47303, 00000, "error deleting Role %s, %s"
// *Cause: An unexpected error occurred deleting the role
// *Action: Please review the definition for accuracy and retry the operation
47304, 00000, "error updating Role %s, %s"
// *Cause: An unexpected error occurred updating the role
// *Action: Please review the definition for accuracy and retry the operation
47305, 00000, "Rule Set violation on %s (%s)"
// *Cause: An operation that was attempted failed due to a rule set violation
// *Action: Ensure you have sufficient privileges for this operation retry
// the operation
47306, 00000, "%s: %s"
// *Document: NO
// *Cause:
// *Action:
47320, 00000, "Rule %s already defined"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47321, 00000, "Rule %s not found"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47322, 00000, "error creating Rule %s, %s"
// *Cause: An unexpected error occurred creating the rule
// *Action: Please review the definition for accuracy and retry the operation
47323, 00000, "error deleting Rule %s, %s"
// *Cause: An unexpected error occurred deleting the rule
// *Action: Please review the definition for accuracy and retry the operation
47324, 00000, "error updating Rule %s, %s"
// *Cause: An unexpected error occurred updating the rule
// *Action: Please review the definition for accuracy and retry the operation
47325, 00000, "Rule %s is used by one or more rule sets."
// *Cause: The specified rule was used by existing rule set(s).
// *Action: Remove the dependent rule sets and retry the operation.
47326, 00000, "The common rule expression contains local object(s)."
// *Cause: Local object(s) were used in the common rule expression.
// *Action: Use common object(s) when creating or updating a common rule expression.
47327, 00000, "The scope of the Rule and the Rule Set are different."
// *Cause: The scope of the Rule and the Rule Set were different.
// *Action: Use Rule and Rule Set of the same scope.
47328, 00000, "cannot rename default rule %s"
// *Cause: An attempt was made to rename a default rule. Default rules cannot be renamed.
// *Action: No action required.
47340, 00000, "Rule Set %s already defined"
// *Cause: The object with this name exists already
// *Action: Choose a unique object name and retry the operation
47341, 00000, "Rule Set %s not found"
// *Cause: The object being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47342, 00000, "error creating Rule Set %s, %s"
// *Cause: An unexpected error occurred creating the rule set
// *Action: Please review the definition for accuracy and retry the operation
47343, 00000, "error deleting Rule Set %s, %s"
// *Cause: An unexpected error occurred deleting the rule set
// *Action: Please review the definition for accuracy and retry the operation
47344, 00000, "error updating Rule Set %s, %s"
// *Cause: An unexpected error occurred updating the rule set
// *Action: Please review the definition for accuracy and retry the operation
47345, 00000, "Rule set %s is used by one or more realm authorizations."
// *Cause: The specified rule set was used by existing realm authorization(s).
// *Action: Remove the dependent realm authorizations and retry the operation.
47346, 00000, "Rule set %s is used by one or more command rules."
// *Cause: The specified rule set was used by existing command rule(s).
// *Action: Remove the dependent command rules and retry the operation.
47347, 00000, "Rule set %s is used by one or more secure application roles."
// *Cause: The specified rule set was used by existing secure application role(s).
// *Action: Remove the dependent secure application roles and retry the operation.
47348, 00000, "Rule set %s is used by one or more factors."
// *Cause: The specified rule set was used by existing factor(s).
// *Action: Remove the dependent factors and retry the operation.
47349, 00000, "error occurred when executing the rule set handler"
// *Cause: Either there was a syntax error on the rule set handler or DVSYS did not have sufficient privilege to execute the rule set handler.
// *Action: Fix the syntax error on the rule set handler or grant execute privilege on the rule set handler to DVSYS.
47350, 00000, "cannot rename default rule set %s"
// *Cause: An attempt was made to rename a default rule set. Default rule sets cannot be renamed.
// *Action: No action required.
47360, 00000, "rule %s already added to rule set %s"
// *Cause: The object with this name existed already.
// *Action: Choose a unique object name and retry the operation.
47361, 00000, "rule %s not associated to rule set %s"
// *Cause: The rule specified was not associated to the rule set.
// *Action: Review the definition for accuracy and retry the operation.
47362, 00000, "error adding rule %s to rule set %s, %s"
// *Cause: An unexpected error occurred while adding the rule to the rule set.
// *Action: Review the definition for accuracy and retry the operation.
47363, 00000, "error deleting rule %s from rule set %s, %s"
// *Cause: An unexpected error occurred while deleting the rule from the rule set.
// *Action: Review the definition for accuracy and retry the operation.
47381, 00000, "Oracle Label Security (OLS) Policy %s not found"
// *Cause: The object being requested did not exist.
// *Action: Choose an object name that exists and retry the operation.
47382, 00000, "Oracle Label Security (OLS) Policy Label %s not found for policy %s"
// *Cause: The object being requested did not exist.
// *Action: Choose an object name that exists and retry the operation.
47383, 00000, "error capturing the session state information"
// *Cause: An internal error occurred capture the session state
// *Action: Please retry the operation if possible
47388, 00000, "Database Vault disable-factor-loading event"
// *Document: NO
// *Cause:
// *Action:
47389, 00000, "Database Vault static-ruleset-evaluation event"
// *Document: NO
// *Cause:
// *Action:
47390, 00000, "failed to audit event, %s"
// *Cause: An internal error auditing the operation
// *Action: Please retry the operation if possible
47391, 00000, "attempt to set Factor %s violates Rule Set %s"
// *Cause: An attempt to set the factor violated the associated rule set
// *Action: Please check to ensure you have the ability to set the factor
47392, 00000, "Factor %s cannot be set"
// *Cause: The attempt to set the factor is not allowed
// *Action: This factor cannot be set so there is no corrective action
47393, 00000, "Factor %s value not allowed"
// *Cause: The value being assigned to the factor is not allowed
// *Action: This factor cannot be set to this value so there is no corrective
// action
47394, 00000, "Factor assignment rule set not defined"
// *Cause: The rule set being associated to the factor does not exist
// *Action: Please review the definition for accuracy and retry the operation
47395, 00000, "error returned by Factor %s evaluation expression %s"
// *Cause: The factor retrieval method resulted in an error
// *Action: Please review the retrieval method definition for accuracy and
// correct it as required
47396, 00000, "error returned by Factor %s validation expression %s"
// *Cause: The factor retrieval method resulted in an invalid value based on
// its validation method
// *Action: Please review the factor definition and correct it as required
47397, 00000, "incorrect identified by value for Factor %s"
// *Cause: The factor identified by value is incorrect
// *Action: Please review the factor definition and correct it as required
47398, 00000, "multiple identities defined for Factor %s"
// *Cause: The factor has duplicate identities defined
// *Action: Please review the factor definition and correct it as required
47399, 00000, "incorrect labeled by value for Factor %s"
// *Cause: The factor labeled by value is incorrect
// *Action: Please review the factor definition and correct it as required
47400, 00000, "Command Rule violation for %s on %s"
// *Cause: An operation that was attempted failed due to a command rule
// violation
// *Action: Ensure you have sufficient privileges for this operation retry
// the operation
47401, 00000, "Realm violation for %s on %s.%s"
// *Cause: An operation that was attempted failed due to a realm protection
// *Action: Ensure you have sufficient privileges for this operation retry
// the operation
47402, 00000, "incorrect evaluation options value for Factor %s"
// *Cause: The factor evaluations options value is incorrect
// *Action: Please review the factor definition and correct it as required
47403, 00000, "NULL returned by Factor %s evaluation expression %s"
// *Cause: The factor evaluated to a NULL value
// *Action: Please review the factor definition and correct it as required
47404, 00000, "NULL trust level for Factor %s"
// *Cause: The factor has a NULL trust level
// *Action: Please review the factor definition and correct it as required
47405, 00000, "negative trust level for Factor %s"
// *Cause: The factor has a negative trust level
// *Action: Please review the factor definition and correct it as required
47406, 00000, "ALWAYS AUDIT option set for Factor %s"
// *Cause: The factor audit option is set to always audit
// *Action: No action required
47407, 00000, "ALWAYS AUDIT option set for Rule Set %s"
// *Cause: The rule set audit option is set to always audit
// *Action: No action required
47408, 00000, "Realm violation for the EXECUTE command"
// *Cause: A realm violation has occurred for a realm-protected stored
// procedure.
// *Action: In order to invoke the realm-protected procedure, you must have
// GRANT privileges to execute the procedure, or you must be
// authorized to operate in the procedure's realm.
47409, 00000, "Command Rule violation for the EXECUTE command"
// *Cause: A command rule violation occurred when trying to perform
// the EXECUTE command for a stored procedure protected
// by a command rule.
// *Action: Ask the Database Vault administrator to perform the operation or
// remove the command rule for the protected stored procedure.
47410, 00000, "Realm violation for %s on %s"
// *Cause: An operation that was attempted failed with insufficient
// privileges due to an attempt to violate a Database Vault Realm
// security policy which is currently enabled and enforced.
// *Action: Ensure you have sufficient privileges for this operation and
// retry the operation.
47411, 00000, "Cannot use %s due to Oracle Database Vault policy."
// *Cause: An operation that was attempted failed because Database Vault policy
// currently prevents the related feature from being used.
// *Action: Ask the Database Vault administrator to allow the feature to be
// used.
47412, 00000, "The DVSYS and DVF users are not allowed to switch containers."
// *Cause: An attempt was made to switch containers while connecting as DVSYS
// or DVF, which is not allowed.
// *Action: Connect as a different user and try again.
47413, 00000, "Cannot connect due to Oracle Database Vault policy."
// *Cause: An attempt to connect to DVSYS or DVF accounts failed because
// the Database Vault administrator had disabled the account.
// *Action: Ask the Database Vault administrator to enable the account.
47420, 00000, "Database Vault policy %s already defined"
// *Cause: The policy with this name already existed.
// *Action: Choose a unique policy name and retry the operation.
47421, 00000, "Database Vault policy %s not found"
// *Cause: The policy being requested did not exist.
// *Action: Choose a policy name that exists and retry the operation.
47422, 00000, "The object already belongs to a Database Vault policy."
// *Cause: An attempt was made to add a realm or command rule to more than
// one Database Vault policy.
// *Action: Make sure the realm or command rule does not belong to any
// Database Vault policy and retry the operation.
47423, 00000, "The object does not belong to Database Vault policy %s."
// *Cause: An attempt was made to delete a realm or command rule from a
// Database Vault policy that did not contain it.
// *Action: Choose the Database Vault policy that contains the realm or
// command rule and retry the operation.
47424, 00000, "The user %s already owns Database Vault policy %s."
// *Cause: An attempt was made to add a user as policy owner to a Database
// Vault policy that the user already owned.
// *Action: Choose a user who does not own the policy and retry the operation.
47425, 00000, "The user %s does not own Database Vault policy %s."
// *Cause: An attempt was made to delete a user as policy owner from a Database
// Vault policy that the user did not own.
// *Action: Choose a user who owns the policy and retry the operation.
47426, 00000, "The object or its parent object belongs to a Database Vault policy."
// *Cause: An attempt was made to modify an object that either belongs to a
// Database Vault policy or has a parent object that belongs to a
// Database Vault policy.
// *Action: Choose a different object or change the related policy state to the
// PARTIAL mode.
47427, 00000, "The %s scope realm %s cannot be added to policy %s."
// *Cause: The realm scope did not match the policy scope.
// *Action: Add the realm to a policy with the same scope.
47428, 00000, "The %s scope command rule cannot be added to policy %s."
// *Cause: The command rule scope did not match the policy scope.
// *Action: Add the command rule to a policy with the same scope.
47429, 00000, "The common scope command rule cannot be created on local objects."
// *Cause: An attempt was made to create a common scope command rule on a local object.
// *Action: Make sure the object is of common scope before creating a common scope
// command rule protecting it.
47430, 00000, "Nested tables cannot be added to Oracle Database Vault realms and command rules."
// *Cause: An attempt was made to add a nested table to a realm or command rule.
// *Action: Protect the base table of the nested table in order to automatically protect
// the nested table.
47431, 00000, "cannot rename default policy %s"
// *Cause: An attempt was made to rename a default policy. Default policy cannot be renamed.
// *Action: No action required.
47500, 00000, "Database Vault cannot be configured."
// *Cause: The Database Vault configuration failed because some Database Vault
// objects were missing.
// *Action: Run the dvremov.sql script to remove Database Vault and then
// reinstall Database Vault.
47501, 00000, "Database Vault has already been configured."
// *Cause: An attempt was made to run this procedure more than once.
// This procedure can be run successfully only once.
// *Action: If you are attempting to grant the DV_OWNER or DV_ACCTMGR roles,
// do so manually.
47502, 00000, "Database Vault is not yet configured."
// *Cause: The Database Vault configuration procedure dvsys.configure_dv()
// had not been run.
// *Action: Run dvsys.configure_dv() before attempting to
// enable or disable Database Vault enforcement.
47503, 00000, "Database Vault is not enabled in CDB$ROOT or application root."
// *Cause: Database Vault was not enabled in CDB$ROOT or application root for this operation.
// *Action: Enable Database Vault in CDB$ROOT or application root and retry the operation.
47504, 00000, "Common audit policies for component Oracle Database Vault not supported."
// *Cause: Audit policies for Oracle Database Vault realms, factors and rule sets
// could not be common audit policies.
// *Action: If creating audit policies for Oracle Database Vault objects in CDB$ROOT,
// include the clause 'container=current'.
47505, 00000, "Oracle Database Vault strict mode cannot be enabled in PDB."
// *Cause: "An attempt was made to enable Oracle Database Vault strict mode in a pluggable database (PDB).
// Strict mode can only be enabled in CDB$ROOT or application root.
// *Action: Enable Oracle Database Vault strict mode in CDB$ROOT or application root.
47800, 00000, "Oracle Data Pump authorization for Oracle Database Vault to %s to execute action %s already exists."
// *Cause: Oracle Data Pump authorization for Oracle Database Vault to execute
// the specified action was already granted to the specified grantee.
// *Action: Choose a different grantee or action and retry the operation.
47801, 00000, "Oracle Data Pump authorization for Oracle Database Vault to %s on schema %s to execute action %s already exists."
// *Cause: Oracle Data Pump authorization for Oracle Database Vault on the
// specified schema to execute the specified action was already granted to the specified grantee.
// *Action: Choose a different grantee, schema or action and retry the operation.
47802, 00000, "Oracle Data Pump authorization for Oracle Database Vault to %s to execute action %s is not found."
// *Cause: Oracle Data Pump authorization for Oracle Database Vault to execute
// the specified action was not granted to the specified grantee.
// *Action: Choose a different grantee or action and retry the operation.
47803, 00000, "Oracle Data Pump authorization for Oracle Database Vault to %s on schema %s to execute action %s is not found."
// *Cause: Oracle Data Pump authorization for Oracle Database Vault on the
// specified schema to execute the specified action was not granted to the specified grantee.
// *Action: Choose a different grantee, schema or action and retry the operation.
47901, 00000, "OLS policy not specified"
// *Cause: An OLS policy name is required for this operation
// *Action: Specify a policy name and retry the operation
47902, 00000, "OLS policy label not specified"
// *Cause: An OLS policy label is required for this operation
// *Action: Specify a policy label and retry the operation
47903, 00000, "OLS policy label %s not found for policy %s"
// *Cause: The policy label being requested does not exist
// *Action: Choose an object name that exists and retry the operation
47904, 00000, "OLS session label does not exist"
// *Cause: The policy label specified does not exist
// *Action: Choose a valid policy label and retry the operation
47905, 00000, "OLS policy label %s is not allowed for policy %s"
// *Cause: The policy label specified is not valid for this policy
// *Action: Choose a valid policy label for this policy and retry the operation
47906, 00000, "OLS policy label not specified for identity %s.%s under policy %s"
// *Cause: The policy label is required for this operation
// *Action: Choose a valid policy label for this policy and retry the operation
47907, 00000, "Database Vault associated OLS policy %s not fully configured"
// *Cause: The Oracle Label Security (OLS) policy was associated with Database Vault. But either the policy was not configured with a factor or the current factor identity was not assigned a label.
// *Action: Based on the cause, either configure a factor with the OLS policy using DVSYS.DBMS_MACADM.ADD_POLICY_FACTOR procedure and assign labels to factor identities using DVSYS.DBMS_MACADM.CREATE_POLICY_LABEL procedure or remove Database Vault association using DVSYS.DBMS_MACADM.DELETE_MAC_POLICY_CASCADE procedure.
47910, 00000, "failure to add language %s"
// *Cause: An error occurred while adding a language to Oracle Database Vault.
// *Action: Review the trace file and identify the cause.
47920, 00000, "Authorization failed for user %s to perform this operation"
// *Cause: The operation attempted is not allowed for this user
// *Action: Please ensure you have privileges to perform this operation
47921, 00000, "error adding host %s to domain %s, %s"
// *Cause: An error occurred adding the host specified to the domain specified
// *Action: Please review the host and domain definition and correct it as
// required
47922, 00000, "error removing host %s to domain %s, %s"
// *Cause: An error occurred removing the host specified to the domain
// specified
// *Action: Please review the host and domain definition and correct it as
// required
47930, 00000, "Privilege capture %s already exists."
// *Cause: A privilege capture with the given name was already in existence.
// *Action: Choose another capture name or drop the existing privilege capture.
47931, 00000, "Privilege capture %s does not exist."
// *Cause: The given privilege capture did not exist.
// *Action: Choose another privilege capture.
47932, 00000, "Privilege capture %s is still enabled."
// *Cause: The given privilege capture was still enabled.
// *Action: Choose another capture or disable the given privilege capture.
47933, 00000, "Privilege capture %s is already enabled."
// *Cause: The given privilege capture was already enabled.
// *Action: Choose another privilege capture.
47934, 00000, "Two privilege captures are already enabled."
// *Cause: The maximum number of two privilege captures were enabled."
// *Action: Disable one of the enabled privilege captures.
47935, 00000, "Another privilege capture is enabled."
// *Cause: Another capture of the same type or another nondatabase-wide
// capture was enabled.
// *Action: Disable the enabled privilege capture.
47936, 00000, "Privilege capture %s is already disabled."
// *Cause: The given privilege capture was already disabled.
// *Action: Choose another capture.
47937, 00000, "Input %s does not match the given privilege capture type."
// *Cause: The given input did not match the given privilege capture type.
// *Action: Change the input or the privilege capture type.
47938, 00000, "GENERATE_RESULT is already running for privilege capture %s."
// *Cause: DBMS_PRIVILEGE_CAPTURE.GENERATE_RESULT was already running for the
// given privilege capture.
// *Action: Wait and retry later or choose another privilege capture.
47939, 00000, "Capture context namespace or attribute does not exist or is invalid."
// *Cause: Context namespace or attribute used in the capture condition did not
// exist or was invalid.
// *Action: Create the namespace or set the attribute or recreate a privilege
// capture with a valid namespace and attribute.
47940, 00000, "cannot create a capture condition for a SYS user"
// *Cause: An attempt was made to create a capture with the condition set as a
// SYS user which is not allowed.
// *Action: You can create capture conditions only for non-SYS users.
47941, 00000, "Privilege capture %s has not been enabled with run name %s."
// *Cause: The given privilege capture has not been run with run name %s.
// *Action: Enable the given privilege capture with the given run name.
47942, 00000, "Privilege capture %s had been enabled with run name %s."
// *Cause: The given privilege capture had been run with the given run name.
// *Action: Enable the given privilege capture with a new run name.
47943, 00000, "Privilege capture %s is enabled with run name %s."
// *Cause: The given privilege capture is running with the given run name.
// *Action: Disable the given privilege capture.
47944, 00000, "Privilege capture %s has not been enabled."
// *Cause: The given privilege capture has not been enabled.
// *Action: Enable the given privilege capture.
47945, 00000, "duplicate roles %s in capture condition"
// *Cause: An attempt was made to specify duplicate roles in a capture
// condition.
// *Action: Specify only unique roles and retry the operation.
47950, 00000, "no value defined for required parameter %s"
// *Cause: The operation requires a value for this parameter
// *Action: Please specify the missing parameter and retry the operation
47951, 00000, "invalid input value or length for parameter '%s'"
// *Cause: The value specified for this parameter is invalid or too large
// *Action: Please specify the a valid parameter and retry the operation
47952, 00000, "Oracle Data Pump authorization for Oracle Database Vault to %s already exists"
// *Cause: Oracle Data Pump authorization for Oracle Database Vault was
// already granted to the given grantee.
// *Action: Choose a different grantee and retry the operation.
47953, 00000, "Oracle Data Pump authorization for Oracle Database Vault to %s on schema %s already exists"
// *Cause: Oracle Data Pump authorization for Oracle Database Vault on the
// given schema was already granted to the given grantee.
// *Action: Choose a different grantee or schema and retry the operation.
47954, 00000, "Oracle Data Pump authorization for Oracle Database Vault to %s on object %s.%s already exists"
// *Cause: Oracle Data Pump authorization for Oracle Database Vault on the
// given object was already granted to the given grantee.
// *Action: Choose a different grantee or a different object and retry the
// operation.
47955, 00000, "Oracle Data Pump authorization for Oracle Database Vault to %s is not found"
// *Cause: Oracle Data Pump authorization for Oracle Database Vault was not
// granted to the given user.
// *Action: Choose a user who has Oracle Data Pump authorization for
// Oracle Database Vault and retry the operation.
47956, 00000, "Oracle Data Pump authorization for Oracle Database Vault to %s on schema %s is not found"
// *Cause: Oracle Data Pump authorization for Oracle Database Vault was not
// granted to the given user on the given schema.
// *Action: Choose a different user or schema and retry the operation.
47957, 00000, "Oracle Data Pump authorization for Oracle Database Vault to %s on object %s.%s is not found"
// *Cause: Oracle Data Pump authorization for Oracle Database Vault was not
// granted to the given user on the given object.
// *Action: Choose a different user or object and retry the operation.
47958, 00000, "Running EXP with direct path option is disallowed when Oracle Database Vault is enabled."
// *Cause: While Oracle Database Vault was enabled, an attempt was made to run
// EXP with the 'direct=y' option.
// *Action: Change the option to 'direct=n' or disable Oracle Database Vault and retry the operation.
47959, 00000, "Oracle transportable tablespace authorization for Oracle Database Vault to %s on tablespace %s already exists."
// *Cause: Oracle transportable tablespace authorization for Oracle Database
// Vault on the given tablespace was already granted to the given
// grantee.
// *Action: Choose a different grantee or tablespace and retry the operation.
47960, 00000, "Oracle transportable tablespace authorization for Oracle Database Vault to %s on tablespace %s is not found."
// *Cause: Oracle transportable tablespace authorization for Oracle Database
// Vault was not granted to the given user on the given tablespace.
// *Action: Choose a different user or tablespace and retry the operation.
47961, 00000, "Oracle Scheduler Job authorization for Oracle Database Vault to %s already exists"
// *Cause: Oracle Scheduler Job authorization for Oracle Database Vault was
// already granted to the given grantee.
// *Action: Choose a different grantee and retry the operation.
47962, 00000, "Oracle Scheduler Job authorization for Oracle Database Vault to %s on schema %s already exists"
// *Cause: Oracle Scheduler Job authorization for Oracle Database Vault
// on the given schema was already granted to the given grantee.
// *Action: Choose a different grantee or schema and retry the operation.
47963, 00000, "Oracle Scheduler Job authorization for Oracle Database Vault to %s is not found"
// *Cause: Oracle Scheduler Job authorization for Oracle Database Vault was
// not granted to the given user.
// *Action: Choose a user who has Oracle Scheduler Job authorization for
// Oracle Database Vault and retry the operation.
47964, 00000, "Oracle Scheduler job authorization for Oracle Database Vault to %s on schema %s is not found"
// *Cause: Oracle Scheduler job authorization for Oracle Database Vault was
// not granted to the given user on the given schema.
// *Action: Choose a different user or schema and retry the operation.
47965, 00000, "DEBUG_CONNECT authorization for Oracle Database Vault to %0!s on schema %1!s already exists."
// *Cause: DEBUG_CONNECT authorization for Oracle Database Vault
// on the given schema was already granted to the given grantee.
// *Action: Choose a different grantee or schema and retry the operation.
47966, 00000, "DEBUG_CONNECT authorization for Oracle Database Vault to %0!s on schema %1!s is not found."
// *Cause: DEBUG_CONNECT authorization for Oracle Database Vault was
// not granted to the given user on the given schema.
// *Action: Choose a different user or schema and retry the operation.
47967, 00000, "DBCAPTURE authorization for Oracle Database Vault to %s already exists."
// *Cause: DBCAPTURE authorization for Oracle Database Vault was
// already granted to the specified grantee.
// *Action: Choose a different grantee and retry the operation.
47968, 00000, "DBCAPTURE authorization for Oracle Database Vault to %s is not found."
// *Cause: DBCAPTURE authorization for Oracle Database Vault was not
// granted to the specified user.
// *Action: Choose a user who has DBCAPTURE authorization for
// Oracle Database Vault and retry the operation.
47969, 00000, "DBREPLAY authorization for Oracle Database Vault to %s already exists."
// *Cause: DBREPLAY authorization for Oracle Database Vault was
// already granted to the specified grantee.
// *Action: Choose a different grantee and retry the operation.
47970, 00000, "DBREPLAY authorization for Oracle Database Vault to %s is not found."
// *Cause: DBREPLAY authorization for Oracle Database Vault was not
// granted to the specified user.
// *Action: Choose a user who has DBREPLAY authorization for
// Oracle Database Vault and retry the operation.
47971, 00000, "Oracle proxy authorization for Oracle Database Vault to %s on schema %s already exists"
// *Cause: Oracle proxy authorization for Oracle Database Vault
// on the given schema was already granted to the given grantee.
// *Action: Choose a different grantee or schema and retry the operation.
47972, 00000, "Oracle proxy authorization for Oracle Database Vault to %s on schema %s is not found."
// *Cause: Oracle proxy authorization for Oracle Database Vault was
// not granted to the given user on the given schema.
// *Action: Choose a different user or schema and retry the operation.
47973, 00000, "Oracle DDL authorization for Oracle Database Vault to %s on schema %s already exists."
// *Cause: Oracle DDL authorization for Oracle Database Vault
// on the given schema was already granted to the given grantee.
// *Action: Choose a different grantee or schema and retry the operation.
47974, 00000, "Oracle DDL authorization for Oracle Database Vault to %s on schema %s is not found."
// *Cause: Oracle DDL authorization for Oracle Database Vault was
// not granted to the given user on the given schema.
// *Action: Choose a different user or schema and retry the operation.
47975, 00000, "PREPROCESSOR authorization for Oracle Database Vault to %s already exists"
// *Cause: PREPROCESSOR authorization for Oracle Database Vault was
// already granted to the specified grantee.
// *Action: Choose a different grantee and retry the operation.
47976, 00000, "PREPROCESSOR authorization for Oracle Database Vault to %s is not found"
// *Cause: PREPROCESSOR authorization for Oracle Database Vault was not
// granted to the specified user.
// *Action: Choose a user who has PREPROCESSOR authorization for
// Oracle Database Vault and retry the operation.
47977, 00000, "Maintenance authorization%s for Oracle Database Vault to %s%s already exists."
// *Cause: Maintenance authorization for Oracle Database Vault was
// already granted to the specified grantee.
// *Action: Choose different parameters and retry the operation.
47978, 00000, "Maintenance authorization%s for Oracle Database Vault to %s%s on schema %s already exists."
// *Cause: Maintenance authorization for Oracle Database Vault on the
// specified schema was already granted to the specified grantee.
// *Action: Choose different parameters and retry the operation.
47979, 00000, "Maintenance authorization%s for Oracle Database Vault to %s on object %s.%s already exists."
// *Cause: Maintenance authorization for Oracle Database Vault on the specified
// schema was already granted to the specified grantee.
// *Action: Choose a different grantee or schema and retry the operation.
47980, 00000, "Maintenance authorization%s for Oracle Database Vault to %s%s is not found."
// *Cause: Maintenance authorization for Oracle Database Vault was not
// granted to the specified user.
// *Action: Choose different parameters and retry the operation.
47981, 00000, "Maintenance authorization%s for Oracle Database Vault to %s%s on schema %s is not found."
// *Cause: Maintenance authorization for Oracle Database Vault was not
// granted to the specified user on the specified schema.
// *Action: Choose a different user or schema and retry the operation.
47982, 00000, "Maintenance authorization%s for Oracle Database Vault to %s on object %s.%s is not found."
// *Cause: Maintenance authorization for Oracle Database Vault was not
// granted to the specified user on the specified object.
// *Action: Choose a different user or object and retry the operation.
47983, 00000, "Diagnostic authorization for Oracle Database Vault to %s already exists."
// *Cause: Diagnostic authorization for Oracle Database Vault was
// already granted to the specified grantee.
// *Action: Choose a different grantee and retry the operation.
47984, 00000, "Diagnostic authorization for Oracle Database Vault to %s is not found."
// *Cause: Diagnostic authorization for Oracle Database Vault was not
// granted to the specified user.
// *Action: Choose a user who has diagnostic authorization for
// Oracle Database Vault and retry the operation.
47985, 00000, "password same as or similar to user"
// *Cause: The password specified similar to the user account name and
// therefore insecure
// *Action: Please specify the more complex password and retry the operation
47986, 00000, "password length must be 8 characters or more"
// *Cause: The password specified is too short and therefore insecure
// *Action: Please specify a password with more characters and retry the
// operation
47987, 00000, "password is too simple"
// *Cause: The password specified can be guessed based on dictionary terms
// and therefore insecure
// *Action: Please specify a password that is not based on dictionary terms
// and retry the operation
47988, 00000, "password should contain at least one numeric and one alphabetic character"
// *Cause: The password does not contain at least one numeric and one
// alphabetic character
// *Action: Please specify a password with at least one numeric and one
// alphabetic character and retry the operation
47989, 00000, "password should differ by at least 3 characters"
// *Cause: The password specified does not differ from the previous one by
// more than 3 characters
// *Action: Please specify a password that differs from the previous one by
// more than 3 characters and retry the operation
47990, 00000, "Function %s has already been added to Oracle Database Vault index functions list."
// *Cause: The function specified had already been added to Oracle Database Vault
// index functions list.
// *Action: Choose a different function and retry the operation.
47991, 00000, "Function %s is not found in Oracle Database Vault index functions list."
// *Cause: The function specified was not found in Oracle Database Vault index functions list.
// *Action: Choose a different function and retry the operation.
47992, 00000, "Function %s is not an Oracle built-in operator."
// *Cause: The function specified was not provided as a built-in operator by Oracle.
// *Action: Choose a different function and retry the operation.
47993, 00000, "cannot run dvremov.sql on the multitenant container database (CDB)."
// *Cause: The Database Vault removal script was not supported on a multitenant
// container database (CDB).
// *Action: None.
47994, 00000, "Database Vault removal script must be run as SYS"
// *Cause: The Database Vault removal script was not run as SYS.
// *Action: Run the Database Vault removal script as SYS.
47995, 00000, "Database Vault must be linked off and disabled before removal"
// *Cause: Database Vault was not linked off and disabled.
// *Action: Link Database Vault off and execute DBMS_MACADM.DISABLE_DV_CHECK as DV_OWNER.
47996, 00000, "The RECYCLEBIN is turned on"
// *Cause: The RECYCLEBIN was turned on.
// *Action: Turn off the RECYCLEBIN and then execute Database Vault Removal script.
47997, 00000, "Database Vault protected schema does not exist"
// *Cause: The Database Vault DVSYS protected schema did not exist.
// *Action: Contact Oracle Support Services for instructions.
47998, 00000, "Database Vault tracing event"
// *Document: NO
// *Cause:
// *Action:
47999, 00000, "internal Database Vault error: %s\n Error: %s"
// *Cause: An internal Database Vault framework error occurred.
// *Action: Contact Oracle Customer Support.
/
/
/ E R R O R S -- NOTE: diaerror.txt is for checkin comments for this file
/
/////////////////////////////////////////////////////////////////////////////
/ 48000 - 48099 are reserved for diagnosability framework errors
/////////////////////////////////////////////////////////////////////////////
/
48001, 00000, "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"
// *Document: YES
// *Cause: This is the generic internal error number for program
// exceptions. This indicated that a process encountered an
// exceptional condition.
// *Action: Report as a bug - the first argument is the internal error number.
// *Comment: The ORA facility mapping for this error is ORA-00600.
/
48002, 00000, "thread terminated by fatal error"
// *Document: YES
// *Cause: The thread was in an unrecoverable state.
// *Action: Examine the thread trace file for more information.
// *Comment: The ORA facility mapping for this error is ORA-00603.
/
48003, 00000, "out of process memory when trying to allocate %s bytes (%s,%s)"
// *Document: YES
// *Cause: Operating system process private memory was exhausted.
// *Action:
// *Comment: The ORA facility mapping for this error is ORA-04030.
/
48004, 00000, "unable to allocate %s bytes of shared memory (\"%s\",\"%s\",\"%s\",\"%s\")"
// *Document: YES
// *Cause: More shared memory is needed than was allocated in the shared
// pool.
// *Action: Reduce your use of shared memory or increase the amount of
// available shared memory.
// *Comment: The ORA facility mapping for this error is ORA-04031.
/
48005, 00000, "illegal argument for function"
// *Document: NO
// *Cause: An illegal argument was passed to dbgc_alloc.
// *Action: Report as a bug.
// *Comment: Ideally we should have signaled an internal error, however
// the KGE facility is not initialized when dbgc_alloc is called
// thus we could not raise an error.
/
48006, 00000, "user requested cancel of current operation"
// *Document: YES
// *Cause:
// *Action:
// *Comment: The ORA facility mapping for this error is ORA-01013.
/
48007, 00000, "name is already used by an existing product type"
// *Document: YES
// *Cause: An attempt was made to define a product type with the same name
// as an already defined product type.
// *Action: Use the already existing product type with the specified name,
// or use a different name for the product type.
/
48008, 00000, "id is already used by an existing product type"
// *Document: YES
// *Cause: An attempt was made to define a product type with the same id
// as an already defined product type.
// *Action: Choose a different name for the product type.
/
/////////////////////////////////////////////////////////////////////////////
/ 48100 - 48179 are reserved for ADS portable layer
/////////////////////////////////////////////////////////////////////////////
48100, 00000, "error encountered when attempting to open a file"
// *Cause: There was an error encountered when attempting to open a file
// with the ADR file interface.
// *Action: Check that the specified directory name, file name, and open
// options are valid.
/
48101, 00000, "error encountered when attempting to read a file [%s] [%s] [%s]"
// *Cause: There was an error encountered when attempting to read a file
// with the ADR file interface.
// *Action: Check the specified arguments to the read interface.
/
48102, 00000, "encountered the end-of-file when reading the file"
// *Cause: The ADR file interface encountered the end-of-file when
// reading the file.
// *Action: Handle the end of file condition.
/
48103, 00000, "error encountered when attempting to write a file [%s] [%s] [%s]"
// *Cause: There was an error encountered when attempting to write a file
// with the ADR file interface.
// *Action: Check the specified arguments to the write interface.
/
48104, 00000, "read mismatch on blocks requested and returned, [%s], [%s]"
// *Cause: There was a mismatch between the number of blocks requested
// for reading and the number of blocks actually returned.
// *Action: Check the file to make sure there are no partial blocks.
/
48105, 00000, "write mismatch on blocks requested and returned, [%s], [%s]"
// *Cause: There was a mismatch between the number of blocks requested
// for writing and the number of blocks actually written.
// *Action: Check that there is enough space left on the device to
// write the requested number of blocks.
/
48106, 00000, "error initializing the ADR %s object"
// *Cause: There was an error encountered during the initialization of
// one of the ADR file objects.
// *Action: Check the validity of the specified directory name and
// file name.
/
48107, 00000, "invalid Bfile input, [%s]"
// *Cause: An invalid Bfile was passed into the routine to convert the
// bfile into a file handle.
// *Action: Verify the contents of the specified Bfile.
/
48108, 00000, "invalid value given for the diagnostic_dest init.ora parameter"
// *Cause: The value given for the diagnostic_dest directory is not a
// valid directory. Either the directory does not exist or
// the process does not have read/write privileges on the directory.
// *Action: Use a value for diagnostic_dest that is a valid directory
// with the proper read and write privileges.
/
48109, 00000, "invalid lock mode for file descriptor, [%s]"
// *Cause: The lock mode associated with the file descriptor was invalid
// in the context of the routine.
// *Action: Verify that a file is not trying to obtain multiple locks and
// that the file is holding a lock when attempting to release
// the lock.
/
48110, 00000, "error encountered while attempting to get a file lock [%s] [%s]"
// *Cause: There was an error encountered while trying to get
// a file lock.
// *Action: Check the state of the file and operating system.
/
48111, 00000, "error encountered while attempting to release a file lock [%s]"
// *Cause: There was an error encountered while trying to release
// a file lock.
// *Action: Check the state of the file and operating system.
/
48112, 00000, "invalid flags for open file, %s"
// *Cause: Invalid flags were passed in to the open file routine.
// *Action: Check to see if the flags are a valid combination.
/
48113, 00000, "unable to write to stream file because of out of space condition"
// *Cause: The system is unable to write the requested number of bytes
// to a stream file. This is due to an out of space condition.
// The additional information shows how many bytes were not written.
// *Action: Check that there is enough space left on the device to
// write the requested number of bytes.
/
48114, 00000, "error encountered when attempting to close a file"
// *Document: YES
// *Cause: There was an error encountered when attempting to close
// a file with the ADR file interface.
// *Action: Check the validity of the file descriptor.
/
48115, 00000, "error encountered while seeking a file position"
// *Cause: There was an error encountered while seeking a position
// in a file.
// *Action: Check that the requested file position falls within the
// file boundaries.
/
48116, 00000, "error encountered when attempting to create a directory [%s]"
// *Cause: There was an error encountered when attempting to
// create a directory.
// *Action: Check the directory name.
/
48117, 00000, "error encountered when attempting to remove a directory [%s]"
// *Cause: There was an error encountered when attempting to
// remove a directory.
// *Action: Check the directory name.
/
48118, 00000, "error encountered with list directory [%s]"
// *Cause: There was an error with listing the elements of a directory.
// *Action: Check the state of the operating system.
/
48119, 00000, "error encountered when attempting to remove a file [%s] [%s]"
// *Cause: There was an error encountered when attempting to remove
// a file with the ADR file interface.
// *Action: Check the directory name and file name.
/
48120, 00000, "error encountered when attempting to retrieve the file size [%s] [%s]"
// *Cause: There was an error encountered when attempting to retrieve
// the file size with the ADR file interface.
// *Action: Check the directory name and file name.
/
48121, 00000, "error with opening the ADR stream file [%s] [%s]"
// *Cause: An error was encountered when attempting to open an
// ADR stream file.
// *Action: Check the rest of the error stack for details of the
// actual error that was encountered.
/
48122, 00000, "error with opening the ADR block file [%s] [%s]"
// *Cause: An error was encountered when attempting to open an
// ADR block file.
// *Action: Check the rest of the error stack for details of the
// actual error that was encountered.
/
48123, 00000, "error encountered when attempting to flush a file"
// *Cause: There was an error encountered when attempting to flush
// a file with the ADR file interface.
// *Action: Check the state of the file.
/
48124, 00000, "device full encountered during write to a file"
// *Cause: The device full error was encountered during the write to a file.
// *Action: Check the amount of free space on the device.
/
48125, 00000, "illegal identifier length, argn:%s, len:%s, lim:%s"
// *Cause: An input identifier was passed in that has a length that is
// greater than the max length.
// *Action: Make sure the input identifier has a length that is less
// than the max length.
/
48126, 00000, "attempting to create a file that already exists"
// *Cause: The client attempted to create a file that already exists.
// *Action: Either remove the file or check if it is okay if the file
// already exists.
/
48127, 00000, "attempting to open a file that does not exist"
// *Cause: An attempt was made to open a file that does not exist.
// *Action: Either create the file or check why the file does not exist.
/
48128, 00000, "opening of a symbolic link is disallowed"
// *Cause: An error was encountered when attempting to open a file that is
// a symbolic link. Users are not allowed to open symbolic links.
// *Action: Check the specified file name.
/
48129, 00000, "invalid input for the full path specification"
// *Cause: Input was incorrectly specified for the full path specification,
// or the default extension may have been incorrectly specified.
// Or an empty string was passed in for the full path.
// *Action: Check that the full path string is non-NULL.
// If you want to specify a relative path from ADR Home for the
// full path specification, then use '<ADR_HOME>' instead of the
// actual path to ADR Home. For ADR Base, use '<ADR_BASE>'.
/
48130, 00000, "invalid lock parameters for get file lock [%s]"
// *Cause: Invalid lock parameters passed in for the get file lock routine.
// The user must pass in file as the lock type. Or, there is a lock
// mode mismatch. Exclusive locks are not allowed in read-only mode,
// and shared locks are not allowed in write-only mode.
// *Action: Check that correct lock type is specified and that the correct
// lock mode is requested for the file given its open flags.
/
48131, 00000, "error encountered when attempting to tell the file position"
// *Cause: An error was encountered when attempting to tell the file
// position using the ADR file interface.
// *Action: Check the directory and file name of the file along with the
// open state.
/
48132, 00000, "requested file lock is busy, [%s] [%s]"
// *Cause: The requested file lock is busy because another process is
// holding the file lock.
// *Action: Try to get the file lock again at a later time.
/
48133, 00000, "file descriptor has already been opened [%s] [%s]"
// *Cause: The specified file descriptor has already been opened.
// *Action: Do not open a file that has previously been opened, or check
// your code to make sure you are cleaning up a file descriptor
// that is being reused correctly.
/
48134, 00000, "invalid file descriptor state for operation, %s, %s, %s"
// *Cause: The state of the file descriptor was invalid for the requested
// operation. An example is that a file was opened for read,
// but a write operation to the file was requested.
// *Action: Check the state of the file descriptor and make sure it
// matches the operation.
/
48135, 00000, "uninitialized file descriptor"
// *Cause: The specified file descriptor is uninitialized.
// *Action: Make sure the file descriptor is initialized before passing
// it into the routine.
/
48136, 00000, "directory already exists [%s]"
// *Cause: Operation failed because the specified directory already exists.
// *Action: Remove the directory or ignore this error.
/
48137, 00000, "uninitialized file handle"
// *Cause: The specified file handle is uninitialized.
// *Action: Make sure the file handle is initialized before passing
// it into the routine.
/
48138, 00000, "invalid directory name input for client address"
// *Cause: An invalid directory name was specified as part of the
// address path specification.
// *Action: Check that the directory name is non-NULL and that the
// directory name length does not exceed the maximum length.
/
48139, 00000, "invalid input to ADR initialization routine"
// *Cause: There was an invalid input to the ADR initialization routine.
// *Action: Check the length of the ADR base, product ID, and instance
// ID input arguments.
/
48140, 00000, "the specified ADR Base directory does not exist [%s]"
// *Cause: The specified ADR Base Directory does not exist.
// *Action: Check that the specified ADR Base Directory is a valid path
// name and that the directory exists.
/
48141, 00000, "error creating directory during ADR initialization [%s]"
// *Cause: Error encountered when creating a directory during the
// initialization of the ADR subsystem.
// *Action: Check the input arguments to the ADR initialization routine
// and the state of the operating system.
/
48142, 00000, "invalid permissions input for change permissions"
// *Cause: Invalid permissions passed into change permissions routine.
// *Action: Check the value of the permissions input.
/
48143, 00000, "error changing permissions for a file"
// *Cause: Error encountered while changing the permissions for a file
// *Action: Check the specified directory and file and the state of
// the operating system.
/
48144, 00000, "error encountered while performing standard file I/O"
// *Cause: Error encountered while performing standard file I/O
// *Action: Check the validity of standard in, out, and error.
/
48145, 00000, "invalid seek location, [%s], [%s]"
// *Cause: Invalid seek location specified for routine.
// *Action: Check the validity of specified seek location.
/
48146, 00000, "missing read, write, or exec permission on directory during ADR initialization [%s] [%s]"
// *Cause: Error encountered when checking if the process has read, write,
// and exec privileges on directories needed by the ADR subsystem.
// This error occurs during the initialization of the ADR subsystem.
// *Action: Check the input arguments to the ADR initialization routine
// and the state of the operating system. Ensure that the user
// has the proper permissions on the ADR directories.
/
48147, 00000, "invalid home location specification for ADR, [%s], [%s], [%s]"
// *Cause: Invalid read or write home location specification for ADR.
// *Action: An invalid home was specified for the ADR Read or Write
// Home location.
/
48148, 00000, "error encountered when attempting to move a file"
// *Cause: There was an error encountered when attempting to move
// a file with the ADR file interface.
// *Action: Check the directory name and file name.
/
48149, 00000, "error encountered when attempting to copy a file"
// *Cause: There was an error encountered when attempting to copy
// a file with the ADR file interface.
// *Action: Check the directory name and file name.
/
48150, 00000, "error encountered with set current working directory"
// *Cause: There was an error with setting the current working directory.
// *Action: Check the path used, or the state of the operating system.
/
48151, 00000, "error getting operating system time for a file"
// *Cause: Error encountered while getting the operating system time for a
// file.
// *Action: Check the specified directory and file and the state of
// the operating system.
48152, 00000, "lock table is full"
// *Cause: Lock table is full - too many locks granted
// *Action: Try again later
/
48153, 00000, "error encountered when getting ADR base directory default"
// *Cause: There was an error encountered when attempting to get
// the ADR base directory default value.
// *Action: Check your environment to see if the $ORACLE_BASE and
// $ORACLE_HOME environment variables are set.
/
48154, 00000, "reached end of file for alert log"
// *Cause: The end of file was reached for reading the Alert Log. There
// are no more messages to read in the Alert Log.
// *Action: Do not read from the Alert Log
/
48155, 00000, "error encountered when read alert log [%s]"
// *Cause: There was an error encountered when attempting to read
// a message from the Alert Log.
// *Action: Check the error message and the contents of the alert message.
/
48156, 00000, "Alert log purge has occurred - retry operation"
// *Cause: The purge of the alert log has occurred.
// *Action: Retry the operation.
/
48157, 00000, "null input to ADR initialization"
// *Cause: There was an null input to the ADR initialization routine.
// *Action: Check the ADR base, product ID, and instance ID input arguments.
/
48158, 00000, "invalid input for ADR base directory"
// *Cause: An invalid input was passed in for the ADR base directory name.
// The ADR base directory name is either NULL or too long of a string.
// *Action: Check the ADR base directory input argument.
/
48159, 00000, "invalid input for ADR product type"
// *Cause: An invalid input was passed in for the ADR product type.
// The ADR product type is out of bounds.
// *Action: Check the ADR product type input argument.
/
48160, 00000, "invalid input for ADR product id"
// *Cause: An invalid input was passed in for the ADR product id.
// The ADR product id is either NULL or too long of a string.
// *Action: Check the ADR product id input argument.
/
48161, 00000, "invalid input for ADR instance id"
// *Cause: An invalid input was passed in for the ADR instance id.
// The ADR instance id is either NULL or too long of a string.
// *Action: Check the ADR instance id input argument.
/
48162, 00000, "string buffer too small to hold input, [%s], [%s], [%s]"
// *Cause: The string buffer is too small to copy an input string
// into.
// *Action: Check the size of the string buffer and the input string.
// Look in the argument for the location in the code where the
// error occurs.
/
48163, 00000, "error concatenating directory onto path, [%s], [%s], [%s]"
// *Cause: Error encountered while concatenating a directory onto
// a path name.
// *Action: Check the error returned by the OS and the size of the input
// and output buffers.
/
48164, 00000, "error concatenating file onto path, [%s], [%s], [%s]"
// *Cause: Error encountered while concatenating a directory onto
// a path name.
// *Action: Check the error returned by the OS and the size of the input
// and output buffers.
/
48165, 00000, "user missing read, write, or exec permission on specified ADR Base directory [%s]"
// *Cause: The specified ADR Base Directory does not have the correct
// permissions.
// *Action: Check the read, write, and exec permissions on the specified
// ADR Base Directory
/
48166, 00000, "error with opening ADR block file because file does not exist [%s] [%s]"
// *Cause: An error was encountered with opening an ADR block file
// because the file does not exist.
// *Action: Check the existence of the ADR Block File.
/
48167, 00000, "invalid argument for checking ADR initialization"
// *Cause: Invalid arguments were specified for the routine to check
// ADR initialization.
// *Action: Check the inputs to the ADR initialization routine.
/
48168, 00000, "the ADR sub-system is not initialized"
// *Cause: The ADR subsystem has not been initialized. The requested
// operation cannot be performed.
// *Action: Check the usage of the call to the ADR services. The ADR
// sub-system must be initialized for the call to work.
/
48169, 00000, "incorrect arguments to ADR deferred initialization"
// *Cause: There are incorrect arguments to the ADR deferred initialization.
// *Action: Check the input arguments. It could be possible that
// the product is not set up for deferred initialization.
/
48170, 00000, "unable to lock file - already in use"
// *Cause: the file is locked by another process, indicating that it is
// currently in use by another process
// *Action: determine which process legitimately owns this file.
/
48171, 00000, "unable to get share lock - file not readable"
// *Cause: share lock request was made on a file not open for read access.
// *Action: file must be open read-only or read-write to get a share lock.
/
48172, 00000, "unable to find a valid ADR base"
// *Cause: Unable to find a valid ADR base. We tried the ORACLE_BASE,
// ORACLE_HOME, home, and tmp directories, but none of the
// directories exist for read/write access.
// *Action: Check the validity of the ORACLE_BASE, ORACLE_HOME, home,
// and tmp directories.
/
48173, 00000, "error checking directory existence during ADR initialization [%s]"
// *Cause: Error encountered when checking directory existence during the
// initialization of the ADR subsystem. Either the diag or product
// type directory does not exist underneath the ADR base.
// *Action: The directory in the error message must exist in order for
// ADR initialization to succeed. Make sure the directories exist.
/
48174, 00000, "error encountered with get current working directory"
// *Cause: There was an error with getting the current working directory.
// *Action: Check the state of the operating system or the size of the
// path buffer.
/
48175, 00000, "the path name must not contain the string '..'."
// *Cause: The specified path name contains '..'.
// *Action: Correct the path name and retry the operation.
/
48176, 00000, "error translating a path name into its full path name"
// *Cause: An error was encountered when translating a path name into
// its full path name.
// *Action: Check the inputted path name to make sure it is a valid
// relative path.
/
48177, 00000, "file name with full path information [%s] not allowed"
// *Cause: Input was incorrectly specified for the file name.
// The inputted file name is greater than the maximum length, or
// the file name has path information. In this case, the file name
// should not have any path information. The path information should
// be specified in a separate argument.
// *Action: Check that the string for the file name is not too long
// and does not have path information.
/
48178, 00000, "error encountered while reading an ADR block file during ADR initialization [%s]"
// *Cause: An error was encountered while reading an ADR block file during
// the initialization of the ADR subsystem.
// *Action: Check the state of the file system.
/
48179, 00000, "OS file synchronization failure"
// *Cause: OS command to synchronize the changes to a file with the operating
// system failed.
// *Action: Check the state of the file system and the amount of free space
// left on your device.
/
/////////////////////////////////////////////////////////////////////////////
/ 48180 - 48199 are reserved for ADS OSD layer
/////////////////////////////////////////////////////////////////////////////
48180, 00000, "OS open system call failure"
// *Cause: OS open system call failed. The system failed to open or create
// a file in the requested mode.
// *Action: Check the OS error code
/
48181, 00000, "OS write system call failure"
// *Cause: OS write system call failed. The system failed to write to
// a file.
// *Action: Check the OS error code
/
48182, 00000, "OS read system call failure"
// *Cause: OS read system call failed. The system failed to read to
// a file.
// *Action: Check the OS error code
/
48183, 00000, "OS close system call failure"
// *Cause: OS close system call failed. The system failed to close
// a file.
// *Action: Check the OS error code
/
48184, 00000, "OS seek system call failure"
// *Cause: OS seek system call failed. The system failed to seek to
// a position in a file.
// *Action: Check the OS error code
/
48185, 00000, "OS file size system call failure"
// *Cause: OS file size call failed. The system failed to retrieve
// the file size for a file.
// *Action: Check the OS error code
/
48186, 00000, "OS check file exists system call failure"
// *Cause: OS check file exists system call failed. The system failed to
// perform the check file exists command for a file.
// *Action: Check the OS error code
/
48187, 00000, "specified directory does not exist"
// *Cause: The specified directory does not exist.
// *Action: Check the directory name.
/
48188, 00000, "user missing read, write, or exec permission on specified directory"
// *Cause: The user does not have valid permissions on the specified
// directory. The user is missing either the read, write, or
// execute permission.
// *Action: Check the permissions of the specified directory.
/
48189, 00000, "OS command to create directory failed"
// *Cause: The OS command to create a directory failed.
// *Action: Check the error number associated with the create directory
// failure.
/
48190, 00000, "OS unlink system call failure"
// *Cause: OS unlink system call failed. The system failed to perform
// unlink on the specified file.
// *Action: Check the OS error code
/
48191, 00000, "user missing read or write permission on specified file"
// *Cause: The user does not have valid permissions on the specified
// file. The user is missing either the read or write permission.
// *Action: Check the permissions of the specified file.
/
48192, 00000, "OS command to move a file failed"
// *Cause: The OS command to move a file failed.
// *Action: Check the error number associated with the move file.
/
48193, 00000, "OS command to open a directory failed"
// *Cause: The OS command to open a directory failed.
// *Action: Check the OS error associated with the open directory failure.
/
48194, 00000, "OS command to close a directory failed"
// *Cause: The OS command to close a directory failed.
// *Action: Check the OS error associated with the close directory failure.
/
48195, 00000, "OS command to remove a directory failed"
// *Cause: The OS command to remove a directory failed.
// *Action: Check the OS error associated with the remove directory failure.
/
48196, 00000, "OS command to release advisory lock failed"
// *Cause: The OS command to release the advisory lock failed
// *Action: Check the OS error associated with the release advisory lock
// failure.
/
48197, 00000, "OS command to get the file status failed"
// *Cause: The OS command to get the file status failed. This could be
// because the file is not open or file descriptor is invalid.
// *Action: Check the OS error associated with the get file status failure.
/
48198, 00000, "OS command to change the file permissions failed"
// *Cause: The OS command to change the file permissions failed.
// *Action: Check the OS error associated with the failure.
/
48199, 00000, "OS command to copy a file failed"
// *Cause: The OS command to copy a file failed.
// *Action: Check the error number associated with the copy file.
/
/////////////////////////////////////////////////////////////////////////////
/ 48200 - 48299 are reserved for AMS layer
/////////////////////////////////////////////////////////////////////////////
48200, 00000, "Illegal Input Argument [%s]"
// *Document: YES
// *Cause: An illegal argument was passed in.
// *Action: Fix the call.
48201, 00000, "Field Length Exceeds Maximum [%s] [%s] [%s]"
// *Document: YES
// *Cause: An illegal field length was used.
// *Action: Fix the call.
48202, 00000, "Illegal Identifier [%s] [%s]"
// *Document: YES
// *Cause: Illegal identifier specified.
// *Action: Use a valid identifier.
48203, 00000, "Illegal Data Type [%s]"
// *Document: YES
// *Cause: Illegal data type specified.
// *Action: Use a valid data type.
48204, 00000, "Illegal Identifier Length [%s] [%s] [%s]"
// *Document: YES
// *Cause: The input identifier is too long.
// *Action: Specify a shorter identifier.
48205, 00000, "Record Length too Big [%s] [%s] [%s]"
// *Document: YES
// *Cause: The sum of the maximum lengths of all fields exceeds the maximum
// record length that is supported.
// *Action: Remove or shorten some of the fields.
48206, 00000, "Illegal Number of Fields [%s] [%s] [%s]"
// *Document: YES
// *Cause: The number of fields specified exceeds the supported maximum.
// *Action: Remove some of the fields in the relation.
48207, 00000, "Illegal Field Name [%s]"
// *Document: YES
// *Cause: The field name is invalid.
// *Action: Specify a valid field name.
48208, 00000, "Duplicate Field Names [%s]"
// *Document: YES
// *Cause: The list of fields specified contains a duplicate field.
// *Action: Remove the duplicate field.
48209, 00000, "Relation Already Exists"
// *Document: YES
// *Cause: The relation already exists.
// *Action: Remove the relation.
48210, 00000, "Relation Not Found"
// *Document: YES
// *Cause: The relation was not found.
// *Action: Either specify a valid relation name or create one with that name.
48211, 00000, "Illegal Access Mode [%s] [%s]"
// *Document: YES
// *Cause: The supplied access mode is not recognized.
// *Action: Supply a valid mode.
48212, 00000, "Open Record Access Not Done"
// *Document: YES
// *Cause: The open record access call was not performed.
// *Action: The open record access call is required before attempting this
// call.
48213, 00000, "Incorrect Access Mode for Operation [%s] [%s]"
// *Document: YES
// *Cause: The relation was opened in a mode not compatible with the
// attempted operation being done.
// *Action: Reopen the relation in the correct mode.
48214, 00000, "Sequence Overflow [%s] [%s] [%s]"
// *Document: YES
// *Cause: The sequence number will exceed the system maximum.
// *Action: Reset the sequence number.
48215, 00000, "Sequence Invalid Operation [%s] [%s]"
// *Document: YES
// *Cause: The specified sequence operation is not valid.
// *Action: Specify a valid operation.
48216, 00000, "Field Len Exceeds Max Field Length [%s] [%s] [%s] [%s]"
// *Document: YES
// *Cause: The field length specified exceeds the defined maximum for the
// field.
// *Action: Supply a smaller field length.
48217, 00000, "Out of Space on Device"
// *Document: YES
// *Cause: The storage subsystem is out of space.
// *Action: Add more space to the storage subsystem.
48218, 00000, "Duplicate Key Name [%s] [%s]"
// *Document: YES
// *Cause: The key name already exists.
// *Action: Specify a different key name.
48219, 00000, "Key Name Doesn't Match Any Existing Key"
// *Document: YES
// *Cause: The key name provided doesn't match an existing key.
// *Action: Specify a key name that exists.
48220, 00000, "Too Many Keys Defined [%s] [%s]"
// *Document: YES
// *Cause: A key is trying to be created that exceeds the maximum number
// of keys supported.
// *Action: Drop another key.
48221, 00000, "Key Exceeds Maximum Allowed Length [%s] [%s] [%s]"
// *Document: YES
// *Cause: The sum of the lengths of the fields in the key exceeds the
// maximum length supported.
// *Action: Remove one or more fields from the key.
48222, 00000, "Predicates/Order By Not Allowed"
// *Document: YES
// *Cause: A predicate or order by can not be added after fetch has started.
// *Action: Put the predicate or order by call before the first fetch.
48223, 00000, "Interrupt Requested - Fetch Aborted - Return Code [%s] [%s]"
// *Document: Yes
// *Cause: User interrupt has occurred.
// *Action: None
48224, 00000, "DDL has occurred since parse - reparse [%s] [%s] [%s]"
// *Document: YES
// *Cause: Another session has performed a DDL (i.e. add field, create key,
// drop key) that prevents this session from being to continue.
// *Action: Call open record access again.
48225, 00000, "No More Space in Order By Buffer"
// *Document: YES
// *Cause: The order by buffer size is not sufficient for the number of rows.
// *Action: Increase the order by buffer size specified.
48226, 00000, "No Fetch in Progress"
// *Document: YES
// *Cause: An attempt to perform update or delete has occurred without a fetch.
// *Action: You must first perform a fetch.
48227, 00000, "Invalid Relation File - [%s] [%s] [%s] [%s]"
// *Document: YES
// *Cause: The AMS file is invalid or corrupt.
// *Action: Do a repair relation
48228, 00000, "Missing Define Call [%s]"
// *Document: YES
// *Cause: A call to define was not performed before doing a fetch.
// *Action: Call the define service before fetch.
48229, 00000, "Invalid Relation Handle Provided [%s] [%s]"
// *Document: YES
// *Cause: An invalid or corrupt relation handle was used.
// *Action: Possible memory corruption.
48230, 00000, "Expression arguments must match types"
// *Document: YES
// *Cause: Incorrect type semantics for fields in the predicate.
// *Action: Correct the predicate.
48231, 00000, "Predicate syntax error"
// *Document: YES
// *Cause: A syntax error exists in the predicate string.
// *Action: Correct the predicate.
48232, 00000, "Debug command syntax error [%s]"
// *Document: YES
// *Cause: An invalid debug command has been specified.
// *Action: Correct the debug command.
48233, 00000, "Invalid Field Handle [%s] [%s] [%s]"
// *Document: Yes
// *Cause: The field handle is invalid.
// *Action: Possible memory corruption.
48234, 00000, "Create Field of Field Name [%s] Failed"
// *Document: No
// *Cause:
// *Action:
48235, 00000, "Operation [%s] on Relation [%s] Failed"
// *Document: No
// *Cause:
// *Action:
48236, 00000, "Operation [%s] on Relation [%s] Field [%s] Failed"
// *Document: No
// *Cause:
// *Action:
48237, 00000, "Operation [%s] on Relation [%s] Key [%s] Failed"
// *Document: No
// *Cause:
// *Action:
48238, 00000, "Invalid Surrogate Length Specified [%s] [%s]"
// *Document: Yes
// *Cause: An invalid length during create field was specified
// *Action: Specify a correct length
48239, 00000, "Invalid Predicate Handle Provided [%s] [%s]"
// *Document: YES
// *Cause: An invalid or corrupt relation handle was used.
// *Action: Possible memory corruption.
48240, 00000, "Field is NOT NULL but NULL value supplied"
// *Document: YES
// *Cause: A field [%s] declared to not allow nulls contains a null value.
// *Action: Specify a correct value
48241, 00000, "File is at wrong version [file = %s] [current = %s]"
// *Document: NO
// *Cause: The file version doesn't match the current version.
// *Action: Drop and recreate the relation
48242, 00000, "Fields that are NOT NULL can not use surrogates"
// *Document: YES
// *Cause: NOT NULL fields can not have surrogates specified.
// *Action: Either remove the constraint or the surrogate.
48243, 00000, "Additional Fields must be declared nulls allowed"
// *Document: YES
// *Cause: A field can not be added to a relation that is defined NOT NULL
// *Action: Do not specify NOT NULL
48244, 00000, "Purge for Retention can't be called while in an Query"
// *Document: YES
// *Cause: A query is already running - purge for retention can't be invoked
// *Action: Fix call sequence
48245, 00000, "Attempt to Update/Delete when at EOF"
// *Document: Yes
// *Cause: The fetch operation is positioned at EOF - can not update/delete
// *Action: Do not call update/delete after fetch has returned EOF
48246, 00000, "Illegal Operation on External Relation"
// *Document: Yes
// *Cause: An illegal call was made using an external relation
// *Action: Do not perform the API Call
48247, 00000, "Predicate Conversion Error %s"
// *Document: YES
// *Cause: A time conversion failed
// *Action: Fix the input
48248, 00000, "Function %s type check error; ityp = %s typ = %s arg = %s"
// *Document: YES
// *Cause: Invalid inputs to the specified function
// *Action: Change the inputs
48249, 00000, "Type mismatch - lhs = %s, rhs = %s, result = %s, op = %s"
// *Document: NO
// *Cause: More documentation on type mismatch
// *Action: Adjust predicate inputs
48250, 00000, "Details: %s"
// *Document: NO
// *Cause: Syntax error
// *Action: Fix the syntax error
48251, 00000, "Failed to open relation due to following error"
// *Document: YES
// *Cause: See error below in the error stack
// *Action: See error below in the error stack
48252, 00000, "Relation does not require migration"
// *Document: YES
// *Cause: Relation on disk is compatible with the current code
// *Action: Don't run the migration services
48253, 00000, "Relation Being Migrated - Can't be opened"
// *Document: NO
// *Cause: Migration in progress
// *Action: Wait till migration finishes
48254, 00000, "Migration Error [%s] [%s] [%s] [%s] [%s] [%s]"
// *Document: NO
// *Cause: Migration Failure - Internal error
// *Action: Migration Failure - Internal error
48255, 00000, "Changes not supported on relations opened read-only"
// *Document: NO
// *Cause: Relation was opened as a not-on-disk relation
// *Action: Can't make changes to this relation
48256, 00000, "Having by not allowed"
// *Document: NO
// *Cause: No group by specified
// *Action: Add a group by clause before adding a having by
48257, 00000, "Grouping function (%s) used - but no group by specified"
// *Document: NO
// *Cause: Group functions require group by clause
// *Action: Add a group by clause
48258, 00000, "AMS Corrupt Page Found - Rebuild Relation"
// *Document: YES
// *Cause: A corrupted page has been found.
// *Action: Do a rebuild of the relation
48259, 00000, "AMS Relation not Created Correctly"
// *Document: YES
// *Cause: Create relation failed
// *Action: Recreate the relation
48260, 00000, "Function %s not found"
// *Document: YES
// *Cause: A reference to a function that is not valid was found
// *Action: Fix the function name
48261, 00000, "Grouping Function %s not allowed in a having clause"
// *Document: NO
// *Cause: A grouping function was used in a having clause incorrectly
// *Action: Fix the having clause
48262, 00000, "Sequence references not allowed in predicates"
// *Document: YES
// *Cause: References to currval or nextval not allowed
// *Action: Remove these references
48263, 00000, "Currval not set yet - use nextval"
// *Document: YES
// *Cause: References to currval can't occur until a nextval is done
// *Action: Remove the reference
48264, 00000, "Internal Application Function Failure"
// *Document: NO
// *Cause:
// *Action:
48265, 00000, "Incorrect number of arguments (%s) provided - expected (%s)"
// *Document: YES
// *Cause: Number of arguments to function is incorrect
// *Action: Specify the correct number of arguments
48290, 00000, "Xaction Control General Fault"
// *Document: NO
// *Cause: See error in the error stack
// *Action:
48291, 00000, "Field name %s can't be unique resolved"
// *Cause: Field name appears in more than one relation
// *Action: Prefix the field name with the relation name
48292, 00000, "Can't use outer join syntax mixed with inner join syntax"
// *Cause: The join condition was specified using both inner and outer join elements"
// *Action: Specify the join condition correctly
48293, 00000, "Outer join syntax not allowed without a join"
// *Cause: Using outer join syntax in the predicate without doing a join
// *Action: Fix the predicate
/////////////////////////////////////////////////////////////////////////////
/ 48300 - 48389 are reserved for AMI layer
/////////////////////////////////////////////////////////////////////////////
48300, 00000, "Incident Record Already Exists"
// *Document: YES
// *Cause: trying to create an incident that already exists
// *Action: retry operation with new incident ID
48301, 00000, "An Invalid Incident ID was specified"
// *Document: YES
// *Cause: the specified incident ID was invalid
// *Action: retry operation with correct incident ID
48302, 00000, "Incident Directory does not exist"
// *Document: YES
// *Cause: the incident directory was not found
// *Action: retry operation with a different incident ID
48303, 00000, "Exceeded max Incident Sequence Value"
// *Document: YES
// *Cause: the maximum supported incident sequence value was exceeded
// *Action: reset incident sequence and retry operation
48304, 00000, "incident staging file not found"
// *Document: YES
// *Cause: the incident staging file is missing
// *Action: retry with a different incident ID
48305, 00000, "incident ID range is too large"
// *Document: YES
// *Cause: the maximum incident sequence value was exceeded
// *Action: retry operation with a smaller range
48308, 00000, "Illegal input parameter: [prm = %s] [pos = %s]"
// *Document: NO
// *Cause: the input parameter is wrong
// *Action: retry operation with correct parameter
48309, 00000, "illegal incident state transition, [%s] to [%s]"
// *Document: YES
// *Cause: the incident cannot be moved to the new state
// *Action: retry operation with a valid incident status
48310, 00000, "Incident %s staging file not found"
// *Document: YES
// *Cause: the incident staging file does not exist
// *Action: retry operation with a valid incident ID
48311, 00000, "Invalid field name [%s]"
// *Document: YES
// *Cause: the specified field name is invalid
// *Action: retry operation with a valid field name
48312, 00000, "Sweep incident %s staging file failed"
// *Document: YES
// *Cause: the sweep action of incident staging file failed
// *Action: check the incident ID and retry
48313, 00000, "Updates not allowed on ADR relation [%s] of Version=%s"
// *Document: YES
// *Cause: Update operations not supported on this version of ADR relation
// *Action: check ADR version and retry
48314, 00000, "Invalid ADR Control parameter [%s]"
// *Document: YES
// *Cause: the specified control parameter is invalid
// *Action: check parameter and reissue command
48315, 00000, "ADR unavailable"
// *Document: YES
// *Cause: the ADR directory is not available
// *Action: enable ADR and retry operation
48316, 00000, "relation [%s] unavailable or cannot be created"
// *Document: YES
// *Cause: the ADR relation is not available
// *Action: check ADR directory and retry operation
48317, 00000, "ADR Relation [%s] of version=%s is obsolete"
// *Document: YES
// *Cause: the version of ADR relation is too old and not supported
// *Action: check the ADR version and retry
48318, 00000, "ADR Relation [%s] of version=%s cannot be supported"
// *Document: YES
// *Cause: the version of ADR relation is too new and cannot be supported
// *Action: need to use a newer release to access the ADR
48319, 00000, "Update operation on ADR relation [%s] not allowed"
// *Document: YES
// *Cause: updates to foreign ADR relation cannot be supported
// *Action: verify ADR location and reissue command
48320, 00000, "Too many incidents to report"
// *Document: YES
// *Cause: the result set of incidents is too large to handle
// *Action: use a predicate to reduce the number of incidents and retry
48321, 00000, "ADR Relation [%s] not found"
// *Document: YES
// *Cause: the required ADR relation is missing, ADR may be corrupted
// *Action: check ADR directory and retry
48322, 00000, "Relation [%s] of ADR V[%s] incompatible with V[%s] tool"
// *Document: YES
// *Cause: the tool version is incompatible with the ADR version
// *Action: use another version of tool and retry
48323, 00000, "Specified pathname [%s] must be inside current ADR home"
// *Document: YES
// *Cause: A file outside of ADR home was not allowed for this type of file.
// *Action: Check the file name and retry.
48324, 00000, "Incompatible staging file encountered"
// *Document: YES
// *Cause: sweep incident failed because staging file is incompatible
// *Action: check the incident ID and version of ADR and retry
48325, 00000, "Staging File Validation Error [%s] line [%s]"
// *Document: NO
// *Cause: staging file is not compliant with the xsd
// *Action: none
48326, 00000, "Illegal Staging File Type %s"
// *Document: NO
// *Cause: staging file type is invalid
// *Action: none
48327, 00000, "Illegal Staging Status Type %s"
// *Document: NO
// *Cause: staging status type is invalid
// *Action: none
48328, 00000, "View already exists - use replace option"
// *Document: NO
// *Cause: View already exists
// *Action: Use Create or Replace
48329, 00000, "Create View Fails with the following errors"
// *Document: NO
// *Cause: See errors below
// *Action: See errors below
48330, 00000, "Expected Clause (%s) not found"
// *Document: NO
// *Cause: Expected syntax element not found
// *Action: Adjust statement
48331, 00000, "Views only allowed %s relations to be specified"
// *Document: NO
// *Cause: Too many relations specified
// *Action: Specify fewer relations
48332, 00000, "invalid relation-field name [%s] in select list"
// *Document: NO
// *Cause: the length of the field name is too long
// *Action: verify field name and reissue command
48333, 00000, "select field name [%s] not found"
// *Document: NO
// *Cause: the name specified in the select list does not exist
// *Action: verify field name and reissue command
48334, 00000, "ambiguous select field name [%s] found"
// *Document: NO
// *Cause: more than one possible target field found for select list
// *Action: verify field name and reissue command
48335, 00000, "illegal function reference to more than one field [%s], relation [%s]"
// *Document: NO
// *Cause: references to more than one row source and field detected
// *Action: verify field name for function and reissue command
48336, 00000, "missing Alias name for function column [%s]"
// *Document: NO
// *Cause: function column must be accompanied by an alias name
// *Action: verify field name and reissue command
48338, 00000, "Invalid function argument"
// *Document: NO
// *Cause: an invalid argument was specified for a function
// *Action: Fix the input arguments
48339, 00000, "view [%s] does not exist"
// *Document: YES
// *Cause: view has not been created
// *Action: verify view name and reissue command
48340, 00000, "operation not supported on view [%s]"
// *Document: YES
// *Cause: unsupported (dml) operation on views
// *Action: verify relation name and reissue command
48341, 00000, "Field [%s] not a grouping field"
// *Document: YES
// *Cause: the field name specified is not a grouping field
// *Action: verify field names and groupby clause and reissue command
48342, 00000, "Field [%s] cannot be mixed with %s fields"
// *Document: YES
// *Cause: the specified field is incompatible with other grouping fields
// *Action: verify this and other field names and reissue command
48343, 00000, "invalid field [%s] reference in %s clause"
// *Document: YES
// *Cause: the specified field in the specified clause is invalid
// *Action: verify this field name and reissue command
48344, 00000, "Invalid Name [%s] specified"
// *Document: YES
// *Cause: Either the name refers to an existing object or violates the
// reserved namespace rules.
// *Action: Pick another name
48345, 00000, "Timeout encountered during operation"
// *Document: YES
// *Cause: The attempted operation conflicted with another operation
// that was already being executed.
// *Action: Retry operation at a later time.
/////////////////////////////////////////////////////////////////////////////
/ 48390 - 48389 are reserved for ADM layer
/////////////////////////////////////////////////////////////////////////////
48390, 00000, "Too many fields"
// *Document: NO
// *Cause: Too many fields being added
// *Action: Use less fields
48391, 00000, "Field %s not found in object"
// *Document: NO
// *Cause: Field is not part of the relation
// *Action: Use the proper field name
48392, 00000, "Field (%s) conversion error - type %s value %s"
// *Document: NO
// *Cause: Invalid input for the type of field
// *Action: Fix the inputted value
48393, 00000, "Field (%s) exceeds maximum length of %s"
// *Document: NO
// *Cause: Invalid input for the type of field
// *Action: Fix the inputted value
48394, 00000, "Field (%s) is declared as NOT NULL"
// *Document: NO
// *Cause: Field contains a null value
// *Action: Fix the inputted value
48395, 00000, "Incident Range Function Only Available on Dual"
// *Document: NO
// *Cause: Must use dual with this function
// *Action: Use dual
48396, 00000, "Invalid range supplied - valid range is [%s.%s]"
// *Document: NO
// *Cause: Invalid range
// *Action: Fix input
48397, 00000, "Range must be a numeric constant"
// *Document: NO
// *Cause: Invalid range - must be a literal, not a field reference
// *Action: Use a literal
/////////////////////////////////////////////////////////////////////////////
/ 48400 - 48499 are reserved for ADV layer
/////////////////////////////////////////////////////////////////////////////
48400, 00000, "ADRCI initialization failed"
// *Document: YES
// *Cause: The ADR Base directory does not exist
// *Action: Either create an ADR Base directory or point to an existing one
// *Comment:
48401, 00000, "SET command requires arguments"
// *Document: YES
// *Cause: No arguments are input for the SET command
// *Action: Input the arguments
48402, 00000, "Variable is not defined"
// *Document: YES
// *Cause: No substitution value is input.
// *Action: Input the substitution value following after the variable name.
48403, 00000, "DEFINE or UNDEFINE command has no arguments"
// *Document: YES
// *Cause:DEFINE and UNDEFINE command need users to input the substitution
// variable name.
// *Action: Input the variable name after the keyword DEFINE or UNDEFINE
48404, 00000, "RUN or @ command has no arguments"
// *Document: YES
// *Cause: RUN and @ commands need users to input script filename
// *Action: Input script filename after RUN and @ commands
48405, 00000, "The option in the command is invalid"
// *Document: YES
// *Cause: The option is not allowed in the command
// *Action: Check the command syntax
48406, 00000, "ECHO or TERMOUT status must be set to ON or OFF"
// *Document: YES
// *Cause: the status of ECHO and TERMOUT commands must be ON or OFF
// *Action: input ON or OFF
48407, 00000, "DESCRIBE and QUERY commands need at least relation name argument"
// *Document: YES
// *Cause: This is no relation name is input as argument
// *Action: Need users to input at least the relation name
48408, 00000, "The incident number exceeds the maximum number [%s]"
// *Document: YES
// *Cause: The input incident number exceeds the maximum number
// *Action: Input fewer incidents
48409, 00000, "The ADR homes exceed the maximum number [%s]"
// *Document: YES
// *Cause: The input ADR homes number exceeds the maximum number
// *Action: Input shorter ADR home string
48410, 00000, "The trace path exceeds the maximum number [%s]"
// *Document: YES
// *Cause: The input trace path exceeds the maximum number
// *Action: Input less trace path
48411, 00000, "The trace files exceed the maximum number [%s]"
// *Document: YES
// *Cause: The input trace file path number exceeds the maximum number
// *Action: Input less trace file path
48412, 00000, "The parameters exceed the maximum number [%s]"
// *Document: YES
// *Cause: The input parameter number exceeds the maximum number
// *Action: Input fewer parameters
48413, 00000, "The number of orderby fields exceeds maximum number [%s]"
// *Document: YES
// *Cause: The orderby field number exceeds the maximum number
// *Action: Input fewer fields
48414, 00000, "The string in the execution option exceeds maximum length [%s]"
// *Document: YES
// *Cause: The string length is too long
// *Action: Divide the commands into two sets or use adrci scripts.
48415, 00000, "Syntax error found in string [%s] at column [%s]"
// *Document: YES
// *Cause: Parsing error found in the user input string
// *Action: Validate the input string
48416, 00000, "Variable value [%s] must be single or double quoted"
// *Document: NO
// *Cause:The variable value must be single or double quoted
// *Action:Check the variable name and single or double quoted the value
48417, 00000, "SHOW command needs arguments"
// *Document: NO
// *Cause: No arguments are input for SHOW command
// *Action: Input show command arguments
48418, 00000, "The variable [%s] is not defined"
// *Document: NO
// *Cause: The substitution variable is not defined
// *Action: Define the variable before attempting to use it
48419, 00000, "Illegal arguments"
// *Document: YES
// *Cause: The input argument is illegal
// *Action: Check the input arguments and make sure it is not null
48420, 00000, "EXPORT command must have a relation name"
// *Document: NO
// *Cause: The relation name is not input as an arguments
// *Action: Input the relation name
48421, 00000, "Predicate string in the command must be single or double quoted"
// *Document: YES
// *Cause:The predicate string is not single or double quoted
// *Action:Put single or double quotes around the predicate string
48422, 00000, "Invalid relation field type [%s]"
// *Document: YES
// *Cause:
// *Action:
48423, 00000, "IMPORT command must have a filename"
// *Document: YES
// *Cause: File name is missing from the command
// *Action: Input the import file name after the IMPORT keyword
48424, 00000, "SHOW TRACE command needs argument"
// *Document: YES
// *Cause:SHOW TRACE command needs arguments
// *Action:Input arguments
48425, 00000, "ADRCI environment is not initialized"
// *Document: NO
// *Cause:
// *Action:
48426, 00000, "The initialization filename is too long"
// *Document: YES
// *Cause:The initialization filename length exceeds the maximum length
// *Action:This is really an internal setting parameter of the ADRCI, report
// it as a bug. Alternatively move the initialization file to the
// current working directory
48427, 00000, "Unknown command"
// *Document: YES
// *Cause:
// *Action:
48428, 00000, "Input command string exceeds max length [%s]"
// *Document: YES
// *Cause: The current command string is too long and exceeds the limit
// *Action: Input less characters
48429, 00000, "Variable name [%s] is an invalid identifier"
// *Document: YES
// *Cause: The substitution variable name is not a valid identifier
// *Action: Input the valid identifier defined by ADRCI
48430, 00000, "Cannot read the parameter"
// *Document: YES
// *Cause:
// *Action:
48431, 00000, "Must specify at least one ADR home path"
// *Document: YES
// *Cause: The command syntax requires at least one ADR home path to be input
// *Action: Check the command syntax and input the home path
48432, 00000, "The ADR home path [%s] is not valid"
// *Document: YES
// *Cause: The adr home user inputs is not valid, which may due to the path
// does not exist.
// *Action: Check if the input home path exists
48433, 00000, "Unknown help topic"
// *Document: YES
// *Cause: The input topic is unknown
// *Action: Check if the topic is valid
48434, 00000, "No DDE commands are input"
// *Document: YES
// *Cause: No DDE commands are input
// *Action: Input a DDE command
48435, 00000, "Input a trace file"
// *Document: YES
// *Cause: Show trace expects a trace file
// *Action: Input a trace file
48436, 00000, "File [%s] does not exist"
// *Document: YES
// *Cause: the file does not exist
// *Action: Validate the trace file name
48437, 00000, "No IPS commands are input"
// *Document: YES
// *Cause: No IPS commands are input
// *Action: Input a IPS command
48438, 00000, "[%s] is not a valid number"
// *Document: YES
// *Cause: The input number is not valid
// *Action: Check the input number
48439, 00000, "The input path name exceeds the maximum length [%s]"
// *Document: YES
// *Cause: The input path name is too long
// *Action: Report as a bug to change the limit
48440, 00000, "Variable [%s] is already defined"
// *Document: YES
// *Cause: The variable name is defined previously
// *Action: Use another variable name
48441, 00000, "The function parameter number exceeds the maximum number [%s]"
// *Document: YES
// *Cause: The function parameter number exceeds the maximum number
// *Action: Report it as bug to change the maximum number
48442, 00000, "The number of control parameters exceeds the maximum allowed [%s]."
// *Document: YES
// *Cause: The control parameters exceeded the maximum number allowed.
// *Action: Check the parameters. If the parameters are correct, contact Oracle
// Support Services.
48443, 00000, "Trace Record type appears in the middle of the path"
// *Document: YES
// *Cause: The trace record cannot be in the middle of the path
// *Action: Validate the input
48444, 00000, "The single \".\" and \"*\" cannot appear in the middle of the path"
// *Document: YES
// *Cause: The single "." and "*" appears in the middle of the path
// *Action: Validate the input
48445, 00000, "Path expression only supports one bucket dump type"
// *Document: YES
// *Cause: The path expression only supports one bucket dump"
// *Action: Change the path expression syntax
48446, 00000, "The command needs path input"
// *Document: YES
// *Cause: No path is input as a parameter
// *Action: Input the path
48447, 00000, "The input path [%s] does not contain any ADR homes"
// *Document: YES
// *Cause: The input path does not contain ADR homes
// *Action: Validate the path
48448, 00000, "This command does not support multiple ADR homes"
// *Document: YES
// *Cause: There are multiple homes in the current adr setting.
// *Action: Use command SET HOMEPATH to set a single home
48449, 00000, "Tail alert can only apply to single ADR home"
// *Document: YES
// *Cause: There are multiple homes in the current setting
// *Action: Use command SET HOMEPATH to set a single home
/
/ Help messages
/
48450, 1, "Syntax:\n"
48451, 2, " adrci [-help] [-script script_filename]\n\n"
48452, 1, "Options Description (Default)\n"
48453, 1, "-----------------------------------------------------------------\n"
48454, 1, "script script file name (None) \n"
48455, 1, "help help on the command options (None) \n"
48456, 1, "-----------------------------------------------------------------\n"
48457, 00000, "ADRCI core dumped"
// *Document: YES
// *Cause: It is adrci internal error.
// *Action: Report to Oracle
48458, 00000, "\"show incident\" failed due to the following errors"
// *Document: YES
// *Cause: There could be a bug or users do not have the access permission
// *Action: Report to Oracle if the errors are not due to ADR permission settings
48459, 00000, "\"describe\" command only supports one ADR home path"
// *Document: YES
// *Cause: Multiple ADR home paths in the command
// *Action: put one ADR home path
48460, 00000, "The home path [%s] is not valid"
// *Document: YES
// *Cause: The input home path is not valid home path
// *Action: Verify the homepath
48461, 00000, "\"describe\" failed due to the following errors"
// *Document: YES
// *Cause: Underlying code failed
// *Action: If it is not due to permission issue, report to Oracle
48462, 00000, "Fatal error encountered in [%s]"
// *Document: YES
// *Cause: Fatal error encountered
// *Action: Report to Oracle
48463, 00000, "The value buffer reached the maximum length [%s]"
// *Document: YES
// *Cause: The value buffer is full
// *Action: Report to Oracle
48464, 00000, "The predicate buffer reached the maximum length [%s]"
// *Document: YES
// *Cause: The predicate buffer is too small
// *Action: Report to Oracle
48465, 00000, "The specified type [%s] is undefined"
// *Document: YES
// *Cause: The purge type specified is undefined
// *Action: Check the type name
48466, 00000, "Internal failure, the report context is not initialized"
// *Document: YES
// *Cause: Internal problem failure.
// *Action: Report to Oracle
48467, 00000, "\"%s\" for the keyword \"%s\" is not a valid number"
// *Document: YES
// *Cause: The keyword value is not a valid number
// *Action: Check the value
48468, 00000, "\"%s\" is not a valid keyword"
// *Document: YES
// *Cause: The keyword is not defined for the command
// *Action: Check the available keywords
48469, 00000, "Keyword \"%s\" cannot be duplicated"
// *Document: YES
// *Cause: The command can only allow one key with the name
// *Action: Remove one keyword name from the command
48470, 00000, "Unknown \"%s\" command"
// *Document: YES
// *Cause: The command is not valid
// *Action: Use help manual to check the command syntax
48471, 00000, "\"%s\" is not a valid shell command"
// *Document: NO
// *Cause: The shell command is not valid
// *Action: Check the command
48472, 00000, "Invalid product name"
// *Document: YES
// *Cause: The product name provided does not exist
// *Action: Specify a product name, see HELP SHOW BASE
48473, 00000, "Internal failure, unknown return code [%s]"
// *Document: YES
// *Cause: Internal program failure
// *Action: Report to Oracle
48474, 00000, "Syntax error specifying product, must not be NULL"
// *Document: YES
// *Cause: The product clause is being used, but no product name is provided
// *Action: Supply the product name
48475, 00000, "[%s] is not a valid timestamp"
// *Document: YES
// *Cause: The input timestamp string is not in valid format
// *Action: None
48476, 00000, "Cannot write the results out to a file, please check if \nthe environment variable TMPDIR is set or the current directory is \nnot writable"
// *Document: YES
// *Cause: The current path may not be writable
// *Action: If the current path is writable, report to Oracle
48477, 00000, "The input path does not contain any valid ADR homes"
// *Document: YES
// *Cause: The input path does not contain any valid ADR homes
// *Action: Check the path if it is valid
48478, 00000, "No alert messages are created"
// *Document: YES
// *Cause: No alert messages are created
// *Action: No action
48479, 00000, "No HM runs are created"
// *Document: YES
// *Cause: There is no hm runs
// *Action: No action
48480, 00000, "No incidents are created"
// *Document: YES
// *Cause: There is no incident
// *Action: No action
48481, 00000, "Report is not available"
// *Document: YES
// *Cause: The requested report does not exist"
// *Action: Check the report ID
48482, 00000, "Report is not generated"
// *Document: YES
// *Cause: The requested report is not ready to be generated
// *Action: Check the report ID
48483, 00000, "Spooling failed, it may be because the spool file cannot be created due to a permission issue"
// *Document: YES
// *Cause: The spooling filename may not be valid or the file cannot be created
// *Action: Check the permissions of the target directory and verify the filename
48484, 00000, "Run script failed, it may be because the script file does not exist"
// *Document: YES
// *Cause: The script file may not exist
// *Action: Check if the script file exist
48485, 00000, "The file exceeds the maximum length [%s]"
// *Document: YES
// *Cause: The filename is too long
// *Action: Report to Oracle
48486, 00000, "The file [%s] exceeds the maximum length [%s]"
// *Document: YES
// *Cause: The filename is too long
// *Action: Report to Oracle
48487, 00000, "The internal predicate string exceeds the maximum length [%s]"
// *Document: YES
// *Cause: The predicate string exceeds the maximum length
// *Action: Report to Oracle
48488, 00000, "The predicate string exceeds the maximum length [%s]"
// *Document: YES
// *Cause: The input predicate string exceeds the maximum length
// *Action: Report to Oracle
48489, 00000, "The input exceeds the maximum length [%s]"
// *Document: YES
// *Cause: The input exceeds the maximum length
// *Action: Report to Oracle
48490, 00000, "The field number exceeds the maximum number [%s]"
// *Document: YES
// *Cause: The input field number exceeds the maximum number
// *Action: Input less field names
48491, 00000, "The program name is too long, exceeds the maximum length [%s]"
// *Document: YES
// *Cause: the program name length exceeds the maximum length setting
// *Action: Report to Oracle
48492, 00000, "The report component name is not defined"
// *Document: YES
// *Cause: the report component name does not exist
// *Action: Check the component name to ensure it is registered
48493, 00000, "Sweep command needs parameters"
// *Document: YES
// *Cause: sweep command needs parameter
// *Action: Check the syntax of the command
/
48494, 00000, "ADR home is not set, the corresponding operation cannot be done"
// *Document: YES
// *Cause: The adr home is not set in the current adrci session
// *Action: Set the adr home using the adrci command "set base" and "set homepath"
48495, 00000, "Interrupt requested"
// *Document: YES
// *Cause: User requested to interrupt the current action
// *Action: No action is needed
48496, 00000, "\"%s\" is a mandatory keyword for the command"
// *Document: YES
// *Cause: The keyword is not specified for the command
// *Action: Input the keyword
48497, 00000, "\"%s\" is an invalid product type"
// *Document: YES
// *Cause: The product type is not registered
// *Action: Check the product type
48499, 00000, "The value of the keyword \"%s\" exceeds the maximum length %s"
// *Document: YES
// *Cause: The keyword value is too long
// *Action: Check the limit and input again
/////////////////////////////////////////////////////////////////////////////
/ 48500- 48599 are reserved for AME layer
/////////////////////////////////////////////////////////////////////////////
48500, 00000, "File Write Error [%s] [%s]"
// *Document: YES
// *Cause: Number of bytes written differs from number requested. Possibly
// due to out of disk space.
// *Action: Ensure sufficient disk space.
48501, 00000, "File Read Error [%s] [%s]"
// *Document: YES
// *Cause: Number of bytes read differs from number requested. Possibly due
// due to corrupted file.
// *Action: Recreate the file.
48502, 00000, "Invalid Command Line - Missing Required Elements"
// *Document: YES
// *Cause: Missing required command line arguments.
// *Action: Review the help message and supply the required arguments.
48503, 00000, "Invalid Parameter Specified"
// *Document: YES
// *Cause: Invalid input parameter supplied.
// *Action: Review the help message and correct the invalid input parameter.
48504, 00000, "Relation Parameter Must be Specified"
// *Document: YES
// *Cause: Relation parameter must be specified during ADR export.
// *Action: Supply the relation parameter.
48505, 00000, "File Parameter Must be Specified"
// *Document: YES
// *Cause: File parameter must be specified during ADR import.
// *Action: Supply the file parameter.
48506, 00000, "Existing Relation at different version than export [%s] [%s]"
// *Document: YES
// *Cause: Attempting to import into an existing relation and the schema
// version of that relation differs from the schema of the relation
// that was exported.
// *Action: Drop the existing relation if you still wish to import the
// relation.
48507, 00000, "Predicate Not Allowed during Import"
// *Document: YES
// *Cause: The predicate option is not allowed during ADR import.
// *Action: Remove the predicate argument.
48508, 00000, "Export File Version [%s] Can Not be Used by Import [%s]"
// *Document: YES
// *Cause: The version of the export file is not able to be read by this
// version of ADR import.
// *Action: Rerun the export using the current version of ADR export.
48509, 00000, "Error occurred during operation. See the following errors"
// *Document: YES
// *Cause: An underlying error has occurred.
// *Action: Review and correct the underlying error.
48510, 00000, "Can not export an in memory relation"
// *Document: YES
// *Cause: In memory relations can not be exported.
// *Action: Pick a different relation.
48511, 00000, "Repair Schema currently not implemented"
// *Document: NO
// *Cause: Feature currently not implemented
// *Action: Use repair relation instead
/////////////////////////////////////////////////////////////////////////////
/ 48600 - 48699 for AMH layer
/////////////////////////////////////////////////////////////////////////////
48600, 00000, "HM run with name [%s] already exists"
// *Document: YES
// *Cause: The specified run name already existed.
// *Action: Specify different run name and re-run the check
48601, 00000, "HM run id[%s] not found"
// *Document: NO
// *Cause:
// *Action:
48602, 00000, "HM finding id [%s] not found"
// *Document: NO
// *Cause:
// *Action:
48603, 00000, "HM recommendation id [%s] not found"
// *Document: NO
// *Cause:
// *Action:
48604, 00000, "Alloc Function Pointer should not be NULL "
// *Document: NO
// *Cause: Wrong usage of AMH layer by its upper layers
// *Action:
48605, 00000, "Argument [%s] value should not be NULL"
// *Document: NO
// *Cause: Wrong usage of AMH layer by its upper layers
// *Action:
48606, 00000, "Argument [%s] value should not be ZERO"
// *Document: NO
// *Cause: Wrong usage of AMH layer by its upper layers
// *Action:
48607, 00000, "Not valid(supported) parameter type"
// *Document: NO
// *Cause: Wrong usage of AMH layer by its upper layers
// *Action:
48608, 00000, "Info list object doesn't have space"
// *Document: NO
// *Cause: Wrong usage of AMH layer by its upper layers
// *Action:
48609, 00000, "Param [%s] was not found in the infolist object"
// *Document: NO
// *Cause: Wrong usage of AMH layer by its upper layers
// *Action:
48610, 00000, "Format of info list text is not correct"
// *Document: NO
// *Cause: Wrong usage of AMH layer by its upper layers
// *Action:
48611, 00000, "Message object doesn't have space for new message"
// *Document: NO
// *Cause: Wrong usage of AMH layer by its upper layers
// *Action:
48612, 00000, "Info list object doesn't have space for new params"
// *Document: NO
// *Cause: Wrong usage of AMH layer by its upper layers
// *Action:
48613, 00000, "Finding set object doesn't have space for new finding"
// *Document: NO
// *Cause: Wrong usage of AMH layer by its upper layers
// *Action:
48614, 00000, "HM run with name [%s] not found"
// *Document: NO
// *Cause:
// *Action:
48615, 00000, "Parameter [%s] value not specified"
// *Document: YES
// *Cause: Run was invoked without specifying the parameter and its value
// *Action: Specify the needed parameter and its value
48616, 00000, "Parameter [%s] is NULL"
// *Document: NO
// *Cause:
// *Action:
48617, 00000, "Parameter [%s] value [%s] length exceeds the maximum limit [%s]"
// *Document: YES
// *Cause:
// *Action:
48618, 00000, "Invalid HM run name specified"
// *Document: YES
// *Cause: An invalid Health Monitor (HM) run name was specified.
// *Action: Specify a HM run name using only alphanumeric and underscore
// characters.
/
///////////////////////////////////////////////////////////////////////////
// Errors 48700 - 48749 reserved for DFW initialization Usage Errors
///////////////////////////////////////////////////////////////////////////
/
48700, 00000, "DBG initialization out of sequence"
// *Document: No
// *Cause: The diagctx was not in a valid state for this operation.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered.
/
48701, 00000, "DBG initialization : bad Library Group ID"
// *Document: No
// *Cause: A bad Library Group Id was passed to a DBG initialization interface.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered.
/
48702, 00000, "DBG initialization : no callbacks specified to disable ADR"
// *Document: No
// *Cause: The ADR disable option was specified but no output redirection
// callbacks were provided.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered.
/
48703, 00000, "DBG initialization : no process-level diag context specified"
// *Document: No
// *Cause: A thread-level diag context initialization performed without
// initializing a process-level diag context.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered.
/
48704, 00000, "DBG initialization : invalid value for initial number"
// *Document: No
// *Cause: A value less than zero was specified for the initial
// number of contexts to populate the diag context pool.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered.
/
48705, 00000, "DBG initialization : invalid value for working number"
// *Document: No
// *Cause: A value less than zero was specified for the working
// number of contexts for the diag context pool.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered.
/
///////////////////////////////////////////////////////////////////////////
// Errors 48750 - 48799 reserved for DFW initialization Internal Errors
///////////////////////////////////////////////////////////////////////////
/
48750, 00000, "DBG context management internal failure"
// *Document: No
// *Cause: Assertion failure in diagnosability layer code.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48751, 00000, "DBG context management internal failure"
// *Document: No
// *Cause: Assertion failure in diagnosability layer code.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48752, 00000, "DBG context management internal failure"
// *Document: No
// *Cause: Assertion failure in diagnosability layer code.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48753, 00000, "DBG context management internal failure"
// *Document: No
// *Cause: Assertion failure in diagnosability layer code.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48754, 00000, "DBG context management internal failure"
// *Document: No
// *Cause: Assertion failure in diagnosability layer code.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48755, 00000, "DBG context management internal failure"
// *Document: No
// *Cause: Assertion failure in diagnosability layer code.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48756, 00000, "DBG context management internal failure"
// *Document: No
// *Cause: Assertion failure in diagnosability layer code.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48757, 00000, "DBG context management internal failure"
// *Document: No
// *Cause: Assertion failure in diagnosability layer code.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48758, 00000, "DBG context management internal failure"
// *Document: No
// *Cause: Assertion failure in diagnosability layer code.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48759, 00000, "DBG context management internal failure"
// *Document: No
// *Cause: Assertion failure in diagnosability layer code.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48760, 00000, "DBG context management internal failure"
// *Document: No
// *Cause: Assertion failure in diagnosability layer code.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48761, 00000, "DBG context management internal failure"
// *Document: No
// *Cause: Assertion failure in diagnosability layer code.
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48762, 00000, "DBG context notification service internal failure"
// *Document: No
// *Cause: Assertion failure in initialization notification service
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
48763, 00000, "DBG memory corruption for thread local root"
// *Document: No
// *Cause: DBG thread local root is corrupted
// *Action: Report as a bug.
// *Comment: This is really an internal error, but we don't have an error
// facility at the time it is encountered. The error code
// uniquely identifies the code location.
/
/////////////////////////////////////////////////////////////////////////////
/ 48800 - 48899 are reserved for ADV layer
/////////////////////////////////////////////////////////////////////////////
48800, 00000, "\"%s\" for the keyword \"%s\" is not in the right format of timestamp"
// *Document: YES
// *Cause: The value format is not right
// *Action: Check the format ADRCI supports
48801, 00000, "The option \"%s\" is duplicated"
// *Document: YES
// *Cause: The option has been specified more than once
// *Action: Check the input
48802, 00000, "The options \"%0!s\" and \"%1!s\" are mutually exclusive."
// *Document: YES
// *Cause: An attempt was made to specify the two options together.
// *Action: Specify only one of the options.
48803, 00000, "The keyword \"%s\" is not defined for this command"
// *Document: YES
// *Cause: The keyword is invalid
// *Action: Check the valid keywords for the command
48804, 00000, "The command needs at least one file input"
// *Document: YES
// *Cause: No files are specified to view
// *Action: Input the files
48805, 00000, "BEGIN BACKUP issued already - must do an END BACKUP first"
// *Document: YES
// *Cause: A begin backup was already issued.
// *Action: Issue END BACKUP
48806, 00000, "Unknown Function Reference (%s)"
// *Document: YES
// *Cause: The function reference is not a valid function
// *Action: Change the reference
48807, 00000, "The SET subcommand requires at least one additional parameter"
// *Document: YES
// *Cause: An argument was not specified for the SET subcommand.
// *Action: Specify additional arguments or precede the command with help.
48808, 00000, "malformed SET CONTROL command - see \"HELP SET CONTROL\""
// *Document: YES
// *Cause: Improper syntax was specified for the SET CONTROL command.
// *Action: Specify additional arguments or use the HELP SET CONTROL command for more information.
48809, 00000, "The number of estimate parameters exceeds the maximum allowed [%s]."
// *Document: YES
// *Cause: The estimate parameters exceeded the maximum number allowed.
// *Action: Check the parameters. If the parameters are correct, contact Oracle
// Support Services.
48810, 00000, "malformed ESTIMATE command - see \"HELP ESTIMATE\""
// *Document: YES
// *Cause: Improper syntax was specified for the ESTIMATE command.
// *Action: Specify additional arguments or use the HELP ESTIMATE command for more information.
/////////////////////////////////////////////////////////////////////////////
/ 48900- 48999 are reserved for UTS layer
/////////////////////////////////////////////////////////////////////////////
48900, 00000, "Illegal Input Argument [%s]"
// *Document: YES
// *Cause: The input argument is invalid
// *Action: Check the input parameter
48902, 0000, "Empty component specification"
// *Document: YES
// *Cause:
// *Action:
48903, 0000, "String [%s] is not a valid library name"
// *Document: YES
// *Cause:
// *Action:
48904, 0000, "String [%s] is not a valid component name"
// *Document: YES
// *Cause:
// *Action:
48905, 0000, "String [%s] is not a valid operation name"
// *Document: YES
// *Cause:
// *Action:
48906, 00000, "Parser context is not valid"
// *Document: YES
// *Cause: The parser context is not initialized
// *Action: Call the initialization routine first before using the context
48907, 00000, "The end of file is reached"
// *Document: YES
// *Cause: The end of file is reached
// *Action: Handle the end of file
48908, 00000, "No trace files are found"
// *Document: YES
// *Cause: This is no file in the navigator context, either it is done with
// parsing, or no file is pushed
// *Action: Check if the file is added to the context
48909, 00000, "Scan context is not initialized"
// *Document: YES
// *Cause: The scan context is not initialized
// *Action: call the initialization routine of the scan context
48910, 00000, "Fetch already started"
// *Document: NO
// *Cause: Cannot add files if the fetch is already started
// *Action: Add the file before fetching
48911, 00000, "The parent node does not exist"
// *Document: NO
// *Cause: The current node does not have parent node
// *Action: Check the input node to see if it has parent
48912, 00000, "The specified trace filename is too long"
// *Document: YES
// *Cause:The resulting trace filename length exceeds the maximum length
// *Action:Use a smaller trace filename suffix or move ADR higher in the
// directory hierarchy
48913, 00000, "Writing into trace file failed, file size limit [%s] reached"
// *Cause:An attempt was made to write into a trace file that exceeds
// the trace's file size limit
// *Action:increase the trace's file size limit.
48914, 00000, "File position is not in right format"
// *Document: YES
// *Cause: The file position format is not right
// *Action: Check if the file format string is the right one
48915, 00000, "The output format is not supported"
// *Document: NO
// *Cause: The requested trace output format is not supported
// *Action: Check the valid output format
48916, 00000, "Cannot open the output file with path [%s] and filename [%s]"
// *Document: NO
// *Cause: The file path may not exist, or the filename may not valid
// *Action: Check the filepath and filename
48917, 00000, "Fail to seek to the requested file position"
// *Document: NO
// *Cause: The file name may not exist
// *Action: Verify the filename
48918, 00000, "Interruption is caught"
// *Document: NO
// *Cause: User entered CTRL-C
// *Action: No action is needed
48919, 00000, "End of Fetch is reached in the trace navigator"
// *Document: NO
// *Cause: The file has reached the end
// *Action: No action is needed
48920, 00000, "The merge context is not initialized"
// *Document: NO
// *Cause: The merge context is not initialized
// *Action: initialize the merge context before other operations
48921, 00000, "The begin timestamp cannot be larger than the end timestamp"
// *Document: NO
// *Cause: The begin timestamp is larger than the end timestamp
// *Action: verify the begin and end timestamp
48922, 00000, "The input homepath is not a valid ADR home"
// *Document: NO
// *Cause: The homepath is not a valid ADR home
// *Action: Verify the homepath
48923, 00000, "There is no file to be merged"
// *Document: NO
// *Cause: There is no file to be merged
// *Action: Verify if the filenames are correct
48924, 00000, "The merge is done"
// *Document: NO
// *Cause: The merge is done
// *Action: Terminate the merge context
48925, 00000, "The incident does not exist"
// *Document: NO
// *Cause: The incident does not exist
// *Action: Check if the incident ID exists
48926, 00000, "The offset is not valid"
// *Document: NO
// *Cause: The requested offset is not valid
// *Action: Verify the position flag is specified
48927, 00000, "The requested line number does not exist"
// *Document: NO
// *Cause: The file does not have the requested line number
// *Action: Check the file and the line number
48928, 00000, "The predicate exceeds the max limit %s"
// *Document: YES
// *Cause: The predicate is too long, exceeds the max limit
// *Action: Use a shorter predicate
48929, 00000, "The trace record size exceeded the max size that can be read [%s]"
// *Document: YES
// *Cause: A trace record is too large to be read by the ADR viewer
// *Action: Report to Oracle
48930, 00000, "Cannot allocate memory for processing traces"
// *Document: YES
// *Cause: A memory allocation request failed
// *Action: Report to Oracle
48931, 00000, "The metadata header of file [%s] is not valid"
// *Document: NO
// *Cause: The metadata is not written correctly
// *Action:
48932, 00000, "The data offset is not in non-decreasing order at byte [%s]"
// *Document: NO
// *Cause:
// *Action:
48933, 00000, "Fail to switch to ADR default home"
// *Document: NO
// *Cause: We are unable to switch to the ADR default home due to an error
// with the internal ADR state.
// *Action: Report to Oracle
48934, 00000, "invalid input for the file name identifier"
// *Cause: An invalid input was given for the file name identifier. The
// file name is not allowed to have slashes ('\', '/') and is not
// allowed to refer to the parent directory using the '..' characters.
// *Action: Check the file name and provide a valid input.
48935, 00000, "bucket snapshotting error: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]"
// *Document: NO
// *Cause: The UTS bucket snapshot was not consistent.
// *Action:
48936, 00000, "The number of relations exceeds maximum number [%s]"
// *Cause: Too many relations listed
// *Action: Reduce the number
48937, 00000, "Feature (%s) currently not allowed for SELECT"
// *Cause: Feature is not allowed
// *Action: Remove feature
48938, 00000, "View select column count differs from select alias list"
// *Cause: The view alias list has a different number of fields than the select list"
// *Action: Change the alias list or view select statement
48939, 00000, "Select * not allowed in a CREATE VIEW"
// *Cause: * is currently not allowed for a create view select list
// *Action: List the fields explicitly
48940, 00000, "invalid value %s (length = %s) for parameter _MAX_INCIDENT_FILE_SIZE"
// *Document: NO
// *Cause: The string supplied for the parameter _MAX_INCIDENT_FILE_SIZE was
// not an integer, an integer followed by 'K', 'M' or 'G', nor the
// special value UNLIMITED.
// *Action: Provide a proper value for this parameter.
48941, 00000, "The maximum metadata version that can be processed is [%s]"
// *Document: NO
// *Cause: The metadata file version being read is greater than the maximum
// version that can be processed by the parser.
// *Action: Upgrade the client to a later release.
///////////////////////////////////////////////////////////////////////////
// Errors 49100 - 49199 reserved for Events++ errors
///////////////////////////////////////////////////////////////////////////
49100, 00000, "Failed to process event statement [%s] "
// *Document: NO
// *Cause:
// *Action:
49101, 00000, "Failed to parse action [%s]"
// *Document: NO
// *Cause:
// *Action:
49102, 00000, "Action definition for [%s] not found"
// *Document: NO
// *Cause:
// *Action:
49103, 00000, "Missing Mandatory argument [%s] for %s [%s]"
// *Document: NO
// *Cause:
// *Action:
49104, 00000, "[%s] is not a valid argument for %s [%s]"
// *Document: NO
// *Cause:
// *Action:
49105, 00000, "Too many arguments specified for %s [%s]"
// *Document: NO
// *Cause:
// *Action:
49106, 00000, "Parameter value [%s] is invalid"
// *Document: NO
// *Cause:
// *Action:
49107, 00000, "Passed end of string while parsing"
// *Document: NO
// *Cause:
// *Action:
49108, 00000, "Event Name [%s] not found"
// *Document: NO
// *Cause:
// *Action:
49109, 00000, "Library Name [%s] not found"
// *Document: NO
// *Cause:
// *Action:
49110, 00000, "Parameter value [%s] length is longer than maximum allowed"
// *Document: NO
// *Cause:
// *Action:
49111, 00000, "Parsing failed because memory allocation failed"
// *Document: NO
// *Cause:
// *Action:
49112, 00000, "Parameter value [%s] is not one of allowed values"
// *Document: NO
// *Cause:
// *Action:
49113, 00000, "Scope event limit exceeded, scoped events may work incorrectly"
// *Document: NO
// *Cause:
// *Action:
49114, 00000, "Target not specified for scope [%s]"
// *Document: NO
// *Cause:
// *Action:
49115, 00000, "Target not specified for event [%s]"
// *Document: NO
// *Cause:
// *Action:
49116, 00000, "SQL ID string [%s] is invalid"
// *Document: NO
// *Cause:
// *Action:
49150, 0000, "Parameter NULL for this call [%s]"
// *Document: NO
// *Cause:
// *Action:
49151, 0000, "Event group not initialized"
// *Document: NO
// *Cause:
// *Action:
49152, 0000, "Event parse context not initialized"
// *Document: NO
// *Cause:
// *Action:
49153, 0000, "Event group sync failed, parent[%s] is not parent of child[%s]"
// *Document: NO
// *Cause:
// *Action:
49154, 0000, "Failed to initialize parse context in [%s]"
// *Document: NO
// *Cause:
// *Action:
49155, 0000, "Failed to initialize event group in [%s]"
// *Document: NO
// *Cause:
// *Action:
49156, 0000, "Failed to destroy parse context in [%s]"
// *Document: NO
// *Cause:
// *Action:
49157, 0000, "Syncing failed, parent and child are same group"
// *Document: NO
// *Cause:
// *Action:
49158, 0000, "Empty Filter Specification"
// *Document: NO
// *Cause:
// *Action:
49159, 0000, "Too many filters specified"
// *Document: NO
// *Cause:
// *Action:
49160, 0000, "Scope or Filter cannot be specified for mapped event, use [%s]"
// *Document: NO
// *Cause:
// *Action:
49161, 0000, "Usage for event %s : %s"
// *Document: NO
// *Cause:
// *Action:
49162, 0000, "[%s] is not a valid scope"
// *Document: NO
// *Cause:
// *Action:
49163, 0000, "Event string must begin with a valid event name/number"
// *Document: NO
// *Cause:
// *Action:
49164, 0000, "Event number is invalid"
// *Document: NO
// *Cause:
// *Action:
49165, 0000, "Too many arguments for event %s"
// *Document: NO
// *Cause:
// *Action:
49166, 0000, "Keyword IMMEDIATE must be at the beginning of event string"
// *Document: NO
// *Cause:
// *Action:
49167, 00000, "Invalid value of parameter [%s] for %s [%s]"
// *Document: NO
// *Cause:
// *Action:
49168, 00000, "Missing value for name-value pair"
// *Document: NO
// *Cause:
// *Action:
49169, 00000, "Event [%s] is not a valid filter"
// *Document: NO
// *Cause:
// *Action:
49170, 00000, "arg=action() construct can not be used in %s [%s]"
// *Document: NO
// *Cause:
// *Action:
49171, 00000, "Type of parameter [%s] is not compatible with action [%s]"
// *Document: NO
// *Cause:
// *Action:
49172, 00000, "Depth of action nesting exceeds allowed limit"
// *Document: NO
// *Cause:
// *Action:
49173, 00000, "Parameter [%s] of %s [%s] must be specified as a literal"
// *Document: NO
// *Cause:
// *Action:
49174, 00000, "Unable to set event in %s due to %s"
// *Document: NO
// *Cause:
// *Action:
///////////////////////////////////////////////////////////////////////////
// Errors 49200 - 49299 reserved for DDE errors
///////////////////////////////////////////////////////////////////////////
49200, 00000, "DDE Internal Error"
// *Document: NO
// *Cause:
// *Action:
49201, 00000, "Arguments not valid for DDE invocation"
// *Document: NO
// *Cause:
// *Action:
49202, 00000, "DDE global context not initialized for DDE invocation"
// *Document: NO
// *Cause:
// *Action:
49203, 00000, "Too many recursive DDE invocations"
// *Document: NO
// *Cause:
// *Action:
49204, 00000, "Recursive DDE invocation at Phase I"
// *Document: NO
// *Cause:
// *Action:
49205, 00000, "DDE async action error [%s] [%s] [%s] [%s] [%s] [%s] [%s] [%s]"
// *Document: NO
// *Cause:
// *Action: None
49206, 00000, "No DDE async actions in queue"
// *Document: NO
// *Cause: An attempt was made to dequeue from an empty queue.
// *Action: None
///////////////////////////////////////////////////////////////////////////
// Errors 49300 - 49399 reserved for DDE User Actions errors
///////////////////////////////////////////////////////////////////////////
49300, 00000, "DDE User Actions Internal Error"
// *Document: NO
// *Cause:
// *Action:
49301, 00000, "Illegal input argument [%s]"
// *Document: NO
// *Cause: An illegal argument was passed in.
// *Action: Fix the calling function.
49302, 00000, "Invalid action/invocation specified [%s] [%s] [%s]"
// *Document: NO
// *Cause: The specified combination of incident, action name and invocation
// doesn't exist.
// *Action: Specify an existing combination of incident, action and invocation.
49303, 00000, "Invalid action specified (action not defined) [%s]"
// *Document: NO
// *Cause: The specified action is not defined in this ADR.
// *Action: Specify an action based on an available action definition.
49304, 00000, "Invalid action/invocation/parameter specified [%s] [%s] [%s] [%s]"
// *Document: NO
// *Cause: The specified combination of incident, action name, invocation and
// parameter (position) doesn't exist.
// *Action: Specify an existing combination. Check the number of parameters.
49305, 00000, "Invalid parameter specified (action parameter not defined) [%s] [%s]"
// *Document: NO
// *Cause: The specified action parameter is not defined in this ADR.
// *Action: Specify an action parameter based on an available parameter
// definition.
49306, 00000, "Invalid parameter length specified, argn:%s, len:%s, lim:%s"
// *Document: NO
// *Cause: A specified parameter value was too long.
// *Action: Input a parameter value of valid length.
49307, 00000, "Invalid length in user credentials, argn:%s, len:%s, lim:%s"
// *Document: NO
// *Cause: A specified username or password was too long.
// *Action: Input a username or password of valid length.
49308, 00000, "Unable to read ADR record [%s]"
// *Document: NO
// *Cause: There was an error reading records from ADR.
// *Action: Check underlying errors on the error stack.
49309, 00000, "Action failed [%s] [%s] [%s]"
// *Document: NO
// *Cause: An action invoked through OCI failed.
// *Action: Verify that the called PL/SQL function exists, and that the
// logged-in user has execute privileges on the function.
49310, 00000, "Invalid command string length [%s] [%s] [%s] [%s]"
// *Document: NO
// *Cause: A too long OS command string was constructed.
// *Action:
49311, 00000, "Command processor not found (system call returned null value) [%s] [%s]"
// *Document: NO
// *Cause: The system call could not execute, because there is no command
// processor.
// *Action: Check the operating system.
49312, 00000, "No incident provided and no default incident set"
// *Document: NO
// *Cause: A command-line command did not specify an incident,
// and no incident had been set using the SET INCIDENT command.
// *Action: Specify an incident id, or use SET INCIDENT to set an incident.
49313, 00000, "Specified parameter cannot be modified [%s] [%s]"
// *Document: NO
// *Cause: A command tried to modify the value of a parameter that has the
// "unmodifiable" flag.
// *Action: Modify the value of another parameter.
49314, 00000, "Specified action is in status INCOMPLETE and cannot be executed"
// *Document: NO
// *Cause: Attempt to execute an action in status INCOMPLETE.
// *Action: Provide all parameters in order to change the action status.
49315, 00000, "Invalid incident type specified [%s]"
// *Document: YES
// *Cause: The specified incident type is not defined in this ADR.
// *Action: Specify an available incident type.
///////////////////////////////////////////////////////////////////////////
// Errors 49400 - 49499 reserved for IPS errors
///////////////////////////////////////////////////////////////////////////
49400, 00000, "IPS Internal Error"
// *Document: NO
// *Cause: An internal error was encountered.
// *Action: Report to Oracle as a bug.
// *Comment: This is a bug.
49401, 00000, "Illegal input argument [%s]"
// *Document: NO
// *Cause: A programming error caused invalid arguments to be passed.
// *Action: Report to Oracle.
// *Comment: This is a bug.
49402, 00000, "Invalid length specified [%s] [%s] [%s]"
// *Document: NO
// *Cause: A programming error caused an invalid length to be specified.
// *Action: Report to Oracle.
// *Comment: This is a bug.
49404, 00000, "No such package [%s]"
// *Document: YES
// *Cause: The specified package does not exist.
// *Action: Specify an existing package.
49405, 00000, "Cannot change package name [%s] [%s]"
// *Document: YES
// *Cause: Attempted to change package name after package generation.
// *Action: Use current name, or create a new package with the desired name.
// *Comment: It's not possible to change the package name after the first
// physical package has been generated.
49406, 00000, "Undefined configuration parameter specified [%s]"
// *Document: YES
// *Cause: The specified configuration parameter was not found in ADR.
// *Action: Specify an existing parameter. Re-populate parameters if necessary.
49407, 00000, "No unpacking history in this home"
// *Document: YES
// *Cause: No packages were unpacked into this home.
// *Action: Verify the current home. Unpack a package if necessary.
49408, 00000, "Invalid home specified [%s]"
// *Document: YES
// *Cause: An invalid ADR_HOME was specified.
// *Action: Verify that the directory exists, and has the correct structure.
49409, 00000, "Incremental package provided when complete expected"
// *Document: YES
// *Cause: No packages were unpacked into this home.
// *Action: Provide a complete package, or use FORCE option.
49410, 00000, "Not an IPS package"
// *Document: YES
// *Cause: The specified file was not an IPS package.
// *Action: Verify that the file is a valid zip file with expected contents.
49411, 00000, "Incompatible package version [%s] [%s]"
// *Document: NO
// *Cause: The package file is from an incompatible version.
// *Action: Regenerate the package with a compatible version, or try unpacking
// with a compatible version. Alternatively, unpack manually,
// or use the FORCE flag (not recommended).
49412, 00000, "Package ID does not match existing ID [%s] [%s]"
// *Document: YES
// *Cause: The package ID in package file did not match previously unpacked
// packages.
// *Action: Use the correct location for unpacking the package.
49413, 00000, "Package name does not match existing name [%s] [%s]"
// *Document: YES
// *Cause: The package name in package file did not match previously unpacked
// packages.
// *Action: Use the correct location for unpacking the package.
49414, 00000, "Package sequence later than expected [%s] [%s]"
// *Document: YES
// *Cause: The package sequence in package file was later than expected.
// *Action: Apply packages in correct order, or use FORCE option.
49415, 00000, "Package sequence earlier than expected [%s] [%s]"
// *Document: YES
// *Cause: The package sequence in package file was earlier than expected.
// *Action: Apply packages in correct order, or use FORCE option.
49416, 00000, "Earlier package sequence applied with FORCE option [%s] [%s]"
// *Document: YES
// *Cause: An earlier package sequence was applied using the FORCE option.
// *Action: Apply a complete sequence which is later than any already applied,
// or use FORCE option to apply an incremental package.
49417, 00000, "Cannot modify already generated package"
// *Document: YES
// *Cause: Attempted to change package attributes after package generation.
// *Action: Create a new package with the desired name.
// *Comment: Certain package attributes, such as correlation level, cannot be
// changed after the first physical package has been generated.
49418, 00000, "Invalid package name specified"
// *Document: YES
// *Cause: An invalid Incident Packaging Service (IPS) package name was
// specified.
// *Action: Specify a package name using only alphanumeric and underscore
// characters.
49420, 00000, "Package too large [%s] [%s]"
// *Document: YES
// *Cause: The package is too large.
// *Action: Remove some files or incidents from the package, or try using
// incremental mode.
49421, 00000, "Maximum number of package files generated [%s]"
// *Document: YES
// *Cause: The command generated the maximum number of package files.
// *Action: Remove some files or incidents from the package, or use
// incremental mode to generate additional files.
49423, 00000, "File outside ADR not allowed"
// *Cause: The specified file is not within the ADR directory structure.
// *Action: Specify a file inside ADR.
49424, 00000, "Directory outside ADR not allowed"
// *Cause: The specified directory is not within the ADR directory structure.
// *Action: Specify a directory inside ADR.
49425, 00000, "File inside ADR not allowed"
// *Cause: The specified file is within the ADR directory structure.
// *Action: Specify a file outside ADR.
49426, 00000, "Directory inside ADR not allowed"
// *Cause: The specified directory is within the ADR directory structure.
// *Action: Specify a directory outside ADR.
49427, 00000, "No such file or file not accessible [%s]"
// *Cause: The specified file does not exist or cannot be accessed.
// *Action: Create the file or verify file permissions.
49428, 00000, "No such directory or directory not accessible [%s]"
// *Cause: The specified directory does not exist or cannot be accessed.
// *Action: Create the directory or verify directory permissions.
49429, 00000, "File already exists and OVERWRITE option not specified [%s]"
// *Cause: The client attempted to create a file that already exists.
// *Action: Either remove the file or use the OVERWRITE option.
49430, 00000, "No such problem [%s]"
// *Document: YES
// *Cause: The specified problem does not exist.
// *Action: Specify a problem that exists in this repository.
49431, 00000, "No such incident [%s]"
// *Document: YES
// *Cause: The specified incident does not exist.
// *Action: Specify an incident that exists in this repository.
49432, 00000, "Problem not part of package [%s]"
// *Document: YES
// *Cause: The specified problem is not included in the package.
// *Action: Specify a problem that is included in the package.
49433, 00000, "Incident not part of package [%s]"
// *Document: YES
// *Cause: The specified incident is not included in the package.
// *Action: Specify an incident that is included in the package.
49434, 00000, "Invalid date format"
// *Document: YES
// *Cause: An invalid format was used to specify a date
// *Action: Specify the date in a supported format.
49435, 00000, "Flood-controlled incident not allowed here [%s]"
// *Document: YES
// *Cause: A flood-controlled incident cannot be included in a package
// *Action: Specify an incident that is not flood-controlled
49436, 00000, "Date conversion error [%s]"
// *Document: YES
// *Cause: An invalid format was used to specify a date
// *Action: Specify the date in a supported format.
49440, 00000, "Warnings while unpacking package, details in file %s"
// *Document: YES
// *Cause: There were some non-fatal errors when unpacking a package
// *Action: Review the specified unpacking log file
49441, 00000, "Warnings while finalizing package, details in file %s"
// *Document: YES
// *Cause: There were some non-fatal errors when finalizing a package
// *Action: Review the specified finalize log file
49450, 00000, "Non-zero return code from archiving utility [%s] [%s]"
// *Document: YES
// *Cause: The archiving utility (zip/unzip) returned a warning or error.
// *Action: Verify that the file and directory exist and are readable,
// and that the file is a valid zip file.
49451, 00000, "Archive file structure error [%s] [%s]"
// *Document: YES
// *Cause: The archiving utility (zip/unzip) returned an error indicating
// that the archive file structure is incorrect.
// *Action: Verify that the file was transferred correctly and that the
// file is a valid zip file.
49452, 00000, "Archiving utility out of memory [%s] [%s]"
// *Document: YES
// *Cause: The archiving utility (zip/unzip) returned an error indicating
// that it was unable to allocate enough memory.
// *Action: Check for operating system limitations on process memory usage.
49453, 00000, "Invalid command invoking archiving utility [%s] [%s]"
// *Document: YES
// *Cause: The archiving utility (zip/unzip) was invoked with an invalid
// command line, or with invalid options.
// *Action: Verify that there are no operating system settings affecting
// the behavior of the archiving utility..
49454, 00000, "Archive is missing or empty [%s] [%s]"
// *Document: YES
// *Cause: The specified archive does not exist, or is empty.
// *Action: Check if the specified archive exists.
49455, 00000, "Archive I/O failed [%s] [%s]"
// *Document: YES
// *Cause: An attempt to create, write to or read from an archive failed.
// *Action: Verify that operating system I/O operations are working correctly.
49456, 00000, "Operation failed due to insufficient disk space [%s] [%s]"
// *Document: YES
// *Cause: An operation on an archive failed due to insufficient disk space.
// *Action: Verify that there is sufficient disk space. Check for operating
// system quotas or other restrictions.
49480, 00000, "Starting to finalize package contents"
// *Document: NO
49481, 00000, "Finished finalizing package contents"
// *Document: NO
49482, 00000, "Starting package generation"
// *Document: NO
49483, 00000, "Finished package generation"
// *Document: NO
49490, 00000, "Getting additional information"
// *Document: NO
49491, 00000, "Getting CRS information"
// *Document: NO
49492, 00000, "Getting OCM information"
// *Document: NO
49493, 00000, "Getting RDA information"
// *Document: NO
49494, 00000, "Getting OSS information"
// *Document: NO
///////////////////////////////////////////////////////////////////////////
// Errors 49500 - 49599 reserved for Incident Meter Errors
///////////////////////////////////////////////////////////////////////////
49500, 00000, "Invalid Transient LifeTime[%s]"
// *Document: NO
// *Cause:
// *Action:
49501, 00000, "Invalid Critical Factor[%s]"
// *Document: NO
// *Cause:
// *Action:
49502, 00000, "Invalid Warning Factor[%s]"
// *Document: NO
// *Cause:
// *Action:
49503, 00000, "Invalid Weight Factor[%s]"
// *Document: NO
// *Cause:
// *Action:
49504, 00000, "Incident meter configuration record not found "
// *Document: NO
// *Cause:
// *Action:
49505, 00000, "Problem record not found"
// *Document: NO
// *Cause:
// *Action:
49506, 00000, "Incident record not found"
// *Document: NO
// *Cause:
// *Action:
///////////////////////////////////////////////////////////////////////////
// Errors 49600 - 49699 reserved for Events++ Parser errors
///////////////////////////////////////////////////////////////////////////
49600,0, ","
// *Document: NO
// *Cause:
// *Action:
49601,2, "syntax error: found \"%s\": expecting one of: \"%s\" etc.."
// *Document: YES
// *Cause: Syntax error discovered when processing event specification
// *Action: Enter correct event specification
49602,0, "attempt recovery: symbol \"%s\" inserted before \"%s\"."
// *Document: NO
// *Cause:
// *Action:
49603,0, "attempt recovery: symbol \"%s\" ignored."
// *Document: NO
// *Cause:
// *Action:
49604,0, "attempt recovery: symbol \"%s\" substituted for \"%s\"."
// *Document: NO
// *Cause:
// *Action:
49605,4, "error: got NULL for lexer callback."
// *Document: NO
// *Cause:
// *Action:
49606,0, "file \"%s\", line \"%s\"."
// *Document: NO
// *Cause:
// *Action:
49607,1, "error: got NULL for debug callback when debug flag is set."
// *Document: NO
// *Cause:
// *Action:
49608,4, "fatal: internal error"
// *Document: NO
// *Cause:
// *Action:
49609,4, "error: too many errors at token %s. cannot recover.. bye!"
// *Document: NO
// *Cause:
// *Action:
49610,4, "error: got NULL for one of memory callbacks and not others"
// *Document: NO
// *Cause:
// *Action:
49611,4, "error: lexer callback doesn't handle PZLEXERRGET."
// *Document: NO
// *Cause:
// *Action:
49612,1, "warning: no 'error' token lookahead for any state on parse stack."
// *Document: NO
// *Cause:
// *Action:
/ Messages 49613 -> 49699 are in diaevtus.msg
/
///////////////////////////////////////////////////////////////////////////
// Errors 49700 - 49799 reserved for diagfw PL/SQL interface
///////////////////////////////////////////////////////////////////////////
49700, 00000, ""
// *Document: NO
// *Cause:
// *Action:
/
49701, 00000, "Parameter '%s' is NULL."
// *Document: YES
// *Cause: NULL was passed to a function that requires a non-NULL parameter.
// *Action: Pass a valid non-NULL parameter.
/
49702, 00000, "unable to allocate '%s' bytes of external procedure call memory"
// *Cause: An attempt to allocate memory in a C external procedure failed due
// to insufficient memory.
// *Action: Try the operation again.
/
49703, 00000, "invalid ADR service name"
// *Cause: A NULL or undefined Automatic Diagnostic Repository (ADR) service
// name was specified.
// *Action: Specify a valid ADR service name.
/
49704, 00000, "invalid incident ID"
// *Cause: A NULL or nonpositive incident ID was specified.
// *Action: Specify a valid ADR incident ID.
/
///////////////////////////////////////////////////////////////////////////
// Errors 49800 - 49899 reserved for ADS and ADU portable layers
///////////////////////////////////////////////////////////////////////////
49800, 00000, "ADR block file [%s] could not be opened using direct I/O"
// *Cause: An error was encountered when attempting to open an Automatic
// Diagnostic Repository (ADR) block file using O_DIRECT. The system
// automatically retries the open without using O_DIRECT.
// *Action: No action is required.
/
49801, 00000, "actual permissions [%s], expected minimum permissions [%s] for effective user [%s]"
// *Document: NO
// *Cause: Informational error with additional details about the next
// error on the error stack (that is, the error above).
// *Action: Use the information provided by this error to determine the
// correct permissions or group for the failing directory.
// Alternatively, use the information to determine the correct user to
// run the diagnostic initialization for the product.
// *Comment:
/
49802, 00000, "missing read, write, or execute permission on specified ADR home directory [%s]"
// *Cause: The specified Automatic Diagnostic Repository (ADR) home directory
// did not have the correct permissions.
// *Action: Check the read, write, and execute permissions on the specified
// ADR home directory.
/
49803, 00000, "Purge not possible due to incompatible schema version."
// *Cause: The Automatic Diagnostic Repository (ADR) found on disk was
// different from the version in the library.
// *Action: Start the product to migrate automatically or use the
// ADRCI utility command MIGRATE SCHEMA.
/
49804, 00000, "cannot modify ADR PDB parameter %s"
// *Cause: An attempt was made to alter the Automatic Diagnostic
// Repository (ADR) pluggable database (PDB) - only parameters
// from a non-consolidated database or root container of a
// consolidated database.
// *Action: ADR PDB parameters cannot be altered from non-consolidated
// database or root container of a consolidated database. Switch
// to a PDB to perform the operation.
/
///////////////////////////////////////////////////////////////////////////////
// Errors 49900 - 49999 reserved for ADL portable layer
///////////////////////////////////////////////////////////////////////////////
49900, 00000, "cannot modify parameter %s"
// *Cause: An attempt was made to alter the parameter from a non-consolidated
// database or pluggable database.
// *Action: The parameter can only be altered in the root container of a
// consolidated database.
/
/////////////////////////////////////////////////////////////////////////////
/ 51000 - 51999 are reserved for HM, IR diagnosability framework errors
/ 51000 - 51099 for HM infrastructure related
/ 51100 - 51189 for IR infrastructure related
/ 51190 - 51199 for DBMS_IR package errors
/ 51200 - 51399 for DATA corruption checks (physical, logical)
/ 51400 - 51499 for ASM checks
/ 51500 - 51699 for Check Name, Descriptions and Parameter Descriptions
/ 51700 - 51749 for Report Framework (dbgx)
/////////////////////////////////////////////////////////////////////////////
51000, 00000, "HM framework error: [%s] [%s]"
// *Document: NO
// *Cause: possible bug in HM/ADR infrastructure or its checkers
// *Action: report to oracle support
// *Comment:
/
51001, 00000, "check [%s] not found in HM catalog"
// *Document: YES
// *Cause: checker name might have been misspelled
// *Action: retry running check with proper checker name
// *Comment:
/
51002, 00000, "Too many parameters"
// *Document: NO
// *Cause: Internal corruption in HM catalog
// *Action: Report as a bug
// *Comment:
/
51003, 00000, "run parameters not formatted correctly"
// *Document: YES
// *Cause: Run parameters were given in a wrong format
// *Action: Correct the run params text and try again
// *Comment:
/
51004, 00000, "Check doesn't take any input params"
// *Document: YES
// *Cause: run params were passed to the check, which doesn't take any inputs
// *Action: don't pass any run params and try again
// *Comment:
/
51005, 00000, "run params missing the parameter name"
// *Document: NO
// *Cause: run params should contain name=value pairs, but name is missing
// *Action: correct the run params format and try again
// *Comment:
/
51006, 00000, "unexpected delimiter ';' in the run params text"
// *Document: YES
// *Cause: run params were not properly formatted.
// *Action: correct the run params format and try again
// *Comment:
/
51007, 00000, "parameter [%s] not registered with this check "
// *Document: YES
// *Cause: Wrong inputs were given to this check.
// *Action: correct the run params and try the check again
// *Comment:
/
51008, 00000, "parameter [%s] value is not a proper number"
// *Document: YES
// *Cause: the given parameter value is a not a proper number
// *Action: correct the run params and try again
// *Comment:
/
51009, 00000, "parameter [%s] value type not supported yet"
// *Document: NO
// *Cause: run params were not properly formatted.
// *Action: correct the run params format and try again
// *Comment:
/
51010, 00000, " NULL context passed "
// *Document: NO
// *Cause: checkers passed NULL value to HM
// *Action: usage issue for checks, internal report to oracle
// *Comment:
/
51011, 00000, " NULL Info passed "
// *Document: NO
// *Cause: checkers passed NULL info to HM
// *Action: usage issue for checks, internal report to oracle
// *Comment:
/
51012, 00000, " Param not found "
// *Document: NO
// *Cause: internal issue
// *Action: usage issue for checks, internal report to oracle
// *Comment:
/
51013, 00000, " default message not found"
// *Document: NO
// *Cause: internal issue
// *Action: usage issue for checks, internal report to oracle
// *Comment:
/
51014, 00000, " Checker Run got Timed Out "
// *Document: NO
// *Cause: checker run got timedout
// *Action: increase the timeout for the run and try again.
// *Comment:
/
51015, 00000, "dummy HM failure with [%s] as arguments"
// *Document: NO
// *Cause: DUMMY HM FAILURE
// *Action:
// *Comment:
/
51016, 00000, "dummy HM recommendation with [%s] as arguments"
// *Document: NO
// *Cause: DUMMY HM RECO
// *Action:
// *Comment:
/
51017, 00000, "dummy HM damage description with [%s] as argument"
// *Document: NO
// *Cause: DUMMY HM RECO
// *Action:
// *Comment:
/
51018, 00000, "list parameter values are of wrong type"
// *Document: NO
// *Cause: List parameter values are of wrong type
// *Action: Correct the run_params and retry the check again
// *Comment:
/
51019, 00000, "unsupported list parameter type"
// *Document: NO
// *Cause:
// *Action: Correct the run_params and retry the check again
// *Comment:
/
51020, 00000, "parameter [%s] not found in info"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51021, 00000, "Element list full"
// *Document: NO
// *Cause: Possible misuse of dbkh_elemlist APIs.
// *Action: report to oracle
// *Comment:
/
51022, 00000, "Invalid element position"
// *Document: NO
// *Cause: Possible misuse of dbkh_elemlist APIs.
// *Action: report to oracle
// *Comment:
/
51023, 00000, "Param type mismatch"
// *Document: NO
// *Cause: Possible misuse of dbkh internal APIs
// *Action: report to oracle
// *Comment:
/
51024, 00000, "unsupported info type"
// *Document: NO
// *Cause: possible corruption with dbkh_info data structure
// *Action: report to oracle
// *Comment:
/
51025, 00000, "check name should be non NULL value"
// *Document: YES
// *Cause: NULL value was passed for check name
// *Action: give a proper check name and retry again
// *Comment:
/
51026, 00000, "Diag ADR not enabled, can't run check"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51027, 00000, "Run name should be non NULL value"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51028, 00000, "Report type should be non NULL value"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51029, 00000, "Report type should be non NULL value"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51030, 00000, "Unsupported report type"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51031, 00000, "Unsupported report level"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51032, 00000, "check name too long"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51033, 00000, "run name too long"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51034, 00000, "pseudo context not allowed"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51035, 00000, "invalid timeout value"
// *Document: YES
// *Cause: User specified an invalid timeout value
// *Action:
// *Comment:
/
51036, 00000, "check [%s] can only be executed in database instance"
// *Document: YES
// *Cause: An attempt was made to run database-specific check
// in ASM environment
// *Action: Don't run the check in ASM environment
// *Comment:
/
51037, 00000, "check [%s] can only be executed in ASM instance"
// *Document: YES
// *Cause: An attempt was made to run ASM-specific check
// in a database environment
// *Action: Don't run the check in database environment
// *Comment:
/
51100, 00000, "Control file is older than datafiles and/or log files"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_CURR_CF_OLD failure
/
51101, 00000, "NOARCHIVELOG mode restore datafile %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_REST_NO_REDO
/
51102, 00000, "cannot change priority of a critical failure %s"
// *Document: YES
// *Cause: An attempt was made to change priority of a failure with CRITICAL priority.
// *Action: No action is required.
/
51103, 00000, "cannot change priority of a closed failure %s"
// *Document: YES
// *Cause: An attempt was made to change priority of a closed failure.
// *Action: No action is required.
/
51104, 00000, "NOARCHIVELOG mode restore datafiles %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_MULT_REST_NO_REDO
/
51105, 00000, "cannot change priority of a failure to CRITICAL"
// *Document: YES
// *Cause: An attempt was made to change priority of a failure to CRITICAL.
// *Action: No action is required.
/
51106, 00000, "check failed to complete due to an error. See error below"
// *Document: YES
// *Cause: While executing the check, an unexpected error occurred.
// *Action: Check the errors below and try rerunning the check.
/
51107, 00000, "failures are changing too rapidly - retry command"
// *Document: YES
// *Cause: Failures were added or closed during a Data Recovery Advisor
// command.
// *Action: Retry the command.
/
51108, 00000, "unable to access diagnostic repository - retry command"
// *Document: YES
// *Cause: A lock or timeout error occurred when trying to read failure or
// repair data from the Automatic Diagnostic Repository.
// *Action: Retry the command.
/
51109, 00000, "repair script file is too large"
// *Document: YES
// *Cause: Data Recovery Advisor generated a repair script file
// that was too large.
// *Action: Retry the command with fewer failures selected.
/
51110, 00000, "buffer size [%s] is too small - [%s] is needed"
// *Document: YES
// *Cause: An internal buffer was too small.
// *Action: This is an internal error. Contact Oracle Support Services.
/
51111, 00000, "failure revalidation timed out"
// *Document: YES
// *Cause: Data Recovery Manager was unable to revalidate all failures
// before timing out.
// *Action: Increase timeout and retry the command.
/
51190, 00000, "Internal error [%s], [%s] from DBMS_IR"
// *Document: YES
// *Cause: An unexpected error occurred while executing a routine in the
// DBMS_IR package.
// *Action: This is an internal error. Contact Oracle Support Services.
/
51191, 00000, "Too many files opened"
// *Document: YES
// *Cause: Data Recovery Advisor attempted to open too many files using the
// DBMS_IR package.
// *Action: This is an internal error. Contact Oracle Support Services.
/
51192, 00000, "File not open"
// *Document: YES
// *Cause: Data Recovery Advisor attempted to read or write from a
// file that was not open.
// *Action: This is an internal error. Contact Oracle Support Services.
/
51193, 00000, "invalid parameter value"
// *Document: YES
// *Cause: An invalid parameter value was supplied in a call to the
// DBMS_IR package.
// *Action: Fix the parameter value and retry the call.
/
51200, 00000, "%s %s has invalid size"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_IO_INV_SIZE
/
51201, 00000, "Database cannot be mounted"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description
/
51202, 00000, "Control file %s is missing"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_CF_MISSING failure
/
51203, 00000, "Control file %s is corrupt"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_CF_CORRUPT failure
/
51204, 00000, "Control file needs media recovery"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_CF_NEEDS_MR failure
/
51205, 00000, "Control file %s does not belong to the database"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_CF_FOREIGN failure
/
51206, 00000, "Control files are mutually inconsistent"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_CF_INCONS failure
/
51207, 00000, "Insufficient kernel memory to access %s %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for failure DBKH_F_ID_IO_NO_MEM
/
51208, 00000, "Database might be unrecoverable or become unrecoverable"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description
/
51209, 00000, "Online log member %s is missing"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_LM_MISSING failure
/
51210, 00000, "Online log member %s is corrupt"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_LM_CORRUPT failure
/
51211, 00000, "%s %s cannot be opened because of limit on number of open files per process"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_IO_SOF_LIMIT
/
51212, 00000, "Online log group %s is unavailable"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_LG_UNAVAIL failure
/
51213, 00000, "%s %s cannot be accessed because of an ASM Failure"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CHECK_ASM_INSTANCE
/
51214, 00000, "%s %s cannot be opened because of system limit on number of open files"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_IO_SOF_LIMIT failure
/
51215, 00000, "Archived redo log file %s is missing"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_AL_MISSING failure
/
51216, 00000, "Archived redo log file %s is corrupt"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_AL_CORRUPT failure
/
51217, 00000, "Database cannot be opened"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description
/
51218, 00000, "%s %s cannot be accessed because of NFS mount error"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_IO_MOUNT_ERR failure
/
51219, 00000, "System datafile %s: '%s' is missing"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_SF_MISSING failure
/
51220, 00000, "System datafile %s: '%s' is corrupt"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_SF_CORRUPT failure
/
51221, 00000, "System datafile %s: '%s' needs media recovery"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_SF_NEEDS_MR failure
/
51222, 00000, "See impact for individual child failures"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description
/
51223, 00000, "%s %s cannot be accessed because of invalid partitioning of raw volume"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_IO_INV_PART failure
/
51224, 00000, "One or more non-system datafiles are missing"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_MDF_MISSING failure
/
51225, 00000, "One or more non-system datafiles are corrupt"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_MDF_CORRUPT failure
/
51226, 00000, "One or more non-system datafiles need media recovery"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_MDF_NEED_MR failure
/
51227, 00000, "%s %s does not have correct access permissions"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_ION_PERM failure
/
51228, 00000, "Datafile %s: '%s' is missing"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_DF_MISSING failure
/
51229, 00000, "Datafile %s: '%s' is corrupt"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_DF_CORRUPT failure
/
51230, 00000, "Datafile %s: '%s' needs media recovery"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_DF_NEEDS_MR failure
/
51231, 00000, "Some objects in tablespace %s might be unavailable"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description
/
51232, 00000, "Datafile %s: '%s' contains one or more corrupt blocks"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_MBL_CORRUPT failure
/
51233, 00000, "Block %s in datafile %s: '%s' is media corrupt"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_BL_CORRUPT failure
/
51234, 00000, "Object %s owned by %s might be unavailable"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description
/
51235, 00000, "Redo log group %s is corrupt near change %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_O_REDO_CORRUPT failure
/
51236, 00000, "Archived redo log file %s is corrupt near change %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_A_REDO_CORRUPT failure
/
51237, 00000, "Recovery cannot be completed"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description
/
51238, 00000, "Perform block media recovery of block %s in file %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_BL_BMR
/
51239, 00000, "Use a multiplexed copy to restore control file %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CF_COPY_MEMBER
/
51240, 00000, "Restore a backup control file"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CF_REST_REC
/
51241, 00000, "If this is a primary database and you have a CREATE CONTROLFILE script, use it to create a new control file"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CF_CREATE
/
51242, 00000, "Restore and recover datafile %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_REST_REC
/
51243, 00000, "Restore and recover datafiles %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_MULT_REST_REC
/
51244, 00000, "Recover datafile %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_RECOVER
/
51245, 00000, "Recover datafiles %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_MULT_REC
/
51246, 00000, "Take datafile %s offline"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_OFFLINE
/
51247, 00000, "Take datafiles %s offline"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_RP_ID_OFL_DFNUM_LIST
/
51248, 00000, "If this is a primary database and a standby database is available, then perform a Data Guard failover initiated from the standby"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DG_STANDBY_FO
/
51249, 00000, "Recover multiple corrupt blocks in datafile %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_MULT_BMR
/
51250, 00000, "Table object %s has corrupted data"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description for DBKH_F_ID_TABLE
/
51251, 00000, "Table %s.%s may not be accessible"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Damage description for DBKH_F_ID_TABLE
/
51252, 00000, "Row %s of table object %s has corrupted data"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description for DBKH_F_ID_TABROW
/
51253, 00000, "Table %s.%s may not be accessible"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Damage description for DBKH_F_ID_TABROW
/
51254, 00000, "Table object %s mismatched with index object %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description for DBKH_F_ID_TABIDX_MISMATCH
/
51255, 00000, "Table %s.%s is not synchronized with index %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Damage description for DBKH_F_ID_TABIDX_MISMATCH and TABIDX_ROW.
/
51256, 00000, "Table row %s of table object %s mismatched with index object %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description for DBKH_F_ID_TABIDX_ROW
/
/ 51257 is available to be used
/
51258, 00000, "Restore and recover database"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DB_REST_REC
/
51259, 00000, "Recover database"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DB_RECOVER
/
51260, 00000, "Drop and re-create redo log group member %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_LF_DROP
/
51261, 00000, "Clear redo log group %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_LG_CLEAR
/
51262, 00000, "Clear unarchived redo log group %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_LG_CLEAR_UNARC
/
51263, 00000, "Clear unarchived redo log group %s using the UNRECOVERABLE DATAFILE clause in the ALTER DATABASE CLEAR LOGFILE statement"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_LG_CLEAR_UNARC_UNREC
/
51264, 00000, "Perform flashback of the database to SCN %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DB_FLASHBACK
/
51265, 00000, "Perform incomplete database recovery to SCN %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DB_PITR
/
51266, 00000, "The repair includes complete media recovery with no data loss"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_NDL_OPT
/
51267, 00000, "The repair includes point-in-time recovery with some data loss"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_PITR_OPT
/
51268, 00000, "The repair makes some data temporarily unavailable"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_TUD_OPT
/
51269, 00000, "Ensure that all disks and network connections are functional"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CHECK_HW
/
51270, 00000, "If file %s was unintentionally renamed or moved, restore it"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_RESTORE_FILE
/
51271, 00000, "If you have an export of tablespace %s, then drop and re-create the tablespace and import the data."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_IMPORT_DATA
/
51272, 00000, "If you have the correct version of the control file, then replace the old control file"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CF_GET_VERS
/
51273, 00000, "If the instance failed when file %s was in online backup mode, then issue ALTER DATABASE END BACKUP. This option must not be used for a restored backup"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_END_BACKUP
/
51274, 00000, "If you re-created inaccessible files in an alternative location, alter initialization parameters in the parameter file appropriately"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_COPY_CF
/
51275, 00000, "Obtain a copy of redo block from an alternative source (if exists)"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_GET_REDO
/
51276, 00000, "Drop damaged log group member and add new member"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_COPY_LF
/
51277, 00000, "%s %s cannot be accessed because file system does not have correct access permissions"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_IO_FSYS_PERM failure
/
51278, 00000, "%s %s cannot be accessed because it is locked by another process"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_IO_FILE_LOCK failure
/
51279, 00000, "Block %s of %s %s cannot be accessed because of device IO error"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_IO_DEV_ERR failure
/
51280, 00000, "%s %s is inaccessible"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_IO_INAC_FILE failure
/
51281, 00000, "Force a commit of the corrupted transaction whose id is %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_FORCE_COMMIT
/
51282, 00000, "Transaction %s is corrupted; its undo segment number is %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51283, 00000, "Transaction %s is not corrupted"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51284, 00000, "Undo segment %s is not corrupted"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51285, 00000, "Damage analysis of transaction %s can be found in %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51286, 00000, "Transaction %s seems to be corrupted; its undo segment number is %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51287, 00000, "Check corrupt list in V$CORRUPT_XID_LIST for transaction %s. If present, then force commit it. If not, then corruption is likely to happen"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51288, 00000, "If you restored the wrong version of data file %s, then replace it with the correct one"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_GET_VERS
/
51289, 00000, "If you know which copy of the control file is correct, replace other copies with it"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_OVWR_CFMEM
/
51290, 00000, "Ensure that file system is mounted properly and OS kernel resources are adequately configured"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_GENERAL_INAC1
/
51291, 00000, "Increase per-process limit on number of open files"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_INCR_PROC
/
51292, 00000, "Increase operating system kernel limit on total number of open files"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_INCR_KERNEL
/
51293, 00000, "Mount NFS with the Oracle-recommended mount options"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_MOUNT_NFS
/
51294, 00000, "Ensure that disk partition provided to Oracle does not start at sector 0"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CHECK_PART
/
51295, 00000, "Mount your file system with the required access mode"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_MOUNT_PERM
/
51296, 00000, "Change access permissions for file %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CHANGE_PERM
/
51297, 00000, "Find process that is holding lock on file %s and resolve lock conflict"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_UNLOCK_FILE
/
51298, 00000, "Ensure that file %s has correct access permissions and is not locked by another process"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_GENERAL_INAC2
/
51299, 00000, "Please contact Oracle Support Services to resolve failure %s: %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CALL_SUPPORT
/
51300, 00000, "Configure operating system kernel so that there is enough memory available to open a file"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_INCR_MEM
/
51301, 00000, "SQL dictionary health check: %s %s on object %s failed"
// *Document: NO
// *Cause: A health check failed
// *Action: See the failure report
// *Comment: Failure description for DBKH_F_ID_DF
/
51302, 00000, "Damaged rowid is %s - description: %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description
/
51303, 00000, "illegal check mask value specified"
// *Document: YES
// *Cause: An illegal check mask value was specified.
// *Action: Specify one of the following legal values: COLUMN_CHECKS, ROW_CHECKS, REFERENTIAL_CHECKS, or ALL.
/
51304, 00000, "Checkpoint database and clear redo log group %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_LG_CHKP_CLEAR
/
51305, 00000, "Checkpoint database and clear unarchived redo log group %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CHKP_LG_CLEAR_UNARC
/
51306, 00000, "Checkpoint database and clear unarchived redo log group %s with unrecoverable datafile(s)"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_LG_CHKP_CLEAR_UNARC_UNREC
/
51307, 00000, "Undo segment %s is corrupted"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description
/
51308, 00000, "Restore database and recover with UNTIL CANCEL option"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DB_PITR_CANCEL
/
51309, 00000, "If you have the correct version of the control file, then replace %s with it"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_RP_ID_CF_FIND_FILENAME
/
51310, 00000, "Ensure that ASM instance is up"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CHECK_ASM_INSTANCE
/
51311, 00000, "Ensure that ASM disk group is mounted"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CHECK_ASM_MOUNTED
/
51312, 00000, "Name for datafile %s is unknown in the control file"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_DF_UNKNOWN
/
51313, 00000, "A repair cannot be performed until the database is restarted. Please shutdown, restart database in nomount mode, and retry ADVISE command"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_RESTART
/
51314, 00000, "If you have the correct version of the control file, then shutdown the database and replace the old control file"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CF_GET_VERS2
/
51315, 00000, "Perform incomplete database recovery"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DB_PITR_NO_LOG
/
51316, 00000, "No check meta-data found on specified table %s"
// *Document: YES
// *Cause: No check meta-data was found for the object
// *Action: Table may not exist or no checks currently defined for the table
/
51317, 00000, "If the file exists, rename data file %s to the name of the real file using ALTER DATABASE RENAME FILE command. If the file does not exist, create a new data file using ALTER DATABASE CREATE DATAFILE command."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_RENAME
/
51318, 00000, "The repair includes flashing the database back with some data loss"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_R_ID_FLSHBK_OPT repair option
/
51319, 00000, "The repair includes recovery in NOARCHIVELOG mode with some data loss"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for repair option DBKH_R_ID_NOARC_OPT
/
51320, 00000, "No backup of block %s in file %s was found. Drop and re-create the associated object (if possible), or use the DBMS_REPAIR package to repair the block corruption"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_MAN_BLK_REP
/
51321, 00000, "If possible, drop and re-create the object associated with the logically corrupted block %s in file %s. Otherwise, use the DBMS_REPAIR package to repair the block"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_MAN_BLK_REP2
/
51322, 00000, "Contact Oracle Support Services if the preceding recommendations cannot be used, or if they do not fix the failures selected for repair"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_LAST_MAND
/
51323, 00000, "A database state change is required to repair some failures. An automatic repair might be feasible if you mount the database."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_MOUNT_DB
/
51324, 00000, "A database state change is required to repair some failures. An automatic repair might be feasible if you open the database."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_OPEN_DB
/
51325, 00000, "Block %s in datafile %s: '%s' is logically corrupt"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_LBL_CORRUPT failure
/
51326, 00000, "Datafile %s: '%s' was not taken offline cleanly. If you do not want to recover it, then take the file OFFLINE FOR DROP and repeat the ADVISE command"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_R_ID_OFFLINE_DROP repair
/
51327, 00000, "The repair includes clearing unarchived redo log with some data loss"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Dataloss repair option description for DBKH_R_ID_CLEAR_NOARC_OPT
/
51328, 00000, "Block %s in control file is corrupt"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_CFBL_CORRUPT failure
/
51329, 00000, "The control file cannot be repaired while the database is mounted or open. Please shutdown, restart the database in nomount mode, and retry the ADVISE command. A backup control file or CREATE CONTROLFILE script will be needed for the repair. If you do not have a backup control file, a CREATE CONTROLFILE script can be built by using 'alter database backup controlfile to trace'."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_R_ID_CF_FIX_RESTART repair
/
51330, 00000, "The control file cannot be repaired while the database is open or mounted. Please shutdown, restart the database in nomount mode, and retry the ADVISE command. A CREATE CONTROLFILE script will be needed for the repair because a backup control file could not be found. If you do not have a script, one can be built by using 'alter database backup controlfile to trace'."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_R_ID_CF_CREATE_RESTART repair
/
51331, 00000, "Control file contains one or more corrupt blocks"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_MCFBL_CORRUPT failure
/
51332, 00000, "Database or some of its functionality may not be available"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure impact description for DBKH_F_ID_CFBL_CORRUPT failure
/
51333, 00000, "Open resetlogs"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_OPEN_RESETLOGS
/
51334, 00000, "Automatic repairs may be available if you shutdown the database and restart it in mount mode"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_RESTART_MOUNT
/
51335, 00000, "Initiate fast-start failover"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_FSFO
/
51336, 00000, "Redo log %s with block size %s is incompatible with native disk sector size"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure description for DBKH_F_ID_LM_DISK_SECTOR
/
51337, 00000, "Move file %s with block size %s to a disk with a compatible sector size"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DISK_SECTOR_MOVE
/
51338, 00000, "Datafile %s: '%s' is offline"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_DF_OFFLINE failure
/
51339, 00000, "Online datafile %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_ONLINE
/
51340, 00000, "One or more non-system datafiles are offline"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_MDF_OFFLINE failure
/
51341, 00000, "Tablespace %s: '%s' is offline"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_TS_OFFLINE failure
/
51342, 00000, "Online tablespace %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_TS_ONLINE
/
51343, 00000, "System datafile %s: '%s' is offline"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_SF_OFFLINE failure
/
51344, 00000, "If datafile '%s' is in the current undo tablespace, then bring it online using ALTER DATABASE DATAFILE %s ONLINE command"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_R_ID_ONLINE_UNDO
/
51345, 00000, "A database state change is required to repair some failures. An automatic repair might be feasible if you shut down the database and reopen it in read/write mode."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_OPEN_DB_RW
/
51346, 00000, "An automatic repair was generated for some of the failures selected for repair. More failures might be repaired if you open the database."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_OPEN_DB_MORE
/
51347, 00000, "An automatic repair was generated for some of the failures selected for repair. More failures might be repaired if you open the database in read/write mode."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_OPEN_DB_RW_MORE
/
51348, 00000, "Open the database read/write to validate and get repair advice for failure %s: %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_OPEN_RW_FAIL
/
51349, 00000, "Open the database to validate and get repair advice for failure %s: %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_OPEN_FAIL
/
51350, 00000, "Mount the database to validate and get repair advice for failure %s: %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_MOUNT_FAIL
/
51351, 00000, "An automatic repair was generated for some of the failures selected for repair. More failures might be repaired if you mount the database."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_MOUNT_DB_MORE
/
51352, 00000, "A database state change is required to repair the following failures."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_STATE_CHANGE
/
51353, 00000, "An automatic repair was generated for some of the failures selected for repair. A database state change is required to repair the following failures."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_STATE_CHANGE_AUTO
/
51354, 0000, "If you have an export of tablespace %s, open the database read/write, then drop and re-create the tablespace and import the data."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_IMPORT_DATA_2
/
51355, 0000, "If you have an export of tablespace %s, offline its data files, open the database read/write, then drop and re-create the tablespace and import the data."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_IMPORT_DATA_3
/
51356, 00000, "Perform a Data Guard role change (using PL/SQL routine DBMS_DG.INITIATE_FS_FAILOVER)."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DG_FSFO_FO
/
51357, 00000, "Perform a Data Guard role change (using Data Guard broker failover)."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DG_BROKER_FO
/
51358, 00000, "Perform a Data Guard role change (failover)."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DG_FO
/
51359, 00000, "Shut down, mount the database and try flush redo using ALTER SYSTEM FLUSH REDO TO 'standby name' command. Then perform a Data Guard role change (using Data Guard broker failover). Available standbys: %s."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DG_SHUTDOWN_FLUSH_BROKER_FO
/
51360, 00000, "Try flush redo using ALTER SYSTEM FLUSH REDO TO 'standby name' command. Then perform a Data Guard role change (using Data Guard broker failover). Available standbys: %s."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DG_FLUSH_BROKER_FO
/
51361, 00000, "Shut down, mount the database and try flush redo using ALTER SYSTEM FLUSH REDO TO 'standby name' command. Then perform a Data Guard role change (failover). Available standbys: %s."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DG_SHUTDOWN_FLUSH_FO
/
51362, 00000, "Try flush redo using ALTER SYSTEM FLUSH REDO TO 'standby name' command. Then perform a Data Guard role change (failover). Available standbys: %s."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DG_FLUSH_FO
/
51363, 00000, "Data Guard Switchover/Failover performance may be affected"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Damage Description
/
51364, 00000, "Recovery cannot continue"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Damage Description
/
51365, 00000, "Datafile %s: contains NOLOGGING data"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_DF_NOLOGGING failure
/
51366, 00000, "Standby redo log group %s is unavailable"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_SLG_UNAVAIL failure
/
51367, 00000, "If this is a standby database and a primary database is available, go to the primary and create a standby control file using ALTER DATABASE CREATE STANDBY CONTROLFILE command"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_R_ID_CF_STBY_CREATE repair
/
51368, 00000, "Creates a standby control file from the primary"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_R_ID_CF_REST_FROM_PRIM_REC repair
/
51369, 00000, "Redo log group may become unavailable"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Impact for DBKH_F_ID_LM_MISSING, DBKH_F_ID_LM_CORRUPT
/
51370, 00000, "Copy datafile %s from another database using BACKUP AUXILIARY FORMAT command"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_R_ID_COPY_AUXILIARY_FORMAT repair
/
51371, 00000, "If the NOLOGGING data in datafile %s exists on another database (primary or standby), take an incremental backup of it and restore it on this database"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_R_ID_INCREMENTAL_BACKUP repair
/
51372, 00000, "Restore datafile %s from primary database"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_REST_FROM_PRIM
/
51373, 00000, "No data loss mode may not be available when database is used as Data Guard"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Impact Message for DBKH_F_ID_SLG_UNAVAIL
/
51374, 00000, "Restore from standby and recover datafile %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_REST_FROM_STBY_REC
/
51375, 00000, "Restore datafile %s and recover database"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_REST_REC_NO_LOG
/
51376, 00000, "If this is a standby database, restore the controlfile for a standby database using RESTORE STANDBY CONTROLFILE FROM AUTOBACKUP command"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_CF_REST_STBY
/
51377, 00000, "Restore database from standby and recover database"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DB_REST_FROM_STBY_REC
/
51378, 00000, "Restore database from primary"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DB_REST_FROM_PRIM
/
51379, 00000, "Restore and recover database"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DB_REST_REC_NO_LOG
/
51380, 00000, "Create a new datafile %s using ALTER DATABASE CREATE DATAFILE command"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_CREATE
/
51381, 00000, "Datafiles are mutually inconsistent"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_DF_INCONS failure
/
51382, 00000, "Database may not be able to open"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for DBKH_F_ID_DF_INCONS failure
/
51383, 00000, "Ensure the primary database is up and recover database using ALTER DATABASE RECOVER MANAGED STANDBY DATABASE UNTIL CONSISTENT command. Check alert log for potential failures that may cause recovery not to run. Potential problems may include missing archived logs or datafiles being in an orphaned incarnation."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_F_ID_PRIM_UP_REC_CONS
/
51384, 00000, "Another primary exists in the Data Guard configuration"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Failure description for DBKH_F_ID_OLD_PRIMARY
/
51385, 00000, "Attempt to reinstate the old primary database, %s, as a standby database of the current primary database by issuing the REINSTATE DATABASE command of the Data Guard Broker CLI (DGMGRL) on the current primary. If the database cannot be reinstated, you must re-create the old primary database from a copy of the current primary database."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_REINSTATE_DB
/
51386, 00000, "Datafile is not protected"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Impact description for offline datafiles on a standby
/
51387, 00000, "Restore datafile %s"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DF_REST_ONLY
/
51388, 00000, "Restore database"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Repair description for DBKH_R_ID_DB_REST_ONLY
/
51401, 00000, "ASM disk group mount failure can result in failure mounting Oracle database."
// *Document: NO
// *Cause: ASM disk group mount failed due to disk(s) missing.
// *Action:
// *Comment: Damage Description for mount failure due to missing disks.
/
51402, 00000, "Disk missing from the disk group. Disk number: %s Name: %s Path: %s. \nSee trace file %s."
// *Document: NO
// *Cause: The specified disk, which is a necessary part of a disk group,
// could not be found on the system.
// *Action: Use operating system commands to restore the unavailable hardware.
// *Comment: Description for mount failure due to missing disks.
/
51403, 00000, "ASM extent allocation failed. ASM disk group may be in unbalanced state."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Damage Description for allocation failure due to disk group space exhausted.
/
51404, 00000, "Disk group '%s' Imbalance: '%s%'. Partner Imbalance: '%s%'. Size Variance: '%s%'"
// *Document: NO
// *Cause: Either Disk group or Disk partners are in imbalance state.
// *Action: Check ASM views to find the available free space in the disk group.
// *Comment: Description for allocation failure due to space exhausted.
/
51405, 00000, "ASM disk not added to disk group as requested."
// *Document: NO
// *Cause: An attempt to add a disk failed because the disk was not visible cluster-wide.
// *Action: Check ASM_DISKSTRING initialization parameter on each node to ensure that requested disks can be discovered.
// *Comment: Damage Description for add disk failure due to missing disks.
/
51406, 00000, "Requested ASM disk(s) not discovered on all nodes where disk group is mounted.\nSee trace file %s."
// *Document: NO
// *Cause: The requested disk(s) could not be discovered on all clustered nodes.
// *Action: See trace file for list of disks that were discovered on each node.
// *Comment: Description for add disk failure due to disk visibility.
/
51407, 00000, "ASM file not dropped as requested\n%s."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Damage Description for drop file failure.
/
51408, 00000, "Database %s on host %s currently accessing file."
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description for drop file failure.
/
51409, 00000, "Too many offline disks detected."
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51410, 00000, "%s"
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51411, 00000, "Insufficient number of disks to establish quorum."
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51412, 00000, "Insufficient memory available for allocation."
// *Document: NO
// *Cause:
// *Action:
// *Comment:
/
51500, 00000, "HM Test Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Name for the health monitor module test check
/
51501, 00000, "Check for health monitor functionality"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description of check
/
51502, 00000, "Number of failures to be raised"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description of parameter
/
51503, 00000, "Number of recommendations to be raised"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description of parameter
/
51504, 00000, "Damage description parameter value"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description of parameter
/
51505, 00000, "Failure description parameter value"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description of parameter
/
51506, 00000, "Dummy element list"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Description of parameter
/
51507, 00000, "DB Structure Integrity Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51508, 00000, "Checks integrity of all database files"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51509, 00000, "CF Block Integrity Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51510, 00000, "Checks integrity of a control file block"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51511, 00000, "Control file block number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51512, 00000, "Data Block Integrity Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51513, 00000, "Checks integrity of a data file block"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51514, 00000, "File number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51515, 00000, "Block number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51516, 00000, "Redo Integrity Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51517, 00000, "Checks integrity of redo log content"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51518, 00000, "SCN of the latest good redo (if known)"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51519, 00000, "Logical Block Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51520, 00000, "Checks logical content of a block"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51521, 00000, "Tablespace number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51522, 00000, "Relative block address"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51523, 00000, "Segment header relative block address"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51524, 00000, "Dictionary object number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51525, 00000, "Data object number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51526, 00000, "Table Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51527, 00000, "Checks integrity of a table"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51528, 00000, "Table object number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51529, 00000, "Table check mode"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51530, 00000, "Table-Index Cross Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51531, 00000, "Checks cross references between a table and one of its indexes"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51532, 00000, "Table object number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51533, 00000, "Index object number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51534, 00000, "Table Row Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51535, 00000, "Checks integrity of a table row"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51536, 00000, "Table object number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51537, 00000, "Table rowid"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51538, 00000, "Table-Index Row Mismatch"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51539, 00000, "Checks the cross references between a table row and an index entry"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51540, 00000, "Table object number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51541, 00000, "Index object number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51542, 00000, "Table rowid"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51543, 00000, "Index entry key"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51544, 00000, "Transaction Integrity Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51545, 00000, "Checks a transaction for corruptions"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51546, 00000, "Transaction ID"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51547, 00000, "Undo Segment Integrity Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51548, 00000, "Checks integrity of an undo segment"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51549, 00000, "Undo segment number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51550, 00000, "No Mount CF Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51551, 00000, "Checks control file in NOMOUNT mode"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51552, 00000, "CF Member Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51553, 00000, "Checks a multiplexed copy of the control file"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51554, 00000, "Control file name"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51555, 00000, "All Datafiles Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51556, 00000, "Checks all datafiles in the database"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51557, 00000, "Single Datafile Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51558, 00000, "Checks a data file"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51559, 00000, "File number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51560, 00000, "Log Group Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51561, 00000, "Checks all members of a log group"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51562, 00000, "Log group number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51563, 00000, "Log Group Member Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51564, 00000, "Checks a particular member of a log group"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51565, 00000, "Log group number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51566, 00000, "Log file name"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51567, 00000, "Archived Log Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51568, 00000, "Checks an archived log"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51569, 00000, "Archived log name"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51570, 00000, "Archived log record ID"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51571, 00000, "Redo Revalidation Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51572, 00000, "Checks redo log content"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51573, 00000, "SCN of the latest good redo (if known)"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51574, 00000, "IO Revalidation Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51575, 00000, "Checks file accessibility"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51576, 00000, "Inaccessible file name"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51577, 00000, "Inaccessible file number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51578, 00000, "IO reason"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51579, 00000, "File block size"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51580, 00000, "File block number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51581, 00000, "Block IO Revalidation Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51582, 00000, "Checks file accessibility"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51583, 00000, "Inaccessible file name"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51584, 00000, "Inaccessible file number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51585, 00000, "File block size"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51586, 00000, "Inaccessible block number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51587, 00000, "Txn Revalidation Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51588, 00000, "Revalidate corrupted transaction"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51589, 00000, "Transaction id"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51590, 00000, "Failure Simulation Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51591, 00000, "Creates dummy failures"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51592, 00000, "Dummy failure id"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51593, 00000, "Dummy failure parameters"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51594, 00000, "Dictionary Integrity Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51595, 00000, "Checks dictionary integrity"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51596, 00000, "Table name"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51597, 00000, "Check mask"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51598, 00000, "ASM Mount Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51599, 00000, "Diagnose mount failure"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51600, 00000, "ASM disk number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51601, 00000, "ASM group number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51602, 00000, "ASM Allocation Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51603, 00000, "Diagnose allocation failure"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51604, 00000, "ASM group name"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51605, 00000, "ASM Disk Visibility Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51606, 00000, "Diagnose add disk failure"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51607, 00000, "ASM File Busy Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51608, 00000, "Diagnose file drop failure"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51609, 00000, "ASM path name"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51610, 00000, "Tablespace Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51611, 00000, "Checks a tablespace"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51613, 00000, "Tablespace number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
51614, 00000, "Mount CF Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51615, 00000, "Checks control file in mount mode"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51616, 00000, "Checks mount failed because there were too many offline disks"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51617, 00000, "Diagnose mount failed because there were too many offline disks"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51618, 00000, "ASM disk number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51619, 00000, "ASM group number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51620, 00000, "Checks mount failed because there were insufficient disks"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51621, 00000, "Diagnose mount failed because there were insufficient disks"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51622, 00000, "ASM group name"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51623, 00000, "Failover Check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check name
/
51624, 00000, "Check if failover has happened"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51625, 00000, "Memory allocation check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: check name
51626, 00000, "Check to adjust memory on allocation failure"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51627, 00000, "ASM memory size"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51628, 00000, "ASM diskgroup was forcibly dismounted (no diskgroup name) check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: check name
/
51629, 00000, "Check if a diskgroup (no diskgroup name) was forcibly dismounted"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51630, 00000, "ASM diskgroup was forcibly dismounted check"
// *Document: NO
// *Cause:
// *Action:
// *Comment: check name
/
51631, 00000, "Check if a diskgroup was forcibly dismounted"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51632, 00000, "ASM diskgroup name"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51633, 00000, "Checks ASM diskgroup synchronous I/O operation failed"
// *Document: NO
// *Cause:
// *Action:
// *Comment: check name
/
51634, 00000, "Diagnose ASM diskgroup synchronous I/O operation failed"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Check description
/
51635, 00000, "ASM Synchronous I/O event type"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51636, 00000, "ASM Synchronous I/O block number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51637, 00000, "ASM disk number"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
51638, 00000, "ASM diskgroup name"
// *Document: NO
// *Cause:
// *Action:
// *Comment: Parameter description
/
/////////////////////////////////////////////////////////////////////////////
/ 51700 - 51749 for Report Framework (dbgx)
/////////////////////////////////////////////////////////////////////////////
51700, 00000, "Invalid file URL"
// *Cause: A URL with invalid syntax was provided, either directly to the
// function or through an XML IMPORT or INCLUDE.
// *Action: Check the URL.
/
51701, 00000, "Invalid file URL or path prefix"
// *Cause: Either a URL or path prefix with invalid syntax was provided.
// *Action: Check the URL.
/
51702, 00000, "Could not find file at URL provided"
// *Cause: The file requested could not be found in the given location.
// *Action: Check the URL provided.
/
51703, 00000, "Missing <body> tag from HTML"
// *Cause: An HTML document was passed to the function missing its <body>
// tag.
// *Action: Check the HTML source.
/
51704, 00000, "Error %s received from XPath engine"
// *Cause: An error was received from the XPath library during an XPath
// operation.
// *Action: Check xmlerr.h to understand the cause of the error and correct
// the relevant client code.
/
51705, 00000, "XML %s error: %s \"%s\""
// *Cause: An error was received from an underlying XDK API and is being
// resignalled.
// *Action: Check xmlerr.h to understand the cause of the error and correct
// the relevant client code.
/
/////////////////////////////////////////////////////////////////////////////
// 53000 - 53999 Reserved for Multimedia error messages
/////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////
/ 53000 - 53199 : Reserved for repository errors
////////////////////////////////////////////////////
53000, 00000, "document type \"%s\" is invalid"
// *Cause: An invalid document type was specified.
// *Action: See the ORDDCM_DOCUMENT_TYPES view for a list of valid
// document types.
53001, 00000, "<TAG> and <TAG_RANGE> tag values are null"
// *Cause: An invalid attribute was found in the private dictionary
// document. The values specified by the <TAG> and
// <TAG_RANGE> tags were null.
// *Action: A private attribute definition must contain either a non-null
// <TAG> value or a non-null <TAG_RANGE> value.
// Correct the values and try the operation again. See the private
// dictionary schema (ordcmpv.xsd) listed in the Oracle Multimedia
// documentation for more information.
53002, 00000, "document name \"%s\" already inserted"
// *Cause: The specified document name was found in the repository.
// *Action: Specify a unique document name and try again.
// See the ORDDCM_DOCUMENTS view for a list of document names.
53003, 00000, "document %s does not exist"
// *Cause: The specified document name was not found in the repository.
// *Action: Correct the value and try again. See the ORDDCM_DOCUMENTS
// view for a list of documents in the repository.
53004, 00000, "The value of tag <VR> \"%s\" is invalid."
// *Cause: An invalid value for the <VR> tag was found in the dictionary
// document.
// *Action: Correct the value and try again. The value of the <VR> tag
// must either be a value defined by DICOM or an Oracle extension.
// See the data type schema (ordcmdt.xsd) listed in the Oracle
// Multimedia documentation for a list of valid <VR> tag values.
53005, 00000, "tag references found in document: %s"
// *Cause: The delete operation failed because some tags in the
// dictionary document were being referenced by the listed
// document.
// *Action: To perform the delete operation, follow these steps:
// 1. Export the listed document to a file.
// 2. Delete the listed document from the repository.
// 3. Remove the referencing tags from the exported document.
// 4. Insert the updated document into the repository.
// 5. Repeat the delete operation.
53006, 00000, "wild card characters are not allowed in <TAG_RANGE> tags"
// *Cause: A <TAG_RANGE> tag containing wild card characters 'x' or 'X'
// was found in the dictionary document.
// *Action: Remove the wild card characters from <TAG_RANGE> tag and try again.
// See the Oracle Multimedia documentation for information about
// the private dictionary schema (ordcmpv.xsd).
53007, 00000, "The document type STANDARD_DICTIONARY is not loaded."
// *Cause: The standard dictionary document was not found.
// *Action: Load the standard dictionary document (ordcmsd.xml). This is an
// installation error. Contact Oracle Support Services.
/
/53008 53010 53011 53012 - not used
/
53008, 00000, "The <NAMESPACE> tag value is not a registered schema."
// *Cause: The schema URL specified by the value of the <NAMESPACE> tag was
// not a registered Oracle XML DB schema.
// *Action: Specify a registered schema URL value. See the ALL_XML_SCHEMAS
// view for a list of registered schemas. See the Oracle XML DB
// Developers's Guide for information about registering schemas.
// See the Oracle Multimedia documentation for information about
// the mapping document schema (ordcmmp.xsd).
53009, 00000, "cannot find the <ROOT_ELEM_TAG> tag value in the metadata schema"
// *Cause: The value of the <ROOT_ELEM_TAG> tag was not found in the metadata
// schema specified by the value of the <NAMESPACE> tag.
// *Action: Correct the value and try again. You can either specify a valid
// value for the <ROOT_ELEM_TAG> tag or clear the value of the
// <NAMESPACE> tag. See the Oracle Multimedia documentation for
// information about the mapping document schema (ordcmmp.xsd).
53010, 00000, "The value of the <VR> tag is null."
// *Cause: A null <VR> tag was found in the dictionary document.
// *Action: Correct the value and try again. If the value of the <VR> tag is
// null, then the value of the <RETIRED> tag must be set to true. See
// the Oracle Multimedia documentation for information about the
// standard dictionary schema (ordcmsd.xsd) and the private
// dictionary schema (ordcmpv.xsd).
53011, 00000, "cannot find the <MAPPED_ELEM> tag value in the metadata schema"
// *Cause: The value of the <MAPPED_ELEM> tag was not found in the metadata
// schema specified by the value of the <NAMESPACE> tag.
// *Action: Correct the value and try again. You can either specify a valid
// value for the <MAPPED_ELEM> tag or clear the value of the
// <NAMESPACE> tag. See the Oracle Multimedia documentation for
// information on the mapping document schema (ordcmmp.xsd).
53012, 00000, "cannot find the <UNMAPPED_ELEM> tag value in the metadata schema"
// *Cause: The value of the <UNMAPPED_ELEM> tag was not found in the metadata
// schema specified by the value of the <NAMESPACE> tag.
// *Action: Correct the value and try again. You can either specify a valid
// value for the <UNMAPPED_ELEM> tag or clear the value of the
// <NAMESPACE> tag. See the Oracle Multimedia documentation for
// information about the mapping document schema (ordcmmp.xsd).
53013, 00000, "cannot find the <ATTRIBUTE_TAG> value: %s in the dictionaries"
// *Cause: The value of the specified <ATTRIBUTE_TAG> tag was not found in
// the standard or private dictionaries.
// *Action: Correct the tag and/or the definer name value and try again.
// The value of the <ATTRIBUTE_TAG> tag must refer to a tag and
// definer name specified in the data dictionaries.
53014, 00000, "The runtime preference table is not empty"
// *Cause: The function was unable to process due to an internal error.
// *Action: Contact Oracle Support Services.
53015, 00000, "An internal dictionary attributes table is empty"
// *Cause: This document could not be processed due to an internal error.
// *Action: Contact Oracle Support Services.
53016, 00000, "null input argument: %s"
// *Cause: The function was unable to process due to an internal error
// *Action: Contact Oracle Support Services.
53017, 00000, "The installation file %s has an incorrect document type"
// *Cause: An incorrect document type was specified for this file during
// installation. The function was unable to process due to an
// internal error.
// *Action: Contact Oracle Support Services.
53018, 00000, "document %s contains an unsupported encrypt action attribute"
/ *******
// *Cause: The operation failed because an unsupported encrypt action
/ *******
// attribute was found in the specified anonymity document.
// *Action: Change the value of the action attribute to none, remove or replace
/ **** ****** *******
// and try the operation again.
53019, 00000, "cannot delete installation document: %s"
// *Cause: The document could not be deleted because it was
// an installation document.
// *Action: See the ORDDCM_DOCUMENTS view for a list of the documents
// in the repository.
///////////////////////////////////////////////////////////////////
/// 53020 - 53030 reserved for constraint errors
///////////////////////////////////////////////////////////////////
53020, 00000, "invalid external reference in the constraint document: %s"
// *Cause: The referenced external rule or macro could not be found
// in the repository.
// *Action: Insert the referenced documents first and try again.
53021, 00000, "cannot insert a rule or macro %s that was already inserted"
// *Cause: The rules or macros existed in the repository.
// *Action: Insert a new rule or macro.
53022, 00000, "rules or macros in the constraint document %s do not exist"
// *Cause: The rules or macros did not exist in the repository.
// *Action: Delete or update an existing rule or macro.
53023, 00000, "cannot delete or update a referenced rule or macro %s"
// *Cause: Because the rules or macros were referenced by other rules
// or macros, they could not be deleted or updated.
// *Action: Delete the referencing rules or macros first and try again.
53024, 00000, "error processing constraint document: %s"
// *Cause: An error occurred while processing the constraint document.
// *Action: If the error described in the message can be corrected, do so;
// otherwise, contact Oracle Support Services.
53025, 00000, "invalid constraint document: %s"
// *Cause: The constraint document was invalid.
// *Action: Correct the error described in the message and try again.
53026, 00000, "failed to insert the constraint %s to the database"
// *Cause: An error occurred while trying to insert the constraint document
// into the database.
// *Action: Contact Oracle Support Services.
53027, 00000, "invalid invocation of a macro %s that is partially defined"
// *Cause: Constraint rules could not invoke partially defined constraint macros.
// *Action: Ensure that all dependent constraint macros are inserted into the repository,
// then try the operation again.
///////////////////////////////// end constraint errors//////////
/
/ general repos error contd
/
53031, 00000, "unable to export or import data model: %s"
// *Cause: An error occurred during export or import data model.
// *Action: If the error described in the message can be corrected, do so;
// otherwise, contact Oracle Support Services.
53032, 00000, "The default preference document cannot be found."
// *Cause: The delete operation failed due to an internal error.
// *Action: When a user-defined preference document is deleted, the default
// values are restored from the Oracle default preference document.
// The default preference document is loaded during installation.
// If this document cannot be found, it is an unrecoverable error.
// Contact Oracle Support Services.
53033, 00000, "The default UID Definition document cannot be found."
// *Cause: The delete operation failed due to an internal error.
// *Action: When a user-defined UID Definition document is deleted, the default
// values are restored from the Oracle default UID Definition
// document. The default UID Definition document is loaded during
// installation. If this document cannot be found, it is an
// unrecoverable error. Contact Oracle Support Services.
53034, 00000, "document %s contains an unsupported action attribute"
// *Cause: The operation failed because an unsupported action
// attribute was found in the specified anonymity document.
// *Action: Change the value of the action attribute to none, remove or replace
/ **** ****** *******
// and try the operation again.
53035, 00000, "The rows for the mapping document (%s) do not exist."
// *Cause: The delete operation failed due to an internal error.
// *Action: Contact Oracle Support Services.
53036, 00000, "An internal table for the mapping document (%s) is empty."
// *Cause: The function failed due to an internal error.
// *Action: Contact Oracle Support Services.
53037, 00000, "invalid range tag, <START_TAG> %s must be less than <END_TAG> %s"
// *Cause: The operation failed because an invalid range tag was specified.
// *Action: Correct the value and try the operation again.
53038, 00000, "The data type name for tag: %s cannot be found."
// *Cause: The function failed due to an internal error.
// *Action: Contact Oracle Support Services.
53039, 00000, "user-defined preference document: %s already exists"
// *Cause: The insert operation failed because only one user-defined preference
// document is allowed.
// *Action: To change an existing user-defined preference document,
// follow these steps:
// 1. Export the specified document to a file.
// 2. Delete the specified document from the repository.
// 3. Make changes to the exported document.
// 4. Insert the updated document into the repository.
// To add a new user-defined preference document, follow these steps:
// 1. Delete the specified document from the repository.
// 2. Insert the new document into the repository.
53040, 00000, "user-defined UID definition document: %s already exists"
// *Cause: The insert operation failed because only one user-defined UID
// definition document is allowed.
// *Action: To change an existing user-defined UID definition document,
// follow these steps:
// 1. Export the specified document to a file.
// 2. Delete the specified document from the repository.
// 3. Make changes to the exported document.
// 4. Insert the updated document into the repository.
// To add a new user-defined UID definition document,
// follow these steps:
// 1. Delete the specified document from the repsitory.
// 2. Insert the new document into the repository.
53041, 00000, "The tag value for a replace action attribute is null."
/ *******
// *Cause: The operation failed because a null tag value was found for
// a replace action attribute in the anonymity document
/ *******
// *Action: Either add a non-null tag value for each replace action attribute
/ *******
// or change the value of the action attribute to none or remove
/ **** ******
// and try the operation again.
53042, 00000, "tag %s is referenced by document: %s"
// *Cause: The insert operation failed because the specified tag in the
// dictionary document was being referenced by the listed document.
// *Action: To perform the insert operation, follow these steps
// 1. Export the listed document to a file.
// 2. Delete the listed document from the repository.
// 3. Remove the specified tag from the exported document.
// 4. Insert the updated document into the repository.
// 5. Repeat the insert operation.
53043, 00000, "tag %s is referenced by unknown document"
// *Cause: The operation failed because a tag in the specified
// dictionary document was being referenced by another
// document in the repository.
// *Action: This is an internal error. Contact Oracle Support Services.
53044, 00000, "invalid tag: %s"
// *Cause: The operation failed because the specified tag was invalid.
// *Action: The tag must match the regular expression ([0-9a-fA-FxX]{8}).
// Correct the tag format and try the operation again.
// See the dictionary schemas (ordcmsd.xsd, ordcmpv.xsd) listed in
// the Oracle Multimedia documentation for more information.
53045, 00000, "invalid tag: %s"
// *Cause: The operation failed because the specified tag was invalid.
// *Action: The tag must match the regular expression ([0-9a-fA-F]{8}).
// Correct the tag format and try the operation again.
// See the dictionary schemas (ordcmsd.xsd, ordcmpv.xsd) listed in
// the Oracle Multimedia documentation for more information.
53046, 00000, "tag: %s collides with existing tag: %s in document: %s"
// *Cause: The operation failed because the specified tag collided with
// an existing tag in the specified document.
// *Action: Tag collisions are not allowed in the dictionary documents.
// Correct the specified tag in the document and try the operation
// again.
53047, 00000, "internal error: %s"
// *Cause: This document could not be processed due to an internal error.
// *Action: Contact Oracle Support Services.
53048, 00000, "definer name DICOM is not allowed in a private dictionary"
// *Cause: The operation failed because the definer name DICOM was found
// in the private dictionary.
// *Action: Correct the definer name and try the operation again.
53049, 00000, "unsupported <ATTRIBUTE_TAG> tag value: %s"
// *Cause: The operation failed because the locator path with FIELD_TAG
// was not supported in the <ATTRIBUTE_TAG> tag in the anonymity
// document.
// *Action: Remove the FIELD_TAG in the locator path and try the
// operation again.
// See the Oracle Multimedia documentation for more information
// about locator path syntax.
53050, 00000, "The data model is being edited by another user."
// *Cause: The operation failed because the data model was being edited by
// another user.
// *Action: The data model can be edited by only one administrator at a time.
53051, 00000, "no editDataModel session found"
// *Cause: The operation failed because there was no editDataModel session.
// *Action: Call the editDataModel procedure first and try the operation again.
53052, 00000, "lock release returned error: %s"
// *Cause: The operation succeeded, but an error occurred while
// releasing a lock.
// *Action: This is an internal error. Contact Oracle Support Services.
53053, 00000, "lock request error: %s"
// *Cause: The operation failed because an exclusive lock could not be
// acquired.
// *Action: This is an internal error. Contact Oracle Support Services.
53054, 00000, "An editDataModel session already exists."
// *Cause: The editDataModel procedure was called more than once in the
// same session.
// *Action: Continue the insert or delete operations,
// call rollbackDataModel to rollback the data model changes, or
// call publishDataModel to publish the data model changes.
53055, 00000, "empty data model table"
// *Cause: The operation failed because the data model table was empty.
// *Action: This is an internal error. Contact Oracle Support Services.
53056, 00000, "unrecognized preference parameter name: %s"
// *Cause: The operation failed because the parameter name was invalid.
// *Action: Correct the value and try the operation again. See the preference
// schema (ordcmpf.xsd) listed in the Oracle Multimedia documentation
// for more information.
53057, 00000, "invalid preference parameter value: %s"
// *Cause: The operation failed because the parameter value was invalid.
// *Action: Correct the value and try the operation again. See the preference
// schema (ordcmpf.xsd) listed in the Oracle Multimedia documentation
// for more information.
53058, 00000, "The <ATTRIBUTE_TAG> value:%s is not a simple tag."
// *Cause: The operation failed because the value of the specified
// <ATTRIBUTE_TAG> tag contained wild card characters 'x' or 'X'.
// *Action: Only simple tags that match the regular expression
// [0-9A-F]{8}(\(.*\))? are allowed in the <ATTRIBUTE_TAG> tag.
// For example: 00080096(DICOM), 00080096 and so on.
// Correct the tag format and try the operation again.
// See the schemas ordcmdt.xsd, ordcmmp.xsd, and ordcman.xsd listed in
// the Oracle Multimedia documentation for more information.
53059, 00000, "document name: %s is too long"
// *Cause: A document name with more than 100 characters was specified.
// *Action: Use a shorter document name and try the operation again.
53060, 00000, "%s is not a standard attribute tag"
// *Cause: The operation failed because the specified standard dictionary
// attribute tag did not have an even group number.
// *Action: A standard dictionary attribute tag represents a two-byte
// hexadecimal number (group number followed by element number)
// and must match the regular expression
// [0-9a-fA-FxX]{3}[02468aceACExX]{1}[0-9a-fA-FxX]{4}.
// Correct the attribute tag format and try the operation again.
53061, 00000, "document name %s contains reserved prefix - ORD"
// *Cause: The operation failed because the specified document name contained
// the ORD prefix that is reserved for Oracle Multimedia documents.
// *Action: Remove the ORD prefix from the document name and
// try the operation again.
53062, 00000, "invalid model name: %s"
// *Cause: The operation failed because the specified model name was invalid.
// *Action: The model name DEFAULT is the only value that is supported
// in this release. Remove the model name or replace it
// with the value DEFAULT and try the operation again.
53063, 00000, "invalid exportOption: %s"
// *Cause: The specified value for the exportOption parameter was not valid.
// *Action: Valid values for the exportOption parameter are USER, ALL,
// or ORACLE. The default value is USER. Remove the specified
// value for the exportOption parameter or replace it with a
// valid value for this parameter.
53064, 00000, "no user-defined documents to export"
// *Cause: The value USER was specified for the exportOption parameter,
// but there were no user-defined documents in the repository.
// *Action: Valid values for the exportOption parameter are USER, ALL,
// or ORACLE. Specify another valid value for the exportOption
// parameter.
53065, 00000, "stored tag list document: %s already exists"
// *Cause: The operation failed because only one
// stored tag list document is allowed.
// *Action: To change an existing stored tag list document,
// follow these steps:
// 1. Export the specified document to a file.
// 2. Delete the specified document from the repository.
// 3. Make changes to the exported document.
// 4. Insert the updated document into the repository.
// To add a new stored tag list document,
// follow these steps:
// 1. Delete the specified document from the repository.
// 2. Insert the new document into the repository.
53066, 00000, "invalid manifest file: %s or directory: %s"
// *Cause: The specified manifest file name or directory name was invalid.
// *Action: Confirm that the manifest file and the directory exist,
// and that the names are valid.
53067, 00000, "validation failed for manifest file: %s "
// *Cause: The specified manifest file did not conform to the
// XML schema ordcmmft.xsd.
// *Action: Ensure that the manifest file conforms to the XML schema
// ordcmmft.xsd.
//
53068, 00000, "cannot import data model because user-defined documents exist"
// *Cause: User-defined documents were found in the repository.
// *Action: First export all user-defined documents in the repository
// so they can be saved, then delete all user-defined documents
// in the repository before importing a data model.
53069, 00000, "doc version:%s in %s is not <= repos version:%s"
// *Cause: The document version of the specified document was not
// compatible with the repository version.
// *Action: You cannot import this data model into this version of the
// repository. Either upgrade or import a data model that is
// compatible with your repository version. See the Oracle Multimedia
// documentation for more information about document versioning
// considerations for the importDataModel procedure.
53070, 00000, "manifest file:%s does not contain all the Oracle documents"
// *Cause: The specified manifest file did not contain the complete set
// of Oracle-defined documents that were included in the
// database release.
// *Action: A manifest file can contain all user-defined documents,
// all Oracle-defined documents, or both. Confirm that the manifest
// file includes all the documents listed in the
// orddcm_dbrelease_docs information view or no Oracle-defined
// documents. See the Oracle Multimedia documentation for more
// information on manifest files.
53071, 00000, "tag: %s from %s is not listed in the stored tag list document"
// *Cause: The specified document contained a tag that was not
// included in the stored tag list document.
// *Action: If the preference parameter MANDATE_ATTR_TAGS_IN_STL
// is set to true the stored tag list document must contain all the
// tags used by the constraint and mapping documents.
// Change the preference parameter value to false,
// or add the listed tag to the stored tag list document.
// See the Oracle Multimedia documentation for more
// information on stored tag list documents.
53072, 00000, "even group number is not allowed in private tag: %s"
// *Cause: The operation failed because the specified private dictionary
// attribute tag contained an even group number.
// *Action: A dictionary attribute tag represents a two-byte
// hexadecimal number (a group number followed by an element number).
// Even group numbers are reserved for the DICOM Standard
// dictionary. Thus, the group number of a private dictionary
// attribute tag must be an odd number. Replace the even group number
// with an odd number in the specified attribute tag,
// and try the operation again.
53073, 00000, "invalid docSet: %s"
// *Cause: The specified value for the docSet parameter was not valid.
// *Action: Valid values for the docSet parameter are USER, ALL,
// or ORACLE. The default value is USER. Remove the specified
// value for the docSet parameter, or replace it with a
// valid value.
53074, 00000, "namespace value is too long"
// *Cause: A namespace value longer than 700 characters was specified
// in the mapping document.
// *Action: Use a shorter namespace value and try the operation again.
53075, 00000, "null ROOT_ELEM_TAG tag value"
// *Cause: The value of the ROOT_ELEM_TAG tag was null or all spaces.
// *Action: Correct the value and try again.
53076, 00000, "attempt to modify data model repository during rolling upgrade"
// *Cause: An attempt was made to modify the Digital Imaging and
// Communications in Medicine (DICOM) data model in an
// administrator editing session during a rolling upgrade.
// *Action: Wait for the rolling upgrade to complete, then try the operation
// again. If a DICOM administrator editing session was in
// progress when the rolling upgrade was started, execute the
// rollbackDataModel() procedure to end the DICOM administrator
// session. Then, after the rolling upgrade completes, execute
// the editDataModel() procedure to restart the session.
///////////////////////////////////////////////////////////////////
/// 531xx - repository loading errors
///////////////////////////////////////////////////////////////////
53100, 00000, "The repository data model is in invalid state."
// *Cause: Error detected while loading the data model from the repository.
// *Action: Contact Oracle Support Services.
/
/53100-53110 - available,53116 - available
/
53111, 00000, "The repository data model is not loaded."
// *Cause: The operation failed because the ord_dicom.setDataModel procedure
// was not called to load the repository data model.
// *Action: Call the ord_dicom.setDataModel procedure first and try the
// operation again.
53112, 00000, "unable to load repository: %s"
// *Cause: The ord_dicom.setDataModel procedure failed to load the repository
// due to the listed error.
// *Action: This is an internal error. Contact Oracle Support Services.
53122, 00000, "invalid document type : %s"
// *Cause: The ord_dicom.setDataModel procedure failed to load the repository
// because an invalid document type was found.
// *Action: This is an internal error. Contact Oracle Support Services.
53124, 00000, "cannot find VR number for data type: %s"
// *Cause: The VR number for the listed data type could not be found in the
// lookup table.
// *Action: This is an internal error. Contact Oracle Support Services.
53125, 00000, "invalid range tag: %s"
// *Cause: The ord_dicom.setDataModel procedure failed to load the repository
// because an invalid range tag was found in the dictionary table.
// *Action: This is an internal error. Contact Oracle Support Services.
53126, 00000, "assertion failure: %s"
// *Cause: The operation failed because an assertion error had occurred.
// *Action: This is an internal error. Contact Oracle Support Services.
////////////////////////////////////////////////////////////////
/ Error thrown from pl/sql object and packages
/ From 53200 - 53399
////////////////////////////////////////////////////////////////
/
/ 53200 - 53209 General Errors
/
53200, 00000, "Argument %s is null."
// *Cause: The argument was expecting a non-null value, but the value of
// the passed argument was null.
// *Action: Check your program and ensure that the caller of the routine
// does not pass a null argument value.
53201, 00000, "Argument %s is null or invalid."
// *Cause: The argument was expecting a non-null, valid value, but the value
// of the passed argument was null or invalid.
// *Action: Check your program and ensure that the caller of the routine
// does not pass a null or invalid argument value.
53202, 00000, "internal error, argument [%s]"
// *Cause: The internal argument was invalid.
// *Action: Contact Oracle Support Services.
53203, 00000, "security violation"
// *Cause: A possible security violation was detected.
// *Action: Check the alert log and trace file for more information.
53204, 00000, "internal interface called"
// *Cause: An internal interface was called.
// *Action: Review the Oracle Multimedia documentation and call the
// desired documented interface.
/
/ 53210 - 53229 Source Checking Errors
/
53210, 00000, "unable to read empty DICOM object"
/ *****
// *Cause: There was no data in the specified DICOM object.
// *Action: See the Oracle Multimedia documentation for
// information about loading DICOM object data into the database.
53211, 00000, "unable to read invalid ORDDicom object"
/ ********
// *Cause: The value of the source attribute or the extension attribute of
// the ORDDicom object was null.
// *Action: See the Oracle Multimedia documentation for
// information about creating a valid ORDDicom object.
53212, 00000, "unable to read invalid ORDImage object: attribute %s is null"
/ ********
// *Cause: The ORDImage object was invalid.
// *Action: See the Oracle Multimedia documentation for
// information about creating a valid ORDImage object.
53213, 00000, "cannot access DICOM data with invalid source type"
/ *****
// *Cause: An invalid source type was stored in the source attribute of the
// ORDDicom object.
// *Action: See the Oracle Multimedia documentation for information
// about the supported source types for DICOM data.
53214, 00000, "cannot access DICOM image data with invalid source type"
/ *****
// *Cause: An invalid source type was stored in the source attribute of the
// ORDImage object.
// *Action: See the Oracle Multimedia documentation for information
// about the supported source types for DICOM image data.
53215, 00000, "cannot access ORDDataSource object with invalid source type"
/ *************
// *Cause: An invalid source type was stored in the ORDDataSource object. Or,
// an error occurred while trying to retrieve a BFILE while the
// object status was local.
// *Action: See the Oracle Multimedia documentation for information
// about the supported source types.
53216, 00000, "cannot export the ORDDataSource object with an external source"
/ *************
// *Cause: The source of the ORDDataSource object was not local.
// *Action: Import the data before calling the export procedure. Or, get
// the data directly from the external source.
53217, 00000, "The source LOB locator is null."
/ ***
// *Cause: The source BLOB locator or BFILE locator was null.
// *Action: Correct the statement to pass an initialized LOB locator.
/
/ 53230 - 53249 Destination Checking Errors
/
53230, 00000, "unable to write to an invalid destination ORDDicom object"
/ ********
// *Cause: The value of the source attribute or the extension attribute of the
// destination ORDDicom object was null.
// *Action: See the Oracle Multimedia documentation for
// information about constructing a valid ORDDicom object.
53231, 00000, "unable to write to a nonlocal destination ORDDicom object"
/ ********
// *Cause: The source attribute of the destination ORDDicom object was
// not local.
// *Action: See the Oracle Multimedia documentation for
// information about constructing a local ORDDicom object.
53232, 00000, "unable to write to an invalid destination ORDImage object"
/ ********
// *Cause: The value of the source attribute of the destination ORDImage
// object was null.
// *Action: See the Oracle Multimedia documentation for
// information about constructing a valid ORDImage object.
53233, 00000, "unable to write to a nonlocal destination ORDImage object"
/ ********
// *Cause: The source attribute of the destination ORDImage object was
// not local.
// *Action: See the Oracle Multimedia documentation for
// information about constructing a local ORDImage object.
53234, 00000, "The destination BLOB locator is null."
/ ****
// *Cause: The destination BLOB locator was null.
// *Action: Correct the statement to pass an initialized BLOB locator.
/
/ 53250 - 53269 Other Parameter Checking Errors
/
53250, 00000, "Mapping document does not exist."
// *Cause: The specified mapping document did not exist.
// *Action: Check the installed mapping documents, and correct the statement
// to pass the name of an installed mapping document.
53251, 00000, "Anonymity document does not exist."
// *Cause: The specified anonymity document did not exist.
// *Action: Check the installed anonymity definition documents, and
// correct the statement to pass the name of an installed
// anonymity definition document.
53252, 00000, "Constraint does not exist."
// *Cause: The specified constraint did not exist.
// *Action: Check the installed constraints, and correct the statement
// to pass an installed constraint name.
53253, 00000, "The metadata for the new DICOM object is invalid."
/ *****
// *Cause: The metadata for the new DICOM object did not conform
// to the default metadata schema (ordcmmd.xsd).
// *Action: Check the metadata argument to ensure it has the correct namespace
// and conforms to the default metadata schema (ordcmmd.xsd).
// See the Oracle Multimedia documentation for information
// about the default metadata schema (ordcmmd.xsd).
53254, 00000, "The SOP INSTANCE UID for the new DICOM object is invalid."
/ **************** *****
// *Cause: The SOP INSTANCE UID for the new DICOM object was invalid.
// *Action: See the Oracle Multimedia documentation for
// information about creating a valid SOP INSTANCE UID.
53255, 00000, "cannot import from a null or invalid source type"
// *Cause: A null or invalid source type was specified in the import procedure.
// *Action: See the Oracle Multimedia documentation for
// information about the supported source types for the DICOM object.
53256, 00000, "cannot export to a null or invalid destination data type"
// *Cause: A null or invalid destination data type was specified in the export
// procedure.
// *Action: See the Oracle Multimedia documentation for
// information about the supported destination data types for
// the DICOM object.
53257, 00000, "Attribute does not exist."
// *Cause: The specified attribute did not exist.
// *Action: Ensure that the attribute name is valid.
53258, 00000, "Metadata attribute is not available."
// *Cause: The value of the metadata attribute of the ORDDicom
// object was null.
// *Action: Call the setProperties method first.
53259, 00000, "cannot extract metadata that conforms to the schema definition"
// *Cause: The extracted metadata did not conform to its schema definition.
// *Action: Check the metadata schema definition, the mapping document
// and the parameters for the extractMetadata method to ensure
// that they are correct. See the Oracle Multimedia
// documentation for information about creating repository
// documents and extracting metadata.
///////////////////////////////////////////////////////////////////
/// 534xx - DICOM Object Runtime Error Messages
///////////////////////////////////////////////////////////////////
53400, 00000, "Missing DICOM magic number."
/ *****
// *Cause: The DICOM object did not contain the DICOM magic number
// "dicm" required by part 10 of the DICOM standard.
// *Action:Fix the DICOM object or the DICOM object source, if possible.
// Otherwise, update the DICOM preference document
// to ignore this category of error.
53402, 00000, "Missing DICOM header."
/ *****
// *Cause: The DICOM object did not contain the file preamble.
// *Action:Fix the DICOM object or the DICOM object source, if possible.
// Otherwise, update the DICOM preference document
// to ignore this category of error.
53404, 00000, "Missing the mandatory DICOM attribute %s."
/ *****
// *Cause: One or more mandatory DICOM attributes were missing from the
// DICOM object.
// *Action:Fix the DICOM object or the DICOM object source, if possible.
// Otherwise, update the DICOM preference document
// to ignore this category of error.
53406, 00000, "The DICOM object contains invalid attribute value %s."
/ *****
// *Cause: The DICOM object did not conform to the DICOM standard
// and contained invalid attribute values.
// *Action:Fix the DICOM object or the DICOM object source, if possible.
// Otherwise, update the DICOM preference document
// to ignore this category of error.
53408, 00000, "The DICOM object encoding is wrong %s."
/ *****
// *Cause: The DICOM object did not conform to the DICOM standard's
// binary encoding rules.
// *Action:Determine if the DICOM object is corrupt. If the DICOM
// object is not corrupt, verify whether it conforms to the
// binary encoding rules in the DICOM standard. If the
// DICOM object is corrupt, fix it if possible. Otherwise,
// update the DICOM preference document to ignore this
// category of error.
53410, 00000, "The attribute %s does not conform to the VM rule."
/ **
// *Cause: The DICOM object either contained an attribute that did not conform
// to the DICOM value multiplicity rule or was missing an attribute
// that was required by the DICOM standard.
// *Action:Determine if the DICOM object conforms to the DICOM
// standard. If it does, verify if the data dictionary
// matches the DICOM object or is more recent than the
// DICOM object. If the data dictionary is obsolete,
// update it using the ORD_DICOM_ADMIN repository API,
// if possible. Otherwise, update the DICOM preference
// document to ignore this category of error.
53412, 00000, "The DICOM object contains an invalid VR value %s."
/ ***** **
// *Cause: The DICOM object with explicit value representation
// encoding had attribute VR values that did not
// match their definitions in the data dictionary.
// *Action:Determine if the DICOM object conforms to the DICOM
// standard. If it does, verify if the data dictionary
// matches the DICOM object or is more recent than the
// DICOM object. If the data dictionary is obsolete,
// update it using the ORD_DICOM_ADMIN repository API,
// if possible. Otherwise, update the DICOM preference
// document to ignore this category of error.
53414, 00000, "The DICOM object contains undefined values %s."
/ *****
// *Cause: The DICOM object had attribute values that were expected
// to be part of the data model.
// *Action:Determine if the DICOM object conforms to the DICOM
// standard. If it does, verify if the data model
// matches the DICOM object or is more recent than the
// DICOM object. If the data model is obsolete,
// update it using the ORD_DICOM_ADMIN repository API,
// if possible. Otherwise, update the DICOM preference
// document to ignore this category of error.
53430, 00000, "The DICOM object contains unsupported values %s."
/ *****
// *Cause: This type of DICOM object is not supported by the current
// release.
// *Action:Check for software updates, and contact Oracle Support
// Services for information about feature enhancements.
53432, 00000, "The DICOM object attribute %s has invalid definer name."
/ *****
// *Cause: A private attribute definer for a private attribute
// contained in this DICOM object had invalid characters.
// *Action:Determine if the DICOM object is corrupt. If the DICOM
// object conforms to the DICOM standard, contact Oracle
// Support Services.
53434, 00000, "Not a DICOM object."
/ *****
// *Cause: The binary object is not a DICOM object.
// *Action:Determine if the DICOM object is corrupt. If the DICOM
// object conforms to the DICOM standard, contact Oracle
// Support Services.
///////////////////////////////////////////////////////////////////
/// 535xx - image/content processing error
///////////////////////////////////////////////////////////////////
53500, 00000, "Not a DICOM image."
/ *****
// *Cause: The binary object was not a DICOM image.
// *Action:Determine if the DICOM object is an image. Only DICOM
// images can be processed with image processing functions.
53502, 00000, "Image processing failure."
// *Cause: An error occurred when processing a DICOM image.
// *Action:Determine if the DICOM image is corrupt, and if
// it is supported by the current release.
///////////////////////////////////////////////////////////////////
/// 538xx - runtime constraint errors
///////////////////////////////////////////////////////////////////
53800, 00000, "The DICOM object does not contain attribute %s."
/ *****
// *Cause: The DICOM object did not contain the attribute that was required
// for conformance validation.
// *Action: Determine if the locator path is properly constructed.
// All attributes used in the locator path must be defined
// in the DICOM standard, and must not be retired. All
// attributes except the last attribute in the locator path
// must be of sequence type. If the locator path is correct,
// verify if the DICOM data dictionary is up to date. If the
// data dictionary is obsolete, update it using the
// ORD_DICOM_ADMIN repository API.
53801, 00000, "cannot apply conformance validation on DICOM attribute %s."
// *Cause: The content length of the attribute exceeded the value of
// the XML_SKIP_ATTR parameter that was defined in the preference
// document.
// *Action: Remove the attribute from the constraint rule or
// increase the value of the XML_SKIP_ATTR parameter that is
// defined in the preference document. Then, attempt the operation
// again.
53802, 00000, "cannot perform conformance validation because recursion level exceeds MAX_RECURSION_DEPTH"
// *Cause: When evaluating the recursive constraint on the DICOM object,
// the number of levels of recursion exceeded the value of the
// MAX_RECURSION_DEPTH parameter that was defined in the preference
// document.
// *Action: Ensure that the constraint definition is correct. If necessary,
// increase the value of the MAX_RECURSION_DEPTH parameter that is
// defined in the preference document. Then, attempt the operation
// again.
53810, 00000, "error logging conformance validation messages"
// *Cause: An error occurred while trying to log conformance validation
// messages.
// *Action: Ensure that the constraint rule definition does not contain
// any ACTION elements if the isConformanceValid method is called
// from a SQL query. If this error persists, contact Oracle
// Support Services.
53820, 00000, "Invalid locator path %s"
// *Cause: A locator path for an attribute was invalid.
// *Action:Please verify the locator path is properly constructed.
// All attribute used in the locator path must be defined in
// the DICOM standard and must not be retired. An attribute
// that is not the last one of the locator path must be
// a sequence type. If the locator path is correct, please
// verify the DICOM data dictionary is up-to-date.
// If the data dictionary is obsolete, please use the
// ORD_DICOM_ADMIN API to update the data dictionary.
///////////////////////////////////////////////////////////////////
/// 539xx - generic error messages
///////////////////////////////////////////////////////////////////
53900, 00000, "I/O failure %s."
/ ***
// *Cause: A device I/O failure occurred when attempting to read
// from and write to a DICOM object.
// *Action:Check the permissions and privileges that have been
// granted for I/O operations.
53910, 00000, "SQL error %s."
/ ***
// *Cause: An error occurred when attempting to run a SQL command.
// *Action: If you are using a JDBC connection string, ensure that
// the connection string is valid. Check the user account
// to see if it is locked. Ensure that the listener
// and the database server are running. And ensure that
// the setDataModel() function has been invoked before any
// other DICOM functions are called.
53920, 00000, "XML error %s."
/ ***
// *Cause: An error occurred when attempting to read from and
// write to XML metadata.
// *Action:Ensure that Oracle XDB and all related schemas are
// properly installed.
53930, 00000, "XSLT error %s."
/ ***
// *Cause: An error occurred while attempting to process XML metadata.
// *Action: Ensure that Oracle XDB and all related schemas are
// properly installed. And, verify that the mapping and
// anonymity documents are valid.
53940, 00000, "make anonymous error %s."
// *Cause: An error occurred while attempting to make DICOM object anonymous.
// *Action: Ensure that the anonymity document content is valid.
53980, 00000, "unimplemented feature: %s"
// *Cause: The specified feature is not implemented.
// *Action: Contact Oracle Support Services.
53990, 00000, "internal error %s."
// *Cause: An internal error occurred while attempting to process
// a DICOM object.
// *Action:Contact Oracle Support Services, and supply them with
// a script that can be duplicated as well as the DICOM
// object that caused this error.
53991, 00000, "cannot move tablespace because tables are being used"
// *Cause: The operation failed because Oracle Multimedia tables
// were being used.
// *Action: End all sessions using Oracle Multimedia tables and try again.
/////////////////////////////////////////////////////////////////////////////
// 54000 - 54499 Reserved for Expression Column error codes
/////////////////////////////////////////////////////////////////////////////
54000, 0000, "Virtual column feature not yet implemented"
// *Cause: Feature has not been implemented.
// *Action: Feature is being implemented.
54001, 0000, "%s: invalid identifier specified for virtual column expression"
// *Cause: Column expression referenced a column that does not exist in the
// table.
// *Action: Rewrite column expression to reference only scalar columns in the
// table.
54002, 0000, "only pure functions can be specified in a virtual column expression"
// *Cause: Column expression contained a function whose evaluation is
// non-deterministic.
// *Action: Rewrite column expression to reference only pure functions.
54003, 0000, "specified data type is not supported for a virtual column"
// *Cause: Only scalar data types are supported for virtual columns. LONG,
// BLOB, REF, and BFILE data types are not supported for virtual columns.
// *Action: Specify the expression column with a supported scalar data type.
54004, 0000, "resultant data type of virtual column is not supported"
// *Cause: The data type of the underlying expression is not supported. Only
// scalar data types are supported for virtual columns. LONG,
// BLOB, REF, and BFILE data types are not supported for virtual columns.
// *Action: Specify the expression of virtual column to return a supported
// scalar data type.
54005, 0000, "keyword VIRTUAL cannot be specified here"
// *Cause: The keyword VIRTUAL was either repeated or incorrectly specified.
// *Action: Remove the keyword from the specified syntax.
54006, 0000, "keyword VISIBLE cannot be specified here"
// *Cause: The keyword VISIBLE was either repeated or incorrectly specified.
// *Action: Remove the keyword from the specified syntax.
54007, 0000, "keyword HIDDEN cannot be specified here"
// *Cause: The keyword HIDDEN was either repeated or incorrectly specified.
// *Action: Remove the keyword from the specified syntax.
54008, 0000, "expression column is not supported for an index organized table"
// *Cause: Attempt to create/alter an index organized table with an
// expression column
// *Action: These columns are not supported, change the DDL.
54009, 0000, "expression column is not supported for an external table"
// *Cause: Attempt to create/alter an external table with an expression column
// *Action: These columns are not supported, change the DDL.
54010, 0000, "expression column is not supported for a temporary table"
// *Cause: Attempt to create/alter a temporary table with an expression column
// *Action: These columns are not supported, change the DDL.
54011, 0000, "expression column is not supported for a clustered table"
// *Cause: Attempt to create/alter a clustered table with an expression column
// *Action: These columns are not supported, change the DDL.
54012, 0000, "virtual column is referenced in a column expression"
// *Cause: This virtual column was referenced in an expression of another
// virtual column
// *Action: Ensure the column expression definition for any virtual column
// does not refer to any virtual column
54013, 0000, "INSERT operation disallowed on virtual columns"
// *Cause: Attempted to insert values into a virtual column
// *Action: Re-issue the statment without providing values for a virtual column
54014, 0000, "Resulting table from a CTAS operation contains virtual column(s)"
// *Cause: Table being created by a CTAS operation contains a virtual column
// definition
// *Action: Remove the virtual column definition from the table being created
54015, 0000, "Duplicate column expression was specified"
// *Cause: Expression of the virtual column being added/created conflicts
// with an existing/previously specified functional index expression
// or virtual column expression
// *Action: Change the expression of the virtual column os there are no
// duplicate expressions
54016, 0000, "Invalid column expression was specified"
// *Cause: Virtual column expression is not a valid arithmetic expression. it
// probably refers to another column in the table
// *Action: Change the expression of the virtual column
54017, 0000, "UPDATE operation disallowed on virtual columns"
// *Cause: Attempted to update values of a virtual column
// *Action: Re-issue the statment without setting values for the
// virtual column
54018, 0000, "A virtual column exists for this expression"
// *Cause: Specified index expression matches an existing virtual column"
// *Action: Re-issue the statment by replacing the index expression with the
// matching virtual column
54019, 0000, "Virtual column expression cannot be changed because it is a partitioning column"
// *Cause: Attempted to modify the expression of a virtual column that was
// also a partitioning column.
// *Action: This is not supported.
54020, 0000, "Virtual column expression cannot be changed because it is a subpartitioning column"
// *Cause: Attempted to modify the expression of a virtual column that was
// also a subpartitioning column.
// *Action: This is not supported.
54021, 0000, "Cannot use PL/SQL expressions in partitioning or subpartitioning columns"
// *Cause: Attempted to partition a table on a virtual column that contained
// PL/SQL expressions.
// *Action: This is not supported.
54022, 0000, "Virtual column expression cannot be changed because an index is defined on column"
// *Cause: Attempted to change the expression of a virtual column that was
// indexed.
// *Action: Alter index unsable. Change expression and then rebuild index.
54023, 0000, "Virtual column expression cannot be changed because a constraint is defined on column"
// *Cause: Attempted to change the expression of a virtual column that had
// a constraint defined on it.
// *Action: Drop constraint and then change expression.
54024, 0000, "expression column is not supported for an organization cube table"
// *Cause: Attempted to create or alter an organization cube table with an
// expression column
// *Action: These columns are not supported, change the DDL.
54025, 0000, "Virtual column cannot have a default value"
// *Cause: Attempted to alter a virtual column to have a default value.
// *Action: This is not valid, change the DDL.
54026, 0000, "Real column cannot have an expression"
// *Cause: Attempted to alter a real column to have an expression.
// *Action: This is not valid, change the DDL.
54027, 0000, "cannot modify data-type of virtual column"
// *Cause: Attempted to change the data-type of virtual column without
// modifying the underlying expression
// *Action: change the underlying expression to be compatible with the
// data-type change
54028, 0000, "cannot change the HIDDEN/VISIBLE property of a virtual column"
// *Cause: Attempted to change the HIDDEN/VIRTUAL property of a virtual column
// *Action: re-issue the DDL without the virtual column property change
54029, 0000, "Virtual column cannot be updated in trigger body"
// *Cause: Attempted to change the value of virtual column in a trigger body"
// *Action: This is not valid, change the trigger definition.
54030, 0000, "datatype mismatch between virtual column and expression"
// *Cause: virtual column expression was changed after column was created"
// *Action: change the underlying expression to return datatype that conforms
// to the virtual column
54031, 0000, "column to be dropped or modified is used in a virtual column expression"
// *Cause: Attempted to drop or modify a column that was used in a virtual
// column expression.
// *Action: Drop the virtual column first or change the virtual column
// expression to eliminate dependency on the column to be dropped.
54032, 0000, "column to be renamed is used in a virtual column expression"
// *Cause: Attempted to rename a column that was used in a virtual column
// expression.
// *Action: Drop the virtual column first or change the virtual column
// expression to eliminate dependency on the column to be renamed.
54033, 0000, "column to be modified is used in a virtual column expression"
// *Cause: Attempted to modify the data type of a column that was used in a
// virtual column expression.
// *Action: Drop the virtual column first or change the virtual column
// expression to eliminate dependency on the column to be modified.
54034, 0000, "virtual columns not allowed in functional index expressions"
// *Cause: An attempt was made to create a functional index with an expression
// defined on one or more virtual columns.
// *Action: Specify the index expression using only regular columns.
54035, 0000, "keyword HIDDEN cannot be specified here"
// *Cause: Attempted to specify HIDDEN key word for a virtual column
// *Action: This is not supported.
54036, 0000, "cannot define referential constraint with ON DELETE SET NULL clause on virtual column"
// *Cause: Attempted to specify ON DELETE SET NULL clause for a referential
// integrity constraint on a virtual column.
// *Action: Reissue the statement without specifying ON DELETE SET NULL clause.
54037, 0000, "table must have at least 1 column that is not virtual"
// *Cause: An attempt was made to create a table with only virtual columns.
// *Action: Include at least 1 column that is not virtual in the table being created.
54038, 0000, "Virtual column cannot be encrypted"
// *Cause: An attempt was made to create or alter a virtual column to have
// encryption.
// *Action: Encryption is unnecessary for a virtual column as the data is not
// stored on disk.
54039, 0000, "table must have at least one column that is not invisible"
// *Cause: An attempt was made to create or alter a table to have only
// invisible columns.
// *Action: Include at least one column that is not invisible in the table
// being created or altered.
54040, 0000, "Visibility of a system-generated column cannot be changed."
// *Cause: An attempt was made to alter the visibility of a system-generated
// column.
// *Action: This is not supported.
54041, 0000, "Visibility of an abstract data type column cannot be changed."
// *Cause: An attempt was made to alter the visibility of an abstract data
// type column.
// *Action: Specify the column visibility change with a supported data type.
54042, 0000, "Invisible column is not supported on this type of table."
// *Cause: An attempt was made to create or alter the visibility of a column
// on an unsupported table type. Invisible columns are only supported
// for heap and index-organized tables (IOT).
// *Action: These columns are not supported, change the DDL.
54043, 0000, "Including column of an IOT cannot be an invisible column."
// *Cause: An attempt was made to alter the visibility of the included column
// of an index-organized table (IOT).
// *Action: This is not supported.
54044, 0000, "Visibility of a column having a column-level object privilege cannot be changed."
// *Cause: An attempt was made to alter the visibility of a column with a
// column-level object privilege.
// *Action: Revoke the column-level object privilege before making the column
// invisible.
54045, 0000, "An invisible column cannot be granted a column-level object privilege."
// *Cause: An attempt was made to grant a column-level object privilege to an
// invisible column.
// *Action: Modify the column to make it visible and then grant the
// column-level object privilege.
54046, 0000, "Column visibility modifications cannot be combined with any other modified column DDL option."
// *Cause: An attempt was made to combine the modification of the visibility
// of a column with other modified column property changes.
// *Action: Separate column visibility modifications into a standalone DDL.
54047, 0000, "virtual columns not allowed for XMLType tables with object-relational storage"
// *Cause: An attempt was made to create an object-relational XMLType table with virtual columns.
// *Action: Do not create virtual columns for XMLType tables with object-relational storage . This feature is not available.
54048, 0000, "Column expression modifications cannot be combined with any other column DDL operation."
// *Cause: An attempt was made to combine the modification of the expression
// of a column with other column operations.
// *Action: Separate column expression modifications into a standalone DDL.
54049, 0000, "expression edition column is not supported for an external table"
// *Cause: An attempt was made to create or alter an external table with
// an edition expression column.
// *Action: These columns are not supported; change the DDL.
54050, 0000, "Unsupported type or attribute on redacted column."
// *Cause: An attempt was made to alter a column with a redaction policy,
// so as to give that column an unsupported type or attribute.
// Virtual columns are not supported by data redaction.
// Columns with the INVISIBLE attribute are not supported by
// data redaction (this applies to both user-specified hidden
// columns and system-generated hidden columns).
// Vector encoded columns are not supported by data redaction.
// *Action: Specify the name of a non-redacted column, or use the DROP_POLICY
// PL/SQL procedure in the DBMS_REDACT package to remove the
// redaction policy from the column before altering it. Look in the
// REDACTION_POLICIES and REDACTION_COLUMNS catalog views for a list
// of all redaction policies and redacted columns.
54051, 0000, "System-generated virtual column cannot be a primary key."
// *Cause: An attempt was made to specify a system-generated virtual column
// * as a primary key.
// *Action: None.
54052, 0000, "System-generated functional index virtual column cannot be renamed."
// *Cause: An attempt was made to rename a system-generated functional index virtual column.
// *Action: None.
54053, 0000, "The visibility of a column from a table owned by a SYS user cannot be changed."
// *Cause: An attempt was made to alter the visibility of a column from a
// table owned by SYS user.
// *Action: Execute the DDL on a table not owned by a SYS user.
54054, 0000, "System-generated virtual column or guard column cannot be in a constraint."
// *Cause: An attempt was made to add a constraint containing the system
// generated virtual column or guard column.
// *Action: None.
54055, 0000, "In-Memory virtual column expression cannot refer to a system-generated or hidden column."
// *Cause: An attempt was made to create a virtual column expression on a system-generated or hidden column.
// *Action: Avoid creating a virtual column expression on a system-generated or hidden column.
54056, 0000, "unsupported operation on sensitive column"
// *Cause: An attempt was made to either alter the visibility of a
// sensitive column or change the sensitive column to vector encode.
// *Action: Specify the name of a non-sensitive column, or use the
// DROP_SENSITIVE_COLUMN PL/SQL procedure in the DBMS_TSDP_MANAGE
// package to remove the sensitivity of the column before
// altering it.
/////////////////////////////////////////////////////////////////////////////
// 54500 - 55499 Reserved for Oracle Spatial Data Option
/////////////////////////////////////////////////////////////////////////////
//
54500, 0000, "invalid combination of elements"
// *Cause: The geometry did not start from the correct level in
// the hierarchy.
// *Action: Correct the hierarchy in the geometry.
54501, 0000, "no holes expected"
// *Cause: The geometry contained one or more unexpected holes.
// *Action: Remove any holes in the geometry.
54502, 0000, "solid not closed"
// *Cause: The solid geometry was not closed i.e.,
// faces of solid are not 2-manifold due to incorrectly
// defined, oriented, or traversed line segment
// because each edge of a solid must
// be traversed exactly twice, once in one direction and
// once in the reverse direction.
// *Action: Correct the orientation of the edges of the neighboring polygons.
54503, 0000, "incorrect solid orientation"
// *Cause: The orientation of the solid was not correct.
// *Action: Correct the orientation or specification of the outer or inner
// solid geometry according to the geometry rules for such a solid.
54504, 0000, "multiple outer geometries"
// *Cause: The geometry contained more than one outer geometry.
// *Action: Remove all but one of the outer geometries.
54505, 0000, "ring does not lie on a plane"
// *Cause: The ring was not flat.
// *Action: Make sure all of the vertices of the ring are on the same plane.
54506, 0000, "compound curve not supported for 3-D geometries"
// *Cause: The 3-D geometry contained one or more compound curves,
// which are not supported for 3-D geometries.
// *Action: Remove all compound curves from the geometry.
54507, 0000, "duplicate points in multipoint geometry"
// *Cause: The multipoint geometry had two points that either had
// identical coordinates or were the same point considering
// the geometry tolerance.
// *Action: Make sure all points are different, considering the tolerance.
54508, 0000, "overlapping surfaces in a multisolid geometry"
// *Cause: The multisolid geometry contained one or more fully or partially
// overlapping surfaces.
// *Action: Ensure that the multisolid geometry contains no overlapping areas.
54509, 0000, "solid not attached to composite solid"
// *Cause: To connect solids in a composite solid geometry, at least one
// of the faces of a solid must be shared (fully or partially) with
// only another solid. However, at least one of the faces in this
// composite solid was not shared by exactly two solids only.
// *Action: Ensure that at least one face in a composite solid is shared by
// exactly two solids.
54510, 0000, "no outer geometry expected"
// *Cause: An outer geometry was found when only inner geometries
// were expected.
// *Action: Remove all outer geometries.
54511, 0000, "edges of inner and outer solids intersect"
// *Cause: An inner solid had a common edge with outer solid.
// *Action: Ensure that edges of inner and outer solids do not intersect.
54512, 0000, "a vertex of an inner solid is outside corresponding outer solid"
// *Cause: A solid geometry contained an inner solid with at
// least one vertex outside its corresponding outer solid.
// *Action: Ensure that all vertices of inner solids are not outside
// their corresponding outer solid.
54513, 0000, "inner solid surface overlaps outer solid surface"
// *Cause: One or more faces of an inner solid surface either fully or
// partially overlapped an outer solid surface.
// *Action: Ensure that inner and outer surfaces have no shared
// (fully or partially overlapping) faces.
54514, 0000, "overlapping areas in multipolygon"
// *Cause: A multipolygon geometry contained one or more common
// (shared, fully or partially overlapped) polygons.
// *Action: Ensure that no polygons in a multipolygon overlap.
54515, 0000, "outer rings in a composite surface intersect"
// *Cause: Outer rings, either on the same plane or different planes, in a
// composite surface intersected.
// *Action: Ensure that outer rings do not intersect. They can share edges.
54516, 0000, "adjacent outer rings of composite surface cannot be on same plane"
// *Cause: The conditional flag was set, and a composite surface had
// at least two outer rings sharing a common edge on the same plane.
// *Action: Change those outer rings into one larger outer ring.
54517, 0000, "outer ring is on the same plane and overlaps another outer ring"
// *Cause: An outer ring in a composite surface shared a common area with
// another outer ring.
// *Action: Ensure that no outer rings fully or partially overlap.
54518, 0000, "shared edge of composite surface not oriented correctly"
// *Cause: A shared edge (one shared by two polygons) in a composite surface
// was not correctly oriented. Each shared edge must be oriented
// in one direction with respect to its first polygon and then in
// the reverse direction with respect to its second polygon.
// *Action: Reverse one of the directions of the shared edge with respect to
// its polygons.
54519, 0000, "polygon (surface) not attached to composite surface"
// *Cause: Not all polygons of a surface had a
// common (fully or partially shared) edge.
// *Action: Ensure that each polygon is attached to the composite surface
// by one of its edges.
54520, 0000, "inner ring not on the same plane as its outer ring"
// *Cause: An inner ring was not on the same plane as its outer ring.
// *Action: Ensure that each inner ring is on the same plane as its outer ring.
54521, 0000, "inner ring is not inside or is touching outer ring more than once"
// *Cause: An inner ring either was not inside its outer ring
// or touched its outer ring more than once.
// *Action: Ensure that the inner ring is inside its outer ring and does
// not touch the outer ring more than once. If an inner ring
// touches its outer ring more than once, then the outer ring is no
// longer a topologically simple or singly connected polygon (ring).
54522, 0000, "inner rings of same outer ring cannot intersect or share boundary"
// *Cause: Two inner rings of the same outer ring intersected or shared a
// boundary.
// *Action: Ensure that line segments of an inner ring do not intersect or
// fully or partially coincide with line segments of another inner
// ring sharing the same outer ring.
54523, 0000, "inner rings of same outer ring cannot touch more than once"
// *Cause: Two inner rings of the same outer ring touched more than once.
// *Action: Ensure that inner rings of the same outer ring touch at no more
// than one point.
54524, 0000, "inner ring cannot be inside another inner ring of same outer ring"
// *Cause: An inner ring was inside another ring of the same outer ring.
// *Action: Ensure that no inner ring is inside another inner ring of the same
// outer ring.
54525, 0000, "incorrect box volume due to wrong ordinates"
// *Cause: The rectangular box in shortcut format did not have its first x,y,z
// coordinates either all greater or less than its second x,y,z
// coordinates.
// *Action: Make sure that the first x,y,z coordinates are either
// all greater or all less than the second x,y,z coordinates.
54526, 0000, "multi or composite geometry must be decomposed before extraction"
// *Cause: The extraction could not be performed because the multi or
// composite geometry must first be decomposed into simple geometries
// (with or without inner geometries). The multi or composite geometry
// had a gtype of GTYPE_MULTISOLID, GTYPE_MULTISURFACE,
// GTYPE_MULTICURVE, GTYPE_MULTIPOINT, or GTYPE_COLLECTION, or the
// geometry was a line string.
// *Action: Use the MULTICOMP_TOSIMPLE parameter to element extractor to
// decompose the multi or composite geometry to a simple geometry.
54527, 0000, "operation not permitted on a simple geometry"
// *Cause: A MULTICOMP_TOSIMPLE parameter to element extractor was attempted
// on a geometry that is already simple.
// *Action: Do not use the MULTICOMP_TOSIMPLE parameter to element extractor on
// simple geometries.
54528, 0000, "inner composite surfaces or surfaces with inner ring(s) expected"
// *Cause: An INNER_OUTER parameter to element extractor was attempted on a
// surface that was not simple or composite.
// *Action: Ensure that the etype of the geometry for the INNER_OUTER
// parameter to element extractor is ETYPE_SURFACE or
// ETYPE_COMPOSITESURFACE.
54529, 0000, "geometry should have multi-level hierarchy (like triangle)"
// *Cause: The geometry did not have the multi-level hierarchy required
// for this operation. For example, if the parameter to element
// extractor (hierarchy level) is not LOWER_LEVEL, but the geometry
// etype is ETYPE_SOLID and gtype is GTYPE_SOLID, an extract operation
// is not allowed, because a simple solid can only be decomposed into
// lower level geometries, such as composite surfaces.
// *Action: Ensure that the geometry has the appropriate hierarchy. For
// example, if the geometry etype is ETYPE_SOLID and gtype is
// GTYPE_SOLID, the parameter to element extractor (hierarchy level)
// should be LOWER_LEVEL.
54530, 0000, "invalid etype for element at element offset"
// *Cause: An invalid etype was encountered.
// *Action: Correct the etype of the geometry.
54531, 0000, "invalid orientation for element at element offset"
// *Cause: The orientation of the current geometry was not valid.
// *Action: Reverse the orientation of the geometry.
54532, 0000, "incomplete composite surface"
// *Cause: The end of composite surface was reached before all necessary
// surfaces were defined.
// *Action: Add more surfaces to match the geometry definition, or
// reduce the specified number of surfaces.
54533, 0000, "invalid etype in composite surface of solid"
// *Cause: The etype of the composite surface of a solid was not valid.
// *Action: Ensure that the etype is orient*1000+ETYPE_SOLID, where orient is 1
// for outer solid and 2 for inner solid.
54534, 0000, "incorrect box surface due to wrong specification"
// *Cause: The elemInfo definition was not correct for the surface of
// the axis aligned box.
// *Action: Change the interpretation to 3 in the elemInfo definition.
54535, 0000, "incorrect box surface because it is on arbitrary plane"
// *Cause: The axis aligned box surface was not
// on the yz, xz, or xy plane.
// *Action: Ensure that the first and fourth coordinates, or the second and
// fifth coordinates, or the third and sixth coordinates are the
// same. This means that the surface is on the yz, xz or xy plane,
// respectively.
54536, 0000, "axis aligned box surface not defined properly"
// *Cause: The inner geometry etype did not start with 2, or the outer
// geometry etype did not start with 1, or both occurred.
// *Action: Use the correct etype for the inner and outer geometries.
54537, 0000, "incorrect box surface due to wrong orientation"
// *Cause: The rectangular surface in shortcut format did not have its
// first x,y,z coordinates all greater than or equal to or all
// less than or equal to its second x,y,z coordinates.
// *Action: Ensure that the first x,y,z coordinates are either all
// greater than or equal to or all less than or equal to the
// second x,y,z coordinates.
54538, 0000, "unexpected gtype"
// *Cause: The gtype of the geometry was not GTYPE_SOLID, GTYPE_SURFACE,
// GTYPE_CURVE or GTYPE_POINT.
// *Action: Correct the elemInfo array to fix any
// invalid gtype and etypes that violate the geometry hierarchy.
54539, 0000, "cannot process the geometry(s) for this operation"
// *Cause: The geometry had errors in it.
// *Action: Validate the geometry or geometries to ensure that each is valid.
54540, 0000, "at least one element must be a surface or solid"
// *Cause: One of the geometries had holes, and the geometries were neither
// (A) simple, composite, or multisurfaces, or
// (B) simple, composite, or multisolids. (Surfaces and
// solids are the only geometries that can have holes.
// Points and curves cannot have holes.)
// *Action: Ensure that each geometry having holes is a surface or
// solid (simple, composite, or multi).
54545, 0000, "holes incorrectly defined"
// *Cause: The holes were defined with incorrect etype.
// *Action: Ensure that the etype is correct in the definition of
// the inner geometry.
54546, 0000, "volume of solid cannot be 0 or less"
// *Cause: The solid geometry having one outer and multiple inner geometries
// had a negative or zero volume.
// *Action: Correct the orientation or specification of the outer solid
// geometry to obey outer geometry rules so that the outer geometry
// has a positive volume. Additionally, correct the orientation or
// specification of inner solid geometries to obey inner geometry
// rules so that each inner geometry has a negative volume.
54547, 0000, "wrong input for COUNT_SHARED_EDGES"
// *Cause: The COUNT_SHARED_EDGES parameter value was not 1 or 2.
// *Action: Ensure that the COUNT_SHARED_EDGES parameter value is either 1 or
// 2.
54548, 0000, "input geometry gtype must be GTYPE_POLYGON for extrusion"
// *Cause: The input geometry gtype was not GTYPE_POLYGON.
// *Action: Ensure that the gtype of the input polygon is GTYPE_POLYGON.
54549, 0000, "input geometry has incorrect elemInfo"
// *Cause: The input 2-D polygon did not have only one outer ring.
// *Action: Ensure that the input 2-D polygon has only one outer ring.
54550, 0000, "input 2-D polygon not valid"
// *Cause: The 2-D polygon violated the rules for polygons and rings.
// *Action: Correct the polygon definition.
54551, 0000, "grdHeight and/or Height array sizes incorrect"
// *Cause: The sizes of grdHeight and Height arrays were not equal to
// half the size of input 2-D polygon's ordinates array.
// As a result, each point in the 2-D polygon could not be
// extruded from the grdHeight entry to the Height
// entry.
// *Action: Ensure that the sizes of the grdHeight and Height
// arrays are half that of input 2-D polygon ordinates
// array.
54552, 0000, "height entries must be >= to ground height entries"
// *Cause: In the definition of a solid, the height values were
// less than the ground height.
// *Action: Ensure that that height values are greater than or equal
// to ground height values.
54553, 0000, "incorrect geometry for appending"
// *Cause: The geometry could not be appended to a homogeneous collection
// (for example, multi-geometry) or to a heterogeneous geometry (for
// example, collection). In other words, the gtype of the geometry to
// be appended was neither GYTPE_COLLECTION or GTYPE_MULTI-X (where X
// is point, curve, surface, or solid).
// *Action: Ensure that the geometries involved in the append operation
// have appropriate gtypes.
54554, 0000, "arcs are not supported as defined"
// *Cause: An arc was defined in a geometry type in which arcs are not
// supported. Arcs are supported for 2-D (circle) polygons,
// 2-D compound polygons, 2-D single arc, and 2-D compound (composite)
// curves only.
// *Action: Remove or simplify the arcs.
54555, 0000, "invalid geometry dimension"
// *Cause: The geometry did not have three dimensions.
// *Action: Ensure that geometry has three dimensions.
54556, 0000, "operation is not supported for 3-D geometry"
// *Cause: A 3-D geometry was passed into an operation that supports only
// 2-D geometries.
// *Action: Check the Spatial documentation for operations that are supported
// and not supported on 3-D geometries.
54557, 0000, "incomplete composite solid"
// *Cause: The end of composite solid was reached before all necessary
// solids were defined.
// *Action: Add more solids to match the geometry definition, or
// reduce the specified number of solids.
54558, 0000, "3D SRID is not found for the corresponding 2D SRID"
// *Cause: In extruding a 2D polygon into a 3D geometry, the SRID conversion
// function did not find an equivalent 3D SRID of the 2D SRID.
// *Action: Specify a 2D SRID that has a 3D equivalent
54559, 0000, "query element and source geometry cannot be the same"
// *Cause: A query element geometry and a source geometry were the same,
// which prevented a label pointing query element in the source geometry from
// being output.
// *Action: Redefine the query element or the source geometry so that a label
// can be output.
54560, 0000, "query element cannot be a collection or multitype geometry"
// *Cause: A query element was a collection geometry or a multitype geometry.
// Such geometries are not permitted in a query element because they are at
// the top of the geometry hierarchy. A query element must be part of the
// source geometry.
// *Action: Redefine the query element or the source geometry so that a label
// can be output.
54601, 0000, "CREATE_PC: invalid parameters for creation of Point Cloud"
// *Cause: An invalid or unknown parameter was specified in the creation of
// Point Cloud.
// *Action: Check for valid set of parameters.
54602, 0000, "CREATE_PC: input points table %s does not exist"
// *Cause: The specified table for loading points into a Point Cloud did not
// exist.
// *Action: Create the points table with appropriate columns, and then
// create the Point Cloud.
54603, 0000, "CREATE_PC: specified total dimensionality cannot exceed 8"
// *Cause: The specified total dimensionality for the Point Cloud exceeded the
// maximum limit of 8.
// *Action: Create the Point Cloud with fewer dimensions. You can store
// the rest in the output points table.
54604, 0000, "CREATE_PC: input points table should not be empty"
// *Cause: The input points table had no data.
// *Action: Insert data into the input points table and then create the Point
// Cloud.
54605, 0000, "CREATE_PC: scratch-tables/views (%s) exist and need to be dropped"
// *Cause: Transient tables/views from a previous CREATE_PC operation were
// still in existence.
// *Action: Delete the invalid Point Cloud from the base table (for cleanup of
// scratch tables), and initialize and create the Point Cloud again.
// Alternately, use SDO_UTIL.DROP_WORK_TABLES with oidstring as the
// parameter.
54607, 0000, "CREATE_PC: error fetching data from input points table"
// *Cause: An internal read error occurred during Point Cloud creation.
// *Action: Contact Oracle Support Services with the error number reported.
54608, 0000, "CREATE_PC: error writing Point Cloud LOB"
// *Cause: An internal LOB write error occurred during Point Cloud creation.
// The cause might be lack of table space.
// *Action: Look for information from other errors in the stack, or contact
// Oracle Support Services with the error number reported.
54609, 0000, "CREATE_PC: input extent cannot be null"
// *Cause: The extent of the Point Cloud was null.
// *Action: Specify an extent for the Point Cloud that is not null.
54610, 0000, "CREATE_PC: input extent cannot be more than 2-D for geodetic data"
// *Cause: The extent of the Point Cloud was more than 2-D for geodetic data.
// *Action: Change the extent to 2-D (longitude, latitude).
54611, 0000, "INIT: either invalid basetable/schema or they do not exist"
// *Cause: The base table or schema, or both, were invalid strings; or the
// base table and schema combination did not exist.
// *Action: Ensure that the specified base table exists in the specified schema
// before performing the initialization operation.
54613, 0000, "INIT: internal error creating DML trigger"
// *Cause: The necessary privileges to create the trigger were not granted.
// *Action: Grant the necessary privileges to create the
// trigger. If necessary, contact Oracle Support Services for help
// with privileges for trigger creation.
54614, 0000, "INIT: block table name has to be unique"
// *Cause: The specified block table name was not unique. For example, it
// might have been used for another block table.
// *Action: Specify a different block table name.
54616, 0000, "INIT: internal error [%d, %s]"
// *Cause: An internal error occurred.
// *Action: Contact Oracle Support Services.
54617, 0000, "CLIP_PC: invalid Point Cloud; extent is empty"
// *Cause: The input Point Cloud for the CLIP_PC operation was invalid.
// *Action: Specify a point cloud that was created using the CREATE_PC
// procedure.
54618, 0000, "CLIP_PC: SRIDs of query and Point Cloud are incompatible"
// *Cause: The Point Cloud and the query geometry had incompatible SRID
// values.
// *Action: Change the query SRID to be compatible with that of the Point
// Cloud.
54619, 0000, "CLIP_PC: query and BLKID parameters cannot both be null"
// *Cause: Both the query and BLKID parameters were null in the call to the
// CLIP_PC operation.
// *Action: Either specify a query geometry that is not null, or specify a
// BLKID for use as a query.
54620, 0000, "CLIP_PC: internal error [%d, %s]"
// *Cause: An internal error occurred.
// *Action: Contact Oracle Support Services.
54621, 0000, "TO_GEOMETRY: TOTAL_DIMENSIONALITY not same as in INIT operation"
// *Cause: The specified TOTAL_DIMENSIONALITY was invalid.
// *Action: Ensure that the TOTAL_DIMENSIONALITY matches that specified in
// the call to the initialization operation.
54622, 0000, "TO_GEOMETRY: internal error [%d, %s]"
// *Cause: An internal error occurred.
// *Action: Contact Oracle Support Services.
54623, 0000, "CREATE_PC: internal error [%d, %s]"
// *Cause: An internal error occurred.
// *Action: Contact Oracle Support Services.
54640, 0000, "PARTITION_TABLE utility: invalid input parameters [%d, %s]"
// *Cause: An internal error occurred.
// *Action: Contact Oracle Support Services.
54641, 0000, "PARTITION_TABLE utility: scratch tables exist with oidstr = %s"
// *Cause: Scratch tables/views could not be created because they already
// existed.
// *Action: Use SDO_UTIL.DROP_WORK_TABLES with the specified oidstr parameter
// to clean up the scratch tables.
54642, 0000, "PARTITION_TABLE utility: invalid SORT_DIMENSION specified"
// *Cause: An invalid string was specified for the SORT_DIMENSION.
// *Action: Specify the SORT_DIMENSION as 'BEST_DIM', 'DIMENSION_1',
// 'DIMENSION_2', or 'DIMENSION_3'.
54643, 0000, "PARTITION_TABLE utility: invalid WORKTABLESPACE parameter"
// *Cause: An invalid string was specified for the WORKTABLESPACE parameter.
// *Action: Specify an existing valid tablespace for WORKTABLESPACE (to hold
// the scratch tables).
54644, 0000, "PARTITION_TABLE utility: error in reading input, output tables"
// *Cause: The names for the input/output tables were invalid, or the
// tables did not exist or did not have the right structure.
// *Action: Check the Spatial documentation for PARTITION_TABLE.
54651, 0000, "CREATE_TIN: invalid parameters specified in creation of TIN"
// *Cause: An invalid or unknown parameter was specified in the creation of
// the TIN.
// *Action: Check the Spatial documentation for CREATE_TIN.
54652, 0000, "CREATE_TIN: input points table %s does not exist"
// *Cause: The specified table for loading points into a TIN did not
// exist.
// *Action: Create the points table with appropriate columns, and then
// create the TIN.
54653, 0000, "CREATE_TIN: specified total dimensionality cannot exceed 8"
// *Cause: The specified total dimensionality for the TIN exceeded the
// maximum limit of 8.
// *Action: Create the TIN with fewer dimensions. You can store
// the rest in the output points table.
54654, 0000, "CREATE_TIN: input points table should not be empty"
// *Cause: The input points table had no data.
// *Action: Insert data into the input points table, and then create the TIN.
54655, 0000, "CREATE_TIN: scratch tables/views(%s) exist and need to be dropped"
// *Cause: Transient tables from previous CREATE_TIN operation still existed.
// *Action: Delete the invalid TIN from the base table (for cleanup of
// scratch tables), and initialize and create the TIN again.
// Alternately, use SDO_UTIL.DROP_WORK_TABLES with oidstring as its
// parameter.
54656, 0000, "CREATE_TIN: error fetching data from input points table"
// *Cause: An internal read error occurred during TIN creation.
// *Action: Contact Oracle Support Services with the error number reported.
54657, 0000, "CREATE_TIN: error writing TIN LOB"
// *Cause: An internal LOB write error occurred during TIN creation.
// The cause might be lack of table space.
// *Action: Look for information from other errors in the stack, or contact
// Oracle Support Services with the error number reported.
54658, 0000, "CREATE_TIN: input extent cannot be null"
// *Cause: The extent of the TIN was null.
// *Action: Specify an extent for the TIN that is not null.
54659, 0000, "CREATE_TIN: input extent has to be 2-D for geodetic data"
// *Cause: The extent of the TIN was more than 2-D for geodetic data.
// *Action: Change the extent to 2-D (longitude, latitude).
54660, 0000, "CLIP_TIN: invalid Point Cloud; extent is empty"
// *Cause: The input TIN for the CLIP_TIN operation was invalid.
// *Action: Specify a TIN that was created using the CREATE_TIN operation.
54661, 0000, "CLIP_TIN: SRIDs of query and TIN are incompatible"
// *Cause: The TIN and the query geometry had incompatible SRID values.
// *Action: Change the query geometry SRID to be compatible with that of TIN.
54662, 0000, "CLIP_TIN: query and blkid parameters cannot both be null"
// *Cause: Both the query and blkid parameters were null in the call to the
// CLIP_TIN operation.
// *Action: Either specify a query geometry that is not null, or specify a
// blkid for use as a query.
54663, 0000, "CLIP_TIN: internal error [%d, %s]"
// *Cause: An internal error occurred.
// *Action: Contact Oracle Support Services.
54664, 0000, "TO_GEOMETRY: internal error [%d, %s]"
// *Cause: An internal error occurred.
// *Action: Contact Oracle Support Services.
54665, 0000, "CREATE_TIN: internal error [%d, %s]"
// *Cause: An internal error occurred.
// *Action: Contact Oracle Support Services.
54666, 0000, "query gtype is a superset of the source geometry"
// *Cause: A query element geometry was at a higher level in the geometry hierarchy
// than the source geometry.
// *Action: Try replacing the source geometry with the query geometry.
54667, 0000, "query element cannot be matched to an element in source geometry (%s)"
// *Cause: A query element geometry was not a part of the source geometry.
// *Action: Redefine the query element or the source geometry.
54668, 0000, "a 2D SRID cannot be used with a 3D geometry"
// *Cause: A 2D SRID was used with a 3D geometry.
// *Action: Replace the 2D SRID with an appropriate 3D SRID.
54669, 0000, "Event to turn off query rewrite for spatial partition pruning"
// *Document: NO
// *Cause: For internal use only.
// *Action: Turns off query rewrite for spatial partition pruning. Set this
// event only under the supervision of Oracle Support Services or development.
54670, 0000, "Event to set the number of leaf nodes used in memory-resident R-tree processing"
// *Document: NO
// *Cause: For internal use only.
// *Action: Set the number of leaf nodes used in memory-resident R-tree
// processing. Set this event only under the supervision of Oracle Support
// Services or development.
54671, 0000, "Event to turn off optimized R-tree bulk inserts"
// *Document: NO
// *Cause: For internal use only.
// *Action: Turn off optimized R-tree bulk inserts. Set this event only under
// the supervision of Oracle Support Services or development.
54672, 0000, "Event to turn off R-tree node caching in bulk updates"
// *Document: NO
// *Cause: For internal use only.
// *Action: Turn off R-tree node cache caching in bulk updates. Set this
// event only under the supervision of Oracle Support Services or development.
54673, 0000, "Event to set the number of cached R-tree nodes in bulk updates"
// *Document: NO
// *Cause: For internal use only.
// *Action: Set the number of cached R-tree nodes in bulk updates. Set this
// event only under the supervision of Oracle Support Services or development.
54674, 0000, "Event to dump the R-tree node cache contents to trace file"
// *Document: NO
// *Cause: For internal use only.
// *Action: Dump the R-tree node cache contents to trace file. Set this event
// only under the supervision of Oracle Support Services or development.
54675, 0000, "Event to enable diagnostic and informational messages to trace file"
// *Document: NO
// *Cause: For internal use only.
// *Action: Enable or disable diagnostic and informational messages to trace
// file. Set this event only under the supervision of Oracle Support Services
// or development.
54676, 0000, "Event to enable direct-row-access performance enhancement"
// *Document: NO
// *Cause: For internal use only.
// *Action: Enable or disable direct-row-access performance enhancement.
// Set this event only under the supervision of Oracle Support Services
// or development.
54677, 0000, "Event to enable faster geometry operations"
// *Document: NO
// *Cause: For internal use only.
// *Action: Enable or disable faster geometry operations. Set this event
// only under the supervision of Oracle Support Services or development.
54678, 0000, "Event to enable within_distance optimization"
// *Document: NO
// *Cause: For internal use only.
// *Action: Enable or disable 'within_distance' optimization. Set this event
// only under the supervision of Oracle Support Services or development.
54679, 0000, "Event to specify an alternate statistics collection algorithm"
// *Document: NO
// *Cause: For internal use only.
// *Action: Specify an alternate statistics collection algorithm.
// Set this event only under the supervision of Oracle Support Services
// or development.
54680, 0000, "Event to specify the maximum number of points used for polygon orientation checking"
// *Document: NO
// *Cause: For internal use only.
// *Action: Specify the maximum number of points used for polygon orientation
// checking. Set this event only under the supervision of Oracle Support
// Services or development.
54681, 0000, "Event to specify the maximum number of buckets to be used for statistics collection"
// *Document: NO
// *Cause: For internal use only.
// *Action: Specify the maximum number of buckets to be used for statistics
// collection other than the standard 512 buckets. Set this event only under
// the supervision of Oracle Support Services or development.
54682, 0000, "Event to force direct-row-access usage"
// *Document: NO
// *Cause: For internal use only.
// *Action: Enable or disable direct-row-access forced usage.
// Set this event only under the supervision of Oracle Support Services
// or development.
54683, 0000, "Event to specify the number of successful operations after which a simulated error will occur"
// *Document: NO
// *Cause: For internal use only.
// *Action: Specify the number of successful operations after which a
// simulated error will occur. Set this event only under the supervision of
// Oracle Support Services or development.
/////////////////////////////////////////////////////////////////////////////
// 55150 - 55199 Reserved for Spatial Web Services Exceptions
/////////////////////////////////////////////////////////////////////////////
55150, 00000, "Spatial Web Services operation failed: %s"
// *Cause: There was an error in the Spatial Web Services operation or the parameters.
// *Action: Check the error message and take the appropriate action or contact
// Oracle Support Services.
55151, 00000, "WCS is not enabled."
// *Cause: Web Coverage Service (WCS) metadata tables were not found.
// *Action: Ensure that WCS is enabled in the proper schema.
55152, 00000, "WCS temporary tables do not exist."
// *Cause: The Web Coverage Service (WCS) operation required temporary tables, but these tables did not exist.
// *Action: Ensure that the WCS temporary tables exist in the schema of the coverage, and that
// the WCS schema has privileges to create, update, and delete rows in the WCS
// temporary tables.
55153, 00000, "WCS publish coverage failed: %s"
// *Cause: Web Coverage Service (WCS) parameter values were invalid, the user had insufficient privileges,
// or the coverage was already published.
// *Action: Ensure that all parameter values are not null, the WCS schema has privileges to access
// the coverage, and the coverage is not already published. The schema of the coverage must grant
// access privileges to the WCS schema.
55154, 00000, "Request to grant or revoke privileges failed: %s"
// *Cause: Parameters were invalid or privileges were insufficient.
// *Action: Check the error message to ensure that the parameters are valid and the user
// has sufficient privileges.
55160, 00000, "MDSYS.SDO_XSD_TABLE does not exist or the specified XSD ID is incorrect."
// *Cause: The XML schema could not be found.
// *Action: Ensure that Oracle Spatial is installed properly, and check
// the XSD_ID column of the SDO_XSD_TABLE table and the USER_SDO_CSW_SERVICE_INFO view.
55161, 00000, "CSW user table: %s"
// *Cause: Either the Catalog Services for the Web (CSW) user table, the SRID parameter, the metadata ID,
// or the XML schema definition (XSD) type was incorrect.
// *Action: Check the error message and take the appropriate action on the CSW user table name, SRID, metadata ID, XSD, or XML column.
55162, 00000, "The XQFT index cannot be dropped or created for the CSW user table."
// *Cause: The XQuery Full Text (XQFT) index could not be dropped or created for the Catalog Services for the Web (CSW) user table.
// *Action: Ensure that the user table is ready for dropping or building an XQFT index.
55163, 00000, "CSW server-side error: %s"
// *Cause: A Catalog Services for the Web (CSW) server-side error occurred.
// *Action: Ensure that the CSW metadata is correct and the CSW user table is properly defined.
55164, 00000, "CSW client-side error: %s"
// *Cause: A Catalog Services for the Web (CSW) client-side error occurred.
// *Action: Ensure that the CSW record types are properly published, and that the sdows.ear file and
// WebLogic Server (WLS) are properly configured.
////////////////////////////////////////////////////
// 55200 - 55300 Reserved for MGD RFID Exceptions
////////////////////////////////////////////////////
55200, 0000, "Java exception from tag data translation java stack"
// *Cause: Java exceptions.
// *Action: Turn on java output by calling dbms_java.set_output(OUTPUT_SIZE); Set java logging level by calling MGD_ID_UTL.setJavaLoggingLevel('INFO'); Analyze java logging messages.
55201, 0000, "Tag data translation category not found"
// *Cause: No matching category ID could be found.
// *Action: Make sure the input category name, category version or category ID is correct.
55202, 0000, "Tag data translation scheme not found"
// *Cause: No matching scheme could be found for the input data format.
// *Action: Make sure the input data format is supported and correct.
55203, 0000, "Tag data translation level not found"
// *Cause: No matching level could be found for the input data format.
// *Action: Make sure the input data format is supported and correct.
55204, 0000, "Tag data translation option not found"
// *Cause: No matching option could be found for the input data format.
// *Action: Make sure the input data format is supported and correct.
55205, 0000, "Tag data translation field validation failed"
// *Cause: Invalid field value.
// *Action: Make sure the field value of the input data is within the range specified in the tag data translation XML.
55206, 0000, "Tag data translation field not found"
// *Cause: Invalid input field.
// *Action: Make sure the spellings of the input fields are correct.
55207, 0000, "Tag data translation rule evaluation failure"
// *Cause: Error occurred when idcode translator tried to evaluate the rule specified in the tag data translation XML.
// *Action: Java proxy must be set in order to evaluate manager look up rules. Call MGD_ID_UTL.setProxy(PROXY_HOST, PROXY_PORT) to enable java proxy.
55208, 0000, "Too many matching levels were found for the input data"
// *Cause: Necessary field values were missing.
// *Action: Add additional field value pairs that are necessary to determine a unique matching level.
////////////////////////////////////////////////////////////////
// 55300 - 55499 Reserved for Semantics/RDF errors //
////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////
// 55300 - 55379 Reserved for Semantic data load and other DML//
// exceptions //
////////////////////////////////////////////////////////////////
55300, 0000, "model %s does not exist"
// *Cause: The specified model could not be found.
// *Action: Make sure that the model has been created.
55301, 0000, "rulebase %s does not exist"
// *Cause: The specified rulebase could not be found.
// *Action: Make sure that the rulebase has been created.
55302, 0000, "insufficient privileges %s"
// *Cause: Sufficient privileges were not granted.
// *Action: Ask the database administrator to grant the appropriate privileges.
55303, 0000, "SDO_RDF_TRIPLE_S constructor failed: %s"
// *Cause: SDO_RDF_TRIPLE_S constructor failed.
// *Action: Check the stack trace for additional information.
55304, 0000, "specified reuse-bNode model-id %s != target model-id %s"
// *Cause: The reuse-bNode model-id specified for the SDO_RDF_TRIPLE_S
// constructor was neither 0 nor the model-id of the target model.
// *Action: Make sure that the reuse-bNode model is either 0 or the
// model-id of the target model.
55305, 0000, "reification constructor functions not supported"
// *Cause: Unsupported reification constructor functions were used.
// *Action: Insert each triple in the reification quad individually.
// See documentation for more information.
55306, 0000, "internal error: invalid %s: value_name=%s value_type=%s"
// *Cause: The value type of this component of the RDF triple was invalid.
// *Action: This is an internal error. Contact Oracle Support Services.
55307, 0000, "invalid value type for lexical value: %s"
// *Cause: The value type of this lexical value was invalid.
// *Action: Make sure that the lexical value format is correct.
// If this error occurs during bulk load from a staging table, then
// this may be an internal error. Contact Oracle Support Services.
55308, 0000, "invalid time zone %s for lexical value %s"
// *Cause: The time zone of this lexical value was invalid.
// *Action: Make sure that the lexical value format is correct.
// If this error occurs during bulk load from a staging table then
// this may be an internal error. Contact Oracle Support Services.
55309, 0000, "hash collision resolution failed for lexical value %s"
// *Cause: Attempts to resolve hash collision exceeded the maximum retry count.
// *Action: This may be an internal error. Contact Oracle Support Services.
55310, 0000, "parse failed for the %s lexical value: %s"
// *Cause: Attempts to insert the specified lexical value failed.
// *Action: This may be an internal error. Contact Oracle Support Services.
55311, 0000, "invalid value type %s for long lexical value %s"
// *Cause: The value type of this long (length > 4000) lexical value was invalid.
// *Action: Make sure that the long value has a valid value type.
55312, 0000, "parse failed for triple: id-form: %s %s %s"
// *Cause: Attempts to insert triple failed.
// *Action: This may be an internal error. Contact Oracle Support Services.
55313, 0000, "SDO_RDF_TRIPLE_S constructor failed to process triple containing bNode"
// *Cause: The SDO_RDF_TRIPLE_S constructor without bNode reuse option
// was invalid for triple containing bNode.
// *Action: Use SDO_RDF_TRIPLE_S constructor that allows bNode reuse.
55314, 0000, "invalid temporary table name (%s) for use with batch load"
// *Cause: Specified temporary table name was not valid.
// *Action: See documentation for rules for temporary table name validity.
55315, 0000, "batch load attempt failed: %s"
// *Cause: The batch load operation failed.
// *Action: This may be an internal error. Contact Oracle Support Services.
55316, 0000, "model %s does not match model %s for table and column"
// *Cause: This column of the table was not associated with the specified model.
// *Action: Make sure to use the correct target model.
55317, 0000, "model %s already exists"
// *Cause: A model with the specified name was already present.
// *Action: Choose a different model name, or delete the existing model
// and create a new model with the specified name.
55318, 0000, "column %s in table %s already contains data"
// *Cause: At model creation time, the table column contained data.
// *Action: Ensure that the table column does not contain data before model creation.
55319, 0000, "model %s create attempt failed: %s"
// *Cause: The attempt to create the specified model did not succeed.
// *Action: This may be an internal error. Contact Oracle Support Services.
55320, 0000, "model %s drop attempt failed: %s"
// *Cause: The attempt to drop the specified model did not succeed.
// *Action: This may be an internal error. Contact Oracle Support Services.
55321, 0000, "network already exists"
// *Cause: Attempt to create the network failed because
// the network already existed.
// *Action: If necessary, drop the network
// before trying to recreate the network.
55322, 0000, "model(s) exist"
// *Cause: An attempt was made to drop a network that contained
// one or more models.
// *Action: Drop all the model(s) and then retry the operation.
55323, 0000, "rulebase(s) exist"
// *Cause: An attempt was made to drop a network that contained one or
// more rulebases.
// *Action: Drop all the rulebase(s) and then retry the operation.
55324, 0000, "no rulebases specified"
// *Cause: Rulebases for the operation were not specified.
// *Action: Specify at least one rulebase.
55325, 0000, "rulebase or rules index %s already exists %s"
// *Cause: A rulebase or rules index with the specified name already existed.
// *Action: Choose a different name, or
// delete the existing rulebase or rules index.
55326, 0000, "rules index (%s) create attempt failed: %s"
// *Cause: The attempt to create the specified rules index did not succeed.
// *Action: This may be an internal error. Contact Oracle Support Services.
55327, 0000, "rule %s yields a triple with a literal subject or predicate"
// *Cause: The specified rule created an invalid triple containing a literal in
// the subject or predicate position.
// *Action: Check and modify the rule to avoid creation of invalid triple.
55328, 0000, "literal value %s insert attempt failed"
// *Cause: The attempt to create the specified literal value failed.
// *Action: This may be an internal error. Contact Oracle Support Services.
55329, 0000, "same model %s specified more than once in the list of models"
// *Cause: The specified model occurred more than once in the list of models.
// *Action: Eliminate duplicate occurrences of the model in the list of models.
55330, 0000, "rulebase or rules index %s is busy"
// *Cause: The specified rulebase or rules index was busy and could not be used.
// *Action: Retry your operation later.
55331, 0000, "user owns RDF objects"
// *Cause: The user could not be dropped because it owns RDF objects.
// *Action: Drop the RDF objects and then retry.
55332, 0000, "virtual model cannot be used in this context"
// *Cause: A virtual model was used as input instead of a model.
// *Action: Use a model as input.
55333, 0000, "virtual model %s does not exist"
// *Cause: The specified virtual model could not be found.
// *Action: Make sure that the virtual model has been created.
55334, 0000, "virtual model name %s is invalid"
// *Cause: The specified virtual model name was not valid.
// *Action: Check Oracle documentation for valid virtual model names.
55335, 0000, "at least one model must be specified"
// *Cause: An empty list of models was specified as the set of models
// for a virtual model.
// *Action: Make sure at least one model appears in the set of models
// used to create a virtual model.
55336, 0000, "insufficient privileges for using one or more of the models and rules indexes"
// *Cause: An attempt was made to create a virtual model
// without the appropriate privileges.
// *Action: Ask the database administrator to perform the operation or
// to grant the required privileges.
55337, 0000, "a virtual model or rules index with the name %s already exists"
// *Cause: A virtual model or rules index with the specified name
// was already present.
// *Action: Choose a different virtual model name.
55338, 0000, "a model with the name %s already exists"
// *Cause: A model with the specified name was already present.
// *Action: Choose a different virtual model name.
55339, 0000, "a virtual model already exists for the specified model-rulebase combination"
// *Cause: A virtual model with identical components was already present.
// *Action: Choose a different set of components for the new virtual model.
55340, 0000, "rules index does not exist for the specified model-rulebase combination"
// *Cause: A rules index did not exist for the specified sets of
// models and rulebases.
// *Action: Make sure a rules index is created for the specified sets of
// models and rulebases.
55341, 00000, "label index out-of-range"
// *Cause: An attempt was made to use an out-of-range index
// for retrieving the label.
// *Action: Correct the input and try again.
55342, 00000,"not a defined label in the policy"
// *Cause: An attempt was made to use an undefined label.
// *Action: Correct the input and try again.
55343, 00000,"invalid dependent component for custom label generator"
// *Cause: An attempt was made to specify an invalid dependent
// component for the label generator.
// *Action: Correct the input and try again.
55344, 00000,"invalid label generator implementation or use"
// *Cause: An attempt was made to use an invalid label generator
// to generate labels for inferred data.
// *Action: Correct the input and try again.
55345, 00000,"invalid use of label generator with no OLS policy"
// *Cause: An attempt was made to use a label generator when
// Oracle Label Security (OLS) was not enabled for
// Resource Definition Framework (RDF) data.
// *Action: None.
55346, 00000,"invalid label generation option with user rules"
// *Cause: An attempt was made to specify an invalid label generation
// option for entailment involving user rules.
// *Action: Correct the input and try again.
55347, 00000,"missing proof for the specified label generation option"
// *Cause: The chosen label generation option required proof, which
// was missing for the entailment.
// *Action: Correct the input and try again.
55348, 00000,"label generator error: RDF data not enabled for %s "
// *Cause: An invalid label generator option was chosen for
// entailment.
// *Action: Correct the input and try again.
55349, 00000,"OLS not installed or in an invalid state"
// *Cause: Oracle Label Security (OLS) support for Resource
// Definition Framework (RDF) was not installed.
// *Action: Consult Oracle documentation to install the Oracle Label
// Security (OLS) support.
55350, 00000,"RDF-OLS table option %s not supported"
// *Cause: An attempt was made to use an unsupported Oracle Label
// Security (OLS) option for Resource Definition Framework
// (RDF) data.
// *Action: Correct the input and try again.
55351, 00000,"RDF secure access option not supported or is invalid"
// *Cause: An attempt was made to use an unsupported secure access
// option for Resource Definition Framework (RDF).
// *Action: Correct the input and try again.
55352, 00000,"insufficient privileges for policy administration"
// *Cause: The necessary privileges needed to administer
// Oracle Label Security (OLS) or Oracle Virtual Private
// Database (VPD) policies for Resource Definition Framework
// (RDF) data were not specified.
// *Action: None.
55353, 00000,"invalid column name for label column %s "
// *Cause: An attempt was made to use an invalid column to maintain
// labels for Resource Definition Framework (RDF) data.
// *Action: Use CTXT2 as the label column.
55354, 00000,"Policy %s does not exist or is inaccessible"
// *Cause: An attempt was made to use a nonexistent policy.
// *Action: Correct the input and try again.
55355, 00000,"RDF network does not exist"
// *Cause: An attempt was made to perform an operation that
// required Resource Definition Framework (RDF) network to
// be present.
// *Action: Create the Resource Definition Framework (RDF) network.
55356, 00000,"OLS not enabled for RDF data"
// *Cause: An attempt was made to perform an RDF-OLS-specific
// operation when Oracle Label Security (OLS) was not
// enabled for Resource Definition Framework (RDF) data.
// *Action: None.
55357, 00000,"insufficient privileges for the current operation"
// *Cause: An attempt was made to perform a Resource Definition
// Framework (RDF) secure access
// operation with restricted privileges.
// *Action: See Oracle documentation.
55358, 00000,"model \"%s\" is not empty"
// *Cause: An attempt was made to reset Oracle Label Security (OLS)
// labels for a model with some data.
// *Action: None.
55359, 00000,"unauthorized operation with policy %s - %s"
// *Cause: An attempt was made to perform an unauthorized
// DML operation on OLS-enabled Resource Definition Framework
// (RDF) repository.
// *Action: None.
55360, 00000,"invalid value for resource position - %s "
// *Cause: An invalid value was specified for the resource
// position while setting labels.
// *Action: Correct the input and try again.
55361, 00000,"duplicate specification for the namespace found"
// *Cause: An attempt was made to use a namespace map that contained
// one or more duplicate specifications.
// *Action: Correct the input and try again.
55362, 00000,"RDF VPD policy may not be created in the SYS schema"
// *Cause: An attempt was made to create an Oracle Virtual Private
// Database (VPD) policy in the SYS schema.
// *Action: None.
55363, 00000,"context %s does not exist"
// *Cause: An attempt was made to specify a nonexistent context for
// the Oracle Virtual Private Database (VPD) policy.
// *Action: Create the context using CREATE CONTEXT command.
55364, 00000,"invalid operation type %s for VPD policy"
// *Cause: An attempt was made to specify an invalid operation
// for the application of Oracle Virtual Private Database
// (VPD) policy.
// *Action: Specify ALL, QUERY, or DML for operation type.
55365, 00000,"invalid metadata for VPD policy"
// *Cause: An attempt was made to define invalid metadata elements
// for the Oracle Virtual Private Database (VPD) policy.
// *Action: See Oracle documentation for valid set of metadata
// elements.
55366, 00000,"unknown namespace prefix \"%s\""
// *Cause: An attempt was made to make use of an undefined namespace
// prefix in Oracle Virtual Private Database (VPD) metadata.
// *Action: Correct the input and try again.
55367, 00000,"invalid maintenance operation for VPD metadata"
// *Cause: An attempt was made to perform an invalid maintenance
// operation on Oracle Virtual Private Database (VPD)
// metadata.
// *Action: Specify ADD or DELETE for VPD metadata maintenance.
55368, 00000,"empty match or apply pattern not allowed in a VPD constraint"
// *Cause: An attempt was made to specify an empty match or apply
// pattern for a Oracle Virtual Private Database (VPD)
// constraint.
// *Action: Correct the input and try again.
55369, 00000,"invalid identifier specified for the constraint group"
// *Cause: An invalid SQL identifier was specified for the
// constraint group.
// *Action: Correct the input and try again.
////////////////////////////////////////////////////////////////
// 55370 - 55429 Reserved for create_entailment errors //
////////////////////////////////////////////////////////////////
55370, 0000, "input parameter not a zero or positive integer"
// *Cause: The input parameter was not zero or a positive integer.
// *Action: Change the input parameter to zero or a positive integer.
55371, 0000, "RDF rules index '%s' exists for different model-rulebase combination"
// *Cause: A rules index with the specified name has already been
// built for a different model-rulebase combination.
// *Action: Specify a different rules index name, or drop the existing
// rules index and then create a new rules index with that name.
55372, 0000, "entailment (rules index) '%s' already exists"
// *Cause: The entailed graph (rules index) already exists.
// *Action: Specify a different rules index name, or drop the existing
// rules index and then create a new rules index with that name.
55373, 0000, "inference internal error: %s"
// *Cause: An unexpected internal error condition occurred.
// *Action: Check the error message and the stack trace.
55374, 0000, "query constants not in the database; no rows selected"
// *Cause: URIs or literals used in the query did not exist in the database.
// *Action: Check the query, and ensure that the URIs or literals do exist.
55375, 0000, "cannot drop table '%s' because this table owns RDF objects"
// *Cause: A table containing RDF data could not be dropped without first
// dropping its RDF model.
// *Action: Drop the corresponding RDF model or models, and then drop the table.
55376, 0000, "cannot alter or drop column '%s' because this column owns RDF objects"
// *Cause: A table column containing RDF data could not be altered or
// dropped without first dropping its RDF model.
// *Action: Drop the corresponding RDF model or models, and then alter or
// drop the column.
55377, 0000, "number of triples less than 1 or null error indication marker"
// *Cause: An internal error occurred during validation. The number of
// triples was less than 1 or the error indication marker was null.
// *Action: Check the input parameters, and ensure that the number of triples
// is 1 or greater and that the error indication marker is not null;
// or contact Oracle Support Services.
55378, 0000, "invalid error code"
// *Cause: An invalid error code was passed in during validation.
// *Action: Specify a valid error code.
55379, 0000, "too many triples"
// *Cause: An internal error occurred during validation. Too many triples were
// passed in.
// *Action: Specify a valid number of triples for the operation,
// or contact Oracle Support Services.
////////////////////////////////////////////////////////////////
// 55430 - 55449 Reserved for SEM_MATCH errors //
////////////////////////////////////////////////////////////////
55430, 0000, "query pattern is null"
// *Cause: The query pattern specified in the SEM_MATCH query was null.
// *Action: Modify the query pattern to be non-null.
55441, 0000, "insufficient privileges to drop virtual model %s"
// Cause: An attempt was made to drop a virtual model without
// the appropriate privileges.
// Action: Ask the database administrator to perform the operation or
// grant the required privileges.
55442, 0000, "a virtual model cannot be used with other models in a SEM_MATCH query"
// Cause: The set of models used as input to a SEM_MATCH query contained
// a virtual model.
// Action: Create a new virtual model with contents that are equivalent to
// the specified SEM_MATCH model set and query the new virtual model.
55443, 0000, "a virtual model cannot be used with a rulebase in a SEM_MATCH query"
// Cause: A rulebase was specified in conjunction with a virtual model
// as input to a SEM_MATCH query.
// Action: Create a new virtual model that expands the specified virtual model
// to include the specified rulebase and query the new virtual model.
////////////////////////////////////////////////////////////////
// 55450 - 55499 Reserved for Semantic Operator exceptions //
////////////////////////////////////////////////////////////////
55450, 00000,"continually refreshed workspaces not supported with RDF"
// *Cause: An attempt was made to use continually refreshed
// workspaces with Resource Definition Framework (RDF) data.
// *Action: None.
55451, 00000,"multi-parent workspaces not supported with RDF"
// *Cause: An attempt was made to use multi-parent workspaces
// with Resource Definition Framework (RDF) data.
// *Action: None.
55452, 00000,"batch mode not allowed with version-enabled models"
// *Cause: An attempt was made to batch load data into a version-
// enabled Resource Definition Framework (RDF) model. This is
// not supported.
// *Action: None.
55453, 00000,"OLS/VPD-enabled indexes must be created with CREATE_ENTAILMENT API"
// *Cause: An attempt was made to create entailment for
// OLS/VPD-enabled models using unsupported API.
// *Action: Correct the input and try again.
55454, 00000,"version-enabled indexes must be created with CREATE_ENTAILMENT API"
// *Cause: An attempt was made to create entailment for version-
// enabled models using unsupported API.
// *Action: Correct the input and try again.
55455, 0000, "rules index status not recognized ( %s )"
// *Cause: The specified rules index status was not recognized.
// *Action: Ensure that the rules index status is VALID, INCOMPLETE,
// or INVALID, and retry the operation.
55456, 0000, "no valid rules index for this model-rulebase combination"
// *Cause: A valid rules index did not exist for specified combination
// of models and rulebases.
// *Action: Create a rules index for the specified models and rulebases
// combination, or use a combination of models and rulebases for
// which a rules index exists, and retry the operation. Also ensure
// that the rules index status matches the status for the rules index
// specified in the query.
55457, 0000, "predicate not found in model"
// *Cause: The predicate value passed in as an argument to the semantic
// operator did not exist in the model.
// *Action: In the query using semantic operators, use a predicate value
// that exists in the model and retry the operation.
55458, 0000, "object not found in model"
// *Cause: The object value passed in as an argument to the semantic operator
// did not exist in the model.
// *Action: In the query using semantic operators, use an object value that
// exists in the model and retry the operation.
55459, 0000, "invalid parameter string"
// *Cause: The parameter string used in the creation of an index of type
// SEM_INDEXTYPE had invalid or malformed parameters.
// *Action: See the documentation for information on how to write a valid
// parameter string.
55460, 0000, "incorrect usage of semantic operators"
// *Cause: There was a syntax error in the call to the SEM_RELATED operator
// *Action: See the documentation for information on how to use the
// SEM_RELATED operator. Check that the value returned by
// SEM_RELATED is compared to 1 or 0.
55461, 0000, "no distance information available"
// *Cause: Distance information was not generated during rules index creation.
// *Action: Retry query without the SEM_DISTANCE operator and/or without
// specifying bounds in the SEM_RELATED operator. See the
// documentation for information on when distance information
// is generated.
55462, 0000, "internal error"
// *Cause: An internal error occurred during a semantic operator query
// or during the creation of an index of type SEM_INDEXTYPE.
// *Action: Contact Oracle Support Services.
55463, 00000,"missing privileges for MDSYS schema for OLS-enabled entailment"
// *Cause: An attempt was made to run entailment with insufficient
// privileges for MDSYS schema.
// *Action: Grant EXEMPT ACCESS POLICY to MDSYS.
55464, 00000,"model \"%s\" does not exist"
// *Cause: An attempt was made to use a nonexistent Resource
// Definition Framework (RDF) model.
// *Action: Correct the input and try again.
55465, 00000,"resource position %s not secured with OLS policy"
// *Cause: An attempt was made to associate labels with resource
// positions that were not secured with Oracle Label
// Security (OLS).
// *Action: Correct the input and try again.
55466, 00000,"one or more triples have incompatible sensitivity label"
// *Cause: An attempt was made to reset a label for a resource
// that participated in triples with incompatible label.
// *Action: Correct the input and try again.
55467, 00000,"model-specific label for the resource is incompatible"
// *Cause: An attempt was made to set a global label for a resource
// when an incompatible model-specific label already existed.
// *Action: Correct the input and try again.
55468, 00000,"rule base \"%s\" does not exist or is not accessible"
// *Cause: An attempt was made to specify a rule base that
// did not exist.
// *Action: Correct the input and try again.
55469, 00000,"rule \"%s\" does not exist or is not accessible"
// *Cause: An attempt was made to set a label for a rule that did
// not exist.
// *Action: Correct the input and try again.
55470, 00000,"OLS may not be applied with one or more models VPD-enabled"
// *Cause: An attempt was made to OLS-enable Resource Definition
// Framework (RDF) repository when one or more models is
// VPD-enabled.
// *Action: Oracle Label Security (OLS) and Oracle Virtual Private
// Database (VPD) may not be used simultaneously.
55471, 00000,"OLS may not be applied to version-enabled RDF repository"
// *Cause: An attempt was made to OLS-enable Resource Definition
// Framework (RDF) repository when one or more models is
// version-enabled.
// *Action: Oracle Label Security (OLS) may not be enabled when one
// or more models is version-enabled.
55472, 00000,"Secure access policy already assigned to RDF data"
// *Cause: An attempt was made to assign an Oracle Label Security
// (OLS) policy to Resource Definition Framework (RDF) data
// when some other policy was already in effect.
// *Action: None.
55473, 00000,"RDF model participating in a virtual model may not be version-enabled"
// *Cause: An attempt was made to version-enable a Resource
// Definition Framework (RDF) model which participated in a
// virtual model.
// *Action: None.
55474, 00000,"internal error: [%s],[%s],[%s]"
// *Cause: There was an internal error with Resource Definition
// Framework (RDF) OLS/VPS support.
// *Action: Contact Oracle Support Services.
55475, 00000,"policy with a matching name already exists"
// *Cause: An attempt was made to specify a duplicate Oracle Virtual
// Private Database (VPD) policy name.
// *Action: Correct the input and try again.
55476, 00000,"policy \"%s\" does not exist"
// *Cause: An attempt was made to use a nonexistent Oracle Virtual
// Private Database (VPD) policy.
// *Action: Correct the input and try again.
55477, 00000,"policy with dependent models may not be dropped"
// *Cause: An attempt was made to drop an Oracle Virtual Private
// Database (VPD) policy with dependent models.
// *Action: Remove the VPD policy from the models and try again.
55478, 00000,"application table with multiple RDF models not suitable for VPD"
// *Cause: An attempt was made to VPD-enable a model which shared the
// application table with another model.
// *Action: None.
55479, 00000,"a policy already assigned to the RDF model"
// *Cause: An attempt was made to assign Oracle Virtual Private
// Database (VPD) policy to a model with a VPD policy already
// in effect.
// *Action: None.
55480, 00000,"model participating in a virtual model may not be VPD-enabled"
// *Cause: An attempt was made to VPD-enable a model that
// participated in a virtual model.
// *Action: None.
55481, 00000,"VPD policy may not be applied for OLS-enabled RDF repository"
// *Cause: An attempt was made to VPD-enable a model with an Oracle
// Label Security (OLS) policy already in effect.
// *Action: OLS and VPD may not be used simultaneously.
55482, 00000,"VPD may not be applied to version-enabled RDF repository"
// *Cause: An attempt was made to VPD-enable a version-enabled
// Resource Definition Framework (RDF) repository. This is
// not supported.
// *Action: None.
55483, 00000,"policy \"%s\" not assigned to the model"
// *Cause: An attempt was made to remove an Oracle Virtual Private
// Database (VPD) policy that was never assigned to the
// model.
// *Action: None.
55484, 00000,"circular dependency not allowed in RDF metadata"
// *Cause: An attempt was made to define metadata elements that had
// a circular dependency for the Oracle Virtual Private
// Database (VPD) policy.
// *Action: Correct the input and try again.
55485, 00000,"metadata may not be directly assigned to an equivalent property"
// *Cause: An attempt was made to assign metadata directly to a
// property that was declared to be an equivalent of
// another.
// *Action: None.
55486, 00000,"metadata exists for the equivalent property"
// *Cause: An attempt was made to make a property equivalent of
// another when some metadata already existed for this
// property.
// *Action: None.
55487, 00000,"VPD constraints exist for the equivalent property"
// *Cause: An attempt was made to make a property equivalent of
// another when some Oracle Virtual Private Database (VPD)
// constraints already existed for this property.
// *Action: Correct the input and try again.
55488, 00000,"metadata definition already exists for the policy"
// *Cause: An attempt was made to add a duplicate metadata definition
// for an Oracle Virtual Private Database (VPD) policy.
// *Action: None.
55489, 00000,"conflicting metadata definition exists for the policy"
// *Cause: An attempt was made to define conflicting metadata
// definitions for an Oracle Virtual Private Database (VPD)
// policy.
// *Action: Correct the input and try again.
55490, 00000,"VPD constraint may not be assigned to an equivalent property"
// *Cause: An attempt was made to assign an Oracle Virtual Private
// Database (VPD) constraint to a property declared to be an
// equivalent of another.
// *Action: Assign the VPD constraint to the property that is the
// target of the equivalent property.
55491, 00000,"VPD policy constraint with matching name already exists"
// *Cause: An attempt was made to specify a duplicate name for the
// Oracle Virtual Private Database (VPD) policy.
// *Action: Correct the input and try again.
55492, 00000,"error creating VPD policy constraint: %s"
// *Cause: The Oracle Virtual Private Database (VPD) constraint had
// errors.
// *Action: See Oracle documentation.
55493, 00000,"specified VPD policy constraint does not exist"
// *Cause: An attempt was made to operate on an Oracle Virtual
// Private Database (VPD) constraint that did not exist.
// *Action: None.
55494, 00000,"input model set may only have a unique VPD policy"
// *Cause: An attempt was made to execute a multi-model query where
// the models, as a set, did not have a unique Oracle
// Virtual Private Database (VPD) policy.
// *Action: Correct the input and try again.
55495, 00000,"application table with multiple models may not be version-enabled"
// *Cause: An attempt was made to version-enable an application table
// associated with multiple Resource Definition Framework
// (RDF) models.
// *Action: Correct the input and try again.
55496, 00000,"unsupported versioning configuration (History/Valid time) for RDF data"
// *Cause: An attempt was made to use an unsupported configuration
// for Resource Definition Framework (RDF) versioning.
// *Action: Correct the input and try again.
55497, 00000,"RDF repository with an OLS policy may not be version-enabled"
// *Cause: An attempt was made to version-enable a model with Oracle
// Label Security (OLS) policy.
// *Action: Versioning is not supported for OLS-enabled Resource
// Definition Framework (RDF) repository.
55498, 00000,"VPD-enabled RDF model may not be version-enabled"
// *Cause: An attempt was made to version-enable a model with an
// Oracle Virtual Private Database (VPD) policy
// in effect.
// *Action: Versioning of VPD-enabled Resource Definition Framework
// (RDF) models is not supported.
/////////////////////////////////////////////////////////////////////////////
// 55500 - 56499 Reserved for Transaction Layer 11g Projects
// 55500 - 55550 Reserved for Flashback Transaction Backout
/////////////////////////////////////////////////////////////////////////////
55500, 0000, "Event to be used for different trace levels"
// *Cause: None.
// *Action: Change level for desired tracing in Flashback Transaction Backout.
55501, 0000, "Backing out live transaction"
// *Cause: Flashback Transaction Backout was requested on a transaction
// that has not committed yet.
// *Action: Commit the transaction before using this feature.
55502, 0000, "Specified input transaction by name has no SCN hint"
// *Cause: The specified transaction names for Flashback Transaction Backout
// was missing an SCN hint.
// *Action: Provide an SCN hint, and guarantee that the named transactions
// start before the given SCN.
55503, 0000, "Mining finished without seeing specified transactions"
// *Cause: The SCN hit passed was not good. The SCN hit may have come after
// the start of any of the input transactions.
// *Action: Give a lesser and more conservative SCN hint, with greater
// probability of having seen the start of a transaction.
55504, 0000, "Transaction conflicts in NOCASCADE mode"
// *Cause: Transactions other than the ones specified conflicts with
// the specified transactions.
// *Action: Try using other options like NONCONFLICT_ONLY or CASCADE or
// NOCASCADE_FORCE.
55505, 0000, "DDL done on an interesting object after mining start SCN"
// *Cause: The Flashback Transaction Backout process encountered an
// interesting object which had its last DDL operation done on it
// after the mining start time. An interesting object is one that
// has been modified by either the specified transactions or any of
// their dependents.
// *Action: Specify transactions that have committed after
// the last DDL done on all the objects they touched.
55506, 0000, "Transaction performed unsupported change"
// *Cause: A transaction in the dependency DAG performed some
// action that cannot be backed out. You can back out a transaction,
// only if undo has been logged for all of its operations. Note some
// operations do not log undo, such as Insert Direct Load and
// LOB changes. If you encounter a transaction that has performed
// any of these operations, you cannot back it out.
// *Action: The specified transaction cannot be backed out.
55507, 0000, "Encountered mining error during Flashback Transaction Backout. function:%s"
// *Cause: Mining error.
// *Action: None.
55508, 0000, "Invalid input to Flashback Transaction Backout"
// *Cause: Null varrays passed or invalid input specified
// *Action: Specify properly formed varrays and valid options
55509, 0000, "Creation of dependencies could not finish"
// *Cause: One or more input transaction or any of its dependents are not
// committed or have been aborted after more than 1 minute of calling
// the backout function.
// *Action: Commit all the active transactions associated with this table and
// try again.
55510, 0000, "Mining could not start"
// *Cause: Mining could not start for the following reasons.
// 1. A logminer session was processing
// 2. The database was not mounted or not opened for read and write
// 3. Minimum supplemental logging was not enabled
// 4. Archiving was not enabled
// *Action: Fix the mentioned problems and try again. Note that if
// you enable supplemental logging now, you will not be able to
// remove a transaction that has committed without supplemental
// logging.
55511, 0000, "Flashback Transaction experienced error in executing undo SQL"
// *Cause: There was a constraint violation exception when executing in
// NOCASCADE_FORCE mode. Users could also get this
// error if appropriate supplemental logging is not enabled causing
// constraint dependencies to go unnoticed.
// *Action: Either use CASCADE or NONCONFLICT_ONLY options or add appropriate
// level for supplemental logging.
55512, 0000, "Backing out PDML or XA-RAC transaction"
// *Cause: One of the transactions in the dependency graph was a
// PDML transaction or a local transaction which is a branch of a
// global XA transaction, spanning multiple RAC instances.
// Currently flashback transaction does not support this type of
// transaction.
// *Action: None
55513, 0000, "Backing out an AQ transaction"
// *Cause: One of the transactions in the dependency graph touched an
// AQ table. As AQ externalizes database information, these
// transactions are not backed out, as the entire effects of the
// transaction cannot be seen from inside the database.
// *Action: None
55514, 0000, "Backing out a DDL transaction"
// *Cause: One of the transactions in the dependency graph is a DDL
// transaction and could not be backed out.
// *Action: None
55515, 0000, "Mining sees input transaction changes without seeing transaction start"
// *Cause: The start SCN provided was higher than the transaction start but
// below the transaction commit. The result was only partial changes
// for the given transaction.
// *Action: Please provide a lower scn hint to flashback transaction.
55516, 0000, "Event to dump the LCR's seen by flashback transaction backout to trace file"
// *Cause: None.
// *Action: Set it to 0 for real flashback transaction. If this is set,
// flashback transaction will not proceed.
55517, 0000, "Internal use"
// *Cause: None.
// *Action: None
55518, 0000, "Mining across reset logs"
// *Cause: Flashback Transaction Backout cannot work with missing changes.
// This error is thrown if we walk across a reset-logs branch,
// where we might have missed changes.
// *Action: If the user knows that the transaction happened in the current
// reset logs branch, then the SCN-hint is possibly incorrect.
// Provide an SCN in the current reset log branch.
55519, 0000, "Supplemental logging not available for mining SCN range"
// *Cause: Flashback Transaction cannot work if there are regions in the
// mining range where supplemental logging is not enabled.
// *Action: If you have provided a SCN/time hint which is approximate and
// far beyond the specified transaction start time, then readjust
// the SCN hint and try again. If the system has figured out the
// transaction start time or you are sure of the range, then the
// specified transaction cannot be backed out.
55520, 0000, "Log record in compatibility lower than 11.0"
// *Cause: The logical change record shows that the compatibility of the
// mined redo is lower than version 11.0. Flashback transaction
// works only on redo versions 11.0 and above.
// *Action: Advance the compatibility and try to back out transactions
// that have occurred after the compatibility increase.
55521, 0000, "Transaction layer temp undo- miscellaneous debug event"
// *Cause:
// *Action:
// Level 1 > Enable general temp undo debug traces
55522, 0000, "failed to extend temporary undo segment number %s"
// *Cause: A failure occurred when trying to extend the temporary undo segment.
// *Action: This is normally followed by another error message that caused
// the failure. Check the size of default the temporary tablespace.
55523, 0000, "Transaction layer parallel transaction- miscellaneous debug event"
// *Cause:
// *Action:
// Level 1 > Enable general parallel transaction debug traces
55524, 00000, "Too many recursive autonomous transactions for temporary undo"
// *Cause: An attempt was made to issue too many recursive autonomous
// transactions causing the temporary undo segment to be out of slots.
// *Action: Reconnect to establish a new session and do not use deep nesting of
// autonomous transactions.
55525, 00000, "cannot generate temporary undo in a distributed transaction"
// *Cause: An attempt was made to generate temporary undo in a distributed
// transaction.
// *Action: Do not change temporary objects in a distributed transaction.
55526, 00000, "temporary tablespace to store temporary undo not available"
// *Cause: An attempt was made to generate temporary undo without adding
// temporary tablespace in the database.
// *Action: Add temporary tablespace prior to enabling temporary undo.
55527, 0000, "Diagnostic event for external SCN-comparing errors"
// *Cause:
// *Action: Set the level to 2 for diagnostics of ORA-30052 or set the level to
// 4 for diagnostics of ORA-30054.
55528, 0000, "maximum number of RECO sessions reached"
// *Cause: To mitigate a potential denial-of-service (DoS) attack via the
// recoverer process (RECO), the creation of a new RECO session has
// been prevented, because the maximum number of RECO sessions has
// been reached.
// *Action: If there is a legitimate requirement for additional concurrent
// RECO sessions, adjust the values for the RECO parameters to allow
// more RECO sessions.
55529, 0000, "value %s of %s is outside the valid range of 2 to 32765"
// *Cause: An attempt was made to set the parameter to an invalid value.
// *Action: Specify a value between 2 and 32765, inclusive.
55547, 0000, "transaction layer in-memory processing- internal event"
// *Document: NO
// *Cause:
// *Action:
55548, 0000, "transaction layer in-memory processing- internal event"
// *Document: NO
// *Cause:
// *Action:
55549, 0000, "transaction layer in-memory processing- miscellaneous debug event"
// *Document: NO
// *Cause:
// *Action:
55550, 0000, "Event to be used for testing ktubu extensions"
// *Cause: None.
// *Action: None
55551, 0000, "Trigger 4136 corruption"
55552, 0000, "Trigger 4137 corruption"
55553, 0000, "Trigger 4139 corruption"
55554, 0000, "Trigger 4140 corruption"
55555, 0000, "Trigger 4152 corruption"
55556, 0000, "Trigger 4143 corruption"
55557, 0000, "Trigger 4144 corruption"
// *Cause: Above events used for testing corruption path
// *Action: None
55558, 0000, "%s is not a corrupted transaction"
// *Cause: the given transaction is not in the corrupt list v$corrupt_xid_list
// *Action: check v$corrupt_xid_list
55559, 0000, "Test proactive txn health check"
55560, 0000, "Test reactive txn health check"
55561, 0000, "Test 25027 corruption"
55562, 0000, "Not able to get TX enqueue, cannot force commit %s"
55563, 0000, "%d is not a valid undo segment number"
// *Cause: the given usn is not a valid one
// *Action: check undo$
55564, 0000, "%s is not a valid transaction id"
// *Cause: the given txn is not a valid one
// *Action: check txn id
55565, 0000, "%s is not a valid undo segment number"
// *Cause: the given usn is not a valid one
// *Action: check undo$
55566, 0000, "SQL statement issued when the database was not open for queries"
// *Cause: Tried to access SMON time zone information when database was not open
// for queries.
// *Action: Reissue the SQL statement after the database is open for queries.
55567, 0000, "The _highthreshold_undoretention value should be at least %s based on the current undo retention settings."
// *Cause: The _highthreshold_undoretention value was not greater than or
// equal to the UNDO_RETENTION setting and the low threshold value
// used for tuning undo retention.
// *Action: Reissue the SQL statement with a higher value.
55568, 0000, "The maximum query length (mql) value should be atmost %s based on the current _highthreshold_undoretention setting."
// *Cause: The maximum query length (mql in minutes) was not less than or
// equal to half the _highthreshold_undoretention parameter setting.
// *Action: Reissue the SQL statement with a lower value for mql or
// increase the value of _highthreshold_undoretention parameter.
55569, 0000, "The UNDO_RETENTION parameter value should be atmost %s, the _highthreshold_undoretention setting."
// *Cause: The UNDO_RETENTION parameter value was not less than or equal to
// the _highthreshold_undoretention parameter setting.
// *Action: Reissue the SQL statement with a lower value for UNDO_RETENTION
// parameter or increase the value of _highthreshold_undoretention
// parameter.
55570, 0000, "transaction layer debug trace event"
// *Cause:
// *Action:
/////////////////////////////////////////////////////////////////////////////
// 55571 - 55599 Reserved for Flashback Transaction Query
/////////////////////////////////////////////////////////////////////////////
//
55571, 0000, "Oracle Flashback Transaction Query is not supported in a consolidated Oracle database running in shared undo mode."
// *Cause: The consolidated database was in shared undo mode and Oracle Flashback
// Transaction Query could not mine undo records across pluggable databases.
// *Action: The consolidated database must be switched to local undo mode.
/////////////////////////////////////////////////////////////////////////////
// 55600 - 55699 Reserved for Flashback Archive
/////////////////////////////////////////////////////////////////////////////
//
55600, 00000, "The table \"%s\".\"%s\" is already enabled for Flashback Archive"
// *Cause: The specified table is already enabled for Flashback Archive.
// *Action: No action required.
//
55601, 00000, "The table \"%s\".\"%s\" cannot be enabled for Flashback Archive"
// *Cause: An attempt is made to enable Flashback Archive for a table which
// should never be enabled for Flashback Archive.
// *Action: Check the table name.
//
55602, 00000, "The table \"%s\".\"%s\" is not enabled for Flashback Archive"
// *Cause: An attempt was made to perform Flashback Archive operation on a
// table on which Flashback Archive is not enabled.
// *Action: Check the table name.
//
55603, 00000, "invalid flashback archive or valid time period command"
// *Cause: An invalid flashback archive or valid time period command was
// specified.
// *Action: Check the SQL statement.
//
55604, 00000, "Incorrect tablespace is specified"
// *Cause: An incorrect tablespace is specified for the Flashback Archive.
// *Action: Check the SQL statement and verify the possible causes,
// 1, the tablespace that was already used by the Flashback Archive.
// 2, the tablespace was not used by the Flashback Archive.
// 3, the tablespace block size is less than 8K.
// 4, the tablespace is a lost write tablespace
//
55605, 00000, "Incorrect Flashback Archive is specified"
// *Cause: An attempt was made to operate on a Flashback Archive that does
// not exist, or to create a Flashback Archive that already exists.
// *Action: Check the SQL statement.
//
55606, 00000, "Event to modify archiver sleep time in seconds"
// *Cause: 30 seconds is recommended as the archiver sleep time for tests.
// *Action: The default archiver sleep time is 300 seconds
//
55607, 00000, "Event to enable debugging of archiver"
// *Cause: The purpose of this event is for debugging.
// *Action: Attach to process specified.
//
55608, 00000, "Default Flashback Archive does not exist"
// *Cause: The default Flashback Archive did not exist.
// *Action: Create the default Flashback Archive first.
//
55609, 00000, "Attempt to create duplicate default Flashback Archive"
// *Cause: An attempt was made to create a default Flashback Archive while
// one already exists.
// *Action: No action required.
//
55610, 00000, "Invalid DDL statement on history-tracked table"
// *Cause: An attempt was made to perform certain DDL statement that is
// disallowed on tables that are enabled for Flashback Archive.
// *Action: No action required.
//
55611, 00000, "No privilege to manage default Flashback Archive"
// *Cause: An attempt was made to create, alter, or drop the default
// Flashback Archive.
// *Action: No action required.
//
55612, 00000, "No privilege to manage Flashback Archive"
// *Cause: An attempt was made to create, alter, or drop a Flashback
// Archive.
// *Action: No action required.
//
55613, 00000, "Invalid Flashback Archive quota size"
// *Cause: An attempt was made to specify invalid Flashback Archive
// quota size.
// *Action: Specify size in MB, GB, TB, PB, or EB.
//
55614, 00000, "AUM needed for transactions on tracked tables"
// *Cause: An attempt was made to execute DML on a tracked table without
// enabling Auto Undo Management.
// *Action: Disable tracking on the table or enable Auto Undo Management.
//
55615, 00000, "Event to test archiver scheduled internal tasks"
// *Cause: The purpose of this event is for testing.
// *Action: No action required.
//
55616, 00000, "Transaction table needs Flashback Archiver processing"
// *Cause: Too many transaction table slots were being taken by transactions
// on tracked tables.
// *Action: Wait for some amount of time before doing tracked transactions.
//
55617, 00000, "Flashback Archive \"%s\" runs out of space and tracking on \"%s\" is suspended"
// *Cause: Flashback archive tablespace quota is running out.
// *Action: Add tablespace or increase tablespace quota for the flashback archive.
//
55618, 00000, "Insufficient privilege to grant Flashback Archive privilege"
// *Cause: An attempt was made to grant Flashback Archive privilege.
// *Action: No action required.
//
55619, 00000, "Invalid privilege to grant on Flashback Archive"
// *Cause: An attempt was made to grant invalid privilege on a Flashback
// Archive object.
// *Action: Specify valid privilege.
//
55620, 00000, "No privilege to use Flashback Archive"
// *Cause: An attempt was made to enable Flashback Archive on a table
// without such privileges.
// *Action: No action required.
//
55621, 00000, "User quota on tablespace \"%s\" is not enough for Flashback Archive"
// *Cause: An attempt was made to create or alter a Flashback Archive quota
// which is larger than the user's quota.
// *Action: No action required.
//
55622, 00000, "DML, ALTER and CREATE UNIQUE INDEX operations are not allowed on table \"%s\".\"%s\""
// *Cause: An attempt was made to write to or alter or create unique index
// on a Flashback Archive internal table.
// *Action: No action required. Only Oracle is allowed to perform such
// operations on Flashback Archive internal tables.
//
55623, 00000, "Flashback Archive \"%s\" is blocking and tracking on all tables is suspended"
// *Cause: Flashback archive tablespace has run out of space.
// *Action: Add tablespace or increase tablespace quota for the flashback archive.
//
55624, 00000, "The table \"%s\".\"%s\" cannot be enabled for Flashback Archive at this point"
// *Cause: An attempt was made to enable Flashback Archive again on a table
// which was just disabled.
// *Action: Try again later.
//
55625, 00000, "Cannot grant Flashback Archive privilege to a role"
// *Cause: An attempt was made to grant or revoke Flashback Archive privilege
// to a role.
// *Action: No action required.
//
55626, 00000, "Cannot remove the Flashback Archive's primary tablespace"
// *Cause: An attempt was made to remove the primary tablespace of the
// Flashback Archive.
// *Action: No action required.
//
55627, 00000, "Flashback Archive tablespace must be ASSM tablespace"
// *Cause: An attempt was made to add a tablespace that was not an ASSM
// tablespace.
// *Action: Add tablespace that is created with segment space management auto.
//
55628, 00000, "Flashback Archive supports Oracle 11g or higher"
// *Cause: An attempt was made to created a Flashback Archive with incorrect
// compatible mode or without auto undo management.
// *Action: Use compatible mode equal to 11.0 or higher, and use auto undo
// management.
//
55629, 00000, "Event to test Flashback Archiver internal management tasks"
// *Cause: The purpose of this event is for testing.
// *Action: No action required.
//
55630, 00000, "Flashback data archive cannot be enabled on a nested table, temporary table, external table, materialized view, AQ table, clustered table, or non-table object."
// *Cause: An attempt was made to enable flashback data archive on an object
// which is not supported by flashback data archive.
// *Action: Do not use the FLASHBACK ARCHIVE clause for this object.
//
55631, 00000, "Table has columns with data types that are not supported by Flashback Data Archive"
// *Cause: An attempt was made to add a column of data type that is not
// supported by Flashback Data Archive. Or, the table on which
// Flashback Data Archive is being enabled contains column(s) with
// data types not supported by Flashback Data Archive.
// *Action: Do not use FLASHBACK ARCHIVE clause for this object.
// If adding column, do not use LONG or Nested Table column data type.
//
55632, 00000, "Tablespace has Flashback Archive tables"
// *Cause: An attempt was made to remove a tablespace that has Flashback
// Archive tables.
// *Action: No action required.
//
55633, 00000, "Cannot do DDL on Flashback Data Archive enabled table"
// *Cause: An attempt was made to do DDL on tracked tables while one DDL is
// runnning.
// *Action: Retry the DDL at a later time.
//
55634, 00000, "Unable to disassociate or re-associate Flashback Data Archive table \"%s\".\"%s\""
// *Cause: Either an incorrect table name was used or an exclusive lock on the
// table could not be acquired.
// *Action: Check the table name and release locks on the table.
//
55635, 00000, "Flashback Data Archive enabled table \"%s\".\"%s\" is disassociated"
// *Cause: An attempt was made to perform operation on a Flashback Data Archive
// enabled table that is currently disassociated for DDL.
// *Action: Retry the operation at a later time.
//
55636, 00000, "Flashback Data Archive enabled table \"%s\".\"%s\" has different definition from its history table"
// *Cause: The Flashback Data Archive enabled table has different table
// definition from its history table.
// *Action: Fix the table definition.
//
55637, 00000, "Flashback Data Archive enabled table \"%s\".\"%s\" is not in the correct compliance mode for this operation"
// *Cause: An attempt was made to perform disassociation operation on a
// Flashback Data Archive enabled table that is in compliance mode.
// Or, DDL are not supported on tables in noncompliance mode.
// *Action: Disable compliance mode before retrying the disassociation operation.
//
55638, 00000, "DDL operations on Flashback Data Archive-enabled table are not allowed at this point"
// *Cause: Flashback Data Archive could not acquire resources to complete the
// operation on Oracle RAC.
// *Action: Retry the DDL at a later time.
//
55639, 00000, "Flashback Data Archive internal SQL error"
// *Cause: Flashback Data Archive encountered internal SQL error.
// *Action: No action required.
//
55640, 00000, "Insufficient privilege to perform the Flashback Data Archive operation"
// *Cause: An attempt was made to disassociate tables enabled for Flashback Data Archive without the required privilege.
// *Action: No action required.
//
55641, 00000, "Cannot drop tablespace used by Flashback Data Archive"
// *Cause: An attempt was made to drop a Flashback Data Archive tablespace.
// *Action: Remove the tablespace from Flashback Data Archive before retrying the operation.
//
55642, 00000, "Table has column names that are reserved by Flashback Data Archive"
// *Cause: The table on which Flashback Data Archive is being enabled contains
// column(s) with names that are reserved by Flashback Data Archive.
// *Action: Rename column name before retry.
//
55643, 00000, "cannot combine Flashback Data Archive operation with other operations"
// *Cause: An attempt was made to combine the Flashback Data Archive operation
// with other ALTER TABLE operations.
// *Action: Ensure that Flashback Data Archive is the sole operation specified in ALTER TABLE statement.
//
55644, 00000, "event to enable system column ORA_XID testing"
// *Cause: The purpose of this event was for testing.
// *Action: No action required.
//
55645, 00000, "Valid time period cannot be enabled on a nested table, temporary table, external table, materialized view, AQ table, clustered table, or non-table object."
// *Cause: An attempt was made to enable a valid time period on an object
// which is not supported by valid time period.
// *Action: Do not use a valid time period for this object.
//
55646, 00000, "application already enabled for flashback archive"
// *Cause: An attempt was made to enable flashback archive on an application
// for a second time.
// *Action: No need to enable flashback archive on this application.
//
55647, 00000, "application not previously enabled for flashback archive"
// *Cause: An attempt was made to disable flashback archive on an application
// that has not been enabled for flashback archive.
// *Action: No need to disable flashback archive on this application.
//
55648, 00000, "table already added to application"
// *Cause: An attempt was made to add a table to an application for a second
// time.
// *Action: Do not add a table to an application more than once.
//
55649, 00000, "table not previously added to application"
// *Cause: An attempt was made to remove a table that has not been added to
// an application.
// *Action: No need to remove table from application.
//
55650, 00000, "application not registered for flashback archive"
// *Cause: An attempt was made to access an application that has not been
// registered for flashback archive.
// *Action: Register the application before accessing it.
//
55651, 00000, "application already registered for flashback archive"
// *Cause: An attempt was made to register an application for flashback
// archive for a second time.
// *Action: No need to register this application for flashback archive.
//
55652, 00000, "application already locked down"
// *Cause: An attempt was made to lock down an application for a second time.
// *Action: No need to lock down this application.
//
55653, 00000, "application not previously locked down"
// *Cause: An attempt was made to unlock an application that was not
// previously locked down.
// *Action: No need to unlock this application.
//
55654, 00000, "too many columns in the base table"
// *Cause: An attempt was made to enable flashback archive on a base table
// with so many columns that the history table has no room for
// metadata columns.
// *Action: Have fewer columns in the base table.
//
55655, 00000, "Flashback archive is being used by an application."
// *Cause: An attempt was made to drop the flashback archive, however,
// it was still being used by an application.
// *Action: Check the SYS_FBA_APP table to see which application is using
// the flashback archive. Drop the application before dropping the
// flashback archive.
/////////////////////////////////////////////////////////////////////////////
// 55700 - 55709 Reserved for MinActiveScn
/////////////////////////////////////////////////////////////////////////////
//
55700, 00000, "Disable MinActiveTxnStartScn block cleanout optimization"
// *Document: NO
// *Cause:
// *Action: Set this event only under the supervision of Oracle Support
// Services or development.
//
55701, 00000, "Turn OFF HP Exadata Storage Server Commit Cache"
// *Document: NO
// *Cause:
// *Action: Turns off the HP Exadata Storage Server Commit Cache; Set this
// event only under the supervision of Oracle Support Services or development.
//
55702, 00000, "Dump the HP Exadata Storage Server Commit Cache on the CellSrv"
// *Document: NO
// *Cause:
// *Action: Dumps the HP Exadata Storage Server commit cache on the
// cellsrv. Internal Event used for debugging.
//
55703, 00000, "Trace min-act to MMON trace file"
// *Document: NO
// *Cause:
// *Action: Dumps min-act-scn tracing to MMON trace file.
//
/////////////////////////////////////////////////////////////////////////////
// 55710 - 55799 Reserved for Clusterwide Global Transactions
/////////////////////////////////////////////////////////////////////////////
//
55710, 00000, "Unable to alter system parameter GLOBAL_TXN_PROCESSES at this time"
// *Cause: The system was in the process of adjusting the number of global
// transaction background processes.
// *Action: Retry the operation at a later time.
//
55711, 00000, "Unable to bind clusterwide global transactions to compatible undo"
// *Cause: Undo tablespace was not onlined for automatic undo management.
// *Action: Create undo tablespace if it has not been created.
//
55712, 00000, "XA transactions on RAC are not supported with GLOBAL_TXN_PROCESSES set to 0"
// *Cause: The initialization parameter GLOBAL_TXN_PROCESSES was set to 0.
// *Action: Set the initialization parameter GLOBAL_TXN_PROCESSES to a value greater than 0.
//
55713, 00000, "GLOBAL_TXN_PROCESSES cannot be set to 0 at runtime"
// *Cause: An attempt was made to set initialization parameter GLOBAL_TXN_PROCESSES
// to 0 at runtime.
// *Action: Set the initialization parameter GLOBAL_TXN_PROCESSES to 0 before starting
// RAC instance to disable GTX background processes. Note that XA transactions
// are not supported on RAC database when GTX background processes are disabled.
//
55714, 00000, "savepoint '%s' disabled with interleaved changes across Oracle RAC instances"
// *Cause: After the savepoints were established, interleaved changes were made
// across Oracle RAC instances within the clusterwide global transaction.
// *Action: Do not make interleaved changes across Oracle RAC instances after savepoints
// are established.
//
55715, 00000, "The current transaction cannot become distributed."
// *Cause: The current local transaction was already bound to an undo segment that was not
// compatible with clusterwide global transactions.
// *Action: Ensure that you set UNDO_MANAGEMENT to AUTO and that an undo tablespace is
// created and configured for the instance.
//
/////////////////////////////////////////////////////////////////////////////
// 55800 - 55899 Reserved for Txn layer control events or generic errors
/////////////////////////////////////////////////////////////////////////////
55800, 00000, "NLS errors while processing Oracle number"
// *Cause: Error occurred when trying to convert Oracle number to an integer.
// *Action: Check the input parameters.
55801, 00000, "Event to control CR activity"
// *Cause: The bit values that we consider.
// 0x1: Remove fix for bug 3514835 which could potentially throw more 8177 errors
// We have conservatively blocked some serializability errors, where there
// could potentially be a dependency between a service transaction in an
// index and forward going transaction.
// *Action: Set event 55801 to 1 to disable the bug fix, thereby reducing 8177
// error, although it might cause some internal errors instead.
55802, 00000, "Event to enable CR in memory tracing"
// *Document: NO
// *Cause: This is for internal use.
// *Action: None.
55803, 00000, "Prepared transaction marked for deletion"
// *Document: NO
// *Cause: This is for internal use.
// *Action: None.
/////////////////////////////////////////////////////////////////////////////
// 55901 - 55999 Reserved for Securefile Logging Service
// 55901/55902 reserved for debug and tracing levels
/////////////////////////////////////////////////////////////////////////////
55901, 0000, "Secure file log Trace event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: None
55902, 0000, "Secure file log Debug event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: None.
55903, 0000, "Secure file log feature unimplemented: %s"
// *Cause: This feature has not been implemented yet.
// *Action: None.
55904, 0000, "Secure file log name too big"
// *Cause: The specified log name was bigger than the maximum identifier
// supported in Oracle.
// *Action: Use a smaller log name.
55905, 0000, "Secure file log %s exists with same name"
// *Cause: Create operation was attempted on an existing secure file log.
// *Action: Destroy the log with the specified name and retry.
55906, 0000, "Secure file log [id: %s name: %s] does not exist"
// *Cause: An open operation for read or write was attempted on a
// nonexistent log.
// *Action: Create the log and retry.
55907, 0000, "Tablespace %s does not exist for secure file log"
// *Cause: The specified tablespace to keep the swap space for the secure file
// log does not exist.
// *Action: Retry with a different tablespace or create one with the specified
// name.
55908, 0000, "Tablespace %s does not support secure files"
// *Cause: Specified tablespace to keep secure file logs did not support
// secure files.
// *Action: Provide a tablespace that supports secure files, or remove
// secure file options in the create statement.
55909, 0000, "Create mode invalid: %s"
// *Cause: The mode to create the log was not supported, or there was
// a discrepancy between the in-memory log creation and the
// persistent definition already present.
// *Action: Retry by correcting the problem.
55910, 0000, "Swap table %s does not exist"
// *Cause: The dictionary-provided swap name did not exist. This could be
// caused by an external dropping of the swap table without going
// through the secure file log API's. This means that all of the
// persistent part of the log was lost.
// *Action: Destroy the specified log and recreate from start.
55911, 0000, "Log with id: %s is being destroyed"
// *Cause: A write, read or open operation was being tried on a log that
// was in the process of being destroyed.
// *Action: None.
55912, 0000, "Invalid thread Id provided to write to a threaded log"
// *Cause: A valid thread Id was not provided in order to write to a threaded
// log. Thread Ids are used to partially order messages to the log
// from different writing processes.
// *Action: Provide a logical thread Id or use a nonthreaded log.
55913, 0000, "Valid thread Id provided to a nonthreaded log"
// *Cause: A valid logical thread Id was provided for a nonthreaded log.
// A partial order will not be maintained in a nonthreaded log
// and messages could be output in random order.
// *Action: Provide a null thread-id for a non-threaded log, or create
// a threaded log to do what is required.
55914, 0000, "An invalid descriptor was passed to a log operation. Reason: %s"
// *Cause: An invalid or uninitialized descriptor was found while doing
// a secure file log read or write.
// *Action: Provide a properly initialized descriptor created by log open.
55915, 0000, "Invalid option: %s"
// *Cause: An invalid option was passed for a log operation.
// *Action: Check the cause and retry.
55916, 0000, "Message too long"
// *Cause: The log is opened with split messages across buffers set to false.
// However, the message size is bigger than what can be fit in one
// buffer.
// *Action: Write the message in smaller segments or allow split messages
// while creating the log.
55917, 0000, "Table flush I/O failed for log ID: %s bucket ID: %s"
// *Cause: Table flush I/O failed. The most common cause for this could
// be out-of-space errors in the tablespace.
// *Action: Resolve the underlying problem and retry.
55918, 0000, "Required buffer size too big"
// *Cause: The buffer size was greater than 16K. Secure file logging supports
// buffer sizes of 4K, 8K and 16K. The only reason a large buffer
// size is required is if split message is set to false, and the
// potential message is large.
// *Action: Request a smaller buffer size, or try to use smaller message
// segments.
55919, 0000, "destroying, purging or partitioning log while writers or readers have open descriptors"
// *Cause: The method to destroy, purge or partition log was called and requested to wait for open descriptors.
// After waiting for 5 minutes, an error is returned
// if writers or readers still exist.
// *Action: Close all open descriptors or call destroylog, purgelog or createpartition with the
// option of not waiting for open descriptors.
55920, 0000, "Buffer sequence is too low"
// *Cause: The buffer sequence was too low or rows were removed from the
// swap table.
// *Action: Try to read from a higher sequence. Note, that the data in
// buffer with this sequence has been lost.
55921, 0000, "Start point provided is incorrect."
// *Cause: The provided start point, from which to begin reading, was
// incorrect.
// *Action: Provide a minimum SCN, timestamp or sequence or specify that
// reading should begin with the oldest data available.
55922, 0000, "PL/SQL API error: %s"
// *Cause : PL/SQL callbacks had a problem
// *Action: Consider the problem string and act appropriately
55923, 0000, "PL/SQL maximum number of array elements exceeded"
// *Cause: Number of elements in an array write exceeded the maximum limit
// 100 message segments in one write.
// *Action: Try a write buffered with multi-segment write or reduce the
// element count in the array write.
55924, 0000, "PL/SQL encountered a NULL element in the array"
// *Cause: A null element was encountered during an array write.
// *Action: Provide non-null VARCHAR2 or RAW elements as an array element.
55925, 0000, "write end called without proper write start"
// *Cause: An attempt was made to end write without a corresponding start
// write.
// *Action: Write starts and ends must be called in the right order for
// writing piecewise or use a write whole option which does not
// need an explicit start or end.
55926, 0000, "Closing log descriptor before calling write end"
// *Cause: An attempt was made to close the log descriptor before the
// corresponding write end.
// *Action: Write end should be called before closing the log write descriptor
55927, 0000, "No tablespace found for the log"
// *Cause: No suitable tablespace was found for the log.
// *Action: Provide a tablespace and retry log creation.
55928, 0000, "Duplicate tablespace being added"
// *Cause: The tablespace being added for the named log already existed
// in the list of tablespaces available for this log.
// *Action: The user should provide a different tablespace for addition
// to the list of available tablespaces for the named log.
55929, 0000, "Creating new partition when current partition is empty"
// *Cause: An attempt was made to create a new partition for the named log
// when the current partition is empty.
// *Action: Do not attempt to create a new partition when the current
// partition is still empty.
55930, 0000, "Version of log, identified by (logname, instanceid), does not exist"
// *Cause: Version of log, identified by (logname, instanceid), did not exist.
// *Action: Provide the correct (logname, instanceid) input.
55931, 0000, "The highest partition of log, identified by (logname, instanceid), does not exist"
// *Cause: The highest partition of log, identified by (logname, instanceid),
// did not exist.
// *Action: Provide the correct (logname, instanceid) input.
55932, 0000, "No SGA memory available for buffers"
// *Cause: An attempt was made to create a secure file log with no available
// memory for buffers.
// *Action: Set SECUREFILE_LOG_SHARED_POOL_SIZE to allocate adequate memory.
55933, 0000, "invalid log owner provided"
// *Cause: The user provided did not own the secure file log under
// consideration.
// *Action: Provide the correct owner of the secure file log.
55934, 0000, "invalid user ID provided"
// *Cause: The specified user ID did not exist in the database.
// *Action: Provide a valid database user ID.
55935, 0000, "invalid user name provided"
// *Cause: The specified user name did not exist in the database.
// *Action: Provide a valid database user name.
55936, 0000, "user ID mismatch"
// *Cause: The user ID provided did not own the secure file log under
// consideration.
// *Action: Provide the correct owner of the secure file log.
55937, 0000, "storage already associated with the secure file log"
// *Cause: An attempt was made to associate storage with a secure
// file log which already has storage.
// *Action: Do not attempt to associate storage with a secure file
// log which already has associated storage.
55938, 0000, "no flush callback associated with the secure file log"
// *Cause: Flush callback was not associated with the secure
// file log under consideration.
// *Action: The secure file log needs to be re-created with valid flush
// callback.
55939, 0000, "database is not open for attempted operation"
// *Cause: The attempted operation failed because the database
// is not yet open.
// *Action: Resubmit the operation when the database opens.
55940, 0000, "An error occurred during execution of ktliIngestExternData."
// *Cause: An error occurred during execution of ktliIngestExternData.
// *Action: See the message associated with the error for remedial action.
55941, 00000, "DML and DDL operations are not allowed on table \"%s\".\"%s\""
// *Cause: A DML or DDL operation was attempted on a Common Logging
// Infrastructure internal table.
// *Action: No action required. Only Oracle is allowed to perform such
// operations on Common Logging Infrastructure internal tables.
55942, 0000, "read not started for read descriptor of the secure file log"
// *Cause: An attempt was made to get a readsavepoint before ktliRead
// successfully returned a message, using the secure file log
// descriptor under consideration.
// *Action: Execute a ktliRead, which returns a message using the secure file
// log descriptor, before attempting to get a readsavepoint.
55943, 0000, "unsupported verison in readsavepoint of the secure file log"
// *Cause: An attempt was made to open a secure file log with a
// readsavepoint which had unsupported version.
// *Action: Contact Oracle Support Services.
55944, 0000, "External flush I/O failed for log ID: %s bucket ID: %s"
// *Cause: External flush I/O failed.
// *Action: Resolve the underlying problem and retry.
55945, 0000, "tablespace name not specified"
// *Cause: The tablespace needed to keep the swap space for the secure file
// log has not been provided by the user.
// *Action: Retry the operation with the appropriate tablespace name.
55946, 0000, "operation failed due to CrossInstanceCall failure - %s %s"
// *Cause: The operation failed due to a CrossInstanceCall failure.
// Check the trace files on remote instances for the underlying
// problem.
// *Action: Resolve the underlying problem and retry.
55947, 0000, "message too long"
// *Cause: The message length was greater than what the Secure file log
// supports.
// *Action: Provide the message with a length that the Secure file log
// supports and retry the operation.
55948, 0000, "flush threshold is invalid"
// *Cause: The flush threshold specified for the secure file log is invalid.
// *Action: The flush threshold for secure file log must be an integer
// greater than or equal to 1 and less than or equal to 100.
55949, 0000, "swap table of secure file log (%s, %s) does not exist"
// *Cause: The swap table of secure file log did not exist. This could be
// caused by an external dropping of the swap table without going
// through the secure file log API's. This means that all of the
// persistent parts of the log were lost.
// *Action: Destroy the specified log and re-create it from the start.
55950, 0000, "storage not associated with the secure file log [ name: %s ]"
// *Cause: An attempt was made to import data from an external source into a
// secure file log which is not associated with tablespace storage.
// *Action: Associate tablespace storage with a secure file
// log before importing data from an external source.
/////////////////////////////////////////////////////////////////////////////
// 56400 - 56450 Reserved for Transaction Cache
/////////////////////////////////////////////////////////////////////////////
56400, 0000, "Transaction global cache debug event"
// *Document: NO
// *Cause: For internal use only.
// *Action: Change level for desired tracing on global transaction cache.
/////////////////////////////////////////////////////////////////////////////
// 56500 - 56699 Reserved for Database Resident connection pool
// 56500 - 56599 Reserved for Pl/Sql procedures of Database Resident CP
/////////////////////////////////////////////////////////////////////////////
56500, 0000, "DRCP: Pool not found"
// *Cause: The pool name passed was either null or an invalid pool name.
// *Action: Input a valid pool name.
56501, 0000, "DRCP: Pool startup failed"
// *Cause: The connection pool failed to start up.
// *Action: Check logs for details.
56502, 0000, "DRCP: Pool is inactive"
// *Cause: The operation is only supported on an active pool.
// *Action: Start the pool.
56503, 0000, "DRCP: Pool is active"
// *Cause: The operation is only supported on an inactive pool.
// *Action: Shutdown the pool.
56504, 0000, "DRCP: Invalid pool configuration parameter name"
// *Cause: The configuration paramter name is null or invalid input.
// *Action: Input a valid configuration parameter name.
56505, 0000, "DRCP: Invalid pool configuration parameter value"
// *Cause: The configuration paramter value is null or invalid input.
// *Action: Input a valid configuration parameter value.
56506, 0000, "DRCP: Pool shutdown failed"
// *Cause: Connection pool failed to shutdown.
// *Action: Check logs for details.
56507, 0000, "DRCP: Pool alter configuration failed"
// *Cause: Connection pool failed to configure pool.
// *Action: Check logs for details.
56508, 0000, "DRCP: Pool startup failed"
// *Cause: Connection Broker failed to startup the pool.
// *Action: Check logs for details.
56509, 0000, "DRCP: Pool shutdown failed"
// *Cause: Connection Broker failed to shutdown the pool.
// *Action: Check logs for details.
56510, 0000, "DRCP: Pool alter configuration failed"
// *Cause: Connection Broker failed to configure the pool.
// *Action: Check logs for details.
// For the NUM_CBROK and MAXCONN_CBROK values, if the initialization
// parameter CONNECTION_BROKERS contains a (TYPE=POOLED) entry, then
// use the parameter instead to update these values.
56511, 0000, "DRCP: Cross instance synchronization failed"
// *Cause: Publish message to all RAC instances failed.
// *Action: Check logs for details.
56512, 0000, "DRCP: Failed to synchronize RAC instances [%s]"
// *Cause: Some of the RAC instances were not synchronized.
// *Action: Perform the same operations on all the failed instances.
56513, 0000, "DRCP: Cannot perform requested operation using pooled connection"
// *Cause: This operation was not supported using connections from a pool.
// *Action: Use a regular connection to perform this operation.
56514, 0000, "DRCP: invalid value for maximum number of connections to Connection broker"
// *Cause: The value passed exceeded the maximum allowed.
// *Action: No action required. The maximum number of connections was automatically set to the maximum allowed value.
56515, 0000, "DRCP: Operation not allowed from a Pluggable Database"
// *Cause: The operation was not allowed in Database Resident Connection Pooling when connected to a Pluggable Database.
// *Action: Connect to the root database and retry the same operation.
56600, 0000, "DRCP: Illegal call [%s]"
// *Cause: An illegal OCI function call was issued.
// *Action: Check the documentation for Database Resident Connection Pool (DRCP) usage.
56601, 0000, "DRCP: Illegal connection class"
// *Cause: Wrong value for connection class was given.
// *Action: Check the documentation for Database Resident connection pool usage.
56602, 0000, "DRCP: Illegal purity"
// *Cause: Wrong value for purity was provided.
// *Action: Check the documentation for Database Resident connection pool usage.
56603, 0000, "DRCP: Internal error"
// *Cause: Malformed input values.
// *Action: Input well-formed values.
56604, 0000, "DRCP: Length[%s] for %s exceeded the MAX allowed"
// *Cause: Length exceeded MAX for the value.
// *Action: Use a value within the MAX allowed.
56605, 0000, "DRCP: Session switching and migration not allowed"
// *Cause: Application tried to switch or migrate session across connections.
// *Action: This usage is irrelevant in the Database Resident connection pooling
// context and is not supported. Release existing session.
56606, 0000, "DRCP: Client version does not support the feature"
// *Cause: The client version is lower than 11g.
// *Action: Upgrade to a higher client version or turn off (SERVER=POOLED)
// in the connect string.
56607, 0000, "DRCP: Connection is already authenticated"
// *Cause: Attempt to reauthenticate the connection which is authenticated.
// *Action: Logoff the connection before reauthenticating.
56608, 0000, "DRCP: Server Group feature is not supported"
// *Cause: Server Group attribute was set on the server handle,
// connected to a Database Resident connection pool.
// *Action: Do not set Server Group attribute on server handles while using
// Database Resident connection pool.
56609, 0000, "Usage not supported with DRCP"
// *Cause: This usage was not supported on a DRCP connection.
// *Action: Use a dedicated connection to perform this task.
56610, 0000, "Multi-property fix up callback error"
// *Cause: The multi-property fix up callback encountered an error or was not
// able to fix up all the properties.
// *Action: Correct the multi-property fix up callback.
56611, 0000, "DRCP: Timeout while waiting for a server"
// *Cause: The value of SERVER_WAIT_TIMEOUT was reached while waiting for a
// server.
// *Action: Check the Database Resident Connection Pool (DRCP) to see why
// servers are not being freed in a timely manner.
56612, 0000, "PL/SQL fix up callback only supported with multi-property tagging"
// *Cause: PL/SQL fix up callback was specified without multi-property tagging.
// *Action: Either remove the PL/SQL fix up callback or use multi-property
// tagging.
/////////////////////////////////////////////////////////////////////////////
// 56700 - 56799 Reserved for DBMS RESOURCE MANAGER error codes
/////////////////////////////////////////////////////////////////////////////
56700, 00000, "plan %s is a subplan and SUB_PLAN attribute cannot be modified"
// *Cause: An attempt was made to modify the SUB_PLAN attribute of the
// specified plan.
// *Action: Do not attempt to modify the SUB_PLAN attribute.
/
56701, 00000, "INTERNAL_USE attribute of consumer group %s cannot be modified"
// *Cause: An attempt was made to modify the INTERNAL_USE attribute of the
// specified consumer group.
// *Action: Do not attempt to modify the INTERNAL_USE attribute.
/
56702, 00000, "consumer group %s is for internal use only and cannot be a switch target"
// *Cause: An attempt was made to specify an INTERNAL_USE
// consumer group as a switch target.
// *Action: Do not attempt to switch to INTERNAL_USE consumer groups.
/
56703, 00000, "VKTM process died unexpectedly"
// *Cause: An explicit kill or internal error caused the death of VKTM
// background process.
// *Action: Restart the instance.
/
56704, 00000, "EXPLICIT consumer group mapping priority must be set to 1"
// *Cause: An attempt was made to set the EXPLICIT mapping priority
// to a value other than 1.
// *Action: Set the mapping priorities to unique integers within the
// documented range with the EXPLICT priority set to 1.
/
56705, 00000, "I/O calibration already in progress"
// *Cause: An attempt was made to run a second instance of I/O Calibration
// *Action: Wait until the first I/O calibration run is complete; then,
// retry the operation.
/
56706, 00000, "The specified Resource Manager plan is a subplan and cannot be set as a top-level plan"
// *Cause: An attempt was made to set a subplan as a top-level plan.
// *Action: Do not attempt to set subplans as top-level plans.
/
56707, 00000, "INTERNAL_QUIESCE plan cannot be specified as a top-level Resource Manager plan"
// *Cause: An attempt was made to specify INTERNAL_QUIESCE as a
// top-level Resource Manager plan.
// *Action: Do not attempt to set INTERNAL_QUIESCE as a Resource Manager plan.
/
56708, 00000, "Could not find any datafiles with asynchronous i/o capability"
// *Cause: There are no datafiles which are asynchronous I/O capable.
// *Action: Make sure asynchronous i/o is permitted to datafiles.
/
56709, 00000, "timed_statistics set to FALSE"
// *Cause: timed_statistics parameter in database is set to FALSE. Needs
// to be enabled for calibration.
// *Action: set timed_statistics=TRUE in init.ora or
// "alter system set timed_statistics=TRUE"
/
56710, 00000, "DBRM process died unexpectedly"
// *Cause: An explicit kill or internal error caused the death of the DBRM
// background process.
// *Action: Restart the instance.
/
56711, 00000, "%s is an invalid %s argument"
// *Cause: The named argument is invalid.
// *Action: Specify a valid argument for this procedure.
/
56712, 00000, "Invalid upcgm_table_type argument"
// *Document: NO
// *Cause: One of the upcgm_table type arguments is either empty or contains
// more than one element and the number of elements is not the same
// as the other upcgm_table_type arguments.
// *Action: Correct your PL/SQL program so the upcgm_table_type arguments
// have at least one element and the number of elements are the
// same for all arguments with more than one element.
/
56713, 00000, "insufficient Resource Manager privileges"
// *Cause: An attempt was made to execute administration procedures
// from the DBMS_RESOURCE_MANAGER package without the appropriate
// privilege. The procedure requires the Resource Manager
// system privilege.
// *Action: Ask the database administrator to grant the Resource Manager
// system privilege to the user.
/
56714, 00000, "Plan name %s exceeds the maximum length allowed"
// *Cause: Plan name is greater than 30 characters long.
// *Action: Do not exceed 30 characters when naming a resource plan.
/
56715, 00000, "%s resource plan contains a reserved word"
// *Cause: The specified plan name is prefixed with a reserved prefix
// such as FORCE or SCHED.
// *Action: Do not prefix resource plan name with FORCE or SCHED.
/
56716, 00000, "Category %s does not exist"
// *Cause: A non-existent category was specified as an argument to a procedure
// in the package, DBMS_RESOURCE_MANAGER.
// *Action: Specify an existing category name or create a new category with
// this name.
/
56717, 00000, "switch directives are set without a corresponding SWITCH_GROUP"
// *Cause: The plan directive contained a switch directive
// (SWITCH_TIME, SWITCH_IO_REQS, or SWITCH_IO_MEGABYTES)
// without a SWITCH_GROUP.
// *Action: Specify a SWITCH_GROUP parameter in the plan directive.
/
56718, 00000, "Timeout occurred while setting resource plan"
// *Cause: A timeout occurred while waiting for one or more RAC instances
// to set the resource plan.
// *Action: Since the resource plan may have actually been set successfully,
// first check the current resource plan for each instance by
// querying gv$rsrc_plan.
// If the resource plan was not successfully set on all instances,
// then retry the operation.
/
56719, 00000, "Error spawning or communicating with calibration slave"
// *Cause: An error occurred in calibration slave process -
// Calibration process aborted.
// *Action: Review trace files for errors.
/
56720, 00000, "I/O data limit exceeded - call aborted"
// *Cause: The Resource Manager SWITCH_IO_MEGABYTES limit was exceeded.
// *Action: Reduce the complexity of the update or query, or contact your
// database administrator for more information.
/
56721, 00000, "I/O data limit exceeded - session terminated"
// *Cause: The Resource Manager SWITCH_IO_MEGABYTES limit was exceeded.
// *Action: Reduce the complexity of the update or query, or contact your
// database administrator for more information.
/
56722, 00000, "I/O request limit exceeded - call aborted"
// *Cause: The Resource Manager SWITCH_IO_REQS limit was exceeded.
// *Action: Reduce the complexity of the update or query, or contact your
// database administrator for more information.
/
56723, 00000, "I/O request limit exceeded - session terminated"
// *Cause: The Resource Manager SWITCH_IO_REQS limit was exceeded.
// *Action: Reduce the complexity of the update or query, or contact your
// database administrator for more information.
/
56724, 00000, "ksfd calibration tracing"
// *Cause:
// *Action: If this event is set then ksfd calibration module generates
// tracing
/
56725, 00000, "Could not spawn additional calibration slaves"
// *Cause: An error occurred when spawning calibration slave process -
// Calibration process aborted.
// *Action: Check OS resources required for spawning processes
/
56726, 00000, "Category %s is referred to by a consumer group and cannot be deleted"
// *Cause: An attempt was made to delete a category that is referred to by a
// consumer group.
// *Action: Modify or remove all consumer groups that use this category and then
// retry.
/
56727, 00000, "Orion (%s) must be invoked using its full, absolute path"
// *Cause: Orion is spawning a child process and cannot determine
// the location of the executable.
// *Action: Use the full, absolute path for Orion.
/
56728, 00000, "SQL blocks cannot be nested"
// *Cause: An attempt was made to start an SQL block using
// DBMS_RESOURCE_MANAGER.BEGIN_SQL_BLOCK() while already inside an
// SQL block.
// *Action: Close the existing SQL block using
// DBMS_RESOURCE_MANAGER.BEGIN_SQL_BLOCK() or remove this call.
/
56729, 00000, "Failed to bind the database instance to processor group %s"
// *Cause: Binding the database instance to the processor group specified by
// the PROCESSOR_GROUP_NAME parameter failed.
// *Action: Set the PROCESSOR_GROUP_NAME to a valid, configured processor
// group and restart the database instance.
/
56730, 00000, "pluggable database plan %s may not specify parameter %s"
// *Cause: Resource plans inside a pluggable database attempted to use
// the following parameters:
// MGMT_P2, MGMT_P3, MGMT_P4, MGMT_P5, MGMT_P6, MGMT_P7, MGMT_P8
// *Action: Remove these parameters and try again.
/
56731, 00000, "pluggable database plan %s may not use subplans"
// *Cause: An attempt was made to set a resource plan that contains
// subplans. Subplans are not supported in pluggable databases
// (PDBs).
// *Action: Specify a valid PDB resource plan or modify the specified plan
// to remove the subplan directives.
/
56732, 00000, "value %s for %s is outside valid range of 0 to 4294967295"
// *Cause: An invalid value was specified for a plan directive parameter.
// *Action: Specify a value between 0 and 4294967295, inclusive.
/
56733, 00000, "logical I/O limit exceeded - call aborted"
// *Cause: The Resource Manager SWITCH_IO_LOGICAL limit was exceeded.
// *Action: Reduce the complexity of the update or query, or contact your
// database administrator for more information.
/
56734, 00000, "logical I/O limit exceeded - session terminated"
// *Cause: The Resource Manager SWITCH_IO_LOGICAL limit was exceeded.
// *Action: Reduce the complexity of the update or query, or contact your
// database administrator for more information.
/
56735, 00000, "elapsed time limit exceeded - call aborted"
// *Cause: The Resource Manager SWITCH_ELAPSED_TIME limit was exceeded.
// *Action: Reduce the complexity of the update or query, or contact your
// database administrator for more information.
/
56736, 00000, "elapsed time limit exceeded - session terminated"
// *Cause: The Resource Manager SWITCH_ELAPSED_TIME limit was exceeded.
// *Action: Reduce the complexity of the update or query, or contact your
// database administrator for more information.
/
56737, 00000, "SWITCH_GROUP is set without a corresponding switch directive"
// *Cause: The plan directive specified a value for SWITCH_GROUP
// without specifying one of the following switch directives:
// - SWITCH_TIME
// - SWITCH_IO_REQS
// - SWITCH_IO_MEGABYTES
// - SWITCH_ELAPSED_TIME
// - SWITCH_IO_LOGICAL
// *Action: Specify a switch directive or remove SWITCH_GROUP directive.
/
56738, 00000, "CDB resource plan %s has more than %s profile directives."
// *Cause: An attempt was made to create or update the specified
// multitenant container database (CDB) resource plan to use
// more than the supported number of profile directives.
// *Action: Remove the directives for profiles that are
// not active on this database.
/
56739, 00000, "cannot modify max_iops or max_mbps parameter"
// *Cause: An attempt was made to alter the Resource Manager
// max_iops or max_mbps parameter in a non-consolidated database.
// *Action: max_iops and max_mbps are pluggable database (PDB) only parameters
// and cannot be altered in non-consolidated databases.
// The max_iops and max_mbps parameters can only be
// altered from a PDB.
/
56740, 00000, "Resource plan %s does not contain mandatory group %s."
// *Cause: An attempt was made to create or set a resource manager plan that
// does not contain a consumer group mandated by the administrator.
// The specified plan has too many plan directives for the system
// to automatically add the mandatory consumer group.
// *Action: Modify the plan to contain the mandatory consumer group, or
// reduce the number of plan directives so that the system can
// automatically add the mandatory consumer group.
/
56741, 00000, "The specified plan uses multilevel management directives and cannot be set in a pluggable database."
// *Cause: An attempt was made to set a resource plan that contains
// multilevel management directives: MGMT_P2, MGMT_P3, MGMT_P4,
// MGMT_5, MGMT_P6, MGMT_P7, or MGMT_P8. Multilevel management
// directives are not supported in pluggable databases (PDBs).
// *Action: Specify a valid PDB resource plan or modify the specified plan
// to be a single level plan, using only the MGMT_P1 or
// SHARES directives.
/
56742, 00000, "cannot modify max_iops or max_mbps parameter on Oracle Exadata"
// *Cause: An attempt was made to alter the Resource Manager
// max_iops or max_mbps parameter on an Oracle Exadata system.
// *Action: The max_iops and max_mbps parameters cannot be altered on
// Oracle Exadata systems. Use Oracle Exadata I/O Resource Manager
// to manage I/Os on Oracle Exadata.
//
/
56743, 00000, "memory_min (%s) cannot exceed memory_limit (%s) in the CDB plan '%s' for the pluggable database '%s'"
// *Cause: An attempt was made to create a multitenant container database
// (CDB) plan directive where memory_min was greater than memory_limit.
// *Action: Change the CDB plan directive so that memory_min is less than
// memory_limit.
//
/
56744, 00000, "memory_min (%s) cannot exceed memory_limit (%s) in the CDB plan '%s' for the profile '%s'"
// *Cause: An attempt was made to create a multitenant container database
// (CDB) plan directive where memory_min was greater than memory_limit.
// *Action: Change the CDB plan directive so that memory_min is less than
// memory_limit.
//
/
56745, 00000, "invalid value %s for parameter %s; must be smaller than parameter %s"
// *Cause: The value for this parameter was invalid.
// *Action: Choose a value as indicated by the message.
/
56746, 00000, "invalid value %s for parameter %s; must be smaller than %s%% of parameter %s"
// *Cause: The value for this parameter was invalid.
// *Action: Choose a value as indicated by the message.
/
56747, 00000, "invalid value %s for parameter %s; must be smaller than parameter %s of the root container"
// *Cause: The value for this parameter was invalid.
// *Action: Choose a value as indicated by the message.
/
56748, 00000, "invalid value %s for parameter %s; must be smaller than %s%% of parameter %s of the root container"
// *Cause: The value for this parameter was invalid.
// *Action: Choose a value as indicated by the message.
/
56749, 00000, "invalid value %s for parameter %s; must be larger than parameter %s"
// *Cause: The value for this parameter was invalid.
// *Action: Choose a value as indicated by the message.
/
56750, 00000, "invalid value %s for parameter %s; must be larger than %s%% of parameter %s"
// *Cause: The value for this parameter was invalid.
// *Action: Choose a value as indicated by the message.
/
56751, 00000, "PQ_TIMEOUT_ACTION is set without a corresponding PARALLEL_QUEUE_TIMEOUT directive"
// *Cause: The plan directive specified a value for PQ_TIMEOUT_ACTION
// without specifying a PARALLEL_QUEUE_TIMEOUT directive.
// *Action: Specify a PARALLEL_QUEUE_TIMEOUT directive or remove the PQ_TIMEOUT_ACTION directive.
/
56752, 00000, "Oracle Database Express Edition (XE) memory parameter invalid or not specified"
// *Cause : An invalid parameter or a value more than the maximum memory allowed
// was specified
// *Action : Use the allowed parameter or reduce the memory size, upgrade
// to the Standard or Enterprise edition.
/
56753, 00000, "Calibration failed because Exadata files are not sufficiently populated."
// *Cause: On Oracle Exadata, the calibration run was terminated because the data
// files did not have a sufficient percentage of populated blocks.
// *Action: Re-run calibration after data is loaded in the data files.
/////////////////////////////////////////////////////////////////////////////
// 56800 - 56899 Reserved for DisKMoN and CELL error codes
/////////////////////////////////////////////////////////////////////////////
56800, 00000, "DSKM process died unexpectedly"
// *Cause: An explicit kill or internal error caused the death of the DSKM
// background process.
// *Action: Restart the instance.
/
56801, 00000, "ksz trace event"
// *Document: NO
// *Cause: Explicitly set.
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Turn on/off various ksz trace and debug features (documentation
// in ksz.c).
56802, 00000, "ksz test event"
// *Document: NO
// *Cause: Explicitly set.
// *Action: Set this event only under the supervision of Oracle development.
// *Comment: Turn on/off various ksz testing features (documentation
// in ksz.c).
56840, 00000, "LIBCELL API error in Master Diskmon"
// *Document: YES
// *Cause: A LIBCELL operation in Master Diskmon failed.
// *Action: Look in the $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log file for additional error information.
56841, 00000, "Master Diskmon cannot connect to a CELL"
// *Document: YES
// *Cause: A LIBCELL operation from Master Diskmon failed to create a network connection to the target CELL.
// *Action: Look in the $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log file for additional error information.
56842, 00000, "LIBCELL operation network error in Master Diskmon"
// *Document: YES
// *Cause: A LIBCELL operation in Master Diskmon failed because of a network error.
// *Action: Look in the $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log file for additional error information.
56843, 00000, "LIBCELL SKGXP error in Master Diskmon"
// *Document: YES
// *Cause: A LIBCELL operation from Master Diskmon failed because of an SKGXP network layer error.
// *Action: Look in the $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log file for additional error information.
56864, 00000, "Master Diskmon \"%s%s\" operation cannot complete because of a LIBCELL network error"
// *Document: YES
// *Cause: A LIBCELL operation between Master Diskmon and a CELL failed because of a network error.
// *Action: Look in the $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log file for additional error information.
56865, 00000, "Invalid IP address in CELLINIT.ORA"
// *Document: YES
// *Cause: One or more of the specified IP addresses in CELLINIT.ORA is not
// valid.
// *Action: Check that all IP addresses in CELLINIT.ORA are valid.
56866, 00000, "No IP parameter"
// *Document: YES
// *Cause: No IP address is set in CELLINIT.ORA.
// *Action: Check that one or more valid IP addresses are set in CELLINIT.ORA.
56867, 00000, "Cannot connect to Master Diskmon on pipe \"%s\""
// *Document: YES
// *Cause: Master Diskmon was not running or the listening pipe was deleted.
// *Action: Look at the $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log,
// $ORA_CRS_HOME/log/<hostname>/hasmsgs.log and
// $ORA_CRS_HOME/log/<hostname>/alert<hostname>.log for additional
// error information.
56868, 00000, "Duplicate IP address in CELLINIT.ORA"
// *Document: YES
// *Cause: One or more of the specified IP addresses in CELLINIT.ORA was
// repeated.
// *Action: Check that all IP addresses in CELLINIT.ORA are unique.
56870, 00000, "Attempt to register dead cell with Master Diskmon"
// *Document: YES
// *Cause: An attempt was made by a process to register a cell that is known
// to be down.
// *Action: None
/
/////////////////////////////////////////////////////////////////////////////
/ 56900 - 56919 : Reserved for pivot errors
/////////////////////////////////////////////////////////////////////////////
56900, 0000, "bind variable is not supported inside pivot|unpivot operation"
// *Cause: Attempted to use bind variables inside pivot|unpivot operation.
// *Action: This is not supported.
56901, 0000, "non-constant expression is not allowed for pivot|unpivot values"
// *Cause: Attempted to use non-constant expression for pivot|unpivot values.
// *Action: Use constants for pivot|unpivot values.
56902, 0000, "expect aggregate function inside pivot operation"
// *Cause: Attempted to use non-aggregate expression inside pivot operation.
// *Action: Use aggregate function.
56903, 0000, "sys_op_pivot function is not allowed here"
// *Cause: invalid use of sys_op_pivot function.
// *Action: Remove sys_op_pivot function.
56904, 0000, "pivot value must have datatype that is convertible to pivot column"
// *Cause: Datatype of pivot value is not convertible to the datatype of pivot
// column.
// *Action: Check and correct pivot value.
56905, 0000, "pivot|unpivot operations are not supported on lateral views"
// *Cause: An attempt was made to do a pivot or unpivot operation on a lateral
// view.
// *Action: This is not supported.
56906, 000, "pivot column or pivot value is too large"
// *Cause: Either the combined column size for multicolumn pivot was too
// large or a multicolumn pivot value was too large.
// *Action: This is not supported.
/////////////////////////////////////////////////////////////////////////////
/ 56920 - 56949 : Reserved for DBMS_DST package errors
/////////////////////////////////////////////////////////////////////////////
56920, 00000, "a prepare or upgrade window or an on-demand or datapump-job loading of a secondary time zone data file is in an active state"
// *Cause: A prepare or upgrade window was started or an on-demand or
// datapump-job loading of a secondary time zone data file was done.
// *Action: Make sure there is no active prepare or upgrade window and no
// active on-demand or datapump-job loading of a secondary time zone
// data file.
//
56921, 00000, "invalid time zone version"
// *Cause: Invalid time zone version passed.
// *Action: Check and correct the time zone version.
//
56922, 00000, "Starting a prepare window failed"
// *Cause: Error(s) occurred when starting a prepare window.
// *Action: Check alert or trace file for error(s).
//
56923, 00000, "database properties related to time zone version are not set up properly"
// *Cause: There were no database properties related to time zone version in
// dictionary table sys.props$.
// *Action: Contact Oracle Support Services.
//
56924, 00000, "prepare window does not exist"
// *Cause: There was no active prepare window.
// *Action: None.
//
56925, 00000, "Ending a prepare window failed"
// *Cause: Error(s) occurred when ending a prepare window.
// *Action: Check alert or trace file for error(s).
//
56926, 00000, "database must be in UPGRADE mode in order to start an upgrade window"
// *Cause: Database was not in UPGRADE mode.
// *Action: Restart database in UPGRADE mode.
//
56927, 00000, "Starting an upgrade window failed"
// *Cause: Error(s) occurred when starting an upgrade window.
// *Action: Check alert or trace file for error(s).
//
56928, 00000, "upgrade window does not exist"
// *Cause: There was no active upgrade window.
// *Action: None.
//
56929, 00000, "Ending an upgrade window failed"
// *Cause: Ending an upgrade window failed or there were tables
// containing TSTZ data which have not been upgraded.
// *Action: Check alert or trace file for error(s) or complete upgrading of
// tables containing TSTZ data.
//
56930, 00000, "database must be restarted before performing upgrade of user tables"
// *Cause: Database was not restarted after starting an upgrade window.
// *Action: Restart database.
//
56931, 00000, "inconsistent DST patching state found"
// *Cause: DST patching was in an inconsistent state.
// *Action: Contact Oracle Support Services.
//
56932, 00000, "\"%s\".\"%s\" does not exist"
// *Cause: Specified table name was invalid.
// *Action: Check the existence of the specified table name.
//
56933, 00000, "Table creation failed"
// *Cause: Error(s) occurred when creating the table.
// *Action: Check the error.
//
56934, 00000, "database property DST_UPGRADE_STATE for datapump job is in an inconsistent state"
// *Cause: Database property DST_UPRGRADE_STATE was not recorded correctly.
// *Action: Check the alert file.
//
56935, 00000, "existing datapump jobs are using a different version of time zone data file"
// *Cause: An attempt was made from a datapump job to request a different
// version of time zone data file from the one used by existing
// datapump jobs.
// *Action: Wait until existing datapump jobs unload the secondary time zone
// data file.
//
56936, 00000, "datapump jobs are utilizing secondary time zone data file"
// *Cause: An on-demand loading of secondary time zone data file was requested
// when there was a secondary time zone data file already loaded in
// the database utilized by existing datapump jobs.
// *Action: Wait until existing datapump jobs unload the secondary time zone
// data file.
//
56937, 00000, "failed to load the secondary time zone data file"
// *Cause: Attempt to load the secondary timezone data file failed.
// *Action: Check alert or trace files for error(s).
//
56938, 00000, "no secondary time zone data file being loaded by on-demand or a datapump job"
// *Cause: There was no secondary timezone data file being loaded by on-demand
// or a datapump job.
// *Action: None.
//
56939, 00000, "failed to unload the secondary time zone data file"
// *Cause: Attempt to unload the secondary timezone data file failed.
// *Action: Check alert or trace files for error(s).
//
/////////////////////////////////////////////////////////////////////////////
/ 56950 - 56970 : Reserved for SQL Diagnostic Advisor
/////////////////////////////////////////////////////////////////////////////
56950, 00000, "Invalid value for incident identifier"
// *Cause: Invalid incident identifier argument passed.
// *Action: Check and correct the identifier
/////////////////////////////////////////////////////////////////////////////
/ 56971 - 56990 : Reserved for SQL Test Case Builder
/////////////////////////////////////////////////////////////////////////////
56971, 00000, "Invalid set of export options"
// *Cause: The options specified are inconsistent
// *Action: Check and a consistent set of option parameters
56972, 00000, "referenced file not found"
// *Cause: One of the file specified in the test case package is mising
// *Action: rebuild the SQL test case or make sure that all the referenced files
// are readable and located in the same directory as the SQL test
// case manifest.
56973, 00000, "import options do not match export options"
// *Cause: The import options specified do not match the export options
// *Action: Check that import is being invoked with the same values for
// options like export environment, export data and export metadata
56974, 00000, "Invalid set of import options"
// *Cause: The import options specified are inconsistent
// *Action: Check that import options are consistent and have valid values
56975, 00000, "invalid SQL_ID"
// *Cause: The SQL_ID specified was incorrect.
// *Action: Cross check SYS.V$SQL for the existence of SQL_ID.
56976, 00000, "invalid export options: %s"
// *Cause: One or more export options were inconsistent.
// *Action: Check that export options are consistent and have valid values.
56977, 00000, "invalid import options: %s"
// *Cause: One or more import options were inconsistent.
// *Action: Check that import options are consistent and have valid values.
56978, 00000, "TCB root directory does not exist"
// *Cause: The root directory for Test Case Builder (TCB) does not exist.
// *Action: Create the TCB root directory or specify any other directory during export of SQL Test Case.
/////////////////////////////////////////////////////////////////////////////
/ 57000 - 58999 are reserved for TimesTen IMDB errors
/////////////////////////////////////////////////////////////////////////////
/
57000, 00000, "TimesTen IMDB error: %s"
// *Document: YES
// *Cause: An error occurred during a TimesTen operation.
// *Action: Look up the error code in the TimesTen error documentation to
// diagnose.
//
57005, 00000, "TimesTen Grid transient transaction failure: %s"
// *Document: YES
// *Cause: A transaction failed because a TimesTen Grid element was
// temporarily unreachable.
// *Action: Roll back the transaction and immediately retry.
//
57006, 00000, "TimesTen Grid transaction failure: %s"
// *Document: YES
// *Cause: A transaction failed because a TimesTen Grid element was
// temporarily unreachable.
// *Action: Roll back the transaction, wait for the element to recover,
// and retry the transaction. Element recovery may require
// administrator action.
//
57007, 00000, "TimesTen Grid transient statement failure: %s"
// *Document: YES
// *Cause: A statement failed because a TimesTen Grid element was
// temporarily unreachable.
// *Action: Immediately retry the current statement.
//
57008, 00000, "TimesTen Grid statement failure: %s"
// *Document: YES
// *Cause: A TimesTen Grid element is temporarily unavailable.
// *Action: Wait for the element to recover and retry the current statement.
// Element recovery may require administrator action.
//
/============================================================================
/ 15000 - 15499 Reserved for Automatic Storage Management [continued from]
/ 59000 - 59999 Reserved for Automatic Storage Management
/
/ Begin messages for Automatic Storage Management
/============================================================================
/
/============================================================================
/ 59000 - 59299 ASM run-time error messages
/============================================================================
59000, 00000, "not all rebalance phases were run"
// *Cause: The previous rebalance for the group did not run all of the phases.
// *Action: See GV$ASM_OPERATION for more details. Run all rebalance phases
// using the ALTER DISKGROUP REBALANCE command.
//
59001, 00000, "Disk '%s' must be online before disk '%s'."
// *Cause: An attempt was made to online a disk that contains old copies
// of the data present in another offline disk.
// *Action: Online the disks in the correct order. FORCE option may be
// used to override this check.
//
59002, 00000, "Disk revalidation failed for ASM disk group '%s' on instance %s due to ORA-%s."
// *Cause: The disk revalidation failure could be due to various reasons.
// Signaling ORA-15020 during discovery was a probable one. See the
// alert log for more details.
// *Action: Ensure that the disks in operation are visible to all the nodes in
// the cluster before issuing a retry.
59003, 0000, "database is not prepared for split."
// *Cause: Split was issued on a database which is either not prepared or
// did not complete the last time.
// *Action: Prepare the database before issuing split on it or drop the
// existing mirror copy and then retry the split mirror operations.
//
59004, 0001, "No rebalance is running for group %s."
// *Cause: An attempt was made to modify the property of a rebalance that
// was not running.
// *Action: Issue the ALTER DISKGROUP REBALANCE command without the MODIFY
// keyword to schedule another rebalance.
59005, 00000, "Oracle ASM IOServer functionality is not supported on this platform."
// *Cause: This platform did not support ASM IOServer functionality.
// *Action: Refer to the documentation for the list of platforms that support
// Oracle ASM IOServer functionality and consider moving to one of
// those platforms.
//
59006, 00000, "connection request from stale database instance is rejected."
// *Cause: The database instance was attempting to fail over from a stale
// IOServer cluster.
// *Action: Restart the database instance to initiate a new connection.
//
59007, 00000, "cannot find a usable network from the client"
// *Cause: The database instance was not using any of the configured ASM
// networks.
// *Action: Check the ASM network configuration in the database instance.
59008, 00000, "All configured ASM networks are unusable."
// *Cause: All configured ASM networks encountered an error. ASM IOServer
// was unable to proceed.
// *Action: Check the status of the configured ASM network interfaces. Restart
// the ASM IOServer instance after the interfaces become operational.
59009, 00000, "ASM IOServer instance is not ready to accept clients."
// *Cause: ASM IOServer instance was not ready to accept clients.
// *Action: Execute 'alter system enable client access' for ASM IOServer
// instance to accept clients.
59010, 00000, "cannot SHUTDOWN ASM IOServer instance with connected client %s."
// *Cause: A SHUTDOWN command was issued to an ASM IOServer instance that had
// one or more connected clients.
// *Action: Stop all clients that are using this ASM IOServer instance and
// retry the SHUTDOWN command. Alternatively, use the SHUTDOWN ABORT
// command to force disconnection with all the clients.
59011, 00000, "operation failure for group %s because too many disks are offline"
// *Cause: Too many disks were offline in the disk group.
// *Action: Ensure that the disks are online and retry the operation.
//
59012, 00000, "Disk %0!s uses an invalid physical sector size (%1!s)."
// *Cause: The disk used a physical sector size value that is not standard or
// is not currently supported.
// *Action: The disk cannot be used for an ASM disk group.
59013, 00000, "Disk %0!s uses an invalid logical sector size (%1!s)."
// *Cause: The disk used a logical sector size value that is not standard or is
// not currently supported.
// *Action: The disk cannot be used for an ASM disk group.
59014, 0000, "file %0!s in disk group %1!s was not prepared for split"
// *Cause: The specified file was not prepared for split.
// *Action: Check the accompanying error messages for more information about
// the reason for the failure.
59015, 0000, "Oracle ASM scrubbing is disabled."
// *Cause: An attempt was made to perform Oracle ASM scrubbing but it was
// disabled.
// *Action: Enable Oracle ASM scrubbing.
59016, 0000, "Disk group %s cannot be mounted due to invalid symbols"
// *Cause: A mount operation was attempted for a disk group that contains
// invalid characters in its name. Starting in version 12.2.0.2.0,
// disk group names should only contain alphanumeric characters and
// the underscore character.
// *Action: Use the 'renamedg' tool to change the disk group name to a valid
// name. Afterwards, change the names of the disks by mounting the
// disk group in restricted mode and using the ASM SQL command 'ALTER
// DISKGROUP name RENAME DISKS ALL'.
59017, 0000, "Oracle ASM scrubbing is stopping a previous operation."
// *Cause: The system cannot accept new scrubbing operations if a previous one
// is being stopped.
// *Action: Wait until the previous Oracle ASM scrubbing operation stops
// completely before initiating a new one.
59018, 0000, "Oracle ASM scrubbing requires an Allocation Unit size of at least 1 MB."
// *Cause: The operation was not executed because the Allocation Unit was less
// than 1 MB.
// *Action: Run the operation on a disk group with an Allocation Unit of at
// least 1 MB.
59019, 0000, "cannot start SCRB process"
// *Cause: The ASM Scrubbing Master (SCRB) process failed during startup.
// *Action: Review the alert log to find out the reason behind the process
// startup failure.
59020, 0000, "dropping mirror copy '%0!s' in disk group '%1!s' is already in progress"
// *Cause: The drop mirror copy was already issued on the specified file
// group.
// *Action: Wait for the previous drop mirror copy to complete. Check the ASM
// alert log or check that the corresponding file group is deleted
// using the V$ASM_FILEGROUP view.
59021, 0000, "drop of child file '%0!s' in disk group '%1!s' is not allowed"
// *Cause: The operation failed because child file deletion was attempted.
// *Action: Child files can be deleted collectively only as part of drop mirror
// copy operation.
59022, 0000, "dropping mirror copy '%0!s' in disk group '%1!s' failed as prepare is not complete"
// *Cause: Prepare of mirror copy has not completed
// *Action: Wait for the prepare mirror copy to complete. Check the ASM
// alert log or check that the split status of the file group using
// the V$ASM_FILEGROUP view.
59023, 0000, "command requires attribute '%0!s' to be set to '%1!s'"
// *Cause: The disk group was still running the necessary background
// operations preventing the attribute <name> from setting to
// value <value>, which is a prerequisite for the command.
// *Action: Confirm that all disks in the disk group are online, and wait
// until the attribute is set to the proper value. The attribute
// may not get set to the proper value if any of the disks in
// the disk group are offline. This may take a while.
//
59024, 0000, "dropping mirror copy '%0!s' in disk group '%1!s' failed as the file split is complete"
// *Cause: Split of mirror copy has completed.
// *Action: None.
59025, 0000, "creation of mirror copy for database '%0!s' failed"
// *Cause: Another mirror copy for the database existed when the operation was
// attempted.
// *Action: Create another database using the existing mirror copy first or
// drop the existing mirror copy and then retry the operation.
//
59026, 0000, "dropping file group '%0!s' in disk group '%1!s' failed as the file group has prepared mirror copies"
// *Cause: Dropping a file group with prepared mirror copies is not allowed.
// *Action: Drop all the prepared mirror copies and try again.
//
59027, 0000, "file group redundancy cannot be modified when there is a mirror copy"
// *Cause: A mirror copy for the database existed or the disk group was still
// running the necessary background operations preventing the file
// group redundancy change.
// *Action: Create another database using the existing mirror copy or drop the
// existing mirror copy and wait for the rebalance operations to
// complete. Then retry the operation.
//
59028, 0000, "rebalance did not complete after the last mirror split operation on database '%0!s'"
// *Cause: Rebalance after the last mirror split operation was either still
// running or not scheduled yet.
// *Action: If a rebalance is already running allow it to complete, otherwise
// issue a new one.
//
59029, 0000, "All ASM disks in %0!s are already online or being brought online."
// *Cause: An attempt was made to bring disks online that were either already
// online or were being brought online.
// *Action: Check the status of the disks before changing the ONLINE statement
// to exclude the disks in the failure group or disk group.
//
59030, 0000, "disk group '%0!s' containing file group '%1!s' has too many offline disks"
// *Cause: A mirror split operation failed because the disk group containing
// the files had insufficient number of online disks. This could
// prevent some files in the target database from being opened. The
// operation failed early to give the administrator a chance to fix
// the errors.
// *Action: Ensure that the disk group has the required number of disks online
// and then retry the command.
//
59031, 00000, "operation cannot be run concurrently with other mirror split operations on mirror copy '%0!s' in disk group '%1!s' "
// *Cause: Another conflicting Mirror Split operation was already running.
// *Action: Retry after the conflicting Mirror Split operation has finished.
//
59032, 0000, "rebalance did not complete after the last mirror split or change redundancy operation"
// *Cause: The rebalance operation after the last mirror split operation or
// change redundancy was either still running or not scheduled yet.
// *Action: If a rebalance is already running, then allow it to complete;
// otherwise, issue the rebalance operation.
//
59033, 0000, "failed to start Oracle ASM instance because it was unable to open SPFILE '%0!s'"
// *Cause: An attempt to start the Oracle ASM instance failed because the ASM
// server parameter file (SPFILE) could not be opened. The SPFILE was
// configured in the indicated disk group. One or more of the disks in
// the disk group were inaccessible. This was likely due to the remote
// node or nodes being inactive.
// *Action: Issue the 'olsnodes' command to retrieve the list of nodes in the
// cluster. Start up all the remote nodes in the cluster that were
// previously inactive. Issue the 'crsctl start cluster' command on
// this node and verify that the Oracle ASM instance is active.
59035, 00000, "HARDCHECK error during I/O"
// *Cause: A Hardware Assisted Resilient Data (HARD) check error was
// encountered by ASM Rebalance (ARB) process during I/O operations.
// *Action: See the alert log for more information. Reconnect to the database
// or the ASM instance. If the process termination resulted in
// instance termination, restart the instance.
/============================================================================
/ 59300 - 59399 ASM SQL usage error messages
/============================================================================
59300, 00000, "missing or invalid site name"
// *Cause: The command did not specify a valid site name.
// *Action: Specify a valid site name.
//
59301, 00000, "incorrect SITE token usage"
// *Cause: Site names were provided for some disks in the SQL statement and
// missing for others.
// *Action: Either specify site names for all of the disks or none in the SQL
// statement and retry the operation.
//
59302, 0000, "The attribute %s must be %s or higher."
// *Cause: An attempt was made to set an attribute to a version that was lower
// than the minimum supported.
// *Action: Set the attribute to at least the minimum supported version.
// Alternatively lower the minimum supported version and try again.
//
59303, 0000, "The attribute %s (%s) of the diskgroup being mounted should be %s or higher."
// *Cause: An attempt was made to mount a diskgroup whose compatibility was lower
// than the minimum supported.
// *Action: Advance the diskgroup compatibility by mounting it in restricted mode
// OR lower the minimum supported compatibility and try again.
//
59304, 00000, "external and global users are not supported for ASM"
// *Cause: A user type not supported by ASM was supplied.
// *Action: Check the Oracle ASM documentation that external and global users
// are not supported for ASM.
//
59305, 00000, "The disk group being mounted is incompatible with this software version."
// *Cause: An attempt was made to mount a disk group using a software
// version that is incompatible with the disk group.
// *Action: Contact Oracle Support Services.
//
59306, 00000, "The parameter '%s' is invalid."
// *Cause: The value of the parameter was invalid.
// *Action: Provide a valid value of the parameter.
//
59307, 00000, "The disk group redundancy is not external."
// *Cause: An attempt was made to rename the disk fail group in a disk group
// whose redundancy type was not external.
// *Action: Specify a disk group whose redundancy type is external.
//
59308, 0002, "The disk '%s' cannot be assigned to a site because the disk group '%s' contains Cluster Synchronization Services voting files."
// *Cause: An attempt to assign a site to a disk failed because the disk group
// contained Cluster Synchronization Services (CSS) voting files.
// *Action: Move the CSS voting files to a different disk group using the
// command 'crsctl replace votedisk' and retry the operation.
//
59309, 00001, "Failure group name '%s' is already used by an existing ASM disk."
// *Cause: The specified failure group name was already used in this diskgroup.
// *Action: Specify a different failure group name.
//
59311, 0000, "The specified ASM instance '%s' does not exist."
// *Cause: The specified ASM instance did not exist or was terminated.
// *Action: Specify a valid ASM instance name.
//
59312, 0001, "Disk '%s' cannot be assigned to a site because it is an Oracle Exadata disk."
// *Cause: An attempt to assign a site to an Oracle Exadata disk failed because
// the operation is not allowed in Oracle Exadata.
// *Action: Run the command 'cellcli -e alter cell siteName' to update the cell
// site information.
//
59313, 0000, "All mirrors of the block are lost, likely due to multiple storage failures."
// *Cause: There were multiple failures in the storage subsystem. All redundant
// copies of the block were lost and Oracle wrote the hexadecimal value
// BADFDA7A into the block location of the lost block to signify
// that the block data could not be recovered from a redundant copy.
// *Action: Check the system logs and storage logs to identify the failure
// that led to the lost block.
//
59314, 00000, "file type not supported for the operation"
// *Cause: The operation did not support files of the given type.
// *Action: Retry the operation with a file of supported type.
//
59315, 00000, "Parity is not supported for file '%0!s' with type '%1!s'."
// *Cause: The given file type did not support the creation of parity files.
// *Action: Retry creating the parity files with a supported file type.
//
59316, 00000, "ASM software is incompatible with disk group %s due to missing patch %s"
// *Cause: The ASM software was not compatible with the disk group.
// *Action: Action: Apply the missing patch and retry the operation.
//
59317, 00000, "client %0!s software is incompatible with disk group %1!s due to missing patch %2!s"
// *Cause: The client software was not compatible with the disk group.
// *Action: Apply the missing patch on corresponding client software and
// retry the operation.
//
59318, 00000, "ASM software is incompatible with disk group %s COMPATIBLE.ASM %s"
// *Cause: The ASM software did not support the attribute value for COMPATIBLE.ASM.
// *Action: Check alert log to identify the missing patches, apply the patches,
// and retry the operation. Or, advance COMPATIBLE.ASM to a version
// that is supported by this software.
//
59319, 00000, "database software is incompatible with disk group %s COMPATIBLE.RDBMS %s"
// *Cause: The specified value for COMPATIBLE.RDBMS was not compatible with
// one or more clients.
// *Action: Check the ASM alert log for information about the clients and missing
// patches, apply the patches on the corresponding database software,
// and retry the operation.
//
59320, 00000, "client %0!s software is incompatible with disk group %1!s patch %2!s"
// *Cause: The client software was not compatible with the specified patch.
// *Action: Apply the missing patch on corresponding client software and
// retry the operation.
//
59321, 00000, "ASM software is incompatible with disk group %s patch %s"
// *Cause: The ASM software did not support enabling the specified patch.
// *Action: Apply the missing patch and retry the operation.
//
59322, 00000, "database software is incompatible with disk group %s patch %s"
// *Cause: The specified patch was not compatible with one or more clients.
// *Action: Check the ASM alert log for information about the clients and
// missing patches, apply the patches on corresponding database
// software, and retry the operation.
//
59323, 00000, "cannot alter exclusive instance mode with more than once instance running"
// *Cause: There was at least one other running ASM instance.
// *Action: Ensure that there is only one ASM instance when running the command.
//
59324, 00000, "cannot alter exclusive instance mode outside of rolling migration or rolling patch"
// *Cause: ASM cluster was not in rolling migration or rolling patch.
// *Action: ASM cluster needs to be in rolling migration or rolling patch.
//
59325, 00000, "cannot start multiple ASM instances under exclusive mode"
// *Cause: There was at least one other running ASM instance, and the ASM
// cluster was in exclusive mode.
// *Action: Ensure that the ASM cluster is not in exclusive mode when trying to
// bring up another ASM instance.
//
/============================================================================
/ 59400 - 59499 ASM tracing and testing error messages
/============================================================================
59400, 0000, "Internal ASM event: retry due to VAM conversion"
// *Document: NO
// *Cause: A cache transaction must be retried due to VAM becoming active.
// *Action: Internal event.
//
59401, 0000, "Internal ASM event: for purpose of backport"
// *Document: NO
// *Cause: An attempt was made to replace underscore parameter in transaction
// which normally cannot be backported.
// *Action: Internal event.
//
/============================================================================
/ 59500 - 59599 Flex ASM and Member Cluster error messages
/============================================================================
59500, 0000, "unable to create member cluster '%s' in the absence of at least one disk group with the ACCESS_CONTROL.ENABLED attribute set to TRUE"
// *Cause: An attempt was made to configure a member cluster when there was
// no mounted disk group with the ACCESS_CONTROL.ENABLED attribute set
// to TRUE.
// *Action: Set the ACCESS_CONTROL.ENABLED attribute to TRUE on an existing
// mounted disk group, mount a disk group that already has the
// ACCESS_CONTROL.ENABLED attribute set to TRUE, or create a disk
// group with the ACCESS_CONTROL.ENABLED attribute set to TRUE. Retry
// the operation.
//
59501, 00000, "failed to register database with IOServer instance"
// *Cause: The database instance failed to register with a valid IOServer
// instance.
// *Action: Check the alert log to identify the underlying reason for the
// failure and take the suggested corrective action.
//
59502, 0000, "relocate client to %s is already in progress"
// *Cause: Another relocate client command was in progress.
// *Action: Retry the command after the initial relocate client command
// completes.
//
59503, 0001, "client '%s' not allowed to reconnect"
// *Cause: The client in Standard mode tried to reconnect to an ASM
// instance that did not support Flex mode.
// *Action: Check the ASM instance configurations within the cluster to match
// the client mode.
//
59504, 0003, "rejecting a request originating from site '%s' to OFFLINE a disk '%s' configured in site '%s'"
// *Cause: The request to OFFLINE a disk was rejected by the ASM instance
// because the request was issued from a site that was different
// from the site in which the disk was configured.
// *Action: Retry the request from the site in which the disk is configured.
//
59505, 0002, "instance '%s' shutting down on site '%s' due to rejected OFFLINE request"
// *Cause: The instance terminated because the storage was inaccessible from
// the site requesting the disk OFFLINE.
// *Action: Issue the command 'crsctl query cluster sites <site_name>' to
// retrieve the status of the indicated site. Address the storage
// accessibility issues if the indicated site is in a QUARANTINED
// state. Issue the command
// 'crsctl modify cluster site <site_name> -s rejuvenate' to set the
// status to ONLINE after the storage access has been restored.
//
59506, 0000, "database process in a network read for too long"
// *Cause: A process on database instance connected to an ASM instance was
// in a SQL*Net read for too long. Possible reasons include failure of
// the node on which ASM instance was running or the communication
// channel disruption. This was detected by the Fence Monitor Process
// (FENC) or the ASM Background Process (ASMB) and the call was
// interrupted.
// *Action: Usually none, as the database instance fails over to another
// available ASM instance. If the problem keeps recurring, contact
// Oracle Support Services.
//
59507, 0000, "mismatch of parameter '%0!s' between database and ASM instance '%1!s'"
// *Cause: The value for the parameter was different in the database instance
// and in the ASM instance to which it was connected.
// *Action: Set the parameter to the same value in both the instances.
//
59508, 0000, "invalid GUID '%s' specified"
// *Cause: The operation was rejected because the supplied Globally Unique
// Identifier (GUID) was syntactically invalid.
// *Action: Retry the command specifying the Globally Unique Identifier (GUID)
// as a text string of 32 hexadecimal digits (0-f) without a hyphen (-)
// character or the hexadecimal literal prefix (0x). Refer to the
// command inline help or product documentation for more information.
//
59509, 0000, "failed to create member cluster '%0!s' because the specified GUID '%1!s' is already configured"
// *Cause: An attempt to add the indicated member cluster with the indicated
// Globally Unique Identifier (GUID) was rejected because a member
// cluster with that GUID was already defined.
// *Action: Execute the command 'asmcmd lscc' to list the existing member
// clusters and cluster GUIDs. Retry the original command with a
// cluster GUID that has not already been configured.
//
59510, 0000, "unable to modify member cluster '%s'"
// *Cause: An attempt to modify the member cluster failed.
// *Action: Check the alert logs and trace files of the Oracle ASM instance for
// more information about the reason for the failure, as well as check
// the accompanying error messages.
//
59511, 00000, "member cluster '%0!s' already configured with disk access mode '%1!s'"
// *Cause: An attempt to modify the member cluster failed because it was
// already configured with the specified disk access mode.
// *Action: No action is required.
//
59512, 0000, "The specified Oracle IOServer instance '%0!s' does not exist."
// *Cause: The specified Oracle IOServer instance did not exist or
// was terminated.
// *Action: Issue the 'srvctl status ioserver' command to list the active
// Oracle IOServer instances. Specify a valid Oracle IOServer
// instance name and retry the command.
//
59513, 0000, "rejecting a request to relocate the client to %s"
// *Cause: The request to relocate a client was rejected because either the
// client or the ASM instance with the client connection
// was not running in Flex Mode.
// *Action: Check the configuration of both instances.
//
59514, 0000, "The command is not supported on a storage server."
// *Cause: An attempt was made to run a command that was not supported on
// a storage server.
// *Action: Rerun the command on a member cluster.
/
/============================================================================
/ 59600 - 59699 ASM Flex Disk Group (File Group, Quota Group) error messages
/============================================================================
59600, 0000, "file %s has too many mirror copies; %s needed, %s allowed"
// *Cause: The specified file had too many mirror copies when the
// requested change was applied.
// *Action: Retry the command using a lower redundancy scheme, or reduce the
// existing redundancy level (if preparing a mirror split), or wait
// for the BALANCE phase of the rebalance operation to complete.
//
59601, 0000, "file group redundancy cannot be modified when associated with a volume"
// *Cause: An attempt was made to modify the redundancy of a file group which
// was associated with an ASM volume and contained at least one file.
// *Action: Drop the ASM volume associated with the file group and retry the
// operation.
//
59602, 00000, "Moving ASM internal files to a file group is not allowed."
// *Cause: An attempt was made to execute an ALTER DISKGROUP MOVE FILE TO
// FILEGROUP statement on a metadata file used by ASM to manage the
// disk group.
// *Action: This action is not allowed.
//
59603, 00000, "operation requires all disks in disk group %s to be online"
// *Cause: An attempt was made to modify the redundancy of a file group
// when some disks were offline.
// *Action: Drop the offline disks and wait for the rebalance operations to
// complete, or online the offline disks and wait for the online to
// complete. Then retry the operation.
//
59604, 00000, "offline disks encountered during rebalance of disk group '%s'"
// *Cause: Rebalance was run in the presence of offline disks.
// *Action: Bring the offline disks online.
//
59605, 0000, "file '%s' not available; file group '%s' has too many disks offline"
// *Cause: A file identify operation failed because the file group specified
// was no longer available.
// *Action: Verify that all disks in this disk group are online or dropped
// and retry the command.
//
59606, 0000, "cannot change redundancy of individual file types in file groups associated with a volume"
// *Cause: An attempt was made to modify the redundancy of one or more file
// types in a file group associated with an ASM volume.
// *Action: Change the redundancy of the entire file group and not that of
// individual file types.
//
59607, 0000, "COMPATIBLE.CLIENT is a read-only property by default"
// *Cause: An attempt was made to modify the COMPATIBLE.CLIENT property of
// a file group without the FORCE option. COMPATIBLE.CLIENT property
// cannot be downgraded under any circumstances so caution should be
// exercised when manually modifying this property.
// *Action: Use the FORCE option to override this check.
//
59608, 0000, "FORCE option cannot be used for file group property '%s'"
// *Cause: An attempt was made to use the FORCE option on a property that
// does not allow it.
// *Action: Remove the FORCE option and try again.
//
59609, 0000, "cannot move a file that has prepared mirror copies"
// *Cause: An attempt was made to move a file that has a prepared mirror copy.
// *Action: Create another database using the existing mirror copy or drop the
// existing mirror copy and wait for the rebalance operations to
// complete. Then, retry the operation.
//
/============================================================================
/ 59700 - 59749 ASM Extended Disk Group error messages
/============================================================================
59700, 0000, "Failgroup %s already belongs to site %s"
// *Cause: An attempt was made to add the specified failgroup to more than
// one site.
// *Action: Retry the operation providing the correct failgroup name and the
// site name while specifying the disk.
//
59701, 0000, "Incorrect number of data sites %s specified. Maximum allowed: %s."
// *Cause: An attempt was made to create an extended redundancy disk group with
// an invalid number of sites.
// *Action: Retry the operation specifying valid number of sites in the
// disk group.
//
59702, 0000, "Incorrect number of quorum sites %s specified. Maximum allowed: %s."
// *Cause: An attempt was made to create an extended redundancy disk group with
// an invalid number of sites.
// *Action: Retry the operation specifying valid number of sites in the
// disk group.
//
59703, 00000, "Inconsistent site information in disk '%s'"
// *Cause: The site information stored in the disk header did not match
// disk group information.
// *Action: Drop the disk from the disk group or provide a site name that
// matches the site stored in the disk header.
//
59704, 00000, "command requires at least %s data sites and %s quorum sites, discovered %s data sites and %s quorum sites"
// *Cause: An insufficient number of sites were specified and discovered when
// creating an extended redundancy disk group.
// *Action: Check that the command specifies the required number of data sites
// and quorum sites, and that all of the specified disks are
// discovered by ASM. A query of the V$ASM_DISK fixed view shows
// the disks discovered by ASM.
//
59705, 00000, "Dropping a site is not allowed."
// *Cause: An attempt was made to drop a site.
// *Action: Set the disks of the given site offline with 'ALTER DISKGROUP <dg>
// OFFLINE DISK <disk>' command.
//
59706, 00000, "The specified allocation unit size '%s' is less than the minimum required for extended disk groups."
// *Cause: Extended disk groups required the allocation unit size to be
// at least 4M.
// *Action: Change the allocation unit size to at least 4M and retry.
//
59707, 00000, "Site \"%s\" does not exist in disk group \"%s\"."
// *Cause: The specified name did not match the site of any disks
// in the disk group. This usually indicates that the site name
// was specified incorrectly.
// *Action: Check the site name.
//
59708, 0002, "Cluster site operation failed with error %s.\n%s"
// *Cause: This is an internal error.
// *Action: Check the accompanying error messages. Contact Oracle Support
// Services.
//
59709, 00000, "No site identified for the disk %s"
// *Cause: The disk did not belong to any site.
// *Action: Specify the site information in the SQL command.
// In the case of an ASM appliance, cellcli command can also be used
// to record the site information for the disk. For non-appliance,
// asmcmd can be used.
//
59710, 0000, "site information mismatch between disk group %s and disk %s"
// *Cause: The site information of the specified disk did not match with the
// existing disks in the disk group.
// *Action: If the site information is associated with the existing disks in
// the disk group, then specify the site information for the new disk.
// If the site information is not associated with the existing disks
// in the disk group, then do not specify the site information for
// the new disk.
//
59711, 0001, "The site identified by GUID '%s' does not exist."
// *Cause: An attempt to retrieve a site failed because there wasn't a
// configured site using the indicated Globally Unique Identifier.
// *Action: Add the indicated site using the command 'crsctl add cluster site
// <site> -guid <guid>'. Retry the original command. If retrying does
// not work, contact Oracle Support Services.
//
59712, 0001, "The site identified by site name '%s' does not exist."
// *Cause: An attempt to retrieve a site failed because there wasn't a
// configured site using the indicated site name.
// *Action: Add the indicated site using the command 'crsctl add cluster site
// <site>'. Retry the original command. If retrying does not work,
// contact Oracle Support Services.
//
59713, 00000, "The site name '%s' does not exist in the disk group '%s'."
// *Cause: An attempt was made to add a disk with a new site name to a disk
// group, which is not allowed.
// *Action: Change the site name to an existing one in the disk group and retry.
//
59714, 0001, "invalid site name '%s' specified."
// *Cause: An invalid site name was supplied.
// *Action: Specify a site name which is at least one character but no more
// than 15 characters in length. The cluster name must be
// alphanumeric, it cannot begin with a numeric character, and it may
// contain hyphen (-) characters. However, it cannot end with a
// hyphen (-) character.
//
59715, 0000, "missing site information in disk group '%s'"
// *Cause: The site information was not present in all the disks of the
// disk group.
// *Action: Specify sites for the disks using the 'asmcmd rename' command or
// using SQLPLUS and retry the operation.
//
59716, 0000, "dropping all disks of the quorum site is not allowed"
// *Cause: Dropping of the specified disks resulted in the loss of the quorum
// site. If only a subset of disks in the quorum site are specfied, then
// check the state of other disks in the V$ASM_DISK view.
// *Action: Modify the command to retain at least one disk in the quroum site
// and retry the operation.
//
59717, 0000, "rebalance could not complete due to an unavailable site in disk group '%s'"
// *Cause: At least one of the sites had each disk in either dropping or
// forcing state.
// *Action: Undrop the dropping disks or add disks to the site.
//
59718, 0000, "One or more disks are identified with a foreign site GUID '%s'."
// *Cause: The indicated site GUID was not associated with any of the
// configured sites.
// *Action: Execute the command 'crsctl query cluster site -all' to list the
// existing sites. Associate the indicated site GUID with a site
// using 'crsctl modify cluster site <site> -addguid <guid>' and
// retry the operation.
//
59719, 0000, "disk group '%s' mounted but contains foreign site GUIDs"
// *Cause: An attempt was made to mount a disk group with foreign site
// GUIDs.
// *Action: This is a warning. Examine the accompanying error messages
// for details.
//
59720, 00000, "data sites in disk group %s have a different number of fail groups."
// *Cause: An attempt was made to create a disk group with a different number of
// fail groups at each data site.
// *Action: Ensure that the data sites have an equal number of fail groups and try
// again.
//
/============================================================================
/ 59750 - 59799 ASM appliance (ODA, EXADATA) error messages
/============================================================================
/============================================================================
/ 59800 - 59819 ASMLIB related error messages
/============================================================================
59800, 00000, "active use of disk '%s' precludes its label clear"
// *Cause: A LABEL CLEAR command specified a disk that was in use.
// *Action: Dismount the disk group that is using this disk and retry the
// the LABEL CLEAR command. Query the V$ASM_CLIENT
// fixed view in an ASM instance or use ASMCMD LSOF to list active
// clients.
//
59801, 00000, "ASM Filter Driver is not configured in the system."
// *Cause: An ASM Filter Driver command was run without either an ASM Filter
// Driver library present or kernel driver loaded.
// *Action: Execute the command ASMCMD AFD_STATE to find the status of
// an ASM Filter Driver.
//
/============================================================================
/ 59820 - 59849 ASM Volume Messages
/============================================================================
/////////////////////////////////////////////////////////////////////////////
/ 60000 - 60999 are reserved for SPACE MANAGEMENT
/////////////////////////////////////////////////////////////////////////////
//
60000, 00000, "SECUREFILE block checking fault injection event"
// *Document: NO
// *Cause: This is an internal debugging event only
// *Action65068: N/A
//
60001, 00000, "adding (%s) blocks to save undo segment in tablespace %s with MAXSIZE (%s)"
// *Document: YES
// *Cause: Save undo for the offline tablespace at segment MAXSIZE.
// *Action: Check the storage parameters for the system tablespace. The
// tablespace needs to be brought back online so the undo can be
// applied.
//
60002, 00000, "adding (%s) blocks to temporary segment in tablespace %s with MAXSIZE (%s)"
// *Document: YES
// *Cause: Extending a temporary segment violated MAXSIZE limit.
// *Action: Increase the MAXSIZE limit and retry command.
//
60003, 00000, "adding (%s) blocks to table %s.%s partition %s with MAXSIZE (%s)"
// *Document: YES
// *Cause: Extending a table partition violated MAXSIZE limit.
// *Action: Increase the MAXSIZE limit and retry command.
//
60004, 00000, "adding (%s) blocks to table %s.%s with MAXSIZE (%s) "
// *Document: YES
// *Cause: Extending a table violated MAXSIZE limit.
// *Action: Increase the MAXSIZE limit and retry command.
//
60005, 00000, "adding (%s) blocks to cluster %s.%s with MAXSIZE (%s)"
// *Document: YES
// *Cause: Extending a cluster violated MAXSIZE limit.
// *Action: Increase the MAXSIZE limit and retry command.
//
60006, 00000, "adding (%s) blocks to index %s.%s partition %s with MAXSIZE (%s)"
// *Document: YES
// *Cause: Extending an index partition violated MAXSIZE limit.
// *Action: Increase the MAXSIZE limit and retry command.
//
60007, 00000, "adding (%s) blocks to index %s.%s subpartition %s with MAXSIZE (%s)"
// *Document: YES
// *Cause: Extending an index subpartition violated MAXSIZE limit.
// *Action: Increase the MAXSIZE limit and retry command.
//
60008, 00000, "adding (%s) blocks to index %s.%s with MAXSIZE (%s)"
// *Document: YES
// *Cause: Extending an index violated MAXSIZE limit.
// *Action: Increase the MAXSIZE limit and retry command.
//
60009, 00000, "adding (%s) blocks to LOB segment %s.%s partition %s with MAXSIZE (%s)"
// *Document: YES
// *Cause: Extending a LOB segment violated MAXSIZE limit.
// *Action: Increase the MAXSIZE limit and retry command.
//
60010, 00000, "adding (%s) blocks to LOB segment %s.%s with MAXSIZE (%s)"
// *Document: YES
// *Cause: Extending a LOB segment violated MAXSIZE limit.
// *Action: Increase the MAXSIZE limit and retry command.
//
60011, 00000, "adding (%s) blocks to lob segment %s.%s subpartition %s with MAXSIZE (%s)"
// *Document: YES
// *Cause: Extending a LOB segment violated MAXSIZE limit.
// *Action: Increase the MAXSIZE limit and retry command.
//
60012, 00000, "adding (%s) blocks to table %s.%s subpartition %s with MAXSIZE (%s)"
// *Document: YES
// *Cause: Extending a table subpartition violated MAXSIZE limit.
// *Action: Increase the MAXSIZE limit and retry command.
//
60013, 00000, "invalid MAXSIZE storage option value"
// *Document: YES
// *Cause: Invalid value was specified for MAXSIZE storage clause.
// *Action: Correct the value and retry command.
// *Cause: Invalid value was specified for MAXSIZE storage clause.
// *Action: Correct the value and retry command.
//
60014, 00000, "invalid MAXSIZE storage option value"
// *Document: YES
// *Cause: Minimum of 1M should have been specified against the MAXSIZE storage clause.
// *Action: Correct the value and retry command.
//
60015, 00000, "invalid RETENTION storage option value"
// *Document: YES
// *Cause: Value of MIN retention should have been nonzero.
// *Action: Correct the value and retry command.
//
60016, 00000, "Operation not supported on SECUREFILE segment"
// *Document: YES
// *Cause: The operation to ALTER FREELIST/RETENTION was not supported on
// SECUREFILE segment.
// *Action: Check the LOB type and reissue the statement.
//
60018, 00000, "adding %s blocks to rollback segment %s with MAXSIZE (%s)"
// *Document: YES
// *Cause: Extending a rollback segment violated MAXSIZE limit.
// *Action: Increase the MAXSIZE limit and retry command.
//
60019, 00000, "Creating initial extent of size %s in tablespace of extent size %s"
// *Document: YES
// *Cause: Creation of SECUREFILE segment failed due to small tablespace
// extent size.
// *Action: Create tablespace with larger extent size and reissue command.
//
60020, 00000, "Internal event"
// *Document: NO
// *Cause:
// *Action: Contact Oracle Support Services
//
60021, 00000, "Internal event"
// *Document: NO
// *Cause:
// *Action: Contact Oracle Support Services
//
60022, 00000, "Internal event"
// *Document: NO
// *Cause:
// *Action: Contact Oracle Support Services
//
60023, 00000, "Internal event"
// *Document: NO
// *Cause:
// *Action: Contact Oracle Support Services
//
60024, 00000, "Internal event"
// *Document: NO
// *Cause:
// *Action: Contact Oracle Support Services
//
60025, 00000, "Event for temp segment cleanup used for temp lobs"
// *Document: YES
// *Cause: Temp LOB segments used for temporary LOBs are deleted
// only on session exit which may lead to large amounts of memory
// being held across multiple sessions.
// *Action: Setting this event will cause temporary LOB segments
// to be freed when there are no active temporary LOBs in
// the session. Setting this event will have a significant
// performance impact as it can cause temporary lob segments
// to be allocated and deleted many times during a session
// rather than once per session. Use this event only when
// temporary LOB segment memory use is an issue.
//
60038, 00000, "SECUREFILE space double allocation checking event"
// *Document: NO
// *Cause: This is an internal debugging event only
// *Action: N/A
//
60051, 00000, "space preallocation tracing event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
60052, 00000, "space preallocation history logging event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
60053, 00000, "space background task cancellation event"
// *Document: NO
// *Cause: This is an internal event used for space background task
// cancellation notification.
// *Action: N/A
60054, 00000, "space background framework shutdown event"
// *Document: NO
// *Cause: This is an internal event used for space background
// framework shutdown notification.
// *Action: N/A
60055, 00000, "Internal debugging event"
// *Document: NO
// *Cause: This is an internal debugging event used for dropping
// temporary segments in SMON instead of in slave process.
// *Action: N/A
60056, 00000, "Internal debugging event"
// *Document: NO
// *Cause: This is an internal debugging event used for simulating
// segment creation error.
// *Action: N/A
60057, 00000, "Internal debugging event"
// *Document: NO
// *Cause: This is an internal debugging event used for simulating
// space background task operation error.
// *Action: N/A
60058, 00000, "Internal debugging event"
// *Document: NO
// *Cause: This is an internal debugging event used for performing
// SYSAUX file online and offline checks in SMON instead of in
// slave process.
// *Action: N/A
60060, 00000, "extent allocation alignment event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
60061, 00000, "temporary space management tracing event"
// *Document: NO
// *Cause: This is an internal debugging event, and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
60062, 00000, "fail to repair LOB segment"
// *Document: NO
// *Cause: The segment_repair routine failed to repair the LOB segment.
// Additional information in the trace file provides details
// about the error.
// *Action: Check additional information in the trace file.
60063, 00000, "Oracle temporary file creation does not allocate space on file systems."
// *Document: NO
// *Cause: Oracle temporary file creation did not allocate space on file systems until it was needed. This enables fast creation of temporary files with no system overhead.
// *Action: Enable this event to have Oracle fill empty blocks in temporary files on file creation.
60064, 00000, "ILM activity tracking is disabled"
// *Document: NO
// *Cause: This is an internal event
// *Action: N/A
60065, 00000, "SYSAUX is disabled"
// *Document: NO
// *Cause: This is an internal event
// *Action: N/A
60066, 00000, "SYSAUX tablespace does not exist"
// *Document: NO
// *Cause: This is an internal event
// *Action: N/A
60067, 00000, "Internal event to trigger extension of ILMSTAT segment"
// *Document: NO
// *Cause: This is an internal event
// *Action: N/A
60068, 00000, "Unable to allocate memory for ILM activity tracking"
// *Document: NO
// *Cause: This is an internal event
// *Action: N/A
60069, 00000, "ILM statistics tracking is disabled"
// *Document: NO
// *Cause: This is an internal event. ILM statistics are not collected
// either because the tablespace is SYSTEM or because it is
// bootstrap processing.
// *Action: N/A
60070, 00000, "ILM activity tracking disabled due to multiple errors"
// *Document: NO
// *Cause: This is an internal event
// *Action: N/A
//
60071, 00000, "internal debugging event to disable SecureFile UFS reservation"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
60072, 00000, "adding (%s) blocks to heat map segment with MAXSIZE (%s)"
// *Document: YES
// *Cause: Extending the heat map segment violated the MAXSIZE limit.
// *Action: Increase the MAXSIZE limit.
//
60073, 00000, "Heat map segment cannot be created"
// *Document: YES
// *Cause: SYSAUX tablespace has uniform extent allocation and the extent
// size is not a multiple of megabyte.
// *Action: Re-create SYSAUX tablespace with autoallocate extent management
// policy or use the uniform extent size which is a multiple of
// megabyte.
60074, 00000, "Heat map activity tracking is disabled"
// *Document: NO
// *Cause: This is an internal event
// *Action: N/A
60075, 00000, "temporary file space management tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
60076, 00000, "Internal event to trigger extension of heat map segment"
// *Document: NO
// *Cause: This is an internal event
// *Action: N/A
60077, 00000, "Unable to allocate memory for heat map activity tracking"
// *Document: NO
// *Cause: This is an internal event
// *Action: N/A
60078, 00000, "Heat map statistics tracking is disabled"
// *Document: NO
// *Cause: This is an internal event. Heat map statistics are not collected
// either because the tablespace is SYSTEM or because it is
// bootstrap processing.
// *Action: N/A
60079, 00000, "Heat map tracking disabled due to multiple errors"
// *Document: NO
// *Cause: This is an internal event
// *Action: N/A
//
60080, 00000, "bitmapped tablespace space management tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
60081, 00000, "extent space management debugging event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: Check the tablespace type.
60082, 00000, "incorrect tablespace specified"
// *Document: YES
// *Cause: Clear free space operation was used on the temporary, undo,
// or SYSTEM tablespace, which is not supported.
// *Action: N/A
60083, 00000, "feature not supported with the current compatibility setting"
// *Document: YES
// *Cause: Clear free space operation requires database compatibility with
// release 12.2.0.2 or later.
// *Action: None.
60100, 00000, "dropping temporary tablespace with tablespace ID number (tsn) %s is blocked due to sort segments"
// *Document: YES
// *Cause: The temporary tablespace had sort segments in use.
// *Action: Wait for sort segments to complete or terminate sort session
// and then retry dropping the temporary tablespace.
60101, 00000, "event used to change retry count before raising ORA-60100"
// *Document: NO
// *Cause: N/A
// *Action: "alter system or session set event 60101 level <retry count>"
60200, 00000, "bigfile tablespace space management tracing event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
60201, 00000, "bigfile tablespace space management debugging event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
60202, 00000, "tablespace operation debugging event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// *Action: N/A
60203, 00000, "SecureFiles LOB force FSG creation event"
// *Document: NO
// *Cause: This is an internal debugging event and must be enabled
// only under the supervision of Oracle Support Services or
// development.
// Oracle server does not allocate Free Space Group until needed.
// *Action: Enable this event to force Oracle server allocate FSG at the
// time of LOB segment creation.
60204, 00000, "invalid value for 'NEXT' property in storage clause"
// *Document: NO
// *Cause: The 'NEXT' property in the storage clause can only assume
// values 1 M or 8 M or 64 M for locally managed tablespaces.
// *Action: Correct the 'NEXT' property in the storage clause and retry.
60205, 00000, "invalid temporary data block found"
// *Document: NO
// *Cause: An invalid temporary data block was read from the disk. The
// cause is uncertain. Possible causes are:
// - The media storage of the temporary tablespace caused corruption.
// - A latent issue caused by an unsuccessful clean up action for a
// previously failed operation involving temporary objects.
// In either cases, there is no permanent data loss.
//
// *Action: Check the alert log for more information and validate storage
// media for the temporary tablespace. Retry the operation to see
// if it succeeds. If the error persists, contact Oracle Support.
//
60206, 00000, "bigfile tablespace segment creation for space optimization during tablespace RESIZE"
// *Document: NO
// *Cause: This is an internal segment creation scheme whereby space for
// initial extent is searched starting from smallest file offset.
// This benefits tablespace RESIZE by allowing for the smallest
// resize value before encountering ORA-03297.
// *Action: Enable this event when creating table or index.
/////////////////////////////////////////////////////////////////////////////
/ 61001 - 62000 are reserved for ADE Virtual Folder (RNFS)
/////////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////////////////////
/ 62001 - 62005 are reserved for parameter properties
/////////////////////////////////////////////////////////////////////////////
62001, 00000, "value for parameter cannot contain a comma"
// *Cause: Parameter value contained a comma.
// *Action: Remove the comma from the parameter value.
//
//
/////////////////////////////////////////////////////////////////////////////
/ 62006 - 62009 are reserved for XML and object replication
/////////////////////////////////////////////////////////////////////////////
62006, 00000, "internal event for XML and object replication"
// *Document: NO
// *Cause: None
// *Action: None
//
//
62007, 00000, "Encountered a value of unsupported type or size for XPath (%s)"
// *Cause: Encountered a value of unsupported type in a SQL/XML DML operator.
// SQL/XML operators, such as UPDATEXML, expect value operands of type
// VARCHAR2 and XMLTYPE. XML DML replication is not supported for SQL/XML
// DML operators with values of unsupported types or very large values of
// supported types.
// *Action: Rewrite the UPDATE statement using XQuery update or set event 19027
// level 1 to dump XML Document as against XMLDiff in redo log.
62008, 00000, "Cannot rewrite a newer version of XML redo diff (encountered: %s, supported: %s)"
// *Cause: Encountered a newer version of XML redo diff that is not supported.
// *Action: Use RDBMS version that supports rewrite of given version of XML redo diff.
//
62009, 00000, "cannot encode an invalid XML character 0x%s in supplemental log"
// *Cause: An attribute was being populated or updated with characters which
// are not valid for XML and therefore could not be supplementally
// logged.
// *Action: Store the desired value in a RAW or BLOB attribute.
//
//
//
/////////////////////////////////////////////////////////////////////////////
/ 62010 - 62029 are reserved for DB Unicode Migration Assistant Kernel-Side
/////////////////////////////////////////////////////////////////////////////
// These messages are not normally visible to customers as they are
// intercepted by DUMA Client. They may be visible in a log file.
// NLS_DO_NOT_TRANSLATE [62010,62029]
62010, 00000, "invalid argument: %s"
// *Document: NO
// *Cause: The specified procedure argument was invalid, for example, NULL.
// *Action: Correct the value.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62011, 00000, "no columns to process"
// *Document: NO
// *Cause: The specified table had no columns to scan or convert.
// *Action: Do not call DBMS_DUMA_INTERNAL for this table or verify
// that all affected columns are registered in DUMA Repository.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62012, 00000, "ROWID range is not supported for index-organized or external tables"
// *Document: NO
// *Cause: Specifying ROWID range was not supported. Index-organized and
// external tables must be processed in their entirety.
// *Action: Specify NULL for START_ROWID and END_ROWID.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62013, 00000, "OCI error status %0!s, source line: %1!s"
// *Document: NO
// *Cause: Unexpected OCI error occurred.
// *Action: Contact Oracle Support Services.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62014, 00000, "internal error, arguments: [%0!s], [%1!s], [%2!s]"
// *Document: NO
// *Cause: Unexpected internal error occurred in DBMS_DUMA_INTERNAL.
// *Action: Contact Oracle Support Services.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62015, 00000, "column \"%s\" has the national character set form"
// *Document: NO
// *Cause: The DBMS_DUMA_INTERNAL.SCAN_TABLE procedure was called
// to scan a NVARCHAR2, NCHAR, or NCLOB column. This is not supported.
// *Action: Remove the column from the table SYSTEM.DUM$COLUMNS or filter
// it out with help of the SCAN_ID parameter.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62016, 00000, "column \"%0!s\" has the unsupported data type %1!s"
// *Document: NO
// *Cause: The DBMS_DUMA_INTERNAL.SCAN_TABLE procedure was called
// to scan a column of an unsupported data type. The internal ID
// of the data type is shown.
// *Action: Remove the column from the table SYSTEM.DUM$COLUMNS or filter
// it out with help of the SCAN_ID parameter.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62017, 00000, "unable to allocate %0!s bytes of memory, argument: [%1!s]"
// *Document: NO
// *Cause: There was no session memory available to satisfy a memory
// allocation request.
// *Action: Try with a lower value of BUFFER_SIZE parameter or free some system
// memory.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62018, 00000, "repository not installed"
// *Document: NO
// *Cause: Repository tables needed by the application were not
// installed in the SYSTEM schema or the current user did not
// have the INSERT privilege for the table SYSTEM.DUM$EXCEPTIONS.
// *Action: Refer to documentation and install the required tables,
// or grant the required privilege.
62019, 00000, "DUMA_ROWID_MAP$ column is missing or is of wrong data type"
// *Document: NO
// *Cause: In copy mode, the target table did not have a column named
// DUMA_ROWID_MAP$ or the column was not of type ROWID.
// *Action: Recreate the target table in the format required by CONVERT_LONG.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62020, 00000, "source row is missing"
// *Document: NO
// *Cause: In copy mode, the source table did not have a row with the ROWID
// stored in the column DUMA_ROWID_MAP$ in the target table.
// *Action: Recreate the target table in the format required by CONVERT_LONG.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62021, 00000, "unrecognized type of the fetched attribute \"%0!s\""
// *Document: NO
// *Cause: When scanning, an attribute value was encountered whose
// type was not among types collected during the preceding describe
// operation. This may mean that the type hierarchy was modified
// during the scan process.
// *Action: Repeat the scan.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62022, 00000, "unrecognized character set %0!s for column \"%1!s\""
// *Document: NO
// *Cause: The character set declared for the column was not recognized
// by the NLS library.
// *Action: Specify another character set. Verify the NLS data files.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62023, 00000, "BLOB exceeds the size limit of LONG column"
// *Document: NO
// *Cause: The BLOB contained more data than the LONG column can hold when
// writing data from the BLOB into the LONG column.
// *Action: Check the size of the BLOB and make sure it does not exceed the
// size limit of LONG data type.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62024, 00000, "invalid table ID"
// *Document: NO
// *Cause: The source table ID argument for the LONG RAW copy operation was
// either NULL or equal to the target table ID.
// *Action: Correct the source table ID, the target table ID, or both.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62025, 00000, "column data types do not match"
// *Document: NO
// *Cause: The target table contained a LONG RAW column while the source table
// contained a LONG column or vice versa.
// *Action: Make sure that source and target tables conform to requirements of
// CONVERT_LONG.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62026, 00000, "unrecognized delayed cleansing action"
// *Document: NO
// *Cause: The values in the scheduled cleansing action columns
// in DUMA Repository were incorrect.
// *Action: Correct the values in the scheduled cleansing action columns.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62027, 00000, "exception logging not supported for external tables"
// *Document: NO
// *Cause: Exception logging was attempted for an external table.
// *Action: Do not use 'V' or 'E' flag when calling SCAN_TABLE to scan
// an external table.
// *Comment: DBMS_DUMA_INTERNAL is an internal package used by
// Database Unicode Migration Assistant (DUMA). It should not be
// called by customers directly. If you see this error reported
// by DUMA, contact Oracle Support Services.
62029, 00000, "DBMS_DUMA_INTERNAL tracing event"
// *Document: NO
// *Cause: Debugging event for DBMS_DUMA_INTERNAL callouts.
// *Action: N/A
// *Comment: Level is a bit mask documented in prvtdumi.sql
//
62030, 00000, "split brain event"
// *Document: NO
// *Cause: Debugging event that triggers a split brain after the first pass
// of instance or crash recovery by making the first pass of crash
// recovery generate redo at the nab
// *Action: N/A
// *Comment: _allow_error_simulation must be enabled
//
/////////////////////////////////////////////////////////////////////////////
/ 62031 - 62080 are reserved for Vector Processing (IMA)
/////////////////////////////////////////////////////////////////////////////
62031, 00000, "QESXL internal tracing event"
// *Document: NO
// *Cause: Debugging event for QE[RS]XL key vector
// *Action: N/A
// *Comment: Level is a bit mask documented in qesxl.h
62032, 00000, "QESXL SO testing event"
// *Document: NO
// *Cause: Debugging event for testing key vector state object recovery
// *Action: N/A
// *Comment: Level is a bit mask documented in qesxl.h
62033, 00000, "QESGV internal tracing event"
// *Document: NO
// *Cause: Debugging event for QE[RS]GV vector group-by
// *Action: N/A
// *Comment: Level is a bit mask documented in qesgv.h
62034, 00000, "Invalid KEY VECTOR"
// *Document: NO
// *Cause: An internal function was called with invalid parameter.
// *Action: Contact Oracle Support Services.
// *Comment: This error is not expected to be hit by users. It typically
// indicates an attempt to call SYS_OP_KEY_VECTOR functions manually.
62035, 00000, "KEY VECTOR duplication failed"
// *Cause: Parallel query failed to duplicate KEY VECTOR across Oracle RAC instances.
// *Action: Increase the size of the System Global Area (SGA) memory.
//
/////////////////////////////////////////////////////////////////////////////
/ 62081 - 62130 are reserved for Vector Encoding (DSBs)
/////////////////////////////////////////////////////////////////////////////
62081, 00000, "duplicate or conflicting VECTOR ENCODE or NO VECTOR ENCODE specifications"
// *Document: YES
// *Cause: The specifications were either a duplicate of each other or were conflicting.
// *Action: Remove the duplicate specification.
62082, 00000, "VECTOR ENCODE only valid for Oracle number column"
// *Document: YES
// *Cause: VECTOR ENCODE was specified on a column that is not an Oracle number.
// *Action: Remove the VECTOR ENCODE clause.
62083, 00000, "operation not allowed for system hidden virtual column"
// *Document: YES
// *Cause: The system hidden virtual columns could not be dropped or modified directly.
// *Action: Avoid dropping or modifying system hidden virtual columns.
62084, 00000, "VECTOR ENCODE not supported for index-organized table"
// *Document: YES
// *Cause: The VECTOR ENCODE clause was specified on a column in an index-organized table.
// *Action: Avoid using the VECTOR ENCODE clause on an index-organized table.
//
/////////////////////////////////////////////////////////////////////////////
/ 62131 - 62230 are reserved for MEMOPTIMIZE features (Project 68493)
/////////////////////////////////////////////////////////////////////////////
62131, 00000, "MEMOPTIMIZE FOR WRITE feature cannot be enabled on IOTs."
// *Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on
// index-organized tables (IOT).
// *Action: None.
62132, 00000, "MEMOPTIMIZE FOR WRITE feature cannot be enabled on TEMPORARY TABLE."
// *Cause: An attempt was made to CREATE TEMPORARY TABLE with MEMOPTIMIZE FOR WRITE feature.
// *Action: None.
62133, 00000, "MEMOPTIMIZE FOR READ feature is not supported on ADG."
// *Cause: An attempt was made to populate data into hash index when in Active
// Data Guard mode.
// *Action: None.
62134, 00000, "MEMOPTIMIZE FOR READ feature cannot be used on table with ROW MOVEMENT enabled."
// *Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a
// table with row movement enabled.
// *Action: None.
62135, 00000, "Specified schema name is invalid."
// *Document: YES
// *Cause: An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure with an invalid schema name.
// *Action: Use a valid schema name for the table.
62136, 00000, "Specified table name is invalid."
// *Document: YES
// *Cause: An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure with an invalid table name.
// *Action: Use a valid table name.
62137, 00000, "Specified schema and table names are either non-existent or MEMOPTIMIZE FOR READ is not enabled on the table."
// *Document: YES
// *Cause: An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure with invalid information.
// Either the specified schema and table names are non-existent or MEMOPTIMIZE FOR READ feature is not enabled on the table.
// *Action: Enable MEMOPTIMIZE FOR READ feature on the table and invoke the procedure with correct schema and table names.
62138, 00000, "MEMOPTIMIZE memory area does not exist."
// *Document: YES
// *Cause: An attempt was made to use the DBMS_MEMOPTIMIZE package without creating the MEMOPTIMIZE memory area.
// *Action: Restart the instance with appropriate value for MEMOPTIMIZE memory area parameter.
62139, 00000, "MEMOPTIMIZE_WRITE hint disallowed for this operation"
// *Cause: MEMOPTIMIZE_WRITE hint was specified for the operation.
// *Action: You cannot specify this hint for this operation. Remove the hint
// from the statement.
62141, 00000, "MEMOPTIMIZE FOR READ feature cannot be used with COMPRESS option"
// *Cause: An attempt was made to use the COMPRESS option with MEMOPTIMIZE FOR READ feature.
// *Action: None.
62142, 00000, "MEMOPTIMIZE FOR READ feature requires NOT DEFERRABLE PRIMARY KEY constraint on the table"
// *Cause: An attempt was made to use MEMOPTIMIZE FOR READ on a table that did not have the PRIMARY KEY constraint or the PRIMARY KEY constraint is DEFERRABLE.
// *Action: None.
62143, 00000, "MEMOPTIMIZE FOR WRITE feature not allowed on table with trigger"
// *Document: YES
// *Cause: An attempt was made to set the MEMOPTIMIZE FOR WRITE attribute on a table with trigger.
// *Action: None
62144, 00000, "MEMOPTIMIZE FOR WRITE feature not allowed on table with foreign key constraint"
// *Document: YES
// *Cause: An attempt was made to set the MEMOPTIMIZE FOR WRITE attribute on a table with foreign key constraint.
// *Action: None
62145, 00000, "MEMOPTIMIZE FOR WRITE feature not allowed on segment with deferred storage"
// *Document: YES
// *Cause: An attempt was made to set the MEMOPTIMIZE FOR WRITE attribute on a table with deferred storage.
// *Action: None
62146, 00000, "MEMOPTIMIZE FOR WRITE feature cannot be used with COMPRESS option"
// *Cause: An attempt was made to use the COMPRESS option with MEMOPTIMIZE FOR WRITE feature.
// *Action: None.
62147, 00000, "MEMOPTIMIZE FOR READ operations are not allowed at PARTITION or SUBPARTITION levels."
// *Cause: An attempt was made to use MEMOPTIMIZE FOR READ
// option on a PARTITION table or SUBPARTITION table level.
// *Action: None.
62148, 00000, "MEMOPTIMIZE FOR READ feature cannot be enabled on IOTs."
// *Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on
// index-organized tables (IOT).
// *Action: None.
62149, 00000, "MEMOPTIMIZE FOR READ feature cannot be enabled on table with VIRTUAL COLUMNS."
// *Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a
// table with VIRTUAL COLUMNS.
// *Action: None.
62150, 00000, "MEMOPTIMIZE FOR READ feature cannot be enabled on table with INVISIBLE COLUMNS."
// *Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a
// table with INVISIBLE COLUMNS.
// *Action: None.
62151, 00000, "MEMOPTIMIZE FOR READ operation is not allowed on COMPOSITE PARTITIONED tables."
// *Cause: An attempt was made to enable or disable MEMOPTIMIZE FOR READ
// attribute on composite partitioned tables.
// *Action: None.
62152, 00000, "MEMOPTIMIZE FOR WRITE feature cannot be enabled on table with LOBs."
// *Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a
// table with LOB columns.
// *Action: None.
62153, 00000, "BLOCK SIZE is not equal to DB_BLOCK_SIZE setting."
// *Cause: An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure
// on a tablespace whose BLOCK SIZE was not equal to DB_BLOCK_SIZE.
// *Action: Use a default BLOCK SIZE.
62154, 00000, "MEMOPTIMIZE FOR WRITE feature cannot be enabled on table with VIRTUAL COLUMNS."
// *Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a
// table with VIRTUAL COLUMNS.
// *Action: None.
62155, 00000, "MEMOPTIMIZE FOR READ feature cannot be enabled on table with LOBs."
// *Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a
// table with LOB columns.
// *Action: None.
62156, 00000, "MEMOPTIMIZE FOR READ feature not allowed on segment with deferred storage"
// *Document: YES
// *Cause: An attempt was made to set the MEMOPTIMIZE FOR READ attribute on a table with deferred storage.
// *Action: None
62157, 00000, "MEMOPTIMIZE FOR READ clause needs to be specified only once."
// *Cause: An attempt was made to use MEMOPTIMIZE FOR READ clause more than
// once.
// *Action: None.
62158, 00000, "MEMOPTIMIZE FOR WRITE clause needs to be specified only once."
// *Cause: An attempt was made to use MEMOPTIMIZE FOR WRITE clause more than
// once.
// *Action: None.
62159, 00000, "MEMOPTIMIZE FOR READ cannot be enabled by CREATE PARTITIONED TABLE."
// *Cause: An attempt was made to CREATE PARTITIONED table with MEMOPTIMIZE FOR
// READ enabled.
// *Action: Use ALTER TABLE to enable MEMOPTIMIZE FOR READ for a partitioned table.
//
////////////////////////////////////////////////////////////////////////////
/ 62231 - 62250 are reserved for approximate top N errors
////////////////////////////////////////////////////////////////////////////
62231, 00000, "DESC is missing in ORDER BY clause within APPROX_RANK."
// *Cause: The DESC keyword was not specified in the ORDER BY clause within the APPROX_RANK function.
// *Action: Add the DESC keyword.
/
62232, 00000, "Invalid expression used in ORDER BY clause within APPROX_RANK."
// *Cause: An invalid expression was used in the ORDER BY clause within the APPROX_RANK function.
// *Action: Use the supported approximate aggregate function in the ORDER BY clause.
/
62233, 00000, "Multiple expressions were used in the ORDER BY clause within the APPROX_RANK function."
// *Cause: Multiple expressions are used in ORDER BY clause within APPROX_RANK.
// *Action: Order by a single expression within APPROX_RANK function.
/
62234, 00000, "The APPROX_RANK functions used different PARTITION BY keys."
// *Cause: APPROX_RANK functions use different PARTITION BY keys.
// *Action: Use the same PARTITION BY keys across APPROX_RANK functions.
/
62235, 00000, "PARTITION BY key in APPROX_RANK is not a subset of GROUP BY key."
// *Cause: The PARTITION BY key in the APPROX_RANK function was not a subset of the key in the GROUP BY clause.
// *Action: Use a subset of the key in the GROUP BY clause in the PARTITION BY key within the APPROX_RANK function.
/
62236, 00000, "Missing GROUP BY clause when approximate top functions are used."
// *Cause: The GROUP BY clause was missing when the approximate top functions were used.
// *Action: Add the GROUP BY clause.
/
62237, 00000, "Missing HAVING clause when approximate top functions are used."
// *Cause: The HAVING clause was missing when the approximate top functions were used.
// *Action: Add the HAVING clause.
/
62238, 00000, "Mixed approximate top functions with window functions or non approximate top functions."
// *Cause: An attempt was made to use window functions or aggregates that were not approximate top functions along with approximate top functions.
// *Action: Remove the window functions or non approximate top functions.
/
62239, 00000, "More than one expression appears in GROUP BY clause but not in PARTITION BY clause."
// *Cause: An attempt was made to involve more than one columns as the top N key.
// *Action: Remove the extra expression(s) from GROUP BY clause, or add extra expression(s) to PARTITION BY part in HAVING clause
/
62240, 00000, "Missing one or more corresponding APPROX_RANK clause in HAVING list when approximate top functions are used."
// *Cause: One or more corresponding APPROX_RANK clauses were missing when approximate top functions were used.
// *Action: Add the APPROX_RANK clause in HAVING list for each approximate top N function that appears in SELECT or ORDER BY clause
/
62242, 00000, "HAVING clause can only contain AND predicates when approximate top functions are used."
// *Cause: the HAVING clause contained predicates other than AND when approximate top functions were used.
// *Action: Only use the AND predicate with the HAVING clause.
/
62243, 00000, "Each predicate in HAVING clause must be in the format of 'APPROX_RANK(PARTITION BY ... ORDER BY ... DESC) <(=) n' when approximate top functions are used."
// *Cause: Illegal predicates were used in the HAVING clause when approximate top functions were used.
// *Action: Correct the format to 'APPROX_RANK (PARTITION BY ? ORDER BY ? DESC) <(=) n'.
/
62244, 00000, "GROUPING SETS, CUBE and ROLLUP cannot be applied to approximate functions."
// *Cause: An attempt was made to use GROUPING SETS, CUBE or ROLLUP over the approximate functions.
// *Action: Remove any GROUPING SETS, CUBE or ROLLUP when using approximate functions.
/
62245, 00000, "Negative value has been passed to APPROX_SUM function."
// *Cause: An attempt was made to pass a negative value to the APPROX_SUM function.
// *Action: Only pass expressions that have non-negative value to APPROX_SUM.
/
62246, 00000, "The subqueries that contain approximate top functions must be unnested."
// *Cause: An attempt was made to execute subqueries that contain approximate top functions without unnesting.
// *Action: Remove the hint or the parameters that are preventing subquery unnesting.
/
/////////////////////////////////////////////////////////////////////////////
/ 62500 - 62549 are reserved for PATTERN MATCHING
/////////////////////////////////////////////////////////////////////////////
62500, 00000, "function is not allowed outside of MATCH_RECOGNIZE clause"
// *Cause: The function was specified outside of the MATCH_RECOGNIZE clause.
// This function is only allowed in the MATCH_RECOGNIZE clause.
// *Action: Rewrite the SQL statement.
62501, 00000, "invalid value specified for bounded quantifier in MATCH_RECOGNIZE clause"
// *Cause: The specified lower bound or upper bound value was greater than
// UB4MAXVAL.
// The lower bound value must be non-negative.
// The upper bound value must be strictly positive.
// The upper bound value must be greater than or equal to the lower
// bound value.
// *Action: Choose an appropriate value and retry the operation.
62502, 00000, "invalid variable name"
// *Cause: The specified variable name was invalid.
// Variable names are not allowed to be "^", "$", or "*".
// *Action: Choose an appropriate variable name and retry the operation.
62503, 00000, "illegal variable definition"
// *Cause: The specified variable definition was invalid.
// Variables defined in the DEFINE clause must be in the PATTERN
// clause.
// Variables defined in the SUBSET clause cannot be in the PATTERN
// clause.
// Variables cannot be defined twice either in the SUBSET clause or
// the DEFINE clause.
// *Action: Choose an appropriate variable and retry the operation.
62504, 00000, "illegal variable reference"
// *Cause: The referenced variable was invalid.
// Variables referenced in the SUBSET clause must be in the PATTERN
// clause.
// Variables referenced in the DEFINE clause, the MEASURES clause, and
// the AFTER MATCH SKIP TO must be in the PATTERN clause or defined in
// the SUBSET clause.
// *Action: Choose an appropriate variable and retry the operation.
62505, 00000, "expression needs to be aliased"
// *Cause: The expression was not aliased.
// MEASURES clause items have to be aliased.
// *Action: Choose an appropriate variable and retry the operation.
62506, 00000, "illegal nesting of operators in MATCH_RECOGNIZE clause"
// *Cause: An attempt was made to nest aggregates/FIRST/LAST/PREV/NEXT.
// Aggregates/FIRST/LAST/PREV/NEXT cannot be nested.
// The only exception allowed is PREV/NEXT(FIRST/LAST()).
// *Action: Modify the query and retry the operation.
62507, 00000, "illegal use of MATCH_NUMBER or CLASSIFIER in MATCH_RECOGNIZE clause"
// *Cause: An attempt was made to use MATCH_NUMBER or CLASSIFIER in
// the MATCH_RECOGNIZE clause.
// CLASSIFIER and MATCH_NUMBER can only be used in the MEASURES clause.
// CLASSIFIER can only be used if the query is ALL ROWS PER MATCH.
// CLASSIFIER and MATCH_NUMBER cannot be used inside
// aggregates/FIRST/LAST/PREV/NEXT.
// *Action: Modify the query and retry the operation.
62508, 00000, "illegal use of aggregates or navigation operators in MATCH_RECOGNIZE clause"
// *Cause: An attempt was made to define aggregates/FIRST/LAST/PREV/NEXT over
// multiple variables.
// Aggregates/FIRST/LAST/PREV/NEXT cannot be defined over multiple
// variables.
// *Action: Modify the query and retry the operation.
62509, 00000, "illegal use of RUNNING or FINAL in MATCH_RECOGNIZE clause"
// *Cause: An attempt was made to use RUNNING or FINAL in MATCH_RECOGNIZE.
// RUNNING or FINAL can only be used on aggregate/FIRST/LAST.
// FINAL aggregate/FIRST/LAST is not allowed in the DEFINE clause.
// *Action: Modify the query and retry the operation.
62510, 00000, "Correlated subqueries are not allowed in MATCH_RECOGNIZE clause."
// *Cause: An attempt was made to use correlated subqueries in the
// MATCH_RECOGNIZE clause.
// Correlated subqueries are currently not allowed in the
// MATCH_RECOGNIZE clause.
// *Action: Modify the query and retry the operation.
62511, 00000, "Correlation variables are not allowed in MATCH_RECOGNIZE clause."
// *Cause: An attempt was made to use correlation variables in the
// MATCH_RECOGNIZE clause.
// Correlation variables are currently not allowed in the
// MATCH_RECOGNIZE clause.
// *Action: Modify the query and retry the operation.
62512, 00000, "This aggregate is not yet supported in MATCH_RECOGNIZE clause."
// *Cause: An unsupported aggregate was specified in the MATCH_RECOGNIZE
// clause.
// Only COUNT, SUM, AVG, MIN, and MAX are currently supported in the
// MATCH_RECOGNIZE clause.
// Distinct aggregates are currently not supported in the
// MATCH_RECOGNIZE clause.
// *Action: Modify the query and retry the operation.
62513, 00000, "Quantified subpatterns that can have empty matches are not yet supported."
// *Cause: There were empty matches for the quantified subpattern in the
// PATTERN clause.
// Quantified subpatterns are currently required to match one or more
// rows.
// *Action: Modify the query and retry the operation.
62514, 00000, "AFTER MATCH SKIP TO variable is not bounded in the match found."
// *Cause: AFTER MATCH SKIP TO variable was not bound in the match found due
// to pattern operators such as |, *, ?, and so on.
// *Action: Modify the query and retry the operation.
62515, 00000, "Exclusion syntax cannot be used with WITH UNMATCHED ROWS."
// *Cause: An attempt was made to use exclusion syntax with WITH UNMATCHED
// ROWS.
// Exclusion syntax {- -} cannot be used with WITH UNMATCHED ROWS.
// *Action: Modify the query and retry the operation.
62516, 00000, "The PARTITION BY, ORDER BY, or MEASURES clause is too large for MATCH_RECOGNIZE."
// *Cause: The number of items in PARTITION BY, ORDER BY, or MEASURES clause
// exceeded the maximum allowed.
// There cannot be more than UB2MAXVAL elements in PARTITION BY,
// ORDER BY, or MEASURES clause.
// *Action: Modify the query and retry the operation.
62517, 00000, "Next match starts at the same point last match started."
// *Cause: AFTER MATCH SKIP TO option repositioned the next match at the start
// of the previous one resulting in an infinite loop.
// *Action: Modify the query and retry the operation.
62518, 00000, "MATCH_RECOGNIZE pattern is too large."
// *Cause: MATCH_RECOGNIZE pattern was too large.
// More than UB2MAXVAL elements in alternation, concatenation,
// or permute, or more than UB4MAXVAL states in the state machine are
// currently not supported.
// Permute with more than 7 elements or bounded quantifier bound
// greater than 200 are also currently not supported.
// *Action: Modify the query and retry the operation.
62519, 00000, "Subquery inside MATCH_RECOGNIZE cannot contain MATCH_RECOGNIZE."
// *Cause: An attempt was made to use a subquery containing a MATCH_RECOGNIZE
// clause inside a MATCH_RECOGNIZE clause.
// Subqueries containing MATCH_RECOGNIZE clauses are currently not
// allowed in the MATCH_RECOGNIZE clause.
// *Action: Modify the query and retry the operation.
62520, 00000, "illegal offset for MATCH_RECOGNIZE navigation operators"
// *Cause: An attempt was made to use something other than a constant or
// a bind variable as the offset for MATCH_RECOGNIZE navigation
// operators FIRST, LAST, PREV, or NEXT.
// Offset for MATCH_RECOGNIZE navigation operators have to be
// constants or bind variables.
// *Action: Modify the query and retry the operation.
62521, 00000, "MATCH_RECOGNIZE is not supported on lateral views"
// *Cause: An attempt was made to use MATCH_RECOGNIZE on a lateral view,
// which is not supported.
// *Action: Modify the query and retry the operation.
/////////////////////////////////////////////////////////////////////////////
/ 62550 - 62554 are reserved for the SQL Row Limiting clause
/////////////////////////////////////////////////////////////////////////////
62550, 00000, "Invalid SQL ROW LIMITING expression was specified."
// *Cause: The SQL ROW LIMITING expression contained components other than
// literals, binds, correlation variables, or subqueries.
// *Action: Modify the SQL ROW LIMITING expression and retry the operation.
/////////////////////////////////////////////////////////////////////////////
/ 62555 - 62599 are reserved for Polymorphic Table Function
/////////////////////////////////////////////////////////////////////////////
//
62555, 00000, "Invalid use of PARTITION BY or ORDER BY clause."
// *Cause: Either the PARTITION BY or ORDER BY was specified on more than one
// argument of a POLYMORPHIC TABLE FUNCTION.
// *Action: Check the SQL statement and rewrite if necessary.
//
62556, 00000, "Incorrect use of COLUMNS operator."
// *Cause: COLUMNS function was used outside a POLYMORPHIC TABLE FUNCTION.
// *Action: Check the SQL statement and rewrite if necessary.
//
62557, 00000, "Invalid use of POLYMORPHIC TABLE FUNCTION."
// *Cause: POLYMORPHIC TABLE FUNCTION was specified inside RECURSIVE WITH
// clause.
// *Action: Check the SQL statement and rewrite if necessary.
//
62558, 00000, "Unsupported data types (%s) for polymorphic table function"
// *Cause: Non-scalar data types were used in polymorphic table function.
// Only scalar data types are supported.
// *Action: Use only scalar data types in polymorphic table function.
//
62559, 00000, "Data types mismatch (%s<<==>>%s) for polymorphic table function"
// *Cause: Data types for the source and target did not match for
// polymorphic table function. In Get_Col and Put_Col APIs,
// both the type of the collection element and the type of the
// polymorphic table function column must match.
// *Action: Ensure the collection element type matches the column type of
// the polymorphic table function
62560, 00000, "Duplicate column name (%s)"
// *Cause: The new column name already existed as a passthrough column in the
// polymorphic table function.
// *Action: Use a different column name that is unambiguous.
//
62561, 00000, "Invalid column ID (%s) in Get_Col or Put_Col"
// *Cause: The column number specified in the Get_Col or Put_Col API for
// polymorphic table functions was incorrect.
// *Action: Use a column ID that is valid for this polymorphic table function.
//
62562, 00000, "The API %s can be called only during execution time of a polymorphic table function."
// *Cause: This API was called in a context other than the execution time context
// of a polymorphic table function. This API is not supported in this context.
// *Action: Use this call only during the execution context of a polymorphic table function.
//
62563, 00000, "typecode not set for a new column in the polymorphic table function"
// *Cause: The type of this new column was not set.
// *Action: Set the typecode and other needed metadata during the describe phase of the
// polymorphic table function.
//
62564, 00000, "This new column name (%s) already exists."
// *Cause: This new column name was already created during the describe phase
// and therefore it is a duplicate column name.
// *Action: Ensure that the new column names are unique for this
// polymorphic table function.
//
62565, 00000, "The %s method failed with error(s). %s"
// *Cause: This method of polymorphic table function had error(s) during SQL compilation.
// *Action: Look at the errors and resolve them.
//
62566, 00000, "One of the new column names is a zero-length identifier."
// *Cause: A zero-length identifier was used as a new column name that was
// created during the describe phase.
// *Action: Specify valid identifiers for new column names.
//
62567, 00000, "One of the new column names is too long."
// *Cause: An identifier with more than 128 bytes was used for one of the
// new column names that was created during the describe phase.
// *Action: Specify at most 128 bytes for new column names.
//
62568, 00000, "invalid use of PARTITION BY or ORDER BY clause"
// *Cause: Either the PARTITION BY or the ORDER BY clause was specified on an
// argument of a non-table semantic POLYMORPHIC TABLE FUNCTION.
// *Action: Remove the PARTITION BY or the ORDER BY clause.
//
62569, 00000, "nested polymorphic table function is disallowed"
// *Cause: A polymorphic table function was specified as an argument of a table
// function.
// *Action: Modify the query so that there is no nested polymorphic table
// function.
//
62570, 00000, "new column name (%s) is invalid"
// *Cause: The new column name was invalid. It should be valid Oracle identifier
// and should not be an Oracle reserved word.
// *Action: Use a different column name that is a valid Oracle identifier
// and that is not an Oracle reserved word.
//
62571, 00000, "new column (%s) has length (%s) that is greater than the maximum allowed length (%s)"
// *Cause: The length specified for a new column for the polymorphic table function
// was greater than the maximum allowed length.
// *Action: Specify a new column length that is less than or equal to the
// maximum allowed length.
//
62572, 00000, "object views are not supported with polymorphic table functions"
// *Cause: An object view was being created with polymorphic table function in
// the select query.
// *Action: Do not use object views with polymorphic table function.
//
62573, 00000, "new column (%s) is not allowed with describe only polymorphic table function"
// *Cause: The new column name was created in describe only polymorphic table
// function.
// *Action: Do not create a new column when no execution methods
// like OPEN, FETCH_ROWS or CLOSE are specified.
//
62574, 00000, "row replication flag was not set"
// *Cause: A row replication API was called, but the Describe method set
// ROW_REPLICATION to FALSE (default).
// *Action: Change the value of ROW_REPLICATION to TRUE in the Describe method.
//
/////////////////////////////////////////////////////////////////////////////
/ 63000 - 63999 are reserved for DATABASE FILE ERRORS (cont. from 1100-1279)
/////////////////////////////////////////////////////////////////////////////
//
63000, 00000, "operation disallowed: data file %s is being moved"
// *Cause: The specified data file was being moved.
// *Action: Wait for the move operation to complete and retry the command.
//
63001, 00000, "file error during move operation"
// *Cause: The move operation encountered an error for the moved data file.
// The error might be caused by file going offline or by an I/O
// error. See alert or trace files in all instances for further
// information.
// *Action: Retry the move command.
//
63002, 00000, "a data file copy that is not current"
// *Cause: An obsolete copy of a data file left from a data file move
// operation was used for the CREATE CONTROLFILE command or
// file header read.
// *Action: Pass a valid file or perform a media recovery on the file.
//
63003, 00000, "a half-done data file copy"
// *Cause: A half-done copy of a data file created from a previous data file
// move operation was used for the CREATE CONTROLFILE command or
// file header read.
// *Action: Check file headers and pass only valid files.
//
63004, 00000, "Database names in file headers are inconsistent: %s and %s."
// *Cause: Differring database names were found in database file headers.
// *Action: Check that correct and valid data files are used.
//
63005, 00000, "Header validation failed for %s File ('%s')."
// *Cause: Oracle server failed to read or write to the specified file
// because the file has an SCN value which is too high for
// this release.
// *Action: Contact Oracle Support Services.
//
63995, 00000, "fractured block detected in control file: (block %s, # blocks %s)"
// *Cause: A fractured block or checksum error was detected on reading
// the control file under no-enqueue control file transaction.
// The reason could be a stalled concurrent block update.
// *Action: Retry the operation later.
//
63996, 00000, "A local temporary file remote call failed"
// *Cause: An operating system error or network error occurred when
// making a remote call to another instance during a local
// temporary space DDL operation.
// *Action: Remedy the operating system or network errors mentioned in the
// error stack and then retry the operation.
63997, 00000, "file size refresh failed"
// *Cause: An operating system error or device error occurred when
// retrieving the file's size.
// *Action: Remedy the operating system or device errors mentioned in the
// error stack and then perform crash recovery.
63998, 00000, "undo tablespace file suffered media failure"
// *Cause: An undo tablespace file was detected as inaccessible due to
// media failure.
// *Action: Restore accessibility to the file mentioned in the error stack
// and restart the instance.
63999, 00000, "data file suffered media failure"
// *Cause: A data file was detected as inaccessible due to media failure.
// *Action: Restore accessibility to the file mentioned in the error stack
// and restart the instance.
/////////////////////////////////////////////////////////////////////////////
// 64000 - 64099 reserved for DBFS API exceptions
/////////////////////////////////////////////////////////////////////////////
64000, 0000, "specified path already exists"
// *Document: YES
// *Cause: The pathname of a new item specified in a DBFS API operation
// already exists.
// *Action: Specify a valid, new pathname for the operation.
64001, 0000, "invalid parent directory in specified path"
// *Document: YES
// *Cause: The pathname of an item specified in a DBFS API operation
// has one or more invalid parent components.
// *Action: Specify a valid pathname with valid parent components for
// the operation.
64002, 0000, "specified path is invalid"
// *Document: YES
// *Cause: The pathname of an item specified in a DBFS API operation
// is invalid.
// *Action: Specify a valid pathname for the operation.
64003, 0000, "an unsupported operation was invoked"
// *Document: YES
// *Cause: The current DBFS API operation is unsupported by a provider.
// *Action: Use the provider feature set to invoke only supported
// operations.
64004, 0000, "an invalid combination of arguments was specified"
// *Document: YES
// *Cause: The current DBFS API operation specifies an invalid
// combination of arguments for the specified pathname(s)
// and operation.
// *Action: Specify a valid combination of pathname(s) and arguments.
64005, 0000, "access control checks failed"
// *Document: YES
// *Cause: The current DBFS API operation failed access control checks
// for the pathname(s) being accessed.
// *Action: Specify valid pathname(s) and principal for the operation,
// or take store-specific actions to enable access.
64006, 0000, "lock conflict in current operation"
// *Document: YES
// *Cause: A DBFS API locking operation could not be completed due
// to conflicts in the locking protocol.
// *Action: Follow the proper lock/unlock protocol according to the
// provider feature set.
64007, 0000, "invalid store specified"
// *Document: YES
// *Cause: The current operation specifies an invalid store name.
// *Action: Specify a valid store name for the operation.
64008, 0000, "invalid mount-point specified"
// *Document: YES
// *Cause: The current operation specifies an invalid mount-point.
// *Action: Specify a valid mount-point for the operation.
64009, 0000, "invalid provider specified"
// *Document: YES
// *Cause: The current operation refers to an invalid or incomplete
// or non-conformant store provider package.
// *Action: Specify a valid, complete, and conformant (per
// "dbms_dbfs_content_spi") store provider package.
64010, 0000, "cannot modify store via read-only mount"
// *Document: YES
// *Cause: The current operation attempts to modify a store via a
// read-only mount (or specifies a read-only store).
// *Action: Specify a valid modifiable store/mount for the operation.
64011, 0000, "cross store operation"
// *Document: YES
// *Cause: The current operation attempts to span 2 or more different
// stores and cannot be implemented entirely by the DBFS API.
// *Action: Split the operation, at the application-level, into multiple
// sub-operations to implement the same overall functionality.
64012, 0000, "specified path is a directory"
// *Document: YES
// *Cause: The current operation specifies a path that is a directory
// element, when a non-directory element is expected.
// *Action: Specify a path of the proper type for the operation.
64013, 0000, "specified path is not a directory"
// *Document: YES
// *Cause: The current operation specifies a path that is not a
// directory element, when a directory element is expected.
// *Action: Specify a path of the proper type for the operation.
64014, 0000, "directory not empty"
// *Document: YES
// *Cause: The current operation specifies a directory element that is
// not empty as required.
// *Action: Specify an empty directory element.
/////////////////////////////////////////////////////////////////////////////
// 64100 - 64199 Reserved for XML Index
/////////////////////////////////////////////////////////////////////////////
64101, 00000, "Cannot alter both a structured and an unstructured component of an XMLIndex in the same ALTER INDEX statement."
// *Cause : An attempt was made to alter the unstructured component and
// structured component of an XMLIndex at the same time.
// *Action: Use separate ALTER INDEX statements to change an unstructured
// component and a structured component of an XMLIndex.
64102, 00000, "Cannot create an XMLIndex with a structured component on a CLOB column within the object-relational storage model."
// *Cause : An attempt was made to create an XMLIndex with a structured
// component on a CLOB column within the object-relational storage
// model.
// *Action: Only unstructured XML indexes can be created on a CLOB column
// within the object-relational storage model.
64103, 00000, "Cannot create an XMLIndex on an object-relational XML type table or column."
// *Cause : An attempt was made to create an XMLIndex on an XML type table or
// column that uses the object-relational storage model.
// *Action: The object-relational storage model does not support an XMLIndex.
64104, 00000, "Column name already used by internal column of the structured component of the XMLIndex."
// *Cause : An attempt was made to use a column name already in use by
// an internal column of the structured component of the XMLIndex.
// *Action: Chose another column name.
64105, 00000, "Cannot create domain index on XMLIndex internal tables."
// *Cause : An attempt was made to create a domain index on an internal
// table of an XMLIndex.
// *Action: Create the domain index on the base table.
64106, 00000, "Incorrect use of comma(,) punctuation in COLUMN definitions."
// *Cause : An attempt was made to define COLUMNS with incorrect use of
// comma punctuation.
// *Action: Properly separate COLUMN definitions with comma punctuation.
64107, 00000, "The XMLIndex has been successfully altered but the metadata could not be updated. "
// *Cause : An internal error occured when updating the index metadata. The dbms_metadata.get_ddl function may return improper metadata.
// *Action: contact Oracle Support Services.
64108, 00000, "Cannot truncate a table that has an XMLIndex whose internal table has been indexed using Oracle Text."
// *Cause : An attempt was made to truncate a table that has an XMLIndex
// whose internal table has been indexed using Oracle Text.
// *Action: Drop the Oracle Text index on the XMLIndex internal table.
64109, 00000, "XMLIndex: problems encountered during the dropping of statistics"
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64110, 00000, "XMLIndex: problems encountered during the gathering of statistics"
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64111, 00000, "XMLIndex: problems encountered during EXPORT"
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64112, 00000, "XMLIndex: problems encountered during IMPORT"
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64113, 00000, "XMLIndex: XDB.XDB$XIDX_IMP_T still has bad data for \"%s\".\"%s\""
// *Cause : See associated error message.
// *Action: Ask the DBA to delete all the rows that belong to the given schema_name.index_name from the system table XDB.XDB$XIDX_IMP_T."
64114, 00000, "XMLIndex: reserved for EXPORT or IMPORT"
// *Cause :
// *Action:
// *Comment: Without a Cause and Action statement, this error will not appear in the documentation.
64115, 00000, "XMLIndex Exchange Partition: the table has no XMLIndex"
// *Cause: The non-partitioned table had no XMLIndex.
// *Action: N/A
64116, 00000, "XMLIndex Exchange Partition: incompatible XPath subsets"
// *Cause: The XMLIndexes on the two tables had different path subsets.
// *Action: Correct the error and retry the command.
64117, 00000, "XMLIndex Exchange Partition: incompatible modes for asynchronous DML"
// *Cause: The XMLIndexes on the two tables had different deferred DML modes.
// *Action: Correct the error and retry the command.
64118, 00000, "XMLIndex Exchange Partition: incompatible unstructured components"
// *Cause: One of the XMLIndexes had no unstructured component.
// *Action: Correct the error and retry the command.
64119, 00000, "XMLIndex Exchange Partition: incompatible structured components"
// *Cause: One of the XMLIndexes had no structured component.
// *Action: Correct the error and retry the command.
64120, 00000, "XMLIndex Exchange Partition: incompatible structured components"
// *Cause: The XMLIndexes had different structured components.
// *Action: Correct the error and retry the command.
64121, 00000, "XMLIndex DDL: failure of the internal \"%s\""
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
// *Comment: The DDLs are executed with different modes.
// Thus the various error codes to help identify the causes of the failure.
64122, 00000, "XMLIndex DDL: failure of the recursive \"%s\""
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64123, 00000, "XMLIndex DDL: failure of a recursive DDL"
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64124, 00000, "XMLIndex: failure during the setting of an event"
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64125, 00000, "XMLIndex: failure during the resetting of an event"
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64126, 00000, "XMLIndex Table Function: failure at the start of the function"
// *Cause : See associated error message.
// *Action: Examine the error messages and take appropriate action.
64127, 00000, "XMLIndex Table Function: failure at the beginning of the function"
// *Cause : See associated error message.
// *Action: Examine the error messages and take appropriate action.
64128, 00000, "XMLIndex Table Function: failure during the function evaluation"
// *Cause : See associated error message.
// *Action: Examine the error messages and take appropriate action.
64129, 00000, "XMLIndex Table Function: failure at the end of the function"
// *Cause : See associated error message.
// *Action: Examine the error messages and take appropriate action.
64130, 00000, "XMLIndex: invalid namespace mapping \"%s\""
// *Cause : Namespace mapping was invalid. The syntax is XMLNS="string".
// *Action: Check the namespace string, correct the error and retry command.
64131, 00000, "XMLIndex Metadata: failure during the looking up of the dictionary"
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64132, 00000, "XMLIndex Metadata: failure during the updating of the dictionary"
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64133, 00000, "XMLIndex DML: failure of the internal \"%s\""
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
// *Comment: The DMLs are executed with different modes.
// Thus the various error codes to help identify the causes of the failure.
64134, 00000, "XMLIndex DML: failure of the recursive \"%s\""
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64135, 00000, "XMLIndex DML: failure of a recursive DML"
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64136, 00000, "XMLIndex Asynchronous DML: synchronization failure"
// *Cause : See associated error message.
// *Action: Correct the error and retry command.
64137, 00000, "Cannot drop an XMLIndex whose internal table has been indexed using Oracle Text."
// *Cause : An attempt was made to drop an XMLIndex whose internal table
// has been indexed using Oracle Text.
// *Action: Drop the Oracle Text index on the XMLIndex internal table.
64138, 00000, "Cannot drop groups from an XMLIndex whose internal table has been indexed using Oracle Text."
// *Cause : An attempt was made to drop groups from an XMLIndex whose internal
// table has been indexed using Oracle Text.
// *Action: Drop the Oracle Text index on the XMLIndex internal table.
64139, 0000, "The type of VIRTUAL column is not XMLTYPE"
// *Document: YES
// *Cause: An attempt was made to create an XML index with VIRTUAL
// column not of XMLTYPE.
// *Action: Specify the type of VIRTUAL column to be XMLTYPE.
64140, 0000, "missing chaining XMLTABLE for VIRTUAL column in the index"
// *Document: YES
// *Cause: An attempt was made to create an XML index with VIRTUAL
// column but without required chaining XMLTABLE.
// *Action: Specify a chaining XMLTABLE after VIRTUAL column.
64141, 000, "Can only have a single XMLType column when a table is shared."
// *Cause: An attempt was made to create a shared table with more than one columns.
// *Action: Specify a correct shared table definition with only one XMLType column.
64142, 000, "Shared tables must have same semantics for truncation."
// *Cause: An attempt was made to create shared tables with inconsistent semantics for truncation.
// Either all shared tables should have or should not have (TRUNCATE) keyword.
// *Action: Be consistent with (TRUNCATE) keyword while defining shared tables.
64143, 000, "Can only share an existing XMLIndex table with an XMLTYPE column."
// *Cause: An attempt was made to share a table without an XMLTYPE column.
// *Action: Drop the group containing the XMLIndex table without an XMLTYPE column and
// re-create the group with new definition.
64144, 000, "Shared tables must have equivalent paths."
// *Cause: An attempt was made to share a table with different paths.
// *Action: Specify a correct shared table definition with appropriate paths.
64145, 000, "This XMLIndex rewrite failed"
// *Cause: One of the rewrites being tried by XMLIndex engine failed.
// *Action: None. This error is for understanding the trace file of XMLIndex rewrite.
64146, 000, "Nonblocking alter XMLIndex error"
// *Cause: Internal error.
// *Action: NONE
64147, 000, "Invalid use of NONBLOCKING COMPLETE or ABORT."
// *Cause: NONBLOCKING COMPLETE or ABORT is only allowed for XMLIndex that is being modified
// using NONBLOCKING ADD_GROUP or ADD_COLUMN.
// *Action: None
64148, 000, "Cannot complete nonblocking alter index operation."
// *Cause: NONBLOCKING COMPLETE is only allowed for XMLIndex that is being modified
// using NONBLOCKING ADD_GROUP or ADD_COLUMN and there are no pending rows left.
// *Action: Call DBMS_XMLINDEX.PROCESS_PENDING to finish pending work.
64149, 000, "Invalid alter XMLIndex operation."
// *Cause: An attemp was made to alter an XMLIndex that is already being modified using
// NONBLOCKING ADD_GROUP or ADD_COLUMN. Only NONBLOCKING COMPLETE or ABORT alter index
// operations are allowed. Also, NONBLOCKING operation is not allowed with alter index rebuild.
// *Action: Call DBMS_XMLINDEX.PROCESS_PENDING to finish pending work and then execute
// NONBLOCKING COMPLETE to successfully finish existing NONBLOCKING operation.
// Execute NONBLOCKING ABORT to cancle existing NONBLOCKING operation.
64151, 000, "Invalid use of DBMS_XMLINDEX.PROCESS_PENDING."
// *Cause: DBMS_XMLINDEX.PROCESS_PENDING was called on an index that was not modified
// using NONBLOCKING ADD_GROUP or ADD_COLUMN.
// *Action: None
64152, 000, "There are no pending rows to process."
// *Cause: DBMS_XMLINDEX.PROCESS_PENDING was called on an index that does not have
// any pending rows to process.
// *Action: Execute NONBLOCKING COMPLETE operation to complete the nonblocking
// alter index.
64153, 000, "Cannot create XMLIndex for data stored in a CLOB column within the object-relational storage model."
// *Cause: An attempt was made to create an XMLIndex on an XML CLOB column stored
// with object-relational storage.
// *Action: Change the XML column storage to binary XML.
64154, 00000, "XMLIndex cannot be created on an autolist partitioned table."
// *Cause: An attempt was made to create an XMLIndex on a table that had an
// autolist partition.
// *Action: None.
64155, 00000, "XMLIndex with unstructured component cannot be created on an interval partitioned table."
// *Cause: There was an attempt to create an Unstructured XMLIndex (UXI)
// component on a table with interval partitioning.
// *Action: Create an XMLIndex with a structured component.
////////////////////////////////////////////////////////////////////////////////////////
64200, 00000, "Internal event to control collection storage during create table"
// *Cause: N/A
// *Action: Do not document
//
/////////////////////////////////////////////////////////////////////////////
/ 64201 - 64299 are reserved for LOB errors
/////////////////////////////////////////////////////////////////////////////
64201, 00000, "unregistered LOB value encountered"
// *Cause: The LOB value associated with the input locator did not exist in
// client-side reference tables.
// *Action: This is an internal error. Contact Oracle Support Services.
64202, 00000, "remote temporary or abstract LOB locator is encountered"
// *Cause: Local database encountered a temporary or abstract LOB created on a
// remote database. Remote access to temporary or abstract LOB is not
// supported.
// *Action: Avoid remote queries that return a temporary or abstract LOB.
64203, 00000, "Destination buffer too small to hold CLOB data after character set conversion."
// *Cause: An attempt was made to convert CLOB to CHAR, where
// the LOB size was bigger than the buffer limit for CHAR types or the CHAR buffer
// was not big enough to hold all data after character set conversion.
// *Action: Do one of the following:
// * Make the LOB smaller before performing the conversion.
// for example, by using SUBSTR on CLOB
// * Use DBMS_LOB.SUBSTR to convert CLOB to CHAR.
//
64204, 00000, "encountered partial multibyte character"
// *Cause: The requested operation could not complete because a partial
// multibyte character was found at the end of the input.
// *Action: Ensure that the input buffer ends with a complete multibyte character
// and retry the operation.
64205, 00000, "Cannot use other triggering events along with LOGICAL LOB UPDATE event"
// *Cause: An attempt was made to use other triggering events (such as INSERT, DELETE and UPDATE)
// with the LOGICAL LOB UPDATE event.
// *Action: Create multiple triggers instead of sharing a trigger for multiple events.
64206, 00000, "Cannot create INSTEAD OF LOGICAL LOB UPDATE trigger"
// *Cause: INSTEAD OF LOGICAL LOB UPDATE trigger was not allowed.
// *Action: None
64207, 00000, "Invalid LOGICAL LOB UPDATE trigger definition"
// *Cause: The LOGICAL LOB UPDATE trigger could not be created on a non-LOB column of a table.
// The column name has to be specified while creating the trigger. Only one column
// name can be specified while creating the trigger.
// *Action: Specify LOGICAL LOB UPDATE trigger with a valid definition.
64208, 00000, "FOR EACH ROW clause is required for before or after LOGICAL LOB UPDATE triggers"
// *Cause: An attempt was made to create a before or after LOGICAL LOB UPDATE trigger without
// a FOR EACH ROW clause.
// *Action: Specify a FOR EACH ROW clause for a before/after LOGICAL LOB UPDATE trigger.
64209, 00000, "WHEN clause is not allowed for LOGICAL LOB UPDATE triggers"
// *Cause: WHEN clause was specified for a LOGICAL LOB UPDATE trigger.
// *Action: Remove the WHEN clause when creating a LOGICAL LOB UPDATE trigger.
64210, 00000, "Cannot reference a trigger of a different type"
// *Cause: The LOGICAL LOB UPDATE trigger did not follow other LOGICAL LOB UPDATE triggers.
// Non-LOGICAL LOB UPDATE triggers cannot follow LOGICAL LOB UPDATE triggers.
// *Action: None
64211, 00000, "Cannot access other columns within a LOGICAL LOB UPDATE trigger body"
// *Cause: An attempt was made to access an invalid column.
// A LOGICAL LOB UPDATE trigger can only access ROWID column and the column
// for which it was specified. Access to other columns is not allowed.
// *Action: Remove references to other columns within a LOGICAL LOB UPDATE trigger body.
64212, 00000, "Cannot create a LOGICAL LOB UPDATE trigger on a view"
// *Cause: A LOGICAL LOB UPDATE trigger could not be created on view.
// *Action: None
64213, 00000, "Cannot create a compound LOGICAL LOB UPDATE trigger with statement level actions"
// *Cause: A compound LOGICAL LOB UPDATE trigger could not contain statement level actions.
// *Action: None
64214, 00000, "Cannot create a crossedition LOGICAL LOB UPDATE trigger"
// *Cause: Crossedition LOGICAL LOB UPDATE triggers were not supported.
// *Action: None
64215, 00000, "PL/SQL subprogram '%s' for internal use only"
// *Cause: An attempt was made to use a subprogram that is for internal Oracle development use only.
// *Action: Do not use this unsupported subprogram. Refer to Oracle
// documentation for available subprograms.
64216, 00000, "Internal event"
// *Document: NO
// *Cause:
// *Action: Contact Oracle Support Services
//
64217, 00000, "Internal event"
// *Document: NO
// *Cause:
// *Action: Contact Oracle Support Services
//
64218, 00000, "Unable to dynamically allocate additional memory"
// *Document: NO
// *Cause: An error occurred during dynamic memory allocation of
// segmented arrays for abstract LOBs because the LOB size
// exceeded the maximum size supported by the Segmented Array
// API.
// *Action: Limit the size of the LOB to the one supported by the Segmented
// Array API.
//
64219, 00000, "invalid LOB locator encountered"
// *Cause: The LOB locator sent from client to server was invalid.
// *Action: Pass a valid LOB locator that was either returned by the database
// or initialized as an empty locator.
//
/////////////////////////////////////////////////////////////////////////////
/ 64300 - 64349 are reserved for ARCHIVE COMPRESSION
/////////////////////////////////////////////////////////////////////////////
64300, 00000, "Invalid compression level specified"
// *Document: YES
// *Cause: The specified archive compression level value was invalid. Valid
// values are LOW or HIGH.
// *Action: Choose a valid level and retry the operation.
//
64301, 00000, "COMPRESS must be specified with HYBRID COLUMNAR organization"
// *Document: NO
// *Cause: COMPRESS was not specified with HYBRID COLUMNAR organization.
// *Action: Specify the COMPRESS clause for HYBRID COLUMNAR organization.
//
64303, 00000, "Incorrect organization clause"
// *Document: NO
// *Cause: HYBRID was specified in organization clause without COLUMNAR.
// *Action: Specify COLUMNAR after HYBRID in organization clause.
//
64304, 00000, "Incorrect organization clause"
// *Document: NO
// *Cause: COMPRESS was not specified with organization HYBRID COLUMNAR.
// *Action: Specify COMPRESS clause when specifying organization HYBRID COLUMNAR.
//
64305, 00000, "LOB update operations are not supported on HYBRID COLUMNAR organization tables of this type"
// *Document: NO
// *Cause: A LOB update using DBMS_LOB or a related interface was attempted on a HYBRID COLUMNAR compressed table that does not support this type of operation.
// *Action: Alter the table to disable HYBRID COLUMNAR compression or do not perform LOB updates on this table.
//
64306, 00000, "LOB update operations are not supported on HYBRID COLUMNAR compressed tables with certain index types"
// *Document: NO
// *Cause: A LOB update using DBMS_LOB or a related interface was attempted on a HYBRID COLUMNAR compressed table with an unsupported index type. Virtual, functional, domain, and join indexes do not support these operations.
// *Action: Drop the index or do not perform LOB updates on this table.
//
64307, 00000, " Exadata Hybrid Columnar Compression is not supported for tablespaces on this storage type"
// *Document: YES
// *Cause: An attempt was made to use Exadata Hybrid Columnar Compression on unsupported storage.
// *Action: Create this table in a tablespace residing on Oracle Exadata,
// Oracle's Sun ZFS or Pillar Axiom storage or use a different compression type.
//
64308, 00000, "hybrid columnar compressed table cannot have column with LONG data type"
// *Document: YES
// *Cause: One of the following was attempted:
// - Create a hybrid columnar compressed table with a LONG data type.
// - Alter an existing table with a LONG data type to be
// hybrid columnar compressed.
// - Add a LONG data type column to a hybrid columnar compressed table.
// *Action: LONG data types are not supported with hybrid columnar compressed
// tables. Create table without LONG column or change table to not be
// hybrid columnar compressed. If adding a column, do not use
// LONG data type. If modifying attributes of a column to change data
// type to LONG, the table cannot be hybrid columnar compressed.
64309, 00000, " Hybrid Columnar Compression with row-level locking is not supported for tablespaces on this storage type."
// *Document: YES
// *Cause: An attempt was made to use Hybrid Columnar Compression with row-level locking on an unsupported storage type.
// *Action: Create this table in a tablespace residing on Oracle Exadata storage or use a different compression type.
//
64310, 00000, "could not get compression analysis lock"
// *Document: YES
// *Cause: An operation could not obtain the compression analysis lock in a
// reasonable amount of time.
// *Action: Retry the operation.
//
/////////////////////////////////////////////////////////////////////////////
/ 64350 - 64399 are reserved for In-Memory Columnar (IMC)
/////////////////////////////////////////////////////////////////////////////
64350, 00000, "only one INMEMORY clause may be specified"
// *Cause: INMEMORY was specified more than once.
// *Action: Specify each desired INMEMORY clause option only once.
64351, 00000, "in-memory area already exists"
// *Document: NO
// *Cause: An attempt was made to create an in-memory area when one was
// already in existence.
// *Action: None.
64352, 00000, "in-memory area does not exist"
// *Document: NO
// *Cause: An attempt was made to drop an in-memory area when none were
// in existence.
// *Action: None.
64353, 00000, "in-memory area size cannot be less than 100MB"
// *Document: NO
// *Cause: An attempt was made to create an in-memory area with less than
// 100MB of space.
// *Action: None.
64354, 00000, "in-memory area size cannot exceed max(sga target, shared pool size)"
// *Document: NO
// *Cause: An attempt was made to create an in-memory area exceeding the
// size of the memory target.
// *Action: Decrease the size of the in-memory area.
64355, 00000, "in-memory Xmem area size cannot be less than 100 MB"
// *Document: NO
// *Cause: An attempt was made to create an in-memory Xmem area
// with less than 100 MB of space.
// *Action: None.
64356, 00000, "in-memory area out of space"
// *Document: NO
// *Cause: The in-memory area had no free space.
// *Action: Drop the in-memory segments to make space.
64357, 00000, "in-memory area out of space for the current container"
// *Document: NO
// *Cause: There was no free space in the in-memory area for the
// current container.
// *Action: Drop the in-memory segments in the current container to make
// space or increase the maximum size limit.
64358, 00000, "in-memory column store feature not supported for IOTs"
// *Document: NO
// *Cause: An attempt was made to enable the in-memory column store feature
// for an index-organized table.
// *Action: None.
64359, 00000, "INMEMORY clause may not be specified for virtual columns"
// *Document: NO
// *Cause: An attempt was made to enable the in-memory selective columns
// feature for a virtual column.
// *Action: None.
64360, 00000, "only one INMEMORY clause may be specified for each column"
// *Document: NO
// *Cause: INMEMORY clause was specified more than once for a column.
// *Action: Specify each desired INMEMORY clause option only once per column.
64361, 00000, "column INMEMORY clause may only be specified for an inmemory table"
// *Document: NO
// *Cause: A column INMEMORY clause was specified for a table that is not
// specified to be in memory.
// *Action: None.
64362, 00000, "INMEMORY clause may not be specified for LONG columns"
// *Document: NO
// *Cause: An attempt was made to enable the in-memory selective columns
// feature for a LONG column.
// *Action: None.
64363, 00000, "invalid value \"%s\" for parameter inmemory_clause_default"
// *Document: NO
// *Cause: The value for the initialization parameter
// 'inmemory_clause_default' was invalid.
// *Action: Choose a value allowed by the parameter syntax.
64364, 00000, "In-memory column store on Oracle RAC is only supported on Oracle-engineered systems."
// *Document: YES
// *Cause: An attempt was made to use the in-memory column store feature with
// Oracle RAC on an unsupported system.
// *Action: Disable Oracle RAC before attempting to use the in-memory column store in
// this environment or use an Oracle-engineered system.
64365, 00000, "In-memory column store FastStart debug event"
// *Document: NO
// *Cause: N/A
// *Action: N/A
64366, 00000, "In-memory column store FastStart internal error"
// *Document: NO
// *Cause: N/A
// *Action: N/A
64367, 00000, "In-memory column store FastStart tablespace is offline."
// *Document: Yes
// *Cause: The FastStart feature was enabled but its tablespace was offline.
// *Action: Disable FastStart or bring the FastStart tablespace online.
64368, 00000, "In-memory FastStart is only supported on Oracle-engineered systems."
// *Document: YES
// *Cause: An attempt was made to use the in-memory column store FastStart
// feature on an unsupported system.
// *Action: Use FastStart on an Oracle-engineered system.
64369, 00000, "In-memory FastStart Oracle Call Interface (OCI) error %s"
// *Document: YES
// *Cause: An OCI error occurred when enabling or disabling FastStart.
// *Action: Mannually correct the problem.
64370, 00000, "INMEMORY clause with DISTRIBUTE BY PARTITION specified for a table that is not partitioned."
// *Document: YES
// *Cause: DISTRIBUTE BY PARTITION was specified for a table that is not partitioned.
// *Action: None.
64371, 00000, "INMEMORY clause with DISTRIBUTE BY SUBPARTITION specified for a table that is not composite."
// *Document: YES
// *Cause: DISTRIBUTE BY SUBPARTITION was specified for a table that is not composite.
// *Action: None.
64372, 00000, "INMEMORY clause with DISTRIBUTE BY SUBPARTITION specified for a table that is not partitioned."
// *Document: YES
// *Cause: DISTRIBUTE BY SUBPARTITION was specified for a table that is not partitioned.
// *Action: None.
64373, 00000, "Unable to get FastStart Admin Enqueue in mode %s"
// *Document: YES
// *Cause: An attempt was made to do FastStart administrative tasks
// while FastStart is in use.
// *Action: Temporarily disable faststart.
64374, 00000, "Action cannot be performed when FastStart is not enabled."
// *Document: YES
// *Cause: An attempt was made to execute a FastStart related action when FastStart was not enabled.
// *Action: Enable FastStart and retry.
64375, 00000, "FastStart is already enabled"
// *Document: YES
// *Cause: FastStart is already enabled.
// *Action: N/A
64376, 00000, "FastStart is already enabled on this tablespace"
// *Document: YES
// *Cause: This tablespace is already assigned to FastStart or some FastStart internal
// objects already exists on this tablespace.
// *Action: Rerun DBMS_INMEMORY.ENABLE_FASTSTART after running DBNS_INMEMORY.DISABLE_FASTSTART
64377, 00000, "Action cannot be performed when database is in read-only mode"
// *Document: YES
// *Cause: An attempt make changes to FastStart objects on a read-only database.
// *Action: Mount the the database in writtable mode and retry.
64378, 00000, "Action cannot be performed on the tablespace assigned to FastStart while the feature is enabled"
// *Document: YES
// *Cause: An attempt to make FastStart tablespace offline when the feature is enabled.
// *Action: Disable the feature and retry.
64379, 00000, "Action cannot be performed on the tablespace assigned to FastStart while the feature is enabled"
// *Document: YES
// *Cause: An attempt drop FastStart tablespace when the feature is enabled.
// *Action: Disable the feature and retry.
64380, 00000, "FastStart cannot be enabled or migrated to a non-ASSM tablespace."
// *Document: YES
// *Cause: An attempt was made to enable or migrate FastStart to a non-automatic segment space management (ASSM) tablespace.
// *Action: Enable or migrate FastStart to an ASSM tablespace.
64381, 00000, "Unable to aquire the tablespace enqueue for the given FastStart operation."
// *Document: YES
// *Cause: The given tablespace was locked by another operation.
// *Action: Try again later.
64382, 00000, "FastStart checkpoint has already started."
// *Document: YES
// *Cause: An attempt was made to initiate a checkpoint when one was already started.
// *Action: Wait for the previous checkpoint to finish.
64383, 00000, "FastStart %s was incomplete."
// *Document: YES
// *Cause: The previous FastStart administrative procedure was incomplete.
// *Action: Run the procedure again or disable the feature.
64384, 00000, "invalid FastStart catalog version detected"
// *Document: YES
// *Cause: The version number of the FastStart catalog was invalid or too old.
// *Action: Rebuild the FastStart catalog.
64385, 00000, "invalid value \"%s\" for parameter cellmemory_clause_default"
// *Document: NO
// *Cause: The value for the initialization parameter
// 'cellmemory_clause_default' was invalid.
// *Action: Choose a value allowed by the parameter syntax.
64386, 00000, "%s not supported for proxy PDB"
// *Document: YES
// *Cause: An attempt was made to use FastStart in the case of a proxy pluggable database (PDB).
// *Action: None.
64387, 00000, "inmemory_size cannot be modified"
// *Document: YES
// *Cause: An attempt was made to modify inmemory_size parameter when database was not opened, was read-only, or was being migrated.
// *Action: Issue the command after opening the database in read/write mode.
64388, 00000, "inmemory_size specified is less than a minimum of (%s) bytes"
// *Document: YES
// *Cause: inmemory_size was less than the minimum expected by the system.
// *Action: Issue the command after changing the value for the inmemory_size parameter.
64389, 00000, "The FastStart tablespace has insufficient space to migrate"
// *Document: YES
// *Cause: An attempt was made to migrate FastStart to a tablespace which did not have sufficient space.
// *Action: Add space to the tablespace that is migrated.
64390, 00000, "FastStart not supported for %s"
// *Document: YES
// *Cause: An attempt was made to use FastStart along with the feature that is not supported.
// *Action: None.
64391, 00000, "Error, obsolete redo seen on IM-enabled ADG, stopping recovery"
// *Document: NO
// *Cause: Obsolete (12.2OPC) redo was seen on standby database or logwriter (LGWR) encountered an error.
// *Action: Recovery stopped. Set inmemory_adg_enabled to FALSE and restart recovery.
64392, 00000, "Population process is being tested"
// *Document: NO
// *Cause: The event was set to test that populate action is triggered after the process died.
// *Action: None
64393, 00000, "In-Memory Expressions capture window is already OPEN"
// *Document: YES
// *Cause: An attempt was made to open an In-Memory Expressions capture
// window with another capture window already in the OPEN state.
// *Action: Close the In-Memory Expressions capture window that is currently
// in the OPEN state.
64394, 00000, "In-Memory Expressions capture window is not OPEN"
// *Document: YES
// *Cause: An attempt was made to CLOSE an In-Memory Expressions capture
// window before opening it first.
// *Action: Open an In-Memory Expressions capture window before attempting a
// CLOSE operation.
64395, 00000, "error encountered while changing the state of In-Memory Expressions capture window"
// *Document: YES
// *Cause: An internal error was encountered in the In-Memory Expressions procedure.
// *Action: Contact Oracle Support Services.
64396, 00000, "Resize of In-Memory Xmem area is not supported."
// *Document: YES
// *Cause: Resize of In-Memory Xmem area was not supported on
// non multitenant container database (CDB) and
// root pluggable database (PDB).
// *Action: None.
64397, 00000, "The new Xmem area size %0!s M is larger than configured Xmem area size %1!s M."
// *Document: YES
// *Cause: The specified In-Memory area size was larger than the
// configured In-Memory XMem area size.
// *Action: Check the new Xmem area size and reissue the command.
64398, 00000, "invalid INMEMORY_SIZE value for cloud configuration, it must be zero"
// *Document: YES
// *Cause: A nonzero value was specified for the INMEMORY_SIZE initialization parameter for a non-Oracle cloud.
// *Action: Remove the INMEMORY_SIZE initialization parameter or set the value to zero.
/////////////////////////////////////////////////////////////////////////////
/ 64400 - 64599 are reserved for XDB errors
/////////////////////////////////////////////////////////////////////////////
64401, 00000, "This manageability package is only supported on Oracle RDBMS versions 10.2, 11.1, and 11.2."
// *Document: YES
// *Cause: Package installation invoked on database version that was not 10.2, 11.1 or 11.2..
// *Action: Use Oracle databaseversion 10.2, 11.1, or 11.2.
//
64402, 00000, "Invalid input. XMLSchema is null."
// *Document: YES
// *Cause: XMLSchema was not provided to the procedure or function call..
// *Action: Provide an XMLSchema.
//
64403, 00000, "Input cannot be null"
// *Document: YES
// *Cause: An input parameter was null.
// *Action: Provide input paramter.
//
64404, 00000, "Input string exceeds the maximum size"
// *Document: YES
// *Cause: An input string was provided whose length exceeded the maximum size allowed. This size is 30 bytes for clients prior to Oracle Database 12c Release 2 (12.2) and 128 bytes otherwise.
// *Action: Provide a shorter input string.
//
64405, 00000, "No matching elements found. Zero annotations were applied."
// *Document: YES
// *Cause: The parameters provided to annotate the XMLSchema did not match any entities in the XMLSchema.
// *Action: Correct the parameters.
//
64406, 00000, "No matching elements found. Zero annotations were removed."
// *Document: YES
// *Cause: The parameters provided to annotate the XMLSchema did not match any entities in the XMLSchema.
// *Action: Correct the parameters.
//
64407, 00000, "Annotation maps to multiple elements."
// *Document: YES
// *Cause: The parameters provided to annotate the XMLSchema matched to multiple entities in the XMLSchema.
// *Action: .
//
64408, 00000, "Name for collection table too long."
// *Document: YES
// *Cause: The name for the collection table exceeded 25 characters.
// *Action: Reduce the length of the name of the collection table.
//
64409, 00000, "XPath could not be mapped to exactly one table."
// *Document: YES
// *Cause: XPath could not be mapped to existing table.
// *Action: Check input parameters.
//
64410, 00000, "Invalid XPath."
// *Document: YES
// *Cause: The XPath string provided to the procedure was not valid.
// *Action: Check XPath string.
//
64411, 00000, "Invalid collection table specified by XPath."
// *Document: YES
// *Cause: An invalid collection table was specified by the XPath string.
// *Action: Check XPath string.
//
64412, 00000, "Procedure called on XML table with BINARY storage model."
// *Document: YES
// *Cause: The procedure renameCollectionTable did not work on binary storage model.
// *Action: .
//
64413, 00000, "Cannot disable constraints/indexes for non-global schemas owned by other users or a non schema based table/column."
// *Document: YES
// *Cause: An attempt was made to disable constraints or indexes for non-global schemas owned by other users or a non schema based table/column.
// *Action: Use an OR schema based table/column or change users to disable constraints or indexes.
//
64414, 00000, "Cannot enable constraints/indexes for non-global schemas owned by other users or a non schema based table/column."
// *Document: YES
// *Cause: An attempt was made to enable constraints or indexes for schemas owned by other users or for a non schema based table/column.
// *Action: Use an OR schema based table/column or change users to enable constraints or indexes.
//
64415, 00000, "Error in namespace declaration."
// *Document: YES
// *Cause: The namespace declaration was invalid.
// *Action: Correct namespace declaration.
//
64416, 00000, "Table does not exist."
// *Document: YES
// *Cause: The tab_name parameter provided the name of a table that did not exist..
// *Action: Correct the tab_name parameter.
//
64417, 00000, "Column does not exist in table."
// *Document: YES
// *Cause: The col_name parameter provided the name of a column that did not exist in the given table.
// *Action: Correct the col_name parameter.
//
64418, 00000, "Column not of XMLType."
// *Document: YES
// *Cause: The col_name parameter provided the name of a column that was not an XMLType column.
// *Action: Correct the col_name parameter.
//
64419, 00000, "Name for collection table already exists."
// *Document: YES
// *Cause: The name for the collection table could not be used because it already exists.
// *Action: Use another name for collection table.
//
64420, 00000, "Table not of XMLType."
// *Document: YES
// *Cause: The table_name parameter provided the name of a table that was not an XMLType table.
// *Action: Correct the table_name parameter or provide the name of an XMLType column in the table.
//
64421, 00000, "XSLT rewrite transformtion to XQuery not successful."
// *Document: NO
// *Cause: The XSLT was not suitable for XQuery transformation optimization.
// *Action: Use proper XSLT construct to faciliate XQuery transformation optimization.
//
64422, 00000, "NoInlining for XSLT to XQuery translation event is set"
// *Document: NO
// *Cause: This is an internal debugging event (19120, 0x200000) only.
// *Action: N/A
//
/////////////////////////////////////////
/// schema evolution error messages /////
/////////////////////////////////////////
64423, 00000, "deletion of global %s is not permitted"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64424, 00000, "deletion of %s from a complex type is not permitted (complex type \'%s\')"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64425, 00000, "addition of non-optional %s to a complex type is not permitted (complex type \'%s\')"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64426, 00000, "deletion from an enumeration list is not permitted (simple type \'%s\')"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64427, 00000, "insertion at the end of an enumeration list is not permitted (simple type \'%s\')"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64428, 00000, "Error %s named \'%s\' - \'%s\' is not a superset of \'%s\'"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64429, 00000, "Error %s named \'%s\' - change from \'%s\' to \'%s\' in non-binary XMLSchema"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64430, 00000, "illegal or unsupported change to %s \'%s\'"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64431, 00000, "illegal or unsupported change to mixed in complex type \'%s\'"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64432, 00000, "illegal or unsupported change to mixed in local complex type"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64433, 00000, "illegal or unsupported change to mixed in complex type \'%s\' of non-binary XMLSchema"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64434, 00000, "illegal or unsupported change to mixed in local complex type of non-binary XMLSchema"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64435, 00000, "type of %s named \'%s\' changed from \'%s\' to \'%s\'"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64436, 00000, "Error %s named \'%s\' changed from being of a local type to type %s"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64437, 00000, "Error %s \'%s\' changed from being reference-based to being of type %s"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64438, 00000, "illegal or unsupported change to complex type \'%s\'"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64439, 00000, "illegal or unsupported change to %s"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64440, 00000, "Error %s \'%s\' changed from being of complex type to being of simple type \'%s\'"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64441, 00000, "maxoccurs in a non-binary XMLSchema cannot be modified (element \'%s\')"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64442, 00000, "deletion of elements, attributes, and so on not supported for binary"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that is not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64443, 00000, "illegal/unsupported change to %s \'%s\'"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that wasnot
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64444, 00000, "illegal/unsupported change within restriction of complex type \'%s\'"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64445, 00000, "Illegal in-place XMLSchema evolution operation"
// *Document: NO
// *Cause: An attempt was made to make an XMLSchema change that was not
// permitted through in-place XMLSchema evolution.
// *Action: Ensure that the XMLSchema changes specified in the XMLDiff
// argument to DBMS_XMLSCHEMA.inPlaceEvolve are permitted.
//
64446, 00000, "Operation %s returned error code %s"
// *Document: NO
// *Cause: A non-RDBMS routine (OraStream, LPX, XML/XSL processing, ...)
// returned an error code specific to that domain.
// *Action: Look up the error number and follow its appropriate
// corrective action.
//
64447, 00000, "Invalid localObject value"
// *Document: NO
// *Cause: An invalid value for the parameter localObject was provided.
// *Action: Correct value for the parameter localObject.
//
64448, 00000, "Failed to create a new stylesheet during %s"
// *Document: NO
// *Cause: Error is returned when trying to compile a new stylesheet.
// *Action: Check the stylesheet document.
//
64449, 00000, "Invalid input value specified"
// *Document: NO
// *Cause: invalid input argument specified
// *Action: Pass a valid input value
//
64450, 00000, "Table or XMLType column does not exist, is not user-visible or not of OR-xmltype"
// *Document: NO
// *Cause: Error is returned when trying to enable/disable indexes/constraints.
// *Action: Check the table/column name and make sure its a OR-based xmltype table/column.
//
64451, 00000, "Conversion of special character to escaped character failed."
// *Document: NO
// *Cause: An attempt to convert a special character to an escaped character failed.
// *Action: Remove the special character that cannot be escaped.
//
64452, 00000, "Bind value was null."
// *Document: NO
// *Cause: An attempt was made to use a bind value that was null.
// *Action: Provide a bind value.
//
64453, 00000, "Function 'XPath2TabColMapping' can only be invoked on table with object-relational (structured) storage mode."
// *Document: NO
// *Cause: An attempt was made to invoke the function 'XPath2TabColMapping' on a table with a non-object-relational storage model.
// *Action: N/A
//
64454, 00000, "Function 'XPath2TabColMapping' can only be invoked on column with object-relational (structured) storage mode."
// *Document: NO
// *Cause: An attempt was made to invoke the function 'XPath2TabColMapping' on a column with a non-object-relational storage model.
// *Action: N/A
//
64455, 00000, "Function 'XPath2TabColMapping' does not accept XPath with a parent axis."
// *Document: NO
// *Cause: An attempt was made to invoke the function 'XPath2TabColMapping' with an XPath expression that contained a parent axis.
// *Action: Remove parent axis.
//
64456, 00000, "Function 'RenameCollectionTable' was not able to map XPath to table."
// *Document: NO
// *Cause: The given XPath could not be mapped to a table..
// *Action: Verify the XPath expression or try the DOT notation in function 'RenameCollectionTable'.
//
64457, 00000, "No owner name provided in renameCollectionTable"
// *Document: NO
// *Cause: An attempt was made to call the procedure renameCollectionTable without an owner name.
// *Action: Provide an owner name.
//
64458, 00000, "No name provided for collection table"
// *Document: NO
// *Cause: An attempt was made to call the procedure renameCollectionTable without a name for the collection table.
// *Action: Provide a name for the collection table.
//
64459, 00000, "No owner name provided in xpath2TabColMapping"
// *Document: NO
// *Cause: An attempt was made to call the procedure xpath2TabColMapping without an owner name.
// *Action: Provide an owner name.
//
64460, 00000, "Function IndexXMLReferences can only be invoked on table with object-relational (structured) storage mode."
// *Document: NO
// *Cause: An attempt was made to invoke the function 'IndexXMLReferences' on a table with a non-object-relational storage model.
// *Action: N/A
//
64461, 00000, "Function IndexXMLReferences can only be invoked on column with object-relational (structured) storage mode."
// *Document: NO
// *Cause: An attempt was made to invoke the function 'IndexXMLReferences' on a column with a non-object-relational storage model.
// *Action: N/A
64462, 00000, "XPath cannot have predicates."
// *Document: NO
// *Cause: An attempt was made to invoke the function 'XPath2TabColMapping' with an XPath expression containing predicates.
// *Action: Remove predicates from XPath.
64463, 00000, "Parent table column could not be found."
// *Document: NO
// *Cause: The collection defined by the XPath expression could not be renamed because parent table column could not be found.
// *Action: Check user name input parameter.
64464, 00000, "XML event error"
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64465, 00000, "zero length XML data"
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64466, 00000, "hexadecimal to raw string conversion failed"
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64467, 00000, "XML diff failed"
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64468, 00000, "XML patch failed"
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64469, 00000, "invalid namespace encountered"
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64470, 00000, "Cannot allocate a new VM. All VMs are in use."
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64471, 00000, "XSLT compiler creation failed"
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64472, 00000, "XSL VM creation failed"
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64473, 00000, "copy to LOB buffer failed"
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64474, 00000, "cannot set VM parameter"
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64475, 00000, "null query in query webservice"
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64476, 00000, "invalid bindXML value"
// *Document: NO
// *Cause: The specified error occurred in XDB.
// *Action: Correct the error or contact Oracle Support Services.
64477, 00000, "Multiple token tables are not supported."
// *Cause: An attempt was made to create a new token table. If encountered
// during an import, a critical patch was possibly missing on the
// export database.
// *Action: Use the default token table. If encountered during an import,
// apply the appropriate patch on the export database and try the
// export and import again.
64478, 00000, "fix invalid XDB schema types"
// *Document: NO
// *Cause: Internally used to fix invalid XDB schema types in a pluggable
// database.
// *Action:
64479, 00000, "element '%s' is missing '%s' annotation; schema cannot be registered by common users"
// *Cause: A common user tried to register a schema with missing type name
// annotations. All type names from the schema and its dependencies
// should be annotated.
// *Action: Ensure that the schema being registered and its dependencies have
// all the element type names annotated.
64480, 00000, "element '%s' is missing default table name annotation; schema cannot be registered by common users"
// *Cause: A common user tried to register a schema with missing default
// table name annotations. All table names from the schema and its
// dependencies should be annotated.
// *Action: Make sure the schema being registered and its dependencies have
// all the default table names annotated.
64481, 00000, "invalid tablespace name"
// *Cause: The tablespace name did not have a closing double quotation mark.
// *Action: Ensure that the last character is also a double quotation mark.
64482, 00000, "Moving XDB to %s is not allowed."
// *Cause: An attempt was made to move XDB to a system tablespace.
// *Action: Ensure that the target tablespace is not a system tablespace.
64483, 00000, "New tablespace %s is smaller than the current tablespace %s."
// *Cause: The new tablespace was smaller than the current tablespace.
// *Action: Ensure that the new tablespace is larger than the current
// tablespsace.
64484, 00000, "New tablespace %s is not ASSM."
// *Cause: The new tablespace was not Automatic Segment Space Management (ASSM).
// *Action: Ensure that the new tablespace is ASSM.
64485, 00000, "invalid pathname"
// *Cause: An invalid resource handle or path name was passed.
// *Action: Pass a valid path name.
64486, 00000, "The internal table is empty."
// *Cause: The internal input table containing the schemas was empty.
// *Action: Insert schemas to be moved into the internal table and invoke procedure.
64487, 00000, "XML schema %s exists for user %s"
// *Cause: The XML schema existed for the user.
// *Action: Ensure that the XML schema is a new one.
64488, 00000, "cannot migrate inherited type %s"
// *Cause: The inherited type could not be migrated.
// *Action: Ensure that it is not inherited by any other type.
64489, 00000, "cannot migrate XML schema %s"
// *Cause: The XML schema could not be migrated.
// *Action: Ensure that the XML schema can be migrated.
64490, 00000, "cannot migrate owner from %s to %s for XML schema %s"
// *Cause: The owner could not be migrated for the XML schema.
// *Action: Ensure that the XML schema can be migrated.
64491, 00000, "cannot grant XML schemas to public"
// *Cause: The XML schema could not be granted to public.
// *Action: Ensure that the XML schema can be granted to public.
64492, 00000, "The level up the hierarchy must be greater than 0."
// *Cause: The level up the hierarchy was less than 1.
// *Action: Ensure that the level up the hierarchy is greater than 0.
64493, 00000, "The resource type is unknown."
// *Cause: The resource type was not recognized.
// *Action: Ensure that the resource is valid.
//
64494, 00000, "Substitution group is not supported when maintainDOM is not set."
// *Cause: maintainDOM was not set to TRUE.
// *Action: Ensure that maintainDOM is set to TRUE.
//
64495, 00000, "XQuery data model has to be allowed."
// *Cause: XQuery data model is not allowed.
// *Action: Ensure that XQuery data model is allowed.
//
64496, 00000, "Position predicate on out-of-line table is not supported when maintainDOM is set to FALSE."
// *Cause: An attempt was made to use position predicate on an out-of-line table when maintainDOM was set to FALSE.
// *Action: Ensure that maintainDOM is set to TRUE.
//
64497, 00000, "File access not over XDB repository is not allowed on server side."
// *Cause: For security reasons, ftp and http access over XDB repository is not allowed on server side.
// *Action: Have file access over XDB repository only or do not specify file access.
//
64498, 00000, "FTP and HTTP access over XDB repository is not allowed on server side"
// *Cause: For security reasons, ftp and http access over XDB repository is not allowed on server side.
// *Action: Do not specify FTP or HTTP access over XDB repository.
//
64499, 00000, "ORADB operations not allowed on client-side."
// *Cause: ORADB client access was a security issue.
// *Action: Do not specify ORADB operation on client-side.
//
////////////////////////////////////////////////////////
// XML PL/SQL package errors: 64500-64506
////////////////////////////////////////////////////////
64500, 00000, "invalid PL/SQL XML parser handle"
// *Cause: The PL/SQL XML parser handle was invalid.
// *Action: Ensure that the PL/SQL XML parser handle is valid.
//
64501, 00000, "invalid PL/SQL XSL processor handle"
// *Cause: The PL/SQL XSL processor handle was invalid.
// *Action: Ensure that the PL/SQL XSL processor handle is valid.
//
64502, 00000, "invalid PL/SQL XSL stylesheet handle"
// *Cause: The PL/SQL XSL stylesheet handle was invalid.
// *Action: Ensure that the PL/SQL XSL stylesheet handle is valid.
//
64503, 00000, "invalid PL/SQL DOM handle"
// *Cause: The PL/SQL DOM handle was invalid.
// *Action: Ensure that the PL/SQL DOM handle is valid.
//
64504, 00000, "invalid PL/SQL DOM %s handle"
// *Cause: The named PL/SQL DOM handle was invalid.
// *Action: Ensure that the named PL/SQL DOM handle is valid.
//
64505, 00000, "NULL or invalid %s argument specified"
// *Cause: The named argument was either invalid or was specified as a NULL.
// *Action: Specify a non-null, valid argument.
//
64506, 00000, "procedure or function not supported"
// *Cause: The PL/SQL procedure or function was not supported.
// *Action: Modify the code to avoid usage of the PL/SQL procedure or function.
//
64507, 00000, "ACL path is not valid."
// *Cause: ACL path was not valid.
// *Action: Ensure the ACL path is valid.
//
64508, 00000, "XSLT parameter is not valid."
// *Cause: XSLT parameter was not valid.
// *Action: Ensure the XSLT parameter is valid.
//
/////////////////////////////////////////////////////////////////////////////
// 64600 - 64609 are reserved for sequence errors
/////////////////////////////////////////////////////////////////////////////
64600, 00000, "duplicate or conflicting SCALE or EXTEND specifications"
// *Document: YES
// *Cause: The specifications were either a duplicate of each other or were conflicting.
// *Action: Remove the duplicate or conflicting specification.
64601, 00000, "duplicate RESTART specified"
// *Document: YES
// *Cause: The specified RESTART was a duplicate.
// *Action: Remove the duplicate specification.
64602, 00000, "CREATE SEQUENCE cannot have a RESTART clause"
// *Document: YES
// *Cause: The RESTART clause was specified in the CREATE SEQUENCE statement.
// *Action: Remove the RESTART clause.
64603, 00000, "NEXTVAL cannot be instantiated for %s. Widen the sequence by %s digits or alter sequence with SCALE EXTEND."
// *Document: YES
// *Cause: The NOEXTEND constraint was specified for the scalable sequence and the generated value was wider than the sequence maximum value.
// *Action: Widen the sequence maximum value or remove the NOEXTEND constraint.
/////////////////////////////////////////////////////////////////////////////
/ 64610 - 64619 are reserved for PL/SQL package UTL_CALL_STACK
/////////////////////////////////////////////////////////////////////////////
64610, 00000, "bad depth indicator"
// *Document: NO
// *Cause: There was no subprogram, error, or backtrace at the specified stack
// depth.
// *Action: Specify a depth for which there is a subprogram, error,
// or backtrace.
//
////////////////////////////////////////////////////////////////////////////
64620, 00000, "duplicate user tablespace specification"
// *Cause: An attempt was made to create more than one user tablespace during
// database creation.
// *Action: Modify the command to contain only one user tablespace.
//
64621, 00000, "SQL statement length (%s) exceeds maximum allowed length (%s)"
// *Cause: An attempt was made to issue a SQL statement that exceeded the
// maximum allowed length of a statement.
// *Action: Modify the SQL statement or the views to which it refers to fit
// within the maximum length or split the SQL statement.
//
/////////////////////////////////////////////////////////////////////////////
// BEGIN error messages reserved for Persistent Memory (64670 - 64699)
/////////////////////////////////////////////////////////////////////////////
64670, 00000, "failure to create persistent memory region"
// *Cause: An attempt to create a persistent memory region failed.
// *Action: Check the alert file for more information.
64671, 00000, "failure to delete persistent memory region"
// *Cause: An attempt to delete a persistent memory region failed.
// *Action: Check the alert file for more information.
64672, 00000, "failure to attach to a persistent memory region"
// *Cause: A process failed to attach to a persistent memory region.
// *Action: Check the alert file for more information.
64673, 00000, "failure to detach from a persistent memory region"
// *Cause: A process failed to detach from a persistent memory region.
// *Action: Check the alert file for more information.
64674, 00000, "failure to allocate persistent memory region"
// *Cause: System did not have %llu bytes of available persistent memory.
// *Action: Allocate the required amount of persistent memory on the system.
64675, 00000, "failure to open a persistent memory region"
// *Cause: The system-wide limit on number of open files has been reached.
// *Action: Increase the system open file descriptors limit.
64676, 00000, "internal error occurred"
// *Cause: An internal error occurred while doing an operation on persistent memory.
// *Action: Contact Oracle Support Services.
64677, 00000, "failure to query system state"
// *Cause: An attempt to query system state failed.
// *Action: Check the alert file for more information.
64678, 00000, "enables XGA tracing"
// *Cause: Tracing was enabled while doing an operation on XGA memory.
// *Action: Set this event only under the supervision of Oracle Support Services.
//
/////////////////////////////////////////////////////////////////////////////
// BEGIN error messages reserved for Recovery Appliance (64700 - 64999)
/////////////////////////////////////////////////////////////////////////////
64700, 00000, "Recovery Appliance is shutting down"
// *Cause: The Recovery Appliance was in the process of shutting
// down. This message is recorded in the incident log for the
// Recovery Appliance. When the shutdown completes, the
// incident is marked as FIXED.
// *Action: Wait for the Recovery Appliance to complete its shutdown.
64701, 00000, "storage location %s can no longer honor its reservations."
// *Cause: The specified storage location did not contain enough space to
// fulfill the reservations of all of the databases assigned to it.
// This error will be seen if a storage location lost part of its
// disk space and was in the process of being repaired.
// *Action: Either shrink the reservations for the databases contained within
// the storage location or add additional disk space to the storage
// location.
64702, 00000, "error repairing container files for storage location %s:\n%s"
// *Cause: An error was returned while trying to rebuild or repair the
// container files used to store data from protected databases.
// *Action: The subsequent error will identify the error that needs to be
// addressed before the Recovery Appliance can be repaired.
64703, 00000, "resource error detected"
// *Cause: A task needed to be interrupted because it detected a resource
// limitation such as insufficient temporary table space or a
// snapshot being too old. It will be retried once the contention
// for the resource decreases.
// The secondary messages will identify the resource that has been
// exhausted.
// *Action: If this error occurs rarely, no user action is required. If the
// condition becomes persistent, the Recovery Appliance administrator
// should increase the resource that is exhausted.
64704, 00000, "unbalanced parenthesis in \"%s\" at column %s"
// *Document: NO
// *Cause: The list of storage destinations contained an entry with
// an unbalanced parenthesis or parentheses inverted. For example )(.
// *Action: Correct the syntax error and retry the operation.
64705, 00000, "no destination in \"%s\" at column %s"
// *Cause: The storage destination contained a syntax error.
// *Action: Correct the syntax error and retry the operation.
64706, 00000, "bad storage size in \"%s\" at column %s"
// *Document: NO
// *Cause: The list of storage destinations contained an entry that
// specified an invalid storage size. While a storage size
// specification is not required, if specified, it must
// be enclosed in balanced parentheses, begin with a string of
// numbers that evaluate to a size greater than zero and be optionally
// terminated by a single character specifying the units of the number
// string: K for kilobytes, M for megabytes, G for gigabytes, T for
// terabytes, P for petabytes, E for exabytes, Z for zetabytes, and Y
// for yottabytes. For example, (32T).
// *Action: Correct the syntax error and retry the operation.
64707, 00000, "no storage size in \"%s\" at column %s"
// *Document: NO
// *Cause: The list of storage destinations contained an entry that
// specified a non-ASM-based storage destination but did not
// provide a storage size. Non-ASM-based storage destinations
// must specify both a storage destination name and a storage
// size.
// *Action: Correct the syntax error and retry the operation.
64708, 00000, "more than one polling_location in \"%s\" at column %s"
// *Cause: More than one polling_location was specified.
// Only one polling_location is allowed.
// *Action: Specify only one polling destination directory and
// retry the operation.
64709, 00000, "ASM polling_location is not supported in \"%s\" at column %s"
// *Cause: The polling_location specified an ASM-based location.
// Only non-ASM-based polling_locations are supported.
// *Action: Specify one non-ASM polling destination and retry the operation.
64710, 00000, "polling_location must not have storage size in \"%s\" at column %s"
// *Document: NO
// *Cause: The polling_location contained a size specification.
// A polling_location must contain only a file specification.
// *Action: Remove the size specification and retry the operation.
64711, 00000, "storage destination do not reference an ASM diskgroup"
// *Cause: The storage destination referenced a non-ASM storage location.
// Only ASM-based storage destinations are allowed. The operation
// has been rolled back.
// *Action: Correct the syntax error and retry the operation.
64712, 00000, "non-ASM storage destination"
// *Document: NO
// *Cause: The storage destinations (considering both existing and new)
// contained more than one non-ASM storage destination.
// Only ASM-based storage destinations are allowed. The operation
// has been rolled back.
// *Action: Correct the syntax error and retry the operation.
64713, 00000, "requested size %s for %s was too small; already using %s"
// *Document: YES
// *Cause: The size requested for the storage destination was smaller than
// its current size.
// *Action: Increase the requested size and retry the operation.
64714, 00000, "requested size %s for %s was larger than total available space %s"
// *Document: YES
// *Cause: The size requested for the storage destination was larger than its
// current used space plus its currect free space.
// *Action: Decrease the requested size and retry the operation.
64715, 00000, "redundancy type \"%s\" for diskgroup %s is invalid"
// *Cause: The redundancy type for the specified diskgroup was not
// one of {NORMAL | HIGH | EXTERN}.
// *Action: Correct the redundancy type of the diskgroup and
// retry the operation.
64716, 00000, "storage location %s allocation size %s does not equal diskgroup %s allocation size %s"
// *Cause: The minimum allocation size of the specified storage location
// was not the same as the specified diskgroup allocation unit size.
// *Action: Specify a different diskgroup or a different storage location and retry the operation.
64717, 00000, "network chunk size %s is not a multiple of diskgroup %s allocation size %s"
// *Cause: The configured network chunk size
// was not a multiple of the specified diskgroup allocation unit size.
// *Action: Specify a different diskgroup or reconfigure the network chunk size
// and retry the operation.
64718, 00000, "diskgroup %s allocation size %s is not a power of two"
// *Cause: The diskgroup allocation unit size was not a power of two.
// *Action: Specify a different diskgroup and retry the operation.
64719, 00000, "diskgroup %s allocation size %s is less than two megabytes %s"
// *Cause: The diskgroup allocation unit size was less than two megabytes.
// *Action: Specify a different diskgroup and retry the operation.
64720, 00000, "no containers were created for storage location %s"
// *Cause: No storage was allocated and initialized for the specified storage location.
// *Action: Specify a different diskgroup for the storage location, increase the size of
// the diskgroup, or reduce the size of the storage location and retry the operation.
64721, 00000, "reserved space %s is less than the minimum reservation %s"
// *Cause: No storage was allocated and initialized for the specified storage location.
// *Action: Specify a different diskgroup for the storage location, increase the size of
// the diskgroup, or reduce the size of the storage location and retry the operation.
64722, 00000, "number of drives must be greater than zero"
// *Cause: The specified number of tape drives was NULL or was less than or equal to zero.
// *Action: Specify a number of tape drives greater than 0 and retry the operation.
64723, 00000, "number of drives reserved for restore operations must be greater than or equal to zero"
// *Cause: The number of tape drives reserved for restore operations was NULL or was less than zero.
// *Action: Specify a number of tape drives reserved for restore operations greater than
// or equal to zero and retry the operation.
64724, 00000, "number of restore drives %s too large; must be less than %s"
// *Cause: The number of tape drives reserved for restore operations was at least
// as large as the total number of drives available. The number of tape drives
// reserved for restore operations must be at least one less than the total
// number of drives available.
// *Action: Specify a number of tape drives reserved for restore operations less than
// the total number of drives available and retry the operation.
64725, 00000, "number of streams must be greater than zero"
// *Cause: The number of streams was less than or equal to zero.
// *Action: Specify a number of streams greater than zero and retry the operation.
64726, 00000, "number of streams %s too large; must be no larger than %s"
// *Cause: The number of streams was larger
// than the total number of drives available. The number of streams
// must be no larger than the total number of drives available.
// *Action: Reduce the number of available streams and retry the operation.
64727, 00000, "number of copies %s not in the range 1 through 4"
// *Cause: The number of copies was either NULL or not in the range
// 1 through 4 inclusive.
// *Action: Specify a number of copies in the range 1 through 4 and retry the operation.
64728, 00000, "replication server name length %s is too long"
// *Cause: The replication server name was longer than 128 characters.
// *Action: Specify a replication server name shorter than 128 characters and retry the operation.
64729, 00000, "replication server proxy port %s must be greater than zero"
// *Cause: The replication server proxy port number was less than or equal to zero.
// *Action: Specify a replication server proxy port number greater than zero and retry the operation.
64730, 00000, "replication server proxy URL provided but proxy port is NULL"
// *Cause: A replication server proxy URL was provided but a proxy port number was not.
// If either a proxy URL or a proxy port are specified, both must be specified.
// *Action: Specify both a replication server URL and a replication server proxy port number
// and retry the operation.
64731, 00000, "replication server proxy port provided but proxy URL is NULL"
// *Cause: A replication server proxy port number was provided but a proxy URL was not.
// If either a proxy URL or a proxy port are specified, both must be specified.
// *Action: Specify both a replication server URL and a replication server proxy port number
// and retry the operation.
64732, 00000, "HTTP server not configured at replication host"
// *Cause: The HTTP server at the replication host site has not been configured.
// *Action: Configure the HTTP server at the replication host site
// and retry the operation.
64733, 00000, "unable to move individual backup piece with BP_KEY %s; not a KEEP backup"
// *Cause: An attempt was made to move an individual backup piece, but the backup set
// of which this backup piece was a member was not a KEEP backup.
// *Action: Specify a backup piece key that is a member of a KEEP backup set
// and retry the operation.
64734, 00000, "storage size is less than minimum %s in \"%s\" at column %s"
// *Document: NO
// *Cause: The specified storage size was less than the minimum required.
// *Action: Specify a larger storage size and retry the operation.
64735, 00000, "unknown incarnation detected at Recovery Appliance, need catalog resync"
// *Cause: A new archived log or backup set belonging to the new incarnation
// was received at Recovery Appliance.
// *Action: Using RMAN, connect to the Recovery Appliance as a recovery catalog,
// primary database as target database and perform the
// resynchronization operation using the RESYNC CATALOG RMAN command.
// If this error occurred at downstream of the Recovery Appliance
// (in a replicated Recovery Appliance setup), the reconcile operation
// fixes this error automatically when the same error is fixed at the
// upstream Recovery Appliance.
64736, 00000, "Task ID %s of type %s has been interrupted %s times."
// *Cause: The specified task was restarted an unexpected number of
// times. Tasks get interrupted when there is competition for
// resources. This is only a warning. It does not necessarily
// indicate a problem with the Recovery Appliance.
// *Action: If these problems persist for long periods, contact
// Oracle Support Services.
64737, 00000, "unable to copy a full backup of database %s to tape or replicated Recovery Appliance"
// *Cause: While creating a full database backup to tape or to a replicated
// recovery appliance, level 0 backups of one or more data files
// were missing.
// *Action: Query the RA_SBT_TEMPLATE_MDF view to determine the data files
// for which backups are missing. If using the "incremental forever"
// backup strategy, perform a level-0 incremental backup for the given
// database and retry the operation.
64738, 00000, "guaranteed copy suspended for database %s"
// *Cause: One of the following operations was performed resulting in the
// database using more than its allotted disk space:
// - UPDATE_DB lowering the DISK_SPACE_RESERVE value.
// - UPDATE_PROTECTION_POLICY setting the guaranteed_copy
// parameter to YES
// - DELETE_SBT_LIBRARY where backup data for the given database
// existed.
// New backup requests may be stalled until the system can recompute
// the safety of allowing additional backup data or backup data may
// be lost.
// *Action: This event can be avoided by ensuring backups are written
// to tape in a timely manner. Conversely, one should avoid the
// activities listed in the Cause statement when backups are not
// being written to tape in a timely manner.
64739, 00000, "RECOVERY_WINDOW_GOAL is lost for database %s"
// *Cause: The recovery window golad was not available for the current set of
// backups. The recovery window goal in the protection policy
// indicates a desire to be able to restore and recover to any point
// in time within that range. This is not possible given the current
// set of backups. Possible reasons are missing archive log backups,
// missing data file backups or lack of reserved disk space.
// *Action: Ensure that backups are done regularly. Ensure that your disk reserved
// space value is set high enough to support your goals. Query RA_DATABASE view
// for DISK_RESERVED_SPACE and RECOVERY_WINDOW_SPACE parameters and compare these
// two parameters to ensure enough space has been provisioned to meet your
// goals. However, you may use the DBMS_RA.UPDATE_PROTECTION_POLICY procedure
// to increase the DISK_RESERVED_SPACE value to ensure additional backups are
// saved. Also, check for KEEP backups consuming space on the disk and decide
// if they should be moved to tape or other disk storage.
64740, 00000, "Backups from database %s have not been seen for more than UNPROTECTED_WINDOW period"
// *Cause: An UNPROTECTED_WINDOW parameter in protection policy has been specified
// and the Recovery Appliance has not received sufficient archive log backups
// or data file backups from the given target database for at least that period.
// *Action: Ensure that backups are being performed in a timely manner and that, if set
// up, redo logs or backups are being sent to the Recovery Appliance.
64741, 00000, "Scheduler %s running task %s of type %s did not stop after %s requests."
// *Cause: The specified Recovery Appliance scheduler process could not be stopped.
// *Action: If these problems persist for long periods, contact
// Oracle Support Services.
64742, 0000, "database %s is being deleted"
// *Cause: The current command failed because the database was in the process of being deleted.
// *Action: No action is necessary.
64743, 0000, "UNUSED"
// *Document: NO
// *Cause:
// *Action:
64744, 00000, "Argument %s is null, invalid, or out of range."
// *Cause: The argument was expecting a non-null, valid value but the
// argument value passed in was null, invalid, or out of range.
// *Action: Check your program and correct the caller of the routine
// to not pass a null, invalid or out-of-range argument value.
64745, 00000, "Name length is %s characters; maximum length is %s characters."
// *Cause: The length of the name exceeded the limit.
// *Action: Specify a shorter name and retry the operation.
64746, 00000, "Name contains invalid characters."
// *Cause: The name incorrectly started with "_", "-", ":", "#" or digits or contained
// non-alphanumeric characters. Verify that all other double quotation marks,
// if any, in the string are adjacent pairs of double quotation marks. Double
// quotation marks must not be used in the middle of the name.
// *Action: Change the name and exclude the invalid characters.
64747, 00000, "Name contains invalid character \"%s\" at the position [%s]."
// *Cause: The name incorrectly started with "_", "-", ":", "#" or digits or contained
// non-alphanumeric characters. Verify that all other double quotation marks,
// if any, in the string are adjacent pairs of double quotation marks. Double
// quotation marks must not be used in the middle of the name.
// *Action: Change the name and exclude the invalid characters.
64748, 00000, "trace file writing initiated using %s"
// *Cause: The configuration of the Recovery Appliance was modified to
// enable the production of trace files. Trace files have the
// capacity to exhaust disk space on the Recovery Appliance.
// *Action: Turn off the tracing when it is no longer required.
64750, 00000, "Instance %s is unable to access %s."
// *Cause: The Recovery Appliance was unable to find a file that
// is required for its operation.
// *Action: Ensure that the file system of the specified file is available
// on the specified instance.
64751, 00000, "Replication setup error during %s. replication server:%s database:%s."
// *Cause: The Recovery Appliance was unable to complete the configuration and setup
// of replication for the database specified.
// *Action: Validate that the downstream replication server is properly configured
// and all network communication paths are valid.
64752, 00000, "storage unavailable for new redo or backups for database %s"
// *Cause: There was a failure while backing up redo or copying backups from a polling location.
// This condition may be due to one of the following reasons:
// * An individual backup piece exceeded the database protection
// policy DISK_RESERVE_SPACE value. * Guaranteed_copy is enabled
// but not enough data has been spooled to tape. * Misconfiguration
// of the storage location size.
// *Action: Check for the value of DISK_RESERVED_SPACE and storage location uses.
64753, 00000, "Incorrect object type specified; specified %s, expected %s"
// *Cause: An incorrect object type was given to an API command.
// *Action: Use the object-specific API. For example, use 'resume_replication_server'
// instead of 'resume_sbt_library'.
64754, 00000, "unable to perform operation with associated tape or replication objects"
// *Cause: An attempt to execute 'update_db' or 'update_protection_policy' and
// change storage locations with a replication server or tape job associated with the
// protection policy failed.
// *Action: Create a temporary protection policy that has the same storage location as the
// current protection policy with the tape and replication attributes of the target
// protection policy, update to the temporary protection policy, and then finally
// update to the target protection policy.
64755, 00000, "failed to delete database %s; the Recovery Appliance is not running"
// *Cause: An attempt was made to delete a database, but the
// Recovery Appliance has been deactivated by the administrator.
// *Action: Have the Recovery Appliance administrator execute
// DBMS_RA.STARTUP_RECOVERY_APPLIANCE and retry the delete_db()
// operation.
64756, 0000, "current task is being canceled"
// *Document: NO
// *Cause: The task is no longer needed and is being run down.
// *Action: None. This is not a user visible exception.
64757, 0000, "unable to restore backup piece with BP_KEY %s"
// *Cause: An attempt was made to restore the specified backup piece which
// resulted in an error. An explanation of the error appears in the
// following messages.
// *Action: Verify the correctness of the backup piece. If it is corrupt,
// either delete it or replace it.
64758, 0000, "unable to grow delta store metadata in tablespace %s"
// *Cause: Additional extents could not be allocated for the tables used to
// to implement the delta store.
// *Action: Add additional storage to the indicated tablespace.
64759, 0000, "Recovery Appliance is leaving restricted resources state"
// *Cause: The Recovery Appliance ended its restrictions on task
// execution. The restricted resources state was entered when
// tasks could not run due to insufficient temporary table space or
// insufficient undo space. At that time, resource intensive tasks
// were put into RESOURCE_WAIT state.
// *Action: None. This is only an informational message entered in the
// alert log.
64760, 0000, "Database %s has had tasks in ordering wait state for over %s days."
// *Cause: The specified database had an INDEX_BACKUP task that could not
// be run because the task did not tile against the delta store.
// An incremental backup piece
// will not tile into the delta store when the full backup that it
// was built upon is not found in the delta store.
// *Action: Provide the missing incremental backups for the database. If no
// other incremental backups can be found, provide a new full backup
// for the database.
64761, 0000, "disk group %s is not usable by the Recovery Appliance"
// *Cause: A disk group was supplied to either the create_storage_location
// or update_storage_location APIs that was not previously prepared
// by the installation software for the Recovery Appliance.
// *Action: Run the ra_update procedure to process the disk group and retry
// the API.
/////////////////////////////////////////////////////////////////////////////
// END error messages reserved for Recovery Appliance (64700 - 64999)
/////////////////////////////////////////////////////////////////////////////
/////////////////////////////////////////////////////////////////////////////
/ 65000 - 65399 are reserved for CONSOLIDATED DATABASES ERRORS
/////////////////////////////////////////////////////////////////////////////
65000, 00000, "missing or invalid pluggable database name"
// *Cause: A valid pluggable database name was not present where required.
// *Action: Reissue the statement with a valid pluggable database name.
//
65001, 00000, "missing or invalid administrative user name"
// *Cause: A valid administrative user name was not present where required
// by the syntax of CREATE PLUGGABLE DATABASE statement.
// *Action: Reissue the CREATE PLUGGABLE DATABASE statement with a valid
// administrative user name.
//
65002, 00000, "missing or invalid administrative user password"
// *Cause: A valid administrative user password was not present where
// required by the syntax of CREATE PLUGGABLE DATABASE statement.
// *Action: Reissue the CREATE PLUGGABLE DATABASE statement with a valid
// administrative user password.
//
65003, 00000, "missing or invalid XML file name"
// *Cause: A valid XML file name was not present where required by the
// syntax of CREATE PLUGGABLE DATABASE statement.
// *Action: Reissue the CREATE PLUGGABLE DATABASE statement with a valid
// XML file name.
//
65004, 00000, "missing or invalid database link name"
// *Cause: A valid database link name was not present where required by the
// syntax of CREATE PLUGGABLE DATABASE statement.
// *Action: Reissue the CREATE PLUGGABLE DATABASE statement with a valid
// database link name.
//
65005, 00000, "missing or invalid file name pattern for file - %s"
// *Cause: Either source or replacement file name pattern was missing or
// invalid in a SOURCE_FILE_NAME_CONVERT or FILE_NAME_CONVERT clause.
// *Action: Correct the SOURCE_FILE_NAME_CONVERT or FILE_NAME_CONVERT clause
// and reissue the statement.
//
65006, 00000, "missing or invalid ENABLE PLUGGABLE DATABASE clause"
// *Cause: An ENABLE PLUGGABLE DATABASE clause was not present where required
// by the syntax of CREATE DATABASE statement.
// *Action: Reissue the CREATE DATABASE statement with a valid
// ENABLE PLUGGABLE DATABASE clause.
//
65007, 00000, "duplicate ENABLE PLUGGABLE DATABASE clause"
// *Cause: A duplicate ENABLE PLUGGABLE DATABASE clause was specified
// in a CREATE DATABASE statement.
// *Action: Reissue the CREATE DATABASE statement with a valid
// ENABLE PLUGGABLE DATABASE clause.
//
65008, 00000, "missing or invalid SEED clause"
// *Cause: A SEED clause was not present where required by the
// syntax of CREATE DATABASE statement.
// *Action: Reissue the CREATE DATABASE statement with a valid SEED clause.
//
65010, 00000, "maximum number of pluggable databases created"
// *Cause: The number of pluggable databases exceeded either the MAX_PDBS
// property value or the maximum supported number of pluggable
// databases.
// *Action: Drop the existing pluggable databases and retry the operation.
//
65011, 00000, "Pluggable database %s does not exist."
// *Cause: User attempted to specify a pluggable database
// that does not exist.
// *Action: Check DBA_PDBS to see if it exists.
//
65012, 00000, "Pluggable database %s already exists."
// *Cause: User attempted to create a pluggable database
// with a name that already exists.
// *Action: Check DBA_PDBS to see if the name exists.
//
65013, 00000, "invalid CONTAINER clause"
// *Cause: An invalid CONTAINER clause was encountered.
// *Action: Reissue the DDL statement with a valid CONTAINER clause.
//
65014, 00000, "invalid SHARING clause"
// *Cause: An invalid SHARING clause was encountered.
// *Action: Reissue the DDL statement with a valid SHARING clause.
//
65015, 00000, "missing or invalid container name"
// *Cause: A valid container name was not present where required
// by the syntax of ALTER SESSION SET CONTAINER or
// ALTER USER ... SET|ADD|REMOVE CONTAINER_DATA statement.
// *Action: Reissue the statement with a valid container name.
//
65016, 00000, "FILE_NAME_CONVERT must be specified"
// *Cause: Data files, and possibly other files, needed to be copied as a
// part of creating a pluggable database. However, Oracle Managed
// Files (OMF) was not enabled, PDB_FILE_NAME_CONVERT was not defined,
// and there was a failure to specify the FILE_NAME_CONVERT clause.
// *Action: Enable OMF or define PDB_FILE_NAME_CONVERT system parameter before
// issuing CREATE PLUGGABLE DATABASE statement, or specify
// FILE_NAME_CONVERT clause as a part of the statement.
//
65017, 00000, "seed pluggable database may not be dropped or altered"
// *Cause: User attempted to drop or alter the Seed pluggable database which
// is not allowed.
// *Action: Specify a legal pluggable database name.
//
65018, 00000, "FILE_NAME_CONVERT or NOCOPY must be specified"
// *Cause: Oracle Managed Files (OMF) was not enabled and
// PDB_FILE_NAME_CONVERT was not defined.
// The FILE_NAME_CONVERT or the NOCOPY clause was not specified
// as a part of creating a pluggable database using data files.
// *Action: Enable OMF or define PDB_FILE_NAME_CONVERT system parameter before
// issuing CREATE PLUGGABLE DATABASE statement, or specify
// FILE_NAME_CONVERT clause or NOCOPY as a part of the statement.
//
65019, 00000, "pluggable database %s already open"
// *Cause: An attempt was made to open a pluggable database that was already
// opened.
// *Action: Check the OPEN_MODE column in V$PDBS view.
//
65020, 00000, "pluggable database %s already closed"
// *Cause: An attempt was made to close a pluggable database that was already
// closed.
// *Action: Check the OPEN_MODE column in V$PDBS view.
//
65021, 00000, "illegal use of SHARING clause"
// *Cause: A SHARING clause was encountered in unexpected context.
// *Action: Do not use SHARING clause outside of Oracle-supplied scripts.
//
65022, 00000, "CONTAINER clause already specified"
// *Cause: A statement contained multiple CONTAINER clauses.
// *Action: Eliminate redundant CONTAINER clauses.
//
65023, 00000, "active transaction exists in container %s"
// *Cause: A statement attempted to create a new transaction in the current
// container while there was an active transaction in another container.
// *Action: Switch to the container with the active transaction and commit, rollback
// or detach the active transaction before attempting to issue any
// statement that will attempt to create a new transaction in another
// container.
//
65024, 00000, "Pluggable database %s is not open."
// *Cause: An operation was attempted on a pluggable database that was not
// open.
// *Action: Open the pluggable database using appropriate open mode.
//
65025, 00000, "Pluggable database %s is not closed on all instances."
// *Cause: An operation was attempted on a pluggable database that was not
// closed on all Oracle RAC instances.
// *Action: Close the pluggable database on all instances and retry the
// operation.
//
65026, 00000, "XML metadata file error : %s"
// *Cause: An error occurred while trying to parse or write to the XML metadata file.
// *Action: Check that the XML metadata file exists and is readable.
//
65027, 00000, "XML metadata file error while getting node or value for (%s - %s)"
// *Cause: An error occurred while trying to parse the XML metadata file.
// *Action: Check and correct the XML metadata file.
//
65028, 00000, "Unable to open plugin data file at path %s"
// *Cause: Error occurred while trying to open the data file.
// *Action: Check that the data file exists at the path.
//
65029, 00000, "a Local User may not grant or revoke a Common Privilege or Role"
// *Cause: A Local User issued a GRANT or REVOKE statement specifying
// CONTAINER=ALL, which is illegal.
// *Action: Remove CONTAINER=ALL from the statement.
//
65030, 00000, "cannot grant a privilege commonly to a local user or role"
// *Cause: A GRANT statement was issued specifying CONTAINER=ALL and naming
// a local user or role as a grantee, which is illegal.
// *Action: If trying to grant a privilege locally, remove CONTAINER=ALL from
// the GRANT statement. If trying to grant a privilege commonly,
// remove local users and roles from the list of grantees.
//
65031, 00000, "cannot revoke a privilege commonly from a local user or role"
// *Cause: A REVOKE statement was issued specifying CONTAINER=ALL and naming
// a local user or role as a revokee, which is illegal.
// *Action: If trying to revoke a privilege locally, remove CONTAINER=ALL
// from the REVOKE statement. If trying to revoke a privilege
// commonly, remove local users and roles from the list of revokees.
//
65032, 00000, "A local role may only be granted or revoked within the current container."
// *Cause: A GRANT or REVOKE statement was issued specifying
// CONTAINER=ALL and listing a local role among the roles
// to be granted or revoked, which is illegal.
// *Action: If trying to grant or revoke a local role, remove CONTAINER=ALL
// from the REVOKE statement. If trying to grant or revoke roles
// commonly, remove local roles from the list of roles being
// granted or revoked.
//
65033, 00000, "a common privilege may not be granted or revoked on a local object"
// *Cause: A GRANT or REVOKE statement was issued specifying
// CONTAINER=ALL and naming a local object on which privileges are
// to be granted or revoked, which is illegal.
// *Action: Remove CONTAINER=ALL from the statement.
//
65034, 00000, "PDB describe output file not specified"
// *Cause: User attempted to describe a pluggable database without specifying
// an output XML file location.
// *Action: Specify an output file location for describe
//
65035, 00000, "unable to create pluggable database from %s"
// *Cause: An attempt was made to clone a pluggable database that did not have
// local undo enabled.
// *Action: Enable local undo for the PDB and and retry the operation.
//
65036, 00000, "pluggable database %s not open in required mode"
// *Cause: Attempted to perform an operation on a pluggable database in
// incorrect open mode.
// *Action: Open the pluggable database in the mode required for this operation
//
65037, 00000, "A privilege on a local user may not be granted or revoked commonly."
// *Cause: A GRANT or REVOKE statement was issued specifying
// CONTAINER=ALL and naming a local user on which privileges are
// to be granted or revoked, which is illegal.
// *Action: Remove CONTAINER=ALL from the GRANT or REVOKE statement.
//
65039, 00000, "container identifier column missing or is of unexpected type in a definition of a CONTAINER_DATA object"
// *Cause: Table or view whose definition contained a CONTAINER_DATA clause
// lacked a column used to identify a container to which data
// belongs or the column was of unexpected type.
// *Action: Correct the statement and reenter.
//
65040, 00000, "operation not allowed from within a pluggable database"
// *Cause: An operation was attempted that can only be performed in the root
// or application root container.
// *Action: Switch to the root or application root container to perform the
// operation.
//
65041, 00000, "CONTAINER_DATA attribute for this user cannot be modified"
// *Cause: An attempt was made to modify CONTAINER_DATA attribute for user SYS
// or SYSBACKUP which is disallowed.
// *Action: Do not attempt to modify CONTAINER_DATA attribute for users SYS
// or SYSBACKUP.
//
65042, 00000, "name is already used by an existing container"
// *Cause: The name was already used by another container.
// *Action: Specify a valid name.
//
65043, 00000, "TABLESPACE keyword expected"
// *Cause: TABLESPACE keyword was missing.
// *Action: Specify a TABLESPACE keyword.
//
65044, 00000, "missing or invalid option following STORAGE keyword"
// *Cause: An option other than MAXSIZE or
// MAX_SHARED_TEMP_SIZE was specified.
// *Action: Specify only legal options.
//
65045, 00000, "pluggable database not in a restricted mode"
// *Cause: An operation was attempted on a pluggable database that was not
// in restricted mode.
// *Action: Open the pluggable database in a restricted mode.
65046, 00000, "operation not allowed from outside a pluggable database"
// *Cause: An operation was attempted that can only be performed from within
// a pluggable database.
// *Action: Switch to a pluggable database to perform the operation.
//
65047, 00000, "Object %s.%s is invalid or compiled with errors in root."
// *Cause: An attempt was made to issue a metadata link DDL for an object
// that was invalid or compiled with errors in a CDB$ROOT or an
// application root.
// *Action: Check the validity of the object in CDB$ROOT or application root.
//
65048, 00000, "error encountered when processing the current DDL statement in pluggable database %s"
// *Cause: An error was encountered when executing a statement in one of the
// pluggable databases.
// *Action: Examine the cause of failure in the pluggable database.
//
65049, 00000, "Creation of local user or role is not allowed in this container."
// *Cause: An attempt was made to create a local user or role in CDB$ROOT or
// an application root.
// *Action: If trying to create a common user or role, specify CONTAINER=ALL.
//
65050, 00000, "Common DDLs only allowed in root."
// *Cause: An attempt was made to issue a common DDL in a pluggable database.
// *Action: Switch to CDB$ROOT or application root and issue the common DDL.
//
65051, 00000, "missing valid container identifier"
// *Cause: A valid container identifer was not specified.
// *Action: Specify a valid container identifier.
//
65052, 00000, "statement involves operations with different container scope"
// *Cause: An attempt was made to combine one operation that applies to all
// containers with another that only applies to the local container
// into one statement.
// *Action: Execute the operations in separate statements.
//
65053, 00000, "A global user cannot change the container in the session."
// *Cause: An attempt was made by a global user to change the container using
// the ALTER SESSION SET CONTAINER statement.
// *Action: This operation is not allowed for global users.
//
65054, 00000, "Cannot open a pluggable database in the desired mode."
// *Cause: An attempt was made to open a pluggable database (PDB) in a mode
// incompatible with the multitenant container database (CDB) or,
// if the PDB belonged to an application container, in a mode
// incompatible with the application root.
// *Action: Open the CDB or the application root in a compatible mode
// first and retry the operation.
//
65056, 00000, "CONTAINER_DATA attribute is not used in a pluggable database."
// *Cause: User connected to a pluggable database attempted to modify a
// CONTAINER_DATA attribute, which is illegal.
// *Action: A user connected to a pluggable database (PDB) may only see rows of
// CONTAINER_DATA objects on which the appropriate privilege has
// been granted and which pertain to that PDB or to the multitenant
// container database (CDB) as a whole. The ability to see this data
// is not controlled by the CONTAINER_DATA attribute, which is only
// used to control the ability to see rows pertaining to certain
// containers while connected to CDB$ROOT or to an application root
// in a CDB.
//
65057, 00000, "CONTAINER_DATA attribute must always include the current container"
// *Cause: User issuing ALTER USER ... SET|REMOVE CONTAINER_DATA = ...
// statement attempted to exclude the current container from a
// CONTAINER_DATA attribute.
// *Action: Ensure that a CONTAINER_DATA attribute always includes the current
// container.
//
65058, 00000, "object-specific CONTAINER_DATA attribute may only be specified for a CONTAINER_DATA object"
// *Cause: Object referenced in an ALTER USER statement modifying an
// object-specific CONTAINER_DATA attribute is not a CONTAINER_DATA
// table or view.
// *Action: Ensure that an object referenced in the statement is a
// CONTAINER_DATA table or view.
//
65059, 00000, "duplicate container name in CONTAINER_DATA clause"
// *Cause: Duplicate references to a name of some container was encountered
// in a CONTAINER_DATA clause.
// *Action: Ensure that no container name appears more than once.
//
65060, 00000, "CONTAINER_DATA attribute is not set"
// *Cause: User attempted to add container(s) to an object-specific
// CONTAINER_DATA attribute which has not been explicitly set or has
// been set to DEFAULT or remove containers from a CONTAINER_DATA
// attribute which has not been explicitly set or has been set to
// DEFAULT.
// *Action: Avoid adding containers to object-specific CONTAINER_DATA
// attribute which has not been explicitly set or has been set to
// DEFAULT or removing containers from a CONTAINER_DATA attribute
// which has not been explicitly set or has been set to DEFAULT.
//
65061, 00000, "some of specified containers do not belong to the CONTAINER_DATA attribute"
// *Cause: User attempted to remove from a CONTAINER_DATA attribute
// container(s) which do not belong to it.
// *Action: Do not attempt to remove from a CONTAINER_DATA attribute
// container(s) which do not belong to it.
//
65062, 00000, "CONTAINER_DATA attribute is set to ALL"
// *Cause: User attempted to add or remove containers to or from a CONTAINER_DATA
// attribute whose current value is ALL, which is not supported.
// *Action: Do not attempt to add or remove containers to or from a CONTAINER_DATA
// attribute whose current value is ALL.
//
65063, 00000, "CONTAINER_DATA clause has already been specified"
// *Cause: The CONTAINER_DATA clause was specified twice.
// *Action: Specify only one CONTAINER_DATA clause.
//
65064, 00000, "incorrect contents of XML metadata file"
// *Cause: The contents of the XML metadata file were different from the
// actual file properties.
// *Action: Check and correct the XML metadata file.
//
65065, 00000, "A local user or role can only be altered within the current container"
// *Cause: The ALTER USER or ALTER ROLE statement was issued specifying
// CONTAINER=ALL and listing a local user or role among the
// users or roles to be altered, which is illegal.
// *Action: If trying to alter a local user or role, specify
// CONTAINER=CURRENT. If trying to alter common users
// or roles, remove local users or roles from the list
// of roles being altered.
//
65066, 00000, "The specified changes must apply to all containers"
// *Cause: An attempt was made to apply the specified changes to the
// current container.
// *Action: Specify CONTAINER=ALL.
//
65067, 00000, "DEFAULT ROLE clause referencing a local role can only apply to the current container"
// *Cause: An attempt was made to reference a local role across all
// containers using the DEFAULT ROLE clause.
// *Action: If you are trying to set a local role as the default role, specify
// CONTAINER=CURRENT. If trying to set common roles as the
// default roles, remove local roles from the list of roles
// referenced in the DEFAULT ROLE clause.
//
65068, 00000, "cannot define a trigger that fires after a pluggable database is unplugged"
// *Cause: An attempt was made to create a trigger that fires after
// a pluggable database has been unplugged. This type of trigger
// is not supported.
// *Action: Do not attempt to create a trigger that fires after a pluggable
// database has been unplugged.
/
65069, 00000, "AFTER DB_ROLE_CHANGE triggers cannot be defined on a pluggable database"
// *Cause: An attempt was made to create a pluggable database trigger that
// fires after a role change occurs from a standby database to
// primary or vice versa. This type of trigger is not supported.
// *Action: Do not specify AFTER DB_ROLE_CHANGE when creating a trigger on a
// pluggable database.
//
65070, 00000, "AFTER CLONE trigger can only be created on a pluggable database"
// *Cause: An attempt was made to create an AFTER CLONE trigger on a schema
// or a database. This type of trigger is not supported.
// *Action: Do not specify AFTER CLONE when creating a trigger on a schema
// or a database.
//
65071, 00000, "BEFORE UNPLUG trigger can only be created on a pluggable database"
// *Cause: An attempt was made to create a BEFORE UNPLUG trigger on a schema
// or a database. This type of triggers is not supported.
// *Action: Do not specify BEFORE UNPLUG when creating a trigger on a schema
// or a database.
//
65072, 00000, "user must be connected to a pluggable database on which a trigger is being created"
// *Cause: An attempt was made to create a database event trigger on a
// pluggable database while not connected to a pluggable database.
// This is not supported.
// *Action: Connect to the pluggable database on which a database event
// trigger needs to be created before attempting to create such a
// trigger.
//
65073, 00000, "cannot define a trigger that fires before a pluggable database is cloned"
// *Cause: An attempt was made to create a trigger that fires before
// a pluggable database has been cloned. This type of trigger
// is not supported.
// *Action: Do not attempt to create a trigger that fires before a pluggable
// database has been cloned.
//
65074, 00000, "editions not supported for common users"
// *Cause: An attempt was made to support editions for common users.
// *Action: Do not attempt to enable editions for common users.
//
65075, 00000, "cannot recover the pluggable database"
// *Cause: The pluggable database has been dropped.
// *Action: None.
//
65076, 00000, "incompatible SYSTEM tablespace in database being plugged in"
// *Cause: An attempt was made to plug in a database that had a SYSTEM
// tablespace whose relative file number was not one. The most
// common cause of this error is when the database has been created
// using Oracle Database release 7 or earlier and then upgraded using
// the migrate utility.
// *Action: Migrate the database to a pluggable database using the Oracle
// Data Pump utility.
//
65080, 00000, "cannot determine pluggable database name"
// *Cause: An attempt was made to map the database ID to the pluggable
// database name.
// *Action: Contact Oracle Support Services.
//
65081, 00000, "database or pluggable database is not open in read only mode"
// *Cause: An operation was attempted on a database or pluggable database
// that is not open in read only mode
// *Action: Open the database or pluggable database in read only mode and
// then retry the operation.
//
65082, 00000, "cannot add any more pluggable databases: limit of %s exceeded"
// *Cause: There was no more room in the control file for adding
// pluggable databases.
// *Action: Recreate the control file.
//
65083, 00000, "pluggable database %s shutdown in progress"
// *Cause: The pluggable database is in the middle of shutdown abort
// *Action: Retry the operation later.
//
65084, 00000, "object %s.%s does not exist in root"
// *Cause: An attempt was made to create a common object that does not
// exist in root.
// *Action: Invoke the script using catcon.pl to create the object in all
// containers.
//
65085, 00000, "cannot open pluggable database in read-only mode"
// *Cause: The pluggable database has either been created and not opened or
// has not been opened in read/write mode after the undo mode has been
// changed for the multitenant container database (CDB).
// *Action: Open the pluggable database in the read/write or the restricted
// mode first.
//
65086, 00000, "cannot open/close the pluggable database"
// *Cause: The pluggable database has been unplugged.
// *Action: The pluggable database can only be dropped.
//
65087, 00000, "Oracle-supplied operation not allowed from within a pluggable database"
// *Cause: An operation in an Oracle-supplied script was attempted that can
// only be performed in the root container.
// *Action: Confirm that the operation is needed in the root container, and
// switch to the root container to perform the operation.
//
65088, 00000, "database open should be retried"
// *Cause: An inconsistency between the control file and the data dictionary
// was found and fixed during the database open. The database open
// needs to be executed again.
// *Action: Retry the database open.
//
65089, 00000, "pluggable database is not clean"
// *Cause: The pluggable database was not open anywhere but was not marked as
// clean yet.
// *Action: Wait until the cleanup is done and retry.
//
65090, 00000, "operation only allowed in a container database"
// *Cause: User attempted an operation that is only allowed in a CDB
// *Action: Connect to a CDB to perform this operation
//
65091, 00000, "operation on %s not allowed in a pluggable database"
// *Cause: An undo tablespace or rollback segment operation was attempted
// that can only be performed in the root container.
// *Action: Switch to the root container to perform the undo tablespace or
// rollback segment operation.
//
65092, 00000, "system privilege granted with a different scope to '%s'"
// *Cause: An attempt was made to revoke a system privilege that was
// granted with a different scope.
// *Action: Specify the correct value for the CONTAINER clause.
//
65093, 00000, "multitenant container database not set up properly"
// *Cause: An attempt was made to open a multitenant container database without
// the correct parameter set for a multitenant container database in
// the initialization parameter file.
// *Action: Set the 'enable_pluggable_database=true' parameter for the
// multitenant container database in the initialization parameter file
// and restart the database.
//
65094, 00000, "invalid local user or role name"
// *Cause: An attempt was made to create a local user or role with a
// name that was not valid for local users or roles. In addition to
// the usual rules for user and role names, local user and role
// names cannot start with C## or c##.
// *Action: Specify a valid local user or role name.
//
65095, 00000, "invalid common object name"
// *Cause: An attempt was made to create a common object with a name
// that was not valid for common objects. In addition to
// the usual rules for object names, common object names
// must consist only of ASCII characters.
// *Action: Specify a valid common object name.
//
65096, 00000, "invalid common user or role name"
// *Cause: An attempt was made to create a common user or role with a name
// that was not valid for common users or roles. In addition to the
// usual rules for user and role names, common user and role names
// must consist only of ASCII characters, and must contain the prefix
// specified in common_user_prefix parameter.
// *Action: Specify a valid common user or role name.
//
65097, 00000, "DML into a data link table is outside an application action"
// *Cause: DML into a data link table was attempted outside an application
// action.
// *Action: Begin the application action before the DML.
//
65098, 00000, "DML into an extended data link table is outside an application action"
// *Cause: DML into an extended data link table was attempted in an
// application root outside an application action.
// *Action: Begin the application action before the DML.
//
65099, 00000, "Operation cannot be performed when the CDB is not open"
// *Cause: An operation was attemped inside a pluggable database that
// requires the container database (CDB) to be open.
// *Aciton: Open the CDB and then reissue the operation.
//
65100, 00000, "missing or invalid path prefix - %s"
// *Cause: Path prefix was missing or invalid.
// *Action: Correct the PATH_PREFIX clause and reissue the statement.
//
65101, 00000, "container database set up incorrectly"
// *Cause: An attempt was made to use a non container database control
// file to startup a container database (CDB).
// *Action: Create a new control file for the CDB.
//
65102, 00000, "missing or invalid instance name"
// *Cause: A valid instance name was not present where required
// by the syntax of a ALTER PLUGGABLE DATABASE statement.
// *Action: Reissue the statement with a valid instance name.
//
65103, 00000, "UPGRADE cannot be specified for PDBs being open in READ ONLY mode"
// *Cause: ALTER PLUGGABLE DATABASE ... OPEN UPGRADE was specified, but the
// root is open READ ONLY, so the specified PDBs will also be opened
// READ ONLY, and UPGRADE cannot be specified for PDBs being opened
// READ ONLY.
// *Action: Reissue the statement without specifying UPGRADE or reopen the root
// in READ WRITE mode and then reissue the statement.
//
65104, 00000, "operation not allowed on an inactive pluggable database"
// *Cause: The pluggable database status was INACTIVE. It was still being
// created or there was an error during the create operation.
// *Action: Wait until the status is changed to CREATED or, in case of
// errors, drop the pluggable database and re-create it.
//
65105, 00000, "SYSTEM data file for pluggable database #%s not found"
// *Cause: Data files were not specified in a CREATE CONTROLFILE statement
// in the SYSTEM tablespace of a pluggable database.
// *Action: Locate the data files and resubmit the CREATE CONTROLFILE
// statement.
//
65106, 00000, "Pluggable database #%s (%s) is in an invalid state."
// *Cause: Data files were not specified in a CREATE CONTROLFILE statement of a
// pluggable database.
// *Action: Drop the pluggable database or locate the data files and resubmit
// the CREATE CONTROLFILE statement.
//
65107, 00000, "Error encountered when processing the current task on instance:%s"
// *Cause: An error was encountered when executing a pluggable database task on
// one of the Oracle RAC instances.
// *Action: Examine the cause of failure on the instance.
//
65108, 00000, "invalid use of a cursor belonging to another container"
// *Cause: An attempt was made to use a cursor that was parsed or
// executed in a different container.
// *Action: Check if there are any incorrect uses of the SET CONTAINER
// statement. Parse, execute, fetch, and close a cursor only
// all in the same container.
65109, 00000, "operation not allowed in CDB$ROOT"
// *Cause: An operation was attempted that is not supported in the Container
// Database root.
// *Action: Switch to a pluggable database to perform the operation.
//
65110, 00000, "Invalid instance name specified"
// *Cause: An attempt was made to use an invalid or inactive instance name
// in the INSTANCES clause.
// *Action: Specify a valid and active instance name.
//
65111, 00000, "Cannot relocate to the same instance"
// *Cause: An attempt was made to relocate a pluggable database to the
// current instance.
// *Action: Specify an instance which is different then the current instance.
//
65112, 00000, "pluggable database %s not closed on all instances of the standby database"
// *Cause: Media recovery stopped because the pluggable database was either
// unplugged, dropped or renamed on the primary database.
// *Action: Close the pluggable database on all instances and restart the
// recovery.
//
65113, 00000, "value of MAX_PDB_STORAGE property for the PDB is too low"
// *Cause: The value of MAX_PDB_STORAGE specified in the ALTER or CREATE
// PLUGGABLE DATABASE statement is less than the current space usage
// of data files and temporary files of the container.
// *Action: Specify a higher value for MAX_PDB_STORAGE.
//
65114, 00000, "space usage in container is too high"
// *Cause: Space usage in the current container exceeded the value of
// MAX_PDB_STORAGE for the container.
// *Action: Specify a higher value for MAX_PDB_STORAGE using the ALTER
// PLUGGABLE DATABASE statement.
//
65115, 00000, "CDB resource plan %s has more than %s PDB directives."
// *Cause: An attempt was made to create or update the specified
// multitenant container database (CDB) resource plan to use
// more than the supported number of directives.
// *Action: Remove the directives for pluggable databases (PDBs) that are
// not active on this database.
//
65116, 00000, "incompatible database character set"
// *Cause: The database character set of the container database was not
// a superset of the database character set of the pluggable database
// being plugged in.
// *Action: Plug the pluggable database into a container database having
// a compatible database character set.
//
65117, 00000, "CONTAINER clause may only be specified when connected to a container database"
// *Cause: The CONTAINER clause was specified when not connected to a
// container database (CDB).
// *Action: Reenter the statement without the CONTAINER clause.
//
65118, 00000, "operation affecting a pluggable database cannot be performed from another pluggable database"
// *Cause: An attempt was made to perform an operation affecting a pluggable
// database while connected to a different pluggable database.
// *Action: Connect to the desired pluggable database and perform the operation.
//
65119, 00000, "incompatible national character set"
// *Cause: The national character set of the container database
// was not the same as the national character set of
// the pluggable database being plugged in.
// *Action: Plug the pluggable database into a container database having
// the same national character set.
//
65120, 00000, "illegal character set ID in XML metadata file"
// *Cause: The XML metadata file for the pluggable database being plugged in
// contained a database or national character set ID that was not
// valid for the container database. This can happen
// if the XML file is manually modified, if it is corrupted on disk,
// or if the set of supported character sets differs between
// the container database and the source database of the pluggable
// database because a user-defined character set has not been
// installed in the Oracle Home directory of the container database.
// *Action: If you have manually modified the XML metadata file of
// the pluggable database, restore the original file or re-create
// the pluggable database from its source database. Manual
// modifications of the XML file are not supported.
// If the pluggable database uses a user-defined character set,
// make sure the character set is installed in the Oracle Home
// directory of the container database.
// Otherwise, contact Oracle Support Services.
//
65121, 00000, "ALTER SESSION SET CONTAINER not allowed from this client"
// *Cause: Clients earlier than Oracle Database 12c Release 1
// do not support this feature.
// *Action: Upgrade the client to Oracle Database 12c Release 1
// or later.
//
65122, 00000, "Pluggable database GUID conflicts with the GUID of an existing container."
// *Cause: While creating a pluggable database, the GUID conflicted with the
// GUID of an existing container in the container database.
// *Action: Retry creating the pluggable database or consider using the
// AS CLONE clause for CREATE PLUGGABLE DATABASE if plugging in a
// copy of another pluggable database.
//
65123, 00000, "cannot perform a SET CONTAINER operation in this context"
// *Cause: An attempt was made to set the container inside a context where
// such an operation is prohibited.
// *Action: Do not set the container from inside a system trigger or a DML context.
//
65125, 00000, "valid XML or PDB archive file name is required"
// *Cause: An attempt was made to provide a file name that did not have an
// XML or a PDB extension.
// *Action: Specify a valid XML or PDB archive file.
//
65126, 00000, "pluggable database %s cannot be unplugged."
// *Cause: The pluggable database was not closed cleanly and there are active
// transactions that need to be recovered.
// *Action: Open the pluggable database in read/write mode before unplugging
// again so that transaction recovery can be performed.
65127, 00000, "PDB recover output file not specified"
// *Cause: An attempt was made torecover a pluggable database (PDB) without
// specifying an output XML file location.
// *Action: Specify an output file location for recovery.
//
65128, 00000, "missing or nonexistent data file or directory name %s"
// *Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by either not
// specifying a data file or directory location, or by specifying a
// nonexistent data file or directory location.
// *Action: Specify a valid data file or directory location and retry the
// operation.
//
65129, 00000, "Pluggable database %s cannot be relocated."
// *Cause: The pluggable database was already opened on all instances.
// *Action: Close the pluggable database without RELOCATE clause or close
// the pluggable database on another instance.
//
65130, 00000, "cannot relocate more than one pluggable database."
// *Cause: An attempt was made to relocate more than one pluggable database.
// *Action: RELOCATE pluggable database one at a time.
//
65131, 00000, "The feature %s is not supported in a pluggable database."
// *Cause: An attempt was made to use a feature that is not supported in a
// pluggable database.
// *Action: Do not use this feature in a pluggable database.
//
65134, 00000, "endian mismatch"
// *Cause: The endian of the container database was not the same as the
// endian of the pluggable database being plugged in.
// *Action: Plug the pluggable database into a container database having
// the same endian.
//
65135, 00000, "cannot perform ALTER SESSION SET CONTAINER operation in this context"
// *Cause: An ALTER SESSION SET CONTAINER operation was attempted in a
// context where such an operation is prohibited.
// *Action: Do not perform the ALTER SESSION SET CONTAINER operation from a
// session that can be migrated or a session from an OCI connection
// pool.
//
65136, 00000, "SPFILE name cannot be specified for a pluggable database"
// *Cause: An attempt was made to specify an SPFILE name for a pluggable
// database.
// *Action: Remove the SPFILE name and retry the operation in the pluggable
// database.
//
65137, 00000, "Pluggable database %s is in the middle of Pluggable Database RESETLOGS operation."
// *Cause: The pluggable database is in the middle of a Pluggable Database
// (PDB) RESETLOGS operation.
// *Action: If possible, recover the Container Database further so that this
// Pluggable database is not in the middle of a PDB RESETLOGS
// operation. Another alternative is to perform PDB point-in-time
// recovery. A message is logged in the alert log indicating SCN and
// time until which the pluggable database can be point-in-time
// recovered.
65138, 00000, "Data file %s of pluggable database %s belongs to an orphan PDB incarnation."
// *Cause: Either the specified data file was restored from a backup that was
// taken during a period of time that was discarded by
// a RESETLOGS operation, or Oracle could not identify which pluggable
// database incarnation the file belongs to. The alert log contains
// more information.
// *Action: Restore a backup of this file that belonged to either the current
// or a prior incarnation of the pluggable database. If you are using
// RMAN to restore, RMAN will automatically select a correct backup.
65139, 00000, "Mismatch between XML metadata file and data file %s for value of %s (%s)"
// *Cause: Either the XML metadata file or the data file was corrupt.
// *Action: Verify that the XML metadata file and the data file are consistent as of
// the point when the unplug was done and retry the operation.
//
65140, 00000, "invalid common profile name"
// *Cause: An attempt was made to create a common profile with a name
// that is not valid for common profiles. Common profile names must
// consist only of ASCII characters, and must contain the prefix
// specified in common_user_prefix parameter.
// *Action: Specify a valid common profile name.
//
65141, 00000, "invalid local profile name"
// *Cause: An attempt was made to create a local profile with a
// name that is not valid for local profiles. Local profile names
// cannot start with C## or c##.
// *Action: Specify a valid local profile name.
//
65142, 00000, "A local profile can be altered only within the current container"
// *Cause: An attempt was made to alter a local profile using
// an ALTER PROFILE statement with the CONTAINER=ALL clause.
// *Action: If attempting to alter a local profile, ensure that you are
// connected to the correct container and optionally specify
// CONTAINER=CURRENT.
//
65143, 00000, "Creation of local profiles is not allowed in this container."
// *Cause: An attempt was made to create a local profile in CDB$ROOT or an
// application root. Except for DEFAULT and ORA_STIG_PROFILE, which
// are out-of-the-box Oracle supplied local profiles, no customer
// created local profiles are allowed in this container.
// *Action: If attempting to create a common profile, do not specify
// CONTAINER=CURRENT.
65144, 00000, "ALTER SYSTEM DISABLE RESTRICTED SESSION is not permitted"
// *Cause: An attempt was made to disable a restricted session while an
// unresolved error existed in PDB_PLUG_IN_VIOLATIONS.
// *Action: Resolve all of the errors before trying to disable a restricted
// session.
65145, 00000, "FORCE open of multiple pluggable databases is not supported"
// *Cause: An attempt was made to FORCE open multiple pluggable databases
// at the same time.
// *Action: Retry the FORCE open of one pluggable database at a time.
//
65146, 00000, "account cannot be unlocked in a PDB while it is locked in the root"
// *Cause: An attempt was made to unlock a common user account in a
// pluggable database (PDB) which was locked in the root of the
// container database.
// *Action: Ensure that a common user account is not locked in the root
// before attempting to unlock it in a PDB.
//
65147, 00000, "DB_UNIQUE_NAME specified without SPFILE scope"
// *Cause: An attempt was made to specify a DB_UNIQUE_NAME in an ALTER SYSTEM
// statement without SCOPE=SPFILE.
// *Action: Use DB_UNIQUE_NAME only with SCOPE=SPFILE.
//
65148, 00000, "cannot FORCE open a pluggable database to or from upgrade mode"
// *Cause: An attempt was made to FORCE open a pluggable database to or from
// upgrade mode.
// *Action: Close the pluggable database first and retry the operation.
//
65149, 00000, "PDB name conflicts with existing service name in the CDB or the PDB"
// *Cause: An attempt was made to create a pluggable database (PDB) whose
// name conflicts with the existing service name in the container
// database (CDB) or the PDB.
// *Action: Choose a different name for the PDB.
//
65150, 00000, "unable to start the instance"
// *Cause: An attempt was made to start an instance as a container or a
// non-container database when atleast one of the other instances was
// started in a different mode.
// *Action: Start the instance in the same mode as all the other instances.
//
65151, 00000, "invalid tablespace name specified"
// *Cause: An attempt was made to use an invalid tablespace name or a
// mandatory tablespace name (SYSTEM or SYSAUX) in the
// USER_TABLESPACES clause when creating a pluggable database.
// *Action: Specify a valid tablespace name.
//
65152, 00000, "cannot bring datafile online"
// *Cause: An attempt was made to bring online one or more datafiles
// belonging to a pluggable database that is disabled for recovery.
// *Action: Issue the ALTER PLUGGABLE DATABASE ENABLE RECOVERY statement first
// and retry the operation.
//
65153, 00000, "cannot bring tablespace online"
// *Cause: An attempt was made to bring online a tablespace that was either
// missing in the plug XML file or excluded when the pluggable
// database was created.
// *Action: Drop and recreate the tablespace to bring it online.
//
65154, 00000, "specified logging attribute for the pluggable database is same as the current attribute value"
// *Cause: An attempt was made to change the default logging attribute to
// be the same as the current attribute value for the pluggable
// database.
// *Action: Change the logging attribute to a different value.
//
65155, 00000, "missing or invalid source file directory %s"
// *Cause: Source file directory was missing or invalid.
// *Action: Correct the SOURCE_FILE_DIRECTORY clause and reissue the statement.
//
65156, 00000, "pluggable database version %s not allowed"
// *Cause: An attempt was made to plug in a pluggable database with an
// incompatible version of the multitenant container database or
// the application root.
// *Action: Plug in a pluggable database with a compatible version of the
// multitenant container database or the application root.
//
65157, 00000, "SOURCE_FILE_NAME_CONVERT and SOURCE_FILE_DIRECTORY cannot be specified together"
// *Cause: SOURCE_FILE_NAME_CONVERT and SOURCE_FILE_DIRECTORY clauses were both
// specified.
// *Action: Use either the SOURCE_FILE_NAME_CONVERT or the SOURCE_FILE_DIRECTORY
// clause and reissue the statement.
//
65158, 00000, "could not find a matching file for - %s"
// *Cause: A matching file was not found in the directory specified with the
// SOURCE_FILE_DIRECTORY clause.
// *Action: Correct the SOURCE_FILE_DIRECTORY clause or check that the file
// exists in the directory and reissue the statement.
//
65159, 00000, "invalid service name specified"
// *Cause: An attempt was made to use an invalid service name in the services
// clause.
// *Action: Specify a valid service name.
//
65160, 00000, "invalid cleanup task ID"
// *Cause: An attempt was made to pass an invalid cleanup task ID to the
// DBMS_PDB.CLEANUP_TASK function.
// *Action: Specify a valid cleanup task ID.
//
65161, 00000, "Unable to create pluggable database with no data"
// *Cause: An attempt was made to clone a pluggable database which contains
// some clustered tables or index organized tables or advanced
// queue tables.
// *Action: Retry the clone operation after dropping all such objects from the
// source pluggable database.
//
65162, 00000, "The password of the common user has expired"
// *Cause: The password of the common user account has expired and needs
// to be changed. Connect to the CDB$ROOT or Application Root of
// the multitenant container database to change the password of
// the common user.
// *Action: Change the password of the common user or contact the DBA.
//
65164, 00000, "PDB instance recovery cannot open a required archived redo log"
// *Cause: The system could not access a required archived redo log file.
// *Action: Ensure that the offline log exists, the storage device is online,
// and the archived redo log file is in the correct location.
//
65165, 00000, "missing or invalid path for file creation %s"
// *Cause: The path specified in CREATE_FILE_DEST clause was missing or
// invalid.
// *Action: Correct the CREATE_FILE_DEST clause and reissue the statement.
//
65166, 00000, "cannot run noncdb_to_pdb.sql if PDB's version differs from CDB's"
// *Cause: An attempt was made to run noncdb_to_pdb.sql when the version of the
// pluggable database (PDB) was different from the version of the
// multitenant container database (CDB).
// *Action: Upgrade the PDB before running noncdb_to_pdb.sql
//
65167, 00000, "cannot run noncdb_to_pdb.sql if container database is in upgrade mode"
// *Cause: An attempt was made to run noncdb_to_pdb.sql when the multitenant
// container database (CDB) was in upgrade mode.
// *Action: Open the CDB in non-upgrade mode.
//
65168, 00000, "missing PFILE name"
// *Cause: An operation involving PFILE was issued in a pluggable database
// without specifying the PFILE name
// *Action: Specify a valid PFILE name and retry the operation in the pluggable
// database.
//
65169, 00000, "error encountered while attempting to copy file %s "
// *Cause: An error was encountered while attempting to copy the file
// while creating a pluggable database.
// *Action: Check additional error messages for the cause of the failure to
// copy the file, and resolve the issue accordingly.
//
65170, 00000, "XML file %s already exists"
// *Cause: An attempt to create an XML file failed because a file with
// that name already exists.
// *Action: Use a different XML file name.
//
65171, 00000, "invalid value for DB_BLOCK_CHECKING parameter"
// *Cause: An attempt was made to specify a value of FALSE or OFF for the
// DB_BLOCK_CHECKING parameter in a pluggable database (PDB), when
// the value of DB_BLOCK_CHECKING parameter in the multitenant
// container database (CDB) is neither FALSE nor OFF. If the CDB has
// enabled the DB_BLOCK_CHECKING parameter, then the PDB cannot
// disable the DB_BLOCK_CHECKING parameter.
// *Action: Specify a value other than FALSE or OFF for the DB_BLOCK_CHECKING
// parameter in the PDB.
//
65172, 00000, "cannot run noncdb_to_pdb.sql unless pluggable database is an unconverted non-container database"
// *Cause: An attempt was made to run 'noncdb_to_pdb.sql' on a pluggable
// database (PDB) that was not an unconverted non-container database.
// *Action: 'noncdb_to_pdb.sql' is not necessary for this PDB.
//
65174, 00000, "invalid or conflicting name in service %s found in the pluggable database"
// *Cause: The service name or network name in the specified service is
// invalid or it conflicts with an existing service name or network name
// in the container database.
// *Action: Use an appropriate SERVICE_NAME_CONVERT clause and reissue the statement.
//
65175, 00000, "cannot grant SYSDBA privilege locally in the root"
// *Cause: An attempt was made to grant SYSDBA privilege locally in the root
// of a multitenant container database (CDB).
// *Action: While connected to the root, SYSDBA privilege can only be granted
// commonly.
//
65176, 00000, "system tablespace block size (%s) does not match configured block sizes"
// *Cause: The block size of the system tablespace of the pluggable database
// to be plugged in did not match the block sizes configured in the
// container database.
// *Action: Configure the appropriate cache for the block size of the system
// tablespace using the DB_<n>K_CACHE_SIZE parameter (where <n> is
// 2, 4, 8, 16, or 32).
//
65177, 00000, "cannot create non-local user, role or profile with the same name as local user, role or profile"
// *Cause: An attempt was made to create a common user, role or profile with
// the same name as an existing local user, role or profile.
// *Action: Specify a different user, role or profile name.
//
65178, 00000, "invalid logging mode specified for the pluggable database"
// *Cause: An attempt was made to either enable a conflicting logging mode
// or to disable a logging mode when it was not enabled.
// *Action: Check the current logging modes in DBA_PDBS for the pluggable
// database and specify a valid mode.
//
//
65179, 00000, "cannot keep datafiles for a pluggable database that is not unplugged"
// *Cause: An attempt was made to drop a pluggable database without
// specifying the INCLUDING DATAFILES clause, and the pluggable
// database has not been unplugged.
// *Action: Unplug the pluggable database before dropping the pluggable
// database or use the INCLUDING DATAFILES clause in the
// DROP PLUGGABLE DATABASE statement.
//
65180, 0000, "duplicate file name encountered - %s"
// *Cause: An attempt was made to issue a CREATE PLUGGABLE DATABASE statement
// with a duplicate source or target file name for the source file
// name mentioned in the message. This could be caused by incorrect
// SOURCE_FILE_NAME_CONVERT or FILE_NAME_CONVERT clause.
// *Action: Use an appropriate SOURCE_FILE_NAME_CONVERT or FILE_NAME_CONVERT
// clause to ensure that there are no duplicate source or target
// file names and then reissue the statement.
//
65181, 00000, "invalid argument supplied to CONTAINERS function"
// *Cause: An attempt was made to create a multitenant container database
// (CDB) view with an invalid table or view name.
// *Action: Specify a valid table or view name of the form
// <owner>.<table_name | view_name>.
//
65182, 00000, "unable to modify the state of pluggable database %s"
// *Cause: An attempt was made to modify the state of a pluggable database which
// is currently in the middle of a state transition.
// *Action: Retry the operation later.
//
65183, 00000, "FORCE open of a PDB on only a few instances where its open on is not allowed"
// *Cause: An attempt was made to FORCE open a pluggable database on only
// a few Oracle RAC instances where it is currently open.
// *Action: Retry the FORCE open and include all Oracle instances where the
// PDB is open
//
65184, 00000, "encountered data files belonging to different PDBs"
// *Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by specifying
// data files or a directory name containing data files belonging to
// different PDBs.
// *Action: Check the paths provided to DBMS_PDB.RECOVER() and retry the
// operation.
//
65185, 00000, "could not find data file belonging to SYSTEM and SYSAUX tablespaces"
// *Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by specifying
// data files or a directory name containing data files where no
// data files belonging to SYSTEM and SYSAUX tablespace were found.
// SYSTEM and SYSAUX tablespaces are critical to recover a pluggable
// database (PDB).
// *Action: Check the paths specified for DBMS_PDB.RECOVER() and ensure that
// they at least contain data files belonging to SYSTEM and SYSAUX
// tablespaces.
//
65186, 00000, "The user, role or profile %s has sync errors."
// *Cause: There were pending SQL statements involving this user, role or
// profile which need to be resolved in order for the pluggable
// database (PDB) to be synced with ROOT.
// *Action: Resolve the pending SQL statement in the PDB and retry the
// operation.
//
65187, 00000, "duplicate file found %s"
// *Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by specifying
// data files or a directory name containing data files which are
// duplicate copies of the same file.
// *Action: Check the paths specified for DBMS_PDB.RECOVER() and ensure that
// they contain unique data files.
//
65188, 00000, "cannot relocate a PDB opened with warnings"
// *Cause: An attempt was made to relocate a pluggable database (PDB) which
// was opened with warnings or there were warnings encountered after
// relocating the PDB.
// *Action: Resolve the warnings in the PDB before attempting to relocate it
// or try relocating the PDB to a different multitenant container
// database (CDB).
//
65189, 00000, "cannot clone a PDB from PDB$SEED as the source PDB"
// *Cause: An attempt was made to clone a pluggable database (PDB) from
// PDB$SEED as the source PDB.
// *Action: Consider using the "create_pdb_from_seed" clause in CREATE PLUGGABLE
// DATABASE statement or clone the PDB from a different source PDB.
//
65190, 00000, "operation allowed only from within an application root"
// *Cause: An operation (such as creation of an application seed) that can
// only be performed in an application root was attempted
// by a user not connected to an application root.
// *Action: Connect to an application root container to perform the operation.
//
65191, 00000, "operation allowed only from within a CDB root"
// *Cause: An operation (such as creation of an application root) that can
// only be performed in a multitenant container database (CDB) root
// container was attempted by a user not connected to the CDB root.
// *Action: Connect to the CDB root container to perform the operation.
//
65192, 00000, "database must be in UPGRADE mode for this operation"
// *Cause: An attempt is made to issue ALTER DATABASE LOCAL UNDO
// [ON | OFF] when the database is not open in UPGRADE mode.
// *Action: Open the database in UPGRADE mode.
//
65194, 00000, "Pluggable database %s does not belong to the application container."
// *Cause: The user connected to an application root attempted to specify a
// pluggable database (PDB) that does not belong to the application
// container in a statement which can only affect PDBs belonging to
// the application container.
// *Action: Check DBA_PDBS to determine which PDBs belong to the application
// container.
//
65196, 00000, "operation allowed only from within a View Pluggable Database"
// *Cause: An operation (such as ALTER PLUGGABLE DATABASE VIEW LOCAL) that
// can only be performed in a View Pluggable Database was attempted
// by a user not connected to a View Pluggable Database.
// *Action: Connect to a View Pluggable Database to perform the operation.
//
65197, 00000, "cannot clone from the PDB - file %s has online backup set or is being moved"
// *Cause: An attempt to clone from a pluggable database (PDB) which had one
// one or more data files that are currently part of an online move
// or a hot backup operation.
// *Action: Retry the operation after the backup or move of the data files is
// complete.
//
65198, 00000, "operation not allowed on a PDB when it is being cloned"
// *Cause: An attempt was made to perform an operation which is not allowed
// when the pluggable database (PDB) is being cloned concurrently.
// *Action: Retry the operation after the clone from the pluggable database is
// complete.
//
65199, 00000, "database busy. operation not allowed now"
// *Cause: An attempt was made to perform an operation while a conflicting
// database wide operation or a read write pluggable database (PDB)
// clone is in progress.
// *Action: Retry the operation after the conflicting operation is complete.
//
65200, 00000, "unable to create pluggable database with no data"
// *Cause: An attempt was made to clone a pluggable database that contains
// some clustered tables or advanced queue tables.
// *Action: Retry the clone operation after dropping all clustered tables
// and advanced queue tables from the source pluggable database.
//
65201, 00000, "DML on CONTAINERS() includes only the CON_ID column"
// *Cause: A DML on CONTAINERS() included the CON_ID column but did not
// include a non-CON_ID column. A DML on CONTAINERS() including the
// CON_ID column can be performed only if a column other than the
// CON_ID column is also specified.
// *Action: Specify a non-CON_ID column in the DML statement together with
// the CON_ID column.
//
65202, 00000, "DML on CONTAINERS() specifies an invalid CON_ID column value"
// *Cause: A DML on CONTAINERS() specified an invalid value for the CON_ID
// column.
// *Action: If the current container is an application root, then specify the
// pluggable database (PDB) ID of the current container or the PDB ID
// of a member of the application container as the value of the
// CON_ID column. If the current container is CDB$ROOT, then specify
// a valid container ID as the value of the CON_ID column.
65203, 00000, "invalid pluggable database name pattern"
// *Cause: An attempt was made to assign an invalid pluggable database
// pattern for this initialization parameter.
// *Action: Specify a valid pluggable database name pattern.
//
65204, 00000, "STANDBYS clause is too long"
// *Cause: The specified STANDBYS clause was too long in CREATE PLUGGABLE
// DATABASE statement.
// *Action: Use an appropriate length of STANDBYS clause and reissue
// the statement.
//
65205, 00000, "missing or invalid lockdown profile name"
// *Cause: A valid lockdown profile name was not present where required.
// *Action: Reissue the statement with a valid lockdown profile name.
//
65206, 00000, "invalid value specified"
// *Cause: An attempt was made to use an invalid value in the VALUE
// clause.
// *Action: Specify a valid value.
//
65207, 00000, "invalid statement or feature or option specified"
// *Cause: An attempt was made to use an invalid statement or option or
// feature in ENABLE or DISABLE clause.
// *Action: Specify a valid statement or option or feature.
//
65208, 00000, "Lockdown profile %s does not exist."
// *Cause: An attempt was made to specify a lockdown profile that did
// not exist.
// *Action: Check DBA_LOCKDOWN_PROFILES to see if a lockdown profile exists.
//
65209, 00000, "Lockdown profile %s already exists."
// *Cause: An attempt was make to create a lockdown profile with a name
// that already existed.
// *Action: Check DBA_LOCKDOWN_PROFILES to see if the lockdown profile
// name exists.
//
65210, 00000, "invalid value for UPGRADE PRIORITY"
// *Cause: The specified value for UPGRADE PRIORITY was outside of the legal
// range.
// *Action: Choose an appropriate value for the option.
//
65211, 00000, "UPGRADE PRIORITY may only be specified for user PDBs"
// *Cause: An attempt was made to specify UPGRADE PRIORITY for CDB$ROOT or
// PDB$SEED, which is illegal.
// *Action: Avoid explicitly specifying CDB$ROOT or PDB$SEED when changing
// UPGRADE PRIORITY.
//
65212, 00000, "operation not allowed from outside an application root"
// *Cause: An operation was attempted that can only be performed in an
// application root.
// *Action: Switch to the application root container to perform the operation.
//
65213, 00000, "existing application action in progress"
// *Cause: An attempt was made to 'purge' or 'begin' an application action
// (install, uninstall, upgrade, or patch) while another action was
// already in progress.
// *Action: Attempt operation after the ongoing application action is complete.
//
65214, 00000, "application action has not begun"
// *Cause: An attempt was made to end an application action
// (install, uninstall, upgrade, or patch) without a prior 'begin'
// call.
// *Action: Begin the action first.
//
65215, 00000, "starting version does not match current version"
// *Cause: The starting version of the application upgrade did not match
// the current version of the application.
// *Action: Attempt operation with the correct starting version.
//
65216, 00000, "invalid minimum version"
// *Cause: The minimum version for the application patch did not exist.
// *Action: Retry the operation with the correct minimum version.
//
65217, 00000, "application %s does not exist"
// *Cause: An action was attempted on an application that did not exist.
// *Action: Install the application.
//
65218, 00000, "patch %s for application %s already installed"
// *Cause: An attempt was made to start an application patch that
// was already installed.
// *Action: Attempt installation of a different application patch.
//
65219, 00000, "patch %s for application %s is not in progress"
// *Cause: An attempt was made to end an application patch that
// was not in progress.
// *Action: Begin the application patch.
//
65220, 00000, "object %s.%s does not exist or is not of supported common type"
// *Cause: An attempt was made to change the sharing status of an object
// that either did not exist, or was of a type that could not be made
// common.
// *Action: Attempt the operation on a different object.
//
65221, 00000, "application %s exists already"
// *Cause: An action was attempted on an application that already exists.
// *Action: Use a different application name.
//
65222, 00000, "%s parameter is only supported in a CDB"
// *Cause: An attempt was made to enable a parameter only supported in a
// multitenant container database (CDB), and the current database is
// not a CDB.
// *Action: Remove the parameter before starting the instance.
//
65223, 00000, "tablespace %s does not exist"
// *Cause: The default tablespace specified in the CREATE PLUGGABLE DATABASE
// statement either did not exist in the source pluggable database
// (PDB) or is not included in the USER_TABLESPACES clause.
// *Action: Specify an existing tablespace to be set as the default.
//
//
65224, 00000, "SQL statement not allowed according to lock down profile %s"
// *Cause: An attempt was made to execute a SQL statement, in a pluggable
// database (PDB), which was disabled according to the corresponding
// lock down profile.
// *Action: Enable the SQL statement in the lock down profile and then try
// to execute the statement.
//
65225, 00000, "cannot run apex_to_common.sql or pdb_to_apppdb.sql on an unconverted non-multitenant container database"
// *Cause: An attempt was made to run 'apex_to_common.sql' or
// 'pdb_to_apppdb.sql' on a pluggable database (PDB) that is an
// unconverted non-multitenant container database.
// *Action: Run 'noncdb_to_pdb.sql' in the PDB first.
//
65226, 00000, "incompatible client version for the current database"
// *Cause: An attempt was made to use an incompatible client version. Clients
// prior to Oracle Database 12c Release 2 (12.2) do not support long
// identifiers.
// *Action: Either upgrade the Oracle client to 12.2 (or higher) or do not use
// long identifiers in the database.
//
65227, 00000, "unable to open pdb archive file %s"
// *Cause: An attempt was made to provide an invalid file name which could not
// be opened for generating the unplug archive.
// *Action: Check that the file name is valid and the file path is accessible.
//
65228, 00000, "invalid host name specified"
// *Cause: An attempt was made to use an invalid host name in the HOST
// clause.
// *Action: Specify a valid host name.
//
65229, 00000, "invalid application version specified"
// *Cause: An attempt was made to use an invalid application version.
// *Action: Specify a valid application version.
//
65230, 00000, "internal database link cannot be altered or dropped"
// *Cause: An attempt was made to directly alter or drop an internal
// database link. An internal database link can be altered or
// dropped only through an ALTER or DROP PLUGGABLE DATABASE
// statement.
// *Action: Specify the correct ALTER or DROP PLUGGABLE DATABASE statement.
//
65231, 00000, "The referenced pluggable database does not exist or it is closed."
// *Cause: An attempt was made to create or access a proxy pluggable
// database that referenced a non-existent or closed pluggable
// database.
// *Action: Create or open the referenced pluggable database.
//
65232, 00000, "unable to support PDB isolation mode in a non-PDB domain instance"
// *Cause: An attempt to support pluggable database (PDB) isolation mode in a
// database without per-PDB recovery domains failed. PDB isolation
// mode is supported only on a per-PDB domain enabled instance.
// *Action: Enable the per-PDB recovery domains to use PDB isolation.
//
65233, 00000, "unable to support PDB isolation mode in a global undo instance"
// *Cause: An attempt to support pluggable database (PDB) isolation mode in
// a global undo enabled pluggable database failed. PDB isolation
// mode is supported only on a local undo enabled CDB instance.
// *Action: All PDBs should use local undo before starting in PDB isolation mode.
//
65235, 00000, "cannot create common user, role or profile with the same name as existing common user, role or profile"
// *Cause: An attempt was made to create a common user, role or profile with
// the same name as an existing common user, role or profile.
// *Action: Specify a different user, role or profile name.
//
65236, 00000, "CON_ID column cannot be dropped"
// *Cause: An attempt was made to drop a CON_ID column of a CONTAINER_DATA
// table which is illegal.
// *Action: Avoid dropping CON_ID column of a CONTAINER_DATA table.
//
65237, 00000, "CON_ID column must have a numeric data type"
// *Cause: An attempt was made to change the data type of a CON_ID column
// of a CONTAINER_DATA table to a non-numeric data type, which is
// illegal.
// *Action: Avoid assigning a non-numeric data type to a CON_ID column of a
// CONTAINER_DATA table.
//
65238, 00000, "operation cannot be performed when the application root is not open"
// *Cause: An operation was attempted inside an application root that
// requires the application root to be open.
// *Action: Open the application root and then reissue the statement.
//
65239, 00000, "missing or invalid service name"
// *Cause: A valid service name was not present where required
// by the syntax of ALTER SESSION SET CONTAINER= SERVICE=.
// *Action: Reissue the statement with a valid service name.
//
65240, 00000, "not connected to an application root"
// *Cause: An attempt was made to create a pluggable database (PDB) by
// cloning or plugging in an application PDB while connected to the
// root of a multitenant container database (CDB).
// *Action: Make sure that you are connected to an application root before
// attempting this operation.
//
65241, 00000, "statement can only be executed when administering an application"
// *Cause: An attempt was made to issue a statement affecting a user, role,
// or object used by an application installed in an application
// container while not installing, upgrading, patching, or
// uninstalling such application.
// *Action: Make sure that an application installed in an application
// container is being installed, upgraded, patched, or uninstalled
// when issuing a statement affecting a user, role, or object.
//
65242, 00000, "CONTAINER_DATA attribute disabled"
// *Cause: An attempt was made to disable a CONTAINER_DATA attribute of a
// table for which it was not enabled.
// *Action: Make sure that the table whose CONTAINER_DATA attribute you are
// trying to disable has it enabled.
//
65243, 00000, "CONTAINER_DATA attribute already enabled"
// *Cause: An attempt was made to enable a CONTAINER_DATA attribute of a
// table for which it is already enabled.
// *Action: Make sure that the table whose CONTAINER_DATA attribute you are
// trying to enable does not already have it enabled.
//
65244, 00000, "application action has begun"
// *Cause: An attempt was made to execute an unsupported statement after an
// application action (install, uninstall, upgrade, or patch) was
// started.
// *Action: End the action first.
//
65245, 00000, "application %s has been uninstalled"
// *Cause: An attempt was made to operate on an application after it was
// uninstalled.
// *Action: Use a different application name.
//
65246, 00000, "invalid user name specified"
// *Cause: An attempt was made to use an invalid user name in the USER
// clause.
// *Action: Specify a valid user name.
//
65247, 00000, "tablespace specified in USER_TABLESPACES clause is not self-contained"
// *Cause: One or more tablespaces listed in the USER_TABLESPACES clause were
// not self-contained.
// *Action: Check the violating tablespaces in the PDB_PLUG_IN_VIOLATIONS view
// and reissue the statement.
//
65248, 00000, "invalid clause"
// *Cause: An attempt was made to alter a lockdown profile with an invalid
// clause.
// *Action: Specify a valid clause while altering the lockdown profile.
//
65249, 00000, "invalid option"
// *Cause: An attempt was made to alter a lockdown profile with an invalid
// option.
// *Action: Specify a valid option while altering the lockdown profile.
//
65250, 00000, "invalid path specified for file - %s"
// *Cause: An attempt was made to use a file name that does not start
// with CREATE_FILE_DEST for the pluggable database.
// *Action: Specify a file name pattern so that the resulting file name has
// CREATE_FILE_DEST value as a prefix.
//
65251, 00000, "ending version already exists"
// *Cause: The ending version of the application upgrade matched a
// previous version of the application.
// *Action: Attempt operation with the correct ending version.
//
65252, 00000, "cannot connect or ALTER SESSION SET CONTAINER to an application root clone"
// *Cause: An attempt was made to connect or ALTER SESSION SET CONTAINER to
// an application root clone.
// *Action: Connect or ALTER SESSION SET CONTAINER to a different pluggable
// database.
//
65253, 00000, "operation not allowed within a proxy pluggable database as SYSDBA or SYSOPER"
// *Cause: An attempt was made to access a proxy pluggable database as SYSDBA
// or SYSOPER.
// *Action: Access a proxy pluggable database with any privilege other than
// SYSDBA or SYSOPER.
//
65254, 00000, "invalid path specified for the directory"
// *Cause: An absolute path was used in the CREATE DIRECTORY statement.
// Since the PDB has set the PATH_PREFIX property, only relative
// path is allowed for directories.
// *Action: Specify a relative path and reissue the statement.
//
65255, 00000, "invalid tablespace number"
// *Cause: An attempt was made to create a pluggable database where one or
// more tablespaces has an invalid tablespace number.
// *Action: Contact Oracle Support Services.
//
65256, 00000, "maximum number of application root clones created for application container"
// *Cause: An attempt was made to create an application root clone for an
// application container that has already reached the maximum
// permitted number of application root clones.
// *Action: Avoid creating too many application root clones.
//
65257, 00000, "target is a non-CDB instance"
// *Cause: An attempt was made to create a proxy pluggable database to a
// non-multitenant container database (non-CDB) instance.
// *Action: Create a proxy pluggable database to a pluggable database.
//
65258, 00000, "referenced pluggable database is an application root clone"
// *Cause: An attempt was made to create a proxy pluggable database that
// references an application root clone.
// *Action: Create a proxy pluggable database that references a different
// pluggable database.
//
65259, 00000, "partial synchronization of application is disallowed"
// *Cause: An attempt was made to synchronize an application that has not
// ended its install, patch, upgrade, or uninstall.
// *Action: End the application install, patch, upgrade, or uninstall.
//
65260, 00000, "unable to create a refreshable clone"
// *Cause: An attempt was made to either create a refreshable clone of a proxy
// pluggable database or to create a proxy pluggable database which is
// also enabled for refresh.
// *Action: Create a refresh clone of a regular pluggable database.
//
65261, 00000, "pluggable database %s not enabled for refresh"
// *Cause: An attempt was made to refresh a pluggable database (PDB) which was
// either not created as a refreshable PDB or the final refresh was
// already complete.
// *Action: Attempt the operation only on a PDB that is enabled for refresh.
//
65262, 00000, "Dismount operation is not allowed."
// *Cause: An attempt was made to dismount a pluggable database with
// parameter enable_pdb_isolation set to FALSE.
// *Action: None.
//
65263, 00000, "internal error"
// *Cause: This is an internally stimulated error.
// *Action: Contact Oracle Support Services.
//
65264, 00000, "Dismount operation is not allowed."
// *Cause: An attempt was made to dismount a pluggable database on a
// standby instance.
// *Action: None.
//
//
65265, 00000, "PDB cannot be dropped or unplugged."
// *Cause: An attempt was made to drop or unplug the root of an application
// container to which one or more application pluggable
// databases (PDBs) belong.
// *Action: Drop the application PDBs belonging to the application container
// before attempting to drop or unplug the application root.
//
65266, 00000, "application root clone may not be dropped, unplugged or altered"
// *Cause: An attempt was made to drop, unplug, or alter an application root
// clone pluggable database which is not allowed.
// *Action: Specify a legal pluggable database name.
//
65267, 00000, "Application PDB %s is open in an incompatible mode."
// *Cause: An attempt was made to reopen an application root in a mode
// incompatible with that of an application PDB belonging to the same
// application container.
// *Action: Reopen the application PDB in a compatible mode and then retry
// the operation.
//
65268, 00000, "PDB cannot be created"
// *Cause: An attempt was made to either relocate a pluggable database (PDB)
// which was created as a refreshable PDB or to create a refreshable
// PDB from a PDB that was already created as refreshable PDB or was
// marked for relocation.
// *Action: NONE
//
65269, 00000, "PDB cannot be refreshed"
// *Cause: An attempt was made to refresh a pluggable database (PDB) with no
// refresh mode.
// *Action: Specify a manual or automatic refresh mode for the PDB.
//
65270, 00000, "operation is not allowed in an application patch"
// *Cause: An attempt was made to perform an operation that is not allowed in
// an application patch.
// *Action: Use application upgrade instead of application patch.
//
65271, 00000, "internal application may not be altered"
// *Cause: An attempt was made to alter an application that was created
// internally.
// *Action: Specify a non-internal application.
//
65272, 00000, "operation not allowed from outside an application PDB"
// *Cause: An operation was attempted that can only be performed in an
// application PDB.
// *Action: Switch to the application PDB to perform the operation.
//
65273, 00000, "The specified changes must be restricted to the current container."
// *Cause: An attempt was made to apply the specified changes to all
// containers.
// *Action: Specify CONTAINER=CURRENT.
//
65274, 00000, "operation not allowed from outside an application action"
// *Cause: An operation was attempted that can only be performed in an
// application action (install, uninstall, upgrade, or patch).
// *Action: Begin an application action.
//
65275, 00000, "invalid operation on a container database (CDB)"
// *Cause: An operation was attempted that can only be performed from within
// a non-container database.
// *Action: Switch to a non-container database to perform the operation.
//
65276, 00000, "rule already exists in the lockdown profile"
// *Cause: An attempt was made to add a rule that already exists in the
// lockdown profile.
// *Action: Specify a rule that does not exist in the lockdown profile.
//
65277, 00000, "Unable to support PDB isolation mode with MEMORY_TARGET or MEMORY_MAX_TARGET."
// *Cause: An attempt was made to support pluggable database (PDB) isolation
// mode with the MEMORY_TARGET or MEMORY_MAX_TARGET configuration
// parameters. PDB isolation mode is not supported with the
// MEMORY_TARGET or MEMORY_MAX_TARGET configuration parameters.
// *Action: Disable PDB isolation mode before starting the instance.
//
65278, 00000, "The PDB SGA size is larger than or equal to the CDB SGA size."
// *Cause: An attempt was made to start a pluggable database (PDB) with a
// system global area (SGA) size larger than or equal to the
// multitenant container.
// *Action: Specify a PDB SGA size which is less than the CDB SGA size in
// the PDB SPFILE.
//
65279, 00000, "The PDB SGA_MAX_SIZE is larger than or equal to the maximum CDB SGA size."
// *Cause: An attempt was made to start a pluggable database (PDB) with
// SGA_MAX_SIZE configuration parameter size larger than or equal
// to the multitenant container database (CDB).
// *Action: Specify a PDB SGA_MAX_SIZE configuration parameter which is
// less than the maximum CDB SGA size in the PDB SPFILE.
//
65280, 00000, "The referenced pluggable database is a proxy pluggable database."
// *Cause: An attempt was made to create a proxy pluggable database that
// referenced a proxy pluggable database.
// *Action: Create a proxy pluggable database that references a different
// pluggable database.
//
65281, 00000, "application %s does not exist in application root"
// *Cause: An attempt was made to create a pluggable database (PDB) by
// cloning or plugging in an application PDB or application root
// having an application that does not exist in the application
// root where the statement was issued.
// *Action: Install the application in the application root where the
// statement is issued.
//
65282, 00000, "Aborting PDB %s's instance recovery due to the progress of its SHUTDOWN ABORT operation"
// *Cause: The instance recovery could not proceed as the pluggable database
// (PDB) was in the middle of the SHUTDOWN ABORT operation.
// *Action: None.
//
65283, 00000, "pluggable database %s does not belong to the current container database"
// *Cause: An attempt was made to perform an operation on a pluggable database
// that did not belong to the current multitenant container database
// (CDB) in the CDB fleet.
// *Action: Connect to the container database where the pluggable database
// was created to perform the operation.
//
65284, 00000, "Version %s for application %s does not exist in application root"
// *Cause: An attempt was made to create a pluggable database (PDB) by
// cloning or plugging in an application PDB or application root
// having an application that has a higher version than the
// application root where the statement was issued.
// *Action: Upgrade the application in the application root where the
// statement is issued.
//
65285, 00000, "Status mismatch for application %s"
// *Cause: An attempt was made to create a pluggable database (PDB) by
// cloning or plugging in an application PDB or application root
// having an application that has a mismatch status between
// application PDB and the application root where the statement
// was issued.
// *Action: Uninstall the application in the application root where the
// statement is issued.
//
65286, 00000, "object %s.%s cannot be made an extended data link"
// *Cause: An attempt was made to change the sharing status of an object
// to extended data link when the object was of a type for which
// extended data links are not supported.
// *Action: Ensure that the object whose sharing status is to be changed to
// extended data link is of appropriate type.
//
65287, 00000, "cannot set a common application context using a local package"
// *Cause: An attempt was made to set a common application context
// using a local package.
// *Action: Associate the common application context with a common package.
//
65288, 00000, "PDB archive file %s already exists."
// *Cause: An attempt to create a pluggable database (PDB) archive file failed
// because a file with that name already exists.
// *Action: Use a different PDB archive file name.
//
65289, 00000, "Application root cannot be relocated to another container database."
// *Cause: An attempt was made to relocate the root of an application
// container.
// *Action: None.
//
65290, 00000, "Application may not be altered."
// *Cause: An attempt was made to alter an application when the application
// pluggable database was not open.
// *Action: Open the application pluggable database and retry.
//
65291, 00000, "invalid container map object"
// *Cause: An attempt was made to assign an invalid container map object to
// container_map property of the database.
// *Action: Create the container map object with partition names corresponding
// to the multitenant container database (CDB) ROOT or application
// container ROOT and their pluggable databases. And the partition
// key for the container map object must be single column.
//
65292, 00000, "invalid common data map object"
// *Cause: An attempt was made to assign an invalid common data map object to
// common_data_map property of the database.
// *Action: Create the common data map object with partition names
// corresponding to the pluggable database (PDB) or application PDB
// and its multitenant container database ROOT or application
// container ROOT, respectively.
65293, 00000, "Implicit users cannot own common objects."
// *Cause: An attempt was made to create a common object to be owned by an
// implicit user.
// *Action: Create a local object.
//
65294, 00000, "PDB's compatible parameter value (%s) is higher than CDB's compatible parameter value (%s)."
// *Cause: An attempt was made to plug in or clone from a pluggable database
// with a higher compatible parameter value than the compatible
// parameter value of the multitenant container database (CDB).
// *Action: Create a pluggable database with the same or lower compatible
// parameter value of the multitenant container database.
//
65295, 00000, "service name or module name mismatch"
// *Cause: An attempt was made to end an application action using a service
// name or module name that does not match the service name or module
// name that was in use when the application action was started.
// *Action: Use the right service name or module name before ending the
// application action.
//
65296, 00000, "unable to create pluggable database"
// *Cause: An attempt was made to create a proxy pluggable database with
// relocate clause specified.
// *Action: Create a proxy pluggable database without the relocate clause.
//
65297, 00000, "operation not allowed inside an application action"
// *Cause: An operation was attempted that can only be performed outside an
// application action (install, uninstall, upgrade, or patch).
// *Action: Perform the operation outside an application action.
//
65298, 00000, "cannot create an application PDB in an application root which is an unconverted non-CDB"
// *Cause: An attempt was made to create an application pluggable
// database (PDB) in an application root which was created by
// plugging in a non-multitenant container database (non-CDB)
// without first running noncdb_to_pdb.sql script.
// *Action: Run the noncdb_to_pdb.sql script in the application root first.
//
65299, 00000, "cannot grant or revoke a privilege to or from multiple grantees"
// *Cause: A GRANT or REVOKE statement was issued specifying more than one grantee
// on an application pluggable database (PDB).
// *Action: If trying to grant or revoke a privilege on a PDB, specify only one grantee
// at a time in the GRANT or REVOKE statement.
//
65300, 00000, "PDB common_user_prefix conflicts with common_user_prefix in CDB."
// *Cause: An attempt was made to set the 'common_user_prefix' parameter in
// a pluggable database (PDB) that conflicts with the value of the
// same parameter in the multitenant container database (CDB.)
// *Action: Choose a different 'common_user_prefix' for PDB.
//
65310, 00000, "blocked by COMMON_SCHEMA_ACCESS lockdown"
// *Cause: An attempt was made to run an AUTHID CURRENT_USER function or
// procedure, or to reference a BEQUEATH CURRENT_USER view, that
// is not safe under the COMMON_SCHEMA_ACCESS lockdown.
// *Action: Either do not call the function or procedure or reference the view,
// or adjust the definition of the function, procedure, or view
// to satisfy the requirements of COMMON_SCHEMA_ACCESS lockdown.
//
65311, 00000, "cannot modify the common object of another application"
// *Cause: An attempt was made to modify a common object that was created by
// another application.
// *Action: Modify the object using the same application as the one
// that created the object.
65312, 00000, "The password of the application common user has expired and cannot be changed."
// *Cause: The password of the application common user had expired and needed
// to be changed in order to successfully log in to application
// containers. But the application ROOT container's application
// status did not allow this operation to succeed either because:
// - An implicit application common user was attempting to change
// the password from within an explicit application action.
// - A non-implicit application common user was attempting to change
// the password from within an implicit application action.
// *Action: Either begin an explicit application action for changing the
// password of a non-implicit application common user or try changing
// the implicit application common user's password inside an implicit
// application action and then try logging in or contact the DBA.
65313, 00000, "cannot synchronize application in a proxy pluggable database without being in a SYSDBA session"
// *Cause: An attempt was made to synchronize an application containing
// statements executed from a privileged session.
// *Action: Synchronize the application as SYSDBA.
//
65314, 00000, "cannot use NOCOPY when plugging in a PDB using an archive file"
// *Cause: An attempt was made to create a pluggable database (PDB) using an
// archive file using the NOCOPY clause.
// *Action: Specify COPY or MOVE and retry the plugin operation.
//
65315, 00000, "invalid path specified for file - %s"
// *Cause: An attempt was made to use a file name that did not start with
// PATH_PREFIX for the pluggable database.
// *Action: Specify a file name that is under the PATH_PREFIX directory for
// the pluggable database.
//
65316, 00000, "bad file name specified"
// *Cause: An attempt was made to use an invalid file name as an argument.
// *Action: Specify a valid file name and retry the operation.
//
65317, 00000, "cannot modify the user created by another application"
// *Cause: An attempt was made to modify a user that was created by
// another application.
// *Action: Modify the user using the same application as the one
// that created the user.
//
65318, 00000, "query to cross-container fixed tables not allowed"
// *Cause: An attempt was made to query the cross-container fixed tables.
// *Action: Avoid querying the cross-container fixed tables.
//
65319, 00000, "DML on CONTAINERS() specified an unsupported CON_ID predicate"
// *Cause: A DML on CONTAINERS() included the CON_ID predicate in an OR chain
// or in an in-list.
// *Action: Specify the CON_ID predicate within an AND chain and without an
// in-list.
//
65320, 00000, "value of CON_ID is not known for DML on CONTAINERS()"
// *Cause: A DML on CONTAINERS() included multiple CON_ID predicates, or
// the single CON_ID predicate specified a value that is not a
// constant or a bind.
// *Action: Specify a single CON_ID predicate as a constant or a bind.
//
65321, 00000, "CON_ID column cannot be updated for CONTAINERS()"
// *Cause: A DML on CONTAINERS() attempted to set a value for the
// CON_ID column.
// *Action: Do not set a value for the CON_ID column for CONTAINERS().
//
65322, 00000, "invalid application patch specified"
// *Cause: An attempt was made to use an invalid application patch.
// *Action: Specify a valid application patch.
//
65323, 00000, "cannot create an object table or object view as a data link or extended data link"
// *Cause: An attempt was made to create an object table or object view as
// a data link or extended data link.
// *Action: Create the object table or object view as a metadata link.
//
65324, 00000, "An invalid value is specified in an ALTER PLUGGABLE DATABASE CONTAINERS DEFAULT TARGET or ALTER DATABASE CONTAINERS DEFAULT TARGET statement."
// *Cause: An invalid value is specified in an ALTER PLUGGABLE DATABASE
// CONTAINERS DEFAULT TARGET or ALTER DATABASE CONTAINERS DEFAULT
// TARGET statement.
// *Action: Specify a valid pluggable database (PDB) name or NONE in the
// ALTER PLUGGABLE DATABASE CONTAINERS DEFAULT TARGET or
// ALTER DATABASE CONTAINERS DEFAULT TARGET statement.
//
65325, 00000, "DML on CONTAINERS() cannot be performed outside the CDB root or application root."
// *Cause: An attempt was made to perform DML on CONTAINERS() outside the
// multitenant container database (CDB) root or an application root.
// *Action: Perform DML on CONTAINERS() in the CDB root or in an application
// root.
//
65326, 00000, "cannot query an object table or object view using CONTAINERS()"
// *Cause: An attempt was made to query an object table or object view
// using CONTAINERS().
// *Action: Query the object table or object view without using CONTAINERS().
//
65327, 00000, "cannot modify the sharing property of an object outside an application action"
// *Cause: An attempt was made to modify the sharing property of an object
// outside an application action.
// *Action: Begin the application action.
//
65328, 00000, "cannot end an application action in the current session"
// *Cause: An attempt was made to end an application action in a manner
// that is inconsistent with the order in which sessions will be
// replayed during application SYNC.
// *Action: Start a new session to end the application action.
//
65329, 00000, "cannot run pdb_to_apppdb.sql unless pluggable database is an unconverted application pluggable database"
// *Cause: An attempt was made to run 'pdb_to_apppdb.sql' on a pluggable
// database (PDB) that was not an unconverted application PDB.
// *Action: 'pdb_to_apppdb.sql' is not necessary for this PDB.
//
65330, 00000, "cannot synchronize an application before pdb_to_apppdb.sql is executed"
// *Cause: An attempt was made to synchronize an application in an
// unconverted application PDB before running 'pdb_to_apppdb.sql'.
// *Action: Run 'pdb_to_apppdb.sql' in the unconverted application PDB.
//
65331, 00000, "DDL on a data link table is outside an application action."
// *Cause: DDL on a data link table was attempted outside an application
// action.
// *Action: Begin the application action before the DDL.
//
65332, 00000, "DDL on an extended data link table is outside an application action."
// *Cause: DDL on an extended data link table was attempted in an
// application root outside an application action.
// *Action: Begin the application action before the DDL.
//
65333, 00000, "cannot purge an application that is installed on application PDB"
// *Cause: An attempt was made to purge an application that was installed
// in one or more application pluggable databases (PDBs).
// *Action: Drop the installed application PDB before purging.
//
65334, 00000, "invalid number of PDBs specified"
// *Cause: An attempt was made to either set the MAX_PDBS database property to
// an invalid number or the number of current pluggable databases (PDBs)
// exceeds the number specified.
// *Action: Specify a valid value which is greater than the current number of
// existing PDBs.
//
65335, 00000, "application action for application %s has not started"
// *Cause: An attempt was made to end an application action using an
// incorrect application name.
// *Action: Use the correct application name.
//
65336, 00000, "incorrect application patch number specified"
// *Cause: An attempt was made to end an application action using an
// incorrect application patch number.
// *Action: Use the correct application patch number.
//
65337, 00000, "cannot modify the profile created by another application"
// *Cause: An attempt was made to modify a profile that was created by
// another application.
// *Action: Modify the profile using the same application as the one
// that created the profile.
//
65338, 00000, "unable to create pluggable database"
// *Cause: An attempt was made to relocate a pluggable database using a
// database link to the source pluggable database.
// *Action: Use a database link that points to the source multitenant container
// database root and retry the operation.
//
65339, 00000, "unsupported operation on the source PDB"
// *Cause: An unsupported operation was performed on the source
// pluggable database, which rendered the target PDB invalid.
// *Action: Re-create the target PDB.
//
65340, 00000, "invalid application compatibility version"
// *Cause: An attempt was made to set the compatibility version of an
// application to a version higher than that of one of the PDBs.
// *Action: Set a higher compatibility version.
//
65341, 00000, "cannot open pluggable database in read/write mode"
// *Cause: An attempt was made to open a refreshable pluggable database in
// read/write mode.
// *Action: Open the refreshable clone in read-only mode or modify the refresh
// mode to NONE and retry the operation.
//
65342, 00000, "source pluggable database %s has unrecovered transaction"
// *Cause: The source pluggable database had an active transaction when
// it was closed.
// *Action: Open the pluggable database in read/write mode so that
// transaction recovery can be performed. End XA transaction.
//
65343, 00000, "cannot unplug pluggable database %s"
// *Cause: An attempt was made to unplug a pluggable database that was
// previously unplugged.
// *Action: Drop the pluggable database to finish the unplug operation.
//
65344, 00000, "cannot uninstall or purge an application that has objects, users, roles, and profiles"
// *Cause: An attempt was made to uninstall or purge an application that had
// objects, users, roles, and profiles.
// *Action: Drop all objects, users, roles, and profiles that belong to
// the application.
//
65345, 00000, "cannot refresh pluggable database"
// *Cause: The foreign archive log required for refreshing the pluggable
// database was not found.
// *Action: Re-create the refresh pluggable database and ensure that archive
// logging is enabled for the source multitenant container
// database (CDB).
65346, 00000, "The PDB version is lower and components (%s) are missing in CDB."
// *Cause: An attempt was made to plug in a pluggable database (PDB) that
// has a lower version and has more components than the multitenant
// container database (CDB) or the application root.
// *Action: Install the missing components in CDB or the application root
// before plugging in the PDB.
//
65347, 00000, "cannot downgrade database that has proxy pluggable databases or application containers"
// *Cause: There were proxy pluggable databases or application containers in
// the database.
// *Action: Prior to downgrade, drop the proxy pluggable databases and
// application containers.
//
65348, 00000, "unable to create pluggable database"
// *Cause: An attempt was made to relocate a pluggable database with
// availability max clause using a target pluggable database name
// which is different from source pluggable database name.
// *Action: Use source pluggable database name as the target pluggable database
// name.
//
65349, 00000, "unable to create pluggable database"
// *Cause: An attempt was made to relocate a pluggable database with
// availability max and service_name_convert clauses together.
// *Action: Do not use service_name_convert clause when relocating
// with the availability max clause.
//
65350, 00000, "cannot run approot_to_pdb.sql"
// *Cause: An attempt was made to run 'approot_to_pdb.sql' on a pluggable
// database (PDB) that was already converted to a regular PDB.
// *Action: 'approot_to_pdb.sql' is not necessary for this PDB.
//
65351, 00000, "invalid partition (%0!s) access with partition map size %1!s"
// *Cause: An attempt was made to access an invalid partition using the
// CONTAINERS() clause.
// *Action: Contact Oracle Support Services.
//
65352, 00000, "Query across containers cannot have an ancillary operator."
// *Cause: An ancillary operator was used with a data link, extended
// data link, or CONTAINERS() clause.
// *Action: Remove the ancillary operator in the query.
//
65353, 00000, "The %s tablespace is missing from the XML metadata file."
// *Cause: An attempt was made to plug in a pluggable database (PDB) using
// an XML file that does not contain the SYSTEM, SYSAUX or undo
// tablespace specifications.
// *Action: Check and correct the XML metadata file. If the XML metadata file
// is missing undo tablespaces, you may need to be regenerate the XML
// using a more recent patchset.
//
// NLS_DO_NOT_TRANSLATE [65354,65354]
65354, 00000, "DML into a data link or extended data link table cannot be done during an application sync operation."
// *Document: NO
// *Cause: DML into a data link or extended data link table was attempted
// during an application sync operation.
// *Action: This is an internal error. Contact Oracle Support Services.
//
65355, 00000, "cannot allocate PDB SGA memory"
// *Cause: The multitenant container database (CDB) did not have sufficient
// system global area (SGA) memory available to open the pluggable
// database (PDB).
// *Result: Increase the CDB SGA size or dismount a PDB to free CDB SGA memory.
//
65356, 00000, "missing or invalid value for lead_cdb_uri"
// *Cause: An attempt was made to specify an incorrect value for lead_cdb_uri.
// The lead_cdb_uri value can either specify the host name, port number
// and service name for the lead multitenant container database (CDB),
// or the value can specify a database link object name in the current
// CDB which connects to the lead CDB in the fleet.
// *Action: Specify a valid value for lead_cdb_uri.
//
65357, 00000, "lead_cdb_uri and lead_cdb cannot be specified in the same CDB"
// *Cause: An attempt was made to specify the lead_cdb_uri property in the
// multitenant container database (CDB) where the lead_cdb property is
// set to TRUE or vice versa.
// *Action: Specify lead_cdb or lead_cdb_uri property in the CDB.
//
65358, 00000, "PDB %s is not a template PDB"
// *Cause: The PDB specified was not a template pluggable database (PDB)
// and thus pdb_template cannot be set to this PDB.
// *Action: Set pdb_template to a template PDB.
//
65359, 00000, "unable to create pluggable database with no data"
// *Cause: An attempt was made to clone a pluggable database that was opened
// in read/write mode.
// *Action: Retry the clone operation after the source pluggable database is
// in read-only mode.
//
65360, 00000, "unable to switchover"
// *Cause: An attempt was made to switchover a pluggable database (PDB) using
// a database link that pointed to the source pluggable database.
// *Action: Use a database link that points to the source multitenant container
// database root and retry the operation.
//
65361, 00000, "pluggable database %s is not a refresh copy"
// *Cause: An attempt was made to switchover to a pluggable database (PDB)
// which was not marked as a refresh copy.
// *Action: Switchover operation is allowed only with a target refreshable
// clone PDB.
//
65362, 00000, "pluggable database %s is not a refresh copy of the source pluggable database"
// *Cause: An attempt was made to switchover to a pluggable database (PDB)
// which was not marked as a refresh copy of the source pluggable
// database (PDB).
// *Action: Switchover operation is allowed only between a refreshable clone
// and its primary PDB.
//
65363, 00000, "pluggable database %s not enabled for snapshots"
// *Cause: An attempt was made to snapshot a pluggable database (PDB) which was
// created with snapshots disabled.
// *Action: Retry the operation after changing the snapshot mode of the PDB.
//
65364, 00000, "snapshot not found"
// *Cause: An attempt was made to create a pluggable database (PDB) using a
// snapshot or to drop a snapshot that could not be found.
// *Action: Check DBA_PDB_SNAPSHOTS for all existing PDB snapshots and retry
// the operation.
//
65365, 00000, "unable to create pluggable database"
// *Cause: An attempt was made to create a pluggable database (PDB) using a
// snapshot when Oracle Managed Files (OMF) was not enabled or if the
// CREATE_FILE_DEST clause was not specified.
// *Action: Enable OMF or specify CREATE_FILE_DEST clause and retry creating
// the pluggable database.
//
65366, 00000, "snapshot already exists"
// *Cause: An attempt was made to create a snapshot of a pluggable database
// (PDB) using a name that already existed.
// *Action: Specify a different name and retry the operation.
//
65367, 00000, "unable to switchover"
// *Cause: An attempt was made to switch over a pluggable database (PDB)
// that was not a normal pluggable database that could be opened
// in read/write mode.
// *Action: Switchover operation is allowed only with a source PDB in NORMAL
// status.
//
65368, 00000, "unable to open the pluggable database due to errors during recovery"
// *Cause: Recovery was required prior to opening the pluggable database, but
// an error during recovery was determined to be fatal enough to end
// both the recovery and the open operation.
// *Action: More specific messages accompany this message. Refer to the
// accompanying messages for the appropriate action.
//
65369, 00000, "The key column for the container map object has multiple values for each partition."
// *Cause: An attempt was made to generate logical partitioning key values
// using a container map object that had multiple values for each
// partition.
// *Action: Specify a container map object that has a single value for each
// partition and retry the operation.
//
65370, 00000, "%s initialization parameter cannot be specified in a lockdown profile"
// *Cause: An attempt was made to specify an illegal initialization parameter
// in a lockdown profile.
// *Action: Do not specify this initialization parameter in a lockdown profile.
//
65371, 00000, "%s initialization parameter cannot be modified in a template pluggable database"
// *Cause: An attempt was made to modify an illegal initialization
// parameter inside a template pluggable database (PDB).
// *Action: Do not modify this initialization parameter inside a template PDB.
//
65372, 00000, "Initialization parameter %0!s cannot be modified when initialization parameter %1!s is already set."
// *Cause: An attempt was made to set the PDB_LOCKDOWN initialization parameter
// along with the PDB_TEMPLATE initialization parameter.
// *Action: Reset the PDB_LOCKDOWN initialization parameter before setting the
// PDB_TEMPLATE initialization parameter or RESET the PDB_TEMPLATE
// initialization parameter before setting the PDB_LOCKDOWN
// initialization parameter.
//
65373, 00000, "operation not allowed in a template PDB"
// *Cause: The specified operation was not allowed in a template pluggable
// database (PDB).
// *Action: Do not perform this operation in a template PDB.
//
65374, 00000, "cannot set PDB_LOCKDOWN initialization parameter to an application lockdown profile"
// *Cause: An attempt was made to set the PDB_LOCKDOWN initialization parameter
// to an application lockdown profile when the PDB_LOCKDOWN
// initialization parameter was already set to a container database
// (CDB) lockdown profile.
// *Action: If PDB_LOCKDOWN initialization parameter is being set in an
// application pluggable database (PDB), contact the CDB administrator.
// If PDB_LOCKDOWN initialization parameter is being set in an
// application ROOT, set the PDB_LOCKDOWN initialization parameter
// in the required application PDBs.
//
65375, 00000, "cannot set PDB_TEMPLATE initialization parameter to an application template %s"
// *Cause: An attempt was made to set the PDB_TEMPLATE initialization parameter
// to an application template when the PDB_TEMPLATE initialization
// parameter was already set to a multitenant container database (CDB)
// template.
// *Action: If the PDB_TEMPLATE initialization parameter is being set in an
// application pluggable database (PDB), contact the CDB administrator.
// If the PDB_TEMPLATE initialization parameter is being set in an
// application ROOT, set the PDB_TEMPLATE initialization parameter
// in the required application PDBs.
//
65376, 00000, "unable to refresh the PDB"
// *Cause: A conflicting operation was in progress in the source pluggable
// database (PDB) for the refresh clone.
// *Action: Retry the operation later.
//
65377, 00000, "parameter cannot be modified"
// *Cause: An attempt was made to modify an in-memory value for the
// SGA_TARGET parameter with pluggable database isolation mode
// enabled.
// *Action: Do not modify an in-memory value for the SGA_TARGET parameter
// in PDB isolation mode.
//
65378, 00000, "illegal use of ALTER SYSTEM clause '%s' in the template pluggable database(PDB)"
// *Cause: An invalid clause was used in an ALTER SYSTEM operation.
// *Action: Choose a valid clause and retry the operation.
//
65379, 00000, "application %s is in transient state"
// *Cause: An attempt was made to unplug an application pluggable database
// (PDB), which had unfinished application action.
// *Action: Fix the application state in the application pluggable database
// (PDB) before unplugging the database.
//
65380, 00000, "unable to materialize"
// *Cause: An attempt was made to materialize a pluggable database (PDB)
// that was not created as a snapshot copy.
// *Action: Retry the operation on a PDB created as a snapshot copy.
//
65381, 00000, "unable to rename application root"
// *Cause: An attempt was made to rename an application root that has
// one or more open application PDBs.
// *Action: Close all application PDBs and retry the operation.
//
65382, 00000, "operation cannot be performed when subscribed template PDB is not open"
// *Cause: The template pluggable database (PDB) to which the current PDB
// was subscribed was not open.
// *Action: Open the template PDB that the current PDB was subscribed to before
// opening the current PDB.
//
65383, 00000, "unable to set MAX_PDB_SNAPSHOTS property to greater than %s"
// *Cause: An attempt was made to set the MAX_PDB_SNAPSHOTS property to a
// higher value than the allowed maximum.
// *Action: Retry the operation with a lower value.
//
65384, 00000, "missing or invalid property"
// *Cause: The issued operation had a missing property name or the property
// specified was invalid or not found in the database.
// *Action: Retry the operation with a valid property name.
//
65385, 00000, "missing or invalid value for property"
// *Cause: The issued operation had a missing property value or the property
// value specified was invalid.
// *Action: Retry the operation with a valid property value.
//
65386, 00000, "unable to alter property"
// *Cause: An attempt was made to specify a property that could not be
// altered using ALTER DATABASE PROPERTY or ALTER PLUGGABLE DATABASE
// PROPERTY statement.
// *Action: Retry the operation with a different property name.
//
65387, 00000, "unable to create pluggable database with the specified USER_TABLESPACES clause"
// *Cause: An attempt was made to create a pluggable database using an XML
// file that was generate with DBMS_PDB.RECOVER and all tablespaces
// were not included.
// *Action: Retry the operation with all tablespaces and regenerate the XML
// using unplug and then redo the subset clone.
//
65388, 00000, "PARTITION_CONTAINED only supported in subset cloning"
// *Cause: An attempt was made to use PARTITION_CONTAINED clause outside subset cloning.
// *Action: Either specify the USER_TABLESPACES clause or remove the PARTITION_CONTAINED clause.
//
65389, 00000, "unable to clone pluggable database"
// *Cause: An attempt was made to create a refreshable clone of a pluggable
// database (PDB) or relocate a PDB from a standby database.
// *Action: Retry the operation using a source PDB that is part of a primary
// database.
//
//
65390, 00000, "unable to mark the application object as No Linked"
// *Cause: An attempt was made to use SET_SHARING_NONE on an object with
// Metadata, Data, or Extended Data Linked status.
// *Action: Do not mark a Metadata, Data, or Extended Data Linked object as No Linked.
//
65391, 00000, "violation of container map partitions"
// *Cause: An attempt was made to insert or update a row in a container
// map enabled table that violated the partitions of the
// container map.
// *Action: Insert or update a row that does not violate the partitions
// of the container map.
//
65392, 00000, "object column is accessed in a fleet proxy pluggable database"
// *Cause: An attempt was made to access an object column in a fleet
// proxy Pluggable Database (PDB).
// *Action: Remove the object column from the query.
//
65393, 00000, "Media recovery to SCN %s must be performed in mount mode."
// *Cause: One or more pluggable databases could not be recovered by the
// RESETLOGS operation because the Oracle Active Data Guard
// standby database was still open.
// *Action: Close Oracle Active Data Guard standby database and restart
// media recovery.
65394, 00000, "LIBRARY does not use a DIRECTORY object"
// *Cause: The LIBRARY objects did not use a DIRECTORY object for the
// pluggable database (PDB) with a defined PATH_PREFIX.
// *Action: Re-create LIBRARY objects in the database to use a DIRECTORY object.
//
65395, 00000, "constraint cannot be added"
// *Cause: An attempt was made to add a referential integrity constraint from
// a table to a data-linked or an extended data-linked table.
// *Action: Add the referential integrity constraint in NOVALIDATE mode.
/
/////////////////////////////////////////////////////////////////////////////
/ 65400 - 64450 are reserved for CLUSTERING clause
/////////////////////////////////////////////////////////////////////////////
65400, 00000, "Table does not have CLUSTERING clause associated with it"
// *Cause: User attempts to modify clustering clasue on a table that
// that does not have one.
// *Action: Create CLUSTERING clause on the table first.
//
65402, 00000, "invalid option on CLUSTERING clause"
// *Cause: Invalid option on CLUSTERING clause. Only [YES | NO ] ON LOAD
// or [YES | NO ] ON DATA MOVEMENT are valid.
// *Action: Correct the option on the CLUSTERING clause.
//
65403, 00000, "invalid usage of CLUSTERING clause"
// *Cause: Invalid usage of CLUSTERING clause. The clause can be specified
// only for CREATE/ATLER TABLE/SNAPSHOT/MATERIALIZED VIEW
// *Action: Don't use CLUSTERING clause in this statement
//
65404, 00000, "CLUSTERING clause specified more than once on a table"
// *Cause: A table can have only one clustering clause. The clasue
// was specified multiple times.
// *Action: Correct the statement to use only one CLUSTERING clause.
//
65405, 00000, "CLUSTERING clause cannot be used with existing table options"
// *Cause: The CLUSTERING clause conflicted with other clauses on the table.
// The CUSTERING clause cannot be used with IOT, CLUSTERED, GLOBAL
// TEMPORARY TABLE, or the EXTERNAL TABLE clause.
// *Action: Correct the statement so the CLUSTERING clause does not conflict
// with other clauses.
//
65406, 00000, "invalid option on CLUSTERING clause"
// *Cause: The CLUSTERING clause was not followed by the
// BY [LINEAR | INTERLEAVED] ORDER option.
// *Action: Correct the option on the CLUSTERING clause.
//
65407, 00000, "CLUSTERING clause already exists on the table"
// *Cause: The ADD CLUSTERING clause was specified on a table with an existing
// CLUSTERING clause.
// *Action: If the table has a CLUSTERING clause, you can only change the
// ON LOAD or ON DATA MOVEMENT options. To change other options, you
// must first drop the clause.
//
65408, 00000, "CLUSTERING clause has too many columns in the BY ORDER subclause"
// *Cause: More than 10 columns were specified in the BY ORDER subclause.
// You can have at most 10 columns in the BY ORDER subclause.
// *Action: Lower the number of columns in the BY ORDER subclause to a value
// of 10 or less.
//
65409, 00000, "CLUSTERING clause has too many INTERLEAVED columns or groups"
// *Cause: More than 40 columns or more than 4 groups were specified in the
// BY INTERLEAVED ORDER subclause. You can have at most 40 columns and
// at most 4 groups in the INTERLEAVED ORDER subclause.
// *Action: Lower the number of columns to 40 or less, and lower the number of
// groups to 4 or less in the BY INTERLEAVED ORDER subclause.
//
65410, 00000, "CLUSTERING clause can have only scalar columns"
// *Cause: A non-scalar column was specified in the BY [LINEAR | INTERLEAVED]
// ORDER subclause. Also, virtual or hidden columns
// are not allowed.
// *Action: Specify only scalar columns in the BY [LINEAR | INTERLEAVED]
// ORDER subclause.
//
65411, 00000, "CLUSTERING clause does not exist"
// *Cause: An attempt was made to modify or drop a CLUSTERING clause in a
// table that had no CLUSTERING clause associated with it.
// *Action: Do not attempt to modify a nonexistent CLUSTERING clause.
//
65412, 00000, "invalid option on ALTER TABLE .. CLUSTERING .."
// *Cause: You specified an invalid option on ALTER TABLE...CLUSTERING.
// For example, you specified DROP and ADD CLUSTERING in one statement.
// *Action: Correct the statement.
//
65413, 00000, "cannot resolve referenced object in the CLUSTERING clause"
// *Cause: An object was referenced in the CLUSTERING clause that could not
// be resolved to a base table reference.
// *Action: The CLUSTERING clause can refer to base tables only.
//
65414, 00000, "column resolves to multiple tables in the CLUSTERING clause"
// *Cause: A column resolved to multiple tables in the CLUSTERING clause.
// *Action: Correct the statement. The column should resolve to only one table.
// The table name should be qualified with its owner name.
//
65415, 00000, "wrong join condition in the CLUSTERING clause"
// *Cause: The CLUSTERING clause had an OR condition and the individual
// join condition on the base table columns was not an equijoin.
// *Action: Correct the statement. Ensure that join conditions are
// equijoins and there are no OR conditions, or no expressions in
// the join.
//
65416, 00000, "multiple dimension tables in the CLUSTERING clause"
// *Cause: Joins in the CLUSTERING clause referenced a dimension table
// more than once.
// *Action: Correct the statement. Remove one of the references.
//
65417, 00000, "illegal dimension table in the CLUSTERING clause"
// *Cause: The dimension table in the CLUSTERING clause was illegal.
// Dimension table cannot be GLOBAL TEMPORARY TABLE or EXTERNAL TABLE.
// *Action: Rewrite the statement so it does not use an illegal option on
// the dimension table.
//
65418, 00000, "primary or unique key constraint missing in CLUSTERING join"
// *Cause: The join between the fact and dimension tables in the CLUSTERING
// clause did not have a primary or unique key constraint on the
// dimension table join column(s).
// *Action: Add a primary or unique key constraint to the join column(s) on
// the dimension table.
//
65419, 00000, "columns in a clustering group come from different tables"
// *Cause: Columns in the clustering group did not come from the same table.
// For example: .. CLUSTERING BY ..( (t1.c1, t2.c2), (t2.c1, t2.c2) ).
// Clustering group (t1.c1, t2.c2) must contain references to only
// one table.
// *Action: Restructure the clustering group so it contains only references
// to a single table.
//
65420, 00000, "columns in a join condition in the CLUSTERING clause are not compatible"
// *Cause: The data type of columns in the join condition of CLUSTERING clause
// were not compatible. They must be of the same type.
// *Action: Select a compatible data type for the join conditions in the
// CLUSTERING clause.
//
65421, 00000, "The CLUSTERING clause is defined on columns that are to be modified"
// *Cause: An ALTER TABLE MODIFY COLUMN command was issued on a column on which
// a CLUSTERING clause exists.
// *Action: Drop the CLUSTERING clause before attempting to modify the column.
//
65422, 00000, "The CLUSTERING clause already has a zonemap defined on it"
// *Cause: An ALTER TABLE MODIFY CLUSTERING command was issued with the WITH
// MATERIALIZED ZONEMAP option but the table already had zonemap define on it.
// *Action: Drop the zonemap associated with the base table before attempting
// to add zonemap using the CLUSTERING clause.
//
65423, 00000, "The CLUSTERING clause does not have a zonemap associated with it"
// *Cause: An ALTER TABLE MODIFY CLUSTERING command was issued with the WITHOUT
// MATERIALIZED ZONEMAP option but the table did not have zonemap
// associated with the CLUSTERING clause.
// *Action: Do not use the ALTER TABLE MODIFY CLUSTERING WITHOUT ZONEMAP.
//
65424, 00000, "CLUSTERING clause has too many joins"
// *Cause: More than 4 joins were specified in the CLUSTERING clause.
// You can have at most 4 joins to the dimension tables.
// *Action: Reduce the number of joins to 4 or less.
//
65425, 00000, "CLUSTERING clause not supported for table stored in tablespace of this storage type"
// *Cause: An attempt was made to define clustering on a table stored in
// non-Oracle Exadata storage.
// *Action: Create this table in a tablespace residing on Oracle Exadata
// storage or remove the CLUSTERING clause.
//
65426, 00000, "Non-scalar data type is used for a clustering column"
// *Cause: Oracle cannot perform data clustering because an attempt was made to populate a
// clustering column with non-scalar data values, or a clustering column defaulted
// to non-scalar values was omitted.
// *Action: Use only scalar data type for the clustering columns, or disable data clustering
// with NO_CLUSTERING hint.
//
65427, 00000, "A system-generated column or unused column is used in a join condition in the CLUSTERING clause."
// *Cause: An attempt was made to use a system-generated or unused column
// in a join condition in the CLUSTERING clause.
// *Action: Remove the system-generated or unused column in the join condition in
// the CLUSTERING clause.
//
/
////////////////////////////////////////////////////////////////////////////
65451, 00000, "Advanced index compression is not supported for tablespaces on this storage type."
// *Cause: An attempt was made to use advanced index compression on
// an unsupported storage type.
// *Action: Drop and re-create the index with a compression option that is
// supported on the current storage type.
//
/
////////////////////////////////////////////////////////////////////////////
/ 65455 - 65466 reserved for family errors
////////////////////////////////////////////////////////////////////////////
65455, 00000, "family %s is invalid"
// *Cause: An invalid family was used to specify a parameter value.
// *Action: Use a valid family.
//
65456, 00000, "family %s is not valid in %s instance"
// *Cause: The specified family could not be used in the current instance type.
// *Action: Remove the family from the environment variable ORACLE_FAMILY.
//
65457, 00000, "family %s is not valid in %s instance"
// *Cause: The specified family could ot be used in the current instance type.
// *Action: Use a family that is valid for this instance to set the
// initialization parameter.
//
65458, 00000, "maximum length of parameter qualifier exceeded"
// *Cause: Too many characters were specified in the parameter qualifier in
// the initialization parameter file.
// *Action: Change the parameter qualifier to a valid SID or family.
//
65459, 00000, "family used with a specific system identifier (SID)"
// *Cause: A SID was used with FAMILY.
// *Action: Use FAMILY without a SID.
//
65460, 00000, "family %s is invalid"
// *Cause: An invalid family was specified for this instance in ORACLE_FAMILY.
// *Action: Use a valid family in ORACLE_FAMILY.
//
65461, 00000, "invalid parameter name specified with CONTAINER clause set to ALL"
// *Cause: The CONTAINER clause was set to ALL in the ALTER SYSTEM SET statement
// for a non-PDB modifiable or non-inheritable PDB parameter.
// *Action: Retry the ALTER SYSTEM SET statement without the CONTAINER clause.
//
65462, 00000, "error while updating a dependent parameter '%s'"
// *Cause: An internal error was encountered while trying to update dependent parameter value.
// *Action: Contact Oracle Support Services.
//
/
65466, 00000, "family '%s' contains an illegal character or is too long"
// *Cause: The specified family contained an illegal character or the family
// specified was too long, which cannot occur in an SPFILE setting.
// Illegal characters include *,#"'=() and whitespace.
// *Action: Use a family that does not contain a special character or whitespace.
// Check platform-specific documentation for the maximum length of
// family.
//
/
////////////////////////////////////////////////////////////////////////////
/ 65470- 65499 reserved for SHADOW LOST WRITE PROTECTION
////////////////////////////////////////////////////////////////////////////
65470, 00000, "unnecessary lost write command - lost write already in requested state"
// *Cause: Lost write was already in the requested state. If enable or disable
// lost write was specified, then lost write was already in the
// enabled or disabled state.
// *Action: No action is necessary. This is an informational message only.
/
65471, 00000, "LOST WRITE PROTECTION cannot be enabled on this type of tablespace."
// *Cause: LOST WRITE PROTECTION could not be enabled for lost write
// tablespaces or temporary tablespaces.
// *Action: Do not attempt to enable LOST WRITE PROTECTION for these types.
/
65472, 00000, "invalid option for ALTER lost write TABLESPACE"
// *Cause: An invalid option was specified while altering
// a LOST WRITE PROTECTION tablespace.
// *Action: Lost write tablespaces cannot be altered with clauses LOGGING,
// ENCRYPTION, REKEY, FLASHBACK, TEMPORARY, DEFAULT,
// or COMPRESS options.
/
65473, 00000, "invalid option for FLASHBACK"
// *Cause: An invalid option was specified while creating or altering
// a flashback tablespace.
// *Action: Lost write tablespaces cannot be used for flashback.
/
65474, 00000, "lost write tablespace does not exist or has insufficient space or lost write is off"
// *Cause: Enabling lost write protection could not succeed because the lost
// write tablespaces did not exist or had insufficient space. It is
// possible that shadow lost write was not enabled for the database.
// *Action: Create a lost write tablespace or add space to an existing lost
// write tablespace. Also, ensure that the shadow lost write
// protection is turned on for the database.
/
65475, 00000, "Write advisory message when a lower SCN tries to overwrite a higher SCN."
// *Document: NO
// *Cause:
// *Action: Enable this event to write advisory messages whenever lost write
// detects a lower SCN trying to overwrite a higher SCN in the lost
// write shadow tablespace. This is not necessarily an error since
// the order of recording lost write SCNs might have been reversed.
// In the future we can consider reading the tracked block from disk
// to check it.
/
65476, 00000, "could not get data file space header"
// *Cause: There was an internal error code.
// *Action: Make sure the data file is online and the database is open.
/
65477, 00000, "lost write protection - invalid state transition"
// *Cause: The object that was manipulated could not be set to the requested
// state.
// *Action: Ensure that the state transition is valid.
/
65478, 00000, "shadow lost write protection - found lost write"
// *Cause: A lost write was found in a data block protected by lost write.
// *Action: The data block can be recovered to fix lost write.
/
65480, 00000, "invalid option for CREATE TABLESPACE"
// *Cause: An invalid option was specified while creating
// LOST WRITE PROTECTION tablespace.
// *Action: LOST WRITE PROTECTION cannot be specified with the DEFAULT,
// EXTENT MANAGEMENT, SEGMENT SPACE MANAGEMENT, FORCE,
// MINIMUM EXTENT, LOGGING, ENCRYPTION, TEMPORARY,
// UNDO, or FLASHBACK options.
/
65481, 00000, "LOST WRITE PROTECTION option already specified"
// *Cause: In CREATE TABLESPACE, the LOST WRITE PROTECTION option was
// specified more than once.
// *Action: Remove all but one of the LOST WRITE PROTECTION specifications.
/
65482, 00000, "invalid option for CREATE TABLESPACE"
// *Cause: An invalid option was specified while creating a
// tablespace.
// *Action: Review the syntax and reissue the command.
/
65483, 00000, "invalid option for creation of LOST WRITE PROTECTION tablespace"
// *Cause: The BIGFILE keyword was not specified while creating a LOST WRITE
// PROTECTION tablespace.
// *Action: Specify the BIGFILE keyword while creating a LOST WRITE PROTECTION tablespace.
/
65484, 00000, "cannot specify LOST WRITE PROTECTION tablespace as default tablespace"
// *Cause: An attempt was made to assign a LOST WRITE PROTECTION tablespace
// to be a user's default tablespace.
// *Action: Assign a permanent tablespace to be the default tablespace.
/
65485, 00000, "cannot create user objects in LOST WRITE PROTECTION tablespace"
// *Cause: An attempt was made to create user objects in a LOST WRITE PROTECTION tablespace. Other system objects such as rollback segments are also illegal.
// *Action: Create the object in a permanent tablespace.
/
65486, 00000, "cannot specify a LOST WRITE PROTECTION tablespace as default tablespace"
// *Cause: An attempt was made to assign a LOST WRITE PROTECTION tablespace
// to be a default tablespace.
// *Action: Assign a permanent tablespace to be the database default tablespace.
/
65487, 00000, "Lost write tablespaces must all have the same block size."
// *Cause: A different block size was specified when a SHADOW LOST WRITE
// tablespace was created.
// *Action: Retry creating the lost write tablespace using the
// same block size as the other lost write tablespaces. If a duplicate
// tablespace name error is encountered then you
// may have to drop this tablespace using the SQL DROP TABLESPACE
// <tablespace_name> command.
/
65488, 00000, "SHADOW LOST WRITE cannot be enabled on a standby database."
// *Cause: An attempt was made to enable SHADOW LOST WRITE on a standby database.
// *Action: SHADOW LOST WRITE can only be enabled on a primary database.
/
65489, 00000, "Lost write tablespace cannot be enabled or created"
// *Cause: An attempt was made to enable lost write when the database was
// not open or an access error occurred when attempting to access the
// new_lost_write_shadows$ dictionary table
// *Action: Enable SHADOW LOST WRITE or create a shadow tablespace
// when the database is open.
/
65490, 00000, "invalid parameters for LOST WRITE PROTECTION tablespace"
// *Cause: Invalid parameters were specified for a LOST
// WRITE PROTECTION tablespace. Only BIGFILE TABLESPACE, SIZE and BLOCKSIZE for
// a LOST WRITE PROTECTION tablespace can be specified upon creation. ALTER
// cannot be used to make a LOST WRITE PROTECTION tablespace read-only.
// *Action: Create the tablespace using the CREATE BIGFILE TABLESPACE
// <tablespace name> ... DATAFILE '<data_file_name>' SIZE <size>
// BLOCKSIZE <block_size> LOST WRITE PROTECTION statement.
65491, 00000, "A lost write bigfile tablespace must exist before attempting to enable lost write"
// *Cause: The lost write tablespace does not exist.
// *Action: Create the tablespace using the CREATE BIGFILE TABLESPACE
// <tablespace_name> ... DATAFILE '<datafile_name>' SIZE <size>
// BLOCKSIZE <size> LOST WRITE PROTECTION statement;
65492, 00000, "Cannot get data file space header"
// *Cause: An internal error occurred.
// *Action: Try disabling the lost write protection and then create the lost write
// tablespace again using the CREATE BIGFILE TABLESPACE <tablespace name>
// DATAFILE '<datafile_name>' SIZE <size> BLOCKSIZE <size>
// LOST WRITE PROTECTION. You may have to drop the lost write tablespace
// first on which this command failed.
65493, 00000, "cannot shrink a lost write tablespace"
// *Cause: An attempt was made to shrink a lost write tablespace.
// *Action: Lost write tablespaces cannot be shrunk. The drop can either drop all tracking data or move it to another lost write tablespace.
65494, 00000, "LOST WRITE PROTECTION could not write to or read dictionary tables or inconsistent dictionary tables."
// *Cause: There was an internal error in lost write subsystem. The SYSAUX
// tablespace may be inaccessible or full.
// *Action: Check the SYSAUX tablespace first. If the SYSAUX tablespace is OK then this is an internal error.
65495, 00000, "LOST WRITE PROTECTION could not create shadow tablespace."
// *Cause: There was an internal error in lost write subsystem.
// *Action: Drop the lost write shadow tablespace just created using the SQL DROP TABLESPACE <tablespace_name> ... command.;
65496, 00000, "Lost write tables are inconsistent. Delete may have occurred."
// *Cause: One of the lost write tracking tables was inconsistent. A parallel
// operation may have caused this problem.
// *Action: If lost write tracking is working properly, then this error can be ignored.
65497, 00000, "Internal event for inducing lost writes"
// *Document: NO
// *Cause: This is an Oracle internal event code. It is used to increment the
// the recorded SCN of blocks that are being logged for lost write.
// This will cause the lost write detection to trigger when these
// blocks are read back in. This should not be set at customer sites.
// *Action: N/A, this is an Oracle internal event code.
65498, 00000, "SHADOW LOST WRITE tablespace could not be dropped."
// *Cause: An internal error occurred when performing drop side effects
// *Action: The lost write tablespace should still be operational.
// Contact Oracle Support Services.
65499, 00000, "Illegal SHADOW LOST WRITE operation on a read-only database"
// *Cause: The attempted lost write operation is prohibited on a read-only database.
// *Action: Set the database to read/write before performing this command.
//////////////////////////////////////////////////////////////////////////////
/ End of shadow lost write messages
//////////////////////////////////////////////////////////////////////////////
65500, 00000, "could not modify DB_UNIQUE_NAME, resource exists"
// *Cause: DB_UNIQUE_NAME could not be modified, because a database resource
// identified by DB_UNIQUE_NAME existed in the cluster. To modify
// DB_UNIQUE_NAME, any resource it identifies must first be removed.
// *Action: Remove the database resource identified by DB_UNIQUE_NAME before
// modifying DB_UNIQUE_NAME.
/
////////////////////////////////////////////////////////////////////////////
/ 65501- 65529 reserved for LOB layer errors
////////////////////////////////////////////////////////////////////////////
65501, 00000, "locator from %s container cannot be used in container %s for this operation"
// *Cause: In a pluggable database environment, an attempt was made to modify
// a LOB using a locator which belongs to a different container.
// *Action: Switch back to the original container.
//
/
65502, 00000, "cannot access temporary LOB data"
// *Cause: The database did not open.
// *Action: Open the database before accessing LOB data.
/
65503, 00000, "cannot send or receive temporary LOB locators over a database link"
// *Cause: An attempt was made to send or receive a temporary LOB locator over
// a database link.
// *Action: Do not send or receive a temporary LOB locator over a database link.
/
65504, 00000, "cannot send or receive LOB locators from an index-organized table over a database link"
// *Cause: An attempt was made to send or receive a temporary LOB locator from
// an index-organized table over a database link.
// *Action: Do not send or receive a LOB locator from an index-organized table
// over a database link.
/
65505, 00000, "cannot pass a remote LOB locator as parameter to this operation"
// *Cause: An attempt was made to pass a remote LOB locator as a parameter to a
// LOB operation which does not accept a remote LOB locator.
// *Action: Do not pass a remote LOB locator as a parameter to this operation.
/
65506, 00000, "cannot pass LOB locators belonging to different databases"
// *Cause: An attempt was made to pass LOB locators belonging to different
// databases as parameters to the same LOB operation.
// *Action: Ensure that all of the LOB locator parameters belong
// to the same database.
/
65507, 00000, "cannot select a LOB locator across multiple database links"
// *Cause: An attempt was made to select from a remote database, a LOB locator
// which was obtained by the remote from another remote database.
// *Action: Ensure that the locator which is selected from a remote database
// belongs to that remote database.
/
65508, 00000, "cannot send or receive an invalid LOB locator over database link"
// *Cause: An attempt was made to send or receive an invalid LOB locator
// over a database link.
// *Action: Ensure that the locator which is sent to a remote database
// or received from a remote database is a valid locator.
/
65509, 00000, "Cannot use remote LOBs in INSERT AS SELECT DMLs with INSTEAD OF triggers."
// *Cause: An attempt was made to perform an operation INSERT AS SELECT on a
// view with INSTEAD OF trigger on it and a remote LOB column in the
// select list.
// *Action: Do not use remote LOB locators in INSERT AS SELECT DMLs with
// INSTEAD OF triggers.
/
65510, 00000, "Distributed LOB operations are not supported on pre-12.2 databases."
// *Cause: An attempt was made to send or receive a LOB locator
// over a database link to a pre-12.2 database.
// *Action: Ensure that the remote database for a distributed LOB operation is
// Oracle Database version 12.2 or higher.
/
65511, 00000, "SQL statement executed on a remote database over a database link cannot access a LOB on the local database with parallel execution enabled on the remote side"
// *Cause: This is likely the result of passing a local LOB locator as a
// bind value to a SQL statement that is executed on a remote
// database over a database link. For example, running the statement
// "INSERT INTO tabl1@@dblink VALUES (:1)" where the bind value is
// a local persistent LOB locator and parallel execution is enabled
// on the remote side.
// *Action: Disable parallel execution for the SQL statement on the remote
// database.
/
////////////////////////////////////////////////////////////////////////////
/ 65530 - 65534 reserved for INDEX layer errors
////////////////////////////////////////////////////////////////////////////
65530, 00000, "CELLCACHE feature not supported for IOTs"
// *Document: NO
// *Cause: An attempt was made to enable the CELLCACHE feature for an
// index-organized table.
// *Action: None.
/
65531, 00000, "maximum level reached in index segment with object id %s"
// *Cause: The attempted operation resulted in the number of index levels
// exceeding the maximum allowed.
// *Action: Reduce the size of the relevant index, for example, by using
// compression or partitioning.
/
65535, 00000, "Oracle Database client cannot handle error code exceeding 65535. Actual error code and message follow:\n"
// *Cause: Oracle Database clients earlier than release 12.1 could not handle
// error codes larger than 65535.
// *Action: Upgrade Oracle Database client library to release 12.1 or later.
OHA YOOOO