Incorrect values might be read from a Teradata TIMESTAMP field when you use a SAS Real-Time Decision Manager data-process node for a decision campaign. Time-zone information is not accounted for correctly. This issue occurs most often when the database time-zone setting, the user time zone, and the Decision Services time zone differ.

There is no workaround for this issue. Instead, you might consider writing a custom DS2 process to read datetime values from Teradata.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Note: Datetime values that are inserted into Teradata by using a data process might be incorrect also. For details, see SAS Note 64031, "Incorrect datetime values might be inserted into the Teradata database when you use a data process in SAS^® Real-Time Decision Manager."

After applying the hot fix for this issue, add the sasds.jdbc.gio.detectTeradata JVM option to every server in your SASServer7 cluster and set it to true. In UNIX operating environments, you set JVM options in the setenv.sh file that resides in SAS-configuration-directory/LevN/Web/WebAppServer/SASServer7_N/bin/. In Microsoft Windows operating environments, you set JVM options in the wrapper.conf file that resides in SAS-configuration-directory\LevN\Web\WebAppServer\SASServer7_N\conf\.

Operating System and Release Information

A fix for this issue for SAS Decision Services 6.4_M1 is available at:

A fix for this issue for SAS Decision Services 6.4 is available at: