ORA-31448: invalid value for change_source

ORA-31448: invalid value for change_source

Cause: The specified value was not a valid name for a Change Source.

Action: Specify a valid name and retry the command.

ORA-31447: cannot create change tables in the SYS schema

ORA-31447: cannot create change tables in the SYS schema

Cause: Attempted to create a change table in the SYS schema. This is not allowed.

Action: Use a different existing schema and retry the command.

ORA-31446: this session does not own the lock handle for string

ORA-31446: this session does not own the lock handle for string

Cause: CDC attempted to acquire a lock on the resource, does not own the the lock associated with the lock. This is an internal error.

Action: Contact Oracle corporation

ORA-31445: invalid lock handle while acquiring lock on string

ORA-31445: invalid lock handle while acquiring lock on string

Cause: CDC attempted to acquire a lock on the resource, but encountered a invalid lock handle, which did not correspond to any existing handle.

Action: Contact Oracle corporation

ORA-31444: parameter error while acquiring lock on string

ORA-31444: parameter error while acquiring lock on string

Cause: CDC attempted to acquire a lock on the resource, but encountered a problem passing parameters to the lock manager.

Action: Contact Oracle corporation

ORA-31443: deadlock detected while acquiring lock on string

ORA-31443: deadlock detected while acquiring lock on string

Cause: CDC attempted to acquire a lock on the resource, but encountered a deadlock.

Action: Contact Oracle corporation

ORA-31442: operation timed out while acquiring lock on string

ORA-31442: operation timed out while acquiring lock on string

Cause: CDC attempted to acquire a lock on the resource, but the operation timed out.

Action: Retry the operation later.

ORA-31441: table is not a change table

ORA-31441: table is not a change table

Cause: User attempted to execute the DROP_CHANGE_TABLE procedure on a table that is not a CHANGE table. This can also occur when a CHANGE table object has been orphaned. CHANGE tables can become orphaned after a CREATE_CHANGE_TABLE failure or an incomplete DROP_CHANGE_TABLE.

Action: Check spelling. If error was due to an incorrect name, then retry the procedure using the correct name. To drop a table that is not a CHANGE table, or an orphaned CHANGE table, use the DROP TABLE DDL command instead.

ORA-31440: change set string is empty and cannot be advanced

ORA-31440: change set string is empty and cannot be advanced

Cause: User attempted to advance a change set which does not contain any change tables. Without change tables, a change set cannot be advanced.

Action: Create change tables in the change set, then retry the advance.

ORA-31439: subscription is already active

ORA-31439: subscription is already active

Cause: The subscription is already active.

Action: Check name and retry.

ORA-31438: duplicate change table string

ORA-31438: duplicate change table string

Cause: A change table by the specified name already exists.

Action: Recreate the change table with a unique name.

ORA-31437: duplicate change set string

ORA-31437: duplicate change set string

Cause: A change set by the specified name already exists.

Action: Recreate the change set with a unique name.

ORA-31436: duplicate change source string

ORA-31436: duplicate change source string

Cause: A change source by the specifed name already exists.

Action: Recreate the change source with a unique name.

ORA-31435: an error occurred during the purge operation

ORA-31435: an error occurred during the purge operation

Cause: An error occurred during the purge operation

Action: Check the logfile for a more detailed report of the underlying errors.

ORA-31434: purge is currently running

ORA-31434: purge is currently running

Cause: Called the PURGE procedure while a purge job was currently running.

Action: Wait for purge to complete before reissueing this command.

ORA-31433: subscriber view does not exist

ORA-31433: subscriber view does not exist

Cause: The subscription did not contain this subscriber view.

Action: Recheck the name, and specify the name of an existing subscriber view.

ORA-31432: invalid source table

ORA-31432: invalid source table

Cause: Either the schema_name.source_table did not exist or it did not belong to this subscription.

Action: Check the spelling of the schema_name and source_table. Verify that the specifed table exists in the specifed schema and is subscribed to by the subscription.

ORA-31431: all source tables must belong to the synchronous change set

ORA-31431: all source tables must belong to the synchronous change set

Cause: Not all of the source tables belong to the synchronous change set.

