Oracle Client Help

[fmrock]

Hey everyone, I thought I would post this here even though I know its not exactly a problem with Oracle.

If you look on page 18 of this document It says
---------------------------------
Oracle connectivity issues

If you are installing Crystal Reports Server 2008 V1 on a 64-bit Windows platform, Oracle database connectivity issues may occur. If Crystal Reports Server 2008 V1 is installed to a location that contains brackets in the folder path, for example, C:\Program Files (x86)\, it will be unable to connect to an Oracle database. Certain Oracle database clients such as version 10.2.0.2 or 10.1.0.2, may not function properly with any application that has brackets in its folder path. When installing Crystal Reports Server 2008 V1, select an installation path that does not contain brackets, such as C:\Program Files x86\ or contact Oracle support for an updated database client.

We are having this exact problem trying to get our Cystal reports server using crystal reports that use TNS name to connect to Oracle.

If anyone has run into a similar problem.. or could think of anything we could try.. we are at our wits end.

Thanks

 

[LKBrwnDBA]

Unfortunately the "Program Files (x86)" directory is the standard location for the 32 bit software on Server 2008 OS.

But on the other hand, you could install the 64 bit client.
-- OR --
Try to install the Oracle 32bit client on some other path like (C:\oracle)??

Good luck!



----------------------------------------------------------------------------
The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb

 

[LKBrwnDBA]

I meant:
-- OR --
Try to install the Crystal reports 32bit on some other path...


----------------------------------------------------------------------------
The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb

 

[CRoberts]

Oracle client installation can be surprisingly complex, but not really difficult once dealt with.

Be consistent between the database and client platforms. So, if the client box is 64 bit then the Oracle client should be also. If the Oracle database is 10g then client should be be at least 10g (or higher, why not its free). The installation normally picks a good Oracle base (c:\oracle is good) and Oracle Home (Note, the Windows registry is updated by the Oracle client). However, Oracle 11R2 is difference. I personally always manually set the base to C:\oracle for 11r2 and then the Oracle home is good to go.

Windows Xp and Windows 7 are a pain in so far as privileges go, they don't inherent very well. Be sure to made grants if another account is involved. Once the Oracle base and Home are defined properly, then problems with brackets, braces and spaces (Oracle hates paths with spaces)are eliminated.

The client installation provides several choices (Run time, Custom, etc). A custom install is needed if ODBC, ODP (Oracles extensions for .NET) and even JDBC drivers are needed. I load all of these just in case. Crystal at one time (10 years ago) required ODBC. If you must pick an ODBC or ODP driver, always pick the Oracle one. The MS drivers for Oracle in many cases fail when used. An Oracle Odbc provides a test button, great item. Remember that ODBC or ODP are a layer over the basic Oracle (OCI) client software.

If you are going to use tnsnames, test your entries using Tnsping. However, you do not even need a tnsnames.ora file if you choose to use EZCONNECT method of connection. See the web for info on this method to bypass the tnsnames.ora file. Tnsping works with EZCONNECT also. Don't ignore the other configuration file, Sqlnet.ora. Here you can set up tracing or specify the EZCONNECT and so on.

So, there are a number of options that can be used to connect Oracle to an application (COTS or not). If the basic Oracle client just is not working with Crystal, then use ODBC as a broker.