Last updated on AUGUST 03, 2016
Applies to:Oracle Rdb Server on OpenVMS - Version 6.0 and later
HP OpenVMS VAX
HP OpenVMS Alpha
HP OpenVMS Itanium
When using SQLMOD to insert a program passed character string that represents an Oracle Rdb TIMESTAMP(2) datatype, unexpected date results occur if the corresponding SQLMOD parameter is declared as a TIMESTAMP(2) datatype.
For example, consider the following extract of a FORTRAN variable declaration, assignment and call to the following SQLMOD procedure:
The resulting date ends up being stored as "1864-03-24 17:27:03.76" instead of the passed value of "1990-2-13 11:54:30.00".
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms