Oracle 11g Error Codes and Solution Suggestions from ORA-23300 to ORA-23400

Oracle 11g Error Codes and Solution Suggestions from ORA-23300 to ORA-23400

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-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-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-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-23305: internal deferred RPC error: string

Cause: An internal error occurred in deferred rpc.

Action: Report the error and other information to support.

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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-23322: Privilege error accessing pipe

Cause: You either tried to create a pipe that already existed and belonged to someone else, or remove a pipe that you were not authorized to use, or put a message into a pipe that you were not authorized for, or get a message from a pipe that you were not authorized for.

Action: You may have to use a different pipename.

ORA-23323: parameter length exceeds deferred RPC limits

Cause: A deferred rpc parameter was longer than the deferred rpc limits of 4000 bytes for char/varchar2 parameters and 2000 bytes for raw parameters.

Action: Use smaller parameters.

ORA-23324: error string, while creating deferror entry at “string” with error string

Cause: The given error was encountered while attempting to create a deferor entry for the give error code and the give database.

Action: Correct the cause of the given error.

ORA-23325: parameter type is not string

Cause: A conflict resolution priority function was given a type different than the type assigned to the priority group; or the priority group has no type assigned or a function; or dbms_defer_sys_query was called to retrieve a deferred rpc parameter from the deferred rpc queue, but the type of the parameter does not match the return type of the function.

Action: Use the function corresponding to the parameter type.

ORA-23326: object group “string“.”string” is quiesced

Cause: Either suspend_master_activity has been called before the object group has resumed normal operation or a (deferred) rpc operation was attempted while the object group was quiesced.

Action: If suspend_master_activity has been called and a resume_master_activity request is pending, wait until it completes, and then reinvoke suspend_master_activity. Otherwise, resume database activity with the resume_master_activity call.

ORA-23327: imported deferred rpc data does not match string of importing db

Cause: Deferred rpc queues were imported from a database with a different global name or operating system than importing database.

Action: Deferred rpc data should only be imported into a database with the same global name and hardware and operating system.

ORA-23328: mview base table “string“.”string” differs from master table “string“.”string“

Cause: When creating a materialized view through repcat, the materialized view base table name did not match a replicated table name at the master.

Action: Change the materialized view ddl to use the same base table as the replicated table name at the master.

ORA-23329: successful user-provided ddl but no materialized view “string“.”string“

Cause: The DDL provided by the user to create a materialized view was executed without error, but materialized view does not exist.

Action: Manually back-out the DDL, and reregister with matching ddl and materialized view.

ORA-23330: column group string already exists

Cause: The column group was already registered in the object group.

Action: Use a column group name not yet registered in the replicated object group.

ORA-23331: column group string does not exist

Cause: The given column group is either null, misspelled or not registered.

Action: Use a registered column group.

ORA-23332: group string is in use; cannot drop

Cause: The given column group or priority group is being used to resolve conflicts.

Action: Call dbms_repcat procedures drop_update_resolution, drop_delete_resolution, drop_unique_resolution so that the column group or priority group is no longer in use before dropping.

ORA-23333: column string is already part of a column group

Cause: Attempted to add a column to a column group when the column was already a member of a column group.

Action: Drop the column from its existing column group before trying to add it to another.

ORA-23334: column string does not exist in table or column group

Cause: The given column is either null, misspelled or is not part of the given table or column group.

Action: Use a column that is a member of the table or column group.

ORA-23335: priority group string already exists

Cause: The priority group was already registered in the object group.

Action: Use a column group name not yet registered in the object group.

ORA-23336: priority group string does not exist

Cause: The priority group was already registered in the object group.

Action: Use a priority group name not yet registered in the object group.

ORA-23337: priority or value not in priority group string

Cause: The specified value or priority has not been registered as part of the priority group.

Action: Either specify a different value or priority that is already part of the priority group, or add the value to the priority group.

ORA-23338: priority or value already in priority group string

Cause: The specified value or priority has already been registered as part of the priority group.

Action: Either specify a different value or priority that not already part of the priority group, or drop the value to the priority group.

ORA-23339: duplicate conflict resolution information

Cause: The specified combination of column group, sequence, conflict type and/or parameter table name, parameter column name, and parameter sequence number has already been registered.

Action: Verify that additional conflict resolution information needs to be added and provide a new sequence number. If modifying existing information, the existing information must be dropped first.

ORA-23340: incorrect resolution method string

Cause: User function is specified when conflict resolution method was not “USER FUNCTION” or specified resolution method is not one of the predefined methods.

Action: If user function is specified when conflict resolution method was not “USER FUNCTION”, either reregister function with method as “USER FUNCTION” or specify a NULL user function. Otherwise Specify one of the documented supported conflict resolution methods.

ORA-23341: user function required

Cause: A NULL user function was specified for the “USER FUNCTION” method.

Action: Provide user function name (e.g., “schema”.”package”.”function”) that conforms to the documented user function specifications or specify one of the documented supported conflict resolution methods.

ORA-23342: invalid parameter column string

Cause: The parameter column name is null or misspelled, the invocation database is not a master, or is of the wrong type for the specified conflict resolution method.

Action: Specify a parameter column from the specified column group that has a correct type for the conflict resolution method.

ORA-23343: no match for specified conflict resolution information

Cause: The specified combination of column group, sequence, conflict type has not been registered (e.g., for adding a comment).

Action: Specify a combination of column group, sequence, conflict type has been registered.

ORA-23344: constraint (string.string) does not exist

Cause: A null, misspelled or nonexistent constraint was specified when registering a uniqueness conflict.

Action: Register a named constraint for the specified table.

ORA-23345: table “string“.”string” not registered to collect statistics

Cause: A procedure that deals with conflict resolution statistics-gathering was called for a table that was not registered to collect statistics.

Action: Call dbms_repcat.register_statistics to register the table.

ORA-23346: primary key or object ID is undefined for table or materialized view string

Cause: Trying to generate replication support for a table or materialized view without a primary key (as defined by a constraint or dbms_repcat.set_columns) or an object ID.

Action: For a table, add a primary key constraint or define a primary key using dbms_repcat.set_columns or use object tables. For a ROWID materialized view, set min_communication to false or use primary key or object ID materialized views.

ORA-23347: datatype string for column string table string not supported

Cause: The table has a column whose datatype is not supported by repcat.

Action: Remove the column from the table, or alter the column to have one of the supported datatypes.

ORA-23348: cannot replicate procedure string; only IN parameters supported

Cause: Trying to generate replication support for a package that has a procedure with OUT or IN OUT parameters.

Action: Remove the procedure from the package, or remove the OUT or IN OUT parameters from the procedure.

ORA-23349: cannot generate replication support for functions

Cause: Trying to generate replication support for a package that has a public function, or for a stand-alone function.

Action: Remove the public function from the package, or alter the function to be a procedure.

ORA-23350: maximum number of recursive calls exceeded

Cause: This usually occurs when trying to resolve conflicts in a table while concurrent updates to the same row create more conflicts.

Action: Re-execute the deferred transaction from DefError using dbms_defer_sys.execute_error

ORA-23351: parameter datatype string for procedure string not supported

Cause: The procedure has a parameter whose datatype is not supported by repcat.

Action: Remove the parameter from the procedure, or alter the parameter to have one of the supported datatypes.

ORA-23352: duplicate destination for deferred transaction

Cause: A duplicate destination was specified for a deferred transaction either in a dbms_defer.call call or an earlier dbms_defer.transaction call or a dbms_defer_sys.add_default_dest call.

Action: Remove the duplicate entry

ORA-23353: deferred RPC queue has entries for object group “string“.”string“

Cause: The requested action cannot be performed until the queue is empty for the given object group

Action: Use dbms_defer_sys.execute or dbms_defer_sys.delete_tran to empty the queue.

ORA-23354: deferred RPC execution disabled for “string” with “string“

Cause: Deferred RPC can not be executed at the destination with the specified catchup value because their propogation has been disabled.

Action: Enable deferred RPC execution with the dbms_defer_sys.set_disabled call.

ORA-23355: object string.string does not exist or is invalid at master site

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

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

ORA-23356: masterdef recognizes a master which does not recognize the masterdef

Cause: Possibly drop_master_repgroup was run at a master site but remove_master_databases was not run at master definition site for that master.

Action: Run remove_master_databases from master definition site to remove the appropriate master (see associated error messages).

ORA-23357: the propagator does not exist

Cause: The propagator does not exist.

Action: Register a new propagator.

ORA-23358: invalid remote user

Cause: The local user does not match the remote user connected via a database link.

Action: Drop and recreate the identified database link with the connect-to user identical to the owner of the database link.

ORA-23359: error on creating a ddl record for a repcatlog record

Cause: The userid in the repcatlog record does not match the userid of the connected user.

Action: Retry the operation with a different user.

ORA-23360: only one materialized view for master table “string” can be created

Cause: Trying to create more than one materialized view on a given master table in the same rep group.

Action: Create these other materialized views in a different rep group at another site.

ORA-23361: materialized view “string” does not exist at master site

Cause: The materialized view does not exist at the master site for offline instantiation of the materialized view.

Action: The correct procedure is to create the materialized view in a different schema at the master site, and then follow the instructions for offline instantiation of materialized views.

ORA-23362: invalid user

Cause: The given user does not exist.

Action: None

ORA-23363: mismatch of mview base table “string” at master and mview site

Cause: The name of the base table of the materialized view at the master site is different from the base table at the materialized view site. This error may arise during offline instantiation of materialized views.

Action: Retry offline instantiation with a materialized view name less than 24 bytes

ORA-23364: Feature not enabled: Advanced replication

Cause: The Advanced Replication feature is not enabled at this site. Updatable materialized views, deferred RPCs, and other replication features are, therefore, unavailable.

Action: Do not attempt to use this feature. Contact an Oracle Customer Support representative if the Advanced Replication feature has been purchased but not enabled.

