Scheduler Functionality Outages For Brief Periods Throughout The Day Citing SDO Object Errors
(Doc ID 2393492.1)
Last updated on MARCH 08, 2019
Applies to:Oracle Utilities Mobile Workforce Management - Version 184.108.40.206 to 220.127.116.11.0 [Release 2.1 to 2.3]
Oracle Real-Time Scheduler - Version 18.104.22.168 to 22.214.171.124.0 [Release 2.1 to 2.3]
Information in this document applies to any platform.
MWM - Oracle Utilities Mobile Workforce Management
Users are reporting scheduler outages for ~10 minutes at a time, several times a day. After this period, functionality ios restored on it's own and normal operation continues.
Here we see a gap of ten minutes in the threadpoolworker (TPW) logs:
Customer confirmed that all Spatial DB objects are valid using, 'Oracle Locator / Oracle Spatial Health Check (Doc ID 800725.1)'.
Customer confirmed setting as discussed in, 'Doc ID 1627191.1 - Creating spatial index with SDO_DML_BATCH_SIZE=1 ON EMPTY TABLE FAILS 126.96.36.199 > 188.8.131.52' / 'Doc ID 2026577.1 - MWM v2 Stuck Threads Due To SDO_DML_BATCH_SIZE'
Scheduler SMAuto logs do not show a process crash.
Customer applied Oracle <Patch 18146463> to 184.108.40.206 Oracle database homes in production but the issue remains.
The client recently performed a DB upgrade from 220.127.116.11 to 18.104.22.168.
The error messages point to an issue with Spatial index. Using the following references, the customer dropped and recreated the spatial indexes though this did not resolve the issue:
Doc ID 1908389.1 - 22.214.171.124 to 126.96.36.199 SE Oracle Locator upgrade fails on Linux X86-84
Doc ID 1418651.1 - EXPDP Raises EXP-00078 For A Spatial Index, Rebuilding The Index Fails With ORA-13209
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!