Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: The subquery within THE operator must select a collection item.
Action: Change the subquery to select a collection item, then retry the operation.
Cause: An attempt was made to compare nested table, VARRAY, or LOB attributes of an object type in the absence of a MAP or ORDER method.
Action: Define a MAP or ORDER method for the type of the object type then retry the operation.
Cause: CURSOR on a subquery is allowed only in the top-level SELECT list of a query.
Action: Remove the CURSOR expression and retry the operation.
Cause: An attempt was made to use the MULTISET expression outside of a CAST to a nested table or VARRAY type.
Action: Put the MULTISET(subquery) expression inside a CAST to a nested table or VARRAY type.
Cause: An invalid reference was made to a nested table column.
Action: Remove invalid reference to the nested table column and retry the operation.
Cause: An attempt was made to access rows of an item whose type is not known at parse time or that is not of a nested table type.
Action: Use the CAST operator to cast the item to a nested table type.
Cause: An attempt was made to perform a DML on a nested table view column where a nested table column of a base table is expected.
Action: Remove the DML statements on nested table view columns and retry the operation.
Cause: The CAST to a type was performed on something other than a nested table or VARRAY type.
Action: CAST only to a nested table or VARRAY type then retry the operation.
Cause: The evaluation of the THE subquery resulted in a NULL value implying a NULL table instance. The THE subquery must result in a single non-NULL table instance.
Action: Ensure that the evaluation of the THE subquery results in a single non-null table instance. If the error occurs in the context of an insert statement where the THE subquery was the target of an insert, then ensure that an empty nested table instance is created by updating the nested table column of the parent table's row specifying an empty nested table constructor.
Cause: The total number of elements used in VARRAY construction exceeds the specified VARRAY limit.
Action: Don't use the more than the specified limit of elements for VARRAY construction.
Cause: Table name was qualified with schema name in the nested table storage clause.
Action: Respecify the nested table storage clause without the schema name qualification. By default, the store table for the nested table is created in the same schema as the containing table.
Cause: The storage clause is specified more than once for the nested table column.
Action: Remove the duplicate storage specification.
Cause: The storage clause is specified for a column or attribute that is not a nested table column or attribute.
Action: Specify a valid nested table column or attribute.
Cause: The storage clause is not specified for a column or attribute that is a nested table column or attribute.
Action: Specify a table name using the Nested Table storage clause.
Cause: Attempt was made to DROP a nested table.
Action: Nested tables cannot be explicitly dropped. Nested tables can only be dropped by dropping their containing parent table.
Cause: Attempt was made to ADD or MODIFY columns of a nested table.
Action: Columns cannot be added or modified for a nested table. You must ALTER the parent table's nested table column to cause any such change.
Cause: Exact FETCH on a query is not allowed if the query returns any cursors.
Action: Do not use an exact FETCH.
Cause: The row containing the LOB was not locked before the lob was updated.
Action: Lock the row containing the LOB before updating the LOB data.
Cause: The buffer length was not big enough to hold the amount of data requested.
Action: Verify that the number of bytes/characters specified in the input amount parameter is not bigger than the number of bytes specified in the input buffer length parameter. Allocate more space for the input buffer if necessary.
Cause: The lob associated with the input locator does not exist. The information in the locator does not refer to an existing LOB.
Action: Repopulate the locator by issuing a SELECT statement and retry the operation.
Cause: An attempt was made to write LOB data by the streaming mechanism (that is, unlimited write) but the input amount of data to stream was specified as 0. This means that an attempt is being made to write 0 bytes to the LOB data.
Action: Write more than 0 bytes to the LOB data.
Cause: The version of the LOB data needed for the consistent read was already overwritten by another writer.
Action: Use a larger version pool then retry the operation.
Cause: An attempt was made to write too much data to the LOB. LOB size is limited to 4 gigabytes.
Action: Either start writing at a smaller LOB offset or write less data to the LOB.
Cause: The input trim length to which the LOB data will be trimmed was specified to be greater than the current length of the LOB data.
Action: Might not need to trim the LOB data because it is already smaller than the trim length specified. Or, if trimming the LOB data really is required, use a smaller trim length.
Cause: An invalid input LOB locator was used; it was never initialized.
Action: Initialize the input LOB locator and pass the initialized LOB locator to the function.
Cause: An attempt was made to grant or revoke an invalid privilege on a directory.
Action: Only CREATE, DELETE, READ and WRITE privileges can be granted or revoked on directories. Do not grant or revoke other privileges.
Cause: The required directory name is invalid or missing.
Action: Specify a valid name.
Cause: Attempt to access a directory that does not exist.
Action: Make sure the name is correct.
Cause: Object types must have map or order methods defined for all comparisons other than equality and inequality comparisons.
Action: Define a map or order method for the object type.
Cause: Order method used to compare two object values returned NULL.
Action: Redefine the order method to not return a NULL.
Cause: Either the expression that was entered is not a view name or the name specified does not correspond to an object view.
Action: Replace the expression with the name of an object view and retry the operation.
Cause: When creating a typed view, the datatype of an expression in the WITH OID clause was not allowed for primary key-based OID.
Action: Replace the expression with one of appropriate scalar datatype and retry the operation.
Cause: A value constituting the primary key-based OID evaluated to NULL.
Action: Ensure the expressions in MAKE_REF system function or WITH OID clause of CREATE VIEW do not evaluate to NULL.
Cause: The size of the primary key-based OID of a typed view was too large.
Action: Specify fewer or smaller primary key columns in the WITH OID clause when creating the typed view.
Cause: WITH OID clause was not specified when creating a typed view.
Action: Specify the WITH OID clause, or create an untyped view instead, or create a typed view on a single typed table or view.
Cause: The object view specified in the MAKE_REF function did not have a primary key-based OID. A primary key-based REF cannot be created for such a view.
Action: Specify an object view that has a primary key-based OID in the MAKE_REF function.
Cause: Number of arguments for MAKE_REF was different from the number of primary key attributes of the object view.
Action: Specify all the necessary arguments for MAKE_REF.
Cause: Either the attribute name is missing in the WITH OBJECT OID clause or it is invalid.
Action: Specify a valid attribute of the object type of the object view.
Cause: Attempted to specify a Nested attribute in the WITH OBJECT OID clause.
Action: Specify a top-level attribute of the object type of the object view.
Cause: Attempt to insert a REF selected from an object view into the REF column of a table. Currently, such a REF cannot be stored in the database.
Action: Make sure the REF to be inserted into a REF column is selected from a table.
Cause: A LOB locator selected in one transaction cannot be used in a different transaction.
Action: Re-select the LOB locator and retry the operation.
Cause: The data to be returned in the argument is greater than the amount of space allocated for the argument.
Action: Allocate more space for the argument.
Cause: A remote LOB column cannot be referenced.
Action: Remove references to LOBs in remote tables.
Cause: Case 1: For LOB write, the amount of data received is different from the amount that was indicated would be sent.
Action: For Case 1: This will happen when using OCI's piecewise mechanism with polling or with a callback function. Modify the code either to send the amount specified or to pass 0 as the input amount so that any amount of data can be sent.
Cause: The source offset for a LOB COPY or LOB LOADFROMFILE is beyond the end of the source LOB.
Action: Check the length of the LOB and then adjust the source offset.
