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

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

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-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-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-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-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-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-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-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-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-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: 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-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-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-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-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-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-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-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-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-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-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 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-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 string is not positive

Cause: The given job number is less than 1.

Action: Choose a positive integer.

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-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-23426: deferred RPC queue has entries for string

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

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

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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-23445: missing template site

Cause: The template site specified by the site name, user name and refresh group template name does not exist.

Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing template sites.

ORA-23446: duplicate template site

Cause: The template site specified by the site name, user name and refresh group template name already exists.

Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing template sites.

ORA-23447: missing user parameter value

Cause: The user parameter value specified by the user name, parameter name and refresh group template name does not exist.

Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_USER_PARMS view to query the existing user parameters.

ORA-23448: duplicate user parameter value

Cause: The user parameter value specified by the user name, parameter name and refresh group template name already exists.

Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_USER_PARMS view to query the existing user parameters.

ORA-23449: missing user name

Cause: The user specified by the user name parameter does not exist in the database.

Action: Correct an invalid user name or create the user in the master database. Use the DBA_USERS view to select the valid database users.

ORA-23450: flavor already contains object “string“.”string“

Cause: The flavor already contains the specified object.

Action: Check that the specified object is correct. To add all columns of a table object, delete the object from the flavor and then add it again.

ORA-23451: flavor string already defined for object group “string“.”string“

Cause: The given object group already contains a (possibly unpublished) definition of the specified flavor.

Action: Check the spelling of the flavor name. Check for an unpublished flavor of the desired name.

ORA-23452: flavor string of object group “string“.”string” is already published

Cause: The given object group already contains a (published) definition of the specified flavor.

Action: Check the spelling of the flavor name.

ORA-23453: requested operation is not supported on top flavor

Cause: The TOP flavor has a NULL name and may not be directly defined or deleted.

Action: Supply the name of a flavor other than the TOP flavor or use dbms_repcat routines to implicitly change the TOP flavor.

ORA-23454: flavor string not defined for object group “string“.”string“

Cause: The given object group does not contain a (published) definition of the specified flavor.

Action: Check the spelling of the flavor name. Ensure the flavor has been defined (and published) for the object group.

ORA-23455: flavor string contains object “string“

Cause: The given flavor contains the object to be dropped.

Action: Purge the flavor or choose another object to drop.

ORA-23456: flavor string does not contain “string“

Cause: The flavor does not contain the given object, column, or attribute.

Action: Either drop the flavor or choose a different object, column, or attribute.

ORA-23457: invalid flavor ID string

Cause: The given flavor ID is invalid.

Action: Make sure this flavor has been instantiated. If the flavor ID is outside the range (-2147483647, 2147483647), contact customer support.

ORA-23458: inappropriate flavor string at string

Cause: The given flavor at the given database prevents the operation from succeeding.

Action: Either change the database flavor or choose a different operation.

ORA-23459: flavor string must contain “string“

Cause: The flavor must contain the given object, column, or attribute.

Action: Either choose a different database flavor or ensure the object, column, or attribute is available.

ORA-23460: missing value for column string in resolution method “string” for “string“.”string“.”string“

Cause: before resolving conflicts, some values necessary resolving conflicts are not available, or after resolving conflicts, some values necessary for re-trying of the SQL are not available

Action: define appropriate flavors, provide necessary values through availability vector in USER FLAVOR FUNCTION for conflict resolution

ORA-23462: flavor string in use at site string

Cause: The given flavor cannot be deleted because it is being used at the given site.

Action: Change the flavor of the site, or unregister it if it is a materialized view site.

ORA-23463: flavor incompatible with object “string“.”string“

Cause: An existing flavor includes the specified object with an incompatible type.

Action: Change the type of the object, or delete the flavor if it is not in use.

ORA-23464: flavor lacks column string of “string“.”string“

Cause: The flavor includes some columns of an object group but not all the required columns.

Action: Change the flavor definition to include all required columns.

ORA-23465: flavor already includes column string of “string“.”string“

Cause: The flavor includes the specified column which is being added.

Action: Check that the specified column is correct.

ORA-23466: flavor requires missing object “string“.”string“

Cause: The flavor includes the specified object which does not exist

Action: Check that the specified object name is correct, and create the object if appropriate.

ORA-23467: flavor lacks object “string“.”string“

Cause: The flavor does not include the specified object which is being dropped.

Action: Check that the specified object is correct.

ORA-23468: missing string string

Cause: The template is missing the object with the specified key.

Action: Add the object to the template.

ORA-23469: string is different between templates

Cause: The values for the specified columns are different in each template for the same key values.

Action: Correct the column values to make the templates the same.

ORA-23470: invalid status

Cause: The status should be DELETED, INSTALLING or INSTALLED. Any other status is invalid.

Action: Check that the specified status value is correct.

ORA-23471: template not authorized for user

Cause: The refresh template is private and the user has not been authorized to instantiate the template.

Action: Authorize the user to use the template.

ORA-23472: materialized view “string“.”string” must be atomically refreshed