Action: Check the spelling of the source tables. Make sure that all of the source tables belong to the synchronous change set.

ORA-31430: subscriber view exists

ORA-31430: subscriber view exists

Cause: A view that is already in use was specified for the subscriber view.

Action: Call the SUBSCRIBE procedure using a different subscriber view name.

ORA-31429: subscription has not been activated

ORA-31429: subscription has not been activated

Cause: The called procedure required an activated subscription.

Action: Check the subscription name and correct if necessary. Call the ACTIVATE_SUBSCRIPTION procedure for this subscription and then reissue the original command.

ORA-31428: no publication contains all the specified columns

ORA-31428: no publication contains all the specified columns

Cause: One or more of the specifed columns cannot be found in a single publication.

Action: Change the subscription request to select only columns that are in the same publication. Consult the USER_PUBLISHED_COLUMNS view to see current publications.

ORA-31427: publication string already subscribed

ORA-31427: publication string already subscribed

Cause: The subscription already contained this publication.

Action: Check the values of subscription_name and publication_id. Check any other subscribe calls to see if they subscribe to columns that are shared among more than one publication on the same source table. Do not attempt to subscribe to the same publication more than once in the same subscription. Use the publication_id variant of the SUBSCRIBE call if needed to specify precise publications.

ORA-31426: cannot modify active subscriptions

ORA-31426: cannot modify active subscriptions

Cause: The subscription was already activated so that additional calls to SUBSCRIBE were prohibited.

Action: Subscribe to all the desired tables and columns before activating the subscription. Ensure that the correct subscription name is specifed.

ORA-31425: subscription does not exist

ORA-31425: subscription does not exist

Cause: The subscription either did not exist or did not belong to this user.

Action: Call the function again with a valid subscription name.

ORA-31424: change table has active subscriptions

ORA-31424: change table has active subscriptions

Cause: The change table is subscribed to, so it cannot be dropped.

Action: Do not drop a change table while there are active subscribers. If this is an emergency, use the FORCE parameter. This will forcibly drop the change table out from under all subscribers.

ORA-31423: change table string does not contain column string

ORA-31423: change table string does not contain column string

Cause: Issued ALTER_CHANGE_TABLE with a drop operation and the specified column does not exist in the change table.

Action: Recheck the names, and call the procedure again.

ORA-31422: owner schema string does not exist

ORA-31422: owner schema string does not exist

Cause: Value specifed for the owner parameter does not contain the name of an existing schema in the database.

Action: Recheck the name, and call the procedure again using an existing schema name.

ORA-31421: change table does not exist

ORA-31421: change table does not exist

Cause: Specified change table does not exist.

Action: Recheck the name, and call the procedure again using an existing change table.

ORA-31420: unable to submit the purge job

ORA-31420: unable to submit the purge job

Cause: When creating the first change table, a purge job is submitted to the job queue. Submission of this purge job failed.

Action: Make sure that job queue processes are enabled and are currently running. If this does not solve the problem, contact Oracle.

ORA-31419: source table string does not exist

ORA-31419: source table string does not exist

Cause: When creating a synchronous change table, the underlying source table must exist when the procedure is called. In this case, the source table did not exist.

Action: Specify the name of an existing table.

ORA-31418: source schema string does not exist

ORA-31418: source schema string does not exist

Cause: Trying to create a synchronous change table and the source schema did not match any existing schema names in the database.

Action: Specify the name of an existing schema.

ORA-31417: column list contains control column string

ORA-31417: column list contains control column string

Cause: Reserved column name was specified in a column list or column type parameter.

Action: Control columns are selected with separate parameters. If you did not want a control column, then change the name of the specified column so that it does not conflict with a reserved column name.

ORA-31416: invalid SOURCE_COLMAP value

ORA-31416: invalid SOURCE_COLMAP value

Cause: A source_colmap value of y was specified for an asynchronous change table.

Action: Specify a source_colmap parameter value of n and call the procedure again.

ORA-31415: change set string does not exist

ORA-31415: change set string does not exist

Cause: Specified change set does not exist or the user does not have access to the publications in that change set. The name specified did not match the name of any existing change set. Certain privileges are required to access the publications within that change set.

