Oracle7 Server Messages

Contents Index Home Previous Next

23300-24299: DBMS PL/SQL Packages

ORA-23300 application_specific_message

Cause:The stored procedure RAISE_SYSTEM_ERROR was called to generate this message.
Action:Correct the problem described in the message or contact the application programmer or database administrator for more information.
ORA-23301 mixed use of deferred RPC destination modes

Cause:Replication catalog determined deferred remote procedure call 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 deferred remote procedure call.
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 deferred remote procedure call.
Action:Dependent on application.
ORA-23304 malformed deferred RPC at arg name of name in call name, in tid name

Cause:A deferred remote procedure call was issued without the correct number of arguments as determined by the count parameter DBMS_DEFER.CALL.
Action:Ensure the number of arguments matches the count.
ORA-23305 internal deferred RPC error: str

Cause:An internal error occurred in the deferred remote procedure call.
Action:Contact customer support.
ORA-23306 schema "name" 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 "name" already exists

Cause:The given database already replicates the given schema.
Action:Choose a different schema or a different database.
ORA-23308 object "name.name" 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 "name.name" of type name 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 a repobject in another object group.
Action:Remove the offending object with the SQL DROP command, unregistered 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 "name" 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-23311 object group "name" is quiesced

Cause:SUSPEND_MASTER_ACTIVITY has been called before the object group has resumed normal operation.
Action:If a RESUME_MASTER_ACTIVITY request is pending, wait until it completes, and then reinvoke SUSPEND_MASTER_ACTIVITY.

ORA-23312 not the masterdef according to name

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 "name" is not mastered at name

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_SNAPSHOT_MASTER if the invocation database is a snapshot site.

ORA-23314 database is not a snapshot site for name

Cause:The invocation database is not a snapshot database for the given object group.
Action:Connect to the desired snapshot database and retry the request, or make the invocation database a snapshot site with CREATE_SNAPSHOT_REPSCHEMA or CREATE_SNAPSHOT_REPGROUP.
ORA-23315 repcatlog version or request name is not supported by version name

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 name

Cause:One of the masters to be removed is the masterdef.
Action:Relocate the masterdef to a master that will not be removed, and then reinvoke the REMOVE_MASTER_DATABASES request at the new masterdef.
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 name 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 name and name

Cause:A missing DDL record for a REPCATLOG record, or inconsistency in REPCAT views.
Action:Retry the request, or make the views consistent.
ORA-23323 parameter length exceeds deferred remote procedure call limits

Cause:A deferred remote procedure call parameter was longer than the deferred remote procedure call limit of 2000 bytes for CHAR/VARCHAR2 parameters and 255 bytes for raw parameters.
Action:Use smaller parameters.
ORA-23324 error num, while creating DEFERROR entry at name with error num

Cause:The given error was encountered while attempting to create a DEFEROR entry for the given error code and the given database.
Action:Correct the cause of the given error.
ORA-23325 parameter type is not type

Cause:A function in DBMS_DEFER_SYS_QUERY was called to retrieve a deferred remote procedure call parameter from the deferred remote procedure call 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 the system is being quiesced

Cause:A deferred remote procedure call operation was attempted while the database was quiesced.
Action:Resume database activity with the DBMS_REPCAT.RESUME_MASTER_ACTIVITY call.
ORA-23327 imported deferred remote procedure call data does not match id of importing db

Cause:Deferred remote procedure call queues were imported from a database with a different global name or operating system than the importing database.
Action:Deferred remote procedure call data should only be imported into a database with the same global name and hardware and operating system.
ORA-23328 snapshot base table name.name must be same as replicated master table

Cause:When creating a snapshot through repcat, the snapshot base table did not match a replicated table name at the master.
Action:Change the snapshot DDL to use the same base table as the replicated table name at the master.

ORA-23329 successful user-provided ddl but no snapshot name.name.

Cause:The DDL provided by the user to create a snapshot was executed without error, but snapshot does not exist.
Action:Manually back-out the DDL, and re-register with matching ddl and snapshot.

ORA-23330 column group name already exists

Cause:The column group was already registered in the object group.
Action:Use a column group name not yet registered in the object group.
ORA-23331 column group name does not exist

Cause:The given column group is either null, misspelled or not registered.
Action:Use a registered column group.
ORA-23332 group name 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 name 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 name does nor 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 name 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 name 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 name

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 name

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 is not already part of the priority group, or drop the value from 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 name

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 name

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, for example, for adding a comment.
Action:Specify a combination of column group, sequence, conflict type that has been registered.
ORA-23344 constraint name.name 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 name.name 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 is undefined for table name

Cause:Trying to generate replication support for a table without a primary key as defined by a constraint or DBMS_REPCAT_COLUMNS.
Action:Add a primary key constraint to the table or define a primary key using DBMS_REPCAT_COLUMNS.
ORA-23347 datatype name for column name table name 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 name; 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 name for procedure name 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 name

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 name

Cause:The execution of a deferred remote procedure call at the destination failed because its propagation was disabled.
Action:Enable deferred remote procedure call execution with the DBMS_DEFER_SYS.ENABLE call.
ORA-23355 object name.name 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, ensure the object is a valid object in all_repobject.

ORA-23360 only one snapshot for master table name can be created

Cause:An attempt to create more than one snapshot on a given master table in the same rep group.
Action:Create these other snapshots in a different rep group at another site.

ORA-23361 snapshot name does not exist at master site

Cause:The snapshot does not exist at the master site for offline instantiation of the snapshot.
Action:The correct procedure is to create the snapshot in a different schema at the master site, and then follow the instructions for offline instantiation of snapshots.

ORA-23363 mismatch of snap base table name at master and snap site

Cause:The name of the base table of the snapshot at the master site is different from the base table at the snapshot site. This error may arise during offline instantiation of snapshots.
Action:Retry offline instantiation with a snapshot name less than 24 bytes.

ORA-23364 replication option not installed

Cause:The replication option was not installed at this site. Updatable snapshots, deferred remote procedure calls, and other replication features were, therefore, unavailable.
Action:Install the replication option. The replication option is not part of the Oracle7 Server product and must be purchased separately. Contact an Oracle Sales representative if the replication option needs to be purchased.
ORA-23365 site name does not exist

Cause:The site specified in argument REFERENCE_SITE or argument COMPARISON_SITE in call to DIFFERENCES() routine or RECTIFY() routine did not name an existing site.
Action:Make sure that database sites specified really do exist, and re-run the routine.

ORA-23366 integer value num is less than 1

Cause:The 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 name is missing the primary key

Cause:The table specified in argument ONAME1 or ONAME2 in call to DIFFERENCES() routine did 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 name 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 the argument to a non-null or a non-empty string.

ORA-23369 value of \"name\" 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 name and table name are not shape equivalent name

Cause:The tables specified were not shape equivalent, which means intuitively that the number of columns, the names, their datatypes and lengths were not the same. Specifically, the problem was in the parentheses and was one of the following: the number of columns were not equal, datatypes of columns with same name in different tables were different, lengths of VARCHAR2 and CHAR columns were not equal, precision and scale of number datatypes were 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 name unknown in table name

Cause:Some column in ARRAY_COLUMNS argument (or COLUMN_LIST argument) to DIFFERENCES() routine did 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 name in table name is unsupported

Cause:Certain types in the table comparison utility were 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 name does not exist

Cause:The group name was null or misspelled, or the group did not exist locally.
Action:Specify the group correctly, or create it with DBMS_REPCAT.CREATE_MASTER_REGROUP().

ORA-23374 object group name already exists

Cause:The given database already replicated the given object group.
Action:Choose a different group or a different database.
ORA-23375 feature is incompatible with database version at num

Cause:A feature not compatible with the specified database was used.
Action:Set or raise the value of the COMPATIBLE parameter in the INIT.ORA file to match the necessary compatibility level.

ORA-23376 node name is not compatible with replication version \"name\"

Cause:A feature that was not compatible with the remote database was used.
Action:Upgrade the remote database and retry the operation.

ORA-23377 bad name name 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 name is not valid for object group name

Cause:The connection qualifier used in the database link for the specified object group does 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 name 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 name is not valid

Cause:The specified propagation is misspelled, or is not supported.
Action:Refer to the manual on replicated data for valid propagation modes.

ORA-23381 generated object for base object name.name@name 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.

ORA-23400 invalid snapshot name "name"

Cause:A null, misspelled, or badly formed snapshot name was given to DBMS_SNAPSHOT.REFRESH.
Action:Provide a valid snapshot name to DBMS_SNAPSHOT.REFRESH.
ORA-23401 snapshot "name.name" does not exist

Cause:A snapshot name was given to DBMS_SNAPSHOT.REFRESH that is not in SYS.SNAP$ or its associated views.
Action:Provide a snapshot name that is in SYS.SNAP$, ALL_SNAPSHOTS, or USER_SNAPSHOTS.
ORA-23402 refresh was aborted because of conflicts caused by deferred transactions

