My Oracle Support Banner

Complying with Daylight Saving Time (DST) and Time Zone Rule Changes in E-Business Suite 11i (Doc ID 458452.1)

Last updated on MARCH 22, 2019

Applies to:

Oracle E-Business Suite Technology Stack - Version 11.5.10.2 to 11.5.10.2 [Release 11.5.10]
Information in this document applies to any platform.
ALL PRODUCT ACCESS - Version: 11.5.10.2


Details

I. Daylight Saving Time (DST) and Time Zone Changes

From time to time, certain countries or regions make Daylight Saving Time (DST) or Time Zone changes. DST changes may include adopting DST for the first time or changing the effective dates for an existing DST. Time Zone changes may include adopting a new time zone or changing the GMT offset for the country time zone. In order to comply with these DST and Time Zone changes, your Oracle E-Business Suite 11i environment may require patching.

II. Affected E-Business Suite Environments

When a country or region changes DST rules or Time Zones, your Oracle E-Business Suite 11i environment will require patching if:

If neither of the above conditions applies to your business, then your E-Business Suite environment is not affected and you do not need to apply the time zone patches.

III. Required Patches for Affected E-Business Suite Environments

Note: All time zone patches are cumulative. It is therefore advisable to always apply the latest available DST patch version since this will also include all prior fixes. If the particular patch you require is not currently available, please request it through support.

The following table lists the required patch numbers for affected E-Business Suite environments. For more detailed information about these patches, including checks to see how your environment could be affected and full instructions, please review the associated Oracle Database DST Note in the table below.

Daylight Saving Time (DST) and Time Zone Patches Table

DST Update1DST RDBMSDST OJVM
Patch5
DST Developer 6iOracle Database DST Note

Pre-Req
Patch

Upgrade Patch
Pre-Req PatchUpgrade
Patch
DST v4
n/a
<Patch 5632264> <Patch 5865568>
n/a
<Patch 5699501> <Document 403311.1> United States & Canada 2007 Daylight Saving Time
DST v6
n/a
<Patch 6113507> <Patch 6113568>
n/a
<Patch 6362118> <Document 454983.1> New Zealand Daylight Saving Time Changes Database and Fusion Middleware Recommendations
DST v7
n/a
<Patch 6672979> <Patch 6708377>
n/a
<Patch 6764685> <Document 549931.1> DSTV7 Update (Australia 2008 and more) Database and Fusion Middleware Recommendations
DST v10 <Patch 7395472> 2 <Patch 7580744> <Patch 7708501> <Patch 7509746> <Patch 7681889> <Document 756112.1> Applying the DSTv10 update for the Oracle Database
DST v11 <Patch 7695070> 3 <Patch 8524113> <Patch 8603182>
n/a
<Patch 9005247> <Document 840118.1> Applying the DSTv11 update for the Oracle Database
DST v13 <Patch 7695070> 3 <Patch 9146268> <Patch 9197935> <Patch 9005247> <Patch 9232401> <Document 975450.1> Applying the DSTv13 update for the Oracle Database
DST v14 <Patch 7695070> 3 <Patch 9742718> <Patch 9751299> <Patch 9005247> <Patch 9814469> <Document 1109924.1> Applying the DSTv14 update for the Oracle Database
DST v15 <Patch 7695070>3 <Patch 10272702> <Patch 10406470> <Patch 9005247> <Patch 10410398> <Document 1274498.1> Applying the DSTv15 update for the Oracle Database
DST v16 <Patch 7695070> 3 <Patch 12320006> <Patch 12565410> <Patch 9005247> <Patch 12851175> <Document 1319204.1> Applying the DSTv16 update for the Oracle Database
DST v17 4 <Patch 7695070> 3 <Patch 12949905> <Patch 12949919> <Patch 9005247> <Patch 13096735> <Document 1362718.1> Applying the DSTv17 update for the Oracle Database
DST v18 <Patch 7695070> 3 <Patch 13417321> <Patch 14112098> <Patch 9005247> <Patch 14162824> <Document 1448706.1> Applying the DSTv18 update for the Oracle Database
DST v19 <Patch 7695070> 3 <Patch 15897859> <Patch 15897884> <Patch 9005247> <Patch 16062507> <Document 1497158.1> Applying the DSTv19 update for the Oracle Database
DST v20 <Patch 7695070> 3 <Patch 16799735> <Patch 16799766> <Patch 9005247> <Patch 16877465> <Document 1552819.1> Applying the DSTv20 update for the Oracle Database
DST v21 <Patch 7695070> 3 <Patch 17432124> <Patch 17443054> <Patch 9005247> Request only 6 <Document 1583376.1> Applying the DSTv21 update for the Oracle Database
DST v22 <Patch 7695070> 3 <Patch 18759211> <Patch 18759260> <Patch 9005247> Request only 6 <Document 1670794.1> Applying the DSTv22 update for the Oracle Database
DST v23 <Patch 7695070> 3 <Patch 19396455> <Patch 19397646> <Patch 9005247> <Patch 19908186> 6 <Document 1907093.1> Applying the DSTv23 update for the Oracle Database
DST v24 <Patch 7695070> 3 <Patch 20875898> <Patch 20875943> <Patch 9005247> Request only 6 <Document 1998748.1> Applying the DSTv24 update for the Oracle Database