Action: Check the name and call the procedure again, with the name of an existing change set. Contact the publisher or database administrator if user privileges are required to access the publications in the change set.

ORA-31414: error(s) occurred during change table advance

ORA-31414: error(s) occurred during change table advance

Cause: One or more errors occurred during the advance operation.

Action: Check the log file(s) for a more detailed report of the underlying errors.

ORA-31413: change set string is currently being advanced

ORA-31413: change set string is currently being advanced

Cause: An advance operation is in progress for this change set and we only allow one at a time.

Action: Since the change set is currently being advanced, the best action is to wait for it to finish advancing. Only one caller at a time can advance the change set. Check for the cause of long running advance operations.

ORA-31412: change set string is disabled and cannot be advanced

ORA-31412: change set string is disabled and cannot be advanced

Cause: The specified change set is disabled. The change set needs to be enabled for the operation to succeed.

Action: Determine why the change set is disabled and correct this condition. Alter the change set specifying y for advance_enable then retry the operation.

ORA-31411: change set string is referenced by a change table

ORA-31411: change set string is referenced by a change table

Cause: The operation cannot be performed because the change set contains one or more change tables.

Action: You will need to drop the change table(s) first, then repeat the operation

ORA-31410: change set string is not an existing change set

ORA-31410: change set string is not an existing change set

Cause: Could not find an existing change set by this name.

Action: Check the spelling of the change set name. Call the procedure again, passing the correct change set name.

ORA-31409: one or more values for input parameters are incorrect

ORA-31409: one or more values for input parameters are incorrect

Cause: One or more of the inputs to the procedure had invalid values.

Action: Identify the bad parameter(s) and supply correct values to the procedure.

ORA-31408: invalid value specified for begin_scn or end_scn

ORA-31408: invalid value specified for begin_scn or end_scn

Cause: The begin_scn was not greater than zero. The end_scn was less than zero. The end_scn was less than the begin_scn.

Action: Check the values of both begin_scn and end_scn. Correct them to make sure that they form a legal SCN range. An end_scn value of zero indicates an infinite scn range.

ORA-31407: end_date must be greater than the begin_date

ORA-31407: end_date must be greater than the begin_date

Cause: The end data of the change set is earlier than the begin date. The end date must always be later in time than the begin date, so that the duration between the begin and end dates is a positive amount of time.

Action: Change the begin date and or or the end date, so that the end date is later than the begin date.

ORA-31406: change source string is referenced by a change set

ORA-31406: change source string is referenced by a change set

Cause: The operation cannot complete because this change source is referenced by one or more change sets.

Action: Drop the change sets first, then re-issue the command. May have to drop some change tables before the change sets are dropped.

ORA-31405: cannot make changes while change set string is advancing

ORA-31405: cannot make changes while change set string is advancing

Cause: The change set is currently advancing. Change sources related to an advancing change set cannot be altered. Change tables related to the advancing change set cannot be created, altered or dropped. Some or all the parameters of the change set cannot be altered while the set is advancing.

Action: Wait until the change set has finished advancing, then reissue the command. If altering the change set, only the advance_enable parameter can be altered during an advance.

ORA-31404: all input parameters are null

ORA-31404: all input parameters are null

Cause: All input parameters are null. At least one property must be altered.

Action: Call the procedure again, making sure that all the required parameters have been specified. Ensure that at least one parameter is not null. Refer to user documentation for the correct way of calling this procedure.

ORA-31403: change table string already contains a column string

ORA-31403: change table string already contains a column string

Cause: Issued ALTER_CHANGE_TABLE with an add operation but a column by this name already exists in the specified table.

Action: Check the names and call the procedure again.

ORA-31402: unrecognized parameter string

ORA-31402: unrecognized parameter string

Cause: Unrecognized parameter was detected.

Action: Check for too many parameters in the call.

ORA-31401: change source string is not an existing change source

ORA-31401: change source string is not an existing change source

Cause: The caller did not use the name of an existing change source. The name given does not match the name of any existing change source.

Action: Check the spelling of the change source name. Choose an existing change source.