Cause:There are outstanding conflicts logged in the DEFERROR table at the snapshot's master.
Action:Resolve the conflicts in the master DEFERROR table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS set to TRUE, which will proceed with the refresh, even if there are conflicts in the master's DEFERROR table. Proceeding despite conflicts can result with an updatable snapshot's changes appearing to be temporarily lost, until a refresh succeeds after the conflicts are resolved.
ORA-23403 refresh group "name.name" already exists. Refresh group not a stored object?

Cause:Making a new refresh group when there is already a group of the same name in SYS.RGROUP$.
Action:Choose a different refresh group name.
ORA-23404 refresh group "name.name" does not exist

Cause:A refresh group name was given that is not in SYS.RGROUP$.
Action:Provide a refresh group name that is in SYS.RGROUP$ or DBS_RGROUP.
ORA-23405 refresh group number "name" does not exist

Cause:A refresh group number was given that is not in SYS.RGROUP$.
Action:Provide a refresh group number that is in SYS.RGROUP$ or DBS_RGROUP.
ORA-23406 insufficient privileges on user "name"

Cause:The caller is not the owner of the snapshot and does not have ALTER ANY SNAPSHOT privileges.
Action:Perform the operation as the owner of the snapshot or as a user with ALTER ANY SNAPSHOT privileges.
ORA-23407 object name "name" must be shaped like "SCHEMA.OBJECT" or "OBJECT"

Cause:The object name, for example, the rollback segment, the snapshot name, or the refresh group, was incorrectly specified.
Action:Retry the operation with the object name properly specified, like "SCHEMA.OBJECT" or "OBJECT".
ORA-23409 could not find an unused refresh group number

Cause:1000 consecutive refresh group numbers, as defined by the RGROUPSEQ number, were already used by rows in SYS.RGROUP$.
Action:Alter the sequence number to be within a legal unused range and destroy unneeded refresh groups.
ORA-23410 snapshot "name.name" is already in a refresh group

Cause:A snapshot of the same name is already in a refresh group.
Action:Subtract the snapshot its the current refresh group and add it to its new refresh group, or combine the two refresh groups into a single refresh group.
ORA-23411 snapshot "name.name" is not in refresh group "name.name"

Cause:The specified snapshot is not in the specified refresh group.
Action:Try again with the proper snapshot and refresh group names.
ORA-23420 interval must evaluate to a time in the future

Cause:The parameter INTERVAL evaluates to a time earlier than SYSDATE.
Action:Choose an expression that evaluates to a time later than SYSDATE.
ORA-23421 job number num is not a job in the job queue

Cause:There is no job visible to the caller with the given job number.
Action:Choose the number of a job visible to the caller.
ORA-23422 Oracle Server could not generate an unused job number

Cause:Oracle Server could not generate a job number that was not used to identify another job.
Action:Retry the operation.
ORA-23423 job number num is not positive

Cause:The given job number is less than 1.
Action:Choose a positive integer.
ORA-23430 argument name cannot be NULL or empty string

Cause:The caller has provided an argument whose value cannot be NULL or the empty string.
Action:Check that the VARCHAR2 value provided is not NULL or the empty string and retry the call.

ORA-23431 wrong state: name

Cause:The routine was executed against a replicated object group that was in the wrong state.
Action:Make sure that the replicated object group is in the state given in the error message.

ORA-23432 master site name already exists

Cause:An attempt was made to instantiate a replicated object group at a master site that was already a part of the object group.
Action:If you were trying to add this site, do nothing because it already exists; otherwise, pick the name of another site, and re-run the routine.

ORA-23433 executing against wrong master site name

Cause:An attempt was made to execute the routine at a site that is different from the site specified in the argument of the routine.
Action:Provide an argument to the routine that correctly indicates the site against which the routine should be executing.

ORA-23434 master site name not known for object group

Cause:The site name given as an argument to a routine was not already known to the replicated object group.
Action:Execute the DBMS_OFFLINE_SCHEMA.BEGIN_INSTANTIATION() routine to add a new site to the replicated schema.

ORA-24275 function name parameter name missing or invalid

Cause:The function <pkgname.funcname> was called with a parameter <parname> that was null, 0 length, or had an invalid value.
Action:Correct the parameter to supply values that comply with its datatype and limits as specified in the documentation.
ORA-24276 function name output name maximum value exceeded

Cause:The function <pkgname.funcname> computed a value for the output <parname> that exceeded the maximum allowed. This can occur when multiple input parameters, each valid separately, combine to specify an invalid result. For example, when a length parameter multiplied by a copies parameter yields a total length exceeding the maximum for the output datatype.
Action:Correct the input values to produce a result that will comply with the limits as specified in the documentation.

Contents Index Home Previous Next