Friday, October 06, 2006

Impact of U.S. Daylight Saving Time Changes in 2007 on peoplesoft

US DST changes may require updating the JRE used in Web/App/Batch servers. More information can be found in these links

http://java.sun.com/developer/technicalArticles/In...

http://www.hp.com/products1/unix/java/DST-US.html

Do you think it will also impact peopletools release as well. I do not see any documents on this on customer connection. Please share your thoughts on this issue.

I think this PeopleSoft Page and associated data stored in PSTIMEZONE and PSDSTTIME must be updated. I have seen one other record PSTZOFFSET which may need to be updated, if you are using this in your environment. The data in this table is not required by peoplesoft and can be used in query to simplify the access to timezone data. This makes the time zone information available in a format that can be easily accessed with SQL. (Exception : May be used by Time and Labor. Check your installation). You may also want to update only for the period 2007 and onwards after applying the updated timezone information.

PeopleTools -> Utilities -> International -> TimeZones and Hit the button Generate Query Offsets and enter the start and end date for which you want to generate the information. This will delete the old data and enter the new data. You may want to update the data only for the year 2007 onwards only.

Here is a link to peoplebooks -> Unserstanding Time Zones

Navigation for PeopleTools 8.4x

PeopleTools -> Utilities -> International -> Time zones
Menu: Utilities
Component: TIMEZONEPNLGRP
Page: TIMEZONEDATA, DSTDATA
Record: PSTIMEZONE, PSDSTTIME

Here is the SQL to update the record.

INSERT INTO PSDSTTIME VALUES ( '2FirstSunNov', 'N', '11', 1, '0', 2, 0, 'First Sunday in Nov, 2:00am' )
INSERT INTO PSDSTTIME VALUES ( '22ndSunMar', 'N', '3', 2, '0', 2, 0, 'Second Sunday in March, 2:00am' )
UPDATE PSTIMEZONE SET DSTSTART='22ndSunMar' WHERE TIMEZONE IN ('AKST','CST','EST','MST','PST');
UPDATE PSTIMEZONE SET DSTEND='2FirstSunNov' WHERE TIMEZONE IN ('AKST','CST','EST','MST','PST');

9 comments:

Tom said...

Thank you for the great info!

Have there been any formal PeopleSoft announcements regarding patches for PeopleTools versions prior to v8.19?

I have found documentation regarding v8.19 and greater, but nothing for previous versions.

Ketan Kothari said...

The Latest PeopleSoft DST Document has been updated to include PeopleTools 7.5 and 7.6. For these releeases, only thing that you may want to apply is tuxedo R502 Rolling patch if you use windows appserver. No Timezone data needs to be updated. Also There is a official resolution 201027921 which describes in detail all the steps that needs to be applied for peoplesoft apps. Here is the link : http://www.urlic.com/psdst
The documents are updated frequently, so keep downloading the new version.

Ketan Kothari said...

You can download the latest version of DST Documents from PeopleSoft ftp site.

ftp.peoplesoft.com
cd /incoming/GSC/DST
userid/password: anonymous/anonymous

Tom said...

Thank you so much!!

Juan Carlos said...

Hey Kothari,

I'm having problems with 2 of my enironments. On the online configurations section, once I click the Generate Query Offsets, input the dates, I get an error occured and get redirected to the PeopleSoft log-in page. Have you encountered this error before?

Thanks

JC

Ketan Kothari said...

You may want to delete the data from PSTZOFFSET. delete from PSTZOFFSET. I have not seen this in my environment.

You may also want to clear the appserver cache and restart the appserver. Make sure to do this in all of your appservers. I suspect some kind of SQL issues.
Check the Appserver Log and you may get more detailed error message. Also Run this for smaller period to test if it works. You can also enable the SQL Trace to see if the error is happening due to any underlying SQL failure.

Juan Carlos said...

Hey Kothari,

I found the resolution to my issue. You are correct in saying that there is a problem with the SQL, but not the SQL itself. It seems that it's trying to select data from the PSDSTTIME table, which, I found out, has been truncated for some reason. By default, Peoplesoft has around 18 DST detail entries under the PSDSTTIME table, but when I checked, it only contains 2 rows of data. I refreshed the table from a DEMO database, and it fixed the issue.

Thanks for your help! Indirectly, your suggestion was a step to find the resolution to my problem.

Juan Carlos said...

Hey Kothari,

I found the resolution to my issue. You are correct in saying that there is a problem with the SQL, but not the SQL itself. It seems that it's trying to select data from the PSDSTTIME table, which, I found out, has been truncated for some reason. By default, Peoplesoft has around 18 DST detail entries under the PSDSTTIME table, but when I checked, it only contains 2 rows of data. I refreshed the table from a DEMO database, and it fixed the issue.

Thanks for your help! Indirectly, your suggestion was a step to find the resolution to my problem.

Juan Carlos said...

Hey Kothari,

I found the resolution to my issue. You are correct in saying that there is a problem with the SQL, but not the SQL itself. It seems that it's trying to select data from the PSDSTTIME table, which, I found out, has been truncated for some reason. By default, Peoplesoft has around 18 DST detail entries under the PSDSTTIME table, but when I checked, it only contains 2 rows of data. I refreshed the table from a DEMO database, and it fixed the issue.

Thanks for your help! Indirectly, your suggestion was a step to find the resolution to my problem.