ORA-31399: Cannot contact LDAP server string at port number

ORA-31399: Cannot contact LDAP server string at port number

Cause: The LDAP server specified could not be contacted. This can happen if the server is down or inaccessible.

Action: Contact the administrator of the LDAP server or or or or or or or or or or or or or or or or or or or or or or or or or or End of DBMS_LDAP OiD messages

ORA-31398: DBMS_LDAP: Shared servers are not supported.

ORA-31398: DBMS_LDAP: Shared servers are not supported.

Cause: The session executing functions from the DBMS_LDAP package is being handled by a shared server in the Database.

Action: Use dedicated database sessions to execute functions in the DBMS_LDAP package.

ORA-31232: DBMS_LDAP: invalid MOD_PROPERTY_SET

ORA-31232: DBMS_LDAP: invalid MOD_PROPERTY_SET

Cause: An attempt was made by a PL or SQL module to use a MOD_PROPERTY_ SET which is not valid and might have already been freed.

Action: Check the MOD_PROPERTY_SET in PL or SQL module involving DBMS_ LDAP.

ORA-31231: DBMS_LDAP: invalid PROPERTY_SET

ORA-31231: DBMS_LDAP: invalid PROPERTY_SET

Cause: An attempt was made by a PL or SQL module to use a PROPERTY_SET which is not valid and might have already been freed.

Action: Check the PROPERTY_SET in PL or SQL module involving DBMS_LDAP.

ORA-31230: DBMS_LDAP: unable to dynamically allocate additional memory

ORA-31230: DBMS_LDAP: unable to dynamically allocate additional memory

Cause: An error occured during dynamic memory allocation from session heap.

Action: Verify that adequate memory resources are available.

ORA-31229: DBMS_LDAP: invalid input parameter

ORA-31229: DBMS_LDAP: invalid input parameter

Cause: An invalid argument has been passed by a PL or SQL module to a DBMS_ LDAP subprogram

Action: Check the input argument to the DBMS_LDAP subprogram in PL or SQL module involving DBMS_LDAP.

ORA-31228: DBMS_LDAP: invalid MOD_ARRAY

ORA-31228: DBMS_LDAP: invalid MOD_ARRAY

Cause: An attempt was made by a PL or SQL module to use a MOD_ARRAY which is not valid and might have already been freed.

Action: Check the MOD_ARRAY in PL or SQL module involving DBMS_LDAP.

ORA-31227: DBMS_LDAP: invalid LDAP MESSAGE handle

ORA-31227: DBMS_LDAP: invalid LDAP MESSAGE handle

Cause: An attempt was made by a PL or SQL module to use an LDAP MESSAGE handle which is not valid and might have already been freed.

Action: Check the LDAP MESSAGE handle in PL or SQL module involving DBMS_ LDAP.

ORA-31226: DBMS_LDAP: MOD_ARRAY size limit exceeded

ORA-31226: DBMS_LDAP: MOD_ARRAY size limit exceeded

Cause: An attempt was made by a PL or SQL module to add an element beyond the MOD_ARRAY size limit.

Action: Increase the MOD_ARRAY size limit in PL or SQL module involving DBMS_LDAP.

ORA-31225: DBMS_LDAP: invalid BER_ELEMENT

ORA-31225: DBMS_LDAP: invalid BER_ELEMENT

Cause: An attempt was made by a PL or SQL module to use a BER_ELEMENT which is not valid and might have already been freed.

Action: Check the BER_ELEMENT in PL or SQL module involving DBMS_LDAP.

ORA-31224: DBMS_LDAP: invalid LDAP session

ORA-31224: DBMS_LDAP: invalid LDAP session

Cause: An attempt was made by a PL or SQL module to use an LDAP session which is not valid and might have already been closed.

Action: Check the LDAP session handle in PL or SQL module involving DBMS_ LDAP.

ORA-31223: DBMS_LDAP: cannot open more than string LDAP server connections

ORA-31223: DBMS_LDAP: cannot open more than string LDAP server connections

Cause: An attempt was made to open more than the maximum allowed LDAP server connections.

Action: Free unused connections.