0 Replies Latest reply on Aug 8, 2012 7:54 AM by user4833450

    Downstream Capture and Extended Datatype Support

      Wondering if anyone has tried downstream capture on tables with datatypes that are not natively supported (e.g. MDSYS.SDO_GEOMETRY)?

      I've had a look at this for upstream capture but at my site we want to,
      a) reduce possible impact of the capture processes on the source database
      b) avoid adding triggers to the source tables being replicated as the application vendor isn't keen on changes to "their" schema. The shadow tables might not be quite such an issue in the source schema but if they can be avoided then that would bve abonus too.

      My first thoughts are that with downstream capture, EDS would still need to be applied on these tables in the source database to handle these data types.

      If anyone has been down this path and has some insights I'd love to hear them.