Here in Russia the daylight saving rules has changed last year, we now no longer step back one hour in autumn. That time change used to happen at last weekend in october. We updated timezone info in server, in java JDK installation, but our PPMC server changed it's internal clock one hour backwards. All requests now created with creation_date one hour before actual creation.
What could it be? Is there anyone with this issue?
Verify the date settings on your application servers and on your database servers. Try running the query 'select sysdate from dual' on your database. We had strange things happen with request dates when the clock on the database server was not synchronized with the rest of the world.
I've applied all necessary timezone patches, and checked: system time at server ("date" command from console) - correct, time at oracle instance (select sysdate from dual) - correct, time at PPM Java machine (wrote a short program which prints current time to console) - time is correct. And surprisingly time is incorrect only in Request management subsistem, when one creates a request it goes one hour in the past, but if one creates a task - time is correct! That's a miracle!
- on the servers (DB and PPM) you should check the timezone setting - it is possible that these servers are set up on a different time zone. I have seen it happening especially for UNIX servers that are not in sync with the AD time server;
- check the settings for the clients' workstations.
let us know if this helps.
--remember to kudos people who helped solve your problem