UPDATE_STOP Messages Indicate "Unable To Connect To Geocode Server" and "STOP could not be geocoded" (Doc ID 1370089.1)

Last updated on DECEMBER 05, 2019

Applies to:

Oracle Real-Time Scheduler - Version 10.4.9 and later
Information in this document applies to any platform.

Why are we seeing Geocode errors when processing stop updates?

	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

Goal

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