Integrated Capture/ Extract Resolves MDRS_* Sequences Part of Spatial Index Causing Replicat Errors (Doc ID 1557409.1)

Last updated on JULY 03, 2017

Applies to:

Oracle GoldenGate - Version 11.2.1.0.0 and later
Information in this document applies to any platform.

Symptoms

 Integrated capture/ Extract resolves MDRS_* sequences part of spatial index causing replicat errors

Insert into MDSYS.USER_SDO_GEOM_METADATA
Values
  ('TEMP_WSZ', 'MERGEDGEOMETRY',
   "MDSYS"."SDO_DIM_ARRAY"(
   "MDSYS"."SDO_DIM_ELEMENT"('X',-2147483648,2147483647,5E-6),
   "MDSYS"."SDO_DIM_ELEMENT"('Y',-2147483648,2147483647,5E-6),
   "MDSYS"."SDO_DIM_ELEMENT"('Z',-2147483648,2147483647,5E-6)),NULL);
   
CREATE INDEX TEMP_WSZSI88 ON TEMP_WSZ
(MERGEDGEOMETRY)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
NOPARALLEL;

Extract is resolving the sequences thats gets created in the background
causing issues to downstream replicat

Wildcard SEQUENCE resolved (entry polymaster.*):
  SEQUENCE "POLYMASTER"."MDRS_6A7B5$";
Resolving source sequence POLYMASTER.MDRS_6A7B5$.

Replicat would fail with following for a sequence that extract shouldn't
have captured.

Wildcard MAP resolved (entry polymaster.*):
  MAP "POLYMASTER"."MDRS_6A7B5$", TARGET polymaster."MDRS_6A7B5$";
...
2013-04-16 10:31:07  ERROR   OGG-00199  Table polymaster.MDRS_6A7B5$ does not
exist in target database.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms