Oracle Error Messages: 04/15/12

Sunday 15 April 2012

ORA-23444: duplicate template parameter

ORA-23444: duplicate template parameter

Cause: The template parameter already exists for the specified refresh group template.

Action: Correct the template parameter value and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the name of the refresh group template and parameter name.

ORA-23443: missing template parameter

ORA-23443: missing template parameter

Cause: The specified template parameter does not exist.

Action: Correct the template parameter value and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the name of the refresh group template and parameter name.

ORA-23442: object already exists for the refresh group template

ORA-23442: object already exists for the refresh group template

Cause: The specified object already exists in the refresh group template.

Action: Change the object name and object type parameters. Query the DBA_ REPCAT_REMPLATE_OBJECTS view to verify the correct name and type of the object.

ORA-23441: object does not exist for refresh group template

ORA-23441: object does not exist for refresh group template

Cause: The specified object does not exist in the refresh group template.

Action: Correct the object name and object type parameters. Check the DBA_ REPCAT_TEMPLATE_OBJECTS view to verify the correct name and type of the object.

ORA-23440: incorrect public template value

ORA-23440: incorrect public template value

Cause: The public template parameter is not Y , N or NULL.

Action: Correct the value of the public template parameter. It must be Y , N or NULL.

ORA-23439: refresh group template already exists

ORA-23439: refresh group template already exists

Cause: The specified refresh group template already exists.

Action: Verify that the refresh group template exists by querying the DBA_ REPCAT_REFRESH_TEMPLATES view.

ORA-23438: missing refresh group template

ORA-23438: missing refresh group template

Cause: The specified refresh group template does not exist.

Action: Verify that the refresh group template does not exist by querying the DBA_REPCAT_REFRESH_TEMPLATES view.

ORA-23437: template authorization already exists for user

ORA-23437: template authorization already exists for user

Cause: The specified user already has been authorized to use the specified refresh group template.

Action: Check the values for user name and refresh template name or query the DBA_REPCAT_USER_AUTHORIZATIONS view to ensure that the correct values were passed as parameters.

ORA-23436: missing template authorization for user

ORA-23436: missing template authorization for user

Cause: The specified template authorization does not exist.

Action: Check the values for user name and refresh template name to ensure a valid row exists in the DBA_REPCAT_USER_AUTHORIZATIONS view.

ORA-23435: cannot create an updatable ROWID materialized view with LOB columns

ORA-23435: cannot create an updatable ROWID materialized view with LOB columns

Cause: The propagation of LOB data from materialized view sites to the master site requires a primary key on the replicated table. Thus updatable ROWID materialized views that contain LOB columns are not supported.

Action: Create a primary key materialized view instead of a ROWID materialized view. If the materialized view already exists, it can be converted to a primary key materialized view using the ALTER MATERIALIZED VIEW DDL command.

ORA-23434: master site string not known for object group

ORA-23434: master site string 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_og.begin_instantiation() routine to add a new site to the replicated object group.

ORA-23433: executing against wrong master site string

ORA-23433: executing against wrong master site string

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-23432: master site string already exists

ORA-23432: master site string 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-23431: wrong state: string

ORA-23431: wrong state: string

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-23430: argument string cannot be NULL or empty string

ORA-23430: argument string 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-23428: job associated instance number string is not valid

ORA-23428: job associated instance number string is not valid

Cause: A job is associated with an instance that is not running.

Action: Choose a running instance for job affinity, or set force parameter to TRUE.

ORA-23427: deferred purge queue argument string out of range

ORA-23427: deferred purge queue argument string out of range

Cause: Specified numeric argument to dbms_defer_sys.purge_queue is invalid.

Action: Fix the argument value and try again.

ORA-23426: deferred RPC queue has entries for string

ORA-23426: deferred RPC queue has entries for string

Cause: The requested action cannot be performed until the queue is empty for the given site or dblink

Action: Use dbms_defer_sys.push, dbms_defer_sys.purge_queue or dbms_defer_ sys.delete_tran to empty the queue.

ORA-23425: invalid materialized view identifier string

ORA-23425: invalid materialized view identifier string

Cause: The argument provided to dbms_mview.purge_mview_from_log is an invalid materialized view identifer or it does not identify an Oracle 8 fast refreshable materialized view or the materialized view has been already purged.

Action: If the materialized view is an Oracle 8 fast refreshable materialized view then provide purge_mview_from_log with its valid materialized view identifier.

ORA-23424: materialized view string . string at string not registered

ORA-23424: materialized view string . string at string not registered

Cause: The specified materialized view has not be successfully registered at this site.

Action: Register the materialized view manually at either the master site or the materialized view site.

ORA-23423: job number string is not positive

ORA-23423: job number string is not positive

Cause: The given job number is less than 1.

Action: Choose a positive integer.

ORA-23422: Oracle Server could not generate an unused job number

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-23421: job number string is not a job in the job queue

ORA-23421: job number string 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-23420: interval must evaluate to a time in the future

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-23419: regenerate replication support before resuming master activity

ORA-23419: regenerate replication support before resuming master activity

Cause: There are tables in the object group that require regeneration of replication support.

