Focal Point
Error connecting to DB2 data source

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/3071061981

October 04, 2006, 10:49 AM
<michka>
Error connecting to DB2 data source
We have two brand new servers that have WF 7.1.3 installed on them. The data source is DB2. On both machines we have installed the DB2 Client software. One machine works correctly and successfully connects to the DB2 data source, the other keeps giving the same error:


(FOC1400) SQLCODE IS -1 (HEX: FFFFFFFF)
(FOC1488) SQL INTERFACE HAS NOT BEEN INSTALLED OR COULD NOT BE INITIALIZED
(FOC1400) SQLCODE IS -1 (HEX: FFFFFFFF)
(FOC1488) SQL INTERFACE HAS NOT BEEN INSTALLED OR COULD NOT BE INITIALIZED
(FOC1479) ERROR CONNECTING TO SQL DATABASE


Both machines are running the same security level. As far as I can both machines have the same configuration setups (edasprof.prf, etc..), yet one works and the other doesn't.

Does anyone have a suggestion ?
October 05, 2006, 10:40 AM
Bryan Klimek
What platform is this on? You say the DB2 client is installed. Are you able to use the DB2 client command line interface and connect to the DB2 subsystem?

Bryan Klimek
Mayo Clinic
October 05, 2006, 06:52 PM
newtofocus
Your best bet is turn the traces on to see what is going on.


WF7.1.4 Prod/Test, MRE, self serve, DM
October 11, 2006, 11:50 AM
Kerry
Hi michka,

Has this issue been resolved? Did the suggestion of turning on the traces help you in finding the cause of the proble?

I ran some search on Information Builders' online documents and came across the following topics which may be of interest:

Resolving FOC1400, FOC1488 and FOC1479 Errors for the DB2 Adapter

Cannot create DB2 Data Adapter on Server Console

You will need to have an InfoResponse userID/password to access these documents.

Hope this helps. Smiler

Cheers,

Kerry


Kerry Zhan
Focal Point Moderator
Information Builders, Inc.
October 12, 2006, 01:58 PM
<michka>
Thanks to everyone for the suggestions. After trying several different options with no luck, we brought the DB2 administrator in to look at it. Turns out there was a problem with the DB2 Client installation (security/permissions). He removed, then re-installed the software and we are now able to connect and retrieve data.