Forum Stats

  • 3,780,767 Users
  • 2,254,438 Discussions
  • 7,879,443 Comments

Discussions

Replicate error (OGG-06441)

We are in the process of upgrading GG 12c to 19c and are facing an issue on the replicat side.

We have tables with unique indexes defined on nullable columns. It seems GoldenGate is not able to see those indexes.

During a replication the process is abended with the following error:

2020-03-30T14:45:39.591+0200  INFO OGG-06441  Oracle GoldenGate Delivery for Oracle, repviz.prm:  Unique key <>for table <> cannot be used due to the inclusion of virtual columns, or user-defined datatypes, or extended long varchar columns, or function-based index columns.

The index is based on a varchar column with normal length.

After changing the column to not null the replicat is seing the index and able to process the row:

alter table <>modify (integration_id  not null);2020-03-30T14:48:52.709+0200  INFO OGG-06510  Oracle GoldenGate Delivery for Oracle, repviz.prm:  Using the following key columns for target table <>: INTEGRATION_ID.

We can also use KEYCOLS (INTEGRATION_ID), but it seems a bit overhead. As we don't control the data model, we can't change the column to not null by default.

Any suggestions? Is this a change in GoldenGate 19c?

According the docs this should be OK:

https://docs.oracle.com/en/middleware/goldengate/core/19.1/oracle-db/preparing-database-oracle-goldengate.html#GUID-644099C5-8950-496C-8592-446FB1566AFD

First unique key alphanumerically with no virtual columns, no UDTs, no extended (32K) VARCHAR2/NVARCHAR2 columns, or no function-based columns, but can include nullable columns.

Michael

Answers

  • User_FKW6T
    User_FKW6T Member Posts: 1 Red Ribbon

    I am experiencing the same problems? Has Oracle address this problem? I have index based on column having basic data types - varchar2(10), varchar2(20), char (1) and GoldenGate is complaining. Like the aforementioned, I see that two of the column are nullable.

  • ORASCN
    ORASCN Member Posts: 1,825 Gold Trophy

    Hi Michael,

    The issue is fixed in OGG 20.1

    Oracle has changed this error to a WARNING.


    Replicat reports OGG-06441 message for a Table with valid unique key column (Doc ID 2754696.1)

    SOLUTION

     This is expected behavior.

     Please consider using following solutions:

    1. Use KEYCOLS for the UI columns in replicat prm file.

    2. Make sure Unique Keys are NOT NULLABLE in replicating tables.

     We have changed this INFO (OGG-06441) into WARNING and modified the text in the Bug 30523672 which is fixed in OGG 20.1.x.

    WARNING OGG-06441 Unique key XXX_UK for table <TABLE_NAME> cannot be used due to the inclusion of virtual columns, nullable columns, or user-defined datatypes, or extended long varchar columns, or function-based index columns.


    Regards,

    Veera