Last updated on APRIL 22, 2014
Applies to:Oracle Utilities Mobile Workforce Management - Version 2.0 and later
Oracle Real-Time Scheduler - Version 2.1.0 and later
Information in this document applies to any platform.
M1_GPS_DATA has grown to be very large and seems to be affecting system performance. Further, a database refresh / import process took more than 3 hours to build the spatial index M1_GPS_DATA_SIDX involving millions of rows.
Is this table needed during database refresh? How can the records in this table get purged?
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