ORA-26675: cannot create Streams capture process string

ORA-26675: cannot create Streams capture process string

Cause: Streams capture process could not be created because one or more parameters contain invalid value.

Action: Refer to trace file for more details.

ORA-26674: Column mismatch in string.string (LCR: string type=string; DB: string type=string)

ORA-26674: Column mismatch in string.string (LCR: string type=string; DB: string type=string)

Cause: The columns in the LCR were not the same or not found in the database table.

Action: Alter the database table.

ORA-26673: duplicate column name string

ORA-26673: duplicate column name string

Cause: An attempt was made to specify a duplicate column name in an LCR.

Action: Remove the duplicate column and retry the operation.

ORA-26672: timeout occurred while stopping STREAMS process string

ORA-26672: timeout occurred while stopping STREAMS process string

Cause: Timeout occurred while waiting for a STREAMS process to shut down.

Action: Retry the operation. If the error persists, try stopping the process with the FORCE option, or contact Oracle Support Services.

ORA-26671: maximum number of STREAMS processes exceeded

ORA-26671: maximum number of STREAMS processes exceeded

Cause: Cannot create additional STREAMS processes since the maximum number of STREAMS processes has been reached.

Action: Remove existing STREAMS processes and retry the operation.

ORA-26670: STREAMS option requires COMPATIBLE parameter to be string or higher

ORA-26670: STREAMS option requires COMPATIBLE parameter to be string or higher

Cause: Streams requires compatibility to be 9.2.0 or higher.

Action: Shut down and restart with an appropriate compatibility setting.

ORA-26669: parameter string inconsistent with parameter string

ORA-26669: parameter string inconsistent with parameter string

Cause: An attempt was made to specify a subprogram parameter value that is inconsistent with another parameter value.

Action: Check the documentation for valid parameter values.

ORA-26668: STREAMS process string exists

ORA-26668: STREAMS process string exists

Cause: An attempt to remove the component failed because it is associated with the STREAMS process.

Action: Either remove the process manually or specify the cascade option in dbms_streams_adm.remove_queue.

ORA-26667: invalid STREAMS parameter string

ORA-26667: invalid STREAMS parameter string

Cause: An attempt was made to specify an invalid parameter.

Action: Check the documentation for valid parameters.

ORA-26666: cannot alter STREAMS process string

ORA-26666: cannot alter STREAMS process string

Cause: An attempt was made to alter a STREAMS process that is currently running.

Action: Stop the STREAMS process and reissue the command.

ORA-26665: STREAMS process string already exists

ORA-26665: STREAMS process string already exists

Cause: An attempt was made to create a STREAMS process that already exists.

Action: Either specify another STREAMS process or remove the existing STREAMS process.

ORA-26664: cannot create STREAMS process string

ORA-26664: cannot create STREAMS process string

Cause: An attempt was made to create a STREAMS process when another was being created concurrently.

Action: Wait for the creation of the other STREAMS process to finish before attempting to create the STREAMS process.

ORA-26663: error queue for apply process string must be empty

ORA-26663: error queue for apply process string must be empty

Cause: The error queue for this apply process contains error entries.

Action: Execute or delete errors in the error queue.

ORA-26662: unable to process STREAMS Data Dictonary information for object

ORA-26662: unable to process STREAMS Data Dictonary information for object

Cause: The database is unable to process STREAMS Data Dictionary for this object.

Action: Check that the compatibility for the database supports the object, and check the trace file for information about the object.

ORA-26660: Invalid action context value for string

ORA-26660: Invalid action context value for string

Cause: The value specified in the action context is invalid for use in STREAMS.

Action: Check that the type and value are correct.

ORA-26650: %s background process string might not be started successfully

ORA-26650: %s background process string might not be started successfully

Cause: An error occurred during creation of a capture or apply background process.

Action: Please review V$Capture and V$Apply_coordinator views for the status of these processes. Please also check the trace file for more information.

ORA-26577: PRESERVE TABLE can not be used when dropping old style materialized view string.string

ORA-26577: PRESERVE TABLE can not be used when dropping old style materialized view string.string

Cause: The materialized view consists of a view and a container table.

Action: Drop the materialized view without PRESERVE TABLE option.

ORA-26576: cannot acquire SR enqueue

ORA-26576: cannot acquire SR enqueue

Cause: An attempt to acquire the SR enqueue in exclusive mode failed.

Action: none

ORA-26575: remote database does not support replication parallel propagation

ORA-26575: remote database does not support replication parallel propagation

Cause: The remote database has a version lower than Oracle 8.0 and hence does not understand replication parallel propagation.

Action: Use serial propagation or upgrade the remote database to Oracle 8.0 or above.

ORA-26572: %s.string.string: argument string does not match replication catalog

ORA-26572: %s.string.string: argument string does not match replication catalog

Cause: the (rpc) call is corrupted

Action: examine total number of arguments and each argument for the rpc call

ORA-26571: %s.string.string: number of arguments (string) does not match replication catalog

ORA-26571: %s.string.string: number of arguments (string) does not match replication catalog

Cause: number of arguments does not match replication catalog

Action: examine total number of arguments for the rpc call

ORA-26566: Couldn t open connect to string

ORA-26566: Couldn t open connect to string

Cause: Failed to open connection using given dblink

Action: Make sure that the dblink is valid and remote m or c is up.

ORA-26565: Call to lamp;lt;lamp;nbsp;typelamp;gt;_arg made before calling dbms_defer.call

ORA-26565: Call to lamp;lt;lamp;nbsp;typelamp;gt;_arg made before calling dbms_defer.call

Cause: User invoked lamp;lt;lamp;nbsp;typelamp;gt;_arg procedure before starting a deferred call

Action: Invoke various procedures in the correct order.

ORA-26564: %s argument is not of specified type

ORA-26564: %s argument is not of specified type

Cause: User passed type of the given argument number doesn t match with the type of the argument in the stored arguments.

Action: Invoke correct type procedure (i.e. get_XXX_arg)

ORA-26563: renaming this table is not allowed

ORA-26563: renaming this table is not allowed

Cause: Attempt to rename a replicated table, an updatable materialized view table or the master table of a materialized view for which a materialized view log has beencreated.

Action: If desired, unregister the replicated table with dbms_repcat.drop_master_ repobject, or use the recommended procedure to rename the master table of a materialized view.

ORA-26536: refresh was aborted because of conflicts caused by deferred transactions

ORA-26536: refresh was aborted because of conflicts caused by deferred transactions

Cause: There are outstanding conflicts logged in the DEFERROR table at the materialized view s master site.

Action: Resolve the conflicts in the master DEFERROR table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS, even if there are conflicts in the master s DEFERROR table. Proceeding despite conflicts can result in an updatable materialized view s changes appearing to be temporarily lost, until a refresh succeeds after the conflicts are resolved.

ORA-26535: %ud byte row cache insufficient for table with rowsize=number

ORA-26535: %ud byte row cache insufficient for table with rowsize=number

Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site.

Action: Increase the RepAPI row buffer size or reduce the width of the replicated tables.

ORA-26534: collision: tranID number ignored and purged

ORA-26534: collision: tranID number ignored and purged

Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site.

Action: See the action section for E_QUEUESYNC (26518).

ORA-26532: replication parallel push simulated site failure

ORA-26532: replication parallel push simulated site failure

Cause: A parallel push executed with event 26531 enabled raises this error to simulation failure of network or destination site.

Action: Do not enable the event for normal operation.

ORA-26530: unable to build materialized view refresh control list

ORA-26530: unable to build materialized view refresh control list

Cause: The materialized view control list could not be constructed. This is generally the result of an error while accessing the local materialized view catalog.

Action: Verify that the named materialized view(s) are properly defined and valid.

ORA-26529: local store callback term phase failed for string.string

ORA-26529: local store callback term phase failed for string.string

Cause: The client callback failed during its TERM phase for the named object.

Action: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error state and notify Oracle support.

ORA-26528: local store callback proc phase failed for string.string

ORA-26528: local store callback proc phase failed for string.string

Cause: The client callback failed during its PROC phase for the named object.

Action: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error state and notify Oracle support.

ORA-26527: local store callback init phase failed for string.string

ORA-26527: local store callback init phase failed for string.string

Cause: The client callback failed during its INIT phase for the named object.

Action: Verify that the objects referenced by the client callback exist and are valid. Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error state and notify Oracle support.

ORA-26526: materialized view sql ddl parse or expansion failed for string.string

ORA-26526: materialized view sql ddl parse or expansion failed for string.string

Cause: The client sql materialized view definition query could not be properly parsed by the master Oracle site.

Action: Check that materialized view ddl sql is compatible with the currently connected version of Oracle and does not violate any of the RepAPI sql limitations or restrictions.

ORA-26525: session connection attempt failed for string (string)

ORA-26525: session connection attempt failed for string (string)

Cause: A connection could not be established to the specified database using the provided connection string.

Action: Check that the user, password, connect string, names services, network, and any remote site listener process are properly installed and working.

ORA-26524: nls subsystem initialization failure for product=string, facility=string

ORA-26524: nls subsystem initialization failure for product=string, facility=string

Cause: The NLS product or facility error message file could not be located or properly initialized.

Action: Check that the error message directory and file(s) have been properly installed.

ORA-26523: rpc termination error

ORA-26523: rpc termination error

Cause: An error occurred during the termination of a PL or SQL rpc. This is usually caused by master site being unable to close an opened cursor or if RepAPI cannot deallocate internal memory.

Action: Fix any server side problems first, determine if the RepAPI memory subsystem has been corrupted.

ORA-26522: rpc execution error

ORA-26522: rpc execution error

Cause: An error occurred during the execution of a PL or SQL rpc.

Action: Check the error messages from the remote procedure and fix any remote site problems that may be preventing the execution of the invoked rpc.

ORA-26521: rpc initialization error

ORA-26521: rpc initialization error