1DST Update: This only shows the DST versions that have been released externally. Other releases were internal only and are not available.

2 Windows Server Users upgrading to DSTv10 may need to apply the DST RDBMS Pre-requisite <Patch 7395472> see step 2.2.1. Apply the DST RDBMS Pre-Requisite Patch to your Database Tier (if required) below for further information.

3 Users upgrading to DSTv11 and higher may need to apply the the DST RDBMS Pre-requisite <Patch 7695070> see step 2.2.1. Apply the DST RDBMS Pre-Requisite Patch to your Database Tier (if required) below for further information.

4 DST 17 is an interim release primarily to include the new DST rules for Russia which take effect from 30th October 2011. At this time the clocks will not move back one hour as in previous years remaining on 'summer time' instead. For information on whether you require this change please see <Document 1335999.1> titled, 'Russia abandons DST in 2011 - Impact on Oracle RDBMS'. Patches for this release have been on a request only basis, therefore not all operating system/patch combinations have been released pro-actively. If you require the OJVM <Patch 12949919>, please request it through support.

5 The OJVM Patch is not generally required and is not always released pro-actively. If you require this patch and it is not currently available please request it through Oracle Support.

6 Developer 6i Patch: For DST 21 and higher the Developer 6i patch is no longer made available proactively. If you have a requirement for this DST release (for example you are running your Db using an affected timezone) request it through support with an appropriate business case and platform requirement.

DST UpdateTZ VersionCountry/Region
DST v4 Updates 2006d United States, Canada, Haiti, Sri Lanka, Uruguay, Kyrgyzstan
DST v6 Updates 2007f New Zealand, Chatham Islands, Syria, Honduras, Asmara, Easter Island, Western Australia, Honduras, Bermuda, Moncton, Blanc-Sablon, Gaza, Cuba, Egypt and Uruguay
DST v7 Updates 2007k

America/Argentina/Buenos_Aires, America/Argentina/Catamarca, America/Argentina/Cordoba America/Argentina/Jujuy, America/Argentina/Mendoza, America/Caracas, Australia/Victoria, Australia/Melbourne, Australia/NSW, Australia/Sydney, Australia/Broken_Hill, Australia/South Australia/Adelaide, Australia/Lord_Howe, Australia/Tasmania, Australia/Hobart, Brazil/East, America/Sao_Paulo, America/Cuiaba, Egypt, Africa/Cairo

DST v10 Updates 2008i Africa/Casablanca, America/Argentina/Buenos_Aires, America/Argentina/Catamarca, America/Argentina/ComodRivadavia, America/Argentina/Cordoba, America/Argentina/Jujuy, America/Argentina/La_Rioja, America/Argentina/Mendoza, America/Argentina/Rio_Gallegos, America/Argentina/San_Juan, America/Argentina/Tucuman, America/Argentina/Ushuaia, America/Buenos_Aires, America/Campo_Grande, America/Catamarca, America/Cordoba, America/Cuiaba, America/Havana, America/Jujuy, America/Mendoza, America/Rosario, America/Santiago, America/Sao_Paulo, Asia/Choibalsan, Asia/Damascus, Asia/Gaza, Asia/Karachi, Brazil/East, Chile/Continental, Chile/EasterIsland, Cuba, Indian/Mauritius, Pacific/Easter.
DST v11 Updates 2009g Africa/Cairo, Africa/Casablanca, Africa/Tunis, America/Adak, America/Anchorage, America/Argentina/Cordoba, America/Argentina/Jujuy, America/Argentina/Mendoza, America/Argentina/Salta, America/Argentina/San_Luis, America/Atka, America/Bogota, America/Cordoba, America/Eirunepe, America/Havana, America/Jujuy, America/Juneau, America/Lima, America/Managua, America/Mendoza, America/Miquelon, America/Nome, America/Noronha, America/Porto_Acre, America/Resolute, America/Rio_Branco, America/Rosario, America/Santiago, America/Thule, America/Yakutat, Antarctica/Palmer, Asia/Amman, Asia/Baghdad, Asia/Baku, Asia/Choibalsan, Asia/Damascus, Asia/Gaza, Asia/Hovd, Asia/Istanbul, Asia/Karachi, Asia/Novosibirsk, Asia/Samarkand, Asia/Tashkent, Asia/Ulaanbaatar, Asia/Ulan_Bator, Brazil/Acre, Brazil/DeNoronha, Chile/Continental, Chile/EasterIsland, Cuba, Egypt, Europe/Chisinau, Europe/Istanbul, Europe/Kaliningrad, Europe/Kiev, Europe/Samara, Europe/Simferopol, Europe/Tiraspol, Europe/Vienna, Europe/Warsaw, Indian/Mauritius, Pacific/Easter, Poland, Turkey, US/Alaska, US/Aleutian
DST v13 Updates 2009s Africa/Cairo, America/Argentina/San_Luis, America/Buenos_Aires, America/Cordoba, America/Catamarca, America/Argentina/Tucuman, Antarctica/Casey, Antarctica/Davis, Antarctica/Mawson, Asia/Hong_Kong, Asia/Karachi, Asia/Gaza, Asia/Damascus, Europe/Samara, Indian/Mauritius, Pacific/Fiji, Pacific/Apia , Egypt, America/Argentina/Buenos_Aires, America/Argentina/Cordoba, America/Argentina/Catamarca, Asia/Dhaka, Hong Kong, NZ-CHAT, America/Rosario, America/Argentina/ComodRivadavia
DST v14 Updates 2010j Africa/Casablanca, Africa/Tunis, America/Argentina/San_Luis, America/Tijuana, America/Santiago, America/Asuncion, Antarctica/Casey, Antarctica/Davis, Asia/Dacca, Asia/Taipei, Asia/Karachi, Asia/Gaza, Asia/Damascus, Asia/Kamchatka, Asia/Anadyr, Europe/Samara, Pacific/Easter,Pacific/Fiji,Pacific/Apia, America/Ensenada,Chile/Continental, Asia/Dhaka, ROC, Chile/EasterIsland, Mexico/BajaNorte
DST v15 Updates 2010o Africa/Cairo, Egypt , America/Bahia_Banderas, Asia/Amman, Asia/Gaza, Europe/Helsinki, Pacific/Fiji, Pacific/Apia, Asia/Hong_Kong, Hongkong, Europe/Mariehamn
DST v16 Updates 2011g Africa/Cairo, Africa/Casablanca, America/Juneau, America/Havana, America/Santiago, Asia/Amman, Atlantic/Stanley, Europe/Istanbul, Pacific/Honolulu, Pacific/Easter, Pacific/Apia, Egypt, Cuba, Chile/Continental, Turkey, US/Hawaii, Chile/EasterIsland, Asia/Istanbul
DST v17 Updates 2011j Africa/Nairobi, Africa/Dar_es_Salaam, Africa/Kampala, America/St_Johns, America/Goose_Bay, America/Resolute, Asia/Yekaterinburg, Asia/Omsk, Asia/Novosibirsk, Asia/Krasnoyarsk, Asia/Irkutsk, Asia/Yakutsk, Asia/Vladivostok, Asia/Magadan, Asia/Kamchatka, Asia/Anadyr, Asia/Sakhalin, America/Metlakatla, Europe/Kaliningrad, Europe/Moscow, Europe/Samara, Europe/Volgograd, Pacific/Apia, Canada/Newfounland, W-SU
DST v18 Updates 2012c Africa/Casablanca, America/Bahia, America/Havana, America/Port-au-Prince, America/Santiago, America/Blanc-Sablon, Antarctica/Casey, Antarctica/Davis, Antarctica/Palmer, Asia/Yerevan, Asia/Gaza, Asia/Damascus, Atlantic/Stanley, Europe/Minsk, Pacific/Easter, Pacific/Fiji, Pacific/Fakaofo, Cuba, Chile/Continental, Chile/EasterIsland
DST v19 Updates 2012j Africa/Tripoli, Africa/Casablanca, America/Bahia, America/Havana, America/Araguaina, Asia/Jerusalem, Asia/Amman, Asia/Gaza, Asia/Hebron, Pacific/Fiji, Pacific/Apia, Pacific/Fakaofo, Libya, Cuba, Asia/Tel_Aviv, Israel
DST v20 Updates 2013c Africa/Casablanca, America/Port-au-Prince, America/Santiago, America/Asuncion, Antarctica/Palmer, Asia/Gaza, Asia/Hebron, Pacific/Easter, Chile/Continental, Chile/EasterIsland
DST v21 Updates 2013e Africa/Casablanca, America/Argentina/San_Luis, Pacific/Fiji, Asia/Jerusalem, Asia/Tel_Aviv, Israel
DST v22 Updates 2014c Africa/Cairo, Africa/Tripoli, Africa/Casablanca, Africa/El_Aaiun, America/Havana, America/Araguaina, America/Porto_Acre, America/Eirunepe, Asia/Jerusalem, Asia/Amman, Asia/Gaza, Asia/Hebron, Europe/Istanbul, Europe/Kiev, Europe/Simferopol, Pacific/Fiji, Egypt, Libya, Cuba, Brazil/Acre, Asia/Tel_Aviv, Turkey, America/Rio_Branco, Israel, Asia/Istanbul
DST v23 Updates 2014f Africa/Cairo, Africa/Casablanca, Africa/El_Aaiun, Asia/Taipei, Asia/Yekaterinburg, Asia/Omsk, Asia/Novosibirsk, Asia/Krasnoyarsk, Asia/Irkutsk, Asia/Yakutsk, Asia/Vladivostok, Asia/Magadan, Asia/Sakhalin, Europe/Kaliningrad, Europe/Moscow, Europe/Simferopol, Europe/Volgograd, Egypt, ROC, W-SU
DST v24 Updates 2015d Africa/Cairo, America/Cancun, America/Grand_Turk, America/Santiago, Antarctica/Palmer, Asia/Dacca, Asia/Hovd, Asia/Ulaanbaatar, Asia/Gaza, Asia/Choibalsan, Asia/Hebron, Europe/Minsk, Pacific/Easter, Pacific/Fiji, Egypt, Jamaica, Chile/Continental, Asia/Dhaka, Asia/Ulan_Bator, Chile/EasterIsland

