ORA-26688 Missing Key in LCR
-
The object for which an LCR is applying a
change does not exist in the destination database. In this case,
it is necessary to ensure that the object exists. Make sure that
the correct character case is used in rule conditions, Apply
handlers, and rule-based transformations.
-
Supplemental logging is not
specified for columns that require supplemental logging at the
source database. In this case, LCRs from the source database may
not contain values for key columns.
-
There may be problem with the primary key
in the destination table. If no primary key exists for the table
or if the target table has a different primary key than the
source table, substitute key columns can be specified using the
set_key_columns procedure in the dbms_apply_adm
package.
ORA-26689 Column Type Mismatch
This error message is returned because one
or more columns at a table in the source database do not match
the corresponding columns at the destination database.
The LCRs from the source database may
contain more columns than the table at the destination database,
or there may be a type mismatch for one or more columns. The
Streams process assumes the same exact set of columns at the
both source and destination end. If the columns differ at the
databases, rule-based transformations can be used to modify and
avoid the errors.
If an apply handler or a rule-based
transformation is used, any SYS.AnyData conversion functions
must match the data type in the LCR that is being converted. For
example, if the column is specified as VARCHAR2, the
SYS.AnyData.CONVERTVARCHAR2 function should be used to convert
the data from type ANY to VARCHAR2.
