BigAdmin: DST: Daylight Saving Time Changes (2008)

Oracle

Submit Content | Check BigAdmin Bucks

Software

<< Back to Software

DST Impacts

Testing tip: 03/11/07 through 04/02/07 and 10/29/07 through 11/04/07 are the periods during which the problem is visible. Outside of those periods, there is no visibility since the computation is the right one.

http://www.hp.com/products1/unix/java/DST-US.html
Timezone Updater Tool
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102775-1
For JRE version 1.4 or later get the tzupdatertool from the from Java SE download page.

Products - Versions

Java version - OS used - how time is used

Need restart?

OS patches required?

Impact if no action taken

Global status

Products - Versions

Java version - OS used - how time is used

Need restart?

OS patches required?

Impact if no action taken

Global status

DSEE Directory Server 6.0

All pfs, ZIP and PKG, shipped with version > 1.5_06 but HP 1.5_03, however HP's JVM is based on Sun's 1.5_06, which fixes the issue.
Time functions rely on OS

n/a

Yes

Issue with logs and password expiration if system not patched

System patch required

DSEE Directory Proxy Server 6.0

All pfs, ZIP and PKG, shipped with version > 1.5_06 but HP 1.5_03, however HP's JVM is based on Sun's 1.5_06, which fixes the issue.
Time use in numeric form only in the core server

n/a

Recommendation should be to patch the OS anyway

DSEE Identity Synchronization for Windows 6.0

ISW Core relies on 1.5_06, which is ok
Admin Server, needed and delivered by ISW, bundles JVM 1.4.2_03

Yes for Admin Server

Logging and Account Lockout are impacted

tzupdate to be RNoted Recommendation should be to patch the OS anyway

DSEE Directory Editor 1.0/6.0

No JVM shipped, so updated JVM has to be recommended

Yes

Password Expiration Remaining time calculation error

JVM update has to be recommended
OS to be patched anyway

Admin Server 5.2
Console

Shipped with 1.4.2_03 - Will be fixed by Java upgrade or tzupdater tool

Console restart needed

Console Log viewer displays incorrect date/time

tzupdate to be recommended
OS to be patched anyway

Directory Server 5.2

Impact on Console : see Admin Server 5.2
Core server impact

n/a

Yes

Issue with logs and password expiration if system not patched

Steps :

Download and decompress tzupdater tool in
Execute the command:
{SERVER_ROOT}/bin/base/jre/bin/java -jar {TZUPDATERDIR}/tzupdater.jar -u

Note: To check whether a JRE is patched, execute the command:

{SERVER_ROOT}/bin/base/jre/bin/java -jar {TZUPDATERDIR}/tzupdater.jar -t

This will execute tests on the JRE distribution. No output and, exit code 0, means JRE is patched. OS patches need to be applied.

Directory Proxy Server 5.2

Impact on Console : see Admin Server 5.2
Core server impact

n/a

Yes

Logs issue

System patch required

Identity Synchronization for Windows 1.0 SP1

1.4 was required when the product was shipped

Yes

Logging and Account Lockout are impacted

tzupdate to be recommended
OS to be patched anyway

Admin Server 5.1
Console

1.3.1_01 - Will be fixed by Java upgrade

Console restart needed

Console Log viewer displays incorrect date/time

Steps:

Stop Admin Console
Download elf-extracting JRE 1.3.1_19 (e.g. JRE )
Rename {DS_INSTALLDIR}/bin/base/jre to {DS_INSTALLDIR}/bin/base/jre.ORIG
Install JRE (e.g for solaris : Execute:
sh ./j2re-1_3_1_19-solaris-sparc.sh )
Copy or link the JRE in {DS_INSTALLDIR}/bin/base/
Restart Admin Console

Directory Server 5.1

Impact on Console : see Admin Server 5.1
Core server impact

n/a

Yes

Issue with logs and password expiration if system not patched

System patch required

LDAPJDK

No JVM shipped, so updated JVM has to be recommended	Yes	No	Erroneous data returned to applications using that lib	JVM update has to be recommended OS to be patched anyway
LDAPCSDK	Not relying on JVM	n/a	Yes	Erroneous data returned to applications using that lib	System patch required