As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
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.
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?
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.