ORA-29250 to ORA-32775
ORA-29250: 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.
ORA-29251: 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.
ORA-29252: 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.
ORA-29253: 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.
ORA-29254: 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.
ORA-29255: 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.
16-2 Oracle Database Error Messages
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.
ORA-29256: 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.
ORA-29257: host string 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.
ORA-29258: 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.
ORA-29259: 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.
ORA-29260: network error: string
Cause: A network error occurred.
Action: Fix the network error and retry the operation.
ORA-29261: 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.
ORA-29262: bad URL
Cause: An improperly formed URL was passed to the PL/SQL API.
Action: Check the URL and retry the call.
ORA-29263: 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.
ORA-29264: 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.
ORA-29265: HTTP header not found
Cause: The requested HTTP header was not found.
Action: Check to make sure that the requested HTTP header is present.
ORA-29266: 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.
ORA-29267: 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.
ORA-29268: HTTP client error string
Cause: The HTTP response indicated that the HTTP client error occurred.
Action: Fix the HTTP client error and retry the HTTP request.
ORA-29269: HTTP server error string
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.
ORA-29270: too many open HTTP requests
Cause: Too many HTTP requests were opened.
Action: End some HTTP requests and retry the HTTP request.
ORA-29271: 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.
ORA-29272: initialization failed
Cause: The UTL_HTTP package failed to initialize.
Action: Free up some memory or other system resources and retry the operation.
ORA-29273: 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.
ORA-29274: 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.
ORA-29275: 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.
16-4 Oracle Database Error Messages
ORA-29276: 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.
ORA-29277: 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.
ORA-29278: SMTP transient error: string
Cause: A SMTP transient error occurred.
Action: Correct the error and retry the SMTP operation.
ORA-29279: SMTP permanent error: string
Cause: A SMTP permanent error occurred.
Action: Correct the error and retry the SMTP operation.
ORA-29280: 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.
ORA-29281: 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”.
ORA-29282: 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.
ORA-29283: 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.
ORA-29284: 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.
ORA-29285: 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.
ORA-29286: 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.
ORA-29287: 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].
ORA-29288: invalid file name
Cause: A NULL or zero length file name was specified.
Action: Correct the file name to be a nonzero length string.
ORA-29289: 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];.
ORA-29290: invalid offset specified for seek
Cause: An attempt was made to seek past the end of the file, or both the absolute
and relative offsets were NULL, or absolute offset was less than zero.
Action: If specifying an absolute offset, ensure it is in the range [0, ], or if specifying a relative offset, ensure it is no greater than
the current byte position plus the number of bytes remaining in the file.
ORA-29291: 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.
ORA-29292: 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.
ORA-29293: 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.
ORA-29294: 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.
ORA-29295: 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:
=????=
ORA-29296: invalid encoded string
16-6 Oracle Database Error Messages
Cause: An error occurred while decoding the input string
Action: Verify that source data is a valid encoded string.
ORA-29297: The compressed representation is too big
Cause: The compressed output is too big to return.
Action: Do not attempt to compress source data.
ORA-29298: 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.
ORA-29299: 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.
ORA-29300: 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.
ORA-29301: 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.
ORA-29302: database is not open clone
Cause: The database was not opened as a clone database.
Action: Mount the database clone and open the database.
ORA-29303: 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.
ORA-29304: tablespace “string” 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.
ORA-29305: cannot point-in-time recover tablespace “string”
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.
ORA-29306: datafile string is not online
Cause: The selected datafile was not online.
Action: Bring the the datafile online and rename it if necessary.
ORA-29307: datafile string error, string
Cause: The datafile is not ready for tablespace point-in-time recovery.
Action: Check the correct tablespace point-in-time recovery procedure.
ORA-29308: 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.
ORA-29309: 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.
ORA-29310: 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.
ORA-29311: export dump file was not generated by this database, string 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.
ORA-29312: changes by release string cannot be used by release string, type: string
Cause: A point-in-time tablespace was chosen to perform the recovery, but the
current database is not compatible with the database that was used to create the
point-in-time tablespace.
Action: Choose a point-in-time and retry the operation.
ORA-29313: tablespace “string” cannot be imported twice
Cause: This is an internal error.
Action: Contact your database administrator.
ORA-29314: tablespace “string” is not OFFLINE FOR RECOVER nor READ ONLY
Cause: Tablespace clean SCN is either 0 or invalid.
Action: ALTER the tablespace OFFLINE FOR RECOVER.
ORA-29315: tablespace “string” 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.
ORA-29316: datafile string been imported twice
Cause: This is an internal error.
Action: Contact your database administrator.
ORA-29317: datafile string does not exist
Cause: The specified datafile could not be found in the production database.
Action: Copy the datafile from the clone database.
ORA-29318: datafile string is online
16-8 Oracle Database Error Messages
Cause: The datafile is online.
Action: Take the datafile offline.
ORA-29319: datafile string 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.
ORA-29320: 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.
ORA-29321: 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.
ORA-29322: 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.
ORA-29323: ALTER DATABASE SET COMPATIBILITY command not supported by
string
Cause: The ALTER DATABASE SET COMPATIBILITY command failed because
one or more instances do not support dynamic compatible setting change.
Action: No action required.
ORA-29324: SET COMPATIBILITY release string format is wrong
Cause: It should be of the form x.x.x
Action: Use the correct format.
ORA-29325: SET COMPATIBILITY release number lower than string
Cause: The SET COMPATIBILITY release compatibility release number was lower
than the current compatible setting.
Action: Specify a higher release number.
ORA-29326: SET COMPATIBILITY release number higher than string
Cause: The ALTER DATABASE SET COMPATIBILITY command failed because
one or more instances had a lower release number.
Action: Specify a lower release number.
ORA-29327: 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.
ORA-29328: too many datafiles in this tablespace “string”
Cause: Too many datafiles in this bitmap tablespace. ORACLE does not support
at this moment.
Action: Call Oracle Support.
ORA-29329: Table not of type XMLType
Cause: Table is not XMLType table
Action: Ensure table is a XMLType table
ORA-29330: 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.
ORA-29335: tablespace “string” is not read only
Cause: The tablespace is not read only.
Action: Make the tablespace read only and retry the operation.
ORA-29336: Internal error [string] [string] from DBMS_PLUGTS
Cause: Internal error from package DBMS_PLUGTS.
Action: Call Oracle Support.
ORA-29337: tablespace “string” has a non-standard block size (string)
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
ORA-29338: datafile string is in an undesired state (string, string)
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.
ORA-29339: tablespace block size string 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.
ORA-29340: export file appears to be corrupted: [string] [string] [string]
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.
ORA-29341: 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.
ORA-29342: user string 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.
16-10 Oracle Database Error Messages
ORA-29343: user string (mapped from user string) 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.
ORA-29344: Owner validation failed – failed to match owner “string”
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.
ORA-29345: 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.
ORA-29346: 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.
ORA-29347: Tablespace name validation failed – failed to match tablespace “string”
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.
ORA-29348: 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.
ORA-29349: tablespace “string” 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.
ORA-29351: can not transport system, sysaux, or temporary tablespace “string”
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.
ORA-29352: event “string” 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.
ORA-29353: The transportable list is too long.
Cause: The transportable list exceeds the buffer size of 32767.
Action: Reduce the list of tablespaces to transport.
ORA-29355: NULL or invalid string argument specified
Cause: The named argument was either invalid or specified as a NULL
Action: Specify non-null, valid arguments.
ORA-29356: These parameters can be specified only for directives that refer to
consumer groups
Cause: The below parameters were specified as an argument to procedure
CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package DBMS_
RESOURCE_MANAGER.where the GROUP_OR_SUBPLAN argument is a
resource plan. “ACTIVE_SESS_POOL_P1”, “QUEUEING_P1”, “PARALLEL_
DEGREE_LIMIT_P1”, “SWITCH_P1”, “SWITCH_P2”, “SWITCH_P3”, “MAX_EST_
EXEC_TIME”, “UNDO_POOL”
Action: Specify these parameters only for consumer group directives.
ORA-29357: object string already exists
Cause: The name specified as argument to procedure CREATE_PLAN, CREATE_
CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER was already in
use.
Action: Specify an unused name.
ORA-29358: resource plan string does not exist
Cause: An invalid plan name was specified as an argument to procedure
UPDATE_PLAN of package DBMS_RESOURCE_MANAGER.
Action: Specify an existing plan name.
ORA-29359: invalid method name string specified for resource plan string
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.
ORA-29360: retry operation. Too much concurrent activity
Cause: An attempt was made to revoke the switch consumer group privilege from
a user for his/her initial consumer group but someone is modifying the user in
another session.
Action: Retry the operation later.
ORA-29361: value string 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.
ORA-29362: plan directive string, string does not exist
Cause: A non-existent plan directive was specified for procedure UPDATE_
PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.
Action: Specify an existing plan directive for update.
ORA-29363: plan directive string, string is mandatory and cannot be modified or
deleted
Cause: An attempt was made to modify a mandatory plan directive.
16-12 Oracle Database Error Messages
Action: Do not attempt to modify mandatory plan directives because they are
required by the Resource Manager and cannot be modified.
ORA-29364: plan directive string, string already exists
Cause: An attempt was made to create a plan directive that already exists.
Action: Retry the create operation using different values.
ORA-29365: parameters string and string cannot both be set
Cause: An attempt was made to set both parameters.
Action: Only set one of parameters or neither of them.
ORA-29366: invalid CONSUMER_GROUP argument specified
Cause: An invalid consumer group name was specified.
Action: Specify a non-NULL, valid consumer group name.
ORA-29367: object string 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.
ORA-29368: consumer group string does not exist
Cause: An non-existent consumer group was specified.
Action: Specify an existing consumer group.
ORA-29369: invalid method name string specified for consumer group string
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.
ORA-29370: 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.
ORA-29371: 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.
ORA-29372: identifier string is too long; it must be less than string characters
Cause: An attempt was made to specify an identifier that is more than 30
characters long.
Action: Use an identifier that is 30 characters or less in length.
ORA-29373: 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.
ORA-29374: resource plan string in top-plan string 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.
ORA-29375: sum of values string for level string, plan string exceeds string
Cause: The sum of plan directive parameter values for the specified plan level
exceeded 100.
Action: Alter the values for the level so that they sum to 100.
ORA-29376: number of consumer groups string in top-plan string exceeds string
Cause: The number of consumer groups in the specified top-plan is more than 32.
Action: Change the top-plan to have no more than 32 consumer groups.
ORA-29377: consumer group string is not part of top-plan string
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.
ORA-29378: 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.
ORA-29379: resource plan string is involved in a loop in top-plan string
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.
ORA-29380: resource plan string 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.
ORA-29381: plan/consumer_group string 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.
ORA-29382: 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.
ORA-29383: all leaves of top-plan string 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.
ORA-29384: number of children for plan string exceeds string
Cause: An attempt was made to create or modify the specified plan, but the plan
has more than 32 children.
Action: Make sure the specified plan points to no more than 32 distinct nodes.
16-14 Oracle Database Error Messages
ORA-29385: cannot create plan directive from string to string
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.
ORA-29386: plan or consumer group string 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.
ORA-29387: 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.
ORA-29388: plan/consumer_group string 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.
ORA-29389: 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.
ORA-29390: 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.
ORA-29391: %s and string 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.
ORA-29392: cpu parameters for level string for plan string 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.
ORA-29393: user string 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.
ORA-29394: session id string and serial# string 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.
ORA-29395: cannot set the initial consumer group to string
Cause: An attempt was made to set the initial consumer group of a user to
OTHER_GROUPS.
Action: OTHER_GROUPS is for the resource manager”s internal use. Specify
another consumer group.
ORA-29396: cannot switch group to string
Cause: An attempt was made to switch the consumer group of a user or a session
to OTHER_GROUPS.
Action: OTHER_GROUPS is for the resource manager”s internal use. Specify
another consumer group.
ORA-29397: cannot grant/revoke switch privilege for string
Cause: An attempt was made to grant or revoke the privilege to switch to
OTHER_GROUPS.
Action: OTHER_GROUPS is for the resource manager”s internal use. Specify
another consumer group.
ORA-29398: 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.
ORA-29399: user string does not have privilege to switch to consumer group string
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.
ORA-29400: data cartridge error string
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.
ORA-29500: 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.
16-16 Oracle Database Error Messages
ORA-29501: 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.
ORA-29502: 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.
ORA-29503: 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.
ORA-29504: invalid or missing schema name
Cause: The required schema name was invalid or missing.
Action: Specify a valid schema name.
ORA-29505: 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.
ORA-29506: invalid query derived from USING clause
Cause: The USING clause did not form a valid query.
Action: Correct the USING clause.
ORA-29507: 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.
ORA-29508: query derived from USING clause did not select a value of type string
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.
ORA-29509: 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.
ORA-29510: name, string.string, 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.
ORA-29511: 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.
ORA-29512: incorrectly formed name resolver specification
Cause: A name resolver was not specified in the required form: ((
, ) …)
Action: Correct the specification.
ORA-29513: 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.
ORA-29514: 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.
ORA-29515: exit called from Java code with status string
Cause: Java code included a call to java.lang.Runtime.exitInternal.
Action: Do not include this call unless non-local exit is desired.
ORA-29516: Aurora assertion failure: string
Cause: An internal error occurred in the Aurora module.
Action: Contact Oracle Worldwide Support.
ORA-29517: 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.
ORA-29518: name string resolved to an object in schema string 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.
ORA-29519: name string resolved via a synonym in schema string 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.
ORA-29520: name string resolved to a class in schema string that could not be
accessed
Cause: An attempt to access a referenced class failed.
Action: Adjust authorizations or name resolution.
ORA-29521: referenced name string could not be found
16-18 Oracle Database Error Messages
Cause: Name resolution failed to find an object with the indicated name.
Action: Adjust name resolver or add missing Java class.
ORA-29522: authorization error for referenced name string.string
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.
ORA-29523: 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.
ORA-29524: wrong types of arguments in call to “string”
Cause: A method was called with argument(s) of incompatible type(s).
Action: Adjust caller.
ORA-29525: referenced name is too long: “string”
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.
ORA-29526: created Java class string”string”
Cause: An informational message, not an error.
Action: None.
ORA-29527: created Java source string”string”
Cause: An informational message, not an error.
Action: None.
ORA-29528: invalid Java call in trigger string
Cause: The Java method specified in trigger does not exist or cannot be called as
used.
Action: Adjust trigger definition.
ORA-29529: invalid function or method call string in trigger string
Cause: The function or method specified in Java trigger call expression could not
be resolved.
Action: Adjust trigger definition.
ORA-29530: could not create shortened name for string
Cause: Insert into shortened name translation table failed.
Action: Retry the insert.
ORA-29531: no method string in class string
Cause: An attempt was made to execute a non-existent method in a Java class.
Action: Adjust the call or create the specified method.
ORA-29532: Java call terminated by uncaught Java exception: string
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.
ORA-29533: attempt to overwrite class or resource string while defining or
compiling string.string
Cause: A class or resource defined by a SQLJ source conflicted with an existing
object.
Action: Remove existing object, or modify SQLJ source.
ORA-29534: referenced object string.string 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.
ORA-29535: 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.
ORA-29536: badly formed source: string
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.
ORA-29537: 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.
ORA-29538: 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.
ORA-29539: 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.
ORA-29540: class string 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.
ORA-29541: class string.string 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.
ORA-29542: class string already defined by source string
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.
16-20 Oracle Database Error Messages
Action: Either drop the old source or modify the new source.
ORA-29543: Java command string not yet implemented
Cause: An attempt was made to use a Java command that is not yet implemented.
Action: Do not use the command.
ORA-29544: 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.
ORA-29545: badly formed class: string
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.
ORA-29546: badly formed resource: string
Cause: An attempt was made to create a Java resource object with data that was
rejected by the Java verifier.
Action: Correct the data.
ORA-29547: Java system class not available: string
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.
ORA-29548: Java system class reported: string
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.
ORA-29549: class string.string 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.
ORA-29550: Java session state cleared
Cause: The Java state in the current session became inconsistent and was cleared.
Action: No action required.
ORA-29551: could not convert string 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.
ORA-29552: verification warning: string
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.
ORA-29553: class in use: string.string
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.
ORA-29554: 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.
ORA-29555: 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.
ORA-29556: 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.
ORA-29557: Java system class string cannot be modified
Cause: A command was attempted that would have modified a Java system class.
Action: No action required.
ORA-29558: 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).
ORA-29655: 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.
ORA-29656: 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.
ORA-29657: 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.
ORA-29658: EXTERNAL NAME clause is not compatible with its supertype
16-22 Oracle Database Error Messages
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.
ORA-29659: SQLJ Object Type validation failed to get default connection
Cause: Unable to connect using the JDBC default connection.
Action: No action required.
ORA-29660: 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.
ORA-29661: 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.
ORA-29662: 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.
ORA-29663: 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.
ORA-29664: 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.
ORA-29665: Java thread deadlock detected
Cause: The Java VM has detected a thread deadlock.
Action: Modify the Java program to avoid the deadlock condition.
ORA-29701: unable to connect to Cluster Manager
Cause: Connect to CM failed or timed out.
Action: Verify that the CM was started. If the CM was not started, start it and then
retry the database startup. If the CM died or is not responding, check the Oracle
and CM trace files for errors.
ORA-29702: error occurred in Cluster Group Service operation
Cause: An unexpected error occurred while performing a CGS operation.
Action: Verify that the LMON process is still active. Also, check the Oracle LMON
trace files for errors.
ORA-29703: 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.
ORA-29704: 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.
ORA-29705: ACTIVE_INSTANCE_COUNT is string 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.
ORA-29706: incorrect value string 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.
ORA-29707: inconsistent value string for initialization parameter string 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.
ORA-29740: evicted by member string, group incarnation string
Cause: This member was evicted from the group by another member of the
cluster database for one of several reasons, which may include a communications
error in the cluster, failure to issue a heartbeat to the control file, etc.
Action: Check the trace files of other active instances in the cluster group for
indications of errors that caused a reconfiguration.
ORA-29741: 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
ORA-29746: 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.
16-24 Oracle Database Error Messages
Action: Check the log file of the Cluster Synchronization Service daemon to verify
the state of the service.
ORA-29760: 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
ORA-29800: invalid name for operator
Cause: The name specified for the operator is incorrect.
Action: Specify a correct name for the operator.
ORA-29801: missing RETURN keyword
Cause: The RETURN keyword has not been specified.
Action: Specify the RETURN keyword or check the SQL statement.
ORA-29802: missing CONTEXT keyword
Cause: The CONTEXT keyword has not been specified.
Action: Specify the CONTEXT keyword or check the SQL statement.
ORA-29803: missing ANCILLARY keyword
Cause: The ANCILLARY keyword has not been specified.
Action: Specify the ANCILLARY keyword or check the SQL statement.
ORA-29804: missing DATA keyword
Cause: The DATA keyword has not been specified.
Action: Specify the DATA keyword or check the SQL statement.
ORA-29805: missing COLUMN keyword
Cause: Keyword COLUMN is expected .
Action: Either specify the COLUMN keyword or specify another option.
ORA-29806: 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.
ORA-29807: 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.
ORA-29808: 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.
ORA-29809: 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.
ORA-29810: 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.
ORA-29811: missing STATISTICS keyword
Cause: This is not a valid option with the ASSOCIATE command.
Action: Specify STATISTICS keyword after the ASSOCIATE command.
ORA-29812: 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.
ORA-29813: 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.
ORA-29814: 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.
ORA-29815: 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.
ORA-29816: 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.
ORA-29817: 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.
ORA-29818: column name not properly specified
Cause: Name of the column should contain the table and the column name.
Action: Specify a valid column name.
ORA-29819: 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.
ORA-29820: 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.
ORA-29821: specified primary operator does not exist
Cause: The specified primary operator does not exist.
16-26 Oracle Database Error Messages
Action: Check the primary operator and the signature specified.
ORA-29822: 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.
ORA-29823: 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.
ORA-29824: operator is invalid
Cause: The operator is invalid.
Action: Drop and recreate the operator.
ORA-29825: 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.
ORA-29826: keyword FOR is missing
Cause: FOR keyword must be provided with Create Indextype statement.
Action: Use FOR keyword and provide relevant operator information.
ORA-29827: 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.
ORA-29828: 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.
ORA-29829: 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.
ORA-29830: 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.
ORA-29831: 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.
ORA-29832: 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.
ORA-29833: 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.
ORA-29834: 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.
ORA-29835: 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).
ORA-29836: 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.
ORA-29837: 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.
ORA-29838: 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 .
ORA-29839: failed to validate implementation type
Cause: Implementation type cannot be compiled.
Action: Try to compile the implementation type.
ORA-29840: 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.
ORA-29841: 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
ORA-29842: option not supported with the version string 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.
ORA-29843: indextype should support atleast one operator
Cause: User attempted to drop all the operators from the indextype
16-28 Oracle Database Error Messages
Action: Do not drop all the operators from the indextype
ORA-29844: 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
ORA-29845: indextype does not support local domain index on string 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
ORA-29846: cannot create a local domain index on a string 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
ORA-29847: 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
ORA-29848: 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.
ORA-29849: 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.
ORA-29850: 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.
ORA-29851: 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.
ORA-29852: 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.
ORA-29853: 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.
ORA-29854: 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.
ORA-29855: 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.
ORA-29856: 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.
ORA-29857: 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.
ORA-29858: 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.
ORA-29859: 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.
ORA-29860: 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.
ORA-29861: 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.
ORA-29862: 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.
ORA-29863: 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.
16-30 Oracle Database Error Messages
ORA-29864: 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.
ORA-29865: indextype is invalid
Cause: The indextype is invalid.
Action: Drop and recreate the indextype.
ORA-29866: 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.
ORA-29867: 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.
ORA-29868: 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.
ORA-29869: 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.
ORA-29870: 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.
ORA-29871: 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.
ORA-29872: 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.
ORA-29873: 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.
ORA-29874: 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.
ORA-29875: 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.
ORA-29876: 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.
ORA-29877: 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.
ORA-29878: 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.
ORA-29879: 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.
ORA-29880: 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.
ORA-29881: failed to validate indextype
Cause: Indextype cannot be compiled.
Action: Try to compile the indextype which is referenced by the domain index.
ORA-29882: 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.
ORA-29883: 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.
ORA-29884: 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.
ORA-29885: domain index is defined on the column to be modified
16-32 Oracle Database Error Messages
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.
ORA-29886: feature not supported for domain indexes
Cause: Feature is not supported for domain indexes.
Action: No action required.
ORA-29887: 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.
ORA-29888: 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]
ORA-29890: 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]
ORA-29892: 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.
ORA-29893: 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.
ORA-29894: 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.
ORA-29895: 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
ORA-29896: Length of PARAMETER string longer than string characters
Cause: An attempt was made to specify a parameter value that is longer than the
allowed maximum.
Action: Reduce the parameter value length.
ORA-29900: 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.
ORA-29901: 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.
ORA-29902: 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.
ORA-29903: 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.
ORA-29904: 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.
ORA-29905: method string does not exist in type string.string
Cause: A required method with the required signature does not exist in the
specified type.
Action: Add the required method to the type.
ORA-29906: indextype string.string does not exist
Cause: The indextype does not exist.
Action: Create the indextype.
ORA-29907: 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.
ORA-29908: 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.
ORA-29909: 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.
ORA-29910: invalid callback operation
Cause: Encountered an invalid callback operation.
Action: Ensure that all the callbacks executed from callouts are valid in the
statement context.
ORA-29911: null scan context returned by ODCIIndexStart() routine
16-34 Oracle Database Error Messages
Cause: The ODCIIndexStart() routine returned a null scan context
Action: Ensure that the ODCIIndexStart() routine returns a non-null scan context.
ORA-29913: error in executing string callout
Cause: The execution of the specified callout caused an error.
Action: Examine the error messages take appropriate action.
ORA-29914: 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.
ORA-29915: cannot select FOR UPDATE from collection operand
Cause: Collection operands cannot be updated
Action: Remove FOR UPDATE clause
ORA-29917: 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
ORA-29918: 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
ORA-29925: cannot execute string
Cause: The specified function does not exist or does not have an appropriate
signature.
Action: Implement the function with the appropriate signature.
ORA-29926: 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.
ORA-29927: error in executing the ODCIStatsCollect / ODCIStatsDelete routine
Cause: The ODCIStatsCollect / ODCIStatsDelete function is causing an error.
Action: Check the ODCIStatsCollect / ODCIStatsDelete function.
ORA-29928: duplicate default selectivity specified
Cause: The keyword DEFAULT SELECTIVITY can only be specified once.
Action: Remove the duplicate keyword.
ORA-29929: missing SCAN Keyword
Cause: The scan context is not specified.
Action: Supply the SCAN keyword.
ORA-29930: 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.
ORA-29931: 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.
ORA-29932: 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.
ORA-29933: 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.
ORA-29934: 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
ORA-29935: missing FROM keyword
Cause: The keyword FROM is missing.
Action: Specify the FROM keyword or check the SQL statement.
ORA-29936: 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
ORA-29950: 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.
ORA-29951: 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.
ORA-29952: 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.
16-36 Oracle Database Error Messages
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.
ORA-29953: 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.
ORA-29954: 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.
ORA-29955: 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.
ORA-29956: 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.
ORA-29957: cannot create a function-based domain index on a string 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.
ORA-29958: 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.
ORA-29959: error in the execution of the string 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
ORA-29960: line string, string
Cause: The ODCIIndex DDL routine has put a warning message into table
SYS.ODCI_WARNINGS$
Action: Check the warning message
ORA-29961: 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
ORA-29962: 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.
ORA-29963: missing BINDING keyword
Cause: Keyword BINDING is expected .
Action: Specify the BINDING keyword or check the SQL statement.
ORA-29964: 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.
ORA-29965: 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.
ORA-29966: 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.
ORA-29967: 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.
ORA-29968: No primary operator bindings found for ancillary binding #string
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.
ORA-29970: Specified registration id does not exist
Cause: An incorrect regid value was passed to dbms_chnf procedure.
Action: pass the correct regid value.
ORA-29971: 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.
ORA-29972: 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
ORA-29973: Unsupported query or operation during change notification registration
16-38 Oracle Database Error Messages
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.
ORA-29974: Internal event for PL/SQL debugging
Cause: None
Action: none
ORA-29975: 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.
ORA-30000: 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.
ORA-30001: 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.
ORA-30002: SYS_CONNECT_BY_PATH function is not allowed here
Cause: SYS_CONNECT_BY_PATH function is called at places other than select
list.
Action: Remove calls to SYS_CONNECT_BY_PATH function at places other than
select list.
ORA-30005: 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.
ORA-30006: resource busy; acquire with WAIT timeout expired
Cause: The requested resource is busy.
Action: Retry the operation later.
ORA-30011: Error simulated: psite=string, ptype=string
Cause: error generated for testing purposes.
Action: None.
ORA-30012: undo tablespace “string” 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.
ORA-30013: undo tablespace “string” 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.
ORA-30014: 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.
ORA-30015: previously offlined undo tablespace “string” 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.
ORA-30016: undo tablespace “string” 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.
ORA-30017: segment “string” is not supported in string 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.
ORA-30018: Create Rollback Segment failed, USN string 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.
ORA-30019: 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.
ORA-30020: UNDO_MANAGEMENT=AUTO needs Compatibility string or greater
Cause: Auto undo management mode not allowed in specified compatibility
release
Action: restart instance in correct compatibility release
ORA-30021: 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
ORA-30022: Cannot create segments in undo tablespace
Cause: Cannot create segments in undo tablespace
Action: Check the tablespace name and reissue command
ORA-30023: 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
ORA-30024: Invalid specification for CREATE UNDO TABLESPACE
16-40 Oracle Database Error Messages
Cause: You have specified an clause that should not used with CREATE UNDO
TABLESPACE
Action: Drop the clause from the command and reissue it.
ORA-30025: DROP segment “string” (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.
ORA-30026: Undo tablespace “string” has unexpired undo with string(sec) left,
Undo_Retention=string(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
ORA-30027: Undo quota violation – failed to get string (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.
ORA-30028: Automatic Undo Management event for NTP testing
Cause: test events for internal use only
Action: none.
ORA-30029: 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.
ORA-30030: suppress resumable related error message
Cause: none
Action: This event is to be used if the errors 30031 and 30032 wish to be
suppressed.
ORA-30031: 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
ORA-30032: 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.
ORA-30033: 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
ORA-30034: 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
ORA-30035: 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
ORA-30036: unable to extend segment by string in undo tablespace “string”
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.
ORA-30037: 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
ORA-30038: 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.
ORA-30039: 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
ORA-30040: Undo tablespace is offline
Cause: Cannot operate on an offlined undo tablespace
Action: Online the undo tablespace and redo the operation
ORA-30041: 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
ORA-30042: 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
ORA-30043: Invalid value “string” 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.
ORA-30044: “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.
ORA-30045: No undo tablespace name specified
16-42 Oracle Database Error Messages
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.
ORA-30046: Undo tablespace string 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.
ORA-30047: Internal event for kti tracing
Cause: internal use only
Action: none
ORA-30048: Internal event for IMU auto-tuning
Cause: internal use only
Action: none
ORA-30049: Internal event for TA enq tracing
Cause: internal use only
Action: none
ORA-30051: VERSIONS clause not allowed here
Cause: A VERSIONS clause was specified when it was not allowed.
Action: Do not use the VERSIONS clause
ORA-30052: 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.
ORA-30053: 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.
ORA-30054: 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.
ORA-30055: NULL snapshot expression not allowed here
Cause: The snapshot expression is NULL.
Action: Specify a non-NULL snapshot expression.
ORA-30060: Internal event for RECO tracing
Cause: internal use only
Action: none
ORA-30061: Internal Event for Savepoint Tracing
Cause: internal use only
Action: none
ORA-30062: Test support for ktulat latch recovery
Cause: internal use only
Action: none.
ORA-30063: Internal Event to Test NTP
Cause: none
Action: none
ORA-30064: Test support for two phase read only optimization
Cause: internal use only
Action: none.
ORA-30065: test support for row dependencies
Cause: internal use only
Action: none.
ORA-30066: test support – drop rollback segment wait
Cause: internal use only
Action: none.
ORA-30067: Internal Event to turn on nested debugging info
Cause: none
Action: none.
ORA-30068: Internal Event to turn on nested
Cause: none
Action: none.
ORA-30069: Auto Undo-Management Error simulation – test site = string
Cause: test events for internal use only.
Action: none.
ORA-30071: 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: none
ORA-30072: 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: none
ORA-30073: 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
16-44 Oracle Database Error Messages
ORA-30074: 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.
ORA-30075: 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.
ORA-30076: invalid extract field for extract source
Cause: The extract source does not contain the specified extract field.
Action: none
ORA-30077: illegal casting between specified datetime types
Cause: Cannot cast between the specified datetime types.
Action: none
ORA-30078: 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.
ORA-30079: 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.
ORA-30081: invalid data type for datetime/interval arithmetic
Cause: The data types of the operands are not valid for datetime/interval
arithmetic.
Action: none
ORA-30082: 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.
ORA-30083: 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.
ORA-30084: 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: none
ORA-30085: syntax error was found in overlaps predicate
Cause: A syntax error was found during parsing an overlaps predicate.
Action: Correct the syntax.
ORA-30086: 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.
ORA-30087: Adding two datetime values is not allowed
Cause: An attempt was made to add two datetime values.
Action: This addition is not allowed.
ORA-30088: 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.
ORA-30089: missing or invalid
Cause: A (YEAR, MONTH, DAY, HOUR, MINUTE, SECOND) is
expected but not found, or a specified the in an
is more significant than its .
Action: none
ORA-30100: internal error [number]
Cause: An internal error has occurred.
Action: Contact Oracle Worldwide Support and report the error.
ORA-30101: unknown parameter name “string”
Cause: You have misspelled the parameter name.
Action: Spell the parameter name correctly.
ORA-30102: “string” is not in the legal range for “string”
Cause: The value of the parameter is not within the legal range.
Action: Refer to the manual for the allowable values for this parameter.
ORA-30103: “string” contains an illegal integer radix for “string”
Cause: An illegal integer radix specification was found.
Action: Only “d”, “h”, “D”, and “H” may be used as radix specifications.
ORA-30104: “string” is not a legal integer for “string”
Cause: The value is not a valid integer.
Action: Specify only valid integers for this parameter.
ORA-30105: “string” is not a legal boolean for “string”
Cause: The value is not a valid boolean.
16-46 Oracle Database Error Messages
Action: Refer to the manual for allowable boolean values.
ORA-30106: reserved for future use
Cause: None.
Action: None.
ORA-30107: parameter name abbreviation “string” is not unique
Cause: The abbreviation given was not unique.
Action: Use a longer abbreviation to make the parameter name unique.
ORA-30108: invalid positional parameter value “string”
Cause: An invalid positional parameter value has been entered.
Action: Remove the invalid positional parameter.
ORA-30109: could not open parameter file “string”
Cause: The parameter file does not exist.
Action: Create an appropriate parameter file.
ORA-30110: syntax error at “string”
Cause: A syntax error was detected.
Action: Change the input so that the correct syntax is used.
ORA-30111: no closing quote for value “string”
Cause: A quoted string was begun but not finished.
Action: Put a closing quote in the proper location.
ORA-30112: multiple values not allowed for parameter “string”
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.
ORA-30113: error when processing file “string”
Cause: A problem occurred when processing this file.
Action: Examine the additional error messages and correct the problem.
ORA-30114: 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.
ORA-30115: 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.
ORA-30116: syntax error at “string” following “string”
Cause: A syntax error was detected.
Action: Change the input so that the correct syntax is used.
ORA-30117: syntax error at “string” at the start of input
Cause: A syntax error was detected.
Action: Change the input so that the correct syntax is used.
ORA-30118: syntax error at “string” at the end of input
Cause: A syntax error was detected.
Action: Change the input so that the correct syntax is used.
ORA-30119: unable to obtain a valid value for “string”
Cause: No valid value was obtained for this parameter.
Action: Rerun the application and enter a valid value.
ORA-30120: “string” is not a legal oracle number for “string”
Cause: The value is not a valid oracle number.
Action: Refer to the manual for allowable oracle number values.
ORA-30121: “string” is not an allowable value for “string”
Cause: The value is not a legal value for this parameter.
Action: Refer to the manual for allowable values.
ORA-30122: value “string” for “string” must be between “number” and “number”
Cause: The value of the parameter is not within the legal range.
Action: Specify a value that is within the legal range.
ORA-30129: invalid function argument received
Cause: A function received an invalid argument
Action: Check function calls, make sure correct arguments are being passed.
ORA-30130: invalid parameter key type received
Cause: A function received an invalid parameter key type
Action: Check parameter key types in function calls
ORA-30131: 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
ORA-30132: invalid key index supplied
Cause: The key index specified was not within bounds
Action: Change key index to ensure it lies within bounds
ORA-30133: reserved for future use
Cause: None.
Action: None.
ORA-30134: reserved for future use
Cause: None.
Action: None.
ORA-30135: 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.
ORA-30150: Invalid argument passed to OCIFile function
16-48 Oracle Database Error Messages
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.
ORA-30151: 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.
ORA-30152: File does not exist
Cause: The OCIFile function requires the file to exist, but it does not.
Action: Make sure that the file exists.
ORA-30153: 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.
ORA-30154: 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.
ORA-30155: 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.
ORA-30156: Out of disk space
Cause: The disks associated with the underlying file system are full.
Action: Create more disk space.
ORA-30157: 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.
ORA-30158: 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.
ORA-30159: 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.
ORA-30160: 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.
ORA-30161: A system error occurred during the OCIFile function call
Cause: A system error occured while executing the OCIFile function.
Action: Depend on the error.
ORA-30162: 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.
ORA-30163: The thread safety initialization failed
Cause: The call to SlgInit failed in OCIFileInit.
Action: Contact support
ORA-30175: 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.
ORA-30176: 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.
ORA-30177: 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.
ORA-30178: duplicate flag used in a format specification
Cause: There is a duplicate flag in a format specification.
Action: Remove the duplicate flag.
ORA-30179: 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.
ORA-30180: argument index is too large
Cause: An argument index exceeds actual number of arguments supplied.
Action: Fix format string or pass additional arguments.
ORA-30181: integer in argument index is not immediately followed by )
Cause: Missing closing parenthesis in argument index.
Action: Fix the format specification.
ORA-30182: invalid precision specifier
Cause: Period in format specification not followed by valid format.
Action: Replace the invalid precision specifier with a valid one.
ORA-30183: invalid field width specifier
Cause: Invalid field width supplied.
Action: Replace the invalid field width with a valid one.
ORA-30184: argument type not compatible with a format code
16-50 Oracle Database Error Messages
Cause: Bad argument type given for a format code.
Action: Make format and arguments be compatible.
ORA-30185: 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.
ORA-30186: “\” 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
ORA-30187: reserved for future use
Cause: None.
Action: None.
ORA-30188: reserved for future use
Cause: None.
Action: None.
ORA-30189: reserved for future use
Cause: None.
Action: None.
ORA-30190: reserved for future use
Cause: None.
Action: None.
ORA-30191: missing argument list
Cause: No argument list supplied.
Action: Modify the argument list to have at least OCIFormatEnd in it.
ORA-30192: reserved for future use
Cause: None.
Action: None.
ORA-30193: reserved for future use
Cause: None.
Action: None.
ORA-30194: reserved for future use
Cause: None.
Action: None.
ORA-30195: reserved for future use
Cause: None.
Action: None.
ORA-30196: reserved for future use
Cause: None.
Action: None.
ORA-30197: reserved for future use
Cause: None.
Action: None.
ORA-30198: reserved for future use
Cause: None.
Action: None.
ORA-30199: reserved for future use
Cause: None.
Action: None.
ORA-30200: Wrong NLS item was passed into OCINlsGetInfo()
Cause: The item is not supported NLS item
Action: Correct the item number passed to OCINlsGetInfo().
ORA-30201: 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
ORA-30202: NULL pointer to OCIMsgh was passed to OCIMsg function
Cause: The NULL pointer was passed.
Action: Check your value of OCIMsgh pointer.
ORA-30203: Cannot open mesage file
Cause: The message may not exist in your system.
Action: Check your message for the given product and facility.
ORA-30204: 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.
ORA-30205: invalid Character set
Cause: The specified character set is invalid.
Action: Check if the character set ID is valid.
ORA-30331: summary does not exist
Cause: A non-existant summary name was specified.
Action: Check the spelling of the summary name.
ORA-30332: 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.
ORA-30333: dimension does not exist
Cause: The dimension named in a dimension DDL statment does not exist.
Action: Check the spelling of the dimension name.
ORA-30334: illegal dimension level name
16-52 Oracle Database Error Messages
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.
ORA-30335: 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.
Action: none
ORA-30336: 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.
ORA-30337: 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.
ORA-30338: 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.
ORA-30339: 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.
ORA-30340: 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.
ORA-30341: 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.
ORA-30342: 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.
ORA-30343: 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.
ORA-30344: 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.
ORA-30345: circular dimension hierarchy
Cause: A circularity was found the dimension hierarchy.
Action: Check the hierarchy for a level name that occurs more than once.
ORA-30346: 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.
ORA-30347: 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.
ORA-30348: 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.
ORA-30349: 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.
ORA-30350: 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.
ORA-30351: 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.
ORA-30352: 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
16-54 Oracle Database Error Messages
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.
ORA-30353: expression not supported for query rewrite
Cause: The select clause referenced UID, USER, ROWNUM, SYSDATE,
CURRENT_TIMESTAMP, MAXVALUE, a sequence number, a bind variable,
correlation variable, a set result,a trigger return variable, a parallel table queue
column, collection iterator, etc.
Action: Remove the offending expression or disable the REWRITE option on the
materialized view.
ORA-30354: 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.
ORA-30355: 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.
ORA-30356: 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.
ORA-30357: 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.
ORA-30358: summary and materialized view are not in same schema
Cause: An internal Oracle error occured.
Action: Report the problem through your normal support channels.
ORA-30359: 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.
ORA-30360: 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.
ORA-30361: unrecognized string type
Cause: An internal Oracle error occured.
Action: Report the problem through your normal support channels.
ORA-30362: dimension column cannot be a sequence
Cause: The dimension statement referenced a column that is a sequence.
Action: Remove the reference to the sequence.
ORA-30363: 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.
ORA-30364: 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.
ORA-30365: 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.
ORA-30366: 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.
ORA-30367: 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.
ORA-30368: 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.
16-56 Oracle Database Error Messages
ORA-30369: 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.
ORA-30370: 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.
ORA-30371: 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.
ORA-30372: 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.
ORA-30373: 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.
ORA-30374: materialized view is already fresh
Cause: If the materialized view is fresh, ORACLE ignores the ALTER
MATERIALIZED VIEW RELY FRESH command, and issues this error
message.
Action: None
ORA-30375: materialized view cannot be considered fresh
Cause: If the materialized view is invalid or unusable, it cannot be considered
fresh with the ALTER MATERIALIZED VIEW CONSIDER FRESH
command.
Action: None
ORA-30376: 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
ORA-30377: table string.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.
ORA-30378: 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.
ORA-30379: 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
ORA-30380: 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
ORA-30381: 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.
ORA-30382: DROP MATERIALIZED VIEW string.string 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
ORA-30383: 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.
ORA-30384: 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.
ORA-30385: specified attribute relationship (“string” determines “string”) exists
Cause: The specified attribute relationship has already been declared in one of the
attribute clauses
Action: Remove the duplicate attribute relationship
ORA-30386: 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
ORA-30387: invalid rewrite mode for REWRITE_EQUIVALENCE API
16-58 Oracle Database Error Messages
Cause: The specified rewrite mode is not supported by REWRITE_
EQUIVALENCE API
Action: Verify the rewrite mode is supported by REWRITE_EQUIVALENCE API
ORA-30388: name of the rewrite equivalence is not specified
Cause: The name of the rewrite equivalence is NULL
Action: Input a valid rewrite equivalence name
ORA-30389: 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
ORA-30390: 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
ORA-30391: the specified rewrite equivalence does not exist
Cause: the specified rewrite equivalence does not exist
Action: Verify the rewrite equivalence has been created
ORA-30392: 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.
ORA-30393: 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
ORA-30394: 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
ORA-30395: dimension options require the COMPATIBLE parameter to be string or
greater
Cause: The following materialized view options require 10.1 or higher
compatibility setting:
o dimension attribute extended level syntax ATTRIBUTE LEVEL
DETERMINES Action: Shut down and restart with an appropriate compatibility setting.
ORA-30396: rewrite equivalence procedures require the COMPATIBLE parameter to
be string or greater
Cause: Query rewrite equivalence APIs require 10.1 or higher compatibility
setting:
o DBMS_ADVANCED_REWRITE.DECLARE_REWRITE_EQUIVALENCE
o DBMS_ADVANCED_REWRITE.ALTER_REWRITE_EQUIVALENCE
o DBMS_ADVANCED_REWRITE.DROP_REWRITE_EQUIVALENCE
o DBMS_ADVANCED_REWRITE.VALIDATE_REWRITE_EQUIVALENCE
Action: Shut down and restart with an appropriate compatibility setting. //
ORA-30397: 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.
ORA-30398: 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.
ORA-30399: 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.
ORA-30400: 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.
ORA-30401: 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.
ORA-30430: 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
16-60 Oracle Database Error Messages
ORA-30431: refresh method must be ANY or INCREMENTAL or FORCE_FULL, not
string
Cause: An invalid refresh method was specified
Action: Verify that the refresh method is one of “ANY” or “INCREMENTAL” or
“FORCE_FULL”
ORA-30432: summary “string.string” is in INVALID state
Cause: The summary is in INVALID state and cannot be refreshed
Action: none
ORA-30433: “string.string” is not a summary
Cause: There is no such summary, therefore it cannot be refreshed
Action: Verify the correct name of the summary
ORA-30434: refresh method must be one of FC?AN, not “string”
Cause: An invalid refresh method was specified
Action: Verify that the refresh method is one of “FC?AN”
ORA-30435: 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
ORA-30436: unable to open named pipe “string”
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
ORA-30437: 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
ORA-30438: unable to access named pipe “string”
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
ORA-30439: refresh of “string.string” failed because of string
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.
ORA-30440: 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
ORA-30442: can not find the definition for filter string
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
ORA-30443: definition for filter string”s item string 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
ORA-30444: rewrite terminated by the sql analyzer
Cause: The sql analyzer terminates the rewrite process
Action: This is an internal error. Notify ORACLE technical support
ORA-30445: 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
ORA-30446: 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.
ORA-30447: internal data for run number string 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
ORA-30448: 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
ORA-30449: syntax error in parameter string
Cause: The syntax for the specified parameter is incorrect
Action: Check ORACLE documentation for the correct syntax
ORA-30450: refresh_after_errors was TRUE; The following MVs could not be
refreshed: string
Cause: One or more errors occurred during a refresh of multiple summaries.
16-62 Oracle Database Error Messages
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
ORA-30451: internal error
Cause: An internal error was detected by the summary refresh subsystem, and
aborted the refresh operation
Action: Notify ORACLE support.
ORA-30452: 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.
ORA-30453: 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.
ORA-30454: 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.
ORA-30455: 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.
ORA-30456: “string.string” 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.
ORA-30457: “string.string” 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.
ORA-30458: “string.string” cannot be refreshed because the refresh mask is string
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.
ORA-30459: “string.string” 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.
ORA-30460: “string.string” 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.
ORA-30461: “string.string” 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.
ORA-30462: unsupported operator: string
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.
ORA-30463: “string” 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
ORA-30464: 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
ORA-30465: supplied run_id is not valid: string
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
ORA-30466: can not find the specified workload string
Cause: The specified workload_id is not valid
Action: Use a valid workload_id or DBMS_OLAP.WORKLOAD_ALL
ORA-30467: internal data for filter number string 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
ORA-30475: feature not enabled: string
16-64 Oracle Database Error Messages
Cause: The specified feature is not enabled.
Action: Do not attempt to use this feature.
ORA-30476: 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.
ORA-30477: 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.
ORA-30478: Specified dimension does not exist
Cause: the specified dimension to be verified does not exist
Action: Check the spelling of the dimension name
ORA-30479: Summary Advisor error string
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.
ORA-30483: 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: none
ORA-30484: missing window specification for this function
Cause: All window functions should be followed by window specification, like
() OVER ()
Action: none
ORA-30485: 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: none
ORA-30486: invalid window aggregation group in the window specification
Cause: If the window specification is specified using RANGE option and there are
multiple ORDER BY expressions, then the aggregation group cannot contain any
expression (It can only have CURRENT ROW, UNBOUNDED PRECEDING, or
UNBOUNDED FOLLOWING). First end point (bound) cannot be UNBOUNDED
FOLLOWING and second end point cannot be UNBOUNDED PRECEDING. If the
first end point is CURRENT ROW, then second end point can only be CURRENT
ROW or /UNBOUNDED FOLLOWING. If the first end point is
FOLLOWING, then second end point can only be /UNBOUNDED
FOLLOWING.
Action: none
ORA-30487: ORDER BY not allowed here
Cause: DISTINCT functions and RATIO_TO_REPORT cannot have an ORDER BY
Action: none
ORA-30488: 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: none
ORA-30489: 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.
ORA-30490: 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
ORA-30493: 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].
ORA-30500: 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.
ORA-30501: 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.
ORA-30502: 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.
ORA-30503: 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.
ORA-30504: system triggers cannot have a FOR EACH ROW clause
16-66 Oracle Database Error Messages
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.
ORA-30505: 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.
ORA-30506: 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.
ORA-30507: normal triggers cannot be based on a schema or a database
Cause: An attempt was made to base a normal trigger on a schema or a database,
but normal triggers can be based only on tables or views.
Action: Make sure the type of the trigger is compatible with the base object.
ORA-30508: 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.
ORA-30509: 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.
ORA-30510: 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.
ORA-30511: invalid DDL operation in system triggers
Cause: An attempt was made to perform an invalid DDL operation in a system
trigger. Most DDL operations currently are not supported in system triggers. The
only currently supported DDL operations are table operations and
ALTER?COMPILE operations.
Action: Remove invalid DDL operations in system triggers.
ORA-30512: cannot modify string.string 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.
ORA-30513: 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.
ORA-30514: 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
ORA-30515: 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.
ORA-30516: 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.
ORA-30550: 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
ORA-30551: 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
ORA-30552: 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
ORA-30553: 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.
ORA-30554: function-based index string.string 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.
16-68 Oracle Database Error Messages
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
ORA-30555: 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.
ORA-30556: functional index is defined on the column to be modified
Cause: An ALTER TABLE MODIFY COLUMN was issued on a column on which
a functional index exists.
Action: Drop the functional index before attempting to modify the column.
ORA-30557: 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
ORA-30558: internal error [string] in function based index
Cause: This is an internal error.
Action: Contact Worldwide support with the exact error text.
ORA-30563: outer join operator (+) not allowed in select-list
Cause: An attempt was made to reference (+) in select-list.
Action: Do not use the operator in select-list.
ORA-30564: 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
ORA-30565: 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
ORA-30566: 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
ORA-30567: 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.
ORA-30568: cannot drop log group – nonexistent log group
Cause: The specified in alter table drop log group is incorrect
or nonexistent.
Action: Reenter the statement using the correct log group name.
ORA-30569: data type of given column is not supported in a log group
Cause: An attempt was made to include a column with one of these unsupported
data types: LONG, VARRAY, nested table, object, LOB, FILE, or REF in a log
group.
Action: Change the column data type or remove the log group. Then retry the
operation.
ORA-30570: 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.
ORA-30571: invalid SEGMENT SPACE MANAGEMENT clause
Cause: An invalid option appears for SEGMENT SPACE MANAGEMENT clause.
Action: Specify one of the valid options: AUTO, MANUAL.
ORA-30572: 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.
ORA-30573: 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.
ORA-30574: 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.
ORA-30575: ConText Option not installed
Cause: Oracle executable doesn”t have ConText Option linked in
Action: get the correct version of Oracle
ORA-30576: ConText Option dictionary loading error
Cause: ConText dictionary tables may be corrupted
Action: not a user error
ORA-30625: 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.
16-70 Oracle Database Error Messages
ORA-30645: 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.
ORA-30646: 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.
ORA-30647: error retrieving access parameters for external table string.string
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.
ORA-30649: missing DIRECTORY keyword
Cause: DEFAULT DIRECTORY clause missing or incorrect.
Action: Provide the DEFAULT DIRECTORY.
ORA-30653: reject limit reached
Cause: the reject limit has been reached.
Action: Either cleanse the data, or increase the reject limit.
ORA-30654: missing DEFAULT keyword
Cause: DEFAULT DIRECTORY clause not specified or incorrect.
Action: Provide the DEFAULT DIRECTORY.
ORA-30655: cannot select FOR UPDATE from external organized table
Cause: A select for update on an external table was attempted.
Action: Don”t do it!
ORA-30656: 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.
ORA-30657: 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!
ORA-30658: 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!
ORA-30659: too many locations specified for external table
Cause: An attempt was made to create an External Organized table with more
than the maximum allowable (32767) locations specified.
Action: Don”t do that, use fewer location clauses. Either consider concatenating
the input files, or, creating two external tables with the input files split between
them.
ORA-30676: 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.
ORA-30677: 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.
ORA-30678: 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.
ORA-30679: 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.
ORA-30680: 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.
ORA-30681: 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.
ORA-30682: 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.
ORA-30683: 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
16-72 Oracle Database Error Messages
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.
ORA-30685: 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.
ORA-30686: 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.
ORA-30687: session terminated by debugger
Cause: Your program”s execution has been stopped by the debugger. This can
occur because of an explicit request to do so sent by the debugger, or because the
debugger disconnected without first telling Oracle to let your program continue to
run after the disconnection. To stop your program completely, Oracle needs to
fully terminate the process.
Action: This is in response to a debugger request; it is not an error. No action
required.
ORA-30688: 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.
ORA-30689: 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.
ORA-30690: 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.
ORA-30691: 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.
ORA-30695: 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.
ORA-30725: JDWP-based debugging is not yet available
Cause: This feature is not yet available for use.
Action: Please wait for a future release.
ORA-30726: 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.
ORA-30727: 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.
ORA-30728: 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.
ORA-30729: 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.
ORA-30730: 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.
ORA-30731: 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.
ORA-30732: 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.
ORA-30733: 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.
ORA-30734: cannot specify scope constraint on ref column with rowid
16-74 Oracle Database Error Messages
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.
ORA-30735: 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.
ORA-30736: 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.
ORA-30737: 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.
ORA-30738: object “string” does not exist in schema “string”
Cause: The specified object does not exist.
Action: Ensure that the specified object exists and retry the operation.
ORA-30739: 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.
ORA-30740: 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.
ORA-30741: WITH HIERARCHY OPTION can be specified only for SELECT
privilege
Cause: The user tried to specify WITH HIERARCHY OPTION for a privilege
other than SELECT privilege.
Action: Ensure that the HIERARCHY OPTION is specified only with the SELECT
privilege
ORA-30742: cannot grant SELECT privilege WITH HIERARCHY OPTION on this
object
Cause: The user tried to grant SELECT privilege WITH HIERARCHY OPTION on
an object that is not one of the following : object table of non final type, object view
of non final type.
Action: Ensure that the SELECT privilege WITH HIERARCHY OPTION is
granted on a valid object.
ORA-30743: “string” is not an object view
Cause: The specified object is not an object view.
Action: Specify an object view and retry the operation.
ORA-30744: “string” is not an object table
Cause: The specified object is not an object table.
Action: Specify an object table and retry the operation.
ORA-30745: error occured while trying to add column “string” in table “string”
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.
ORA-30746: error occured while trying to drop column “string” in table “string”
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.
ORA-30747: cannot create substitutable tables or columns of non final type
string.string
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.
ORA-30748: column string already enabled to store objects of type string.string
Cause: The user is trying to enable a column to store instances of a type for which
it is already enabled.
Action: None
ORA-30749: column string not enabled to store objects of type string.string
Cause: The user is trying to disable a column from storing instances of a type for
which it is already enabled.
Action: None
ORA-30750: cannot enable column string to store objects of type string.string
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.
ORA-30751: cannot disable column string from storing objects of type string.string
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.
ORA-30752: column or table string is not substitutable
Cause: The user is performing an operation that is not allowed on non
substitutable column or table.
Action: None.
16-76 Oracle Database Error Messages
ORA-30753: column or table string is substitutable
Cause: The user is performing an operation that is not allowed on substitutable
column or table.
Action: None.
ORA-30754: column or table string 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
ORA-30755: 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.
ORA-30756: 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.
ORA-30757: 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.
ORA-30765: 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.
ORA-30766: 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.
ORA-30767: 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: none
ORA-30768: 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.
ORA-30770: 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.
ORA-30771: Cannot add more than one referential constraint on REF column
“string”
Cause: Multiple referential constraints were specified for a single REF column.
Action: Remove the additional referential constraints and retry the operation.
ORA-30772: 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.
ORA-30926: 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.
ORA-30927: 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.
ORA-30928: 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.
ORA-30929: 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.
ORA-30930: 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.
ORA-30931: Element “string” 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
ORA-30932: Reference node “string” not contained in specified parent node “string”
Cause: When using a reference node, it must have the specified parent node
Action: Use a node in the specified parent as the reference
16-78 Oracle Database Error Messages
ORA-30933: Element “string” may not appear at this point within parent “string”
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
ORA-30934: “string” (string node) cannot be inserted in parent “string” (string 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
ORA-30935: XML maxoccurs value (string) 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.
ORA-30936: Maximum number (string) of “string” 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.
ORA-30937: No schema definition for “string” (namespace “string”) in parent
“string”
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.
ORA-30938: No prefix defined for namespace “string” (particle string)
Cause: An XML namespace mapping (xmlns:=) must
be defined for each particle (element or attribute) stored in an schema-constrained
XMLType document.
Action: Add an xmlns attribute definition (attribute name=”xmlns:prefix” and
value=”namespace URL”) to the current XMLType document. The safest place to
add this attribute is in the root node of the document to ensure that the mapping
will be in scope.
ORA-30939: Order violation: Element “string” may not follow element “string”
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
ORA-30940: Cannot resolve prefix “string” for QName node “string”
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
ORA-30941: Cannot specify empty URI for non-default namespace “string”
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
ORA-30942: XML Schema Evolution error for schema “string” table string column
“string”
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
ORA-30943: XML Schema “string” is dependent on XML schema “string”
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.
ORA-30944: Error during rollback for XML schema “string” table string column
“string”
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
ORA-30945: Could not create mapping table “string”
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
ORA-30946: 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. ///// End of XML Schema
Evolution errors (30942 to 30950 reserved)
ORA-30951: Element or attribute at Xpath string 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.
ORA-30952: 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.
16-80 Oracle Database Error Messages
Action: Specify values for both elements http2-port and http2-protocol, AND set
different values for http-port and http2-port.
ORA-30953: XML minoccurs value (string) 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. ////// Errors 30955 to
30989 reserved for XML Index
ORA-30956: invalid option for XML Index
Cause: Unexpected error.
Action: File a bug.
ORA-30957: 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.
ORA-30959: 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.
ORA-30960: The entity is neither an XPATH nor a NAMESPACE.
Cause: The given string had invalid syntax.
Action: Check the syntax for XPATH and NAMESPACE.
ORA-30961: internal SQL statement is too long
Cause: unexpected internal error
Action: File a bug and provide the test case.
ORA-30962: inconsistent ODCI input arguments
Cause: unexpected internal error
Action: File a bug and provide the test case.
ORA-30963: 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.
ORA-30964: 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.
ORA-30965: 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.
ORA-30966: error detected in the XML Index layer
Cause: Unexpected error.
Action: File a bug.
ORA-30967: 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.
ORA-30968: invalid XPATH or NAMESPACE option for XML Index
Cause: An attempt was made to use an unsupported option.
Action: Use the appropriate option.
ORA-30969: invalid syntax for PARAMETERS
Cause: An attempt was made to specify an invalid option.
Action: Check and use valid options.
ORA-30970: option not supported for XML Index
Cause: An attempt was made to specify an invalid option.
Action: Check and use valid options.
ORA-30971: 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.
ORA-30972: invalid ALTER INDEX option for XML Index
Cause: An attempt was made to use an unsupported option.
Action: Use the appropriate option.
ORA-30973: invalid Path Table option for XML Index
Cause: An attempt was made to use an unsupported option.
Action: Use the appropriate option.
ORA-30974: invalid Path Id Index option for XML Index
Cause: An attempt was made to use an unsupported option.
Action: Use the appropriate option.
ORA-30975: invalid Order Key Index option for XML Index
Cause: An attempt was made to use an unsupported option.
Action: Use the appropriate option.
ORA-30976: invalid Parent Order Key Index option for XML Index
Cause: An attempt was made to use an unsupported option.
Action: Use the appropriate option.
ORA-30977: invalid Value Index option for XML Index
Cause: An attempt was made to use an unsupported option.
Action: Use the appropriate option.
ORA-30978: 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.
ORA-30979: Partitioned XML Index not yet supported.
Cause: An attempt was made to create a partitioned XML Index.
16-82 Oracle Database Error Messages
Action: Do not attempt to create partitioned XML Index.
ORA-30980: Invalid Input.
Cause: The input to the function is not valid.
Action: Make sure the input is valid (both syntactically as well as semantically).
///// End of XML Index (30955 to 30989 reserved)
ORA-30990: insufficient privileges to change owner of resource string
Cause: An attempt was made to change the field of an XML DB
resource without sufficient privileges to do so.
Action: Switch to SYS before performing the ownership change, or have the
intended recipient of the resource perform the transfer.
ORA-30991: 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.
ORA-31000: Resource “string” 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
ORA-31001: Invalid resource handle or path name “string”
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.
ORA-31002: Path name string 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.
ORA-31003: Parent string already contains child entry string
Cause: An attempt was made to insert a duplicate child into the XDB hierarchical
resolver.
Action: Insert a unique name into the container.
ORA-31004: Length string of the BLOB in XDB$H_INDEX is below the minimum
string
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.
ORA-31005: Path name length string exceeds maximum length string
Cause: The length of a path name passed to the XDB hierarchical resolver
exceeded the maximum length.
Action: Choose a shorter path name.
ORA-31006: Path name segment length string exceeds maximum length string
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.
ORA-31007: Attempted to delete non-empty container string/string
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.
ORA-31009: Access denied for property string
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
ORA-31010: XML element index string exceeds maximum insertion index string
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.
ORA-31011: 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.
ORA-31012: 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.
ORA-31013: Invalid XPATH expression
Cause: XPATH expression passed to the function is invalid.
Action: Check the xpath expression for possible syntax errors.
ORA-31014: 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.
ORA-31015: 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.
ORA-31016: 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.
ORA-31017: Error generating unique OID for XML document
Cause: An error occurred while generating a globally unique OID for storing an
XML document.
Action: none
ORA-31018: Error deleting XML document
16-84 Oracle Database Error Messages
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.
ORA-31019: Recursive deletion snapshot too old for string/string
Cause: Changes were made to the structure of a directory while it was being
recursively deleted.
Action: Try deleting the directory again.
ORA-31020: The operation is not allowed, Reason: string
Cause: The operation attempted is not allowed
Action: See reason and change to a valid operation.
ORA-31021: Element definition not found
Cause: The element definition was not found.
Action: Supply the definition for the element or use a defined element.
ORA-31022: Element not found
Cause: The element was not found.
Action: Make sure the specified element exists.
ORA-31023: Index size error
Cause: The index is greater than the allowed value.
Action: Make sure the index is less than allowed value.
ORA-31025: 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.
ORA-31027: Path name or handle string 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.
ORA-31028: Resource metadata length string exceeded maximum length string
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.
ORA-31029: 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.
ORA-31030: 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.
ORA-31033: Requested number of XML children string exceeds maximum string
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.
ORA-31035: Could not bind locked resource to path string/string
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.
ORA-31037: Invalid XML attribute name string
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.
ORA-31038: Invalid string value: “string”
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.
ORA-31039: XML namespace length string exceeds maximum string
Cause: The length of the disk-formatted XML namespace exceeded the maximum.
Action: Keep XML namespace declarations below the maximum length.
ORA-31040: Property string: XML type (string) not compatible with internal memory
type (string)
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.
ORA-31041: Property string: Memory type (string) not compatible with database
type (string)
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.
ORA-31042: Too many properties in type “string”
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.
ORA-31043: Element “string” not globally defined in schema “string”
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.
ORA-31044: Top-level prefix length string exceeds maximum string
16-86 Oracle Database Error Messages
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.
ORA-31045: Cannot store more than string 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.
ORA-31046: 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
ORA-31047: Could not retrieve resource data at path string
Cause: An error occurred while retrieving the contents and/or metadata of a
resource.
Action: Contact Oracle customer support.
ORA-31048: 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.
ORA-31050: 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.
ORA-31051: 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.
ORA-31052: 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.
ORA-31053: 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
ORA-31054: The string 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
ORA-31055: 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
ORA-31056: The document being inserted does not conform to string
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
ORA-31057: 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
ORA-31058: cannot modify read-only XOBs
Cause: Read-Only XOBs cannot be modified.
Action: Use only read operations on such a XOB.
ORA-31059: 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.
ORA-31060: Resource at path string 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.
ORA-31062: 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.
ORA-31064: Cannot instantiate abstract element or property [string]
Cause: An attempt was made instantiate an abstract element.
Action: Use only read operations on such elements.
ORA-31065: Cannot modify read-only property [string]
Cause: An attempt was made to modify an immutable XML node.
Action: Use only read operations on such properties.
ORA-31066: Insertion of string into string 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.
ORA-31067: 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.
16-88 Oracle Database Error Messages
ORA-31068: updateXML expected data format [string] instead of [string]
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.
ORA-31069: 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.
ORA-31070: Invalid database user ID string
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.
ORA-31071: Invalid database username or GUID string
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.
ORA-31072: 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.
ORA-31073: 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.
ORA-31074: XML comment length string exceeds maximum string
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
ORA-31075: invalid string declaration in XML Schema
Cause: The XML schema contains an invalid declaration identified by the
message.
Action: Fix the identified error and try again.
ORA-31076: required attribute “string” not specified
Cause: The XML schema does not specify a required attribute.
Action: Specify a value for the required attribute.
ORA-31077: invalid attribute “string” specified
Cause: The XML schema specifies an invalid attribute.
Action: Remove specification of the invalid attribute.
ORA-31078: 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.
ORA-31079: unable to resolve reference to string “string”
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.
ORA-31080: type not specified for attribute or element “string”
Cause: The identified attribute or element does not have a type.
Action: Make sure that every attribute and element has a valid type specification.
ORA-31081: 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.
ORA-31082: invalid attribute “string” specified in declaration of “string”
Cause: The XML schema specifies an invalid attribute.
Action: Remove specification of the invalid attribute.
ORA-31083: error while creating SQL type “string”.”string”
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.
ORA-31084: error while creating table “string”.”string” for element “string”
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.
ORA-31085: schema “string” 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.
ORA-31086: insufficient privileges to register schema “string”
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.
ORA-31087: insufficient privileges to delete schema “string”
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.
ORA-31088: object “string”.”string” depends on the schema
Cause: An attempt was made to delete a schema which has dependent objects.
16-90 Oracle Database Error Messages
Action: Either drop the dependent objects prior to deleting the schema or use the
CASCADE or FORCE options.
ORA-31089: schema “string” does not target namespace “string”
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.
ORA-31090: invalid database schema name “string”
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.
ORA-31091: 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.
ORA-31092: invalid SQL name “string”
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.
ORA-31093: null or invalid value specified for parameter : string
Cause: The argument value passed for the given parameter is null or invalid.
Action: Make sure that all the input argument values are valid.
ORA-31094: incompatible SQL type “string” for attribute or element “string”
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.
ORA-31095: cannot generate string : “string.string” 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.
ORA-31096: validation failed for schema
Cause: The XML Schema could not be validated.
Action: Make sure that the SQLType and other datatype mapping is valid.
ORA-31097: 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.
ORA-31099: XDB Security Internal Error
Cause: An XDB Security internal error has occurred.
Action: Contact Oracle Support. ////// 31100 – 31110 reserved for WebDAV
compliant resource locks
ORA-31100: XDB Locking Internal Error
Cause: An XDB Locking Internal error has occurred.
Action: Contact Oracle Support.
ORA-31101: Token “string” not given while locking resource “string”
Cause: Locking attempted on resource when the pricipal already owns a lock
given by the token above.
Action: Reattempt the lock with the token.
ORA-31102: 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.
ORA-31103: 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.
ORA-31104: Cannot find lock with token “string” on “string” for unlock
Cause: The lock may have been unlock or it may have expired.
Action: No action needed. Unlock already successful.
ORA-31105: User does not own lock “string”
Cause: The lock to be unlocked is not owned by the user.
Action: none
ORA-31107: Action failed as resource “string” is locked by name lock
Cause: Lock requests cause the whole request URI to be locked
Action: Supply lock token or unlock the lock
ORA-31108: Action failed as resource string is locked
Cause: Delete/Rename failed because of an existing lock
Action: Do lockdiscovery to find the lock and delete it.
ORA-31109: Action failed as parent resource string is locked
Cause: Delete/Rename failed because of an lock on parent resource
Action: Do lockdiscovery to find the lock and delete it.
ORA-31110: Action failed as resource string 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.
ORA-31111: table string cannot be hierarchically enabled
Cause: Trigger _xdb_pitrigger already exists
16-92 Oracle Database Error Messages
Action: Delete all rows in the hierarchical index and then rebuild it.
ORA-31112: fail to string for string 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.
ORA-31113: 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.
ORA-31114: 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.
ORA-31115: XDB configuration error: string
Cause: An error related to XDB configuration has occurred.
Action: Make sure the configuration resource contains valid data.
ORA-31116: Tablespace not specified correctly
Cause: XDB cannot be moved to the specified tablespace.
Action: Specify a valid tablespace.
ORA-31117: Table “string”.”string” 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
ORA-31121: The string operator can not be FALSE
Cause: The value of the operator that is specified is FALSE
Action: Specify an operator that evaluates to TRUE
ORA-31122: The string operator has incorrect RHS value
Cause: The right hand side value that has been specified for the operator does not
evaluate to TRUE
Action: Specify value on the right hand side that evaluate to TRUE ////// 31151
– 31189 reserved for XML Schema Compiler
ORA-31151: Cyclic definition encountered for string: “string”
Cause: The schema definition for this type has cycles.
Action: Remove cyclic definition and re-compile schema.
ORA-31153: 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.
ORA-31154: invalid XML document
Cause: The XML document is invalid with respect to its XML Schema.
Action: Fix the errors identified and try again.
ORA-31155: attribute string 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.
ORA-31157: 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.
ORA-31158: schema “string” 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.
ORA-31159: 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
ORA-31160: max substitution group size string exceeded by “string” (string) for head
element “string” (string)
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.
ORA-31161: element or attribute “string” 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
ORA-31162: element or attribute “string” 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
ORA-31163: element or attribute “string” has invalid attribute value “string” (should
be “string”)
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
ORA-31164: cannot load object-relational XML attribute using direct path
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.
16-94 Oracle Database Error Messages
Action: Perform the load with conventional path mode.
ORA-31165: cannot load object-relational XML attribute using direct path
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.
ORA-31167: 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.
ORA-31168: 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.
ORA-31180: 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.
ORA-31181: 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.
ORA-31182: 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.
ORA-31183: Node type string 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.
ORA-31185: 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.
ORA-31186: 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.
ORA-31187: Cannot Add Node “string” (type=”string”) to Simple Type Node “string”
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.
ORA-31190: Resource string 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.
ORA-31191: Resource string 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
ORA-31192: Resource string 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
ORA-31193: This versioning feature isn”t supported for resource string
Cause: Either one of the following is the Cause:
– Container cannot be put under version-controlled.
Action: Avoid using these features.
ORA-31194: Resource string is already deleted
Cause: Access a version-controlled resource that is already deleted.
Action: Remove the cyclic definitions in the type and retry compilation.
ORA-31195: XML node “string” (type=string) 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.
ORA-31196: XML nodes over string 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.
ORA-31197: Error in processing file string
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
16-96 Oracle Database Error Messages
Action: Ensure that the specified file is correct. Look at the next error on the stack
and take appropriate action.
ORA-31198: 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
ORA-31199: Warning in processing file string
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. ////////////////////////// DBMS_
LDAP & OiD messages
ORA-31201: DBMS_LDAP: generic error: string
Cause: There has been an error in the DBMS_LDAP package.
Action: Please report the error number and description to Oracle Support.
ORA-31202: DBMS_LDAP: LDAP client/server error: string
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.
ORA-31203: 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.
ORA-31204: 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.
ORA-31205: 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.
ORA-31206: 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.
ORA-31207: 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.
ORA-31208: 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.
ORA-31209: 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.
ORA-31210: 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.
ORA-31211: 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.
ORA-31212: 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.
ORA-31213: 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.
ORA-31214: 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.
ORA-31215: 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.
ORA-31216: 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.
ORA-31217: 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.
16-98 Oracle Database Error Messages
ORA-31218: 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.
ORA-31219: 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.
ORA-31220: 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.
ORA-31221: 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.
ORA-31222: 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.
ORA-31223: DBMS_LDAP: cannot open more than string LDAP server connections
Cause: An attempt was made to open more than the maximum allowed LDAP
server connections.
Action: Free unused connections.
ORA-31224: 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.
ORA-31225: 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.
ORA-31226: 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.
ORA-31227: 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.
ORA-31228: 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.
ORA-31229: 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.
ORA-31230: 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.
ORA-31231: 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.
ORA-31232: 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.
ORA-31398: 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.
ORA-31399: Cannot contact LDAP server string at port number
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
ORA-31401: change source string 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.
ORA-31402: unrecognized parameter string
Cause: Unrecognized parameter was detected.
Action: Check for too many parameters in the call.
ORA-31403: change table string already contains a column string
16-100 Oracle Database Error Messages
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.
ORA-31404: 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.
ORA-31405: cannot make changes while change set string 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.
ORA-31406: change source string 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.
ORA-31407: 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.
ORA-31408: 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.
ORA-31409: 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.
ORA-31410: change set string 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.
ORA-31411: change set string 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
ORA-31412: change set string 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.
ORA-31413: change set string 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.
ORA-31414: 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.
ORA-31415: change set string 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.
ORA-31416: 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.
ORA-31417: column list contains control column string
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.
ORA-31418: source schema string 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.
ORA-31419: source table string 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.
ORA-31420: 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.
16-102 Oracle Database Error Messages
Action: Make sure that job queue processes are enabled and are currently
running. If this does not solve the problem, contact Oracle.
ORA-31421: 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.
ORA-31422: owner schema string 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.
ORA-31423: change table string does not contain column string
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.
ORA-31424: 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.
ORA-31425: 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.
ORA-31426: 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.
ORA-31427: publication string 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.
ORA-31428: 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.
ORA-31429: 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.
ORA-31430: 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.
ORA-31431: 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.
ORA-31432: 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.
ORA-31433: 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.
ORA-31434: 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.
ORA-31435: 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.
ORA-31436: duplicate change source string
Cause: A change source by the specifed name already exists.
Action: Recreate the change source with a unique name.
ORA-31437: duplicate change set string
Cause: A change set by the specified name already exists.
Action: Recreate the change set with a unique name.
ORA-31438: duplicate change table string
Cause: A change table by the specified name already exists.
Action: Recreate the change table with a unique name.
ORA-31439: subscription is already active
Cause: The subscription is already active.
Action: Check name and retry.
ORA-31440: change set string 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.
16-104 Oracle Database Error Messages
ORA-31441: 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.
ORA-31442: operation timed out while acquiring lock on string
Cause: CDC attempted to acquire a lock on the resource, but the operation timed
out.
Action: Retry the operation later.
ORA-31443: deadlock detected while acquiring lock on string
Cause: CDC attempted to acquire a lock on the resource, but encountered a
deadlock.
Action: Contact Oracle corporation
ORA-31444: parameter error while acquiring lock on string
Cause: CDC attempted to acquire a lock on the resource, but encountered a
problem passing parameters to the lock manager.
Action: Contact Oracle corporation
ORA-31445: invalid lock handle while acquiring lock on string
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
ORA-31446: this session does not own the lock handle for string
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
ORA-31447: 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.
ORA-31448: 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.
ORA-31449: 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.
ORA-31450: 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.
ORA-31451: invalid value string 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.
ORA-31452: invalid value string 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.
ORA-31453: invalid value string 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.
ORA-31454: invalid value string 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.
ORA-31455: 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.
ORA-31456: 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.
ORA-31457: 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.
ORA-31458: an internal error occurred
Cause: This is an internal error.
Action: Contact Oracle Worldwide Customer Support and report the error.
ORA-31459: 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.
ORA-31460: logfile location string 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
16-106 Oracle Database Error Messages
ORA-31461: logfile location string contains no files that match pattern string
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
ORA-31462: internal error while accessing metadata
Cause: An unexpected internal error occurred while CDC was accessing its
internal Metadata.
Action: Contact Oracle Corporation
ORA-31463: logfile location string 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
ORA-31464: 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
ORA-31465: 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.
ORA-31466: 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.
ORA-31467: 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.
ORA-31468: 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”.
ORA-31469: cannot enable Change Data Capture for change set string
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.
ORA-31470: 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.
ORA-31471: 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.
ORA-31472: Importing Change Data Capture version string.string 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.
ORA-31475: 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
ORA-31476: 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.
ORA-31477: 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
16-108 Oracle Database Error Messages
which Change Data Capture attempted to detach the LogMiner session as part of
recovery. The detach session also failed
Action: Contact Oracle Corporation
ORA-31478: 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
ORA-31479: 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
ORA-31480: 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.
ORA-31481: change source string 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.
ORA-31482: 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.
ORA-31483: cannot have spaces in the parameter string
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.
ORA-31484: 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.
ORA-31485: 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.
ORA-31486: cannot support column string 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.
ORA-31487: 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.
ORA-31488: cannot support change set string 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.
ORA-31490: 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
ORA-31491: 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
ORA-31492: 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
ORA-31493: 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
ORA-31494: 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
ORA-31495: error in synchronous change table on “string”.”string”
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.
16-110 Oracle Database Error Messages
ORA-31496: 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.
ORA-31497: 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.
ORA-31498: 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.
ORA-31499: null value specified for required parameter string
Cause: A null value was specified for a parameter that requires an explicit value.
Action: Correct call to supply a value for this parameter.
ORA-31500: change source string 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.
ORA-31501: change source string 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.
ORA-31502: 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.
ORA-31503: 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.
ORA-31504: 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.
ORA-31505: 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.
ORA-31506: duplicate subscription name string
Cause: A subscription by the specifed name already exists.
Action: Recreate the subscription with a unique name.
ORA-31507: %s parameter value longer than maximum length string
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.
ORA-31508: 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.
ORA-31509: 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.
ORA-31510: 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$
ORA-31511: 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
ORA-31512: 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
ORA-31513: 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.
ORA-31514: change set string disabled due to capture error
Cause: This change set has encountered a capture error and was disabled.
16-112 Oracle Database Error Messages
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.
ORA-31515: CDC change source string 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.
ORA-31516: CDC change set string 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.
ORA-31517: CDC change table string.string 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.
ORA-31518: change column string already exists in CDC change table string.string
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.
ORA-31519: CDC subscription string 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.
ORA-31520: CDC subscription string already subscribes to publication ID string
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.
ORA-31521: CDC subscription string already subscribes to publication ID string
column string
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.
ORA-31522: could not find Streams object string for CDC change set string
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.
ORA-31523: could not find change source string for CDC change set string
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.
ORA-31524: could not find change set string for CDC change table string.string
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.
ORA-31525: could not find column string in CDC change table string.string
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.
ORA-31526: could not find source table string.string for CDC change table
string.string
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.
ORA-31527: could not find source column string for CDC change table string.string
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.
ORA-31528: could not find change set string for CDC subscription string
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.
ORA-31529: could not find publication for CDC subscriber view string.string
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.
16-114 Oracle Database Error Messages
ORA-31530: could not find published column string for CDC subscriber view
string.string
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.
ORA-31531: could not find column string in CDC subscriber view string.string
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.
ORA-31532: cannot enable change source string
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.
ORA-31533: only one change set (string) 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.
ORA-31534: Change Data Capture string publisher string 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.
ORA-31535: cannot support change source string 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.
ORA-31536: cannot support encrypted column string 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
ORA-31600: invalid input value string for parameter string in function string
Cause: A NULL or invalid value was supplied for the parameter.
Action: Correct the input value and try the call again.
ORA-31601: Function string cannot be called now that fetch has begun.
Cause: The function was called after the first call to FETCH_xxx.
Action: Correct the program.
ORA-31602: parameter string value “string” in function string inconsistent with
string
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
ORA-31603: object “string” of type string not found in schema “string”
Cause: The specified object was not found in the database.
Action: Correct the object specification and try the call again.
ORA-31604: invalid string parameter “string” for object type string in function string
Cause: The specified parameter value is not valid for this object type.
Action: Correct the parameter and try the call again.
ORA-31605: the following was returned from string in routine string: LPX-number:
string
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.
ORA-31606: XML context number 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.
ORA-31607: function string 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.
ORA-31608: specified object of type string not found
Cause: The specified object was not found in the database.
Action: Correct the object specification and try the call again.
ORA-31609: error loading file “string” from file system directory “string”
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.
ORA-31610: 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.
ORA-31612: Allocation of process descriptor failed.
16-116 Oracle Database Error Messages
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.
ORA-31613: Master process string 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.
ORA-31614: routine string received this error from string: string
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.
ORA-31615: routine string received this error: string
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.
ORA-31616: unable to write to dump file “string”
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.
ORA-31617: unable to open dump file “string” 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.
ORA-31618: dump file size too small
Cause: The value specified for the FILESIZE parameter or the VOLUMESIZE
parameter was too small to hold the header information for the export file, plus
any data.
Action: Increase the value of the FILESIZE or VOLUMESIZE parameter.
ORA-31619: invalid dump file “string”
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.
ORA-31620: file or device “string” cannot be specified for string operation
Cause: There was an inappropriate use of file or device in the current operation.
Action: Correct operation or job setup.
ORA-31621: 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.
ORA-31622: ORACLE server does not have string access to the specified file
Cause: An attempt was made to read or write files within protected directories.
Action: Correct the file/directory permissions and try the call again.
ORA-31623: 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.
ORA-31624: 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.
ORA-31625: Schema string 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.
ORA-31626: 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.
ORA-31627: 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.
ORA-31628: 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.
ORA-31629: unable to allocate additional memory
Cause: A dynamic memory allocation failure occurred.
Action: Report this problem to a database administrator.
ORA-31630: a job name is required to attach a job for user string
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.
16-118 Oracle Database Error Messages
ORA-31631: 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.
ORA-31632: master table “string.string” 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.
ORA-31633: unable to create master table “string.string”
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.
ORA-31634: 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).
ORA-31635: 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.
ORA-31636: session is already attached to job string for user string
Cause: The session executing the attach is already attached to the specified job.
Action: Select a different job or create a new session.
ORA-31637: cannot create job string for user string
Cause: Unable to create or restart a job. Refer to any following or prior error
messages for clarification.
Action: Eliminate the problems indicated.
ORA-31638: cannot attach to job string for user string
Cause: Unable to attach a job to a session. Refer to any following or prior error
messages for clarification.
Action: Eliminate the problems indicated.
ORA-31639: 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.
ORA-31640: unable to open dump file “string” 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.
ORA-31641: unable to create dump file “string”
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.
ORA-31642: the following SQL statement fails: string
Cause: An internal error was generated from package DBMS_METADATA.
Action: Contact Oracle Customer Support and report the error.
ORA-31643: unable to close dump file “string”
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.
ORA-31644: unable to position to block number string in dump file “string”
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.
ORA-31645: unable to read from dump file “string”
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.
ORA-31648: Timeout before master process string 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.
ORA-31649: Master process string 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.
16-120 Oracle Database Error Messages
Correct the error, if possible, and try the operation again. If the error occurs again,
contact Oracle Customer Support and report the error.
ORA-31650: 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.
ORA-31651: 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.
ORA-31652: 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.
ORA-31653: 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.
ORA-31654: 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.
ORA-31655: 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.
ORA-31656: 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.
ORA-31657: 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.
ORA-31658: 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.
ORA-31659: 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.
ORA-31660: 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.
ORA-31661: 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.
ORA-31662: 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.
ORA-31663: 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.
ORA-31664: 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.
ORA-31665: 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.
ORA-31666: Master process string 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.
ORA-31667: 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.
ORA-31668: Timeout before worker process string finished initialization.
Cause: The worker process whose name is listed started up but did not finish its
initialization within the allowed time limit.
16-122 Oracle Database Error Messages
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.
ORA-31669: Worker process string 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.
ORA-31670: 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.
ORA-31671: Worker process string 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.
ORA-31672: Worker process string 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.
ORA-31673: 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.
ORA-31674: 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.
ORA-31675: 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.
ORA-31676: illegal value for number of workers, string
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.
ORA-31679: Table data object string has long columns, and longs can not be
loaded/unloaded using a network link
Cause: Table data objects that contain long columns can not be selected over a
network link.
Action: Export this table to a file and then import the same table from the file.
ORA-31686: 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.
ORA-31687: error creating worker process string with worker id string
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.
ORA-31688: Worker process string 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.
ORA-31689: illegal value for base worker id, string
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.
ORA-31690: Process name buffer size must be specified and must be greater than 0.
16-124 Oracle Database Error Messages
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.
ORA-31691: The worker received message number string from the MCP, which is
invalid.
Cause: Bad code.
Action: Fix mcp code and reissue export/import command.
ORA-31692: The following SQL statement failed trying to insert a row into the
Master table: string
Cause: Bad code.
Action: Fix code and reissue export/import command.
ORA-31693: Table data object string failed to load/unload and is being skipped due
to error: string
Cause: Table failed to load or unload due to some error.
Action: Check load/unload error, correct problem and retry command.
ORA-31694: master table string failed to load/unload
Cause: Master table failed to load or unload.
Action: Check load/unload error, correct problem and retry command.
ORA-31695: Inconsistent master table on restart. The following SQL statement
returned string identical objects. string
Cause: Master table on restart has the same object inserted multiple times.
Action: Restart not possible, reissue original export/import.
ORA-31696: unable to export/import string using client specified string method
Cause: Table attributes prevent client specified method for exporting or importing
data.
Action: Use default “DATA_ACCESS” parameter value.
ORA-31697: aborting operation at process order number string
Cause: User asked for it.
Action: Don”t ask for it.
ORA-31698: 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.
ORA-31700: Very long string supplied for AUDIT_SYSLOG_LEVEL parameter
Cause: Very long string supplied for AUDIT_SYSLOG_LEVEL in init.ora
Action: Use a valid facility.level such as “local1.notice” as described in syslog”s
manual pages
ORA-31901: the current operation was cancelled by the user
Cause: The user requested to cancel current operation
Action: No action is necessary
ORA-32001: write to SPFILE requested but no SPFILE specified at startup
Cause: An alter system command or an internal self tuning mechanism requested
a write to the SPFILE but no SPFILE was used to startup the instance
Action: Create an SPFILE and re-start the instance using the SPFILE.
ORA-32002: 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
ORA-32003: error occured processing parameter “string”
Cause: An error occured while parsing the parameter file.
Action: See additional errors to determine the root cause.
ORA-32004: obsolete and/or deprecated parameter(s) specified
Cause: One or more obsolete and/or parameters were specified in the SPFILE or
the PFILE on the server side.
Action: See alert log for a list of parameters that are obsolete. or deprecated.
Remove them from the SPFILE or the server side PFILE.
ORA-32005: error while parsing size specification [string]
Cause: The value specified for an alter operation on a size parameter is not valid
Action: Correct the value and retry the operation
ORA-32006: %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.
ORA-32007: internal
Cause: A parameter error occured.
Action: Call Oracle support.
ORA-32008: error while processing parameter update at instance string
Cause: An error occured while processing a parameter on a remote instance.
Action: See accompanying error messages.
ORA-32009: cannot reset the memory value for instance string from instance string
Cause: Memory resets of local parameters are only allowed.
Action: Retry the query for the local instance if needed.
ORA-32010: 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.
ORA-32011: 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.
16-126 Oracle Database Error Messages
Action: Specify a different SPFILE name
ORA-32012: failure in processing system parameters from restored SPFILE
Cause: Failure during processing of parameters from restored SPFILE
Action: Further diagnostic information should be in the error stack.
ORA-32013: 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.
ORA-32014: error processing parameter “string” 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.
ORA-32015: 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.
ORA-32016: parameter “string” cannot be updated in SPFILE
Cause: Database is mounted.
Action: Unmount the database to update the parameter in the SPFILE
ORA-32017: failure in updating SPFILE
Cause: A failure occured while updating the SPFILE.
Action: See associated errors.
ORA-32018: 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
ORA-32019: 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.
ORA-32020: 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=*
ORA-32021: parameter value longer than string 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.
ORA-32022: parameter value longer than string characters
Cause: An attempt was made to alter a parameter value but the combined length
of all the parameter values was more than the allowed maximum.
Action: Reduce the parameter value length and retry the command. For the
DISPATCHERS parameter, use listener aliases to reduce value length.
ORA-32024: invalid directory specified for audit_file_dest parameter
Cause: Either the directory does not exist or it is not writable.
Action: Retry the command by specifying a valid directory or granting
appropriate directory permissions.
ORA-32025: %s.string 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.
ORA-32026: %s.string has fewer columns compared to string 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.
ORA-32027: There is no string column with the matching type in string.string.
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.
ORA-32028: 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
ORA-32031: 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.
ORA-32032: 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
ORA-32033: unsupported column aliasing
Cause: column aliasing in WITH clause is not supported yet
Action: specify aliasing in defintion subquery and retry
ORA-32034: unsupported use of WITH clause
Cause: Inproper use of WITH clause because one of the following two reasons:
1. nesting of WITH clause within WITH clause not supported yet
2. For a set query, WITH clause can”t be specified for a branch.
3. WITH clause can”t sepecified within parentheses.
16-128 Oracle Database Error Messages
Action: correct query and retry
ORA-32035: 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
ORA-32036: unsupported case for inlining of query name in WITH clause
Cause: There is at least one query name which is inlined more than once because
it”s definition query is too simple and references another query name. This is
currently unsupported yet.
Action: remove such query name and retry
ORA-32037: 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
ORA-32050: %s operation failed
Cause: A mapping operation failed.
Action: Check FMON trace files for errors.
ORA-32051: 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.
ORA-32052: failed to start mapping service
Cause: The mapping service failed to start properly.
Action: Check FMON trace files for errors.
ORA-32053: 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.
ORA-32054: lost communication with FMPUTL process
Cause: Lost communication with mapping utility.
Action: Check FMON and FMPUTL trace files for errors.
ORA-32055: invalid file type
Cause: Invalid file type used when mapping files.
Action: Specify one of expected file types.
ORA-32056: invalid number of extents
Cause: Invalid number of extents used for map operation.
Action: Specify a non-negative number of extents.
ORA-32057: invalid lock mode
Cause: An invalid mode was used for a lock operation.
Action: Specify one of expected lock modes.
ORA-32058: operation restricted to SYSDBA users
Cause: Operation requires SYSDBA priviliges.
Action: Connect to the database as SYSDBA.
ORA-32059: deadlock detected on mapping structures
Cause: Mapping structures already locked by the same session.
Action: Unlock mapping structures before proceeding with current operation.
ORA-32060: channel failure
Cause: Channel failure between foreground and background process.
Action: Check foreground trace files for errors.
ORA-32100: 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
ORA-32101: 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
ORA-32102: 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.
ORA-32103: 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.
ORA-32104: 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.
ORA-32106: 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.
ORA-32107: internal OCI memory allocation failure
Cause: Memory could not be allocated from an OCI heap.
Action: Increase the process memory size.
ORA-32108: 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.
ORA-32109: invalid column or parameter position
Cause: An invalid column or parameter position is specified.
Action: Specify a valid column or position number.
16-130 Oracle Database Error Messages
ORA-32110: Connection not specified
Cause: A null connection was passed.
Action: Pass a valid, non-null connection.
ORA-32113: Null object passed
Cause: Null object was passed.
Action: Pass a non-null object.
ORA-32114: 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.
ORA-32116: 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.
ORA-32117: 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.
ORA-32118: 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.
ORA-32120: 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.
ORA-32121: 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.
ORA-32123: 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.
ORA-32124: Illegal attribute passed
Cause: The attribute passed is not applicable for the described object.
Action: Pass a valid attribute.
ORA-32125: 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.
ORA-32126: 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.
ORA-32127: 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.
ORA-32128: 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.
ORA-32129: 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.
ORA-32130: 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.
ORA-32131: 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.
ORA-32132: 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.
ORA-32133: 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.
ORA-32134: Cannot assign LOBs
Cause: An open stream exists on the target LOB.
Action: Close the stream on the target LOB before assigning the LOBs.
ORA-32135: Cannot assign FILEs
Cause: An open stream exists on the target FILE.
Action: Close the stream on the target FILE before assigning the FILEs.
ORA-32136: Cannot perform operation on an invalid stream
Cause: The LOB/FILE from which the stream was obtained had been nullified or
destroyed.
16-132 Oracle Database Error Messages
Action: Use a valid stream.
ORA-32139: 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.
ORA-32140: 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.
ORA-32141: 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.
ORA-32142: 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.
ORA-32143: Environment not specified
Cause: A null environment was passed.
Action: Pass a valid, non-null environment.
ORA-32144: 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.
ORA-32145: 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.
ORA-32146: 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.
ORA-32147: 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.
ORA-32150: 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.
ORA-32151: 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.
ORA-32152: 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.
ORA-32153: 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.
ORA-32154: Anydata context not specified
Cause: A null anydata context was passed.
Action: Pass a valid, non-null anydata context.
ORA-32155: Anydata not specified
Cause: A null anydata was passed.
Action: Pass a valid, non-null anydata.
ORA-32156: Cannot perform operation on stream
Cause: This operation is not applicable to streams obtained from LOBs.
Action: none
ORA-32158: Invalid type passed
Cause: An inapplicable type was passed to this call.
Action: Pass an applicable type.
ORA-32159: Cannot set prefetch options for a null Type
Cause: A null Type name was passed.
Action: Pass an non-null Type name.
ORA-32161: 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
ORA-32162: 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
ORA-32163: 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
ORA-32164: Method called on Invalid Connection type
Cause: A non-XA call made on an XA Connection or XA call made on non-XA
Connection
16-134 Oracle Database Error Messages
Action: Make sure Connection type is OK
ORA-32165: 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
ORA-32166: 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
ORA-32167: 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.
ORA-32168: 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.
ORA-32300: cannot drop a secondary materialized view “string”.”string”
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.
ORA-32301: 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.
ORA-32302: 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.
ORA-32303: 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.
ORA-32304: 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.
ORA-32305: 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.
ORA-32306: 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.
ORA-32307: 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.
ORA-32308: 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.
ORA-32309: object mview type “string”.”string” 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.
ORA-32310: 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.
ORA-32311: 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.
ORA-32312: cannot refresh a secondary materialized view “string”.”string”
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.
ORA-32313: REFRESH FAST of “string”.”string” 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.
16-136 Oracle Database Error Messages
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.
ORA-32314: REFRESH FAST of “string”.”string” 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.
ORA-32315: REFRESH FAST of “string”.”string” 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.
ORA-32316: REFRESH FAST of “string”.”string” 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.
ORA-32317: 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.
ORA-32318: 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.
ORA-32319: Cannot use direct loader log to FAST REFRESH materialized view
“string”.”string”
Cause: The direct loader log might have been dropped
Action: Need to do complete refresh
ORA-32320: REFRESH FAST of “string”.”string” 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.
ORA-32321: REFRESH FAST of “string”.”string” 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.
ORA-32322: PCT refresh of “string”.”string” 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
ORA-32330: invalid operation on online redefinition interim table “string”.”string”
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.
ORA-32331: type “string”.”string” 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.
ORA-32332: cannot refresh materialized view “string”.”string” 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.
ORA-32333: 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
ORA-32334: 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
ORA-32335: 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.
16-138 Oracle Database Error Messages
ORA-32336: cannot use USING NO INDEX to create materialized view
“string”.”string”
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.
ORA-32337: cannot alter materialized view with pending changes refresh on commit
Cause: There are some pending changes in the detail tables
Action: Execute an on-demand refresh on the materialized view to synchronize
the data between the materialized view and the detail tables and then issue an
ALTER MATERIALIZED VIEW statement.
ORA-32338: 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: none
ORA-32339: 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.
ORA-32340: 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.
ORA-32341: The EXPLAIN_MVIEW facility failed to explain the materialized view
“string”.”string”
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.
ORA-32342: 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.
ORA-32343: 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.
ORA-32344: 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.
ORA-32345: fail to refresh the materialized view string.string 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.
ORA-32400: cannot use object id columns from materialized view log on
“string”.”string”
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.
ORA-32401: materialized view log on “string”.”string” 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.
ORA-32403: cannot use new values from mv log on “string”.”string”
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.
ORA-32404: 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.
ORA-32405: 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.
ORA-32406: 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.
ORA-32407: cannot exclude new values when materialized view log includes new
values
16-140 Oracle Database Error Messages
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.
ORA-32408: materialized view log on “string”.”string” already has new values
Cause: The materialized view log on the indicated table already has new values.
Action: No action required.
ORA-32409: materialized view log on “string”.”string” already excludes new values
Cause: The materialized view log on the indicated table already excludes new
values.
Action: No action required.
ORA-32411: 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.
ORA-32412: encrypted column “string” 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.
ORA-32500: Dirname “string” cannot exceed “number” characters
Cause: Path name too long
Action: Use shorter pathname than maximum specified for dirname.
ORA-32501: Writing SGA to file failed
Cause: Underlying OSDs encountered an error
Action: Check additional information. slercerrno contains errno.
ORA-32502: 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.
ORA-32503: Mapping SGA from file failed
Cause: Underlying OSDs encountered an error
Action: Check additional information. slercerrno contains errno.
ORA-32504: expecting one of string, string, string, or string but found string
Cause: illegal value specified for create watchpoint mode
Action: specify one of the expected modes
ORA-32505: too many watchpoints
Cause: too many watchpoints created
Action: increase appropriate initialization parameters
ORA-32506: expecting one of string, string, or string but found string
Cause: invalid arguments provided
Action: provide one of the expected arguments
ORA-32507: expecting string but found string
Cause: invalid arguments to command
Action: provide one of the expected arguments
ORA-32508: no such watchpoint id
Cause: invalid watchpoint id
Action: use oradebug show to list valid watchpoint ids
ORA-32509: watchpoint was already deleted
Cause: trying to delete an already deleted watchpoint
Action: use oradebug show to list valid watchpoint ids
ORA-32510: cannot create watchpoint on unreadable memory
Cause: trying to create watchpoint on invalid address
Action: provide a different valid address
ORA-32511: 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
ORA-32512: type “string” is unknown
Cause: trying to dump an invalid type name
Action: specify a known type
ORA-32514: cannot dump multiple “string” types: structure size is unknown
Cause: trying to dump an invalid address
Action: provide a different valid address
ORA-32515: cannot issue ORADEBUG command; waited number ms for process
string
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.
ORA-32516: cannot wait for ORADEBUG command completion; waited number ms
for process string
Cause: The execution of the ORADEBUG command took longer than the the
timeout value specified.
Action: Increase the timeout value.
ORA-32517: cannot issue ORADEBUG command (waited number ms for process
string); total wait time exceeds number 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.
ORA-32518: cannot wait for ORADEBUG command completion (waited number ms
for process string); total wait time exceeds number ms
16-142 Oracle Database Error Messages
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.
ORA-32550: Replacement occured despite hint to the contrary
Cause: This should never be signalled; it”s internal.
Action: Report to Oracle support.
ORA-32575: 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.
ORA-32576: missing TYPE keyword
Cause: keyword TYPE is missing.
Action: Use TYPE keyword.
ORA-32577: 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.
ORA-32578: 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.
ORA-32579: 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.
ORA-32580: 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.
ORA-32581: 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.
ORA-32582: 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 (+).
ORA-32583: 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.
ORA-32584: missing LOG keyword
Cause: keyword LOG is missing.
Action: Use LOG keyword.
ORA-32585: 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.
ORA-32586: 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.
ORA-32587: Cannot drop nonexistent string supplemental logging
Cause: specified supplemental log attribute does not exist.
Action: None
ORA-32588: supplemental logging attribute string exists
Cause: specified supplemental logging attribute exits.
Action: retry the alter/create ddl after removing this supplemental logging
attribute.
ORA-32589: 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.
ORA-32590: 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.
ORA-32591: connect string too long
Cause: The connect string specified for the database link was more than 2000
characters.
16-144 Oracle Database Error Messages
Action: Specify a connect string less than 2000 chracters.
ORA-32592: 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.
ORA-32593: 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.
ORA-32594: 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.)
ORA-32600: RETENTION and PCTVERSION cannot be used together
Cause: cannot use both RETENTION and PCTVERSION together.
Action: Use either RETENTION or PCTVERSION.
ORA-32601: value for retention cannot be provided
Cause: cannot give a value for Retention Period.
Action: do not provide the value for parameter.
ORA-32602: FREEPOOLS and FREELIST GROUPS cannot be used together
Cause: cannot use both FREEPOOLS and FREELIST GROUPS together.
Action: Use either FREEPOOLS or FREELIST GROUPS.
ORA-32603: 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.
ORA-32604: invalid REBUILD option
Cause: Keyword FREEPOOLS expected after the REBUILD keyword.
Action: User must specify FREEPOOLS keyword.
ORA-32605: invalid REBUILD option
Cause: cannot rebuild freepools while creating table with lob column.
Action: User must not specify REBUILD… in this context.
ORA-32606: missing NAV keyword in MODEL clause
Cause: The NAV keyword was specified where it is expected.
Action: Specify the NAV keyword or check the SQL statement.
ORA-32607: 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.
ORA-32608: 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.
ORA-32609: 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.
ORA-32610: 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.
ORA-32611: 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.
ORA-32612: 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.
ORA-32613: not a MODEL cell
Cause: The operator requires a MODEL cell as operand.
Action: Specify MODEL cell as operand, check SQL statement.
ORA-32614: 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.
ORA-32615: 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.
ORA-32616: 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.
ORA-32617: 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.
ORA-32618: 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.
16-146 Oracle Database Error Messages
ORA-32619: 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.
ORA-32620: illegal subquery within MODEL rules
Cause: A subquery was used illegally within the MODEL rule.
Action: Check the SQL statement and rewrite if necessary.
ORA-32621: illegal aggregation in UNTIL iteration condition
Cause: An aggregate function was used in UNTIL condition.
Action: Check the SQL statement and rewrite if necessary.
ORA-32622: 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.
ORA-32623: 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.
ORA-32624: 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.
ORA-32625: 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.
ORA-32626: 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.
ORA-32627: 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.
ORA-32628: 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.
ORA-32629: 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.
ORA-32630: 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.
ORA-32631: 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.
ORA-32632: 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.
ORA-32633: 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.
ORA-32634: 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.
ORA-32635: not a single cell reference predicate
Cause: A predicate that is not a single cell reference predicate was specified where
a single cell reference predicate was expected. A single cell reference predicate is
either a constant expression or a predicate of the form
Action: Make sure that the predicate is a proper single cell reference. In some
cases, you might have to put explicit type conversion operators (or casts) on the
constant expression.
ORA-32636: 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.
ORA-32637: 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.
ORA-32638: 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.
16-148 Oracle Database Error Messages
ORA-32639: 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.
ORA-32640: 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.
ORA-32641: 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.
ORA-32642: 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.
ORA-32643: 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.
ORA-32644: 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.
ORA-32690: Hash Table Infrastructure ran out of memory
Cause: Not enough memory.
Action: Increase memory.
ORA-32695: HTI: Not enough memory
Cause: Memory is not enough.
Action: Increase memory.
ORA-32696: HTI: No free slot
Cause: There is not enough memory.
Action: Increase memory.
ORA-32700: 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.
ORA-32730: 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
ORA-32731: 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
ORA-32732: Parallel Oradebug session is aborted
Cause: Group reconfiguration is occurring among DIAGs
Action: Issue the command later when group reconfiguration completes
ORA-32733: 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
ORA-32734: 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
ORA-32735: 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
ORA-32736: Hang analysis aborted due to wrong message type
Cause: DIAG received wrong message.
Action: Check DIAG trace files for errors.
ORA-32737: Hang analysis aborted due to failed memory allocation
Cause: DIAG couldn”t allocate buffer for remote copy.
Action: Check DIAG trace files for errors.
ORA-32738: Hang analysis aborted due to failed memory copy
Cause: DIAG couldn”t copy buffer to remote node.
Action: Check DIAG trace files for errors.
ORA-32739: 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.
ORA-32740: The requested operation cannot be proceeded
Cause: Operation was aborted because instance termination was in progress.
Action: Retry later after restarting the instance.
ORA-32741: 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.
ORA-32742: Hang analysis initialize failed
Cause: Hang analyzer was not able to allocate memory to initialize.
Action: Check the trace files.
ORA-32743: command cannot be executed on remote instance
Cause: The database was not mounted in SHARED mode.
Action: Mount the database in SHARED mode.
16-150 Oracle Database Error Messages
ORA-32761: Turn off Temp LOB Ref Count Feature
Cause: None
Action: Turn off the whole temp lob ref count feature
ORA-32762: Turn on Temp LOB Ref Count Tracing
Cause: None
Action: Check Trace file for debug info
ORA-32763: 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 ////////////////////////////
ORA-32766: 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.
ORA-32767: 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.
ORA-32771: 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.
ORA-32772: 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.
ORA-32773: operation not supported for smallfile tablespace string
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.
ORA-32774: more than one file was specified for bigfile tablespace string
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.
ORA-32775: cannot change size attributes of read only tablespace string
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.
Good Luck !
Leave a Reply
You must be logged in to post a comment.