I have two Windows 7 64 bit machines A and B. In Machine A, BI 4 Server is installed and in Machine B, BI 4 Client tools are installed.
There are reports based on Oracle database that are not running in BI Launcpad. They are throwing TNS Error but the reports are running fine in B Machine Rich Client. In A and B, both 32 bit and 64 bit Oracle is installed and the TNSNAMES.ORA file is updated so I am not understanding why the reports are not running in Launchpad.
Another issue is that in my VD which is Windows 7 32 bit, the reports are throwing TNS Error in Rich Client as well. Oracle 32 bit is installed on my VD and tnsnames.ora file is updated.
I know there is some issue happening because of this 32 bit and 64 bit which I am not aware. Could someone help please.
On your server, do a TNSPing to the database from BOTH the 32 and 64 bit Oracle homes. You can tell which one you’ve executed via the first line of the output:
TNS Ping Utility for 32-bit Windows: Version 11.2.0.1.0 - Production on 13-SEP-2016 11:08:49
I’ll bet that the 64-bit Oracle home doesn’t have the full tnsnames.ora.
Also check sqlnet.ora on both; it’s possible that they have different default names/zones.
I have synced the sqlnet.ora file but still I am getting error. Oracle is installed in the server and the tnsnames.ora file is up to date but still getting “Database error: ORA-12154: TNS could not resolve the connect identifier specified. (IES 10901)(Error: INF)”.
Can there be any other reason why this issue is popping up?
No, you need to use the database instance name, or the alias - the exact same name that’s used in the universe connection.
The error that you’re getting indicates that either the Oracle client can’t find the TNSNames.ora file, or the file doesn’t contain a reference to the database (or the reference is wrong). TNSPing will use the tnsnames.ora file to look up the database name. If the 32-bit tnsping works but the 64-bit tnsfails, then that’s good evidence that the tnsnames.ora file in the 64-bit client’s directory is the problem.
Your first test did not actually use the 32-bit client. You were in the client_6 directory but should have been in client_6\bin.
Although both of your tests used the 64-bit client, they were both successful, and WIReportServer uses the 64-bit client. So that’s about all I can suggest for debugging tips. The only other thing I can possibly think of is that the service account that the SIA runs as does not have full access to the Oracle directory. You might need to have an Oracle DBA look at the client configuration.
(BOB member since 2002-08-15)
(BOB member since 2002-08-29)