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.