ORA-29250 to ORA-32799

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. 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 name 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: An HTTP protocol error occurred during the HTTP operation.

Action: Check the HTTP server on which 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 administrator 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.

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: An SMTP transient error occurred.

Action: Correct the error and retry the SMTP operation.

ORA-29279 SMTP permanent error: string

Cause: An 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 by issuing the statement 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, both the absolute and relative offsets were NULL, or the absolute offset was less than zero.

Action: If specifying an absolute offset, then ensure it is in the range [0, <total number of bytes in the file>], or if specifying a relative offset, then 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, 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-29300 ORACLE error, tablespace point-in-time recovery

Cause: Another Oracle error occurred 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 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 tablespace 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 database not compatible, string 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 re-created.

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

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 occurred 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 SET COMPATIBILITY command cannot be used for releases before 8.0.0

Cause: The rolling release feature was first implemented in 8.0.3.

Action: Try 8.0.3 or later.

ORA-29324 SET COMPATIBILITY release string format is wrong

Cause: It should be of the form 8.x.x.

Action: Use the correct format.

ORA-29325 SET COMPATIBILITY release number mismatches compatibility release number

Cause: In 8.0.3, it should be the same as compatibility release number.

Action: Specify the same as the COMPATIBLE initialization parameter. Note that this cannot be a release number less than 8.0.0.

ORA-29326 specified SET COMPATIBILITY release number reduced to string.string.string.string.string

Cause: One or more instances had a lower release number.

Action: To roll the release to the specified number, all instances will need to migrate to the same release number or higher.

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.

Action: Contact Oracle Support Services.

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: Contact Oracle Support Services.

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, then contact Oracle Support Services.

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.

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 referenced owner. There are two cases in which this may occur:

• 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.
• This user is specified in the TTS_OWNER list, but this user does not own any data in the transportable set.

Action: Retry the import with a different OWNER list.

ORA-29345 can not plug a tablespace into a database using a different character set

Cause: Oracle does not support plugging a tablespace into a database using a different 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 PL/SQL User's Guide and Reference and use the correct format.

ORA-29347 Tablespace name validation failed - failed to match tablespace 'string'

Cause: The system failed to match the referenced tablespace. There are two case in which this may happen:

• 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.
• 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: An attempt was made to plug-in a tablespace which already exists.

Action: Drop the offending tablespace if possible. Otherwise use a different method (for example, import/export) to move data.

ORA-29350 server version string incompatible with package string version string

ORA-29351 can not transport system or temporary tablespace 'string'

Cause: The referenced tablespace is either the system tablespace or a temporary tablespace.

Action: Do not include this tablespace in the transportable set.

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 the 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 percentage string is outside valid range of 0 to 100

Cause: An invalid percentage value was specified.

Action: Specify a percentage 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.

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 NULL or invalid GROUP_OR_SUBPLAN argument specified

Cause: A NULL or invalid GROUP_OR_SUBPLAN was specified as an argument to procedure CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.

Action: Specify a non-NULL, valid argument.

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.