Cause: An error occurred during the initialization of a PL or SQL rpc.

Action: Verify that the procudure to be invoked exists and is valid at the master site and is executable by the RepAPI user.

ORA-26520: internal memory failure

ORA-26520: internal memory failure

Cause: An internal memory error was detected.

Action: Check if other errors have occurred or determine if any local application may have corrupted the memory subsystem.

ORA-26519: no memory available to allocate

ORA-26519: no memory available to allocate

Cause: There was no memory left for the RepAPI process. This error may occur when RepAPI is trying to allocate a new table buffer area.

Action: Shutdown one or more local applications to attempt to free heap memory and retry the RepAPI operation.

ORA-26518: push queue synchronization error detected

ORA-26518: push queue synchronization error detected

Cause: Client tried to repush a transaction has already been committed at the master site. A common cause of this problem is an error at the local site in initializing or updating the local site transaction sequence mechanism.

Action: Verify that transaction data that RepAPI was attempting to repushed to the master site exists at the master table and is valid and consistent with the local site. If this error occurs, redundantly identified transactions are ignored and then purged from the local updatable materialized view logs. Check that the local site is correctly assigning new transactionIDs and is not accidently generating non-unique values.

ORA-26517: materialized view control entry for string.string was not found

ORA-26517: materialized view control entry for string.string was not found

Cause: The specified materialized view catalog control reocrd was not found.

Action: Verify that the local materialized view catalog is valid and that the local materialized view is properly defined.

ORA-26516: no push transaction acknowledgement

ORA-26516: no push transaction acknowledgement

Cause: RepAPI was unable to confirm that the last pushed transaction was successfully commited by the master site.

Action: Verify that the communications link between the local site and the master site is still valid. If the transaction has not been committed at the master, repush the transaction.

ORA-26515: no master log available for string.string

ORA-26515: no master log available for string.string

Cause: The specified master log was not found or available for the named table.

Action: Create the master log at the master site or correct any problems that may exist with the log.

ORA-26514: object string.string not found

ORA-26514: object string.string not found

Cause: The specified object was expected but not found.

Action: Verify that the specified object exists and is valid.

ORA-26513: push error: master proc. string$RP.string failed for trans:string seq:string

ORA-26513: push error: master proc. string$RP.string failed for trans:string seq:string

Cause: A conflict or error occurred at the master site while executing a $RP.rep_ insert(), rep_update(), or rep_delete() function which was not handled by conflict resolution logic at the master.

Action: Notify master site system adminstrator or DBA.

ORA-26512: error pushing transaction to def$error

ORA-26512: error pushing transaction to def$error

Cause: An unexpected error occurred while sending an def$error rpc to the master site

Action: Verify that the DBMS_DEFER package is valid and executable by the RepAPI client. Contact the local or master site administrator, if necessary.

ORA-26511: master table string.string not found

ORA-26511: master table string.string not found

Cause: A RepAPI operation was attempted against a non-existent or invalid master table

Action: Verify that the master table object exists.

ORA-26510: materialized view name: string is greater than max. allowed length of string bytes

ORA-26510: materialized view name: string is greater than max. allowed length of string bytes

Cause: The specified materialized view name was too long.

Action: Shorten the materialized view name.

ORA-26509: null materialized view control structure

ORA-26509: null materialized view control structure

Cause: An internal materialized view control structure could not be obtained.

Action: Check that the owner and users provided are correct.

ORA-26508: null materialized view connection

ORA-26508: null materialized view connection

Cause: The client connection handle was or became invalid.

Action: Verify that the client connection is valid.

ORA-26507: null master connection

ORA-26507: null master connection

Cause: The master connection handle was or became invalid.

Action: Verify that the master connection is valid.

ORA-26506: null global context

ORA-26506: null global context

Cause: An internal buffer control structure was NULL

Action: Verify that sufficient memory resources are available to RepAPI.

ORA-26505: unexpected internal null

ORA-26505: unexpected internal null

Cause: An internal buffer control structure was NULL

Action: Verify that sufficient memory resources are available to RepAPI.

ORA-26504: operation not implemented

ORA-26504: operation not implemented

Cause: The caller requested a RepAPI operation that was not implemented

Action: Do not issue this call.

ORA-26503: internal RepAPI operation failure on object string.string

ORA-26503: internal RepAPI operation failure on object string.string

Cause: An unexpected internal RepAPI failure was detected

Action: Contact Oracle support.

ORA-26502: error resignal

ORA-26502: error resignal

Cause: An internal service failed and signalled an error

Action: consult detail error message.

ORA-26501: RepAPI operation failure

ORA-26501: RepAPI operation failure

Cause: An external RepAPI operation failed.

Action: consult detail error message.

ORA-26500: error on caching string . string

ORA-26500: error on caching string . string

Cause: Attempt to cache the replication information which is unavailable in the catalog for the object.

Action: Use dbms_reputil.sync_up_rep to validate the replication catalog, or use dbms_reputil.make_internal_pkg to validate internal package.