My Oracle Support Banner

Siebel Timezone Issue Detected For CREATED and LST_UPD 1 Hour Ahead of System Time Post DST Time Change When "Universal Time Coordinated = FALSE" and "Default Time Zone=(GMT-04:00) Santiago" (Doc ID 2867066.1)

Last updated on JUNE 30, 2022

Applies to:

Siebel Financial Services CRM - Version 21.5 and later
Information in this document applies to any platform.


Siebel Timezone Issue Detected for CREATED and LST_UPD 1 Hour Ahead of System Time After DST Time change in April when "Universal Time Coordinated = FALSE" and "Default Time Zone=(GMT-04:00) Santiago"

Usually CREATED and LST_UPD should be same as DB_LST_UPD. But, there is 1 hour gap it showing when checking about record

The issue can be reproduced at will with the following steps:


1. log in to Siebel application object manager URL ( Thin Client )
2. Go to  Site Map --> Administration - Application -> System Preference
3. Query for Universal Time Coordinator and Set the "Universal Time Coordinator = FALSE"
4. Update "Default Time Zone = (GMT-04:00) Santiago"
5. Set Operating System time zone also referring to (GMT-04:00) Santiago
6. Data Base side also referring to same Operating System timezone as (GMT-04:00) Santiago
7. Restart the machine to take time zone effect and Db and Siebel enterprise restart to take effect.
8. After the Siebel application is online, log into the Application
9. Try to create one account record or any record in Siebel application and
click on About Record which shows 1 hour ahead of original system time




 DST change during month of April 2022


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

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