My Oracle Support Banner

Some Workorders in MWM v1 Not Assigned, Due to 'Order [x] Will Not Be Geocoded', 'ORA-29532: Java call terminated by uncaught Java exception: Error: null' (Doc ID 1997270.1)

Last updated on APRIL 08, 2015

Applies to:

Oracle Utilities Mobile Workforce Management - Version 1.4.5 to 1.5.0 [Release 1.4 to 1.5]
Information in this document applies to any platform.

Symptoms

Recently it was reported that some workorders are not assigned by MWM. When looking at the Server logs we see an error occurred geocoding the order. Order [RCE6703346001] will not be geocoded.

INFO¦10:19:30¦ 416¦Before call to GeocodeOrder for order [ACE6704112345]...Street Address [1586 MAIN ST]
              City/State/Zip [CITY1,ON K4A 1A2] Country [CA] Match Mode [RELAX_BUILTUP_AREA]. (XThreadSvF
              oEx::GeocodeFieldOrder)
...
INFO¦10:19:30¦ 416¦GeocodeOrder elapsed time: 187 ms (XPerformanceTimer::DisplayElapsedTime)
INFO¦10:19:30¦ 416¦Database Exception occurred.  Call GeocodeFieldOrder again to have it reconnect to datab
              ase. (XThreadSvFoEx::ProcessMfFieldOrderIcd)
INFO¦10:19:30¦ 416¦Geocode database connection is being closed, so it can be reconnected. (XThreadSvFoEx::G
              eocodeFieldOrder)
INFO¦10:19:30¦ 416¦Before call to GeocodeOrder for order [ACE6704112345]...Street Address [1586 MAIN ST]
              City/State/Zip [CITY1,ON K4A 1A3] Country [CA] Match Mode [RELAX_BUILTUP_AREA]. (XThreadSvF
              oEx::GeocodeFieldOrder)
...
INFO¦10:19:32¦ 416¦GeocodeOrder elapsed time: 2156 ms (XPerformanceTimer::DisplayElapsedTime)
INFO¦10:19:32¦3720¦Error occurred geocoding the order.Order [ACE6704112345] will not be geocoded. (CServerD
              lg::WriteAuditMessage)
INFO¦10:19:32¦3720¦Error occurred geocoding the order.Order [ACE6704112345] will not be geocoded. (XThreadS
              vFoEx::GeocodeFieldOrder) / Database Exception occurred in GeocodeOrder. (XThreadSvFoEx::Geoc
              odeFieldOrder) / Error occurred opening recordset for geocoding order...rc [-1]. (XDbServer::
              GeocodeOrder) (::)

 
This issue has been ongoing for almost one year. The database was upgraded from 10.2.0.3 to 10.2.0.4 about 6 months ago.  The component versions involved are:

MWM v1.4.5.22
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for 32-bit Windows: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


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