Different Timezone In Two Ifw_sync Queues
(Doc ID 2403961.1)
Last updated on JUNE 07, 2022
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management (BRM), 18.104.22.168.0 version, it is observed that different timezones are being used for different ifw_sync queues.
For example, after creating a new "ifw_sync_dataonly2" queue in Oracle 11G 22.214.171.124, the "ENQ_TIME" of "ifw_sync_dataonly2" stores GMT time but ifw_sync stores a timestamp based on local time (eg. HKT or GMT+8).
As per the below column timezone in AQ$QUEUE_TABLES, ifw_sync and ifw_sync_dataonly2 values are GMT and GMT+8 respectively.
Recently Oracle database have upgraded from 10G to 11G (126.96.36.199). In Oracle 10G environment, the timezone setup is GMT+8. After upgrade, the Oracle 11G environment changed timezone to UTC.
How can the queue table columns ENQ_TIME and DEQ_TIME both be in Hong Kong Time (HKT)?
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