Action: Check the generation_status column in the all_repobjects view. Regenerate replication support for any table in the object group with a NEEDSGEN status. Resume master activity.

ORA-23418: cannot unregister the propagator who is currently in use

ORA-23418: cannot unregister the propagator who is currently in use

Cause: The propagator is currently used in propagating replication RPCs.

Action: Try again later when there is no transaction active in propagating replication RPCs.

ORA-23417: unknown materialized view type: string

ORA-23417: unknown materialized view type: string

Cause: A fast refresh is being performed on a materialized view of an unknown or unsupported type.

Action: Check all_mviews and ensure that the materialized view being refreshed a valid materialized view.

ORA-23416: table string . string does not contain a primary key constraint

ORA-23416: table string . string does not contain a primary key constraint

Cause: The master table does not constaint a primary key constraint or the primary key constraint has been disabled.

Action: Create a primary key constraint on the master table or enable the existing constraint.

ORA-23415: materialized view log for string . string does not record the primary key

ORA-23415: materialized view log for string . string does not record the primary key

Cause: A primary key materialized view is being fast refreshed, but the materialized view log does not record primary key information.

Action: Use the CREATE MATERIALIZED VIEW LOG...ADD PRIMARY KEY command to begin recording primary key information in the materialized view log.

ORA-23414: materialized view log for string . string does not record rowid values

ORA-23414: materialized view log for string . string does not record rowid values

Cause: A rowid materialized view is being fast refreshed, but the materialized view log does not record rowid information.

Action: Use the CREATE MATERIALIZED VIEW LOG...ADD ROWID command to begin recording rowid information in the materialized view log.

ORA-23413: table string . string does not have a materialized view log

ORA-23413: table string . string does not have a materialized view log

Cause: The fast refresh can not be performed because the master table does not contain a materialized view log.

Action: Use the CREATE MATERIALIZED VIEW LOG command to create a materialized view log on the master table.

ORA-23412: master table s primary key columns have changed

ORA-23412: master table s primary key columns have changed

Cause: The master table s primary key constraint was modified after the primary key materialized view was created.

Action: Drop and recreate the primary key materialized view

ORA-23411: materialized view string . string is not in refresh group string. string

ORA-23411: materialized view string . string is not in refresh group string. string

Cause: The specified materialized view is not in the specified refresh group.

Action: Try again with the proper materialized view and refresh group names.

ORA-23410: materialized view string . string is already in a refresh group

ORA-23410: materialized view string . string is already in a refresh group

Cause: A materialized view of the same name is already in a refresh group.

Action: Subtract the materialized view from the current refresh group and add it to its new refresh group, or combine the two refresh groups into a single refresh group.

ORA-23409: could not find an unused refresh group number

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-23408: this replication operation is not supported in a mixed configuration

ORA-23408: this replication operation is not supported in a mixed configuration

Cause: operation is not supported if the object group is replicated at a pre-V8 node.

Action: Ensure that all nodes of the replicated object group are V8.

ORA-23407: object name string must be shaped like schema . object or object

ORA-23407: object name string must be shaped like schema . object or object

Cause: The object name (e.g., the rollback segment, the materialized view name, the refresh group) was incorrectly specified.

Action: Retry the operation with the object name properly specified (like schema. object or object )

ORA-23406: insufficient privileges on user string

ORA-23406: insufficient privileges on user string

Cause: The caller is not the owner of the materialized view and does not have ALTER ANY MATERIALIZED VIEW privileges.

Action: Perform the operation as the owner of the materialized view or as a user with ALTER ANY MATERIALIZED VIEW privileges.

ORA-23405: refresh group number string does not exist

ORA-23405: refresh group number string 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-23404: refresh group string . string does not exist

ORA-23404: refresh group string . string 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-23403: refresh group string . string already exists

ORA-23403: refresh group string . string already exists

Cause: Making a new refresh group when there is already a group of the same name in sys.rgroup$.

Action: Choose a diifferent refresh group name.

ORA-23402: refresh was aborted because of conflicts caused by deferred txns

ORA-23402: refresh was aborted because of conflicts caused by deferred txns

Cause: There are outstanding conflicts logged in the DefError table at the materialized view 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 materialized view s changes appearing to be temporarily lost (until a refresh succeeds after the conflicts are resolved).

ORA-23401: materialized view string . string does not exist

ORA-23401: materialized view string . string does not exist

Cause: A materialized view name was given to dbms_mview.refresh that is not in sys.snap$ or its associated views.

Action: Provide a materialized view name that is in sys.snap$, all_mviews or user_mviews.

ORA-23400: invalid materialized view name string

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.

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

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-23398: user name string at database link string does not match local user name string

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-23397: global name string does not match database link name string

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-23396: database link string does not exist or has not been scheduled

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-23395: object string . string of type string does not exist or is invalid

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-23394: duplicate propagator

ORA-23394: duplicate propagator

Cause: More than one valid propagator exist.

Action: Unregister any duplicate propagator.

ORA-23393: the user is already the propagator

ORA-23393: the user is already the propagator

Cause: The given user is already the current propagator.

Action: none

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

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.