ORA-23321: Pipename may not be null

ORA-23321: Pipename may not be null

Cause: You called dbms_pipe with a null pipe name.

Action: Find out the name of the pipe and call function with non-null pipename.

ORA-23320: the request failed because of values string and string

ORA-23320: the request failed because of values string and string

Cause: A missing ddl record for a repcatlog record, or inconsistency in repcat views.

Action: Retry the request, or make the views consistent.

ORA-23319: parameter value string is not appropriate

ORA-23319: parameter value string is not appropriate

Cause: The given value of a parameter is either null, misspelled, or not supported.

Action: Refer to the documentation and use parameter values that are appropriate for the given situation.

ORA-23318: a ddl failure has occurred

ORA-23318: a ddl failure has occurred

Cause: User-supplied or system-generated ddl did not execute successfully.

Action: Examine ddl, database state, repcatlog, and all_errors to determine why the failure occurred.

ORA-23317: a communication failure has occurred

ORA-23317: a communication failure has occurred

Cause: The remote database is inaccessible.

Action: Ensure the remote database is running, the communications network is functioning, and the appropriate database links are present.

ORA-23316: the masterdef is string

ORA-23316: the masterdef is string

Cause: The requested operation is not permitted on a masterdef site.

Action: Relocate the masterdef to another master and retry the operation.

ORA-23315: repcatlog version or request string is not supported by version string

ORA-23315: repcatlog version or request string is not supported by version string

Cause: Either incompatible repcat versions are used, or a repcatlog record has been corrupted.

Action: Convert the master to a compatible version of repcat or retry the request.

ORA-23314: database is not a materialized view site for string . string

ORA-23314: database is not a materialized view site for string . string

Cause: The invocation database is not a materialized view database for the given object group.

Action: Connect to the desired materialized view database and retry the request, or make the invocation database a materialized view site with create_mview_ repschema or create_mview_repgroup.

ORA-23313: object group string . string is not mastered at string

ORA-23313: object group string . string is not mastered at string

Cause: The group name is null, the group name is misspelled, the invocation database is not a master, or the invocation database does not believe the given database is a master.

Action: If the given group name was correct, connect to a current master and retry the request, make the invocation database a master with add_master_database, or use switch_mview_master if the invocation database is a materialized view site.

ORA-23312: not the masterdef according to string

ORA-23312: not the masterdef according to string

Cause: The group name is null, the group name is misspelled, the invocation or given database is not the masterdef, or one of the masters does not believe the invocation database is the masterdef.

Action: If the given group name and masterdef were both correct, connect to the masterdef and retry the request, or relocate the masterdef at the (errant) databases using relocate_masterdef.

ORA-23310: object group string . string is not quiesced

ORA-23310: object group string . string is not quiesced

Cause: The requested operation requires the object group to be suspended.

Action: Invoke suspend_master_activity at the repgroup s masterdef, wait until the status has changed to quiesced, and then retry the original request.

ORA-23309: object string.string of type string exists

ORA-23309: object string.string of type string exists

Cause: An object in the same namespace exists, perhaps with a different type or shape, or the same object has already been registered as an repobject in another object group.

Action: Remove the offending object with the SQL DROP command, unregister the offending object with dbms_repcat.drop_master_repobject(), or reinvoke the request using TRUE for a boolean parameter such as retry or use_existing_object.

ORA-23308: object string.string does not exist or is invalid

ORA-23308: object string.string does not exist or is invalid

Cause: The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object, or the object does not exist as a replicated object with the appropriate status.

Action: Ensure the object is valid in the database, is visible to the user, and, if appropriate, is a valid object in all_repobject.

ORA-23307: replicated schema string already exists

ORA-23307: replicated schema string already exists

Cause: The given database already replicates the given schema.

Action: Choose a different schema or a different database.

ORA-23306: schema string does not exist

ORA-23306: schema string does not exist

Cause: The schema name was null or misspelled, or the schema does not exist locally.

Action: Specify the schema correctly, or create it with CREATE USER.

