Oracle Database Errors or Warnings from Error ORA-23377 to ORA-23387

SQLServerF1

ORA-23377: bad name string for missing_rows_oname1 argument
Cause: An attempt was made to use the name of the reference site table as the name of the missing_rows_oname1 argument.
Action: Provide a separately created table with a different name for missing_rows_oname1 argument. The separately created table will contain the differences between the tables being compared.
ORA-23378: connection qualifier “string” is not valid for object group “string”.”string”
Cause: The connection qualifier used in the database link for the specified object group does not match the qualifier specified for the group in create_master_repgroup.
Action: Use or create a database link which contains the correct connection qualifier.
ORA-23379: connection qualifier “string” is too long
Cause: The maximum length of a database link, including the connection qualifier, is 128 bytes.
Action: Use a shorter connection qualifier, or shorten the name of the database link

ORA-23380: propagation mode “string” is not valid
Cause: The specified propagation may be misspelled, or is not supported. For materialized view sites, all materialized view object groups at the same materialized view site with the same master object group must all have the same propagation method.
Action: Refer to the manual on replicated data for valid propagation modes. For materialized view sites, also ensure that the propagation modes of all materialized view object groups with the same master object group are the same.
ORA-23381: generated object for base object string.string@string does not exist
Cause: The system generated object(s) for the specified base object do not exist at the specified site. The current operation requires the base object to have generated replication support.
Action: Ensure that the generated replication object(s) for the base object exist and are valid at the specified site. If the generated object(s) do not exist, then the procedure dbms_repcat.generate_replication_support() needs to be called from the master definition site for the base object. missing_rows_oname1 argument. The separately created table will contain the differences between the tables being compared.
ORA-23382: materialized view repgroup “string”.”string” is not registered at site string
Cause: The materialized view repgroup is not currently registered at the master and so cannot be unregistered.
Action: None

ORA-23383: registration for materialized view repgroup “string”.”string” failed at site string
Cause: Insertion into local repschema table failed.
Action: None
ORA-23384: replication parallel push string argument out of range
Cause: Specified numeric argument to dbms_defer_sys.push is invalid.
Action: Fix the argument value and try again.
ORA-23385: replication parallel push string argument not valid
Cause: Specified string argument to dbms_defer_sys.push is invalid.
Action: Fix the argument value and try again.
ORA-23386: replication parallel push cannot create slave processes
Cause: An error was occurred while creating slave processes for parallel push.
Action: None
ORA-23387: replication parallel push dequeue error
Cause: An attempt to dequeue a deferred transaction failed while trying to assign a new queue batch number.
Action: None

Above are list of Oracle Database Errors or Warnings from Error ORA-23377 to ORA-23387 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *