ORA-26747: The one-to-many transformation function string encountered the following error: string

ORA-26747: The one-to-many transformation function string encountered the following error: string

Cause: The specified transformation function encountered an error.

Action: Ensure that the function does not process or return DDL LCRs. Also ensure that the function does not return NULL.

ORA-26746: DDL rule string . string not allowed for this operation

ORA-26746: DDL rule string . string not allowed for this operation

Cause: A DDL rule was specified for this operation.

Action: Specify a non-DDL rule for this operation.

ORA-26745: cursors (string) are not sufficient

ORA-26745: cursors (string) are not sufficient

Cause: The maximum number of open cursors was too small for Streams Apply.

Action: Increase the value of open_cursors.

ORA-26744: STREAMS capture process string does not support string . string because of the following reason: string

ORA-26744: STREAMS capture process string does not support string . string because of the following reason: string

Cause: STREAMS capture encountered a table with an unsupported property. The most common reason is an unsupported column data type.

Action: Revise the Capture rules to skip over the table in question. One way might be to add a negative rule excluding changes from the unsupported table from being captured. Also query the DBA_STREAMS_UNSUPPORTED view to determine which tables are not supported by STREAMS and for what reason. Consider adding negative rules for any tables that may be captured, but are present in this view. For potential workarounds to certain unsupported properties, see Metalink.

ORA-26742: Maximum number of ignored transactions exceeded

ORA-26742: Maximum number of ignored transactions exceeded

Cause: An attempt was made to add more than the allowed number of ignored transactions.

Action: Please clear the current list of ignored transactions.

ORA-26741: cannot assemble lobs

ORA-26741: cannot assemble lobs

Cause: An attempt was made to assemble lobs, but the compatibility of the source database for the LOB information is lower than 10.2.0.

Action: Set ASSEMBLE_LOBS to FALSE in the DML or error handler while this handler is processing LOB information from a source database with a compatibility level lower than 10.2.0.

ORA-26740: cannot downgrade because there are file groups

ORA-26740: cannot downgrade because there are file groups

Cause: An attempt was made to downgrade a database that has file groups.

Action: Drop all file groups before attempting the downgrade.

ORA-26738: %s string is not empty

ORA-26738: %s string is not empty

Cause: The FILE GROUP or FILE GROUP VERSION being dropped contained objects.

Action: Remove the child objects, then retry the operation.

ORA-26737: version string already has an export dump file

ORA-26737: version string already has an export dump file

Cause: A Data Pump dump file was added to a file group version that already has a dump file.

Action: Remove the existing dump file if appropriate, and retry the operation.

ORA-26736: Data Pump error

ORA-26736: Data Pump error

Cause: A Data Pump error occurred when the procedure performed a File Group Repository operation.

Action: Check the error stack and trace file for error details.

ORA-26735: operation not allowed on the specified file group version

ORA-26735: operation not allowed on the specified file group version

Cause: One or more datafiles or export dump file(s) were missing from the specified file group version.

Action: Retry the operation after adding all the data files and Data Pump dump file(s) to the specified version.

ORA-26734: different datafiles_directory_object parameter must be specified

ORA-26734: different datafiles_directory_object parameter must be specified

Cause: The attempted operation involved datafiles platform conversion which required the datafiles_directory_object parameter to be specified for placing the converted data files.

Action: Retry the operation after specifying a valid datafiles_directory_object parameter. This directory must be different from the directory objects for any of the datafiles for the specified file group version.

ORA-26733: timed-out waiting for file group lock

ORA-26733: timed-out waiting for file group lock

Cause: The procedure waited too long while getting a lock to perform a file group repository operation.

Action: Retry the operation.

ORA-26732: invalid file group string privilege

ORA-26732: invalid file group string privilege

Cause: The specified privilege number that was specified is invalid.

Action: Check specification of dbms_file_group for valid privileges.

ORA-26731: %s string does not exist

ORA-26731: %s string does not exist

Cause: A FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE was specified that does not exist.

Action: Make sure the object exists and re-attempt the operation.

ORA-26730: %s string already exists

ORA-26730: %s string already exists

Cause: An attempt to use FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE failed because the item in question already exists.

Action: Remove the object if appropriate and re-attempt the operation.

ORA-26727: Cannot alter queue_to_queue property of existing propagation.

ORA-26727: Cannot alter queue_to_queue property of existing propagation.

Cause: The queue_to_queue property was specified for an existing propagation.

Action: Pass NULL for the queue_to_queue argument.

ORA-26726: logical standby and DOWNSTREAM_REAL_TIME_MINE are incompatible

ORA-26726: logical standby and DOWNSTREAM_REAL_TIME_MINE are incompatible

Cause: An attempt was made to set the logical standby database and DOWNSTREAM_REAL_TIME_MINE option of the Streams capture process on the same database.

Action: Do not attempt to set the DOWNSTREAM_REAL_TIME_MINE option for a Streams capture process on a logical standby database. Do not attempt to make a database logical standby if there exists a Streams capture process with the DOWNSTREAM_REAL_TIME_MINE parameter set to Y.

ORA-26725: cannot downgrade apply handlers

ORA-26725: cannot downgrade apply handlers

Cause: An attempt was made to downgrade apply handlers that are not associated with a local database object, or the apply handlers are associated with a specific apply process.

Action: Drop the associated apply handlers before attempting the downgrade.

ORA-26724: only SYS is allowed to set the Capture or Apply user to SYS.

ORA-26724: only SYS is allowed to set the Capture or Apply user to SYS.

Cause: The Capture or Apply user was specified as SYS by a user other than SYS.

Action: Set SYS as the Capture or Apply user while logged in as SYS.

ORA-26723: user string requires the role string

ORA-26723: user string requires the role string

Cause: The user was not granted the specified role required to proceed.

Action: Grant the specified role to the user.

ORA-26721: enqueue of the LCR not allowed

ORA-26721: enqueue of the LCR not allowed

Cause: An apply process attempted to enqueue an LCR with a LONG column. This is not supported.

Action: Modify rules or unset the enqueue destination to prevent LCRs with LONG columns from being enqueued by the apply process.

ORA-26718: transaction limit reached

ORA-26718: transaction limit reached

Cause: The specified transaction limit was reached for the Apply process.

Action: Restart the Apply process, increasing the TRANSACTION_LIMIT parameter if necessary.

ORA-26717: SCN limit reached

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.

ORA-26716: message limit reached

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-26715: time limit reached

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-26714: User error encountered while applying

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-26713: remote object does not exist or is inaccessible

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-26712: remote object is string . string or string

ORA-26712: remote object is string . string or 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-26711: remote table does not contain a primary key constraint

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-26710: incompatible version marker encountered during Capture

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-26709: Streams RFS restart

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-26708: remote DDL not supported by STREAMS : dblink string

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-26706: cannot downgrade capture process

ORA-26706: cannot downgrade capture process

Cause: An attempt was made to downgrade a capture process that has a higher version than the downgrade release version.

Action: Drop the capture process after capture has finished consuming all the redo logs before attempting the downgrade.

ORA-26705: cannot downgrade capture process after Streams data dictionary has been upgraded

ORA-26705: cannot downgrade capture process after Streams data dictionary has been upgraded

Cause: An attempt was made to downgrade a capture process after it has upgraded the Streams data dictionary.

Action: Drop the capture process before attempting the downgrade.

ORA-26701: STREAMS process string does not exist

ORA-26701: STREAMS process string does not exist

Cause: An attempt was made to access a STREAMS process which does not exist.

Action: Check with the relevant security views for the correct name of the object.

ORA-26699: STREAMS message consumer string already exists

ORA-26699: STREAMS message consumer string already exists

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

Action: Either specify another STREAMS message consumer or remove the existing STREAMS message consumer.

ORA-26698: %s did not have a string rule set

ORA-26698: %s did not have a string rule set

Cause: The STREAMS client does not have a rule set of the indicated type.

Action: Verify that the Streams client has a rule set of the specified type, and retry the operation.

ORA-26697: LCR contains extra column string

ORA-26697: LCR contains extra column string

Cause: The LCR contained more columns than the replicated table.

Action: Alter the database object.

ORA-26696: no streams data dictionary for object with number string and version number string from source database string

ORA-26696: no streams data dictionary for object with number string and version number string from source database string

Cause: An attempt to access the database object failed because the data dictionary for the object was either never populated or it was purged.

Action: Make sure the streams data dictionary is created by calling DBMS_ CAPTURE_ADM.PREPARE_%_INSTANTIATION.

ORA-26695: error on call to string: return code string

ORA-26695: error on call to string: return code string

Cause: A locking related call failed.

Action: Try the call again after fixing the condition indicated by the return code.

ORA-26694: error while enqueueing into queue string.string

ORA-26694: error while enqueueing into queue string.string

Cause: An error occurred while enqueueing a message.

Action: If the situation described in the next error on the stack can be corrected, do so.

ORA-26693: STREAMS string process dropped successfully, but error occurred while dropping rule set string

ORA-26693: STREAMS string process dropped successfully, but error occurred while dropping rule set string

Cause: An attempt to drop an unused rule set failed after dropping the STREAMS proccess successfully.

Action: Check existence of rule set and manually drop if necessary.

ORA-26692: invalid value string, string should be in string format

ORA-26692: invalid value string, string should be in string format

Cause: The parameter specified was not in the correct format.

Action: Specify the parameter value in the correct format.

ORA-26691: operation not supported at non-Oracle system

ORA-26691: operation not supported at non-Oracle system

Cause: The apply process attempted an operation that is either not supported by the non-Oracle system or by the Oracle transparent gateway through which the apply is being done. Some kinds of DML (like procedure and function calls) and all DDL will cause this error to be raised.

Action: Do not attempt to apply such LCRs to non-Oracle systems. If possible, filter out such LCRs before applying.

ORA-26690: datatype not supported at non-Oracle system

ORA-26690: datatype not supported at non-Oracle system

Cause: One of the columns of the LCR being applied was of a datatype not supported by either the target non-Oracle system or by the Oracle transparent gateway through which the apply is being done.

Action: Do not apply data of this type. If possible, filter out columns containing such datatypes before applying.

ORA-26689: column datatype mismatch in LCR

ORA-26689: column datatype mismatch in LCR

Cause: The datatypes of columns in the LCR are not the same as the datatypes in the database object.

Action: Alter the database object.

ORA-26688: missing key in LCR

ORA-26688: missing key in LCR

Cause: Metadata mismatch, or not enough information in the user generated LCR.

Action: Alter the database object, or provide all defined keys in the LCR.

ORA-26687: no instantiation SCN provided for string . string in source database string

ORA-26687: no instantiation SCN provided for string . string in source database string

Cause: Object SCN was not set. If the object is a table, then both fields will be filled, for example SCOTT . EMP . If the object is a schema, only one field will be set, for example SCOTT . . And if the object is the entire database, no fields will be set, for example . .

Action: Set the SCN by calling DBMS_APPLY_ADM.SET_%_INSTANTIATION_ SCN

ORA-26686: cannot capture from specified SCN

ORA-26686: cannot capture from specified SCN

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

Action: Retry with a valid SCN.

ORA-26685: cannot apply transactions from multiple sources

ORA-26685: cannot apply transactions from multiple sources

Cause: Transactions from multiple sources were sent to the same apply process.

Action: Create multiple apply processes and create appropriate rules so that transactions from only one source reach an apply process.

ORA-26684: invalid value for value_type

ORA-26684: invalid value for value_type

Cause: The value_type parameter should be one of OLD , NEW or *

Action: Retry with proper value_type.

ORA-26683: invalid value for value_type

ORA-26683: invalid value for value_type

Cause: The value_type parameter should be either OLD or NEW

Action: Retry with proper value_type.

ORA-26682: invalid value for publication_on

ORA-26682: invalid value for publication_on

Cause: The publication_on parameter should be either Y or N

Action: Retry with a proper value for publication_on.

ORA-26681: command type not supported

ORA-26681: command type not supported

Cause: The specified command type is not supported.

Action: Retry with a supported command type.

ORA-26680: object type not supported

ORA-26680: object type not supported

Cause: The specified object type is not supported.

Action: Retry with a supported object type.

ORA-26679: operation not allowed on LOB or LONG columns in LCR

ORA-26679: operation not allowed on LOB or LONG columns in LCR

Cause: Certain operations on LOB or LONG columns of the LCR through rule-based transformations, DML handlers, or error handlers were not allowed.

Action: Do not perform restricted operations on LOB or LONG columns in LCRs. See the documentation for operations that are restricted on LOB or LONG columns in LCRs.

ORA-26678: Streams capture process must be created first

ORA-26678: Streams capture process must be created first

Cause: Must create Streams capture process before attempting this operation.

Action: Create a Streams capture process, then retry the operation.

ORA-26677: Streams downstream capture process string cannot proceed

ORA-26677: Streams downstream capture process string cannot proceed

Cause: Database global name has been set to a value which is same as the source database name of the downstream capture process.

Action: Change database global name to a value other than the source database name for the downstream capture.

ORA-26676: Table string.string has string columns in the LCR and string columns in the replicated site

ORA-26676: Table string.string has string columns in the LCR and string columns in the replicated site

Cause: The number of columns in the LCR was not the same as the the replicated site.

Action: Alter the table structure