1.) Depends on your definition of properly set. Timezone is set as GMT - Dublin, Edinburgh etc with automatic adjustments for Daylight Savings. We are in Ireland. The Actual time is synched with timeserver time.windows.com
2.) Underlying OS on our Teradata Servers is Windows Server 2003. My PC would be synched with Domain at logon, not sure what master time server is used for this.
Remembering that the consistent issue is with the day of month element only have we anymore ideas?
When I run the below statements in Queryman the 1st gives me a wrong date and the 2nd one is correct. When my colleagues do the same they get 2 correct dates. When I run them in BTEQ they are both correct. I'm not sure if this causes the underlying issue as it clouds the issue further. I am going to reboot & have coffee just to be sure.
SELECT CAST(CURRENT_TIME(2) AS TIMESTAMP(2)); -- 2007-09-29 15:47:36.94 SELECT CAST(CURRENT_TIMESTAMP(2) AS TIMESTAMP(2)); -- 2007-10-03 15:47:37.06
"CURRENT_DATE, CURRENT_TIME, and CURRENT_TIMESTAMP do not return the correct value for the default session time zone. Instead, they returned the year, month, day, hour, and minute having the same value no matter what the session time zone is. Therefore, CURRENT_TIME and CURRENT_TIMESTAMP are only correct when the session time zone is equal to the time zone specified in DBSControl."
If this problem impacts your application, contact the Teradata Support Center for fix availability info.