[sohail malik]

We have been using ERV with JDBC/oracle for something like 3 years. We have a large collection of web apps and and integration processes using linux/java/jdbc.

The planned retirement of the Oracle connection for ERV is troubling. Especially since there is no alternate JDBC driver offered and no apparent plan to do so.

I have filed an enhancement request as suggested but is seems odd to ask for an enhancement when the oracle client connection has been an established and documented feature many years.

It seems like a migration plan other than “use windows or file an enhancement request” is needed. Is this in the works?

For our purposes we just require JDBC based and the chance to test it BEFORE the oracle driver is retired.
This is a cached copy. Click here to see the original post.

[jtannone]

RE: Oracle Connection Retirement

Is there a definitive date for retirement on this? I’ve heard rumblings of “End of Year” but nothing concrete from NetSuite.

[mhuffman]

There isn’t a definite date yet to deprecate the old Enterprise Reporting feature, but we will send out a notification at least a couple of months in advance to allow time to transition your current setup and queries.

We don’t have plans to offer a non-Windows/JDBC driver for the new ODBC views in the immediate future, though we will certainly monitor how much demand exists for this functionality. I apologize for any inconvenience this causes to prior users of the Enterprise Reporting feature.

[sohail malik]

RE: Oracle Connection Retirement

Is the OpenRDA ODBC Driver for UNIX an option for us or is there something that precludes connection with something other than NetSuite provided driver?

Given we’d have to shell out the $’s, but is it possible?

[mhuffman]

A proprietary license key is required on both the server and clients for the OBDB connection to function. That is why the NetSuite driver is required.

[Author]

Posts