Unable To Sync Retired Devices After Applying Service Pack 3

(Doc ID 2132365.1)

Last updated on MAY 05, 2016

Applies to:

Oracle Utilities Meter Data Management - Version 2.1.0.3 and later
Information in this document applies to any platform.

Symptoms

On : 2.1.0.3 version, Common

Unable to sync Retired devices after applying Service Pack 3

After applying MDM Service Pack 3 (v2.1.0.3) we are unable to perform an update sync that moves a device from Active to Retired status.

When processing the inbound sync request, the D1-OngoingSyncRequestDevice BO goes to Update Error state. On version 2.1.0.2 the same inbound sync request is processed correctly.

On viewing the (attached) log files from the D1-SIOPE batch, it appears that the BO Status of the Device is not being updated to Retired prior to the Retirement Date being validated in the D1-VALRETDT script. This causes the above-mentioned error to be raised. Conversely the logs for version 2.1.0.2 show the Device BO Status being set to Retired prior to D1-VALRETDT being executed.

ERROR
-----------------------

 "Retirement Date is not allowed if device is not retired".


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Start with active Device in MDM environment
2. Submit an ongoing sync request to retire the Device
3. Get the error as shown above

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot retire devices.

Cause

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 hundreds of Community platforms