Actions

IV. Steps for Applying Required Patches

Affected E-Business Suite Release 11i environments must be patched to display the correct time in the affected time zones during the new or changed DST period or after the effect of the new time zone. The following sections describe the steps to patch your environment for the Oracle E-Business Suite and the Oracle Server Technology products.

Step 1: Apply Operating System Patches (Required)

The SYSDATE function (and similar functions) relies on the Operating System (OS), to provide the time. If the OS time is not correct, then SYSDATE will also not provide the correct time. Therefore, users in affected Time Zones should contact their OS vendor to obtain the correct patch to update their operating system or to verify their individual extended DST or extended DST or new time zone requirements.

ProviderWebsite
Microsoft http://www.microsoft.com/
Redhat http://www.redhat.com/
Sun http://www.oracle.com/technetwork/systems/patches/solaris/index.html
HP http://www.hp.com/
IBM http://www.ibm.com/

Step 2: Apply Daylight Savings Time (DST) Patches (required)

2.1 Ensure that your database is running on Oracle 9i or higher

If running a database release earlier than Oracle 9i you must first upgrade your database before applying any DST patch upgrades.

2.2 Apply the Daylight Saving Time DST RDBMS Patches to the Database Tier (Required)

This section provides an overview of the requirements needed to upgrade the DST version on your dtabase tier. For further information and full instruction also follow the Oracle Database DST Note as appropriate to the DST version you are upgrading to in the Daylight Saving Time (DST) and Time Zone Patches Table.

