05-09-2024 03:58 PM
Hi all - We're preparing to move (IPUP) from EP3 to OnBase 24.1 and in the documentation there's a recommendation which I haven't seen before for Oracle clients (we've been using OnBase on Oracle since version 13).
Specifically, setting the "Bind Timestamp to Date" Oracle ODBC Client/Driver setting for the DSN. Oracle's documentation indicates that the function "force the Oracle ODBC Driver to bind SQL_TIMESTAMP
parameters as the Oracle DATE
type instead of as the Oracle TIMESTAMP
type (the default)."
So - what are the implications of doing this (changing the ODBC configuration to map to a DATE field rather than the current default unchecked setting for Oracle 12c clients) as part of an upgrade?
We are just now upgrading from Oracle 12c to 19c on the database side (doing this before the upgrade to 24.1 later this year), and are planning on leaving our current Thick clients and servers using ODBC on the 12c client and only planning the push to Oracle 19c clients (with this option, as needed) for when we build the servers and update the Thick Client installs.
Thanks!
Ken Piper
Systems Administrator
Information Technology Services (ITS)
San Francisco State University
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.