ODBC Setup Error

[pavandyke]

I have Crystal Reports XI Release 2 installed on a PC. The operating system is Windows XP. I am trying to setup an ODBC datasource using the DataDirect 5.1 Drivers (CR Oracle ODBC Driver 5.1) to make a connection to an Oracle data base. I have downloaded and installed the ODBC driver but when I try to add a new data source I get the following error message: "The setup routines for the CR Oracle ODBC Driver 5.1 ODBC Driver could not be loaded due to system error code 126". I click the OK button and another error appears "Could not load the setup or translator library". I encounter the same problem installing on a Windows 2003 server machine.
Has anyone encountered this problem before with Crystal XI Release 2?

 

[synapsevampire]

Why are you using that driver?

Just use the native connectivity listed under Create New Connection->Oracle Server.

And you must have an Oracle client installed first.

-k

 

[pavandyke]

We are using that driver for two different reasons. WE are currently using Crystal 10 and our database was just converted to Oracle 10. I was doing research to determine what issues we might encounter when we migrate to XI when I discovered this problem. We had been using Oracle's ODBC driver but response time went from seconds to in many cases minutes until we converted the reports to using Crystal's ODBC driver (version 4.2 of the DataDirect driver which works great). We discovered this in our preliminary testing of the Oracle 10 database. A number of our reports are actually scheduled or run from a VB.NET or VB 6 application and I am uncertain how to make the connection to the report programmatically using a native Oracle connection.

 

[pavandyke]

Thanks synapsevampire. I was able to get the modified database connection code from Business Objects tech support for a native connection. Now there is no need to deploy these Crystal ODBC drivers. The reports run great using the native connection.

 

[synapsevampire]

Good to hear, and no ODBC connections required now.

I believe that the crystal supplied ODBC drivers go away in XI anyway...

-k

 

[pavandyke]

They don't actually go away. It is just that they are a separate stand alone installation in XI. However, as I found out there are definitely issues with actually getting an ODBC data source set up using it.

 

[synapsevampire]

Ahhh, you can still get them, good to know.

Last I tested the Oracle ODBC drivers were almost as fast as the native in CR XI.

The CR ODBC was always MUCH slower than native connectivity, so you should be enjoying increased performance now as well.

-k

 

[pavandyke]

It is strange how these things work. Up until the point where we converted our database to Oracle 10G from 9I we had almost always used the Oracle ODBC driver. Since that "upgrade" we have had a number of reports where execution time went from seconds to minutes and the users are none too happy. Most of those we converted to Crystal's ODBC driver and they were back to normal execution time. Now we are running into the deployment issue of the Crystal ODBC driver to machines that don't have Crystal installed on them. So far the native connection works fine for the apps that are being worked on. Hopefully it will continue. Thanks for directing me down the right path here.

 

[synapsevampire]

Weird.

It was never suggested that you use the Oracle ODBC drivers, in fact the reverse in older versions of CR.

One problem is it would return the wrong data (I demonstrated this at Standard and Poors in what they were usijng as live reports a number of years ago).

I'd guess that you've been doing the same thing unwittingly.

They're not off by much, just a bit...

-k

 

[Turkbear]

Hi,
Just a note on the newest versions of the ODBC drivers from Business Objects..The DataDirect wire-protocol drivers have the advantage of not needing to be installed on a machine with Oracle client software installed...They connect directly to ( actually, through) the listener on the database server..

There may be other issues, but performance should be at least as fast, if not faster, than with an Oracle Client ( SqlNet) connection...






To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[pavandyke]

I tried the Wire Protocol Driver but got the same error that started this whole thread in the first place. So unless Business Objects or some of you good folks here on Tek-Tips can help resolve that problem, I think the native Oracle connection is the only viable solution at this point.

 

[Turkbear]

Hi,
Just to confirm, because there are 2 versions of the DataDirect 5.1 drivers, are you sure you specified the Wire Protocol (CR Oracle Wire Protocol ODBC Driver 5.1) version and not the 'standard' (CR Oracle ODBC Driver 5.1) one?





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[pavandyke]

I have both drivers installed and ran into the same error with both. Originally I had installed the ODBC driver for Oracle, for XML and for text as those are three that we have found use for at various times. After the errors and no resolution from Business Objects I went back and installed the Wire Protocol driver and got the same error.

 

[rdharmar]

Did you find a solution to this Pavandyke? I have the exact same problem.

 

[pavandyke]

rdharmar,

No I have not found a solution yet (other than changing to use a native Oracle connection). The Oracle DBA today suggested that I contact DataDirect to see if their driver supports Oracle 10. I have not had an opportunity to do that yet.