Cause: Non-atomic refresh is not supported for the specified materialized view.

Action: Set the value of the ATOMIC parameter to FALSE in the refresh procedure being used or remove the specified materialized view from the set of materialized views being refreshed.

ORA-23473: replication RPC processing for “string“.”string” is disabled

Cause: The processing of replication RPCs for the object group that contains this object is disabled. This includes RPCs in the error queue.

Action: Processing of replication RPCs is disabled when the object group is being offline instantiated. Wait until offline instantiation is finished.

ORA-23474: definition of “string“.”string” has changed since generation of replication support

Cause: The current columns in the specified table and their column types do not match the columns and column types when replication support was last generated.

Action: Regenerate replication support for the affected table. All flavors that include the specified table should be checked for validity. Types for any UDT columns should also be checked for validity.

ORA-23475: key column string must be sent and compared

Cause: The specified column is a key column and must be sent and compared during replication propagation.

Action: Make sure every key column is sent and compared.

ORA-23476: cannot import from string to string

Cause: This object was imported from a database with a different global name than the importing database.

Action: Only import this object into a database with the same global name.

ORA-23477: unable to alter propagation mode for object group “string“.”string“

Cause: The propagation method of a materialized view object group can only be altered when no other object groups with the same master object group are sharing the materialized view site.

Action: Ensure that there are no other materialized view object groups at the local site with the same master object group.

ORA-23478: object group “string” is already mastered at string

Cause: There is at least one other materialized view repgroup at the local site with the same group name but a different master site.

Action: Ensure that all materialized view repgroups at the local site with the same group name have the same master.

ORA-23480: Column string is not a top-level column of “string“.”string“.

Cause: The column is either not a top-level column or is not present in the table or materialized view.

Action: Ensure only valid top-level columns are used.

ORA-23482: column string of “string“.”string“: object types not allowed.

Cause: The column is of Object Type.

Action: Ensure that all the columns are not of Object Type.

ORA-23483: object “string“.”string” not allowed in this operation.

Cause: The specified operation does not support the given object.

Action: Do not invoke the operation for this object.

ORA-23484: internal internet Application Server error: string

Cause: An internal error occurred in internet Application Server.

Action: Report the error and other information to support.

ORA-23485: Column group “string” must consist of a single numeric column only

Cause: The column group doesn’t contain only one numeric column.

Action: Use a column group containing a single numeric column.

ORA-23487: object groups “string“.”string” and “string“.”string” do not have the same connection qualifier

Cause: The specified two object groups do not have the same connection qualifier.

Action: Do not invoke the operation on the above object groups, or ensure they have the same connection qualifier.

ORA-23488: propagation mode “string” for “string” is not allowed for this operation

Cause: This operation does not support the specified dblink in the above propagation mode.

Action: Do not invoke the operation for this dblink, or change the propagation mode for this dblink.

ORA-23489: duplicate entry “string“

Cause: The specified value is duplicated in the parameter list.

Action: Remove duplicated entries in the parameter list.

ORA-23490: extension request “string” with status “string” not allowed in this operation

Cause: The specified operation is not allowed for the extension request with the specified status.

Action: Ensure the extension request has the appropriate status before retrying this operation.

ORA-23491: no valid extension request at “string“

Cause: The specified database does not have a valid extension request.

Action: Ensure there is a valid extension request in DBA_REPEXTENSIONS view before retrying this operation.

ORA-23492: no new sites for extension request “string“

Cause: There is no new site with the specified extension request.

Action: Ensure there is at least one new site in DBA_REPSITES_NEW view for this request before retrying this operation.

ORA-23493: “string” is not a new site for extension request “string“

Cause: The specified extension request does not include the specified site as a new site.

Action: Ensure the specified site is a new site for this extension request before retrying this operation.

ORA-23494: too many rows for destination “string“

Cause: The specified destination has too many rows in system.def$_destination table.

Action: Ensure the specified destination has at most two valid rows before retrying this operation.

ORA-23495: serial propagation can not be used for “string“

Cause: The sites involved may be in the process of adding a new site without quiescing.

Action: Check the def$_destination table for this destination and try parallel propagation.

ORA-23496: can not change disabled status for “string” and “string“

Cause: The disabled status for this site is set internally for synchronization during adding a new master without quiescing.

Action: Ensure adding a new master without quiescing finished before invoking this procedure.

ORA-23497: repgroup name cannot be null

Cause: The array of Repgroup names contains a null value.

Action: Ensure that the array of Repgroup names is dense and is not null terminated.

ORA-23498: repgroups specified must have the same masters

Cause: The Repgroup names specified do not have the same masters.

Action: Ensure that the Repgroup names specified have the same masters.

ORA-23500: cannot switch master for a multi-tier materialized view repgroup “string“.”string“

Cause: An attempt was made to switch master for a materialized view repgroup when its parent repgroup is also a materialized view repgroup. This is not allowed.

Action: Drop and recreate the materialized view repgroup based on a proper parent repgroup.