Replicate Abends during table update with NOT NULL column ORA-1407
edited Aug 8, 2016 9:48AM in GoldenGate, Streams and Distributed Database (MOSC) 10 commentsAnswered ✓
I have a table ALL_DB_OBJECTS ( copy of ALL_OBJECTS ). When I update STATUS column for all rows to a value = 'INVALID'
UPDATE ALL_DB_OBJECTS SET STATUS = 'INVALID';
commit;
on the source db -
replicate on the target db abends with ORA-1407. In the log file it complains that OWNER is NULL.
My question - Do I need to enable supplemental logging columns in ALL_DB_TABLES to eliminate the error? I thought if I updated one column it would only bring the change for one column.
Anyone can point to a location in the documentaion where this is described? Is it the replicate that see the update on the table and wants to see values for all columns in the table or is it extract that generates the update statement?
UPDATE ALL_DB_OBJECTS SET STATUS = 'INVALID';
commit;
on the source db -
replicate on the target db abends with ORA-1407. In the log file it complains that OWNER is NULL.
My question - Do I need to enable supplemental logging columns in ALL_DB_TABLES to eliminate the error? I thought if I updated one column it would only bring the change for one column.
Anyone can point to a location in the documentaion where this is described? Is it the replicate that see the update on the table and wants to see values for all columns in the table or is it extract that generates the update statement?
0