Comp_id 'SDO' Is Missing In Dba_Registry Though Locator Has Been Installed
(Doc ID 1662822.1)
Last updated on MARCH 04, 2019
Applies to:Oracle Spatial and Graph - Version 188.8.131.52 and later
Information in this document applies to any platform.
comp_id 'SDO' is missing in dba_registry though Locator has been installed
'select sdo_version from dual' to check whether Locator functionality is available.
Unfortunately, this query returns NULL because the instance has no comp_id = 'SDO' in the dba_registry.
It contains only CATALOG, CATPROC, OWM, JAVAVM, XML, CATJAVA, EXF, XDB, RUL, ORDIM, EM, CONTEXT.
workaround to customer to return the 184.108.40.206.0 string but hardcode might not be the best option so we provided one based on ORDIM
conn / as sysdba
alter session set current_schema=MDSYS;
create or replace function SDO_VERSION
return varchar2 DETERMINISTIC PARALLEL_ENABLE as
select VERSION into sdo_verno
from dba_registry where comp_id = 'ORDIM';
Still customer is hesitant to use this workaround and would like Oracle to modify the SDO_VERSION function to deal with the case where Locator is installed but not Spatial.
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