My Oracle Support Banner

OCIDESCRIBEANY() Failed To Find An UDT Object When Sdo_geometry Prefixed With Schema Name Instead Of Public (Doc ID 1334920.1)

Last updated on FEBRUARY 20, 2019

Applies to:

Oracle Spatial and Graph - Version 10.2.0.4 and later
Information in this document applies to any platform.

Symptoms

In 11g, when a table with a column SDO_GEOMETRY is created within a specific schema , the type is created as SDO_GEOMETRY type, the db will automatically change the udt schema to PUBLIC instead, while for 10g, the column type remains as SDO_GEOMETRY

This is causing a call to the GoldenGate program "extract" to error out with:

Source Context :
SourceModule : [ggdb.ora.udt]
SourceID : [/mnt/ecloud/workspace/Build_FBO_OpenSys_r11.1.1.0.26_001_[46254]/perforce/src/gglib/ggdbora/ociudt.c]
SourceFunction : [checkForSynonym]
SourceLine : [365]

2011-03-10 08:47:34 ERROR OGG-00746 Error (100, no data found) selecting data in checkForSynonym.

The error is caused because the SDO_GEOMETRY type is being prefixed with the schema that created the table and not PUBLIC.


Workaround:
Recreate the table prefixing the column with MDSYS or the owner of the object data type. Note that
this is not exclusive of SDO_GEOMETRY but any object datatype. Workaround not acceptable for
some customers  because they may have objects in the order of terabytes that they can not recreate.

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.