Goldengate expects a column that is not in the unique constraint

Question

I do not know golden gate. I am working with a golden gate engineer who doesn't really know oracle. I am the DBA supporting this. This is the issue we are having. Please bare with me if I have trouble explaining it.
I am pulling from oracle and loading to teradata. I confirmed that the unique index is correct in teradata (don't have access. I asked).
Oracle 10.2.0.5
golden gate: 11.1.1.0.29
error: the name of the schema listed in the error is from teradata. So TERADATA_SCHEMA. represents that.
Key column my_id is missing from update on table TERADATA_SCHEMA.MYTABLE
Missing 1 key columns in update for table TERADATA_SCHEMA.MYTABLEbelow is a create table statement. I have altered table and column names. but the structure is the same.
it does NOT have a primary key. It has a unique key. I am not allowed to add a primary key
UNIQUE INDEX: UNIQUE_ID
When we test an updates, golden gate is expecting MY_ID to be sent as well and golden gate abends
The DDL below includes the partitioning/subpartition, unique index, and supplemental logging command that golden gate runs.
I have also run the following 2 commands to turn on supplemental logging:
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
ALTER SYSTEM SWITCH LOGFILE;
CREATE
  TABLE MYTABLE
    "UNIQUE_ID"       NUMBER(10,0) NOT NULL ENABLE,
    "MY_ID"       NUMBER(10,0),
    "MYNUMBER" NUMBER(8,0),
    "TOTALNUMBER"  NUMBER(8,0),
    "USED" NUMBER(8,0),
    "LOTSUSED  NUMBER(8,0),
    "LAST_UPDATE_USER"  VARCHAR2(30 BYTE),
    "LAST_UPDATE_DATE" DATE,
    "MYDATESTAMP" DATE,
    "MYTYPE" NUMBER(2,0) NOT NULL ENABLE,
    "MYTHING"    CHAR(1 BYTE) NOT NULL ENABLE
  PARTITION BY RANGE
    "MYTYPE"
  SUBPARTITION BY LIST
    "MYTHING"
  SUBPARTITION TEMPLATE
    SUBPARTITION "MYTHING_X" VALUES
      'X'
    SUBPARTITION "MYTHING_Z" VALUES
      'Z'
    PARTITION "MYTHING1" VALUES LESS THAN (2) ,
    PARTITION "MYTHING2" VALUES LESS THAN (3) ,
    PARTITION "MYTHING3" VALUES LESS THAN (4) ,
    PARTITION "MYTHING4" VALUES LESS THAN (5) ,
    PARTITION "MYTHING5" VALUES LESS THAN (6) ,
    PARTITION "MYTHING6" VALUES LESS THAN (7) ,
    PARTITION "MYTHING7" VALUES LESS THAN (8) ,
    PARTITION "MYTHING8" VALUES LESS THAN (9) ,
    PARTITION "MYTHING_OTHER" VALUES LESS THAN (MAXVALUE)
ALTER TABLE MYTABLE  ADD SUPPLEMENTAL LOG GROUP
"MYGROUP_555"
  "UNIQUE_ID"
ALWAYS;
CREATE UNIQUE INDEX MY_IND ON MYTABLE  (
    "UNIQUE_ID"
  ;Edited by: Guess2 on Nov 3, 2011 12:57 PM
Edited by: Guess2 on Nov 3, 2011 1:21 PM

Answer 1

GoldenGate expects a primary key, a unique key, or a list of key columns.
The addition of supplemental logging for the table can be done via SQL, but typically, it is done via the GGSCI interface:
GGSCI 4> dblogin userid <your DB GoldenGate user>, password <your password?
GGSCI 5> add trandata schema_owner.table_name
How Oracle GoldenGate determines the kind of row identifier to useUnless a KEYCOLS clause is used in the TABLE or MAP statement, Oracle GoldenGate selects a
row identifier to use in the following order of priority:
1. Primary key
2. First unique key alphanumerically with no virtual columns, no UDTs, no function-based
columns, and no nullable columns
3. First unique key alphanumerically with no virtual columns, no UDTs, or no function-based
columns, but can include nullable columns
4. If none of the preceding key types exist (even though there might be other types of keys
defined on the table) Oracle GoldenGate constructs a pseudo key of all columns that
the database allows to be used in a unique key, excluding virtual columns, UDTs,
function-based columns, and any columns that are explicitly excluded from the Oracle
GoldenGate configuration.
NOTE If there are other, non-usable keys on a table or if there are no keys at all on the
table, Oracle GoldenGate logs an appropriate message to the report file.
Constructing a key from all of the columns impedes the performance of Oracle
GoldenGate on the source system. On the target, this key causes Replicat to use
a larger, less efficient WHERE clause.
How to specify your own key for Oracle GoldenGate to use
If a table does not have one of the preceding types of row identifiers, or if you prefer those
identifiers not to be used, you can define a substitute key if the table has columns that
always contain unique values. You define this substitute key by including a KEYCOLS clause
within the Extract TABLE parameter and the Replicat MAP parameter. The specified key will
override any existing primary or unique key that Oracle GoldenGate finds.>
"I have altered table and column names. but the structure is the same."
What column name did you alter?
The source table table and target table are either identical, or there must be a source definition file created on the source and copied over to the target and referenced in the replicat.
I don't see why my_id would cause a problem (based on what you posted), unless the tables are different.