Oracle Database Errors or Warnings from Error ORA-26708 to ORA-26717

SQLServerF1

ORA-26708: remote DDL not supported by STREAMS : dblink string
Cause: The apply process attempted to apply a DDL LCR via a dblink. This is not supported.
Action: Do not attempt to apply DDL LCRs via a dblink. If possible, filter out DDL LCRs before applying.
ORA-26709: Streams RFS restart
Cause: Remote file server (RFS) process was restarted to reflect a change in DOWNSTREAM_REAL_TIME_MINE option of the Streams capture process.
Action: No action required. This is an informational message only.
ORA-26710: incompatible version marker encountered during Capture
Cause: Capture process cannot mine redo from a version higher than the current software release version.
Action: Drop and recreate the capture process.

ORA-26711: remote table does not contain a primary key constraint
Cause: The master table for remote apply does not constain 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-26712: remote object is “string”.”string”\@”string”
Cause: See the preceding error message to identify the cause. This message names the remote object, usually a table or view, for which an error occurred when Streams tried to access it for remote apply.
Action: See the preceding error message.
ORA-26713: remote object does not exist or is inaccessible
Cause: Streams replication could not access the named table or view at a remote database to apply changes.
Action: Confirm that the given remote table or view exists and is accessible through the given database link. When using a Heterogeneous Services database link to access a non-Oracle system, it may be necessary to check administration details for network connections at the non-Oracle system.

ORA-26714: User error encountered while applying
Cause: An error was encountered while applying.
Action: Query the dba_apply_error view to determine the error and take the appropriate action.
ORA-26715: time limit reached
Cause: The specified time limit was reached for the STREAMS process.
Action: Restart the STREAMS process, increasing the TIME_LIMIT parameter if necessary.
ORA-26716: message limit reached
Cause: The specified message limit was reached for the Capture process.
Action: Restart the Capture process, increasing the MESSAGE_LIMIT parameter if necessary.
ORA-26717: SCN limit reached
Cause: The specified SCN limit was reached for the STREAMS process.
Action: Change the MAXIMUM_SCN parameter, then restart the STREAMS process.

Above are list of Oracle Database Errors or Warnings from Error ORA-26708 to ORA-26717 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *