Last updated on MARCH 10, 2015
Applies to:Oracle Spatial and Graph - Version 184.108.40.206 and later
Oracle Transportation Management - Version 6.2.2 and later
Information in this document applies to any platform.
With 220.127.116.11 database and Oracle Spatial 18.104.22.168 elocation, geocoder, routeserver configured with Oracle Transportation Management (OTM), errors are logged approximately every minute in the geocoder.log as soon as Spatial is started via
The same errors continue to occur even with OTM turned off.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms