ORA-32322: PCT refresh of string . string not allowed the sequence of DMLs or PMOPs

ORA-32322: PCT refresh of string . string not allowed the sequence of DMLs or 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-32321: REFRESH FAST of string . string unsupported after detail table TRUNCATE

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-32320: REFRESH FAST of string . string unsupported after container table PMOPs

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-32319: Cannot use direct loader log to FAST REFRESH materialized view string. string

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-32318: cannot rename a materialized view

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-32317: cannot run a job from a job

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-32316: REFRESH FAST of string . string unsupported after mixed DML

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-32315: REFRESH FAST of string . string unsupported after mixed DML and Direct Load

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-32314: REFRESH FAST of string . string unsupported after deletes or updates

ORA-32314: REFRESH FAST of string . string unsupported after deletes or 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-32313: REFRESH FAST of string . string unsupported after PMOPs

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.

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-32312: cannot refresh a secondary materialized view string . string

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-32311: materialized view definition query selects an unsupported user-defined type

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-32310: object materialized views must select from an 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-32309: object mview type string . string does not match the master table type

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-32308: object materialized views must use SELECT *

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-32307: must use FROM ONLY clause when referencing an object table

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-32306: updatable materialized views with user-defined types must use SELECT *

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-32305: RepAPI materialized views with user-defined types are not supported

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-32304: materialized views with user-defined types cannot use prebuilt table

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-32303: mviews with user-defined types cannot reference multiple master sites

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-32302: object materialized views must be object ID based

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-32301: object-relational materialized views must be primary key based

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-32300: cannot drop a secondary materialized view string . string

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-32168: Cannot perform operation on a null AnyData

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-32167: No payload set on the Message

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-32166: Cannot get XA connection

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-32165: Cannot get XA environment

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-32164: Method called on Invalid Connection type

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

Action: Make sure Connection type is OK

ORA-32163: Method called on Invalid Environment type

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-32162: Read or Write SQL method not registered

ORA-32162: Read or Write SQL method not registered

Cause: readSQL or writeSQL method was NULL or was not registered

Action: Register readSQL or writeSQL by calling put method in Map

ORA-32161: Cannot perform piecewise fetch

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-32159: Cannot set prefetch options for a null 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-32158: Invalid type passed

ORA-32158: Invalid type passed

Cause: An inapplicable type was passed to this call.

Action: Pass an applicable type.

ORA-32156: Cannot perform operation on stream

ORA-32156: Cannot perform operation on stream

Cause: This operation is not applicable to streams obtained from LOBs.

Action: none

ORA-32155: Anydata not specified

ORA-32155: Anydata not specified

Cause: A null anydata was passed.

Action: Pass a valid, non-null anydata.

ORA-32154: Anydata context not specified

ORA-32154: Anydata context not specified

Cause: A null anydata context was passed.

Action: Pass a valid, non-null anydata context.

ORA-32153: Environment not specified

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-32152: Cannot perform operation on a null number

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-32151: Environment not specified

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-32150: Cannot perform operation on a null timestamp

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-32147: Environment not specified

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-32146: Cannot perform operation on a null date

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-32145: Environment not specified

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-32144: Cannot perform operation on a null interval

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-32143: Environment not specified

ORA-32143: Environment not specified

Cause: A null environment was passed.

Action: Pass a valid, non-null environment.

ORA-32142: maximum number of iterations exceeded

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-32141: get method does not match the type of the parameter

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-32140: cannot peform this operation on stream

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-32139: Cannot write to the 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-32136: Cannot perform operation on an invalid stream

ORA-32136: Cannot perform operation on an invalid stream

Cause: The LOB or FILE from which the stream was obtained had been nullified or destroyed.

Action: Use a valid stream.

ORA-32135: Cannot assign FILEs

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-32134: Cannot assign LOBs

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-32133: Cannot get stream from LOB or FILE

ORA-32133: Cannot get stream from LOB or FILE

Cause: An open stream exists on the the LOB or FILE on which the operation was attempted.

Action: Close the stream before getting another.

ORA-32132: maximum iterations cannot be changed

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-32131: bind data type cannot be changed

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-32130: invalid offset or index refrenced in Bytes

ORA-32130: invalid offset or index refrenced in Bytes

Cause: The offset or 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-32129: cannot get information about this column

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-32128: setDataBuffer called after fetch has started

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-32127: REFs do not belong to any connection

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-32126: Cannot perform operations on a null REF

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.