Oracle Realtime Scheduler (ORS) Latitude and Longitude Precision is Lost Due to Incorrect NLS_LANG and NLS_TERRITORY Database Instance Settings
(Doc ID 1086135.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Real-Time Scheduler - Version 1.13.0 and later
Information in this document applies to any platform.
When a job is being entered using the web service the correct latitude and longitude coordinates are entered but when the Resource Manager Gateway (RMGW) updates the stop the precision of the coordinates has been lost.
In the web service log files it can bee seen that stop id 00001240 has the full precision of the latitude and longitude coordinates attached to it prior to the data being written to the database and the job being passed to the Switch. In the RMGW log file however, when the job is picked up as a New stop it is then passed to the scheduler without any precision.
### Steps to Reproduce ###
Enter a Job using the web service and conditional assignment. Search for the job in the scheduler once the gateway has processed the message and it can be seen that the lat long has lost it's precision.
-- Business Impact:
Unable to enter jobs at their true lat/long hence routing is inaccurate
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