2.2.1. Apply the DST RDBMS Pre-Requisite Patch to your Database Tier (if required)

DST v10 Upgrades:

Unix Users upgrading to DST v10 do not need to apply <Patch 7395472> as this fix is already included in the upgrade <Patch 7580744>. Continue to step 2.2.2.

Windows Server Users must apply an appropriate Windows patch bundle that includes pre-requisite <Patch 7395472>. For further information on the minimum Windows patch bundle required for your database version please see the Oracle Database DST Note as appropriate to the DST version you are upgrading to in the Daylight Saving Time (DST) and Time Zone Patches Table above. Also follow the appropriate Oracle Database DST Note for further information and requirements when upgrading your database tier. For availability of the Windows patch bundles please see <Document 161549.1> Oracle Database Server and Networking Patches for Microsoft Platforms. After the patch bundle has been applied continue to step 2.2.2.

DST v11 and Higher Upgrades:

Unix Users upgrading to DSTv11 or higher must apply pre-requisite <Patch 7695070> if required, see Pre-requisite Patch Exceptions below.

Note: If you are upgrading from DSTv10, and have previously applied <Patch 7395472> to your environment it will be rolled back when you apply <Patch 7695070>.
This is expected behavior because <Patch 7395472> is included in <Patch 7695070>.

Windows Server Users must apply an appropriate Windows that includes <Patch 7695070> if required, see Pre-requisite Patch Exceptions below. For further information on the minimum Windows patch bundle required for your database version, see the Oracle Database DST Note as appropriate to the DST version you are upgrading to. For availability of the Windows patch bundles please see <Document 161549.1> Oracle Database Server and Networking Patches for Microsoft Platforms. If you have previously applied a patch bundle containing this fix there is no need to apply it again.

Pre-requisite Patch Exceptions:

If you are upgrading to a higher DST release and have previously applied pre-requisite <Patch 7695070> you do not need to apply it again.

  • 10g Users running 10.2.0.5 do not need to apply pre-requisite <Patch 7695070> as the fix is already included in this release.
  • 11g Users running 11.2.0.1 or higher do not need to apply pre-requisite <Patch 7695070> as the fix is already included in this release.
  • 12g Users running 12.1.0.1 or higher do not need to apply pre-requisite <Patch 7695070> as the fix is already included in this release.

