ORA-29314: tablespace string is not OFFLINE FOR RECOVER nor READ ONLY

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-29313: tablespace string cannot be imported twice

ORA-29313: tablespace string cannot be imported twice

Cause: This is an internal error.

Action: Contact your database administrator.

ORA-29312: changes by release string cannot be used by release string, type: string

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-29311: export dump file was not generated by this database, string does not match

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-29310: database is not open, or opened as a clone

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-29309: export dump file was generated by different version of DBMS_PITR package

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-29308: view TS_PITR_CHECK failure

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-29307: datafile string error, string

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-29306: datafile string is not online

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-29305: cannot point-in-time recover tablespace string

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-29304: tablespace string does not exist

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-29303: user does not login as SYS

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-29302: database is not open clone

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-29301: wrong DBMS_PITR package function or procedure order

ORA-29301: wrong DBMS_PITR package function or procedure order

Cause: The DBMS_PITR package function or procedure was called in an incorrect order.

Action: Restart tablespace point-in-time recovery with a correct procedure.

ORA-29300: ORACLE error, tablespace point-in-time recovery

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-29299: Invalid handle for piecewise compress or uncompress

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-29298: Character set mismatch

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-29297: The compressed representation is too big

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-29296: invalid encoded string

ORA-29296: invalid encoded string

Cause: An error occurred while decoding the input string

Action: Verify that source data is a valid encoded string.

ORA-29295: invalid mime header tag

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: =?lamp;lt;lamp;nbsp;charsetlamp;gt;?lamp;lt;lamp;nbsp;encodinglamp;gt;?lamp;lt;lamp;nbsp;encoded stringlamp;gt;?=

ORA-29294: A data error occurred during compression or uncompression.

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-29293: A stream error occurred during compression or uncompression.

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-29292: file rename operation failed

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-29291: file remove operation failed

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-29290: invalid offset specified for seek

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, lamp;lt;lamp;nbsp;total number of bytes in the filelamp;gt;(, 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-29289: directory access denied

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-29288: invalid file name

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-29287: invalid maximum line size

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-29286: internal error

ORA-29286: internal error

Cause: A fatal error occurred while allocating PL or SQL session memory.

Action: Verify that the PL or SQL session is connected and that adequate memory resources are available.

ORA-29285: file write error

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-29284: file read error

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-29283: invalid file operation

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-29282: invalid file ID

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-29281: invalid mode

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-29280: invalid directory path

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-29279: SMTP permanent error: string

ORA-29279: SMTP permanent error: string

Cause: A SMTP permanent error occurred.

Action: Correct the error and retry the SMTP operation.

ORA-29278: SMTP transient error: string

ORA-29278: SMTP transient error: string

Cause: A SMTP transient error occurred.

Action: Correct the error and retry the SMTP operation.

ORA-29277: invalid SMTP operation

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-29276: transfer timeout

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-29275: partial multibyte character

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-29274: fixed-width multibyte character set not allowed for a URL

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-29273: HTTP request failed

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-29272: initialization failed

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-29271: not connected

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-29270: too many open HTTP requests

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-29269: HTTP server error string

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-29268: HTTP client error string

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-29267: illegal call

ORA-29267: illegal call

Cause: The call to the PL or SQL API was illegal at the current stage of the operation.

Action: Retry the call at a different stage of the operation.

ORA-29266: end-of-body reached

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-29265: HTTP header not found

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-29264: unknown or unsupported URL scheme

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-29263: HTTP protocol error

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-29262: bad URL

ORA-29262: bad URL

Cause: An improperly formed URL was passed to the PL or SQL API.

Action: Check the URL and retry the call.

ORA-29261: bad argument

ORA-29261: bad argument

Cause: A bad argument was passed to the PL or SQL API.

Action: Check the arguments passed to the PL or SQL API and retry the call.

ORA-29260: network error: string

ORA-29260: network error: string

Cause: A network error occurred.

Action: Fix the network error and retry the operation.

ORA-29259: end-of-input reached

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-29258: buffer too small

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-29257: host string unknown

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-29256: Cursor contains both regular and array defines which is illegal

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 or SQL tables and regular defines to move data from select queries into PL or SQL variables.

Action: Modify your PL or SQL program to only perform calls to one of the two functions depending on the situation at hand.

ORA-29255: Cursor contains both bind and define arrays which is not permissible

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 or SQL tables and array binds to bind PL or SQL tables to non-select queries.

Action: Modify your PL or SQL program to only perform calls to one of the two functions depending on the kind of cursor at hand.