My Oracle Support Banner

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

Last updated on JUNE 05, 2019

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
  ('<TABLENAME>', 'COLUMNNANME>',
   "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 <INDEXNAME> ON <TABLE_NAME>
(COLUMNNAME)
INDEXTYPE IS MDSYS.SPATIAL_INDEX
NOPARALLEL;

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

Wildcard SEQUENCE resolved (entry <USERNAME>.*):
  SEQUENCE "<USERNAME>"."MDRS_xxxxx$";
Resolving source sequence <USERNAME>.MDRS_xxxxx$.

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

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

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.