My Oracle Support Banner

Database Errors On Failover (Doc ID 2686778.1)

Last updated on JULY 02, 2020

Applies to:

Oracle Documaker - Version 12.4 and later
Information in this document applies to any platform.


We run GENDAW32.exe behind Docupresentment. We keep these GENDAW32.exe up and running to establish a cache of forms.
These GENDAW32 instances reference our MRL and WIP databases. Those databases are SQLServer and have failover partners.
Traditionally we have used ODBC connections to connect to the database, but recently have switched to using JDBC
with the .bindings file. When using ODBC and our intial setups with JDBC, an established GENDAW32.exe upon failover of the database.
We always noted that the intial transaction after the failover would fail with a database error (for that instance of IDS). We then noted
that subsequent requests through after the initial failure would work fine and connect to the database connection. We had hoped that switching
from ODBC to JDBC would have helped us, but noted it did not. Switching to the .bindings file we noted the use of commons-pool behind the scenes,
and added a validation query to our connection. However, this still did not resolve the issue.

Is there a way to make this work as we expect it, so we do not see any outage in the event of a database failover?


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.