Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 29250-29399: DBMS_SQL Messages

##### ORA-29250: invalid index specified 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. 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. 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-29300: ORACLE error, tablespace point-in-time recovery

Cause: An ORACLE error occurred in the DBMS_PITR package.

Action: See the text of the Oracle 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: 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: 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 `name' 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 `name'

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 name is not online

Cause: The selected datafile was not online.

Action: Bring the datafile online and rename it if necessary.

##### ORA-29307: datafile name error, name

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, name not match

Cause: The production database is not the same as the clone database.

Action: Open the correct production database and try the import again.

##### ORA-29312: database not compatible, name name

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 different point-in-time and retry the operation.

##### ORA-29313: tablespace `name' cannot be imported twice

Cause: This is an internal error.

Action: Contact your database administrator.

##### ORA-29314: tablespace `name' is not OFFLINE FOR RECOVERY nor READ ONLY

Cause: Tablespace clean SCN (system commit number) is either 0 or invalid.

Action: ALTER the tablespace OFFLINE FOR RECOVER.

##### ORA-29315: tablespace `name' has been recreated

Cause: An attempt was made to recover a tablespace to a point-in-time before it was recreated.

  For example, you CREATE TABLESPACE FINANCIAL on 1/1 and DROP it on 1/10. On 1/12, you CREATE a new tablespace also called FINANCIAL. ORACLE allows you to do this. Note that the two FINANCIAL tablespaces are different. To continue the example, on 1/14, you try to recover tablespace FINANCIAL to 1/5. ORACLE returns the above error because although ORACLE finds the FINANCIAL tablespace on 1/5, it is not the FINANCIAL tablespace that exists on 1/14. This is because FINANCIAL was recreated.

Action: Choose a different point in time for recovery.

##### ORA-29316: datafile name been imported twice

Cause: This is an internal error.

Action: Contact your database administrator.

##### ORA-29317: datafile name 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 name is online

Cause: The datafile is online.

Action: Take the datafile offline.

##### ORA-29319: datafile name 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 while reading the 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. It is assumed that no more than 100 datafiles were added since the point-in-time.

Action: Divide the recovery set into smaller subsets and contact Oracle.

##### 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 as the value for SET COMPATIBILITY.

##### ORA-29324: SET COMPATIBILITY release string format is wrong

Cause: The SET COMPATIBILITY release string was not specified in the form 8.x.x.

Action: Enter a release string in the form 8.x.x. For example, 8.0.3.

##### ORA-29325: SET COMPATIBILITY release number mismatches compatibility release number

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

Action: Specify the release number to be 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 release_number

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.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index