Continue to step 2.2.2.

2.2.2. Apply the DST RDBMS Upgrade Patch (required)

Apply the Daylight Saving Time (DST) RDBMS upgrade patch as specified in the Daylight Saving Time (DST) and Time Zone Patches Table above to your database tier.

2.2.3. Post-Install Steps for 11g and 12g Users Only (required)

  • 11g users must follow the steps in <Document 977512.1> titled, 'Updating the RDBMS DST version in 11gR2 (11.2.0.1 and up) using DBMS_DST' to activate and use the new DST version files in the database.
  • 12g users must follow the steps in <Document 1509653.1> titled, 'Updating the RDBMS DST version in 12c Release 1 (12.1.0.1 and up) using DBMS_DST' to activate and use the new DST version files in the database.
2.3 Apply the Oracle Java Virtual Machine (OJVM) Time Zone Patch (if required)

Java Stored Procedures are deployed in Oracle, but not managed in Oracle, and in many cases the original Java source code is never loaded into Oracle. There is no simple way to see if you are using Timezones in Java stored procedures from the database.
If your applications use Java stored procedures you should take this up with the vendor/developer of the application to see if the application actually uses timezone information from the OJVM.
If you do require the OJVM patch, please ensure that the Oracle JVM is installed correctly before applying the patch. See <Document 397770.1>, titled, How to Correctly Check if the Oracle JVM is Installed in the Database.
Also see <Document 416860.1>, titled, Testing your Oracle JVM Time Zone Setup, provides a Java Stored Procedure which tells you if time zone data is usable in the OJVM. If it is you can apply the OJVM patch, if it's not then please do NOT apply the OJVM patch. This procedure cannot tell you if the OJVM Timezone data is used!

If required, please apply the OJVM patch as specified in the Daylight Saving Time (DST) and Time Zone Patches Table above. For further information and extra steps required when applying this patch please follow the appropriate Oracle Database DST Note referenced in the table above.

Step 3: Apply Application Server Tier Patches (required)

Note: The Oracle E-Business Suite application tier uses 32-bit code even when running on a 64-bit platform. When applying DST patches to the application tier please use the 32-bit patches.

3.1 Apply the Developer 6i DST Patches to the 8.0.6 ORACLE_HOME (required)

If you are running Developer 6i Patchset 9 (6.0.8.18.x) or earlier, you must first upgrade to Developer 6i Patchset 10 (6.0.8.19.x) or later before applying the Developer 6i Daylight Saving Time (DST) or Time Zone patch. For information about upgrading Developer 6i, please refer to <Document 125767.1> Upgrading Developer 6i with Oracle Applications 11i. (Oracle recommends that all Oracle E-Business Suite customers upgrade to the latest certified Developer 6i patchset).

3.1.1 Apply the Developer 6i DST Pre-Requisite Patch to the 8.0.6 ORACLE_HOME (if required)

If you are upgrading to DST v10 or DST v13 or higher, please apply the Developer 6i pre-requisite patch as specified in the Daylight Saving Time (DST) and Time Zone Patches Table above by following its readme.

Note: There is no need to copy in the timezlrg.dat and timezone.dat files from this patch (Steps 3 and 4 from the patch readme) as you will be installing later versions of these files in Step 3.1.2 below.

Note:After applying the DST Developer 6i pre-requisite patch, either <Patch 7509746> (required for DST v11) or <Patch 9005247> (required for DST v13 and higher), also relink forms by running:

$ORACLE_HOME/forms60/lib make -f ins_forms60w.mk install

Note: If you applied <Patch 9005247> (required for DST v13 and higher) in a previous upgrade, there is no need to apply it again.

3.1.2. Apply the Developer 6i DST Upgrade Patch (required)

Apply the Developer 6i Daylight Saving Time (DST) Upgrade patch as specified in the Daylight Saving Time (DST) and Time Zone Patches Table above to your 8.0.6 ORACLE_HOME.

