Hi,
We have a problem creating a connection to an Oracle 10g database.
I am not sure if the length of the connection name FRTRACKING_PCTREAD is too long? (18 characters too long?)

We're not sure whether the database's environment may cause the inability to connect.
We do have another connection that can connect successfully to another Oracle 10g db but that db is on a different OS.

I am going to put the Oracle 10g softwares version here at the end of the text.

Does anyone know if it is the OS that is making the difference between why one connection works and the other cannot even be created?
Thank you.

Oracle 10g softwares connection that works in WF
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for Solaris: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production

Oracle 10g softwares connection that cannot even be created
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 64-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production

This message has been edited. Last edited by: Kerry,

The only thing that makes a difference is the version of the Oracle client on the WebFocus server box.

What you can use is determined by the OS that you are running on and the Version of WebFocus that you are using.

For 5.3.2 on AIX you should probably have a 9.2.0 client even though you are connecting to a 10G Oracle database.

Naturally the Oracle instance must be correctly configured in the TNSNAMES.ora
for the client.

The connection name is simply a logical name associated with the adapter configuration
and can be anything you like, it has no relationship to the actual target DB other than usually using a descriptive name.

If you have a configured connection that works what length is it’s name?

It is very simple to change the name to find out if length is the actual problem.

Eliminate that issue and you will then be able to see if the connection works, but if it doesn’t you should at least get some valid error messages

Could it not also be a question of oracle being 64 bit and webfocus 32 bit?
If so, that would imply that it does not really have any influence on the solaris setup, but that it would mean windows to choke.
I do seem to remember that if you use a 64 bit oracle that you would then have to interface with it using the highest available version of the 32 bit oracle client on windows.
But I might be quite wrong here. Anyway, it's worth investigating.

Hi JG,
The length of that connection name that works with the Ora10g is 11 characters. I then changed it to be 18 chars like the one I'm trying to create now and tested it and it gave me the error:
(FOC1400) SQLCODE IS 12154 (HEX: 00002F7A)
(FOC1394) CONNECT FAILURE
: ORA-12154: TNS:could not resolve service name
(FOC1405) SQL PREPARE ERROR.

I'm pretty sure for us, I have to make the connection name equal the entry in the .ora file otherwise it would not work. It works when I changed it back to the original name that is the same as in the .ora file. Maybe it could be the 64-bit Windows version. The dba is checking some stuff for me right now. Thanks.

We are uisng Oracle Client 8.1.7 on the Dev BI Server not Oracle 92 Client. That's because the AIX V5.1 we have cannot support a higher version than Java 1.4.2 Thus, we have to sue Oracle Client 817. Thanks.

Sorry I meant use Oracle Client 817 not "sue".

Hi Adrian,

Can you please test by adding a new entry in tnsnames that is 8 characters or less and then reconfigure the adapter? If that does not work either and you would like to pursue further, please open a case with Information Builders' Customer Support Services so that it can be tested in-house. To open a case, you may either call at 1-800-736-6130, or access online at InfoResponse.

Cheers,

Kerry

Hi Kerry,
I cannot go into the tnsnames.ora file for our Dev BI Server and simply change it. I do not have access. Only the dba can do it for us.
We do have a tns entry that is longer than 8 characters for a Ora 10g connection and it works fine. The project manager here has requetsed that a port (1521) be opened for us.
Once that port is opened then I will try to connect again to the Ora 10g db.
I have already requested that the ticket be on hold thru Bj Stepien. Thanks.