LAST_UPDATE_TIME Timestamp in JOBS Not Getting Updated with Unpublishing ERT (Doc ID 1999654.1)

Last updated on JULY 13, 2016

Applies to:

Oracle Network Management for Utilities - DMS - Version 1.11.0 to 1.12.0.2 [Release 1.11 to 1.12]
Oracle Utilities Network Management System - Version 1.11.0 to 1.12.0.2 [Release 1.11 to 1.12]
Information in this document applies to any platform.

Symptoms


The JOBS.Last_update_time timestamp is not getting updated with a global ETR (estimated restore time, ERT) override in Stormman.


When a Storm Management user publishes the ETRs, the est_rest_time and when_provided_est_rest_time fields in the JOBS table are updated properly.  However, it does not appear to update the last_update_time field to flag the record for extraction to the BI. According to the business users, using Storm Management they first unpublish all the ETRs to clear out what was there before, then they publish the new ETRs.

The trigger on the jobs table (cu_jobs) is supposed to update that last_update_time when the est_rest_time changes, but that doesn't appear to be happening - at least not for all events - when the Storm Management ETRs are published.


The issue can be reproduced at will with the following steps:
1. Submit calls to create outages
2. Query the JOBS table to review the est_rest_time and last_update_time for events
3. In Stormman select an ERT override and unpublish the est_rest_times
4. Verify whether the last_update_time was changed when the est_rest_time goes to null.



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