3.2 Apply the Time Zone Java Fixes

Download and apply the appropriate JDK version on all Oracle Application Middle Tier nodes. If required contact your operating system vendor to obtain the latest JDK version containing the appropriate DST fixes for your platform and Java release. If you do not wish to update your Java version at this time, or the fix is not yet available, please run the appropriate version of the "JDK DST Timezone Update Tool". You are strongly advised to consult your JDK provider for additional information:

For further details on this upgrade, refer to <Document 300482.1> Overview of Using Java with Oracle E-Business Suite Release 11i.

3.3 Apply the latest Plug-in version (Optional)

Oracle recommends that all Oracle E-Business Suite customers upgrade to the latest certified version of Sun JRE native plug-in. The latest version available on either stream is recommended but not required to support Time Zone related changes. For information on upgrading JRE native plug-in, refer to <Document 290807.1> Upgrading Sun JRE with Oracle Applications 11i.
Note: Customers using Oracle Field Service, Oracle Work in Process, Oracle Shop Floor Management, or Oracle Enterprise Asset Management may observe display problems on Gantt charts. You may also observe similar problems with Oracle Client System Analyzer. To fix these issues, upgrade to Jinitiator 1.3.1.26 or higher or JRE native plug-in.

Step 4: Apply E-Business Suite Release 11i Patches (Conditional)

If you are running Release 11.5.10, 11.5.10.CU1, or 11.5.10CU2, review the corresponding sections below.

4.1 Releases 11.5.10 or 11.5.10CU1

If you are running any of the following products, which include extensive support of time zone in Release 11.5.10 and 11.5.10CU1 or, in conjunction with these products, you have enabled User Preferred Time Zone, you must apply the FND and HZ patches indicated below.

Patches

4.2 Release 11.5.10CU2

If you are running Release 11.5.10CU2 and are using User Preferred Time Zone or an Oracle product with extensive time zone support, you must apply the FND and HZ patches below.

Note: If you are relying on Time Zone support in E-Business Suite but, (a) 11.5.10CU2 has not been applied, or (b) you are running 11.5.10 or 11.5.10CU1 for products that are not listed in Section 4.1, your configuration is not supported by Oracle. Oracle recommends that you apply 11.5.10CU2, or disable the profile options described above. The operating system patches, database tier patches, and application server tier patches must still be applied.

V. Consequences of Not Applying These Patches?

If your environment is affected as determined in Section II and you have not applied the patches in Section III, your Oracle Applications environment will not respect the new DST or Time Zone rules. Most Oracle E-Business Suite modules will be impacted by one or more of the following:

  1. User Preferred Time Zone: If enabled at your site, the Date with Time components displayed in interactive user interfaces might be incorrect.
  2. Date Defaulting (SYSDATE): The system generated dates and dates with time component might be incorrect. For dates without time components, the incorrect date might be generated.
  3. Gantt Charts: Others time zone related functionality such as scheduling and representations in Gantt charts will be incorrectly rendered.
  4. Integrated Systems: Unpatched E-Business Suite environments that have been integrated with external systems will process inbound and outbound data with time components incorrectly.

VI. Further Information

Changing Your Server Timezone

Oracle strongly recommends that the Server timezone is not changed on a live Oracle E-Business Suite Database. There is no simple method to ensure that data currently held within the database can be maintained correctly if such a change is made. A requirement to do this would therefore require Oracle Consultancy as it is outside the scope of Oracle Support. For further details please see <Bug 14552703>.

Contacts

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
Details
 I. Daylight Saving Time (DST) and Time Zone Changes
 II. Affected E-Business Suite Environments
 III. Required Patches for Affected E-Business Suite Environments
Actions
 IV. Steps for Applying Required Patches
 V. Consequences of Not Applying These Patches?
 VI. Further Information
Contacts
 VII. Obtaining Support
 VIII. References
 IX. Change Log
References

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