You are viewing limited content. For full access, please sign in.

Question

Question

Issues with Oracle database lookup from Workflow?

asked on January 29, 2018

Does anyone have experience of successfully configuring workflow (10.2) to connect to an Oracle data source?

I was trying to set this up the other day for a client and the results were very mixed. It seems to be an issue related to 32 bit and 64 bit drivers but we get differing causes of failure with each.

Using the 64 bit Oracle Client (11.2) and the Oracle ODBC driver, the list of tables/views fails to load due to an arithmetic overflow error. We switched to the 32 bit Oracle client and in design time mode (i.e. testing the query using sample data) it makes the connection and returns the x number of rows. However, at runtime we get an error stating that the Oracle version must be version 8.1.7 or higher and the lookup fails.

Workflow itself is the 64 bit version (all the installed files are in Program Files\Laserfiche rather than Program Files (x86)\Laserfiche. 

Does anyone have any advice on which versions of which components should work? I've tried using the Oracle ODBC dirver only so far, not sure about the ODP driver, or whether we should/could install the Oracle Data Access components?

 

Any advice appreciated!
 

0 0

Replies

replied on January 29, 2018

We have always used the Direct/ODP option for connecting to data sources. It may require configuring the TNS Names file. Its been pretty bullet proof for us.

We are running LF/WF 9.1.1 and the Oracle 12 client. We used the 11.2 client previously and it worked as well.

1 0
replied on January 29, 2018

Please open a support case for the arithmetic overflow error. The CPU architecture of Workflow needs to match the CPU architecture of the ODBC driver used. A 64-bit Workflow server will not be able to use a 32-bit driver.

0 0
replied on January 31, 2018

Thanks both for your input. We'll proceed with the 64bit driver in the first instance - the client are due to migrate to a new server in the very near future so we will wait until then as we will have more control on what we can install. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.