My Oracle Support Banner

MDM On-Demand Read Using Creation Date To Determine Activity Expiration Date (Doc ID 2414498.1)

Last updated on JULY 16, 2018

Applies to:

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

Symptoms

MDM On-Demand Read Activity is using creation date/time to determine the expiration date/time. For any ODR activities with a future dated effective date, the activity is forced to timeout immediately after the ODR is sent to the Head-End System.

The issue appears to be with algorithm D1-WTTMOUTEX
 

It is expected that the Activity should determine expiration date/time based on when the Activity Outbound Communication was sent.



Changes

 

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.