$LastRunTime variable time shifted to different... Skip navigation

$LastRunTime variable time shifted to different timezones

score 45
You have not voted. Active

For several of our interfaces, we have to timeshift the $LastRunTime variable back to our local timezone in order to effectively use a Last_Update_Date comparison on the source...


The problem is that Informatica provides the time in GMT, but our database has the times in our local timezone.


For now, we are adding the required number of hours to the variable to get the correct time in our local timezone.


The REAL problem is that our local timezone changes twice a year to accomodate daylight savings, so we would have to change all of our interfaces twice a year to add an extra hour, then 6 months later remove that extra hour...


It would be great if we could have the $LastRunTime variable providing the $LastRunTime in a specified timezone, so we dont have to do any of this workaround effort...


Vote history