My Oracle Support Banner

UIM Cancelled Purge -- Start Date In UTC End Date In BST (Doc ID 2899863.1)

Last updated on JUNE 19, 2023

Applies to:

Oracle Communications Unified Inventory Management - Version 7.3.5.0.0 and later
Information in this document applies to any platform.

Symptoms

UIM purging procedures sometimes use the CURRENT_TIMESTAMP function (i.e. to update the PURGE_AUDIT table) and sometimes they use SYSTIMESTAMP function (i.e. to update the PURGE_ERROR_LOG table). These two functions can return different values if the DB is running in a different timezone to the session.

Most of the purging functions are being called from scheduled jobs whose sessions run from the DB host (that is running in UTC) so timestamps are being recorded in UTC. But when we call the cancel_entity_purge procedure from a SQL Develper session from a client that is running in BST, the timestamp recorded in the PURGE_AUDIT.ENDDATE column is in BST.

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!


In this Document
Symptoms
Changes
Cause
Solution
References


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