Re: OGG-01169

Posted by ErmanArslansOracleBlog on Oct 05, 2019; 9:01am
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/OGG-01169-tp7738p7757.html

If the symptoms given in that note are similar to yours, yes why not..
It says: we have function-based index on top of the key cols and we can't use a function-based index to find unique rows.
That's why the suggest you to create unique index in the target.
That note is based on the KEYCOLS principle, which can be read in the note ->

-------------------------------
https://docs.oracle.com/goldengate/1212/gg-winux/GWURF/gg_parameters160.htm

The following column-types are not supported in KEYCOLS:

Oracle column types not supported by KEYCOLS:

Virtual columns, UDTs, function-based columns, and any columns that are explicitly excluded from the Oracle GoldenGate configuration.

SQL Server, DB2 LUW, DB2 z/OS, MySQL, SQL/MX, Teradata, TimesTen column types not supported by KEYCOLS:

Columns that contain a timestamp or non-materialized computed column, and any columns excluded from the Oracle GoldenGate configuration. For SQL Server Oracle GoldenGate enforces the total length of data in rows for target tables without a primary key to be below 8000 bytes.

Sybase column types not supported by KEYCOLS:

Computed columns, function-based columns, and any columns that are explicitly excluded from the GoldenGate configuration.
----------------