ORA-23305: internal deferred RPC error: string

ORA-23305: internal deferred RPC error: string

Cause: An internal error occurred in deferred rpc.

Action: Report the error and other information to support.

ORA-23304: malformed deferred rpc at arg string of string in call string, in tid string

ORA-23304: malformed deferred rpc at arg string of string in call string, in tid string

Cause: A deferred RPC call was issued without the correct number of arguments as determined by the count parameter to dbms_defer.call

Action: Be sure the number of actuals matches the count.

ORA-23303: application raised generic exception during deferred RPC

ORA-23303: application raised generic exception during deferred RPC

Cause: An application declared a generic failure during a defered RPC.

Action: Determined by the application

ORA-23302: application raised communication failure during deferred RPC

ORA-23302: application raised communication failure during deferred RPC

Cause: An application declared a communication failure during a defered RPC.

Action: Retry the application when communication is restored.

ORA-23301: mixed use of deferred rpc destination modes

ORA-23301: mixed use of deferred rpc destination modes

Cause: Replication catalog determined deferred RPC destinations were mixed with destination determined by other mechanisms in the same transaction.

Action: Do not mix destination types in the same transaction.

ORA-23300: %s

ORA-23300: %s

Cause: The stored procedure raise_system_error was called which causes this error to be generated.

Action: Correct the problem as described in the error message or contact the application administrator or DBA for more information.

ORA-23293: Cannot rename a column which is part of a join index

ORA-23293: Cannot rename a column which is part of a join index

Cause: The column participates in a join index.

Action: If you need to rename the column, you need to drop the join index.

ORA-23292: The constraint does not exist

ORA-23292: The constraint does not exist

Cause: The given constraint name does not exist.

Action: Give an existing constraint s name.

ORA-23291: Only base table columns may be renamed

ORA-23291: Only base table columns may be renamed

Cause: Tried to rename a column of a non-base table, like object table or nested table or materialized view table.

Action: None. This is not allowed.

ORA-23290: This operation may not be combined with any other operation

ORA-23290: This operation may not be combined with any other operation

Cause: ALTER TABLE RENAME COLUMN or CONSTRAINT operation was given in conjunction with another ALTER TBALE Operation. This is not allowed.

Action: Ensure that RENAME COLUMN or CONSTRAINT is the only operation specified in the ALTER TABLE.

ORA-22999: CLOB or NCLOB data may have been corrupted

ORA-22999: CLOB or NCLOB data may have been corrupted

Cause: CLOB or NCLOB contains invalid character data. One possible cause is that the wrong csid was specified for the external file when calling DBMS_ LOB.LOADCLOBFROMFILE or DBMS_XSLPROCESSOR.READ2CLOB to load CLOB or NCLOB data from external files.

Action: Reload the CLOB or NCLOB data with the correct csid specified for the external file.

ORA-22998: CLOB or NCLOB in multibyte character set not supported

ORA-22998: CLOB or NCLOB in multibyte character set not supported

Cause: A CLOB or NCLOB in a fixed-width or varying-width multibyte character set was passed to a SQL character function which does not support multibyte LOB data.

Action: Use DBMS_LOB functions such as DBMS_LOB.INSTR() and DBMS_ LOB.SUBSTR()

ORA-22997: VARRAY | OPAQUE stored as LOB is not specified at the table level

ORA-22997: VARRAY | OPAQUE stored as LOB is not specified at the table level

Cause: An attempt was made to specify a VARRAY|OPAQUE column to be stored as LOB at the partition or subpartition or template level. However the VARRAY|OPAQUE column was not specified to be stored as LOB at the table level when the table was created.

Action: Specify the VARRAY | OPAQUE column to be stored as LOB at the table level when the table is created. Alternatively, do not specify the VARRAY | OPAQUE column to be stored as LOB at the partition or subpartition or template level if it is not specified at the table level when the table is created.

ORA-22996: NEXT extent size is smaller than LOB chunksize

ORA-22996: NEXT extent size is smaller than LOB chunksize

Cause: An attempt was made to create or alter a LOB segment so that its NEXT extent size was less than the LOB chunksize

Action: Specify a NEXT extent size that is greater than or equal to the LOB chunksize

ORA-22995: TABLESPACE DEFAULT option is invalid in this context

ORA-22995: TABLESPACE DEFAULT option is invalid in this context

Cause: TABLESPACE DEFAULT option can be specified for LOB columns only in the following contexts: TABLESPACE DEFAULT option in a different context.

Action: Remove the TABLESPACE DEFAULT option.

ORA-22994: source offset is beyond the end of the source LOB

ORA-22994: source offset is beyond the end of the source LOB

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.

ORA-22993: specified input amount is greater than actual source amount

ORA-22993: specified input amount is greater than actual source amount

Cause: (1) For LOB write, the amount of data received is different from the amount that was indicated would be sent. (2) For LOB copy and loadfromfile, the end of the source LOB or FILE value was reached before the specified input amount was copied or loaded.

Action: (1) 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. (2) will happen if the specified input amount is too large for the source LOB or FILE given the starting source offset. Either decrease the starting source offset, or decrease the amount to copy or load.

ORA-22992: cannot use LOB locators selected from remote tables

ORA-22992: cannot use LOB locators selected from remote tables

Cause: A remote LOB column cannot be referenced.

Action: Remove references to LOBs in remote tables.

ORA-22991: insufficient space allocated for argument string

ORA-22991: insufficient space allocated for argument string

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.

ORA-22990: LOB locators cannot span transactions

ORA-22990: LOB locators cannot span transactions

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.

ORA-22984: view query cannot contain references to a super view

ORA-22984: view query cannot contain references to a super view

Cause: The query defining the view contains references to a super-view of the view being created.

Action: Make sure that the view query does not reference a super-view.

ORA-22983: not a user-defined REF

ORA-22983: not a user-defined REF

Cause: Attempt to use a system generated REF value where a user-defined REF value should be used.

Action: Make sure the REF value is user-defined.

ORA-22982: cannot create sub-view under this view

ORA-22982: cannot create sub-view under this view

Cause: The view derives its OID from a table or view having primary key based OID and sub-views cannot be created under such views.

Action: Specify view having system generated OID or a view created with the specification of attributes in the WITH OBJECT ID clause and retry the operation.

ORA-22981: must specify a table or view having system generated OID

ORA-22981: must specify a table or view having system generated OID

Cause: The super-view is based on a table or view having the system generated OID and the sub-view must also be based on a similar table or view.

Action: Specify table or view having system generated OID and retry the the operation.

ORA-22980: must specify a set of attributes for the WITH OBJECT OID clause

ORA-22980: must specify a set of attributes for the WITH OBJECT OID clause

Cause: The WITH OBJECT OID DEFAULT clause was used, but the underlying view or table does not have a OID.

Action: Specify attributes for the WITH OBJECT OID clause to create a primary key based object identifier for the object view.

ORA-22979: cannot INSERT object view REF or user-defined REF

ORA-22979: cannot INSERT object view REF or user-defined REF

Cause: Attempt to insert an object view REF or user-defined REF in a REF column created to store system generated REF values

Action: Make sure the REF to be inserted is not from an object view or from a user-defined REF column

ORA-22978: only simple attribute name is allowed in the WITH OBJECT OID clause

ORA-22978: only simple attribute name is allowed in the WITH OBJECT OID clause

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.

ORA-22977: missing or invalid attribute

ORA-22977: missing or invalid attribute

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.

ORA-22976: incorrect number of arguments to MAKE_REF

ORA-22976: incorrect number of arguments to MAKE_REF

Cause: Number of arguments for MAKE_REF is different from the number of PRIMARY KEY attributes of the object view.

Action: Specify all the necessary arguments for MAKE_REF.

ORA-22975: cannot create a PRIMARY KEY-based REF to this object view

ORA-22975: cannot create a PRIMARY KEY-based REF to this object view