ORA-23365: site string does not exist

Cause: site specified in argument “reference_site” or argument “comparison_site” in call to “differences()” routine or “rectify()” routine does not name an existing site.

Action: Make sure that database sites specified really do exist, and re-run the routine.

ORA-23366: integer value string is less than 1

Cause: Value of argument “max_missing” to routine “differences()” cannot be less than 1. Value of argument “commit_rows” to routines “differences()” and “rectify()” cannot be less than 1.

Action: Choose an integer value for those arguments to be 1 or greater.

ORA-23367: table string is missing the primary key

Cause: Table specified in argument “oname1” or “oname2” in call to “differences()” routine does not contain either a primary key or a virtual primary key (defined through dbms_repcat package under symmetric replication).

Action: Make sure the tables specified have a primary key defined.

ORA-23368: name string cannot be null or the empty string

Cause: Argument “sname1,” “sname2,” “oname1,” “oname2,” “missing_rows_sname,” “missing_rows_oname1,” “missing_rows_oname2” to “differences()” or “rectify()” cannot be NULL or ” (empty string).

Action: Change argument to non-null or non-empty string.

ORA-23369: value of “string” argument cannot be null

Cause: Argument “max_missing” to “differences()” routine cannot be NULL.

Action: Legal values for “max_missing” are integers 1 or greater.

ORA-23370: table string and table string are not shape equivalent (string)

Cause: The tables specified are not shape equivalent, which means intuitively that the number of columns, the names, their datatypes and lengths are not the same. Specifically, problem is in the parentheses and is one of the following: the number of columns are not equal, datatypes of columns with same name in different tables are different, lengths of varchar2 and char columns are not equal, precision and scale of number datatypes are not equal.

Action: Make sure the two tables being compared have the same number of columns, same column names, and same datatypes.

ORA-23371: column string unknown in table string

Cause: Some column in “array_columns” argument (or “column_list” argument) to “differences()” routine does not correspond to a column in the specified table.

Action: Make sure that all the columns in either “array_columns” or “column_list” are present in the specified table.

ORA-23372: type string in table string is unsupported

Cause: Certain types in the table comparison utility are not supported.

Action: Make sure that the types of columns in the tables to be compared are the ones supported by symmetric replication.

ORA-23373: object group “string“.”string” does not exist

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

Action: Specify the group correctly, or create it with dbms_repcat.create_master_repgroup().

ORA-23374: object group “string“.”string” already exists

Cause: The given database already replicates the given object group. A materialized view repgroup cannot be created at a given site where a master repgroup with the same name already exists.

Action: Choose a different group or a different database.

ORA-23375: feature is incompatible with database version at string

Cause: A feature not compatible with the specified database was used

Action: Set or raise the value of the “compatible” INIT.ORA parameter to match the necessary compatibility level.

ORA-23376: node string is not compatible with replication version “string“

Cause: A feature not compatible with the remote database was used

Action: Upgrade the remote database and retry the operation

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

ORA-23388: replication parallel push watermark error

Cause: An error occurred during parallel push while trying to update the high-water-mark information in system.def$_destination.

Action: None

ORA-23389: obsolete procedure; drop objects and recreate using new master

Cause: dbms_repcat.switch_mview_master is no longer supported.

Action: Drop the objects in the object group and recreate them using the new master.

ORA-23392: could not find materialized view to be associated with “string“.”string“

Cause: Could not find materialized view associated with a trigger or index that is being pulled from the master site.

Action: Ensure that materialized view, master, and master index or trigger is registered as replicated objects.

ORA-23393: the user is already the propagator

Cause: The given user is already the current propagator.

Action: None

ORA-23394: duplicate propagator

Cause: More than one valid propagator exist.

Action: Unregister any duplicate propagator.

ORA-23395: object “string“.”string” of type “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-23396: database link “string” does not exist or has not been scheduled

Cause: the database link does not exist in the schema of the replication propagator or has not been scheduled.

Action: Ensure that the database link exists in the database, is accessible and is scheduled for execution.

ORA-23397: global name “string” does not match database link name “string“

Cause: the database link name at the local node does not match the global name of the database that the link accesses.

Action: Ensure that global names is set to true and the link name matches the global name.

ORA-23398: user name “string” at database link “string” does not match local user name “string“

Cause: the user name of the replication administration user at the local node and the user name at the node corresponding to the database link are not the same. Symmetric replication expects the two users to be the same.

Action: Ensure that the user ID of the replication administration user at the local node and the user ID at the node corresponding to the database link are the same.

ORA-23399: generation of replication support for “string“.”string” is not complete

Cause: Replication support for the specified object has not been generated or the generation process is not yet complete.

Action: Ensure that replication support has been generated for the object. Use DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT() to generate replication support for the object.

ORA-23400: invalid materialized view name “string“

Cause: A null, misspelled, or badly formed materialized view name was given to dbms_mview.refresh.

Action: Provide a valid materialized view name to dbms_mview.refresh.

10 total views, no views today

Follow