Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 26500-26999: Replication

This section lists messages generated by replicatiuon.

##### ORA-26500: error on caching name.name

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.

##### ORA-26501: RepAPI operation failure

Cause: An external RepAPI operation failed.

Action: Consult detail error message.

##### ORA-26502: error resignal

Cause: An internal service failed and signalled an error.

Action: Consult the detailed error message which accompanies this one.

##### ORA-26503: internal RepAPI operation failure on object name.name

Cause: An unexpected internal RepAPI failure was detected.

Action: Contact Oracle Worldwide Support.

##### ORA-26504: operation not implemented

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

Action: Do not issue this call.

##### ORA-26505: unexpected internal NULL

Cause: An internal buffer control structure was NULL.

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

##### ORA-26506: NULL global context

Cause: An internal buffer control structure was NULL.

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

##### ORA-26507: NULL master connection

Cause: The master connection handle was or became invalid.

Action: Verify that the master connection is valid. Then retry the operation.

##### ORA-26508: NULL snapshot connection

Cause: The client connection handle was or became invalid.

Action: Verify that the client connection is valid.

##### ORA-26509: NULL snapshot control structure

Cause: An internal snapshot control structure could not be obtained.

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

##### ORA-26510: snapshot name: name is greater than max. allowed length of num bytes

Cause: The specified snapshot name was too long.

Action: Shorten the snapshot name.

##### ORA-26511: master table name.name 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-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-26513: push error: master proc. name$RP.name failed for trans:name seq:name

Cause: A conflict/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 administrator or DBA.

##### ORA-26514: object name.name not found

Cause: The specified object was expected but not found.

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

##### ORA-26515: no master log available for name.name

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-26516: no push transaction acknowledgment

Cause: RepAPI was unable to confirm that the last pushed transaction was successfully committed 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-26517: snapshot control entry for name.name was not found

Cause: The specified snapshot catalog control record was not found.

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

##### 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 repush 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 snapshot logs. Check that the local site is correctly assigning new transaction IDs and is not accidently generating non-unique values.

##### 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-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-26521: RPC initialization error

Cause: An error occurred during the initialization of a PL/SQL RPC.

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

##### ORA-26522: RPC execution error

Cause: An error occurred during the execution of a PL/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-26523: RPC termination error

Cause: An error occurred during the termination of a PL/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-26524: NLS subsystem initialization failure for product=name, facility=name

Cause: The NLS product/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-26525: session connection attempt failed for name (@name)

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-26526: snapshot SQL DDL parse/expansion failed for name.name

Cause: The client SQL snapshot definition query could not be properly parsed by the master Oracle site.

Action: Check that snapshot DDL SQL is compatible with the currently connected version of Oracle and does not violate any of the RepAPI SQL limitations or restrictions.

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

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 states and notify Oracle Worldwide Support.

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

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 Worldwide Support.

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

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 Worldwide Support.

##### ORA-26530: unable to build snapshot refresh control list

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

Action: Verify that the named snapshot(s) are properly defined and valid. Then retry the operation

##### ORA-26531: replication parallel push failure recovery test event

Cause: N/A.

Action: Event used to simulate site failure for parallel push testing.

##### ORA-26532: replication parallel push simulated site failure

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

Action: Do not enable the event for normal operation.

##### ORA-26534: collision: tranID num 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 (ORA-26518).

##### ORA-26535: num byte row cache insufficient for table with rowsize=num

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-26536: 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 site.

Action: Do one of the following:

- Resolve the conflicts in the master DEFERROR table and refresh again after the table is empty.
- Refresh with REFRESH_AFTER_ERRORS, even if there are conflicts in the master site's DEFERROR table. If you proceed even with existing conflicts, an updatable snapshot's changes could appear to be temporarily lost. A refresh that succeeds after the conflicts are resolved should restore the changes.

##### ORA-26563: renaming this table is not allowed

Cause: An attempt was made to rename a replicated table, an updatable snapshot table, or the master table of a snapshot for which a snapshot log has been created.

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 snapshot.

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

Cause: The passed type of the given argument number does not match the type of the argument in the stored arguments.

Action: Invoke the correct type procedure (that is, GET_XXX_ARG).

##### ORA-26565: call to <type>_ARG made before calling DBMS_DEFER.CALL

Cause: An attempt was made to invoke the <type>_ARG procedure before starting a deferred call.

Action: Invoke the needed procedures in the correct order.

##### ORA-26566: could not open connect to name

Cause: Failed to open connection using given DBLINK.

Action: Make sure that the DBLINK is valid and remote m/c is up.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index