Cause: The object view specified in the MAKE_REF function does not have a PRIMARY KEY-based object identifier. A PRIMARY KEY-based REF cannot be created for such a view.

Action: Specify an object view that has a PRIMARY KEY-based object identifier in the MAKE_REF function.

ORA-22974: missing WITH OBJECT OID clause

ORA-22974: missing WITH OBJECT OID clause

Cause: WITH OBJECT OID clause is not specified when creating an object view.

Action: Specify the WITH OBJECT OID clause.

ORA-22973: size of object identifier exceeds maximum size allowed

ORA-22973: size of object identifier exceeds maximum size allowed

Cause: Size of the PRIMARY KEY-based object identifier of an object view exceeds the maximum size of 4000 bytes.

Action: Specify fewer or smaller PRIMARY KEY attributes in the WITH object OID clause when creating the object view.

ORA-22972: NULL value not allowed in PRIMARY KEY-based object identifier

ORA-22972: NULL value not allowed in PRIMARY KEY-based object identifier

Cause: A value constituting the PRIMARY KEY-based object identifier is NULL.

Action: Ensure the expressions in MAKE_REF system function or attributes in the WITH OBJECT OID clause of an object view do not evaluate to NULL.

ORA-22971: invalid datatype for PRIMARY KEY-based object identifier

ORA-22971: invalid datatype for PRIMARY KEY-based object identifier

Cause: When creating an object view, the datatype of an expression in the WITH OBJECT OID clause is not allowed for PRIMARY KEY-based OID.

Action: Replace the expression with one of appropriate scalar datatype.

ORA-22970: name does not correspond to an object view

ORA-22970: name does not correspond to an object view

Cause: Either the expression 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.

ORA-22958: This operation is not allowed in check constraints or triggers

ORA-22958: This operation is not allowed in check constraints or triggers

Cause: An invalid operation is used in a check constraint or trigger

Action: Do not use the operation

ORA-22957: NULL is an invalid input to powermultiset and COLLECT functions

ORA-22957: NULL is an invalid input to powermultiset and COLLECT functions

Cause: NULL was given as input to the powermultiset or COLLECT function.

Action: Give a non-null value as input

ORA-22956: The set contains no elements

ORA-22956: The set contains no elements

Cause: An empty set was given as input to the powermultiset function.

Action: Give a non-empty set as input

ORA-22955: The cardinality parameter is not within the allowed limits

ORA-22955: The cardinality parameter is not within the allowed limits

Cause: The cardinality parameter has to be greater than 1 and less than or equal to the cardinality of the input.

Action: Give a valid cardinality value.

ORA-22954: This multiset operation is not supported for this element type.

ORA-22954: This multiset operation is not supported for this element type.

Cause: The multiset operation attempted was not supported for the nested table element type.

Action: Use a supported element type.

ORA-22953: Cardinality of the input to powermultiset exceeds maximum allowed

ORA-22953: Cardinality of the input to powermultiset exceeds maximum allowed

Cause: The cardinality of the input nested table to the powermultiset should not exceed 32 elements

Action: Reduce the number of elements to the input.

ORA-22952: Nested Table equality requires a map method on the element ADT

ORA-22952: Nested Table equality requires a map method on the element ADT

Cause: Nested Table equality was tried where the element ADT did not have a map method defined on it.

Action: Define a map method on the element ADT..

ORA-22951: NULL returned by ORDER method

ORA-22951: NULL returned by ORDER method

Cause: ORDER method used to compare two object values returned NULL which is not allowed.

Action: Redefine the ORDER method to not return a NULL.

ORA-22950: cannot ORDER objects without MAP or ORDER method

ORA-22950: cannot ORDER objects without MAP or ORDER method

Cause: an object type must have a MAP or ORDER method defined for all comparisons other than equality and inequality comparisons.

Action: Define a MAP or ORDER method for the object type

ORA-22933: cannot change object with type or table dependents

ORA-22933: cannot change object with type or table dependents

Cause: Attempt to replace, drop or rename an object with type or table dependents.

Action: Drop depending objects or use FORCE option if available.